WooCommerce HPOS and legacy order storage are two ways to store orders in WooCommerce. High-Performance Order Storage, or HPOS, uses a dedicated order storage system. Legacy order storage uses the WordPress post-based model.
Table of Contents
What changes with HPOS?
HPOS changes where WooCommerce order data is stored and how connected tools access that data. Legacy order storage uses WordPress posts as the order data model. HPOS uses a dedicated order storage model instead.
This distinction matters because an extension, report, or custom integration may expect orders to exist as WordPress posts. A store can therefore have a valid WooCommerce setup that still requires compatibility checks before changing its order storage method.
WooCommerce stores use orders to manage transactions and related store activity. Order storage is therefore connected to more than the checkout itself. It can also affect reporting, administration tools, integrations, and custom code that reads or updates order records. For broader context on how WooCommerce stores manage products and orders, see the mybox WooCommerce and PrestaShop comparison.
HPOS and legacy storage compared
| Area | HPOS | Legacy order storage |
|---|---|---|
| Order data model | Uses the HPOS order storage model. | Uses WordPress post-based order storage. |
| Extension compatibility | Requires extensions and integrations to support HPOS. | May suit tools built around the legacy post-based model. |
| Performance focus | Designed for stores assessing order storage and database performance. | Uses the existing post-based order structure. |
| Migration risk | Requires a compatibility review, testing, and a rollback plan. | Provides the current storage path for stores that are not ready to change. |
Which stores are the best candidates for HPOS?
HPOS is most suitable when the store has reviewed its extensions and integrations, has a clear need to assess order-related database performance, and can test the change before applying it to live order data.
- Stores with a high order volume: order storage and database behaviour become more important as the store handles more order records and more order-related activity.
- Stores with a controlled extension set: compatibility is easier to assess when the store knows which extensions, reports, and integrations access order data.
- Stores with database or administration performance concerns: HPOS can be considered when order storage is part of the performance review.
- Stores with a strong testing process: a staging test, review of reports and integrations, and a documented rollback plan reduce migration risk.
HPOS is not automatically the right choice for every store. A smaller store with few order records may gain little from changing storage if its current setup is stable and its extensions have not been checked.
What compatibility checks are needed?
Start with every component that reads, writes, exports, searches, or reports on WooCommerce orders. This includes extensions, reporting tools, payment or fulfilment integrations, custom code, and internal processes that depend on order records.
- List all extensions and integrations that use WooCommerce orders.
- Identify reports and exports that depend on order data.
- Check whether each component supports HPOS.
- Review custom code that expects orders to use the WordPress post-based model.
- Record any component that must remain on legacy storage until it is compatible.
Compatibility is not limited to whether checkout works. A store should also confirm that order administration, reporting, exports, and connected services continue to use the expected order data.
How should performance and reporting be assessed?
Performance should be assessed against the store’s own workload. Order volume, order searches, administration activity, reporting needs, and connected integrations all form part of the assessment. HPOS should be considered as a database and order-storage decision, not as a general replacement for wider site optimisation.
Reporting needs deserve a separate review. A report may still open while returning incomplete, delayed, or differently handled data if it depends on the legacy post-based structure. Compare important reports before and after testing, including order counts, totals, filters, exports, and date ranges used by the business.
What must be ready before migration?
A migration should begin only after compatibility has been reviewed and the store has a safe testing path. The store should have:
- a complete list of extensions and integrations that use order data;
- confirmation that critical components support HPOS;
- test cases for checkout, order management, reporting, exports, and connected services;
- a comparison of important reports before and after the change;
- a tested rollback plan;
- a suitable time to monitor the store after the change.
Testing should use realistic orders and the reports the store depends on. A successful test is more than a working checkout. It should also confirm that order records, administration tasks, reports, exports, and integrations behave as expected.
When is delaying migration sensible?
Delaying migration is sensible when a critical extension or integration does not support HPOS, when reporting results have not been compared, or when the store cannot test and reverse the change safely. It is also reasonable to delay when the current legacy setup is stable and there is no clear order-storage or database reason to change it.
Use HPOS when its benefits match the store’s workload and the surrounding tools are ready. Keep legacy order storage while compatibility, reporting accuracy, testing, or rollback readiness remains unresolved. This decision gives store owners a practical way to balance performance goals with operational continuity.