No second customer with the same phone number
The customer asks: A cashier creating a customer whose mobile number is already on another one gets the existing customer, not a duplicate
- Verdict: Ready, with limits (4)
- Door: Configure · area: Customers and loyalty › New and existing customers
- Recipe: Save rules: one tax id per customer group, and a submit kept for a role
- Sample: none yet
- Checked: carried 2026-10-25 · not re-run (read in the POS app's code)
What you build
At the till, nothing: when the cashier adds a new customer, a phone number already on an enabled customer attaches that customer instead of making a second one. The till compares digits only, reading a leading 0 with your site's dialling code (on a UAE site, 0501234567 is +971 50 123 4567), and looks in both the till's Phone Number and Desk's Mobile No. Online it also matches a known e-mail. For customers made in Desk, by an import or over the API, add save rules of kind unique across on the customer's Mobile No and on its Phone Number (card unique-across-records), and a pattern rule of shape international number if every number must be written the same way.
Limits
- A save rule compares the number as written, in one field: 0501234567 and +971501234567 are two values to it, and a number in Mobile No is not compared with one in Phone Number. Use the pattern rule, so every number is written the one way.
- A disabled customer still holds its number for the save rule, while the till skips it when matching: with a rule on Phone Number, the till's new customer with that number is then refused.
- Offline, the till matches by phone only. A number written with 00 in front is not matched with one written with +.
- Two people sharing one number: the till always attaches the existing customer, so the second can be made only in Desk, and a save rule refuses it there too. Showing the cashier the customers with that number to choose from is a request to us.
Tell the customer
A customer is found by their phone number at the till, so a returning customer is not created again; with the save rules set, the back office refuses a second customer with the same number written the same way.
What next
- Tell the customer the 4 limits above, and write them into the proposal.
- Follow the recipe: Save rules: one tax id per customer group, and a submit kept for a role.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Check it on your sandbox as the people who will use it; where it touches a price or a total, the money kit's release gate proves it (testing and release).
- Make the same settings on the customer's site, from the list you wrote down, through the customer's own change process.
Nothing to code: write down each setting you make on your sandbox, so it is made the same way on the customer's site.
Related needs
- A tax number on one customer only — Ready, with limits (5)
- No more than so many manager discount approvals per store per day — Ready, with limits (5)
- Only the receiving store receives a transfer; only a supervisor cancels it — Ready, with limits (4)
- Refuse a batch whose remaining shelf life is below our minimum, unless a named role accepts it — Ready, with limits (4)
Start a project shortlist with this need · Put it in your blueprint · Every need