B2B wholesale, multi-store retail, marketplaces, large catalogs. Where Magento is worth its running cost, plus the revenue and edition questions that come before site type.
Most pages answering "what is Magento used for" list features and call them use cases. Product catalog management is not a use case. It is a thing every ecommerce platform does.
The question a merchant is actually asking is whether Magento is the right platform for their store, and that has two forks before site type ever comes up. The first is scale. Magento is expensive to build and expensive to keep running, and below roughly one to two million dollars of yearly revenue on a straightforward catalog, Shopify or WooCommerce will serve you better and cost a fraction. We will say that to your face before quoting a build. The second fork is edition: Magento Open Source is free and capable, Adobe Commerce is licensed on your gross merchandise value and starts in the low five figures a year, and features people assume are standard Magento, native B2B being the obvious one, exist only on the paid edition.
Clear those two and site type becomes a useful conversation. Magento pays off when the store itself is complicated: many attributes per product, several storefronts or currencies from one backend, pricing that differs per customer, or an ERP that must stay in sync. Below is where we have seen that hold, and where we have watched merchants regret it.
Only above a certain size. At $5M+ a year with 20K+ SKUs and complex catalog logic, Magento's flexibility pays back. Under that, Shopify or WooCommerce costs less and ships faster, and we'll say so.
Magento's home turf. Customer-specific pricing, NET payment terms, quote workflows and requisition lists ship in Adobe Commerce B2B out of the box. No other open-source platform comes close.
Multi-vendor and multi-store setups running several brands or country storefronts from one admin. Magento was built for this; most hosted platforms charge per storefront or simply can't.
The scale test, stated plainly
Under about $1M a year with a few hundred simple products, Magento is a mistake. You will spend on hosting, developers and extensions what a hosted platform charges you in total, and you get a slower start. Between $1M and $5M it depends entirely on catalog complexity, not revenue. Above that, or anywhere with B2B pricing rules and multi-store requirements, Magento starts winning on the things hosted platforms charge extra for or refuse outright.
Open Source or Adobe Commerce
Magento Open Source runs a serious store and costs nothing in licence. Adobe Commerce adds native B2B, advanced customer segmentation, page builder, and Adobe's hosting and support, and it is quoted per merchant against your revenue. The honest rule we use: stay on Open Source until a specific paid feature is blocking money, then price the licence against building that feature. For B2B specifically the maths is usually the deciding factor, which we work through on the B2B Suite page.
Where Magento is the wrong answer
Content-led sites with a small shop attached, where the editorial experience matters more than the catalog: WordPress with WooCommerce. Single-product or subscription businesses with simple fulfilment: Shopify. Any team without access to a developer, because Magento without maintenance is not a cheap store, it is a security incident with a countdown.
What running it actually costs
Budget for hosting built for Magento rather than generic shared hosting, a patch cadence that follows Adobe's security releases, and extension renewals. Stores that skip the patch cadence are the ones we meet during an emergency. If you want the maintained version of that, our Magento development services page covers builds and retainers, and the Magento extensions library covers what we install and why.
Start with the closest fit
Read the page that matches your store: Magento for B2B covers company accounts, contract pricing and the edition decision, Magento for ecommerce covers the standard multi-store retail case, and Magento for marketplaces covers multi-seller builds. If your store does not resemble any of them, that is a signal worth taking seriously before you commit to a platform this expensive to run.
Ecommerce stores complicated enough that a hosted platform gets in the way. In practice that means large catalogs with many product attributes, several storefronts or currencies from one backend, wholesale and retail pricing side by side, and integrations with an ERP or PIM that must stay in sync. Nike, Ford and other large brands run Magento, but the reason to pick it is the shape of your catalog, not the size of the logos already on it.
As a rule of thumb, under about $1M a year with a simple catalog it does not, and Shopify or WooCommerce will cost you far less to run. Between $1M and $5M the answer depends on how complicated your products and pricing are rather than the revenue figure. Above that, the total cost usually favours Magento because the alternatives start charging per transaction or refusing the requirements outright.
Start on Open Source. It is free and it runs a real store. Move to Adobe Commerce when a specific paid feature is blocking revenue, most often native B2B, advanced segmentation, or a procurement requirement for vendor support. The licence is quoted per merchant against gross merchandise value and starts in the low five figures a year, so price it against what building the equivalent would cost you.
Yes, particularly in B2B, wholesale, and multi-market retail. The small end of the market left for Shopify years ago, which makes the platform look smaller than it is. What has genuinely changed is the frontend: Hyva has become the default choice for new builds, replacing the Luma theme that gave Magento its reputation for slow storefronts.
It is one of the strongest options available, with the significant caveat that native B2B features are Adobe Commerce only. Company accounts, shared catalogs, negotiable quotes and approval workflows do not exist in Open Source; you would install a third-party suite from a vendor such as Amasty or Webkul instead. Decide the edition first, because it changes the entire build.
The licence is only part of it. Plan for hosting built for Magento rather than a generic shared plan, a developer or agency applying Adobe's security patches on schedule, and annual renewals on paid extensions. The stores that get into trouble are the ones that budget the build and nothing after it.
Not natively, but it is a common build with a marketplace extension on top, and it holds up better than most platforms because the catalog and pricing model are flexible enough to carry seller-specific rules. It is a real project rather than a configuration exercise, so scope it as one.
30 minutes with a senior engineer. No salespeople. We respond within one business day with a brief outline.
Send a project brief →