How to create custom order statuses in WooCommerce

Choose a short, unambiguous label such as Awaiting shipment, Ready for pickup or In production. Decide whether it is only an internal workflow label or whether customers should see it and receive an email.

Do not use a custom status as a replacement for payment logic. WooCommerce treats statuses such as Processing and Completed as paid statuses by default, so a new status may not appear in sales totals or reports unless you deliberately add it to the relevant workflow and reporting rules.

WooCommerce has no core admin screen for creating arbitrary statuses. The manual route requires two registrations: WordPress must know about the post status, and WooCommerce must include it in its order-status list. The standard pieces are register_post_status() on init and the wc_order_statuses filter.

Add this to a site-specific plugin or your child theme's functions file, not the parent theme:

add_action( 'init', function() { register_post_status( 'wc-awaiting-shipment', array( 'label' => 'Awaiting shipment', 'public' => false, 'show_in_admin_all_list' => true, 'show_in_admin_status_list' => true ) ); } ); add_filter( 'wc_order_statuses', function( $statuses ) { $statuses['wc-awaiting-shipment'] = 'Awaiting shipment'; return $statuses; } );

Use a unique key, keep it short, and include the wc- prefix in the registered status key. WooCommerce stores the status in a field limited to 20 characters, so an overlong key can fail when the order is saved.

Save the code, clear any cache, then open WooCommerce > Orders and edit a test order. The new label should be available in the status selector. Save the order and confirm that the label remains after refreshing the page.

If it is missing, check for a PHP syntax error, a duplicated status key, or code placed in a file that is not loading. If the status appears but orders disappear from the All view, check that show_in_admin_all_list and show_in_admin_status_list are enabled.

Move a test order from its current status to the new one, then check the order notes, customer account and admin order list. Also test a bulk update if your store relies on bulk processing.

A custom status does not automatically create a customer email, mark an order as paid, permit downloads, or include the order in every report. The transition itself is available to integrations through woocommerce_order_status_changed, but the email and business rules still need to be added separately.

For a code-only setup, you need additional development for a dedicated WooCommerce email, conditional automation, payment rules, customer cancellation rules or reporting changes. Do not assume that changing the label will trigger the Completed or Processing email.

If you use a status-management extension, create the email under its status-email settings or WooCommerce > Settings > Emails, enable it, select the correct transition and send a test. A common Friday-afternoon failure is creating the status but leaving its email disabled; another is selecting the same status as both the starting and ending status, which cannot trigger a transition email.

For most stores, the faster route is to install WooCommerce Order Status Control, activate it, then open its settings and add the status with its label, slug, colour or display options, customer visibility and notification rules. You can then manage statuses from the dashboard instead of maintaining PHP.

It fits when you need custom statuses together with conditional automation, bulk updates, notifications and change logs. The manual code route is fine for one simple internal status, but a plugin is safer when the status affects customers, fulfilment staff, emails or reporting.