# Cimulate licence cost: what Agentic Commerce Search costs to run Cimulate now lives inside Salesforce as Agentic Commerce Search. A toggle in B2C Commerce, headless APIs for other platforms, and a price that is quote-only on every page. **Published:** 2026-08-03 **Canonical:** https://synconai.com/cimulate-salesforce-licence-cost **Author:** SynconAI Architecture Team ## In short Salesforce completed the Cimulate acquisition on 3 March 2026, and its technology now appears as Agentic Commerce Search. No price is published for it. B2C Commerce Premium and Payments both read contact for pricing on Salesforce's Commerce pricing page. Cost it as a quote and ask what the toggle meters, who owns the trained model, and what happens at exit. ## Sources - **Salesforce Signs Definitive Agreement to Acquire Cimulate** (retrieved 2026-03-03) https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-cimulate/ > Salesforce completed its acquisition of Cimulate on March 3, 2026. - **Agentic Commerce Search** (retrieved 2026-10-13) https://www.salesforce.com/commerce/ai/agentic-search/ > Yes, ecommerce customers on any platform can get started with Agentic Commerce Search. - **Salesforce Commerce Pricing** (retrieved 2026-10-13) https://www.salesforce.com/commerce/pricing/ > Explore commerce pricing and find the right solutions for your business. ## What to take away - Agentic Commerce Search is the Salesforce product now carrying Cimulate's technology, and its metrics are footnoted to Cimulate customers. No price is published for it. - It works for any platform through headless APIs and is a toggle inside B2C Commerce, so you may be buying it without being a B2C Commerce customer. - The search is a custom small language model trained on your catalogue and shopper data. Ownership of that model and the training data at exit is the contract question that matters. - Salesforce's Commerce pricing page lists B2C Commerce Premium and Payments as contact for pricing, so any figure quoted to you is a negotiated one. ## The guide A retailer's e-commerce director asks a reasonable question: if search is the weak point on the site, what does the Cimulate technology cost now that Salesforce owns it? The honest answer is that the price is not published anywhere we could find, but a great deal about the licence can still be established from Salesforce's own pages. Most of the cost risk sits in the contract terms, not in a list price. ## What the acquisition became The completion note is brief. "Salesforce completed its acquisition of Cimulate on March 3, 2026." The announcement described Cimulate as an emerging leader in AI-powered product discovery and agentic commerce, and said the acquisition would strengthen Salesforce's investment in Agentforce Commerce by improving search and discovery. It described an intent-aware context engine that combines real and simulated shopper journey data to understand intent. The product that carries that capability now is Agentic Commerce Search. We read its page on 13 October 2026. It never says the word acquisition, but its performance claims are footnoted as "Cimulate customer success metrics", which tells you whose engine it is. We are not repeating those claims, because they are the vendor's own and your site is not theirs. ## What the product page does tell you about licensing The page answers the question that decides who needs a licence at all: "Yes, ecommerce customers on any platform can get started with Agentic Commerce Search." For customers of Salesforce B2C Commerce, it is natively integrated and starts with a toggle. For customers on other platforms, the page names Shopify, commercetools, SAP Hybris and Adobe Commerce, or a homegrown platform, and says they can integrate through headless APIs. That has a commercial implication that is easy to miss. If you run on another platform, you would be a Salesforce customer for search only, with a separate contract and no B2C Commerce relationship to bundle against. Check whether the vendor will sign that way, what minimum term applies, and whether the headless route has different usage terms from the toggle. The page also states what the system needs to start: a product catalogue feed in any format and shopper activity data. It says there is no minimum traffic threshold and no requirement for a highly attributed catalogue. The convenience is real, but it makes the contract the place where data rights are defined, because you are handing over the two assets a competitor would most like to see. ## The price: quote-only The [Commerce pricing page](https://www.salesforce.com/commerce/pricing/), which invites you to "Explore commerce pricing and find the right solutions for your business.", is not a rate card. When we read it on 13 October 2026, B2C Commerce Premium showed contact for pricing in every currency, described with 100 sites and 3,500 price books, and Salesforce Payments also read contact for pricing. Agentic Commerce Search had no separate price on the Commerce pricing page or on its own page. There are two ways to read that absence. Either it is a priced add-on that is quoted per deal, or it is bundled into a B2C Commerce relationship at a rate negotiated alongside the platform. The pages do not say which. Your quote will, and you should ask in writing. The Premier Success Plan on that page is priced as a share of net licence fees, so a higher licence value also raises support cost, which is worth modelling. ## What could set the quote With no published unit, here are the meters worth asking about, as questions rather than as claims about how Salesforce prices this product. - Search requests, because a busy storefront generates a great many and a metered price could scale with traffic. - Catalogue size, meaning the number of products and variants the model must understand. - Number of sites or storefronts, which matters if you run several brands. - Whether the conversational features inside Agentforce Shopper Agent are inside the base price or draw on Agentforce credits. - Environments, for example a test storefront where you tune ranking before release. If Agentforce Shopper Agent is part of the plan, the [Agentforce pricing page](https://www.salesforce.com/agentforce/pricing/) shows Flex Credits at US$500 per 100,000 credits and 20 credits an action, on the date read. Ask whether the conversational layer is metered that way for your deal. ## The model is the asset: contract terms to settle Agentic Commerce Search builds a custom small language model trained on your catalogue and shopper data. The page describes a model of one to seven billion parameters, and explains that it generates synthetic searches, clicks and purchases to make up for gaps in behavioural data, tuned with real shopper behaviour. That is a design with licence consequences that a conventional search tool would not raise. Settle these in the contract before you start: 1. Who owns the trained model, and whether it can be exported or only deleted. 2. Whether your catalogue and shopper data are used to improve anyone else's model. 3. How long synthetic data derived from your data is retained after you leave. 4. What service levels apply to latency, since search sits on the critical path of every page. 5. Whether you can run search in a test environment against a copy of the catalogue without paying again. The earlier guide on [Cimulate and Agentforce Commerce](/cimulate-agentforce-commerce) covers the catalogue fields search may read and the person who publishes a product, which matter just as much as the price. ## Right-sizing before you sign Resist sizing on the whole estate. Pick the category pages or product ranges where search is demonstrably failing, using your own zero-result and abandonment data, and ask for a term that covers those. Agree the metric of success before the model trains, such as conversion from search sessions, and the date at which you will review it. If the vendor will not accept a review point with an exit, the commitment is larger than the pilot justifies. Keep the storefront release on its own line. A search upgrade is not a replatform, and a quote that bundles the two has mixed the books. Changes to ranking should not write into price fields, and the guide on [integrating Cimulate with Salesforce](/integrating-cimulate-with-salesforce) explains why price is a commerce field and ranking is an order. ## Comparing two offers | Row | What to compare | | --- | --- | | Route | B2C Commerce toggle or headless APIs, and who is the contracting party | | Meter | Requests, catalogue size, sites, or a flat fee | | Conversational layer | Inside the price, or drawing on Agentforce credits | | Data rights | Training use, retention of synthetic data, ownership of the model | | Environments | Test storefront included or extra | | Term and review | Minimum term, success measure, exit right | | Support | Share of licence fees, response times, named contact | ## Three routes, three signatories Which route you take decides who you sign with and what you can bundle, so make it explicit before the first call. If you run B2C Commerce, the search toggle sits inside a relationship you already have. The commercial question is whether search is added to the existing order form, whether it changes the price of the platform at renewal, and whether switching it on mid-term triggers a new minimum. Because the Commerce pricing page shows B2C Commerce Premium as contact for pricing, any figure is negotiated, and a bundle may be more attractive than a separately priced add-on. If you run another platform and use headless APIs, you become a customer for search alone. Ask whether Salesforce will sign a standalone order, whether the term and minimum differ from the toggle route, and which service levels apply to calls that cross from your platform into theirs. Latency and availability become your problem the moment search is on the critical path of a product listing page. If you are on B2B commerce or a hybrid estate, check explicitly that the product page's description of "any platform" covers your case, and ask for that to be written in the order form instead of left to the sales conversation. ## Peak trading and the meter Retail demand is lumpy. A search product that is metered on requests would be most expensive in the weeks you can least afford to throttle it, such as a sale or a seasonal peak. The pages we read do not say whether Agentic Commerce Search is metered at all, so the safe approach is to ask three things up front: whether there is a request cap, what happens when traffic exceeds the allowance, and whether you pay overage or are rate limited. A flat annual fee with a stated capacity is easier to budget than an uncapped meter, and an uncapped meter with a ceiling you set yourself is better than one without. Also ask about environments. Tuning ranking before a sale needs a test storefront, and a test environment that is billed as a second production site changes the economics of a small pilot. ## How to run a defensible pilot Treat the first term as a measured test, not a rollout. Choose a category where shoppers visibly struggle, using your own search logs: zero-result queries, high exit rates after a search, and the long tail of intent phrases that your current synonym rules cannot handle. Fix the success measure and the review date in the contract. Compare the pilot against a control, so that seasonality is not mistaken for improvement. During the pilot, keep a log of every manual override your merchandisers still make. The aim of a learning search engine is to reduce rules, and a pilot that leaves the rule count unchanged has not shown what it was bought to show. Agree in advance what level of reduction would justify extending the licence. Finally, define the exit. If the review shows no gain, what is deleted, how quickly, and in what form can you take the search logs and any tuned configuration with you? A vendor that is comfortable with a clean exit usually has more confidence in its product than one that resists. ## Shopper data and the training set Search that learns from shopper behaviour is processing personal data. Click streams, searches and purchases tied to a visitor or an account can be personal information under privacy law, and a vendor that trains a model on them is a processor whose terms you must understand. The product page says the system needs your catalogue and your shopper activity data, and that it supplements real behaviour with synthetic journeys. It does not set out retention, location or the legal basis. Before the pilot, ask for the data processing terms, the list of sub-processors, the locations where training and serving happen, and the retention period for both raw and derived data. Confirm that your privacy notice covers the use, and that any consent you collect for analytics extends to this purpose. If you operate in several jurisdictions, check whether the model can be trained and served in the region you need. These are not reasons to avoid the product. They are the reasons the contract, and not the price, is where most of the risk sits, and they are cheaper to settle before data flows than after. ## Where the neighbouring questions are answered The acquisition facts are on [what happened to Cimulate](/what-happened-to-cimulate), and the decision about whether to change search at all, as against replatforming, is in [should I migrate from Cimulate](/should-i-migrate-from-cimulate). ::: note Read on 13 October 2026. The pages show no price for Agentic Commerce Search and say pricing is subject to change. Treat any figure you are quoted as negotiated. ::: ## What to ask your account executive Ask which line on the quote covers search, whether it is metered, and what the rate is when you exceed it. Ask who owns the model and what happens to your data on exit. Ask whether the conversational layer is included. Then ask for the test environment terms in writing, since tuning search without one is guesswork. ## Questions ### Is there a published price for Cimulate or Agentic Commerce Search? No. As at 13 October 2026 Salesforce's Commerce pricing page showed contact for pricing for B2C Commerce Premium and Payments, and neither that page nor the Agentic Commerce Search page listed a price for search. Treat it as a quote and ask what it meters. ### Can I use Agentic Commerce Search without B2C Commerce? Yes, according to Salesforce's page, which says customers on any platform can get started and names Shopify, commercetools, SAP Hybris, Adobe Commerce and homegrown platforms via headless APIs. Confirm in writing that the vendor will contract for search alone. ### Who owns the model trained on my catalogue and shoppers? The pages do not say, so settle it in the contract. Ask whether the model can be exported or only deleted, whether your data trains anyone else's model, and how long synthetic data derived from yours is kept after you leave. ### Does the conversational shopping feature cost extra? Not stated on the pages read. Agentic Commerce Search is integrated into Agentforce Shopper Agent, and Agentforce Flex Credits were US$500 per 100,000 with 20 credits an action. Ask whether conversational use is inside your price or draws on credits. ### How do I size a first Cimulate or search licence? Pick the product ranges where search measurably fails, set the success measure before the model trains, and ask for a short term with an exit if the measure is not met. Keep the storefront release as a separate line. --- SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Salesforce consultancy (https://synconai.com/salesforce-consultancy).