Skip to main content
Talk to an expert
PlatformSalesforce Commerce

Salesforce Commerce for complex ecommerce.

Salesforce Commerce (B2C Commerce Cloud and B2B Commerce) is an enterprise SaaS commerce platform tied closely to the wider Salesforce estate. It earns its place when customer, service and commerce data already live inside Salesforce and the trading model needs that proximity. This page covers where Salesforce Commerce fits, what needs planning properly across PIM, ERP and operational systems, and how iWeb helps shape the right ecommerce architecture around the brief.
600+
Commerce projects
40+
Engineers · on staff
31
Years · systems behind commerce
1995
Founded
Contents · 6 sections
  1. 01Where Salesforce Commerce fits and where it does not
  2. 02Selected case studies.
  3. 03How this platform fits the wider commerce estate.
  4. 04Questions we get asked.
  5. 05Clients we build for.
  6. 06Where this fits in the wider estate.
01 · Where Salesforce Commerce fits and where it does not

Where Salesforce Commerce fits and where it does not

When Salesforce Commerce fits
When the merchant already runs Salesforce CRM and Service Cloud across the business, and the commercial value of a single Salesforce data fabric justifies the licensing weight.
B2C vs B2B Commerce
B2C Commerce Cloud and B2B Commerce are different products with different operating shapes. iWeb is clear about which is on the table and what each does well.
Catalogue depth and PIM
Deep catalogue governance lives in PIM, not in the commerce platform. Akeneo or Salsify behind Salesforce Commerce keeps the boundary clean for trade-scale catalogues.
ERP and stock truth
ERP owns commercial data, pricing and stock. Salesforce Commerce reads the boundary; it does not own the system of record for accounts and prices.
Operational SLAs and trade behaviour
B2B trade behaviour (price lists, depot stock, quote-to-cart, partial dispatch) needs to be designed into the platform shape, not assumed from a B2C blueprint.
Total cost over five years
Salesforce Commerce licensing, implementation partners and operational cost compound. iWeb will give an honest read on whether the commercial case actually holds.
CRM and Service Cloud boundary
Where Salesforce CRM and Service Cloud already run, commerce shares customer and case data through governed APIs rather than parallel customer records.
OMS, WMS and fulfilment
Fulfilment, partial dispatch and returns live in operational systems. Salesforce Commerce orchestrates orders; it does not run the warehouse.
Marketing and lifecycle messaging
Marketing Cloud and lifecycle campaigns trigger from commerce events with the data boundary kept clean.
Search and merchandising surface
Native commerce search plus specialist engines where the query mix justifies one. Merchandising is a continuous activity, not a launch artefact.
Ownership in delivery and support
Implementation partner, internal team and iWeb roles named upfront so support has a route to resolution after launch.
Honest delivery posture
iWeb does not lead net-new Salesforce Commerce builds. Where merchants run the platform, iWeb supports the wider estate (PIM, ERP, operational systems) alongside it; partnership status is held by the client where required.
02 · Relevant iWeb work
03 · Platform fit and estate context

How this platform fits the wider commerce estate.

Fit against operational shape
Catalogue depth, trade complexity, branch logic and ERP integration named honestly before the platform decision is fixed, not assumed from a vendor demo.
Integration boundary with ERP
ERP owns commercial data, pricing and stock. The commerce platform reads the boundary through governed APIs; the boundary itself is the most important design decision in the estate.
PIM as the catalogue system of record
Deep catalogue governance lives in PIM (Akeneo, Salsify or similar). The commerce platform reads from PIM rather than re-modelling product data in the storefront.
OMS and fulfilment surface
Order management, partial dispatch, returns and customer-visible order state live in operational systems. The platform reads what operations actually did.
Search and merchandising
Native search plus specialist engines (Algolia, Constructor.io) assessed against the actual query mix, not a vendor benchmark. Relevance is a continuous activity.
B2B and trade behaviour
Account-only catalogues, customer-specific pricing, depot stock, quote-to-cart and partial dispatch modelled inside the platform rather than patched at the storefront.
Multi-store and multi-territory
Brand, market and territory storefronts modelled with shared catalogue, pricing and operations rather than parallel sites that drift apart.
Total cost over five years
Licence, hosting, engineering and support modelled honestly across the lifecycle, not just year one. The cheap year-one platform is often the expensive five-year one.
Headless and composable trade-offs
Headless or composable storefronts where they earn their place, not as a default. The trade-off between optionality and integration surface is named upfront.
Operational ownership and runbook
Long-term support, releases and integration ownership inside a UK agency that runs platforms day to day, with a written runbook the on-call team can act on.
Replatform sequencing
Where a platform move is on the table, sequencing by domain, traffic share or territory keeps trading live throughout. Big-bang relaunches are rarely the right shape.
Honest "do not move" advice
Where the existing platform is the right answer, iWeb says so on the record. A senior, written read on the brief is the deliverable, not a sales pitch.
04 · Questions we get asked

Questions we get asked.

Does iWeb deliver new Salesforce Commerce implementations?

iWeb does not lead net-new Salesforce Commerce builds. Where merchants already run the platform, iWeb supports the wider estate (PIM, ERP boundaries, operational systems) alongside it.

When is Salesforce Commerce the right choice?

When Salesforce CRM and Service Cloud are already strategic, and the commercial case for a single Salesforce data fabric is genuinely there. Without that, lighter-weight platforms usually fit more cleanly.

How does Salesforce Commerce connect to ERP?

Through APIs and middleware. ERP owns commercial data, pricing and stock. The commerce platform reads the boundary; iWeb makes that boundary explicit and observable.

Where does PIM sit relative to Salesforce Commerce?

PIM (Akeneo, Salsify or similar) holds catalogue truth. Salesforce Commerce reads from PIM rather than re-modelling deep catalogue governance inside the storefront.

Can iWeb give an independent read on a Salesforce Commerce brief?

Yes. iWeb is platform-aware rather than tied to a single vendor and will give a senior, written read on fit, trade-offs and total cost.

How does iWeb choose between platforms?

Against operational shape: catalogue depth, trade complexity, ERP integration, multi-territory rules and five-year cost. The decision is written down with trade-offs, not assumed from a vendor demo.

Where does ERP integration sit in the platform decision?

It is a primary input. Some platforms make ERP integration straightforward, some make it expensive. iWeb names the trade-off rather than hiding it.

Does iWeb deliver headless or composable storefronts?

Where they earn their place. The trade-off between optionality and integration surface is named upfront; composable is not a default.

How is search handled on this platform?

Native search where the query mix supports it; specialist engines (Algolia, Constructor.io) where the catalogue, volume or merchandising appetite justify them. Relevance is a continuous activity.

Where does PIM sit relative to the commerce platform?

PIM owns catalogue truth (attributes, variants, assets, channel readiness). The commerce platform reads from PIM rather than re-modelling deep product data in the storefront.

Can iWeb take over an existing build on this platform?

Yes, where the brief fits. iWeb will give a senior, written read on what is working, what needs remediation and what is honestly fixable, and the first month on support stays deliberately conservative on change.

How does iWeb size a five-year total cost picture?

Licence, hosting, engineering and support across the lifecycle, including the integration surface and operational ownership. The headline year-one number is rarely the honest comparison.

Accreditations & assurance
Gold Commerce Partner
Specialised in Commerce & AI
ISO certified
27001 · 9001 · 42001
Cyber Essentials Plus
Independently verified security
WCAG 2.2 AA
Accessibility embedded by design
Employee-owned
The same team, long term
Next step

Salesforce Commerce brief still open?

Send the brief. You'll get a written response from a senior expert on the platform, ERP and operational realities we'd look at first, not a pitch deck.
Talk to an expertor compare platforms →