Google is testing a shopping experience in India that moves Gemini and AI Mode closer to completing a purchase rather than simply helping someone find a product. In the limited experiment, selected Flipkart listings can show a Buy button inside Google’s AI interfaces and take the shopper into a Flipkart checkout flow.
From product discovery to transaction
Search engines have spent years helping people compare products, prices and merchants. The next step is to let an AI assistant perform more of the transaction itself. Google’s Flipkart test is an example of that shift because the assistant is no longer stopping at a product recommendation. A shopper can move from an AI-generated result into a purchase path without first returning to a conventional search-results page.
The initial test is deliberately limited. It covers selected users and a relatively small group of products, including smartphones, electronics and mobile accessories. That makes the experiment less about immediate scale and more about testing whether people are comfortable allowing an AI interface to sit between them and an online retailer.
The checkout flow also matters. The current experiment appears to take shoppers to a Flipkart-branded checkout experience rather than forcing every transaction through a Google-hosted payment page. That suggests Google is testing more than one technical model for agentic commerce.
Why India is an important test market
India is a large mobile-commerce market with strong usage of both Google services and Flipkart. That combination gives Google a useful environment for testing AI-assisted shopping before expanding the feature to other regions.
The timing is also connected to the country’s major festive shopping period. A shopping assistant that can identify products and then help complete transactions could become more useful during a period when consumers are already searching for phones, electronics and household products.
Google also has an existing financial relationship with Flipkart. The company invested in the e-commerce business as part of a funding round, giving the two companies a relationship that goes beyond a simple merchant integration.
The Universal Commerce Protocol connection
Google has separately been developing the Universal Commerce Protocol, an open standard intended to let AI systems interact with retailers throughout a shopping journey. The broader objective is to make product discovery, inventory information and checkout accessible to agents in a consistent way.
That infrastructure becomes important if AI shopping moves beyond one company’s assistant. A useful agent should eventually be able to compare retailers, understand availability, apply relevant purchasing constraints and complete a transaction without every merchant building a completely different integration.
The Flipkart experiment shows why the details matter. Even when the user begins inside Gemini, the final transaction may still happen through a retailer’s own checkout. The boundaries between assistant, search engine, marketplace and merchant are becoming less clear.
The hard part is trust
An AI assistant recommending a product is relatively low risk. An AI assistant purchasing the product is different. A mistaken recommendation can waste a few minutes. A mistaken transaction can spend money, select the wrong configuration or send an order to the wrong address.
That means agentic commerce needs strong confirmation rules, clear product identity, transparent pricing and reliable handoff to the merchant. It also needs safeguards against malicious product pages or instructions designed to manipulate the agent.
Google’s limited test is therefore useful even if the feature changes before a broad rollout. The company is testing the user interface and the technical connection at the same time. The eventual product will reveal how much control shoppers want to retain and how much work they are willing to delegate.
What the change means in practice
For users, the most useful way to judge this development is to look past the announcement and examine the workflow it changes. The technology matters when it removes a real bottleneck, creates a new capability or changes how an existing service is delivered. Specifications are only part of that equation.
The practical impact will also depend on availability, reliability and the surrounding software. A feature that works perfectly in a demonstration can still be frustrating if it requires too many permissions, depends on a cloud service or behaves differently across devices and accounts.
That is why early deployments are often more informative than launch claims. Real users expose edge cases that controlled demonstrations do not.
The bigger technology trend
This development also fits into a broader shift in technology toward systems that combine software with specialized hardware, data and automation. The individual product may be new, but the direction is familiar: companies are trying to make complex computing capabilities easier to use without requiring users to understand the underlying infrastructure.
That trend creates new engineering requirements. Interfaces have to become simpler while the systems underneath become more sophisticated. Security, privacy, reliability and maintenance therefore become product features rather than back-office concerns.
The next stage will be determined by adoption. If people repeatedly use the capability, competitors will copy the approach and the category will mature. If usage remains limited, the technology may remain a niche experiment.
Key points
- The test is limited to selected Flipkart products.
- The experience can move from Gemini into Flipkart checkout.
- Google is testing a broader agentic-commerce model.
The bottom line
The important change is not the Buy button itself. It is the direction of travel. Gemini and AI Mode are being tested as interfaces that can carry a shopping task from intent to transaction. If that model works, search could become less about sending users to websites and more about completing structured tasks across them.
The development is still early, so some details will change as the product, service or security response matures. That is normal for fast-moving technology. The useful signal is the underlying direction: a new capability is being tested in a real environment, and the next round of evidence will come from deployment, independent testing, customer behavior and the engineering changes that follow.
Privacy and security also become more important as technology becomes more connected. A device that collects health information, an agent that can access online services and a platform that knows a user’s age all create data that needs protection. The best product designs make the minimum necessary data available to the system and keep sensitive permissions separated from ordinary functionality.
There is also a less visible implementation issue. A technology becomes dependable only when the surrounding workflow can handle failure. Users need a clear way to retry an operation, understand what happened and recover without losing work. That requirement is easy to miss in a product announcement because demonstrations normally show the successful path. In real deployments, however, the failed path is part of the product. Teams adopting the technology will therefore pay attention not only to its headline capability but also to logs, support tools, permissions, compatibility and recovery procedures.
Another factor is interoperability. New technology rarely exists in isolation. It has to connect to devices, accounts, data stores, payment systems, business software or existing security controls. If the integration is difficult, the theoretical advantage can disappear in deployment. Companies that make new capabilities easy to connect tend to have an advantage because customers can test them without redesigning an entire workflow.