Every part of a WooCommerce or CloudCart store, moved in one click. Then one store leads and the others follow, in their own currency. Nothing is written until you have seen the plan.
Your old store is read, every part of it, and written into Shopify with one click once you have seen the plan. Its look comes too: its pages, menus and pictures rebuilt on a Shopify theme for you to publish.
Your Shopify store in one click through Shopify’s install screen. Your old store by its address, and a key if you have one.
Every part of the old store is read and shown to you, record by record. The old store is never changed.
Each part’s changes are worked out and laid out on one screen before anything is written.
One click writes it into Shopify, parts in the order they depend on each other.
One store leads. The others follow the parts you choose, in their own currency, keeping what is theirs. This is our demo fleet as it stands, one product in each store.
Mark one store the lead. Every other store follows the parts you choose, and keeps the fields that are its own.
Each store takes prices from the lead by its own rule: an exchange rate, how to round, a percentage off.
See where each store differs from its lead, part by part and record by record.
Send chosen records to chosen stores from a plan you have seen. Put a send back while the store still holds what it left.
A move, a send to three stores or one price: each is laid out record by record as what it becomes. This is the plan of the move above.
Each one is read, moved, compared between stores and sent. You choose which parts a move brings or a store follows.
An old store on its way in, an EU and a UK store, an outlet, a store per brand. One console for all of them.
Each product once, across every store that holds it, matched by SKU. Products missing a SKU, picture, price or description are flagged.
Each store takes its prices from the lead by its own rule: an exchange rate, how to round, and a percentage off for an outlet.
A store can keep its own titles, any other field, or a whole record. Nothing sent to it overwrites them.
Every change is a plan first. If the store changed since the plan, the write is refused. After writing, it reads back and flags any difference.
A change can be undone while the store still holds what it left. Each store keeps a timeline of every change.
Turn it on per store and changes to products, collections or discounts are picked up as they happen. No nightly sync.
Connect Claude, Codex or any assistant that speaks MCP. It reads, compares and plans by the same rules you do, and each change it makes is logged as made through it.
Admins connect stores and write; members look. Store keys are encrypted twice. Who opened customers or orders, and when, is logged.
No. Those are only read. Catalogwright writes to Shopify and nowhere else.
No. There are thirteen parts and you choose which come across. The usual ones are ticked for you.
No. Each store follows only the parts you choose, and keeps the fields and records that are its own.
Each store follows prices by its own rule: an exchange rate, how to round, and a percentage off if it is an outlet.
The write is refused. Work the plan out again and you get one that matches the store as it is now.
Yes, while the store still holds what it left. Every store keeps a timeline of each change made to it.
In the EU. It is seen only by your team and never sold. Removing a store removes everything read from it.
We are opening Catalogwright one team at a time, so every start begins with a conversation.
We’ll write to you from hello@smarch.co to find a time for the call.