Distribution resource planning software for multi-warehouse networks
Distribution resource planning software tells you, week by week, how much of each product every warehouse, branch or shop will need, when it has to be shipped or ordered to get there in time, and what that means for the central warehouse, the trucks and the purchasing budget. It replaces gut feel and reorder points that each location sets for itself with one time-phased plan for the whole network. We build DRP software around your locations, lead times and allocation rules, connect it to your ERP and warehouse system, host it in the EU and hand your company the source code.
- You see the result before it goes live
- Fixed price for the agreed scope, in writing before work starts
- Source code, domain and accounts in your company's name
When reorder points stop working
A single warehouse can live on reorder points: when stock falls below a level, order more. Once there are several locations, each one reordering on its own, the network starts to fight itself. Branches order in bursts, so the central warehouse sees lumpy demand it cannot predict. One branch runs out while another sits on months of the same item. The central warehouse runs out because three branches ordered in the same week. Purchasing buys on the central stock level alone, without seeing what the branches will need next month.
Distribution resource planning, DRP, solves this by planning from the edge of the network inwards. Demand is forecast where customers buy, each location's needs are calculated period by period, and those needs roll up as planned shipments to the location that supplies it, all the way to the factory or the supplier. Every level sees future demand, not just today's orders.
How a DRP plan works
For each item at each location, the plan runs across time buckets, usually weeks. The same lines appear in every DRP record, and planners who have used one recognise them at once:
- Gross requirements. The forecast for the period, or confirmed customer orders where they are higher.
- Scheduled receipts. Shipments already on the way or purchase orders already placed, with their arrival week.
- Projected available balance. Stock expected at the end of each period if nothing new is ordered.
- Net requirements. What is missing when the projected balance would fall below safety stock.
- Planned receipts and planned orders. The quantity that must arrive to cover the need, rounded to your order rules such as pallet or case quantities, and the week it must be shipped or ordered, offset by the lead time.
A made-up example shows the logic. A branch forecasts 40 units a week of one item, holds 100 units today, keeps a safety stock of 30, receives from the central warehouse with a one-week lead time and orders in cases of 50.
| Week | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Gross requirements | 40 | 40 | 40 | 40 |
| Scheduled receipts | 0 | 0 | 0 | 0 |
| Projected available, before new orders | 60 | 20 | -20 | -60 |
| Planned receipts | 0 | 50 | 0 | 50 |
| Projected available, with planned receipts | 60 | 70 | 30 | 40 |
| Planned shipment from central warehouse | 50 | 0 | 50 | 0 |
Without new stock the branch would fall below its safety stock in week 2, so a case must arrive that week, which means it ships in week 1. Week 3 ends exactly at safety stock, and week 4 needs another case, shipped in week 3. The central warehouse now knows, weeks ahead, that this branch will pull 50 units in week 1 and 50 in week 3, and so does every other branch's plan. Planners do not work through these tables by hand; the software does, for every item and location, and shows the planner only the exceptions.
The planned orders of every branch become the gross requirements of the warehouse that supplies it. That roll-up is what makes DRP a network plan. When a forecast changes at one shop, the effect on the regional warehouse, the central warehouse and the purchase order to the supplier is visible the same day.
From requirements to resources: DRP II
The quantities are only half of the plan. Distribution resource planning in its full form, often written DRP II, turns the time-phased quantities into the resources needed to move them: pallet positions in each warehouse, picking and receiving hours, truck loads per route and week, and the value of stock and purchases per period. That is where the plan becomes useful to the warehouse manager, the transport planner and finance, not just purchasing.
- Warehouse space. Projected pallet positions per location, with a warning before a warehouse overflows.
- Transport. Planned transfers grouped into full loads per route, with the option to pull a shipment forward to fill a truck.
- Labour. Receiving and picking hours per week, from the planned volumes and your handling rates.
- Money. Stock value and purchase spend per period, so the plan can be checked against the working capital budget.
What our DRP software includes
- Your network as it is. Central and regional warehouses, branches, shops, vans and drop-ship suppliers, with the supply route and lead time for each item and location.
- Forecasts per location. Built from your own sales history, adjusted for seasons, promotions and new or ending products, with forecast accuracy measured per item.
- Safety stock by service level. Set per item and location from demand variation and lead time, or as fixed days of cover where that is simpler.
- Exception lists, not spreadsheets. Planners see only what needs a decision: shortages, overstocks, late receipts and orders that must be released this week.
- Allocation when stock is short. Fair share by forecast, priority locations or customers, or the lowest stock-out cost, by the rule you choose.
- Transfers and purchasing. Approved planned orders become transfer orders and purchase orders in your ERP, with one approval step.
Ready-made planning suite or custom software?
There are capable ready-made products for supply and distribution planning, such as SAP Integrated Business Planning, Kinaxis, RELEX, Slimstock and Netstock, and DRP features inside ERPs such as Microsoft Dynamics 365 Supply Chain Management and Oracle NetSuite. For a distributor whose ERP one of them supports well, a product is often the faster route, and we will say so in the first reply to your brief.
| Situation | Ready-made suite | Custom software |
|---|---|---|
| Standard network, an ERP the suite supports | Usually the right choice | Rarely worth building |
| A few warehouses, planning in spreadsheets | Often more than you need | The spreadsheet's logic, made reliable |
| Unusual rules: shelf life, batches, regional ranges | Configured where possible | Built in as they are |
| Older or home-made ERP | Integration project of its own | Read through whatever it exposes |
| Ownership of data and code | Licensed per user or site | In your company's own account |
Connected to the systems you already have
DRP lives on data from other systems: stock and open orders from the ERP, in-transit quantities from the warehouse or transport system, sales history from the ERP, the online store and the point of sale. We read them through each system's interface where one exists, or a file export it accepts, on a schedule you choose. Approved orders go back the same way. For the stock records themselves, see inventory management software; for factories that make what they distribute, see production scheduling software, material resource planning software and ERP for manufacturing.
How we build it
- Map the network. Locations, supply routes, lead times, order rules and how planners decide today, written down with the people who do it.
- Scope and fixed price in writing. Items, locations, integrations and what the first phase leaves out, signed before work starts.
- Back-test on your history. The plan is run on last year's data and compared with what actually happened: stock-outs, overstocks and stock value.
- Parallel planning. For a few cycles planners order the usual way and check the DRP proposals beside it, and parameters are tuned.
- Go live and measure. Service level, stock value and planners' hours are compared with the numbers recorded at the start.
You own it
As a standard term, the source code sits in a repository in your company's own account, and the database and hosting are in your company's name, running in an EU data region. You can keep us for maintenance, run it yourself or hand it to another team. For the wider system, see ERP for small business and data analytics consulting. See prices.
Questions we get
What is the difference between DRP and MRP?
MRP plans the materials needed to make products, working down a bill of materials. DRP plans the finished goods needed in each warehouse, working up a distribution network from the locations closest to customers towards the central warehouse, the factory or the supplier. Many companies use both: DRP demand at the central warehouse becomes the input for MRP or purchasing.
What does the II in DRP II mean?
Distribution requirements planning, the original DRP, plans quantities. Distribution resource planning, often written DRP II, extends the same time-phased plan to the resources behind it: warehouse space, handling labour, transport capacity and the money tied up in stock.
Do we need a forecast for DRP to work?
Yes, at the locations closest to demand. It does not need to be sophisticated to start: a moving average of past sales per item and location, adjusted for known promotions and seasons, is often enough for the first phase. Forecast accuracy is measured from day one and improved where it matters.
Can it work with our current ERP and warehouse system?
That is the normal case. Stock, open orders, in-transit quantities and lead times are read from the ERP and warehouse system, and approved transfer and purchase orders are written back. Nothing is retyped.
What happens when there is not enough stock for every warehouse?
The plan shows the shortage early and applies your allocation rule, such as fair share by forecast, protecting key customers first or filling the locations with the highest stock-out cost. A planner approves the allocation before transfers are released.
Who owns the software?
Your company. The source code is in a repository in your own account, and the database and hosting are in your company's name, in an EU data region.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.