To edit WooCommerce products with Claude, connect your store through Meikero, ask Claude to read one product by its ID, and have it propose a new short and full description based only on information the product already contains or that you supply. After you approve the wording, Claude updates just those two fields, using the product’s current edit hash so it cannot overwrite a newer version, and then reads the product back so you can confirm nothing else changed.
This guide walks through that workflow step by step, with a prompt you can copy and the checks that keep prices, stock and variations safe.
What you need
- WooCommerce active on a self-hosted WordPress site.
- Claude connected to the site. If it is not yet, follow how to connect Claude to WordPress with MCP or the Meikero setup guide.
- Permissions. WooCommerce set to view only is enough for Claude to read products and suggest copy. To save changes, WooCommerce must be allowed to change.
- Meikero Pro to apply edits. Free lets Claude read products and draft proposals; writing them back is a Pro feature. See Meikero Free and Pro.
Claude runs in your own Claude account, so there is no Anthropic API key and no Meikero action credit involved. Your Claude plan’s availability and usage limits still apply.
Step 1: Pick the product by ID
Product names are easy to confuse — “Linen apron” and “Linen apron (kids)” are two different records. Ask Claude to search the catalogue first, then confirm the exact product ID before anything else happens. In Meikero, product search returns IDs and edit hashes for published and draft products.
Step 2: Inspect what Meikero supports
Reading a product returns its type, name, short and full description, prices, SKU, stock, categories, images, attributes, variation IDs and an edit hash. Not every field that WooCommerce stores can be changed through Meikero, and that is deliberate:
| Product data | Claude can read | Claude can update (Pro) |
|---|---|---|
| Short and full description | Yes | Yes |
| Name, SKU, categories, tags | Yes | Yes |
| Regular and sale price, stock status and quantity | Yes | Yes |
| Product image (by media ID) | Yes | Yes |
| Attributes and gallery images | Yes | No |
| Variations of a variable product | Yes | No |
| Orders, customers, payments, coupons | No | No |
For a description task, only the first row should change. Everything else is context.
Step 3: Propose new copy from verified facts
Good product copy is specific, and specific claims have to be true. Give Claude its sources: the current description, the product’s attributes and anything you paste in, such as a supplier spec sheet. Ask it to flag missing information rather than fill gaps with plausible-sounding details like materials, dimensions or certifications.
WooCommerce’s own guide to adding and managing products is a useful reminder that product types behave differently — a variable product, for example, can carry a separate price, SKU and stock level for each variation. Knowing the type tells you whether the description you are editing is the one shoppers actually read for the option they choose.
Copy this prompt, replacing the product ID:
Improve the descriptions of WooCommerce product ID 123 using Meikero.
1. Read the product with the available Meikero tools and tell me its type, name, current short description, current description, attributes and whether it has variations. Note the edit hash.
2. Propose a new short description (one or two sentences) and a new full description. Use only facts that appear in the product data or in notes I give you. Do not invent materials, dimensions, certifications, compatibility or delivery promises. List any information you would need but could not find.
3. Show the current and proposed text side by side, then wait for my approval. Do not change anything yet.
4. After I approve, update only short_description and description on this product. Do not send prices, stock, SKU, categories, images or any other field. Use the edit hash from your latest read; if the update is refused because the product changed, read it again and show me the difference before retrying.
5. Read the product back and confirm that the two descriptions match the approved text and that price, SKU and stock are unchanged.A fictional before-and-after example
Illustrative example. The shop and product below are invented to show the format; they are not a customer case or a measured result.
Product data available: stoneware, 350 ml, matte glaze, made in small batches; the merchant’s notes add “dishwasher-safe”.
| Before | Proposed | |
|---|---|---|
| Short description | Great mug. Buy now! | A 350 ml stoneware mug with a matte glaze and a wide, comfortable handle. Dishwasher-safe. |
| Description | This is our best mug. High quality. Perfect gift. | Each mug is made in small batches from stoneware and finished with a matte glaze, so no two are exactly alike. It holds 350 ml — enough for a large coffee or a pot of tea — and goes straight into the dishwasher. |
Note what is missing: the proposal does not say “microwave-safe”. No source confirmed it, so Claude should list it as a question for you rather than write it in.
Step 4: Apply only the approved fields
Meikero updates products through WooCommerce’s own product functions and only touches the fields included in the request. If Claude sends just the short and full description, prices, stock, SKU and variations are not part of the change.
Every product update also requires the edit hash from Claude’s latest read. If someone edited the product in the admin in the meantime, the hash no longer matches and the update is refused instead of silently overwriting their work. Product updates keep a data backup that can be restored if you change your mind.
Step 5: Review a small batch before expanding
Start with three to five products from one category. Read them together and check:
- Is every claim backed by product data or your notes?
- Does the tone match your shop, and do the products still sound different from each other?
- Are measurements, units and spelling consistent?
- Did the short description stay short enough for your theme’s layout?
Fix the prompt based on what you see, then continue in batches rather than across the whole catalogue at once.
Step 6: Read back and check the product page
The read-back in the prompt confirms what was stored. Then open the public product page yourself: where the short and full description appear depends on your theme, and a page cache may need clearing before the new text shows. Check it on a phone as well as a desktop.
Limits to keep in mind
- Product-level fields only. Variations, attributes and gallery images can be read but not edited through Meikero.
- No store operations. Orders, customers, payments and coupons are outside Meikero’s tools.
- Other plugins. Extra product fields added by other plugins are not specifically supported.
- You are the editor. Claude can write fluent copy that is still wrong. Review before approving, and keep your normal backups.
FAQ
Can I use this workflow on Meikero Free?
Partly. On Free, Claude can read products and propose new descriptions, and you can paste the approved text into WooCommerce yourself. Saving it directly through Claude needs Pro and WooCommerce change permission.
Could Claude change a price by accident?
Only if a price field is included in the update. The prompt above restricts the update to the two description fields and asks Claude to confirm afterwards that price, SKU and stock are unchanged.
What about variable products?
Claude can update the parent product’s descriptions and read its variations for context, but it cannot edit individual variations. If your theme shows variation descriptions, update those in WooCommerce.
Try it on one product
Pick a product whose description you already know is weak, run the prompt and compare. The WooCommerce tools in the Meikero reference list exactly what each tool reads and changes.
Once the copy is right, the same review loop works for search snippets: see how to update Yoast SEO titles and descriptions with Claude.
Related workflow: adding a new product rather than improving one? See how to turn product notes into a WooCommerce listing.