Orders reach your hub the moment they're ready to fulfil
A delayed order is a delayed shipment. If a child store's sales only reach your main dashboard on a schedule — every fifteen minutes, every hour — your fulfilment team is always working from slightly stale information, and same-day dispatch targets become a guessing game.
Stillpoint closes that gap by pushing an order to the hub the instant it reaches 'processing' status on the child store, which is the moment WooCommerce itself considers it ready to be picked and packed. If the hub happens to be briefly unreachable — mid-deployment, under maintenance, or experiencing a network blip — the push is retried automatically until it succeeds, so an order is never silently lost because of a few seconds of bad timing.
Key benefits
No polling delay
Orders arrive at the hub the moment they're marked processing, not on the next scheduled check-in.
Faster dispatch times
Same-day and next-day shipping commitments are easier to hit when fulfilment sees the order within seconds of payment confirmation.
Automatic retry on failure
If the hub is temporarily unreachable, the push is queued and retried, rather than failing silently.
Triggered by a meaningful status
Syncing on 'processing' rather than 'pending payment' means only orders that are actually ready to fulfil reach your fulfilment queue.
Consistent across every child store
The same instant-push behaviour applies to every connected store, so fulfilment timing doesn't vary by storefront.
How it works
- 1
Order reaches processing
A payment completes and WooCommerce marks the order 'processing' on the child store, as it would with any standalone store.
- 2
Push is triggered immediately
Stillpoint detects the status change and prepares the order payload for transfer without waiting for a scheduled cycle.
- 3
Signed delivery attempt
The order is sent to the hub over a secure, signed API call.
- 4
Retry on failure
If the hub doesn't acknowledge receipt, the push is automatically retried at increasing intervals until it succeeds.
- 5
Confirmation logged
Once received, the order appears in the hub's Orders list and the sync is recorded in the activity log.
Real-world examples
A footwear retailer's DE storefront takes an order for a set of hiking boots at 9:14am local time. Because the sync fires on the 'processing' status rather than waiting for a cron cycle, the order is visible in the UK hub's Orders list by 9:14am too, giving the warehouse team the full working day to pick and dispatch it.
During a scheduled maintenance window on the hub, an order comes through from the AU store. The push attempt fails on the first try because the hub is temporarily offline; Stillpoint retries automatically a few minutes later once the maintenance completes, and the order lands in the queue without anyone needing to notice or intervene.
On a high-traffic sale day, dozens of orders reach 'processing' within the same few minutes across the UK, AU and DE stores. Each one triggers its own instant push rather than waiting to be batched, so the fulfilment team sees a steady stream of ready-to-pack orders throughout the morning instead of one large backlog appearing all at once.
Who it's for
Suited to multi-store merchants with same-day or next-day dispatch targets, and to agencies operating fulfilment on behalf of clients who need order visibility in near real time rather than on a delay.
Frequently asked questions
Ready to put instant order sync on processing to work?
See pricing and pick the plan that matches how many stores you run.