Pre-Orders: Does “Released” Mean Paid, Ready to Ship or Already Delivered?

For a pre-order, agree separately when the customer pays, when the product leaves its pre-release stage and when the order is fulfilled. One green “complete” label should not stand in for all three. A release date also needs a clear meaning: it must not quietly become a guaranteed delivery date.

This is commissioning guidance for a shop or ordering app. It does not define cancellation rights, accounting treatment or whether a promised date is legally acceptable. Have those questions reviewed for the actual business and market.

Show the payment promise before checkout

A hypothetical shop might take payment for a forthcoming printed workbook immediately, or wait until release. Those choices affect what the customer needs to understand before placing the order. Avoid an ordinary “buy now” presentation that leaves the timing unclear.

The WooCommerce Pre-Orders documentation distinguishes upfront payment from payment upon release. Upfront means charging at checkout. For release-time payment, the documented process can use a supported gateway to charge automatically or ask the customer to pay through a payment-required email.

Do not assume that saving an order means money has been collected. Ask the implementer which path your actual payment integration supports, what the customer sees and how staff recognise a failed or still-required payment. Keep payment credentials out of staff notes and acceptance examples.

Name the release milestone without claiming delivery

WooCommerce has a pre-order status separate from the normal order status. Completing the pre-order moves it into ordinary order management. The underlying order may still need payment or processing; the documentation does not make release completion equivalent to delivery.

For your app, decide what release actually authorises. Does it open a download, start warehouse preparation or ask the customer to pay? Write that event beside the status rather than relying on a vague “completed” badge.

For physical goods, keep preparation, dispatch and receipt distinct from the release milestone. For a digital item, define what grants access and what a customer sees if payment remains outstanding. Do not infer either path merely from the presence of a date.

Treat a delay as a change to an existing promise

Agree who may change availability and how existing customers will be told. Preserve enough history to distinguish the date originally communicated from the current expectation. A revised product page alone may not explain the change to someone who already ordered.

Check the exact date-change and release controls in the chosen implementation. WooCommerce documents a dedicated release-date action for active pre-orders. Do not assume that every administrative date edit executes the same release or payment actions. Rehearse the supported path on controlled records, including time-zone display and an unpaid order.

Cancellation needs a separate money follow-up

The documentation expressly warns that cancelling an upfront-paid pre-order does not automatically reverse its charge. Model cancellation and refund handling as separate work with a responsible person. A cancelled order must not disappear from the team’s view while an unresolved customer payment remains.

The same principle applies to messages: an email saying “cancelled” should not say “refunded” unless the refund result is known. Decide what staff do when payment or refund status is uncertain rather than blindly repeating a money-changing action.

Check the cart you actually intend to sell

WooCommerce Pre-Orders documents an important product restriction: one pre-order product per order, without other products. That is not a universal rule for custom shops, but it can change a purchasing journey that assumes customers can combine a future release with immediately available goods.

Before committing to a solution, test your intended mixed-cart journey and decide whether separate orders are acceptable. Include upfront payment, release-time payment, a changed date, release with payment still due and cancellation with an unresolved refund in the brief for your ordering app. The useful outcome is a clear customer promise with a traceable handover into payment and fulfilment, not just a countdown.