You want to point Claude at your Shopify catalog and say rewrite every product description to lead with the material, fix the SEO titles, and clean up the tags. What stops you is the storefront. It is live, it converts, and most ways of wiring AI to a store write straight to it, so one confident rewrite ships to every product before you can read it.
Scratch changes where the edit happens. Claude does 99% of the work, reading and rewriting every product as files on your laptop. The last 1%, deciding what actually ships to the storefront, stays with you. Nothing goes live until you have seen the change as a diff and approved it.
How it works
- Scratch pulls your catalog into files. Every product comes down as one JSON file in Shopify's GraphQL Admin shape, in a folder on your laptop.
- Claude edits the products. Open the folder in the Claude desktop app. Try a prompt on a few products in Chat, then let Cowork or Code run it across the whole catalog. Rewrite every description to under 160 words and lead with the material. Claude edits the files, never the live store.
- You review every diff and publish. Scratch shows each changed field next to the original, word by word. Approve what ships, and Scratch writes only those products back through the Admin API, one at a time.
What people use it for
Most people arrive with a catalog they have outgrown, because fixing it by hand means opening every product one at a time.
- Rewrite every description to a consistent length and voice.
- Write the missing SEO title and meta description across the catalog.
- Lead each description with the material, fit, or benefit instead of boilerplate.
- Clean up vendor, type, and tags so collections and filters behave.
- Refresh your blog and pages to match a new brand voice.
Pull 50 products to feel the loop, then point Claude at thousands. The first job on that list is on video, start to finish, including the moment the review step catches an edit Claude was never asked to make:
Why not an MCP server?
A Shopify MCP server or app hands Claude a direct line to your live catalog. The publish button is wired straight in, so one overzealous rewrite ships to every product at once and you are fixing it by hand.
Scratch gives Claude the same full read and write access, but against a local copy. The publish step is pulled out and handed to you. Claude can change anything; only you can ship it. On a storefront that is making sales, that is the difference that matters.
What Claude edits in Shopify
- Product titles, descriptions (HTML), and handles
- Vendor, type, and tags
- Product SEO title and meta description
- Articles, blogs, and pages
Prices, variants, inventory, and metafields stay locked at the connector level. Claude cannot write them back even if it tries, and length and taxonomy validators flag problems right on the diff. For the full field list, see Scratch for Shopify.
Questions people ask
Is this an MCP server or a Shopify app?
No. An MCP or app gives Claude the publish button straight to your store. Scratch does not. Claude gets the same access, but publishing is a separate step you approve, one product at a time.
Will Claude touch my prices or inventory?
No. Prices, variants, inventory, and metafields are locked at the connector. They cannot be written back, even by mistake.
Can I undo a change after it ships?
Yes. Every published product is reversible from Scratch, per row. The original sits next to the rewrite until you decide which one stays.
Why not just bulk-edit with a CSV or an app?
A CSV import and a bulk-edit app both write straight to the live catalog with no word-level diff and no per-product approval, and a find-and-replace only does exactly what you spelled out. Scratch puts an agent on the edit, so it handles the messy cases a rule cannot, and holds every change as a diff you approve before anything ships.
Can it handle my whole catalog at once?
Yes, that is the use case. Pull 50 products to feel the flow, then pull thousands. Cowork and Code are built for catalog-scale jobs.
Do I need to be technical?
No. Install Scratch, connect Shopify, point Claude at the folder, and approve the diffs. Validators are optional, for when you run the same job often enough to want guardrails.
See it on your own catalog
The fastest way to trust it is to watch it run on your products. Book a 30-minute demo on your Shopify catalog →, or try Scratch free and run the first pass yourself.