Strategy

    Distribution Planning: from static DRP to a live plan

    Alexandre Erhart
    2026
    20 min read

    Distribution is not only moving boxes between warehouses. It is deciding, every day, how much each center should receive, where it comes from, in which modal, respecting real demand and what logistics can deliver — without sinking any DC in stockout or excess.

    From static DRP to a live plan

    Most companies still plan distribution with fixed batches, moving averages or a single network-wide coverage rule. The outcome is predictable: one DC always in stockout, another always in excess, panic transfers and freight cost climbing without clear cause.

    Mature distribution planning is the opposite of that.

    It is a demand-driven plan, frequently recomputed, connecting regional demand, stock per DC, transport capacity and fair-share rules — producing an executable, balanced transfer plan.

    Planning distribution is not about moving boxes. It is about deciding, based on every network constraint, where to transfer, how much and when — before the problem shows up at the counter.

    A structured process starts from regional demand, projects coverage per DC, generates transfers respecting capacity and applies fair share when stock is limited:

    1

    01 — Consolidated regional demand

    Per DC, with seasonality and variability

    Each destination has its own demand curve. Replenishment starts from projected demand per unit, not a global company average.

    2

    02 — Stock and coverage per DC

    Available, in transit, reserved

    For each DC, the engine projects coverage in days and identifies which units are at risk and which carry excess.

    3

    03 — Planned transfers

    Origin, destination, modal, calendar

    The system generates transfer orders respecting transport capacity, pickup windows at origin and receiving windows at destination.

    4

    04 — Fair Share when stock is limited

    Coverage, commercial priority, financial

    When there is not enough stock for every destination, allocation follows business rules: those in stockout receive first, weighted by commercial and financial factors.

    5

    05 — Feasible plan with real constraints

    Transport, warehousing, calendar

    The result is not a theoretical suggestion: it is a plan that respects truck capacity, warehouse physical capacity and each DC's operating calendar.

    Demand Driven replenishment

    If your demand varies, replenishment must vary too. Computing transfer volume from fixed quantities or moving averages looks simple, but guarantees that coverage breaks at peaks and inflates at valleys.

    The correct rule is to maintain the coverage target. If DC-North targets 14 days and demand jumped from 100 to 140 units/day, the next transfer must deliver enough volume for 14 × 140 = 1,960 units, not the old 1,400.

    Variable replenishment, not fixed

    Fixed batch and moving average do not keep up with peaks. Replenishment must rise when demand rises and shrink when it slows, keeping the same coverage target.

    Coverage as the health metric

    The question is not "how many units in stock" but "how many days of future demand this balance covers". Coverage abstracts variation and exposes the real risk.

    Per SKU × DC differentiated policy

    The same SKU may target 30 days of coverage at a central DC and 7 days at a regional DC near the hub. A single company-wide policy destroys the balance.

    Reacts to real variation, not historical average

    If weekly demand jumped 40%, the next replenishment window already absorbs that. It does not wait for month-end to correct.

    Coverage is a promise to the customer; fixed batch is a spreadsheet convenience.

    Inter-plant transfers

    Well-planned transfers balance the inventory health of the entire network. Instead of each DC reacting in isolation, the whole operation behaves as a single chain, with material flowing from where it is in excess to where it is short.

    OriginDestinationSKUQuantityModalLead timeReason
    HUBDC-N4001-011.200 unRoad3dCritical coverage
    HUBDC-W4001-01600 unRoad5dScheduled replenishment
    DC-EHUB4001-01800 unRoad4dExcess → balancing
    HUBDC-S4002-02300 unAir1dSpecial order

    Each transfer plan row carries origin, destination, modal, quantity, lead time and reason. That last field is essential: it explains the why and lets the decision be audited later.

    Fair Share: allocating limited stock

    Quite often, central stock is not enough to fully serve every destination. The question shifts from "how much to send" to "whom to send first". Without a clear rule, this becomes informal pressure — the loudest gets served.

    Fair Share is the allocation ruleset that systematically and auditably decides how to split scarce stock. Good implementations combine objective factors:

    Typical Fair Share factors

    • Projected coverageDCs in stockout receive before DCs in healthy coverage.
    • Commercial priorityStrategic customer, SLA contract, product launch carry more weight.
    • Margin and profitabilityWhen stock is limited, it makes sense to prioritize destinations with higher financial contribution.
    • Service historyAvoids repeatedly penalizing the same DC across scarcity cycles.
    • Logistics costModal and distance matter: partial delivery may keep cost viable.
    Fair Share is not equal justice. It is smart justice: prioritizing who has more to lose and who delivers more value to the company.

    Finite logistics capacity

    A classic DRP (DRPII) computes transfer requirements ignoring whether transport and storage can absorb them. The theoretical result becomes an execution nightmare: trucks missing or piling up, receiving clogged, freight waiting for a slot.

    NPLAN distribution solutions go further: the engine considers finite transport and per-DC storage capacity, producing a plan that does not break the operation.

    Transport capacity

    Available fleet, modal per route, maximum vehicles per day. There is no point planning 50 transfers if the fleet only supports 30.

    Storage per destination

    Each DC has limited physical capacity in pallets, m³ or m². A plan that ignores this creates cargo that does not fit and clogs the operation.

    Pickup and receiving window

    Origin DC releases freight only in specific shifts; destination DC receives in specific windows. The plan respects the calendar instead of forcing the operation.

    Transfer lead time

    An 800 km road transfer does not arrive the next day. The engine projects arrival using the real lead time of the chosen modal.

    A distribution plan that ignores capacity creates orders; a plan that respects capacity creates execution.

    Service × cost balance

    Distribution is essentially a balancing problem across three tensioned variables: service level (meeting demand), cost (freight, storage, tied capital) and efficiency (fleet and warehouse usage).

    Pushing service without criteria inflates urgent freight cost and parks stock at the wrong DCs. Cutting cost without criteria kills service. The right tool lets you simulate scenarios and visualize the trade-off — before committing.

    Scenario A — High service

    Coverage +20% · Freight +15%

    Avg stock: +18%

    Scenario B — Balanced

    Coverage baseline · Freight base

    Avg stock: baseline

    Scenario C — Low cost

    Coverage −15% · Freight −22%

    Stockout risk: high

    The best distribution plan is not the cheapest nor the safest. It is the one that best balances service, cost and capacity usage — for the company's moment.

    How we solve it with NPLAN

    NPLAN's Distribution Planning projects let companies plan their product distribution logistics considering every chain constraint — seeking the best balance among service, cost and efficiency. It is the DRP tool you are looking for.

    HUBCENTRALDC-Ncov.4dRISKDC-Ecov.28dEXC.DC-Scov.12dOKDC-Wcov.8dLOWS1S2S3S4S5DC-N4d6d9d11d12dDC-S12d11d11d12d13dDC-E28d24d20d17d15dDC-W8d10d12d12d12dDC-NCritical coverage58%DC-WCommercial priority75%DC-SFull fulfillment100%
    Inputs and Hub
    DRP engine
    DC at risk
    Healthy coverage

    Native demand-driven DRP

    Replenishment that follows real demand variation per DC. Coverage target defined per SKU × DC, not by global average.

    Automatic transfer generation

    Origin, destination, quantity, date and modal computed by the engine based on stock, demand and transport capacity.

    Configurable Fair Share

    When stock is insufficient, allocation follows business rules: critical coverage first, commercial priority, destination financial weight.

    Finite logistics capacity

    More than a classic DRPII. The plan considers fleet, destination warehousing, calendar and operating windows — producing an executable plan.

    Consolidated network view

    The entire DC network in a single screen: coverage, planned transfers, alerts and per-bucket balancing recommendations.

    ERP and TMS integration

    Approved transfers become ERP orders and TMS instructions. The plan stops being a spreadsheet and becomes traceable execution.

    Important note

    Distribution does not fix demand or inventory policy problems. If regional forecast is poor or coverage target is not well defined per SKU × DC, the transfer plan inherits those problems. DRP executes what it receives.

    Test your Knowledge

    Five quick questions to lock in the key concepts of distribution planning.

    Question 1 of 50 correct

    Why is fixed-batch replenishment insufficient?

    Mature distribution is not a replenishment spreadsheet. It is a demand-driven engine, with smart fair share and respect for real logistics capacity — recomputed at the frequency the operation demands.

    Continue the series

    Restart the series: Demand Planning

    With distribution synchronized, the cycle closes and starts again. Every supply-chain decision begins with a reliable demand forecast.

    Back to the start of the series