Handcrafted Beautiful Bootstrap HTML Templates for your Business Website.
High-Performance Order Storage (HPOS) is the biggest change to how WooCommerce stores orders in the platform’s history. Instead of keeping orders in the WordPress posts and postmeta tables, where they shared space with blog posts and pages, HPOS stores them in dedicated order tables designed for the job. New stores use it by default, and WooCommerce has been encouraging established stores to switch.
For most stores the switch is smooth. But the WordPress.org forums have a steady trickle of threads that show what can go wrong: “HPOS doesn’t complete order sync”, “HPOS sync is not working”, “Reports not working when HPOS enabled”, “HPOS disabled after sync”. Integrations that stop receiving orders after an update are another common complaint, usually from a plugin that reads orders the old way.
Your orders are your business records. This checklist is about making sure the move doesn’t quietly damage them: what to check before, how to migrate with a safety net, and how to verify afterwards that every order still adds up.
| Legacy (posts) storage | HPOS | |
|---|---|---|
| Where orders live | wp_posts + wp_postmeta |
Dedicated wc_orders tables (plus related tables) |
| How plugins should read orders | WooCommerce CRUD functions (or directly from posts, which many old plugins did) | Only through WooCommerce CRUD functions |
| Performance | Slows as order and post volume grow | Designed to scale |
| Admin order screen | Posts list screen | WooCommerce’s own orders screen |
The key risk is in the second row. Plugins that read or write order data directly from the posts tables, instead of through WooCommerce’s order functions, won’t see orders stored in HPOS tables, or will write data WooCommerce no longer reads. That’s how integrations “stop syncing” and reports go blank.
WooCommerce shows a compatibility notice on WooCommerce → Settings → Advanced → Features listing extensions that haven’t declared HPOS compatibility. WooCommerce’s guidance is to enable HPOS only once all the extensions you use are compatible.
Pay special attention to plugins that touch orders:
shop_order posts)Before changing anything, record numbers you can compare afterwards:
Full database backup, tested restore. Non-negotiable.
Fix existing order problems before migration, so you don’t carry them across and then blame HPOS. Stuck payments, refund mismatches and totals that don’t add up are easier to explain before the switch than after. (The free Ordafide scan is a quick way to establish this baseline.)
Run the full migration on a staging copy first, with test payment keys. Test the order flows your store actually uses.

WooCommerce’s migration uses synchronization as its safety net. Under WooCommerce → Settings → Advanced → Features (custom data stores in some versions), you can keep the posts table and the new order tables in sync. WooCommerce’s developers describe sync as a temporary failsafe.
A cautious sequence:
If something breaks while sync is on, you can switch back to posts storage, because the data is still being written there. WooCommerce’s FAQ describes rollback in exactly these terms.
Sync isn’t free: writing every change to two places adds overhead. That’s the trade-off for safety during the transition.

This is the step most stores skip. “The orders page loads” is not verification.
A store enables HPOS after its compatibility screen shows only one warning, for an older PDF invoice plugin the owner thinks is “just for printing”.
Because the store migrated with sync on, the fix was simple: switch authoritative storage back to posts, replace the invoice plugin with an HPOS-compatible one, then switch to HPOS again. Without sync, the store would have been untangling three weeks of mixed data.
The lesson: an “incompatible” warning on anything that touches orders deserves a fix before migration, not after.
Ordafide Order Integrity for WooCommerce is HPOS native. It declares HPOS compatibility and reads orders through the WooCommerce CRUD layer, so it behaves identically whether your store uses the new order tables or the legacy posts storage. That makes it useful on both sides of the switch:
To be clear about scope: Ordafide doesn’t compare the posts and HPOS tables row by row or perform the migration. WooCommerce’s sync does that. Ordafide checks that the orders themselves still make sense after the move.
Ordafide Pro adds gateway reconciliation (read-only, for Stripe, PayPal, Square, Mollie and Razorpay), a strong post-migration check because it compares orders against what the gateway actually collected, independently of how WooCommerce stores them. Its CSV/JSON audit export gives you a before-and-after record for your accountant.
For the first two weeks after switching, spend ten minutes a day on this:
If everything is quiet for two weeks, you can relax the routine, and consider whether it’s time to turn sync off.
Before migrating, tell everyone who works with orders:
Most post-migration problems are spotted first by the people who work in the orders screen every day.
Is it safe to switch WooCommerce to HPOS?
For most stores, yes, provided every extension that touches orders is HPOS-compatible and you migrate with sync enabled as a safety net.
What happens to plugins that aren't HPOS compatible?
WooCommerce warns about them, and its guidance is not to enable HPOS until they're compatible. Plugins that read orders directly from the posts table may not see orders stored in HPOS tables.
Can I roll back from HPOS?
While sync is enabled, yes. You can switch authoritative storage back to posts because both are kept up to date.
How do I verify my orders after migrating to HPOS?
Compare order counts, revenue and sample orders against a pre-migration baseline, exercise every order flow, and run an order integrity scan for stuck, duplicate, refund and total problems.
Does Ordafide work with HPOS?
Yes. It's HPOS native and also works on legacy posts storage, reading orders through WooCommerce's CRUD layer.
How long does HPOS sync take?
It depends on order volume and how healthy your background processing is. Small stores sync in minutes; very large stores can take hours or longer.
Do I need to turn sync off after migrating?
Not immediately. Running with sync on is the safety net. Many stores keep it on for a few weeks, then turn it off once every order flow and integration has been confirmed.
Will HPOS make my store faster?
It's designed to scale better, especially for stores with many orders, because orders no longer share the posts tables with other content. The gain depends on your store size and plugins.