Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

E-commerce Marketing › E-commerce Conversion

Setting and Keeping Delivery Promises

How online stores set delivery promises they can keep, state them the same way on pages, feeds and ads, handle peaks and delays, and measure promises kept.
Guideintermediate11 min readUpdated

A delivery promise is a claim

Every store makes a delivery promise, whether it means to or not. The product page says "free delivery over a certain amount" or "arrives in a few days"; the checkout offers options with dates or costs; the confirmation email names a day; the shopping ad shows a delivery cost. Each is a statement the customer relies on, and together they form the promise. Customers decide to buy partly on it, and they decide whether to buy again largely on whether it was kept. The repeat purchase and loyalty guide names delivery as promised among the first-order experiences that decide whether a second order follows.

Treating the promise as a claim changes who sets it. It is not copy for the marketing team to make attractive. It is a commitment the business has to keep, which means operations set it and marketing states it. Consumer protection bodies take the same view of claims generally: the free shipping threshold experiment records that bodies such as the Competition and Markets Authority expect prices and delivery charges to be presented clearly. That is direction, not legal advice; take advice on the rules in each market where the store sells.

Setting a promise operations can keep

Delivery is capacity, in the same sense as stock or staff hours. The guide to marketing within capacity lists delivery and fulfilment among the capacities operations share with marketing, with cut-off dates, backlog and regions with longer lead times as the things to watch. The promise has two parts that operations own: how long it takes the store to dispatch an order, and how long the delivery service takes from dispatch to the door.

Set each from the store's own records rather than from what competitors advertise. For dispatch, look at how long orders actually take from payment to leaving the building, on ordinary days and on busy ones, and what the cut-off time for same-day dispatch really is. For delivery, look at how long parcels sent by each service actually took to arrive, by destination area. Then set the promise at a point the store meets on nearly every order, not on an average day. A promise met on average is missed on a large share of orders.

Different products may need different promises. Items that ship from another warehouse, are made to order, or are too bulky for the usual service take longer, and a single promise stretched over all of them is either too slow for most products or false for some. Split the promise by product type where the difference is real, and show each product's promise on its own page. The guide to selling made-to-order and personalised products covers stating the making time apart from delivery and keeping customers informed while the item is made.

Part of the promiseWho sets itWhere the evidence comes from
Dispatch time and cut-offOperationsThe store's own order and dispatch records
Delivery time by service and areaOperationsDelivery records from each service the store uses
Delivery cost and any free-delivery thresholdCommercial owner, with financeContribution per order; the threshold experiment
Wording and placementMarketing, checked by operationsThe promise operations set, stated without rounding up
Changes for peaks and delaysOperations, announced by marketingBacklog, capacity plans and the services' own notices

The cost side of the promise, including whether a free-delivery threshold is worth having, belongs to the average order value guide and the free shipping threshold experiment, which tests it.

Stating it the same way everywhere

A promise that differs from one place to another is a broken promise even before the parcel ships. The customer who sees one delivery cost in an ad and another at checkout, or a date on the product page and a later one in the confirmation, concludes that at least one of them was not true.

Cost and date belong early. The checkout optimisation guide reports that the Baymard Institute's research finds costs that appeared late the most-cited reason for abandonment, with slow delivery also among the reasons shoppers give; that is a reason to show delivery cost and timing on the product page rather than revealing them at the last step, and it bears directly on the cart abandonment rate. The product page optimisation guide places the delivery cost, any threshold and an arrival estimate near the button.

The same promise has to reach the places the store does not render itself:

  • The shopping feed. The Merchant Center feed setup checklist sets shipping and returns settings to match the site, by country. The product feeds guide treats shipping as a feed attribute, from Google's product data specification, and keeps offers such as free delivery out of product titles, in the attributes where they belong. The product feed is a statement of the promise in its own right.
  • Structured data. The product structured data tutorial records that Google's merchant listings use more detailed offer data, including shipping and returns details, and adds them where the store shows them. The markup should say what the page says.
  • Ads and emails. Delivery claims in ad copy and campaign emails come from the same source as the page. When the promise changes, the ads and scheduled emails change with it.

The simplest way to keep these aligned is to keep the promise in one place, a short written statement owned by operations, and to check every channel against it whenever it changes.

Cut-off times, peaks and last order dates

The promise changes with the calendar. Each day has a cut-off time after which an order waits until the next dispatch; weekends and public holidays stretch the time to the door; and in peaks, dispatch slows as volume grows and delivery services slow too. A promise that ignores these is true on a quiet Tuesday morning and false the rest of the time.

State the cut-off plainly, near the delivery information on the product page and at checkout, so the customer knows whether ordering now or in an hour makes a difference. Before any date that matters to customers, such as a holiday or a season when people buy gifts, set a last order date for each delivery option, from operations' plan for that period, and state it once, in the same words, everywhere the promise appears. Then keep it. A last order date that the store quietly moves earlier when volume grows, or later to catch a few more orders, breaks the promise for everyone who relied on it. The guide to selling gifts online covers last order dates for gift seasons in detail.

During a peak, the capacity guide's choices apply: shift, slow, queue or stop demand. If dispatch falls behind, lengthen the promise on the site for new orders before the backlog grows, rather than taking orders the store knows it will deliver late.

International delivery

Delivery to other countries adds services, distances and costs that differ by market. The guide to localising websites and campaigns asks a store to state delivery times, costs, duties and returns terms that are true for each market, and notes that duties collected on delivery are a common cause of refused parcels and angry reviews; where they apply, say so and, where possible, include them in the price. The rules on duties and imports themselves are not covered here. The feed setup checklist's per-country settings apply to each market too: a feed that is right for one country can be wrong for the next.

Keeping customers informed after the order

Once the order is placed, the promise moves into the messages that follow it. The order confirmation restates the expected date; the dispatch message confirms it or corrects it; a delivery message closes the loop. The post-purchase email flow tutorial maps these order emails and fits the store's other post-purchase messages around them.

These are service messages, a kind of transactional email. The promotional versus transactional guide explains why they should stay free of promotion: a prominent offer turns a service message into a promotional one, with the rules that apply to marketing. A dispatch message that says when the parcel will arrive, and how to track it, does its job; one that leads with a discount code for the next order has changed what it is.

Customers who cannot find the answer in a message will ask. The support channels and self-service guide treats tracking queries as quick, repetitive questions that are better served by a self-service route than by a busy phone line; a tracking page and a help page that explain what each delivery status means are that route.

When a promise breaks

Some promises will break: a service has a bad week, a warehouse falls behind, weather closes roads. What decides the customer's view of the store is what happens next. Tell affected customers before they ask, with the new date, a one-sentence reason and what they can do if the new date no longer works for them, such as cancelling or changing the delivery option. Then update the promise on the site for new orders, so that the problem stops growing. The guide to proactive service messages applies the same habit to faults, cancellations and other disruptions, from finding who is affected to the closing message.

The service recovery and complaints guide covers making it right with customers who were let down, including what to offer and how to keep the remedy proportionate, and the tutorial on setting remedies and goodwill limits writes a standard remedy for a late delivery that every agent can offer without asking. If the broken promise was sent out in bulk, such as a confirmation email with the wrong date sent to every customer who ordered on one day, the guide to fixing a mistake in a sent email covers the correction. In every case, the delay notice is a service message and stays free of promotion.

Measuring promises kept

A delivery promise can be measured directly, from the store's own data. Three readings cover most of it:

  • Promises kept. The share of orders delivered by the date the customer was shown when they ordered. Record the promised date at the moment of the order, not the date recalculated later, and compare it with the delivery date the service reports. Read it by delivery option, product type and destination area, since a store-wide figure hides where the misses happen.
  • Contacts about delivery. The number of support contacts about where an order is, per order shipped. A rise means either the promise is missed more often or customers cannot find the answer themselves.
  • Repeat purchase by delivery experience. The repeat purchase rate of first-time customers whose first order arrived on time, compared with those whose first order arrived late. The difference is an estimate of what a missed promise costs, read with caution because the two groups may differ in other ways.

On the front of the funnel, watch the conversion rate (CVR) and checkout abandonment when the promise changes, so that a change in what is promised can be weighed against a change in how often it is kept. The tutorial on measuring whether delivery promises are kept builds these readings step by step, starting from the order, dispatch and delivery records.

A garden supplier resets its delivery promise (illustrative)

Illustrative example — not a real result

Mulchmerry Garden Supply splits its promise by product type

Mulchmerry Garden Supply is an invented online garden supplier. Its pages promise next-day delivery on everything. Seeds, tools and small items ship by a parcel service and mostly arrive the next day. Bulky compost and bark sacks go on a pallet service that takes three to five working days. Over a quarter, 71% of all orders arrive by the date promised, but only 18% of orders containing bulky items do, and delivery questions make up 44% of support contacts.

Operations set two promises: next working day for parcel items ordered before 1pm, and three to five working days for bulky items. The product pages, the checkout and the confirmation email show the promise for each item, and an order with both kinds shows both. The Merchant Center shipping settings are updated to match, with the bulky items in their own shipping group, and the ads stop saying "next-day delivery" for compost. The dispatch email for bulky orders now gives the delivery date the pallet service confirms.

In the next quarter, 93% of orders arrive by the date promised, delivery questions fall to 19% of contacts, and the share of first-time bulky-item customers who place a second order within three months rises from 14% to 22%. The team reads the last figure with caution, because spring demand also changed, and keeps measuring.

Common mistakes

  • Letting marketing set the promise. Operations set what can be kept; marketing states it.
  • Promising the average. A promise met on an average day is missed on many orders; set it where the store meets it on nearly every one.
  • One promise for every product. Bulky, made-to-order or remotely stocked items need their own.
  • Different promises in different places. The page, checkout, feed, markup, ads and emails should say the same thing.
  • Revealing delivery cost at the last step. Show it early, on the product page.
  • Moving a last order date after announcing it. State it once and keep it.
  • Taking orders the store knows will be late. Lengthen the promise for new orders before the backlog grows.
  • Promotions in delay notices. A delay notice is a service message; an offer in it reads as indifference.
  • Measuring delivery speed instead of promises kept. The customer judges the store against what it promised.

Frequently asked questions

Should a store show an exact delivery date or a range?

Show what operations can keep. A date is clearer for the customer, but it is only honest if the store knows its dispatch times and its delivery services well enough to hit it, and if the date shown accounts for the cut-off time, weekends and the customer's area. Where the store cannot be that precise, a range stated in working days, with the cut-off for same-day dispatch, is better than a precise date that is often missed. Whatever the format, the same promise should appear on the product page, at checkout and in the order confirmation.

Does the delivery cost in a Google shopping feed have to match the checkout?

The site's feed setup checklist sets shipping and returns settings in Merchant Center to match the site, by country, and the product feeds guide treats shipping as a feed attribute, from Google's product data specification. A shopper who sees one delivery cost in a shopping ad and another at checkout has been given a reason to leave. Check Merchant Center's current help pages for the detail of how shipping settings work.

What should a store do when it knows orders will arrive late?

Tell the affected customers before they ask, with the new date, the reason in a sentence, and what they can do if the new date no longer suits them. Then update the promise on the site for new orders, so the problem stops growing. The service recovery guide covers making it right afterwards. A delay notice is a service message, so keep it free of promotion.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Product data specification — Google Merchant Center Help
  2. Product structured data — Google Search Central
  3. Baymard Institute UX research — Baymard Institute
  4. Competition and Markets Authority — GOV.UK

Related