Before merging duplicate Shopify customers, confirm that both profiles belong to the same person. Then check whether Shopify permits the merge, which profile will remain and what connected apps will do with their records. Shopify cannot reverse a completed merge, so the review before confirmation matters more than the speed of the cleanup.
This guide is for the store operator handling a duplicate-profile request and the person responsible for customer-data integrations. Start with the customer’s actual problem: missing order history, an outdated email address or a loyalty balance that appears on another profile. Merging is one possible action, not the definition of a successful resolution.
A matching address is a clue, not proof
A household can contain several customers with the same surname and delivery address. One person can also use different email addresses over time. Neither similarity nor difference settles who owns the records. Use the store’s established identity-verification process before combining access to purchase history.
Consider two illustrative profiles with orders delivered to the same family address. Support still needs to establish whether the requester owns both profiles. Do not reveal an unfamiliar order or address as a shortcut to verification. If ownership remains uncertain, keep the records separate and escalate the case.
Record the two customer IDs and the requested outcome. An ID identifies the record you are investigating even when its email changes. Keep this case record private, with only the details needed for the work and the store’s normal access and retention controls.
Check eligibility before preparing a merge
Shopify’s current guidance blocks a merge if either profile has ever had a subscription contract, has a store credit account or has a vaulted credit card. B2B restrictions include an active company connection and links to past B2B orders. Multipass logins, deleted or redacted profiles, and certain pending customer-data operations are also excluded. Check the full current list for the affected pair.
A canceled subscription is not necessarily an eligible profile: Shopify’s restriction includes past subscription contracts. A zero balance is not the same as having no store credit account. Do not remove unrelated records just to make a merge possible.
Shopify also caps the combined notes at 5,000 characters, including spaces, and combined tags at 250. If the merge is blocked, identify the exact restriction before treating it as an app-sync fault. Ask Shopify or the affected provider for the supported way to resolve the customer’s underlying request.
Choose the retained profile deliberately
Do not assume that the customer profile you opened first will survive. Under Shopify’s documented rules, if only one of the two profiles has an email address, that profile remains. If both have email addresses, the retained email determines which profile remains. If neither has an email address, the profile selected in “Find a customer to merge with” remains.
That makes the contact-information review an integration decision as well as a support decision. Before confirming, record the expected retained customer ID and check how each connected app refers to it. Resolve conflicting information before continuing.
- Open Customers and the relevant profile, then choose More actions > Merge customer. Find and select the verified matching profile.
- Inspect Merged customer and View merge details. Check what will remain and what will be discarded; use Change contact information where needed.
- Compare the preview with the agreed customer request and app checks. Cancel and resolve conflicts if they do not match. Only then complete Merge and Confirm.
Shopify combines information including orders, addresses, notes and tags. Its preview is the place to inspect the actual pair. A private before-and-after record helps with troubleshooting; it does not create an undo function.
Verify app records separately from Shopify
A completed Shopify merge does not establish what happened inside every connected app. List the systems that depend on either customer ID and ask each owner what its supported merge behavior is. Include loyalty, marketing, support and any custom customer-data connection relevant to the request.
Rivo provides a useful, specific example. Its July 2026 help article explains that loyalty data can remain tied to the profile that earned or redeemed it; using a different profile after a merge may leave balances or history split. Its recommended investigation is to compare the involved profiles and contact support when records need correction. This is Rivo guidance, not a rule for every loyalty app.
Do not simply add the two displayed loyalty balances or issue replacement rewards to make the screen look right. Have the program owner inspect earning, redemption and adjustment history first. Otherwise, an attempt to restore a missing benefit could create a second benefit for the same activity.
| Area | Evidence to keep with the case |
|---|---|
| Shopify identity | Original IDs, retained ID and the contact information selected in the preview. |
| Orders and account access | The expected orders belong to the verified customer, and the intended account journey works. |
| Loyalty or other app records | Provider confirms the relevant balance, history and record mapping; discrepancies have an owner. |
| Marketing settings | Conflicting preferences have been reviewed and the resulting settings checked in the sending system. |
Pay particular attention to marketing settings. Shopify documents a subscribed result when one profile is subscribed to email and SMS marketing and the other is not. That platform behavior is a reason to review conflicting preferences before merging. Do not treat combining profiles as a fresh customer opt-in or assume a sending app has adopted the intended settings.
- Shopify: marketing status and other merge considerations
- Related: test customer identity in a loyalty integration
Close one case before expanding the cleanup
For the first approved case, define the expected result before anyone clicks Confirm. After the merge, compare Shopify and each affected tool against that record. Close the request when the customer’s problem is resolved, not merely when a duplicate disappears from search. If an app still shows the wrong history, record the retained ID and discrepancy for its owner.
Before a larger cleanup, test representative cases in an appropriate test environment and agree how staff will handle ambiguous matches and blocked profiles. A matching score or an app’s bulk action does not replace the identity decision. Ask any proposed tool to demonstrate its limits and supported recovery process without assuming that a stored snapshot reverses Shopify’s merge.
Finally, trace how the repeated records were created. Compare the source and identifiers used by imports, point-of-sale processes and integrations. Investigate the actual creation path instead of assuming all guest checkouts produce duplicates. Fixing that path can prevent the team from handling the same kind of support request repeatedly.
Questions that affect the support response
Does changing an order’s contact email move it to another customer account?
Will Shopify tell the customer that their profiles were merged?
Can a backup restore the two original profiles after a merge?
Take one verified duplicate pair, write down the intended retained identity and get the affected app owners’ answers. If those answers are incomplete, resolve the customer’s immediate request through a supported alternative and leave the merge pending.
Sources
