The abandoned cart email is the most dependable money in ecommerce. Someone puts a jacket in the cart, wanders off, and your flow fires an hour later, then a day later, maybe with a nudge about shipping. Every retention team I know has tuned that sequence until it squeaks.
On October 15, Google started rolling out a cart that your sequence will never see.
Universal Cart is now live in the U.S. across Google Search, including AI Mode, and the Gemini app. Shoppers can save products from different retailers into one cart that follows them across those surfaces. Google watches the saved items and sends notifications when a price drops or something comes back in stock. It surfaces promo codes and, through Google Wallet, suggests which of the shopper’s cards earns the most on the purchase. When the shopper is ready, they either pay with Google Pay inside the cart at participating stores or transfer the items to the merchant’s own cart. Google names Nike, Sephora, Target, Ulta Beauty, Walmart, Wayfair and many Shopify merchants for those checkout options. The merchant stays the seller of record either way. Google said in May that YouTube and Gmail would get the cart later. There is still no date.
Most of the coverage reads this as a checkout story. I think the marketing consequence sits one step earlier. For the shoppers who use it, Google now holds the saved cart, the price watch and the reminder. You hold the inventory and the price. That changes who writes the most profitable message in your holiday calendar.
The save happens where you cannot see it
Start with what actually reaches your systems. Google’s developer guide for the Cart API, the part of the Universal Commerce Protocol that powers cart transfer, is blunt. When a shopper adds items, Google accumulates them on its side and does not call the merchant as items are added. A single request arrives only when the shopper clicks to transfer, carrying everything at once. This first release is one-way: Google can create a cart on your site, and updating, deleting or syncing cart contents between Google and your system is not supported.
Then look at the reporting. Merchant Center’s UCP analytics, and the alpha Merchant API view that mirrors it, count buy button clicks, linked accounts, purchases, cancellations, cart transfers and average cart value. At the product level you get buy button clicks. Search Engine Journal’s Matt Southern went through the same pages on launch day and found no metric for products saved to a cart. I went through the API reference and could not find one either.
So the shopper who saves your item in AI Mode on a Tuesday and forgets about it is, from your side, nobody. No cart event. No session. No email capture. Your abandoned cart flow keys off a cart on your site tied to a shopper you can identify, and this cart is on Google. The only signal you will ever get is the moment they come back and act.
Your markdown is now someone else’s push notification
This is the part I would put in front of the merchandising team this week.
Google says the cart is built on its Shopping Graph, more than 60 billion continually refreshed product listings, and works in the background to send notifications about price drops and restocks. Read that from the merchant side. The trigger for the most persuasive cart reminder a shopper can get is your own price change, picked up from your feed or your page. Google writes the message, picks the moment, and puts it on the shopper’s phone next to whatever else they saved from other stores.
That makes every price change a broadcast to everyone who saved the item. A planned Black Friday markdown is fine. That is the point. The problems are the changes nobody thinks of as marketing: a two-day price test, a regional price that leaks into the feed, a clearance price on one size, a price match that gets applied site-wide, a feed error that shows $19 instead of $91 for an hour. On your site those are pricing operations. In Universal Cart they can become alerts.
Google has not published what counts as a drop worth notifying, how often a shopper can be pinged, or whether a drop on one variant alerts someone who saved another. I would not guess. I would plan as if any lower price is eligible.
The same goes for promo codes. Google says the cart will show relevant promo codes right from the cart. The launch post does not say where those codes come from. Merchant Center already accepts promotions you submit and runs an automated promotions program that pulls offers from product pages, but Google has not tied either one to the cart in writing. If your code book includes single-use apology codes, employee codes, or creator codes that pay a commission, assume anything findable on the open web can end up beside a cart you never saw.
There is also a sequencing shift. Your current reminder flow probably holds the discount back: the first email is plain, the second mentions shipping, the third offers ten percent. Google’s reminder fires when the price moves. If you discount early in November, everyone who saved the item hears about it early. If you hold, they hear on the day you cut. The order of your markdowns now sets the order of reminders for shoppers you cannot see.
The handoff is a snapshot, so the landing has to be right
If you choose cart transfer, Google calls your endpoint with the shopper’s line items and you return a continue_url that points to a prefilled cart on your site, along with an expiry time for that cart session. That is the whole conversation. Nothing flows back.
That makes the transfer landing one of the most important pages you have this season, and most teams have not built it yet. A few things I would check before the traffic arrives:
- The prefilled cart loads fast and shows the price the shopper saw on Google. Google recommends responding in under a second and planning endpoint capacity for the referral traffic you expect during peak campaigns.
- The expiry you set is long enough for a shopper who transfers on a phone and finishes on a laptop that evening.
- Your developers tag the
continue_urlso analytics can tell a Universal Cart arrival from an ordinary Google visit. You write that URL, so you can mark it. - The page earns the email address. This may be your first contact with a shopper who did all their browsing on Google, so sign-in, loyalty and opt-in on that cart page have to work hard.
Google’s own pitch to merchants for cart transfer is the chance to upsell and cross-sell on your site. Fine. That only works if the page is ready to do it.
When the purchase stays on Google
Native checkout is the other route, and the measurement trade gets sharper there. Shopify’s help page for its Google AI Mode and Gemini channel says direct checkout is on by default for eligible U.S. stores. It says Google Analytics and custom pixels do not fire in that checkout (only server-to-server started and completed events do), and that checkout blocks for loyalty, upsells, and collecting consent for data use and communication preferences might not display. You also cannot require customers to sign in. Southern noted on launch day that he could not confirm whether purchases made inside Universal Cart from Shopify merchants run through that same direct checkout. I could not confirm it either. If you sell on Shopify, check your own orders before you assume anything.
The practical result: you keep the order, the fulfillment and the customer service, and you may lose the browser-side tracking and the opt-in moment. Google lists identity linking, the piece that would bring loyalty benefits and signed-in checkout to native checkout, as coming soon. For a holiday acquisition push that depends on turning first-time buyers into January email subscribers, that is a real cost.
Keep it in proportion
None of this means half your fourth quarter moves to Google next week. Universal Cart asks shoppers to change a habit. Analysts quoted when Google previewed it were openly skeptical. Neil Saunders of GlobalData warned against overhyping something he called embryonic, and Matt Maher of M7 Innovations doubted shoppers would come back to a Google cart days later. They may be right. Shopify, for its part, announced on October 13 that shoppers will be able to connect any AI agent to their Shop account and buy across its catalog, so the Google cart is one of several places a basket can now live outside your site.
That is the real planning problem. You do not need to win Universal Cart. You need your pricing, promo and measurement habits to hold up when some baskets sit somewhere you cannot see. That arrived this week, six weeks before Black Friday.
What I would do this week
Pick your route on purpose. In Merchant Center, the UCP integration hub (rolling out gradually in the U.S.) lets you support transfer to your own cart, native checkout on Google, or both. On Shopify, direct checkout sits under Sales channels, then Agentic. Decide based on what you lose at checkout. If consent capture, loyalty sign-in or bundles carry your economics, cart transfer is the safer default. Write the decision down with an owner.
Put price changes under marketing review for the season. Freeze price tests on hero products from now through Cyber Monday. Add a feed price check to the daily pacing call. Treat any markdown on a product people can save as a customer message, because for some shoppers it now is one.
Sequence markdowns knowing they double as reminders. Decide which drop you want shoppers to hear about first. If your deepest price lands on Black Friday, do not let a soft early cut spend the alert two weeks before.
Audit the code book. List every active promo code, who it is for, and whether it is findable on the open web. Kill or restrict the codes you would not want shown in a cart next to another store’s items. Submit the codes you do want public through Merchant Center promotions. Google has not confirmed that feeds the cart, but it is the official channel you control.
Build the transfer landing. Prefilled cart, matching price, sensible expiry, tagged URL, sign-in and opt-in that earn their place. Load test it against your peak hour, not an average Tuesday.
Start a Universal Cart line in the measurement plan. Pull Merchant Center UCP analytics daily: buy clicks, purchases, cancellations, cart transfers and average cart value. Reconcile purchases against your order system, not your analytics tool. Ask your analytics team to send server-side order events for orders that never touch the browser. Agencies should script the pulls now, because the Merchant API’s UCP views only work on individual accounts, not on multi-client advanced accounts.
Give Google-sourced buyers their own welcome. Your abandoned cart program still matters for carts on your site. Add a post-purchase path for orders that arrive through Google checkout or a transfer, because the first email those buyers get from you may be an order confirmation.
Questions for Google or your rep
- What price change counts as a drop worth notifying, and how often can one shopper be alerted about the same item?
- Where do the promo codes shown in the cart come from, and can a merchant exclude specific codes?
- Will merchants ever see saved-to-cart counts, even aggregated by product?
- For Shopify merchants, does an in-cart Google Pay purchase run through the same direct checkout as AI Mode and Gemini?
- When does identity linking go live, so loyalty members are recognized at native checkout?
Who owns the moment now
For a decade the cart reminder was yours because the cart was yours. Universal Cart moves the cart, for some shoppers, to Google, and with it the timing and the wording of the nudge. What you still control is the trigger: your price, your codes, your landing page, and the measurement that tells you whether any of it worked.
Set those on purpose this week. Otherwise Google will send your holiday cart reminders for you, timed to whatever your pricing team did last Tuesday.
