The same person ends up with several accounts: ordered as a guest, then registered, then signed in through a social network. The purchase history is broken apart, points are scattered, and analytics counts one person as three.

What it does

• Merging accounts from the user list or from an account page: choose the main one and add the rest.
• Orders, reward points, user groups and other data moved into the main account.
• The source record is hidden so it does not clutter the customer list.
• Every action written to the CS-Cart event log, with a comment in the order about the change of owner.
• Configurable emails to customers about the merge.
• A «Merged» filter in the extended search, and the new main account shown on hidden records.
• Multi-level merges: on a repeat merge child records are reassigned to the new parent.

When it helps

Stores with a long-standing customer base where duplicates have piled up over the years, and projects with several ways to sign in — by email, by phone and through external services. Managers stop hunting for a customer's orders across three records, and the analytics becomes honest.

Support and updates

The merge procedure is covered in the documentation. Six months of free updates, questions through HelpDesk.

FAQ

Are orders lost during a merge?

No, they move to the main account and every order gets a comment about the change of owner.

Can I tell which records were merged?

Yes, the extended search has a «Merged» filter, and a hidden record shows the main account it now belongs to.