ERP for B2B wholesale: what matters for pricing, inventory and master data

The ERP system that carries a central item master, complete pricing logic, stock management across several locations including drop shipment, and structured document exchange in the standard – not as customisation. Three system classes do this in different ways. An industry ERP for wholesale brings condition types, rebate settlement and drop shipment as master data; the price is a smaller vendor and partner market. A standard ERP with an industry add-on combines a broad base system with a partner's wholesale logic; the price is two release cycles and dependence on that one partner. A generalist ERP gives the greatest freedom, but requires conditions and drop shipment to be built and maintained in-house. Which class fits is decided by four numbers from your business: items, condition types in use, locations and drop-shipment share.

With real-time stock per location and separate order types for warehouse sales, stock transfers and drop shipment. In a warehouse sale, the order reserves stock at the delivering location. In a stock transfer, the central warehouse supplies the branch, and the stock stays visible as "in transit" rather than disappearing. In drop shipment, the supplier delivers directly to the customer; the ERP creates the purchase order from the sales order, books no stock and tracks the supplier's delivery date. Without this separation, the branch reorders what is already on its way, and the customer gets a date nobody can keep. Planning also has to know which location serves which customer and from what quantity drop shipment is cheaper than stock.

Since 1 January 2025, businesses in Germany must be able to receive and process e-invoices from other businesses. The obligation to issue e-invoices follows in transitional stages until 1 January 2028. A structured format to the European standard EN 16931 is required, such as XRechnung or ZUGFeRD; a PDF sent by email will then no longer count as an e-invoice. For a wholesaler with many customers and suppliers this is not a side issue: the ERP must create structured invoices, read incoming ones and automatically match invoices to purchase orders and goods receipts. Check whether this happens in the standard or through an add-on with its own release cycle – and whether your existing EDI exchange with large trading partners is affected.

As important as the trading partners who require it. Large customers and suppliers exchange orders, despatch advices and invoices electronically, often in the EDIFACT standard with messages such as ORDERS, DESADV and INVOIC. For the ERP this means documents must come in and go out without manual entry, items must be uniquely matched via the GTIN, and deviations – a different quantity, a different price, a partial delivery – must show up as a case to resolve instead of being posted silently. Many wholesalers run EDI through a service provider; then the interface between provider and ERP is what counts. An ERP change is a good moment to count your EDI partners and check what share of documents is still keyed in by hand.

With a central data model and a release process, not with a one-off clean-up. Suppliers deliver item data in different formats – in wholesale often as catalogues in BMEcat or Datanorm format. The ERP must import this data, map it to its own data model and detect changes without overwriting maintained fields. The organisation matters just as much: who may create items, who checks, who releases? At Hagos eG, with 45,000 items and ten branches, a three-stage workflow – local entry, central check, release – reduced the error rate in master data by 73%. That shows the order: first data model and responsibility, then the system that maps both.

Often yes – and in many cases it is the more economical route. A standard ERP with a wholesale add-on is enough if the add-on carries your condition types, drop shipment and multi-warehouse logic in the standard and the partner keeps it up to date with every release of the base system. For a wholesaler with few locations, manageable conditions and a low drop-shipment share it is often the right choice: the broad base system brings finance, available staff and a large ecosystem, the add-on brings the industry logic. In this constellation we would not recommend a specialised industry ERP just because it can do more – the extra depth goes unused but costs money in operation. It is different when rebate models, member conditions or a high drop-shipment share carry the business.

Not automatically. The warehouse functions of many ERP systems are enough for warehouses with fixed bin locations, manageable picking and few orders per hour. A dedicated WMS pays off when the warehouse itself becomes the bottleneck: chaotic storage, route optimisation, wave or zone picking, conveyor technology or high-bay racking, forklift guidance. Then the interface between ERP and WMS becomes the critical point. The ERP holds stock and order, the WMS holds location and movement, and both must know the same quantity at every moment. The question therefore belongs in the ERP selection, not after it. Anyone who asks it only after signing the contract buys either an ERP whose warehouse logic goes unused or a WMS that has to be adapted to the ERP.

The time does not go into comparing systems, but into process analysis and the requirements specification: item and supplier data, condition types, locations, drop shipment, EDI partners. Only once these cases are described can a vendor show in a proof of concept how its system works with your data – and not with its demo data. We plan each stage individually – process analysis, requirements specification, market analysis, selection with proof of concept – and fix its scope before it starts.

The effort depends on the number of processes, locations, condition types and EDI partners, not on company size alone. A wholesaler with one warehouse and list prices has fewer ERP-relevant processes than a purchasing cooperative with ten branches, member conditions and drop shipment. We therefore price each stage separately – process analysis, requirements specification, market analysis, selection with proof of concept – and fix its scope before it starts. You can stop, continue or adjust the scope after each stage. Our fee is independent of the system you choose in the end: we do not sell licences and receive no vendor commission.