On June 24, 2026, Salesforce announced that Agentforce Commerce reached general availability. Three agents — Shopper Agent, Buyer Agent, and Merchant Agent — are activatable today by any Salesforce Commerce customer. Each one is, in Salesforce's own words, "wired natively into your catalog, inventory, and orders from the first day."
That phrase makes data readiness part of the activation decision: the quality of customer-facing answers depends on the records and integrations available to the agents.
What Salesforce Released on June 24
According to Salesforce's announcement, the three generally available agents each carry distinct data dependencies:
Shopper Agent checks real inventory, confirms carrier cutoffs, offers store pickup, and closes the sale within a single conversation. Those actions depend on current inventory and fulfillment records. As a Metrotechs risk scenario, stale inventory or carrier-cutoff data could lead to a commitment the fulfillment team cannot meet.
Buyer Agent handles B2B procurement over WhatsApp and SMS — including SKU confirmation via image and contract pricing — without requiring a portal login. That detail matters: the agent surfaces contract and account-specific pricing directly in a messaging thread. If that pricing lives only in your ERP and is not synchronized to Salesforce, the Buyer Agent may be unable to apply the correct contract price. This is a Metrotechs risk scenario based on the announced data dependencies.
Merchant Agent lets teams organize catalogs, create boost/bury rules, and tune sort orders using natural language. The agent executes those changes against your catalog structure. If catalog data quality or change governance is weak, a natural-language change could spread an existing catalog error. This is a Metrotechs risk scenario, not a vendor-documented outcome.
Salesforce also confirmed a direct integration with OpenAI that syncs sellers' product catalogs to ChatGPT "without extra software or third-party tools," with the retailer remaining merchant of record for all resulting orders. That sync is only as accurate as the catalog it reads.
Salesforce confirmed Agentforce Commerce includes full headless flexibility for B2B commerce, allowing businesses to use the agent capabilities without a Salesforce storefront. Businesses running a custom storefront or a third-party front end are not exempt from these data dependencies.
What the GA Date Actually Changes
General availability means the feature is available to enable — not that it's enabled, not that it's been tested against your data, and not that your records are ready for it. Before activation, test how your configuration handles incomplete records, stale integrations, and failed lookups.
Salesforce cited in its announcement that AI influenced 20% of global online sales worth $262 billion during the 2025 holiday season. Treat that figure as vendor context rather than independent evidence of readiness or business impact.
Digital Commerce 360 reported on June 25, 2026 that 78 of the Top 2000 North American online retailers use Salesforce as their ecommerce platform, combining for more than $192.60 billion in web sales in 2025. The figures show the scale of the Salesforce commerce footprint; they do not establish readiness for any individual business.
The Data Split Problem That Can Surface When Agents Go LivernrnMetrotechs analysis: If catalog, inventory, pricing, and order records operate across Salesforce, an ERP, a WMS, or a PIM, discrepancies between those systems could become customer-facing when agents are enabled.
Catalog attributes and descriptions may live in a PIM that syncs to Salesforce on a scheduled batch. Inventory availability may be mastered in a WMS with a sync frequency measured in minutes or hours, not seconds. Order history may be split across channels, with some fulfillment paths not writing back to Salesforce as the merchant of record.
The operational change is that enabled agents can expose those records during customer conversations without the same review points as a traditional storefront.
If your Buyer Agent quotes list price because contract pricing isn't reflected in Salesforce, you may have a pricing dispute before the order is placed. This is Metrotechs analysis based on the native data architecture Salesforce has described for Agentforce Commerce; your actual exposure depends on your sync frequency, system-of-record assignments, and integration design.
What to Audit Now
The following are Metrotechs recommendations based on the cited Agentforce Commerce architecture and data dependencies.
- Catalog completeness: What percentage of active SKUs have complete attributes, accurate descriptions, and current pricing in Salesforce? Incomplete records may lead to incomplete or incorrect agent responses.
- Inventory feed latency and accuracy: What is the actual sync frequency between your ERP or WMS and Salesforce Commerce Cloud? Measure actual latency, not scheduled frequency. Identify which SKUs or warehouse locations are excluded from the sync.
- Contract pricing ownership: Does account-specific and contract pricing live in Salesforce, or only in your ERP? Before enabling the B2B Buyer Agent, verify how it resolves contract pricing and handles a failed lookup.
- Order data ownership: Do all active fulfillment channels write orders back to Salesforce as the merchant of record? Channels that do not reconcile to Salesforce could create gaps in order history, loyalty data, and account context.
- Data split across systems: Which catalog, pricing, or inventory records exist only in your ERP, WMS, or PIM with no live sync to Salesforce?
- ChatGPT catalog sync: If you enable the OpenAI integration, the product catalog exported to ChatGPT reflects whatever is in Salesforce at sync time. Verify that current pricing, availability, and fulfillment rules are accurate in Salesforce before that sync runs.
- Agent governance: Who owns boost/bury rules and sort-order configurations? Does a change-control process exist before the Merchant Agent can execute catalog changes? Apply the same change-control and ownership rules to natural-language catalog changes as to other production configuration changes.
What to Watch
Salesforce says Google Search, including AI Mode, and Gemini integrations are planned for summer 2026. Review the official configuration guidance for each channel before enabling it.
Metrotechs analysis: Buyer Agent interactions over WhatsApp and SMS may introduce a customer path your team has not instrumented or monitored. Before production use, verify pricing access controls, order logging, escalation handling, and integration monitoring for those channels.