Before putting Odoo Shop Floor on a tablet, define the handoffs

Cutting has started, but the planner still sees a work order that has not begun. At the end of the shift, someone enters the time in one go. The hours may be roughly right, yet nobody can say confidently when the job moved to the next station. A tablet at the machine looks like the obvious fix. It can help, but the important decision comes first: what event does each tap record, and whose work does it represent?

Odoo’s Shop Floor app is a visual interface for manufacturing and work orders. Our own sample Odoo implementation shows the underlying work orders as separate operations attached to work centers. Starting and finishing them leaves time entries. Those are related observations, not the same test: we have verified the example work order flow in our demo, but have not separately verified the Shop Floor interface in that demo. For the tablet interface, we rely on Odoo’s Shop Floor documentation. That distinction matters when deciding what you can promise your team about a proposed rollout.

Design the station before buying the screen

Shop Floor offers an overview of manufacturing orders, a view of work orders assigned to the active operator, and views for individual work centers. When the app is first opened at a workstation, work centers can be selected for that workstation. In practical terms, a cutting station does not have to present the same crowded list of jobs as a coating station. Selecting the right work center is a small configuration choice with a large effect on what the operator sees.

In our sample flow, a metal part has three operations: laser cutting, press brake bending and powder coating. Each operation belongs to a work center and appears separately in the manufacturing order’s Work Orders tab. These are sample records created to explain a process, not a customer’s production data. Their value is in making a handoff visible. The exact station names should come from your process, not from a demonstration. If two operations are performed as one continuous task, splitting them on paper just to create two tablet buttons may produce extra entries without better information.

Start with one station and one product family. Ask the operator to locate the correct work order before touching Start. Merely opening the station view does not mean a job has begun. That sounds obvious until the team reviews yesterday’s records and discovers that people considered an open screen to be evidence that production had started. Agree on the event that counts as a start and check the entry against that event on the floor.

A shared tablet still needs an operator

A device at a workstation may be used by more than one person over a shift. According to Odoo’s documentation, the Shop Floor operator panel can list multiple employees, but only one profile is active at a time. That active profile is used to track the employee’s time. If an employee has a PIN configured, switching to their profile requires it. Do not assume this protection is enabled in your environment; verify how your own employee profiles are set up before treating the tablet log as a reliable attribution of work.

Starting a work order from its card starts a timer. Odoo distinguishes the time spent on the work order from the time attributable to individual operators. The work order form can be used to inspect detailed time tracking. This distinction should survive into the conversation at the end of the day. “The operation took two hours” and “this person worked on it for two hours” are not interchangeable observations. If several people help with an operation, an unexplained total duration will not tell the planner who did what.

The recorded start is also not automatically the exact moment a machine began cutting. Someone may first fetch the material, make a setup adjustment, or remember to tap Start only after work is under way. Ask the team what they count as preparation and what they count as processing. If those events matter to your planning, agree on the recording practice before drawing conclusions from the timer. A more precise looking number is not necessarily a better description of the shop floor.

Finishing an operation is not shipping an order

A work order can be marked complete from the Shop Floor card. Odoo’s documentation also describes closing production at the final operation and completing required quality checks before the manufacturing order closes. This is a useful guard against a common misunderstanding: the last touch at a workstation is not identical to completion of every record in the order chain. In our sample Odoo flow, finishing work orders, completing the manufacturing order and validating the warehouse delivery are distinct steps.

Shop Floor documentation also describes the ability to create a quality alert from a work order card. It does not follow that pressing the button creates a working escalation procedure. Someone must decide who reviews the alert, whether the part can continue and where the resolution is recorded. Those are operating decisions. Without them, the screen may capture the problem but leave the response to an informal conversation.

For a first trial, follow one manufacturing order from both sides of the process. Check component availability on the manufacturing order. Check the operation sequence in its work orders. At the station, verify that the person on the job has selected the right operator profile and has started the right card. When the work ends, compare the entry with the actual handoff, then inspect the manufacturing order separately. Do not assume that a network outage will be handled safely or that entries will synchronize later; test that behavior in your own installation before designing a process around it.

The point of a shop floor screen is not to make every movement look instantaneous. It is to make the boundary between “waiting,” “started” and “finished” mean the same thing to the workshop and the planner. If you are mapping those boundaries into Odoo, the Fabrika Yazılım Odoo services and module catalogue offers a useful view of the related manufacturing records.

Verification note: The operation and time entry flow was checked against our sample Odoo implementation. Shop Floor views and operator behavior were checked against Odoo’s application documentation; the Shop Floor interface was not separately tested in our demo.