What is the best manufacturing operating system?

The phrase is newer than ERP and vendors use it loosely. Strip the marketing and it describes three habits. First, one data model: an item, a work order and a purchase order are the same record wherever they appear, so stock, cost and accounts never disagree. Second, the shop floor is a first-class user, with job cards, scanning and labour logging rather than office-only screens. Third, the people who run the shop can change the system, adding fields and rules without a developer. Any product that shows all three can fairly use the label. Any product that fails one is an ERP, an MRP or an inventory tool wearing a new name.

Run these in the demo with your own records.

• Issue material to a work order and check the stock ledger shows the movement at once, with the cost it carried.
• Close a job and read its cost per unit without a report being built for you.
• Log labour at a work centre from a job card and see it land on the job.
• Add a custom field to the work order form and a rule that fires on a status change, yourself, during the demo.
• Export items, customers, vendors and transactions to CSV and open the file.

The categories overlap, and the names matter less than what the system records. This table gives the usual centre of gravity of each. A product may sit in two rows at once; what matters is which row it was designed around.

A system built around this idea suits shops that want one place for everything and are small enough to run it themselves. It is a poor fit in three cases. A large plant with hundreds of users and a dedicated IT team will want the depth and partner network of a mid-market or enterprise ERP. A process manufacturer whose unit of work is a batch with a formula, not a work order with a routing, needs a system designed for that. A company whose contracts require software on its own servers needs an on-premise product, and most manufacturing operating systems are cloud only.