Adobe Commerce review

Adobe Commerce is an enterprise ecommerce platform for selling across storefronts, markets, and channels. It brings together storefront tools, product discovery, personalization, and B2B features, with APIs and apps for extending or integrating the platform. The product description says its AI features include conversational discovery and semantic search, while commerce data can tailor recommendations, campaigns, and storefront content.

There are three paid packages in the pricing information reviewed: Adobe Commerce as a Cloud Service (SaaS), Adobe Commerce on Cloud (PaaS), and Adobe Commerce Optimizer. All require a custom quote; monthly and annual prices are not published. Magento Open Source is listed at $0 per month for teams that can self-host. That is a free software license, not a statement that hosting or implementation is free. The pricing information does not publish a free trial.

Adobe Commerce is built for stores with complex catalogs, markets, or selling requirements—not just a standard storefront. Its described capabilities cover product pages, carts, checkout, content creation, and A/B testing, alongside AI-assisted search and product discovery. Personalization tools use commerce data to adjust recommendations, campaigns, and storefront content.

• B2B workflows: The platform supports company accounts, customer-specific catalogs and pricing, quick orders, and online quote negotiation.
• Expansion and integration: Adobe describes APIs, apps, and precomposed services for extending the platform, plus support for multi-market growth and auto-scaling.
• Large catalogs: The product information says it supports catalogs with millions of SKUs. It does not give a maximum SKU count.

That breadth may help merchants that have outgrown simpler tools or need business-specific buying flows. One Reddit discussion about moving from Shopify Plus raised inventory sync and checkout customization as pain points, though it does not establish that Adobe Commerce will solve them for every store. Buyers should map those requirements to an implementation plan before treating feature availability as a migration case.

The main drawback is price uncertainty. The three paid packages—SaaS, Cloud (PaaS), and Commerce Optimizer—are listed as custom quote, with no published monthly or annual price. The reviewed pricing information also gives no plan-by-plan feature matrix or specific caps for users, markets, catalog size, or usage. Adobe says catalogs can contain millions of SKUs, but does not publish a maximum in the material reviewed. Get those limits and any overage terms in writing before comparing quotes.

Cloud costs and migration effort are another concern. In a Reddit thread, merchants reported that Adobe Commerce Cloud could raise total cost of ownership and cost more than alternative hosting; those are individual accounts, not a universal price comparison. A separate thread described one merchant's estimated implementation cost as 2–3x its current annual Shopify spend before a functioning store. That is not an Adobe quote, but it shows why license price alone is a poor comparison. Teams may also need developers familiar with the cloud deployment model, according to commenters.

Adobe Commerce’s paid packages require a custom quote; the published pricing information lists no monthly or annual rates. That means there’s no public tier ladder to compare, and we can’t quantify the jump between cloud options. The listed paid plans are Adobe Commerce as a Cloud Service (SaaS), Adobe Commerce on Cloud (PaaS), and Adobe Commerce Optimizer. All three are quote-based.

The free option is Magento Open Source: $0 per month for the software license, with self-hosting required. That is not the same as a free hosted Commerce plan. Hosting and other operating costs are not priced in the published information, so teams should budget separately rather than treat the license price as the total cost. The pricing data lists no add-ons, but that does not establish that every extra capability is included. Monthly and annual billing prices are not published. Ask Adobe for a quote that spells out package scope, contract term, and any extra costs before comparing it with a migration budget.

Treat a move to or from Adobe Commerce as a project, not a storefront swap. Before migrating, map the catalog, customer-specific pricing, company accounts, quick orders, quote workflows, storefront content, and integrations you rely on. Those capabilities are part of the product description; the published information does not explain how they transfer or what export tools are available. Get those details, plus any contract and data-exit terms, in writing before committing.

Adobe describes the platform as API-based and extensible, with storefront tools and support for catalogs with millions of SKUs. That flexibility can mean more integrations and workflows to account for when changing platforms; the published material does not quantify migration time or effort. We also don’t have Reddit posts or comments in the published sources, so we can’t responsibly report what users say makes them leave. If cloud migration risk or unclear pricing is a concern, resolve those questions before signing rather than assuming a future exit will be simple.