A status shows where the order is. A due date answers when it will be ready.

Custom order statuses tell customers what stage the order is in. That is useful, but on its own it is only half the answer. The question underneath every status check is the same: when is this going to be done?

Without a date, even a clear status leaves room for anxiety. "In production" is informative. "In production, expected to ship by May 2" is reassuring.

The gap custom statuses cannot close on their own

Stages show movement. Dates show commitment. Customers lean harder on the second than most brands realize.

A status flow without dates works for short fulfillment windows, where the customer does not need to plan around the delivery. It breaks down on anything longer. Made-to-order, pre-orders, multi-week production runs, anything involving a supplier. Every one of these categories is dominated by a single customer question that a stage label cannot answer.

A visible due date on the order page is the most direct way to answer it.

Set the due date as early as possible

The best moment to set a due date is the moment the order is placed. Even an automatic default based on your standard lead time is better than nothing.

Automatic defaults work for predictable products. For made-to-order, custom work, or anything that depends on a supplier, a manual due date set by your team after reviewing the order is usually more accurate. Both approaches are valid. Most brands end up using a combination: automatic for the predictable majority, manual for the exceptions.

The important point is that the order page should almost never go out to the customer without a date on it. An empty due date field is a missed opportunity to remove ambiguity for free.

Use a range when a single date overpromises

Fulfillment timelines are usually a window, not a point. A due date of "May 2" sounds specific but can backfire if the actual date slips by a day. A due date of "May 2 to May 6" communicates the same intent without setting up a near-miss.

Ranges tend to perform well for:

• Made-to-order production with variable finishing time
• Pre-orders where the warehouse arrival window is known but not exact
• International shipping where the carrier timeline varies by a few days
• Any product with a build time that depends on material availability

For in-stock products with reliable same-day dispatch, a single date is fine. For everything else, a range protects both the customer and your team.

Match the wording to your brand

"Due date" is an operational term. It reads fine on a spreadsheet but can feel cold on a customer-facing page, especially for higher-end brands where the language around the purchase matters.

Customizable wording lets the label fit the tone of the store. A few examples:

• "Estimated ready date" for made-to-order workshops
• "Ship by" for fast-fulfillment retail
• "Arriving" for post-shipment tracking
• "Expected completion" for custom or commissioned work

The date itself is the load-bearing part. The wording is what makes it feel like it belongs on your brand's order page rather than a warehouse dashboard.

Show it on the order page and in every email

A due date that only lives on the order page gets checked less often than you might think. A due date that also appears in the order confirmation, the production update, and the shipping email is the one that actually sets expectations.

Email is where customers first encounter the date. The order page is where they verify it. Both need to show the same number, phrased the same way, or the two channels start to compete.

The order page has one advantage email does not: it updates in real time. If the date shifts, the page reflects the new date the next time the customer visits. Email snapshots the date at send time and never changes. Use both, but lean on the order page as the current source of truth.

Tell your own team when a due date changes

Due dates tend to move. A supplier is a day late, a run has to be redone, a quality check adds time. The customer-facing update is important, but the internal side matters just as much.

Internal email notifications on due date changes give operations, support, and sales a single source of truth without anyone having to check the order manually. Support knows before the customer does. Sales sees the change before a VIP pings them about it. Operations can respond to a slipped date while there is still time to do something about it.

This is one of those features that sounds minor and changes daily life. A team that gets notified when a due date shifts spends far less time answering internal messages about order status.

Treat a missed due date as a conversation, not a crisis

The worst outcome is not a missed due date. It is a missed due date the customer discovers themselves.

If a date is about to slip, update it early and send a short, specific note. "We are moving your due date from May 2 to May 6 because of a supplier delay" almost always lands well. A silent slip followed by an apology later almost never does.

Because the date is visible on the order page, changing it takes seconds. Because it is in the notification system, the customer hears about it automatically. The whole sequence takes less effort than replying to one frustrated email after the fact.

Final takeaway

Custom statuses show the customer where their order is. Due dates show them when it will be done. Putting both on the order page, in every email, and in front of your own team turns a post-purchase experience from reactive into predictable.

StatusPro supports automatic and manual due dates, date ranges, customizable wording, order page and email display, and internal notifications when a date changes, so Shopify merchants can keep customers and their own team aligned on every order.