Connect WooCommerce to ChatGPT, the practical path from catalog to feed

Connect WooCommerce to ChatGPT: the practical path from catalog to feed

Connecting WooCommerce to ChatGPT means exposing your product catalog through a structured feed that OpenAI's shopping surface can read, using the Agentic Commerce Protocol (ACP). It requires a feed with mandatory fields (id, title, description, link, image_link, price, availability, brand, and gtin or identifier_exists), registered through OpenAI's merchant onboarding, then validated before it goes live.

Most WooCommerce stores already have a product catalog that works fine for human shoppers browsing the site. What ChatGPT reads is different: it needs a feed, a structured file with defined fields, not a webpage. A crawler visiting a product page can infer a price from the layout; a feed reader cannot infer anything, it only reads the field it expects in the format it expects. That's the practical gap between having a nice-looking store and having a store that an AI assistant can actually cite in an answer.

Why connecting WooCommerce to ChatGPT matters right now

Shoppers increasingly ask AI assistants directly for product recommendations, and an assistant can only mention products it can read from a structured, machine-readable source.

This is not about replacing your existing SEO work: it's an additional surface. Google Shopping, your own store, and ChatGPT's shopping feed each have separate technical requirements, and being ready for one doesn't mean being ready for the other. A product page that ranks well in classic search can still be completely invisible to an AI assistant if the underlying feed is missing or malformed.

Think of it in layers: the store layer is what a human sees, with photos, layout, reviews and a checkout button; the feed layer is what a machine reads, a flat list of fields with no visual context at all. A product can look perfect on the store layer and still fail completely on the feed layer, because the two layers are built for different readers. This is why a store owner can be surprised the first time a feed submission is rejected: nothing looks wrong on the site itself, but the feed behind it never had the right fields to begin with.

Catalog readiness: what to verify before connecting

Before connecting anything, check that every product has the nine fields ACP requires filled in with real, non-placeholder values.

The fields are: id (a stable unique identifier, usually the SKU), title, description, link (the canonical product URL), image_link, price (with currency), availability (in stock, out of stock, preorder), brand, and either gtin or identifier_exists set to false when no GTIN applies. Missing even one of these on a chunk of the catalog is usually the reason a feed submission gets rejected or partially ignored.

1. Open the WooCommerce Products list and export the catalog to CSV using the built-in exporter, under Products > All Products > Export.
2. Open the export and add a column for each of the nine ACP fields, checking off any product row where a field is empty, generic, or a placeholder value like "N/A".
3. For every product missing a gtin, decide case by case whether one genuinely exists (check the supplier packaging or invoice) or set identifier_exists to false.
4. Compare the price column against the live price shown on each product page, since sales and rounding often create silent mismatches.
5. Check the availability value against WooCommerce's stock status field, making sure it maps to one of the three accepted values, not a custom label.

• Titles that are just a model number, with no descriptive text
• Descriptions copied verbatim from a supplier PDF, including irrelevant boilerplate
• Variants (size, color) sharing the same id, which breaks uniqueness
• Prices without currency, or prices that don't match what's shown on the live page
• Missing brand field on private-label or handmade items

Stores with fewer than fifty products

A small catalog is easier to check by hand, product by product, before generating the feed. It's worth doing this once thoroughly rather than fixing errors after a rejected submission. For example, a shop with thirty candles can go through the exported CSV row by row in under an hour, flagging anything that reads "scented candle" as a title with no brand or size mentioned, and fixing it before the feed is even generated.

Multichannel sellers already listing on Amazon, Etsy or eBay

If you already maintain listings elsewhere, you likely already have most of the required data somewhere, just not in the WooCommerce fields ACP expects. The gap is usually in mapping, not in missing information. A GTIN sitting in an Amazon listing, for instance, often never made it into the WooCommerce product's custom field, so the feed generator sees it as missing even though the data exists somewhere in your systems.

How to connect your WooCommerce catalog to the ChatGPT product feed

There are two practical routes: the Stripe extension for WooCommerce that exposes an ACP feed, or a feed generated separately and submitted to OpenAI's merchant program.

The first route uses the official Stripe for WooCommerce extension, which can expose your catalog in the ACP feed format directly from your store's checkout infrastructure, since ACP is built around Stripe's agentic checkout. If your store already processes payments through Stripe, this is the shortest path: install the extension, confirm the product mapping, and the feed endpoint is generated for you.

1. From the WordPress admin, go to Plugins > Add New and search for "Stripe for WooCommerce".
2. Install and activate the extension, then go to WooCommerce > Settings > Payments > Stripe to confirm your existing Stripe account is connected.
3. Inside the extension's settings panel, locate the ACP Feed section and enable feed generation for your product catalog.
4. Review the field mapping shown on screen, confirming that id, price, and availability pull from the correct WooCommerce product attributes rather than defaults.
5. Copy the generated feed URL shown at the bottom of the panel; this is what you'll paste into OpenAI's merchant onboarding later.

The second route is generating the feed independently, outside of Stripe, and submitting it directly through OpenAI's merchant onboarding. This is the path for stores using a different payment processor, or for sellers who want a feed generated from a catalog audit rather than raw WooCommerce data. A dedicated guide covers this in detail: how to submit the WooCommerce product feed to ChatGPT without errors.

A feed without the nine ACP fields filled in is not invisible to ChatGPT: it's unreadable, the same way a form with blank required fields never submits.

Merchant onboarding, step by step, with the exact menu names

OpenAI's merchant onboarding asks you to register as a seller, submit the feed URL, and confirm ownership of the domain before the feed goes into review.

1. Go to the OpenAI merchant program sign-up and create an account with a business email tied to your store's domain.
2. In the onboarding form, under Store details, enter your store name and the canonical domain (the one that matches your product link field).
3. Under Product feed, paste the feed URL: either the endpoint generated by the Stripe extension, or the URL of your independently hosted feed file.
4. Confirm domain ownership through the verification method offered (usually a DNS TXT record or a file upload).
5. Submit for review. OpenAI checks the feed's structure and a sample of fields before approving it.

Before starting the onboarding form, it helps to have all these pieces ready in one place: the exact canonical domain (with or without "www", matching exactly what's in your link field), the feed URL already tested in a browser to confirm it loads, and access to your domain's DNS settings or hosting file manager for the ownership verification step. Missing the domain verification step, or verifying a different domain than the one used in the product links, is a common reason onboarding stalls partway through.

How to confirm the connection actually worked

Confirmation means checking the feed against the required schema before submission, then verifying the feed status inside the merchant dashboard after review.

Before submitting, run the feed through Katapic's free feed validator. It checks every product row against the nine ACP fields and flags what's missing, without touching your store, so you can fix errors before OpenAI's own review flags them and delays approval.

1. Paste your feed URL into the validator and run the check.
2. Review the report row by row: each flagged product lists the exact field that's missing or malformed.
3. Fix the underlying WooCommerce product data, regenerate the feed, and re-run the validator until the report comes back clean.
4. Only then submit the feed URL in OpenAI's onboarding form, or resubmit it if you already did once and it was rejected.
5. After approval, check the merchant dashboard periodically for a status flag such as "needs attention", which signals that a later catalog change broke a previously valid field.

Common mistakes

Most rejections come from a handful of recurring issues, each with a specific, literal error message, a clear cause, and a straightforward fix.

• "Missing required field: gtin or identifier_exists". Causa: né il GTIN né identifier_exists sono stati impostati sul prodotto. Rimedio: imposta identifier_exists su false in modo esplicito per gli articoli handmade o a marchio privato che non hanno davvero un GTIN, invece di lasciare il campo vuoto.
• "Duplicate id detected". Causa: di solito una variante condivide l'id del prodotto padre. Rimedio: assegna a ogni variante un id proprio, distinto da quello del prodotto padre.
• "image_link unreachable". Causa: l'URL dell'immagine restituisce un 404 o reindirizza altrove. Rimedio: verifica che l'hosting delle immagini non blocchi le richieste esterne e che l'URL punti direttamente al file immagine.
• "price mismatch". Causa: il prezzo nel feed è diverso da quello mostrato sulla pagina prodotto live. Rimedio: rigenera il feed subito dopo ogni modifica di prezzo, specialmente dopo la fine di una promozione.
• "availability value not recognized". Causa: il campo usa un testo libero come "pochi pezzi rimasti" invece di un valore accettato. Rimedio: mappa lo stato dello stock WooCommerce solo su in stock, out of stock o preorder.

What changes after: monitoring citations in AI answers

Once the feed is live, the next task is watching whether your products actually get mentioned when someone asks ChatGPT for a recommendation in your category.

Being technically connected doesn't guarantee a citation; it only makes citation possible. It's worth periodically asking the kind of question a customer would ask, in your own category, and checking whether your store shows up, and which competitors get mentioned instead. This is a monitoring habit, not a one-time check, because feeds go stale and catalogs change.

1. Once a week, ask ChatGPT a natural shopping question in your category, phrased the way a real customer would phrase it.
2. Note whether your store is mentioned, and if not, which competitors are mentioned instead.
3. Cross-check any product mentioned against your live feed to confirm the price and availability shown are still accurate.
4. If a previously cited product stops appearing, check the validator again first, since a stale field is the most common cause.

A feed submitted once and never checked again drifts out of sync with the live store the first time a price or a stock level changes.

Sellers who update prices or stock frequently

If your prices change often (seasonal items, limited drops), the feed needs to reflect that in near real time, otherwise the price mismatch error becomes a recurring problem rather than a one-off fix. For example, a store running a flash sale on Friday and reverting to full price on Monday needs the feed regeneration to happen automatically, not manually, or the mismatch will surface every single week.

Sellers managing a catalog with many handmade or one-off items

Handmade items rarely have a GTIN, and each one is a slightly different id. Getting the identifier_exists field right at scale is the most common friction point for this group. A practical fix is to build the id field from a consistent pattern, such as category code plus a sequential number, so that even one-off pieces get a stable, unique identifier without manual guesswork each time.

Next steps to keep the catalog ready for ChatGPT

Keeping a feed ready for ChatGPT is an ongoing task: check field completeness after every catalog change, re-run the validator before re-submitting, and review a checklist periodically.

A structured checklist helps turn this into a repeatable routine rather than a one-time fix: the WooCommerce feed checklist before sending it to ChatGPT walks through the same fields covered here in a shorter, repeatable format. For a broader view of what AEO readiness means beyond the feed itself, five ways to measure WooCommerce product AEO readiness covers signals that matter even before a feed submission.

How Katapic supports the WooCommerce to ChatGPT connection

Katapic generates a ChatGPT-ready feed from your existing WooCommerce catalog and lets you check it against the required fields before you submit anything.

The free WooCommerce scan reads a public catalog in read-only mode, up to 100 products, without an account, and scores each product on classic search readiness, AI assistant readiness, relevance, and completeness, the field-level gaps that usually cause a feed to fail. The channel readiness view then shows which products are ready specifically for the ChatGPT feed (ACP), alongside Google Shopping, Meta, and your own store, and exports the Google Shopping CSV for Merchant Center for only the products that pass. The free feed validator at the link above catches the same nine-field issues before OpenAI's review does. None of this replaces human judgment on your catalog: Katapic works on the facts you already have, and a rewritten field is never charged unless it actually passes the fact-check gate. You can start from Katapic's homepage with the free scan, no account required.

Frequently asked questions

How do I submit a WooCommerce product feed to ChatGPT?

Generate a feed with the nine ACP fields filled in (id, title, description, link, image_link, price, availability, brand, gtin or identifier_exists), then submit its URL through OpenAI's merchant onboarding, either via the Stripe for WooCommerce extension or an independently hosted feed file, and confirm domain ownership before it goes into review.

Can I use an AI product description generator for WooCommerce before submitting the feed?

You can, but the description field in the feed still needs to match what's shown on the live product page, and it should describe real product facts rather than invented specifications. Any rewriting tool used should preserve the actual attributes you already have, not fabricate new ones.

What's the difference between the WooCommerce OpenAI product feed and a regular Google Shopping feed?

Both share several required fields, but the ChatGPT feed follows the Agentic Commerce Protocol structure tied to OpenAI's merchant program, while Google Shopping feeds follow Google Merchant Center's own specification. A product can be ready for one and not the other if field mapping differs.

Do I need a consultant to connect WooCommerce to ChatGPT, or can I do it with software?

Most of the work is mechanical: filling required fields, validating the feed, and fixing literal error messages. A consultant can help with strategy and edge cases, but the field-by-field readiness check is something a validator tool covers directly; a longer comparison of the two approaches is in consulting or software for your artisan catalog.

How much does WooCommerce SEO consulting typically cost compared to using a feed tool?

Consulting costs vary widely by scope and are usually billed as ongoing retainers, while feed and catalog readiness tools are typically a one-time or per-action cost. A detailed breakdown of what a WooCommerce SEO consulting engagement usually involves is covered in what a WooCommerce SEO consultation really costs.

Why isn't my WooCommerce product feed showing up correctly in ChatGPT?

The most common causes are missing required fields, duplicate ids across product variants, image links that return an error, or a price in the feed that no longer matches the live product page. Running the feed through a validator before resubmission usually surfaces the exact field causing the rejection.

Where can I check if my WooCommerce catalog is ready for AI search before building a feed?

A free, read-only scan can flag missing fields and completeness gaps at the catalog level before you even generate a feed. A list of free tools for this exact check is covered in free tools to check if your catalog is ready for AI search.