Every Magento Open Source merchant eventually asks the question: is Adobe Commerce worth the licence fee? The honest answer is that it depends almost entirely on your revenue, your B2B ambitions and your team. We have advised merchants in both directions - some should upgrade tomorrow, others would be paying for shelf-ware.
What the Licence Actually Buys
Adobe Commerce is not a different platform; it is Open Source plus a commercial layer. The features that genuinely change businesses:
- B2B suite: company accounts, shared catalogs, negotiable quotes, requisition lists and purchase approval rules. If you sell to businesses, this alone can justify the licence.
- Content staging and preview: schedule campaigns, price changes and CMS updates with full preview before they go live.
- Live Search and Product Recommendations: Adobe Sensei-powered search and personalisation that replace third-party extensions.
- Visual Merchandiser, customer segments, reward points, gift cards, RMA - the retention and merchandising toolkit.
- Cloud infrastructure option: Adobe Commerce on cloud includes Fastly, New Relic and managed deployment tooling.
The Numbers That Matter
Adobe prices the licence on gross merchandise value. As a rough rule, merchants under about one million pounds in annual online revenue rarely extract enough value from the commercial features to cover the fee, unless B2B is central to the model. Above that threshold, the maths often flips: negotiated quotes alone can recover the licence cost through larger basket sizes.
Do not forget the hidden savings. Open Source merchants frequently pay for extensions that replicate B2B companies, content staging and advanced search. Add up those extension licences, the integration maintenance, and the agency time spent keeping them compatible, and the gap narrows considerably.
What the Migration Involves
Moving from Open Source to Adobe Commerce on your own hosting is one of the easier Magento projects: the codebase is shared, so the work is installing the commerce modules, re-running setup upgrade, and testing custom code against the new features. Expect days, not months. Moving to Adobe Commerce Cloud at the same time is a bigger commitment - your deployment pipeline, environments and integrations all change, so plan it as a separate workstream.
When We Advise Against It
- Your catalogue and checkout are simple, B2C only, and extensions already cover your needs.
- Your team cannot use content staging or personalisation operationally - unused features are pure cost.
- You are considering cloud purely for support; Adobe support is not a managed service and expectations should be set accordingly.
Making the Decision
Score your requirements against the feature list above, price the extensions you would otherwise buy, and model the licence against realistic GMV. If B2B, scheduled merchandising or Adobe’s search stack are on the roadmap within eighteen months, upgrading early is cheaper than retrofitting. Otherwise, a well-tuned Open Source build remains a formidable platform - we run plenty of both.