Two different buyers were merged into one customer profile

Contain the merged profile before sorting it

The active harm in a wrong merge is misdirection: order updates, marketing messages and account notifications addressed to one buyer now reach the other. Before editing anything, pause the automations, segments and export jobs that consume this profile, and hold any queued messages that reference either buyer's orders. Record what you paused and when, so containment can be lifted deliberately rather than rediscovered later.

Containment is not correction. Do not compensate by sending an explanatory message to the merged contact, because that discloses one buyer's activity to the other. If a buyer has already received another person's order details, record that disclosure as its own event for the merchant's responsible owner; it is not resolved by fixing the profile.

Rebuild the two profiles from before the merge

Shopify's customer documentation says profiles can arise from purchases, abandoned checkouts, mailing-list signups or manual addition, and that merging is intended for profiles of the same customer. Those distinct origins are your first evidence: a profile created by a newsletter signup and a profile created by completed purchases serve different relationships, and combining them does not make them one person. Locate the merge event in the platform's records, note its date and the staff account that performed it, and identify the two pre-merge profiles it combined.

No reversible unmerge feature is verified for this situation, so treat reconstruction as records work rather than a button. For each original profile, list what existed before the merge: orders placed, their dates and totals, the contact fields present at that time, and any notes with timestamps. Screenshot-level certainty is not required, but every claim in the reconstruction should point at a record in an authorized system, not at a staff member's recollection.

Sort ownership as three separate questions

Order ownership is settled by the orders themselves. Each order belongs to the profile its own pre-merge record shows, regardless of which contact field the merged profile now displays. Do not reassign an order to make the merged profile tidy, and do not infer identity from a shared company name, a shared shipping address or a shared email domain; those are reasons two profiles looked similar, not evidence that one buyer placed both sets of orders.

Contact fields are the second question. Where the two originals held different email addresses, phone numbers or names, record which profile held which, and mark the currently displayed value as belonging to one of them only if the pre-merge record says so. Where both genuinely shared a contact detail, record the sharing instead of awarding the detail to one buyer.

Support history is the third question. Attribute each note, ticket and timeline entry to the buyer its content and timing concern, using internal references rather than pasting message text into a worksheet. Saved payment methods and any subscription relationships belong to whichever original profile held them; a merge never transfers payment rights between people, and this worksheet does not move them.

Correct through the platform and preserve both trails

Make corrections with the platform's supported customer-editing path, adjusting the fields the evidence assigns to each buyer and, where the platform allows, recreating a separated profile for the buyer whose record was absorbed. Keep the merged profile's history intact while you work: deleting the combined record would destroy the order links and notes you need for attribution, and deleting the apparently wrong half could erase the other buyer's only account.

Where the platform's standard editing cannot express the correction, for example separating order history that now displays under one customer, route the case to the platform's own support channel with internal references and a non-sensitive summary. Record the answer you receive. A support agent's suggested action is evidence for your log, but the merchant's authorized data owner still approves any change that affects order ownership or contact disclosure.

Recheck downstream systems and name the owner

A corrected store profile does not automatically repair the marketing platform, help desk or fulfillment tool that already synced the merged record. For each connected system, compare its current record against the corrected profile and either confirm the match or record the discrepancy with an owner. Only then re-enable the paused automations, and verify the first post-fix message or export goes to the intended buyer.

Close the case by naming who decided each unresolved point: order-ownership disputes and contact-disclosure questions belong to the merchant's authorized data owner, with qualified advice where a disclosure raises privacy obligations. If the merge exposed weaknesses in how your public checkout or account pages collect identifying details, a Prism website review can examine those public surfaces within an agreed scope; responsibilities, fees and terms are confirmed before any work.

Customer-merge correction record

Complete one record for the affected merged profile, using internal references rather than buyer contact details or message contents. Unknowns stay marked unknown until the authorized data owner resolves them; no row authorizes deleting a profile, moving an order or transferring a saved payment method.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.