B2B eCommerce for technical wholesale: what to look out for

An eCommerce platform for technical wholesale has to handle customer-specific pricing and variant-rich assortments natively, and pull that logic from the ERP in real time. So judge a platform on four points: price hierarchy, variant management, ERP integration and the total cost over several years. The lowest licence fee tells you very little about any of them.

Technical wholesale places demands that an ordinary webshop cannot meet: complex pricing, vast variant-rich assortments, customers ordering from their own procurement system, and organisations with multiple buyers and approval steps. This article works through the questions that together determine whether a platform was genuinely built for technical wholesale, and how to assess your options side by side.

What makes B2B eCommerce for technical wholesale different from an ordinary webshop?

B2B eCommerce for technical wholesale differs from a consumer webshop because every customer has their own prices and their own assortment. Where a consumer sees one fixed price, a business customer sees the price agreed in their contract, with the volume tier that applies to them. Pricing and assortment logic is therefore the heart of the platform.

A technical wholesaler rarely sells the same item at the same price to everyone. One customer has an annual contract with fixed rates; another buys at the day price with a discount above a certain quantity. The assortment is large and layered: a single item exists in dozens of variants by size, material, colour and packaging unit. On top of that, your customer is an organisation with multiple buyers and approval steps, and your largest accounts want to order from their own procurement system. A platform that was not built for this forces you into endless manual work, or into customisation you will be maintaining for years.

Why do technical wholesalers outgrow Shopify and Magento?

Technical wholesalers outgrow Shopify and Magento because those platforms were designed for consumer sales with one price per product. Customer-specific pricing and large variant-rich assortments can only be bolted on through plug-ins or customisation, and that construction becomes fragile and expensive as soon as the assortment and the number of customer agreements grow.

In the beginning it often works well enough. A few hundred items and a handful of customers with a discount can be handled with some configuration and an extension. The problem starts at scale. Once you have thousands or tens of thousands of SKUs, with prices that differ per customer and have to come from your ERP as well, the webshop becomes a second administration that you must keep permanently in sync with your source. Every price change and every new customer agreement then has to be correct in two places. That is the moment companies realise they have outgrown the platform.

What pricing logic does a B2B platform need to handle?

A B2B platform has to handle at least four types of prices at the same time:

• list prices
• customer-specific contract prices
• volume tier prices based on quantity purchased
• project prices for temporary agreements

Crucially, the platform has to apply these in the right order, so that a logged-in customer always sees the price that will appear on their invoice.

That price hierarchy is exactly where things go wrong if you record prices in the webshop itself. The correct price for a customer is often the outcome of several rules that override one another: a tier that only applies within a contract, or a net price that rules out every discount. That logic already lives in your ERP. Record it in the webshop as well and you maintain it twice, with the risk that the displayed price differs from the invoiced price. That last point destroys your customer's trust immediately.

The better approach is for the webshop to pull the price from the ERP in real time, at the moment the customer looks at it. Then there is a single source of truth, and the webshop price matches the administration by definition.

How important is the ERP integration?

ERP integration is the most important technical criterion in your platform choice, because pricing, stock, customer data and assortment all live in the ERP. A platform that pulls this data natively and in real time from the ERP saves you a second administration and prevents the webshop and back office from drifting apart.

There is a difference between a platform with a connector and a platform built on integration. With the first you build or buy a connector that pushes data back and forth, and you keep maintaining it with every change on either side. With the second, integration is the foundation: the platform assumes the ERP is leading and shows what is held there. For a technical wholesaler, where pricing and stock logic are complex, that difference determines your long-term maintenance burden.

CloudSuite is built on proven integrations with every serious ERP system on the market, with the price hierarchy and the assortment coming straight from the ERP. On platforms without that foundation, you end up configuring and maintaining the same logic yourself.

How do you connect to the procurement systems of large customers?

Large customers prefer to order from their own procurement system, via punchout (OCI or cXML) or EDI. A B2B platform for technical wholesale has to support those connections, so the customer stays in the system they know and the order still lands correctly in your ERP.

For your largest accounts, the webshop rarely plays a part in the ordering process. Their buyers work in a procurement system such as SAP Ariba or Coupa, and expect to pull your catalogue and prices in there via punchout and send the order back via EDI. A platform that cannot do this shuts your most valuable customers out of the digital route and keeps them on the phone. Treat punchout and EDI as hard requirements as soon as you serve enterprise accounts.

How do you handle large, variant-rich assortments?

Large variant-rich assortments only stay manageable if variants are data-driven, coming from the PIM or ERP, and if search and filtering scale to hundreds of thousands of SKUs without slowing the webshop down. Manual variant management collapses as soon as the assortment grows.

An item in technical wholesale is rarely a single product. It is a family of variants: the same pipe comes in five diameters and three lengths, and that number climbs fast once material and packaging unit are factored in. If every variant is a separate product that somebody creates and maintains by hand, the catalogue becomes unmanageable and full of errors. Data-driven variants, with the structure coming from your source system, keep it consistent and scalable.

How do you ensure good product data and classification?

Good product data means complete, structured item information in line with the industry standards ETIM and 2BA, with correct specifications, units, images and documentation. Without that data quality the customer will not find the right item and your filters and search fall apart, however good the rest of the platform is.

In technical wholesale, product data determines whether the webshop is usable at all. Customers search on item number and on technical properties. At the item they expect the data sheet and the certificates, with the correct packaging unit alongside. The sector uses standards such as ETIM for product classification and, in the installation trade, 2BA for item and pricing data. A platform that supports these classifications and pulls the data from your PIM keeps the catalogue consistent and findable. Poor or incomplete data is the most underestimated reason a B2B webshop ends up going unused.

How do you make online ordering easy for repeat customers?

Repeat customers will only order online if it is faster than calling. That calls for features that build the standing order in seconds:

• saved order lists
• quick ordering by item number
• repeating earlier orders
• CSV upload of an order file
• favourites

Most revenue in technical wholesale comes from repeat orders of the same items. If the customer has to rebuild that order by hand every time, they will keep calling. Ordering convenience is therefore the main reason a customer switches to online. Quick entry by item number and saved order lists take the friction out. Combined with a search function that scales to large catalogues, this decides whether the webshop is used daily or gathers dust.

How do you support collection and click and collect for tradespeople?

Tradespeople prefer to collect materials from the counter the same day. A B2B platform for technical wholesale therefore has to show live counter stock per branch and allow online reservation with collection, including the moment the item will be ready. Collection convenience decides whether the tradesperson orders online or simply drives over.

A large share of a technical wholesaler's customers are tradespeople on site or on the road who need the material within the hour. For them, delivery is often too slow. They want to see at the nearest branch whether the item is in stock and have it set aside online, so all they have to do at the counter is sign. That calls for real-time stock per branch. One national stock figure is no help to the tradesperson standing at the counter. It also calls for a collection process that connects the counter and the webshop. A platform that only knows delivery misses precisely the way the tradesperson prefers to buy.

How do you handle multiple buyers, budgets and approvals?

At a business customer, ordering is rarely done by one person. The platform has to handle multiple buyers per customer, with their own roles, order budgets, cost centres and approval flows, so a junior buyer can order within their limit while larger orders go past an approver.

Your customers employ several buyers, often with different authorities and budgets, and sometimes with an approval step above a certain amount. A consumer platform only knows the idea of one account with one user and runs aground straight away. A B2B platform for technical wholesale models the customer organisation as it actually works, with roles and authorisations. That is what larger accounts need before they move their purchasing to your webshop.

How do you get existing customers to order online?

Existing customers switch to ordering online when the webshop is demonstrably easier than phone and email, and when you actively guide them through the change. The biggest accelerator is the generational shift: younger buyers expect a digital experience and will choose it of their own accord, provided the platform delivers on it.

The hardest question is often customer behaviour. Someone who has ordered through the sales desk for years will not switch unprompted. Adoption requires a webshop that shows their own prices and assortment, and active guidance from sales and the internal sales desk. At the same time the generational shift works in your favour: a new generation of buyers expects to arrange online what used to go by phone. A platform that meets that expectation lets adoption grow along with the shift.

Is your platform ready for AI and agentic commerce?

Agentic commerce means your customers will soon have their own AI agents doing the buying, reading your catalogue and live prices directly. A future-proof B2B platform makes that data available in structured form, for example through an MCP layer, so your customer's agent can order just as well as a human.

The next shift in B2B purchasing is the buyer's AI agent placing the order. That only works if your platform offers prices and stock in a machine-readable and reliable way. The same properties that make a platform good for people, customer-specific prices in real time from the ERP and clean structured product data, also make it ready for agents. Whoever sets this up now will be the supplier that the customer's agent can find and deal with.

Which platforms are out there and where do they differ?

The serious platforms for technical wholesale differ mainly on four points: do they handle the price hierarchy natively, how strong are volume tiers and variants, is the architecture composable, and what is the total cost of ownership over several years. The comparison below sets out the main options side by side.

The main divide is between platforms that pull pricing and assortment logic from the ERP and platforms where you configure and maintain that logic in the webshop layer. For a technical wholesaler with many customer-specific agreements, that choice determines the bulk of the maintenance burden and therefore of the long-term cost.

What does a B2B platform really cost?

The real cost of a B2B platform sits in the total cost of ownership over three to five years: implementation, customisation, maintaining connections, and the time your team spends on manual administration. The licence is usually the smallest part of it. A platform with a low entry price can work out more expensive once you have to build and maintain the logic it lacks.

So work with the total cost of ownership over five years, of which the licence fee is only one component. Add up what it costs to get customer-specific prices and variants working and keep them working, and what maintaining the ERP connection requires each year. Add the internal sales time that disappears into manual corrections because the webshop and the ERP have drifted apart. On cheap platforms the cost simply moves from licence to customisation and maintenance. The heart of the cost story is what the platform costs year after year to do what technical wholesale needs.

What should you check before you choose?

Before you choose a platform, check five points:

1. can the platform handle your price hierarchy natively
2. are variants and product data managed in a data-driven way
3. is ERP integration the foundation or a separately maintained connector
4. does it support the way your customers order, from ordering convenience and multiple buyers through to punchout and EDI
5. are the total costs over several years predictable

Together these questions predict whether you will outgrow the platform again within a few years.

In practice that means: have a vendor demonstrate how a logged-in customer sees their own contract price and volume tier, and where that price comes from. Ask how variants and product data are built up and whether that is manual or data-driven, including classification to ETIM and 2BA. Ask as well how the platform models multiple buyers with their own budgets and approval steps, and whether punchout, EDI and collection with real-time stock per branch are supported. Have them explain what integration with your ERP requires in practice in terms of maintenance, and ask for a cost breakdown over five years including customisation and maintenance. A vendor who answers these questions concretely and with a demo shows you whether the platform was genuinely built for technical wholesale.