Make the Phone Field Optional Unless Delivery Actually Needs It

Count the fields in your checkout and ask what each one earns. The phone field usually cannot answer. It sits there because the platform default put it there, required, with a validation rule strict enough to reject perfectly real numbers.

We have removed or relaxed this field on multiple stores. Nothing in the warehouse caught fire. Completion, particularly on mobile, got a little better, and a little better on a field everyone touches is not little.

When a number is genuinely needed

Same day and local delivery, freight and pallet drops, click and collect where a text signals readiness, and some international routes where the courier will not attempt delivery without a local number. Those are real requirements, attached to specific delivery methods.

So attach the requirement to the method. If the shopper picks same day courier, ask then, with one line explaining why: the driver will text you. Context converts a suspicious demand into an obvious favour, and shoppers give numbers freely when the reason is standing next to the field.

Format validation is where the damage happens

Strict phone validation rejects valid numbers constantly: spaces, brackets, country codes typed with or without a plus, numbers pasted from a contacts app in formats the regex did not imagine. Each rejection is a full stop in the flow with an error that often insists the shopper's own phone number is wrong.

Accept digits generously, normalise in the background, and only block on the obviously empty or impossibly short. A loose field with a working order beats a pristine database field attached to an abandoned checkout, every single time.

The privacy hesitation is real and unspoken

Plenty of shoppers will hand over an email and balk at a phone number, because they know what follows: marketing texts they did not ask for. If the number is for delivery only, say so at the field, delivery updates only, and then honour it in your messaging platform settings, not just in the copy.

Nothing burns trust faster than an order update number that starts receiving promotions. It also, in many jurisdictions, creates a consent problem your legal team will enjoy even less than your customers do.

What to do on Shopify and similar platforms

Set the field to optional in checkout settings, then use delivery method logic, or a post purchase step for the orders that need it, to collect the number only where it matters. Test mobile completion before and after for at least a full traffic cycle before declaring victory.

Keep an eye on courier exception rates for a month. In our experience they do not move, because carriers were rarely using the number for standard parcels anyway. If yours do move, you have learned something specific about your carrier mix, and you can target the ask precisely.

Frequently asked questions

Why do checkouts ask for a phone number at all?

Historically for delivery problems and order questions. In practice, standard parcel carriers rarely call, and most contact is by email or tracking updates. The field persists mainly as a platform default rather than an operational need.

When should the phone field be required?

When the chosen delivery method needs it: same day courier, freight, click and collect text notifications, and some international services. Attach the requirement to that method and explain why at the field, rather than requiring it from everyone.

Can strict phone validation hurt conversion?

Yes. Shoppers paste numbers with spaces, brackets, and country codes in formats strict rules reject. Each false rejection stalls the order and tells the shopper their real number is wrong. Validate loosely and normalise behind the scenes.

Should I collect phone numbers for marketing instead?

Not inside the delivery field. If you want SMS marketing consent, ask for it separately with clear opt in language. Mixing marketing collection into a delivery field creates both a trust problem and, in many places, a consent problem.