A business buyer is rarely one person with a card. It is a company: several people, their own prices, someone who approves, an invoice to pay later.
Magento Open Source and Mage-OS know customers, customer groups and tier prices. Neither ships a company account, a negotiated quote or a purchase order approval. For a store selling to consumers, that is fine. For a manufacturer or distributor, the missing part lands on the sales team, in phone calls and spreadsheets.
What real B2B means
Real B2B means the store treats the company as the customer.
- Customers run their own accounts: members, roles, teams and addresses.
- Every buyer sees their own price and their own catalog.
- The customer's own rules hold at checkout: budgets, approvals and spend limits.
- Credit and invoices sit next to the orders they belong to.
- ERPs, headless storefronts and AI agents get the same prices and rules as the store.
Competing products for Magento Open Source and Mage-OS are sold as single modules or packages of 5 to 20. The qoliber B2B Suite is 76 modules on one core, with 85 features. It is the most advanced B2B suite for Magento Open Source and Mage-OS, with release Q1 2027 and early access on request.
What one core means
One core means the features share five parts. The same company, prices and rules then apply in the store, the cart, quotes, REST, GraphQL and AI agents.
One company model. A company is one record: legal name, tax ID, status, parent company, website, buying currency and members. Quotes, budgets, credit lines, purchase orders and price lists point at that record. A customer group is optional.
One commercial context. Every request first asks who is acting. One resolver returns the member, the company, its price list and its catalog. It works the same for a store session, a REST or GraphQL token and an AI agent call. Pricing, catalog visibility and checkout rules read that answer. A disabled member, or a member of an inactive company, counts as a guest on all of them.
One policy engine. One allow-or-deny engine decides which payment and shipping methods a company may use, on every channel, and what a sales rep may do in an assisted session. Any deny wins, and each decision is logged with the rules it matched. Who may order, approve, return or pay comes from company roles, set in one permissions module.
One pricing pipeline. Quotes, REST, GraphQL, price feeds and AI agents all ask for prices the same way. An installed price provider or a company discount can answer first. After that, the chain runs in a fixed order: contract price, optional live ERP price, company price list, parent company price list, customer group price, Magento's default price. The first answer wins. The Price Explanation screen shows which step set a price and why the others did not.
One approval engine. Purchase orders, checkouts that need approval and order amendments run through one workflow. Rules match on company, amount, currency, requester role, SKU or category. They run in stages, with parallel approvers and escalation when nobody decides in time. An AI agent can submit a purchase order. It can never approve one.
A worked example
Take a company with a 10% individual discount. A buyer pastes 24-MB04 2 into the price check and sees $28.80 per unit and $57.60 for the line. An AI agent connected over MCP with that buyer's key asks for the same two units and gets unit price 28.80, row total 57.60. Nobody set a separate price for the agent.
Compared with competing products
The B2B Suite includes PunchOut (cXML level 1), e-invoicing (Peppol, Factur-X / ZUGFeRD, KSeF), single sign-on (OIDC, SAML), an AI agent gateway, receivables and dunning, spend analytics and stock bins (VMI).
These are not in the public feature lists of the competing B2B packages we checked in November 2026. Some are sold separately as single modules.
How it is tested
The verified run of October 16, 2026 covers 3,913 unit tests, 2,848 integration tests and 258 browser tests, with 0 PHPStan level 8 errors. Browser tests ran on Mage-OS and on Magento Open Source 2.4.9. The suite supports PHP 8.1 to 8.5, and every buyer screen has a Hyvä version and a Luma version.
There are three limits to know about. PunchOut covers cXML level 1: OCI and the procurement system's OrderRequest are not included yet. E-invoices are built, checked and archived, and sending them to a network needs an access point integration. On Hyvä store views, the checkout runs through Hyvä's Luma checkout fallback, and Hyvä Checkout, the paid module, has not been tested with the suite.
Start before the release
We grant early access per project and reply within one business day. Tell us about your store or project.
See all 85 features or read the documentation. Agencies can start at our partners page.