Distribution requirements planning across warehouses

Turn each location’s dated shortage into a transfer proposal, with lead time and source availability visible.

Kartik Deshpande··5 min read

Distribution requirements planning calculates when each location needs stock and works backward to find when replenishment must leave its source. A transfer plan should name the SKU, quantity, origin, destination, receipt date, and release date. Review the origin’s balance before treating the planned transfer as supply.

Oracle’s distribution requirements planning documentation describes netting demand against organization-specific supply and using a replenishment structure to assign planned orders. For a network that uses an approved central warehouse, the outbound transfer becomes demand at that warehouse and dated supply at the destination. Represent both sides from one movement so its status can change without adding duplicate stock.

Project the destination’s balance by week

Start with usable stock by SKU and destination. Add open inbound transfers on their expected receipt dates and subtract planned consumption or demand under a documented forecast rule. If confirmed orders already consume the forecast, count each unit of demand once. Keep inspection stock outside the usable balance until the plant releases it.

Set a buffer by location if your service policy requires one. Calculate the net requirement to end the period at that buffer. Report a negative projected balance as a shortage and show the date it first appears. A positive balance below the buffer warrants review, but it does not mean an open customer order is already short.

Align all source extracts to the same cutoff. A destination export from before receiving and an origin export from after shipping can make an in-transit unit disappear from a consolidated count. Use the movement ID, ship status, and receipt status to reconcile it.

Build the lead time from the events the lane controls. A warehouse may take a day to pick, the carrier may move only on certain weekdays, and the destination may need a receiving appointment. A week of average transit cannot tell you whether a transfer released Friday will be usable next Wednesday. Use the release calendar for the route you intend to use.

Offset a warehouse shortage by the lane lead time

Assume a branch starts Week 1 with 70 units. It expects 20 units in Week 2, plans to use 30 units in Week 1 and 55 in Week 2, and wants 25 left after each period. Without a new transfer, Week 1 ends at 40 and Week 2 at five. The Week 2 requirement is twenty units to reach the 25-unit buffer.

The normal lane takes one week from release to usable receipt. Propose a Week 1 release from the central warehouse for a Week 2 receipt. If the approved pack contains 12 units, propose two packs, or 24 units. With the proposed transfer, the branch ends Week 2 at 29, four above the buffer. Keep pack rounding visible as a decision (it affects the source warehouse too).

Suppose the source has only 18 units it can transfer after protecting existing demand. It can supply one 12-unit pack under the stated packing rule, which leaves the branch at 17. Flag the eight-unit shortfall against the branch’s target. Check an alternate lane or an approved pack exception before allocating more.

Branch projectionWeek 1Week 2
Opening or carryover7040
Existing receipts020
Expected demand3055
Ending balance without new transfer405
Ending balance with two packs4029
A requirement travels through the transfer lane
Branch
Needs 20 units in Week 2
Lane
One week and 12-unit packs
Central warehouse
Check 24 units before releasing
The proposal only becomes open supply after a release is recorded against it.

Compare receipts and transfers at one branch

Bring a stock snapshot and movement export into Permute to inspect the location and transfer keys.

Keep the proposed transfer distinct from an open movement

Name one system that owns the released transfer. When the proposal becomes a warehouse order, replace the proposal’s expected supply with the actual transfer record. Retain their relationship so the next run does not count both the proposal and the open order.

Test a split shipment and a canceled transfer. If the origin ships only one pack, keep the unshipped balance and the expected receipt dates separate. If the remaining pack is canceled, remove only that planned receipt and recalculate the destination’s exposure. Check that the source balance is released only for the canceled quantity.

Compare the transfer plan with available to promise before quoting a customer. A planned receipt may be sufficient for a planner’s projected balance and still lack the confirmation required for a delivery promise.

Use the safety stock formula to set buffers separately from the lane lead time.

Review the dependency when two branches request stock from the same origin. Assign a policy for which demand takes priority when the origin cannot supply both. Hold the unfilled requirements open with their original need dates, rather than showing stock at both branches from the same planned release.

Test one item that has a second approved source. Check the alternate source’s inventory, lane calendar, and pack size before using it. A ten-unit pack may cover the branch’s shortage while leaving the main source free to supply a higher-priority branch. Save the override reason and its expiry so the next planning run can tell whether the new source applies to one transfer or an ongoing route.

Compare projected and received quantities at the same location after the transfer closes. If eight units are missing, check whether they were never shipped, arrived damaged, or remain unmatched to the receiving movement. Leave the original projection visible until the planner can distinguish timing from a real quantity difference.

How Permute connects the evidence

Permute is the context layer we sell between business data and the AI tools people already use. Connect supported inventory, demand, and transfer sources and reconcile item, location, and movement identifiers across them.

Define projected stock and treatment of in-transit units once. A distribution planner can then ask which movement supports a location’s plan and inspect the source records and cutoff dates behind that answer.

What stays in the source systems

Keep planning decisions and releases in your ERP or warehouse system. Permute reads connected data for review and can help reconcile the inputs. It does not generate a forecast or write the planned transfer back.

Trace the planned quantity to its source

Distribution requirements planning starts with a dated shortage or buffer gap at a particular location. Convert it to a proposed transfer using the lane’s receipt time and pack rules, then verify the origin can spare the units. Once the movement is released, use its actual record in the next plan. The branch and origin can then reconcile the same units without counting the transfer twice.

Review a proposed transfer against source capacity

Bring a branch projection and the movements claiming stock at its supplying warehouse.

Questions about distribution planning

Does DRP replace material requirements planning?

DRP plans replenishment between locations. Material requirements planning can use demand to plan components and production. If a central plant supplies the network, a distribution requirement can become an input to that production plan.

Can the destination use a transfer before it arrives?

It can project the transfer as dated supply under its policy. Keep it outside physical usable stock until receiving and any required inspection are complete.

How should planners handle a split transfer?

Track each open portion and its expected receipt date under the same movement. Recalculate the destination’s balance using the quantities that can arrive in each period.