Odoo Manufacturing, New Zealand

Recipes, batch sizes and yields in a discrete system

Odoo Manufacturing was designed around discrete production: a bill of materials lists components, and producing one unit consumes them. Food and dairy-adjacent production is closer to process manufacturing. A cheese batch starts with a volume of milk and ends with a variable weight of cheese and whey. An ice cream run produces a base that is then flavored and packed into several pack sizes.

Odoo can handle much of this with careful modeling:

• Recipes set at the plant's usual batch quantity, so a production order for half or double a batch scales ingredients proportionally.
• Intermediate products such as a base, mix or curd, produced and stocked as their own items, then consumed in packing orders.
• By-products recorded as secondary outputs on the BoM, with a share of cost assigned if your accountant wants one.
• Actual consumption adjusted on each order, so yield differences are captured rather than assumed.

What is harder: true catch weight, where items are sold by variable weight but counted in units; potency or solids-based formulation adjustments; and complex co-product cost allocation. These may need add-ons, custom work or a process-focused system. I test your hardest recipes first, because a design that only works for the simple products will fail when production gets busy. For how Odoo treats work orders and routings outside the food context, read the Odoo Manufacturing overview.

Co-packers, contract production and packing for others

Many New Zealand food and beverage brands do not own all of their production. A beverage brand may have product canned by a contract packer, a snack brand may use a co-manufacturer, and a nutritional powder brand may have blending and canning done by a licensed facility. Some producers are on the other side, packing for other brands as well as their own.

For production you outsource, Odoo's subcontracting feature fits well:

• A purchase order to the co-packer for finished goods can trigger the transfer of ingredients and packaging you supply.
• The finished goods receipt consumes those components from the subcontractor's location, so your stock stays accurate.
• The co-packer's fee adds to product cost, alongside your own materials.
• Batch numbers recorded on receipt keep traceability intact even though production happened elsewhere.

I agree with you how often stock held at the co-packer is counted and reconciled, and how rejected or short batches are recorded. For production you do for others, the questions are whether the brand supplies materials, how its stock is kept separate from yours, and how each batch is reported back. That stock ownership design connects to the provider and cold store setup on my Odoo Inventory in New Zealand page.

Allergens, quality checks and batch records

A New Zealand food manufacturer's food safety program will expect controls on allergens, critical control points and batch records. The program itself is designed by your food safety consultant and verified externally; Odoo's job is to support the records and controls, not to replace the plan.

Within Odoo, I set up:

• Allergen attributes on ingredients and finished products, so a product's allergen profile follows from its recipe and changes are visible when a supplier substitutes an ingredient.
• Production sequencing guidance, for example running allergen-free products before those containing nuts or dairy on shared lines, recorded as work order instructions agreed with your quality lead.
• Quality control points such as temperature checks, metal detection confirmations or label verification at defined operations, using the Quality app, which is Enterprise. Community users can record some checks as work order steps or through third-party modules.
• Batch release, holding finished goods in a quarantine location until tests are passed.

Small engineering manufacturers have different quality needs: inspection of welds, dimensions or finishes, and serial numbers for warranty. The same tools apply with different control points. I confirm the edition and version for the specific checks you need before relying on them, and keep the number of mandatory checks realistic for the people on the line.

Batch costing, and why manufacturing tests the Xero decision

Owners of growing New Zealand producers usually want one answer from manufacturing data: what does a batch, a case or a unit really cost? Odoo builds that from ingredient and packaging costs on the BoM, labor and machine time through work center rates, and any overhead included in those rates. With your accountant, I agree the costing method per product category, how yield and price variances are treated, and how work center rates are reviewed as wages and energy costs change.

Manufacturing is also where keeping Xero as the ledger becomes awkward. Production creates many stock and valuation movements: ingredients consumed, intermediate products produced, finished goods valued, variances posted. Odoo Accounting records these automatically when perpetual valuation is used. If Xero is the ledger, those movements must be summarized and transferred, usually by a connector or a periodic journal, and reconciling stock value across two systems becomes a monthly task.

That does not mean Xero must go. Some producers keep Xero with periodic stock journals and accept the extra reconciliation. Others move to Odoo Accounting when production starts in Odoo. I lay out both options with your accountant, including bank feeds, payroll and reporting habits. The accounting side is detailed on Odoo Accounting in New Zealand, and job costing in general on ERP for job costing.

Questions for the implementer, and plants Odoo does not suit

Several points change scope and cost, so put them to Odoo or the implementer in writing for the exact version and hosting you plan:

• Enterprise holds the Quality app, product lifecycle management, forecast-based production scheduling and the richer tablet screens for operators; decide which of these the plant truly relies on.
• How the version handles by-products, scaling batches and expiry dates on produced lots.
• Whether add-ons for catch weight, formulation or your Xero connector are maintained for your version and can run on your hosting, given that Odoo Online restricts third-party modules.
• Whether stock valuation accounts and GST in the local localization suit your accountant, and whether an Australian company would share the database.

Odoo is probably the wrong tool for large dairy or meat processors with complex co-products, regulatory export systems and high-volume continuous lines, which tend to run specialist process systems. It may also be too much for a small kitchen producing a few products in simple batches, where a production add-on to Xero could do. For machine-intensive plants needing finite scheduling, a specialist planning tool beside Odoo is worth considering. For the overall decision, read Odoo in New Zealand; for broader context, my New Zealand overview and food and beverage ERP pages, and ERP advice for New Zealand businesses.