Agentic Commerce: Indian Brands Ko Ab Kya Samajhna Chahiye?
Online commerce ka interface quietly change ho raha hai. Customer product page par filters click kare, comparison spreadsheet banaye aur checkout form manually fill kare—yeh journey ab ek AI agent compress kar sakta hai. User sirf intent bata sakta hai: “₹8,000 ke under office chair find karo, delivery date compare karo aur purchase se pehle approval lo.” Agent discovery, comparison, form filling aur payment hand-off tak kaam kar sakta hai.
September 2026 ke developments is shift ko practical banate hain. Meta ka Muse personal agent browser use kar sakta hai, forms fill kar sakta hai aur purchase se pehle approval leta hai. Meta ne launch ke waqt Stripe Link checkout confirm kiya aur Shop Pay ko “coming soon” kaha. Shopify–Meta partnership ki reporting ke mutabik Muse users Shopify merchants se Shop Pay ke through transact kar sakenge. Seller side par Amazon ne Seller Assistant ko deeper memory, always-on workflows aur external AI-tool integrations ke saath expand karne ki reported update di.
Indian brands ke liye message “kal se Muse ads chalao” nahi hai. Muse ki reported app availability US aur Canada tak limited thi, Shop Pay integration launch-stage par thi, aur Amazon feature availability seller account aur marketplace par depend karti hai. Real opportunity preparation mein hai: product data, inventory truth, merchant policies, attribution aur approval controls ko agent-readable banana.
Agentic Commerce Kya Hai?
Traditional ecommerce mein customer har step operate karta hai. Conversational commerce mein chatbot recommendation deta hai, but checkout mostly customer complete karta hai. Agentic commerce mein software user ke behalf par multi-step actions plan aur execute karta hai—within granted permissions.
Buyer-side agent kya kar sakta hai?
Buyer agent query clarify kar sakta hai, multiple stores compare kar sakta hai, stock aur delivery constraints check kar sakta hai, cart build kar sakta hai aur final purchase ke liye approval maang sakta hai. Meta ke official Muse announcement ke mutabik agent browser open, forms fill aur negotiate kar sakta hai. Sensitive actions, including purchase, se pehle user confirmation design ka part hai.
Seller-side agent kya karta hai?
Seller-side agent customer ke behalf par nahi, merchant operations ke andar kaam karta hai. Amazon ka Seller Assistant inventory, account health, compliance aur growth decisions mein seller ko support karta hai. September 2026 ki reported expansion persistent business memory, conditions monitor karne wale workflows aur Amazon Quick/Claude plugin access par focus karti hai. Iska value stock planning, pricing alerts, review signals aur repetitive operational checks mein ho sakta hai.
Dono sides ko mix na karein. Buyer agent conversion path change karta hai; seller agent operating model. Strategy tab strong hogi jab brand dono ko separately govern kare.
Confirmed Developments: Dates, Scope Aur Caveats
Meta Muse launch
Meta ne Muse ko 8 September 2026 ko personal AI agent ke roop mein announce kiya. Official page ke mutabik Muse dedicated secure VM mein operate karta hai, connected services ke access ko user control karta hai, sensitive actions se pehle permission maangta hai aur audit trail dikhata hai. Checkout ke liye Link by Stripe launch feature tha; Shop Pay “coming soon” tha.
Reuters ne 22 September ko report kiya ki Muse iOS aur Android par US aur Canada regions mein available tha. Isliye India-wide consumer access assume nahi kiya ja sakta. Meta ka “built for billions” positioning product ambition hai, India rollout confirmation nahi.
Shopify and Shop Pay
Shopify–Meta partnership ki 21–22 September reporting says Muse ko Shop Pay agentic checkout ke saath connect kiya ja raha hai, so eligible Shopify stores ka product and checkout infrastructure agent journey mein participate kar sake. Public information har merchant, geography aur plan ke liye identical live availability prove nahi karti. Merchant ko apne Shopify admin, eligibility notice aur supported-market documentation verify karni hogi.
Amazon’s two-sided response
Amazon ne Muse ko apne retail store access ke liye authorised na hone ki baat kahi, transparency aur opt-out concerns raise kiye. Yeh important market signal hai: open web access ko platform permission samajhna risky hai. Agent distribution powerful ho sakta hai, but merchants platform terms, robots rules, account-security controls aur data permissions ignore nahi kar sakte.
Seller side par Amazon already Seller Assistant ko agentic business partner ke roop mein position karta hai. Official 2025 announcement inventory monitoring, FBA recommendations, account-health alerts, compliance help, advertising concepts aur authorised actions describe karta hai. A 23 September 2026 reported update adds persistent memory, custom automations and integrations with Amazon Quick and Claude. India availability, account eligibility and no-additional-cost status should be verified inside the relevant Seller Central marketplace; the 2025 official page confirmed universal access only for the U.S. store at that time.
India-Specific Implications
Product data becomes a sales interface
Agent ko beautiful homepage se zyada clean facts chahiye: exact title, variant, price, stock, delivery promise, return conditions, warranty, material, dimensions, compatibility and exclusions. Conflicting data—website par one price, feed mein another, marketplace listing mein outdated stock—agent recommendation aur customer trust dono hurt karega.
Indian catalogues mein regional complexity extra hai. GST-inclusive pricing, COD availability, PIN-code serviceability, prepaid discounts, exchange policy, language variants aur festival delivery cut-offs machine-readable and current hone chahiye. Hinglish description useful ho sakti hai, but structured attributes incomplete hon to agent confident decision nahi le sakta.
SEO se “agent visibility” tak
Traditional SEO disappear nahi hota. Agents bhi searchable pages, feeds, reviews and merchant APIs se evidence collect karenge. Lekin agent-ready commerce ke liye content ko answerable banana hoga: specifications tables, transparent FAQs, policy pages, organisation identity, current contact details and stable product URLs.
Brand ko “best” claims repeat karne se zyada verifiable evidence dena chahiye. Certifications, test method, warranty scope, delivery area and return exceptions clearly state karein. Agent comparison mein vague superlatives weak signals hain.
Attribution gets harder
Agent journey multiple surfaces cross kar sakti hai: recommendation elsewhere, product verification on the merchant site, checkout through a wallet, and post-purchase communication on email or WhatsApp. Last-click report full story nahi batayega.
Indian teams ko server-side order source, campaign IDs, referral metadata, coupon governance aur post-purchase survey combine karna chahiye. “AI agent” ko one generic channel bana dena bhi premature hai; Muse, search agents, marketplace assistants and direct integrations separately tag karein where technically possible.
Payments and consent need explicit boundaries
Agent ko payment authority dena convenience hai, unlimited permission nahi. High-value orders, subscriptions, saved addresses, regulated products, cross-border purchases and refunds ke liye step-up confirmation define karein. Displayed price, taxes, delivery date and return terms user approval ke waqt freeze ya clearly re-confirm hone chahiye.
India mein UPI, cards, wallets and COD coexist karte hain. Agent flow har rail par same nahi hoga. Until a provider publishes India-specific support, merchant should not claim “AI checkout available” merely because the global announcement exists.
Practical Recommendations for Brands and Sellers
1. Build an agent-ready product record
Top 50 revenue products se start karein. Each SKU ke liye canonical name, unique ID, current price, stock status, tax treatment, dimensions, compatibility, delivery constraints, returns, warranty and source-of-truth owner record karein. Website, Merchant Center, marketplace and CRM data reconcile karein.
2. Separate recommendation from execution
AI ko comparison aur draft cart tak broader access diya ja sakta hai. Purchase, refund, price override, promotion change, inventory transfer and customer communication ke liye explicit approval gates rakhein. Seller Assistant automation enable karte waqt allowed action, threshold, owner and rollback define karein.
3. Create merchant allowlists
Customer-facing agent integrations ke liye approved domains, payment providers and support contacts publish karein. Internal agent ke liye approved marketplaces, accounts and destinations restrict karein. Unknown login page, unexpected CAPTCHA or access-denied response hard stop hona chahiye.
4. Protect commercial logic
Agent ko entire margin model, supplier agreements or customer database dena necessary nahi. Use task-specific views dein. Pricing automation ke liye floor price, maximum daily change, promotion exclusions, inventory threshold and escalation rule define karein. “Optimize price” without boundaries business instruction nahi hai.
5. Design human-readable audit trails
Every automated action ke saath reason, source data, before/after value, approver and timestamp capture karein. Amazon ya Shopify dashboard output ko blindly final record na samjhein; high-impact actions ko internal change log mein mirror karein.
A 30-Day Agentic Commerce Readiness Plan
Days 1–7: Inventory and scope
• Buyer journey map karein: discovery, comparison, product detail, cart, payment, delivery and returns.
• Seller operations map karein: listing, pricing, inventory, reviews, compliance and advertising.
• Top products and highest-risk actions identify karein.
• Muse, Shop Pay or Seller Assistant availability ko actual account evidence se verify karein.
Days 8–14: Data cleanup
• Product feed, schema, policy pages and marketplace listings reconcile karein.
• Broken variants, duplicate SKUs, outdated delivery claims and unclear return terms fix karein.
• Analytics taxonomy mein agent/referral fields reserve karein.
• Internal permissions review karein; shared admin credentials retire karein.
Days 15–21: Controlled pilot
• One product category ya one seller workflow choose karein.
• Read-only recommendations se start karein.
• Purchase, price, inventory and customer-message actions par approval require karein.
• Baseline metrics capture karein: task time, error rate, stock-outs, price overrides, conversion and support contacts.
Days 22–30: Review and decide
• Agent recommendations ko actual outcomes se compare karein.
• False alerts, missed constraints, policy conflicts and attribution gaps document karein.
• Rollback, audit log and incident escalation test karein.
• Scale only when time saved and business outcome measurable ho—and exceptions manageable hon.
Update Verified Sep 29, 2026: Gemini Buy Test and Meta Enterprise
Two fresh developments strengthen the agentic-commerce direction without proving universal rollout. India mein Google is testing a “Buy” flow with Flipkart inside Gemini/AI Mode, while Meta has announced a broader enterprise platform around Muse and business agents. Dono items ko existing readiness framework mein merge karna better hai than separate hype-driven articles.
Gemini–Flipkart Buy test in India
The Indian Express report updated Sep 29, 2026 says selected users saw a Flipkart-branded Buy option inside Gemini and AI Mode for a limited catalogue including smartphones, electronics and mobile accessories. Flow discovery se checkout hand-off tak friction reduce kar sakta hai. Google spokesperson ne only said the company regularly tests new experiences and had no additional details.
Report broader October availability mention karti hai, but Google ne reviewed response mein nationwide date, merchant eligibility, supported categories, fees, measurement method or final product design confirm nahi kiya. Isliye Indian brands ko “Gemini shopping is live for everyone” claim nahi karna chahiye.
Practical readiness: clean product titles, current price, stock, seller identity, delivery promise, returns and warranty ko source-of-truth mein reconcile karein. Referral and order-source fields reserve karein, but tracking behaviour actual test traffic se verify karein. Feed visibility ko payment or checkout eligibility ka substitute na samjhein.
Meta Enterprise Platform
Meta ne Sep 28, 2026 ko Meta Enterprise Platform announce kiya. Official overview initially Muse agent, Meta Business Agent, Muse API, Muse Code and future enterprise tools ko one full-stack offering ke under position karta hai. Meta security and privacy ko built-in principle ke roop mein describe karta hai.
Reviewed announcement India pricing, plan structure, launch schedule, service levels, data residency, customer outcomes or universal availability publish nahi karti. “Enterprise platform launched” ko “Indian firms can buy every module today” ke roop mein translate karna unsupported hoga.
For Indian businesses, near-term action vendor dependency se pehle governance ready karna hai: approved data sources, task-specific permissions, human approval for purchases or public actions, audit trails, retention rules, incident owner and kill switch. Muse API or Business Agent evaluation tab meaningful hogi when business problem, allowed actions and measurable baseline defined hon.
Confirmed status and professional analysis
Confirmed: a limited Gemini–Flipkart test was reported for selected Indian users; Google did not confirm nationwide timing. Confirmed: Meta announced the enterprise platform and named initial components. Not confirmed: India-wide commercial availability, common pricing, conversion lift, merchant access or a fixed October rollout.
Analysis: buyer-side discovery, checkout hand-off and enterprise-side agent orchestration are converging, but merchant advantage will come from trustworthy data and controlled execution. Brands should prepare interoperability and measurement now, while avoiding premature integration claims.
Update sources
The Indian Express: Gemini–Flipkart Buy test — report updated Sep 29, 2026; selected-user test, limited catalogue and Google’s no-details response. https://indianexpress.com/article/technology/tech-news-technology/google-flipkart-buy-option-gemini-ai-india-report-10895842/
Meta: Launching Meta Enterprise Platform — official announcement published Sep 28, 2026; initial components and platform positioning. https://about.fb.com/news/2026/09/launching-meta-enterprise-platform/
Muse for Small Business Update: Connectors, Approvals and India Readiness
Meta ne Sep 29, 2026 ko Muse for Small Business announce kiya. Official post says Muse can connect with Instagram professional analytics, Facebook Pages and Meta ad accounts, plus business tools including Asana, Box, Canva, Dropbox, Figma, Granola, HighLevel, QuickBooks, Klaviyo, Lovable, Notion, Shopify, Slack, Stripe and Zoom. Custom connectors are also described.
Meta positions the experience for tasks such as growth planning, email and calendar triage, ad and content improvement, financial-performance review and expense-anomaly detection. Crucially, the company says Muse does not publish, send or spend without approval.
India Availability Ko Assume Na Karein
Reviewed Meta materials place the base Muse product in the US and Canada. The small-business announcement does not establish a universal Indian rollout, rupee pricing, support SLA, data-residency commitment or identical connector availability for every account. Meta says the service is free for most common needs, with subscriptions for more usage, but India-specific commercial details remain unconfirmed.
Indian businesses ke liye immediate opportunity access claim karna nahi, connector readiness improve karna hai. Social analytics, ads, Shopify, accounting, CRM, email and collaboration systems mein duplicate or conflicting records clean karein. Agent ko sirf woh data expose karein jo task ke liye necessary hai.
Approval Is A Control, Not A Strategy
“Nothing publishes, sends or spends without approval” useful boundary hai, but approval quality depend karti hai reviewer context par. Approval screen ko request purpose, destination, amount, audience, source data and expected effect clearly show karna chahiye. Rubber-stamp approval agent risk ko human-click risk mein convert kar deta hai.
30-Day Readiness Actions
• Connector inventory banayein: owner, data type, permission scope, retention and revocation path.
• One narrow workflow choose karein—weekly growth brief, content-performance summary or expense-anomaly review.
• External publishing, ad-spend change and payment actions ko human approval ke behind rakhein.
• Output accuracy, time saved, correction rate and business outcome compare karein.
• Account access unavailable ho toh mock workflow and data hygiene complete karein; rollout claim na karein.
Confirmed Facts Versus Analysis
Confirmed: Meta published Muse for Small Business on Sep 29, 2026, named first-party and third-party connectors, and said approval is required before publishing, sending or spending. Meta’s reviewed Muse materials establish US and Canada availability, not universal India access.
Analysis: Connector breadth can make agentic commerce and marketing operations more useful, but the competitive advantage will come from clean systems, narrow permissions and meaningful approvals. For Indian SMEs, readiness work is valuable even before access arrives.
Update source: Meta, “Introducing Muse for Small Business,” published Sep 29, 2026. https://about.fb.com/news/2026/09/introducing-muse-small-business/
Confirmed Facts Versus Professional Analysis
Confirmed facts
• Meta announced Muse on 8 September 2026 and documented browser use, form filling, user approvals, Link checkout and planned Shop Pay support.
• Reuters reported Muse availability in the US and Canada on 22 September; no India-wide rollout is established by the reviewed sources.
• Shopify–Meta partnership reporting describes Shop Pay-powered agentic checkout, but universal merchant availability is not established.
• Amazon said Muse was not authorised to access its store and raised transparency and opt-out concerns.
• Amazon’s official Seller Assistant material confirms agentic inventory, account-health, compliance and authorised-action capabilities; a 23 September 2026 report describes added memory, automations and external AI integrations.
Professional analysis
• Indian brands should invest first in trustworthy product data and controlled execution, not in speculative “AI commerce” badges.
• Agent-driven journeys can reduce friction but also weaken brand visibility and attribution unless the merchant exposes clear evidence, stable identifiers and post-purchase relationship paths.
• Seller automation is most valuable for repetitive monitoring; strategic pricing, regulated claims and customer-impacting changes still deserve accountable human ownership.
Conclusion
Agentic commerce ka near-term winner woh brand nahi hoga jo sabse loud AI claim karega. Winner woh business hoga jiska catalogue accurate, policies unambiguous, inventory current, payments controlled and measurement resilient hai.
Meta Muse, Shop Pay and Amazon Seller Assistant ek common direction show karte hain: software sirf advice nahi dega; it will increasingly act. Indian businesses ko rollout rumours chase karne se better apni operating readiness improve karni chahiye. Jab access actually arrive ho, clean data and clear guardrails experiment ko faster—and safer—banayenge.
Sources and Verification Notes
Meta: Introducing Muse — published September 8, 2026; official capabilities, Secure VM, approvals, Link checkout and Shop Pay “coming soon” status.
Reuters: Wall Street expects Meta’s Muse to become a revenue engine — published September 22, 2026; US/Canada availability, Amazon access objection and rollout context.
PYMNTS: Shopify brings Shop Pay checkout to Muse — published September 22, 2026; partnership timing and agentic-checkout description.
Amazon: Seller Assistant agentic AI announcement — published September 17, 2025; official inventory, account-health, compliance, advertising and authorised-action baseline.
Amazon Seller Central: Seller Assistant help page — current product reference checked September 24, 2026.
NDTV Profit: Amazon upgrades Seller Assistant with automation and plugin support — published September 24, 2026; reported memory, workflows and Amazon Quick/Claude integration. India availability was not confirmed.
ChatGPT Virtual Try-On Update: Discovery Se Confidence Tak
ChatGPT Shopping ab eligible clothing aur accessory results ke saath “Try on” experience dikha sakta hai. User selfie upload ya capture karke ChatGPT Images se generated visual dekh sakta hai; item image upload karke direct try-on request bhi ki ja sakti hai. Yeh agentic-commerce journey mein discovery aur pre-purchase confidence ke beech ek naya layer add karta hai.
Confirmed facts
- OpenAI ki shopping help guidance ke mutabik try-on clothing aur accessories ke liye available ho sakta hai.
- Generated image product ya user appearance ko exactly represent karne ki guarantee nahi deta.
- Try-on size ya fit guarantee nahi karta; merchant measurements, product details aur return policy check karna zaroori hai.
- Shopping results independently selected hain, ads nahi; eligible products aur merchants ke liye Instant Checkout appear ho sakta hai.
- Shopify catalogue ChatGPT Shopping ke saath integrated hai, aur merchants direct product-feed access request kar sakte hain.
Indian brands ke liye implications
Virtual try-on creative asset ka substitute nahi, product-data amplifier hai. Agar colour, material, dimensions, variant identifiers, availability aur returns unclear hain, impressive visual ke baad bhi conversion friction rahega. Indian apparel, jewellery, eyewear aur accessory sellers ko catalogue imagery, size charts, shade naming, GST-inclusive pricing, dispatch promise aur returns ko consistent rakhna chahiye. Regional-language explanation useful ho sakti hai, lekin material facts har language mein identical rehne chahiye.
Practical action plan
- Hero images aur variant images ko clean, current aur high resolution rakhiye.
- Size chart ko body-measurement instructions aur tolerance note ke saath publish kijiye.
- Product feed, website schema, marketplace listing aur checkout data reconcile kijiye.
- Try-on influenced sessions ko normal sessions se separate measure karne ke liye UTM aur analytics plan banaiye.
- Generated visual ko “fit proof” ya exact colour guarantee ke roop mein advertise mat kijiye.
- Return reasons track kijiye: size, colour expectation, material, delivery aur product mismatch.
- India availability ko assume na karein; account, category aur merchant eligibility verify kijiye.
Confirmed fact: try-on capabilities, limitations aur shopping independence OpenAI ki guidance mein documented hain. Analysis: India rollout timing, conversion lift aur category-wise impact guaranteed nahi hai.
OpenAI help page updated Oct 2, 2026. Source: https://help.openai.com/en/articles/11128490-shopping-with-chatgpt-search
Update: Google Commerce Audience Sharing — Oct 9, 2026
Confirmed facts
Google Ads now documents commerce audience sharing for eligible commerce media network campaigns. A commerce partner—such as a retailer or marketplace—can share selected first-party audience segments with an advertising partner such as a brand or seller. Both sides must meet applicable requirements and link the advertiser’s Google Ads account with the commerce partner’s Merchant Center and advertising data-sharing account.
Use is tightly scoped. Shared audiences can be applied only to eligible commerce media network campaigns, and traffic must return to the domain approved by the commerce partner. The feature is not a general permission to reuse retailer data across ordinary Search, Shopping or Performance Max activity.
Who can see what?
Google says the commerce partner can access campaign performance and spend metrics such as impressions, clicks and conversions. The advertising partner can see shared-segment details such as name, customer type, list size and membership status, plus relevant partner-site conversion performance. The commerce partner chooses which audiences to share, and accepting a data-sharing link does not give the partner direct access to the advertiser’s full Google Ads account.
India-specific opportunity
For Indian marketplaces, retail networks and large distributors, this can support supplier-funded campaigns built on high-intent first-party signals. A consumer-electronics marketplace, for example, might create an eligible segment for category visitors and allow a participating brand to reach those users while sending traffic back to the marketplace.
The business value depends on more than targeting. The parties need clear commercial terms, audience definitions, destination ownership, creative approval, conversion taxonomy, reporting access, data retention and dispute handling. Smaller sellers should compare incremental sales with media fees, marketplace margin, discount funding and cannibalisation of organic marketplace demand.
Governance checklist
Define data-controller and processor roles with counsel where relevant. Record the lawful and contractual basis for audience use. Minimise fields and avoid sensitive-category inference. Confirm Customer Match eligibility when that audience type is involved. Use an approved-domain allowlist. Separate partner-funded spend from the brand’s direct media. Agree which conversion events are authoritative. Set an unlinking and deletion process before the campaign starts.
Measurement plan
Create a baseline for sales on the partner domain, then run a controlled eligible campaign where scale permits. Measure incremental orders, contribution margin, new-to-brand or new-to-seller quality, cancellations, returns and repeat purchase. Do not report shared-audience ROAS without explaining that the conversion happens on the commerce partner’s property and may use partner-defined attribution.
What brands should not assume
Do not assume access is universal in India. Do not upload or combine customer data without the required permissions. Do not treat a partner audience as owned data. Do not redirect users to an unrelated brand domain. And do not describe this as an agent automatically negotiating or completing purchases; it is an audience collaboration capability inside eligible commerce media campaigns.
Confirmed facts versus analysis
Confirmed: Google documents the linking requirements, shared-audience controls, eligible-campaign limitation, approved-domain restriction and the visibility available to each party. Analysis: the capability can strengthen retail media cooperation in India, but economics, access and incrementality will vary by partner and agreement.
Update source
Google Ads Help: About commerce audience sharing through Google Ads — eligibility, linking, controls and measurement visibility.
UPDATE — 16 OCTOBER 2026
Google Universal Cart: US Launch and India Readiness
CONFIRMED FACTS
Google launched Universal Cart in the United States on 15 October 2026 across Google Search and the Gemini app. The cart lets users save products from multiple retailers in one place, retain their progress across Google, receive price-drop or back-in-stock notifications, view relevant promo codes and consider payment-card benefits.
Google says the cart is powered by the Universal Commerce Protocol and its Shopping Graph, which contains more than 60 billion continually refreshed product listings. At checkout, users can pay with Google Pay at participating stores or transfer products to the merchant’s website. The merchant remains seller of record and provides order confirmation and customer support.
Google named merchants including Nike, Sephora, Target, Ulta Beauty, Walmart and Wayfair, along with many Shopify merchants. The announcement does not provide an India launch date, India merchant-eligibility list or Indian payment-method support.
INDIA-SPECIFIC ANALYSIS
Indian retailers should not advertise Universal Cart as available locally. The useful action is preparation for a commerce journey in which discovery, comparison, saved intent and checkout may span Search, Gemini and the merchant site.
Readiness depends on fundamentals:
• correct product titles and identifiers;
• current price and availability;
• clean promotion data;
• reliable delivery and return information;
• merchant-policy consistency;
• mobile checkout quality;
• conversion and order reconciliation;
• clear seller-of-record responsibilities.
The launch also reinforces why product data must be treated as operational data, not only an advertising feed. If price, stock or promotions are stale, an intelligent cart can scale customer disappointment as easily as it can reduce friction.
For Indian brands selling into the United States, do not infer eligibility simply from having a US-facing website. Confirm Merchant Center standing, participating checkout integrations, Google Pay setup, Shopify or other platform compatibility, and actual account availability.
MEASUREMENT PLAN
Track saved-product activity only when a supported report becomes available; do not invent a metric. On the merchant side, monitor product-page visits, checkout starts, completed orders, promo-code use, payment failures, cancellations and customer-service contacts.
Keep marketplace, direct website and agentic-commerce orders separate where attribution permits. The business question is not merely whether Google sent a visit, but whether the order was profitable, fulfilled and retained.
CONFIRMED FACTS VS ANALYSIS
Confirmed:
• Universal Cart launched in the US on 15 October 2026.
• It is available across Search and the Gemini app.
• It can combine items from multiple merchants and provide price, stock, promotion and payment information.
• Checkout may happen with Google Pay or on the merchant website.
• Merchants remain seller of record.
Analysis:
• India-focused merchants should prepare product and transaction data while waiting for a confirmed rollout.
• US-selling Indian brands should verify individual eligibility rather than assume access.
• Product-data quality, fulfilment and customer support will determine whether reduced shopping friction creates profitable growth.
SOURCE
Google Shopping announcement, published and launched 15 October 2026:
https://blog.google/products-and-platforms/products/shopping/universal-cart-launch