Explainers · Explainer
What Is HPOS in WooCommerce? A Plain Explanation
Short answer
HPOS, short for High-Performance Order Storage, is WooCommerce's system for storing orders in dedicated database tables instead of the WordPress posts tables. It was released as stable in WooCommerce 8.2 in October 2023 and is on by default for new installations. Existing stores can switch to it, but they are not moved over on their own.
Key takeaways
- HPOS stores WooCommerce orders in 4 dedicated tables instead of the WordPress posts and postmeta tables.
- HPOS has been on by default for new WooCommerce installations since version 8.2, released in October 2023.
- Existing stores are not moved to HPOS on their own and must switch in WooCommerce Settings.
- Compatibility mode keeps the old posts tables and the new HPOS tables in sync during a switch.
- All extensions sold on WooCommerce.com are HPOS compatible, while outside extensions may block the switch.
- You can switch back to WordPress posts storage if HPOS causes a problem with an extension.
What is HPOS in WooCommerce?
HPOS is WooCommerce's dedicated system for storing orders in tables built for orders, instead of storing them as WordPress posts.
HPOS stands for High-Performance Order Storage. WooCommerce describes it as a solution built for online stores, with a simple database structure that uses its Create, Read, Update, Delete design. It was previously called Custom Order Tables.
The name points to the goal, not to a new checkout design. HPOS changes where order data lives in the database. It does not change what customers see at checkout, and it does not add new order fields by itself.
How did WooCommerce store orders before HPOS?
Before HPOS, WooCommerce stored each order as a WordPress post in the posts table, with most order details in the postmeta table.
WooCommerce states that before version 8.2 it relied on the _post and _postmeta table structures to store order information. That design reused the WordPress post system, so orders shared tables with posts and pages.
The WordPress Developer Resources page on managing post metadata explains that post meta is stored as key and value pairs linked to a post ID. For an order, that meant many small rows for one order, such as billing details, totals, and status notes.
That layout worked for small stores, but it made some order queries harder as order counts grew. A single order could need many postmeta rows, and a search could scan rows that had nothing to do with orders.
How does HPOS store orders now?
HPOS stores order data in 4 dedicated tables, with separate tables for the order, its addresses, its working data, and its extra meta values.
WooCommerce lists the 4 tables as _wc_orders, _wc_order_addresses, _wc_order_operational_data, and _wc_orders_meta. The order table holds core order fields, the addresses table holds billing and shipping addresses, and the meta table holds extra values added by extensions.
The WooCommerce developer blog post on the HPOS database schema gives a clear size contrast. It says a new order once needed 1 insert for the posts row plus almost 40 inserts for postmeta rows, while the new structure should need at most 5 inserts.
Dedicated columns also help lookups. The same schema post notes that the main order table adds columns for meta values used most often, so WooCommerce can read them from indexed columns instead of rebuilding them from many meta rows.
| Storage | Where orders live | How details are stored |
|---|---|---|
| WordPress posts storage (legacy) | _posts and _postmeta | One post row plus many key-value meta rows per order |
| HPOS | _wc_orders, _wc_order_addresses, _wc_order_operational_data, _wc_orders_meta | Core fields in columns, addresses in their own table, extra values in a meta table |
| HPOS with compatibility mode | Both sets of tables | Order data is written to both places while the tables stay in sync |
Why does HPOS matter for a store?
HPOS matters because it gives WooCommerce dedicated tables and indexes for orders, which helps stores with many orders search, filter, and manage them.
WooCommerce lists 3 gains from HPOS: scale, reliability, and simplicity. For scale, it points to dedicated tables and indexes that cut read and write work. For reliability, it points to simpler targeted backups and read and write locks that help prevent race conditions.
The WooCommerce developer blog post on HPOS benchmarking reported faster lookups in its own tests. It said adding indexes sped up a meta query lookup by about 10 times, and a query to get all orders for a customer was 40 times faster with HPOS.
Those numbers came from WooCommerce's own benchmark setup, so your store will not match them exactly. The direction is still useful: HPOS helps most when order lists, searches, and filters slow down. If speed is a wider problem, read our guide on how to speed up WordPress before you change storage alone.
Is HPOS already turned on for your store?
HPOS is on by default only for new WooCommerce installations from version 8.2 onward, so an older store may still use posts storage.
WooCommerce states that HPOS is enabled by default for new installations from WooCommerce 8.2 onward. The WooCommerce 8.2 release post dates that change to 10 October 2023, when it says HPOS was released under the stable flag and enabled by default for new installations.
Existing stores are not moved over on their own. WooCommerce states that existing stores will not be migrated to HPOS automatically, and the feature is completely opt-in.
To check your store, open WooCommerce, then Settings, then Advanced, then Features. Look at the “Order data storage” setting. It shows either “High-performance order storage (recommended)” or “WordPress posts storage (legacy)”.
How do you switch an existing store to HPOS?
You switch an existing store in WooCommerce Settings, after you turn on compatibility mode and let the old and new tables sync.
WooCommerce gives these steps for an existing store. First, go to WooCommerce, then Settings, then Advanced, then Features. Next, tick "Enable compatibility mode (synchronizes orders to the posts table)".
Background actions then copy orders across. WooCommerce says the backfill runs 25 orders at a time, and more actions are scheduled until the sync is done. You can watch them under WooCommerce, then Status, then Scheduled Actions.
After both tables are in sync, select “High-performance order storage (recommended)” and save the page. WooCommerce advises keeping compatibility mode on for some time, so you can switch back to posts storage at once if a problem appears.
Before you start, back up the site and keep a copy you can restore. Our guide on how to back up WordPress covers the steps. Also keep extensions that use custom post types active during the switch, such as Woo Subscriptions and WooCommerce Bookings.
How do you check that HPOS is working after the switch?
You check HPOS by reading the Features setting, by opening the Orders screen, and by running the WP-CLI status and verify commands if you have shell access.
First, return to WooCommerce, then Settings, then Advanced, then Features. The “Order data storage” value should read “High-performance order storage (recommended)”. If it still reads “WordPress posts storage (legacy)”, the switch did not take effect.
Next, open WooCommerce, then Orders, and open a recent order. Check that the customer, items, totals, and status look right. Then place a test order if you can, and check that it appears with the same details.
WP-CLI gives a deeper check. The WooCommerce developer docs for wc hpos commands list wp wc hpos status for a summary of HPOS settings and sync status, and wp wc hpos verify_data to verify migrated order data against the original posts data.
| WP-CLI command | What it does | Default batch size |
|---|---|---|
wp wc hpos status | Shows HPOS settings and sync status | Not a batch command |
wp wc hpos sync | Syncs order data between the custom order tables and the posts tables | 500 orders |
wp wc hpos verify_data | Verifies migrated order data with original posts data | 500 orders |
wp wc hpos count_unmigrated | Prints the number of orders pending sync | Not a batch command |
The same docs note that the older wc cot commands are deprecated. Use wp wc hpos instead, because wc cot migrate no longer works at all.
What happens if a plugin is not HPOS compatible?
If an incompatible extension is active, WooCommerce disables the HPOS switch in the admin and shows a link to the list of incompatible extensions.
WooCommerce states that all extensions available on WooCommerce.com are HPOS compatible. It says it requires developers to declare compatibility, and this is checked on each version update.
For extensions from outside the WooCommerce Marketplace, the rule is different. WooCommerce states that if you use an extension from outside the Marketplace that is not compatible, the option to switch is disabled under WooCommerce, then Settings, then Advanced, then Features.
In that case, click “View and manage” to see the list. Then contact the extension developer and ask for HPOS support. The recipe book for developers explains the fix: code should use WooCommerce order APIs such as wc_get_order(), not direct post and postmeta calls.
Extension cost can affect the choice too. If a paid extension needs an update or a replacement, see how much WooCommerce extensions cost before you commit to a new tool.
Payment extensions deserve extra care. Compare WooPayments vs Stripe for WooCommerce if your payment setup is part of the change.
What does HPOS not change?
HPOS does not change your products, your checkout page, your order numbers, or your host, and it does not remove the posts tables at once.
WooCommerce states that there are no hosting restrictions for HPOS. Any host that can run WordPress and WooCommerce should have no trouble running it, as of November 2026.
HPOS also does not change how orders are numbered for customers. It changes the storage tables, not the order ID rules. Do not expect a new numbering scheme after the switch.
The old tables do not vanish the moment you switch. With compatibility mode on, WooCommerce keeps writing to both places. That is the point: it gives you a way back if an extension misbehaves.
One newer option sits beside HPOS. WooCommerce states that full-text search for orders is available in experimental mode from WooCommerce 9.0. It only works when order data storage is set to HPOS.
What mistakes should you avoid?
The main mistakes are switching without a backup, switching with an incompatible extension active, and turning off compatibility mode too soon.
First, do not switch on a live store without a backup and a staging check. A backup lets you restore the site if an extension writes order data to the wrong place during the move.
Second, do not ignore the compatibility warning. If WooCommerce disables the switch, find the named extension first. Turning HPOS on around it can leave order data in a place that extension does not read.
Third, do not turn off compatibility mode on day 1. WooCommerce advises keeping it on for some time after the switch. Wait until orders, refunds, and extension reports look right, then turn it off.
Fourth, do not reactivate a custom post type extension after the move without a sync check. WooCommerce warns that this can create data gaps, because old data stays in the posts table.
If that happens, switch back to posts storage, let the sync finish, then switch back to HPOS.
Frequently asked questions
Does HPOS make WooCommerce faster for every store?
Not in a way you can feel on every store. HPOS helps most when a store has many orders and order lists, searches, or filters feel slow. A small store with few orders may see little change, because the database work was already light. Check order volume and admin speed before you treat HPOS as a speed fix.
Can I switch back to posts storage after enabling HPOS?
Yes. Open WooCommerce, then Settings, then Advanced, then Features, and select WordPress posts storage (legacy). Make sure compatibility mode is on first, and wait for the sync to finish before you switch. Save the page between changes, and check a few recent orders after you switch back.
Do I need a new host to use HPOS?
No. WooCommerce says there are no hosting restrictions for HPOS, and any host that can run WordPress and WooCommerce should run it. Your host still matters for speed and reliability, but HPOS itself does not add a host requirement. If your host is slow, HPOS alone will not fix that.
Will HPOS break my WooCommerce extensions?
It can break extensions that read or write order data with direct WordPress post functions instead of WooCommerce order APIs. Extensions sold on WooCommerce.com are HPOS compatible. For outside extensions, check the compatibility list on the Features page and ask the developer for HPOS support before you switch.
Does HPOS change my order numbers?
No. HPOS changes where order data is stored in the database, not how WooCommerce assigns or shows order numbers. Your existing order IDs stay the same, and new orders keep the same numbering pattern. If you want sequential or custom order numbers, that is a separate feature, not part of HPOS.
Sources
- High-Performance Order Storage WooCommerce
- HPOS extension recipe book WooCommerce Developer Docs
- wc hpos commands WooCommerce Developer Docs
- WooCommerce 8.2.0 Released WooCommerce Developer Blog
- High-Performance Order Storage: Database Schema WooCommerce Developer Blog
- Performance Benchmarking for WooCommerce HPOS WooCommerce Developer Blog
- Managing Post Metadata WordPress Developer Resources
- WooCommerce WordPress.org
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
