Skip to main content
FHAVI

Free resource

Choose the promise your fulfilment can actually keep

A delivery estimate is a promise a customer will hold you to, and a reviewer will check for consistency. Most stores set it from a competitor's site rather than from their own measured times — which is how a store ends up with a 3–5 day promise on a 12-day supply chain.

Read this first

Two numbers, not one

Delivery time is handling time plus transit time. Handling is how long before the parcel leaves the warehouse; transit is how long the carrier takes. Suppliers quote one number and call it the other constantly, which is why a “5-day delivery” turns into eleven days when you count from payment.

Where you are drop-shipping, handling also includes the supplier's queue. If they dispatch in three days and transit is eight, the honest promise is not five days. It is “ships in 3 working days, arrives 8–12 days after dispatch” — and both halves must appear on the site.

Set the promise from your measured worst week, not your best. A promise kept 95% of the time generates complaints; one kept 99% looks like reliability.

Step 1

Measure before you publish

01

What to record

  1. Payment to dispatch, per order, across at least twenty orders — not a supplier's stated handling time.
  2. Dispatch to first delivery attempt, per order, from the carrier's own tracking timestamps.
  3. The worst case in that sample, not the median. Customers remember the worst case.
  4. Failure modes: what happens to a parcel refused, returned or lost, and how long that adds to resolution.
  5. Cost per order for the carrier you actually use, including the return leg where applicable.

Step 2

Write the promise in the four places it appears

02

Where it must be identical

  1. The shipping policy page — handling time, transit time, carriers, cost, and what happens for remote areas.
  2. The product page — the delivery line customers read before deciding, not a vague badge.
  3. Checkout — the number shown next to the shipping option, matching the policy page exactly.
  4. Merchant Center shipping settings — the same processing and transit windows, or a reviewer sees a mismatch.
  5. Order confirmation — restating the same number, because that is the page customers screenshot.
03

How to word it honestly

  1. State handling and transit separately, in working days, with the carrier named for each option.
  2. Give a range grounded in your sample, not round numbers chosen to look fast.
  3. Say what happens at busy periods, rather than silently breaking the promise in December.
  4. State clearly whether the estimate is from payment or from dispatch.
  5. If you offer expedited shipping, only publish it if you have measured it for that carrier route.

Step 3

What promising too fast actually costs

04

The arithmetic nobody runs

  1. Every day a promise overstates speed adds a share of customers who ask for a refund before delivery — and a refund before delivery is a lost order, not a return.
  2. It also adds support volume, which is a cost per contact rather than a percentage you notice.
  3. Under-promising costs conversion on the product page; over-promising costs refunds, chargebacks and reviews. Pick the cheaper failure.
  4. If the honest promise kills conversion, the fix is a nearer supplier or a different product — not a shorter promise.

More resources

Keep going

The rest of the library

Every checklist here is free and ungated. The research pages carry the reasoning behind them.

All resources · Research library

Delivery promise and reality disagree?

Send your median and worst-case dispatch-to-delivery. We will tell you whether the fix is the carrier, the supplier or the promise on the page.

Prefer email? Write to md@fhavi.com