Skip to main content
Talk to an expert
SectorWider experience

Wider sector ecommerce experience.

Most of iWeb's engagements sit inside the six core sectors. The team has also worked outside those sectors where the operational shape (B2B trade, complex catalogue, ERP-integrated commerce) is the same. This page covers that wider experience without inventing a new sector page for every example.
600+
Commerce projects
40+
Engineers · on staff
31
Years · complex commerce
1995
Founded
Contents · 6 sections
  1. 01Where wider sector experience fits
  2. 02Selected case studies.
  3. 03How wider sector experience fits iWeb engagements.
  4. 04Questions we get asked.
  5. 05Clients we build for.
  6. 06Where this fits in the wider estate.
01 · Where wider sector experience fits

Where wider sector experience fits

A sector that looks like trade
Account customers, contracted pricing, branch or depot stock, ERP-backed accounts. The shape is familiar even when the sector label is not.
Complex catalogues
Deep attributes, units of measure, pack rules, technical data and editorial governance. PIM is usually part of the answer.
ERP-integrated commerce
Pricing, stock, accounts, invoices, orders and fulfilment flowing between storefront and an operational ERP.
Mixed B2B and B2C
Operators serving both trade and retail audiences from the same catalogue, with different rules per audience.
Regulated or specialist data
Sectors where product data carries compliance, certification or hazard rules and the storefront has to reflect them.
Operational maturity
Sectors where operations already run on serious systems, and the storefront has to plug into them honestly.
Multi-territory operations
Sectors where the merchant trades across territories with different tax, language and content rules per market.
Marketplace and channel presence
Sectors where marketplaces or partner channels are a real sales surface alongside the storefront.
After-sales and service
Sectors where the order is not the end of the relationship: installation, service contracts, warranty and parts.
Returns and credit handling
Sectors where returns, credits and exchanges are a meaningful share of the operation, not an edge case.
Long-cycle buyer journeys
Sectors where buyers research over weeks or months before committing, with showroom, sales-rep or quote touchpoints in the buying journey.
Honest sector fit assessment
Where the sector is genuinely outside iWeb's shape, the team will say so on the record rather than taking a brief that will not pay back. The deliverable is a senior read, not a pitch.
02 · Related work
03 · Wider sector context

How wider sector experience fits iWeb engagements.

How the sector fit is judged
Whether the operational shape (catalogue depth, trade behaviour, ERP integration, multi-territory) genuinely matches iWeb's strengths, not whether the sector label matches a marketing page.
Catalogue and PIM shape
Whether catalogue depth, attribute governance and channel readiness justify PIM, and where the boundary with the commerce platform sits.
ERP and operational integration
Whether the sector runs on a serious ERP and how that integration is shaped against the storefront, accounts, pricing and stock.
B2B, B2C and mixed audiences
Whether the merchant serves trade, retail or both, and how the catalogue, pricing and account rules differ across audiences.
Regulated and specialist data
Where compliance, certification or hazard data shapes the catalogue, the storefront reflects those rules honestly rather than hiding them.
Multi-territory operating model
Territory storefronts, currency, language and per-market compliance treated as a first-class design concern rather than a launch retrofit.
Marketplace and channel surface
Where marketplaces and partner channels are a meaningful sales surface, integration sits alongside the storefront rather than running as a parallel operation.
After-sales and service
Service contracts, installation, warranty and parts catalogues governed where the engagement extends past the order itself.
Returns and credit handling
Returns, exchanges and credit handling treated as core operation rather than an edge case, with the ERP and OMS keeping the numbers honest.
Long buying cycles
Showroom, sales-rep and quote touchpoints in the buying flow wired into the platform where the sector buys over weeks or months.
Proof through governed case studies only
iWeb surfaces sector-adjacent case studies only when those projects are governed. Proof is named, not implied.
Honest fit assessment
Where the sector is genuinely outside iWeb's shape, the team says so on the record rather than taking a brief that will not pay back.
04 · Questions we get asked

Questions we get asked.

When does a sector outside the six core specialisms still fit iWeb?

When the operational shape matches: B2B trade, complex catalogue, ERP-integrated commerce or mixed B2B / B2C. The decision is on the brief, not on the sector tag.

Which commerce platforms come up in wider-sector work?

Mostly Adobe Commerce and Magento, where the team has direct project experience. The operational patterns apply on other commerce platforms where the architecture and project evidence support it.

Which systems usually matter outside the core sectors?

The same ones: a PIM where catalogue complexity warrants it, an ERP for pricing, stock and accounts, and an OMS / WMS where fulfilment crosses multiple locations.

What is iWeb cautious about taking on outside the core sectors?

Briefs where the operational shape is unfamiliar and the timeline does not allow for proper discovery. The team will say so rather than overcommit.

Which trading models suit iWeb outside the six core sectors?

B2B trade, mixed B2B / B2C, ERP-integrated commerce and complex catalogue operations. The decision is on the shape of the brief, not the sector tag.

How does iWeb approach a sector it has less direct proof in?

Discovery first. The operational shape is mapped against the patterns iWeb already runs, and any gaps are named openly. The team will say so when evidence does not exist, rather than borrow it.

Do you have proof outside the six core sectors?

Yes. The work archive lists projects across a wider set of sectors than the six core specialisms. Where a project is not public, iWeb can walk through it under NDA.

Are search, PIM and ERP patterns the same outside the core sectors?

Yes. The boundary between ERP, PIM, search and commerce is the same regardless of sector. What changes is which flows are heavy, not the architecture.

Can iWeb take over an existing build in an unfamiliar sector?

Yes. The team reads the codebase, integrations and incident history first, then writes down what to keep, stabilise or change. The first month on support is deliberately conservative on change.

How is pricing approached for less common sectors?

The same way as for the core sectors. iWeb brackets cost against the integration scope, the data complexity and the support model rather than the sector tag.

Will iWeb take on work outside the six core sectors?

Yes, where the engagement fits the team's strengths and the operational shape (catalogue, ERP integration, trade behaviour, multi-territory) matches. The decision is on the merits of the brief, not on a sector tag.

Does iWeb invent sector proof to fill a landing page?

No. Sector proof surfaces only through governed case studies, and only when those case studies are direct or honestly adjacent. Pages do not exist as a sector-roll-call exercise.

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

Brief sits outside the six core sectors?

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 core sectors →