Skip to main content
Talk to an expert
PlatformCentra

Centra for fashion and lifestyle ecommerce.

Centra is a headless commerce platform built around fashion and lifestyle brands, with strong wholesale and multi-market handling. It earns its place when the trading model spans D2C, wholesale and several markets, and the catalogue needs to move at brand speed. This page covers where Centra fits, what needs planning around PIM, ERP and operational systems, 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 Centra 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 Centra fits and where it does not

Where Centra fits and where it does not

When Centra fits
When the brief is fashion or lifestyle, the product shape matches Centra's native model (size and colour variants, season-led merchandising), and wholesale sits alongside D2C.
Headless storefront
Centra is headless by design. The storefront is a separate concern, usually Next.js or similar; iWeb works the boundary so the storefront and commerce service stay clean.
Wholesale and D2C in one estate
Centra handles wholesale and D2C together, which is genuinely useful for lifestyle brands operating both channels. The catalogue and pricing rules are the design decision.
Multi-market handling
Multi-currency, multi-language and per-market pricing are native. The implementation work is in market governance, not in the platform.
PIM and product enrichment
Centra is not a PIM. Deep product enrichment, asset governance and channel readiness belong in Akeneo or Salsify behind it.
Order management and fulfilment
Centra orchestrates orders; the operational systems (WMS, 3PL) still own the physical operation. The boundary is defined and observable.
Season and drop merchandising
Season-led merchandising, line sheets and drop scheduling shape the catalogue model and influence release cadence.
B2B account behaviour
Wholesale buyer accounts, price lists and minimums modelled inside Centra alongside D2C, not in a parallel spreadsheet.
Storefront performance
Storefront framework choice (Next.js or similar) and CDN strategy designed against real buying journeys, not synthetic homepages.
Editorial content boundary
Editorial and brand content typically lives in a headless CMS alongside Centra; the storefront composes both.
Ownership and support
iWeb supports the wider estate (PIM, ERP, operational systems) alongside Centra; net-new storefront delivery is scoped honestly per brief.
Honest delivery posture
Net-new Centra storefront delivery is not iWeb's primary shape. iWeb supports merchants running Centra on the wider estate (PIM, ERP, operational systems) and will be honest about that 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 deliver Centra builds?

iWeb works alongside Centra merchants on the wider estate (PIM, ERP boundaries, operational systems). Net-new Centra storefront delivery is not iWeb's primary shape; the team will be honest about that on first conversation.

When is Centra the right fit?

For fashion and lifestyle brands where the product shape matches the platform and wholesale sits alongside D2C. For trade and B2B-heavy operating models, other platforms usually fit more cleanly.

How does Centra handle wholesale?

Natively, alongside D2C in the same catalogue and stock model. The design work is in pricing rules, customer groups and channel governance.

Does Centra need a separate PIM?

For deep catalogue and asset governance, yes. Akeneo or Salsify behind Centra keeps the boundary clean. For small catalogues the native model is often enough.

Where does ERP sit relative to Centra?

ERP owns commercial data, pricing and stock. Centra reads the boundary via APIs. The integration boundary is the most important architecture decision.

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

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