Magento 2
A practical guide to what Magento 2 is, what it’s good at, what it costs, and when it’s the right choice.
Magento 2 is a powerful eCommerce platform you run and own: it’s self-hosted (or cloud-hosted via a provider), highly extensible, and built for businesses that need custom workflows, advanced catalog logic, and integrations with other systems. Unlike SaaS platforms with fixed limits, Magento 2 is designed to be shaped around your business model, whether you sell B2C, B2B, or both.
Best for:
complex catalogs, B2B, multi-store, custom integrations
Typical build paths
classic / Hyvä / headless
Ongoing needs
hosting + maintenance + upgrades
TL;DR: Magento 2 in 60 seconds
What is Magento 2?
Magento 2 (including Adobe Commerce) is a flexible eCommerce platform built for businesses that have outgrown simpler platforms. If your catalog is complex, your pricing logic is non-standard, or you're running B2B alongside B2C — this is where Magento earns its place. You own the platform entirely: the code, the data, the infrastructure, and the roadmap.
Who is it for?
Mid-market and enterprise merchants or fast-growing brands who need custom checkout or catalog logic, B2B features, multi-store setups, or complex integrations with ERP, CRM, or PIM systems.
Key strengths
Deep customization, strong ecosystem, multi-store/multi-language support, robust catalog management, and a proven path for B2C + B2B. Works well with modern frontends like Hyvä or headless when performance and UX matter.
Key trade-offs
Higher total cost of ownership than SaaS: you'll need experienced developers, good infrastructure, and ongoing updates. Poorly chosen extensions or weak hosting can hurt speed and stability. Many merchants start with a focused MVP build — this lets you launch faster, validate business value, and learn what custom features really matter before deeper investment.
→ Not sure if Magento is right for you? See the decision guide below.
Is Magento 2 Right for Your Business?
Use this quick matrix to self-qualify. If most of your situation maps to the left column, Magento 2 is likely worth the investment. If it maps to the right, a SaaS platform (like Shopify) will serve you better.
| ✓ Consider Magento 2 when… | ✗ Consider SaaS (Shopify, BigCommerce) when… |
|---|---|
| You have 1,000+ SKUs, complex attributes, or configurable products | You have under 500 SKUs with straightforward catalog needs |
| You need B2B features: company accounts, shared catalogs, quotes, approvals | You sell B2C only and need standard checkout out of the box |
| You run or plan to run multiple storefronts, brands, or countries from one backend | You need a single storefront launched quickly |
| You require custom checkout logic, contract pricing, or procurement workflows | You prefer apps + themes over custom engineering |
| You integrate with ERP, CRM, PIM, WMS, or marketplaces | You want minimal ongoing maintenance responsibility |
| You need full ownership of your data, code, and infrastructure | You're a startup validating a concept with a tight timeline and budget |
💡 Starting point tip
Many merchants launch a focused MVP on Magento: a single storefront, core catalog, essential integrations. This validates business value faster and reveals what custom features genuinely matter before deeper investment. You don't need to build everything on day one.
What Magento 2 Includes Out of the Box?
Magento 2 is not a plug-and-play template store. It's a modular system built to be shaped around your business model — whether you sell B2C, B2B, or both.
Core Capabilities
| Area | What's included |
|---|---|
| Admin panel | Manage products, customers, content, promotions, and store configuration from one backend |
| Catalog management | Complex product types (simple, configurable, bundled, virtual, downloadable), attributes, categories, layered navigation, pricing rules |
| Checkout | Customisable checkout flow, payment methods, shipping methods, taxes, promotions, and discount logic |
| Order management | Orders, invoices, shipments, refunds, customer accounts, and built-in reporting |
| Multi-store support | Multiple storefronts, brands, currencies, and languages managed from a single admin |
| Extensibility | APIs, webhooks, and a module system for custom features and third-party integrations |
A Large Ecosystem
One reason Magento 2 stays relevant is its ecosystem: thousands of extensions covering payments, shipping, marketplaces, SEO, B2B tools, and more. There is a mature developer community, established agencies, and proven patterns for performance, security, and long-term maintenance.
The flip side: you need a team that can choose extensions responsibly, avoid conflicts, and maintain upgrades without breaking business-critical flows. Extension governance is not optional — it is one of the biggest cost and stability levers on the platform.
Magento 2 Editions: Open Source vs. Adobe Commerce
Magento 2 comes in two main editions. The right choice depends on your feature requirements, budget, and support expectations.
| Magento Open Source | Adobe Commerce | |
|---|---|---|
| Licensing cost | Free (you pay for development, hosting, maintenance) | Annual license — quote-based, typically tied to GMV |
| Core features | Strong catalog, configurable checkout, multi-store, extensible via modules | Everything in Open Source + B2B suite (company accounts, quotes, shared catalogs), Page Builder, Content Staging, advanced merchandising |
| Typical merchant | SMB to mid-market; businesses with a strong in-house or agency team | Mid-market to enterprise with complex B2B, multi-brand, heavy content needs |
| Support model | Community support + your agency and hosting provider — your agency is effectively your support tier | Adobe support tickets, dedicated TAMs at higher tiers, documented SLAs — still commonly supplemented by an agency |
| Hosting | Self-hosted or managed hosting providers — you choose and manage infrastructure | Flexible: self-host like Open Source, or Adobe Commerce Cloud (PaaS) with hosting included |
Support in Practice: What the Editions Actually Mean
A common buyer question: "What happens when something breaks at 2am?"
-
Magento Open Source: There is no Magento direct support. Support comes from your agency SLA, community forums (Magento Stack Exchange, Slack communities), and your hosting provider. Choosing your agency is effectively a support decision — their responsiveness and platform knowledge define your support tier.
-
Adobe Commerce: Access to Adobe support tickets and, at higher tiers, dedicated Technical Account Managers with documented SLAs. Even so, Commerce merchants typically supplement this with an agency for version upgrades, extension work, and immediate debugging — Adobe support covers the platform, not your custom code.
-
Practical implication: For most mid-market Open Source deployments, your agency or in-house team is your support. Vet them accordingly: ask about their out-of-hours process, SLA terms, and how they handle security patches.
How Much Does Magento 2 Cost?
Magento cost is best understood as total cost of ownership (TCO): build/migration, infrastructure, ongoing maintenance, extensions, and a license if you choose Adobe Commerce. Costs range from a few hundred dollars per year for a lean self-managed setup to over a million for a full enterprise implementation.
The Five Cost Buckets
| Bucket | What's inside |
|---|---|
| Build / migration | Store setup, data migration, SEO redirects, QA, launch support. Includes frontend theme implementation (Luma, Hyvä, or headless) and custom business logic. |
| Integrations | ERP, CRM, PIM, WMS, payment gateways, shipping providers, marketplaces, marketing automation. Middleware complexity adds significant cost. |
| Hosting & infrastructure | Server resources, CDN, caching stack (Redis, Varnish), monitoring, backups, staging/UAT. Typically $1,200–$12,000/year depending on scale. |
| Ongoing maintenance | Security patches, Magento version upgrades, extension updates, bug fixes, performance work. Often the most under-budgeted line item. |
| Extensions | One-time or annual licenses. Average $50–$1,000+ per extension. Budget for both purchase and upgrade compatibility work. |
| License (Adobe Commerce only) | Annual, quote-based, GMV-linked. Not applicable for Open Source. See benchmark table below. |
Adobe Commerce License Benchmarks
Adobe does not publish a public price list. These are commonly cited planning benchmarks from industry sources. Final pricing is quote-based and subject to negotiation. Contact Adobe for a current quote.
| Annual GMV | Adobe Commerce (self-hosted) | Adobe Commerce Cloud (PaaS) |
|---|---|---|
| Under $1M | $22,000/year | $40,000/year |
| $1M – $5M | $32,000/year | $55,000/year |
| $5M – $10M | $49,000/year | $80,000/year |
| $10M – $25M | $75,000/year | $120,000/year |
| $25M – $50M | $125,000/year | $190,000/year |
| $50M+ | Custom pricing | Custom pricing |
Source: Eltrino Magento 2 cost guide, based on commonly cited industry benchmarks.
Frontend Stack: Hyvä & Headless Licensing
Your frontend choice affects both build cost and long-term maintenance. Key licensing costs as of early 2026:
| Product | Pricing | Notes |
|---|---|---|
| Hyvä Theme | €0 (free since Nov 2025) | Modern lightweight frontend — strong Core Web Vitals baseline |
| Hyvä UI Components | €250 one-off | Optional component library |
| Hyvä Checkout | €1,000 + €250/year | Commercial checkout; one-off plus optional annual updates |
| Hyvä Commerce (bundle) | €3,000/year | Includes Theme, UI, and Checkout |
| Hyvä Enterprise (Adobe Commerce) | €2,500/year | Required for Adobe Commerce compatibility |
| Alokai/Vue Storefront OSS | €0 license | Headless option; higher build and ownership cost |
| Alokai Enterprise | Quote-based | Traffic-driven pricing |
Build Cost Ranges: 6 Real Scenarios
These scenarios are based on 14 years of Magento project experience (source: Eltrino cost guide). Ranges are wide because scope varies significantly — treat these as order-of-magnitude guides, not quotes.
Scenario 1 — Lean Launch (Self-Managed)
Stack: Magento Open Source + DigitalOcean + Hyvä Theme. You handle setup, configuration, and support yourself.
| Cost Item | Year 1 | Year 2+ |
|---|---|---|
| Magento Open Source license | $0 | $0 |
| Hosting (DigitalOcean Basic 4GB) | $288/yr ($24/mo) | $288/yr |
| Hyvä Theme | €0 | €0 |
| Extensions (optional) | $0–$500 | $0–$500 |
| Setup & support (self-managed) | $0 | $0–$1,500 |
| Estimated total | ~$300–$800 + €0–250 | ~$300–$2,300 |
Scenario 2 — Small Business Store (Professional Build)
Stack: Magento Open Source + Hypernode + Hyvä Theme. Professionally built, minimal ongoing maintenance. Typical for established small businesses wanting reliable performance.
| Cost Item | Year 1 | Year 2+ |
|---|---|---|
| Magento Open Source license | $0 | $0 |
| Hosting (Hypernode entry plan) | €1,548/yr | €1,548/yr |
| Extensions | $500–$2,000 | $500–$2,000 |
| Professional build (theme + core setup) | $20,000–$45,000 | — |
| Support & maintenance (minimal) | $3,000–$8,000 | $4,000–$10,000 |
| Estimated total | $24k–$55k + hosting | $5k–$12k + hosting |
Scenario 3 — Growth Store (Custom UI + Integrations)
Stack: Magento Open Source + Hypernode + Hyvä Commerce + ERP/CRM/PIM integrations. Mid-market scale with real system connections.
| Cost Item | Year 1 | Year 2+ |
|---|---|---|
| Magento Open Source license | $0 | $0 |
| Hosting (Hypernode mid plan) | €2,844–4,656/yr | €2,844–4,656/yr |
| Hyvä Commerce (Theme + UI + Checkout) | €3,000/yr | €3,000/yr |
| Extensions | $2,000–$8,000 | $2,000–$8,000 |
| Build + custom UX + performance | $60,000–$140,000 | — |
| Integrations (ERP/CRM/PIM/3PL) | $15,000–$80,000 | $5,000–$25,000 |
| Support & maintenance | $18,000–$60,000 | $24,000–$90,000 |
| Estimated total | $95k–$288k + hosting | $31k–$123k + hosting |
Scenario 4 — Growth Store (Headless Architecture)
Stack: Magento Open Source + Alokai (Vue Storefront OSS) + Vercel/Netlify. Maximum frontend flexibility at higher build and ownership cost.
| Cost Item | Year 1 | Year 2+ |
|---|---|---|
| Magento + Alokai OSS licenses | $0 | $0 |
| Frontend hosting (Vercel/Netlify) | $0–$2,400 | $0–$2,400 |
| Magento hosting | $1,200–$6,000 | $1,200–$6,000 |
| Headless build (frontend + middleware) | $90,000–$220,000 | — |
| Integrations | $15,000–$80,000 | $5,000–$25,000 |
| Support & maintenance | $24,000–$90,000 | $30,000–$120,000 |
| Estimated total | $130k–$398k | $36k–$153k |
Scenario 5 — Enterprise B2B
Stack: Adobe Commerce + Hypernode + Hyvä Enterprise + Hyvä Commerce. Complex B2B workflows, multi-warehouse, advanced integrations.
| Cost Item | Year 1 | Year 2+ |
|---|---|---|
| Adobe Commerce license | $75k–$190k/yr | $75k–$190k/yr |
| Hosting (Hypernode larger plan) | €4,656–€10,000+/yr | €4,656–€10,000+/yr |
| Hyvä Commerce + Hyvä Enterprise | €5,500/yr | €5,500/yr |
| Implementation (B2B + custom flows) | $180k–$450k | — |
| Integrations & data workflows | $40k–$200k | $15k–$80k |
| Support & maintenance | $60k–$200k | $90k–$300k |
| Estimated total | $355k–$1.24M | $180k–$570k |
Scenario 6 — Adobe Commerce Cloud (PaaS) Enterprise
Stack: Adobe Commerce on Cloud + Enterprise implementation + integrations. Fully managed, cloud-hosted, premium support.
| Cost Item | Year 1 | Year 2+ |
|---|---|---|
| Adobe Commerce on Cloud license (hosting included) | $40k–$190k/yr | $40k–$190k/yr |
| Implementation | $200k–$600k | — |
| Integrations & data | $40k–$250k | $15k–$120k |
| Support & maintenance | $60k–$220k | $90k–$350k |
| Estimated total | $340k–$1.26M | $145k–$660k |
What Drives Cost Up
- Complex business logic (custom checkout, pricing rules, promotions, quoting)
- Number and API maturity of integrations — and whether you need middleware
- Catalog complexity (large catalogs, complex attributes, configurators, multi-language)
- B2B requirements (company accounts, contract pricing, approvals, shared catalogs)
- Multiple storefronts and countries (currencies, tax rules, shipping logic, SEO setup)
- Extension landscape — more extensions means more testing and upgrade friction
- Performance targets (Core Web Vitals, peak traffic, global rollout)
How to Reduce Cost Without Cutting Corners
- Start with a clear MVP scope — launch revenue-critical features only, then iterate from real data
- Use native Magento capabilities or proven extensions before building custom logic
- Standardise your extension stack around one trusted provider where possible to reduce conflicts
- Keep integrations clean: define data ownership clearly (ERP vs. Magento) and document flows
- Budget for maintenance from day one — regular updates prevent expensive emergency fixes
- Right-size infrastructure at launch but design for easy scaling at peak traffic
- Work with an experienced team — higher hourly rates often mean lower total cost due to fewer mistakes and faster delivery
→ For a detailed breakdown and project-specific estimate, see our Magento cost calculator.
Magento 2 Performance: Is It Fast?
A well-built Magento 2 store regularly achieves 90+ Core Web Vitals scores. Most slowdowns trace back to a handful of predictable causes — and every one of them is fixable.
Why Magento Stores Can Feel Slow
-
Heavy frontend stack: Luma-based builds ship with more JS/CSS than needed. Custom themes can add even more. This is the single biggest Core Web Vitals lever for most stores.
-
Too many or poorly built extensions: Every module can add observers, plugins, DB queries, layout updates, JS, and tracking scripts. Extension sprawl is a major hidden performance cost.
-
Hosting not configured for Magento: Magento needs properly tuned PHP-FPM, OPcache, Elasticsearch/OpenSearch, and a caching strategy. Generic hosting rarely delivers this.
-
Caching not configured end-to-end: Missing or misconfigured full-page cache, Varnish, Redis, CDN, or cache warmup makes a fast store feel slow.
-
Third-party scripts: Tag managers, chat widgets, A/B testing tools, and personalisation scripts often hurt Core Web Vitals more than Magento itself.
-
Images and media: Oversized images, no responsive image strategy, missing WebP/AVIF formats, and no CDN optimisation.
Hyvä vs. Luma: The Frontend Decision
What is Hyvä?
Hyvä is a modern storefront ecosystem for Magento that replaces the default Luma frontend with a lighter, faster stack based on Alpine.js and Tailwind CSS — instead of Luma's heavier RequireJS/KnockoutJS layer. Hyvä Theme is now free (since November 2025).
Migrating from Luma to Hyvä frequently yields significant Core Web Vitals improvements: less JavaScript, simpler template structure, fewer extension conflicts, and faster iteration. If you are planning a frontend rebuild, this is the first option to evaluate. See our Hyvä vs. Luma performance test for detailed benchmarks.
Quick Wins Checklist
- Enable full-page cache and configure Varnish correctly
- Move sessions/cache to Redis and tune PHP-FPM + OPcache
- Audit and remove/reduce third-party scripts, especially those delaying INP/LCP
- Optimise images: responsive sizes, WebP/AVIF, lazy-load, preload the LCP image
- Review extensions: remove unused, update risky ones, profile slow observers/plugins
- Verify indexers and cron run reliably and do not reindex unnecessarily
- Use a CDN for static assets and media; verify cache headers and hit rate
- Profile with real-user monitoring (RUM) and synthetic tests to validate improvements
→ For a prioritised performance plan, start with a structured Magento Performance Audit (free option available).
Magento 2 Implementation: What to Expect
A simple Magento store can launch in 2–3 months. Builds with custom features, integrations, or custom design typically take 4–9 months or longer. The discovery phase, clear requirements, and timely feedback are the biggest variables in keeping a project on schedule.
Typical Build Phases
| Phase | Typical Duration | What happens |
|---|---|---|
| Discovery & scoping | 2–4 weeks | Requirements, integration inventory, SEO baseline, architecture decisions, phased roadmap |
| Design / UX | 2–8 weeks | UX/UI design, theme selection or custom design, design system decisions |
| Development | 8–24 weeks | Theme implementation, backend configuration, custom modules, integration builds |
| QA & testing | 2–4 weeks | Functional testing, performance testing, staging validation, UAT |
| Launch & cutover | 1–2 weeks | DNS migration, SEO redirect validation, cache warmup, post-launch monitoring |
Common Pitfalls — and How to Avoid Them
Most Magento project failures trace back to a predictable set of issues. These are not rare edge cases — they are regular patterns that experienced teams have systematic ways to avoid.
-
Under-scoped data migration: Product attributes, customer history, order records, and SEO URLs all need careful mapping before migration. Audit your current data model early and include migration in your project scope explicitly.
-
Extension conflicts discovered late: Test extensions on a staging environment that mirrors production from day one. Do not approve new extensions without a compatibility check against your existing stack.
-
Skipping load and performance testing: UAT on a staging server with one user tells you nothing about how the store behaves at Black Friday peak traffic. Run synthetic and load tests before launch.
-
Weak hosting chosen to save money at launch: Magento is infrastructure-sensitive. Hosting that feels adequate during development often fails under real traffic. Choose Magento-configured hosting — managed providers like Hypernode are purpose-built for this.
-
Customisations made to core files: Any code change outside a custom module will be overwritten by the next Magento update. Always extend via modules. This is non-negotiable and has a long-term maintenance impact.
-
Hard cutover on a fixed deadline: A phased rollout or soft launch surfaces problems in a controlled environment. Going live on a hard deadline with unresolved issues is the riskiest launch model.
-
Choosing the wrong agency: Look for official Adobe/Magento certifications, a proven portfolio of similar projects, and references from clients in your business model. Ask specifically how they handle upgrades and long-term support — not just the launch.
Magento 2 Strengths and Trade-offs
| ✓ Strengths | ✗ Trade-offs |
|---|---|
| Flexibility without platform limits — Magento can be shaped around your business logic (custom checkout, pricing rules, unique catalog structures). If your process is unique, you do not need to reshape it to fit the platform. | Longer time to launch than SaaS — Magento projects require discovery, development, QA, and infrastructure setup. If you need a storefront live in 4 weeks, SaaS will serve you better. |
| Catalog depth — configurable products, attribute sets, layered navigation, and complex product types work well for large catalogs with thousands of SKUs across multiple dimensions. | Higher TCO if not maintained — skipping upgrades, accumulating extensions, or running on under-spec hosting leads to performance issues and expensive catch-up work. Ongoing investment is structural. |
| Serious B2B capabilities — company accounts, role-based buyers, custom pricing, procurement workflows, and quoting are native to Magento (especially with Adobe Commerce). Few platforms match this out of the box. | Requires experienced development and operations — Magento needs solid engineering practices: code quality, staging environments, testing, monitoring. Your agency or team quality directly determines your long-term cost and stability. |
| Multi-store from one backend — multiple brands, countries, languages, currencies, and B2B/B2C storefronts managed centrally, with shared catalog logic where it makes sense. | Extension sprawl risk — adding extensions without governance leads to conflicts, upgrade friction, and performance degradation. A disciplined extension strategy is required, not optional. |
| Large ecosystem — thousands of extensions and a mature developer community mean proven patterns for almost every feature need, and a wide pool of agencies to choose from. | Infrastructure responsibility — you own or commission your server configuration, monitoring, backups, and scaling. This is a feature for some and a burden for others. |
Next Steps
If Magento 2 looks like the right fit — or if you're still deciding — here are the practical routes forward.
| You want to… | Start here |
|---|---|
| Understand your build cost | Use our Magento cost calculator, or contact us for a scoped estimate after a discovery call |
| Evaluate Magento vs. Shopify | See our platform comparison guide — we'll help identify which fits your business model and growth trajectory |
| Audit an existing Magento store | Start with a Magento Performance Audit — a structured review of your current setup with prioritised recommendations (free option available) |
| Plan a migration | Begin with a discovery engagement: data audit, integration inventory, SEO baseline, timeline estimate |
| Get started or discuss your needs | Reach out via our contact form or email — we begin with an intro call to understand your goals and propose practical next steps tailored to your situation |