Looking for a WooMultistore alternative?
Rather than trash-talk any specific plugin, here's an honest checklist of what actually matters when you're running products and orders across multiple WooCommerce stores — and how Stillpoint approaches each one.
Capability checklist
| Capability | Why it matters | Stillpoint |
|---|---|---|
| Modern dashboard UI/UX | A clean admin experience that doesn't feel bolted onto WordPress. | |
| Durable background sync queue with retries | Product changes are queued and retried automatically if a store is briefly unreachable, instead of failing silently. | |
| True order pull-through into native Orders | Orders from every connected store land in your hub's real WooCommerce → Orders screen — not a separate reporting tab. | |
| Source store name + original order number shown | Every pulled-through order is labelled with which store it came from and its original order ID for easy reconciliation. | |
| Full variation, attribute, image & taxonomy sync | Variable products, galleries, categories and tags all sync — not just simple products and titles. | |
| Per-product store targeting (not push-to-all) | Choose exactly which stores each product belongs to, rather than every product landing on every connected site by default. | |
| HPOS (High-Performance Order Storage) compatible | Works cleanly with WooCommerce's modern order storage as well as legacy post-based orders. | |
| Instant order sync the moment an order hits processing | Child stores push the order to the hub straight away rather than waiting for the next scheduled poll, with automatic retry if the hub blinks. | |
| Two-way order capture with a manual safety net | Scheduled pulls, instant pushes and per-order “Push to hub” buttons mean an order has three ways to reach your dashboard. | |
| Auto-sync on save with a process-now option | Editing a product on the hub queues it to its target stores immediately, so pricing changes propagate in minutes rather than overnight. | |
| Signed HMAC transport with nonce replay protection | Every hub-to-store request is signed and timestamped with a one-time nonce, and pairing keys are scoped and revocable. | |
| Works with Multisite and separate installs | Connect sub-sites on a WordPress Multisite network, or entirely separate WooCommerce installs via a signed API — your choice. |
Always verify current capabilities directly on each vendor's own site — plugin features change over time.
The differences you feel on day one
Orders land in the dashboard you already use
Child-store orders arrive in your hub's native WooCommerce → Orders list — full billing and shipping, phone, payment method, customer note and original order date — so your existing packing slips, filters and fulfilment plugins keep working.
Read the detailNo waiting for a cron window
As soon as an order reaches processing on a connected store it is pushed to the hub, and a failed push retries by itself until it lands.
Read the detailNothing is pushed everywhere by default
Each product carries its own list of target stores, set from a checkbox panel on the edit screen or by ticking cells in the sync matrix. Your outlet store never inherits the flagship range by accident.
Read the detailVariable products arrive complete
Every size, colour and width comes across with its own SKU, price, stock and image, and missing attributes are recreated on the target store rather than silently flattened.
Read the detailMedia that doesn’t multiply
Featured images, galleries and variation images are written into each store’s own media library and deduplicated by source, so the tenth re-sync adds nothing to the uploads folder.
Read the detailReliability you can audit
A durable job queue with exponential backoff and idempotent writes keeps product saves and checkout fast, while the activity log records what changed, where, and why anything failed.
Read the detailModern WooCommerce, not legacy assumptions
HPOS order storage, PHP 7.4 through 8.3 and current WordPress and WooCommerce releases are all supported, so your hosting roadmap isn’t held back by your multistore plugin.
Read the detailWho each approach is for
Stillpoint fits stores that need
- Reliable background sync that survives a flaky connection or two.
- Orders from every store to actually appear as fulfillable WooCommerce orders.
- Control over exactly which products go to which stores.
- A mix of Multisite sub-sites and standalone installs in the same network.
A simpler tool might suit you if
- You only need to mirror a handful of simple products with no variations.
- You don't need orders consolidated in one dashboard.
- You're not concerned with per-store targeting and are happy pushing everything everywhere.
Migrating to Stillpoint
- 1
Install Stillpoint on the WooCommerce store you want as your hub — this doesn't affect your existing plugin until you're ready.
- 2
Connect your first child store with a signed API key (or select it directly if it's a Multisite sub-site).
- 3
Run an initial sync pass on a small product category to confirm variations, images and stock levels arrive correctly.
- 4
Gradually target the rest of your catalog using the sync matrix, then deactivate your previous multistore plugin once you're confident.
See the difference in your own catalog
Connect a store, target a handful of products, and watch background sync and order pull-through work in real time.