Answers

Questions DTC operators ask, answered directly and with the source attached. Every page leads with a complete answer before it argues for it — including the ones where the honest answer is that our product is not the point.

Looking for a single term rather than a full answer? The commerce glossary defines each one in a sentence.

Agentic commerce

What is agentic commerce?

Agentic commerce is commerce in which an AI agent completes steps a human shopper used to complete by hand: it reads a goal in natural language, queries merchant catalogs for real-time price and availability, compares options against stated constraints, and — where the merchant supports it — builds a cart and authorizes payment within limits the shopper set. For a merchant it is less a new sales channel than a new class of customer: one that never renders a page, never sees a promotion, and buys strictly on machine-readable data.

ACP vs UCP vs AP2 vs MCP: which agentic commerce protocol matters?

The four protocols named in agentic commerce solve different layers and largely compose rather than compete. MCP (Anthropic) defines how an agent discovers and calls tools. UCP (Google and Shopify) covers catalog discovery and cart construction. ACP (OpenAI and Stripe) specifies product feeds, checkout sessions and delegated payment inside an AI interface. AP2 (Google-initiated, donated to the FIDO Alliance in April 2026) proves cryptographically that a human authorized a given payment. A merchant needs discovery first, payment authorization last.

How do you make an ecommerce store readable by AI shopping agents?

Making a store agent-readable is four pieces of work: server-render product data so price, availability and identifiers exist in raw HTML rather than after client-side rendering; mark it up with schema.org Product including offers, price, priceCurrency, availability and a GTIN or SKU; publish a discovery layer — robots.txt admitting assistant crawlers, a sitemap, and an llms.txt; and expose a programmatic quote and cart endpoint so an agent can obtain a binding price without driving a browser. The first item resolves most of the gap on its own.

What are the latest agentic commerce statistics?

As of Q1 2026, AI-sourced traffic to US retail sites grew 393% year over year, and AI-referred visitors converted 42% better than non-AI traffic in March 2026 — a reversal from March 2025, when they converted 38% worse. Revenue per visit from AI referrals ran 37% above non-AI traffic. Retail product pages score 66% on machine readability, the lowest of any page type. McKinsey projects agentic commerce will mediate $900 billion to $1 trillion in US retail revenue by 2030 and $3–5 trillion globally.

What is MCP and what does it do for ecommerce?

MCP — the Model Context Protocol, published by Anthropic — is an open specification for how an AI agent discovers what tools it can call and then calls them with typed arguments. In ecommerce it is the mechanism by which an assistant learns that your store exposes operations like "search catalog", "create draft order" or "issue refund", and invokes them directly instead of simulating a human clicking through an admin UI. The protocol carries no permission model of its own, so scoping and audit are the merchant platform's responsibility.

Can AI agents actually run an ecommerce store?

Agents reliably handle the read-and-draft half of store operations today: catalog work, merchandising changes, campaign drafting, analytics investigation, support triage and routine customer service. They are not reliable unsupervised on irreversible money movement — ad spend, refunds, price changes on live SKUs, bulk customer messaging. The practical division is not by task difficulty but by reversibility: an agent can be trusted with anything you can undo, and needs an approval gate on anything you cannot.

What tools does a store’s UCP MCP endpoint expose?

Thirteen, on every store we measured: three for catalog (search, lookup, get product), four for carts (create, get, update, cancel), five for checkout (create, get, update, complete, cancel) and one for orders (get order). It is a complete commerce API rather than a checkout bolt-on. Listing the tools requires nothing; calling them requires the agent to present its own resolvable identity, so an anonymous request is refused.

How do I tell whether my store already supports agent checkout?

Request /.well-known/ucp on your storefront domain. A JSON document naming a version and payment handlers means agents can already discover your store; a 404 means they cannot. If the first request succeeds, post a tools/list request to the MCP endpoint that document names to see the commerce tools exposed. Of 147 DTC brands checked in August 2026, 70 answered both — almost always because the platform enabled it, not the merchant.

Does llms.txt actually do anything?

Google has said directly that it does not: John Mueller stated in June 2025 that no AI system currently uses llms.txt, comparing it to the abandoned keywords meta tag. No assistant vendor has documented reading it since, and no controlled test has shown a ranking or citation effect. Adoption is high anyway, mostly because platforms generate the file automatically. Treat it as cheap and unproven rather than as a requirement or a trick.

What is the difference between llms.txt and robots.txt?

robots.txt states which crawlers may fetch which paths; it is a permission file that well-behaved crawlers honour voluntarily. llms.txt offers a summary of what a site is and which URL answers which question; it grants and withholds nothing. Removing robots.txt changes what crawlers are allowed to do. Removing llms.txt changes only what they are handed as a shortcut. Neither file enforces anything — enforcement happens at your edge.

How should an ecommerce store write its llms.txt?

Generate the file from the same data that builds your navigation and sitemaps, so it cannot drift. Open with two or three sentences on what the store sells and who it serves, then list category and key content URLs with a short description each. Keep it small. Before publishing, request the path and read what is already there — replacing a platform-generated file can remove endpoint information you did not know it contained.

How do you get your products to show up in ChatGPT and other AI assistants?

There is no submission form for ChatGPT and no way to buy placement — product results are organic and ranked on relevance. What determines whether an assistant surfaces your product is: structured product data an agent can parse without executing JavaScript, real-time accurate price and availability, brand facts stated consistently everywhere they appear, and third-party presence in reviews, publications and communities. The last factor weighs most and is the one you control least.

Should an ecommerce store block AI crawlers in robots.txt?

Block model-training crawlers if you want to; it costs nothing in search rankings or AI answer visibility. Do not block answer-engine crawlers such as OAI-SearchBot, PerplexityBot and Claude-SearchBot, or live agent fetches like ChatGPT-User — those are what put you in AI answers and bring referral traffic. The distinction matters because around a quarter of ecommerce and B2B SaaS sites block major LLM crawlers unintentionally, often at the CDN rather than in robots.txt.

What is the difference between GPTBot, OAI-SearchBot and ChatGPT-User?

They are three OpenAI agents doing different jobs. GPTBot collects content for model training — blocking it costs nothing in search rankings or AI answer visibility. OAI-SearchBot builds the search index ChatGPT answers from — blocking it removes you from AI answers. ChatGPT-User is a live fetch made on behalf of a specific person asking about you right now — blocking it turns away a customer mid-question. A merchant should block at most the first.

How do you check whether AI crawlers are visiting your site?

Grep your access logs for the user-agent strings of the three crawler classes and count them separately: training crawlers (GPTBot, ClaudeBot, CCBot, Bytespider), answer engines (OAI-SearchBot, PerplexityBot, Claude-SearchBot) and live agent fetches (ChatGPT-User, Perplexity-User). Seeing zero answer-engine hits over a week is the finding that matters — it almost always means a CDN or WAF rule is refusing them before your origin ever logs the request.

Does blocking AI crawlers hurt your Google rankings?

Blocking model-training crawlers such as GPTBot, ClaudeBot and CCBot has no effect on Google Search rankings. Google does not use those crawls; its index comes from Googlebot, a different agent. What blocking can cost you is presence in AI answers, and only if you block the wrong class — answer-engine crawlers like OAI-SearchBot and PerplexityBot. Those two outcomes are frequently conflated, and conflating them is how a training-crawler decision accidentally removes a brand from a growing referral channel.

How do merchants implement UCP and ACP at the same time?

They are not an either-or, and most of the implementation is shared. Both require the same foundation — a machine-readable catalog with product identity, variants, and price and availability that are accurate at read time. UCP then specifies discovery and cart construction; ACP specifies the checkout session and delegated payment inside an AI interface. Build the catalog layer once, and the remaining protocol-specific work is the transaction path, which is also the part still moving.

What is ACP, the Agentic Commerce Protocol?

ACP — the Agentic Commerce Protocol — is a specification published by OpenAI and Stripe covering how merchants expose product feeds and checkout sessions so an AI agent can complete a purchase, including delegating payment processing. Its April 2026 revision spans checkout, payment delegation, cart, feed and authentication, plus a hook letting ACP-aware agents advertise checkout capability through MCP tool discovery. Its practical centre of gravity moved to discovery during 2026 after OpenAI shut down Instant Checkout.

What is UCP, the Universal Commerce Protocol?

UCP — the Universal Commerce Protocol — is an open standard developed by Google and Shopify that lets AI agents read merchant catalogs, retrieve real-time pricing and inventory, manage shopping carts and complete purchases. Its design goal is cross-platform reach: any conformant agent should transact with any participating merchant, rather than each assistant negotiating bilateral integrations with each retailer. For merchants the core obligation is a machine-readable catalog whose price and availability are genuinely current.

What is AP2, the Agent Payments Protocol?

AP2 — the Agent Payments Protocol — uses verifiable digital credentials and cryptographic mandates to prove that a specific human authorized a specific agent-initiated purchase, within limits they set. Announced by Google in September 2025, it addresses the question the commerce protocols leave open: how anyone later establishes that the cardholder actually consented. Google released v0.2 and donated the protocol to the FIDO Alliance on 28 April 2026, moving it out of single-vendor control.

What are the best agentic commerce platforms in 2026?

There is no defensible single ranking of agentic commerce platforms, and nearly every published list places its own author at the top. Four shipped capabilities are what actually separate them: whether product data is machine-readable by default rather than via a plugin, whether an open protocol (UCP, ACP, AP2) is implemented in production rather than on a roadmap, whether agents can perform write operations through scoped credentials with an audit trail, and whether irreversible actions pass a human approval gate. Most platforms ship the first two; far fewer ship the last two.

How do AI assistants decide which products to recommend?

AI assistants rank product recommendations organically rather than through paid placement, weighing four signals: the quality of your structured product data including GTINs and schema markup, consistency of brand information across channels, content that answers shopper questions directly, and third-party authority from reviews, press and community discussion. The constraint most guidance omits is that brand-owned sites account for only 5–10% of the sources AI search draws on — affiliate content, publishers and user-generated content exceed 65% in key categories.

Subscriptions & retention

What should you evaluate when looking for a Recharge alternative?

Evaluating a Recharge alternative comes down to four structural properties rather than features, which converge quickly across serious vendors. Whether stored payment credentials are portable determines whether you can ever leave without asking every subscriber to re-enter a card. Whether dunning branches on issuer decline codes determines how much involuntary churn you recover. Whether subscription state shares a database with orders and inventory determines whether you manage a permanent class of reconciliation bugs. And ownership stability now matters after the April 2026 consolidation.

How do you reduce involuntary churn on a subscription business?

Involuntary churn is recurring revenue lost when a renewal payment fails rather than when a customer chooses to leave. It is reduced by four things in order of impact: honouring the issuer decline code instead of retrying blindly, since a hard decline will never succeed and burns network trust; enrolling cards in account updater services so expiry and reissue are handled before the charge; timing retries against the issuer's replenishment cycle rather than fixed intervals; and pre-dunning outreach before the renewal, not after the failure.

What is dunning in subscription billing?

Dunning is the automated process a subscription business runs after a renewal payment fails: retrying the charge on a schedule, notifying the customer, requesting an updated payment method, and eventually pausing or cancelling if recovery does not succeed. Effective dunning branches on the issuer decline code rather than applying one schedule to every failure, because a hard decline such as a closed account will never succeed on retry while an insufficient-funds decline usually will.

What is the best subscription platform for a DTC brand?

There is no single best subscription platform, but the criteria that predict long-term fit are consistent: whether you own the payment credential or the vendor does, how deeply dunning branches on decline codes, whether subscription state lives in the same system as orders and inventory or is synced across an integration boundary, and what migrating away would cost. Feature checklists converge quickly between vendors; those four structural properties do not, and they determine your options later.

What is a good subscription churn rate for a DTC brand?

Average monthly churn for DTC subscription ecommerce in 2026 runs 6.5% to 8.5%. Below 7% is good and below 5% is top-quartile. Category matters substantially: supplements and consumables run 5–8%, coffee 5–10%, pet 6–10%, meal kits 8–15%, beauty boxes 8–14%. The more useful number is the split — involuntary churn from failed payments is typically 25–40% of the total, and unlike voluntary churn it is a payments-infrastructure problem with a technical fix.

Which subscription metrics should a DTC brand actually track?

The subscription metrics worth a standing report are cohort retention curves, contribution-margin LTV, the voluntary/involuntary churn split, and payment authorization rate. Each one changes a specific decision. The widely-tracked metrics that most often mislead are blended churn, which averages cohorts behaving nothing alike; gross-revenue LTV, which flatters thin-margin subscriptions; and conversion rate, which moves with traffic mix as much as with anything you control.

Platform & migration

Payments & checkout