| Term<\/th> | What it measures<\/th> | Who controls it<\/th> | What the customer sees<\/th><\/tr><\/thead> | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Dispatch date<\/strong> (also: ship date, date of dispatch)<\/td> The day the parcel is handed to the carrier<\/td> | You \u2014 your processing time and cutoff<\/td> | \u201cYour order has been dispatched\u201d<\/td><\/tr> | Shipping date<\/strong><\/td> | Ambiguous. Sometimes the dispatch day, sometimes the whole transit period<\/td> | Depends entirely on who wrote it<\/td> | Usually a source of confusion<\/td><\/tr> | Delivery date<\/strong><\/td> | The day the parcel actually arrives at the address<\/td> | The carrier, inside the window you set<\/td> | \u201cArriving Thu, 14 May\u201d<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n | These three terms get used interchangeably online, but they measure different parts of the order journey. Here’s exactly what each one means, how large the gap between them usually is, and how to use them correctly on your own store.<\/p>\n\n\n\n Dispatch Date: When the Order Leaves Your Hands<\/h2>\n\n\n\nThe dispatch date \u2014 sometimes called the ship date, the date of dispatch, or the shipment date \u2014 is the day your warehouse actually hands the package to the carrier. This is entirely within your control, and it’s driven by your processing time and order cutoff time.<\/p>\n\n\n\n If an order is placed after your daily cutoff, the dispatch date pushes to your next working day. This is the number most stores get wrong when they promise \u201cship in 24 hours\u201d without a clear cutoff \u2014 an order placed at 11pm often can’t reasonably dispatch by the next morning.<\/p>\n\n\n\n Two things the dispatch date is not<\/em>: it is not the day the customer’s payment cleared, and it is not the day you printed the label. A parcel sitting on your packing bench with a label on it has not been dispatched. The carrier taking possession is the event that matters, because that is the moment transit time starts counting.<\/p>\n\n\n\n \u201cShipping date\u201d gets used two different ways depending on who’s talking, which is exactly why it causes confusion. Sometimes it means the same thing as dispatch date. Other times it’s used loosely to mean the entire shipping period \u2014 as in \u201cshipping takes 3-5 days,\u201d which is really describing transit time, not a single date.<\/p>\n\n\n\n The honest answer: this term is genuinely ambiguous in everyday use. If you’re writing customer-facing copy, avoid \u201cshipping date\u201d on its own and use \u201cdispatch date\u201d or \u201ctransit time\u201d instead, so there’s no room for the reader to guess which one you mean.<\/p>\n\n\n\n The delivery date is the one number customers actually care about: when the package physically arrives at their door. It’s the sum of your processing time, plus dispatch, plus carrier transit time, minus any non-delivery days in between.<\/p>\n\n\n\n This is also the number most stores fail to calculate correctly. It requires combining several variables, not just carrier transit time on its own.<\/p>\n\n\n\n A plugin like QuickShipD handles this by combining your delivery days, cutoff time, and non-delivery days into one accurate window. That’s different from just showing carrier transit time and calling it \u201cdelivery.\u201d<\/p>\n\n\n\n No \u2014 and this is the single most common mix-up in ecommerce. They are separated by the carrier’s transit time, which is almost never zero.<\/p>\n\n\n\n The confusion is understandable, because the two get collapsed constantly in everyday language. A store writes \u201cships in 2 days\u201d and a customer reads \u201carrives in 2 days.\u201d Both people think they had the same conversation. Then the parcel turns up on day five and only one of them is surprised.<\/p>\n\n\n\n There is exactly one case where the two dates genuinely coincide: same-day local delivery, where you dispatch and deliver inside the same working day using your own driver.<\/p>\n\n\n\n In every other setup \u2014 a national carrier, a courier, anything crossing a border \u2014 there is a gap. Pretending otherwise is what generates \u201cwhere is my order?\u201d tickets.<\/p>\n\n\n\n If you are a shopper and your tracking page has just changed to \u201cdispatched,\u201d it means the store has finished its part. The parcel has physically left the seller and is now with the carrier. Nothing more is waiting on the store.<\/p>\n\n\n\n What it does not<\/em> mean is that delivery is imminent. Dispatched is the starting gun for transit, not the finish line. From that moment the clock the customer cares about is the carrier’s transit time, which is why a status of \u201cdispatched\u201d on a Friday afternoon frequently means a Tuesday arrival rather than a Saturday one.<\/p>\n\n\n\n Store owners: this is a useful thing to say out loud in your dispatch email. \u201cYour order has been dispatched and is expected to arrive by Thursday 14 May\u201d prevents far more support tickets than \u201cYour order has been dispatched\u201d on its own, because it answers the question the customer is about to ask anyway.<\/p>\n\n\n\n It varies by service, and knowing the rough shape of it is what lets you set an estimate you can actually hit. These are typical ranges rather than guarantees \u2014 check them against your own carrier’s published transit times and, better still, against your own order history.<\/p>\n\n\n\n Note that every figure in that table starts after<\/em> dispatch. Your own processing time sits in front of all of it. A store with a two-day processing time on a 3\u20135 day standard service is quoting a customer five to seven days, not three to five \u2014 and that arithmetic is where most inaccurate estimates come from.<\/p>\n\n\n\n |
![\"order](\"https:\/\/quickshipd.com\/blog\/wp-content\/uploads\/2026\/04\/order-cutoff-time-1024x439.png\")
<\/figure>\n\n\n\n![\"delivery](\"https:\/\/quickshipd.com\/blog\/wp-content\/uploads\/2026\/04\/dates.png\")
<\/figure>\n\n\n\n