A shared email or phone creates a review candidate; it does not prove two records are the same person or organization. Merge deletes the secondary customer record and retires that customer code. Use Household for related people, Ignore for intentionally separate records, and cancel when accounting, CRM, vault-token, or legal identity is unclear. There is no Files field or Files tab in the current customer profile, and the merge flow does not claim to consolidate arbitrary uploaded files.
Step by step
- Go to Contacts → Contacts. The potential-duplicate banner appears only for an owner or administrator when pending candidates exist. CentriPOS runs a background scan on the first authorized load; Rescan requests another scan. The current scanner groups active customers by normalized primary email and by normalized primary or additional phone numbers.
- Open the banner. The count is all pending candidates, while the working queue loads at most the 500 most recently updated pending rows. Summary buttons show up to four shared-email or shared-phone groups, their contact count, and pair-review count. Choose one group to narrow the queue, or Show all queued pairs.
- Use Search duplicate matches by name, email, phone, address to narrow the loaded queue. Each pair displays Customer A and Customer B with available name, email, phone, address, match type, and shared-match detail. Compare customer codes and open the underlying Contacts or Customer Profiles separately when the card lacks enough evidence.
- Choose Ask CentriAI for a review of up to the first 12 currently filtered pairs. CentriAI receives the shown IDs, names, codes, emails, phones, companies, addresses, match reason, and queue summary. Treat its response as a prioritization aid—not authorization or proof—and verify every proposed action yourself.
- Choose Ignore when the two records are intentionally separate despite sharing contact information. Ignore resolves this candidate pair so it leaves the pending queue; it does not merge, edit, associate, or delete either customer. A later scanner implementation or newly generated candidate can still require review.
- Choose Household when the pair represents two related people who should remain separate. CentriPOS creates a household named from the two customer names, links both customer IDs as members, and resolves this candidate as household. Review and rename the association afterward; this shortcut does not copy address, roles, billing configuration, or notes into the new household.
- Choose Merge only when both records are the same identity. You can also check exactly two rows in the Contacts list and choose the bulk Merge action. More or fewer than two selected contacts cannot enter the comparison.
- In Merge Customers, review the automatically suggested master. The suggestion scores profile completeness—usable name, email, phone, additional phone lines, company, address, nonzero balance, and nonzero store credit—and penalizes Dialpad-generated source identities. This is only a default; choose the record whose customer code and external identity should actually survive.
- Choose the master profile. Its customer ID and customer code survive, and choosing it resets every field-selection row to that record. The secondary customer will be deleted and its code retired. Review any distinct CentriCRM, Dialpad, QuickBooks, financing, or payment-vault identity before proceeding because the dialog does not present every external identifier.
- Choose Contact A or Contact B separately for Name, Email, Phone, Company, Street address, Street address 2, City, State, ZIP code, Tax exempt, and Credit limit. A blank selected text field falls back server-side to an available master or secondary value, so do not assume choosing a visible dash guarantees a blank final value.
- Review phone consolidation. CentriPOS combines additional phone-line arrays from both records and inserts the selected primary phone as Primary, then removes duplicate numbers using their normalized last ten digits when possible. The selected primary phone remains the customer_phone field. Verify labels and primary status after the merge.
- Review the financial totals. Customer account Balance and Store credit balance are added, including negative values; they are not selectable field rows. This can double a liability if the two records already represent the same underlying amount. Reconcile the A/R invoices and store-credit transaction ledger before and after merging.
- Understand the current transactional reassignment. CentriPOS moves the secondary customer’s sales, customer notes, matched CRM external events, customer interactions, A/R invoices, store-credit transactions, parked sales, payment intents, financing applications and preapprovals, gift cards, recurring billing plans, storefront orders, inventory movements carrying customer context, and customer vault-card token rows to the master.
- Group memberships are copied to the master without duplicating an existing same-group link, then removed from the secondary. Household/company association memberships are changed to the master ID and merged name. If an existing relationship or another database constraint conflicts, the database merge fails as one transaction rather than intentionally completing a partial merge; read the error and leave both records unchanged for investigation.
- The merge changes matched CRM event ownership to the master, marks nondismissed rows Matched with high confidence and customer_merge reason, and updates interaction/preapproval identity snapshots from the merged fields. It does not prove that an external CentriCRM, Dialpad, QuickBooks, financing, or processor-side contact was independently deduplicated. Review those systems where separate identities existed.
- Read the irreversible warning naming the secondary contact and retired code, then choose Merge into [master name] ([customer code]). Do not refresh, close the browser, or repeat the action while Merging… is shown. A successful message names the surviving contact and confirms the secondary was deleted.
- After success, search Contacts by both names, both codes, email, and phone. The secondary should no longer be an active contact. Open the survivor and verify selected identity fields, all labeled phone lines, tax status, credit limit, associations, groups, Activity, Notes, Store credit, Account, Payment methods, financing, and representative receipts.
- Reconcile financial and operational evidence: Account balance against open A/R rows, Store credit balance against its combined transaction ledger, a representative receipt and parked sale, group and association membership, payment token labels, and any matched CRM/Dialpad activity. The merge result is not verified merely because only one Contact row remains.
- If the pair is missing a customer record by the time Merge opens, CentriPOS removes the stale candidate from the working queue as already resolved. If Rescan reports candidates found, that count is scanner output—not a count of confirmed duplicates. When no current screenshot exactly matches the live merge dialog, the help center intentionally omits one rather than displaying a fabricated or unrelated image.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Potential-duplicate banner | Owner/admin-only Contacts alert shown when pending candidate pairs exist. |
| Background scan | Runs once on the first authorized Contacts load and checks active customers for normalized shared email or phone values. |
| Rescan | Requests the current duplicate scan again and refreshes the pending queue. |
| Pending count | All pending candidate rows; the visible working queue is limited to the 500 most recently updated. |
| Shared email / phone summary | Up to four candidate groups with contact and pair-review counts. |
| Duplicate search | Searches the loaded pair cards by match detail and displayed customer name, email, phone, or address. |
| Ask CentriAI | Advisory review of up to 12 currently filtered candidate pairs; human identity verification remains required. |
| Ignore | Resolves only the candidate pair as intentionally separate. |
| Household | Creates a minimal household association with both customer IDs and resolves the candidate; profiles stay separate. |
| Merge | Loads both full customer records into the irreversible comparison. |
| Bulk Merge | Contacts action available only when exactly two rows are selected. |
| Suggested master | Completeness-based default with a penalty for Dialpad-generated identities; it is not authoritative. |
| Master profile | Surviving customer ID and customer code. Changing it resets all field choices to that contact. |
| Secondary contact | Deleted customer record whose customer code is retired after a successful merge. |
| Field-by-field selection | Chooses A or B for Name, Email, Phone, Company, address fields, Tax exempt, and Credit limit. |
| Blank-field fallback | A selected empty text value can fall back to the available master or secondary value in the database function. |
| Phone-line consolidation | Combines both line arrays plus the selected primary phone and deduplicates normalized numbers. |
| Balance | Exact sum of both stored customer account balances; verify against open A/R records. |
| Store credit | Exact sum of both stored store-credit balances; verify against the combined liability ledger. |
| Reassigned sales and operations | Sales, parked sales, storefront orders, payment intents, gift cards, recurring billing, financing, and customer-linked inventory movements move to the master. |
| Reassigned customer context | Notes, interactions, A/R invoices, store-credit transactions, financing preapprovals, and matched CRM events move to the master. |
| Payment methods | Customer vault-card token rows move to the master; full card credentials are not displayed or merged in the dialog. |
| Groups | Secondary memberships are copied to the master without duplicate same-group links, then removed from the secondary. |
| Associations | Household/company member links are repointed to the master and use the merged name. |
| CRM event update | Repoints matched events and sets nondismissed rows to matched with customer_merge evidence; external-system deduplication is not guaranteed. |
| Transactional boundary | A database error aborts the merge instead of intentionally retaining a partially completed reassignment. |
| Merge into… | Irreversible confirmation naming the master and surviving code. |
| Post-merge verification | Identity, phone lines, balances, ledgers, receipts, notes, activity, tokens, groups, associations, financing, and external identities must reconcile. |
| No exact screenshot | The article omits a merge image until an exact safe Harbor & Hearth capture exists. |
Expected result
The verified master customer is the only remaining active contact; selected identity fields and deduplicated phone lines are correct; account and store-credit sums reconcile to their transferred A/R and ledger records; representative sales, notes, interactions, CRM events, groups, associations, tokens, financing, and other supported customer-linked rows point to the master; the secondary code is retired; and any distinct external CRM, accounting, financing, or processor identity has been reviewed separately.
Troubleshooting
- Search by more than one identity field before creating or merging a customer.
- Confirm the selected customer, company, or household before changing balances or associations.
- Do not place payment credentials or unnecessary private information in notes.
CentriPOS API explorer · API Center administration