Stage a whole catalog before anyone sees it live
Launching on a new store or preparing a seasonal range usually means either building every product live and hiding it with plugins, or waiting until the last possible moment to start populating a new site — both of which add risk right before launch. Most sync tools only move published products, leaving draft work stranded on the hub.
Stillpoint syncs drafts, pending and private products the same way it syncs published ones, and carries the status through to the target store. That means you can build out an entire catalog on your hub — descriptions, pricing, images, variations — and push it to a new or existing store while it's still unpublished, then flip it live on your own schedule.
Key benefits
Draft status carries through
A product left in draft on the hub arrives as a draft on the target store, not published by accident.
Stage entire launches in advance
Build out a full seasonal range or a new store's catalog ahead of time, without exposing it to shoppers early.
Pending review products sync too
Products awaiting internal approval sync in their current state, keeping review workflows intact across stores.
Private products supported
Products marked private stay private on the target store, useful for restricted or trade-only ranges.
Flip live on your own timeline
Publish a synced draft on the target store whenever you're ready, independent of when it synced.
Reduces launch-day risk
Because the catalog is already staged and synced, launch day becomes a status change rather than a data-entry scramble.
How it works
- 1
Build the product on your hub
Create the product as a draft, pending or private item, exactly as you would a published one.
- 2
Target the store
Choose the store — new or existing — that should receive this staged product.
- 3
Sync with status intact
Stillpoint syncs all product data and carries the current status across to the target store.
- 4
Review on the target store
Check the staged product on the target store's own admin before it goes live there.
- 5
Publish when ready
Change the status to published on the target store whenever your launch timing calls for it.
Real-world examples
A footwear retailer is opening a new DE store and wants the full 800-SKU catalog ready before launch day. Over three weeks, the team builds out products as drafts on the UK hub and targets them at the new DE store, so by launch day the DE store already holds a complete, correctly-priced catalog waiting only to be published.
A spring range is under internal review before release, with several styles marked pending while sizing and pricing get finalised. Those pending products sync to the AU store in the same pending state, letting the regional merchandising lead review currency-adjusted pricing on the AU site itself before anyone signs off.
A trade-only walking boot line is kept private, available only to logged-in wholesale accounts. When the range is targeted at both the UK and DE stores, the private status carries through on both, so the products don't appear in either public catalog until the trade access settings are separately configured on each store.
Who it's for
Aimed at multi-store merchants preparing new store launches or seasonal ranges in advance, and at agencies building out client catalogs ahead of a scheduled go-live date.
Frequently asked questions
Ready to put draft & unpublished product sync to work?
See pricing and pick the plan that matches how many stores you run.