HPOS in WooCommerce: a safe move to new order storage
Enable HPOS in WooCommerce only after checking extensions, custom code and systems that handle orders. Flipping a switch is not a migration plan. For an existing shop, I recommend testing a copy first, synchronizing data next and changing the authoritative storage last. Judge success by a complete order journey from payment to dispatch, not by a green notification in the dashboard.
This guide is for an owner who needs to approve the scope and conditions of the transition. It is not an instruction to change a live shop without technical support. When planning an online shop with Webiant, include operational tests in the brief rather than treating them as optional work after deployment.
What HPOS changes and what not to expect
HPOS stands for High-Performance Order Storage: it stores order data in dedicated WooCommerce tables instead of the traditional WordPress posts-based storage. It is a change to order storage. The official HPOS documentation explains the basics.
Do not treat migration as proof that every cause of a slow shop has been resolved. Before starting, choose a specific task, such as opening an order or preparing the daily export. Record its behavior using comparable data and repeat it after the change. Do not promise a percentage improvement without measuring your own shop.
When to approve the move and when to postpone it
Separate software readiness from operational readiness. Ask your supplier for the exact versions involved, test results and the person responsible for reverting. Use the following table as a proposed approval rule.
| Situation | Decision | Evidence needed |
|---|---|---|
| Critical processes passed on a test copy | Schedule a controlled transition | Test record and a prepared fallback |
| Unclear custom invoicing code | Audit the code first | Review of order reads and writes |
| No warehouse integration test | Postpone deployment | Confirmed receipt and update of an order |
| Backup restoration does not work | Do not approve the change | A successful restoration test |
An incompatible extension can block HPOS activation in WooCommerce. Do not bypass that block just to meet a deadline; resolve it with the extension developer. See the section on incompatible extensions. An available switch is not a substitute for your acceptance tests either.
Example: the dashboard works but the morning export fails
Illustrative example, not a customer case study: a shop sells spare parts, an extension generates invoices and a custom export supplies the warehouse each morning. During testing, an order is created, payment is confirmed and staff see the correct address. Yet the export omits the new order. Judging only by the dashboard, the team would incorrectly approve the migration.
One possible cause is an export that reads the legacy tables. Direct order reads or writes through the old storage can use outdated or unused data with HPOS; a developer should review the WooCommerce CRUD API. The developer compatibility guide describes this issue.
In this example, I would require an export fix and another test of both a new and an updated order. Manually adding the missing row is not enough to declare the migration complete. If connections run outside WordPress, include them in the integration scope and assign an owner to each exception. The Webiant technical articles can provide background, but cannot replace testing your own shop.
A practical procedure for an existing shop
The official procedure starts under WooCommerce settings, Advanced, Features: enable compatibility mode, complete synchronization and then select HPOS. Background actions perform synchronization. The HPOS enablement guide confirms this sequence. The exact labels depend on the dashboard language.
- List dependencies. Include payments, invoicing, shipping, inventory, exports, reports and changes in the theme or small extensions. Name an owner and a test for each item.
- Prepare an isolated copy. Restrict access, use test payments and prevent real dispatches or customer messages. Test restoring a backup.
- Record the baseline. Select older and new orders, different payments, a refund and custom fields. Keep the expected values for comparison.
- Rehearse data migration. Keep legacy storage authoritative, enable compatibility and monitor synchronization to completion. Unresolved errors are a reason to stop.
- Switch the test copy to HPOS. Repeat the critical processes. Later, test with synchronization disabled on that same isolated copy.
- Approve the production window. Arrange an available technician, a fresh backup, checks of new orders and stop conditions. In production too, finish synchronization and data checks before switching to HPOS. Do not combine migration with a redesign or a gateway replacement.
- Review operations. Initially keep compatibility enabled after the production switch. Make disabling it a separate evidence-based decision, not a reaction to an arbitrary number of days.
WooCommerce recommends testing critical processes with synchronization on and off, and checking external systems. This also supports the test plan above; see the migration guide for larger shops. Estimate your migration time from your rehearsal, not somebody else’s example.
What an acceptance test must cover
For each scenario, record the input, expected outcome, actual outcome and test order identifier. I suggest the following minimum; add your own rules for subscriptions, bookings or specialized wholesale processes.
- A new order through every payment method in use, including a failed payment and delayed confirmation where supported by the integration.
- Address, note and status changes: the same result in the dashboard and the connected system.
- Full and partial refunds, if the shop uses them, with checks of amounts and documents.
- Finding an older order and displaying its custom fields without manual repairs.
- Warehouse export, shipping document creation and verification of invoicing details.
Test without synchronization outside production first. Comparing order counts is not enough: compare items, amounts, addresses and custom data for a selected sample too. An operations colleague who knows the correct document and expected inventory state should be able to confirm the result.
Reverting is not restoring an old database
To revert from HPOS, enable compatibility, wait for synchronization to finish and only then select legacy WordPress storage. The documentation on disabling HPOS specifies this sequence. Do not assume an immediate fallback after running without synchronization.
I recommend distinguishing a storage switch from restoring the whole database from backup. During an incident, first record orders and changes received since the backup, stop the problematic automation and agree the next steps with the administrator. Do not blindly restore an old backup into a shop that has continued accepting purchases.
Mistakes to avoid include testing only one payment, ignoring morning exports and declaring HPOS support in custom code without an audit. Set a project boundary too: do not expand migration into cleaning every table or deleting history. Approve each additional change separately.
Pre-approval checklist
- Every critical dependency has an owner and a documented test result.
- The migration rehearsal and backup restoration passed with no unresolved critical issue.
- Operations confirmed the order, invoice, export and data update.
- Post-switch monitoring and fallback conditions are agreed.
- Disabling compatibility has its own decision and test record.
Frequently asked questions about HPOS
Must I make the switch during the next campaign?
Linking it to an advertising deadline without readiness is unwise. I recommend a separate window with an available administrator and operations colleague. If critical test results are missing, prioritize completing them over formally meeting a date.
Is an extension developer’s compatibility confirmation enough?
Use it as an input, not as final approval. Ask which version it covers and add tests of your own shop, including customizations and exports. Base acceptance on recorded results for the whole process.
How long should compatibility remain enabled?
Set conditions rather than a fixed number of days: successful representative orders, refunds, regular exports and resolved exceptions. Agree a review date in advance. Approve disabling it only after testing without synchronization on an isolated copy.
What deliverables should I request from the supplier?
Ask for a dependency inventory, migration results from a copy, an acceptance record and a fallback procedure. The handover should also state the compatibility setting and remaining limitations. A screenshot of an enabled switch is not sufficient evidence of completion.
Next step and references
If you do not know who maintains old exports or custom order fields, start by listing them. Through the Webiant contact page, send your WooCommerce version, integration list and a description of the critical process. Do not send passwords or customer data; an anonymized description is enough to define the initial audit scope.