Set up customer verification
Last updated: September 9, 2026
By default, anyone with a tracking link can open the page and see it. Customer verification lets you put a check in front of that — so a customer has to prove who they are with a detail only the real recipient would know before the page unlocks, or before they can change any delivery detail.
You set it up in the Customer verification section of the editor sidebar, on the During delivery tab of Engage ▸ Tracking Customization. The setting is one standing configuration for your whole organization, like the rest of the tracking page — it applies to every customer page Nash renders once you save.
Availability varies by organization. Customer verification is a gated, pilot capability. If you don't see the Customer verification section, or you'd like it turned on, reach out to Nash — it isn't something you switch on yourself.
What you configure
The section is three controls over a single verification setting. Choose a method first; the other two controls stay disabled until you do.
Verify customers with
The check the customer has to pass. Pick one:
- Off — no verification; anyone with the link can open the page.
- Last 4 digits of their phone number.
- Delivery postcode.
- Order reference.
Whatever you pick has to be a detail Nash actually holds for the delivery. An order that doesn't carry the detail you chose can't be verified — with View the tracking page those customers never get past the verification screen, and with Edit delivery details they're offered nothing to edit. The editor calls this out beneath the control.
What the check protects
Choose what the verification gates:
- View the tracking page — the customer has to verify before they see the page at all. Until they do, they get a branded verification screen instead of the tracking page.
- Edit delivery details — the page is open to anyone with the link, but a customer has to verify before they can change any of the details you allow below.
Customers can edit
When you gate Edit delivery details, tick the fields a verified customer is allowed to change:
- Delivery instructions.
- Phone number.
- Delivery address, before a driver is assigned.
If you choose Edit delivery details but tick no fields, the customer has nothing to edit — the editor flags that so you don't leave it half-set.
Compatibility notes
Some methods only make sense when the page isn't already giving the answer away. If you protect edits with the delivery postcode, for example, the page can't also be showing the dropoff location or the live driver pin — those reveal the postcode, so the check would be pointless. Where a combination like this conflicts, the editor shows a note right beside the control telling you exactly what to change (which section to hide, or to verify to view the page instead). Fix what the note asks and the conflict clears; the setting is also checked again when you save.
Preview it on every tab
The live preview shows your verification setting on all three journey tabs — Before delivery, During delivery, and After delivery — so you can see what the customer meets at each stage:
- A View the tracking page gate shows the branded verification screen on every tab, so you can confirm the locked page looks right end to end.
- An Edit delivery details gate shows the edit affordances only on the tab and for the fields where they apply, with verified-only details kept hidden until the customer passes the check.
The preview is illustrative only — it doesn't submit anything. As with the rest of the tracking page, nothing changes for your customers until you Save.
Related
- Customize your tracking page — the rest of the editor: the two panes, the tabs, and how to save.
- How the tracking page works — how one org-level configuration becomes each customer's own page.
- Choose what appears on the tracking page — the sections a compatibility note may ask you to hide.