Skip to main content
Talk to an expert
PlatformMagento

Magento Open Source for complex ecommerce.

iWeb has worked on Magento and Adobe Commerce for years, across builders merchants, foodservice, automotive parts, manufacturing, retail and health and wellness clients. We replatform, rescue and run Magento 2 estates and integrate them into the ERP that actually runs the business.
600+
Commerce projects
40+
Engineers · on staff
31
Years · systems behind commerce
1995
Founded
Contents · 5 sections
  1. 01What iWeb delivers on Magento.
  2. 02Selected case studies.
  3. 03Where Magento sits in the wider estate.
  4. 04Questions we get asked.
  5. 05Where this fits in the wider estate.
01 · What iWeb delivers on Magento

What iWeb delivers on Magento.

Senior Magento engineering
Magento and Adobe Commerce delivery from a UK ecommerce agency, not a contractor pool. Architecture, code and release decisions sit with named senior engineers who stay with the estate after launch.
Replatform onto Magento 2 and Adobe Commerce
Moves from Magento 1, bespoke stacks and unfit SaaS planned around live trading. Sequencing by territory, brand or traffic share keeps the business trading while the new platform is brought up.
Rescue and stabilisation
Stalled, slipping or unstable Magento builds taken on with a senior diagnosis and a written remediation plan. The first month on support stays deliberately conservative on change while the estate is brought back under control.
Long-running managed support
Incidents, releases, upgrades, performance and platform health run by a named UK team with an on-call rota and a written runbook. Storefront, middleware and ERP sit under one accountable route.
B2B trade behaviour
Account hierarchies, customer-specific pricing, branch and depot stock, approver chains and quote workflows modelled inside Magento. Trade rules live in the platform rather than as bolt-on extensions that fight each release.
ERP integration
Pricing, stock, accounts, orders and fulfilment need clear ownership between Magento, the ERP and middleware. The important decision is what is real-time, what is scheduled and who owns failures after launch.
PIM as the product data source
Catalogue truth lives in PIM, not in Magento. Akeneo or an existing PIM owns attributes, enrichment, assets and channel readiness so the storefront stays a trading surface rather than a product database.
OMS, WMS and fulfilment
Order capture, dispatch, partial fulfilment and returns live in the operational systems that own them. The storefront reads what operations actually did so customer-visible state matches the warehouse.
Hyvä and storefront performance
Hyvä frontends with measurable page-type budgets, image pipeline discipline and caching strategy held against real trade traffic. Performance is treated as a continuous metric, not a launch artefact.
Search and merchandising
Native, Algolia or Constructor chosen against the actual query mix and catalogue depth. Merchandising rules respect long-tail B2B, account-only visibility and considered-purchase journeys rather than retail defaults.
Multi-store and multi-territory
Brand, market and territory storefronts run as one operation with shared catalogue, pricing and release discipline. Locale, currency and tax sit inside the platform rather than per-store patches.
Upgrades and technical debt
Magento upgrade paths, extension cleanup and removal of accumulated patches handled without freezing the trading roadmap. Release windows respect trade days rather than engineering convenience.
02 · Proof
03 · Integration patterns

Where Magento sits in the wider operational estate.

ERP-connected ecommerce
Pricing, stock, account records, orders and fulfilment need clear ownership between Magento, ERP and middleware. The important decision is what should be real-time, what can be scheduled and who owns failures after launch.
PIM as the product data source
Magento should not become the place where product truth is manually rebuilt. A PIM such as Akeneo can own attributes, enrichment, assets and channel readiness while the storefront handles trading, search and checkout.
OMS, WMS and fulfilment handoff
Order capture, dispatch, partial fulfilment and returns live in operational systems that the depot team trusts. The storefront reads what the warehouse actually did rather than holding a parallel order state.
Search and merchandising
Search runs as a continuous activity, not a launch deliverable. Native, Algolia or Constructor chosen against the real query mix, with merchandising rules that respect account-only catalogues and trade behaviour.
Storefront performance under trade load
Page-type performance budgets held against pre-7am trade traffic and seasonal peaks. Hyvä, caching strategy and image pipeline tuned to how buyers actually arrive, not synthetic test runs.
B2B accounts and contract pricing
Account hierarchies, contract pricing, shared catalogues, approver chains and quote-to-order modelled where the architecture and extensions support it. Pricing comes from the ERP and has to hold across cart, quote and invoice.
Multi-store and multi-territory
Brand, market and territory storefronts run as one operation with shared catalogue, pricing and release discipline. Locale, currency and tax behaviour sit inside the platform rather than per-store retrofits.
Upgrades and technical debt
Magento upgrade paths, extension cleanup and removal of accumulated patches handled without freezing the trading roadmap. Release control is written down so trade days are protected from unsafe changes.
Hosting, monitoring and release control
Cloud or self-managed Magento hosting wired into monitoring, alerting and an explicit release calendar. Deploy windows, freeze periods and rollback paths reflect actual trading patterns, not vendor defaults.
Migration off legacy Magento
Replatform paths from Magento 1 and unmaintained Magento 2 estates onto a supported Magento or Adobe Commerce footprint. Sequencing keeps the business trading rather than betting the year on a single launch event.
Payments, tax and fraud
Payment, tax and fraud checks sit inside the order flow, not beside it. Refunds, captures, failed payments and reconciliation need clear ownership so support teams are not left guessing the next morning.
Support and technical ownership
Long-running ecommerce support only works when ownership is written down. Storefront, middleware, ERP, releases and incident response need one accountable route rather than a queue of disconnected suppliers.
04 · Questions we get asked

Common questions.

Do you still support Magento?

Yes. iWeb actively supports and develops Magento Open Source for clients whose operational fit is right. Magento is treated as a current platform, not a legacy one.

Can you rescue a Magento project?

Yes. Magento rescues typically focus on platform stability, security posture, integration health and release process before any larger change is scoped.

When should Magento merchants consider replatforming?

When the cost of staying outweighs the cost of moving: ERP integration is brittle, the catalogue cannot model how you sell, releases are slow, or security and patching are slipping. The decision is commercial first.

Can Magento connect to ERP and PIM?

Yes. Magento is integrated with Microsoft Dynamics 365 Business Central, Epicor BisTrack, Intact iQ, NetSuite, Sage and bespoke ERPs, and with Akeneo PIM as the product data source.

Will Magento Open Source remain viable?

Magento Open Source remains viable when it is patched, supported and integrated to a current standard. Where that has slipped, the choice is whether to invest in restoring it or to plan a move to Adobe Commerce or another platform on commercial grounds.

When is Magento Open Source the right platform today?

When the operational fit is right, the codebase is patched and supported, and the cost of moving outweighs the cost of staying. Magento Open Source still earns its place for B2B and trade estates that are integrated and stable.

When does Magento Open Source stop being viable?

When security patching has slipped, integrations are unsupported, releases take weeks and the team supporting it has thinned out. At that point the choice is to invest in restoring it or to plan a move.

Do you still migrate Magento 1 sites?

Yes. Magento 1 sites are replatformed to Adobe Commerce, Magento Open Source on a current version or another commerce platform, depending on the commercial brief. The migration is treated as a replatform, not a patch.

Do you support Hyvä or PWA frontends on Magento?

Yes, where they earn their place. iWeb works on the frontend pattern that fits the brief rather than insisting on a single approach.

Can Magento support B2B trade accounts and contracted pricing?

Yes. Magento supports company accounts, buyer roles, account-only catalogues and contracted pricing when integrated against the ERP. The pattern is the same as on Adobe Commerce; the surface area differs.

How are Magento upgrades and security patches handled?

Security patches and platform upgrades sit on a written cadence: assessment, regression in staging and a controlled release. We look at the extension footprint and customisation depth first, because that is what sets the realistic window.

How is Magento hosting and monitoring usually run?

Magento runs well on Cloud or self-managed infrastructure; the deciding factor is the team that has to support it. Monitoring covers storefront, integrations and the ERP boundary so incidents are tracked across the whole estate, not blamed on the web tier.

Next step

Have a Magento brief?

Send the brief. You'll get a written response from a senior expert, scope, integrations and the operational context we'd look at first, not a pitch deck.
Talk to an expertor browse all platforms →