Duplicate customer groups found by the scan, with confidence and matched signals
Customer Merge is a module for PrestaShop stores that finds duplicate registered and guest accounts and consolidates them into one reviewed customer record without rewriting issued sales documents. Installation, a scan scope and the first scan are enough to produce a review list with conservative starting settings.
Duplicate accounts divide orders, addresses, support conversations, customer groups and spending totals between several identities. Exact email matching misses aliases, changed phone formats, address variations and the link between a guest checkout and a later registered account. The result is an incomplete customer history wherever the team needs the full relationship.
The module scores each possible match from independent evidence: exact and normalized email, phone, name with postal address, company or VAT details, payment evidence and the guest-to-registered relationship. You choose which signals are active, their weights, the address-similarity level and separate thresholds for human review and unattended merging. Conflicting evidence lowers the result, while a shared company or payment detail never decides identity by itself.
Before anything changes, you choose the surviving account and the value kept for every conflicting field, view similar addresses side by side and receive exact counts for records moved, collapsed or left untouched. Customer Merge discovers customer-linked data from installed extensions as well as the store itself, stops on an unsafe source, preserves invoices, payments and historical addresses, keeps an encrypted return point and records every operation in a verifiable history. Scheduled scans, guarded unattended merging, all-shop coverage and result summaries keep later cleanup under the same rules.
The result is one dependable customer history, accurate support and customer-value data, issued documents that remain true, less manual investigation and a cleanup process that starts simply yet offers precise control over every important decision.
What does Customer Merge do?
Customer Merge finds duplicate customer and guest accounts, shows the merchant exactly how they become one record and protects the commercial history attached to them. A first scan works with conservative settings, while the sections below map the deeper controls.
- Duplicate detection: seven evidence families reveal matches that an exact email search misses.
- Reviewed plan: the survivor, conflicting fields, addresses and exact affected-record counts are settled before writing.
- Complete history: orders, addresses, support data, groups, carts and installed-extension records move to the right owner.
- Historical protection: issued documents, payments, totals and order content retain their original facts.
- Return and evidence: encrypted snapshots reverse a merge and a verifiable history records every action.
- Controlled automation: scheduled work, all-shop scope, strict limits and result summaries reduce recurring administration.
How does the module recognize the same person behind different accounts?
Customer Merge combines exact email, email aliases, normalized phone numbers, name with postal address, company or VAT details, payment evidence and the relationship between a guest checkout and a registered account. Similar evidence from one family counts once, contradictory details reduce certainty and business or payment data remains supporting evidence rather than proof of identity.
You choose the active signals, their weights, the minimum address similarity and the scores that send a group to review or qualify it for unattended work. The module also requires independent personal evidence before a high score becomes an automatic decision. Each group therefore arrives with its reasons, confidence and a suggested survivor based on registered status, account activity, orders and account age.
What is settled before the merge changes any customer data?
The five-step review selects the surviving account, keeps the chosen value for every conflicting customer field and places identical and similar addresses side by side. Every decision remains attached to the review while moving forward, going back or refreshing, so the final plan uses exactly the choices already approved.
The simulation lists every affected data source and the precise number of records moved, duplicate records collapsed and records left untouched. It carries a digital seal and is rebuilt after the relevant data is locked; changed customers, rules, sources, strategies or conflicts cancel the old plan instead of executing a different one. Irreversible deletion receives its own deliberate confirmation tied to the current plan, and any change requires a fresh confirmation.
Which parts of customer history move, and what remains untouched?
Orders, returns, credit slips, messages, addresses, carts, customer groups, support records, individual prices, B2B data, wishlists, reviews, stock notifications and loyalty records follow the surviving customer. Customer Merge also finds customer-linked data belonging to extensions it has never seen before. You choose whether each unfamiliar source moves, moves with exact duplicates collapsed, stays untouched or requires a manual decision.
Issued invoices and credit slips are never rewritten. Payments, order totals, products and order history keep their original content, and only the customer who owns the order changes. An address used by an order keeps its identifier and every field printed on historical documents. A read-only source, a source that changes records by itself, a non-reversible source, a missing stable identifier or an unsafe conflict blocks the merge, so unknown structure becomes a visible task instead of a partial result.
How does one action return the accounts and prove what happened?
Before writing, Customer Merge stores an authenticated encrypted picture of the complete customer state. The Undo action first verifies that later changes, reused identities and new conflicts will not be overwritten, then restores the absorbed accounts and their records in one controlled operation. Safely validated customer sessions are re-established only for their proven owner, so full reversal never hands access to the wrong person.
Every completed merge, reversal and failure enters an append-only history. Each entry verifies the one before it, making removal or editing visible, while the screen shows the actor, survivor, absorbed accounts, affected records and result. The history exports to a spreadsheet file. A privacy erasure always takes priority and removes any retained return data that would recreate erased personal information.
How simple is the first scan, and how far does automation go?
Installation starts detection with conservative defaults. You choose the current customer domain or all shops, start the first complete scan and review the resulting groups. Later scans resume in bounded batches and focus on accounts affected by customer, address, order or privacy changes, while routine cleanup removes expired working data.
Unattended merging stays off until the merchant enables it. Once enabled, only groups above the chosen certainty, independent-evidence, group-size and affected-record limits enter the scheduled queue; one unfamiliar source or conflict returns the group to manual review. Larger approved merges use a dedicated maintenance workflow with explicit authorization and recorded responsibility. Scheduled scans and merges send localized summaries with counts, skipped groups, failures and direct review links.
-
Referencemprcustomermerge
-
In stock2147483647 Items
-
PrestaShop CompatibilityPS 1.6 – 9.x
-
Pricing ModelOne-time Purchase
-
Module TypeBack-office
-
GDPR RelevantYes
-
Business GoalStreamline Operations
-
External Account NeededNo
-
Module ComplexityComplete Solution
-
Customer Journey StageManage Store
-
Works With PlatformNo External Platform
What customers say about us
Company reviews
5.0
★
★
★
★
★
(4 reviews)
Loading customer reviews...
No product reviews yet
Be the first to share your experience with this module.
Write a Review
Install
Upload the ZIP through Modules > Module Manager > Upload a module, then install it. The module creates its own tables and adds a Customer Merge section under Customers in the menu.
It needs PrestaShop 1.6.1 or later and PHP 7.1 or later. Undo additionally needs the OpenSSL AES-256-GCM cipher; System Check tells you whether your server has it.
Have a question about this product?
Our experts are here to help. Ask anything about installation, compatibility, or specifications.
1301
questions
9
categories
2013
building modules since
1.6–9
PrestaShop versions
v1.0.02026-07-28
- Initialrelease
- InitialDuplicate detection scored on exact email, Gmail dot and plus aliases, lookalike characters, phone numbers normalised to international format, fuzzy name and postal address, company and VAT number, and guest to registered signals
- InitialSQL-first indexing with keyed fingerprints and capped match buckets, so only hashes are stored and the scan holds up on large customer bases
Loading full changelog...
Works Well With Customer Merge
Modules our team genuinely pairs with this one, and exactly why each belongs in the same setup.
Complement
Customer Merge unifies the people; Cleanup Revolution clears out the stale carts, logs and orphaned records they leave behind.
Complement
Points and tiers stop being split across duplicate accounts, so the customer sees the balance they actually earned.
Complement
Fewer duplicate accounts are created at checkout in the first place, so there is less to merge later.
Loading feature requests...
30 days return right
Easy return - no questions asked
Plug & Play Modules
Install, set up and take profit
Dedicated Support First
Priority Help & Satisfaction Over Sales
You might also like
