Adobe Commerce B2B: Native Features, Fit, Limits and Rollout

Adobe Commerce B2B is the set of business-to-business features built into Adobe Commerce. It covers company accounts with roles, shared catalogs with company-specific prices, negotiable quotes, purchase orders with approval rules, requisition lists, quick order and payment on account. On Adobe Commerce on Cloud or on-premises it's an extension your developers install. On Adobe Commerce as a Cloud Service there's no install step, but B2B still has to be in your contract.

This guide explains each feature, who it suits, the integrations B2B stores need, the gaps that need custom work and a rollout plan.

What is Adobe Commerce B2B?

Adobe Commerce B2B is a module that lets one Adobe Commerce store sell to companies as well as to consumers. Adobe built it for sellers whose customers are companies, often with complex structures. Those companies have many buyers, each with different roles and purchasing rights. B2B and B2C can run side by side on the same instance.

It exists only on Adobe Commerce. It isn't part of Magento Open Source. The storefront package that B2B features need on Adobe's newer storefront doesn't support Open Source either.

How you get it depends on how you run Commerce:

• Adobe Commerce on Cloud or on-premises (PaaS): developers add the B2B extension with Composer, the PHP package manager. At the time of writing, B2B 1.5.3 is the supported version for Adobe Commerce 2.4.9 and 2.4.8.
• Adobe Commerce as a Cloud Service (SaaS): Adobe marks the Composer install as PaaS only. You switch features on in the Admin, and Adobe installs the B2B storefront package for you.

Either way, every B2B feature starts switched off. Turning on company accounts also turns on shared catalogs, B2B quotes and B2B payment and shipping methods. Quick order and requisition lists can be enabled on their own.

One licensing point catches people out. Adobe's storefront documentation calls Adobe Commerce B2B a "separate extension and license on Commerce." It tells you to ask your account representative to add it to your contract. Check that it's on your order form before you plan around it.

What B2B features does Adobe Commerce include?

Adobe Commerce B2B covers the main buying workflows of distributors and manufacturers, from account structure to approvals. The table gives the short version, and the sections below explain how each feature behaves in practice.

Feature	What it does	Who uses it
Company accounts	Groups buyers under one company with roles	Buyer admins, sales reps
Company hierarchy	Links subsidiaries under a parent company	Merchant admins
Shared catalogs	Company-specific products and prices	Merchandisers, pricing teams
Negotiable quotes	Price negotiation between buyer and seller	Buyers, sales reps
Quote templates	Reusable pre-agreed terms for repeat orders	Key accounts
Purchase orders	Orders that pass approval rules first	Managers, finance
Requisition lists	Saved lists for repeat buying	Frequent buyers
Quick order	Ordering by SKU or product name	Buyers who know part numbers
Payment on account	Buying on a company credit line	Finance teams

Company accounts and hierarchy

The company account is the building block that every other B2B feature depends on. A company administrator sets up divisions, users and roles, then decides who can order, request quotes, see credit or edit the profile. New customers can apply for a company account from the storefront.

Since B2B 1.5.0, one buyer can belong to several companies and switch between them on the storefront. Catalogs, prices, quotes and orders change with the company. Since 1.5.1, each company also keeps its own cart. Merchants can group companies under a parent, so a head office can manage its regional businesses from one place.

Shared catalogs and contract pricing

Shared catalogs give each company its own product range and prices. There's one public shared catalog for guests and individual shoppers, plus custom catalogs that only members of assigned companies can see. Adobe's documentation notes that the system supports only one public shared catalog at a time.

Turning shared catalogs on hands control of category permissions to them, and existing customer group permissions are ignored. On a live store, plan that switch carefully. Products can disappear from view if the catalog setup isn't finished first.

Negotiable quotes and quote templates

A buyer can request a quote from the cart, or a sales rep can start one from the Admin. Both sides then add items, change quantities and apply discounts until they agree, and the history is kept on the quote. Buyers can save draft quotes, rename and copy them. Sellers can lock a line-item discount so a later quote-level discount doesn't stack on top.

Quote templates, added in B2B 1.5.0, handle standing agreements. You negotiate terms once and set minimum and maximum quantities or order commitments. The buyer then creates pre-approved linked quotes for each repeat order. Adobe's product pages call these standing quotes.

Purchase orders and approval rules

When purchase orders are on for a company, every order is created as a purchase order first. Company admins write approval rules based on order total, shipping cost or the number of distinct SKUs, and choose which roles must approve. If several rules apply, every required approver has to sign off.

Two details matter in day-to-day use. A purchase order freezes prices, discounts and shipping at the moment it's created, even if prices change later. Online payment details are only collected after approval. Adobe's documentation lists PayPal Express and Braintree as the supported online methods for approval flows, alongside offline ones.

Requisition lists, quick order and payment on account

Requisition lists save time for buyers who reorder the same items. A buyer can keep several lists, for different sites, teams or projects, and add a whole list to the cart at once. Quick order lets a buyer who knows part numbers order by SKU or product name without browsing.

Payment on account lets a company buy against a credit line that you set. You allocate the credit limit, manage reimbursements and let buyers see their company credit in their account. If the real balance lives in your ERP, you'll need an integration to keep the two in step.

How does B2B work on Adobe Commerce as a Cloud Service?

On the SaaS version, B2B runs inside the Adobe-managed service and reaches shoppers through B2B drop-in components on the Edge Delivery Services storefront. In January 2026 Adobe released drop-ins for company management, company switching, purchase orders, quotes and requisition lists. Quick order followed in March 2026.

These drop-ins rely on a B2B compatibility package that adds the storefront GraphQL calls they need. On the cloud service, Adobe installs it for you. On Commerce on Cloud or on-premises, it's only available if you've added Adobe Commerce Optimizer.

Releases have filled gaps quickly. During 2026 Adobe added a company address book shared across purchase orders, quotes and returns, plus requisition list sharing. It also added seller-assisted buying, where a rep places orders for a customer who has allowed it. One limit to check: in the June 2026 release, the storefront hierarchy block handled a parent and its direct children only.

The bigger change is how you customize. The cloud service is out-of-process only, so you build changes with APIs, events, webhooks and App Builder, not PHP modules. Data model changes are limited to custom attributes on core and B2B entities. If your B2B plan depends on heavy custom PHP, settle that first.

Our guide to Adobe Commerce on Edge Delivery Services covers the storefront side in full. It also explains what the storefront needs on each backend.

Who is Adobe Commerce B2B a good fit for?

It fits businesses that sell to companies on negotiated terms, with several buyers per account and some kind of approval. It also suits teams that want B2B and B2C on one platform. Typical examples are manufacturers selling to dealers, distributors with thousands of trade accounts and brands running a wholesale portal next to their consumer store.

Signs it's a strong fit:

• Prices differ by customer, contract or region, and buyers must only see their own.
• Buyers reorder often and know part numbers.
• Customers want approvals and spending control inside the store.
• Your sales team still negotiates, but wants the quote and the order in one place.
• You run, or plan to run, consumer and trade sites from the same catalog.

It's a weaker fit when your B2B selling is simple, such as one price list paid by card, since you'd pay for depth you won't use. It's also a stretch when most of the value sits in complex product configuration or engineered-to-order quoting. That work usually belongs in a configure-price-quote (CPQ) tool. And if your ERP stays the only place where prices and credit are true, integration becomes the biggest part of the project.

Which systems does a B2B store need to integrate with?

Almost every B2B store connects to an enterprise resource planning (ERP) system. Many also connect a product information management (PIM) system, a CPQ tool and a customer relationship management (CRM) platform. The B2B module runs the buying experience, while those systems usually own the data behind it.

System	What usually flows	Direction
ERP	Prices, credit, stock, orders, invoices	Both ways
PIM	Product data, attributes, media	Into Commerce
CPQ	Configured products and quoted prices	Into quotes
CRM	Accounts, contacts, sales rep owners	Both ways
eProcurement	Punchout sessions and purchase orders	Both ways

Adobe gives you several building blocks for this work. Its integration starter kit provides templates, onboarding scripts and reference flows for orders, customers, inventory, products and shipping status. App Builder, API Mesh, events and webhooks handle custom flows outside the core code. Adobe also points to prebuilt connectors on Adobe Exchange for systems such as Microsoft Dynamics 365, SAP S/4HANA and IBM Sterling Order Management.

Picking or replacing the ERP itself is a separate decision with its own trade-offs. Our note on choosing an ERP for Adobe Commerce looks at that question.

What are the limits, and what needs custom work?

The native features cover the buying workflow well. But they don't connect themselves to your back office, and some common B2B needs aren't native at all. Plan for these early, because they drive cost far more than feature setup does.

Need	Native today?	Usual approach
Contract prices from the ERP	Partly, shared catalogs hold prices	Integration that feeds shared catalogs
Live credit and invoices	Partly, company credit exists	ERP integration and account pages
Punchout to buyer procurement	No documented native feature	Marketplace extension or custom build
Complex product configuration	No	CPQ integration or custom configurator
Deep hierarchies on the new storefront	One level in June 2026	Custom block, or wait for updates
Online payment in PO approvals	PayPal Express and Braintree listed	Confirm your gateway early
B2B pricing in Commerce Optimizer	Needs the B2B connector	Add the B2B connector

Punchout deserves a closer look. Adobe's documentation doesn't describe a built-in punchout feature, and Adobe's Commerce Marketplace lists third-party punchout extensions. Adobe's May 2026 cloud service release did add an option that it says "enables B2B punchout workflows." It lets a one-time password login run without reCAPTCHA. That's a useful building block, not a finished punchout catalog.

Other limits are worth knowing before you scope:

• The base Adobe Commerce Optimizer connector syncs B2C catalogs only. It doesn't carry shared catalogs or company assignments, which need the separate B2B connector.
• On PaaS, shared catalog prices, quote prices and purchase order processing run through message queue consumers. If those consumers stop, prices and approvals quietly stall.
• B2B versions are tied to Commerce versions, so upgrades need planning. Adobe's notes have flagged PHP compatibility issues between some B2B and Commerce versions.

How do you roll out Adobe Commerce B2B?

Roll it out in stages. Model your customers, settle where each kind of data lives and build the integrations. Then pilot with a few friendly companies before you move everyone. B2B buyers are less patient with a broken reorder than consumers are, because the store is part of their working day.

• Map your customers. List the company structures, roles and approval habits you really see. Decide which accounts get custom catalogs and which use the public one.
• Decide the source of truth. Settle whether the ERP or Commerce owns prices, credit, stock and order status, and how fresh each must be.
• Pick your platform and storefront. Choose between the cloud service and PaaS, and between the Edge Delivery Services storefront and your current front end. Our overview of Adobe Commerce solutions explains the options.
• Build integrations before features. Shared catalogs and quotes are only as good as the prices feeding them.
• Load companies and users. B2B 1.5.3 added import and export of company customer data through the standard Admin tools.
• Pilot with a handful of accounts. Choose companies that buy in different ways, and watch reorders, quotes and approvals for a few cycles.
• Train sales and service teams. Reps need to know quoting, assisted buying and how to help a buyer who's stuck.
• Roll out in waves. Move accounts by region or segment, and keep the old ordering route open until each wave is stable.

Many teams bring in a specialist for the build. If you're hiring, our guide to choosing an Adobe Commerce B2B development agency covers skills, proposals and risks.

How much does Adobe Commerce B2B cost?

Adobe doesn't publish list prices for Adobe Commerce or its B2B module. Its packages and pricing page asks you to request pricing for each package. Its storefront documentation treats B2B as a separate license on Commerce.

What moves your total cost is mostly the work around the module:

• The number and complexity of back-office integrations, especially ERP pricing and credit.
• How many custom catalogs and price rules you maintain.
• Your deployment, since the cloud service needs out-of-process customizations while PaaS allows PHP.
• Your storefront choice, and if you're rebuilding it at the same time.
• Data migration for companies, users and order history.
• Ongoing support, upgrades and the integrations you'll have to keep running.

Ask Adobe to confirm B2B is in scope on the order form. Ask implementers to price each integration as its own line. Our Adobe Commerce RFP template has sections for both.

What should you do next?

Start by writing down how your best customers buy today, then test that against what Adobe Commerce B2B offers natively. A short, honest list of gaps is worth more than any feature demo.

• Confirm with Adobe that B2B is included in your Adobe Commerce contract.
• List company structures, roles and approval rules from real accounts.
• Decide which system owns prices, credit, stock and order status.
• Note the needs that aren't native, such as punchout, CPQ and deep hierarchies, and get them estimated.
• Choose your deployment and storefront before you scope the B2B build.
• Plan a pilot with three to five companies that buy in different ways.
• On PaaS, check message consumers and B2B version compatibility before go-live.

When you're ready to compare implementers, filter firms in our Adobe Commerce partner finder, or browse the full Adobe Commerce partner list.