# Agentforce Commerce just went GA: what it means for your product pages Salesforce's Agentforce Commerce is now live, plugged natively into ChatGPT, Google AI Mode and Gemini. Here is what the GA actually changes for brands trying to win a sale through an AI agent. By Rohin Aggarwal · 2026-07-30 Salesforce shipped Agentforce Commerce to general availability on 6 July 2026, with native integrations into ChatGPT, Google AI Mode and Gemini. The announcement was covered widely in the CRM and platform press. Almost nobody wrote about what it means for the product page, which is the part that actually touches the shopper. **Quick answer** - Salesforce Agentforce Commerce went GA on 6 July 2026, natively integrated with ChatGPT Shopping, Google AI Mode and Gemini. - Agent-facilitated commerce spend is projected to triple by 2030, per Salesforce research. - Agents read your PDP evidence to form a recommendation. A thin PDP loses that recommendation to a competitor with richer content. - UGC (video reviews, tagged posts, Q&A) is the highest-trust evidence type for agent recommendations because it comes from verified buyers, not from the brand. - Idukki feeds UGC directly into the llms.txt + MCP layer that AI agents read. This is how you show up before someone asks your sales team. The Agentforce Commerce GA is not a product launch you need to buy into. It is an infrastructure shift in how shoppers discover and evaluate products. A growing share of purchase journeys now run through an AI agent that reads, synthesises and recommends, rather than through a search results page the shopper scrolls manually. The GA means that pipeline is now production, not beta. ## What the GA actually changed Before July 2026, Agentforce Commerce was available in limited release. The GA opens it to all Salesforce Commerce Cloud and Einstein licences and, more significantly, wires it natively to three of the highest-traffic AI surfaces: ChatGPT Shopping, Google AI Mode and Gemini. A shopper asking "which running shoe suits wide feet for trail running under £100" on any of those surfaces can now receive a Salesforce-powered recommendation that resolves to a specific product at a specific retailer. The agent does not browse your site. It reads the structured data you have already published: product schema, review schema, llms.txt, any feed you syndicate. It assembles a recommendation from that, then routes the buyer. If your data is thin, the agent routes elsewhere. - **3×** — projected agent-facilitated spend by 2030 (Salesforce research, published at GA announcement) - **3 surfaces** — native integrations at GA: ChatGPT, AI Mode, Gemini (Salesforce Agentforce Commerce GA announcement, July 2026) - **$0** — ad spend to get cited by an agent (Agents read published structured data, not ad auctions) _The Agentforce commerce landscape as of GA._ ## What the agent actually reads on your PDP Every AI agent reading a product page is looking for the same thing a late-stage buyer looks for: evidence that the product does what it claims for a person like them. The hierarchy of evidence that agents cite, based on how retrieval systems weight trust signals: - Verified buyer reviews with structured attribution (author, date, product variant, verified purchase flag in JSON-LD) - Video and photo reviews that can be associated with a specific SKU - Q&A threads where the question maps to a real objection and the answer is attributed to a real person - Brand-written descriptions and spec sheets (lowest trust; agents deprioritise self-reported claims when third-party evidence is available) The pattern holds across all three surfaces now integrated at Agentforce GA. A brand that has published rich, structured UGC content (video reviews tagged to SKUs, Q&A with attributed answers, a properly formatted llms.txt) is feeding the agent the exact signal hierarchy it weights most. A brand that has only a product description and a star rating is competing on the weakest evidence tier. ## The PDP gap this creates The practical problem is not that agents exist. The practical problem is that most PDPs are not set up for agent retrieval. The evidence that agents weight highest (structured UGC, attributed Q&A, variant-level review data) is also the evidence that is hardest to publish correctly without a platform that generates it in the right format. **What an agent reads vs. what most PDPs actually publish** - **Hero — Brand-written: low agent trust:** Title, price, short description. Agent reads it but weights it below buyer evidence. - **Reviews band — Highest agent trust if structured:** Photo/video reviews with JSON-LD attribution. Most apps publish star counts, not structured reviews. - **Q&A section — High trust: objection resolution:** Attributed Q&A pairs. Rare on most PDPs; powerful when present. - **UGC gallery — High trust: social proof at scale:** Tagged posts, creator videos, shoppable clips. Rarely structured for agent consumption. - **Buy box / CTA — Conversion mechanism:** The destination the agent routes to. Irrelevant if the agent never recommends the product. ## How UGC is the answer, and why format matters UGC is the right answer to the Agentforce retrieval problem for a specific reason: it is the only type of content on a PDP that reads as independently verified. An agent trained to surface trustworthy evidence over promotional copy will consistently prefer a real customer's tagged video over a brand-written feature bullet, because the video is third-party by origin. The format caveat matters as much as the content itself. A UGC gallery of embedded Instagram clips that only loads client-side is invisible to the agent. Review content that lives in a JavaScript framework without a structured fallback gets missed. The content has to be published in a form the agent can read: JSON-LD for reviews and Q&A, a properly formatted llms.txt for the broader content map, an MCP endpoint for agents that request structured data directly. > **How Idukki feeds AI agents:** Idukki generates an llms.txt for every connected store (served at idukki.io/llms.txt for the platform itself) and exposes an MCP endpoint that AI agents can query for product-tagged UGC by SKU. This means a ChatGPT Shopping agent asking "show me verified buyer videos for SKU X" can resolve that query directly against the UGC dataset, not just the PDP HTML. ## Three things to check before the next agent read **Structured review JSON-LD on every PDP.** The Product schema block needs to include a review array with real attributed reviews (author, reviewBody, datePublished, verified flag). A star rating aggregate with no individual reviews attached gives agents nothing to quote. **UGC that is server-side readable.** If your gallery only renders after JavaScript executes, agents miss it. Either serve a structured feed (llms.txt, MCP) or confirm that your UGC platform renders structured HTML that crawlers reach without JS. **A Q&A block with attributed answers.** Q&A is the format that maps most directly to how a shopper prompts an agent ("does this fit wide feet", "is this suitable for outdoor use"). A structured Q&A with a real answer and a real person attached to it is the format agents quote. An FAQ section that is just a brand-written paragraph does not carry the same attribution weight. **In one line:** Agentforce Commerce GA means the agent-facilitated purchase path is now production infrastructure for three of the highest-traffic AI surfaces. The brands that show up in agent recommendations are the ones with structured buyer evidence on their PDPs, not the ones with the best ad creative. [The twelve JSON-LD shapes agents quote](/blog/twelve-json-ld-shapes-agents-quote) covers the specific markup needed to pass each evidence type through to AI retrieval. [The AEO 2026 playbook](/blog/answer-engine-optimisation-2026-playbook) has the full setup sequence if you are starting from a thin PDP. ### FAQ **Q: What is Salesforce Agentforce Commerce?** A: Agentforce Commerce is Salesforce's agentic shopping infrastructure: an AI layer that helps brands surface products and complete transactions through conversational AI agents. It went to general availability on 6 July 2026 with native integrations into ChatGPT Shopping, Google AI Mode and Gemini. **Q: Does Agentforce Commerce affect Shopify stores?** A: Yes, indirectly. Agentforce powers the recommendation layer across several AI surfaces that shoppers use regardless of where you are hosted. The agent reads your structured data (schema, llms.txt, review JSON-LD) rather than your Shopify admin, so the impact is on what is published on your public PDP, not on your platform choice. **Q: How do I make my products visible to AI agents?** A: Publish structured review JSON-LD on every PDP, ensure your UGC is server-side readable (not client-side-only JavaScript), add a Q&A block with attributed answers, and publish an llms.txt that maps your product catalogue. Idukki handles the UGC structured feed and llms.txt/MCP outputs automatically for connected stores. **Q: What does "agent-facilitated spend tripling by 2030" actually mean?** A: Salesforce research projects that a growing share of total commerce spend will originate from or be influenced by an AI agent interaction rather than a traditional search or browse session. Tripling by 2030 from the 2025 baseline is their published projection. It is a directional forecast, not a precise number, but the trend is consistent with how AI Mode, ChatGPT Shopping and Gemini are growing. ### Sources - Salesforce Agentforce Commerce GA announcement, July 6 2026 — GA date, native integrations (ChatGPT, Google AI Mode, Gemini), agent-facilitated spend projection - [Idukki: twelve JSON-LD shapes agents quote](/blog/twelve-json-ld-shapes-agents-quote) - [Idukki: AEO 2026 playbook](/blog/answer-engine-optimisation-2026-playbook) --- Canonical: https://idukki.io/blog/agentforce-commerce-ga-product-pages Tags: Agentforce, Agentic commerce, AI shopping, Product pages, Salesforce