In this blog
B2C checkout is a person with a credit card. B2B buying is a committee with a budget, a contract, an approval chain and a procurement system — and platforms that treat it as "B2C with bigger carts" collapse on contact with reality. Adobe Commerce's B2B suite models the real thing natively, and it is the sharpest reason complex sellers choose the platform. Here is the machinery, and the implementation playbook that makes it convert.
Company accounts: the org chart, digitized
The B2B foundation is that the customer is a company, not a person. Commerce models it directly:
- Company accounts with profiles, credit terms and assigned sales reps
- Buyer roles and permissions — who can browse, who can order, who can only requisition
- Hierarchies and teams — divisions and locations under one company umbrella
- Company administration delegated — the client's own admin manages their users, which procurement teams actively want
This structure is what everything else hangs from: pricing, quotes, approvals and reporting all key off the company, matching how your sales team already thinks about the book of business.
Shared catalogs: contract pricing without catalog forks
The pricing backbone. A shared catalog defines, per company (or company tier), which products are visible and at what negotiated prices — implementing contract assortments and pricing without duplicating your catalog per client.
| Need | Shared catalog answer |
|---|---|
| Distributor sees trade pricing | Company assigned to distributor catalog with tier prices |
| Key account has negotiated rates | Account-specific catalog with contract prices |
| Some SKUs are restricted | Excluded from that company’s catalog entirely |
| Public site shows list prices | Default shared catalog for guests/B2C |
Implementation note: shared catalogs reward planning. Model your real pricing tiers first — a catalog per negotiated contract scales; a catalog per whim does not. This is exactly the architecture conversation our implementation team front-loads.
Quotes: digitizing the negotiation
Real B2B revenue closes through negotiation, and Commerce's negotiable quotes bring it in-platform: a buyer builds a cart and submits it as a quote request; the seller responds with adjusted pricing, line comments and expiration; rounds continue until the quote converts to an order — all tracked, all auditable, none of it living in email threads and spreadsheet attachments.
The operational win is as large as the revenue one: quote history becomes data (win rates, discount depth, cycle time) instead of tribal knowledge in reps' inboxes.
Buying tools procurement actually uses
Repeat purchasing is B2B's rhythm, and the suite serves it directly: requisition lists (persistent, multiple, shareable — the reorder templates of real procurement), quick order (SKU or CSV entry for buyers who know exactly what they need), and purchase approvals — rules by amount, role or budget that route oversized orders to approvers before submission, mirroring the client's own governance instead of fighting it. Payment on account with credit limits completes the picture for invoice-based relationships.
None of these are glamorous. All of them are the difference between a portal procurement teams adopt and one they route around back to fax and phone.
Architecture patterns that work
- B2B + B2C on one instance — multi-store serves the D2C storefront and the dealer portal from shared services, with separated pricing, experience and payments; the consolidation play that makes CFOs smile
- ERP as the system of record — inventory, credit and order truth integrate from ERP; Commerce is the experience and capture layer, not a second ledger
- Headless where it helps — GraphQL serves punchout-style integrations and custom buyer UIs without forking the core
- The full-stack view — commerce behavior feeding Analytics and account-level audiences turns the portal into a revenue-intelligence source, not just a channel
The implementation playbook
B2B commerce succeeds or fails on adoption — by your sales team and your customers' procurement teams — more than on features:
- Involve sales from design. The reps who own accounts know how buying actually happens; a portal designed without them is a portal they will undermine
- Migrate pricing truthfully. Contract prices in the portal must match contracts, day one — a single wrong price costs more trust than a month of downtime
- Pilot with friendly accounts. Two or three real customers shape the rollout before the book of business arrives
- Define the quote SLA. A quote request answered in four days trains buyers to call instead; the workflow needs owners and clocks
- Measure adoption as revenue. Portal-routed share of orders, quote cycle time, reorder rates — the numbers that prove the project
The bottom line
If B2B mechanics — companies, contracts, quotes, approvals — are load-bearing in your revenue, Commerce's native suite is the strongest argument in the platform comparison, and the wider feature set rides on the same foundations. Licensing drivers are in the pricing guide. For a B2B readiness assessment — or a rescue of a portal your buyers route around — talk to a consultant; bring your pricing tiers and your quote-to-close process, and we will map them to the machinery above in one working session.
Frequently asked questions
What B2B features does Adobe Commerce have?
Company accounts with buyer roles and hierarchies, shared catalogs with per-company pricing, negotiable quotes, requisition lists, quick order, purchase-order workflows with approval rules, and credit/payment-on-account options.
What is a shared catalog in Adobe Commerce?
A pricing and assortment layer assigned per company: which products a customer sees and at what negotiated prices. It implements contract pricing without duplicating the catalog per client.
How do quotes work in Adobe Commerce B2B?
Buyers submit carts as quote requests; sellers counter with adjusted pricing, comments and expiry; the negotiated quote converts to an order. The full negotiation is tracked in-platform instead of over email.
Can Adobe Commerce handle purchase approvals?
Yes — company admins define approval rules (by amount, role or budget), and orders exceeding thresholds route to approvers before submission, mirroring procurement governance.
Can B2B and B2C run on the same Adobe Commerce instance?
Yes — multi-store architecture commonly serves a D2C storefront and a B2B portal from one instance, sharing catalog and services while separating pricing, experience and payment methods.