Order capture with three layers of redundancy, not one
Relying on a single sync mechanism for something as business-critical as orders is a risk most merchants don't notice until an order goes missing. A single failed webhook, a missed cron job, or a brief outage at the wrong moment can mean a paid order sits unfulfilled on a child store while the hub has no idea it exists.
Stillpoint is built on the assumption that any one mechanism can occasionally fail, so it never relies on just one. The hub actively pulls orders from each child store's WooCommerce REST API on a regular schedule and on demand, every child store also pushes new orders instantly the moment they're ready, and per-order and bulk 'Push to hub' buttons give your team a manual safety net whenever they want certainty on demand. It's belt-and-braces order capture: three independent paths to the same result, so a gap in one is covered by the other two.
Key benefits
Three independent capture paths
Scheduled pulls, instant pushes and manual buttons all feed the same Orders list, so no single point of failure can cause a missed order.
Scheduled pulls catch what instant push misses
Even if an instant push fails for any reason, the hub's regular pull from each store's REST API picks it up on the next cycle.
On-demand pull for peace of mind
Trigger a pull from any connected store whenever you want to confirm the hub is fully up to date, without waiting for the schedule.
Manual push as a last resort
A per-order 'Push to hub' button lets staff force a specific order across immediately if they ever suspect it hasn't synced.
Bulk push for batches
Select multiple orders on a child store and push them to the hub in one action, useful after reconnecting a store or resolving an outage.
Confidence at scale
With three overlapping mechanisms, merchants running high order volumes across many stores can trust that nothing slips through.
How it works
- 1
Instant push fires first
As soon as an order reaches 'processing' on a child store, it attempts to push to the hub immediately.
- 2
Scheduled pull runs independently
On its own schedule, the hub queries each child store's REST API for any orders it doesn't yet have.
- 3
On-demand pull available anytime
Staff can trigger an immediate pull from a specific store rather than waiting for the next scheduled run.
- 4
Manual push as backup
If a specific order or a batch of orders needs to be sent across right away, the 'Push to hub' buttons handle it in one click.
- 5
Deduplication on arrival
Whichever path an order arrives by, Stillpoint checks it hasn't already been imported before creating a duplicate on the hub.
Real-world examples
A shoe retailer's AU store experiences a brief hosting-level network issue right as a customer's order moves to 'processing'. The instant push attempt fails silently at that moment, but the hub's scheduled pull runs twenty minutes later, finds the order via the AU store's REST API, and imports it — the fulfilment team never even notices anything went wrong.
After reconnecting the DE store following a plugin update, the store manager wants certainty that every recent order has made it across. Rather than waiting for the next scheduled pull, they trigger an on-demand pull for that store from the hub, and any orders placed during the update window come through immediately.
A customer service lead spots that one specific UK order seems to be missing from the hub after a payment gateway hiccup. Instead of investigating logs, they open that order on the source store and click 'Push to hub' directly, and it appears in the main Orders list within seconds — no need to wait for any scheduled process at all.
Who it's for
Aimed at multi-store merchants who cannot afford to miss a paid order regardless of network conditions, and at agencies who need a reliable, auditable order pipeline across every client store they manage.
Frequently asked questions
Ready to put reliable two-way order capture to work?
See pricing and pick the plan that matches how many stores you run.