Originally published at forgemesh.io.
Sixty billion is an attention-grabbing number. The useful question is what a shopper can do with the products an assistant finds. Google already has a vast product catalog. A reported Flipkart pilot in India gives us a smaller, more concrete development to examine: checkout inside the AI interface.
The big number has a date attached
Google said its Shopping Graph contained over 60 billion product listings on May 19, 2026. That is a company-reported catalog measure, and it was public months before this week’s discussion. Read Google’s announcement.
Listings should not be read as distinct products, completed orders or products available for agent checkout. A catalog count alone cannot tell a merchant how often an assistant recommends its inventory, or whether the shopper can complete a purchase there.
| 60B+ | product listings reported by Google in May 2026 |
| Limited test | Flipkart checkout in India, according to reporting |
The fresh signal is a checkout pilot in India
TechCrunch reporting, also syndicated by Yahoo, describes a limited test in which selected Flipkart listings show a Buy button in Gemini and Google’s AI Mode in India. It opens a Flipkart-branded checkout within the AI interface. The reported scope includes selected users and products such as smartphones, electronics and accessories.
That is a useful development to follow. It brings the step after a recommendation into the same interface. We have not run a purchase through this pilot ourselves. The reporting should not be treated as proof of general availability, unattended purchasing or adoption across the whole Shopping Graph.
Read the stack one layer at a time
Google’s broader commerce plan gives this context. Its January UCP announcement describes a common protocol for commerce interactions and checkout on eligible listings. Flipkart appears among its endorsers. Google separately describes AP2 as a way to bind delegated payments to authorization and spending limits in its May announcement.
Those announcements explain the direction. They do not establish the implementation of this particular India pilot. We have not verified that the Flipkart flow uses UCP or AP2, and the evidence reviewed here does not connect it to Base or x402.
For an agent builder, keep three questions separate: Can the assistant find the offer? Can it start a supported checkout for that offer and region? Can it complete an authorized purchase and produce an order record? A large answer to the first question leaves the other two open.
Why this belongs on a builder’s radar
Our read: Google’s advantage is the opportunity to connect product discovery with a supported purchase path in interfaces shoppers already use. The limited pilot matters because it tests that connection with a merchant. The catalog number provides the scale of the discovery side.
For a merchant, visibility is only the first checkpoint. Price, stock, shipping coverage and variant selection need to stay correct through checkout. An assistant recommending the right shoe still has to order the right size and deliver it to the right place.
For a builder, measure the steps separately. Count recommendations, eligible checkout starts, authorized orders and failed handoffs. If a user must leave the assistant to finish, record that too. This is our suggested testing approach, not a claim about results from Google’s pilot.
A practical test for your own storefront
Pick one product and one target region. Check whether the assistant finds the exact variant at the current price. Follow the supported checkout path with an authorized tester. Confirm the final total, shipping destination, consent step and order record. Then check how cancellation or a return is handled.
Keep a dated record of which account and region were eligible. A screenshot of a Buy button is evidence of a checkout entry point; a confirmed order and receipt are evidence of a completed purchase. Measure both.
We will be watching for documented rollout scope, merchant integration instructions and evidence of completed purchases. Those are the next facts that would change a builder’s decision. The 60 billion figure earns attention. A working purchase path earns a test.
Follow the parts that actually change. The ForgeMesh Brief follows agent commerce from discovery through payment. Get the next Brief.
Top comments (0)