B2B commerce sounds like a subcategory of eCommerce. In practice it is a fundamentally different business: different buying decisions, different pricing structures, different relationships between buyer and seller. A B2C store retrofitted for B2B sales rarely solves the problem – it manages it.
This article covers what a B2B online store actually needs in 2026, what Magento covers natively, what still requires custom development, and when Magento is the right platform choice for B2B.
What separates B2B from B2C
The technical requirements in B2B come not from preferences, but from the structure of the business itself:
- Multiple buyers per account. A corporate customer often has a purchaser, an accountant, an approver, and a warehouse manager – all with different permissions under the same account.
- Negotiated pricing. Price A for customer A, price B for customer B – often by volume, by contract, by product category. Not one price for everyone.
- Credit lines instead of immediate payment. B2B buyers often pay on invoice with 30- or 60-day payment terms, not by credit card at checkout.
- Repeat orders with a fixed assortment. The purchasing manager of a wholesale company orders the same items every month – and does not want to start a new product search each time.
- Approval workflows. Some orders need internal sign-off before they reach the supplier.
None of these are nice-to-have features. They are the baseline that determines whether a B2B buyer actually uses the store or just calls their account manager instead.
What the Adobe Commerce B2B module covers
Magento 2 in its Open Source version has no native B2B functionality. B2B features are exclusively part of Adobe Commerce (formerly Magento Commerce) – the licensed version. What the module covers:
- Company Accounts. A corporate customer is managed as its own entity, not as a collection of individual users. Roles and permissions can be set individually within the company structure.
- Shared Catalogs. Different product catalogs and prices for different corporate customers or customer groups. A wholesale customer sees different prices than a retail customer – without needing a separate store.
- Negotiated Quotes. A buyer can submit a price request directly from the store, which the seller processes within the admin interface and sends back.
- Purchase Orders and approval workflows. Orders can be routed internally for approval before reaching the supplier. Limits, roles, and approval tiers are configurable.
- Requisition Lists. Saved order lists for repeat purchases – the purchaser maintains a list of standard items and can add them to the cart in one click.
- Quick Order. Direct SKU entry or CSV upload to place large orders without product browsing.
This is a solid foundation for many B2B scenarios. But it is a foundation, not a finished system for every use case.
What still requires custom development
Almost every B2B merchant running Adobe Commerce needs custom development on top of it. The most common categories:
- ERP integration. The B2B module does not know your inventory levels, customer credit limits, or order statuses – those come from the ERP (SAP, Microsoft Dynamics, SAGE, industry-specific systems). Synchronization in both directions, on a schedule that matches the business, is always custom development.
- Industry-specific pricing logic. Adobe Commerce’s Shared Catalog system is powerful, but it has limits. If prices depend on quantities, on product combinations, on customer revenue in the current year, or on external factors – native configuration runs out.
- Custom approval rules. The standard Purchase Order workflows cover many scenarios. Companies with complex purchasing structures (multiple branches, multi-tier approvals, budget limits per cost center) need custom logic.
- Custom checkout behavior. Mandatory fields, reference numbers, cost centers, delivery addresses with their own approval process – the standard checkout is not built for this.
- Buyer-side reporting. B2B buyers often want to see open invoices, order history, and spend by cost center directly in the portal – not by emailing a support team.
Magento Open Source vs. Adobe Commerce for B2B
A direct question that gets asked more often than it gets answered:
Magento Open Source has no native B2B features. Shared Catalogs, Company Accounts, Purchase Orders, Requisition Lists – none of them are in the Open Source core. There are third-party extensions that add individual functions, but building a coherent B2B system on Open Source means either many extensions with potential compatibility issues, or significant custom development.
Adobe Commerce (Cloud or On-Premise) includes the B2B module as part of the license. License costs are significant – from around $22,000 per year for smaller stores, significantly more for higher revenue. That makes sense when:
- The B2B channel accounts for a meaningful share of revenue
- The business model relies heavily on the native B2B features
- The alternative (custom development on Open Source) would cost as much as the license
For smaller B2B volumes or stores with very specific requirements, Magento Open Source with targeted custom development may be the more economical option. The decision depends on the specific requirements – not the brand name on the license agreement.
What is often missing in practice
After years of B2B implementations, the same gaps keep appearing – regardless of whether it is Adobe Commerce or Open Source:
- Onboarding new corporate customers. The process of creating a new B2B customer, setting a credit limit, assigning the right catalog, and setting up users is still manual in many implementations. An automated onboarding flow saves significant back-office time.
- Visibility for the buyer. Open invoices, order status, delivery timelines – B2B buyers want to see this in self-service, not ask via email. What is not visible in the portal becomes a support request.
- Price transparency on requests. Adobe Commerce’s quote process works, but many buyers want a first price indication before submitting a formal request. How much transparency makes sense depends on the business model – but the absence of any indication raises the barrier.
- Mobile usability. B2B buyers also order on the go, from the warehouse floor, from a trade show. A checkout experience designed for desktop that barely works on mobile costs real orders.
When Magento is the right B2B choice
Magento is a good fit for B2B when several of these conditions apply:
- The catalog is complex: many products, many variants, customer- or group-specific pricing
- There is a mix of B2B and B2C channels to manage on one platform
- Integrations to ERP, PIM, or other back-office systems are central – Magento has the most mature ecosystem here among established platforms
- Business logic is complex enough that a SaaS platform would hit its limits
Magento is less suitable when the B2B channel is small and requirements can be covered by simpler solutions – a wholesale plugin on Shopify or a straightforward order portal. Platform selection should follow complexity, not brand preference.
Conclusion
B2B commerce on Magento works well when implemented correctly – meaning: Adobe Commerce with B2B module as the foundation, supplemented by the custom development the business model actually needs, and integrated with the systems that run the operational business.
What it is not: a project you solve with an extension list from the Marketplace. The gaps between native functionality and what a real B2B process needs are almost always present – and almost always specific to the individual company.
If you are evaluating whether and how Magento fits your B2B channel, we are happy to talk it through. We implement B2B projects on Magento 2 and can assess what makes sense in your specific situation – and what does not.
