Excel and separate systems are no longer enough when one production decision depends on several plan versions, manual material checks and an unclear work order status. The issue is not the spreadsheet itself, but broken information flow between sales, purchasing, warehouse, production and accounting. At that point, manufacturing digitalisation requires a shared process rather than another file.
Excel in manufacturing often has a valid role. It is useful for quick analysis, one-off calculations, data preparation and working scenarios outside the scope of a standard system. The problem begins when a spreadsheet becomes the main location for the production plan, material status, deadlines, work orders and costs.
In this operating model, each function may have its own tool and its own version of reality:
This arrangement does not necessarily stop operations immediately. Experienced people often sustain it through personal knowledge, calls and additional checks. Yet the process becomes vulnerable to a priority change, an individual's absence, an urgent order or a delayed delivery. The more manual reconciliation is required, the harder it becomes to establish which data is valid at the moment of a decision.
The most visible sign appears when the planner, production manager and sales team work from different versions of the plan. File names such as "new_plan", "final_plan" or "final_plan2" are not proof of a problem on their own, but they often reveal its cause: changes have no single recorded location or clear audit trail.
The consequences are not merely administrative. Production may start the wrong order, purchasing may order material against an outdated requirement, and sales may confirm a delivery date already changed in the plan. The important question is not who has the latest spreadsheet, but where a change is formally confirmed and who it automatically or procedurally affects.
A manual stock check before opening an order, changing a plan or ordering material often points to disconnected data. The planner may see demand from a bill of materials, the warehouse sees physical stock, purchasing sees open purchase orders, and production has already reserved material. When these details are not connected, every significant decision starts another round of checks.
It is especially important to distinguish available quantity from recorded stock. Material may physically be in the warehouse but reserved for another order, awaiting quality control or unavailable because a receipt has not been reconciled. A spreadsheet can display a number, but without clear rules and connected transactions it struggles to show the business context behind that number.
The question "what stage is the order at?" should have a verifiable answer. In a fragmented process, the answer often depends on whom to ask. An order may be open in one program, physically underway on the shop floor, partly recorded on paper and closed only after a shift or week has ended.
Without a reliable status, priority management is difficult. The planner does not know whether to move the next order, sales cannot communicate a delivery date clearly, and the production manager lacks a shared view of waiting time, stoppages, consumption or completed quantities. It is not necessary to track every detail in real time, but the organisation needs agreement on which changes are recorded, who confirms them and when they become available to others.
A variance can mean higher material consumption, lower output, a recipe change, scrap, downtime, unplanned work or a date shift. In a disconnected environment, such events often become visible only when an order is closed, spreadsheets are compared at the end of a period, or costs are calculated.
Late variance detection limits the available response. When production or purchasing receives information several days later, priorities may already have changed, material may have been ordered and a customer date may have been confirmed. The value of a connected process is not only its report, but earlier visibility of the difference between plan and execution.
A decision about integration or an ERP upgrade should not begin with the question of which program to buy. It is more useful to map one real flow, from receiving an order through closing the work order and calculating costs.
For that flow, establish:
This review often shows that the issue is not missing data, but missing shared rules. If the same data is copied into several places, identify the source record. If a plan change moves through phone calls or email, define the event that changes the plan and the visibility of that change.
Integration can be a reasonable step when existing systems cover the core functions, data has clear owners, and the issue is mainly the transfer of a limited set of information. For example, an organisation may need reliable transfer of orders, stock, work orders or production confirmations between two systems. This approach requires precisely defined data, responsibilities and rules for errors or exceptions.
An ERP upgrade or implementation of ERP for manufacturing becomes more relevant when the process itself is dispersed. This is evident when there is no single work order lifecycle, bills of materials and operations live in several files, material requirements are created manually, or accounting receives data only after repeated subsequent reconciliation.
A simple decision framework can look like this:
A manufacturer receives an order change after the plan has already allocated capacity and material. Sales enters the change in its spreadsheet. The planner receives a message, checks another document, then calls the warehouse about availability. Purchasing separately checks open purchase orders. The production manager checks order status on the shop floor.
If this sequence is a rare exception, clearer notification rules and one data transfer may be enough. If it is a regular occurrence, the organisation has more than a communication problem. It lacks one place where an order change triggers a review of capacity, materials, priorities and delivery-date consequences.
In the second case, it is useful to assess process scope, master-data quality and required connections before selecting a solution. ERP and process screening can structure this assessment around real workflows, decisions and data handover points.
A connected system does not remove the need for planning, maintaining bills of materials or responsible work confirmation. It cannot compensate for inaccurate entry, unclear accountability or a physical process with no agreed steps. A project that is too broad can also increase workload if the organisation does not decide before starting what requires standardisation and what can remain local practice.
Excel will not disappear from manufacturing. It remains suitable for analysis, simulations and preparation of specific reports. The difference is its role: a spreadsheet should not be the only record of a critical transaction or the channel through which operational truth is maintained.
Manufacturing digitalisation makes sense when it reduces uncertainty in everyday decisions. This may mean better data flow, clearer work order status or earlier recognition of variances. The scope of the solution should follow the actual problem, not a list of available functions.
Start with one product, one order family or one frequent plan-change scenario. Follow it from order to costing and record every manual copy, call, separate spreadsheet and point at which status becomes unclear. This trace provides a more concrete basis for a decision than the broad question of whether a "new system" is needed.
For organisations seeking to connect planning, materials and production execution, ORKA for manufacturing outlines areas worth considering in relation to their own process.