Practical framework / 5 MIN READ
Prove the customer match before combining records
Protect order history and preferences from convenient but uncertain identity assumptions.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
Customer records can look similar without belonging to the same person. A mistaken merge can expose private history, transfer benefits and change communication preferences, so identity confidence matters more than a tidy database.
What you will leave with: Create a profile-match review with evidence, conflict checks and a safe unresolved state.
Use this when
- Customers have several apparent accounts across store and online channels.
- Staff want to merge records based on a shared name or address.
This is not permission to merge, erase or expose customer records, nor a method for bypassing account-verification requirements.
Separate a suspected duplicate from a verified identity
Use a clear candidate state for records that might match. A shared surname, address or device can represent household members or unrelated people. A mistyped email may belong to someone else. Do not let a similarity score become automatic authority to combine personal records.
Define the approved verification process and the staff who can apply it. Use the minimum evidence necessary, and avoid asking for passwords, full card details or unnecessary identity documents. If the customer initiates a request, verify the relevant account control through the appropriate secure route rather than trusting a claim in an ordinary message.
Inspect what the operation will combine or discard
Shopify documents profile merges, limitations and irreversible behavior. It also describes possible effects on marketing status. Review the current platform details and the proposed result before any authorized action. A merge is more consequential than adding a harmless internal duplicate label.
Check orders, addresses, balances, subscriptions, tax settings and communication preferences under the actual tool’s rules. Some records may be ineligible. Do not bypass a limitation by deleting data or moving benefits manually without the appropriate authorization. Keep uncertainty visible and escalate unresolved conflicts.
Preserve the customer’s latest valid choices
Compare preference records by source and timing rather than assuming the most permissive status is correct. An old subscribed record should not silently override a later opt-out. Have the responsible privacy or compliance team determine how conflicts should be resolved.
Check who would gain access to order history after the operation. Household members may share a delivery address without agreeing to share purchases. Explain the relevant consequence when seeking required approval. Avoid presenting a merge as a purely cosmetic cleanup when it changes what a person can see or use.
Verify the result without creating another identity error
If the authorized merge is permitted and confirmed, inspect the surviving profile and connected systems. Check that the correct contact details and preferences remain. Record the decision evidence and outcome at an appropriate level without copying unnecessary personal data into a broad audit log.
Where a merge cannot be safely completed, retain a documented unresolved state and offer the supported customer route. A duplicate count is not a sufficient success metric. Track mistaken associations, lost preferences and access problems. The objective is accurate customer service, not the smallest possible number of profiles.
Make the reasoning concrete.
A fictional homeware retailer finds two profiles named Alex Patel at the same address. One has opted out of marketing and the other has recent purchases. Staff propose merging them to improve the loyalty dashboard.
Verify before combining
Opening: Use the approved account process to determine whether one person controls both records and resolve preference conflicts.
Hypothesis: The retailer avoids exposing one person’s purchases to another.
Risk: The match may remain uncertain or the platform may prohibit the merge.
Name-and-address shortcut
Opening: Merge because both fields match.
Hypothesis: The duplicate report becomes smaller.
Risk: The profiles may belong to different household members, and consent may be overwritten.
Keep the records separate until identity, consequences and authorization are established. Do not use dashboard cleanliness as the decision criterion.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Match evidence
What establishes that these records belong to the same person?
Consequences
What history, balance or access will change?
Conflicts
Which contact details or preferences disagree?
Authorization
Who is allowed to approve and perform this operation?
Safe fallback
How will an unresolved candidate be handled without merging?
Watch for the wrong conclusion.
- Treating a shared address as proof of identity.
- Letting an old subscription override a later opt-out.
- Deleting information to bypass a merge restriction.
Your next action
Write the evidence and consequence checklist for one suspected duplicate without changing either record.
Sources & scope
Frameworks, worksheets and proposed tests are original editorial synthesis. Examples are hypothetical and do not report measured outcomes. Source checking is not an independent audit of effectiveness. Platform features and applicable law can change. No named human author or reviewer is claimed.
- Shopify Help Center: Managing customers →Primary provider guidance · Supports: Documents profile merges, irreversible merge behavior, limitations and possible marketing-status effects. Technical capability does not establish that two records represent the same person or authorize a merge.