Odoo Manufacturing Consultant, Australia

Replenishment built around long and variable import lead times

In Odoo, purchase and manufacturing suggestions come from reordering rules, make-to-order routes and the lead times attached to suppliers and products. If those lead times assume a fortnight when the real figure is a long sea voyage plus port delays, planners see suggestions too late and stop trusting the system. For Australian plants I rebuild the planning data from evidence:

• Vendor lead times taken from actual purchase-to-receipt history for each supplier, not from their quotes.
• Purchase security days for suppliers on routes that are often disrupted, so orders go out earlier without inflating every item.
• Minimum and maximum quantities sized to cartons, pallets or container loads, and to the shelf life of perishable inputs.
• The replenishment list reviewed by a planner on a fixed rhythm, ordering once or automating per item where your version offers that choice, with automation reserved for items whose data has proven reliable.

For seasonal products, such as food lines ahead of summer or agricultural equipment before planting, the Master Production Schedule in Enterprise lets planners set production by period and see component demand early enough to place import orders. Smaller ranges can manage with rules and manual orders. The mechanics are covered on my Odoo Manufacturing and Odoo Inventory pages.

Producing in one state, selling in all of them

Many Australian manufacturers make product in one location and hold it in warehouses or third-party logistics sites in other states. Odoo can model each site as a warehouse with resupply routes from the plant, so a reordering rule in Perth or Brisbane triggers a transfer from the factory warehouse, and the factory's own rules then trigger production. Set up well, the planner sees national demand driving production rather than guessing from the factory's stock alone.

Design points I settle with operations:

• Whether interstate sites are full Odoo warehouses or locations fed from a logistics provider's system, which changes the integration work.
• Transit times between states, entered as lead times on the resupply route so transfers are planned realistically.
• How stock in transit is shown, since a truck or rail container crossing the Nullarbor can be away for days.
• Which finished goods are made to stock nationally and which are made to order for a particular customer.

Where a logistics provider runs the remote warehouse, stock updates normally come through an integration or file exchange. I scope that with the provider early under ERP integration, because a manual daily spreadsheet quickly undermines the planning logic and puts planners back on guesswork.

Batch dates, quality release and recall readiness

Food, beverage, cosmetics and supplement makers in Australia work within the Food Standards Code or the relevant product regulator, and supermarket customers expect recognized food safety certification and fast recalls. Engineering suppliers to mining and infrastructure customers face their own inspection and certificate demands. The Odoo setup that supports this:

• Lots with dates: use-by or best-before, removal and alert dates on lots, so stock nearing its date is flagged and expired stock is not picked. Check that the expiry features are active in your edition and version.
• Release control: receipts and finished batches held in a quality location until checks pass.
• Quality control points: checks at receipt, at mixing or filling, and before dispatch, with measurements recorded against the lot. This uses the Enterprise Quality app.
• Documents: certificates of analysis from suppliers attached to incoming lots.

Allergen and specification management usually stays in a dedicated food safety system, with Odoo holding the operational record. During acceptance testing I run a timed trace from a finished batch back to ingredient lots and forward to customers; if it is slow in testing, it will be slower during a real recall. The approach is part of my testing and UAT work.

Co-packers, outside finishers and shift-loaded labor costs

Australian brands often outsource part of production. A beverage or food company may use a co-packer, a cosmetics brand a contract blender, a fabricator a powder coater or galvanizer. Odoo's subcontracting handles this through a subcontracting BoM: you supply components, or have them delivered straight to the third party, and the receipt of finished goods records consumption and the service charge. For a finishing step between two in-house steps, I make the finished part its own item, so stock at the coater stays visible.

Labor costing is the other Australian specific. Award loadings make night and weekend production more expensive, and averaging that away hides which runs earn their margin. Odoo work centers carry an hourly cost, and depending on version employee costs can also apply to work order time. Options I discuss with your accountant:

• A blended rate per work center, reviewed periodically, when shift patterns are stable.
• Separate work centers or rates for weekend runs, where the difference is material to pricing.
• Leaving loadings in overhead, with a monthly analysis of penalty hours by line.

Pay calculation and Single Touch Payroll reporting stay in your payroll system; Odoo only needs accurate hours by work order. The finance side is on Odoo Accounting Australia.

Edition choice and when Odoo MRP is not the answer in Australia

For Australian manufacturers, the Community versus Enterprise choice mostly comes down to manufacturing features. Quality, the Master Production Schedule, PLM, barcode scanning and the tablet shop floor screens are generally Enterprise, while BoMs, manufacturing orders, work orders and subcontracting are in Community. Check the current list on odoo.com, and if third-party modules are proposed to fill gaps, ask who maintains them through upgrades.

Odoo MRP is the wrong tool when:

• You run a winery, brewery or distillery where blending, vessel tracking, volumes changing over time and excise records are central. Specialist software usually fits better.
• Meat or seafood processing needs catch weight and carcass yield breakdowns.
• Finite scheduling of shared filling or packing lines, with allergen-driven sequencing, is the main planning problem.
• Engineer-to-order mining equipment projects need full project scheduling and costing beyond what manufacturing orders and analytic accounts provide.

In those cases I compare options neutrally before you commit, starting from ERPNext vs Odoo for manufacturing. The national Odoo picture is on Odoo consultant Australia, plant-level advice on manufacturing ERP Australia, and more on ERP consultant Australia and the Australia hub.