How to pull orders from all your WooCommerce stores into one dashboard

The fulfilment problem

Product sync gets the most attention in multistore setups, but the daily operational pain usually comes from orders. If your business runs a UK store, an AU store and a DE store, and each one is a fully independent WooCommerce install, fulfilling those orders means someone checks three separate wp-admin dashboards, on three separate schedules, hoping nothing sits unnoticed in the store nobody logged into that morning.

The fix is to pull orders from all WooCommerce stores into one dashboard so fulfilment, support and reporting all work from a single, familiar WooCommerce → Orders screen — regardless of which storefront actually took the sale.

How order pull-through actually works

Order Pull-Through takes an order placed on a connected spoke store and creates a matching native order on the hub — with full billing details, shipping address, line items, payment method and totals — so it shows up in the exact same Orders list your team already uses for orders placed directly on the hub. There's no separate "child store orders" screen to remember to check.

This matters because it means your existing tools keep working unmodified: order status emails, shipping label plugins, accounting integrations and reporting all operate on the hub's Orders table without any special-casing for which store an order originated from.

• Orders arrive as real WooCommerce orders, not a summary or a read-only log entry.
• Fulfilment staff mark orders processed or completed from the hub, exactly as they would for a hub-placed order.
• Works whether the hub is on legacy order storage or High-Performance Order Storage — see Security & HPOS Compatibility.

Instant push versus scheduled pull

A common failure mode in DIY order-syncing setups is relying on a single mechanism — usually a nightly cron job — to move orders across. That's fine until a customer calls about an order placed two hours ago that support can't find anywhere on the hub yet.

Instant Order Sync pushes an order to the hub the moment it reaches "processing" status on a spoke store, with automatic retry if the hub happens to be briefly unreachable. Layered on top, Two-Way Order Capture has the hub also pull on a schedule and on demand, plus a manual push button on the spoke side as a fallback. The result is redundancy by design: three different paths for an order to reach the hub, so a single missed webhook doesn't mean a lost order.

Knowing which store an order came from

Once every order lands in one list, you still need to know where it came from — for accounting, for regional tax handling, and for support conversations where a customer references "my order" without specifying which storefront they used.

Source-Store Order Tracking tags every imported order with its origin store and original order number, surfaced in a dedicated Source store column on the Orders screen. Support can find an order by number or customer email without knowing in advance which store it came from, and finance can reconcile revenue back to the correct storefront at month end.

Worked example: three storefronts, one queue

Take that same shoe retailer running UK, AU and DE storefronts. A customer in Sydney places an order on the AU store at 9pm local time. Within moments, Instant Order Sync pushes it to the UK hub, where it appears as a native order tagged "Source: AU Store," with the AU order number preserved alongside the hub's own.

Overnight in the UK, the fulfilment team works through one Orders screen covering all three markets rather than checking three separate dashboards on three separate timezones. A support agent fielding a query the next morning searches by email, finds the order immediately, and can see at a glance it came from the AU store without needing to ask the customer which site they used or log into a second wp-admin to check.

If the AU store happens to be mid-update and briefly unreachable when the order is placed, the scheduled pull on the hub catches it on its next run a few minutes later — the order still arrives without anyone needing to notice or intervene.

What happens when a store is offline

Networks fail, hosting providers have bad days, and plugin or theme updates occasionally take a site down for a few minutes. Order sync needs to survive that without losing orders or creating duplicates once things come back up.

• Failed pushes retry automatically rather than being dropped after one attempt.
• The background job queue (see Background Sync & Reliability) means a temporarily unreachable hub doesn't block checkout on the spoke store — the order still completes for the customer and syncs once the hub is reachable again.
• Idempotent writes mean a retried push that technically succeeded the first time won't create a second copy of the same order on the hub.
• The activity log (Drift Detection & Activity Log) surfaces any order that did fail every retry, with a reason, instead of failing silently.

Getting started

If your team is still fulfilling from separate admin panels for each storefront, order pull-through is usually the highest-impact place to start — it's the part of the workflow staff touch every single day, more than product sync itself. Read centralizing orders from multiple WooCommerce stores for more on the reporting and support benefits, or see the full feature list for how order and product sync work together. Plans that include order pull-through and source-store tracking are on the pricing page.