In this guide
Why a working store can have a broken report
A retailer switches WooCommerce to High-Performance Order Storage, or HPOS. Checkout still works and staff can see orders in WooCommerce, but a custom sales report, dispatch integration or CRM export suddenly shows fewer orders. In some cases the report appears to stop on the day HPOS was enabled. That does not automatically mean the orders have vanished.
The likely issue is that an older plugin or custom script reads orders directly from WordPress post tables. HPOS uses dedicated order storage, and WooCommerce can make those tables authoritative. Code that bypasses WooCommerce's order APIs may then read incomplete or out-of-date compatibility data.
Establish which order data is authoritative
Open WooCommerce settings and inspect the order storage configuration under Advanced features. Confirm whether HPOS is enabled and whether compatibility synchronisation is active. Also check the WooCommerce version, the relevant extension versions and recent changes to the store.
A backed-up staging copy is a safer place to investigate than live checkout. Before changing any storage setting, confirm that you have a tested database backup and understand the site's current synchronisation state. Simply toggling a feature in production can complicate an already inconsistent integration.
Compare a known order in both views
Choose an order that appears in WooCommerce but not in the custom report. Record its ID, creation date, status and total. Check whether the report fetches data through WooCommerce's order query functions or directly from wp_posts and wp_postmeta. The legacy pattern may include queries against post_type shop_order, get_posts calls or direct reads of order metadata.
Older approaches worked when orders were stored as WordPress posts. With HPOS enabled, the supported method is to use WooCommerce's order object and querying APIs, such as wc_get_order and wc_get_orders, for business logic that handles orders. Avoid writing a replacement report that simply changes from one private database table to another; the supported API protects against future schema changes.
How a stale read causes a false business decision
Imagine the fulfilment team prints a daily list from a custom dashboard. The dashboard asks wp_posts for orders created today. WooCommerce's own order screen shows 18 orders, while the dashboard lists 12. Staff may assume six customers never checked out and leave their orders unfulfilled.
The right diagnosis is not to recreate those six orders. It is to find where the query was reading from, confirm the authoritative datastore and correct the reporting integration. Duplicate recreations could lead to duplicate charges, invoices or stock reservations.
Review writes as well as reads
Some older extensions do more than report on orders. They update post status or custom order metadata using generic WordPress functions. If those writes bypass the supported WooCommerce API, a process can appear successful in its own logs while WooCommerce continues to display the previous value.
Search custom code for order-related uses of direct database queries, get_post_meta, update_post_meta and functions that assume shop_order is stored as a standard post. Not every occurrence is wrong; evaluate its purpose before changing it. Product and content metadata follow different rules from HPOS order data.
For an order-specific integration, load the order through the WooCommerce API, make a supported change, save it and verify the result through a fresh supported read.
Understand compatibility mode
WooCommerce offers compatibility synchronisation to keep legacy post storage and HPOS order tables aligned while a store transitions. This is helpful when moving an established site, but it should not become an excuse to leave critical custom code dependent on outdated storage assumptions.
Check the synchronisation status and pending background actions. In large stores, backfills can take time. WooCommerce's tooling includes ways to inspect HPOS compatibility and pending migrations. Run migration or sync operations only after a backup and a clear understanding of the authoritative datastore.
Compatibility mode also has operational costs. Keeping two data representations in sync increases work, so a long-term plan should migrate integrations towards supported interfaces rather than treating dual storage as the permanent architecture.
Test the entire order lifecycle
A report that loads the correct order count is only one test. Place controlled orders through each payment method used by the business. Test cancelled and refunded orders, status updates, partial refunds, customer edits and any special subscriptions or fulfilment workflows.
Check totals, line items, tax information, shipping and the link to payment references. Make sure an order exported to a CRM or accounting system is not exported again merely because its storage representation changed. Existing transaction mappings and idempotency checks should survive the migration.
Use realistic order history when comparing old and new reports. Historical returns, draft orders and custom statuses may affect a report's filters. A discrepancy can be caused by both a storage problem and a business-rule difference.
Make custom reporting more maintainable
A reliable integration should separate data retrieval from the report layout. One tested service can request orders through supported WooCommerce APIs, normalise the required fields and pass them to sales reports, inventory updates or CRM exports.
Keep the integration's own operational records where necessary, including last successful export, external document ID, error state and retry history. Do not write operational markers into arbitrary WooCommerce storage tables simply because it is convenient.
Monitor failures explicitly. A daily job that returns zero orders should not automatically be considered a successful export when checkout was active throughout the day.
A small compatibility test that catches big mistakes
Before deploying the repaired report, compare a sample of order IDs spanning older and newer sales, different statuses and at least one refunded transaction. Ask the new query layer for each order and check its attributes against the WooCommerce administration screen. Next, verify that the reporting totals still follow the business's definitions: does revenue exclude cancelled orders, include shipping, or count refunds separately? Those questions are distinct from HPOS storage and can hide inside the same migration. Finally, test the integration on a staging site with compatibility mode arranged as it will be in production. Record expected outcomes so a future WooCommerce update can be tested against the same cases.
When a developer should be involved
If a store relies on legacy custom reports, a warehouse connector or years of tailored WooCommerce code, an HPOS compatibility review is worthwhile before or after the transition. The work may be modest, but the effects of a faulty report can reach dispatch, finance and customer support.
Digital4Front develops and maintains WooCommerce systems and custom integrations. We can trace the affected data queries, move order handling to supported WooCommerce APIs and test the downstream workflows before the change goes live. The objective is preserving reliable business operations as the underlying platform evolves.
