Commerce discovery is being rebuilt around AI. Here’s the developer platform built for it.
๐ง๐ต๐ฒ ๐ด๐ผ๐น๐ฑ ๐ฟ๐๐๐ต ๐ณ๐ฟ๐ฎ๐บ๐ถ๐ป๐ด ๐ถ๐ ๐ฟ๐ฒ๐ฎ๐น, ๐ฎ๐ป๐ฑ ๐๐ผ ๐ถ๐ ๐๐ต๐ฒ ๐๐ฎ๐ฟ๐ป๐ถ๐ป๐ด ๐ฎ๐๐๐ฎ๐ฐ๐ต๐ฒ๐ฑ ๐๐ผ ๐ถ๐

PYMNTS published a dedicated “Agentic Commerce Deep Dive” this week as part of its Global Digital Shopping Index series. Salesforce data, cited in a Modern Retail state-of-industry report, attributes 20% of all retail sales and $262 billion in 2025 holiday spend to AI and agent-assisted transactions. Ninety percent of the 80 surveyed brand, retailer, and agency respondents are already using AI to improve shopping experiences; 70% are experimenting with or actively deploying agentic storefronts. HSBC and Visa published a joint initiative to build the payment and trust layer beneath autonomous agent transactions. Lotte Duty Free, one of Asia’s largest duty-free operators, launched what is being reported as Korea’s first ChatGPT-powered shopping service.
The last two years changed how software gets built. Copilot, Codex, and Claude turned the editor into a place where developers assemble from AI capabilities instead of writing every line, and the Model Context Protocol made those capabilities callable by any agent in minutes instead of months.
Commerce discovery is going through the same rebuild, one layer down. Shoppers describe what they want in full sentences, search with images, and increasingly ask AI agents to find products for them. ChatGPT alone handles roughly 50 million shopping queries a day, and AI-referred traffic converts at close to five times the rate of organic search. The keyword box that has run storefronts for twenty years was not designed for any of this.
So the practical question for anyone who builds storefronts is simple: what do you build discovery with now?
๐ง๐ต๐ฒ ๐ด๐ฎ๐ฝ ๐ถ๐ป ๐๐ต๐ฒ ๐บ๐ถ๐ฑ๐ฑ๐น๐ฒ
Today the tooling splits into two ends. At the baseline, Shopify gives every merchant something free but generic: a deliberately narrow set of agent-callable tools, bimodal search, no precise color, no try-on, and it works only inside the platform’s own walls and take rate. At the other end, enterprise vendors like Constructor sell powerful, clickstream-trained discovery sales-led to a hundred or so large accounts, with no self-serve, no free tier, and nothing an AI agent can call on its own. Between the walled floor and the enterprise ceiling sits almost everyone actually building right now: agency developers shipping for merchant clients, product engineers inside retail brands, and mid-market merchants who want discovery richer than the default but adoptable without a six-figure contract. That middle is wide open.
๐ช๐ต๐ฎ๐ ๐ฑ๐ถ๐๐ฐ๐ผ๐๐ฒ๐ฟ๐๐ฃ๐ง ๐ถ๐
discoverGPT is a 360-degree AI discovery platform for commerce, delivered as production REST APIs and 24 MCP tools behind one credential, over one canonical product catalog. Connect a catalog once and every capability below is available immediately, over the same API, against the same data. No stitched-together vendors, no per-product integrations. Four capabilities cover the full discovery loop. (Free-4-Life Tier to the 1st 500 registered devs/agencies. Links in the 1st comment below)
๐๐ด๐ฒ๐ป๐๐ถ๐ฐ ๐ณ๐ฒ๐ฒ๐ฑ๐ ๐ฎ๐ป๐ฑ ๐๐๐ข. Machine-readable discovery feeds (JSON-LD, llms.txt, ACP/UCP) that make a catalog readable to ChatGPT, Gemini, and Google Merchant Center. Visibility tracking then shows how those agents actually see the store, so you can tell what is landing and what is not.
๐ง๐ฟ๐ถ๐บ๐ผ๐ฑ๐ฎ๐น ๐๐ฒ๐ฎ๐ฟ๐ฐ๐ต. Embedded natural language, precise color, and image similarity in one flow, across the whole catalog from 100s to 100,000-plus SKUs. Shoppers describe, show, or point at what they want and find it in seconds instead of scrolling through near-misses.
๐๐ฎ๐๐ฎ ๐พ๐๐ฎ๐น๐ถ๐๐ ๐ฎ๐ป๐ฑ ๐ฒ๐ป๐ฟ๐ถ๐ฐ๐ต๐บ๐ฒ๐ป๐. AI cleans, enriches, and quality-scores product data at the source, repairing bad supplier feeds, missing attributes, and inconsistent titles. It is the foundation the rest of the loop stands on, so garbage in stops being garbage out.
๐ฉ๐ถ๐ฟ๐๐๐ฎ๐น ๐๐ฟ๐-๐ผ๐ป. A “Try it on” button lets a shopper create a form-fitting avatar or generate one from a single selfie, then see themselves in the piece across tops, bottoms, shoes, dresses, and jumpsuits, with their outfits kept session-scoped and never trained on. Live today and apparel-tuned, with on-model catalog photography on the same engine coming next.
๐ ๐๐ฃ-๐ป๐ฎ๐๐ถ๐๐ฒ ๐ฎ๐ป๐ฑ ๐ฝ๐น๐ฎ๐๐ณ๐ผ๐ฟ๐บ-๐ป๐ฒ๐๐๐ฟ๐ฎ๐น
Every capability is exposed two ways: as clean REST endpoints, and as tools over the Model Context Protocol. Point any MCP-aware host, Claude, ChatGPT, Cursor, or a custom agent, at the gateway and it discovers all 24 tools automatically, with the same OAuth credential for both. What you build is not just an app that calls an API. It is a capability an agent can find and use on its own, which is exactly where commerce is heading. And none of it is tied to one stack: catalogs come from Shopify, Salesforce, Magento, BigCommerce, WooCommerce, custom PIMs, or a flat CSV, all mapped into one canonical schema, with a free in-browser column mapper that turns any CSV header set into a suggested mapping automatically. Build once, serve merchants wherever they sell.
๐ข๐ป๐ฒ ๐ฒ๐ป๐ด๐ถ๐ป๐ฒ, ๐ฝ๐ฟ๐ผ๐๐ฒ๐ป ๐ผ๐ป ๐ฎ ๐ฟ๐ฒ๐ฎ๐น ๐๐๐ผ๐ฟ๐ฒ๐ณ๐ฟ๐ผ๐ป๐
One engine sits under all four: one schema, one integration, clean data at the foundation, search on top of it, feeds that carry the same catalog to agents outside the store, and a visual layer over it. This is not an AI wrapper. It is 350k+ lines of AI-native infrastructure code, patent pending on 34 claims, and all four core capabilities run live today on our proof-of-concept merchant, Cassie’s Kurations, a real Shopify store rather than a sandbox. Merchants roll any of it out on their own traffic with built-in A/B testing and can roll back in under two minutes, so their own numbers make the case. We have also packaged the four capabilities as single-click Shopify apps, shopperGPT, cleanerGPT, catalogGPT, and studioGPT, one live in the App Store and three shipping imminently, that agencies can deploy to merchants as-is or use as reference implementations for what discoverGPT makes possible.
๐ง๐ฟ๐ ๐ถ๐: ๐น๐ถ๐๐ฒ ๐ป๐ผ๐ ๐ถ๐ป ๐ฃ๐ฟ๐ฒ๐๐ถ๐ฒ๐
discoverGPT is in Preview, and the Starter tier is ๐ณ๐ฟ๐ฒ๐ฒ ๐ณ๐ผ๐ฟ ๐น๐ถ๐ณ๐ฒ ๐ณ๐ผ๐ฟ ๐๐ต๐ฒ ๐ณ๐ถ๐ฟ๐๐ ๐ฑ๐ฌ๐ฌ ๐ฟ๐ฒ๐ด๐ถ๐๐๐ฒ๐ฟ๐ฒ๐ฑ ๐ฑ๐ฒ๐๐ฒ๐น๐ผ๐ฝ๐ฒ๐ฟ๐: all four capabilities, full REST and MCP access, unlimited stores and seats, no credit card and no trial clock. An API playground with a shared demo catalog lets you make your first call in minutes, before connecting a catalog at all. The developer portal, docs, and playground are live now; the links are in the first comment.
If you are building commerce discovery, for clients, for a brand, or for an agent, the middle ground between the walled baseline and the enterprise ceiling is the most interesting place to build right now.
But alongside every one of those validation signals, a counterweight appeared. TechRadar published a pointed warning: the agentic commerce gold rush risks repeating early ecommerce’s biggest structural mistakes. The early ecommerce era rewarded speed to market and penalized structural integrity – thin product descriptions, inconsistent sizing data, low-resolution images, attribute fields left blank. Those gaps were survivable when the discovery mechanism was a keyword box and a patient human. They are not survivable when the discovery mechanism is an autonomous agent making inferences, ranking options, and transacting on a shopper’s behalf. The agent cannot ask a clarifying question. It works with what it has, or it fails silently.
๐ช๐ต๐ ๐ฏ๐ฒ๐ฎ๐๐๐’๐ ๐๐ ๐ฐ๐ถ๐๐ฎ๐๐ถ๐ผ๐ป ๐ฑ๐ฎ๐๐ฎ ๐ถ๐ ๐๐ต๐ฒ ๐บ๐ผ๐๐ ๐ถ๐บ๐ฝ๐ผ๐ฟ๐๐ฎ๐ป๐ ๐๐๐ฎ๐ ๐ผ๐ณ ๐๐ต๐ฒ ๐๐ฒ๐ฒ๐ธ
Glossy reported this week on data from 5W AI Communications showing that ingredient-transparent beauty brands – The Ordinary, CeraVe, La Roche-Posay – are dominating AI-generated product citations across ChatGPT, Claude, Perplexity, and Google AI Overviews. The Ordinary appeared in 7% of AI beauty responses. Legacy brands like Estee Lauder ranked as low as 18th. NielsenIQ puts beauty-related ChatGPT searches at over 1 billion per week. Fifty-eight percent of Google searches now produce zero clicks to external sites.
This data matters beyond beauty, and beyond citations. What it reveals is the mechanism. Large language models favor brands with detailed, factual, structured product content – ingredient disclosures, dermatologist credentials, precise attribute data. The brands winning AI discoverability did not win it with bigger ad budgets. They won it because their product data was built for machine consumption, not just human browsing. The brands losing were not necessarily worse products. They were products described in marketing language rather than structured data.
Translate that finding to any discovery-heavy retail vertical: apparel fit and fabric attributes, material composition, construction details, occasion and style tagging. A merchant whose catalog reads as a collection of lifestyle headlines rather than structured, attribute-rich product records is invisible to an AI agent trying to match a shopper’s intent. The citation gap in beauty is a preview of the discoverability gap coming everywhere else.
๐ฆ๐ต๐ผ๐ฝ๐ถ๐ณ๐’๐ ๐๐บ๐ฎ๐น๐น-๐บ๐ผ๐ฑ๐ฒ๐น ๐ฏ๐ฒ๐ ๐ฟ๐ฎ๐ถ๐๐ฒ๐ ๐๐ต๐ฒ ๐ณ๐น๐ผ๐ผ๐ฟ, ๐ป๐ผ๐ ๐๐ต๐ฒ ๐ฐ๐ฒ๐ถ๐น๐ถ๐ป๐ด
VentureBeat reported this week that Shopify is leaning into smaller, more efficient AI models deployed across merchant workflows – a strategy aimed at embedding AI deeply without the cost and latency overhead of frontier models. This is a sensible infrastructure choice for a platform operating at Shopify’s scale, and it signals continued investment in native AI capability.
Two things can be true simultaneously. Shopify investing in AI infrastructure raises the baseline expectation for every merchant on the platform – and that is directionally good for the market. Merchants who assumed default storefront tooling was sufficient will find that baseline rising. But Shopify’s native investments have consistently targeted operational efficiency and administrative workflow: fraud detection, inventory forecasting, logistics optimization, merchant analytics. The storefront discovery surface – the place where a shopper is actively trying to find a specific product in a specific color or described by a visual reference they uploaded – is a different and more complex problem than any small-model efficiency play resolves. The search process in Shopify themes remains primarily keyword-driven today. A conversational NLP agent and an optional visual search surface, both on the platform roadmap, do not add up to an integrated, on-storefront engine that handles natural language, precise color matching, and image similarity simultaneously. That combination is not a platform feature yet. It is a product architecture decision that merchants have to make deliberately.
The correct read of Shopify’s AI investment is that it sets a new minimum merchants must clear on their own storefront. It does not clear it for them.
๐ง๐ต๐ฒ ๐ฐ๐ต๐ฎ๐๐ฏ๐ผ๐ ๐ฝ๐ฎ๐ฟ๐ฎ๐ฑ๐ผ๐ : ๐๐ต๐ผ๐ฝ๐ฝ๐ฒ๐ฟ๐ ๐๐ฟ๐๐๐ ๐๐ต๐ถ๐ฟ๐ฑ-๐ฝ๐ฎ๐ฟ๐๐ ๐๐ ๐บ๐ผ๐ฟ๐ฒ, ๐ฏ๐๐ ๐ฐ๐น๐ผ๐๐ฒ ๐ผ๐ป ๐๐ต๐ฒ ๐บ๐ฒ๐ฟ๐ฐ๐ต๐ฎ๐ป๐’๐ ๐๐๐ผ๐ฟ๐ฒ๐ณ๐ฟ๐ผ๐ป๐
A Gartner survey of over 3,500 B2C and B2B customers, reported by Retail Dive this week, found shoppers are three times more likely to use a third-party generative AI tool such as ChatGPT or Claude than a brand-owned chatbot for assistance. Third-party AI usage has doubled year-over-year; brand chatbot adoption has flatlined since 2022. Two-thirds of consumers now use generative AI in their personal or professional lives.
This finding is sometimes misread as evidence that on-site, merchant-deployed AI is losing relevance. The conclusion does not follow. Shoppers trust the AI interfaces they already use habitually for the exploratory and advisory phase. That is where they build intent and shortlist options. The transaction still completes on the merchant’s storefront. That is where price, margin, inventory, and customer relationship live. The merchant’s on-storefront discovery layer is not competing with ChatGPT for the shopper’s attention – it is the place the shopper arrives after ChatGPT has pointed them in a direction. When they arrive, the on-site experience either confirms and converts the intent or bleeds it out through poor search results, missing product attributes, and a catalog that cannot respond to the way the shopper is now describing what they want.
The off-site and on-site layers are complementary surfaces of a single discovery journey, not rival architectures. The merchants positioned well for both are the ones investing in catalog structure and on-storefront intelligence simultaneously – not choosing one over the other.
๐ฆ๐ผ ๐๐ต๐ฎ๐ ๐ถ๐ ๐๐ต๐ฒ ๐ฎ๐ฐ๐๐๐ฎ๐น ๐ฑ๐ฒ๐ฐ๐ถ๐๐ถ๐ผ๐ป ๐บ๐ฒ๐ฟ๐ฐ๐ต๐ฎ๐ป๐๐ ๐ป๐ฒ๐ฒ๐ฑ ๐๐ผ ๐บ๐ฎ๐ธ๐ฒ ๐ฟ๐ถ๐ด๐ต๐ ๐ป๐ผ๐?
The week’s signal, read as a single argument, points to one decision that separates merchants building durable agentic commerce positions from those building fragile ones. It is not a decision about which agent interface to deploy or which platform feature to enable. It is a decision about catalog architecture.
Agents – whether they live in ChatGPT, in a Visa-HSBC payment rail, in Lotte Duty Free’s conversational layer, or on a merchant’s own storefront – are only as useful as the product data they are reasoning over. The beauty citation data shows exactly what structured catalog investment produces in terms of AI discoverability. The TechRadar warning shows exactly what happens when merchants skip that investment and go straight to deploying agentic interfaces on top of thin, inconsistent, marketing-language product records.
The question I would put to any merchant or commerce operator reading this: if an AI agent right now tried to answer the query “show me a relaxed-fit linen shirt in mint green under $80, suitable for a beach wedding” using only your current catalog data – no human curation, no keyword matching, pure structured attribute inference – how many of your qualifying products would it actually surface? And how many would it miss because the color is labeled “light green” in one record, “sea-foam” in another, and left blank in a third?
That gap is the decision. The channel architecture comes after.