WooCommerce HPOS: switching order storage safely
Short answer: High-Performance Order Storage (HPOS) moves WooCommerce orders out of WordPress's general posts tables into dedicated order tables. New installations have had it switched on by default since WooCommerce 8.2; older shops often still run on the legacy tables and see a notice inviting them to switch. Do it in stages: check plugin compatibility, turn on compatibility mode so both storage systems stay in sync, test on staging, switch over, and only then stop syncing.
If you've run a WooCommerce shop for a few years, there's a good chance your orders still live where WooCommerce originally put them. Here's what the change involves and a sequenced plan for making it without losing orders or breaking the plugins you depend on.
What HPOS changes, in plain terms
WooCommerce's developer documentation explains that orders were historically stored as a custom WordPress post type, with order details spread across the posts and post meta tables shared with pages, blog posts and everything else. HPOS, previously known as "Custom Order Tables", stores order data in four dedicated tables instead: orders, order addresses, order operational data and order meta.
The docs give three reasons for the change: scalability (fewer read/write operations on busy shared tables), reliability (targeted backups and better protection against conflicting writes) and simplicity (order data in tables designed for orders).
From WooCommerce 8.2, released in October 2023, HPOS is enabled by default for new installations. Existing stores need to switch deliberately.
Before you start: who needs to care
- Stores with steady order volume. Shared tables grow with every order; separating them is where the performance benefit is meant to come from.
- Stores with custom code or older plugins that read orders directly from the posts table. These are the ones that can break.
- Very small or new stores. If you installed WooCommerce recently, check the setting; you may already be on HPOS.
The plan, step by step
Week 1: take stock
- Check where you are. Go to WooCommerce → Settings → Advanced → Features. The documentation describes the option to choose between "WordPress posts storage" and "High-performance order storage".
- Review incompatible plugins. According to WooCommerce's docs, if any active plugin is not compatible, the HPOS option is disabled and a "View and manage" link lists the offenders. Note each one.
- Check custom code. If a developer has written snippets or a custom plugin that queries orders, ask whether it uses WooCommerce's own order functions or reads the posts table directly. The latter needs rewriting.
- Update everything on a staging copy first: WooCommerce core, payment gateways, shipping, invoicing and reporting plugins. Many plugins added HPOS support in updates.
Week 2: resolve incompatibilities
For each incompatible plugin, you have three choices: update it, replace it with a compatible alternative, or remove it if you no longer need it. Don't force the switch while incompatible plugins remain active; the compatibility check exists for a reason.
Week 3: sync on staging
- Enable compatibility mode while keeping the legacy storage authoritative. WooCommerce's documentation explains that with compatibility mode on, order data is synchronised between the posts/post meta tables and the new order tables.
- Let the sync finish. Existing orders are copied in the background; large stores take longer. Wait until the settings screen shows nothing pending.
- Switch the authoritative store to HPOS, still with compatibility mode on, so the old tables continue to receive a copy as a backup. The docs describe exactly this arrangement: the authoritative tables are the working ones, and the backup tables receive a copy whenever synchronisation happens.
- Test real flows on staging: place orders with each payment method, issue a refund, edit an order, run reports, print invoices or packing slips, and check that any connected accounting, shipping or email tools receive orders correctly.
Week 4: switch live
- Take a full backup of the live database.
- Repeat the staging steps on live at a quiet trading time: compatibility mode on, sync, switch to HPOS as authoritative.
- Watch the first days closely. Check new orders appear in every connected system and that order notes, statuses and stock levels behave as expected.
Later: decide when to stop syncing
WooCommerce's merchant guide advises keeping compatibility mode on for some time after switching, and notes that reverting to the posts table can then be done instantly. Running with compatibility mode on does mean every order write happens twice, which adds overhead. Once you're confident (many stores wait a few weeks of normal trading), you can turn compatibility mode off. Before you do, be sure you won't need to switch back quickly, because switching back without sync means the legacy tables won't have recent orders.
Rollback: know your exit before you need it
While compatibility mode is on, both table sets hold the same orders, so switching the authoritative storage back to WordPress posts is a settings change. That's the main reason to keep sync running through the first period on live. If you've already disabled sync, re-enable it and let it complete before switching back.
Common problems and where they come from
- An order report or export is suddenly empty. Usually a plugin or custom report reading the posts table directly. Update or replace it.
- The HPOS option is greyed out. An active plugin hasn't declared compatibility. Use the "View and manage" list.
- Orders look different in two places. Sync hasn't finished, or a tool writes to the old tables without going through WooCommerce. Check pending sync and the tool's documentation.
FAQ
Is switching to HPOS mandatory?
New installations use it by default from WooCommerce 8.2. For existing stores, the WooCommerce settings screen lets you choose; check WooCommerce's current documentation for any future changes to legacy storage.
Will my customers notice anything?
They shouldn't. Checkout and account pages work the same. The change is in how orders are stored behind the scenes.
How long does the sync take?
It depends on how many orders you have and your hosting. It runs in the background in batches; very large order histories can take a long time, which is why staging comes first.
Do I need a developer for this?
Not always. A store with up-to-date, mainstream plugins can often switch through the settings screen. Custom code that touches orders is the point where developer help is worth having.
Got an older WooCommerce shop and a list of plugins you're not sure will survive the move? Send us the list and we'll plan the order-storage switch with you.