Customers often have their own numbers in stores, customer service and transaction systems. If you directly use the name to make the association, you will mistakenly identify the customer. If you use the mobile phone number, you may also encounter changing numbers or sharing contact information.

Difficulties in actual use

Establish a mapping between the source number and the platform main number, and clarify the authorization fields that can be used for association; low-confidence matches enter manual review, and the guess results are not written as confirmed facts.

How to arrange functions and responsibilities

For example, if two records have the same name but different order subjects, they should remain independent; record the basis when confirming the merger, and retain the entrance to cancel the merger.

Scenario example

Check whether the merged tags, orders and permissions have changed synchronously. Pay special attention to the historical reports after the revocation to avoid unbundling in one place while other data is still mixed together.

Check the processing results item by item

  • The merge operation should be previewed.
  • The page first displays which orders will be re-associated and which fields are in conflict, and then allows people with authority to confirm.
  • Which company the contact belongs to and whether there is a group relationship between the companies must also be expressed separately. Group relationships cannot replace customer identity.
  • Especially for historical reports summarized by customer, the total number may change after consolidation, and it should be stated that the change comes from related adjustments rather than new transactions.
  • It is recommended to retain the original source number and prevent business personnel from modifying the upstream primary key in order to adapt to the platform.
  • The review queue needs to display candidate reasons, and excluded combinations do not need to pop up repeatedly when the basis does not change.
  • In this way, manual judgment can gradually settle, instead of starting over every time it is imported.

Verification and continuous maintenance

Identity conflicts cannot be determined by technical personnel alone. The business party should explain the true relationship between the two subjects. The platform retains the pending confirmation status so that data whose association has not yet been determined will not be used for key customer statistics in advance.