Magento is ecommerce software that has belonged to Adobe since 2018, when Adobe completed its purchase of Magento Commerce for $1.68 billion. It comes in two main forms. Magento Open Source is free, with its code on GitHub. Adobe Commerce is the paid edition, run on a business’s own servers or on Adobe’s cloud, and there’s also Adobe Commerce as a Cloud Service, a version Adobe runs entirely itself.
The current release, 2.4.9, came out in May 2026, and Adobe gives each Adobe Commerce release three years of standard support from launch. StoreLeads counts around 100,000 live Magento stores, about 5,800 of them in the UK.
One install, many stores
A single Magento installation can run several websites, each with its own stores and store views, which is how one business runs separate brands, countries or languages from the same back office.
Adobe Commerce adds a full set of B2B features: company accounts, shared catalogs with pricing per customer, negotiable quotes, requisition lists, quick ordering, purchase order approvals and payment on account.
Which system owns Magento’s stock and prices
Connecting Magento to an ERP such as NetSuite or SAP starts with one decision per kind of record: whose version wins when the two systems disagree.
Stock is where Magento’s own arithmetic matters. It sells from a salable quantity, which is the stock held across its sources minus reservations for orders placed but not yet shipped. Each reservation clears when its order ships or is canceled. So the figure an ERP sends in should be the physical count. If the ERP sends its free stock, already net of open orders, those orders get subtracted twice until they ship, and the store shows fewer units than the warehouse holds.
Prices can sit in more than one place. Beyond each product’s own price there are tier prices, set per customer group or per website, and on Adobe Commerce, shared catalogs that price products per company. When the ERP holds the price list, the integration writes to whichever of these the store uses, and a price changed in Magento’s admin lasts until the next sync.
Customer accounts split the same way. On Adobe Commerce B2B, Magento holds company accounts and the credit each company can spend through Pay on Account. If finance sets credit limits in the ERP, that figure has to reach Magento, or a buyer can keep ordering on account past the limit finance agreed.
Hosting and updates
Who applies updates depends on the edition. A self-hosted store is looked after by its own developers. On Adobe’s cloud hosting, Adobe issues the updates and the merchant applies them, and on the Cloud Service, Adobe installs core updates itself.
Adobe ships a full release each May, with regular security releases in between that cover Magento Open Source too.
REST, GraphQL and SOAP in Magento
Magento has REST and GraphQL APIs, with SOAP still supported. Third-party apps sign in with OAuth, and an integration’s access lasts until someone revokes it. The Cloud Service uses Adobe’s own server-to-server sign-in instead.
For big catalogs, bulk endpoints take many changes of the same kind in one request, and asynchronous endpoints queue the work so the store keeps serving customers while it’s processed.
Signing in after an upgrade
Since version 2.4.4, an integration’s access token can’t be used on its own as a bearer token, because a token that never expires gives lasting access to the store if it leaks. Integrations that signed in that way are refused after the upgrade. The fix is to sign each request with all four of the integration’s OAuth credentials, or to switch the old behavior back on through an admin setting under OAuth consumer settings, which Adobe doesn’t recommend.
Webhooks and events
Adobe Commerce 2.4.4 and later can call out to other systems as things happen, through webhooks that run in step with an action and Adobe I/O Events that report it afterward. On Magento Open Source, integrations usually check for new orders and changes on a schedule.
Adobe’s direction for new work is building outside the core, with App Builder for custom apps and API Mesh for combining Magento’s APIs with other systems’ in one place. Keeping custom work out of the core also makes each upgrade simpler.
Testing
Developers can run Magento locally with Cloud Docker for Commerce. Adobe’s cloud plans include a staging environment that mirrors production, and the Cloud Service gives each update a 30-day window for testing in a sandbox first.
Stock and orders across systems
Magento’s APIs and events give an ERP plenty to work with. Stock can follow the warehouse system that owns the count, B2B prices and credit limits can come from finance, and orders can flow out to be filled from several locations, each record with its own rule for whose version wins.
With a full release every May and security releases in between, any integration around Magento also needs someone looking after it once it’s live. Who owns the integration after it ships covers what that looks like.