Juspay Breeze Universal puts your catalog in ChatGPT

Juspay launched Breeze Universal, a global pilot that makes a merchant's existing product catalog discoverable inside AI assistants, Finextra reported on September 2. It connects to Shopify, WooCommerce, Magento and custom stores, then exposes that catalog across ChatGPT, Claude, and merchants' own first-party surfaces. The agentic commerce plumbing is arriving as a vendor integration, which is the part worth reading carefully.

What actually happened

Breeze Universal is built on Google's Universal Commerce Protocol. Shoppers type @breeze inside ChatGPT and get cross-brand product recommendations without leaving the chat. Brands can also publish their own @brand app inside ChatGPT, published by Breeze, plus an AI-powered storefront with a single search bar over the whole catalog. Delivery comes three ways: drop-in components, a headless kit, or APIs.

UCP itself is the more durable fact here. Per Google's merchant documentation, the retailer stays Merchant of Record on UCP transactions and keeps the customer data and the customer relationship. Payment is tokenized, and every authorization carries cryptographic proof of user consent — an audit trail, not a handshake. UCP-powered checkout is live for eligible U.S. merchants with global expansion planned through 2026.

Why agentic commerce discovery matters for your business

Strip the branding and this is a syndication decision, the same one you made about Google Shopping feeds a decade ago. Something reads your catalog and shows it somewhere you do not control. The questions have not changed.

Who owns the feed? If a vendor normalizes your catalog into their schema and pushes it to three AI surfaces, switching vendors means rebuilding that mapping. Keep a clean, complete product feed you generate yourself — titles, attributes, availability, price, canonical URL — and hand vendors a copy. Do not let their transform become the only place your structured data exists.

What do you learn? Discovery inside someone else's chat window gives you far less signal than a session on your own site. Insist on order-level attribution back to the surface, or you are optimizing blind.

What breaks at 2 a.m.? An agent quoting a price you changed an hour ago is a chargeback and a bad review. Sync latency is the real integration risk, not the API surface.

We build catalogs that stay portable — one source of truth, feeds generated from it, vendors downstream. That way the next protocol is a new export, not a migration.

Sources: Finextra, Google Merchant Center Help.