Skip to main content
Talk to an expert
PlatformPlatform-agnostic commerce

Platform-agnostic ecommerce delivery.

iWeb is a UK ecommerce agency with 31 years in ecommerce and a Gold Adobe Commerce partner status, choosing the platform around the brief rather than the other way round. This page covers how iWeb works across ecommerce platforms and where each shape genuinely fits.
600+
Commerce projects
40+
Engineers · on staff
31
Years · systems behind commerce
1995
Founded
Contents · 6 sections
  1. 01Platform decisions iWeb helps with
  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 · Platform decisions iWeb helps with

Platform decisions iWeb helps with

The platform decision
A clean read on the trade-offs between Adobe Commerce, Magento, Shopify Plus, BigCommerce and composable, against your actual operational shape.
B2B and trade complexity
Trade accounts, customer-specific pricing, branch stock and ERP integration. Some platforms model these well, some do not.
Catalogue and PIM fit
Where the catalogue lives, and which platforms keep that boundary clean.
ERP and operational fit
Which platforms make ERP integration straightforward and which make it expensive.
Total cost over five years
License, hosting, engineering and support modelled honestly, not just year one.
Future moves without lock-in
Decisions made today that do not paint future moves into a corner.
Search and merchandising fit
Native search, specialist engines and merchandising tooling assessed against the actual query mix, not the vendor demo.
Composable vs monolith trade-offs
Where composable earns its place and where a well-scoped monolithic platform delivers faster and cheaper.
Operational support after launch
Which platforms iWeb can support long-term, and how the support model is shaped for each.
Replatform sequencing
How a platform move is sequenced (by domain, by traffic, by territory) so trading stays live throughout.
Honest "do not move" advice
Where the existing platform is the right answer and a rebuild would not pay back, iWeb will say so on the record.
Decision read deliverable
A senior, written read on platform fit, integration boundary, total cost over five years and operational ownership, sized to the brief rather than as a parallel engagement.
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.

Is iWeb tied to Adobe Commerce or Magento?

iWeb has the deepest history on Adobe Commerce and Magento. It is not the only platform iWeb delivers on. Choice follows the brief.

When does Shopify Plus make sense?

When the operational shape (catalogue, trade complexity, ERP integration) fits inside Shopify Plus without bending it. iWeb will say so if it does not.

What about composable / headless?

Composable is justified for specific shapes, not as a default. iWeb names the trade-offs honestly rather than treating composable as a buzzword.

Will iWeb tell me a platform is wrong for my business?

Yes, where it matters. A senior, written response to the brief is the point, not a sales pitch.

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.

Will iWeb tell us a platform is wrong for our business?

Yes, where it matters. A senior, written response to the brief is the deliverable, not a sales pitch; that includes saying "do not move" when the existing platform is the right answer.

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

Platform decision 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 see platforms →