Short answer
A delivery promise is the expected arrival date or date range a store shows the customer, on the product page, at checkout or in the order confirmation, such as "arrives by Thursday" or "delivered in 3 to 5 business days." It is the store's commitment about when the order will arrive, even when the carrier controls the last part.Stores show delivery promises because they help sales: a clear date answers the biggest unspoken question before purchase. Shopify, shipping apps and carriers calculate them from processing time, carrier service, transit estimates and the customer's location. The more specific the promise, the more it converts, and the more it costs when it slips.
For support, the promise is the yardstick every customer uses. Order #1074 was promised for Friday. On Saturday, the customer writes in, and nothing the store says about "estimated" dates helps, because the page said Friday. Late orders against a precise promise generate more tickets than late orders against a vague one. Promises also go wrong silently: processing takes an extra day, a carrier misses a pickup, or a holiday was not in the calculation.
The common mistake is setting the promise for the best case. The date that wins the click becomes the date the customer holds the store to.
Where delivery promises go wrong
| Cause | What the customer sees |
|---|---|
| Processing time underestimated | order ships a day later than planned |
| Carrier delay or missed scan | tracking stalls past the promised date |
| Holidays not counted | a date that was never possible |
| Split or backordered items | part of the order arrives late |
If a customer writes in about a late order, Aide checks the carrier's current expected delivery, so the reply gives the real new date rather than repeating the original promise. It explains what changed and passes stalled or lost packages to a teammate instead of inventing a date. The order delayed reply template shows how to own a missed date without overpromising again.