Manufacturing
Batch manufacturing orders against versioned recipes, with work orders for charging, reaction, filtration, blending and packing.
Chemical manufacturing turns a recipe into a batch, and the batch rarely matches the recipe exactly. Yield moves, potency varies, and the gap between the two is where margin and compliance both live.
Odoo handles batch production, lot genealogy, quality checks and consumption against the recipe — and we are explicit about the places where process manufacturing needs development rather than configuration.
Businesses running Odoo with OdooBots
Odoo ERP for chemicals manages batch manufacturing, raw material lot traceability, quality control and the consumption that reveals yield. Bills of materials hold the recipe, manufacturing orders produce tracked batches, quality control points gate release, and lot genealogy links a dispatched drum back to every raw material lot it came from.
Odoo is a discrete manufacturing system used for batch work. Co-product cost allocation, potency-based consumption and continuous process control are the three places it genuinely needs development, and we name them before quoting.
Odoo connects what a chemical operation runs on: Manufacturing for batch production, Inventory for raw materials and finished goods with lot control, Quality for incoming and release testing, Purchase for sourcing, and Accounting for batch costing.
Batch manufacturing orders against versioned recipes, with work orders for charging, reaction, filtration, blending and packing.
Raw materials and finished goods by lot, with expiry where relevant, quarantine and released locations, and bulk-to-pack conversions.
Incoming inspection, in-process checks and certificate-of-analysis release testing, with results recorded against the lot.
Approved supplier lists, incoming quality gates and lead times that reflect import and hazardous transport constraints.
Safety data sheets, specifications and certificates held against the product and reachable by the people who need them.
Batch costing with yield variance visible, GST and e-invoice, and margin by product and customer.
A raw material lot arrives and is quarantined until quality releases it. A batch consumes released lots against the recipe, actual output is recorded against expected, and the finished lot carries a genealogy a regulator or a customer can follow.
These are the configuration decisions that are cheap to make now and structural to change later. We walk through each one before a single record is migrated.
Whether incoming material lands in quarantine until released. Without it, unreleased material can be consumed by a manufacturing order and the whole quality system is theatre.
Whether variance posts to cost or is only recorded. Posting it makes batch costing honest and makes some months look worse than people expect.
Odoo supports by-products but not automatic cost allocation by market value. If you have genuine co-products, this needs development and we price it up front.
How a bulk batch becomes drums, cans or bottles, and whether the pack lot links back to the bulk lot.
Which materials are lot-tracked. In chemicals this is usually almost everything, which makes receipt and issue discipline the real project.
We run a mock recall during testing: trace a dispatched lot back to raw materials, timed. If it takes hours, the configuration is not finished.
Who keeps safety data sheets current and where they live, so the version a customer receives is the current one.
The right configuration depends on how your business actually operates, not on your sector label. Two companies with the same description on paper often need different warehouse steps, different approval chains and different reports.
We would rather say this before you buy licences than after. These are the areas where we scope real development, recommend a bolt-on, or tell you Odoo is the wrong tool.
Recipes where usable quantity depends on measured potency are not native. Custom fields and custom consumption logic are required.
Splitting batch cost across multiple saleable outputs by market value or yield needs development on manufacturing order valuation.
Odoo is discrete. Continuous plants with DCS or SCADA control need those systems; Odoo takes summarised output.
Hazardous substance registers and jurisdiction-specific returns are country-specific and usually custom.
Laboratory information management and automated result capture are specialist integrations.
Volume-by-level tank stock with temperature correction needs custom modelling.
Implementing Odoo for chemicals needs more than installing the applications. Your ERP should reflect how your operations actually run.
Understand your recipes, batch sizes, quality checkpoints, lot obligations, packing formats and any co-product or potency requirements.
Map receipt to release to dispatch onto Odoo, and settle quarantine flow and yield treatment before any stock is loaded.
Configure the applications above around your requirements rather than installing them at their defaults.
Prepare and migrate masters, open items and opening balances. Data cleaning is scoped explicitly, because it is usually the largest single task. See Odoo migration.
Connect the systems you are keeping and build only what configuration genuinely cannot reach. See integration and customization.
Your own team runs real transactions in a test database before go-live. Role-based training for the people who key them daily. See Odoo training.
Cutover planning, opening balance freeze, hypercare in the first weeks, then ongoing support and AMC.
We do not publish one implementation price, because the same application list costs very differently depending on the factors below. We do publish what moves the number, and the price is fixed in writing before work starts.
We say plainly where Odoo stops. Batch, lot genealogy and quality it handles well; potency-based consumption, co-product allocation and continuous process control need development. You get that list before you commit, not after.
Product capabilities stated on this page are documented by Odoo. The configuration advice and limitations come from our own implementations.
Tell us whether your process produces co-products and whether potency affects consumption. Those two answers decide whether this is configuration or development, and the diagnosis call is free.