Estimated Delivery Dates — The Most Underrated Conversion Lever in the Cart

Ask a shopper what they want to know before they check out and delivery timing will be in the first three answers. Look at what most Shopify stores show them and you will find either a shipping speed, a policy link, or nothing at all.

That gap is unusual in ecommerce, because closing it is cheap, technically straightforward and produces a measurable effect on both conversion and support load. It just does not look like a growth lever, so it stays on the backlog behind things that do.

Why a date beats a speed

"Ships in 1–2 business days, delivery 3–5 business days" is a sentence that asks the reader to do work.

To turn it into an answer they need to know: what time your cut-off is, whether today counts, whether Saturday counts, whether the two ranges are additive, and what your carrier does over a public holiday. Most people will not do that calculation. They will approximate it, get it wrong, and either accept a vague sense of "about a week" or go and look for a clearer answer somewhere else.

"Arrives Tuesday 26 August" removes all of it. There is no arithmetic, no assumption and no ambiguity. It is also, importantly, a commitment, which is a different psychological object from an estimate — and commitments are what shoppers use to decide.

The gap widens on mobile, where the shopper is more likely to be doing something else at the same time and much less likely to sit and work out what "3–5 business days from Thursday" means.

What uncertainty costs you

The mechanism is specific and worth naming, because it explains where the value comes from.

A shopper in your cart who is unsure about delivery has three options. Guess and continue. Leave the cart to find your shipping policy. Or abandon.

The middle option is the expensive one, and it is the most common. It requires navigating away from the cart, finding a policy page written for legal completeness rather than for answering this question, parsing a table, and then finding their way back. Every step in that sequence is a place to lose them, and the policy page is a particularly good place to lose them because it usually does not answer the question either.

Putting the date in the cart removes the reason to leave.

Calculating a date you can honour

The estimate is the sum of four components. Getting it right is mostly about not forgetting any of them.

1. Order cut-off. Orders after your daily cut-off do not start processing until the next working day. This is the component most often omitted, and it is why so many estimates are systematically one day optimistic.
2. Processing time. From paid to handed to the carrier. Be honest about this. If your warehouse takes two days during peak, the peak estimate is two days.
3. Transit time. Per carrier, per service level, per destination lane. Not one global number.
4. Non-working days. Weekends, and the public holidays of both the origin and destination country.

Then apply a confidence policy. You have two reasonable choices:

• A range — "26–30 August". Honest, easy to hit, slightly less persuasive.
• A single date at a high percentile — the date you hit 90% of the time, not the date you hit on a good week. Persuasive, and safe if you actually use the percentile rather than the median.

What you must not do is show the best-case date. A promise you keep two thirds of the time is worse than no promise at all, because the third of customers you miss are now customers with a specific grievance rather than a vague disappointment.

Where to show it

Three surfaces, in descending order of value.

The cart

Highest value, because this is where uncertainty converts directly into abandonment. The shopper has committed to the products and is now evaluating the transaction as a whole, and delivery timing is the largest remaining unknown.

Place it near the subtotal, in the same visual group as the shipping line. It should read as part of the transaction summary, not as a marketing message.

The product page

Second, and it does a different job. In the cart the date removes an objection; on the product page it influences the add-to-cart decision itself, particularly for gift purchases and anything with a deadline. "Order within 4 hours for delivery Tuesday" is the strongest legitimate form of urgency available to an ecommerce store, because it is simply true.

The order confirmation

Third, and mostly a support-cost play rather than a revenue one. Repeating the date after purchase reinforces the expectation and removes the reason for the customer to write in on day three.

Localisation is not optional here

Of everything in a cart, the delivery estimate is the element that varies most by destination — and therefore the element most damaged by showing one global value.

Three rules:

• Compute per destination lane. Domestic transit time shown to an international shopper is not an estimate, it is a false claim.
• Use the destination's calendar. Public holidays at the destination affect final-mile delivery. So do the origin country's holidays for dispatch.
• Format the date unambiguously. 08/09 is 8 September in most of Europe and 9 August in the US. Spell the month.

If you cannot compute a defensible estimate for a market, show nothing there. An absent estimate is neutral. A wrong one is a liability.

The honest limits

Delivery dates are not a magic lever and it is worth being clear about where they do not help.

• If your delivery is genuinely slow, showing the date will reduce conversion on those orders. That is the estimate working correctly — you are filtering out customers who would have been disappointed and become refund requests. It is a short-term loss and a long-term gain, but it is a real short-term loss.
• If your fulfilment is unpredictable, an estimate makes the unpredictability visible and quantifiable, which will generate complaints you were previously absorbing invisibly. Fix fulfilment first.
• If you dropship from multiple origins, a single order can have several arrival dates. Showing one date for a multi-origin order is worse than showing per-item dates, even though per-item dates look messier.

What to measure

• Cart-to-checkout rate, before and after. This is where the effect should show up first.
• Add-to-cart rate on product pages that gained the estimate.
• "Where is my order" ticket volume as a share of orders. Expect a meaningful decline.
• On-time delivery rate against the shown estimate. This is the guardrail. If it drops below your target percentile, widen the estimate rather than hoping.
• Refund and cancellation rate for late orders specifically.

The last two are what keep this honest. An estimate engine is only as valuable as the promise it makes is reliable, and the only way to know that is to score yourself against the date you displayed rather than the date you hoped for.

Frequently asked questions

Share: X LinkedIn Copy link

Ninety9 Team

We build 5 conversion apps used by Shopify merchants in Bulgaria and beyond. Everything we write here comes out of what we see in real store data.