What we do
Tools
Industries
Department
How we workLet's talk →
Home/Magento/Magento B2B Features, Edition by Edition
Adobe Commerce B2B

Magento B2B: Company Accounts, Quotes and Shared Catalogs Your CRM and ERP Never See

A buyer from one of your trade accounts logs in, sees their own catalog at their own prices, and sends a quote request instead of checking out. That's Magento B2B. It's a module for Adobe Commerce, the licensed edition, and it doesn't come with Magento Open Source, where extensions do the same jobs. Either way, your CRM and your ERP see none of it until something carries it across.

What the B2B module adds to an Adobe Commerce store

01

Company accounts

One business, many buyer logins. A company admin sets up users, teams and roles, and each role decides what a buyer can see and do.

02

Shared catalogs

A catalog and price list assigned to one or more companies, so a trade account sees only the products and rates you've agreed with it. They need company accounts switched on.

03

Negotiable quotes

A buyer starts a quote from the cart, and your team counters on product or shipping prices in the Admin. The whole exchange stays on the quote.

04

Purchase orders and approval rules

With purchase orders on for a company, every order is created as a PO first. Approval rules send POs over a set total, or matching other conditions, to a named approver.

05

Requisition lists and quick order

Saved lists for the items a buyer reorders, and a quick order form that takes SKUs straight into the cart.

06

Company credit

Payment on Account with a credit limit per company, and a running history of what's been charged and reimbursed.

Which Magento B2B records an integration can reach, and how

Adobe publishes which B2B modules are REST-enabled. That list sets what a CRM or ERP sync can read and write directly.

REST-enabled

Reachable from a back-office integration

  • Company accounts, with their users, teams and company relations.
  • Company credit: limits, balances and history.
  • Negotiable quotes.
  • Purchase orders.
  • Shared catalogs, with their products, categories and company assignments.
Not in REST

Storefront GraphQL, or the Admin

  • Requisition lists and quick order.
  • Purchase order approval rules.
  • Company payment method settings.

Most of what sales and finance care about, accounts, credit, quotes and POs, sits on the left. A job that depends on something on the right needs GraphQL, which works as a buyer rather than as a back-office system, or a custom endpoint. Plan for that before the build starts.

Magento B2B by edition and setup

If your store is You have What to plan for
Adobe Commerce, B2B installed but not enabled The features, off until you enable B2B and the pieces you want in the B2B Features configuration. Turning on shared catalogs changes how pricing and category permissions work for every customer, so try it on staging first.
Adobe Commerce with B2B running Company accounts, shared catalogs, quotes, POs and company credit in the store. Each one lives only in Magento until an integration copies it to the CRM and the ERP.
Magento Open Source No official B2B module. Customer groups and tier prices are in core; company accounts and quote requests come from Marketplace extensions. Each extension stores its data its own way, so an integration is written against that extension's API or tables, not Adobe's B2B endpoints.

The trade account your CRM has never heard of

A rep takes a call from a buyer asking why their last order came through at the wrong price. The answer sits in a shared catalog in the Magento Admin, which the rep can't log in to. In the CRM there's a company name and a phone number, and nothing about negotiated rates, open quotes or credit left.

Finance has the mirror image. A quote is approved in Magento at an agreed price, the order reaches the ERP, and the ERP prices it from its own list instead of the line price Magento sent. It comes to light when the customer disputes the invoice.

n-frames builds the integration on the REST-enabled B2B modules: company accounts, credit and open quotes on the CRM record your reps work from, and approved quote pricing carried onto the ERP order line by line. The order side in general is covered on Magento ERP integration.

Let's talk

Wholesale accounts that read the same in the store, the CRM and the books

n-frames builds Magento B2B integrations for Adobe Commerce stores, and for Open Source stores running a B2B extension: company accounts and shared catalog pricing into the CRM, approved quotes and purchase orders into the ERP at the agreed price, and credit balances where finance can see them.

Quotes that arrive in the ERP as agreed →

Magento B2B questions on editions, quotes and credit

Is Magento B2B the same thing as Adobe Commerce B2B?

Yes. It's one module, sold as part of Adobe Commerce. People call it Magento B2B because Adobe Commerce runs on the Magento codebase. Magento Open Source doesn't include it.

Does Magento Open Source have B2B features?

Not Adobe's B2B module. Open Source has customer groups and tier prices in core, which handle simple wholesale pricing, and Marketplace extensions add company accounts, quote requests and similar features on top.

What is a requisition list in Magento?

A saved list of products and quantities that a buyer adds to the cart in one go, for the things the account orders again and again. A buyer can keep several. It's part of the B2B module, and Adobe exposes it through storefront GraphQL rather than REST.

Can Magento's B2B quotes sync to my CRM or accounting system?

Only once something carries them. Negotiable quotes are REST-enabled, so an integration can read a quote's status, lines and negotiated prices and pass them on. If you already run a CRM connector, check whether it maps quotes and not only customers and orders. Where it doesn't, n-frames writes the sync against the quote endpoints.

Does Magento B2B handle credit limits for trade accounts?

Yes, through company credit and the Payment on Account method: each company gets a limit, and orders on account draw it down. The credit data is REST-enabled, so an ERP that owns credit decisions can read balances and history from the store.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.