How do you build one customer view across site, marketplaces and WhatsApp?

A step-by-step way for D2C brands to link website orders, marketplace buyers, WhatsApp chats and Instagram DMs into one customer record.

Anadoris Digital · · 4 min read

Smiling woman with a phone
Photo: rawpixel.com / Unsplash (CC0)

A single customer view means that when anyone on your team opens a customer, they see every order, conversation, complaint and campaign touch in one timeline. For an Indian D2C brand the hard part is that customers rarely use one channel. They discover you on Instagram, ask a question on WhatsApp, buy on a marketplace for faster delivery, then order the refill on your site.

Here is a practical way to join those pieces without a large data project.

Pick one identity key

In India the mobile number is usually the most reliable identifier. It is collected at checkout, it is the WhatsApp address, and couriers need it. Email is a useful second key, especially for prepaid orders. Decide that a customer record is defined by a normalised mobile number, stored in one format with the country code, and treat everything else as attributes.

  • Strip spaces, dashes and leading zeros before storing numbers.
  • Always store the country code so ‘98…’ and ‘+9198…’ match.
  • Keep a second field for alternate numbers instead of overwriting.
  • Use email as a fallback match, never as the only key.

Connect each channel in order of value

Start with the channels that hold the richest, most reliable data, then add the noisier ones.

  • Website store: sync customers and orders automatically; this is your cleanest source.
  • WhatsApp: connect the WhatsApp Business Platform through an approved provider so chats attach to the matching record.
  • Instagram DMs: link conversations to a record once the person shares a number or order ID.
  • Marketplaces: import order data where the platform allows; buyer contact details are often limited or masked.
  • Offline and wholesale: add retail and B2B buyers as contacts linked to a company record.

Accept that marketplaces are partial

Marketplaces usually restrict how much buyer information sellers can see and how it can be used. Respect those terms. Rather than trying to extract data, give marketplace buyers a reason to connect directly: a product registration card, a usage guide on WhatsApp, or a warranty that needs a number. When they do, link that contact to the order reference so their marketplace purchase appears in the timeline.

Set merge rules before you import

Most single-view projects fail because of duplicates. Agree up front what happens when two records share a number but have different names, or the same name with different numbers. A common rule: merge automatically on exact number match, flag for human review on email-only or name-only matches, and never auto-merge B2B company contacts with D2C shoppers.

Keep a merge log so that a wrong merge can be undone. When two records are combined, the CRM should keep both original values for a while, along with who merged them and when. That safety net lets the team clean data confidently instead of leaving obvious duplicates alone for fear of losing something important.

What the team should see on one screen

The point of all this joining is a screen that answers questions in seconds. When a customer messages on WhatsApp, the person replying should see, without switching tabs, the last few orders with their delivery status, any open complaint, the products they usually buy, whether they are a wholesale or retail contact, and what marketing messages they received recently. That context changes the reply from a generic script to something that feels personal.

It also prevents awkward moments. Nobody sends a ‘we miss you’ message to a customer who reordered on a marketplace yesterday, or a review request to someone with an open damage complaint, because the timeline shows both. Design the record view with the team that answers customers, not only with whoever sets up the tool, and keep the most-used facts at the top.

Finally, decide which system is the master for each field. Addresses and orders usually belong to the store, conversations and lead stages to the CRM, and stock or invoices to the ERP. Writing that down avoids sync loops where two systems keep overwriting each other.

Checklist for a working single customer view

  • One normalised mobile number field used as the primary key.
  • Store orders syncing automatically, including returns and cancellations.
  • WhatsApp and Instagram conversations attached to the customer record.
  • Marketplace orders linked where the customer has identified themselves.
  • Tickets and complaints visible on the same timeline as orders.
  • Marketing consent stored per channel with a date and source.
  • A weekly duplicate review owned by a named person.

Combining data from different sources may change how you need to describe data use in your privacy notice. Check current requirements under India’s data protection law and each platform’s terms before linking records.

Where to start

  • Export customers from your store and normalise every phone number.
  • Connect store orders and WhatsApp to the CRM first; leave other channels for later.
  • Run a duplicate check and fix the top cases by hand to learn your patterns.
  • Add Instagram and marketplace links once the core record is clean.

Anadoris Digital sets up these connections for D2C brands and can help you decide the matching rules that suit your channels.

Related service: CRM Solutions · More on this topic: CRM Solutions articles

Common questions

Why use the phone number instead of email as the main key?

Indian shoppers often skip email or use several addresses, while the mobile number is needed for delivery and is the WhatsApp identity. That makes it the field most likely to be present and consistent across channels. Email still helps as a secondary match for prepaid and international orders.

Can I see marketplace customers in my CRM?

Partly. Most marketplaces share order details but limit or mask buyer contact information, and their seller terms restrict how it can be used. You can import order data where allowed and link a buyer once they contact you directly through your own channels.

What if one phone number is shared by a family?

It happens, especially with gifting and household purchases. Keep one record per number but allow multiple delivery names and addresses under it. Use order-level data for personalisation, and avoid assuming the name on the latest order is the account holder.

How often should duplicates be reviewed?

Weekly works for most small brands. Automatic merging should handle exact number matches, and a named person should review the flagged cases. Leaving duplicates for months makes segments and reports unreliable and is harder to fix later.

Your next chapter

Let’s build what comes next.

A new website. A better system. A simpler way to work. Tell us where you want to begin.

Discuss your project