Adobe Commerce B2B is the set of business-to-business modules Adobe builds for Adobe Commerce: company accounts, shared catalogs with company-specific pricing, negotiable quotes, purchase orders with approval rules, requisition lists, quick order and payment on account. For many wholesalers, distributors and manufacturers, it is the reason to choose Adobe Commerce over Magento Open Source. It is also where scoping goes wrong most often in Adobe Commerce B2B implementation projects, because teams assume the module covers more than it does.
This guide covers the module itself: which editions include it, what is in the box, how it is switched on, how it sits next to an ERP and a PIM, and where it stops. Every product fact comes from Adobe's documentation as of October 2026. For a feature-by-feature walkthrough of the buyer experience, see our guide to Magento B2B features. If you are still choosing a platform, our Adobe Commerce vs BigCommerce B2B comparison covers that decision.
What Adobe Commerce B2B is, and which editions include it
Adobe's developer documentation describes B2B for Adobe Commerce as a set of modules installed on top of Adobe Commerce, and labels it a feature exclusive to Adobe Commerce. Adobe's Admin guide describes it as an integrated solution for both B2B and B2C, so one store can serve company buyers and consumers from the same catalog and back office.
| Edition | Adobe Commerce B2B |
|---|---|
| Magento Open Source | Not included. B2B features come from third-party extensions or custom code. |
| Adobe Commerce on-premises | Installed as the B2B extension with Composer, then enabled in the Admin. |
| Adobe Commerce on Cloud (PaaS) | The same extension, added to the Cloud project and deployed. |
| Adobe Commerce as a Cloud Service (SaaS) | Pre-installed with core B2B features, such as company management and quoting. |
What does Adobe Commerce B2B cost? Adobe does not publish Adobe Commerce prices. Its pricing page offers a "Get pricing" request for each edition instead of a number, so licensing is quote-based. Confirm that your Adobe agreement covers the edition you plan to run B2B on, and budget the implementation separately.
What the Adobe Commerce B2B module includes
Adobe ships B2B as named modules (Company, CompanyCredit, SharedCatalog, NegotiableQuote, PurchaseOrder, QuickOrder, RequisitionList and others). In business terms, that is eight capabilities:
| Capability | What it does | Depends on |
|---|---|---|
| Company accounts | One account per business, with a company administrator, teams, users, roles and permissions | Enable Company |
| Company hierarchy | Child companies assigned to a parent, managed by the parent's company administrator | Company accounts |
| Payment on Account | Purchases against a credit limit the merchant sets, with a credit history per company | Company accounts |
| Shared catalogs | Which products and prices each company sees: one public catalog plus unlimited custom catalogs | Company accounts |
| Negotiable quotes and quote templates | Price, quantity and shipping negotiation; templates reuse negotiated terms for recurring orders | Company accounts |
| Purchase orders and approval rules | Orders become purchase orders that route through the company's approval rules | Enabled per website and per company |
| Requisition lists | Saved lists of frequently ordered products, up to 999 per buyer account | Independent setting |
| Quick order | Ordering by SKU or product name, typed in or imported | Independent setting |
B2B 1.5.0, released October 30, 2024, added company hierarchy, users who belong to several companies and switch between them on the storefront, and quote templates with order thresholds. Our feature-by-feature guide shows how each capability looks to a buyer.
How to install and enable Adobe Commerce B2B features
On Adobe Commerce as a Cloud Service there is nothing to install. On-premises and on Adobe Commerce on Cloud, B2B is a Composer metapackage, magento/extension-b2b, installed after Adobe Commerce with your repo.magento.com keys. On Cloud, Adobe recommends starting in an Integration or Staging environment: add the package to composer.json, push to deploy, and confirm the Magento_B2b module is enabled. On-premises, run composer require and the usual setup and deploy commands.
Match the versions. Each B2B release supports specific Adobe Commerce versions. As of October 2026, Adobe lists B2B 1.5.3 for Adobe Commerce 2.4.8 and 2.4.9, and B2B 1.5.2-p5 for 2.4.6 and 2.4.7, both released May 12, 2026. PHP 8.3 requires B2B 1.5.0 or later. If you are still on 2.4.4 or 2.4.5, read our guide to Magento 2.4 versions and end-of-support dates first.
Keep the consumers running. The extension uses MySQL message queues, and shared catalogs, quotes and purchase orders depend on their consumers, such as sharedCatalogUpdatePrice and negotiableQuotePriceUpdate. Adobe's install guide includes cron entries that restart the shared catalog consumers if they stop. When shared catalog prices do not update after launch, check the consumers first.
Enable features in the Admin. All B2B features start disabled. Turn them on under Stores > Settings > Configuration > General > B2B Features, scoped to the right website on multi-site installations:
- Enable Company switches on Shared Catalog, B2B Quote and the B2B payment and shipping methods automatically.
- Quick Order and Requisition List are independent settings.
- Purchase orders are enabled per website, then per company in each company's advanced settings.
- Payment on Account is a payment method you can offer globally or per company.
- Quote settings define the minimum cart amount for a quote request, the default expiration period and allowed attachment types.
On Adobe Commerce as a Cloud Service, the storefront differs: Adobe states the SaaS edition does not support Luma storefronts, and in January 2026 it released B2B drop-in components for Commerce Storefront on Edge Delivery Services, covering company management, purchase orders, quotes and requisition lists. Our comparison of Adobe Commerce as a Cloud Service and Adobe Commerce on Cloud covers the rest of that choice.
How the B2B module fits with your ERP and PIM
The B2B module models companies, catalogs, quotes and approvals. It does not replace the ERP, which usually stays the source of truth for customer accounts, contract prices, credit and invoices. Integration work is mostly deciding which system owns each object:
- Company accounts mirror ERP customer accounts, including parent and child relationships, which B2B 1.5.0 made manageable through a Company Relations REST endpoint.
- Shared catalogs hold company prices as a fixed price or a percentage discount per product, plus tier prices, so ERP price lists must be mapped into that model. Adobe notes the shared catalog's Custom Price column is blank for configurable, grouped and gift card products, so check how your product types map.
- Company credit tracks limits, purchases, refunds and reimbursements. Out of the box, an admin records customer payments in the Admin, so on an ERP-connected store the integration usually posts them through the CompanyCredit API.
- Purchase orders and quotes become ERP sales orders once approved or accepted.
- The PIM feeds product data; shared catalogs then decide which companies can see and buy each product.
Adobe lists Company, CompanyCredit, NegotiableQuote, PurchaseOrder and SharedCatalog as REST-enabled modules; QuickOrder, RequisitionList and PurchaseOrderRule are not, although GraphQL covers requisition lists and approval rules for storefront use. On the SaaS edition, 2026 releases added shared catalog events for Adobe I/O Events and REST filtering of orders and invoices by company, and Adobe offers an App Builder integration starter kit for back-office connections.
The native model is a starting point, not a requirement. On QC Supply's headless Adobe Commerce build, Microsoft Dynamics NAV drives catalog, inventory, pricing and orders through a custom bidirectional integration, and the B2B Pro portal runs on customer groups and NAV-driven tiered pricing, replacing the Shared Catalog model while keeping company and sub-account structures. Our Adobe Commerce integrations team scopes that kind of mapping, and our Magento ERP integration guide compares connector, middleware and custom options.
For every B2B object, write down which system creates it, which system can change it, and how fast changes must reach the other side. Company records, contract prices and credit balances cause the most rework when nobody decides up front.
What Adobe Commerce B2B can't do on its own
Some limits are documented by Adobe; others are things the module was never meant to do.
Boundaries Adobe documents
- No Magento Open Source. The B2B modules are exclusive to Adobe Commerce.
- One public shared catalog. Only one public shared catalog can exist at a time, and once Shared Catalog is enabled it controls all category permissions, ignoring existing customer group permission settings.
- No Payment on Account on multi-address orders. It is not offered for orders with multiple shipping addresses.
- Purchase order payment rules. Approval flows support PayPal Express and Braintree for online payments, and checkouts that send the buyer to another site are not supported. Gift cards, store credit and reward points are not supported with online payments on purchase orders, and a purchase order cannot become an order while any of its products is disabled or out of stock.
- Three approval rule types. Rules are based on order total, shipping cost or number of SKUs. Other approval logic needs custom development.
- Quotes are for companies. Negotiation is open to authorized company buyers and sales reps. A buyer's change sends the quote back to the seller, and no discounts can be added after the buyer accepts.
- Account structure rules. A user can belong to several companies but administer only one. A parent cannot be assigned to another parent, and each child has one parent, so deeper account trees need custom work.
- Version lockstep. Every Adobe Commerce upgrade needs a matching B2B release and PHP version.
- SaaS data model. The SaaS edition offers custom attributes for core and B2B entities rather than full data model customization, and Adobe notes industry-specific customizations may need additional implementation work.
What is not in the box
Adobe's B2B module list has no ERP connector, PIM, product configurator, parts-compatibility logic or punchout catalog; those come from integrations, extensions or custom code. Headless builds need attention too: on QC Supply's PWA Studio storefront, B2B account management, roles and company structure were delivered through a custom module.
When you need custom work or a B2B extension
Most B2B builds mix native configuration, extensions and custom code:
- Configure natively when pricing fits fixed, percentage or tier prices per catalog, approvals fit the three rule types, and your storefront already supports the B2B screens.
- Add an extension when the gap is common and a maintained extension covers it, from a vendor that keeps pace with Adobe Commerce and B2B releases.
- Build custom when the logic encodes how your business differs: prices the ERP calculates at order time, multi-warehouse order splitting, headless B2B screens, or catalog logic no extension models. For a Fortune 500 equipment OEM, that meant a parts finder that matches by model and serial number, built on Adobe Commerce, because no B2B setting can tell a buyer which part fits their machine.
Keep custom code in its own tested modules or apps so upgrades do not break order flow. Our Adobe Commerce development services team builds and maintains that layer.
Adobe Commerce B2B implementation steps and timeline factors
The order of work is consistent from project to project:
- Confirm edition and versions, with Adobe Commerce, B2B and PHP versions that support each other.
- Model the companies: accounts, parent and child relationships, buyer roles and approval rules.
- Choose the pricing model: shared catalogs, customer groups with tier prices, ERP-calculated prices, or a mix.
- Design the integrations, with an owner for every object.
- Install and enable in a non-production environment, with consumers and cron running.
- Build the storefront B2B experience on your theme, a headless front end or the SaaS drop-ins.
- Migrate and clean data: companies, users, roles, credit limits and price lists.
- Test with real buyer roles, including approvers and sales reps.
- Roll out in phases, starting with a group of accounts.
The install rarely drives the timeline. The number of companies and roles, the size of shared catalogs, how prices are calculated, the depth of the ERP integration, the storefront type and the state of your account data do. Adobe's 2026 SaaS releases include several fixes for large shared catalogs, so test catalog scale early.
Adobe Commerce B2B vs Magento Open Source plus B2B extensions
Magento Open Source B2B stores are built from third-party extensions and custom code rather than Adobe's modules. The trade-offs are predictable:
| Adobe Commerce B2B | Magento Open Source plus extensions | |
|---|---|---|
| Where B2B comes from | Adobe-built modules for companies, catalogs, quotes, purchase orders and credit | Third-party extensions or custom modules |
| Compatibility | Adobe releases B2B versions for each supported Commerce release and documents tested pairings | Each vendor's own schedule; you test the combination |
| APIs | Adobe-documented REST and GraphQL for B2B entities | Varies by extension |
| Hosting | On-premises, Adobe Commerce on Cloud, or pre-installed on SaaS | Self-hosted |
| Licensing | Adobe Commerce license, quote-based | No platform license; extension licenses vary |
Open Source with extensions can work when B2B needs are narrow, such as customer group pricing, quick order and a simple quote request, and your team will own upgrade testing. Adobe Commerce B2B fits better when hierarchy, approvals, negotiated quotes and credit all matter and you want them released and tested together. Our Magento Open Source vs Adobe Commerce comparison covers the edition decision, and our B2B ecommerce development team can compare Adobe Commerce with other B2B platforms.
Either way, the module is only part of the answer; the rest is how your accounts, prices and ERP data fit it, which is where our work on B2B ecommerce on Magento and Adobe Commerce starts.
Scoping an Adobe Commerce B2B project?
We will map your companies, pricing and ERP data against the B2B module, show you what works natively and what needs an extension or custom code, and give you a firm, itemized quote.
Book a 30-minute assessmentFrequently asked questions
Is Adobe Commerce B2B available on Magento Open Source?
No. Adobe documents B2B as exclusive to Adobe Commerce. Magento Open Source stores get B2B features from third-party extensions or custom development.
Is the B2B module included with Adobe Commerce, and what does it cost?
On Adobe Commerce as a Cloud Service, core B2B features are pre-installed. On Adobe Commerce on Cloud and on-premises, B2B is an extension you install with Composer. Adobe does not publish prices; you request pricing for each edition, so confirm B2B coverage in your Adobe agreement.
How do I enable B2B features in Adobe Commerce?
After installing the extension on Cloud or on-premises, go to Stores, Settings, Configuration, General, B2B Features in the Admin. Setting Enable Company to Yes turns on shared catalogs, B2B quotes and the B2B payment and shipping methods. Quick order, requisition lists and purchase orders have their own settings.
Which B2B version do I need for my Adobe Commerce version?
As of October 2026, Adobe lists B2B 1.5.3 for Adobe Commerce 2.4.8 and 2.4.9, and B2B 1.5.2-p5 for 2.4.6 and 2.4.7. PHP 8.3 requires B2B 1.5.0 or later. Check Adobe's B2B release notes before every upgrade.
Can Adobe Commerce B2B connect to my ERP?
Yes, through integration rather than a built-in connector. Adobe provides REST APIs for companies, company credit, negotiable quotes, purchase orders and shared catalogs, and the ERP side is built with a connector, middleware or custom code.
What are the main limitations of Adobe Commerce B2B?
It is not available on Magento Open Source, supports one public shared catalog at a time, does not offer Payment on Account on multi-address orders, limits approval rules to order total, shipping cost and number of SKUs, and includes no ERP connector, configurator or parts-compatibility logic.