ChatGPT commerce plugins: guest carts and checkout
What OpenAI’s commerce plugin guide means for retailers: guest carts, checkout handoffs, identity and the current Wallet limitation.
A product feed helps ChatGPT find a retailer’s products. A commerce plugin connects supported shopping actions to the retailer’s backend. They solve different parts of the journey, so an engineering team should identify the missing action before commissioning another integration.
OpenAI’s commerce overview separates discovery through feeds and other sources from transactions through a website browser or plugin. Browser access uses the existing website; a plugin requires more integration work. This is a guide to the documentation checked on 15 November 2026, not a claim that every merchant has gained a new checkout entitlement.
What the plugin must handle
The commerce plugin guide describes an MCP server with skills. It recommends a headless integration: structured tools rather than a merchant iframe. The suggested tool groups cover product lookup, persistent carts, supported checkout and reordering. Their names and schemas are examples, not a mandatory contract.
Discovery and cart operations should work without customer sign-in, and the cart should survive sign-in at checkout. Product lookup should distinguish the selected variant, location-specific availability and eligibility for purchase. Stock alone does not mean checkout is supported.
If a required checkout step cannot finish through the plugin, return a continue_url to the website. The guide recommends preserving the same cart and session; a generic checkout link does not automatically provide that continuity. It also documents mTLS for server authentication without requiring guest shoppers to log in.
Keep identity and purchase approval separate
OpenAI’s Sign in with ChatGPT guide says access is limited to select commercial partners. The merchant verifies the identity and starts its own session; that identity is not purchase approval. Confirm access and account-linking requirements before promising customers this option.
Decide what needs building
Our recommendation is to trace one purchase from product selection to confirmed order. Record where price, stock, customer identity and cart state are checked, and who owns failures at each step. Test an unavailable variant and an interrupted checkout, not just a successful purchase.
Ask a prospective integration supplier to demonstrate those cases against your actual backend. Do not assume that an existing feed, another commerce protocol or a social demonstration establishes compatibility. Compare the work with your current ChatGPT Wallet website checkout before adding another system to maintain.
Industry commentator Juozas Kaziukėnas raised the protocol-overlap question in the original post below. It is commentary, not an OpenAI compatibility guarantee.
Juozas Kaziukėnas on commerce plugins, 15 November 2026
More from AI
See all →
