Bills of materials and variants
Product structures, components, operations and variants can be managed centrally. Changes flow through to purchasing requirements, cost and manufacturing orders.
Odoo for the manufacturing industry
Odoo brings sales, inventory, purchasing, manufacturing, quality, maintenance and administration together. For manufacturing companies, the real value emerges when planning reflects what machines and employees actually do, not just what was planned in the office.
Daily reality
Many manufacturing companies still plan with standard times established years ago and rarely measured again. On paper, the order fits the weekly plan. In reality, changeovers take longer, materials are not ready or a short fault is never recorded. The planner sees the difference only when delivery is already under pressure.
Production feedback is often entered at the end of the shift or even the next day. Employees reconstruct quantities, downtime and consumption from memory and notes. Work in progress, inventory and capacity then lag behind reality, while planning continues to calculate with outdated information.
Actual cost also remains incomplete. Energy, scrap, rework, waiting time and extra operations disappear into overhead. Quotations are based on standards while actual execution is insufficiently visible. The problem is rarely a lack of commitment; it is a recording process that demands too much from people at the busiest moment of the day.
A strong standard foundation
Odoo provides a broad and coherent foundation for manufacturing. The apps share the same products, customers, orders, inventory and financial data. Information therefore no longer needs to be copied continuously between separate systems.
Product structures, components, operations and variants can be managed centrally. Changes flow through to purchasing requirements, cost and manufacturing orders.
A manufacturing order can be divided across work centres and operations. Employees see what needs to be completed, which materials are required and which step follows.
Capacity, sequence and lead time become visible in a shared plan. Dependencies and conflicts can be discussed earlier than when using separate spreadsheets.
Checks can be linked to products, operations, receipts and manufacturing orders. Deviations remain connected to the relevant batch or order.
Preventive and corrective maintenance can be planned, assigned and followed up. Maintenance history remains with the relevant work centre or device.
Raw materials, semi-finished products, serial numbers and lots remain visible in the same chain. Receipt, consumption, manufacturing and delivery align administratively.
For many companies, these standard functions are already a major step forward. They replace separate lists and enable one order flow from quotation to delivery and actual costing. The quality of the result still depends on good master data, clear responsibilities and consistent feedback.
An honest boundary
Odoo plans on the basis of the data it receives. It does not automatically verify whether a work centre is actually running, whether an employee has temporarily stopped the machine or whether the standard time still matches reality. When feedback is missing, planning therefore continues to rely on assumptions.
Produced quantities are confirmed by a person as standard. This works well when recording is simple and employees have time. With high volumes, many short operations or several machines per operator, delays and entry errors arise more easily. Short stops often disappear entirely because nobody wants to perform an action for every interruption.
Odoo's standard OEE view also depends on the data supplied to it. Waiting time between operations, actual energy use and specific machine conditions are not captured automatically. An additional shop-floor layer can therefore add value where direct source information is needed.
Connecting the office and shop floor
The shop-floor layer does not replace Odoo. It ensures that relevant events from machines and devices become available at the right time for processes already managed in Odoo.
Actual operation times can be compared with standards. Routings, quotations and capacity plans gradually become more realistic as a result.
Short interruptions that are normally not recorded can also become visible as patterns. This helps teams discuss causes and priorities more effectively.
Where appropriate, production counts come from the machine or a connected device instead of being reconstructed afterwards.
Relevant conditions can be recorded against the corresponding order or batch, providing more context for quality and traceability.
Scales can make values available for receipt, dosing, manufacturing, quality or shipping without duplicate entry.
Printers can receive labels, work documents or shipping information from the process step where they are needed, even when the printer itself has no network or Wi-Fi connection.
During the technical survey, we determine which available information is meaningful and reliable for your machine and process. This may include digital or analogue I/O, relay and contactor contacts, limit switches, light curtains, sensor outputs or power consumption. The result is dependable process information in Odoo without unnecessary changes to equipment that already works.
Read how Linky Business connects machines and devices to Odoo.
Different manufacturing environments
Odoo has a broad foundation, but the emphasis differs by type of manufacturing. We therefore do not start with a list of apps, but with the order flow, shop floor and information needed to improve decisions.
Small batches, frequent changeovers and limited machine capacity make standard times and current progress important. Downtime, tool changes and rework quickly affect delivery dates and margin.
Design changes, project purchasing and assembly overlap. Odoo can connect sales, projects, purchasing, bills of materials and manufacturing, but change management must be configured carefully.
Moulds, cycle times, material lots and quality conditions determine execution. Short stops and differences between standard and actual cycle times particularly require reliable source information.
Lots, shelf life, recipes, allergens and quality checks require strong traceability. Weighing and recording must fit into the process without unnecessarily slowing production.
Many variants, short jobs and tight delivery windows require fast order changes. Labels, material consumption and completion feedback must match the job that was actually executed.
Old, new, advanced and simple machines often operate side by side. We assess each machine or device by the information it can reliably provide rather than by a fixed supported-device list.
Start in a manageable way
A manufacturing implementation can begin in phases with one product family, one department or one order flow. First, the most important processes, master data and responsibilities are configured in a workable way. Connections to machines, scales, printers or sensors can then be added where manual recording is unreliable or too time-consuming.
The machine-connectivity model consists of a fixed monthly fee per location, a fixed monthly fee per additional node and a one-off fee for custom work. Specific amounts are listed only on the pricing page. A pilot with two machines can demonstrate technical feasibility and the usefulness of the data before a wider rollout.
Also read how we build an Odoo implementation and what involvement we need from your organisation.
From sales to actual costing
A manufacturing order does not start at the machine. Execution quality is already influenced by the quotation, product variant, delivery date and agreements with the customer. When that information is incomplete, urgent purchasing, manual adjustments and uncertainty about what exactly must be delivered arise later. Odoo makes it possible to organise sales, material requirements, purchasing, manufacturing and delivery from the same order context.
After execution, the same chain must look back at reality. Which materials were actually consumed? Which operations took longer? Where did scrap or rework occur? Was the delivery date met and does the margin still match the quotation? When shop-floor data and administrative records align, the controller receives useful actual costing per order or product group instead of a general explanation afterwards.
That is why we do not assess apps in isolation. We test a complete flow with a normal order, a change, a material shortage and a deviation. This reveals whether employees, planning and administration see the same reality and whether the chosen configuration remains workable under pressure.
Frequently asked questions
Often it does. A modern network port or known protocol is not always required. During the technical survey, we assess which existing signals or outputs can provide useful information without modifying the machine internally.
No. Start with one process where delayed or duplicate recording has a significant impact. A good first phase provides insight and makes the next genuinely valuable step clear.
We first investigate whether your current ERP supports the desired processes sufficiently and whether integration is more sensible than migration. Odoo is not automatically the right choice for every organisation.
That depends on scope, data quality, the number of departments, training and integrations. After an assessment, we create a phased plan with clear decision points and responsibilities.
Yes. A defined product group, line or department is often a sensible start, provided the foundation is designed so that other departments can join logically later.
We determine which master data, open processes and history are required. Data is cleaned, tested and checked before it is used in the new configuration.
Show us where planning, production feedback or inventory currently differs from the shop floor. We will explain honestly what standard Odoo solves and where additional connectivity is needed.