Skip to main content
Talk to an expert
TechnologyPlatform-agnostic, integration-specialist

The platforms, PIM systems and ERPs we work with.

iWeb is a UK ecommerce agency with 31 years in ecommerce. The team replatforms, builds, rescues and supports complex B2B and B2C commerce, governs product data, and integrates commerce with the ERP, OMS, WMS, search, CMS and marketplace systems that already run the business. The platform is chosen around the brief, not the other way round.
600+
Commerce projects
40+
Engineers · on staff
31
Years · systems behind commerce
1995
Founded
Contents · 6 sections
  1. 01Platforms, PIM, ERP and operational systems iWeb covers
  2. 02Selected case studies.
  3. 03How this system fits next to commerce, PIM and ERP.
  4. 04Questions we get asked.
  5. 05Clients we build for.
  6. 06Where this fits in the wider estate.
01 · Platforms, PIM, ERP and operational systems iWeb covers

Platforms, PIM, ERP and operational systems iWeb covers

Ecommerce platforms
Adobe Commerce, Magento, Shopify Plus, BigCommerce and composable stacks. The list is short because it is the list iWeb actually delivers on, not a vendor directory.
PIM and product data
Akeneo PIM as the catalogue system of record alongside Adobe Commerce, Magento and other platforms. Enrichment, governance and channel readiness, not a parallel product database.
ERP and operational systems
Microsoft Dynamics, SAP, Oracle, NetSuite, Sage, Epicor, Kerridge, Intact, Infor and trade ERPs integrated to commerce so price, stock, accounts and orders stay honest.
OMS and order orchestration
Order management, partial dispatch, branch fulfilment and returns wired into the storefront so customers see what operations actually did.
WMS and warehouse
Warehouse and depot systems integrated to commerce for live stock, pick paths and dispatch confirmations, not nightly batch approximations.
Search and merchandising
Native platform search, Algolia and Constructor.io assessed against the actual query mix. Relevance is a continuous activity, not a launch task.
CMS and content
Contentful, Adobe Experience Manager and platform-native CMS where editorial and commerce need to move at different speeds without breaking each other.
Marketplaces and channels
Mirakl and partner channels integrated alongside the storefront rather than as a parallel operation, with one product spine across the estate.
Payments and risk
Payment service providers, alternative payment methods, account credit, deferred payment and fraud tooling integrated against the actual buyer mix.
Composable and specialist tech
Headless and composable stacks where they earn their place. The trade-off between optionality and integration surface is named upfront, not assumed.
Vendor partnerships, honestly
Where iWeb holds a partnership it is named; where the client holds it, the team works alongside that arrangement. No badge-led recommendations.
Honest "do not change" advice
Where the existing platform or system is the right answer, iWeb will say so on the record. A senior, written read on the brief is the deliverable, not a sales pitch.
02 · Related work
03 · Integration and operational context

How this system fits next to commerce, PIM and ERP.

Where this system lives in the estate
The integration boundary with commerce, PIM, ERP and operational systems named, versioned and observable, not implied by a connector setting.
Catalogue and PIM separation
Catalogue truth lives in PIM. This system reads from PIM rather than maintaining a parallel product record that drifts away from it.
ERP boundary and commercial data
ERP still owns price, stock and accounts. This system orchestrates around the ERP rather than replacing it; the boundary is the design decision.
Storefront and customer surface
How customers see the output of this system on the storefront (search, content, order state, payments) governed with the same rigour as the commerce platform itself.
Real-time vs scheduled sync
Read paths cached at the storefront boundary, writes posted through monitored queues, reference data refreshed on a defined cadence tuned to ERP and PIM load.
Multi-territory and locale handling
Locale-aware behaviour wired in early, not bolted on per project. Translation, currency and per-market rules belong inside the platform rather than the storefront.
Governance and editorial workflow
Approval, completeness and audit workflows that match how the merchant actually edits, releases and runs the estate day to day.
Operational telemetry
Throughput, failures, queue depth and reconciliation reports surfaced as visible signals with on-call ownership, not as silent backlog.
AI under governance
AI features (query understanding, attribute mining, recommendations) scoped to where they earn their place, with decision logs and override controls.
Long-term support and incident response
Releases, incidents and upgrades governed under the same operating model as the wider estate, with a written runbook the on-call team can act on.
Takeover and stabilisation
Inherited builds audited, stabilised and documented before any larger change. The first month on support is deliberately conservative on change.
Honest vendor independence
iWeb names the right tool for the brief rather than the closest partner badge. Decisions are written down with their trade-offs, not assumed.
04 · Questions we get asked

Questions we get asked.

Is iWeb tied to a single platform vendor?

No. The deepest history is on Adobe Commerce, Magento and Akeneo PIM. The team also delivers on Shopify Plus, BigCommerce and composable stacks where the brief fits.

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 technology decision?

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

Why is Akeneo PIM listed alongside commerce platforms?

Because for deep catalogues PIM is the system of record, not the storefront. Adobe Commerce, Magento and other platforms read from PIM rather than re-modelling product data.

How does iWeb pick a search engine?

Against the actual query mix and merchandising appetite. Native search where it fits; Algolia or Constructor.io where the catalogue, volume or relevance work justifies them.

Where do OMS and WMS sit in the picture?

OMS owns the order lifecycle and customer-visible state; WMS owns warehouse and depot execution. Commerce reads what they did rather than reinventing it.

Does iWeb work with marketplaces?

Yes, where they are a meaningful sales surface. Mirakl and partner channels integrate alongside the storefront with one product spine across the estate.

What about CMS and editorial systems?

Contentful, Adobe Experience Manager and platform-native CMS where editorial and commerce need to move at different speeds without breaking each other.

Can iWeb take over an inherited integration?

Yes. The first month on takeover is deliberately conservative on change: audit, stabilise and document before any larger move.

How are vendor partnerships handled?

Honestly. Where iWeb holds a partnership it is named; where the client holds it, the team works alongside that arrangement. Recommendations are not badge-led.

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

Yes, where it matters. A senior, written response to the brief is the deliverable, including "do not move" where the existing platform or system is the right answer.

How long does a technology review take?

A short, paid technology decision read typically lands inside two to four weeks against a defined brief, not an open-ended consultancy engagement.

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

Have a technology decision to make?

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 erp integrations →