Industrial planning with Anaplan
Yoplait - Sodiaal
Discover how Yoplait optimizes industrial planning with Anaplan, combining production scheduling, inventory deployment and fresh dairy constraints.





Excel has become the default planning tool for many Supply Chain teams. Its apparent flexibility and ease of use make it the obvious choice. However, when faced with the realities of modern planning processes (multidimensional, collaborative and highly interconnected) Excel reveals limitations that undermine both reliability and performance.
These limitations are not isolated: they reinforce one another and ultimately affect the entire planning cycle. This article examines these limitations across three main areas, from technical constraints and functional shortcomings to data governance challenges, and explains how Anaplan addresses each of them.
Before collaboration or governance even become an issue, Excel is held back by fundamental architectural limitations. This is where the problem begins: a tool designed to manipulate two-dimensional spreadsheets is being used to manage the inherent complexity of Supply Chain planning.
Supply Chain planning requires organisations to work across multiple dimensions simultaneously, including products, warehouses, geographical regions and planning horizons. Excel handles these dimensions within a two-axis spreadsheet structure. As soon as three or more dimensions need to be combined within the same calculation, the model quickly becomes unmanageable. Planners multiply worksheets, lose visibility into calculations and can no longer guarantee data consistency.
This limitation cannot be overcome through better spreadsheet design or user expertise. It is inherent to Excel’s architecture and only becomes more problematic as data volumes continue to grow.
As Excel workbooks grow, they rapidly become difficult to manage. Beyond a certain volume of data, waiting times become a significant operational constraint:
In a time-sensitive planning cycle, this level of latency is unacceptable. It forces planners to reduce the number of planning iterations they can perform, ultimately limiting the quality of business decisions. But performance is only part of the problem—Excel’s overall reliability is equally at stake.
An unsaved crash can erase hours of work. VBA macros developed on one workstation may fail on another. Compatibility issues between Microsoft Office versions can introduce silent errors. And because Excel offers no native mechanism for automated collaboration, files continue to circulate via email with little or no traceability.
Across the projects we deliver with our clients, these situations are far from exceptional. They occur repeatedly, regardless of industry or company size. Excel’s technical fragility is not a theoretical risk—it is an operational reality that many Supply Chain teams have gradually accepted simply because they lacked a viable alternative.
These three limitations: restricted multidimensionality, poor calculation performance and technical fragility, form the foundation of Excel’s shortcomings in Supply Chain planning. Yet they represent only the first layer of the problem. Even if these issues could somehow be eliminated, Excel would still remain fundamentally unsuited to collaborative planning.
The technical limitations described above have direct consequences: they make collaboration difficult, interfaces cumbersome and scenario planning almost impossible. Excel was designed as an individual productivity tool. Supply Chain planning, by contrast, is fundamentally a collaborative process.
Demand planners, merchandising planners, supply planners, logistics managers and commercial teams all need to work with consistent, up-to-date data. Excel simply does not support this way of working. Simultaneous edits create conflicts. Naming conventions and file formats vary from one workbook to another. Managing user access by business scope is either non-existent or entirely manual.
As a result, teams work in silos, using different versions of the same data, and spend a significant amount of time reconciling discrepancies instead of focusing on planning. This loss of efficiency is also reflected in the day-to-day user experience.
Complex Excel models quickly accumulate worksheets containing raw data, intermediate calculations, summary tables and charts. Navigation is not intuitive or guided. A planner responsible for a limited business scope is often exposed to the entire model. Reporting remains largely static and frequently requires exporting data to Power BI before it becomes truly actionable.
This daily friction slows down planning cycles and increases the likelihood of input errors, particularly in poorly secured models. It also limits the ability of planners to test assumptions and compare alternative scenarios efficiently.
Scenario planning is a fundamental requirement of any S&OP process. Excel provides no native capability to manage multiple scenarios within the same planning model. The most common approach is to duplicate the entire workbook for every new assumption. Pivot tables do not update automatically across scenarios, and consolidating multiple business units into a single enterprise plan remains a manual, time-consuming and error-prone exercise.
Ultimately, Excel’s functional limitations are far more than simple inconveniences. They reduce the quality of decisions made during S&OP reviews and weaken the consistency of the entire planning process. The same lack of robustness can also be seen in the way data itself is managed.
The collaboration challenges described in the previous section inevitably lead to another issue: data fragmentation. Once it takes hold, it becomes extremely difficult to reverse. This is arguably Excel’s most significant limitation in a Supply Chain environment, as it directly affects the trust organisations can place in the data used to make critical business decisions.
Every planning cycle managed in Excel generates new workbooks. They are shared by email, stored in shared folders with inconsistent naming conventions and duplicated across multiple stakeholders. Over time, identifying the authoritative version becomes increasingly difficult. Teams end up working with inconsistent data, and confidence in planning decisions gradually declines.
This lack of governance is not simply the result of poor internal processes that could be resolved through better discipline. It is a structural limitation of Excel as a planning tool, creating countless opportunities for errors to occur.
Excel is, by design, an open environment. Any user can accidentally overwrite a formula with a manually entered value. An incorrect copy-and-paste operation can break an entire calculation chain. A planner may unintentionally modify another colleague’s planning scope without anyone noticing. Excel provides no native control centre capable of detecting these issues. In many organisations, maintaining the planning model depends on a single expert, creating a significant operational risk.
These risks are far from theoretical. We encounter them regularly in the planning processes implemented by our clients, where they directly impact the quality of operational decisions. And when organisations attempt to address these issues, they often face one final obstacle: the model itself becomes increasingly difficult to evolve.
Enhancing a complex Excel model quickly becomes a project in its own right. VBA macros are written in an ageing programming language that is difficult to document, maintain and transfer to new team members. Adding a new planning dimension often requires restructuring the entire model. Knowledge of how the workbook functions is frequently concentrated in the hands of a single specialist, meaning that any departure can halt future development.
This technical debt accumulates planning cycle after planning cycle until the model becomes virtually untouchable—precisely when business requirements are evolving faster than ever. It is the inevitable outcome of using a spreadsheet application designed for data manipulation to support planning processes of far greater complexity.
The three categories of limitations explored in this article are closely interconnected. Excel’s technical constraints make collaboration more difficult, collaboration challenges lead to fragmented data, and fragmented data ultimately creates a growing maintenance burden that becomes increasingly difficult to manage. It is a vicious cycle that becomes harder to break as organisations grow accustomed to their existing processes and planning models become more complex over time.
Excel remains an effective tool for ad hoc analyses and quick exploratory work. However, when the objective is to build a robust, collaborative and scalable planning process, its structural limitations can no longer be compensated for by the ingenuity of experienced planners.
The real question is no longer whether Excel is sufficient. It is how much these limitations actually cost: time lost reconciling inconsistent data, undetected errors, inefficient planning cycles and strategic decisions based on unreliable information. Anaplan is designed to break this cycle by combining a multidimensional calculation engine, real-time collaboration, built-in data governance and integrated scenario planning. These capabilities provide the foundation on which our clients build planning processes that match the growing complexity of today’s Supply Chains.
behind the article
An engineering graduate of CentraleSupélec, specialising in supply chain and operations management, Julian supports OneHive’s clients in the design and implementation of planning solutions on Anaplan. As a certified Anaplan Model Builder, he contributes to the transformation of demand planning, business planning and integrated S&OP/IBP planning processes. His experience in modelling enables him to contribute to defining requirements, building models and implementing collaborative workflows, particularly for forecasting, budgeting and production planning. His work in the luxury, retail and agri-food sectors allows him to combine an understanding of operational challenges with data analysis and technical expertise.
Our latest news
Cas Client
Industrial planning with Anaplan
Discover how Yoplait optimizes industrial planning with Anaplan, combining production scheduling, inventory deployment and fresh dairy constraints.
Article • 10 min
October 19, 2026
Learn how to structure trade-offs, define the right planning granularity and make better decisions with Anaplan.
Cas Client
Supply Chain Planning
Transformation of supply chain planning operations at a major French perfumes and cosmetics group, in partnership with Argon & Co
Discover answers to key questions about our services and approach.
Excel was designed to manipulate two-dimensional data on an individual workstation. Supply Chain planning requires organisations to work across multiple dimensions simultaneously—including products, warehouses and planning horizons, while enabling collaboration between multiple stakeholders and managing large volumes of data. These requirements go far beyond what Excel can reliably and efficiently support.
Excel's limitations fall into three main categories. First, technical constraints such as slow calculation times, limited reliability and the inability to handle multidimensional planning models. Second, functional shortcomings, including the lack of real-time collaboration, guided user interfaces and integrated scenario planning. Finally, data governance challenges, such as version proliferation, accidental formula overwrites and increasingly difficult model maintenance caused by technical debt.
For a large planning workbook of 20 to 50 MB, a common size in Supply Chain environments, recalculation after a data update can take anywhere from 30 seconds to several minutes. Opening the workbook itself may also take more than a minute. These delays reduce the number of planning iterations teams can perform during each planning cycle, ultimately affecting the quality of business decisions.
Anaplan was purpose-built for enterprise planning. Its Hyperblock™ calculation engine natively supports multidimensional models, performs in-memory calculations on the server and enables multiple users to work simultaneously within the same planning model. Scenario planning, plan consolidation and role-based access management are built into the platform, eliminating the need for duplicated spreadsheets while improving governance and data reliability.
The transition becomes worthwhile when Excel models are no longer maintainable by a single expert, when S&OP cycles are disrupted by inconsistent data across teams, or when calculation times begin to slow decision-making. It is also a strong indicator that the organisation needs more advanced scenario planning, stronger data governance and complete traceability of planning changes.
Didn’t find what you were looking for?
Contact usLet’s explore how we can make your project a success.
Connect with our experts