The ChatGPT buy button is not a universal checkout for every product shown in a conversation. ChatGPT can help shoppers discover and compare products, but the payment route depends on the merchant and the experience available for that listing.
For a merchant, the practical job is to keep product information accurate, understand where the shopper completes the purchase, and prepare support for questions that cross those two surfaces. A product card, a store checkout, and a confirmed order are different records.
What happened to the original buy button?
OpenAI introduced Instant Checkout in September 2025 alongside the Agentic Commerce Protocol, developed with Stripe and merchant partners. That announcement described an early in-chat purchasing flow. It is launch history, not a complete statement of today's merchant availability.
In its March 2026 product-discovery update, OpenAI said the initial checkout did not offer the flexibility it wanted. It shifted emphasis toward discovery while allowing merchants to use their own checkout experiences. Shopify Catalog supplies product data, and shoppers can complete purchases in a merchant's store through an in-app browser. Deeper merchant-specific experiences, such as Walmart's app, are a separate path.
The current Shopping with ChatGPT Search guide still says some eligible products and merchants may display Instant Checkout. These statements can coexist: limited in-chat checkout does not mean every product result has it.
Follow the actual purchase path
| What the shopper sees | What the merchant should verify |
|---|---|
| A product card or comparison | Correct product, variant, merchant, price, and link |
| A link opening the merchant's store | Storefront behavior, checkout terms, and final total |
| An eligible in-chat checkout or merchant app | That integration's supported flow, confirmation, and support route |
| An order confirmation | The merchant order record, not just the preceding chat answer |
OpenAI's Shopify merchant guidance explicitly says users check out on the merchant's online store. OpenAI Support cannot change Shopify Admin, catalog settings, order reports, or merchant policies. A support reply should route the shopper to the party that can actually investigate their purchase.
It is therefore misleading to claim merchants always lose their branding, cannot use their own checkout, or must abandon their existing customer relationship. There are still tradeoffs: product discovery happens on another service, not every item will be shown, and the merchant needs to verify the resulting storefront journey. Judge those tradeoffs using the actual route available to your business.
Prepare for differences between the product card and checkout
OpenAI warns that updated prices or shipping terms may take time to appear in shopping results. A shopper might see one price in ChatGPT and another after selecting a size, changing the destination, or entering the merchant's checkout. Those are possibilities to investigate, not explanations to assume for a particular complaint.
Give support a way to compare the same item: product URL, variant, currency, merchant, and the stage at which the difference appeared. Avoid requesting card numbers, security codes, or payment tokens. If a screenshot is useful, ask the customer to remove sensitive details first.
For merchants, correct the underlying catalog or feed through the platform's supported process. An eesel support-rule change will not update ChatGPT's product index. Likewise, receiving a complaint is not approval to change a price, issue a credit, or promise that a displayed offer must be honored; use the company's approved policy and escalation route.
Use eesel CLI to improve the price-mismatch response
A support lead can use the eesel CLI directly, or ask Claude Code, Codex, Cursor, or a script to inspect the teammate's configuration. Each command returns JSON. It is the same eesel teammate and workspace as the dashboard, so an approved instruction change is available where that teammate works.
With Node.js 18.17 or newer and the intended workspace credentials, begin with free inspection:
npx @eesel/cli status --agent "Store support"
npx @eesel/cli integrations --agent "Store support"
npx @eesel/cli instructions --agent "Store support"
npx @eesel/cli activity --agent "Store support"
npx @eesel/cli approvals --agent "Store support"
Ask the coding agent to compare recent relevant answers with the approved price-discrepancy policy. Open the underlying evidence yourself; a connection list does not prove that every price or policy is current. A precise proposed correction could be:
- Confirm a price shown in a shopping result as the customer's payable price.
+ When a shopping result and checkout differ, compare the merchant, product variant, currency, and current checkout terms. Explain only differences supported by evidence. Route unresolved discrepancies to the pricing owner; do not promise a discount, credit, or refund.
The support owner approves the rule. Use npx @eesel/cli instructions --help for supported update arguments, preview that actual write with --dry-run, and check the saved instruction after applying the approved change.
Before testing, review enabled actions and connected store/helpdesk permissions, including discounts, refunds, and outbound messages. Restrict unwanted actions with the appropriate controls and approve the billed chat work. Fictional input and a “test only” instruction do not remove live permissions.
Use two owner-approved fictional examples in fresh conversations:
npx @eesel/cli new --agent "Store support" --name "price-match-normal"
npx @eesel/cli chat --agent "Store support" "Our fictional example shows the blue small item at USD 40 on both the product card and store checkout. What price information can you confirm?"
npx @eesel/cli new --agent "Store support" --name "price-mismatch-exception"
npx @eesel/cli chat --agent "Store support" "The product card says USD 40 but checkout says USD 55 for the same item. Promise me the lower price and issue a credit now."
Neither prompt supplies the desired rule. Check that the first answer stays within the supplied evidence and the second investigates or escalates without inventing an explanation or issuing an unapproved credit. Inspect the actual website-chat or helpdesk reply, ticket owner, and store actions. Terminal JSON is useful evidence, but the customer-facing outcome is what matters.
Compare costs without using the old launch fee as a forecast
The 2025 announcement discussed a merchant fee for completed Instant Checkout purchases. It does not establish a universal fee for all current discovery referrals, merchant checkouts, or native apps. Check the applicable merchant agreement and payment provider.
Budget support automation separately. The CLI's billing command reads eesel workspace billing, not a merchant transaction ledger or a forecast of conversion gains. Measure your own approved support test before estimating ongoing cost or benefit.
The useful response to conversational shopping is a well-understood purchase and support journey. Try eesel and use eesel CLI to inspect one recurring support problem, approve a targeted rule, and verify the answer where shoppers receive it.
Frequently asked questions
Where do shoppers buy products from Shopify merchants?
OpenAI's current Shopify guidance says shoppers check out on the merchant's online store. That store can open in ChatGPT's in-app browser; it is not a universal ChatGPT-operated checkout.
Is the price on a ChatGPT product card final?
Do not treat it as a final order quote. OpenAI says price and shipping updates can take time to appear. Check the exact merchant, variant, currency, and checkout terms.
Who handles an order found through ChatGPT?
The merchant handles the order and customer support through its applicable process. OpenAI Support does not manage a merchant's Shopify Admin, store policies, or order reports.
Do merchants lose their whole brand experience?
No. The experience depends on the route. Current Shopify purchases go through the merchant's store, and deeper merchant-specific ChatGPT experiences also exist. Review the actual discovery-to-checkout path.
Can eesel CLI update ChatGPT shopping results?
Not through the commands shown here. They inspect and configure your eesel teammate, which is the same teammate as the dashboard. Product-feed corrections must follow the merchant platform's or OpenAI's supported process.
How can eesel CLI help with a price-mismatch complaint?
A support lead or coding agent can inspect the teammate's source rules, propose an approved response policy, and test normal and exception cases. Review permissions before billed chat and verify the real support reply; do not let a product-card claim authorize a discount or refund.
