By Diosh — Founder, AHAeCommerce | eCommerce decision intelligence for $50K–$5M GMV operators
The Adobe Commerce pitch always leads with the license number, and the license number is the small one. Somewhere between $22,000 and $125,000 a year, depending on your GMV tier — a figure that sounds large until you discover it is roughly a fifth of what the platform actually costs to operate. This is a cost piece for operators being told that Adobe Commerce (the platform formerly and still commonly called Magento) is the natural enterprise upgrade from Shopify Plus. The non-obvious reality is that Adobe Commerce's defining feature — total flexibility — is also its defining cost: every capability is a development project, not an app install, and a platform that "can do anything" is one where you must build, and then perpetually maintain, everything. Read this before you calculate the license. Read it especially before you sign.
The License Is the Decoy Number
Adobe does not publish Adobe Commerce pricing the way Shopify publishes Plus pricing, and that opacity is itself a signal. Pricing is quote-based, tiered on Gross Merchandise Value and Average Order Value, and negotiated per contract. Based on publicly circulated analyst estimates and reseller disclosures, the Adobe Commerce (cloud) license lands roughly between $22,000 and $125,000 per year — the low end for a brand doing a few million in GMV, the high end for one approaching $50M. Adobe's own product positioning describes Commerce as an enterprise-grade, composable platform sold to mid-market and large merchants; what it does not foreground is the operating model that license assumes. See Adobe's commerce product pages for the marketed feature set, and read it knowing the feature set is the capacity to build, not the built thing.
Here is the trap in the framing. When a $25M GMV operator hears "$80,000 a year for the platform," they mentally file it next to their Shopify Plus invoice — which, at that scale, runs in a comparable range once you account for variable platform fees. The two numbers look like peers. They are not peers. The Shopify Plus number is close to all-in: the platform is hosted, patched, secured, and upgraded by Shopify, and most extension needs are met by installing an app from a marketplace and paying a monthly fee. The Adobe Commerce number is the entry ticket. It buys you the right to operate a system that does almost nothing useful until a development team builds it out and keeps building.
The decision error is comparing license to license. The correct comparison is fully-loaded total cost of ownership against fully-loaded total cost of ownership, and the moment you run that comparison honestly, the gap is not 10% — it is 5x to 10x. An operator who signs based on the license number has not made a pricing decision. They have made a staffing decision they did not know they were making.
Every Feature Is a Development Project
The single sentence that should reframe your entire evaluation: on Adobe Commerce, the answer to "can the platform do X?" is almost always yes, and the answer to "how?" is almost always "a developer builds it." This is the inverse of the Shopify model, where the answer to "how?" is usually "install an app." That difference — install versus build — is the entire cost story.
Consider a concrete scenario. A $30M GMV home-goods brand wants tiered B2B pricing: wholesale accounts see net pricing, retail accounts see MSRP, and a third tier of contract buyers sees negotiated rates that change quarterly. On Shopify Plus, this is a B2B feature plus possibly one app, configured in days. On Adobe Commerce, this is a genuine strength of the platform — native B2B price lists, shared catalogs, company accounts — but configuring it correctly, integrating it with the ERP that holds the contract rates, and testing it across account types is a multi-week development engagement billed at developer rates. The platform can do it beautifully. Doing it costs money every time.
Now multiply that across every requirement you have. A custom checkout step. A loyalty program. A subscription flow. A returns portal. A connection to your 3PL. Each is a project. Each project has a build cost, and — this is the part operators systematically forget — each project becomes a piece of code your team now owns and must maintain through every future platform upgrade. The flexibility compounds in both directions: it lets you build exactly what you want, and it obligates you to maintain exactly what you built.
This is why Adobe Commerce TCO cannot be estimated from a feature list. The honest input is your customization surface area — how many things you need the platform to do that the platform does not do out of the box. The larger that surface, the more the build-everything model works against you, and the more decisive the question in our eCommerce platform decision framework becomes: are your requirements genuinely non-standard enough to justify a build-everything platform, or are you about to pay enterprise development rates to recreate features Shopify ships for free?
The Real Line Item Is People
Strip away the license and the hosting, and the dominant cost of Adobe Commerce is human. Magento is a notoriously deep, idiosyncratic codebase, and developers who can work in it safely are a specialized and well-compensated labor category. Salary aggregators put experienced Magento and Adobe Commerce developers in the range of roughly $120,000 to $180,000 in fully-loaded annual cost in major U.S. markets — and that range is consistent with broader software developer compensation data from the U.S. Bureau of Labor Statistics, which reports a median wage for software developers well above the six-figure mark before benefits and overhead. Glassdoor's salary data for Magento-specialized roles reflects the same premium: the scarcity of the skill set keeps the price high.
You will pay for that skill set in one of two structures. The first is in-house: you hire one or more dedicated Magento developers. At a fully-loaded cost of $120K–$180K each, a single senior developer is rarely enough to run a $30M operation safely — you generally need at least one and a half to two FTEs of capacity to handle build work, emergency fixes, and upgrade labor without single-person risk. That is $180K–$320K a year in payroll before the developer has shipped a single new feature, just to keep the lights on and the code current.
The second structure is an agency retainer. Specialized Adobe Commerce agencies bill ongoing retainers that, based on agency benchmarks across the mid-market, commonly run between $8,000 and $25,000 per month — $96,000 to $300,000 a year — for a team that handles maintenance, builds, upgrades, and on-call support. The retainer trades the single-person risk of in-house for a dependency on the agency's roster and rate card, and it almost never includes large build projects, which are scoped and billed separately on top.
Either way, the math is unavoidable: the people line is the platform. Add the people cost to the license and the hosting and you arrive at the number that should govern your decision — and that number, for a typical $10M–$50M GMV Adobe Commerce operation, lands in the range of $250,000 to $600,000 per year in total cost of ownership. The license is 5–15% of that. The team is the rest.
The Upgrade Tax Nobody Budgets
Here is the recurring cost most operators never put on the spreadsheet, because nobody on the sales side will name it: keeping Adobe Commerce patched, secure, and current is itself a continuous, labor-intensive project. Magento ships security patches and version upgrades on a regular cadence, and applying them to a customized installation is not a one-click operation. Every customization you built — every one of those development projects from two sections ago — must be tested against the new version, and frequently re-engineered when an upgrade breaks a dependency.
For a moderately customized store, the annual labor of staying current — applying patches, regression-testing, fixing what the patches broke, occasionally executing a major version migration — runs, by practitioner estimate, somewhere in the range of $30,000 to $80,000 a year. That is not a one-time replatforming cost. It is a permanent line item, recurring every year you operate, and it exists for one reason: an unpatched Magento store is a documented, actively-exploited security liability. You do not get to skip it. You only get to choose whether to pay it deliberately or be surprised by it.
This is the cost that converts a "we'll figure out maintenance later" decision into a breach. The operators who get burned are the ones who budgeted the build and forgot the upkeep, then let patches lapse because the developer was busy, then discovered the consequence the way everyone discovers it. If you are weighing whether a customized platform is worth it at all, the upgrade tax is the variable that most often flips the answer — and it is the throughline in the replatforming trap, where the costs that sink projects are always the recurring ones the migration plan treated as one-time.
There is also a quieter version of this tax. Adobe Commerce's flexibility means your store accretes integrations — to your ERP, your PIM, your tax engine, your shipping rate calculator, your marketing stack. Every one of those connections is custom-built and must survive every upgrade on both sides. That ongoing integration maintenance is its own compounding burden, and we treat it as a discipline in itself in the integration tax. On Adobe Commerce, the integration tax and the upgrade tax are the same money, paid twice.
Running the Honest TCO Against Shopify Plus
The only way to make this decision correctly is to build a fully-loaded TCO model and run it against the realistic Shopify Plus alternative — not the marketing comparison, the operator comparison. Put every line on the table.
For Adobe Commerce, the line items are: the license ($22K–$125K/year), cloud hosting and infrastructure (variable, often $40K+/year at scale on Adobe's cloud tiers), the dev team or agency retainer ($96K–$320K/year), third-party extension licenses (each commercial extension carries its own annual fee), and the upgrade-and-maintenance tax ($30K–$80K/year). Sum the realistic midpoints and you are in the $250K–$600K range for a $10M–$50M operation. Now build the parallel Shopify Plus model — platform fee, app subscriptions, a smaller technical team or development partner, and near-zero upgrade labor because Shopify carries that burden. We walk through that side of the model in detail in Shopify cost at scale; the point of running both is that the comparison is rarely close once the maintenance and people lines are honest.
Adobe Commerce wins this comparison in a specific and identifiable set of cases — and it genuinely does win them. If your business has deep, genuinely non-standard B2B requirements (complex company hierarchies, contract pricing, quote workflows, requisition lists), if you need ownership of your data model and logic at a level a hosted platform structurally cannot offer, or if your catalog and merchandising logic are so specific that the build-everything model is a feature rather than a tax, Adobe Commerce can be the right call. The development overhead, in those cases, buys you something Shopify cannot sell. The decision discipline here is the same one that governs whether to build custom software at all — the calculus in custom eCommerce: when to build applies directly, because operating Adobe Commerce is closer to running a custom application than to subscribing to a SaaS platform.
What Adobe Commerce does not win is the comparison where an operator chose it for prestige, picked it because it is the "serious enterprise platform," and has requirements a hosted platform would have met for a tenth of the operating cost. That is the most common Adobe Commerce mistake, and it is expensive precisely because the costs are back-loaded — the license looks reasonable, the build looks like a one-time project, and the true cost only reveals itself in year two when the team payroll and the upgrade tax are running at full rate.
What to Verify Before You Sign
Treat the Adobe Commerce decision as a procurement and staffing decision, not a software decision, and verify the numbers in this order.
First, get the real license quote in writing, tied to your GMV and AOV, and confirm what is and is not included — hosting, support tier, and which features require additional licensing. Independent platform evaluations from Gartner's Magic Quadrant for Digital Commerce and Forrester's digital commerce research are worth reading at this stage not for the rankings but for how analysts frame Adobe Commerce's positioning: an enterprise platform whose strength is extensibility, sold to organizations equipped to staff that extensibility. If you are not equipped to staff it, the analyst framing is telling you something.
Second, decide your people structure before you sign the license, not after. Will you hire in-house ($180K–$320K/year for adequate coverage) or retain an agency ($96K–$300K/year plus project fees)? Get a real retainer quote from a specialized agency, and get it to specify what the retainer covers versus what is billed separately. The most common surprise is discovering that the retainer covers maintenance but every new feature is a fresh statement of work.
Third, put the upgrade tax on the spreadsheet explicitly — $30K–$80K/year as a recurring line, not a footnote. An operator who omits this line is not modeling Adobe Commerce; they are modeling a fantasy version of it that does not require security patching.
Fourth, build the side-by-side. License plus hosting plus team plus extensions plus upgrade labor for Adobe Commerce, against the all-in Shopify Plus number for the same business. Then apply the only question that matters: do your requirements justify the build-everything overhead, or are you about to pay $300,000 a year to own what you could have rented for $60,000? If your B2B and customization needs are deep and genuine, Adobe Commerce earns its cost. If they are not, the platform that "can do anything" will charge you for the privilege of doing everything yourself — every year, in perpetuity, whether you use the flexibility or not.
