Where is the order stuck on the shop floor?

A customer asks when an order will ship. The planner finds its manufacturing order, but “in production” does not answer the question. Is material missing, has cutting finished, or is the part waiting for coating? Sales, the warehouse and the workshop can all be looking at the same order and still give different answers. Often the problem is not that the information is absent. It is that each team is reading a different part of the record chain.

Visibility is not merely a dashboard that says a job is green or red. A useful conversation starts with a narrower question. Can work begin? Which operation has started or finished? Has the finished product actually entered stock? In our Odoo sample implementation, those questions lead to different places: the manufacturing order, the availability of its components and its individual work orders. Reading them together is more helpful than asking one status field to explain an entire production day.

A manufacturing order is not an operation

The manufacturing order is the main record for making a particular product in a particular quantity. Its bill of materials defines the required components. When operations are defined against work centers, the Work Orders tab lists the stages separately. A cutting operation and the order as a whole do not have the same status simply because they belong to the same product. We discussed how these records fit together in an earlier article on bills of materials and work orders. Here the question is how to use that distinction to find a delay.

The sample flow follows a metal part through laser cutting, bending and powder coating. These are sample records, not data from a customer installation. At the beginning of the flow, the manufacturing order shows that required components are unavailable. The fact that three work orders are listed does not make the job ready to start. Before debating the sequence at the machines, the planner needs to establish whether the material has reached the warehouse.

Once the receipt is validated in the example, the manufacturing order shows the components as available and moves to a ready state. Its Work Orders tab lists the operations by work center. Starting and finishing each work order records time against that work. Rather than asking everyone in the building why the job has not moved, a planner can now direct the question toward the stage that is actually waiting.

Three kinds of waiting

The first is waiting for material. The manufacturing order can reveal an availability problem before production begins. In the sample implementation, missing components lead to a purchasing step, followed by a warehouse receipt. The point is not to admire a colored indicator on the screen. The receipt must be validated before the stock position changes. Treating material on its way as material on the shelf would produce a reassuring display and an unreliable plan.

The second is waiting between operations. If components are available but the cutting work order has not started, there is a different question for the shop floor. If cutting has finished and bending has not begun, the work order records identify the handoff. In the example, each of the three operations is listed separately, with time recorded as work starts and ends. That does not tell us why an employee paused. A status can locate the gap; the team still has to explain it. A machine might be unavailable, or the part may need a check before moving on. Those are possibilities to investigate, not facts that a work order screen proves.

The third is waiting after physical work is done. Finishing operations, completing a manufacturing order and dispatching a product are different events. In the sample flow, completing the manufacturing order consumes the components, moves finished units into inventory and retains actual consumption and time. The delivery is then validated separately in the warehouse. If the workshop says “finished,” sales should not quietly translate that into “already shipped.” The handoff has its own record.

A practical way to read the records

Start with the manufacturing order and check component availability. If something is missing, look at purchasing and the receipt before committing to a completion date. If components are available, open the Work Orders tab. Which operation is waiting, and which work center owns it? Then check whether the manufacturing order has been completed. If someone asks about dispatch, look for the finished stock movement and the separate delivery record. These checks put different questions in front of the people who can actually answer them.

This is not a universal manufacturing metric or a promise that every workshop can use the same routing. A part may cross fewer stations, or a production process may have a different point at which material is accepted. The three operations in the sample are useful for understanding the records, but copying them into an unrelated factory would create tidy screens and poor process data. Use your own bill of materials and the actual order of work when testing visibility.

For a small trial, choose one product family. Open a manufacturing order and note whether its components are available. After a receipt, inspect the same order again. As work proceeds, compare the start and finish entries of its operations with what happened at each station. If an operation has not started, do not label that an operator delay based on the screen alone. Agree on how the team will record exceptions, such as a hold that needs explanation. Otherwise the system will show that something stopped, while everyone still has to reconstruct the reason from memory.

A useful status question therefore has three levels. Stock and receipts explain whether material is ready. Work orders show the progress of individual operations. Manufacturing and delivery records distinguish a finished job from a dispatched order. Odoo can hold these records in one workflow, but their value still depends on timely entries and on people willing to explain exceptions honestly.

If you want to see how those records relate in a working example, the Odoo services and module catalogue is a natural place to continue.

Verification note: The screens and state changes described here were checked against Fabrika Yazılım’s Odoo sample implementation, including its manufacturing order, receipt, work orders and completion steps. All scenario data is illustrative.