Distinguish the two purchase journeys
A customer can discover a product in ChatGPT and follow a link to the merchant. Some eligible products and merchants can also have an Instant Checkout option within ChatGPT, according to OpenAI's current shopping help. These are different paths, and a product carousel alone does not establish which one the customer will receive. [1]
The distinction is especially important for platform merchants. Shopify currently says its ChatGPT customers complete purchases at the online-store checkout in an in-app browser or new tab. It also says Shopify admin has no ChatGPT direct-checkout activation setting. A guide that tells every Shopify merchant to switch on Instant Checkout would contradict that documented route. [2]
Use a fictional simple product priced at $29 to compare the journeys. In the referral path, the buyer reaches the store and completes its checkout. In an eligible in-chat path, the supported surface coordinates the purchase through its defined integration. Both need accurate terms, a valid payment and merchant fulfilment. The amount is illustrative, and this guide has not tested a merchant account.
Two ChatGPT shopping paths
Discovery
The surface presents a relevant product and merchant information.
Merchant order
Either route still needs a traceable payment, order and delivery result.
Verify requirements for the actual merchant route
Start with the merchant's platform, product type, seller country, buyer destination, currency and payment integration. Check the current channel documentation and the account's supported configuration. An open checkout specification is not proof that every combination is enabled for public distribution.
OpenAI's shopping help describes eligibility conditionally. It does not establish a complete universal country or merchant-onboarding matrix for every reader's integration. Where your scenario is not answered by the linked documentation, keep that requirement unresolved and obtain current channel-specific evidence. Do not fill the gap with launch announcements or another merchant's experience. [1]
For the documented Shopify ChatGPT path, the platform lists US customers while allowing stores based outside the US, along with Catalog, terms and policy requirements. Those facts apply to that platform route. They should not be copied into a general ACP eligibility table as if every merchant integration had the same conditions. [2]
Requirements to verify, checked October 8, 2026
Scroll the table to compare all columns.
| Question | General ChatGPT shopping | Documented Shopify path |
|---|---|---|
| Purchase location | Merchant link or conditional Instant Checkout | Online-store checkout |
| Eligibility | Specific products and merchants; verify your route | US customers, eligible Catalog products and listed store requirements |
| Activation evidence | Current onboarding/configuration for the merchant route | No ChatGPT direct-checkout switch in the documented admin route |
| Catalog | Accurate relevant product data | Shopify Catalog rules and access configuration |
| Payment | Supported integration and customer authority | Store’s accepted checkout payment methods |
| Post-purchase | Merchant order and delivery operations | Existing store order and support operations |
Prepare current product and policy information
A product offer should identify the actual item, variant and relevant restrictions. If the customer asks for a particular model or license, the merchant must preserve that selection into checkout. A shortened AI display title should not cause an old edition or different variant to become the purchased item.
Keep product information current at the source used by the route. The checkout needs to validate the final amount and availability, because discovery data can be stale. If a price or product term changes materially, the purchase decision should use the current terms and applicable authority rather than a remembered search result.
Provide the store policies required by the actual channel and merchant operation. Make delivery, returns and customer support understandable. Do not generate a universal policy detached from the product, payment method and operator. A customer needs to know what the merchant promises before approving the financial action.
Understand what the checkout contract does
OpenAI's Agentic Checkout specification describes the merchant session lifecycle and order notifications. The merchant returns calculated checkout information and handles supported completion requests. Implement the real schema and operational requirements for the chosen route, with authoritative pricing and order services behind it. [3]
Keep payment processing distinct from the session record. A supported credential permits an attempt under its contract; the provider outcome establishes the financial result. The resulting order should connect the purchased item, applicable authority and verified payment reference. A model's statement that it bought the item is not the evidence the merchant should use to grant access.
After a timeout, retrieve or resolve the existing attempt through the supported contract. Starting a new unrelated purchase immediately can create a duplicate if the original completion succeeded. The merchant needs a durable order that remains inspectable after the conversational interaction is closed.
Design for the buyer’s actual approval
The buyer should understand the item, seller, total and recurring or one-time nature of the purchase. A $35 maximum does not allow a different subscription merely because its first payment costs $29. Changed material terms need the applicable new decision or policy check.
If customer interaction is required by the route or payment provider, preserve that boundary. A pending state with a specific next action is preferable to a fabricated success message. The assistant should not bypass a required challenge or infer permission from a general request to research products.
Keep sensitive payment and account data in the supported handling systems. The merchant's order record generally needs references and outcomes, not raw credentials copied into a conversation log. Collect the information necessary for the purchase and delivery rather than every field from an unrelated sample.
Keep order and support operations ready
The merchant needs to deliver what was purchased and resolve exceptions. A report download, physical shipment or service booking each has its own fulfilment evidence. Do not treat the checkout interface as proof that the customer received the promised output.
Give the buyer a durable order reference and a real support route. If payment succeeds while delivery fails, retain the paid order and recover the failed step. Do not ask the assistant to buy again. If a refund is the appropriate resolution, track the actual provider operation and outcome rather than only a support approval note.
Support also needs to know the checkout location. A customer who arrived through ChatGPT and paid on the website may have a conventional store order with referral attribution. An eligible in-chat route can have different channel records. Describe the actual path so the operator searches the right systems.
Test before making a public availability claim
Check the customer interface for the correct product, current total and supported purchase action. Confirm where checkout finishes and inspect the resulting merchant order. Then test changed price, unavailable product, unresolved payment and delivery failure using safe supported methods.
Record the channel, date, merchant configuration and actual evidence. A documented specification can support a statement about the API; only the observed or explicitly enabled merchant route supports a statement about your customer experience. These are recommended checks, not a claim that this portal tested Instant Checkout for a store.
Avoid general promises such as “all products can now be bought in ChatGPT.” Use wording that matches the actual integration. A referral route is useful on its own terms and should be described accurately. Conditional in-chat checkout should remain conditional until the merchant's applicable channel evidence establishes it.
- Confirm product discovery and the actual checkout location for this merchant.
- Verify current platform, product, seller and buyer eligibility using the applicable source.
- Check the current variant, total, policies and permitted payment action.
- Inspect the merchant order and payment reference after a supported test.
- Exercise changed terms, unavailable product, uncertain payment and failed delivery; keep the original purchase traceable.
- Record date/configuration and distinguish planned checks from observed results.
Monitor the boundaries that can change
Keep current source links and the merchant's onboarding evidence with the integration record. Product discovery, native checkout and payment support can change independently. Recheck material requirements after a channel or platform update, especially if the customer journey changes location or adds a new payment interaction.
Measure stages separately: product exposure, store referral, valid checkout, payment and fulfilment. A rising product-view count does not explain whether the checkout works. A payment count does not establish delivery. The distinction helps the merchant direct work toward the actual blocker.
Use the platform guide for the store-specific path, the ACP guide for the checkout contract and the readiness checklist for unresolved work. ChatGPT Instant Checkout is a route to evaluate with current eligibility and operational evidence. It should not become a blanket label applied to every AI-assisted store visit.