Author: James Synder is a Certified Master Anaplanner and Associate Director at Accenture.
Where is the gap?
A strong foundation and a familiar planning challenge
One of the most rewarding aspects of implementing the Anaplan Supply Chain Applications is seeing how quickly an organization can connect demand, inventory, and supply planning. The application suite provides a pre-built foundation for demand analysis, demand planning, inventory planning, rough-cut capacity planning, and production planning. Rather than beginning with a blank model, implementation teams configure the applications, test them against business requirements, and identify extensions through fit-gap analysis.
That acceleration does not eliminate the complexity of the real supply chain. In several client situations, replenishment recommendations were mathematically consistent with the information in the model, but critical operating constraints were managed elsewhere. Contract-manufacturer capacity, upstream inventory shortages, or SKU-transition rules were known to planners, yet not fully represented in the standard planning flow.
This distinction matters: the issue is not necessarily that the planning logic is wrong. The issue is that a feasible plan requires visibility to every material constraint. When a constraint is absent, the plan may look achievable in the model while remaining difficult to execute operationally and support anticipated demand.
How the standard planning flow works
The process begins with demand. Demand is forecast by product and customer(or demand-generating entity). Inventory Planning maps those demand-generating entities to the locations that supply them, such as distribution centers. The application then projects inventory and applies policy settings to determine target inventory and replenishment need.
Those policies can incorporate product segmentation, including ABC-XYZ classifications, together with planning parameters such as order frequency, lead time, minimum order quantity, and order multiples. Based on projected need, the application produces suggested orders intended to maintain the target inventory position.
The planning flow becomes more sophisticated in a multi-tier network. A customer-facing distribution center may be replenished by an upstream distribution center rather than directly by a vendor or manufacturer. In that configuration, the downstream inventory requirement is passed upstream so the supplying node can incorporate network demand into its own replenishment calculation.
The elegance of multi-tier replenishment
Multi-tier inventory planning introduces a classic dependency: the downstream location needs a planned receipt from the upstream location, while the upstream location needs the downstream requirement to calculate how much inventory it must procure. The Inventory Planning design addresses this through successive calculation passes.
In the IVP200 inventory forecasting module, the Tier 1 calculation determines inventory need at each node. Where a distribution center is resupplied by another distribution center, that need is shifted to the supplying location using the associated lead time. The Tier 1 & 2 calculation then incorporates the passed requirement, while the receiving location recognizes the expected inbound quantity as Planned Receipts from Network Replenishment.
This is a powerful design pattern. It allows the downstream need to be fed back into the network calculation without creating a circular reference, and it gives the upstream purchasing or manufacturing node visibility to the inventory it must source for the broader network.
Where the gaps begin to appear
1️⃣ The customer-facing shortage can be hidden.
A downstream distribution center may assume that inventory will arrive from its supplying distribution center within the configured transfer lead time. The shortage, however, is calculated at the upstream supplying node. If upstream inventory is insufficient, the receiving location can still reflect the planned network receipt even though the transfer may not be fully achievable.
The practical blind spot is customer impact. The network recognizes a shortage at the supplying location, but the model may not directly express that shortage as constrained sales at the customer-facing location. Planners therefore need a way to trace upstream scarcity back to the demand it may prevent the network from serving.
2️⃣ External capacity is not automatically a planning constraint.
Many organizations manage capacity with contract manufacturers, co-packers, plants, or central purchasing teams. Those groups may allocate a finite quantity across products, locations, or periods. If that capacity is not represented in the Inventory Planning process, the replenishment algorithm can recommend supply based on need without knowing whether the manufacturer or plant can produce the required volume.
This creates a gap between unconstrained replenishment need and executable supply. The requirement is visible, but the scarce capacity must still be allocated deliberately.
3️⃣ Demand and inventory may live at different levels.
A third challenge occurs during SKU transitions. A business may forecast demand at an aggregate SKU or product level while holding inventory at a more detailed variant level. Older variants may need to be depleted before the organization procures the replacement variant.
In that situation, aggregate demand must be allocated across eligible variants according to lifecycle rules. Standard inventory policy parameters determine when and how much to replenish, but they do not, by themselves, define which version of a product should satisfy demand first or when procurement should shift to the new variant.
A fit-gap opportunity, not a failure of the application
These scenarios should not be interpreted as evidence that the Supply Chain Applications are ineffective. They illustrate why application implementations still require business discovery, configuration, fit-gap analysis, extension design, and regression testing. The standard application provides the planning engine and connected data flow. The implementation must then represent the constraints that are distinctive to the company, industry, and operating model.
Framing the issue this way also protects the value of the standard application. The objective is not to replace the core replenishment logic with custom development. It is to add targeted extensions that expose constraints, allocate scarce supply, or translate shortages to the level at which planners make decisions.
What comes next
Each of these gaps can be addressed through thoughtful Anaplan design patterns. Part 2 explores approaches for translating upstream shortages to customer-facing demand, constraining replenishment with manufacturer or plant capacity, and managing allocation across SKU variants during a product transition.
Because in supply chain planning, the most dangerous constraint is not the one you can see. It is the one your planning system does not know exists.