Cookies on softitland.com

We use essential storage to run this site. With your permission we would also like to use analytics cookies to see which pages help visitors, and marketing cookies to measure our ads. You can change your choice at any time with “Cookie settings” in the footer. Privacy Policy

Ecommerce

WooCommerce High-Performance Order Storage: what to check before you switch

Moving a WooCommerce store to High-Performance Order Storage: plugin checks, compatibility mode, staging tests, WP-CLI checks and rollback.

Cover image for the article WooCommerce High-Performance Order Storage: what to check before you switch
Key takeaways
  • Stores installed before WooCommerce 8.2 may still keep orders in the WordPress posts tables until someone switches them.
  • WooCommerce blocks the switch while incompatible plugins are active; custom code and outside systems need their own check.
  • Compatibility mode syncs both storage systems, so you can switch and switch back without downtime.
  • Rehearse on a staging copy of the live database and time the sync before touching the live store.
  • Run the cleanup command only after the store has run cleanly through a full business cycle.

What should you check before switching WooCommerce to HPOS?

Confirm that every plugin, your theme code and every outside system work with the new order tables, rehearse the move on a staging copy, turn on compatibility mode and let the sync finish, then switch while sync stays on so you can switch back at once if something breaks. Delete the old order data only after the store has run cleanly for a while.

High-Performance Order Storage (HPOS) moves WooCommerce orders out of the general WordPress posts tables into dedicated order tables. According to the WooCommerce developer docs, it has been on by default for new installations since WooCommerce 8.2 in October 2023. Older stores are a different story: the WooCommerce HPOS document says existing stores will not be migrated over to HPOS automatically. If your store is older than that, it may still be on the old storage today.

What does HPOS change in your store?

Before HPOS, orders lived in wp_posts and wp_postmeta, the same tables as pages, posts and products. HPOS stores them in four tables of their own: wc_orders, wc_order_addresses, wc_order_operational_data and wc_orders_meta, as listed in the developer docs.

WooCommerce's own platform update reported up to 5x faster order creation and up to 1.5x faster checkout from the change. Treat those as WooCommerce's figures, not a promise for your store. The practical point for this checklist is different: any code that still reads orders from the posts tables will, after the switch, read stale or missing data. The HPOS recipe book warns that directly reading from the WordPress tables may mean reading an outdated order.

How do you know your plugins are ready?

WooCommerce checks for you. Under WooCommerce, Settings, Advanced, Features, the HPOS document explains that the option to switch is disabled while incompatible plugins are active, and a "View and manage" link lists them. The same document says all extensions sold on WooCommerce.com are HPOS-compatible, so the risk sits mostly with free plugins, older plugins and custom code.

  • Plugins: a compatible plugin declares it in code with FeaturesUtil::declare_compatibility( 'custom_order_tables', __FILE__, true ), per the recipe book. A plugin that declares nothing is not proof of a problem, but it needs testing.
  • Custom code and theme functions: search for get_post(), get_post_meta() and update_post_meta() used on orders. The recipe book replaces them with wc_get_order() and the order's own meta methods followed by save().
  • Extensions built on custom post types: the HPOS document says extensions such as Woo Subscriptions and WooCommerce Bookings must be active before you switch, or the data can fall out of step.

If a plugin you depend on is not ready, update it, ask its developer, replace it, or have the code fixed. Our guide to custom or off-the-shelf WordPress plugins helps with that choice, and our WordPress plugin development team updates custom plugins to the WooCommerce order API.

What about systems outside WordPress?

This is the step most often missed. Accounting links, shipping tools, reporting databases and any script that queries the database directly may read the posts tables. WooCommerce's guide for large stores asks you to verify that data warehouses, shipping tracking and accounting systems are not reading the posts tables directly, and to update them before you continue.

Make a list of every system that reads or writes orders, and check how each one connects. Integrations that use the WooCommerce REST API are usually fine; direct database queries are not. If your store also syncs stock with a POS, read our guide to syncing a POS with WooCommerce stock and include that link in your checks.

How does compatibility mode work?

Compatibility mode keeps both storage systems in step during the move. The enable HPOS guide puts it under WooCommerce, Settings, Advanced, Features, labelled "Enable compatibility mode (synchronizes orders to the posts table)".

  • When you tick it, WooCommerce schedules background actions that copy existing orders across in batches of 25, which you can watch under WooCommerce, Status, Scheduled Actions (enable HPOS guide).
  • Orders created or changed while sync is on are copied straight away, per the developer docs.
  • The same docs say you cannot switch storage while orders are still waiting to be synced.

How should you test the switch on staging?

WooCommerce's platform update recommends testing on a staging site before the live store. Copy the live database to staging, run the sync there and time it, because that tells you how long the live sync will take. The large store guide notes that WooCommerce's own test store of 9 million orders took about a week.

The WP-CLI tools help on stores of any size. Use wp wc hpos count_unmigrated to see what is left, wp wc hpos sync to run the copy, and wp wc hpos verify_data and wp wc hpos diff to compare the two stores of data. The older wp wc cot commands are deprecated.

Then test the store the way customers and staff use it:

  • Checkout with every payment method, including a failed payment.
  • Refunds, order notes, status changes and customer emails.
  • Subscription renewals, bookings or memberships if you use them; see our WooCommerce subscriptions guide.
  • Order search, exports, reports, shipping labels and accounting sync.

How do you switch and roll back safely?

  • Take a full backup first, as WooCommerce recommends before updates.
  • With posts storage still in charge, turn on compatibility mode and wait until the sync is complete.
  • Switch Order data storage to High-performance order storage, keeping compatibility mode on.
  • Watch new orders, emails and integrations closely for the first days.

The enable HPOS guide calls it advisable to keep compatibility mode on for some time after the switch. While it is on, the large store guide says the store can be reverted to the posts table instantly, with no downtime. In that guide, WooCommerce turned off sync on read first and fully disabled sync only after one week of stable operation. Once sync is off, a rollback means backfilling the posts tables before you can switch back.

When is it safe to delete the old order data?

Only when you are sure you will not roll back. The CLI docs describe wp wc hpos cleanup, which removes the old order data once HPOS is on and compatibility mode is off, as a destructive operation. Check your backups, confirm every integration has run through a full business cycle, such as a month-end close, and then clean up.

Our ecommerce development team runs HPOS switches end to end: the plugin and code audit, staging rehearsal, the switch and the rollback plan. For stores that need ongoing care afterwards, our maintenance and security team keeps updates and backups on a schedule.

Frequently asked questions

Is HPOS already turned on for my store?

Check WooCommerce, Settings, Advanced, Features and look at Order data storage. Stores installed on WooCommerce 8.2 or later started with HPOS by default. Older stores stay on WordPress posts storage until someone switches them, even after updating WooCommerce, so many established stores have never moved.

Will customers notice the switch?

Done carefully, no. With compatibility mode keeping both stores of data in step, the switch itself needs no downtime, and you can switch back at once if something breaks. The risk is a plugin or integration that reads the old tables, which is why you test checkout and integrations on staging first.

What if a plugin we rely on is not compatible?

WooCommerce will not let you switch while an incompatible plugin is active. Update the plugin, ask its developer about HPOS support, replace it, or have a developer update its code to use the WooCommerce order functions. Do not deactivate plugins that store data in custom post types just to get past the check.

How long does the order sync take?

It depends on how many orders you have and on your server. WooCommerce copies orders in background batches, and WP-CLI can run the sync faster. Time a full sync on a staging copy of your live database before you plan the live switch, so you know the real figure for your store.

Can we switch back to the old storage later?

Yes, as long as compatibility mode is still on, because both sets of tables stay in sync and the switch back is instant. If sync has been turned off, the posts tables must be backfilled first. After you run the cleanup command, the old copy is gone, so keep that step until you are sure.

Last updated

Start a project

Have a project in mind? Let’s build it.

Tell us what you need. You get a clear plan, a fixed quote and a timeline before any work starts.

Prefer email? info@softitland.com