Shared stock that stays accurate everywhere, instantly
When the same product is listed on several WooCommerce stores, stock is the field that breaks trust fastest. A customer completes checkout on one storefront for what turns out to be the last unit, while two other regional sites still advertise it as available — the result is a cancelled order, a refund, and an apology email that shouldn't have been necessary.
Stillpoint treats stock as shared state across the stores a product is synced to, not a per-store copy that drifts over time. A sale, a manual stock edit, or a warehouse correction on any connected store propagates the new quantity and status to every other store carrying that product, keeping availability consistent network-wide without anyone manually reconciling numbers.
Key benefits
No overselling
Once stock is depleted on one store, every other connected store reflects that immediately, closing the window where duplicate sales happen.
Sales and edits both propagate
It doesn't matter whether the stock change comes from a checkout or a manual admin edit — both trigger the same real-time update.
Stock status and quantity together
In-stock, out-of-stock and backorder status sync alongside quantity, so a store never shows a contradictory state.
Per-product control
Not every product needs shared stock — you decide which items pool inventory across stores and which stay independent.
Fast enough to matter
Propagation happens in the seconds after the triggering event, not on the next scheduled batch run.
Resilient under load
Built on the same background queue as the rest of Stillpoint, so a burst of orders during a sale doesn't cause stock updates to fall behind.
How it works
- 1
A stock-affecting event occurs
A checkout completes on any connected store, or someone edits stock manually on the hub or a store.
- 2
Shared quantity recalculates
Stillpoint updates the shared stock figure for that product based on the new information.
- 3
The change queues for propagation
A sync job is created for every other store carrying that product.
- 4
Each store updates independently
Target stores receive the new quantity and status over the signed API and apply it to their native WooCommerce stock fields.
- 5
Drift checks run in the background
Periodic drift detection compares stock across stores to catch anything that falls out of sync unexpectedly.
Real-world examples
A shoe retailer with UK, AU and DE stores lists a limited-run trail runner as a shared-stock product across all three, with 60 units total. A customer in Manchester buys the last pair in size 9 at 11:04am UK time. Within seconds, the AU and DE stores — still mid-morning and midday locally — both show size 9 as out of stock, without either regional team having touched their own dashboard.
During a warehouse stocktake, the operations team discovers three pairs of a discontinued style were miscounted and adjusts the figure down on the hub store from 12 to 9. That correction propagates the same way a sale would: the AU and DE storefronts drop to 9 units immediately, preventing either site from selling stock that doesn't physically exist.
A flash promotion on the DE store drives a surge of 40 orders in under a minute for a popular sneaker. Because stock decrements are processed through the queue in order rather than all at once against a single number, the shared quantity lands accurately at zero rather than going negative, and the UK and AU stores flip to out-of-stock the moment the last unit sells.
Who it's for
Built for multi-store merchants selling the same or overlapping catalogs across regional or brand-specific storefronts, and for agencies managing inventory-sensitive client networks.
Frequently asked questions
Ready to put real-time inventory & shared stock to work?
See pricing and pick the plan that matches how many stores you run.