Magento B2B: Adobe Commerce wholesale buying
Understand Adobe Commerce B2B company accounts, shared catalogues, quotes and purchase approvals before mapping a wholesale ordering workflow.
- Published
- Last updated
Magento B2B wholesale workflows use Adobe Commerce’s B2B extension for company accounts, agreed catalogue prices and purchasing controls. Magento Open Source needs a separately chosen extension or custom implementation for those company workflows.
Start with the edition and the buyer’s actual ordering process. A trade price alone doesn’t establish who can see a restricted range or who must approve a purchase.
Separate Magento and Adobe Commerce B2B options
Adobe Commerce B2B requires Adobe Commerce plus the installed and enabled B2B extension. Adobe’s installation guide covers cloud infrastructure and on-premises deployments, with an extension version compatible with the deployed Commerce version.
“Magento B2B module” can mean Adobe’s extension or a third-party product. A marketplace listing describes that vendor’s module, so its name doesn’t establish that it supplies Adobe’s full B2B suite.
The routes differ in what you configure:
- Adobe Commerce with its B2B extension supplies company accounts and shared catalogues, alongside negotiable quotes and purchase-order approvals. Each workflow still needs its feature settings and company configuration.
- Magento Open Source has customer groups and quantity-based tier pricing. Adobe’s B2B suite isn’t included in that installation.
- A third-party module adds its documented functions to a compatible edition. For example, Amasty B2B Company Account supports company users and roles, customer-group pricing and an order-approval payment method.
Amasty’s Marketplace listing includes Magento Open Source 2.4 compatibility. Its guide describes additional compatibility packages for Hyvä storefronts and checkout, and a separate Request a Quote integration. That account module’s group pricing and approval method must be assessed separately from Adobe’s Shared Catalog and purchase-order workflow.
Before choosing a module, match its supported release to your exact store version and checkout. Include the required companion packages in the implementation scope.
Model companies and purchasing permissions
An Adobe Commerce company account groups buyers under a company administrator, with roles controlling their access to sales and company information. The administrator can organise teams and users to reflect who reports to whom.
Consider a fictional distributor’s customer, Northside Maintenance. Priya buys supplies for its workshop, while Alex approves purchases above the company’s spending threshold.
Give Priya the permissions needed to build baskets and submit purchases. Give Alex the approval permissions and responsibility defined by the company’s rules. Keep company administration with the person who manages users and purchasing policy.
The role permissions determine access to each resource. A role’s name doesn’t enforce a spending limit by itself. Approval rules decide which purchases require review.
Use Priya’s login for buyer checks. A company administrator has full permissions and can bypass purchase-order approval rules, so that account can hide a restriction that affects ordinary buyers.
Assign shared catalogues and negotiated prices
Shared catalogues control the products and custom prices available to assigned companies. Adobe Commerce B2B has a public shared catalogue for guests and ordinary customers, plus custom catalogues for assigned company members.
For Northside, suppose the distributor sells a restricted industrial cleaner alongside a public cleaning range. Add the cleaner to Northside’s custom catalogue and assign the company to it. A different company’s catalogue must retain its own product selection and prices.
Adobe’s catalogue assignment instructions explain that changing the shared catalogue also changes the customer group for company members. Trace that assignment when a buyer sees the wrong trade price.
Separate these decisions in the setup:
- Product visibility controls whether the buyer can discover the cleaner.
- Purchasing permission governs basket access and completion of the permitted workflow.
- Agreed pricing determines the applicable company price. Tier pricing adds quantity breaks where configured.
In an illustrative price setup, Northside pays $18 per unit before tax, falling to $16 for quantities of 20 or more. A basket of 19 units stays at the lower-quantity price. At 20 units, confirm that the intended tier applies to every qualifying unit.
Adobe documents the quantity-break behaviour. Shared catalogue configuration also controls category permissions when enabled, so older customer-group permission settings cannot be treated as the final authority.
Connect quotes, purchase orders and approvals
A negotiable quote agrees terms between the buyer and seller. Purchase-order approval applies the customer company’s authority to spend.
For a special bulk purchase, Priya can request a quote from the basket if company accounts and B2B Quotes are enabled. The seller reviews the request and sends an offer. Changes to quantities or products return through the documented negotiation process before acceptance.
For routine purchases, configure purchase-order approvals at both website and company level. The company then applies rules to the relevant buyer roles. An illustrative rule could require Alex’s approval when an order total exceeds $1,000, including tax.
A seller’s accepted price and a company’s spending approval answer different questions. Test the negotiated-quote checkout as its own path alongside the ordinary basket path, including the configured approval behaviour.
The standard offline Purchase Order payment method, which records a purchase-order number, also exists in Magento Open Source. Selecting it doesn’t establish Adobe Commerce B2B’s company approval process.
Payment on Account requires the payment method to be enabled and the company credit settings to permit the purchase. The merchant assigns a company credit limit and manages repayments. Approval permission and available credit remain separate controls.
Payment timing also changes the journey. Adobe documents online payment details being entered after approval, while supported offline payments can complete automatically after approval. Match the chosen payment method to its supported approval flow.
Make large and repeat orders practical
Quick Order suits buyers who already know the stock keeping unit (SKU) or product name. Adobe Commerce B2B supports individual entry, multiple SKU entry and a file-based order list when Quick Order is enabled.
For Northside’s next workshop restock, Priya can enter the required SKUs, adjust quantities and choose required product options before completing the basket. The useful test is whether a long order remains understandable when one line has a problem.
Check the buyer’s experience with these distinct cases:
- Enter a valid SKU and a mistyped SKU. The buyer must be able to identify which product needs correction.
- Change a quantity across a tier-price threshold and compare the basket price with the agreed catalogue terms.
- Request more stock than is available. Confirm that the message and checkout follow the store’s stock and backorder settings.
- Add a product with required options. Ensure the buyer can complete those choices before ordering.
A requisition list saves frequently purchased products and stays available after items are added to the basket. Enable it separately, then let signed-in buyers maintain lists for repeat purchasing.
Order history supplies another repeat-order route. Adobe’s My Purchase Orders workflow lets the buyer copy an existing purchase order into the basket and change its contents. The new purchase must follow the applicable checkout and approval process.
Validate the company buyer journey
Validate Adobe Commerce B2B with separate company buyers and an approver, so the results expose account boundaries as well as successful ordering. Use the Northside example as an acceptance scenario, with expected outcomes agreed before launch.
| Scenario | Buyer action | Expected result |
|---|---|---|
| Catalogue isolation | Open Northside’s restricted product as a guest and as another company’s buyer | The restricted range and Northside’s negotiated price remain unavailable to unauthorised visitors |
| Buyer access | Sign in as Priya and open Northside’s assigned range | The authorised products and applicable company prices appear |
| Approval rejection | Submit a purchase above the example threshold and reject it as Alex | The purchase records the rejection and doesn’t become a completed sales order |
| Approved reorder | Copy an earlier purchase into the basket, change the quantity and obtain the required approval | The new purchase follows the configured payment flow and appears in the appropriate account history |
| Stock changes | Reduce available stock while an order awaits approval | Conversion follows stock and backorder settings, with an actionable error when the quantity cannot be supplied |
Keep public answers separate from authorised account answers. Published product specifications and general delivery or returns policies can answer public questions. Contract prices, company credit and another buyer’s orders require the relevant signed-in company context and permissions.
Apply the same boundary to any search or shopping assistant connected to the store. A product being present in a catalogue feed doesn’t authorise disclosure of its company-specific price.
If product discovery needs separate work, use the Magento SEO guide for catalogue search settings. For a wider platform decision, compare the trade-ordering approaches in the B2B ecommerce platforms guide.
Choose the edition and extension route that can complete the buyer’s permitted journey, including rejection and repeat ordering. A working trade-price display is only one part of that journey.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.