A warehouse can have stock and still lack dispatch capacity. A carrier can offer a transit estimate and still not have received the parcel. The customer's decision depends on the combined journey, not the fastest number in either team's report.
Inventory gives one limit; the shared queue gives another
Fictional example: Alder sells a single boxed desk kit, one unit per order in the example window. All quantities, capacity, service assumptions and copy below are teaching inputs, not an Aright service promise or real carrier performance.
Assume 18 kits are physically present and released for their intended use. Two are protected safety stock. Six are committed to existing accepted orders. Inventory headroom for new orders is therefore 18 − 2 − 6 = 10 kits.
The same team can dispatch four kits per business day over the next three dispatch days: 12 slots in total. The six existing orders consume six of those slots. That leaves 12 − 6 = six new slots, not twelve. Inventory allows ten, but the declared dispatch window allows six. The new-order limit is the smaller number: six.
This filled schedule demonstrates one feasible allocation, rather than merely assuming that the old orders are somebody else's problem:
| Dispatch day in the planning window | Existing orders | New orders | Total kits dispatched |
|---|---|---|---|
| Business day 1 | 4 | 0 | 4 |
| Business day 2 | 2 | 2 | 4 |
| Business day 3 | 0 | 4 | 4 |
| Total | 6 | 6 | 12 |
The six new orders can therefore be dispatched on days two or three, under these assumptions. Four physically uncommitted kits remain after those new allocations, but no further slot exists in this window. Selling them under the same promise would overbook work without overselling physical stock.
Shopify's inventory-state guidance distinguishes stock available to sell from committed and unavailable quantities. It does not supply Alder's labour capacity. A stock counter and a service-capacity limit need to be reconciled, not treated as equivalent controls.
Separate acceptance, handling and transit
For this fictional offer, assume:
- Orders accepted by 14:00 warehouse time, fixed at UTC−5 for this exercise, enter that business day's plan. Later orders enter the next business day's plan.
- Handling uses Monday–Friday business days, excluding the relevant non-working holidays. No holiday interrupts the example's three-day window.
- New accepted orders in this window are handed to the carrier in two to three business days, as the schedule shows.
- The verified carrier estimate for the specifically served US postal-code zone is three to five business days after handoff. Its business-day calendar matches the handling calendar for this example.
- Other postal codes have no established estimate and must be checked before payment. No expedited service has been verified.
The combined estimate for an eligible order accepted before cutoff is therefore five to eight business days, not two to three. It is a planning estimate, not a guaranteed arrival date. Cutoff, holidays, destination and interruptions can change what a real checkout must display.
Google Merchant Center's delivery guidance separately defines the calculation using handling, transit and cutoff with business-day calendars. That helps expose the missing time; it does not certify this fictional carrier's estimate or replace checking the actual route.
Put the important distinctions where the buyer decides
A weak module says:
In stock. Delivery in 2–3 days. Order now.
It collapses the inventory and capacity decisions and calls handling “delivery.” A replacement example could read:
Alder desk kit — this dispatch window
For the listed eligible US postal codes, we can accept up to six new one-kit orders in this window. Availability is checked again before payment.
Dispatch: Two to three business days after acceptance for orders confirmed by 14:00 warehouse time (UTC−5 in this example). Orders confirmed later start the next business-day plan.
Carrier transit: An estimated three to five business days after dispatch. The combined estimate before cutoff is five to eight business days; this is not a guaranteed arrival date. Business days exclude weekends and applicable holidays.
Different address or a fixed deadline? Ask us to confirm the route before paying. We have not established expedited delivery. Do not order on the assumption that the handling estimate is your arrival date.
The checkout needs a shorter confirmation of the same meaning: the customer's destination, accepted dispatch window, delivery estimate and applicable charges should be visible before commitment. It must not revert to a generic “2–3 day delivery” badge or silently move an order into a later queue.
This copy is a fictional finished example, not a claim that a six-slot allocation feature exists. A real implementation must enforce the limit across all sales channels and simultaneous checkouts. If it cannot confirm a slot reliably, use a genuine pre-payment confirmation process instead of taking payment against a guessed date. Multiple units consume multiple kit slots, even if the cart contains only one order number.
What happens when the sixth slot is taken?
Pause this window's purchasing or present a separately supported later offer before payment. Updating the advertisement alone is too slow: an old email, saved link or returning visitor can still reach checkout. The final acceptance boundary needs the current information.
Existing customers require separate treatment. A new page cannot rewrite their accepted promise. For covered US online merchandise orders, the FTC's consumer explanation discusses the seller's stated shipment timing and the delay choice of agreeing to wait or cancelling for a refund. Dispatch obligations and customer rights need proper application to the real transaction; a carrier estimate is not permission to ignore them, and US guidance is not every market's rule.
If a carrier interruption or staffing loss undermines the window, stop adding affected orders, identify the accepted orders and follow the appropriate customer process. Do not respond by relabeling a missed dispatch as “extra processing time” after the fact.
The promise changes when the constraint changes
Alder could accept more if independently confirmed extra dispatch capacity becomes available, existing commitments move through an agreed process, or the next window is supported separately. More stock alone does not solve this window's labour constraint. Equally, extra staff does not replace product availability or a feasible carrier route.
Before launch, walk one order through a before-cutoff address, an after-cutoff address, the last available slot and an unserved postal code. Confirm that payment, order messages, warehouse instructions and support use the same dates and definitions. These are proposed tests, not observed results.
A clear delivery promise is the visible result of a commercial decision: this product, for this address, at this time, within this capacity. Write that decision first. A reassuring number can come afterwards—if the business can stand behind what the number means.