Magento 2 and Adobe Commerce: where the platform earns its keep
Magento 2, shipped either as the free Open Source edition or as Adobe Commerce, fits a project built around a large or fast-growing catalogue, several stores or languages under one back office, or B2B pricing and quoting rules; it is the wrong route for a small brochure site or a workflow no commerce platform models. OutsourcingVN is operated by Netbase JSC, and this page keeps platform fit separate from any vendor claim.
Submit a project See the Netztech migration recordReviewed by David Nguyen (CEO) · Updated 29 Sep 2026
Where Magento fits, and where it doesn't
Good fit
- A catalogue with thousands of SKUs, configurable products or complex attribute sets
- Several storefronts, languages or currencies run from one shared catalogue and back office
- B2B pricing tiers, negotiated quotes, company accounts or purchase-order checkout
- Deep integration with an ERP, PIM or warehouse system, and an in-house team to operate it
Another route fits better
- A few dozen products with no variants, where a lighter cart adds needless overhead
- A single small storefront, where WooCommerce usually costs less to run
- A workflow the checkout was never built to model, where a custom application build fits better
- A team with no capacity to patch and test a commerce platform on its own release cadence
Implementation patterns
Two editions cover most projects. Magento Open Source is the free, self-hosted core: catalogue, cart, checkout, customer accounts and the extension ecosystem, run on infrastructure you choose and patch yourself. Adobe Commerce adds B2B functionality, Page Builder, advanced promotions, business intelligence and a managed cloud hosting option on top of the same core, at the cost of a recurring platform fee that Open Source does not carry.
A common architecture keeps Magento as the commerce and order engine while a separate layer carries presentation or a headless front end such as Next.js, so checkout logic and catalogue rules stay in Magento while the storefront renders independently. Netbase built exactly this pairing in the headless reward shop platform for a Dubai-based loyalty and rewards technology company that is not named: Magento 2 Open Source with a Next.js front end, individually branded shops per client programme, a hybrid points-plus-cash checkout, a multi-vendor module with fulfilment routing, and integrations with the client's own points middleware over four delivery phases spanning 3.5 to 4.5 months.
A second pattern is the platform migration itself. In the Netztech migration record, Netbase delivered a Magento 1 to Magento 2 Commerce migration in 35 working days, moving 11 extensions across with installation, configuration, customization and data transfer for each one. That project shows the shape of the work when a store's platform reaches end of life and every extension has to be re-proven, not assumed to carry over unchanged.
Trade-offs to weigh
Every Magento decision moves cost somewhere else rather than removing it.
- Licence fee against hosting and headcount. Open Source avoids a platform fee but assumes an internal or contracted team capable of patching, scaling and securing the stack. Adobe Commerce's fee buys managed cloud infrastructure and features Open Source does not carry.
- Extension breadth against upgrade risk. A large extension marketplace covers most requirements quickly, but each installed extension is one more dependency that must be re-tested on every core upgrade.
- Feature depth against launch speed. Magento's catalogue and pricing engine handle complexity that simpler platforms cannot, at the cost of a longer build than a template storefront.
- Flexibility against patch discipline. A self-managed Magento store that skips security patches becomes the more exposed choice over time, regardless of edition.
A worked scenario
A hypothetical distributor sells the same catalogue to retail customers at standard rates and to wholesale accounts on negotiated terms, through three regional storefronts that share one warehouse feed. A single-storefront cart cannot hold that pricing model without workarounds stacked on workarounds.
- Milestone one stands up the shared catalogue and the retail storefront, with the warehouse feed wired to stock and pricing.
- Milestone two adds company accounts, tiered pricing and a quote-to-order flow for wholesale buyers, scoped against the B2B rules the business already runs on paper or in email.
- Milestone three launches the second and third regional storefronts from the same catalogue, each with its own domain, language and currency.
Each milestone closes against a written acceptance checklist before the next one starts, so pricing rules are proven on one storefront before they are copied to the rest.
Where AI fits on a Magento storefront
The categories that pay off fastest on a commerce platform are catalogue search and product-attribute enrichment, a support assistant that answers order-status and policy questions before a human ticket opens, and personalised recommendation logic layered onto existing merchandising rules. None of it replaces the checkout and pricing engine Magento already owns; it sits alongside it. Netbase works with commercial and open-source AI models chosen per project, with no vendor partnership implied, and the custom product engineering service scopes where an AI feature belongs against where a merchandising rule already does the job.
What to check before you commit
Adobe's own product-availability documentation lists Magento Open Source and Adobe Commerce 2.4.9 as the current release as of September 2026, with supported versions running from 2.4.4 through to it; Adobe tests and supports that matrix directly, and versions outside it may still run but carry no official support. Confirm four things with any vendor before scoping a build:
- Which release line, and its PHP, database and search-engine requirements, checked against the current compatibility matrix rather than an older tutorial.
- Which edition, since Open Source and Adobe Commerce diverge on B2B features, Page Builder and hosting.
- The extension inventory, each one named, versioned and owned by someone who will re-test it on the next upgrade.
- The patch and upgrade cadence your team, or the team supporting you, actually commits to, since an unpatched Magento install is a recurring security exposure rather than a one-time risk.
Failure modes
-
An extension count nobody wrote down
A store with a dozen undocumented extensions turns every core upgrade into an investigation before it can become a plan.
-
B2B rules bolted onto a B2C cart
Tiered pricing and purchase orders added late tend to fight the checkout instead of extending it.
-
Headless taken on without a reason
Splitting the front end from Magento adds real engineering surface; it earns its cost only when the storefront needs independent release cycles or a framework like Next.js for performance or SEO.
-
A migration treated as a lift-and-shift
The Netztech project covered 11 extensions individually because assuming they would carry over unchanged is where migrations slip.
What Netbase has built on Magento
Netbase delivered the Netztech migration described above, in 35 working days across 11 extensions, with no business result recorded for the project; the duration and scope are the record. Separately, in the Magento recovery and hardening record, Netbase scoped and ran a three-phase recovery of a compromised Magento store for an existing client: investigation and a damage assessment, malware and backdoor removal with core files restored at the matching version, then file repair and hardening, typically 6 to 13 days depending on the damage, with no guarantee of full recovery implied. Representative commerce work on the platform also includes Magento stores built with companion Android and iOS apps for clients that are not named: a women's fashion retailer in the Netherlands, an omnichannel fashion retailer in Nigeria, and a US parts and equipment seller.
Each of that company's client programmes gets its own branded reward shop, shoppers pay with a mix of points and cash, and orders route to the right supplier.
Keep Reading
For an existing client store running Magento that had been compromised, Netbase scoped a three-phase recovery: investigate and assess, clean and restore, then repair and harden.
Keep Reading
No business result was recorded for this project, so none is published.
Keep ReadingCommon questions
It depends on whether B2B features, Page Builder and managed cloud hosting are worth a recurring platform fee to you, and whether your team can operate self-hosted infrastructure. Both share the same core, so the catalogue and checkout logic transfer either way.
Yes. Netbase's Dubai reward-shop platform paired Magento 2 Open Source as the commerce engine with a Next.js front end, which is the pattern to reuse when the storefront needs independent release cycles.
The Netztech migration took 35 working days across 11 extensions; your own timeline depends on your extension count, data volume and how much customization has to carry over.
Netbase's recovery pattern runs investigation, cleanup and hardening in three phases, typically 6 to 13 days, with security patches applied and the administrator area hardened at the end; full recovery is never guaranteed in advance.
Engineering on the platform itself: the Netztech migration from Magento 1 to Magento 2, the recovery and hardening of a compromised store, and the Magento storefront work in the loyalty and web-to-print records linked above.
Where Netbase applies this stack
Custom product engineering for a bounded release outcome
One defined release of your product, built to named outcomes and handed over with acceptance evidence.
Learn More
Legacy application modernization, one bounded capability at a time
The code is assessed first, then one bounded capability moves at a time, with a way back.
Learn More
From platform decision to project
Bring your catalogue size, storefront count and any B2B pricing rules to a brief, and a custom product engineering scope can tell you within discovery whether Magento, WooCommerce or a different route carries the workflow best; the other four platform pages sit under Technologies. If your current Magento store only needs a security fix, an extension upgrade or an integration, legacy application modernization is usually the cheaper path, and the e-commerce platform modernization checklist covers that decision for any platform. OutsourcingVN is operated by Netbase JSC and is Netbase's own outsourcing-services platform; submit a project with your current platform version and extension list.