Top-Down Reconciliation is a hierarchical forecasting technique where a prediction is first generated for a total aggregate series, and this top-level forecast is then disaggregated and allocated down to the constituent lower-level series based on historical or calculated proportions. This ensures perfect mathematical coherence, where the sum of all bottom-level forecasts exactly equals the aggregate forecast, preventing planning discrepancies across the business hierarchy.
Glossary
Top-Down Reconciliation

What is Top-Down Reconciliation?
A method for enforcing coherence in hierarchical forecasts by generating predictions at an aggregate level and then distributing them to lower levels.
Unlike Bottom-Up Reconciliation, which sums granular forecasts upwards, the top-down approach relies on the assumption that the aggregate signal is more stable and statistically reliable than noisy granular data. The disaggregation is typically performed using static historical proportions of each child node's contribution to the parent, though dynamic models can adjust these proportions based on recent trends or external regressors to improve accuracy at the leaf level.
Key Characteristics of Top-Down Reconciliation
A method for ensuring hierarchical forecast coherence by generating a forecast at the aggregate level and then disaggregating it down to lower levels based on historical proportions.
Definition and Core Mechanism
Top-Down Reconciliation is a hierarchical forecasting strategy that first generates a forecast for the total aggregate level of a business structure (e.g., total national demand) and then disaggregates this single number into lower-level forecasts (e.g., regional or SKU-level) using calculated historical proportions. This approach guarantees that the sum of all lower-level forecasts perfectly equals the top-level forecast, enforcing mathematical coherence by design. It is the conceptual opposite of Bottom-Up Reconciliation, which starts at the granular level and sums upwards.
Disaggregation Proportions
The accuracy of top-down reconciliation depends entirely on the method used to calculate the historical proportions for disaggregation. Common approaches include:
- Average Historical Proportions: Using the simple mean of each child node's contribution over a historical window.
- Proportions of Historical Averages: Calculating the ratio of each child's historical mean to the parent's historical mean, which is more stable when individual series are noisy.
- Rolling Window Proportions: Using only the most recent periods to capture shifting trends, making the method responsive to concept drift in market share.
Primary Use Cases
Top-down reconciliation is strategically preferred in specific business contexts:
- High-Level Strategic Planning: When the primary forecast of interest is the aggregate number (e.g., total corporate revenue) and granular forecasts are only needed for allocation.
- Noisy Granular Data: When bottom-level time series are highly volatile, sparse, or exhibit intermittent demand, making reliable statistical modeling at the SKU level impossible.
- Stable Product Mix: In mature product categories where the relative proportion of sales between items remains consistent over time, making historical proportions a reliable predictor of future distribution.
Advantages and Limitations
Advantages:
- Simplicity: Computationally inexpensive and easy to implement without complex multivariate models.
- Noise Reduction: Aggregate forecasts are inherently more stable and less affected by the erratic variance of individual bottom-level series.
- Guaranteed Coherence: The hierarchy is mathematically consistent by definition.
Limitations:
- Masking Granular Signals: It cannot capture a sudden surge in demand for a specific SKU if the aggregate forecast remains flat.
- Proportion Rigidity: Relies on the assumption that historical proportions will persist, failing during rapid market share shifts or product cannibalization events.
Comparison with Optimal Reconciliation
Unlike Top-Down or Bottom-Up methods, which are single-pass strategies, Optimal Reconciliation (e.g., MinT) uses a regression model to combine forecasts from all levels of the hierarchy. It generates a set of coherent forecasts that minimizes a global loss function, leveraging the information in every node. While top-down reconciliation discards all bottom-level model forecasts in favor of a single aggregate prediction, optimal reconciliation treats every level's independent forecast as a valuable signal to be weighted and adjusted.
Implementation in Supply Chain
In a Supply Chain Digital Twin, top-down reconciliation is often used for financial planning and budget allocation, where a corporate revenue target (the top-level forecast) must be distributed across business units. For operational execution, such as setting Reorder Points and Safety Stock at individual warehouses, this method is often supplemented or replaced by Demand Sensing and bottom-up models to ensure local demand signals are not lost in the aggregation process.
Top-Down vs. Bottom-Up Reconciliation
Comparison of the two primary strategies for ensuring mathematical consistency across hierarchical forecast levels, from aggregate to granular.
| Feature | Top-Down Reconciliation | Bottom-Up Reconciliation | Middle-Out Reconciliation |
|---|---|---|---|
Forecast Generation Level | Aggregate level first | Most granular level first | Intermediate level first |
Disaggregation Logic | Historical proportions or weights | Simple summation upward | Bidirectional propagation |
Granular Forecast Accuracy | Lower; noise at detail level is smoothed | Higher; captures local patterns | Moderate; balances both |
Aggregate Forecast Accuracy | Higher; leverages total market signal | Lower; errors compound upward | Higher; constrained by middle level |
Data Requirements | Aggregate-level time series only | Full granular time series for all nodes | Partial hierarchy data |
Handling of Intermittent Demand | Poor; zero-demand periods lost in aggregation | Good; models sporadic patterns directly | Moderate; depends on middle-level sparsity |
Computational Complexity | Low; single model at top level | High; many models at leaf nodes | Medium; subset of models |
Cold Start Resilience |
Frequently Asked Questions
Clear answers to common questions about top-down reconciliation, its mechanics, and its role in ensuring coherent demand forecasts across complex retail hierarchies.
Top-down reconciliation is a hierarchical forecasting method that ensures mathematical coherence by first generating a forecast at an aggregate level and then disaggregating it down to lower levels based on historical proportions. The process begins with a single, high-level forecast—such as total national demand for a product category—which is then distributed to regional, store, and SKU levels using static or dynamic disaggregation weights. These weights are typically derived from the historical contribution of each lower-level node to its parent. For example, if Store A historically accounts for 12% of a region's sales, it receives 12% of the regional forecast. This approach guarantees that the sum of all child forecasts exactly equals the parent forecast, eliminating forecast bias that can arise when bottom-up estimates are independently generated and fail to align with strategic top-line projections. The method is computationally efficient because it requires training only a single aggregate model, but it assumes that historical proportions remain stable and may obscure emerging trends at granular levels.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Top-down reconciliation is one of several strategies for ensuring forecast coherence across hierarchical business structures. Explore the complementary methods and foundational concepts below.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us