A pragmatic Magento 2 and Adobe Commerce practice for brands past $5M GMV running enterprise catalogs, multi-store, B2B, and complex tax. We know the platform's strengths, and we will name the day it is time to move.
Magento 2 (Adobe Commerce and Open Source) still powers more of the internet's enterprise catalogs than any other self-hosted platform. Magento can always do the job. The real question is whether the support calendar, upgrade cost, and hiring market add up over three years.
We run Magento for brands where the platform's strengths are genuinely needed. We run the migration to Shopify Plus for brands where the math has flipped. The audit tells which side you are on.
Magento Open Source and Adobe Commerce share the core engine. Everything built on Open Source runs on Commerce. The difference is what Commerce layers on top: page builder, targeted rules, Elasticsearch, B2B module, and Adobe support.
Commerce costs $22K-$125K per year depending on GMV. Most mid-market brands replicate those features via community extensions and keep license spend at zero. Enterprise brands ($50M+ GMV) often choose Commerce for the official support and page builder.
| dimension | Open Source | Adobe Commerce |
|---|---|---|
| license fee | $0 | $22K-$125K annual |
| page builder | via extension (free or $300 one-time) | included, tightly integrated |
| B2B module | via extension ($600-$2K) | included, official |
| targeted rules | build yourself or extension | included |
| elastic search | self-hosted Elasticsearch or OpenSearch | Adobe Live Search included |
| support | community + your agency | Adobe SLA |
| cloud option | self-host anywhere | Adobe Commerce Cloud (managed) |
Magento 2's nine indexers are the heart of catalog performance. When misconfigured, they reindex on save and slow admin to a crawl. When tuned to "Update on Schedule" with cron-driven batch processing, they keep the storefront cache warm while admin edits fly.
The animation below shows a 100K SKU catalog reindex in motion.
Product Price owns your Monday. Every Magento admin has watched it run for 45 minutes after a catalog rule change.
Understanding what each indexer does, when to set it to "Update on Schedule" versus "Update on Save", and how to batch-process during low-traffic windows is half of Magento performance work.
Fast. Rebuilds on theme or config change. Safe at "Update on Save".
Admin customer search index. Rebuild batches on customer imports.
Which products belong to which categories. "Update on Schedule" for large catalogs.
Reverse lookup. Required for storefront tree rendering. Schedule-mode.
The slowest. Tier pricing, catalog rules, customer group prices, tax-inclusive. Always schedule-mode, nightly rebuild ideal.
Filterable attribute index for layered navigation. Schedule-mode.
Catalog price rules per product. Rebuild on rule changes.
Which rules apply to a product. Schedule-mode.
Inventory index. Multi-source inventory stores have the heaviest reindex cost.
The biggest Magento 2 performance decision is the frontend you choose.
Hyva Themes (Alpine JS + Tailwind) typically drops LCP from 4-6 seconds to 1.5-2.2 seconds without a PWA rewrite. PWA Studio gives you React-based interactivity at higher engineering cost. Luma is the default theme and hits a performance ceiling.
| Luma (default) | Hyva Themes | PWA Studio | |
|---|---|---|---|
| stack | jQuery + Knockout + LESS | Alpine JS + Tailwind CSS | React + GraphQL |
| LCP mobile typical | 4-6s | 1.5-2.2s | 1.2-2.0s |
| rebuild cost | low (stays as-is) | 10-16 weeks | 14-24 weeks |
| extension ecosystem | every Magento extension works | ~80% extensions compatible; others need Hyva port | narrowest, React-rewrites needed |
| best for | stores keeping Magento as legacy | 80% of modern Magento rebuilds | brands with React app-shared codebase |
Magento's three-level hierarchy (Website, Store, Store View) handles multi-brand and multi-region cleanly on a single install.
You choose: shared or isolated catalog, shared or isolated customer base, per-store pricing, per-store payment, per-store tax. The architecture decision in week one sets the ceiling for everything downstream.
Defines customer scope (shared customer base across websites or isolated), payment methods, base currency. Usually one website per legal entity.
Root category determines which products a store sells. Multiple stores per website share customer base but can offer different catalogs. Useful for B2B vs DTC on one instance.
Locale, translations, per-view theme. Multi-language sites use store views per language; multi-country sites often use separate stores for catalog differences.
Magento's B2B module (bundled with Adobe Commerce, available via extension on Open Source) covers the full enterprise B2B surface: company accounts with sub-users, internal approval workflows, quote-to-order, NET payment terms, per-customer catalog visibility, and tiered pricing.
This is one of Magento's strongest value propositions. Shopify Plus B2B is catching up, but Magento still wins on the deeper edge cases like tax exemption flows and contract pricing.
Multi-region tax is one of the genuinely hard problems SaaS platforms struggle to express. Magento integrates directly with TaxJar, Avalara, and Vertex through official connectors.
Magento also supports native tax rules per store view, per customer group, and per product class. That combination handles EU VAT (including OSS and IOSS), UK VAT post-Brexit, US sales tax across all 50 states, Canadian GST/HST/PST, and Australian GST with the same architecture.
Best pick for US-first brands with Canada. Economic nexus monitoring, rate API, reporting. $19-$300/mo depending on volume.
Most comprehensive. 12,000+ tax jurisdictions. Required for brands shipping to 20+ countries. Higher cost, includes filing services.
Wholesale, tax-exempt certificates, use tax, manufacturing exemptions. Right pick for industrial distributors and complex B2B.
Most Magento performance complaints stem from Luma-era baselines. On a properly-tuned Hyva build with Elasticsearch, Redis full-page-cache, and Varnish, here are our performance targets.
These benchmarks are measured on mid-tier Android over throttled 4G.
| template | LCP | INP | CLS | note |
|---|---|---|---|---|
| homepage | < 2.0s | < 150ms | < 0.05 | hero + featured products |
| category / layered nav | < 2.4s | < 180ms | < 0.08 | 100+ SKUs filterable |
| product (configurable) | < 2.2s | < 180ms | < 0.08 | variation swatches |
| cart | < 2.2s | < 200ms | < 0.10 | tax calc round trips |
| checkout | < 2.5s | < 200ms | < 0.10 | payment iframe + tax service |
Unlike SaaS platforms that auto-qualify for SAQ-A, self-hosted Magento defaults to SAQ-A-EP (the merchant controls the checkout page even if tokenized).
We architect checkouts to stay at SAQ-A by using hosted payment fields, redirect flows, or Adyen-style drop-in components. Card data never reaches your server or your checkout's DOM.
Our readiness audit calculates total cost of ownership: hosting, license (if Adobe Commerce), engineering retainer, extension licenses, and upgrade overhead.
We compare that honestly against Shopify Plus plus a rebuild amortized over 3 years. If migration wins, we run it ourselves through our Shopify migration practice. If staying wins, we run the Hyva rebuild. We have no ideological commitment to either platform.
35K SKU catalog, 140 B2B customers with per-company catalogs and NET-30 terms. Luma LCP at 5.2s killing search rankings. Hyva rebuild + B2B module upgrade + TaxJar integration. 14-week engagement.
12K SKU home goods brand on Adobe Commerce Cloud. License + hosting + retainer at $165K/year. Catalog complexity was manageable in Shopify metafields. Migration to Plus saved $90K/year. 16-week migration.
Magento work comes in four shapes. The readiness audit determines which one fits. Every shape starts from the same honest cost-of-ownership math.
3 weeks. Indexer health, cache, extensions, TCO vs Shopify. Refundable. Contact for quote.
10-16 weeks. CWV rebuild on Alpine + Tailwind. Contact for quote.
14-24 weeks. Multi-store, B2B, tax, ERP. Contact for quote.
12-20 weeks. Magento → Shopify Plus with 99% URL kept. Contact for quote.
A Magento decision sets your platform cost for the next three years. The audit behind it has to be honest.
These are the proofs that come before the brief.
"Magento Open Source, Adobe Commerce, Hyva rebuilds, and migrations off Magento across nine years and two thousand storefronts. Because we run both sides, the readiness audit recommends what the three-year math says, not the engagement we would rather sell."
For the right brand, yes. Magento 2 Open Source wins when you run a complex catalog (10K+ SKUs with tiered pricing, multi-warehouse inventory, or complex attribute sets), when B2B requires company accounts with internal approval and NET terms, or when international tax needs per-country logic that SaaS platforms do not expose.
Adobe Commerce wins when you need Enterprise features (targeted rules, page builder, advanced search) and can absorb the license cost. For $1M to $5M brands with simpler catalogs, Shopify or Shopify Plus is usually the honest answer. We say so.
Sometimes. The math flips when your Magento maintenance, hosting, and developer retainer together exceed Shopify Plus's annual fee plus a build-cost amortized over 3 years.
That usually happens for $5M to $30M brands whose B2B needs fit Shopify's features and whose catalog complexity is not genuinely Magento-specific. Brands above $50M with real multi-warehouse, multi-region tax, and complex B2B often stay. We run both platforms. The decision is unsentimental, numbers-based, and we will tell you which way the audit goes.
Magento work costs more than Shopify or WooCommerce at every project shape. US and UK senior engineers run $140 to $200 per hour at boutique agencies. Indian mid-market seniors run $90 to $140 per hour.
A Hyva or PWA Studio frontend rebuild runs 10 to 16 weeks. A custom Magento build with B2B, multi-store, and tax runs 14 to 24 weeks. Enterprise Adobe Commerce with ERP runs 20 to 40 weeks. A readiness audit is 3 weeks and refundable. Scoped quote in 48 hours.
Hyva Themes (Alpine JS + Tailwind CSS) is our default for brands that want dramatic CWV improvement without a PWA rewrite. Typical LCP drops from 4-6 seconds on Luma to 1.5-2.2 seconds on Hyva.
PWA Studio is the right pick for brands committed to React, willing to pay for offline support and app-like interactivity. Luma (the default) is acceptable for small catalogs but hits a performance ceiling. We benchmark all three before recommending.
Magento's multi-store architecture is one of the platform's genuine strengths. One instance runs multiple storefronts across different domains, currencies, languages, and catalogs with shared or isolated customer bases.
We design the hierarchy at week one: website (billing boundary, customer scope), store (catalog scope), and store view (language and design). You choose whether catalog is shared across brands or isolated. We have shipped both shapes.
Named integrations with NetSuite, SAP, Microsoft Dynamics, QuickBooks Enterprise, and Acumatica. Three patterns cover most: bi-directional via middleware (Boomi, MuleSoft, Celigo) for mid-market brands, direct API for simpler ERP like QuickBooks or Xero, and custom message-queue for enterprise Adobe Commerce with real-time inventory.
We isolate the integration in a dedicated Magento module or external middleware, never inline in the theme, so upgrades do not break data flow. Failure modes are monitored and alertable from day one.
Magento out-of-the-box can end up at SAQ-A-EP (the stricter self-assessment) because the checkout page is hosted on your server, even if card data is tokenized.
To stay at SAQ-A, we configure payment integrations (Stripe, Braintree, Adyen) using hosted payment fields or redirect flows. Card data never touches your Magento server.
We audit for script origins, Content Security Policy, card logging, TLS 1.2+, and HSTS. Enterprise Adobe Commerce can stay at SAQ-A-EP with full QSA audit documentation.
You own it all.
Magento installation is on your hosting (MageMojo, Nexcess, AWS, or your own infrastructure). Custom modules live in a private GitHub repository under your organization from day one. You hold the admin access and ERP credentials.
We're added as named engineers and removed anytime you choose.
On exit we transfer the repository, document every custom module, record a Loom walkthrough of architectural choices, and provide 30 days of support.
No lock-in through code or configuration.
Three weeks. Indexer health, cache, extensions, and honest TCO vs Shopify Plus. Refundable against any engagement that follows. Scoped quote in 48 hours.
Published reviews from our Fiverr profile, reproduced word for word. 397 public reviews across 4 gigs, from clients in 36 countries. Read them all on Fiverr.
I am extremely satisfied with the website. The design looks very professional, premium, and exactly how I wanted it. Communication was great throughout the entire process, and every detail I requested was implemented carefully. I highly recommend working with him if you want a high-quality Shopify store or e-commerce website. Thank you for the excellent work!
Exceptionally responsive team. Any iterations to website done almost instantaneously.. The final website design and aesthetic far exceeded my expectations. Highly recommend.
Communication was excellent throughout the process, and they kept me updated throught out the project and that is good thing, because i had faced the worst with previous freelancer but they are perfect team and they know how and what to do Highly recommend
They understood exactly what I wanted and kept my existing Shopify theme while giving the store a much more modern and premium look, I'm very happy with the final result and would definitely recommend them to anyone looking for a professional Shopify developer. Thanks again!
My store finally looks like a real premium brand. The redesign is clean, elegant, mobile-friendly, and far beyond what I expected for the budget. I'll definitely be back for future Shopify work.
Really impressed with how they improved the customer journey without disrupting our existing store setup. The store finally feels like a premium supplement brand instead of a basic Shopify template
Reviews are reproduced as published on Fiverr, captured 2026-08-03. Fiverr shows the buyer's username and country publicly; no other client detail is used here.
115 people across five studios in New York, Delhi, London, Sydney and Lucknow, shipping ecommerce, web, software and mobile work for founder-led brands. Senior engineers only, no account-manager relay, and the same team from kickoff to launch.
Senior iOS Engineer · Delhi · 2 posts on the site
Published · Last updated .
Pinch, scroll or double-tap to zoom · drag to pan
Share your name and email so we can follow up.
Please enter your name and a valid email.
