Manufacturing with Odoo Community: What still needs an owner?

A small fabrication shop wants to give two more planners access to its production system. Not having to calculate a licence charge for each additional account is appealing. But those planners also need current bills of materials, appropriate permissions and production records that will still be available after a server failure. Odoo Community addresses the first concern. The others need operational decisions, whether or not the software itself is free to use.

Luke van Enkhuizen’s overview of open-source tools for metal fabricators points out that Odoo Community has manufacturing and no user limit. That makes it a useful candidate for a shop that wants to test a shared production system without committing to an Enterprise subscription for every person involved. The question here is not how to construct a bill of materials or link it to work orders. It is what the Community edition gives the shop, and what the shop must supply itself.

What does free actually remove?

Odoo describes Community as its open-source core and Enterprise as its licensed edition. Its public source repository contains the manufacturing module. A team can install that edition and set up a manufacturing workflow without buying a per-seat Enterprise subscription first. Adding another production user does not in itself introduce a Community licence fee.

That is not the same as a zero-cost production system. Somebody must run the server and database, manage updates, back up production records, review security access and deal with broken integrations. If the shop has no one to do that work internally, it needs outside help. Removing a software licence charge changes where money and time are spent; it does not remove the need for maintenance.

Nor does unlimited user count imply unlimited privileges. A cutting operator recording a completed operation, a planner arranging the queue and an administrator changing a product definition have different responsibilities. Create accounts around those responsibilities. Giving everybody administrator access because there is no seat limit makes it much harder to find the source of a mistaken change later.

Manufacturing is not one checkbox

Odoo’s edition comparison lists Manufacturing (MRP) along with other shop-floor and supply-chain capabilities. The extracted text of a comparison table does not always preserve which checkmark belongs to which edition, so it would be unsafe to infer the availability of every specific screen from that page alone. Test the workflow on the actual Community installation that the shop plans to operate.

One workshop may need to create manufacturing orders, check material requirements and record work against operations. Another may require a particular tablet-based control panel, detailed scheduling, integrated quality processes or maintenance triggers. Both might say they need “manufacturing,” but they are asking for different combinations of features. Before designing a process around a demonstration screen, confirm whether that screen is included in Community, requires Enterprise, or depends on an additional module.

List requirements as actions: an operator can see the next approved job; a planner can identify missing material. Note the version and installed modules for each test. A tick beside “MRP” is not enough evidence for a shift supervisor.

A modest test on the shop floor

Consider an illustrative sheet-metal shop making two sizes of cabinet. One order contains a few of the first size and a larger batch of the second. Material has not arrived for one size; cutting shares a machine; assembly happens on another shift. Start with this narrow product family rather than importing the whole catalogue into a fresh Odoo database.

Create a bill of materials for each size and open one manufacturing order. Compare the material requirement with the actual stock position. If the process uses operations, set up cutting and assembly separately. Sign in as a planner and then as a shop-floor user, and check whether each person can see and record what they need. Record what the system displays while material is missing and after cutting is complete. This is a test of the installed system, not a claim that Community automatically handles every exception in a real factory.

A failure in this pilot is useful evidence. If an operator cannot access the expected view, is it an access-rule issue, a missing module or a difference between editions? If the manufacturing order closes with an inaccurate material quantity, is the bill of materials wrong or is the recording practice unclear? Resolving those questions with one example costs less than discovering them during a busy production week.

A second pass should introduce a drawing revision after the order is opened. Which order still uses the earlier definition? Odoo holds records, but the workshop decides which one is authoritative. Access to the code will not settle a revision dispute.

More users mean more discipline

As more people use the same database, duplicated product cards become more consequential. One employee creates a new material code with an abbreviated name; another consumes stock under the older code. The system now shows two separate stock positions for what the team believes is one item. Upgrading the licence will not fix that. A product-code convention and an owner for master data will.

Before expanding the pilot, decide who creates product cards, approves bill-of-materials changes and corrects wrongly closed orders. Keep training orders separate from live stock. A practice order in a real production report can undermine confidence early.

Operations also need a recovery path. Odoo’s guide for switching from Community to Enterprise starts with a database backup. The same precaution matters when staying on Community and installing an update or third-party module. Take the backup before changing the environment, and test a restore in a separate instance. A backup file existing on disk is not evidence that a team can recover the jobs, users and stock movements it needs after a failure.

What is a sensible decision point?

The choice is not between a “free ERP” and a paid ERP in the abstract. Ask whether the selected product family can move from bill of materials to material checks, manufacturing order and the required shop-floor records in the edition actually installed. Check whether roles match the shop’s work division and whether a backup can be restored. List any missing capabilities and the accepted workaround or alternative module for each one.

If those questions have satisfactory answers, Community can be a credible starting point without a per-user subscription. If they do not, the absence of a licence fee does not compensate for a production process the team cannot reliably operate. What matters is the boundary between software capability and the work of keeping the production record trustworthy.

Sources: Luke van Enkhuizen’s overview of open-source manufacturing tools, Odoo’s edition comparison, the Odoo manufacturing module source, and Odoo’s Community-to-Enterprise migration guide. The workshop example is illustrative.