SWARN / INTEGRATION ROADMAP
See where customer data moves after the sale.
A bill becomes a customer record. A spreadsheet becomes a message list. SWARN is being built to show the hand-offs your team has to check when a customer changes a choice. These provider connections are planned, not available today.
Many tools.
One decision to trace.
Illustrative architecture · Provider names are independent third-party examples
Provider names identify independent third-party tools. No vendor partnership is implied; no working connection is offered on this site.
BUILT AROUND BUSINESS JOBS
Where customer data travels.
These categories describe common jobs, not a measured ranking of the most-used providers. All examples are currently being built.
Accounting and billing
Understand where customer and invoice records begin.
An invoice or contact import does not prove permission for another purpose.
- TallyPrimeBeing built — not available yetStatus checked 2026-09-27
- Vyapar CSVBeing built — not available yetStatus checked 2026-09-27
- BUSYBeing built — not available yetStatus checked 2026-09-27
CRM and customer records
Keep the customer record and its stated purpose together.
A CRM record alone is not a complete consent record.
- Zoho CRMBeing built — not available yetStatus checked 2026-09-27
Spreadsheets and productivity
Find the lists that teams use outside their main systems.
Spreadsheet rows can be copied; a change in one sheet does not update every copy.
- Google SheetsBeing built — not available yetStatus checked 2026-09-27
Payments
Connect a transaction context to the purposes that follow it.
A payment receipt and an optional marketing choice are separate events.
- RazorpayBeing built — not available yetStatus checked 2026-09-27
Commerce
Trace customer touchpoints in online ordering and fulfilment.
A storefront action does not show that every downstream system acknowledged a later change.
- ShopifyBeing built — not available yetStatus checked 2026-09-27
- WooCommerceBeing built — not available yetStatus checked 2026-09-27
Messaging
Review how customer communication requests reach messaging tools.
A request sent to a channel can remain pending or require manual follow-up.
- WhatsApp Business PlatformBeing built — not available yetStatus checked 2026-09-27
THE INTENDED WORKFLOW
From a business tool to a reviewable action.
This describes the product direction. It does not make a provider connection available.
- 01
Choose a source
Identify the business tool and the data flow you need to understand.
- 02
Review purpose and fields
Check why each field is needed before mapping it across systems.
- 03
Create a SWARN record
Keep the notice version, choice, source and event distinct in a planned record.
- 04
Send an allowed action
Only a verified connection could later send a permitted downstream change.
- 05
Check acknowledgement
Show what was confirmed and what is still pending or needs manual follow-up.
Contact import is not consent. A copied contact does not supply a purpose-specific choice.
Withdrawal is not erasure. A recorded request does not prove every downstream copy was deleted.
Pending stays pending. A sent action may need manual follow-up before anyone can claim acknowledgement.
WHAT YOU CAN USE TODAY
Explore the engineering evidence while connections are being built.
DPDPHQ's existing architecture, controls, patterns and source notes remain available as educational material. They do not certify a product or a business.
Open the engineering library