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 · 6 sections
  1. 01What iWeb delivers on Magento.
  2. 02Selected case studies.
  3. 03How Magento connects to ERP, PIM and operations.
  4. 04Magento Open Source vs Adobe Commerce.
  5. 05Questions we get asked.
  6. 06Related sectors, services and technology.
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. Buyer question: who actually owns the Magento codebase decisions once the launch team steps back, and are those people still here in year two?
Proven with Huws Gray Building Supplies & Solutions and Covers Timber & Builders Merchants.
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. Buyer question: which is the bigger risk to sequence around first, an unsupported Magento 1 estate, an unmaintained Magento 2 build, or a bespoke stack no one wants to touch?
Proven with Bidfood and Just Kampers.
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. Buyer question: which extensions and community modules are actually fighting each release, and which of them have to be retired before any new roadmap work starts?
Proven with Demon Tweeks and Arnold Laver.
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. Buyer question: without Adobe vendor support behind the platform, who owns a Magento incident at 6am, and is that written down anywhere the team can act on?
Proven with Huws Gray Building Supplies & Solutions and Covers Timber & Builders Merchants.
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. Buyer question: which trade rules genuinely justify a governed custom module in Magento Open Source, and which belong in the ERP where finance already owns them?
Proven with Arnold Laver and Huws Gray Building Supplies & Solutions.
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. Buyer question: without the Commerce B2B suite on the table, where does customer-specific and contract pricing live, and how does it stay in agreement across cart, quote and invoice?
Proven with Demon Tweeks and Bidfood.
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. Buyer question: is the catalogue big and volatile enough to earn a governed PIM alongside Magento, or is holding product truth inside Magento still the honest answer for now?
Proven with Just Kampers and Covers Timber & Builders Merchants.
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. Buyer question: what does the depot team already trust to be the order of record, and does the Magento storefront read that system or hold a parallel state that drifts?
Proven with Huws Gray Building Supplies & Solutions.
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. Buyer question: does moving to Hyvä pay for itself against the current storefront budget, or does the theme just need honest performance work first?
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. Buyer question: is native Magento search carrying the current query mix, or is it quietly hiding revenue on the long tail no one is looking at?
Proven with Arnold Laver and Bidfood.
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. Buyer question: one Magento estate across brands and territories with shared release discipline, or parallel builds that inevitably drift into separate projects?
Proven with Demon Tweeks and Just Kampers.
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. Buyer question: how many accumulated patches and community extensions have to come out before the next Magento upgrade is safe to schedule against a trading calendar?
02 · Proof
03 · Integration patterns

How Magento connects to ERP, PIM and operations.

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.
Proven with Covers Timber & Builders Merchants and Bidfood.
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.
Proven with Arnold Laver and Covers Timber & Builders Merchants.
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.
Proven with Huws Gray Building Supplies & Solutions and Demon Tweeks.
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 · Platform comparison

Magento Open Source vs Adobe Commerce.

Magento Open Source and Adobe Commerce (formerly Magento Commerce) share the same core codebase. The choice is a commercial one about licence, B2B suite, hosting and support - not a fork of the platform. iWeb delivers both.

Dimension
Magento Open Source
Adobe Commerce
Licence
Free, open-source licence. No Adobe fee.
Commercial licence from Adobe, priced on gross merchandise value.
Core codebase
Same Magento 2 core, without the Commerce-only modules.
Same Magento 2 core with the Commerce modules layered on top.
B2B suite
Company accounts, shared catalogues, quotes and approver rules are achievable through extensions or custom modules, not a shipped suite.
Company accounts, shared catalogues, quotes, requisition lists and approver rules included.
Content and page building
Community Page Builder and third-party modules. No native staging.
Page Builder, staging and preview, content scheduling included.
Hosting
Any competent Magento-capable host. No mandated cloud.
Adobe Commerce Cloud is the reference target. Self-managed on-premise is also supported.
Support
No vendor support. Agency support and the Magento community.
Adobe vendor support on the platform itself, alongside agency support.
Upgrades
Same release cadence for the core. Fewer moving parts to upgrade.
Adobe releases apply to both editions. Commerce-only modules add their own upgrade surface.
Typical fit
Teams that already run a mature Magento 2 estate, prefer full stack control, and cover B2B behaviour through governed extensions or bespoke code.
Established B2B and B2C operations that want the Commerce B2B suite, staging and vendor-backed support in the operating model.

iWeb delivers replatforms, builds, rescue and support on both editions. The recommendation follows the trading pattern and ERP shape, not a platform preference.

05 · 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.

How does Magento Open Source differ from Adobe Commerce?

Same core codebase, different edition. Adobe Commerce adds the B2B suite, staging and preview, page builder, hosted search and Adobe Commerce Cloud as a supported hosting option. Magento Open Source is the free edition without those. The right choice is on operational fit and total cost, not on the badge.

Is Hyvä worth adopting on Magento?

Where storefront performance is the bottleneck, yes. Hyvä frontends are delivered with measurable page-type budgets and an image pipeline held against real trade traffic. Where the native frontend already meets the brief, iWeb will say so rather than add a build target the team has to support.

Can Magento integrate with Sage?

Yes. Magento is integrated with Sage alongside Business Central, Epicor BisTrack, Intact iQ, NetSuite and bespoke ERPs. Pricing, stock, accounts, orders and invoices flow through a governed middleware boundary with a written owner for each direction.

How long does a Magento replatform take?

Most Magento replatforms iWeb runs land between four and nine months end to end. The variable is integration scope with the ERP, PIM and account model, not the front end. Sequencing by territory, brand or traffic share keeps the business trading while the new platform is brought up.

Do you deliver Magento for builders merchants and trade?

Yes. Builders merchants and wider trade estates are a core sector for iWeb Magento work: branch stock, trade accounts, customer-specific pricing and ERP integration with systems such as Epicor BisTrack, Intact iQ, Kerridge and Business Central.

How is search implemented on Magento?

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. Search is treated as a continuous activity, not a launch deliverable.

Do you apply AI for Commerce on Magento estates?

Yes, where the AI change earns its place against a live commerce metric such as search relevance, merchandising, content operations or support workload. Magento is one of the platforms iWeb runs AI for Commerce work on; the pattern is governed by outcome rather than by tool.

Can Magento publish to marketplaces alongside the storefront?

Yes. Marketplace and channel integrations sit alongside the Magento storefront, with product data governed in the PIM and orders reconciled through the OMS. The storefront owns the buying experience; channels get their own scoped view of the catalogue.

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 →