Create WooCommerce Products with AI: From a Message to a Draft

To create WooCommerce products with AI, you describe a product to an assistant in your own words (name, price, stock, category) and it builds that product in your shop. BEAR's MCP server is what connects the two: it gives an assistant such as Claude a fixed set of tools for your catalogue, and the tool that adds products works in two steps, a preview you read and a creation you agree to. The new product arrives as a draft, so customers see nothing until you publish it.

Before you start. You need BEAR 2.2.4 with the MCP server option switched on in the BEAR settings, a shop served over HTTPS, and an assistant connected to it with your MCP key: Claude in the browser, the desktop app or Claude Code, or another client that speaks MCP. The access behind that key has to allow editing products; adding photos also needs access to the media library. The connection itself is described step by step in the MCP server documentation.

Create a WooCommerce product with AI: one example from start to finish

Say a new apron has arrived and you want it in the shop. You type:

Add a new product: Linen Apron Natural, price 34.90, SKU AP-LIN-01, 25 in stock, category Kitchen textiles. Short description: heavy washed linen, adjustable neck strap, two front pockets.

This is what happens next.

1. The assistant looks up the category. BEAR takes categories only as IDs of categories that already exist, never as names. So the assistant first reads your category list and finds the ID of Kitchen textiles. If there is no such category, it tells you instead of guessing. The reason is simple: a name with a typo would otherwise turn quietly into a new, empty category.
2. It asks for a preview. The preview tool (woobe_create_preview) writes nothing. It returns the product as it would be created (type, name, regular and sale price, SKU, stock, categories and other terms) together with any warnings. The assistant reads this back to you, usually as a short table.
3. You confirm. You check the price and the SKU and answer Yes, create it. The creation tool runs only when the assistant passes on that confirmation; without it BEAR answers that creating needs an explicit yes from you after the preview, and nothing is created.
4. The product is created as a draft. The answer contains the new product ID and a link to its edit screen in wp-admin. Because you gave a quantity, stock management is switched on for the product. It is not visible in the shop yet.
5. Photos. You write I have three photos for it. The assistant gives you an upload link, you drag the files in, and they are attached to the apron. How that works is explained below.
6. You publish. After a look at the draft you write Publish it. The assistant changes the product status to published, a single field edit that is recorded in BEAR's History like any other edit.

The names and numbers are only an example; the order is what matters: preview, your yes, a draft, photos, then publishing when you are satisfied.

What the assistant can set when it creates a product

One creation request can carry the following. Only the product type and the name are required, and an ordinary product with one price is the simple type.

Some things are not part of the creation step: images, weight and dimensions, shipping and tax class, sale dates. The assistant sets them on the draft afterwards, one field at a time, with the same rules as for editing any existing product. In the free version some of those fields are closed to the assistant, and it says so plainly rather than pretending; the free version limitations list which. Photos are a separate step for a practical reason: the files have to reach your shop first.

Variable products are created the same way. Make a variable product Linen Apron in natural, charcoal and olive, 34.90, 10 of each gives a preview with the attributes and a table of every variation with its price and stock, and the number of rows is stated before anything exists: three colours and four sizes is twelve variations, and the preview says twelve. You can strike rows or change prices per row before you agree. SKUs given to individual variations are not checked in the preview, and one that is already taken is left off its variation, so ask the assistant to read the variations back after creating. Creating WooCommerce variations with AI covers variable products in full.

Drafts first: review, then publish

New products are drafts on purpose. A product is often put together over several messages (created, then photos, then a weight), and a half-finished item on a live shop is worse than no item at all. The draft is also where you catch what the assistant got wrong: a price of 349 instead of 34.90 costs nothing while the product is a draft.

To check a draft, open the edit link from the answer, or ask Show me the product you just created and the assistant reads it back from the shop. Then publish it in one of these ways:

• One product: Publish it. The assistant switches the status to published on that product. The change is in History with your name and the mark that it was made through an AI agent.
• Several drafts: Publish the four drafts you created today. The assistant can do this as one bulk status change: it selects those products, tells you the count, and writes only after you confirm that number. A bulk operation is recorded in History as a whole, so it can be rolled back to drafts in one step.
• Straight to the shop: if you want a product live immediately, say so: Create it and publish it right away. The assistant is instructed to pass the published status only when you explicitly asked for it. Otherwise the product stays a draft.

What BEAR checks, warns about and refuses

The preview and the creation are built from the same plan, so the preview cannot promise something the creation then does differently. That is also why the checks happen in the preview, before you agree.

Warnings: you decide whether to go ahead

• A product with the same name exists. If a product with exactly this name is already in the shop (published, draft, pending, private or scheduled; the trash does not count), the preview gives its ID. Usually that means the request was sent twice, not that you want a second product.
• The SKU is already in use. The preview names the product that owns it. WooCommerce allows each SKU only once, so if you create the product anyway it gets no SKU at all, and the creation answer says that the SKU was left empty. Give another SKU instead; bulk editing SKUs explains the uniqueness rule.
• A category or term does not exist. An ID that is not in the taxonomy is skipped, with a warning. A product left without any category goes to WooCommerce's default category, which on most shops is Uncategorized.
• New attribute values. For a variable product, a value your shop has never used is created on the way. When it looks like a value you already have, such as "S" next to "Small" or "Gray" next to "Grey", the preview names the existing value so you can choose it instead of adding a second size or colour that no filter knows.
• Variations without a price. WooCommerce does not sell a variation that has no price, so the preview counts them.
• An empty group. A grouped product with nothing in it, or a product ID in the group that does not exist.

Refusals: nothing is created

• No name, or a type other than simple, variable, external or grouped.
• An external product without its product URL.
• A taxonomy or global attribute that does not exist on the shop. A misspelled taxonomy is refused as a whole rather than ignored.
• A variable product without attributes, a listed variation without a value for every attribute, two rows for the same combination, or more than 200 variations.
• Creating without your confirmation after the preview.
• Something your access does not cover. With a personal key that is closed for attributes or for variations, a product that would create new attribute values or variations is refused before anything is written, and the preview already tells you so.

Photos from your computer

A photo pasted into the chat cannot be put on a product: the assistant receives a picture to look at, not a file it could pass on to your server. Ask for an upload link instead: I have photos for the apron. The assistant gets a link tied to that product from BEAR, you open it in any browser, on a computer or a phone, and drag the photos in. The page needs no login, names the product, sends the files one at a time and shows each one as added or with the reason it was refused. When you say you are done, the assistant asks BEAR what arrived and reads the file names back.

If the product has no main image yet, the first photo becomes the main image and the others go into the gallery in the order they were sent. If it already has one, every photo goes to the gallery. To change that afterwards, say what you want in full: Make the second photo the main image and move the current main image into the gallery.

The link works for fifteen minutes, counted again from each file that arrives, and takes up to 20 images. Each file can be as large as your server accepts for uploads. Photos that are already online can be imported from their address, and photos already in your media library can be found by name or upload date. All of that, with matching photos to many products by SKU, is in bulk upload WooCommerce product images with AI.

Add many products to WooCommerce from a list

Paste the list as it is, as lines of text or a table copied from a spreadsheet:

Create these as drafts in the category Aprons, and show me all the previews in one table before you create anything:

• Linen Apron Natural, 34.90, AP-LIN-01, 25 in stock
• Linen Apron Charcoal, 34.90, AP-LIN-02, 18 in stock
• Canvas Apron Olive, 29.00, AP-CAN-01, 40 in stock

BEAR creates one product per call, so the assistant works through the list: a preview for each product and, after your yes, a creation for each. Asking for all the previews as one table first is the useful habit. You can correct a row, drop one, and then agree to the whole list at once. Each creation answer gives the new ID and edit link, and at the end the assistant can sum up what was made.

• Repeated lists are caught. If a conversation breaks off halfway and you paste the same list again, the products that already exist show up in the previews with the duplicate-name and SKU warnings, instead of being created a second time.
• The same SKU twice in one list slips through when all the previews are made before anything is created, because neither product exists yet at that moment. The first product then gets the SKU; the second is created without it, and its creation answer says so. Check the SKU column of the preview table for repeats.
• Approvals. Claude asks before it uses a tool, according to its connector settings. With writing tools set to need approval, you approve every creation. On a long list that is slower, but you see each product go in.
• Size. A few dozen products are comfortable in one conversation. For hundreds of rows from a supplier file, WooCommerce's own product CSV importer is the faster tool, and the assistant is then useful for checking and correcting what came in.
• Not the generator. BEAR's MCP server also has a generator that fills a test shop with thousands of invented products. It is meant for development shops only, never for a real catalogue.

Undo: removing a product you did not want

Creating a product is not an edit of values that existed before, so it is not an entry in BEAR's History and there is no rollback for it. History starts with the first change made to the product afterwards, for example publishing it or changing its price; those changes can be rolled back as usual.

The way back from a creation is deleting the product: Delete the draft Linen Apron Natural. The assistant shows what would be removed, asks you to confirm the count, and moves the product to the trash, its variations with it. From there it comes back with Restore the apron I just deleted, or from Products, Trash in wp-admin.

Two things stay behind after a delete. Attribute values created for a variable product remain in the attribute, ready for other products; removing a value is a separate request with its own confirmation, and that one cannot be undone. Uploaded photos stay in the media library, because the same image may be used elsewhere.

Ready prompts

• "Create a simple product: Canvas Tote Bag, 24.00, SKU TOTE-01, 60 in stock, category Bags."
• "Add Linen Apron Charcoal as a draft, 34.90 with a sale price of 29.90, tags linen and kitchen."
• "Create these products as drafts in Aprons and show me all the previews in one table first: …"
• "Make a variable product Linen Apron in natural, charcoal and olive, 34.90, 10 of each colour."
• "Create an external product Cast Iron Pan, 89.00, sold at https://example.com/pan, button text Buy from the maker."
• "Create a grouped product Apron Gift Set with the natural and the charcoal apron."
• "Write a short description for the tote bag from these notes: 12 oz canvas, inner pocket, made in Portugal. Show it to me before you create the product."
• "I have photos for the tote bag. Give me an upload link."
• "Read back the products you created today: name, price, SKU, stock and category."
• "Publish the tote bag and the two aprons you created today."

Questions

Can I add products to WooCommerce with ChatGPT?

Any assistant connected to BEAR's MCP server uses the same tools, with the same preview and confirmation. Claude connects with the BEAR key in the browser, the desktop app and Claude Code. ChatGPT's custom connectors currently expect a sign-in flow rather than a key, so a direct connection may not be available yet; some releases offer a field for an API key, and if yours does, the key goes there.

Will the AI write product descriptions for me?

Only when you ask. Without your text or a request, the description stays empty: the creation tool tells the assistant not to invent copy for your shop. When you do ask, have it show you the text before the product is created, because the preview itself lists the product data, not the description.

Does the free version of BEAR limit creating products?

Creating products and adding photos are not counted toward the free version's writing allowance of 100 products every 30 minutes. Publishing a draft and the fields set afterwards are edits: each product counts as one, and only the fields open in the free version can be written.

How many products can I create in one conversation?

BEAR sets no limit on the number of products, only 200 variations per variable product. The practical limits are your patience with approvals and the length of the conversation; for hundreds of products, import a CSV file.

Checklist

• The MCP server is on, the assistant is connected, and your access covers products (and the media library for photos).
• Give the name, price, SKU, stock and an existing category. Say "publish" only when you mean it; otherwise you get a draft.
• Read the preview: price, SKU, category, the variation count, and every warning (same name, SKU in use, missing category, new attribute values).
• Answer yes only to what the preview shows.
• Add photos through the upload link and check which one became the main image.
• Open the draft, then publish it.
• For a list, ask for all previews as one table first, and use distinct SKUs.
• For a product you did not want, delete the draft: it goes to the trash and can be restored.

If creating products through the assistant does not behave as described here, ask on the BEAR support forum.