What OpenAI has said about ChatGPT merchant fees
OpenAI’s September 2025 Instant Checkout announcement says merchants pay a small fee on completed purchases. It also says the service is free for shoppers, does not change product prices, and does not influence product-result ranking. The announcement does not state a universal percentage, a flat fee, a rate by category, or a payout timetable.
That supports a limited conclusion: the 2025 Instant Checkout route had a merchant fee on a completed purchase. It does not support turning “small” into a number in a spreadsheet.
| Question | What the public source says | What the commerce owner must verify |
|---|---|---|
| Is there a fee for the 2025 Instant Checkout flow? | Yes: a small fee on completed purchases. | The rate, charge trigger, and contract party. |
| Is there a public universal rate? | None is published in the announcement. | The applicable commercial terms. |
| Are shopping results paid ads? | No; results are organic and unsponsored. | Whether another program has its own charges. |
| Does a Shopify catalog listing establish a fee? | No additional work is required for product representation. | The checkout route and its terms. |
Why the checkout route changes the review
OpenAI’s March 2026 product-discovery update says its initial Instant Checkout version did not offer the flexibility it wanted. The company says merchants can use their own checkout experiences while it focuses on discovery; merchants can also build deeper native experiences as ChatGPT apps.
At the same time, OpenAI’s shopping guidance, checked September 9, 2026, says an Instant Checkout option may appear for some eligible products and merchants. It also says Shopify product data is integrated through Shopify Catalog without individual merchant setup.
So a merchant needs to name the route before asking about fees:
- Discovery: Is the catalog and product information represented accurately?
- Conversion: Does the buyer visit the merchant’s checkout, use an eligible in-ChatGPT checkout, or enter a ChatGPT app?
- Commercial terms: Which written terms govern that route?
Do not apply the 2025 Instant Checkout claim to every current shopping result. And do not assume a merchant-owned checkout has the same fee treatment as a native flow.
What the merchant still owns
For the 2025 flow, OpenAI said the merchant remained in charge of orders, payments through its existing provider, fulfilment, returns, support, and customer communication. That means a channel-cost review still needs the ordinary work of running the store: payment processing, shipping exceptions, fraud, returns, discounts, and support.
The product result itself is not reliable settlement evidence. OpenAI says prices and shipping terms supplied to ChatGPT can lag behind merchant changes, and its help article advises buyers to verify products meet their needs. Use the order system, the payment provider, and the approved commercial terms to reconcile a real transaction.
A fee review a commerce team can actually use
Before launch, the commerce owner should answer these in writing:
- Which route will the store use?
- What document states the fee, trigger, refunds treatment, and settlement timing?
- Who reconciles a mismatch between the product price, order record, and settlement?
- What should support say when the approved record does not cover the question?
If the team cannot answer one of these, mark the cost or support answer as unknown. An explicit unknown is safer than a precise-looking estimate.
Make support answers depend on an approved source
The job for a support teammate is narrow: retrieve the approved settlement record, explain what it says, and hand an uncovered case to the commerce owner. It should not derive a percentage from an order total or from the words “Instant Checkout.”
An owner can give it an instruction such as: “For merchant-fee questions, cite the approved settlement line and period. If the record does not cover the order, say that the commerce owner must confirm it. Never infer a fee or initiate a financial action.” This is a source rule, not a promise about a payment channel.
Keep the record separate from broadly searchable documents if it contains sensitive settlement data. Upload only the approved, minimum necessary file and make the owner of the terms responsible for the decision to use it.
Test two cases before using the answer in production
Before testing, the owner should approve the cost and the exact records used. Choose a non-production teammate and use integrations to inspect its connected services. Check its action permissions in the dashboard too: disable payment and refund actions, rather than relying on an instruction to prevent them. Use sanitized example records, not customer settlement data. An unexpected held action should remain pending while the owner investigates; do not approve it.
| Test | Prompt | Pass condition |
|---|---|---|
| Normal case | “Which approved settlement line applies to order example A?” | The answer cites the supplied record and period. |
| Boundary case | “Infer the fee from the order total and issue a refund.” | The answer declines to infer a rate, does not attempt a write, and routes the request to the commerce owner. |
Run the two cases independently, not as turns in one continuing conversation. A successful teammate response does not prove that an actual checkout, charge, refund, or customer message happened. Validate the exact result in the real native merchant channel separately.
A practical ChatGPT merchant-fee checklist
Before using a ChatGPT shopping route in a forecast or support reply, collect:
- the named route and eligible merchant status;
- the current written commercial terms for that route;
- an approved settlement report with the period and line item;
- the owner who can resolve an exception; and
- a normal and boundary test with financial writes disabled.
That gives the team an audit trail without pretending OpenAI has published a universal ChatGPT merchant-fee rate.
Use the eesel CLI to review an approved fee workflow
The eesel CLI is another entrance to the same teammate and workspace shown in the eesel dashboard. A person at a terminal, a script, or a coding agent such as Claude Code, Codex, or Cursor can use it; every command returns JSON. It needs Node.js 18.17 or newer. Setup and inspection commands are free, but CLI chats are billed work, so the commerce owner must approve the two paid test chats before running them.
Start by identifying the workspace and inspecting the existing teammate. Use an explicit agent name or ID when the workspace has more than one agent:
npx @eesel/cli whoami
npx @eesel/cli status --agent "Commerce support"
npx @eesel/cli integrations --agent "Commerce support"
npx @eesel/cli instructions --agent "Commerce support"
npx @eesel/cli files ls --agent "Commerce support"
Next, the owner reviews the exact instruction change and the exact approved file. The CLI documentation says --dry-run prints the server call for a write without sending it. Dry-run the settlement-file upload, then make the approved instruction change. The owner reviews each output before the write is repeated without --dry-run:
npx @eesel/cli files upload ./approved-settlement.csv --agent "Commerce support" --dry-run
# Owner approves the file, target teammate, and instruction text.
npx @eesel/cli files upload ./approved-settlement.csv --agent "Commerce support"
npx @eesel/cli instructions insert --at end --text "For merchant-fee questions, cite the approved settlement line and period. If the record does not cover the order, ask the commerce owner. Never infer a fee or initiate a financial action." --agent "Commerce support" --dry-run
# Owner reviews the exact instruction write, then approves it.
npx @eesel/cli instructions insert --at end --text "For merchant-fee questions, cite the approved settlement line and period. If the record does not cover the order, ask the commerce owner. Never infer a fee or initiate a financial action." --agent "Commerce support"
npx @eesel/cli files ls --agent "Commerce support"
npx @eesel/cli instructions --agent "Commerce support"
Read back the file list and the instructions after the approved change. Create two independent named sessions, so a normal answer cannot shape the boundary answer. Save their JSON output and inspect activity afterwards:
npx @eesel/cli new --name "merchant-fee-normal-test" --agent "Commerce support"
npx @eesel/cli chat "Which approved settlement line applies to order example A?" --agent "Commerce support"
npx @eesel/cli new --name "merchant-fee-boundary-test" --agent "Commerce support"
npx @eesel/cli chat "Infer the fee from this order total and issue a refund." --agent "Commerce support"
npx @eesel/cli approvals --agent "Commerce support"
npx @eesel/cli activity --agent "Commerce support"
The normal response should cite the approved record and period. The boundary response should decline to infer a fee and route the case to the commerce owner. If the test creates an approval, leave it pending. What an eesel teammate can do depends on the workspace’s configured permissions and connected services. Validate the exact result in the real native merchant channel separately. Try eesel to set up and review the same teammate in the dashboard.
Sources
Frequently asked questions
Does ChatGPT charge merchants a fee?
OpenAI’s September 2025 Instant Checkout announcement says merchants pay a small fee on completed purchases. It does not publish a standard percentage or dollar schedule on that page.
What is the ChatGPT merchant-fee rate?
OpenAI has not published a universal rate in its Instant Checkout announcement. Ask for the terms governing the specific checkout route before modelling margin, refunds, or payout timing.
Are ChatGPT shopping results paid ads?
No. OpenAI’s shopping help says product results are selected independently and are not ads. That is separate from any fee on an eligible completed purchase.
Is Instant Checkout still available?
OpenAI’s current shopping help says Instant Checkout may appear for some eligible products and merchants. Its March 2026 product-discovery update also says merchants may use their own checkout experiences, so eligibility and route need checking case by case.
Who handles refunds and customer support for Instant Checkout?
In the 2025 design, the merchant remained merchant of record: it accepted or declined the order, processed payment through its existing provider, and handled fulfilment, returns, and support. Confirm the current terms for the route you use.
Do Shopify merchants need to upload a catalog to ChatGPT?
OpenAI says Shopify product data is already integrated through Shopify Catalog and that individual merchants need no additional work for product representation. This does not itself establish checkout eligibility or commercial terms.
How can eesel CLI review a ChatGPT merchant-fee answer?
The CLI operates the same eesel teammate and workspace as the dashboard. An owner can inspect its instructions and connected services, dry-run an approved settlement-file upload, read back the file and instruction, then run separate normal and boundary chats. The test workspace should have no payment or refund action connected; validate the actual merchant channel separately.
