Building a variable product by hand is a lot of clicking. You create the attributes, add each term, tick the box that marks them as used for variations, generate the grid, then open every single variation to set its price, SKU, and image. For a shirt in four sizes and three colors that is a dozen variations, and by the eighth one you have lost the thread.
This lets you describe the whole product once and have the agent do the assembly. It plans first and shows you the full grid, then builds everything as a draft. Nothing goes live until you have looked at it and published it yourself.
I want to add a new variable product to this WooCommerce store. Here is thespec:
[name, short and long description, the attributes and their options (forexample Size: S, M, L; Color: Black, Blue), the price for each variation or arule like "all the same price", SKUs if I have them, and any image URLs orimage notes]
Do not build anything yet. First, show me the full plan as a table: theproduct, which attributes you will reuse from what already exists versuscreate new, the complete variation grid with each price and SKU, and whichimage goes where. Let me correct it.
Only after I approve, upload the images, create any attributes that aregenuinely missing, then create the product as a draft and build eachvariation under it. Leave it as a draft so I can review and publish itmyself. At the end, give me the draft link and list everything you created.Why this is safe to run
Nothing is written until you approve the plan. The first pass turns your spec into a table, the attributes it will reuse against the ones it will create, the full variation grid with prices, and where each image lands, so you catch a wrong price or a duplicate attribute before it exists.
When you approve, the build still ends short of your customers. The product is created as a draft, never published, so it sits out of sight until you open it and hit publish yourself. This keeps the plugin’s rule intact: the agent drafts, a human publishes. Each of the write abilities behind this, uploading media, creating an attribute, creating the product, and creating a variation, stays off until you enable it, every call is checked against the capability of the user you bound the agent to, and every write lands in the Activity Log. If the draft is wrong, you can trash it and nothing was ever live.
Already connected? You do not have to paste this at all. Ask your agent for the “create a product from scratch with attributes and variations” recipe, hand it the spec, and it runs the same plan-then-build flow on your own store.