A returning shopper gives their name at the till. Two profiles appear.
One has their recent purchases. The other has the contact details the team recognises. Someone suggests merging them before the next customer reaches the counter.
That is an illustrative situation, but it captures the decision I would slow down. A shorter customer list is useful only if the remaining record still tells the right story.
Before merging duplicate customer profiles, establish three things: these records belong to the same person, the retained details are correct, and the information the business needs will remain connected.
If one of those answers is uncertain, leave the case open. Tidying the screen is not a good reason to guess.
Why retailers need a pre-merge check
In a Square merchant discussion about duplicate profiles, a retailer described the concern as "merge is not in a controlled way". Their account raised questions about which information survives and how customer relationships behave afterwards.
That is a merchant's experience, not an independently verified diagnosis of every Square setup. The useful question travels beyond one provider: what exactly should the remaining profile contain?
A duplicate can arise when someone uses different contact details online and in store, a member of staff creates a new record instead of finding an existing one, or an import adds a second version. Similar-looking records can also belong to different people.
The cleanup therefore needs a decision, not just a matching rule.
First decide whether it is one person
An identical email address or phone number can help identify a possible match. It is not enough on its own to authorise a merge.
People share household contact details. Businesses use a common purchasing address. Old details can remain on a profile after a customer changes them.
Review information the business is authorised to use, such as the customer record, relevant transaction context and any appropriate confirmation from the customer. Do not collect extra identity documents merely to complete an ordinary cleanup task.
Use three possible outcomes:
- Confirmed duplicate: the available evidence supports one person and the intended retained details are clear.
- Different people: similar details do not justify combining the records.
- Unresolved: conflicting or insufficient information needs follow-up.
That third outcome prevents uncertain cases becoming silent mistakes.
Write down what should remain
Before pressing a confirmation button, use this compact review sheet. Keep any working record in an approved, access-controlled place and follow the business's retention rules. A general spreadsheet should not become a second customer database.
| Check | Question before changing anything | Expected result to verify afterwards |
|---|---|---|
| Identity | Why do we believe both records belong to one person? | The retained profile represents that person, not a household or colleague. |
| Contact details | Which name, email, phone and address should remain? | The intended details are present; an older value has not silently won. |
| Marketing preferences | What preferences and statuses exist on each record? | The supported result matches the reviewed choice; a merge is not treated as new permission to market. |
| Purchase history | Which relevant orders or transactions are linked to each profile? | Expected history is still reachable through the supported customer view. |
| Notes and groups | Which service notes, tags or segments matter? | Important context remains available without avoidable duplication or conflict. |
| Rewards and connected services | Are there balances, benefits, subscriptions or other linked records to consider? | Their supported treatment is understood and checked, not assumed. |
| Authority and recovery | Who can perform the action, and can it be reversed? | An authorised person completes it, with a clear escalation route if something is missing. |
Not every platform combines all these items, and not every profile is eligible for merging. This is a list of questions to resolve against the current provider documentation, not a universal merge specification.
Check the provider's rules before confirming
The differences between providers are a reason to read the current instructions.
Square's profile-management guidance says to review potential duplicates and allows suggestions that are not duplicates to be ignored. It also warns that a merge cannot be undone.
Shopify's customer-management guidance explains reviewing the proposed retained information and lists restrictions for certain profiles. It too describes merging as irreversible. Confirm eligibility before planning any change.
For connected systems, the visible contact fields are only part of the job. Square's developer guidance warns that creating a replacement customer, copying fields and deleting the old record breaks existing relationships. That is a specific warning about Square, not proof that every platform has identical internals. It explains why I would not improvise a delete-and-copy workaround.
If the supported process cannot handle the case, ask the provider what can be preserved and which action is appropriate. Do not cancel a subscription or recreate customer value simply to bypass a restriction.
Three examples that should produce different decisions
The following examples are illustrative. They are not customer cases or claims about a particular product's behaviour.
1. One shopper, two confirmed profiles
A shopper confirms that an older email and a current email are both theirs. Staff can see relevant purchases on each record and establish which contact details should remain.
The next step is to review eligibility and the provider's supported merge behaviour, including linked information. If those checks pass, an authorised person can complete the action and verify the result.
The matching decision does not itself prove that every balance, preference or connected service will transfer as intended.
2. Two people using one household phone
Two customers have different names and separate purchase histories but share a phone number.
That is not a confirmed duplicate. Keep the profiles separate unless there is appropriate evidence that they represent one person. A matching phone number should not erase the distinction between household members.
3. Conflicting details and an unresolved balance
Two records have similar names. One contains an older address; the other has reward context that staff cannot explain. Nobody can confirm which details are current.
Hold the case. Assign someone to resolve the identity and linked-record questions through the supported process. Do not choose the newer profile merely because its timestamp looks more convincing.
After the merge, reopen the record
A successful confirmation message tells you that an action completed. It does not replace checking the result.
Reopen the retained profile and compare it with the review sheet. Check contact details, relevant history, important notes and the connected records your provider supports. Where a separate service holds information, confirm its documented behaviour rather than assuming the customer screen proves everything.
Record who reviewed the case, the action taken and any unresolved exception. Prefer record references and concise reasons over copying unnecessary personal details into a cleanup log.
If something is missing, stop and escalate. Repeating edits until the display looks right can make the original problem harder to explain.
Fix the habit that keeps creating duplicates
Once the immediate case is resolved, look at how the second profile appeared.
Can staff find an existing shopper before creating another record? Are online and till workflows using the same supported customer identity? Does an import or integration create a new record when it should reference an existing one?
These are different questions from a one-off CRM migration acceptance check. Migration concerns what survives a change of system. Everyday cleanup concerns whether the business keeps identifying and serving the same customer correctly afterwards.
Better customer data also needs useful access and an appropriate purpose. Our guide to first-party customer data in retail covers that wider foundation. A tidy profile list alone does not establish why someone will return; that belongs in the separate work of building repeat custom without relying on discounts.
Where EzyCarto fits
At EzyCarto, the aim is to connect the customer relationship with the rest of the retail operation. Our CRM and customer-engagement information describes profiles with shopping history, preferences and reward balances, connected with loyalty, checkout and inventory.
That makes the quality of the customer record important. It does not mean the merge controls described for another provider are EzyCarto features. Confirm the exact cleanup, merge and recovery actions supported in your configuration before relying on them.
Start with a small, authorised sample of likely duplicates. For each pair, establish the identity, the intended retained information and the supported action. Leave uncertain matches on hold, then verify what remains connected after any change.
The useful outcome is a customer record the next person serving that shopper can trust.