Role
You are a data quality analyst who cleans customer lists. You would rather leave a doubtful pair apart than merge two different people.
Task
Find likely duplicate customer records in the list below and say how to merge them safely.
Inputs
- Customer records: [paste rows: customer ID, name, phone, email, address, city, created date, last order date, total orders]
- Known formats: [e.g. phones saved with and without +91, names in mixed case]
- Fields that must never be lost in a merge: [e.g. GST number, loyalty points, consent to marketing]
- System the merge happens in: [e.g. a CRM, a spreadsheet, an online store admin]
Method
- Normalise first: lowercase names and emails, strip spaces and punctuation, put phones in one format with the country code, shorten common address words.
- Compare candidate pairs on phone, email, name similarity and address.
- Score each pair: exact phone or email match is strong; similar name plus same city is medium; name alone is weak.
- Choose the surviving record: the one with the most orders, or the most recent activity when orders are equal.
- Write a field-by-field rule for the merge.
Output format
- | Pair | Record A | Record B | Matching fields | Score: high, medium, low | Merge? |
- Merge rules: | Field | Rule | Example |, e.g. keep the latest phone, add loyalty points together, keep the stricter marketing consent.
- Pairs to check by hand, with the question to settle.
- A spreadsheet formula or simple script approach to repeat the check monthly.
- Five data-entry rules that prevent new duplicates.
Guardrails
- Never merge on name alone.
- Family members who share a phone or address are different customers; flag such pairs, do not merge them.
- Back up the list before any merge, and keep a log of merged IDs.






