Service
Agentic Commerce
Assistants now find products, compare them and in some cases buy them. Your feed is the thing they read, and most feeds were never built to be read by a machine deciding on a shopper’s behalf.

What is agentic commerce?
Agentic commerce is a fancy name for letting an AI assistant do some of the shopping legwork: hunting for products, comparing them, checking price and stock, now and then even placing the order. Nobody opens ten tabs any more. They ask ChatGPT, Gemini, Copilot or Alexa and get a shortlist back. So for a seller, software now reads and judges your products before any person sees them.
Say a family in Pune needs a new mixer grinder. A few years ago, they’d search Google, open Amazon and Flipkart, read reviews and watch a YouTube comparison. Now they might ask an assistant: “best 750W mixer grinder under ₹5,000 with a good warranty, available for delivery by Saturday”. Behind the scenes the assistant reads feeds, specs, reviews and stock, picks three, and links to where you can buy. The brands with full, accurate, machine-readable data made the cut. The rest were invisible.
- Jan 2026Google and Shopify announced the Universal Commerce Protocol with 20+ backers.
- Mar 2026ChatGPT’s Instant Checkout was scaled back after a few months.
- 1thing every agent depends on: accurate product data.
- ~2xnew-customer rate Walmart reported from assistant referrals compared with search.
- What you can check this week.
- How agent shopping works.
- What actually shipped.
- The protocols, explained plainly.
- Product feed readiness.
- Product content agents can use.
- Using AI on product data.
- Checkout, payments and handoff.
- Marketplaces and agents.
- Measuring agent traffic.
- How we run it.
- Three examples.
- Checklist.
- Common questions.
How agent shopping works
Shopping with an AI follows roughly the steps you’d take yourself. What changes is who does each step, and what they trust.
- Ask. The buyer describes what they need, often with budget, timing and preferences.
- Search. The agent queries product feeds, search indexes, catalogues and reviews.
- Filter. It drops options that don’t fit: wrong price, no stock, no delivery to that pin code.
- Compare. It weighs specs, ratings, return policies and seller trust.
- Hand off or buy. It links to the merchant, adds to a cart, or in some cases completes the purchase.
Look at what decides the filter step: price, stock, delivery and policies. If your feed says “in stock” when you’re sold out, or omits shipping costs, the agent either drops you or recommends you and disappoints the buyer. Both are bad. An agent can’t phone your shop to check. It trusts whatever data it can read.
Who the agents are
| Agent. | Where it shows up. | Main data it reads. |
|---|---|---|
| Google AI Mode and Gemini. | Google Search, Android, the Gemini app. | Google Merchant Center feeds, Shopping Graph, websites. |
| ChatGPT shopping. | ChatGPT apps and web. | Merchant feeds, partner catalogues, web search. |
| Microsoft Copilot. | Windows, Edge, Bing. | Bing shopping data, Microsoft Merchant Center, websites. |
| Perplexity shopping. | Perplexity apps. | Partner catalogues and web pages. |
| Amazon’s assistant. | Amazon app and Alexa devices. | Amazon’s own catalogue and reviews. |
What actually shipped, and what didn’t
Agentic commerce has had a lot of announcements and a few quiet retreats. Knowing the difference saves merchants from spending money on things that don’t matter yet.
| When. | What happened. | What it means for merchants. |
|---|---|---|
| Sept 2025. | OpenAI and Stripe launched the Agentic Commerce Protocol (ACP) and Instant Checkout in ChatGPT, starting with Etsy sellers. | First large test of buying inside a chat. |
| Sept 2025. | Google announced AP2, a protocol for agents to make payments with the user’s permission. | Groundwork for safe agent payments. |
| Jan 2026. | Google and Shopify announced the Universal Commerce Protocol (UCP) with retailers including Walmart, Target, Etsy and Wayfair. | An open standard for agents to read catalogues, build carts and hand off. |
| Mar 2026. | Instant Checkout in ChatGPT was scaled back after weak sales; ACP continues as infrastructure for apps. | Buyers still prefer to pay on merchant sites. |
| Mar 2026. | Shopify turned on Agentic Storefronts by default for eligible merchants. | Many Shopify stores became visible to assistants automatically. |
| 2026. | Amazon expanded its assistant with features to buy on the user’s behalf, keeping transactions inside Amazon. | Marketplace listings matter even more. |
The pattern that settled is simple: discover in the assistant, buy on the site. Assistants have taken over much of the research that used to happen on category pages and comparison blogs. People still mostly pay where they already trust the checkout. Walmart said openly that buying inside the chat converted far worse than sending shoppers to walmart.com.
Details in this space change month to month. We re-check each platform’s documentation before every project and treat vendor claims about conversion rates as unverified until we see real data.
What this means in practice
For most merchants, the priority isn’t building an in-chat checkout. It’s making sure agents can find, understand and trust your products, and that the handoff to your site is smooth when they send a buyer over. That’s less exciting than the headlines and much more useful.
Why buyers are shifting
Online shopping has a research problem. A buyer looking for a washing machine faces hundreds of models, confusing specs, sponsored listings and reviews they’re not sure they can trust. Comparison takes hours. Type “front load, 7 kg, good for hard water, under ₹35,000, delivery in Lucknow this week” and get three sensible picks back. That’s hours saved.
A few things made this practical in 2025 and 2026:
- The assistants simply got better at reading product data and following fussy requests.
- Google, OpenAI, Microsoft and Amazon connected their assistants to live product catalogues.
- Platforms like Shopify opened their merchants’ catalogues to agents by default.
- Payment firms worked out how agents can pay safely, with the user’s say-so.
Plenty of people still love browsing, of course. For bigger purchases, though, like a fridge, a sofa or a wedding gift, more of the homework now happens inside an assistant. Sell those things and your product data is now part of the shop window.
The protocols, explained plainly
“Protocol” just means two systems have agreed how to talk. For shopping agents, it covers how the assistant reads your catalogue, fills a cart, hands over payment and tells you about the order. Skip the technical bits if you like. Knowing roughly what each does is enough to quiz your developer or platform.
| Protocol. | Backed by. | What it does in simple terms. | Who should care. |
|---|---|---|---|
| Universal Commerce Protocol (UCP). | Google, Shopify and major retailers. | Lets agents read products, build carts and hand buyers to the merchant’s checkout. | Shopify merchants and anyone selling through Google’s AI surfaces. |
| Agentic Commerce Protocol (ACP). | OpenAI and Stripe. | Lets agents pass orders and secure payment tokens to merchants, used in ChatGPT apps. | Merchants on Stripe looking at ChatGPT. |
| AP2 (Agent Payments Protocol). | Started by Google, now under the FIDO Alliance. | Creates signed proof that a user approved a purchase, so payments by agents can be trusted. | Payment providers, banks and large merchants. |
| Model Context Protocol (MCP). | Started by Anthropic, widely adopted. | A general way for AI assistants to connect to tools and data, including store catalogues. | Merchants building their own assistant integrations. |
Do you need to implement these yourself?
Usually not directly. If you’re on Shopify, much of UCP support comes through the platform. On Stripe, the ACP options show up in your Stripe dashboard. WooCommerce, Magento and home-built stores rely on plugins and payment partners, and support is patchy. The standards also stack rather than compete: a merchant can be readable through UCP, accept payments that use AP2 mandates and still support ACP for ChatGPT apps.
For businesses in India, there’s an extra layer. UPI dominates digital payments, and NPCI with partners has been piloting agent-initiated UPI payments. Cash on delivery is still common. Global protocols will need to work with these local habits, and that’s still being sorted out. Our Universal Commerce Protocol service tracks what’s live in each market.
A sensible order: get your product data right first, then turn on whatever agent features your platform already offers, and only then consider custom protocol work.
What you can check yourself this week
You don’t need an agency to start. These checks take an afternoon and show where you stand.
Ask the assistants
Open ChatGPT, Gemini and Copilot. Ask five questions your buyers would ask, budget and city included. Note which brands come up and whether you’re one of them.
Open Merchant Center
Look at the diagnostics page. How many products are disapproved or have warnings? What are the top three reasons?
Compare ten products
Pick ten products and compare the feed price and stock with your live site. Any difference is a problem worth fixing first.
Read your titles aloud
Would a stranger know what each product is from the title alone? If not, agents won’t either.
Test a variant link
Copy the link for one size or colour and open it in an incognito window. Does it show that exact variant?
Check robots.txt and bot protection
Make sure Googlebot, bingbot and AI search crawlers aren’t blocked from product pages.
If most of these look fine, you’re ahead of many stores. If several fail, those are your first fixes.
Product feed readiness
A product feed is basically a big spreadsheet of your products: title, price, stock, pictures, brand, barcodes, shipping and so on. Google and Microsoft Merchant Center read it, so does Meta, and so do most AI shopping tools. Feed accuracy used to be a hygiene task for the ads team. With agents, it decides whether you’re eligible to be recommended at all.
The fields that matter most to agents
| Field. | Why agents care. | Common mistake. |
|---|---|---|
| Price and sale price. | Budget filters drop anything that doesn’t fit. | Feed price different from site price. |
| Availability. | Agents avoid recommending out-of-stock items. | Feed updated once a day while stock changes hourly. |
| Shipping cost and speed. | “Delivered by Saturday” questions need this. | Shipping left blank or set as one national rate. |
| GTIN, brand, MPN. | Helps agents match your product to reviews and comparisons. | Missing or invented barcodes. |
| Detailed attributes. | Size, colour, material, wattage, compatibility answer specific questions. | Only the basic required fields filled in. |
| Return policy. | Agents and buyers compare it. | Not set in Merchant Center. |
| Images. | Shown in product cards. Checked against the title. | Watermarks, text overlays, low resolution. |
Keeping it fresh
Stale data is the most common problem we find. A feed that updates once a night can’t keep up with a festive sale where stock moves every few minutes. Options include more frequent scheduled fetches, Merchant Center’s API for instant updates, and structured data on product pages that Google can read when it crawls. Shopify and most newer platforms sync on their own. Custom builds and ERPs are usually the ones lagging behind.
Checking feed health
- Merchant Center diagnostics: disapproved items, warnings, price and availability mismatches.
- A sample of 20 products checked by hand against the live site every month.
- Price and stock spot checks during sales, when mismatches cause the most damage.
Our product feed readiness service does this audit and the fixes. Our e-commerce SEO work covers the site side.
Feed details that matter in India
Indian e-commerce has habits that global feed guides often skip. Getting these right helps both buyers and the agents answering their questions.
- Prices including GST. Indian consumers expect tax-inclusive prices. The feed price should match what the buyer pays before shipping.
- MRP and selling price. Packaged goods must show MRP under Legal Metrology rules. Show MRP and your price the same way everywhere and you avoid mismatches and confused buyers.
- Delivery by pin code. Delivery time can vary from one day in metros to a week in smaller towns. Region-based shipping settings in Merchant Center let agents answer “when will it reach me?” more honestly.
- Cash on delivery. Many buyers filter for COD. Stating availability and any COD charges clearly helps.
- Hindi and regional names. People search “kurti”, “chappal”, “tawa” and “dhurrie”. Including common local names in titles or descriptions, where natural, helps matching.
- Country of origin. Required on many marketplaces in India and more and more asked about by buyers.
Product content agents can use
Feeds give agents the facts. Product pages and descriptions give them the context to match a product to a real need. A buyer rarely asks for “SKU 4471-B”. They ask for “a lightweight cotton kurta for office wear in Jaipur summer, under ₹1,500”. Products whose pages answer that sort of question plainly are the ones that win.
Titles
Say what it is first. Then the details shoppers in that category care about. “Cotton A-line kurta, women, block print, sleeveless, indigo” beats “Summer Breeze Collection Style 22”. Brand names that mean nothing to new buyers belong later in the title.
Descriptions
Write for the questions people ask. Who is it for? What problem does it solve? What’s it made of? How do you care for it? What’s in the box? What doesn’t it do? Honest limits help: “not suitable for commercial kitchens” stops wrong buyers and makes the agent’s recommendation more reliable.
Specifications
Put specs in a clear table, using standard units. Agents compare wattage, capacity, dimensions and weight across brands. Missing specs often mean being left out of comparisons.
Reviews and questions
Agents read reviews to judge quality and fit, much like you do. A steady trickle of real reviews, with you replying politely to the grumbles, beats a handful of perfect five-stars. Customer questions and answers on the page also feed agents useful detail. Never write fake reviews. Besides being dishonest, India’s consumer protection framework has rules on online reviews, and platforms remove them.
Hard for agents to use
“Experience luxury like never before with our premium, world-class mixer. Perfect for every kitchen!”
Easy to use
“750W motor, 3 stainless steel jars (1.5 L, 1 L, 0.4 L), 5-year motor warranty, 2-year product warranty. Suited to Indian wet grinding like idli and dosa batter.”
Our shopping feed content service rewrites titles, descriptions and attributes at scale, with people checking the output.
Structured data on product pages
Structured data is a bit of hidden code, usually JSON-LD, that spells out for machines what’s on the page. For products, Schema.org’s Product and Offer types cover the name, brand, price, currency, stock, shipping, returns and reviews.
Google uses it for star ratings and prices in results, and to double-check your feed. Assistants that read pages directly get clean facts from it too. The rules are simple:
- Mark up only what’s visible on the page. Mark up things that aren’t on the page, or inflate them, and Google can penalise you.
- Prices and stock in the code must match the page and the feed.
- Include shipping and return details where Google supports them.
- Test with Google’s Rich Results Test after changes.
Most store platforms add basic product schema for you. What’s usually missing is shipping, returns, barcodes and variants, and that’s where we dig in.
Technical access for shopping agents
Agents need to reach your product pages to read prices, specs and reviews. Several technical issues quietly stop them:
- Bot protection that’s too strict. Some CDN and firewall settings block or challenge any automated visitor, including Google’s and Microsoft’s crawlers and AI search agents.
- Prices loaded by JavaScript only. If the price appears only after scripts run, agents that read raw HTML may see no price.
- Location pop-ups. A forced pin code or city selector before showing products can block crawlers from seeing anything.
- Slow pages. On Big Billion Days, a page that takes eight seconds to load may as well not exist for a crawler.
- Broken canonical tags. Variants pointing to the wrong canonical URL confuse which page is the real product.
Our technical SEO team checks these as part of the audit.
Using AI to improve product data at scale
A store with 5,000 products can’t rewrite every title by hand in a week. AI tools help, as long as they work from real data and people check the output.
Here’s a sensible way to do it:
- Start from facts. Hand the AI the supplier’s spec sheet, current attributes and photos. A product name alone isn’t enough. Its job is to tidy facts, never to invent them.
- Use templates per category. A title pattern for sarees differs from one for phone cases. Agree the pattern first.
- Fill attributes from descriptions. It’s very good at fishing “fabric: cotton” or “capacity: 1.5 L” out of a messy paragraph and dropping it into the right field.
- Flag gaps instead of guessing. If a spec is missing, the output should say “unknown” so someone can check, not make up a number.
- Review a sample. Check at least one in twenty products by hand, and every product in regulated categories.
- Roll out in batches. Update the top-selling products first, watch Merchant Center for problems, then continue.
Done this way, a large catalogue can be cleaned up in weeks rather than months, without filling it with errors that agents will repeat to buyers.
Checkout, payments and handoff
Most agent trips end with the shopper landing on your site. So the handoff is where you win or lose the sale. Someone arriving from an assistant has already decided, more or less. They want that exact product, at that price, and a quick way to pay.
What a good handoff looks like
Deep links to the right variant
The link opens the exact size and colour the agent recommended, not the home page or a generic category.
Matching price and stock
No surprises. If the price changed, the buyer should see why, not just a different number.
Cart transfer where supported
Some agents can pass a ready cart to the merchant. Google added cart transfer to merchant sites in the US in 2026, with other countries to follow.
Fast checkout
Guest checkout, saved addresses, UPI and wallets in India, cards and local methods elsewhere. Every extra step loses buyers.
Clear delivery and returns
Delivery date by pin code and a short return policy right on the checkout page.
Payments and trust
When an agent buys on someone’s behalf, the merchant needs to know the buyer really approved it. That’s what tokenised payments and protocols like AP2 aim to handle: the agent never sees card details. And there’s a signed record of what the user agreed to. Payment providers such as Stripe, Adyen and others have started supporting these. For Indian merchants, payment gateways like Razorpay, PayU and Cashfree are the ones to ask about agent-ready options, since UPI rules from NPCI and RBI shape what’s possible.
Fraud and returns
Agent orders bring new questions. What if the agent misunderstood and ordered the wrong size? Who’s responsible? Send a clear confirmation, allow easy cancellation for a while, and keep returns fair. Everybody’s protected. We help set these up with your operations team. See our checkout and handoff service and our conversion rate optimization work for the site side.
Images and video for agents
Assistants show your pictures in their answers, and some compare the image with the title to catch mismatches. Poor photos hurt twice. The agent trusts you less, and the shopper scrolls past anyway.
- A clean main image on a plain background, showing the actual product, with no text or watermarks.
- Extra images showing scale, details, packaging and the product in use.
- One image per variant, so the green option actually shows green.
- Fast-loading formats such as WebP on your site, while keeping high-resolution originals for feeds.
- Short demo videos for products where use matters, like appliances and tools.
- Descriptive alt text that says what’s in the image, which also helps accessibility.
Store policies agents can read
Buyers ask assistants things like “which store has free returns on shoes?” or “does this seller offer installation?”. Agents answer from whatever policy text they can find. Vague or buried policies lose you sales.
- Write shipping, returns, warranty and cancellation policies in plain language on dedicated pages, as text rather than images or PDFs.
- State the key numbers clearly: return window in days, who pays return shipping, refund time, warranty length.
- Enter the same details in Merchant Center’s return and shipping settings.
- Keep the policy the same on your site and marketplaces, or say clearly why it differs.
- Link policies from every product page and the checkout.
Clear policies also reduce support questions and disputes, so the work pays off even without agents.
Marketplaces and agents
A big slice of Indian online shopping happens on Amazon and Flipkart, and both are building their own AI shopping helpers. Those helpers only read their own catalogue, reviews and seller data. Your listing quality on each marketplace decides whether their assistant recommends you.
What marketplace assistants look at
- Complete listings: every attribute filled, not just the mandatory ones.
- Images and video: clear, multiple angles, with lifestyle shots where they help.
- Reviews and ratings: volume, recency and how the seller handles complaints.
- Questions answered: customer Q&A on the listing is read by the assistant.
- Delivery promise: fulfilment by the marketplace usually means faster, more reliable delivery dates.
- Price and stock stability: frequent stock-outs hurt ranking and recommendations.
Amazon’s assistant and buy-for-me features
Amazon has expanded its shopping assistant with features that can buy on a user’s behalf, including from some brands’ own websites in certain markets. The transaction mostly stays in Amazon’s world. For brands, this means Amazon listings, brand store content and A+ content matter as much as their own site.
ONDC and open networks
India’s Open Network for Digital Commerce lets sellers list once and be found through many buyer apps. As agents grow, open catalogues like this could become another source assistants read. It’s worth keeping ONDC listings accurate if you’re on the network.
Our marketplace agent readiness service and our marketplace marketing team work on listings together.
Measuring agent traffic
Attribution breaks quietly with agents. When an assistant reads your catalogue and sends a buyer straight to a product page, there may be no useful referrer. The sale shows up as “direct” or gets credited to whatever channel touched the buyer last. A channel that’s working can look like nothing at all.
What we track
| Signal. | How. |
|---|---|
| Referrals from assistant domains. | chatgpt.com, perplexity.ai, gemini.google.com, copilot.microsoft.com as sources in GA4. |
| UTM tags on feed links. | Where platforms allow, tagged URLs in feeds show which agent sent the click. |
| Agent bot visits. | Server logs and CDN reports show which agents read product pages. |
| Landing on deep product URLs as “direct”. | A rise in direct visits to deep product pages often signals agent traffic. |
| Post-purchase survey. | “How did you find us?” with AI assistant as an option. |
| Merchant Center reports. | Performance in Google’s shopping surfaces, including AI features where reported. |
Why the value per visit differs
Agent-referred visitors behave differently. They’ve already compared options, so they often know what they want. Walmart reported assistant referrals brought about twice the new-customer rate of search engines, even where conversion was lower. Judging this channel by conversion rate alone can undervalue it. We look at new-customer rate, order value and repeat purchases too. Our agent attribution service builds this measurement.
Reviews and reputation across agents
Agents don’t only read your product pages. They read what people say about you all over: Google reviews, Flipkart stars, Reddit threads, YouTube comparisons, the odd news piece. Brilliant specs won’t save a product whose reviews keep mentioning late delivery or rude service.
What helps:
- Ask every buyer for a review at the right time, after they’ve used the product, not the day it ships.
- Reply to negative reviews calmly and fix the underlying issue where you can.
- Put warranty and service details somewhere obvious. Agents look for them.
- Send products to honest reviewers and creators, without paying for positive verdicts.
- Keep seller ratings healthy on every marketplace, because they feed the marketplace’s own assistant.
Reputation can’t be faked for long. Since agents read so widely, the surest way to look good to them is boringly simple: treat customers well.
Tracking how assistants describe your products
Alongside traffic data, we run a fixed set of shopping questions on each assistant every month. For each answer we note whether your products appear, at what price, in which position, and what reasons the assistant gives. Those reasons are useful. If an assistant says a competitor is “better for hard water” or “has a longer warranty”, that tells you exactly what buyers and agents are comparing. And where your product data or the product itself may be falling short.
We also note mistakes, such as wrong prices, discontinued models or old policies, and trace them back to the source. Usually it’s a stale feed, an old marketplace listing or a review site that hasn’t updated. Fixing the source fixes the answer over the following weeks.
How we run it
There’s no standard agentic commerce package, because every store’s starting point differs. The order of work, though, stays roughly the same.
- Week 1
Shopping prompt baseline
We ask the major assistants the questions your buyers ask and record which products and stores they suggest, at what prices, and with what reasons.
- Week 1–2
Feed health audit
Merchant Center diagnostics, field completeness, price and stock accuracy, update frequency, shipping and returns setup.
- Week 2
Site and structured data check
Product schema, variant handling, page speed, crawl access for shopping agents, deep-link behaviour.
- Week 2–3
Platform and protocol review
What your platform supports now (Shopify Agentic Storefronts, UCP, ACP options, payment provider features) and what’s worth turning on.
- Month 1–3
Fixes and content
Feed fixes first, then titles, descriptions and attributes for priority products, then checkout and handoff improvements.
- Ongoing
Measure and repeat
Monthly prompt runs, attribution reports, feed health checks, and updates as platforms change.
What gets handed over
- A feed that passes diagnostics.
- Priority products with complete attributes.
- Product schema matching feed and site.
- A shopping prompt set and baseline.
- Attribution set up for agent traffic.
- A plain-language note on which protocols apply to you.
What it cannot do
We can’t make an assistant suggest a product that’s overpriced, poorly reviewed or often out of stock. Agents are designed to protect buyers, and that’s a good thing. The work makes strong products easy to find and understand. It doesn’t hide weak ones.
How long it takes and what it costs
| Work. | Typical time to see change. |
|---|---|
| Merchant Center disapproval fixes. | Days to two weeks. |
| Price and stock sync fixes. | Immediate once live. |
| Titles and attributes for priority products. | 2–8 weeks to show in answers. |
| Full catalogue content. | 1–3 months, depending on size. |
| Reviews and reputation. | Ongoing, months. |
| Attribution setup. | 2–4 weeks. |
Cost depends mostly on catalogue size and data quality. A store with 100 products and a healthy feed might need a short audit and a few fixes. A store with 20,000 products from several suppliers, inconsistent attributes and an ERP that doesn’t talk to the feed needs ongoing work. We scope after the audit, once we know what’s actually broken.
Three examples
These are composite scenarios based on common situations, not specific client results.
The brand sells about 400 products. In Gemini and ChatGPT, questions like “hand block printed cotton kurta under ₹2,000” bring up larger brands, never theirs. The audit finds Merchant Center disapprovals on a third of products for missing GTINs and image text overlays, titles built around collection names. And no fabric or care details in the feed.
The fix: products marked as handmade without GTINs where that’s allowed, images cleaned, titles rewritten to lead with product type, fabric and print. And attributes like fabric, sleeve length and occasion filled in. Shopify’s agent features were already on, but bad data had kept them from helping. After about three months, the brand appears in several of the tracked prompts and Merchant Center clicks rise.
The seller runs its own WooCommerce site and sells on Amazon and Flipkart. Its feed updates once a night. So during sales, assistants keep showing products that are sold out, and buyers land on “out of stock” pages. Moving to hourly feed updates plus instant updates through the Merchant Center API for fast-moving items. And fixing variant links so each colour opens correctly, cuts those dead-end visits sharply.
Ratings are great, but the listings are thin: no jar sizes, no years on the motor warranty, nothing about compatibility. So for detailed questions, Amazon’s assistant keeps sending people to rivals. Filling every attribute, adding A+ content with comparison charts, answering the top customer questions and adding short demo videos makes the listings far more complete. The brand starts showing up in assistant answers for specific questions like “mixer for idli batter with 5-year warranty”.
How it varies by product category
| Category. | What agents weigh most. | Key data to get right. |
|---|---|---|
| Electronics and appliances. | Specs, warranty, ratings, compatibility. | Full spec tables, warranty terms, model numbers, GTINs. |
| Fashion and apparel. | Fit, fabric, style, returns. | Size charts, fabric, occasion, colour names that match images. |
| Beauty and personal care. | Ingredients, skin type, reviews. | Ingredient lists, suitability, certifications, expiry and batch info. |
| Grocery and FMCG. | Price per unit, delivery speed. | Pack size, unit price, delivery slots by pin code. |
| Furniture and home. | Dimensions, material, delivery and assembly. | Exact sizes, materials, assembly info, delivery timelines. |
| Handmade and crafts. | Authenticity, story, uniqueness. | Maker details, technique, origin, care instructions. |
For regulated categories like supplements, medicines and baby food, assistants are more cautious, and labelling rules apply. Product claims must match what’s legally allowed and printed on the pack.
Selling across borders
Lots of Indian brands now sell overseas: block prints, silver jewellery, Ayurveda, spices. Each country’s agents read local feeds and follow local rules, so exporters need extra care.
- Separate feeds per country with prices in local currency, local shipping times and correct duties details.
- Local language titles where the market expects them, not machine translations left unchecked.
- Country rules for product claims, especially for cosmetics, supplements and food, which vary widely.
- Returns policies that are realistic for international shipping, stated clearly.
- Payment methods buyers use in that market, which the agent may check before recommending.
Agent protocols are also rolling out country by country. Features like Google’s cart transfer started in the US. So what’s possible for a US buyer may not yet apply in India, the UK or the Gulf. We check per market.
Agents in B2B buying
Office buyers use assistants as well, usually Copilot or ChatGPT at their desk, to shortlist suppliers, compare specs and draft purchase requests. A purchase manager in Vapi might type:
For B2B sellers, agent readiness looks a little different:
- Product and capability pages with real specs, certifications, minimum order quantities and lead times.
- Accurate listings on IndiaMART, TradeIndia and industry directories, which assistants often cite.
- Downloadable spec sheets backed by the same facts as text on the page.
- Clear “request a quote” paths that work when a buyer arrives from an assistant.
Our generative engine optimization service covers how B2B companies get cited in these research answers.
Agentic commerce checklist
Feed
- Merchant Center account healthy with few disapprovals.
- Prices and stock match the site at all times.
- Shipping costs and delivery times set.
- Return policy configured.
- GTIN, brand and MPN filled where they exist.
- Category-specific attributes complete.
- Feed updates at least as often as stock changes.
Site
- Product schema with price, stock, shipping and returns.
- Each variant has its own working URL.
- Product pages load quickly and work without heavy scripts.
- Shopping and search agents aren’t blocked.
- Guest checkout and local payment methods available.
Content
- Titles lead with product type and key attributes.
- Descriptions answer real buyer questions.
- Spec tables with standard units.
- Genuine reviews, with replies to complaints.
Measurement
- Assistant referrals tracked in analytics.
- Shopping prompt set run monthly.
- Post-purchase “how did you find us” survey includes AI.
- New-customer rate tracked by channel.
Common myths
Who should own product data
Ask “who owns our product data?” in most companies and you’ll get a long pause. Ads look after the feed, operations handles stock, the web team edits pages, and someone in purchasing adds new items to the ERP. Everyone edits their own copy, and within a month the copies disagree.
A simple governance setup helps:
- One source of truth for each field. For example: price from the ERP, descriptions from the website, stock from the warehouse software.
- One owner who checks feed health weekly and has authority to fix problems across teams.
- New product checklist so every new item launches with complete attributes, images and identifiers.
- Sale-day checks before big events like Diwali, Big Billion Days or Great Indian Festival, when mismatches hurt most.
- Monthly review of disapprovals, attribute gaps and agent visibility.
This doesn’t need a big team. In a small business, it might be one person spending two hours a week. The point is that someone owns it.
A feed audit, step by step
Here’s what a first audit might look like for a made-up Surat saree brand, “Tana Bana Weaves”, selling about 900 products on its own WooCommerce site.
Step 1: the shopping prompts
We write 30 questions buyers might ask: “Banarasi silk saree for wedding under ₹15,000”, “lightweight georgette saree for office”, “Kanjivaram style saree with blouse piece delivered to Bengaluru in 3 days”. Each runs on Gemini, AI Mode, ChatGPT and Copilot. Tana Bana appears in two answers, both on Gemini.
Step 2: Merchant Center
Out of 900 products, 610 pass, 190 carry warnings and 100 are rejected. Why? A sale plugin changes site prices but never touches the feed. Shipping settings are blank. Several photos have “FLAT 40% OFF” stamped on them.
Step 3: attributes
The feed has titles, prices and images, but no fabric, weave, occasion, length or blouse-piece details. Most product titles read like “TBW-SAR-0412 Pink”. An agent asked for “georgette saree for office” has nothing to match.
Step 4: the site
Product pages have basic schema without shipping or return details. Colour variants share one URL, so a link to the green version opens the pink one. Delivery time isn’t shown anywhere before checkout.
Step 5: the plan
Fix the sale plugin so feed prices update with the site. Set shipping rules by region in Merchant Center. Replace promotional images. Rewrite titles for the top 200 products first (“Georgette saree, office wear, lightweight, pink, with blouse piece”). Add fabric, weave, occasion and length as feed attributes. Give each variant its own URL. Show estimated delivery by pin code on product pages. Re-run the prompts after six to eight weeks.
Mistakes we see often
- Chasing protocols before fixing data. A fancy integration on top of a broken feed sends agents wrong details faster.
- Feed prices that lag the site. The most common reason products get disapproved or recommended at the wrong price.
- Ignoring shipping and returns fields. Agents answer “delivered by Friday?” and “easy returns?” with these.
- Creative brand titles. Clever names mean nothing to an agent matching a specific need.
- One URL for all variants. Agents send buyers to the wrong colour or size.
- Blocking shopping bots. Aggressive bot protection can stop agents from reading product pages.
- Judging the channel by last-click data. Agent influence often shows up as “direct”, so it gets undervalued and cut.
Agentic commerce for service businesses
It isn’t only products. Assistants are starting to book tables, compare hotels, find a salon with a free slot on Saturday and fix appointments. Service businesses play by the same rules: clear, machine-readable details about what you offer, when, where and for how much.
- Restaurants: menus with prices on the website as text (not just images), opening hours on every listing, booking links that work.
- Hotels and homestays: room types, rates and availability through booking platforms and your own site, with clear policies.
- Clinics and salons: services, prices and online booking that an assistant can link to directly.
- Coaching and courses: fees, batch dates, duration and enrolment links clearly stated.
Our AI platform optimization service covers how each assistant finds this details.
What’s changing next
A few developments are worth watching over the next year or two.
- More agents with permission to buy. As payment standards mature, assistants will complete more purchases within limits users set, such as “reorder detergent when it runs low, up to ₹500”.
- Agent-to-agent negotiation. Some businesses are testing their own agents that answer questions from shopping agents about stock, bulk pricing or custom orders.
- Ads inside AI shopping answers. Google already shows ads in AI Mode and AI Overviews, and others are testing. Paid and organic will sit side by side.
- Voice shopping in Indian languages. As assistants handle Hindi and regional languages better, more first-time online buyers may shop by voice.
- Stronger consumer protection. Regulators will likely set rules on who’s responsible when an agent buys the wrong thing. Clear policies now will make that transition easier.
The basics will stay the same through all of this: accurate data, honest content, a trusted checkout and good treatment of buyers.
Common questions about agentic commerce
Do we need to support checkout inside the assistant?
Not right now for most merchants. In-chat checkout was tried and largely scaled back in 2026, because buyers prefer to pay where they already trust the checkout. Focus on accurate data and a smooth handoff to your site. Turn on in-assistant buying when your platform supports it and your buyers use it.
We’re on Shopify. Are we already covered?
Partly. Shopify turned on agent features for eligible stores, which makes your products available to assistants. But they still rely on your product data. Missing attributes, weak titles and wrong stock will hold you back even with the features on.
What about WooCommerce or a custom store?
You’ll rely more on your Merchant Center feed, structured data and plugins. Support for UCP and ACP depends on your payment provider and plugins. We check what’s available for your setup.
How is this different from Google Shopping ads?
Shopping ads are paid placements. Agentic commerce is about being recommended in AI answers, mostly organically. They use much of the same feed, so fixing data helps both.
Can a small brand compete with big retailers in AI answers?
Often, yes, especially on specific questions. An agent asked for “handwoven cotton dhurrie 5×7 for a living room” looks for the best match, not the biggest brand. Clear data and good reviews matter more than size.
How do we know if agents are sending us sales?
Track referrals from assistant domains, watch direct traffic to deep product pages, tag feed links where possible and ask buyers how they found you. Expect the numbers to be undercounted.
Is buying through an AI agent safe for customers?
The new payment standards are designed so agents never see card details and every purchase has a record of user approval. Merchants should still send clear confirmations and make cancellations easy, in case an agent misunderstood.
How does this work in India with UPI and cash on delivery?
Most agent journeys still end on the merchant’s site or app, where UPI, cards and COD work as usual. Agent-initiated UPI payments have been piloted, and wider options will depend on NPCI and RBI rules. We keep checking what’s live.
How long until we see results?
Feed fixes can show in Merchant Center within days and in AI answers within weeks. Content improvements for large catalogues take longer, usually one to three months for priority products.
What does it cost?
It depends on catalogue size, platform and how much data needs fixing. A small store may need a one-time audit and fixes. Large catalogues need ongoing feed management. See our pricing page for how we scope work.
Should we block AI agents from our store?
Blocking AI search and shopping agents removes your products from their answers. Some stores block training crawlers while allowing search agents. For most merchants who want sales, allowing shopping and search agents makes sense.
Will agents replace our website?
No. Most purchases still finish on merchant sites and apps, and buyers often visit a site to check details before paying. Your site becomes the place where agent-referred buyers confirm and pay, so it needs to be fast and trustworthy.
Do marketplaces and our own site need different work?
The principles are the same: complete, accurate data and good reviews. The execution differs. Marketplaces have their own listing fields and assistant, while your site depends on Merchant Center, structured data and open agent protocols.
Can you help if our catalogue lives in an ERP?
Yes. Many feed problems start in ERPs that weren’t designed for e-commerce. We work with your IT team or ERP partner to map fields, set update frequency and fill gaps in a layer between the ERP and the feed.
Where should a small store start?
Start with Merchant Center. Fix disapprovals, make sure prices and stock match your site, and set shipping and returns. Then rewrite titles and fill attributes for your 20 best-selling products. Those two steps cover most of what agents need, and they cost little beyond time.
Inside Agentic Commerce
The specific pieces of work this service is made of, each scoped separately.
Product feed readiness
Make the catalogue an assistant reads accurate enough that it recommends you rather than working around you.
Product feed readinessUniversal Commerce Protocol setup
Get your catalogue into the protocol Google and Shopify built for agents, properly.
Universal Commerce Protocol setupAgent traffic attribution
See the revenue assistants are sending you, which currently arrives looking like direct traffic.
Agent traffic attributionShopping content for assistants
Write product data for the machine doing the comparing, not only for the person doing the browsing.
Shopping content for assistantsMarketplace agent readiness
Be answerable inside the marketplaces that now have assistants of their own.
Marketplace agent readinessCheckout and agent handoff
Make the journey from an assistant to a completed purchase on your own site as short as it can be.
Checkout and agent handoffAgentic Commerce by industry
The same discipline, with each sector’s own buyers, rules and measures.
Other services
- Generative Engine Optimization
- Answer Engine Optimization
- Technical SEO
- Entity and Semantic SEO
- Local SEO
- Ecommerce SEO
- Digital PR and Link Building
- Google Ads Management
- Paid Social and Meta Ads
- Conversion Rate Optimization
- Website Design and Development
- AI Automation and Workflows
- AI Platform Optimization
- App Store Optimization
- Marketplace Marketing
- Content and Editorial
- Lifecycle and Email
- Analytics and Measurement
- Brand and Creative
Ask us to look at your agentic commerce setup
We look before the call, so the call is about findings rather than introductions.
Ask what we would do first, and why
Tell us what you have already tried. Knowing what failed narrows this down faster than anything else.
