
Magento Open Source vs Adobe Commerce: The TCO Decision for SMEs
Same code, different package
Here's what actually separates the two editions in day-to-day use.| Area | Magento Open Source | Adobe Commerce |
| Licence | Free (OSL 3.0) | Annual fee, based on gross merchandise value (GMV) |
| Core shop: catalogue, checkout, MSI, GraphQL, Page Builder | Included | Included |
| B2B: company accounts, shared catalogues, quotes, requisition lists, purchase orders | Extensions or custom development | Native modules |
| Content staging and scheduled campaigns | Not included | Included |
| Customer segments, gift cards, reward points, store credit, returns (RMA) | Extensions | Included |
| Search | OpenSearch, tuned by you | OpenSearch, plus Adobe's Live Search service |
| Security patches | Same schedule, you apply them | Same schedule, you apply them (Adobe-managed on the SaaS edition) |
| Support | Your agency or in-house team | Adobe support included |
| Hosting | Your choice | Your choice, or Adobe Commerce Cloud |
What three years really cost
Start with the licence, because it's the line everyone asks about first. Agency planning estimates for the annual Adobe Commerce licence by GMV look like this:| Annual GMV | Estimated licence per year | Typical setup |
| $2–10M | ~$22,000 | Self-hosted or Cloud Starter |
| $10–25M | ~$40,000 | Self-hosted or Adobe cloud |
| $25–50M | ~$80,000 | Self-hosted or Adobe cloud |
| $50M+ | $125,000+ | Cloud Pro, hosting included |
- Build or migration. This is normally the biggest single bill, whichever edition you choose. Adobe Commerce’s native B2B features can cut the build time. On Open Source, you either buy those pieces as extensions or have them built.
- Hosting. On Open Source and self-hosted Adobe Commerce, you pick the provider. Adobe Commerce Cloud includes hosting in the price, which saves you a decision but makes the numbers harder to line up side by side.
- Extensions. Each one looks cheap on its own. Ten of them don’t. And every extension is more code that has to survive each upgrade.
- Patching and upgrades. Adobe sends out the same monthly security fixes for both editions, but somebody still has to test and install them. One agency puts that at $15,000–30,000 a year for a mid-sized shop.
- Support. Adobe Commerce comes with Adobe support. On Open Source, support means your agency retainer.
- Integrations. Connectors for ERP, PIM, payment and shipping cost about the same either way, since they plug into the same APIs.
When is the Adobe Commerce licence worth it?
Ask yourself one thing: would the licence save you work or risk you’re already paying for? If the answer is yes, it deserves a closer look. It tends to be worth it when:- B2B drives most of your revenue. Think hundreds of trade customers, each with their own price list, buyers with spending limits, and quotes that bounce back and forth for days. You can rebuild all of that on Open Source. You’ll also be maintaining every line of it yourself.
- You’d like fewer suppliers to chase. With Adobe support and Adobe’s cloud hosting, there’s one company to call when something goes wrong. If your IT team is two people, that alone can justify a good chunk of the fee.
- Marketing runs a lot of campaigns. Content staging lets the team set up an entire sale in advance, prices, banners and category changes included, and schedule it to switch on at a set time. On Open Source, someone usually ends up doing that by hand at midnight.
- Your revenue makes the fee look small. If you turn over $30M a year, a licence of around $80,000 is less than 0.3% of sales.
It’s harder to justify when:
- You sell B2C with simple pricing. Most of what Adobe Commerce adds was built for B2B sellers and big marketing departments.
- A good agency already looks after the shop. If your patches, monitoring and support are covered, Adobe support would partly pay for the same thing twice.
- Your B2B requirements are fairly basic. Customer-specific prices and a quick-order form can come straight from your ERP connector. On Open Source, for example, SAP Business One price lists and discounts can sync into Magento customer groups.
- Your annual sales are below roughly $5M. At that size the licence turns into one of your largest running costs, and you may not use many of the features it pays for.
And Adobe Commerce as a Cloud Service?
There’s a third route these days. Adobe Commerce as a Cloud Service is the SaaS version, first announced at Adobe Summit 2025. Adobe hosts and runs the application, takes care of patches and pushes out updates often. In autumn 2026 there were several releases a month. Building on it works differently. Classic PHP modules don’t go into the core anymore. Your customisations sit outside it, connected through App Builder, API Mesh and webhooks, and the storefront can run on Adobe’s Edge Delivery Services. The upside is easy to see. No more upgrade projects, and no monthly patch routine for your team. The downside is less visible. With releases this frequent, an API can change under your feet. Adobe’s November 2026 release notes, for instance, mention that REST orders for physical products now fail without a shipping address. Every integration you run, your ERP connector included, has to keep pace. Who it suits: bigger teams starting from scratch, with money set aside for API-first development and no wish to run another upgrade project ever again. Who it doesn’t: shops carrying years of custom PHP modules, and small teams who’d rather have a stable codebase they understand than one that changes every few weeks. For most SMEs in 2026, Open Source or classic Adobe Commerce is still the more sensible pick.Still weighing it up?
Ingold Solutions is an Adobe Solution Partner and SAP Silver Partner, and we build shops on both editions, so we’re happy to recommend whichever one suits you. Tell us how you sell, what your B2B customers need and how SAP Business One is set up, and we’ll run both options through the same three-year cost model. [Book a free edition review]Frequency Ask Question
Under the hood they’re the same software. Adobe Commerce adds native B2B modules, content staging, customer segments, Adobe’s search and recommendation services, Adobe support and the option of Adobe-hosted cloud. You pay for those with a yearly licence.
Adobe doesn’t list prices publicly. Agencies estimate roughly $22,000 a year for shops selling $2–10M annually, rising past $125,000 a year once sales go above $50M.
In many cases, yes. Your ERP can supply customer-specific prices, and extensions handle quick order and quotes. It gets harder when you need company accounts with buyer roles, approval steps and negotiable quotes for lots of customers. That’s where Adobe’s built-in B2B modules save serious development time.
Yes, on the same dates. With Open Source and classic Adobe Commerce, though, installing them is up to you or your agency.
Yes. They share a codebase, so moving up means swapping packages and adding a licence rather than rebuilding the shop. Plan some testing for extensions that do the same job as Adobe’s own features.




