Know exactly what happened on every sync, every store
The hardest part of running a WooCommerce multistore network isn't usually getting sync to work — it's finding out when it hasn't, and why. Without visibility, problems surface as customer complaints: a price that's wrong on one store, a product still showing an old description weeks after it was updated everywhere else, with no record of what went wrong or when.
Stillpoint keeps a complete activity log of every sync event across your network — what changed, which store it was sent to, and the result — alongside drift detection that actively compares each store's product data against the hub and flags divergence before it becomes a customer-facing problem. When something does fail, the log surfaces the specific error reason so you're troubleshooting a known cause, not guessing.
Key benefits
Full audit trail
Every sync event is recorded with what changed, the target store, and the outcome, giving you a complete history to refer back to.
Proactive drift detection
Stillpoint periodically checks synced products for divergence from the hub, catching manual edits or failed syncs before customers notice.
Actionable error reasons
Failures show the specific cause — an authentication issue, a missing field, a timeout — instead of a generic 'sync failed' message.
Per-store breakdown
See sync status and history filtered by store, useful when diagnosing an issue affecting only one site in your network.
Confidence at scale
As your network grows to dozens of connected stores, the log remains the single place to verify sync health rather than checking each site manually.
Supports accountability
When multiple team members or an agency manage the network, the log makes it clear who changed what and how it propagated.
How it works
- 1
Every sync job is recorded
As jobs run through the background engine, each attempt, retry and outcome is written to the activity log.
- 2
Drift checks run on a schedule
Stillpoint periodically compares product data on target stores against the hub's version.
- 3
Divergence is flagged
If a store's data no longer matches — due to a manual edit, a failed sync, or an external change — it's flagged for review.
- 4
Errors surface with context
Failed jobs record the specific reason for failure, not just a pass/fail status.
- 5
You review and resolve
From the activity log, you can identify the affected product and store and decide whether to re-sync, override, or investigate further.
Real-world examples
A shoe retailer's DE store manager, unaware that pricing is meant to sync from the hub, edits a product's price directly in the DE WooCommerce admin to run a local promotion. The next drift check flags that product as diverged, showing the hub price alongside the DE store's local value, so the merchandising team can decide whether to leave the local override in place or resync from the hub.
During a bulk update pushing new season imagery to 200 products across the UK, AU and DE stores, the AU store's API credentials had been rotated the week before without updating Stillpoint's connection settings. The activity log shows every job for the AU store failing with an authentication error, immediately pointing the team to the fix rather than leaving them to guess why only one store's images hadn't updated.
Three months after launch, the retailer's operations lead wants to confirm a specific SKU's price history across all three stores ahead of an audit. The activity log provides a timestamped record of every price change synced to that product, including who triggered each edit on the hub, giving a clear paper trail without needing to check each store individually.
Who it's for
Built for multi-store merchants who need confidence that sync is working correctly, and for agencies accountable to clients for the accuracy and traceability of multistore operations.
Frequently asked questions
Ready to put drift detection & activity log to work?
See pricing and pick the plan that matches how many stores you run.