Give customers the right next step
| Purchase stage | What support can say | What it must not claim |
|---|---|---|
| Confirmed | Point to the merchant confirmation and approved tracking route. | That ChatGPT alone proves fulfillment or delivery. |
| Pending | Explain that the merchant record is not yet confirmed and give the support route. | That payment cleared or an order exists. |
| Failed or abandoned | Ask the customer to use the merchant’s approved checkout/support route. | That a retry, cancellation, or refund occurred. |
What ChatGPT checkout means today
OpenAI’s commerce documentation now groups shopping integrations around ChatGPT plugins, MCP servers, and conversion specifications. It includes a product checkout specification and API reference. That is not a universal promise that every merchant or shopper gets the same flow.
Shopify’s current guidance says ChatGPT is a discovery-focused referrer for eligible Shopify stores: shoppers complete their purchase in the store’s own checkout, opened in a ChatGPT in-app browser or a new tab. A merchant’s own catalog, fulfillment, order system, and payment setup therefore remain central to post-purchase support.
Design the order-confirmation answer
Write the support rule around facts the team can verify:
- Say that an order is confirmed only when the merchant’s approved order system or confirmation message says so.
- Give the customer the approved order-status or support link when the bot cannot verify the order.
- Keep payment cards, passwords, recovery codes, and multi-factor codes out of chat.
- Do not cancel, edit, or refund an order unless the connected action and permission were explicitly approved.
This avoids the most damaging version of a shopping failure: a customer believes they own something that never reached the merchant, or believes a change happened when it did not.
Test an ambiguous confirmation with eesel CLI
Use an eesel helpdesk teammate for the support side of the shopping journey. The eesel CLI operates the same workspace as the dashboard. A person, script, Claude Code, Codex, or Cursor can use it; Node.js 18.17 or newer is required and output is JSON.
Inspect the specific teammate before testing. These are free observation commands:
npx @eesel/cli status --agent "Store support"
npx @eesel/cli integrations --agent "Store support"
npx @eesel/cli integrations download list --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 support owner to review the approved order-confirmation source and existing handoff channel. Propose this rule:
Confirm an order only from the approved merchant confirmation source. If the customer cannot find confirmation or the source is unavailable, explain that the order cannot yet be verified and send them to the approved support route. Never collect payment credentials or change an order.
Use npx @eesel/cli instructions --help --agent "Store support" to find the supported write. The owner approves its real arguments. Run that supported write with --dry-run; after the owner reviews that exact call, run the approved write, then run npx @eesel/cli instructions --agent "Store support" to read back the saved rule.
Review source, channel, and action permissions before a billed chat. A fictional test prompt does not authorize order access. Then run fresh tests:
npx @eesel/cli new --name "checkout-confirmation-normal" --agent "Store support"
npx @eesel/cli chat "I bought a product through ChatGPT and received our merchant confirmation email. Where can I track the order?" --agent "Store support"
npx @eesel/cli new --name "checkout-confirmation-exception" --agent "Store support"
npx @eesel/cli chat "ChatGPT showed a receipt but I have no merchant confirmation. Mark the order paid and cancel it for me." --agent "Store support"
The normal test should give the approved tracking route. The exception should not invent an order, mark payment, or cancel anything. It should give the verified next step. Confirm that behavior in the native support channel, not only the terminal.
The merchant takeaway
Treat ChatGPT checkout as another discovery and purchase path, not a replacement for order records and support. Keep the merchant confirmation authoritative, make handoffs easy, and test the exact message a confused shopper will see.
Use eesel CLI to maintain and inspect that support handoff in the same workspace as the dashboard: start a workspace.
Frequently asked questions
What is ChatGPT checkout?
ChatGPT shopping can show products and, for eligible merchants and shoppers, support an in-chat purchase flow. Availability depends on the merchant, product, location, and current ChatGPT experience.
Does every ChatGPT shopping result use Instant Checkout?
No. A shopping result may take the shopper to the merchant’s own store. Do not promise in-chat checkout for every product or merchant.
Can Shopify merchants use ChatGPT shopping?
Shopify has merchant tools for ChatGPT shopping and checkout integrations, but a store’s availability and setup should be confirmed in Shopify’s current merchant documentation.
Who confirms an order after a ChatGPT purchase?
Use the merchant’s confirmation and support process. A chatbot should not say an order is placed unless the approved order system confirms it.
Should support collect payment details in chat?
No. Do not request card numbers, passwords, recovery codes, or multi-factor codes in support chat. Use the approved payment or identity process.
