Estimated Delivery Date on Shopify

An estimated delivery date answers the question a shopper asks right before adding a product to the cart: when will this arrive? A store that answers it on the product page saves the shopper a trip to the shipping policy, a guess, or an email to support. A store that answers it badly, with a date that slips or a countdown that resets every visit, trades a small convenience for a broken promise. This post explains where Shopify shows a delivery estimate on its own, the four inputs every honest estimate is built from, a worked example with three shoppers, and how to word and time the line so it reads as what it is: an estimate from your own schedule.

Where Shopify shows a delivery estimate today

Shopify has fulfillment time and delivery date settings in the shipping area of the admin. Its Help Center says those settings display estimated arrival times at checkout. The page does not describe a product page placement, and checkout is late in the visit: by then the shopper has already chosen the product, the size and the quantity.

That gap is why stores add a delivery line under the price or the add to cart button. The line does not change shipping rates, carriers or what checkout charges. It repeats, earlier in the visit, a date your own operations already imply. Everything that follows is about making sure the date it prints is the date your warehouse and your carrier can meet.

The four inputs behind every honest estimate

Any delivery date, from any tool, is arithmetic on four inputs. Get them right on paper first, then type them in.

1. The daily cutoff. The time, on your store's clock, after which a new order waits for the next packing day. Use the time your last parcel actually leaves, minus the time it takes to pick and pack one order, not the time the carrier truck arrives.
2. Packing days. How many working days pass between the order and the hand-off to the carrier. In-stock items might pack the same day; personalized or made-to-order items might need five days.
3. Working days and closed dates. The weekdays you ship, plus the holidays and shutdowns when nobody packs. A count that ignores a closed week in late December prints a date you cannot meet.
4. Transit ranges. The earliest and latest delivery, in working days, for each destination you ship to. Take them from your own tracking history, not from the quickest service the carrier advertises.

The estimate is then simple: start from the order time, move to the next packing day if the cutoff has passed, add the packing days while skipping closed days, then add the transit range. The result is a pair of dates, the earliest and the latest, or a single date if you prefer to show the later one only.

A worked example: one product, three shoppers

Take a candle shop that ships Monday to Friday, has a 2 p.m. cutoff, packs in-stock candles the same day and closes from December 24 to December 26. Its transit range is two to four working days in the United States and five to eight working days to Canada.

A shopper in Ohio orders on a Tuesday at 11 a.m. The cutoff has not passed, so the order packs that Tuesday. Two to four working days of transit gives Thursday to the following Monday. The product page says the order arrives between those two dates.

A second shopper in Ohio orders the same Tuesday at 4 p.m. The cutoff has passed, so packing moves to Wednesday, and the range moves to Friday through Tuesday. If the first shopper's tab is still open at 2 p.m., the line should change at that moment, not on the next page load, or it will show a date the shop has already missed.

A third shopper in Toronto orders at 11 a.m. on the same Tuesday. Packing is the same, but the Canadian range applies, so the line shows a later window. If the shop also sells a hand-poured candle with three packing days, a rule for that product, tag or collection adds those days for every destination.

Word the line so it reads as an estimate

A product page is not the place for legal fine print, but the words still matter. "Arrives Thu, Dec 4 to Mon, Dec 8" tells the shopper exactly what to expect. "Get it by Monday" sounds friendlier, and it is also a promise you need to keep for every order that sees it.

The FTC's Mail, Internet or Telephone Order Merchandise Rule, in 16 CFR Part 435, asks a seller to have a reasonable basis for any shipping time it states, and sets out what to do when an order cannot ship on time. Our post on shipping promises and the FTC 30-day rule walks through the text. For a delivery line, the practical reading is to keep records that support your packing days, to widen a transit range before a peak season rather than after, and to show a range when a single date would hide real variation.

Three wording habits help:

• Name the day of the week. "Thu, Dec 4" is quicker to read than a bare date, and it makes a weekend gap obvious.
• Say what the countdown is for. "Order within 2 hours 10 minutes" means little on its own; "Order within 2 hours 10 minutes to get it by Thu, Dec 4" ties the timer to a reason.
• Handle the edge cases in plain words. Where you do not ship, write that, instead of leaving the line blank. When an option is sold out, hide the date or show your own backorder text.

Countdowns that stay truthful and accessible

A countdown to the cutoff is useful only when the cutoff is real. A timer that restarts on every visit, or that counts down to an arbitrary moment, teaches shoppers that your dates are decoration. Tie it to the same cutoff your warehouse uses, and let it end: after the cutoff the line should move to the next date and say so.

Timers are also auto-updating content in the sense of WCAG 2.2. Success criterion 2.2.2, Pause, Stop, Hide, covers information that starts on its own and updates next to other content, and asks for a way to pause, stop or hide it unless the update is essential. In practice that means the ticking digits should not be read aloud every second, the remaining time should be available as plain words, and animation should stop for shoppers who ask for reduced motion.

Check the schedule before peak season

Build the schedule once and review it before each busy period. A short routine covers most stores:

• Pull the last few weeks of orders and compare the date each one shipped with the date it was placed. That gap is your real packing time.
• Compare the tracking delivery date with the ship date for each destination you serve, and set your transit ranges from those, rounded out to whole working days.
• Enter every holiday and planned shutdown for the year, including the days your carrier does not deliver.
• Open a product page from a phone just before and just after the cutoff, and from a second country if you ship abroad, and check that each date matches your arithmetic.

If a range slips during a peak, widen it the same day. A later date that holds builds more trust than an early one that misses, and a few minutes in the settings is cheaper than the support tickets a missed date brings in.

When a delivery line is not the right fit

A product page date is not for every store. If most of your orders ship from several warehouses with different schedules, a single schedule per store will be wrong for some of them. If you need the date to follow the order into the cart, checkout and confirmation emails, a product page line covers only the first step. And if your shipping times change daily with carrier capacity, an estimate from fixed ranges cannot keep up; you need live carrier data instead.

For everyone else, the work is mostly the arithmetic above. Once the cutoff, packing days, closed dates and transit ranges are written down, putting them on the product page is the easy part.