Separate identity consolidation from entitlement correction
Synthetic customer IDs C-M1 and C-M2 are verified as the same person through accepted internal evidence. C-M1 survives. Their two packages are distinct purchases and remain separate records; their bookings are for different occurrences and both remain. Conflicting contact preferences enter review instead of selecting whichever enables more messages.
| Item | Before merge | After merge | Review requirement |
|---|---|---|---|
| P-C1 | C-M1 / 2 available | C-M1 / unchanged | Keep purchase and expiry |
| P-C2 | C-M2 / 3 available | C-M1 / separate P-C2 | Keep purchase and expiry |
| B-C1 and B-C2 | Different occurrences | Both reference C-M1 | Do not deduplicate by customer |
| Contact preference | Conflicting values | Review pending | Resolve from accepted evidence |
Preserve a reversible merge map
- Verify same-person evidence and choose the surviving identity.
- Inventory bookings, package IDs, membership intervals and contact conflicts before reassignment.
- Repoint references, retain C-M2 as a merged alias and reconcile all quantities and states.
Shared household details are not proof of one person. Uncertain identity blocks the merge; financial adjustments or erased purchase history are outside this workflow.
Does merging the customer create one five-session package?
Show the worked answer
No. The person has two separate packages with two and three available sessions. Their combined quantity is five, but allocation still checks each package’s own scope and expiry.
Keep pre-merge references and a post-merge reconciliation record so corrections can identify which source record needs restoring.