Sync that never slows down your storefront
Real-time multistore sync sounds appealing until it starts blocking the very things it's meant to support — a product save that hangs for ten seconds, a checkout that times out because a plugin is busy calling three other sites. Many WooCommerce sync tools run their work inline, on the same request that a customer or staff member is waiting on, and any slow or unreachable connected store becomes everyone's problem.
Stillpoint avoids this by design. Every sync operation — product updates, stock changes, order pull-through — is handed off to a durable background job queue the instant it's triggered, so the person editing a product or checking out sees no delay at all. Jobs run asynchronously, retry automatically on failure with exponential backoff, and are built to be idempotent, meaning a retried job can never apply the same change twice or corrupt data.
Key benefits
Zero perceived delay
Saving a product or completing a checkout returns immediately; sync work happens afterwards, off the request cycle.
Automatic retries with backoff
A failed job doesn't just vanish — it retries with increasing delays, giving a slow or briefly offline store time to recover.
Idempotent by design
Every job is safe to retry or replay without risk of double-charging stock, duplicating orders, or reapplying a price change twice.
Isolated failures
One unresponsive connected store can't hold up sync for the rest of your network — each job runs and fails independently.
Queue visibility
You can see what's pending, what's retrying and what's failed, rather than guessing why a store looks out of date.
Scales with your catalog
Whether you're pushing one product edit or a bulk category rollout to a dozen stores, the same queue infrastructure handles the load.
How it works
- 1
An action triggers a job
A product edit, stock change, or order event on your hub creates one or more sync jobs.
- 2
Jobs enter the queue
Rather than running immediately, jobs are queued for background processing so the triggering request completes instantly.
- 3
Workers process asynchronously
Background workers pick up queued jobs and deliver them to the relevant target stores over the signed API.
- 4
Failures retry with backoff
If a store is unreachable or returns an error, the job retries after a short delay, then progressively longer delays, rather than hammering the target.
- 5
Outcome is logged
Whether a job succeeds after the first attempt or the fifth, the final result is written to the activity log for full traceability.
Real-world examples
A footwear retailer runs a UK flagship store plus separate AU and DE storefronts for regional pricing and language. During a Boxing Day sale, the merchandising team updates sale pricing and stock on over 400 SKUs in a single afternoon. Because each update is queued rather than processed inline, the WooCommerce admin stays responsive throughout — no editor sits waiting on a spinning save button while 1,200 sync jobs (400 products across three stores) work through the queue in the background.
Midway through the rollout, the AU store's hosting provider runs a scheduled maintenance window and briefly returns connection timeouts. Rather than failing outright, the jobs destined for the AU store retry automatically with exponential backoff — a few seconds, then longer gaps — and succeed as soon as the site is back. The UK and DE stores, unaffected, receive their updates on the original schedule with no cross-store delay.
A week later, a warehouse mis-scan causes the same stock adjustment to be submitted twice in quick succession for a popular trainer SKU. Because sync jobs are idempotent, the second job resolves to the same end state as the first instead of decrementing stock twice — the shoe retailer's stock count stays accurate across all three stores despite the duplicate trigger.
Who it's for
Built for multi-store merchants running high edit volumes or frequent sales, and for agencies who need sync behaviour that won't degrade client storefront performance under load.
Frequently asked questions
Ready to put background sync engine to work?
See pricing and pick the plan that matches how many stores you run.