Every WooCommerce order moves through a series of states, from the moment a customer clicks “Place order” to the moment it’s delivered or refunded. Those states, the WooCommerce order statuses, aren’t just labels. They trigger emails to customers and staff, reduce or restore stock, decide whether an order appears in sales reports and control what customers see in their account.
When store owners misunderstand them, real problems follow. Orders sit in “pending payment” because a webhook failed, and nobody notices. Customers receive a “completed” email before their parcel has even shipped. Stock is reduced for orders that were never paid. This article explains each default status, what moves an order between them and when adding your own custom statuses makes your workflow clearer.
The default statuses
Pending payment
The order has been created, but payment hasn’t been received. This happens when a customer starts a payment at an external gateway and hasn’t completed it, or when payment failed and they haven’t retried.
Pending orders don’t reduce stock by default in all cases, and they don’t count in sales reports. WooCommerce automatically cancels unpaid pending orders after a time limit set under WooCommerce, Settings, Products, Inventory, “Hold stock (minutes)”.
A large number of pending orders that never move on usually means one of two things: customers abandoning at the payment step, or payment confirmations failing to reach your store, typically due to webhook problems.
Failed
Payment was attempted and declined, or the payment gateway reported an error. The customer may retry. Failed orders don’t reduce stock and don’t count as sales.
A spike in failed orders can indicate card testing attacks.
Processing
Payment has been received, stock has been reduced and the order needs fulfilling. This is the status most physical-product stores work from day to day. WooCommerce sends the customer a “Processing order” email, and the admin receives a “New order” email.
Orders containing only virtual and downloadable products skip processing and go straight to completed, since there’s nothing to ship.
On hold
The order is awaiting action, usually payment confirmation for offline methods such as direct bank transfer or cheque. Stock is reduced, so the items are reserved, but the order isn’t confirmed as paid. You change it to processing manually once payment arrives.
On hold is also used by some gateways and fraud tools when a payment needs review.
Completed
The order has been fulfilled. For physical products, that should mean shipped. WooCommerce sends the customer a “Completed order” email. Completed orders count fully in reports.
A common mistake is marking orders completed when they’re packed but not yet handed to the courier, or using completed to mean “delivered”. Decide what completed means for your store and use it consistently, because the email customers receive says their order is complete.
Cancelled
Cancelled by an admin or the customer, or automatically when pending payment times out. Stock reduced for the order is restored. No payment is captured.
Refunded
Fully refunded. WooCommerce sets this automatically when a full refund is processed. Stock can be restored during the refund. Partial refunds don’t change the status, but they appear on the order and in reports.
Draft
Introduced with the block-based checkout, checkout-draft is a temporary status for orders being built during checkout before the customer places them. You won’t normally see these in the orders list, and they’re cleaned up automatically.
How statuses connect to stock and emails
Understanding these links prevents surprises:
- Stock is typically reduced when an order moves to processing, on hold or completed, and restored when cancelled.
- Customer emails are sent for processing, completed, on hold, refunded and failed transitions, plus notes you send to the customer.
- Admin emails are sent for new orders, cancelled orders and failed orders.
You can enable, disable and customise these emails under WooCommerce, Settings, Emails.
Common problems and their causes
Orders stuck in pending payment although customers were charged. The gateway’s confirmation didn’t reach your site. Check webhook settings and logs in the gateway dashboard, and make sure firewalls, security plugins and caching don’t block the webhook URL.
Orders going straight to completed for physical products. Products may be incorrectly marked as virtual, or a plugin automatically completes orders.
Customers receiving the wrong email. Statuses were changed in an order that doesn’t match your actual process, or bulk actions changed many orders at once.
Stock not reducing. The order skipped a status that reduces stock, or stock management is disabled for the product.
When custom statuses help
The default statuses suit simple stores. Stores with more complex fulfilment often need more steps. Examples:
- Awaiting artwork for personalised products, where the customer must approve a design before production
- In production for made-to-order items
- Ready for pickup for click and collect
- Shipped separately from completed, when completed means delivered
- Awaiting stock for backorders
- Quality check before dispatch
- Return requested for returns workflows
Custom statuses make the orders list easier to read and filter. Staff can see at a glance which orders are waiting for which step. They also allow targeted emails, such as notifying the customer when their order is ready for pickup.
Adding custom statuses
Several plugins add custom order statuses with a settings screen, including options for colours, icons, emails and whether the status counts as paid. For most stores, a well-maintained plugin is the easiest route.
For developers, registering a status takes a small amount of code:
With High-Performance Order Storage, statuses are stored in the orders table, but registration works the same way.
To count a custom status as paid in reports and analytics, add it to the paid statuses with the woocommerce_order_is_paid_statuses filter. To send an email on transition, create a custom email class or use a plugin that provides one.
Things to check before adding statuses
- Reports and analytics. WooCommerce Analytics only includes certain statuses by default. Configure “Actionable statuses” and “Excluded statuses” under Analytics settings so custom statuses are counted correctly.
- Integrations. Shipping, accounting and fulfilment integrations often only recognise default statuses. A custom status may stop orders from syncing. Test each integration.
- Payment gateway behaviour. Some gateways set statuses automatically after payment. Make sure your custom statuses fit in after that, not instead of it.
- Stock handling. Decide whether stock should be reduced or restored when entering or leaving your custom status.
Keep it simple
Add only the statuses your team actually uses. Each new status is another thing for staff to remember and another place for orders to get stuck. A store with three custom statuses that everyone understands works far better than one with ten that half the team ignores. Clear WooCommerce order statuses, used consistently, make fulfilment smoother for staff and clearer for customers.
Designing statuses around your real process
Before adding anything, write down how an order actually moves through your business. Who sees it first? What has to happen before it can ship? Where do orders wait, and why? The answers often reveal that the default WooCommerce order statuses already cover most steps, and that one or two custom statuses would fill the gaps.
For example, a bakery offering local delivery might use processing for paid orders, a custom “Baking” status for orders in production, a custom “Out for delivery” status with an email to the customer, and completed when delivered. A print-on-demand store might add “Awaiting approval” for customer proof sign-off. A store with click and collect might add only “Ready for pickup”.
Each custom status should answer a question the team asks often, such as “which orders are waiting for artwork?”, and should tell the customer something useful when it changes.
Training staff
Statuses only work if everyone uses them the same way. Write a one-page guide explaining what each status means in your store, who changes it and when, and which emails the customer receives. New staff can learn the workflow in minutes, and experienced staff stop improvising.
Automating status changes
Some status changes can be automated safely. Shipping integrations can move orders to a “Shipped” status when a label is printed or a tracking number is added. Delivery confirmations from couriers can trigger completion. Automation reduces manual work and keeps customers informed promptly, but test each rule carefully, because an automation that misfires can send hundreds of misleading emails in minutes. Start with one automated transition, watch it for a few weeks and add more only when it proves reliable.
Frequently asked questions
Can customers see order statuses?
Yes, in My Account, Orders, and in emails. Choose clear, customer-friendly names for custom statuses.
Can I change many order statuses at once?
Yes, with bulk actions in the orders list. Be careful, because each change may trigger customer emails.
Why do some orders go straight to completed?
Orders containing only virtual and downloadable products skip processing by default.
Will custom statuses survive switching to HPOS?
Yes, as long as they’re registered in code or by a plugin that supports HPOS.




