Adobe Commerce official features: B2B and multi-store
According to its official documentation, Adobe Commerce offers B2B features through a dedicated extension (company accounts, shared catalogs, requisition lists, negotiable quotes, purchase orders, payment on account), a multi store hierarchy of websites, stores and store views, and a catalog with seven product types. It is a very complete platform for complex organisations. The buying question in 2026 is whether you will use enough of it to justify what it demands.
A clear disclosure: my work is on Sylius and custom shops, so I am an outsider here with a commercial interest in alternatives. Every feature below comes from Adobe's own documentation, which you can verify.
B2B: what the extension provides
The B2B introduction sets out the core functions. Company accounts group several buyers under one corporate account, with divisions and subdivisions. Shared catalogs set custom per product prices for different companies. Requisition lists let buyers keep frequently ordered products and add them to the cart. Negotiable quotes allow a back and forth on price and quantity, started by the buyer from the cart or by the seller in the Admin. Purchase orders can be subject to approval rules, and Pay on Account gives companies a credit line that you manage.
Roles deserve a closer look, because this is where large buyers are demanding. The roles documentation describes a company administrator with full permissions, a default user role, and as many custom roles as you need, such as senior and assistant buyer. Permissions cover sales, quotes, purchase orders and the company profile, and a manager can be allowed to see orders from subordinates in the hierarchy.
None of this runs on its own. The setup guide says the extension must be installed and that all B2B features are off by default. Setting Enable Company to Yes turns on company accounts, shared catalogs, quotes and the default B2B payment and shipping methods. Purchase orders and payment on account are switched on separately. So ask your integrator what is included in the "B2B" line of a quote, and which functions will be configured or adapted.
Multi store: three levels with real consequences
Adobe's multi site overview explains that one instance, with one code base and one Admin, can run several websites or store views with different languages, domains, categories, products and currencies. The structure matters more than the feature itself:
| Level | Use it for | What to remember |
|---|---|---|
| Website | Fully independent sites | Top level container; does not need to share carts, delivery or payment methods |
| Store | Separate ranges under one website | Can share carts and payment gateways; has its own catalog structure |
| Store view | Language or presentation | Mainly for locales, can have its own currency |
Two consequences are often discovered too late. The same overview says inventory quantity is managed only at website or global level, so a stock rule per store is not a given. And Adobe's store structure documentation notes that a dedicated checkout under its own domain needs specific setup, including its own security certificate. Before anyone configures a store, draw the structure on one page and have your legal, finance and logistics people read it.
Catalog: product types and the Open Source boundary
The catalog documentation lists simple, configurable, grouped, virtual, bundle, downloadable and gift card products. Configurable products are made of simple products with their own SKU, so stock is tracked per variation. Gift cards are available only in Adobe Commerce. Similarly, Order by SKU is documented as exclusive to Adobe Commerce and unavailable in Magento Open Source. If you are planning on the free edition, check each must have function by name.
Versions and support to plan for
Per endoflife.date, the latest release is 2.4.9, from 12 May 2026, with extended support for Adobe Commerce to 31 May 2029. Version 2.4.8 is listed to 31 May 2028 and 2.4.6 to 31 August 2027, while support for 2.4.5 ended on 11 August 2026. If you already run an older branch, that last date is the first thing to check. I did not find a public price for Adobe Commerce in the pages I read, so request a quote and ask for the complete three year cost.
When Adobe Commerce is the wrong choice
Adobe Commerce makes sense when you have several brands or countries, buyers who need approval chains and credit lines, and a budget for a skilled team. It is too much when you run a single store with a few price lists. You would then be paying for capacity you never use, and your updates would carry its full weight. A hosted option such as Shopify's B2B features may be enough. If you have very specific rules and want a Symfony base, look at what Sylius offers. And if you need Adobe's depth, hire a specialist integrator rather than a generalist like me: that is a better use of your money.
Questions to ask before signing
Ask your supplier which B2B functions are native, configured or custom in their proposal. Ask how the website, store and store view structure maps to your legal entities and your stock. Ask which version the project starts on, who applies patches, and what a move away would involve, including who holds the code and data. A good integrator will welcome these questions.
Next step
If you want an outside view before a large commitment, or if you suspect that a lighter platform could do the job, explain your situation via my ecommerce page. I reply within 24 working hours, and I will tell you if Adobe Commerce is the right answer.