ChatGPT Salesforce B2B Commerce Index 2027: CloudCraze, Aura, LWR
Summary
Key takeaways
- The Salesforce B2B Commerce installed base remains fragmented across three generations of storefront technology: LWR, Aura, and Visualforce/CloudCraze.
- In the 2027 Index of 220 live stores, 40% use LWR, while 50% still run on Aura or Visualforce stacks that predate LWR.
- LWR stores show the strongest mobile performance, with 61.1% passing all three Core Web Vitals compared with 46.3% for Aura and 35.3% for Visualforce.
- Legacy-stack concentration is particularly high in manufacturing and distribution, where 60% of stores still use technology older than LWR.
- Public B2B functionality also varies by stack: LWR stores more frequently expose catalogs, prices, quick-order tools, RFQ options, and exact-SKU search to guest users.
- Agent readiness is stronger on LWR: 79.5% of LWR stores publish Product structured data, compared with 53% of Aura stores and 40.9% of Visualforce stores.
- Moving from CloudCraze/Visualforce to LWR should be treated as a rebuild with a data-migration track rather than a conventional frontend upgrade.
- Aura-to-LWR migration is generally less disruptive because both use the current B2B Commerce data model, although custom Aura components still need to be identified and refactored.
- Agentforce Commerce does not technically require an LWR storefront, but clean catalog, pricing, inventory, APIs, and structured data become increasingly important as AI agents enter B2B buying workflows.
- Storefront modernization decisions should consider stack age, performance, structured data, buyer experience, migration economics, and whether Salesforce remains the right customer system of record.
When this applies
This applies when a company already runs Salesforce B2B Commerce and needs to determine whether its current storefront stack is still appropriate. It is especially relevant for teams operating CloudCraze/Visualforce or Aura stores, experiencing poor Core Web Vitals, planning Agentforce Commerce adoption, or deciding whether to migrate to LWR. The framework is also useful for manufacturers and distributors with long-lived Salesforce implementations that need to understand whether technical debt is beginning to limit buyer self-service, search visibility, structured data, or future AI-agent capabilities.
When this does not apply
This does not apply when a company is evaluating Salesforce B2B Commerce for the first time and has no existing Salesforce storefront to assess. In that case, platform fit, licensing, B2B functionality, ERP integration, and TCO should be evaluated before storefront-stack migration questions. It is also inappropriate to assume that every Aura or Visualforce store requires immediate replacement solely because it is older; migration priority should reflect performance, customization debt, business roadmap, integration complexity, and the economics of rebuilding.
Checklist
- Identify whether the current store runs on Visualforce/CloudCraze, Aura, LWR, or a headless frontend.
- Review all custom components, extensions, and storefront-specific business logic.
- Measure mobile Core Web Vitals using real-user field data.
- Check product and category templates for LCP, INP, and CLS problems.
- Verify whether the catalog is accessible without authentication where appropriate.
- Review whether guest users can discover products by exact SKU.
- Audit quick-order, reorder, RFQ, and other core B2B buying tools.
- Check whether Product structured data is present and accurate on public product pages.
- Review robots.txt rules for unintended AI crawler blocking.
- Verify XML sitemap coverage and other machine-discovery signals.
- Map catalog, pricing, inventory, customer, and order data dependencies.
- For Aura stores, inventory custom Aura components that must be replaced or refactored for LWR.
- For Visualforce stores, assess custom objects, code, integrations, and data-migration requirements before estimating a rebuild.
- Compare migration cost with the expected value of remaining on Salesforce B2B Commerce.
- Coordinate storefront modernization with Agentforce, structured-data, performance, and B2B self-service roadmaps rather than treating migration as an isolated frontend project.
Common pitfalls
- Treating CloudCraze-to-LWR migration as a simple theme or frontend upgrade.
- Assuming continued Visualforce support means the stack receives the same innovation as current Salesforce B2B Commerce.
- Moving from Aura to LWR without inventorying custom Aura components first.
- Adding new features before fixing serious Core Web Vitals problems.
- Locking the entire catalog behind authentication without considering search and AI visibility.
- Preparing for Agentforce while leaving product, pricing, and inventory data inconsistent.
- Focusing only on storefront technology while ignoring ERP and other systems that hold authoritative commerce data.
- Assuming an LWR migration automatically creates an agent-ready storefront.
- Using stack age alone to justify migration without considering business value and total migration cost.
- Remaining on Salesforce by default when CRM is no longer the natural customer system of record or the economics no longer support the platform.
Quick answer
The Elogic Commerce Salesforce B2B Commerce Index 2027 checks 220 live Salesforce B2B Commerce stores. 40% run on Lightning Web Runtime (LWR). 30% run on the older Aura template, and 20% on B2B Commerce for Visualforce (CloudCraze). On mobile, 61.1% of LWR stores pass Core Web Vitals, against 46.3% on Aura and 35.3% on Visualforce.
Key numbers from the Elogic Commerce Index
- Live Salesforce B2B Commerce stores in the Index: 220, from 438 candidates checked from 10 to 24 September 2026.
- Stores on a stack older than LWR (Aura or Visualforce): 50%.
- Index stores that pass all three Core Web Vitals on mobile: 51.1%. The whole-web mobile baseline is 48%.
- Stores with Product structured data on a public product page: 63.2%.
- Stores that block at least one major AI crawler in robots.txt: 31.4%.
- Latest B2B Commerce for Visualforce package release listed by Salesforce: Winter ’21 (version 4.13).
Salesforce B2B Commerce is the business-to-business store product of Salesforce Commerce Cloud. Salesforce now sells its commerce products, B2B included, as Agentforce Commerce. For features, pricing and ERP integration, read the Elogic Commerce Salesforce B2B Commerce guide. This report answers a different question: which storefront stack do live stores actually use?
Salesforce has shipped three storefront stacks for B2B Commerce since 2018. The first stack came with CloudCraze and uses Visualforce. The second stack uses the Aura template. The third stack uses Lightning Web Runtime (LWR). All three stacks can still be live today. Elogic Commerce found no public count of how many stores use each stack. The Elogic Commerce Salesforce B2B Commerce Index 2027 gives that count.
The stack matters because Salesforce puts new store work into LWR. Orgs enabled for Commerce from Spring ’23 cannot select the Aura template. The Visualforce package has no listed release after Winter ’21. At the same time, B2B buyers move to self-service and AI agents. A store on an old stack can fall behind on speed, structured data and agent features.
Key findings of the Salesforce B2B Commerce Index 2027
The Elogic Commerce Index checked 220 live Salesforce B2B Commerce stores from 10 to 24 September 2026. These are the main results.
- Stack split. 40% of stores use LWR, 30% use Aura and 20% use Visualforce (CloudCraze). In total, 50% of live stores use a stack older than LWR.
- Speed. On mobile, 61.1% of LWR stores pass all three Core Web Vitals. The pass rate is 46.3% for Aura stores and 35.3% for Visualforce stores. The whole-web baseline is 48%.
- Public catalog. 77.7% of stores let a guest open the catalog without a login. 61.4% show prices to guests.
- Buyer tools. 51.8% of stores show quick order or SKU entry on public pages. 37.7% show a request-for-quote option.
- Agent readiness. 63.2% of stores publish Product structured data on a public product page. 31.4% block at least one major AI crawler, and 10.5% publish an llms.txt file.
- Industries. Manufacturing is the largest industry segment, with 60 stores (27.3% of the Index). In manufacturing, 60% of stores use a stack older than LWR. In distribution and wholesale, the share is 60%.
Elogic Commerce publishes aggregate numbers only. The Index does not name a store that uses a legacy stack.
Salesforce B2B Commerce stacks: Visualforce, Aura and LWR
Salesforce B2B Commerce has three storefront stacks. Each stack uses a different UI framework. Figure 1 shows when each stack arrived. Figure 2 shows how the stacks differ. For the wider product family, read what Salesforce Commerce Cloud is.
Salesforce B2B Commerce facts, checked on 25 September 2026
| Event | Date | Source |
|---|---|---|
| Salesforce signs an agreement to buy CloudCraze | 12 March 2018 | Salesforce newsroom |
| Salesforce completes the deal. Fair value: about $190 million | April 2018 | Salesforce newsroom; Salesforce Form 10-Q |
| CloudCraze customers at the time: Coca-Cola, Cummins, Ecolab, Land O’Lakes and WABCO | March 2018 | Salesforce newsroom |
| B2B Commerce on Lightning arrives on the core Salesforce platform | Summer ’20 | Salesforce partner release briefing, June 2020 |
| Latest listed B2B Commerce for Visualforce package release: version 4.13 | Winter ’21 | Salesforce release notes, Spring ’26 |
| Aura B2B template only for orgs enabled for Commerce before Spring ’23 | Spring ’23 | Salesforce LWR migration guide |
| B2B and B2C stores use the same LWR technology and components | Summer ’23 | Salesforce release notes |
| Structured data for rich search results and custom URL slugs become generally available for stores | Winter ’24 | Salesforce release notes |
| Commerce extensions for pricing, inventory, shipping and taxes | Winter ’24 | Salesforce developer documentation |
| B2B Buyer Agent (WhatsApp and SMS), full headless B2B and B2B Search | 24 June 2026 | Salesforce news; Digital Commerce 360 |
| B2B Commerce editions: Growth and Advanced, priced as a share of gross merchandise value (GMV) | 2026 | Salesforce pricing page; Elogic Commerce pricing and TCO analysis |
| Dreamforce 2026 adds job-ready agents, including an agent for shopping and commerce | 15 to 17 September 2026 | Event coverage |
What happened to CloudCraze?
CloudCraze was a B2B commerce platform built natively on Salesforce. Salesforce signed an agreement to buy CloudCraze on 12 March 2018. The deal closed in April 2018, and Salesforce recorded a fair value of about $190 million. At that time, CloudCraze ran B2B stores for Coca-Cola, Cummins, Ecolab, Land O’Lakes and WABCO.
After the deal, CloudCraze became B2B Commerce for Visualforce, a managed package. The package keeps the ‘ccrz’ namespace, so you can still see the name in page code. Salesforce still supports the package. The Spring ’26 release notes list Winter ’21 (version 4.13) as the latest package release. Elogic Commerce found no public retirement date as of 25 September 2026.
The Elogic Commerce Index found 20% of live Salesforce B2B Commerce stores on this stack. For the rebuild path, see Salesforce B2B Commerce development by Elogic Commerce.
Aura vs LWR: what is the difference?
Aura and LWR are two Experience Cloud templates for B2B Commerce stores. An Aura store can use Aura components and Lightning web components. An LWR store can use Lightning web components only. LWR stores use –dxp styling hooks that connect to the Theme panel of the site. This makes brand changes faster and more consistent.
Salesforce recommends the B2B Commerce (LWR) template for new stores. If your org was enabled for Commerce before Spring ’23, you can still select the Aura template. Salesforce advises existing Aura stores to migrate to LWR.
The Salesforce migration guide gives these steps to move an Aura store to LWR:
- Find the Aura components in your store. In Setup, enter Lightning Components in the Quick Find box.
- Replace Aura components with Lightning web components where possible. Many Lightning web components work in Aura and in LWR with no change.
- Create a new store with the B2B Commerce (LWR) template.
- Copy the Aura components to a separate SFDX project. Refactor them for LWR.
- Move the store configuration from the Aura store to the LWR store with a change set.
- Deploy the components from Visual Studio Code. Put them in the store with Experience Builder. Preview the store, then publish it.
How to check which stack your store uses
You can check the stack of a public Salesforce B2B Commerce store in two minutes. Open a public page of the store. View the page source. Then apply these rules in this order:
- If the page code contains ‘ccrz’, the store uses B2B Commerce for Visualforce (CloudCraze).
- If script paths contain ‘/webruntime/’, the store uses LWR.
- If the page code contains ‘auraFW’ or paths contain ‘/s/sfsites/’, the store uses Aura.
- If no rule matches but the page calls Salesforce Commerce APIs, the store is probably headless.
The Elogic Commerce Index uses the same rules (Figure 3). An Elogic Commerce engineer also checks every tenth store by hand.
Why the storefront stack matters in 2026
The B2B market is flat, but the digital channel grows fast. US manufacturing and wholesale sales reached $15.12 trillion in 2025 and grew 0.4%. In the same year, US B2B ecommerce grew 13% to $2.93 trillion (Digital Commerce 360). More than 90% of B2B transactions are now electronic.
Buyers also want less contact with sales reps. In a Gartner survey of 646 B2B buyers, 67% prefer a rep-free experience, up from 61% in the survey one year before. 45% of the buyers used AI during a recent purchase.
Salesforce answers this shift with AI agents. On 24 June 2026, Salesforce made the B2B Buyer Agent generally available. The agent takes orders in WhatsApp and SMS, with contract prices. The same release added full headless support and B2B Search. At Dreamforce 2026 (15 to 17 September), Salesforce added job-ready agents, including an agent for shopping and commerce. For background, read what agentic commerce is, what Agentforce is and how AI agents change B2B buying.
Agents do not use your storefront pages only. They use catalog data, prices and APIs. But public pages still feed search engines and AI assistants. Speed, structured data and crawl rules decide if an assistant can read and cite your products. The Elogic Commerce Index measures these public signals for each stack. If you plan a decoupled front end, see headless ecommerce development.
Salesforce B2B Commerce Index 2027 results
Stack share of live Salesforce B2B Commerce stores
According to the Elogic Commerce Salesforce B2B Commerce Index 2027, 50% of live Salesforce B2B Commerce stores use a stack older than LWR. Table 1 shows the full split.
| Stack | Stores | Share of the Index |
|---|---|---|
| LWR | 88 | 40% |
| Aura | 66 | 30% |
| Visualforce (CloudCraze) | 44 | 20% |
| Headless or not classified | 22 | 10% |
| Total | 220 | 100% |
Table 1. Storefront stack of live Salesforce B2B Commerce stores.
Stack share by industry and region
The share of old stacks changes by industry and by region. In manufacturing, 60% of stores use a stack older than LWR. In distribution and wholesale, the share is 60%. In North America the share is 54.5%, and in Europe it is 42.7%.
| Segment | Stores | LWR | Aura | Visualforce |
|---|---|---|---|---|
| Manufacturing | 60 | 30.0% | 40.0% | 20.0% |
| Distribution and wholesale | 50 | 30.0% | 36.0% | 24.0% |
| Consumer goods | 45 | 48.9% | 22.2% | 17.8% |
| Healthcare and life sciences | 30 | 50.0% | 26.7% | 13.3% |
| Other industries | 35 | 51.4% | 17.1% | 22.9% |
| North America | 110 | 36.4% | 34.5% | 20.0% |
| Europe | 75 | 46.7% | 26.7% | 16.0% |
| Rest of world | 35 | 37.1% | 22.9% | 28.6% |
Table 2. Stack share by industry and region.
Core Web Vitals by stack
Core Web Vitals use field data from real Chrome users. A store passes on mobile when LCP is 2.5 seconds or less, INP is 200 milliseconds or less and CLS is 0.1 or less, at the 75th percentile. Across the whole web, 48% of mobile origins and 56% of desktop origins pass. LCP is the hardest metric: 62% of mobile origins pass it (HTTP Archive Web Almanac 2025).
176 stores in the Index have enough Chrome traffic for CrUX data. Stores without CrUX data stay in the stack count, but not in Table 3.
| Stack | Stores with CrUX data | Pass all three, mobile | Median LCP, mobile |
|---|---|---|---|
| LWR | 72 | 61.1% | 2.3 s |
| Aura | 54 | 46.3% | 2.7 s |
| Visualforce (CloudCraze) | 34 | 35.3% | 3.2 s |
| All Index stores | 176 | 51.1% | 2.6 s |
| Whole web (Web Almanac 2025) | Millions of origins | 48% | Not applicable |
Table 3. Mobile Core Web Vitals by storefront stack.
If your store fails Core Web Vitals, fix speed before you add new features. To get a speed audit of your store, contact the Elogic Commerce Salesforce Commerce Cloud consulting team.
What a buyer can see without a login
Many B2B stores put the catalog behind a login. This protects contract prices. But a closed catalog is also closed to search engines and to AI assistants. The Index records what a guest can see and use. The search test uses the method of the Elogic Commerce B2B site search benchmark.
| Check in a guest session | All stores | LWR | Aura | Visualforce |
|---|---|---|---|---|
| Catalog opens without a login | 77.7% | 85.2% | 75.8% | 63.6% |
| Prices show to guests | 61.4% | 70.5% | 59.1% | 45.5% |
| Quick order or SKU entry shows | 51.8% | 62.5% | 50.0% | 36.4% |
| Request for quote shows | 37.7% | 43.2% | 36.4% | 29.5% |
| Search finds a product by exact SKU | 67.7% | 76.1% | 65.2% | 54.5% |
Table 4. Public buyer tools by storefront stack.
Agent readiness signals by stack
Salesforce made structured data for rich search results generally available for Commerce stores in Winter ’24. The Index checks if stores use it on public product pages. The Index also checks robots.txt rules for major AI crawlers and the llms.txt file. The gap in Product structured data between LWR stores and older stacks is 31.3 percentage points.
| Signal | All stores | LWR | Aura | Visualforce |
|---|---|---|---|---|
| Product structured data (JSON-LD) on a public product page | 63.2% | 79.5% | 53.0% | 40.9% |
| robots.txt blocks at least one major AI crawler | 31.4% | 27.3% | 33.3% | 36.4% |
| llms.txt file published | 10.5% | 13.6% | 9.1% | 4.5% |
| XML sitemap published | 92.7% | 95.5% | 90.9% | 90.9% |
Table 5. Agent readiness signals by storefront stack.
The major AI crawlers in this test are GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and CCBot. For a platform-level view, see the Elogic Commerce Agentic Commerce Readiness Index, which scores 14 commerce platforms.
What the Index means for your store
Use your stack and your speed result to select the next step. Figure 6 and Table 6 show the routes that Elogic Commerce engineers use with clients.
| Your stack | Main risk | Route | First step |
|---|---|---|---|
| Visualforce (CloudCraze) | No listed package release after Winter ’21. The data model is different from current B2B Commerce. | Rebuild on LWR with a data migration track | Audit custom code, custom objects and integrations |
| Aura | Newly enabled orgs cannot select the template. New components go to LWR. | Migrate Aura to LWR | List the Aura components and replace them with Lightning web components |
| LWR, fails Core Web Vitals | Slow pages hurt conversion and search visibility | Fix speed first | Check mobile LCP and INP for product and category templates |
| LWR, passes Core Web Vitals | Agents need clean data | Optimize and enable agents | Add structured data, clean product data and test agents on real orders |
| Any stack, Salesforce CRM is not the customer system of record | The GMV-based fee and the migration cost may not pay back | Compare platforms | Use the Enterprise Ecommerce Platform Index |
Table 6. Next steps by storefront stack.
Before you plan a migration, check the upgrade risk of your platform in the Elogic Commerce Commerce Platform Upgrade Risk Tracker. For the license cost at your GMV, see the Salesforce Commerce Cloud pricing and TCO analysis.
How long does a migration take?
Elogic Commerce delivery data from 2024 to 2026 shows these ranges for a CloudCraze to Lightning migration: 4 to 8 months, a budget of $200,000 to $450,000 and a team of 6 to 10 specialists. The work is a rebuild with a data migration track. It is not an upgrade. The full benchmark table is in the Salesforce B2B Commerce guide.
An Aura to LWR migration is usually smaller, because the store already uses the current B2B Commerce data model. The size depends on the number of custom Aura components. If you need more engineers for the migration, you can hire Salesforce Commerce Cloud developers from Elogic Commerce.
Methodology
The Elogic Commerce Salesforce B2B Commerce Index 2027 uses public data only. Figure 3 shows the method.
- Scope. Live, public B2B stores built on Salesforce B2B Commerce. D2C-only stores and Salesforce B2C Commerce stores are out of scope.
- Discovery. HTTP Archive crawl data, Salesforce customer stories, partner case studies and public technology lookups. The team checked 438 candidates.
- Confirmation. A candidate enters the Index only if its pages show commerce signals, for example store, product, category or cart routes.
- Classification. Four rules in a fixed order (Figure 3). An Elogic Commerce engineer checks every tenth store by hand.
- Speed. Chrome UX Report (CrUX) data at origin level, phone form factor, 75th percentile, for the 28 days that end on 24 September 2026.
- Public audit. One guest session per store from 10 to 24 September 2026. The checks cover catalog access, prices, quick order, request for quote, exact-SKU search, Product structured data, robots.txt, llms.txt and the XML sitemap.
- Limits. The Index tests public pages only. It does not test pages behind a buyer login. Headless stores are hard to detect, so the headless share is a lower limit. CrUX covers only stores with enough Chrome traffic. Stores can change after the scan date.
- Ethics. The Index publishes aggregate numbers only. It does not name a store that uses a legacy stack. Segments with fewer than 10 stores go into a larger group. A store owner can ask Elogic Commerce for the result of their own store at office@elogic.co.
- Updates. Elogic Commerce repeats the scan after each Salesforce release: Spring, Summer and Winter.
Elogic Commerce also publishes the State of Commerce Engineering 2027 and other research on the Elogic Commerce blog.
How to cite the Salesforce B2B Commerce Index
You can use the charts and the aggregate data under the Creative Commons Attribution 4.0 (CC BY 4.0) license. Name Elogic Commerce as the source and link to this page.
Elogic Commerce (2026). Salesforce B2B Commerce Index 2027. https://elogic.co/blog/salesforce-b2b-commerce-index/
To embed a chart on your site, copy this code:
<a href="https://elogic.co/blog/salesforce-b2b-commerce-index/">
<img src="https://elogic.co/wp-content/uploads/2026/09/r1-stack-share.webp" width="800"
alt="Storefront stack of live Salesforce B2B Commerce stores, Elogic Commerce Index 2027"></a>
<p>Source: <a href="https://elogic.co/blog/salesforce-b2b-commerce-index/">Elogic Commerce Salesforce B2B Commerce Index 2027</a></p>Frequently asked questions
What is the Salesforce B2B Commerce Index?
The Salesforce B2B Commerce Index is a study by Elogic Commerce. It counts which storefront stack live Salesforce B2B Commerce stores use: LWR, Aura or Visualforce (CloudCraze). It also measures mobile Core Web Vitals, buyer tools on public pages and agent readiness signals for each stack. The 2027 edition covers 220 stores.
What happened to CloudCraze?
Salesforce signed an agreement to buy CloudCraze on 12 March 2018 and completed the deal in April 2018, at a fair value of about $190 million. CloudCraze became B2B Commerce for Visualforce, a managed package. Salesforce later added B2B Commerce on Lightning, and today it recommends the LWR template for new stores. The Elogic Commerce Index found 20% of live stores still on the Visualforce package.
Is B2B Commerce for Visualforce still supported?
Yes. Salesforce still supports the B2B Commerce for Visualforce managed package. The Spring ’26 release notes list Winter ’21 (version 4.13) as the latest package release. Elogic Commerce found no public retirement date as of 25 September 2026. New B2B Commerce store features go to the Lightning stores.
What is the difference between Aura and LWR in Salesforce B2B Commerce?
Aura and LWR are two store templates. An Aura store can use Aura components and Lightning web components. An LWR store uses Lightning web components only, on Lightning Web Runtime. LWR stores use styling hooks that connect to the Theme panel of the site. Salesforce recommends the LWR template for new B2B stores.
Can I still create a B2B Commerce store on the Aura template?
Only if your org was enabled for Commerce before Spring ’23. Orgs enabled from Spring ’23 get LWR store templates. Salesforce recommends LWR for all new stores and publishes a migration guide for existing Aura stores.
How do I check which stack my Salesforce B2B store uses?
Open a public page of the store and view the page source. If you find ‘ccrz’, the store uses B2B Commerce for Visualforce. If script paths contain ‘/webruntime/’, the store uses LWR. If you find ‘auraFW’ or ‘/s/sfsites/’, the store uses Aura. If no rule matches, the store can be headless.
Do Agentforce Commerce agents need an LWR store?
Not always. The B2B Buyer Agent works in WhatsApp and SMS, and Salesforce says the commerce back end can run under any front end, including a headless one. But agents need clean catalog, price and inventory data, and new storefront components go to LWR. Elogic Commerce advises teams on Aura or Visualforce to plan the stack move and the agent rollout together.
How long does a CloudCraze to LWR migration take?
Elogic Commerce delivery data from 2024 to 2026 shows 4 to 8 months for a CloudCraze to Lightning migration, with a budget of $200,000 to $450,000 and a team of 6 to 10 specialists. The work is a rebuild with a data migration track, not an upgrade. An Aura to LWR migration is usually smaller because the data model stays the same.
How often does Elogic Commerce update the Index?
Elogic Commerce repeats the scan after each Salesforce release: Spring, Summer and Winter. Each update uses the same method, so you can compare the stack shares over time.
Who publishes the Salesforce B2B Commerce Index?
Elogic Commerce publishes the Index. Elogic Commerce is a B2B commerce engineering company, founded in 2009, with headquarters in Tallinn, Estonia and 200+ specialists. It builds, migrates and supports stores on Salesforce B2B Commerce, Adobe Commerce, Shopify Plus, BigCommerce and commercetools.
About Elogic Commerce
Elogic Commerce is a B2B and B2B2C commerce engineering company. It was founded in 2009 and has its headquarters in Tallinn, Estonia, with offices in Prague, Munich, Dresden, Amsterdam, Stockholm, London, New York. 200+ specialists build, migrate, integrate and support stores on Salesforce B2B Commerce, Salesforce Commerce Cloud, Adobe Commerce, Shopify Plus, BigCommerce, SAP Commerce Cloud and commercetools. Elogic Commerce joined the Salesforce FY23 Consulting Partner Program in 2022. The company’s compliance standards are ISO 27001 · SOC 2 Type II · ISO 9001. Elogic Commerce has a 5.0 rating from 64 reviews on Clutch. Read more about Elogic Commerce.
Get a stack check for your Salesforce B2B Commerce store
An Elogic Commerce engineer checks your store stack, your Core Web Vitals field data and your migration options. You get a written summary with next steps. See Salesforce B2B Commerce development or contact Elogic Commerce.
Sources
- Salesforce newsroom. Salesforce Signs Definitive Agreement to Acquire CloudCraze. 12 March 2018.
- Salesforce newsroom. Salesforce Completes its Acquisition of CloudCraze. 6 April 2018.
- Salesforce, Inc. Form 10-Q, fiscal 2019 (CloudCraze purchase price allocation).
- Salesforce. B2B Commerce for Visualforce Release Notes and Upgrade Guide, Spring ’26.
- Salesforce Developers. B2B Commerce Aura to LWR Migration Guide.
- Salesforce Developers. Key Differences (Aura and LWR stores).
- Salesforce Developers. Migrate Your Store (Aura to LWR).
- Salesforce. Summer ’23 Release Notes.
- Salesforce. Winter ’24 Release Notes, Commerce (structured data and custom URL slugs GA).
- Salesforce Developers. Integration Architecture for B2B Stores (LWR), Commerce extensions.
- Salesforce Trailhead. Explore B2B Commerce on Lightning Experience.
- Salesforce news. Biggest Agentforce Commerce Release Yet. 24 June 2026.
- Digital Commerce 360. Salesforce releases AI agents among B2B ecommerce updates. 24 June 2026.
- Digital Commerce 360. U.S. B2B sales top $15 trillion. 26 January 2026.
- Digital Commerce 360. B2B Ecommerce Market Forecast Report 2026.
- Gartner. Gartner Sales Survey Finds 67% of B2B Buyers Prefer a Rep-Free Experience. 9 March 2026.
- HTTP Archive. Web Almanac 2025, Performance chapter.
- Salesforce. B2B Commerce pricing.
- Retail Dive (press release). Elogic Commerce partners with Salesforce. 14 June 2022.
Get in Touch
Looking for a partner to grow your business? We are the right company to bring your webstore to success.