How do you connect a CRM with Shopify, marketplaces and your ERP?
A practical integration plan for D2C brands linking CRM, Shopify, marketplaces, couriers and ERP: which system owns what data, and how to avoid sync problems.
Anadoris Digital · · 4 min read

A growing D2C brand usually runs several systems: a store platform such as Shopify, one or more marketplaces, a courier aggregator, an accounting or ERP system for stock and invoices, a WhatsApp provider and a CRM. Each holds part of the customer story. Connecting them is what turns a CRM from an address book into a useful working tool.
Done carelessly, integrations create duplicates, overwrite good data and break quietly. Here is a practical way to plan them.
Decide which system owns what
Before connecting anything, write a simple table of data types and their owning system. The owner is where the data is created and corrected; other systems receive copies.
- Store platform: D2C orders, customer accounts, addresses, product catalogue for the site.
- Marketplaces: marketplace orders and their status, within each platform’s data limits.
- ERP or accounting: stock levels, invoices, payments, B2B balances, cost data.
- Courier system: shipment status, delivery attempts and NDRs.
- CRM: conversations, tickets, lead and deal stages, tasks, notes, marketing consent and segments.
When two systems both need to edit the same field, such as a phone number, pick one as the owner and push changes from it.
Write the table down and share it with everyone who touches these systems, including agencies and freelancers. Many sync problems start when someone edits a customer address in the CRM, the store overwrites it on the next sync, and the courier ships to the old address. A shared rule prevents that kind of quiet error.
Use a shared customer key
Every connected system needs a way to recognise the same customer. In India the normalised mobile number usually works best for D2C, with email as a secondary key. For B2B accounts, the GSTIN or an account code works better. Agree the format once and make every integration look up existing records before creating new ones.
Connect in order of value
- Store to CRM: customers and orders, including refunds and cancellations.
- WhatsApp to CRM: conversations attached to customer records.
- Courier to CRM: delivery status and NDRs as tasks.
- ERP to CRM: invoices, balances and stock visibility for B2B accounts.
- Marketplaces to CRM: order data where allowed, linked to identified customers.
- CRM to marketing tools: segments and consent for campaigns.
Get each connection stable and checked before adding the next. Several half-working integrations are worse than two reliable ones.
Think about history as well as new data. When you first connect the store, decide how far back to import orders. Enough history to calculate repeat behaviour and segments is useful; importing years of test orders and cancelled carts is not. Clean the history before importing rather than trying to fix it inside the CRM afterwards. Test imports on a small batch first and check a few customers by hand.
Choose the integration method
Options include native integrations built by the CRM or store vendor, marketplace apps from third parties, automation platforms that connect tools without code, and custom connectors built on each system’s API. Native and well-supported apps are easiest to maintain. Custom connectors give the most control and suit workflows such as linking wholesale orders to ERP stock, but need ongoing ownership as APIs change.
Whichever method you use, decide how often each sync runs. Order and conversation data usually needs to be close to real time so the team sees current information when a customer messages. Stock and invoice data may be fine every few hours. B2B balances might sync daily. Matching frequency to need keeps integrations simpler and cheaper to run.
Monitor integrations like any other system
Integrations fail quietly: an expired token, a changed API, a field renamed by a colleague. Set up simple monitoring. Each day or week, compare order counts in the store and the CRM, check for sync errors, and alert someone when a connection stops. Keep a short document listing every integration, what it syncs, who owns it and how to reconnect it.
Integration checklist
- Data ownership table agreed and shared.
- Normalised mobile number as the D2C customer key; GSTIN or code for B2B.
- Integrations update existing records instead of creating duplicates.
- Refunds, cancellations and returns sync, not just new orders.
- Consent and opt-outs flow to every sending tool.
- Daily or weekly reconciliation of record counts.
- Integration list with owners and reconnection steps.
Marketplaces restrict how seller data and buyer information may be used. Check each platform’s current terms before importing marketplace data into your CRM or using it for marketing.
Where to start
- Write the data ownership table for your current systems.
- Connect store orders and WhatsApp to the CRM first.
- Add courier status next so COD and NDR work moves into the CRM.
- Bring in ERP data for B2B accounts once the D2C side is stable.
Anadoris Digital builds CRM, store, courier and ERP integrations for D2C brands and can help you plan data ownership before anything is connected.
Related service: CRM Solutions · More on this topic: CRM Solutions articles
