Guides

How to sell on ChatGPT without Shopify or Etsy (2026 guide)

ChatGPT shopping is not a marketplace you sign up for. It is an answer engine that recommends whatever it can read and trust. Here is how it sources those answers, the three realistic routes in, and the checklist worth doing this week even if you never touch a product feed.

Updated July 13, 2026 · 10 min read

ChatGPT is now a place where people shop. Salesforce reported that AI influenced $262 billion of 2025 holiday sales, and OpenAI has been steadily building commerce into ChatGPT itself: product results inside answers, an Instant Checkout flow, and a published protocol for merchants who want in. Almost every guide to this assumes you have a Shopify or Etsy catalog. What if you don’t?

Plenty of businesses that could sell through ChatGPT have no product feed at all. Consultants, agencies, studios, clinics, trainers, local service companies. This guide covers how ChatGPT actually sources shopping answers, the three realistic routes in as of mid-2026, and the do-it-today checklist that applies no matter which route you pick.

How ChatGPT sources its shopping answers

There is no dashboard where you buy placement. When someone asks ChatGPT for “a deep-tissue massage near Capitol Hill” or “a branding consultant for a product launch,” the model assembles an answer from two kinds of sources.

• The open web. OpenAI’s OAI-SearchBot crawls and indexes pages for ChatGPT search, and ChatGPT-User fetches pages live when a conversation triggers browsing. If your site blocks these crawlers, or your prices only exist inside JavaScript an agent never executes, you are invisible to this half of the pipeline.
• Structured merchant data. OpenAI and Stripe published the Agentic Commerce Protocol (ACP) as an open spec in September 2025. Merchants, or the platforms they sell on, submit product feeds through it, and that feed data powers rich product results and in-chat checkout.

OpenAI has said shopping results are organic and ranked on relevance, not paid placement. That cuts both ways: you cannot buy your way in, but a small business with clean data genuinely can appear next to much larger competitors.

The March 2026 change matters most for this guide. OpenAI revamped Instant Checkout toward discovery-first: merchants can now surface in shopping results and route buyers to their own checkout, with in-chat checkout as a deeper enrollment tier rather than the price of admission. The bar dropped from “integrate a checkout API” to “publish data agents can read.”

Route 1: ride a platform integration

The launch cohort came in through platforms. OpenAI switched on Instant Checkout in September 2025 with Etsy sellers first and Shopify merchants following, and those platforms handle the feed and checkout plumbing behind what is essentially a toggle. If you already run a Shopify store, this is your answer: meet the eligibility requirements at chatgpt.com/merchants, enroll, done.

The problem is who it leaves out. Platform integrations assume your business is a catalog of SKUs living inside their cart. A fractional CFO, a dog trainer, a wedding photographer, an HVAC company: none of these have a Shopify catalog, and standing one up just to generate a product feed means paying for and maintaining a store you do not otherwise need.

Route 2: build a direct ACP integration

ACP is an open specification, so nothing stops you from integrating directly. That is genuinely good news: there is no gatekeeper, and the documentation is public on OpenAI’s developer site. But go in with clear eyes about the scope. A direct integration means:

1. Publish a product feed in the ACP format and keep it current as prices and availability change.
2. Implement the checkout API: REST endpoints where the agent creates a checkout session, updates it with address and fulfillment choices, and completes it.
3. Handle delegated payments with Stripe’s Shared Payment Tokens, so the buyer’s payment credential reaches you scoped to that single transaction.
4. Wire up order-lifecycle webhooks, verify request signatures, and make every endpoint idempotent so a retried call never double-charges.
5. Test against the sandbox, then apply for enrollment and wait on OpenAI’s review.

For a team with backend engineers this is a real but bounded project. Think weeks rather than days, plus ongoing maintenance as the spec versions. For a business without engineers, it is not a realistic weekend job. We wrote a separate step-by-step for the build path in our ACP enrollment guide, and if you are wondering how this relates to Google’s competing spec, see UCP vs ACP vs MCP. Supporting the second protocol roughly doubles the surface you maintain.

Route 3: use a hosted agent-commerce layer

The third route is the one current search results barely cover: keep the website you have, and let a hosted layer publish your offers in the formats agents consume. It is the same move card acceptance made decades ago. You do not implement the network protocols yourself; you plug into something that already speaks them.

This is what we built Nexez to do. You describe your offers once, or import them from your site, Stripe, or Calendly, and Nexez serves them as structured listings agents can actually use: clean HTML plus JSON-LD, agent.json, llms.txt, an OpenAPI spec, and a per-merchant MCP server listed in the official MCP registry. On the checkout protocols, the ACP and UCP product feeds are live for discovery today, with checkout enrollment in progress. Buyers can already pay through hosted Stripe checkout with you as the merchant of record, including real Calendly-backed scheduling for bookable services.

The honest tradeoffs: you are relying on a layer you do not control, and it costs money past the 7-day trial. Discovery is included on every plan; agentic checkout is a Pro feature (details on the pricing page). What you get for that is hours-to-live instead of weeks, and one catalog feeding every protocol as the landscape keeps shifting.

The three routes compared

Effort estimates assume you have a working website and no existing Shopify or Etsy presence.

Selling services when there is no “product” to feed

Most “get into ChatGPT shopping” advice quietly assumes physical goods. Services differ in ways an agent actually notices: the thing being sold is a slot in a calendar, price often depends on scope, and fulfillment is an appointment rather than a shipment.

None of that excludes services. It changes what your data has to say. An agent acting for a buyer needs a named, priced offer (“90-minute deep-tissue massage, $140”) instead of a menu of vague categories, and it needs availability it can act on rather than a “call to book” line. We cover the mechanics in how AI agents book service businesses.

Location is part of legibility too. Agents cross-check where you actually operate, so a LocalBusiness or Service JSON-LD block with a real address and service area does more work than a paragraph of marketing copy. If that is your situation, the local services use case walks through the specifics.

The do-it-today checklist

Whichever route you take, including “none yet,” these steps make you legible to the crawling half of ChatGPT’s pipeline. All of them fit in a week.

1. Let OpenAI’s crawlers in. Check that robots.txt allows OAI-SearchBot (the crawler behind ChatGPT search citations) and ChatGPT-User (live fetches during conversations). OpenAI documents its bots at platform.openai.com/docs/bots. Blocking GPTBot, the training crawler, is a separate decision that does not remove you from search.
2. Publish real prices. An agent comparing options skips “contact us for pricing.” An offer without a number cannot be ranked, compared, or bought.
3. Add JSON-LD structured data. Product schema for goods; Service plus Offer for services, with price, currency, and availability filled in. This is the same markup Google rewards, so none of it is wasted if agentic shopping grows slower than you hope.
4. Add an llms.txt file, with expectations in check. Ahrefs found no ranking correlation for llms.txt and Google’s guidance says it is not required. It also takes ten minutes, some agent tooling does read it, and writing one forces a plain-language summary of what you sell. Details in what is llms.txt.
5. Give every offer its own page. One URL per service or product, a descriptive H1, and two plain sentences on who it is for and what it costs. Agents cite pages, not paragraphs buried in a homepage carousel.
6. Check your work the way an agent would. Run your site through the free scanner, or fetch your own pages with curl and see whether price, offer, and booking information survives without JavaScript.

How you will know it is working

This channel is measurable, which is more than most new channels can claim. Three signals are worth watching from day one:

• Server logs. Hits from OAI-SearchBot mean OpenAI’s index is looking at you; hits from ChatGPT-User mean real conversations are pulling your pages.
• Referral traffic. Links ChatGPT cites typically arrive tagged with utm_source=chatgpt.com, so one analytics segment shows you the channel’s size and trend.
• Direct questioning. Ask ChatGPT the questions your customers ask, city and niche included, and see whether you are cited. Anecdotal, but it surfaces legibility problems fast.

Set expectations honestly. For most small businesses this is an early, compounding channel, not an overnight one. The reason to move now is that the underlying work, structured offers with real prices on crawlable pages, is cheap, durable, and exactly what every future agent surface will read too.