Case study · ecommerce · conversion

The missing delivery date: Why 'when will it arrive?' decides the sale

An interactive case study: a gift shop finds shoppers leave because they can't tell if a present will arrive in time, and tests an honest delivery date.

Teaching example

Slide 1 of 10

Parcel & Petal: lots of browsing, not much buying

Parcel & Petal sells flowers and small gifts for delivery. Product pages get plenty of visits, but the add-to-cart rate is low compared with similar categories in the shop.

Nothing on the page looks broken. So what's missing?

Phil says: When nothing looks broken, the problem is often a question the page doesn't answer.

Slide 2 of 10

WXM 1 · Wonder (Look)

Wonder: what the numbers show

The team checks tracking, then looks at the product pages by traffic source and day of week.

  1. Add-to-cart is lowest from Wednesday to Friday, the days before weekend birthdays and events.
  2. Many visitors click from the product page to the Delivery information page, then leave the site from there.
  3. Site search for 'next day', 'Saturday delivery' and 'arrive by' is common.
Product page add-to-cart rate by weekday Original wireframe, not a screenshot.
  1. A timing pattern. The closer to the weekend, the fewer shoppers add to cart.

Slide 3 of 10

WXM 1 · Wonder (Look)

Wonder: what shoppers are asking

Numbers suggest timing. The team reads chat logs and adds a one-question survey on product pages: Is anything stopping you from ordering today?

  1. Chat: the most common question is some version of "Will it arrive by Saturday?"
  2. Survey: "Not sure it'll get there in time", "Couldn't find delivery days".
  3. Published research points the same way: in Baymard's US survey, 20% of abandoners cite delivery being too slow. [Source](#src-baymard-checkout)

Phil says: For a gift, 'too late' is the same as 'never'. The shopper isn't asking about price. They're asking about a date.

Slide 4 of 10

WXM 1 · Wonder (Look)

Wonder: what the shopper sees today

The product page shows a photo, price, a card message field and the button. Delivery timing lives on a separate page.

Control (A)
Product page, current version Original wireframe, not a screenshot.
  1. Answer hidden. The question that decides the sale is behind a link to another page.

Slide 5 of 10

WXM 2 · Architect (Plan)

Architect: from evidence to a hypothesis

Because chat logs, site search and survey answers show shoppers can't tell whether a gift will arrive in time, we believe showing the next available delivery date and the real order cut-off under the price for all product pages will increase orders per visitor, because it answers the deciding question at the moment of decision.

Your turn: Which of these would turn the delivery line into a dark pattern?
Show Phil’s answer

A countdown that restarts every time the page loads. A timer that resets isn't a real deadline. It's fake urgency. A real cut-off, and an honest later date when it has passed, give shoppers information they need.

Phil says: Notice it says 'real cut-off'. If the shop can't keep the promise, the test would win orders and lose customers.

Slide 6 of 10

WXM 2 · Architect (Plan)

Architect: how does it score on PXL?

A small, visible change on every product page, supported by survey and analytics evidence. The build needs live cut-off data from the courier, so ease is moderate.

PXL score: 10 / 14

PXL criteria breakdown
Is the change above the fold?Yes1
Is it noticeable within 5 seconds?Yes2
Does it add or remove an element?Yes2
Is it designed to increase user motivation?Yes1
Does it run on high-traffic page(s)?Yes1
Does it address an issue found in user testing?No0
Does it address an issue found in qualitative feedback (surveys, polls, interviews)?Yes1
Does it address insights found in digital analytics?Yes1
Is it supported by mouse-tracking heatmaps or eye tracking?No0
Ease of implementationUnder 2 days1

PXL by CXL. A high score ranks an idea; it does not predict a win.

Slide 7 of 10

WXM 3 · Validate (Test)

Validate: the variation

One line under the price shows the delivery date and the real cut-off. After the cut-off, it shows the next honest date. Nothing else on the page changes.

Control (A)
A: delivery details on a separate page Original wireframe, not a screenshot.
Variation (B)
B: delivery date and real cut-off under the price Original wireframe, not a screenshot.
  1. The deciding answer. When it arrives, and what to do to make that happen. Pulled from live courier data.

Slide 8 of 10

WXM 3 · Validate (Test)

Validate: the test plan, written before launch

Fixed in advance:

  1. Primary metric: orders per product-page visitor.
  2. Guardrails: late-delivery complaints, refunds, average order value.
  3. Duration: whole weeks, because behaviour changes by weekday. Avoid big holidays, or plan the test around one on purpose.
  4. QA: cut-off switches correctly at 2 pm in the shop's time zone; dates are right for weekends and bank holidays; screen readers announce the line.
  5. Decision rule: ship if orders improve and late-delivery complaints don't rise.

Phil says: The scariest bug here is a wrong date. QA the cut-off on a Friday afternoon, not on a quiet Tuesday morning.

Slide 9 of 10

WXM 4 · Expand (Grow)

Expand: whatever the result, the cycle continues

This is a teaching case, so there's no result to report. Here's what each outcome would lead to.

  1. Win: show the same date in the basket and confirmation email, and test a 'choose your delivery day' picker.
  2. Inconclusive: maybe the dates themselves are too late. Next Wonder: how many shoppers need Saturday delivery?
  3. Loss: check whether showing dates put off shoppers outside the next-day area. Segment by postcode region.

Slide 10 of 10

Your turn

Read your last 50 chat or support questions from shoppers who hadn't ordered yet. What's the most common question? If your product page doesn't answer it next to the button, you have a hypothesis. Use the ecommerce CRO checklist for more.

What this case teaches

  • Wonder combined weekday analytics, site search and chat logs to find the question behind the drop.
  • Architect built an ethics check into the hypothesis: the promise must be real.
  • Validate planned QA around the riskiest detail, the cut-off time.
  • Expand kept the next questions specific: dates, regions, delivery days.

Parcel & Petal is a made-up shop used for teaching.

Frequently asked questions

Should product pages show an estimated delivery date?

When timing matters to shoppers, usually yes, as long as the date is accurate. A real cut-off and a realistic date answer the question 'will it arrive in time?' before the shopper has to go looking.

Is a delivery countdown a dark pattern?

Not if the cut-off is real and the date is accurate. It becomes one when the timer resets, the cut-off is invented, or the date is optimistic. Then it's fake urgency.

Is Parcel & Petal a real company?

No. It's a made-up shop used to teach the method, so there's no real result to report.

Sources (3)

  1. 50 Cart Abandonment Rate Statistics 2026. Baymard Institute. Accessed 12 November 2026.
  2. WXM: the Wave Experimentation Model. Wavesy. Accessed 4 November 2026.
  3. PXL: A Better Way to Prioritize Your A/B Tests. CXL. Accessed 4 November 2026.

Learn the principles behind this case

Search lessons, guides, case studies and templates. Press Esc to close.