---
title: How ChatGPT Shopping Works for Merchants (2026)
description: ChatGPT can show your products from a feed. In-chat Instant Checkout is approved partners, not a switch in Shopify admin. ACP checkout is five endpoints. Catalog gaps still get you skipped.
url: https://www.factualminds.com/blog/chatgpt-shopping-for-merchants-2026/
datePublished: 2026-09-25T00:00:00.000Z
dateModified: 2026-09-25T00:00:00.000Z
author: palaniappan-p
category: AI Agents
tags: ai-agents, ecommerce, agentic-commerce
---

# How ChatGPT Shopping Works for Merchants (2026)

> ChatGPT can show your products from a feed. In-chat Instant Checkout is approved partners, not a switch in Shopify admin. ACP checkout is five endpoints. Catalog gaps still get you skipped.

On **25 September 2026**, ChatGPT shopping is two different projects that vendors keep merging. One is **discovery**: your products show up when someone asks what to buy. The other is **checkout**: an approved merchant completes the order inside the conversation. Most stores are in the first. Almost none should assume the second is a setting.

**Who this is for.** An eCommerce leader or architect deciding what to build for ChatGPT. The protocol comparison is [ACP vs UCP vs MCP](/compare/acp-vs-ucp/). This page is the merchant path for the OpenAI side only.

**Our take:** publish a feed you can defend. Do not staff an ACP checkout build until a partner agreement exists and the catalog survives a comparison.

## What OpenAI actually documents

The [Agentic Commerce Protocol](https://github.com/agentic-commerce-protocol/agentic-commerce-protocol) is maintained by **OpenAI and Stripe** and the repository still marks it **beta**. It was released **29 September 2025** under Apache 2.0.

OpenAI's [checkout spec](https://developers.openai.com/commerce/specs/checkout) says merchants integrate by implementing the Agentic Checkout Spec, and that **Instant Checkout in ChatGPT is currently available to approved partners**. The same spec says the point is to keep orders, payments, and compliance on the merchant's existing stack.

OpenAI's [product discovery note](https://openai.com/index/powering-product-discovery-in-chatgpt/) extends ACP so merchants share product feeds and promotions. It names a Shopify Catalog path: Shopify merchants' product data is already integrated, and OpenAI says no additional feed work is required from those individual merchants. It also says the first Instant Checkout did not give merchants the flexibility OpenAI wanted, so merchants may use **their own checkout** while OpenAI focuses on discovery. ChatGPT apps remain a separate, deeper option (Walmart is the example they give).

Those two pages can both be true. Discovery is the wide door. In-chat complete is a partner program, not a default.

## What the shopper sees versus what you run

| Step | Who owns it |
| --- | --- |
| The question ("a waterproof jacket under $200") | The shopper and ChatGPT |
| Which products are eligible to appear | Your feed or, on Shopify, Shopify Catalog |
| Price, availability, variants | Your catalog, at the moment the feed was built |
| Cart math (tax, shipping, discounts) | Your checkout endpoint, if you are in the partner flow |
| Payment credential | A scoped token on `complete`, not a raw card in the prompt |
| Order record | Your OMS. You are still the merchant |
| "Where is my order" after | Your stack, unless you also send webhook updates |

ChatGPT is not your storefront theme. It will not apply your onsite merchandising rules unless those rules are in the data you publish.

## The five endpoints, if you are approved

The **2026-01-30** checkout OpenAPI says the merchant implements:

- `POST /checkout_sessions` — create, return **201** and a rich cart
- `POST /checkout_sessions/{id}` — update (address, fulfillment)
- `GET /checkout_sessions/{id}` — retrieve
- `POST /checkout_sessions/{id}/complete` — pay and create the order
- `POST /checkout_sessions/{id}/cancel`

Every response is supposed to carry authoritative cart state: items, pricing, tax, shipping, discounts, totals, status. Optional headers worth honoring: `Idempotency-Key`, signature, timestamp, request id. The spec allows `affiliate_attribution` on the agent side. That field is a hint, not an analytics platform. What you can actually report is covered in [agentic commerce attribution](/blog/agentic-commerce-attribution-2026/).

A later spec tree, **2026-04-17**, adds feeds, carts, orders, authentication, and MCP. Pin the version you implement. Do not mix 2026-01-30 payloads with 2026-04-17 assumptions.

## Where this fails

> **What broke** — A team mapped "be in ChatGPT" to a custom app with `write_orders` because a demo needed to place a test order. The feed was never validated. **Detection:** two prices for one SKU, one in the feed and one in checkout, and a token that could refund. **Fix:** delete the admin token, publish one feed, and stop the checkout build until partner status and a price match exist. **Lesson:** discovery does not require order-write scope.

Other misses:

- Variants encoded in the title instead of structured options. The agent cannot tell size from color.
- Inventory without a timestamp. You sell a unit the warehouse already allocated.
- Logging the payment credential beside the order JSON.

The catalog work is [the AI-ready product catalog](/blog/ai-ready-product-catalog-agentic-commerce-2026/). Readiness checks are [shopping-agent readiness](/blog/ai-shopping-agents-ecommerce-readiness-2026/).

## If you only do one thing

Open the product that would embarrass you if an agent quoted it: missing size, stale price, or a description that contradicts the spec table. Fix that record before you talk about endpoints.

## What to do this week

1. Read OpenAI's checkout page and the product-discovery note. Confirm whether you are an approved Instant Checkout partner. If not, do not schedule the five endpoints.
2. If you are on Shopify, audit Shopify Catalog accuracy instead of building a second feed that can drift.
3. If you are not on Shopify, define one feed and a refresh SLA.
4. Compare Google's path in [Gemini shopping for merchants](/blog/google-gemini-shopping-for-merchants-2026/) before you fund both.
5. [Prepare the commerce platform](/contact-us/?focus=ai-agents) with [agentic commerce readiness](/services/agentic-commerce-readiness/) when the catalog is the blocker. The field guide hub is [/resources/ecommerce-ai-agents/](/resources/ecommerce-ai-agents/).

## What this post doesn't cover

- A revenue estimate for ChatGPT referrals. We do not have one.
- Google's Buy button. That is UCP.
- Building an agent that buys on behalf of your company. That is the outbound agent program, not this page.
- PCI redesign. Delegate tokens do not shrink the cardholder environment on your side; they change what the agent is allowed to hold.

## FAQ

### When should a merchant NOT build ACP checkout?
When the catalog attributes an agent compares on are still trapped in description HTML, or when you expected a self-serve Instant Checkout toggle. OpenAI's checkout guide says Instant Checkout is for approved partners. Fix the feed first. A handshake on a thin catalog does not get you recommended.

### What could go wrong if we hand ChatGPT our admin API token?
That is not how ACP works. The merchant hosts checkout endpoints and returns cart state. An admin token lets a model cancel and refund. Do not substitute a store admin credential for the protocol.

### Do Shopify stores need a separate feed?
OpenAI's product-discovery post says Shopify product data already reaches ChatGPT through Shopify Catalog, and that individual Shopify merchants do not do extra feed work for that path. You still own accuracy in Shopify. A second custom feed that disagrees with the catalog is how you publish two prices.

### What could go wrong if we treat a shared payment token like a saved card?
The ACP complete call carries a scoped payment credential for that merchant and that checkout, not a reusable PAN for the agent to store. Re-playing it, or logging it next to the order id in plaintext, is the failure. Idempotency-Key exists so a retry does not create a second order.

### Is MCP the same as ACP?
No. MCP is a tool protocol. ACP is the commerce handshake. See the ACP vs UCP comparison, which now includes MCP as a third layer rather than a third checkout.

---

*Source: https://www.factualminds.com/blog/chatgpt-shopping-for-merchants-2026/*