A customer contacts their account manager not for advice, but to confirm an agreed price, discount or stock position. When that happens every day, ecommerce has not reduced the workload; it has simply added another channel. A well-designed B2B ecommerce platform with customer-specific pricing lets signed-in buyers see the terms agreed for their account and place an accurate order without assistance.
This is more than one blanket discount for registered users. Trade prices can depend on contracts, volume, location, season and account history. The platform must represent those rules without turning every exception into a manual task.
Why a standard price list is not enough
The same product may have different terms for a national account, independent installer, retail chain and occasional trade buyer. Add volume breaks, credit, approved ranges and timed agreements, and a generic wholesale price quickly stops being credible.
If the portal is wrong, sales becomes the integration layer: checking ERP terms, sending quotations and correcting emailed orders. The larger cost is loss of trust. A B2B channel succeeds when price, availability and payment terms are as dependable as the account manager’s answer.
How should customer-specific pricing work?
First establish where each price is created. The ERP may remain the system of record, with Magento storing synchronised, indexed prices or carrying out a time-limited live validation. The right approach depends on how often prices change, the volume of data, response times and the commercial impact of showing an outdated value.
Magento Open Source provides group prices, tier prices, special prices and price rules. Adobe Commerce B2B adds company accounts and shared catalogues with company-specific products and prices. Licensing and operating cost should be compared with maintained extensions or a focused bespoke module.
Separate contract pricing from promotions. A contract is a trading term; a promotion is a temporary marketing action. Define precedence explicitly or the system may stack discounts beyond the intended margin.
Practical example: national contract and volume break
A facilities-management company pays £24.60 net for a filter cartridge under a national contract. Orders of 200 or more qualify for £22.90, but only when delivered to approved depots. A public 15% promotion must not be applied on top of the contract price. Signed-in buyers see their applicable net price and VAT, while unauthorised locations fall back to the normal company catalogue.
Practical example: price confirmed at basket
A metals distributor updates prices every hour from the ERP. Category pages use the last validated account price for speed; the basket requests a final quote because commodity prices can move quickly. If the ERP times out, the system keeps the basket, explains that confirmation is pending and routes the order for review rather than substituting a public price.
Match catalogue visibility to the relationship
Price alone is insufficient if every account sees products it cannot buy. Technical and industrial sellers may restrict ranges by accreditation, contract, market or compatibility. Availability should reflect the warehouse and delivery promise relevant to the account, not a global stock number that cannot be fulfilled.
After sign-in, the buyer may also need pack sizes, minimum order quantities, quick order by SKU, CSV upload, saved lists, previous-order reordering, documents and shared company baskets. Multiple buyers may have roles and approval limits.
UK price and tax design
Trade portals commonly lead with prices excluding VAT, but must make the basis clear and produce correct VAT invoices. Decide whether the interface shows net, VAT and gross totals at line and basket level, and make GBP rounding consistent with the ERP.
If the same platform serves consumers, the B2C experience must normally present the total price including mandatory taxes and charges. Current CMA price-transparency guidance is relevant to product cards, product pages and checkout. Do not let a trade-oriented net-price design leak into consumer journeys.
ERP integration: value and risk
B2B integration commonly exchanges accounts, price lists, products, stock, orders, invoices and payment status. Not every field needs real-time synchronisation. Product content may be batched; a final price, credit decision or available-to-promise calculation may need fresher data.
Design failure behaviour before launch. If the ERP is unavailable, can the customer order using a time-stamped price? Does the order enter review? Who is alerted? Use idempotent messages and reconciliation so retries cannot duplicate valuable orders.
Performance still matters to trade buyers
B2B users often know what they want. Fast search, filters, basket updates and reordering directly affect task completion. Avoid one price-service call per product and test realistic logged-in category pages and 100-line baskets.
Hyvä for Magento 2 can provide a leaner frontend, but extension and checkout compatibility must be audited. Backend pricing design, cache segmentation and integration response times remain just as important.
What must change in the organisation?
Clean price lists, consistent SKUs and clear data ownership are prerequisites. If commercial terms live in several spreadsheets, technology cannot create a reliable source of truth by itself. Map how the ERP, finance, warehouse, sales and ecommerce teams create and approve data. Our delivery process starts with this discovery work before scope and implementation are agreed.
Sales does not disappear. It gains time for negotiation, account development and complex purchases. The platform should remove status enquiries and repeat order entry, not remove human expertise where it adds value.
Start with a controlled scope
Map the actual sales process and identify the group of customers most likely to benefit from self-service. A first release may cover sign-in, correct prices, catalogue access, quick order and ERP order submission. Later stages can add credit, approvals, quotations and advanced catalogue personalisation. When the scope is clear, it can form part of a controlled Magento 2 store development project rather than an open-ended list of features.
Pilot with accounts representing simple group pricing, individual product terms, volume breaks and multiple branches. Reconcile displayed prices and ERP orders, including expiry, cancellation and credit notes.
A B2B platform creates value when a buyer trusts the price on screen as much as the quote from their account manager. That confidence comes from disciplined commercial rules, data ownership and failure handling — not from the catalogue alone.
