WooCommerce High-Performance Order Storage (HPOS) moves orders out of WordPress's wp_posts and wp_postmeta tables into dedicated order tables. New stores have used it since WooCommerce 8.2, but a store that was running before October 2023 is still on the old posts storage unless someone switched it. This guide explains what HPOS changes, how to check your plugins, and how to make the switch on an existing store without losing an order.
What Is WooCommerce HPOS?
WooCommerce High-Performance Order Storage changes how your store manages order data. Instead of storing orders in WordPress's generic wp_posts table alongside blog posts and pages, HPOS creates database tables designed for order data.
Traditional WooCommerce stores every order as a custom post type in wp_posts, with every address line, total and flag as a row in wp_postmeta. Order notes live in wp_comments. As order volume grows, every order screen and report has to join and filter across tables that were designed for blog content, and the wp_postmeta table in particular becomes enormous.
HPOS introduces dedicated tables, wp_wc_orders, wp_wc_order_addresses, wp_wc_order_operational_data and wp_wc_orders_meta. Common fields such as totals, status, currency and customer id become real columns with real indexes rather than meta rows, which is what lets the database answer order queries directly.
WooCommerce's own documentation describes the goals as scalability, reliability and simplicity. HPOS was previously known as Custom Order Tables (COT), and you will still see that name in older posts and in the deprecated wp wc cot command namespace.
How HPOS Improves WooCommerce Performance
HPOS changes the shape of the data rather than adding caching, so the gains show up wherever WooCommerce has to find, filter or count orders.
Database Query Optimization
The most significant improvement comes from removing the wp_postmeta joins. Filtering orders by status, date or customer on the legacy store means joining wp_posts to wp_postmeta once per field. On HPOS those fields are indexed columns on wp_wc_orders, so the same filter is a single indexed lookup.
Reduced Memory Usage
The legacy store loads an order by loading a post object and all of its meta. HPOS reads the order's columns and only the meta that exists in wp_wc_orders_meta, so order-heavy operations such as bulk status changes, exports and reports hold less in PHP memory.
This matters most on stores running a current PHP version with sensible memory limits, where memory per request determines how many customers you can serve at once.
Improved Admin Performance
The Orders screen, order search and order filters are where merchants notice HPOS first, because they are the screens that query across the whole order history. Order search in particular benefits, and WooCommerce 9.0 added full-text search of orders for HPOS stores.
Do not take anyone's benchmark on faith, including ours. Measure your own store before and after with the method in the "What to Measure" section below. The gain depends on how many orders you have, how much order meta your plugins add and how your database is tuned.
HPOS Migration Process
Switching an existing store to HPOS is a settings change with a sync step in the middle. The work is in the preparation, especially the plugin audit.
Pre-Migration Requirements
WooCommerce's documentation states that there are no hosting restrictions for HPOS. Any host that can run current WordPress and WooCommerce can run HPOS, and the general WooCommerce server requirements apply. Beyond that, what you need is:
- WooCommerce 8.2 or later, where HPOS is a stable feature (it is available from 7.1 as an opt-in)
- Every active extension that touches orders must declare HPOS compatibility. If an incompatible plugin is active, WooCommerce disables the HPOS option in settings until you deactivate or update it
- A fresh backup taken immediately before the switch, not the night before. On TopSyde the backup is taken right before the change is made
Audit your active plugins first. WooCommerce shows the list under Plugins with the "Incompatible with HPOS" filter (wp-admin/plugins.php?plugin_status=incompatible_with_feature&feature_id=custom_order_tables), and the same information is available from WP-CLI:
wp wc hpos compatibility-info
For an overview of the store's current storage, sync and cleanup state, run:
wp wc hpos status
Step-by-Step Migration
WooCommerce stores one set of tables as authoritative and, with compatibility mode on, writes every change to the other set as well. The switch is only allowed once both sets agree.
-
Turn on compatibility mode Go to WooCommerce > Settings > Advanced > Features. Under "Order data storage" tick "Enable compatibility mode (synchronizes orders to the posts table)" and save. Your store is still on posts storage, but WooCommerce now starts copying existing orders into the HPOS tables.
-
Let the sync finish, or run it yourself WooCommerce backfills orders in the background through Action Scheduler, 25 orders per batch, which you can watch and nudge under WooCommerce > Status > Scheduled Actions. On a store with many orders it is much faster to run the sync from the command line:
wp wc hpos syncCheck how many orders are still pending with
wp wc hpos count_unmigrated. The switch is not available until the count is zero. -
Verify the copy
wp wc hpos verify_dataThis compares the two stores order by order. For a single order,
wp wc hpos diff <order_id>shows any field that differs. -
Select HPOS as the authoritative store Back on the Features page, select "High-performance order storage (recommended)" under "Order data storage" and save. Keep compatibility mode on. From this moment orders are read from and written to the HPOS tables, and every change is mirrored back to the posts tables.
-
Run on HPOS with compatibility mode on Leave both stores in sync for a while and watch checkout, payment gateway callbacks, order status emails, reports and any custom order workflow. While compatibility mode is on you can switch back in a single setting change with no data loss.
-
Turn off compatibility mode Once you are confident, untick compatibility mode and save. WooCommerce stops writing to the posts tables. Later, when you no longer need the legacy copy,
wp wc hpos cleanup allremoves the old order data fromwp_postsandwp_postmeta.
The same steps can be run entirely from the command line with wp wc hpos enable --with-sync, which turns on HPOS and compatibility mode together and refuses to proceed if orders are still pending sync.
Migration Rollback Options
With compatibility mode on, rolling back is the same settings change in reverse. Wait for pending orders to finish syncing, select "WordPress posts storage (legacy)" under "Order data storage", and save. From the command line, wp wc hpos disable does the same and will stop with an error if any orders still need syncing, pointing you at wp wc hpos sync.
Once compatibility mode is off, the posts tables fall behind. You can still revert, but you must first run wp wc hpos sync (or let the scheduled backfill run) so the posts tables catch up on the orders placed since. After wp wc hpos cleanup has removed the legacy data, reverting means a full sync back from the HPOS tables. That is why the documentation recommends running with compatibility mode on for a period before turning it off.
On TopSyde the backup taken immediately before the switch is a further safety net. On Complete, staff can restore it or run the sync back for you as part of the plan.
Plugin Compatibility Considerations
HPOS compatibility varies across the WooCommerce plugin ecosystem. Core functionality and the major extensions support HPOS. Older or custom plugins may require updates or replacement.
Compatible Plugin Categories
Mainstream WooCommerce extensions declare HPOS compatibility, and WooCommerce will not let you enable HPOS while an active plugin has not. The compatibility list on your own store is the only one that matters, which is why the plugin audit comes first.
Problematic Plugin Types
Certain plugin categories commonly have HPOS compatibility issues:
- Plugins that read or write order meta with
get_post_meta()andupdate_post_meta()instead of the order object's methods - Older inventory and reporting plugins that run direct SQL against
wp_postsandwp_postmeta - Plugins that register their own admin screens for orders using post type hooks
- Third-party ERP, CRM and accounting integrations, which often lag in HPOS support
- Anything outside WordPress that reads the database directly, such as a data warehouse or shipping system. WooCommerce's large-store guide calls these out specifically because a code audit will not find them
Testing Plugin Compatibility
The compatibility flag tells you a plugin declared support. It does not test it. With compatibility mode on, test the store yourself:
- Process test orders through each payment gateway, including a refund
- Verify shipping calculations and tracking updates
- Trigger order status changes and confirm the emails
- Check reports and exports against known numbers
- Walk through any custom order workflow end to end
Document any compatibility issues and contact plugin developers for HPOS-compatible updates. Most active plugin developers have shipped HPOS support, since the feature has been the default for new stores since 2023.
What to Measure
Rather than trusting published numbers, record your own baseline before you touch the settings and repeat the measurements after the switch.
- Time to load the Orders admin screen with the default filters
- Time to search orders by a customer email and by an order number
- Time for a date-range report to render
- Checkout completion time measured with Query Monitor or your host's APM
- Database query count and total query time on the Orders screen, from Query Monitor
Run each measurement several times and use the median. Checkout itself is usually the smallest change, because placing one order is cheap on either store. The order list, search and reports are where you will see the difference.
Supernova Digital, a commerce agency running 16 WooCommerce stores on TopSyde, is a useful reminder that storage is only one part of store performance. Their checkout time during sales went from 1.9 seconds to 320 milliseconds through caching, Redis object caching and database work together, and all 16 stores stayed up through Black Friday.
HPOS Best Practices
Getting the most from HPOS requires proper implementation and ongoing attention. These practices keep performance high and reduce the chance of problems.
Database Optimization
HPOS performance depends on a healthy database:
- Keep
wp_postmetaandwp_optionslean. HPOS removes orders from them, but autoloaded options and leftover plugin meta still slow every request - Archive or clean up legacy order data with
wp wc hpos cleanuponce you no longer need the posts copy - Use Query Monitor to find slow queries from plugins that still hit the old tables
- Schedule regular database cleanup
TopSyde Complete includes database cleanup on every site, and the stack runs MariaDB with Redis object caching available. Details are on the stack page.
Monitoring HPOS Performance
Set up monitoring to track HPOS performance improvements and catch potential issues:
- Compare checkout completion times before and after HPOS
- Track order management screen load times in the admin
- Watch slow query logs for HPOS-related performance issues
- Watch error rates during high-traffic periods
Backup and Recovery Considerations
A database backup includes every table, so a normal full backup already covers the HPOS tables. What changes is the restore procedure. Make sure whoever restores a backup knows which store is authoritative and whether compatibility mode was on, because restoring a backup from before the switch puts the store back on posts storage.
TopSyde takes daily backups of every site, keeps them 30 days with one-click restore, and takes an additional backup immediately before an HPOS switch. For large stores, enterprise hosting adds staff-run migration and sync.
Common HPOS Migration Issues
Understanding common HPOS migration challenges helps prevent problems and reduces downtime during transitions.
Data Synchronization Problems
The most frequent HPOS migration issues involve data synchronization between the legacy and HPOS stores:
- Large stores relying on the 25-order background batches can take a long time to sync. Run
wp wc hpos syncinstead - Custom order meta written through post meta functions does not round-trip until the plugin is updated
- Orders changed outside normal WooCommerce flows (direct SQL, imports) can leave the two stores out of step.
wp wc hpos verify_datafinds them
Check wp wc hpos status before and after the switch, and run the verify command before turning compatibility mode off.
Plugin Conflicts
Plugin compatibility issues often surface during HPOS testing:
- Query failures in legacy plugins that read orders directly from
wp_posts - Plugins accessing order meta through WordPress post meta functions
- Custom order management screens breaking with HPOS enabled
Maintain a detailed plugin inventory and test each extension individually during the migration process.
Performance Degradation
Occasionally, an HPOS switch results in unexpected performance issues:
- A plugin that still queries
wp_postmetafor order data is now doing so against tables that no longer hold it, and may fall back to slow paths - Compatibility mode doubles writes, so a store with heavy order volume will see more database load until it is turned off
- Database connection limits and PHP memory limits that were already tight do not get looser because the tables changed
These issues typically resolve with plugin updates, turning compatibility mode off once you are confident, and sensible server configuration. On Complete, staff look at this with you as part of the plan.
Frequently Asked Questions
Should all WooCommerce stores migrate to HPOS?
New stores on WooCommerce 8.2 or later are already on HPOS. For an existing store on posts storage, the benefit grows with the number of orders and the number of admin users working the order screens. A small store will see a smaller change, but it also has the least to lose from the switch. There are no hosting restrictions, so the only real gate is plugin compatibility.
Can I revert from HPOS back to legacy storage?
Yes. With compatibility mode on, both stores hold the data, so reverting is a settings change once pending orders have synced. With compatibility mode off, run wp wc hpos sync first so the posts tables catch up, then switch. After wp wc hpos cleanup has removed the legacy data, reverting requires a full sync back from the HPOS tables.
Does HPOS affect WooCommerce plugin compatibility?
Modern WooCommerce plugins support HPOS, and WooCommerce blocks the switch while an incompatible plugin is active. Plugins that query wp_posts directly for order data or use post meta functions on orders need updates. Test them with compatibility mode on, where both stores hold the data and you can switch back in one setting.
How long does HPOS migration take for large stores?
It depends on order count and whether you use the command line. The background sync copies 25 orders per scheduled batch, which is slow on a large store. wp wc hpos sync is far faster; WooCommerce's own documentation shows roughly a thousand orders syncing in about fourteen seconds. The store stays online throughout, because the sync writes to the inactive tables while customers keep using the active ones.
Will HPOS migration affect my store's SEO or frontend performance?
HPOS has no direct effect on SEO rankings or product page load times, because it only changes where orders are stored. The direct beneficiaries are the admin order screens, search and reports. A lighter database can help the whole site indirectly, but measure it rather than assume it.
Does TopSyde switch my store to HPOS for me?
TopSyde takes a backup immediately before the switch, and on Complete staff help with the plugin audit, the switch and the sync as part of the plan. Every Complete site includes one developer hour a month, which covers the switch on most stores.
Topics

Content & SEO Strategist
7+ years SEO & content strategy, Google Analytics certified
Elena drives content strategy and SEO at TopSyde, helping clients maximize organic visibility and AI search presence. She combines technical WordPress knowledge with data-driven content optimization.



