ERP for wholesale and distribution: what your system must handle

A wholesaler lives on the gap between what it pays and what it charges. That gap is thin, it moves daily, and it is eroded by small things: a supplier price rise that never reaches the price list, a rebate nobody accrued, stock that sits in the wrong depot. A wholesale distribution ERP exists to make those leaks visible and to close them.

This page walks through the main needs of a distributor, what the ERP must cover for each, which of the ERP products we cover suit it and under what conditions, and the questions to put to an integrator. If you are still at the stage of defining what an ERP is, start with our guide to what an ERP is.

What makes ERP for wholesale and distribution different

An ERP for wholesalers is not a manufacturing system with the production module switched off. Three things set it apart:

• Volume of transactions. Many orders, many lines, many small price decisions. Speed of entry and automation matter more than depth of planning.
• Margin on every line. The system must know the true landed cost, not only the purchase price, and show the margin before the order is confirmed.
• Stock as the main asset. Availability, location, age and reservation drive customer service and cash.

If you also assemble, kit or lightly process goods, check whether you need part of a manufacturing ERP as well. If you sell online, the e-commerce ERP page covers the web-shop side.

Purchasing and supplier management

Buying well is half of wholesale. The ERP should cover the whole chain from need to payment.

What the ERP must cover

• Replenishment suggestions based on sales history, minimum levels and lead times, not only on a fixed reorder point.
• Purchase orders, confirmations and expected delivery dates, with alerts on late supplier deliveries.
• Supplier price lists with validity dates, and automatic update of cost when a new list is loaded.
• Goods receipt matched to the purchase order and to the supplier invoice, so that you pay only for what arrived.
• Landed cost: freight, duty and other charges spread across the received goods, so the margin is real.
• Purchases in foreign currencies, with exchange differences handled in the accounts.

Since Brexit, imports and exports add customs paperwork and duty to the cost of a line. Ask how the ERP records them and whether they feed the landed cost.

Which ERP suits this need

Questions for the integrator

• How does the system propose purchase quantities, and can we tune the rules by product family?
• How is landed cost calculated, and can it be revised after the invoice arrives?
• What happens when the supplier invoice does not match the receipt?

Price lists, discounts and rebates

This is where wholesale ERP projects succeed or fail. Real price structures are rarely tidy: list prices, customer-specific prices, quantity breaks, promotions, contract prices and end-of-year rebates often coexist.

What the ERP must cover

• Several price lists, by customer, group or channel, with start and end dates.
• Quantity breaks and mixed-basket discounts.
• A clear rule for which price wins when several apply, and a record of why a price was applied.
• Rebates and bonuses accrued automatically through the year, then settled by credit note.
• Margin shown on the quote and the order, with an approval step below a threshold.

Which ERP suits this need

Every product we cover can hold price lists and discounts. The difference is in how easily your actual rules can be expressed without custom code. Odoo is often chosen when pricing rules are unusual and need adapting. Microsoft Dynamics 365 Business Central covers standard price and discount structures well, and extensions can complete them. Oracle NetSuite handles complex price levels across entities when the organisation is large enough to need them.

Questions for the integrator

• Can you load and test our ten most complicated customer price cases before we sign?
• How are rebates accrued and reported in the accounts during the year?
• Who can override a price, and is the override traceable?

Multi-warehouse stock and traceability

Most distributors hold stock in more than one place: a main depot, regional sites, a trade counter, vans, goods in transit, stock held at a third party. The ERP must treat these as one picture with several locations.

What the ERP must cover

• Stock by warehouse and by location, with transfers between sites and visibility of goods in transit.
• Reservation and available-to-promise, so that sales staff do not sell stock that is already allocated.
• Units of measure and pack sizes: buy by the pallet, sell by the case or the single unit.
• Batch or serial numbers and expiry dates where the goods require them, with traceability in both directions.
• Stock valuation methods agreed with your accountant, and reliable stock counts, including cycle counting.
• Handling of returns, damaged goods and supplier credits.

Which ERP suits this need

For fresh or date-sensitive goods, the page on food and beverage ERP goes further on batches and shelf life.

Questions for the integrator

• Can we see a demonstration with our own units of measure, including pallet-to-unit conversions?
• How does the system prevent the same stock being promised twice?
• How are stock counts performed while the warehouse keeps trading?

Warehouse operations and logistics

Once an order is confirmed, it has to be picked, packed and delivered. A distributor can have a basic stockroom or a fully organised warehouse, and the ERP requirement differs accordingly.

What the ERP must cover

• Pick lists sorted by location, with handheld scanners and standard barcodes for picking and receiving.
• Wave or batch picking when order volume is high.
• Packing, despatch notes, labels and integration with carriers and pallet networks.
• Delivery routes and slots for your own vehicles, where you deliver directly.
• Back orders and partial deliveries managed without losing the customer's priority.

If transport is a core part of your business model, see also logistics ERP. Many wholesalers instead pair a business-focused ERP with a dedicated warehouse system; ask the integrator which approach is realistic for your size.

Questions for the integrator

• Is scanning native, or does it rely on a third-party app, and who supports it?
• Which carriers can be connected, and what do labels and tracking look like?
• What is the fallback when the network drops in the warehouse?

EDI and trading with large customers

Supplying retailers, buying groups or marketplaces often means exchanging orders, despatch advice and invoices in a prescribed electronic format. Failing to do so can cost you the account.

What the ERP must cover

• Receiving customer orders electronically and turning them into sales orders without re-keying.
• Sending despatch advice and invoices in the format each partner requires.
• Checking incoming orders against your price list and flagging differences.
• A log of every message, with clear errors when a message is rejected.

The UK is also moving towards structured electronic invoicing, and public and private buyers are asking for it. Our guide to e-invoicing in your ERP explains what to prepare.

Most ERP products reach EDI through a connector or a specialist provider rather than natively. That is normal. What matters is who owns the connector, who pays for each new trading partner, and who answers when a message fails.

Questions for the integrator

• Which EDI formats do you already deliver for similar distributors?
• Is the connector part of the ERP or a separate service, and how is it priced and supported?
• How long does it take to onboard a new trading partner, and who does the testing?

Margin analysis and finance

A distributor needs more than a profit and loss at month end. It needs margin by customer, product, supplier, salesperson and branch, available while decisions are still open.

What the ERP must cover

• Margin per line, per order, per customer and per product family, based on true landed cost.
• Credit control: credit limits, overdue alerts and the ability to hold an order.
• VAT handled correctly for domestic and international sales, and compliance with Making Tax Digital requirements.
• Cash forecasts that combine supplier payments, customer receipts and stock investment.
• Consolidation across companies and currencies when you operate more than one entity.

Sage is already familiar to many British finance teams, which can ease adoption, and SAP Business One offers integrated finance and reporting for growing businesses. Where the group has several legal entities and currencies, NetSuite is often considered.

Questions for the integrator

• Can we see margin by customer reported from the live system, not from an export?
• How is the VAT return prepared, and how does the ERP support Making Tax Digital?
• What does month-end closing look like, and which steps are automated?

Choosing between the ERP options

No ERP wins on every criterion. Use this summary as a starting point for a shortlist, not as a verdict.

For head-to-head views, see Odoo vs Business Central and Odoo vs Sage. If your business is small, our page on ERP for small business will help you size the project.

How to start without wasting months

1. Write down your real cases. Price structures, units of measure, special deliveries, rebates. These are what the ERP must handle, not the brochure.
2. List what you must keep. Connections to your web shop, carriers, EDI partners and accounting.
3. Decide where the project stops. A first phase that covers sales, purchasing, stock and finance is easier to deliver than everything at once.
4. Ask for a demonstration with your data. A scripted demo proves little; your own products and prices prove much more.
5. Check the integrator's distribution references. Experience in your sector shortens the project and reduces surprises.

Our requirements template helps you turn these points into a document, and how to choose an ERP integrator explains how to judge the people who will carry out the work. To understand how the budget builds up without fixed figures, read about ERP cost.

Get matched with a distribution integrator

Our service is free. You describe your business, your software preferences and your constraints, and we introduce you to a certified integrator suited to a wholesale or distribution project. We stay neutral between software publishers, and the integrator, not us, delivers the project. How the matching works is explained step by step.

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.