If you sell pre-orders on WooCommerce, there's one failure that hurts more than any other: an order for a product that doesn't exist yet lands in Processing, your warehouse sees it, and someone tries to pack it.
It happens more often than you'd think, and it's rarely a bug in your shop. It's how WooCommerce order statuses work.
Why it happens
WooCommerce has no built-in idea of "paid, but must not ship yet". Once a payment succeeds, the gateway calls $order->payment_complete(), and WooCommerce moves the order to Processing (or Completed for virtual/downloadable products). To your fulfilment flow, Processing means "ship it".
Some common ways a pre-order ends up there:
- Card and wallet payments. Stripe, Apple Pay and Google Pay often confirm the payment through a webhook a few seconds after checkout. The webhook marks the order paid, and the status jumps to Processing.
- Cash on delivery. The COD gateway puts new orders straight into Processing by default.
- Manual and bulk edits. Someone selects 40 orders in the list and runs "Change status to Completed". The pre-orders go with them.
- Other plugins and automations. Shipping, ERP or label plugins that react to Processing will pick the order up the moment it gets there.
So putting "Pre-order" on the product page isn't enough. You need something that controls the order status.
The quick fix (and its limits)
If your gateways all go through payment_complete(), you can redirect pre-orders to another status with one filter:
add_filter( 'woocommerce_payment_complete_order_status', function ( $status, $order_id, $order ) {
foreach ( $order->get_items() as $item ) {
$product = $item->get_product();
if ( $product && 'yes' === $product->get_meta( '_my_preorder' ) ) {
return 'on-hold';
}
}
return $status;
}, 10, 3 );
This works for many gateways, but it leaves gaps:
- Gateways that set the status directly (like COD, which has its own
woocommerce_cod_process_payment_order_statusfilter) skip it. - A manual or bulk status change still goes through.
- On hold is shared with "awaiting bank transfer" and other cases, so pre-orders get mixed in with everything else.
- Nothing releases the orders when the product finally arrives. You have to remember to do it.
A more robust approach
The reliable way is to stop thinking about payments and guard the status itself:
- Give pre-orders their own status, for example "Pre-ordered", so they're never confused with other on-hold orders.
- Check every status change, not just the payment step. Whenever an order is saved, if it contains a pre-order item and its release date hasn't passed, block any move to Processing or Completed, and leave a note explaining why.
- Release automatically. A scheduled check moves orders to Processing once every pre-order item has reached its release date, and emails the customer.
- Allow an intentional override. If stock arrives early, an explicit "release now" action should be the only way to ship before the date.
Point 2 matters most: because it doesn't care how the change happened (a webhook, COD, a bulk edit, another plugin), it covers the cases the payment filter misses.
If you don't want to build it yourself
Disclosure: I'm the developer of Preorvo, a free plugin on WordPress.org that does exactly the four steps above. Paid pre-orders wait in their own "Pre-ordered" status, any early move to Processing/Completed is blocked and logged in the order notes, and orders are released and customers emailed on the release date. It works with HPOS and the block checkout.
https://wordpress.org/plugins/preorvo/
Whether you use it or roll your own, the key idea is the same: don't trust the payment flow to keep a pre-order on hold. Guard the order status.
If you've run into other ways pre-orders slip through, I'd like to hear about them in the comments.
Top comments (0)