WooCommerce HPOS Sync Not Working After the 2026 Migration

What HPOS is and what changed in 2026

High-Performance Order Storage moves WooCommerce orders out of the generic wp_posts and wp_postmeta tables and into purpose-built tables, primarily wp_wc_orders, wp_wc_orders_meta, wp_wc_order_addresses, and wp_wc_customer_lookup. The new schema uses dedicated columns for status, totals, dates, and customer ID, with NOT NULL and UNIQUE constraints where the data model requires them. For stores with more than about 50,000 orders, the move from a generic key-value meta table to a relational schema with proper indexes drops Orders dashboard load time from tens of seconds to under one. That is the upside.

The downside is migration. HPOS does not tolerate the messy historical data that wp_postmeta happily stored for years. Orders without an _order_key, addresses missing required fields, programmatic orders skipping the standard CRUD path, and custom checkout flows that wrote non-standard meta all fail the new schema constraints. The migrator does not auto-clean. It either crashes or, on PHP 8.4, silently rolls back the transactions without telling you anything.

Which symptom matches yours

Find the row that matches your situation. Each one points to a different root cause and a different fix path.

The three root causes

The HPOS issues clustering in 2026 fall into three buckets. Each one needs a different fix. Knowing which applies determines whether the work takes 20 minutes or two days.

DIY vs hand it off

HPOS issues span from one-filter-fixes to multi-day data-cleanup projects. If the left column matches your situation you can probably resolve this in an afternoon. If the right column matches, get help.

How to diagnose with WP-CLI

The Orders settings UI is too quiet to be useful for diagnosis. Run these in order from the command line and the failure mode reveals itself.

How to fix it

Each fix branch below stands alone. Pick the one your diagnosis pointed to.

# Confirm CLI is now on PHP 8.2
wp --info

# Reset HPOS state if available in your version
wp wc hpos reset || echo "reset subcommand not available in this version"

# Run sync with small visible batches
wp wc hpos sync --batch-size=50

# Watch the unmigrated counter actually decrease
wp wc hpos count_unmigrated

-- Find orders with empty or missing _order_key
SELECT post_id
FROM wp_postmeta
WHERE meta_key = '_order_key'
  AND (meta_value = '' OR meta_value IS NULL);

-- Or find orders that never had the row at all
SELECT p.ID
FROM wp_posts p
LEFT JOIN wp_postmeta m
  ON p.ID = m.post_id AND m.meta_key = '_order_key'
WHERE p.post_type = 'shop_order'
  AND m.meta_id IS NULL;

-- Backfill with a unique value per order (WooCommerce uses 'wc_order_' prefix + random)
UPDATE wp_postmeta
SET meta_value = CONCAT('wc_order_', SUBSTRING(MD5(CONCAT(post_id, RAND())), 1, 13))
WHERE meta_key = '_order_key'
  AND (meta_value = '' OR meta_value IS NULL);

add_filter( 'woocommerce_hpos_enable_sync_on_read', '__return_true' );

// Wrong, no longer syncs to HPOS in WC 10.7+
update_post_meta( $order_id, '_billing_phone', '555-1234' );

// Right, writes to HPOS through CRUD
$order = wc_get_order( $order_id );
$order->set_billing_phone( '555-1234' );
$order->save();

Data corruption most merchants miss

Even after sync reaches 100 percent and the dashboard loads fast, the data inside HPOS may not be what you think it is. Two specific corruptions hide on single-order screens and only surface in reports.

The wp_wc_customer_lookup mismatch

GitHub issue 60214, opened in August 2025 against the WooCommerce repository, documented that for a significant subset of registered customers, the email, first_name, and last_name in wp_wc_customer_lookup do not match the actual billing data on orders linked to the same customer_id. The reporter showed a concrete example: order 27854 with customer_id 774 had billing data for one customer, but the lookup table said customer 774 was a different person entirely. The root cause is a flaw in the initial HPOS migration that mapped legacy WordPress user IDs to the new HPOS customer IDs incorrectly. Detect it with a query like this:

-- Find customer_id values where the lookup email does not match the order billing email
SELECT
  o.id AS order_id,
  o.customer_id,
  c.email AS lookup_email,
  m.meta_value AS billing_email
FROM wp_wc_orders o
JOIN wp_wc_customer_lookup c
  ON o.customer_id = c.customer_id
LEFT JOIN wp_wc_orders_meta m
  ON o.id = m.order_id AND m.meta_key = '_billing_email'
WHERE c.email IS NOT NULL
  AND m.meta_value IS NOT NULL
  AND c.email != m.meta_value
LIMIT 100;

If this returns rows, your lookup table is corrupted. WooCommerce does not currently ship a one-click repair. The supported fix is a scripted UPDATE that rewrites the lookup table from the authoritative billing data, deduplicated by customer_id.

The empty total_amount on partially migrated orders

Orders that survived a sync run where constraints were bypassed often end up in wp_wc_orders with total_amount empty or zero. The individual order view still shows the correct total because it falls back to wp_postmeta. The Orders list view reads from wp_wc_orders directly and shows zero. Any analytics or accounting query that joins on total_amount understates revenue, which has real consequences. The only supported path is the clean-reschema sequence in the fix section above.

A real 276k-order debug session

Anonymized and condensed from a real WordPress.org support thread documenting a December 2025 migration debugging session, with permission of the pattern owner.

WooCommerce HPOS FAQ

Sources and further reading

Every WooCommerce-specific claim on this page traces back to WooCommerce's own documentation, the WooCommerce GitHub repository, or the WordPress.org support forum.

• WooCommerce: High-Performance Order Storage documentation
• WooCommerce Developer: Large store guide to enabling HPOS
• WooCommerce Developer Advisory: HPOS sync on read disabled by default in 10.7 (February 16, 2026)
• WordPress.org Support: HPOS compatibility mode sync never finishes on large order store (December 2025 thread)
• GitHub Issue 60214: Systematic data corruption in wp_wc_customer_lookup after HPOS migration
• GitHub Issue 39656: Old database records are not deleted after HPOS migration
• GitHub Issue 41172: HPOS reconcile sync problems