A B2B platform does far more than put a product catalogue online. It should streamline the sales process: let customers place orders themselves, apply each account’s agreed pricing and terms, and cut down on manual admin for the sales team. A Magento 2 B2B implementation should therefore begin with the bottlenecks in the current sales process, not with a theme or a shopping list of extensions.
For a wholesaler, manufacturer or distributor, the value should be visible in day-to-day operations. How many emailed orders have to be keyed into the ERP by hand? How long do customers wait for stock or price confirmation? How many regular buyers struggle to find the right variant, upload a replenishment order or download an invoice? Magento can solve these problems, but only when the technology reflects how the business actually sells.
What makes a Magento 2 B2B implementation successful?
The most common mistake is to treat the project as a standard consumer shop with a sign-in screen. B2B buying has different rules. One company may have several buyers, multiple delivery locations, an agreed price list, an account credit limit, a named account manager and an internal approval chain. Buyers may order hundreds of lines at once rather than make a one-off impulse purchase.
Adobe Commerce B2B supports company accounts, buyer roles, shared catalogues, quick order, requisition lists, negotiable quotes, purchase orders and payment on account. Some of those capabilities are only available with the paid Adobe Commerce B2B package, rather than Magento Open Source, so the licensing and build decision must be made against real requirements. Open Source can still support a tailored B2B model, but features such as company structures and approval workflows may need carefully selected extensions or custom development.
Not every historical exception should be rebuilt on day one. During discovery, I separate rules that create genuine commercial advantage from workarounds caused by missing automation. Account-specific discounts may be essential; asking a salesperson to re-key every order merely to confirm the price usually is not.
Define customers, prices and permissions
In B2B, “the price” can depend on the customer, customer group, order volume, brand, channel, delivery country or a time-limited promotion. The project must also decide whether prices are hidden before sign-in, whether the buyer sees net prices, VAT-inclusive prices or both, how price breaks are presented and who is allowed to submit or approve an order.
For the UK market, VAT treatment needs deliberate design. A trade portal will commonly lead with net prices, but invoices must carry the correct VAT information and the buyer should never be left uncertain about the amount payable. Mixed B2B and B2C sites need even clearer separation because consumer-facing price communications normally need to include unavoidable taxes and charges. HMRC’s VAT guidance should be reflected in pricing, invoice and ERP acceptance tests.
Edge cases reveal the true scope. What happens when an account exceeds its credit limit? Can it order a line that is only partly available? Can an account manager place an order on the customer’s behalf? Can a head office and its branches buy under a shared agreement but use separate delivery addresses and cost centres?
Three practical B2B scenarios
Electrical wholesaler: an installer signs in and sees a contract catalogue containing approved cable, switchgear and accessories. Entering 20 product codes into Quick Order produces the correct pack multiples and branch-specific stock. A £12,000 basket exceeds the buyer’s £10,000 approval threshold, so it routes to a procurement manager instead of being sent straight to fulfilment.
Industrial parts distributor: a customer buys a bearing at £38.40 under a twelve-month agreement, while the public list price is £46.00. At 50 units, the agreed volume price becomes £35.90. If the ERP price service is unavailable, checkout does not silently fall back to the public price: it either uses a time-stamped cached contract price within an agreed tolerance or places the order into review.
Multi-site hospitality group: head office owns the trading account and credit terms, but each hotel has its own buyers, delivery address and cost centre. Local managers can create orders; spend above £2,500 requires regional approval. Consolidated invoices and account statements remain visible to finance without exposing one site’s operational permissions to another.
ERP integration is the centre of the process
Magento is often not the system of record for stock, negotiated prices or debt exposure. That role usually belongs to an ERP, sometimes alongside a WMS, PIM and CRM. The platform must receive the right data, present it at the right moment and pass orders back without manual intervention.
Assign ownership for each data domain. The ERP may own customer accounts, SKUs, stock, price lists, credit and sales documents. Magento owns the online buying journey, basket and account experience. A PIM may own descriptions, assets and marketing attributes. When ownership is ambiguous, duplicate records and “which price is correct?” disputes follow.
Not every exchange needs to be real time. Fast-moving availability and the final basket price may justify a live check; long-form product copy may be synchronised in batches. Adobe provides REST APIs as well as asynchronous and bulk endpoints, but the correct pattern depends on volume, latency and the consequence of stale data.
Every integration needs monitoring, retry rules and idempotency. An order that fails to reach the ERP cannot disappear into a queue. The team must know who receives the alert, whether the message can be replayed safely and how duplicate order creation is prevented.
A B2B catalogue should shorten the route to an order
A buyer who already knows a manufacturer part number does not want to browse several levels of navigation. They need dependable search, filters based on technical attributes, clear variants, relevant availability and fast ordering by SKU. Regular buyers also benefit from requisition lists, previous-order reordering, saved baskets and CSV upload.
Design around the person doing the work. An installer may order from a mobile between jobs; a procurement team may prepare a 300-line order on a desktop and need purchase-order references and cost centres. Analytics, customer interviews and observation of the sales desk are more useful here than copying a generic B2C pattern.
A modern Hyvä frontend can make Magento materially faster and simpler to maintain, but compatibility must be audited. Luma-based extensions generally require a Hyvä compatibility module, as the Hyvä documentation explains. A fast storefront with the wrong pricing logic still loses trust.
An MVP must still be production-ready
A sensible B2B MVP is the first production release that completely supports the most valuable revenue stream. It is secure, observable and complete for the selected scenarios. It does not mean provisional integration, missing tests or postponing critical controls.
I split requirements into three groups: essential for launch, important for near-term growth and ideas whose value still needs evidence. Launch scope commonly includes sign-in, correct account pricing, effective search, order placement, ERP integration and essential documents. A product configurator, advanced quotation portal or service area can follow later, provided they are not essential to day-to-day sales.
Test the commercial process, not merely the interface
Acceptance testing should cover real accounts and awkward cases: an agreed price list, partial availability, payment on account, an approval threshold, a changed delivery address, an amended order and a failed ERP hand-off. Include sales, customer service, finance and warehouse staff; they will spot exceptions that wireframes miss.
Before launch, test security, backups, monitoring and storefront performance as well. Our guide to Core Web Vitals for ecommerce explains how to combine field data with laboratory testing when setting performance priorities.
For UK operations, test pounds sterling rounding, VAT codes, credit notes, postcode and address behaviour, local delivery services, payment providers and any Northern Ireland flows separately where the tax or fulfilment model differs. If consumer and trade sales share one estate, test that B2C cancellation, delivery and total-price information remains clear without imposing irrelevant consumer messaging on negotiated business contracts.
Launch is the beginning of improvement
After go-live, measure more than online revenue. Track the share of orders placed through self-service, order-processing time, price and availability enquiries, account activation, integration failures and repeat purchases. Pair these operational measures with a structured programme of ecommerce conversion rate optimisation to see whether the platform is genuinely making life easier for customers and staff.
Development should then follow a controlled rhythm: evidence, priority, implementation, testing and measurement. The best time to put B2B sales on a sound footing is while growth is still manageable, not after the sales team has become a human bridge between disconnected systems. Get the foundations right and the platform can grow with the trading model instead of preserving every workaround indefinitely.
