Magento pricing and Adobe Commerce costs in 2026

Costing Magento or Adobe Commerce? Separate licensing from hosting, development and payment costs before budgeting a store and its ongoing support.

Magento pricing starts with the edition: Magento Open Source has no software licence fee, while Adobe Commerce needs a tailored quote. Both need a budget for implementation and ongoing store operations. A free download doesn’t pay for the people who build and maintain your store.

For Adobe Commerce, name the deployment in your quote request. Adobe Commerce as a Cloud Service and Adobe Commerce on Cloud have different operating models and allowances. Comparing their headline contract prices alone leaves out work your team or agency still owns.

Magento and Adobe Commerce pricing routes

Magento Open Source is the self-managed software route. Adobe’s Magento Open Source page describes it as a free ecommerce platform. You arrange hosting and the work needed to operate it.

Adobe’s Commerce pricing page sends buyers to sales for customised pricing. It lists Adobe Commerce as a Cloud Service, a multi-tenant software-as-a-service (SaaS) product with automatic feature and security updates. Adobe Commerce on Cloud uses single-tenant, dedicated infrastructure through a platform-as-a-service (PaaS) model.

Adobe Commerce Optimizer is a storefront and merchandising offer that can use an existing transaction engine. Treat it as a different purchasing scope from a complete replacement commerce platform.

There’s no universal Magento enterprise pricing figure to apply to every store. The Commerce on Cloud product description defines pricing levels through gross merchandise value (GMV), average order value (AOV), order limits or another pricing tier. Its sales order also sets infrastructure allowances. A per-customer cost calculation therefore needs your actual contract and a defined customer count.

For Magento B2B pricing, separate the software entitlement from implementation. Adobe’s extension documentation identifies Adobe Commerce B2B as a separately licensed Commerce extension. It covers capabilities such as company accounts, negotiated quotes and company-specific pricing. Those capabilities aren’t an entitlement supplied by downloading Magento Open Source.

Specify the B2B workflows you need and have the supplier identify their package, extension or custom implementation. Keep configuration and ongoing support as separate lines. For SaaS, use the quoted package’s inclusions instead of assuming that the PaaS extension’s licensing applies unchanged.

Hosting and technical operations

Magento hosting costs depend on who operates each part of the store. With Open Source or self-managed Adobe Commerce, assign responsibility for server capacity and database operation. Add backups, restore testing, security monitoring and deployment work to that scope.

Adobe Commerce cloud pricing already includes an infrastructure service. The PaaS product description lists environment and capacity allowances in the sales order, with additional capacity available as add-ons. Don’t add an equivalent full hosting bill again. Adobe lists 24/7 technical support for Commerce. Budget separately for your store’s implementation and application support.

Adobe’s shared responsibility model assigns infrastructure security and availability to Adobe. Merchants still own their custom code, integrations and application patching on PaaS. They also own testing and performance checks for the customised application. Included technical support doesn’t replace an agency’s maintenance of your checkout customisations.

For backups, name who runs them, how long they’re retained and who restores the store after a failed release. Put release approval and rollback responsibility in the support agreement. Capacity without someone responsible for recovery is an incomplete operating budget.

SaaS changes the maintenance split because Adobe deploys platform updates automatically. It still needs a scoped storefront implementation, connected business systems and support for retailer-specific work. The SaaS product description sets sales-order limits and separately purchasable allowances for catalogue capacity, requests and environments. Include the allowances your catalogue and traffic require.

Implementation, extensions and migration

An implementation estimate pays for building your particular store. Its scope starts with product types and storefront design, then follows each connection required to take and fulfil an order.

Ask the implementation partner to cost the following work separately.

  • Product attributes, configurable variants and catalogue import rules.
  • Theme or storefront development, including mobile behaviour and accessibility.
  • Connections to inventory, accounting and order fulfilment systems.
  • Payment, tax and delivery rules for each market.
  • Migration of product records, customer accounts and relevant order history.
  • Redirects, acceptance testing, staff training and launch support.

An agency’s estimate is its services fee. It isn’t an Adobe licence charge, even when one proposal contains both.

The Commerce Marketplace documentation describes both free and paid extensions. Extension installation and support need their own scope. A download price alone doesn’t describe the effort to fit an extension into a customised store.

For each extension, record the licence period, supported platform versions and support entitlement. Adobe’s extension agreement ties applicable subscription and overage fees to the extension listing. It also states that fees exclude indirect taxes. Apply each third-party supplier’s own terms to its products.

Budget for compatibility testing when the platform or an extension changes. Custom development also needs a named maintainer. Ask whether that person fixes only their own code or investigates failures across several suppliers’ components.

Payments and other running charges

Payment processing is a separate operating expense from the platform licence and the work to connect checkout. Model it from your expected transactions and the payment provider’s terms. Include the effects of payment methods, international cards, refunds and disputes where they apply.

Adobe’s extension documentation distinguishes the installed payment extension from the provider account and its processing fees. Keep connection work, processing charges and ongoing payment support separate. The guide to Magento payments covers the provider setup decisions.

Search and reporting can create other recurring costs. List the capabilities already included in the selected Commerce package before adding outside services. For example, the Commerce on Cloud product description distinguishes its base package from the Commerce Intelligence bundle or upgrade.

Include integration subscriptions and the work to monitor failed data transfers. A connector’s subscription and an agency’s support retainer pay for different things. Record both when both are required, with one owner for investigating failures.

Budget for catalogue and shopping assistance

Catalogue work must keep each sellable variant consistent from the product page to the basket and customer conversation. A configurable product’s parent record alone doesn’t establish the price or available stock of every size and colour.

Include attribute mapping, variant identifiers and stock updates in the integration scope. Define which system supplies product facts and which supplies availability. Assign someone to correct failed imports and keep delivery, returns and sizing documents current. The guide to product information management explains the ownership of product information across systems.

shoppa is an AI shopping agent that helps customers discover, compare and buy products in your site’s chat using your catalogue and store documents. It also handles order support and returns. Its per-session or per-token pricing sits separately from the Commerce contract and integration work.

For Magento, scope the catalogue feed and required basket, payment and order connections. shoppa supports a two-line embed and JSON or CSV product feeds for other sites. That route needs a defined integration scope rather than an assumed native Magento connector. Include the cost of maintaining those connections when products or checkout rules change.

Make implementation quotes comparable

Give every supplier the same store scope and ask them to show one-off costs separately from recurring commitments. Use the same trading forecast and comparison period, with currency and goods and services tax (GST) treatment stated on every quote.

Include these items in the request.

  • The exact edition, deployment model and B2B entitlements.
  • Product and variant counts, store views, languages and markets.
  • The same integration list, including each system’s data direction and update frequency.
  • Production, staging and development environments, with capacity and usage allowances.
  • Migration scope and the records you’ll retain in the old system.
  • Responsibility for backups, security patches, releases and incident recovery.
  • Included support hours, response commitments and extra-work rates.
  • Extension renewals, usage overages and contract renewal terms.

Illustrative self-managed and managed scopes

Consider a retailer with one storefront, configurable products, a stock-system connection and a payment provider. These are illustrative scopes, not supplier quotes.

Cost responsibilitySelf-managed Magento Open SourceQuoted Adobe Commerce on Cloud deployment
PlatformNo software licence feeQuoted Commerce package and entitlements
InfrastructureRetailer buys and operates hosting or contracts a hostHosted infrastructure within the sales-order allowances
Store buildTheme, catalogue mapping and required connectionsStorefront work and required connections, separately scoped
Application maintenanceRetailer or agency patches and tests the applicationRetailer or agency still owns its PaaS application work
Capacity growthHost charges and operations workAdditional allowances or contract changes where required
Other servicesPayment processing, extensions and optional servicesPayment processing and services outside the package

For a first-year comparison, add implementation to the committed charges for that year and the forecast usage costs. For a later-year comparison, retain maintenance and renewals but separate future project work. Show internal staff effort alongside supplier invoices.

The totals become comparable only when the catalogue scope, capacity assumptions and support responsibilities match. Choose the proposal that funds every required responsibility, with a named owner for each, before treating the lower total as a saving.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup