Can ChatGPT sell your WooCommerce products? How ChatGPT Shopping listing works

Yes — ChatGPT can surface your WooCommerce products, and it does it through two separate doors: it crawls your live store with a bot called OAI-SearchBot for organic listings, or you submit a structured product feed through the merchant program at chatgpt.com/merchants. As of mid-2026 the crawl door is open to every store in the world, while the feed door is rolling out to U.S. merchants first — so "can ChatGPT sell my products" has a different answer depending on which door you mean.

Almost every guide we've read describes only the feed door: register as a merchant, add GTINs, install a feed plugin, submit. That path is real, but it skips the fact that the organic door is already live for you today and depends on something the feed can't fix — whether OAI-SearchBot can physically fetch your pages. We build AI-visibility tooling for WordPress, and the failure we see most is a store that does everything the feed checklist says and still never appears, because the crawler gets a 403 before any of it matters.

Can ChatGPT actually sell my WooCommerce products right now?

It can list and link to them right now through organic discovery, and it can take the full purchase inside the chat only if you're in the merchant program. Two different capabilities hide behind the word "sell." The first is showing your product as a recommendation with a price and a link back to your store — that happens through OAI-SearchBot crawling, needs no application, and works globally. The second is Instant Checkout, where the buyer pays without leaving ChatGPT; that runs on the Agentic Commerce Protocol (ACP) and, as of July 2026, is limited to approved U.S. merchants.

So a small WooCommerce store outside the U.S. can absolutely be recommended by ChatGPT this week — it just can't yet complete the sale in-chat. That second door matters less than it used to: OpenAI retreated from in-chat checkout in March 2026 after it converted about three times worse than a click-out, which is why its 4% fee stopped being a decision worth agonising over. The distinction matters because the two doors have completely different requirements, and optimizing for the wrong one is wasted effort.

What are the two ways WooCommerce products get into ChatGPT Shopping?

Organic crawl-based discovery and the merchant feed program — one reads your existing site, the other reads a file you submit. Every WooCommerce store starts with the first and can graduate to the second.

The trap is treating these as sequential steps in one funnel. They aren't. The feed program gives you control and unlocks checkout, but it does not replace the crawl — OpenAI still cross-references what you submit against what it can fetch, and Shopify stores are wired in automatically through Shopify Catalog while WooCommerce is not. That "not" is the whole reason a WooCommerce owner has to think about both doors deliberately. Both read the same underlying product record, which is why getting that record right — the discipline we call feed engineering — pays off no matter which door you walk through.

Why does OAI-SearchBot access decide whether you appear at all?

Because if OAI-SearchBot can't fetch your product page, nothing downstream runs — not organic listing, not the feed cross-check, nothing. OAI-SearchBot is the crawler OpenAI uses specifically for ChatGPT's search and shopping features; it's separate from GPTBot (which is for training) and it does not execute JavaScript. That last point is where WooCommerce stores quietly lose. A price, a variation, or a stock status that your theme injects client-side simply isn't there when the bot reads the raw HTML, so the product record ChatGPT builds is missing the fields that decide a shopping answer.

The blockers are usually invisible from inside your browser: a robots.txt line disallowing the bot, a security plugin or Cloudflare rule challenging non-browser user agents, or a CDN returning a 403 to anything without a JavaScript engine. We've watched stores with immaculate product data stay absent from ChatGPT for weeks over a single WAF rule. This is exactly what Contexta's AI Visibility check tests — it fetches your pages as OAI-SearchBot, GPTBot and PerplexityBot, reports whether each is allowed or blocked at the robots.txt and live-request level, and flags content that only appears after JavaScript runs.

How do you check ChatGPT can actually reach your store?

Fetch one of your product pages the way OAI-SearchBot does — no browser, no JavaScript — and confirm the price, title and availability are present in the returned HTML. A single curl -s -A "OAI-SearchBot" https://yourstore.com/product/... tells you more than any dashboard, because it reproduces exactly what the crawler receives.

Run that check before spending a day on feed formatting. The reachability failures are the same ones that keep AI assistants from citing any page on your site, and they're worth ruling out first — we walked through the full set in why AI assistants never cite your content. If the fetch comes back empty or blocked, no amount of GTIN cleanup will put you in a ChatGPT answer.

What does the ChatGPT merchant feed program actually require?

A product feed with valid unique identifiers, submitted and validated through chatgpt.com/merchants, plus eligibility that as of mid-2026 means a U.S.-based merchant. The concrete requirements are narrower than most write-ups admit: every product needs a GTIN or MPN, the feed should be JSONL (OpenAI's stated preference), and submissions go through a validation pass that typically takes a day or two before products go live.

For WooCommerce specifically, the sticking point is the identifier and the format, not the plugin. WooCommerce added a native GTIN field under Product data → Inventory in a 2024 release, but older catalogs usually left it blank or stuffed the SKU into it — and OpenAI's validator rejects a GTIN that fails its check digit, the same way Google Merchant Center does. A feed generated over incomplete product data validates poorly no matter which feed plugin builds it, which is why the field-level work comes first. Those exact fields — image, price, GTIN, brand, weight, availability — are the ones we broke down in the AI shopping agent data checklist.

What's the difference between being listed and Instant Checkout?

Being listed means ChatGPT recommends your product and links out to your store for the purchase; Instant Checkout means the buyer pays inside ChatGPT and the order lands in your system through the ACP. Listing is the organic outcome and needs only crawlable, well-structured data. Instant Checkout is a commerce integration — OpenAI and Stripe introduced it in September 2025 — and it requires the merchant program plus a supported checkout connection.

For most WooCommerce owners in 2026 the honest sequence is: earn organic listings first, because they're free and available now, then pursue the merchant program and checkout once you're eligible and your data already validates. Instant Checkout is a competing agentic-commerce standard to Google's UCP, and a store can eventually support both; we compared the two protocols and what WooCommerce needs for each in Google's UCP for WooCommerce. Rushing to the checkout layer over an incomplete catalog transacts nothing — the data door has to open first either way.