shoppa vs Agentforce for Australian Retailers 2026

For shoppa vs Agentforce, choose shoppa when you want a shopping agent across storefront platforms with a two-line embed. Choose Agentforce when Salesforce already runs your commerce and service, and you want agents working through those shared records.

Both can help customers discover products and buy. The decision is how much of your shopping experience you want tied to Salesforce, and who manages the agent after launch.

What Agentforce Does for Retailers

Salesforce Agentforce is a platform for building and running AI agents across commerce, service and sales. Its agents use the business data and actions you connect to answer questions and complete tasks.

Agentforce Commerce is Salesforce’s commerce suite, also known as Commerce Cloud, with agents built around its storefronts and customer data. It covers consumer shopping and business purchasing, with order management and payments in the wider suite.

Salesforce’s commerce use-cases page names Shopping Assistant Agents, Recommendation Agents, Merchandising Agents, Inventory Agents, Checkout Agents and Post-Purchase Agents. These describe different jobs across the shopping journey. The features available on your store depend on the agent template and storefront you use.

Here are three retail uses from Salesforce’s own pages:

• A customer asks for products suited to their needs. Salesforce’s Commerce Use Cases page describes conversational guidance and recommendations using product data and customer context.
• A business buyer wants the same supplies again. Salesforce Help’s Guided Shopping for B2B Commerce documents past-order lookup, reordering and order-status answers.
• A customer needs a return resolved. Salesforce’s Agentforce Service Agent page describes handling product returns through a service conversation.

Agentforce for Service focuses on resolving enquiries and cases through Service Cloud. The service agent uses customer history and knowledge, and passes a conversation to a service representative when needed. The commerce shopping agent focuses on discovery, basket actions and purchasing. Those jobs can share Salesforce data, but a service licence alone doesn’t define your storefront’s shopping features.

Agentforce 360 is Salesforce’s name for its wider portfolio connecting business applications, agents and data. It covers more than one shopping agent or licence. Data 360 is the data layer previously called Data Cloud.

Salesforce documentation still contains Agentforce 1 Edition references. The Australian Agentforce pricing page now labels its bundled employee editions Agentforce Max Editions, alongside Agentforce add-ons and user licences. A retailer’s commercial package needs the commerce products and customer-facing agent usage as well as any employee licences it buys.

The Agentforce Commerce Shopping Agent

Salesforce’s shopper-facing commerce agent can guide product discovery and perform shopping actions, with support that depends on the storefront. Its business-to-consumer (B2C) documentation calls it the Shopper Agent. Business-to-business (B2B) documentation uses Guided Shopping Agent.

For consumer retail, Salesforce’s Shopper Agent for Storefront Next documentation describes recommendations and purchases through the Commerce Client chat. Its B2C setup guide separates product discovery, cart actions, order confirmation and site FAQs into subagents. Human escalation is configurable.

Storefront differences affect the practical comparison. Salesforce’s 25.10 B2C release note lists cart management and order confirmation for composable PWA Kit storefronts. That release lists product search and FAQs for Storefront Reference Architecture (SFRA) storefronts. A shopping-agent capability shown for one storefront must not be assumed to apply to every Salesforce store.

shoppa is an AI shopping agent for your own site. Customers refine a search over several messages, compare products side by side, add items to their basket and pay in the chat. They can then check order status or start a return in the same conversation.

Customer task	shoppa	Agentforce Commerce
Find and narrow products	Searches your catalogue and remembers earlier requirements	Shopper Agent guides discovery using connected Commerce data and search
Compare choices	Shows an attribute comparison table with trade-offs	Salesforce’s commerce use-cases page describes guided product comparison
Add to basket	Adds chosen products in the conversation	Cart actions are documented for supported storefront configurations
Place an order	Customers pay without leaving the chat	Storefront Next documentation describes purchases in Commerce Client chat
Ask about an order	Answers by order number, with signed-in order history across devices	B2B Guided Shopping documents order lookup, status and reordering
Get policy help	Uses your delivery, sizing and returns documents	Site FAQs use configured data libraries
Reach a person	Hands the conversation to your staff or helpdesk	Configured escalation passes conversation context to a service representative

For example, a customer can ask shoppa for a coat, narrow the results to navy and compare two materials before buying. That is an illustrative shopping journey. The deciding benefit is that your catalogue and policy documents supply the answers throughout it.

shoppa’s branding uses your agent name and colours. The conversation and customer relationship stay with your store.

From Salesforce Einstein to Agentforce

Salesforce Einstein is its earlier AI brand for predictions and generated content inside Salesforce applications. Einstein capabilities continue alongside Agentforce. A product recommendation model and an agent that changes a basket perform different jobs.

Einstein GPT was the branding for Salesforce’s generative AI services. Salesforce’s legal notices still name Einstein GPT for Commerce, Sales and Service within those services. Einstein Copilot became Agentforce, with Salesforce’s announcement describing an assistant upgraded to retrieve data, plan tasks and take actions.

For a retailer already paying for Einstein, the naming change doesn’t establish a new entitlement. Existing predictive recommendations can remain useful while a shopping agent needs its own actions and commerce setup. The licence package, enabled features and customer-facing consumption determine what you can use.

The Einstein Trust Layer connects AI responses to trusted business data and applies protections around model use. Salesforce Help documents prompt defence and toxicity detection. Audit records give teams visibility into interactions. Third-party model providers operate under zero-retention commitments, while Salesforce stores prompts, responses and trust signals in Data 360.

Data masking needs a precise distinction. The broader Trust Layer includes masking capabilities, but Salesforce’s Agentforce guidance says masking is disabled for agents. Its external-model zero-retention policy still applies. Zero retention by an external model provider does not mean Salesforce keeps no conversation records.

That gives Salesforce customers a governed data environment within their existing platform. shoppa gives retailers control over the shopping agent’s content and settings in its workspace. Use the AI vendor assessment guide to compare retention and access requirements against the needs of your store.

Adobe Sensei and the Adobe Commerce Approach

Adobe Sensei is Adobe’s AI and machine-learning technology brand, including product recommendations in Adobe Commerce. Adobe’s Experience League still describes Sensei-based recommendations such as showing similar products on a product page.

Adobe Commerce Live Search adds AI-driven filtering and ranking to catalogue search. Its current product pages also describe semantic search that matches the meaning of a customer’s request. Recommendations and search help customers discover products, but they are separate from a conversational shopping agent.

Adobe Sensei GenAI was the name used for generative features in Experience Cloud, including creating marketing content and customer journeys. Adobe still publishes Sensei and Sensei GenAI material. Its newer commerce features use names such as Brand Concierge and semantic search, while Firefly is the name for its creative generative models.

Adobe’s Australian Commerce page describes an integration with Adobe Brand Concierge for shopper-facing conversation. It includes product cards, comparisons and recommendations from live Commerce pricing and stock. The page describes in-conversation checkout as forthcoming, so it must be distinguished from the shopping guidance already described.

Developers can also build agents with Adobe Commerce’s Storefront Model Context Protocol (MCP) server. That connects compatible assistants to Commerce data and shopping actions. It is a development route within Adobe Commerce, distinct from adding a ready-configured shopping agent to a store.

Salesforce and Adobe both connect their AI closely to their commerce platforms. That can suit a retailer already committed to the platform’s data and operations. Changing platforms later means replacing or reconnecting those dependencies. shoppa uses native storefront apps or a product feed and script embed. You can choose its shopping assistance separately from the commerce platform.

Cost, Setup Time and Who Runs It

Agentforce combines platform licences with agent usage, while shoppa has per-session or per-token pricing. The Salesforce Australian pricing page lists customer-facing Conversations and action-based Flex Credits, with AUD labels for those usage options. Employee licences and bundled editions are separate purchase options.

A conversation charge and an action charge measure different things. One customer’s chat can trigger several actions, such as retrieving a product or looking up an order. Salesforce’s pricing examples also separate agent consumption from Data 360 consumption and other services. Budget for the applicable commerce licences and implementation work alongside usage.

shoppa’s per-session option gives predictable costs as traffic grows. Per-token pricing charges for what the agent uses. Its general comparison puts shoppa about 40% cheaper than other AI shopping agents for a typical retailer. The saving against an individual Agentforce contract depends on that contract’s costs.

An Australian Agentforce implementation involves a Salesforce team or consulting partner with Commerce Cloud and Data 360 experience. Salesforce’s Australian partner directory lets retailers filter experts by location, product and industry. A retailer with an experienced internal Salesforce team can run the work itself.

The project starts with choosing the shopping and service tasks, then establishing the required licences and data access. Salesforce’s setup guidance requires Data 360 provisioning and Einstein activation. The team then configures agent actions, connects the storefront and sets human escalation. Testing precedes activation, with conversation traces used to refine the behaviour.

This is work across your Salesforce environment, even with prebuilt templates. The work needed depends on your existing data and storefront, so the two products cannot be compared through a promised installation time.

shoppa installs with a two-line embed on stores that allow a script embed. Your ecommerce team connects the catalogue and policy documents, then configures the agent in its workspace. You can test changes privately and publish them for the next message. Version history gives you one-click rollback without waiting for someone to rebuild the storefront.

Salesforce has product demos and guided tours before purchase. Salesforce Foundations gives eligible existing customers a way to start using Agentforce tools. A complete commerce shopping agent needs the applicable licences and deployment work. shoppa has a free trial. For its usage pricing, Get a quote.

Choose shoppa or Agentforce

Choose Agentforce when your retailer already uses Salesforce deeply and wants shopping and service to work through one vendor’s records and workflows. It suits a team that can own Salesforce configuration and accepts the platform and consumption commitments.

Choose shoppa when your main goal is shopping assistance on your existing site, with an agent you can manage directly. The same conversation covers comparison, payment and order support. Your team controls its content and branding, and the embed works on stores that allow scripts without a platform migration.

For other ways to replace the Salesforce shopping-agent route, read the Agentforce alternatives. The shopping-agent comparisons cover other named options. For the wider change in how customers buy, read how agentic commerce works. If your priority is a shopping agent that your ecommerce team can configure and roll back itself, choose shoppa.