Start by giving ChatGPT one product, a reliable set of facts and a specific job. Use it to sharpen your product copy, find conflicting information and answer the questions that keep landing in your inbox. You can do all of that without installing a WooCommerce AI plugin.
“Improve my store” is a wish. “Compare this description with these three product variants and show me what contradicts what” is a useful brief.
The workflows below use information you paste or upload to ChatGPT, followed by changes you make in WooCommerce. Pasting a store URL doesn’t give ChatGPT access to your product editor, orders or settings.
In this guide
Give ChatGPT a reusable shop brief
Before asking for copy, tell ChatGPT what you sell, who buys it and what good writing looks like for your shop. Include one short example you like. “Professional but friendly” could describe half the internet.
If you’ll use it regularly, create a ChatGPT project for your shop. Add your approved product information and put the recurring writing rules in its instructions. Projects keep related chats, files and instructions together; start a separate chat for each distinct job. OpenAI’s project guidance.
Copy this brief and replace the brackets:
We run [shop name], a WooCommerce store selling [products] to [specific customer] in [main market]. Customers usually choose based on [fit, size, compatibility, material, delivery or other real buying criteria]. Write in [US/UK English or another language]. Sound [brief voice description]. Here is a paragraph that gets our voice right: [example]. Use the product facts and policies I supply. Preserve model names, SKUs, units and limits. Put missing information in a separate questions list. Prepare drafts only. Today's task: [one specific outcome].
Useful trick: date your source files and name the current one in the prompt. A folder containing “delivery-final”, “delivery-final-2” and “delivery-final-actually-final” is already doing enough damage without asking AI to choose the winner.
1. Write the two descriptions WooCommerce needs
Give the short description and main description different jobs. The short version should help a buyer decide whether to keep reading. The main description should explain the details that make the product right for the job.
WooCommerce has separate product-description and product-short-description fields. Open Products → All Products → Edit to work on them; your theme or page builder can change how they appear. WooCommerce’s product editor guide.
Write copy for this WooCommerce product using only the facts below. Buyer: [who is choosing it and for what job] Approved facts: [specifications, included items, options and limits] Current copy: [paste] Return: 1. A short description: one useful opening sentence and up to four buying-point bullets. Maximum 90 words. 2. A main description of 180–250 words, with headings for the job it suits, key details and what is included. 3. Questions I must resolve before publishing. Don't repeat the short description word for word in the main one. Don't add claims such as “waterproof”, “food-safe” or “compatible with all models” unless my facts explicitly support them.
The word counts are starting points, not targets to pad out. A replacement washer may need a precise fit statement more than it needs 250 words.
A simple example: suppose your supplied facts describe a 60-litre storage box measuring 600 × 400 × 320 mm, with a lid sold separately. An opening could be: “A 60-litre storage box measuring 600 × 400 × 320 mm. Add the matching lid separately if you need a covered box.” It answers a purchase question. “Discover the ultimate storage solution” does not.
Before saving, compare the numbers and included items with your source. Put the approved short copy in the short-description field and the detailed copy in the main description. Preview the product on your phone as well as your computer.
2. Find contradictions between variants
Variable products deserve their own check. A shared paragraph can promise a feature that only one option has: an oak worktop on a vinyl model, a battery on the mains-only version, or a pack of ten when the buyer has selected one.
In WooCommerce, each variation can have its own price, SKU and other details. Compare the shared copy with the actual variation data, not just the product title. WooCommerce’s variable-product documentation.
Check this variable product for contradictions. Don't rewrite it yet. Shared title and descriptions: [paste] Approved variation table: [paste each SKU, option, included items and specifications] Return a table with: - Exact wording that causes a problem - Affected SKU or option - The conflicting fact - A precise replacement sentence Separate confirmed contradictions from missing information. Shared copy must remain true for every option. Don't infer a variant's features from its name alone.
Useful trick: request the exact conflicting sentence. That turns a vague “check consistency” answer into a list you can act on.
After editing, select each option on the live product page and check the visible copy, price, SKU and images. ChatGPT can compare what you provide; it hasn’t demonstrated that your selector updates correctly just by reading a table.
3. Turn repeated questions into page improvements
If customers keep asking whether the charger is included, answer that near the buying controls. You don’t need a grand content strategy for a missing charger.
Collect a small batch of real questions. Remove names, email addresses, order numbers and other personal details before sharing them. Include your approved answers or relevant policy text.
Use these customer questions to improve our product pages. Questions: [anonymised questions, one per line] Approved product facts and policies: [paste] Group questions by the buying decision behind them. Count only the questions I supplied. For each group, give: 1. The question in plain customer language 2. A concise answer supported by the supplied facts 3. Where it belongs: short description, specification, delivery information or FAQ If the answer is missing, write “Owner answer needed”. Do not invent delivery promises or returns terms.
Put the most consequential answer where someone needs it. Package contents belong beside the product; a less common fitting question may work well in an FAQ. A long FAQ at the bottom shouldn’t become a storage cupboard for everything the page forgot to say.
Useful trick: ask for a second output: “Write an 80-word draft reply using our approved answer.” You get a reusable customer-service response as well as better website copy.
4. Help customers choose between similar products
When three products look almost identical, “premium quality” is not a comparison. Give ChatGPT the differences that matter: dimensions, capacity, fit, included accessories and price if it’s relevant.
Help a [type of customer] choose between these products. Product facts, SKUs and current URLs: [paste a table] Main uses customers ask about: [list] Create a compact comparison with no more than five decision criteria. Use the same units throughout, showing any conversion separately. Then write one “Choose this if…” sentence per product. Base each recommendation on a supplied difference. If the facts don't support a recommendation, identify the missing fact. Use only the URLs I supplied. Don't call any product “best overall”.
Use the result in a category introduction or buying guide, with links to the products. Keep it brief enough that someone can reach an actual item without scrolling through a dissertation on your commitment to excellence.
Useful trick: finish with “Which two products are still difficult to distinguish, and what one fact would resolve that?” This often gives you a better question for your supplier than another round of copywriting.
5. Check a product export for missing information
Once you’ve improved a few pages, use a product export to find the next batch. Start with one category so you can review the findings properly.
WooCommerce’s built-in exporter is under Products → All Products → Export. Choose the columns and category you need, then select Generate CSV. Keep identifiers, names, descriptions, category and relevant attribute columns; include Type and Parent when checking variations. WooCommerce’s export instructions and column schema.
Upload that working copy to ChatGPT, or paste a small table if file upload isn’t available. Keep SKUs as text so leading zeros survive. Use product data for this job, not a customer or order export.
Review this WooCommerce product export. Produce a findings table; don't change the file. First report the row count, column names and product types you can read. If any rows couldn't be processed, identify them. Check for missing descriptions, repeated generic descriptions, inconsistent units and contradictions between parent-product copy and variation attributes. For each finding give the exact SKU or ID, column, observed value, issue and suggested next action. Keep identifiers unchanged. Distinguish a blank field from information contradicted elsewhere. A blank variation description is not automatically an error if the parent copy applies. Prioritise ten rows for my review. Don't invent missing specifications or rank products by sales data that isn't in this file.
Check the row count against your spreadsheet and open a few flagged products. An empty export field doesn’t prove the live page lacks the information; your page builder may supply it elsewhere.
Make the first fixes manually. If you later use CSV import for bulk updates, preserve the original export, match existing products using the correct IDs or SKUs, inspect the column mapping and test a small batch on a staging copy. WooCommerce documents that matching identifiers determine which existing products are updated. Import and update guidance.
Small prompting changes that make a difference
Ask for diagnosis before a rewrite. “Show me the three biggest buying questions this page leaves unanswered” gives you a reason to change it.
Show one good example. Include an approved paragraph and say what to copy about its style. OpenAI’s prompting guidance recommends giving the goal, relevant context and intended output, then refining the result with specific follow-ups. OpenAI’s prompting guide.
Make feedback narrow. Try: “Keep the technical facts. Cut the introduction in half. Replace vague benefits with the buying information already in the source.” That’s more useful than “make it better”.
Ask for a change list. “List every factual statement you added or changed, alongside the source supporting it.” Check that list against the original. A second AI pass can help you find an issue; it doesn’t turn an unsupported claim into a fact.
Keep prices and stock in their proper fields. Don’t scatter today’s price or availability through paragraphs that won’t update when the product data changes.
Your first job today
Choose one product that matters to your shop. Gather its current copy, approved specifications and options. Run the contradiction check first, then rewrite the weakest section. Publish the checked improvement and record what changed.
That’s a useful first session with ChatGPT: one clearer product page and a repeatable way to tackle the next one.
Updated 9 September 2026.