Overview
How might we let an AI shop across merchants into one cart, so people review and pay once instead of visiting each storefront themselves?
When AI sources from more than one merchant
- Shopping assistants that assemble kits or lists from multiple retailers.
- Builds where compatibility and seller clarity matter (PC parts, appliances, gifts).
- Flows where price watching belongs on the shared basket, not only on each PDP.
- Checkout that places merchant-specific orders from one saved wallet.
When a single-item buy-now is enough
- Single-SKU flows where instant buy is enough and a multi-merchant cart adds noise.
- Markets where multi-merchant carts violate local commerce or tax rules.
- Products that cannot show clear merchant of record or return ownership per line item.
States
Design the cart as the place AI shopping intent becomes a reviewable, multi-merchant order plan.
Sourcing
The assistant finds items across merchants for the user’s goal and proposes a basket.
Adding
Accepted items enter one cart. Every line keeps retailer attribution.
Watching
The cart monitors price, stock, and fit across merchants while the shopper reviews.
Insight
Proactive notices surface drops, restocks, or incompatibilities before pay.
Reviewing
The cart groups by merchant with clear subtotals. Shoppers can edit or remove lines.
Paying
One wallet pay places the merchant orders. Explicit consent still gates spend.
Confirmed
Separate confirmation IDs per merchant. Each brand remains merchant of record for its lines.
Key UX elements
The parts that must be present when AI shops across merchants into one cart.
Let AI pull from multiple merchants.
The assistant finds candidates across retailers for one shopping goal, instead of sending the user store-hopping.
Keep one reviewable basket.
Accepted items land in a single cart the user can edit before any money moves.
Show who fulfills each line.
Group by merchant so returns, shipping, and support ownership stay clear.
Make the cart proactive.
Price drops, stock, and compatibility across items appear before pay.
Place merchant orders from one wallet.
One pay action charges the saved wallet and creates separate merchant orders with clear totals.
Confirm per merchant.
Show confirmation IDs, sellers, and line totals so dual orders do not feel like one opaque charge.
Anti-patterns to avoid
Hiding which retailer fulfills each line so returns and support are unclear.
Silent price or availability changes at pay time with no notice.
Charging once without showing that separate merchant orders will be placed.
Forcing users back to each storefront to finish what the AI already assembled.
How products use it
| Product | Implementation |
|---|---|
| Google Universal Cart | AI-assisted shopping cart that holds items from multiple retailers and monitors deals and fit before checkout. |
| Google Shopping / UCP | Checkout that can pay with a saved wallet while each brand stays merchant of record for its lines. |
| Gemini | Chat finds products across sellers and adds them into one reviewable cart before pay. |
| Perplexity Shopping | Research and buy paths that compare merchants, then stage purchase without sending users store-hopping. |
Implementation
Copy this prompt to generate a production-ready implementation in Cursor, Claude Code, Lovable, or any AI coding agent.
Generate a production-ready implementation of the "Universal Cart" AI interface design pattern.
Pattern Definition:Frequently asked questions
What is a universal cart in AI shopping UX?
A single cart for when AI shops across merchants. Items stay attributed to each retailer, and one pay step places the underlying orders so users do not rebuild the basket on every site.
How is it different from shopping without AI?
Without AI, people open each merchant, compare listings, and check out separately. Universal cart lets the assistant assemble the multi-store basket and present one place to review and pay.
How is it different from instant buy?
Instant buy completes one product purchase in the moment. Universal cart stages a multi-merchant basket, watches price and compatibility, then places the orders when the user is ready.
What should the cart do before pay?
Group by merchant, show who fulfills each line, watch price drops and stock, flag incompatibilities across items, and make clear that pay will place separate merchant orders from the saved wallet.