Production
BOM, work orders, and batch costing that consume stock into the ledger.
What you get
- BOM & work orders — Recipes and batches with cost that survives month-end.
- Manufacturing & central kitchen — The same engine for factories and recipe-driven kitchens.
- Tied to purchases & pay — Materials from AP and labour from HR land on the same job truth.
Who runs this
- Distribution & wholesale
- Retail (multi-branch)
- Logistics & freight forwarding
- Contracting & construction
Questions
Is this a full MES with machine signals? No — Omnizone covers BOM, work orders, and costing — not shop-floor PLC control.
Operators plan and cost batches in the ERP. Machine telemetry stays with specialised MES tools.
Do work orders move stock? Yes — issues and receipts update inventory and cost.
Components leave stock; finished goods arrive with batch cost into WAC.
Can a central kitchen use the same module? Yes — recipes and batches use the same production engine.
Food and light manufacturing share inventory and ledger rules.
How does production meet VAT and CIT? COGS and inventory sit in the same books that feed statutory papers.
You do not export a production CSV into a separate tax file.
Is barcode / bin WMS required? No for basic production — warehouse bins wait on the WMS epic.
You can run work orders with location-level stock today; deep bin scanning is a later gate.
What about multi-currency materials? Purchases keep document currency; inventory and COGS keep LCY honesty.
Same FX rules as the rest of Omnizone finance.
What this does not do
- Replace a shop-floor MES or PLC historian
- Promise deep bin scanning before the warehouse epic publishes
- Run MRP for every possible constraint solver scenario
Connected to the rest of the system
FAQ
Does production post into inventory?
Yes — issues, receipts, and batch cost update stock and COGS in Omnizone.
Is this a MES?
No — BOM and work-order costing, not machine-level MES control.