A hierarchical time series is a structured collection of individual time series linked by linear aggregation constraints, where lower-level series (e.g., SKU-level sales) sum exactly to higher-level nodes (e.g., product category or national totals). This structure imposes a strict mathematical coherence requirement: forecasts generated independently at different levels will almost certainly violate the sum-to-one consistency, necessitating formal forecast reconciliation to align bottom-up and top-down predictions.
Glossary
Hierarchical Time Series

What is Hierarchical Time Series?
A structured collection of time series organized by aggregation constraints, such as product categories rolling up to departments or regional demand summing to national totals.
The hierarchy is typically defined by a summing matrix that encodes the organizational structure—whether a product taxonomy, geographic rollup, or cross-dimensional lattice combining both. Advanced approaches like the MinT (Minimum Trace) reconciliation method leverage the covariance structure of base forecast errors to produce optimal coherent forecasts that minimize expected loss across all levels simultaneously, ensuring supply chain decisions at any aggregation node are consistent with granular operational plans.
Key Characteristics
Hierarchical time series impose aggregation constraints that require specialized modeling and reconciliation techniques to ensure coherent, decision-ready forecasts across all levels of the supply chain.
Aggregation Constraints
A defining property where lower-level series must mathematically sum to higher-level totals. In supply chains, daily SKU-level demand at a specific warehouse must equal the weekly regional demand for that product category.
- Summing matrix: A linear operator that maps bottom-level forecasts to all higher aggregation nodes
- Coherency violation: Occurs when independently generated forecasts at different levels produce conflicting totals
- Cross-sectional hierarchy: Product, geographic, and temporal dimensions create intersecting aggregation paths
- Example: National sales forecast ≠ sum of regional forecasts, creating confusion for inventory planners
Reconciliation Strategies
Methods for adjusting base forecasts to enforce mathematical coherence across the hierarchy without sacrificing accuracy at any level.
- Bottom-up: Generate forecasts at the most granular level and aggregate upward—preserves detail but amplifies noise
- Top-down: Forecast at the highest level and disaggregate using historical proportions—stable but loses local patterns
- Middle-out: Start at an intermediate level, forecast up and down—balances granularity and stability
- Optimal reconciliation: Uses generalized least squares to produce coherent forecasts that minimize total error variance across all levels
Cross-Level Correlation
The statistical dependencies that exist between series at different hierarchical levels, which naive independent forecasting ignores.
- Shared shocks: A supply disruption at a regional distribution center simultaneously impacts all downstream store-level series
- Information pooling: Higher-level aggregates often exhibit more stable patterns, providing useful regularization for noisy bottom-level forecasts
- Covariance estimation: Optimal reconciliation requires estimating the full covariance matrix of base forecast errors across all nodes
- Example: A national promotion lifts all regional demand simultaneously, creating correlated forecast errors that reconciliation must account for
Temporal Hierarchies
Aggregation constraints that operate across time dimensions, where daily forecasts must sum to weekly, monthly, and quarterly totals.
- Non-overlapping aggregation: Daily → Weekly → Monthly → Quarterly → Annual
- Seasonal alignment: Weekly patterns must be preserved when aggregating to monthly buckets
- Forecast horizon consistency: Short-term daily forecasts and long-term annual projections must not contradict each other
- Example: A demand sensing model predicting daily sales must reconcile with the S&OP process's monthly volume forecast
Probabilistic Coherence
Extending reconciliation beyond point forecasts to ensure that entire predictive distributions are consistent across hierarchy levels.
- Distributional reconciliation: Adjusts quantile forecasts so that the sum of lower-level distributions matches the upper-level distribution
- Copula-based methods: Model the dependence structure between hierarchical nodes to preserve joint distributional properties
- Gaussian aggregation: Under normality assumptions, the mean and variance of aggregated forecasts can be derived analytically
- Example: The 95th percentile of national demand must equal the convolution of regional demand distributions, not their simple sum
Forecast Value Added Analysis
A diagnostic framework for measuring whether hierarchical reconciliation improves or degrades accuracy at each node compared to base forecasts.
- Node-level metrics: Evaluate reconciliation impact using CRPS or MASE at every aggregation point
- Reconciliation penalty: Some nodes may experience accuracy loss to achieve global coherence—quantify this trade-off
- Disaggregation gain: Bottom-level forecasts often improve when informed by stable top-level patterns
- Example: A retail chain finds that reconciliation reduces regional forecast error by 12% but increases store-level error by 3%, requiring a business decision on acceptable trade-offs
Frequently Asked Questions
Clear, technically precise answers to the most common questions about structuring, reconciling, and optimizing hierarchical time series models for enterprise supply chain intelligence.
A hierarchical time series is a structured collection of individual time series organized by aggregation constraints, where lower-level data (e.g., SKU-level daily sales) sums exactly to higher-level data (e.g., category-level monthly totals). The structure works by defining explicit parent-child relationships across multiple dimensions—such as product hierarchies (item → brand → category → division) and geographic hierarchies (store → city → region → country)—creating a tree or lattice topology. Each node in the hierarchy generates its own forecast, but these independent predictions almost never satisfy the aggregation consistency constraint naturally. The core operational challenge is that the sum of bottom-level forecasts rarely equals the independently generated top-level forecast, creating a mathematical incoherence that must be resolved through reconciliation algorithms. In supply chain contexts, this structure enables planners to generate demand signals at the granular SKU-location level while maintaining strategic alignment with aggregate financial and capacity plans at the regional and global 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
Master the ecosystem of concepts that surround hierarchical time series forecasting, from reconciliation mathematics to the probabilistic models that power modern supply chain intelligence.
Forecast Reconciliation
The mathematical process of adjusting forecasts generated independently at different hierarchy levels to ensure aggregate consistency. Without reconciliation, bottom-level SKU forecasts will not sum to the category total, creating planning chaos.
- Top-down: National forecast is disaggregated to lower levels using historical proportions
- Bottom-up: Detailed forecasts are summed upward to create higher-level views
- Middle-out: A middle level is forecast, then both aggregated up and disaggregated down
- Optimal reconciliation uses the covariance structure of forecast errors to produce the most accurate coherent forecasts across all levels
Temporal Fusion Transformer
An attention-based deep learning architecture purpose-built for interpretable multi-horizon forecasting with native support for hierarchical structures. Unlike black-box models, TFT provides variable selection networks and attention weights that explain which features drive predictions.
- Handles static metadata (product category, location), known future inputs (holidays, promotions), and observed historical inputs (past sales) simultaneously
- Quantile outputs produce full prediction intervals, not just point estimates
- Naturally extends to hierarchical settings by sharing learning across related time series
Bottom-Up vs. Top-Down Approaches
Two fundamental strategies for generating coherent hierarchical forecasts, each with distinct trade-offs in accuracy and computational complexity.
- Bottom-up: Forecast at the most granular level (SKU-store-day), then aggregate upward. Preserves local patterns but accumulates noise and may miss macro trends
- Top-down: Forecast at the aggregate level, then distribute downward using historical proportions. Stable and fast but obliterates granular signals
- Middle-out hybrid approaches often outperform both extremes in practice, especially when combined with optimal reconciliation
DeepAR
Amazon's autoregressive recurrent neural network that produces probabilistic forecasts by learning a parametric distribution (e.g., negative binomial for count data) from hundreds or thousands of related time series. DeepAR excels in hierarchical settings because it shares global parameters while maintaining local context.
- Outputs full probability distributions, enabling quantile-based safety stock calculations
- Handles cold-start items by leveraging learned similarities across the hierarchy
- Particularly effective for intermittent and lumpy demand patterns common in spare parts supply chains
Prediction Intervals & Service Levels
The direct bridge between probabilistic hierarchical forecasts and operational inventory decisions. A prediction interval specifies the range within which future demand will fall with a given probability (e.g., 95%).
- A 95% prediction interval means there is only a 5% chance actual demand exceeds the upper bound
- Service level targets (e.g., 98% fill rate) map directly to specific quantiles of the forecast distribution
- Hierarchical reconciliation must preserve the coherence of uncertainty — the variance of the aggregate forecast should equal the sum of lower-level variances plus covariance terms
Continuous Ranked Probability Score
The strictly proper scoring rule used to evaluate probabilistic hierarchical forecasts. CRPS measures the integrated squared difference between the predicted cumulative distribution function and the observed outcome, rewarding both calibration and sharpness.
- Unlike point-error metrics (MAE, RMSE), CRPS penalizes overconfident narrow intervals that miss the truth
- A CRPS of zero indicates a perfect probabilistic forecast
- Essential for model selection when comparing DeepAR, TFT, and other probabilistic methods across hierarchy levels

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