Google began rolling out Universal Cart in the United States on October 15, across Search and the Gemini app. The feature brings together products saved from multiple retailers, tracks price and availability changes, and lets shoppers continue a purchase through Google Pay or on the retailer’s website. The merchant remains the seller responsible for the order and the customer relationship.
The rollout puts the previously previewed cart into use while leaving the shopper in control of the process. Products can be collected in one place before the person decides what to buy. The announcement for this stage specifically names Search and Gemini in the United States, defining the distribution area separately from broader presentations about AI-assisted commerce.
Products stay together across Search and Gemini
According to Google, Universal Cart retains a selection as the user moves between Google experiences. An item saved in AI Mode in Search can remain alongside products added later in Gemini. The list therefore belongs to the user’s shopping journey rather than being tied exclusively to a single store visit or an individual browser tab.
Product information comes from the Shopping Graph, which Google says contains more than 60 billion continually refreshed listings. This allows the cart to send notifications when a saved product drops in price or an unavailable item comes back into stock. The figure describes the catalog size reported by the company, rather than the number of stores offering every purchasing option.
Another component uses the connection with Google Wallet to highlight payment-method benefits. The cart can help users choose between cards based on their benefits and display relevant promotional codes. Google describes this as part of organizing a purchase: payment benefits and promotions are considered in the context of products that the user has already added to the cart.
Two routes to completing an order
Shoppers can pay with Google Pay directly inside the cart at retailers supporting that experience. The other option transfers the items to the merchant’s cart, where the user continues the order process. The announcement lists Nike, Sephora, Target, Ulta Beauty, Walmart, Wayfair and many Shopify merchants as examples of these simplified experiences, without stating that every store participates automatically.
Under either route, the merchant provides the confirmation and customer support. It remains the seller responsible for the transaction, described in the documentation as the Merchant of Record. Starting a selection in a Google interface does not transfer the store’s commercial responsibility for purchased products or its management of the customer relationship after the order to the search engine.
The technical connection is the Universal Commerce Protocol, the UCP standard Google uses for these commerce interactions. The protocol separates cart-transfer capabilities from payment functions within Google’s interface. For an online store, that distinction is practical: receiving a selection of products and processing a native checkout are separate integrations with different technical responsibilities.
Cart transfer has a defined function
The Cart API documentation describes a one-way transfer from Google surfaces to the merchant’s system. The CreateCart method creates and populates a cart on the website before checkout. The initial release covers this creation and transfer; updating, deleting and continuously synchronizing the contents between Google and the store are outside the scope of this capability.
The Cart API is available starting with UCP version 2026-04-08. A store declares the relevant capability in its UCP profile, and Google uses the technical endpoint published there for its calls. Transfer can be implemented without the separate native checkout API, payment handlers or order-lifecycle integration, according to the boundaries Google has published for this feature.
Transfer calls are triggered by the user’s decision to send the cart to the store. Their volume therefore follows user traffic and shopping intent. Google recommends a fast response, ideally under one second, and explains that exceeding that interval does not automatically cause the transfer to fail. The recommendation concerns the technical experience of handing the selection over to the website.
The user confirms payment during checkout
For native checkout, the retailer separately exposes services that create and manage the shopping session. The flow described by Google moves from building the selection to an interface where the person enters sensitive shipping and payment details and submits the order. The AI agent is not involved in that part of the confirmation, according to the published architecture.
Session statuses distinguish incomplete information, payment preparation, final validation and a completed order. The store calculates shipping options and totals using the address it receives. The merchant also checks inventory in real time and signals through its technical response when a product is unavailable or an address falls outside the areas to which it can deliver.
Merchant Center remains central to the ecosystem. Google requires product information, brand assets, return policies and business contact details to be complete and current. According to its explanation, native UCP integration adds a direct-purchase option, while the ranking of offers in product listings continues to be handled separately from the choice of this integration.
The October 15 update concerns the US rollout of Universal Cart, following the initial preview in May. Romania is outside the market named for this launch. For participating merchants, the selection retained across Search and Gemini, the transfer to a website and native checkout are defined components of the same shopping journey, each with documented functions and integration conditions.
