Keep your staging store in sync, without losing what you built there

The first clone gives staging a full copy of your live store. From then on, your team keeps working in the live store: new products, price changes, a rewritten page. Meanwhile someone is testing a new collection layout in staging. You can't clone again every time, because a clone would replace what's being tested. That's what a sync is for.

Only what changed

A sync reads what changed in your live store since the last one and copies only that. New products arrive with their variants, images, filled fields and collections. Edited records are updated. Nothing else is touched, so a sync is quick even on a large catalog.

A preview first

Before anything is written, the preview lists what will be created and what will be updated in staging. Check it, then sync.

Edited in both stores? You decide

Sometimes the same product was changed in the live store and in staging. Cartsella Studio doesn't pick a winner for you. It flags a conflict and asks: use the live store's version, keep staging's, or skip it for now.

You can also tell a sync what to leave alone. Under Fields to copy, untick SEO, prices or images for products, collections, pages and blog posts, and staging keeps its own. Records you protect (one product, a handle pattern like qa-*, a whole type or a metafield namespace) are never changed by a sync.

Nothing in staging is removed

A sync never deletes what exists only in staging: test products, draft pages and experiments stay where they are. Removing them is a separate choice you make when you clone, and it always takes a backup first.

By hand, on a schedule, or live

• Sync now, on every plan: one click whenever you want staging to catch up.
• On a schedule, on every paid plan: anything from every hour to once a week.
• Live, on Agency: each change in the live store reaches staging about a minute later, and a daily check catches anything that was missed.

Every sync runs in the background. Close the tab and come back later; if it's interrupted, it resumes where it stopped without creating duplicates.

Your live store is only read

A sync copies from your live store into staging, never the other way. Customers, orders and draft orders are never copied. When product fields you filled in staging are ready, you move them to the live store yourself, with a preview and an undo.

Read next: How clone & sync works · Fill in product fields in staging, publish them when they're ready