Skip to main content
Talk to an expert
Platformcommercetools

commercetools for complex ecommerce.

commercetools is a composable, API-first commerce platform for businesses that need flexibility across storefronts, services, channels and systems. This page covers where the model earns its keep, what needs to be planned properly, and how iWeb helps shape the right commerce architecture around the brief.
600+
Commerce projects
40+
Engineers · on staff
31
Years · systems behind commerce
1995
Founded
Contents · 6 sections
  1. 01Where commercetools 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 commercetools fits and where it does not

Where commercetools fits and where it does not

When composable earns its keep
When operating shape genuinely needs independent storefront, checkout, catalogue and order services. For most merchants a well-scoped monolithic platform delivers faster and cheaper.
Cost of optionality
Composable buys flexibility and pays for it with integration surface area. iWeb will give an honest read on whether the brief actually needs the flexibility.
B2B at enterprise scale
commercetools fits where B2B trade complexity (price lists, complex hierarchies, multi-territory) sits at enterprise scale and the merchant has the engineering bench to run it.
PIM and product truth
Catalogue depth still belongs in PIM (Akeneo, Salsify) rather than inside the commerce service. The boundary is the same as on any other platform.
ERP, OMS and stock
ERP and OMS still own commercial data and fulfilment. Composable commerce does not change that; it makes the integration boundary more explicit.
Five-year operating cost
Composable commerce shifts cost from licence to engineering and operations. The total picture across five years is the honest comparison, not year one.
Storefront framework choice
commercetools is headless; the storefront is a separate decision (Next.js, Remix, native). iWeb keeps storefront and commerce service contracts clean.
Service choreography
How storefront, checkout, customer, cart and order services choreograph at runtime is the design work. Done badly, composable becomes a distributed monolith.
Observability across services
Logs, metrics and traces wired across services so incidents have a route to resolution, not a finger-pointing exercise.
Release discipline
Independent service deploys need release governance, contract testing and rollback discipline. iWeb is honest about the engineering maturity required.
Migration off a monolith
Where merchants migrate to commercetools from a monolith, staged migration by domain (catalogue, checkout, order) keeps trading live throughout.
Honest delivery posture
Net-new commercetools builds are not iWeb's primary delivery shape. iWeb works alongside merchants running commercetools on the wider estate (PIM, ERP, OMS) and will say so on first conversation.
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 build on commercetools?

iWeb works alongside merchants running commercetools as part of the wider estate (PIM, ERP, OMS). Net-new commercetools builds are not iWeb's primary delivery shape; the team will be honest about that on first conversation.

When is composable commerce the right answer?

When operating shape genuinely needs independent commerce services and the merchant has the engineering bench to run them well. For most briefs a well-scoped monolithic platform delivers faster.

Where does PIM sit with commercetools?

PIM owns catalogue truth. commercetools reads from PIM via API; it does not replace deep product data governance.

How does commercetools connect to ERP?

Through governed APIs. ERP owns commercial data, pricing and stock. The commerce services read the boundary; the boundary is the most important design decision.

Can iWeb give an independent read on a commercetools brief?

Yes. The read covers fit, total cost over five years, integration surface and operational requirements, not vendor advocacy.

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

commercetools 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 →