A missing order may be hidden by an administrator filter, stored under an unexpected status, present in High-Performance Order Storage but missed by old code, or never created. Payment reconciliation comes first because a provider charge can exist without a visible order.
Do not recreate or delete records until you establish whether an order already exists under another view.
Clear the administrator view
Remove search text, date, customer, status and custom filters. Check All, Draft, Pending, Failed, Cancelled and Trash. Record the URL because plugins can add hidden query parameters.
Test with an administrator account known to have full WooCommerce permissions. Shop-manager roles may be restricted by custom code or multi-vendor plugins.
Do not grant permanent administrator access merely to bypass an unexplained permission defect.
Search by stable references
Use order number, billing email, gateway transaction ID, approximate time and amount. Account for custom sequential order numbers, which may differ from the internal order ID.
Check gateway records first if the report involves payment. Provider metadata may contain WooCommerce’s internal order ID or key.
Sequential numbering extensions can leave intentional gaps.
Keep customer details out of shared screenshots and search logs.
Confirm the active order-storage mode
High-Performance Order Storage stores orders in dedicated WooCommerce tables. Extensions that query only wp_posts can report an order missing even though WooCommerce loads it correctly.
Check WooCommerce > Settings > Advanced > Features and system status. Use the supported query API:
$order = wc_get_order( $order_id );
if ( $order ) {
$status = $order->get_status();
}Do not infer absence from a single direct SQL query against posts.
Check data synchronisation health
During HPOS migration or compatibility mode, synchronisation may be pending or failed. Review WooCommerce tools, Scheduled Actions and PHP logs for the affected time.
Never switch storage modes repeatedly on a live store to make records appear. Take a database backup and repair compatibility or migration failures through supported WooCommerce tooling.
Confirm every active order-management extension supports the chosen storage mode.
Inspect permissions and list customisation
Plugins can modify order-list queries by role, warehouse, language or vendor. A custom filter may exclude orders without particular metadata.
Compare the same administrator URL with plugins isolated in staging. Search maintained code for order query filters and capability checks.
A hidden table column is cosmetic; a filter altering query arguments changes which records appear. Inspect the generated query or WooCommerce debug information without logging personal data.
Determine whether creation failed
If no supported order query finds the record, match the checkout time with PHP, database and gateway logs. A fatal error or failed database write may have occurred after payment initiation.
Search Checkout draft orders and provider metadata. Do not ask the customer to retry while an authorisation or capture remains unresolved.
Classify the incident as hidden order, damaged order or payment without order.
Repair without duplicating the transaction
Correct the filter, permission, HPOS compatibility issue or failed synchronisation. If a paid transaction genuinely has no order, follow a documented reconstruction or refund process that preserves the provider reference.
Avoid inserting order rows with raw SQL. WooCommerce APIs create related addresses, items, totals and metadata consistently.
Verify all operational views
Confirm the repaired order appears in the administrator, reports and fulfilment integration with correct status and totals. Test a new controlled transaction and verify one order in the active storage.
Recurring care should compare gateway payments, WooCommerce order counts and HPOS sync failures. An order list is an interface, not the sole source of truth, so monitoring should reconcile the systems behind it.