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.
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.
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.
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.
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.
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.
Saved lists for the items a buyer reorders, and a quick order form that takes SKUs straight into the cart.
Payment on Account with a credit limit per company, and a running history of what's been charged and reimbursed.
Adobe publishes which B2B modules are REST-enabled. That list sets what a CRM or ERP sync can read and write directly.
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.
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.
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 →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.
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.
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.
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.
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.