A regular customer has spent around twelve thousand dirhams with you over two years. Roughly half of that was online under one email address, and the other half at your Dubai counter under a phone number. As far as your systems are concerned, these are two different people, neither of whom looks especially valuable.
So when your loyalty tier kicks in at eight thousand dirhams, she qualifies for nothing. When your team pulls a list of top customers for a private sale, she is not on it. She is one of your best customers and you cannot see her.
This is the sixth post in our WooCommerce series, after integration basics, inventory sync, click and collect, pricing across channels, and cross-channel returns. Stock and money have been dealt with. This one is about the customer record underneath all of it.
Why the Split Record Costs More Than It Looks
The obvious cost is the loyalty miss above. The less obvious cost is that every decision you make from customer data is being made on half the picture, which quietly distorts a lot of ordinary retail judgement.
Your average order value looks lower than it is, because one customer’s spending is spread across two records. Your repeat purchase rate looks worse, because second purchases through the other channel register as first purchases from a new person. Reactivation campaigns target people who have not gone anywhere, they simply bought through the other channel last time.
There is a commercial argument for fixing it too. McKinsey’s work on the subject notes that omnichannel customers shop around 1.7 times more often than single channel shoppers, and tend to spend more as well. If that group is genuinely your most valuable, then a system that cannot identify them is hiding your best customers from you.
The principle: a customer is a person, not a channel. One record should follow them from the website to the counter and back, whichever way they arrive.
The Matching Problem
Connecting the two sides sounds simple until you try it. Online, the identifier is almost always an email address, because that is what checkout requires. In store, staff capture a mobile number if they capture anything at all, since asking for an email at a busy counter slows the queue.
In the UAE the mobile number is usually the stronger identifier of the two. People change email addresses and often keep separate ones for shopping, but the mobile number tends to be stable and is the thing customers actually remember. The practical approach for most retailers is to treat the phone number as the primary key and the email as secondary, then match on either.
Number formatting deserves a mention because it silently breaks matching. The same phone can be stored as 050 followed by the local digits, or with the country code, with or without spaces. Unless numbers are normalised into one format on the way in, the same customer generates a fresh record every time the format differs. It is a small detail that accounts for a surprising share of duplicates.
Capturing Identity Without Slowing the Queue
The counter is where the single customer view is usually won or lost. If capturing a customer adds thirty seconds to every transaction, staff will skip it during busy periods, which is exactly when your most valuable customers are shopping.
The realistic version is a single field, a phone number, entered in a few seconds. If the number is already known, the existing record loads and the sale attaches to it. If it is new, a minimal record is created and can be enriched later. Anything more elaborate than that tends not to survive a Saturday afternoon.
It also helps if staff have a reason to ask beyond the retailer’s convenience. A loyalty balance, a warranty record, or a receipt sent by message gives the customer something in exchange for the number, which makes the request feel less like data collection for its own sake.
What the Unified Record Actually Enables
Once both channels write to one record, several things that were previously awkward become straightforward.
| Capability | What Changes |
|---|---|
| Loyalty points | Earned and redeemed in either channel against one balance |
| Tier qualification | Based on total spend, not spend per channel |
| Returns and warranty | Counter staff can see online purchases without asking for proof |
| Member pricing | The customer is recognised wherever they buy |
| Segmentation | Lists reflect real behaviour rather than channel artefacts |
| Lifetime value | Calculated per person, so it is actually meaningful |
The returns row connects back to the previous post in this series. A customer returning an online order to a branch is far easier to serve when their purchase history is already attached to the record the counter has open.
The member pricing row closes a gap left open in the pricing post. Recognising a customer in one channel but not the other produces exactly the kind of unexplainable price difference that erodes trust at the till.
Data Protection Is Part of the Design
Merging customer records means consolidating personal data, which brings obligations rather than just opportunities. The UAE’s framework sits under Federal Decree-Law No. 45 of 2021, summarised on the government’s own data protection laws page. It sets out how personal data may be processed and generally prohibits processing without the consent of the person it belongs to, subject to defined exceptions.
Worth noting alongside it: the consumer protection law referenced in that same summary also addresses consumer data and restricts suppliers from using it for marketing. In practice this means collecting a phone number to complete a sale is not the same thing as earning permission to send that customer promotional messages. Those are two separate consents and are best captured as two separate flags on the record.
A few habits keep this straightforward. Ask for marketing consent explicitly rather than bundling it into a purchase. Store consent against the customer record with a date, so you can evidence it later. Make opting out genuinely easy. Collect what you need and no more, since every extra field is something you are then responsible for protecting.
Free zone entities may sit under a different regime, and the detail of how the law applies varies by structure. This is worth a conversation with a UAE-qualified advisor rather than a decision made from a blog post, ours included.
Before you merge: decide how you will handle conflicting details across two records, such as different addresses or names. Usually the most recent verified detail wins, but the rule should be written down rather than left to whoever runs the merge.
Cleaning Up an Existing Mess
Most retailers reading this already have duplicates rather than a clean slate. That is normal and fixable, though it is worth doing carefully because merging is much harder to reverse than to perform.
A sensible order is to normalise phone number formats first, since that alone collapses a meaningful share of duplicates. Then match on exact phone or email and merge those with confidence. What remains are the ambiguous cases, such as a shared family email or two people at one number, and these are better reviewed by hand than resolved by a rule. Keep a record of what was merged, and take a backup before starting.
Do this before launching a loyalty programme rather than after. Duplicates that exist quietly become visible and expensive the moment points are attached to them, and customers notice immediately when a balance looks wrong.
MultiTech POS keeps customer records, loyalty balances and purchase history in the same retail POS software that runs your counter, connected to your site through the WooCommerce POS integration, so a customer recognised online is recognised in store as well. Across branches, multi-location integration means the same record follows them between outlets rather than starting again at each one.
Do you know who your best customers actually are?
Book a demo and we will look at how your online and in-store customer records line up today, and what it would take to merge them.
Frequently Asked Questions
1. Should we match customers on email or phone number? Phone number is usually the stronger identifier in the UAE, since people change email addresses more often. Matching on either, with the phone as primary, works well in practice.
2. How do we capture customers at the counter without slowing service? Keep it to a single phone number field. Anything longer gets skipped during busy periods, which is when your best customers are usually in the store.
3. Can loyalty points be earned online and spent in store? Yes, provided both channels write to one customer record. Points against a shared balance are what make a loyalty programme feel coherent to the customer.
4. Does collecting a phone number let us send marketing messages? Not automatically. Consent to complete a transaction and consent to receive marketing are separate, and should be recorded separately against the customer record.
5. What is the safest way to merge existing duplicate records? Normalise phone formats first, merge exact matches, then review ambiguous cases manually. Back up beforehand and log what was merged, because merges are difficult to undo.