Delivery Options and Costs, Stated Before Checkout
Delivery choices should be understandable before the buyer reaches them: what the options are, what each costs, and when each arrives. This guide covers naming options plainly, defaulting honestly and keeping promises consistent.
The short answer
State delivery options the way buyers decide between them: by arrival and by cost, together, in plain names. Every option wherever it is chosen - cart estimate or checkout step - should carry its price and its realistic arrival window in the same line, and the totals must update the moment the option changes. Name options by what the buyer gets ('arrives Thursday', in your own realistic terms) rather than by internal courier service names that mean nothing to them. Delivery clarity is mostly a labelling and consistency discipline, and it removes one of the most common late surprises in the whole journey.
The decision starts before checkout
Buyers plan around delivery before they check out: a gift deadline, a holiday, a work trip. The cart should therefore carry a delivery estimate for the standard option, and the product page its short line as covered earlier in this bench, so the checkout selection confirms an expectation instead of creating one. Where an exact choice needs a postcode, ask for it in the cart with a clear purpose and remember it into checkout rather than asking twice. An estimate later contradicted is worse than none; keep estimates honest ranges and let the checkout refine, never worsen, the story without explanation.
Name options by arrival and cost
Internal names leak into checkouts constantly: service codes, courier product names, warehouse shorthand. Rename options around the buyer's two questions - when does it arrive and what does it cost - and keep any courier naming secondary or absent. Where options differ in kind rather than speed, such as collection versus delivery, name the kind first and its terms beside it: where collection happens, when it is ready, what to bring. A buyer choosing between clearly named options feels served; a buyer decoding service codes feels that the store's back office has been left in the shop window, and hesitates accordingly.
Defaults must be honest, not strategic
The preselected option should be the one most buyers would choose knowing the facts - usually standard delivery - never the fastest or most expensive option set quietly as the default to lift revenue. A buyer who discovers at the payment review that an express charge was applied by default reads it as a trap, and the discovery colours the whole order. If your standard option is free, the default is easy. If buyers genuinely split, consider no preselection with the options clearly priced, rather than a default that profits from inattention. Defaults are a trust surface: treat them as a promise, not a lever.
When the choice changes the total, show it working
Selecting a delivery option is a price event, so the order total must update visibly and immediately, with the delivery line itemised in the summary the buyer carries through payment. Never let the summary lag a step behind the selection, and never let a later screen restate the total differently. Where choosing an option affects availability of another promise - a faster option that cannot include a bulky item - say so at the option, not after selection. Buyers accept paying more for faster arrival readily when the exchange is explicit; it is ambiguity about what changed and why that sends them backwards.
Remote areas, heavy items and other honest edges
Most delivery resentment is born in exceptions: the postcode that costs more, the island that takes longer, the item too heavy for the standard service. Surface the exceptions as early as your systems know them - at postcode entry in the cart is far better than at payment - and in the same plain terms as the main options. A buyer told early that their address changes the price has information; the same buyer told at the final step has a grievance about the whole journey. Review your exception wording whenever carriers or zones change, and keep product page promises inside what the exceptions allow.
One story from product page to doorstep
The delivery option chosen, its cost and its window should read identically in the cart, the checkout, the confirmation email and the dispatch notice, allowing only for the window becoming a date as time passes. Inconsistencies between these documents are read as carelessness with the buyer's money and time. Assign one source of truth for option names and windows inside the business, and let every template draw from it. The companion guide on delivery and returns on product pages begins this story; checkout is where the story is either confirmed as trustworthy or quietly rewritten.
Sources and evidence on the record
- Baymard Institute, research blog - published findings from its checkout and product-page usability studies.
- Shopify, Shopify Help Center - platform documentation for themes, cart, checkout and Shop Pay.
Evidence basis: Platform guide. Behaviour described is as documented by the platform in the sources listed below, checked on 24 October 2026; platform behaviour changes, so re-check before a rebuild. Applies when: Any store offering more than one delivery speed, method or price