Preview on the real store. Not a stale copy.
Your theme runs on the client's live WooCommerce site, visible only to people with the preview link. Everyone else sees the store as usual.
Staging starts aging the day you clone it.
A staging clone
- Products from the day you cloned
- New content missing, orders out of date
- Client needs a login to look
A ThemeSync preview
- Today's catalogue and every active plugin
- No copy to reconcile afterwards
- One link, no login
Connect once. Push like normal.
A small plugin on the client's site does the swapping. You keep working in git.
Install the plugin
Paste an Application Password and ThemeSync installs it for you, or upload the zip.
Connect your repo
Turn on auto-sync and each push reaches the preview on its own.
Publish when approved
Switch the store to your theme from the dashboard.
Screenshots and client comments, on the live store.
The same review tools Shopify teams use, pointed at the real shop, cart and product pages.
- Screenshots of every mapped page
- A CSS and JavaScript browser scan
- PageSpeed audits on the preview
What WordPress developers ask first.
Do shoppers see my unfinished theme?
No. The theme only loads for visitors who open the preview link. Everyone else sees the live theme.
What does the plugin need?
WordPress 5.6 or newer and an admin Application Password for the remote install. You can also upload the plugin zip yourself.
What about caching plugins?
Preview requests are marked as uncacheable. Some host or CDN caches ignore that, so you may need a bypass rule for the preview link.
Does it work with child themes?
Not yet. Previews run as standalone themes for now.
Is it a replacement for staging?
For theme review, yes. For plugin or PHP updates, keep your staging site.
Stop fighting staging drift.
Connect a WooCommerce site and send your first preview link.