Industry · Chemical manufacturing

Batch traceability and COAs for chemical manufacturers in Odoo

One example batch, followed from raw-material receipt to a shipped drum, then traced back again for a recall. What Odoo does as standard, what needs an Enterprise app, and what we build as custom work.

By Octagotech Team8 min read

Key takeaways

  • Lot tracking, expiry dates and FEFO removal are standard Odoo Inventory.
  • Quality control points, PLM, Documents and Barcode are Enterprise apps.
  • A certificate of analysis is a custom report built from the batch's own test results.
  • GHS labels and hazmat fields are custom work, or stay in your labeling software.
  • A recall starts from one traceability report: lot back to raw materials, forward to customers.

Traceability in a chemical plant comes down to one question asked in two directions. Which raw-material lots went into this drum? And which customers received drums made from this raw-material lot? When formulas live in a spreadsheet, batch sheets on a clipboard and certificates of analysis in Word, answering either one takes a day. In Odoo, both answers come from records the plant creates while it works, provided the configuration is right before the first batch.

This article follows one batch through Odoo, step by step. The product, lot numbers and quantities are hypothetical, chosen to look like a typical specialty chemicals plant. Where a step uses an Enterprise app or needs custom work, we say so.

The setup: five decisions before the first batch

Traceability is decided in configuration, not at recall time. Before any batch runs, five things need to be in place.

  • Lots on every tracked product. Turn on lots and serial numbers in Inventory, and track raw materials and finished products by lot. Any untracked input is a gap in the chain.
  • Expiration dates. Switch them on and give each product its shelf life, so Odoo calculates expiry, best-before, removal and alert dates for each new lot.
  • FEFO removal. Set first expired, first out as the removal strategy on the product category, so reservations take the lot that expires first.
  • Formula BOMs. Load each formula as a bill of materials in the units you work in, with by-products where the process makes them.
  • Quality control points (Enterprise). Define checks on receipts and on the manufacturing operation, with the limits your specifications set.

Step 1: receiving the raw material

A delivery of resin arrives with the supplier's lot number and the supplier's COA. On the receipt, the warehouse records the lot, R-2291 in our example. Odoo's lot record is designed to hold the manufacturer's lot number, with a separate internal reference if you number lots your own way, so the supplier's number is never lost. With the Barcode app (Enterprise), the receiver scans instead of typing.

The expiry date is calculated from the product's shelf life when the lot is created, and can be overwritten with the date on the supplier's paperwork. If the receipt has a quality control point, the check opens before the material is accepted: a pass-fail check that the supplier COA matches your purchase specification, or a measurement check if your lab re-tests on arrival. With three-step receipts, the material waits in a quality location, out of production's reach, until the check passes and it moves to stock. A failed check can raise a quality alert on the lot.

Step 2: making the batch

Production creates a manufacturing order, WH/MO/00057, for a 1,000 kg batch. Odoo scales the formula BOM to the quantity entered, so every component line shows what this batch needs. The operator records the lots actually consumed, R-2291 among them, and the real quantities. If the BOM's consumption setting is set to warn, a batch whose quantities differ from the formula raises a warning before the order closes.

Where the process makes a by-product, it sits on the same BOM and is recorded on the same order. Give it a cost share and it carries part of the batch cost, which is how Odoo handles co-products.

The finished batch gets its own lot, B-0917, created on the manufacturing order, with its expiry calculated from the product's shelf life. From this point the link is permanent: B-0917 knows which component lots went into it. With PLM (Enterprise), the formula itself is under change control. Changes run as engineering change orders, QA approves a new version before it goes live, and earlier versions are archived rather than overwritten.

Step 3: testing the batch and building the COA

A quality control point on the manufacturing operation asks for one measurement check per test in the specification: viscosity, pH, solids content, whatever your product sheet lists. Each measurement check carries a norm and a tolerance, so an out-of-spec result fails the check at once and can raise a quality alert on the batch. The results are stored on the manufacturing order, with who recorded them and when.

That is the data a certificate of analysis needs, but Odoo does not print a COA as standard. We build it as a custom QWeb report. It reads the batch's measured results and the specification limits, lays them out in your format or a customer's required one, and prints for each lot on the delivery. Nobody retypes a number from the lab notebook, which removes the typo that ships with the drum.

Scope the COA early. Collect the COA formats your customers require during scoping, not after go-live. Every test that must appear on a certificate has to exist as a quality check first, so the list of tests and the list of control points are the same list.

Step 4: filling, labeling and storing

The batch is filled into 200 kg drums. With packages switched on, each drum can be tracked as a package holding lot B-0917, and product packagings (merged into units of measure in Odoo 19) let sales quote by the drum while stock is kept in kilograms. Converting between weight and volume depends on each product's density, which Odoo's units of measure do not model, so plants that sell by the liter get a density-based conversion as custom work.

The drum label is where the standard system stops. GHS labels with pictograms and hazard statements are either a custom label report in Odoo or stay in the labeling software you already use, fed with the lot and expiry. UN numbers and hazard classes become custom product fields. The current SDS for each product lives in Documents (Enterprise), with replaced versions kept in the file history. Odoo stores the SDS. It does not write it.

Step 5: shipping earliest expiry first

A customer orders four drums. With FEFO as the removal strategy, the delivery reserves the lot that expires first, not the newest batch on the shelf. The picker confirms or scans the lot, and the delivery records exactly which lots left the building. An Inventory setting prints those lot numbers on the delivery slip, and the custom COA prints alongside it for each lot shipped.

The recall: tracing lot R-2291

Months later, in our example, the resin supplier reports a contamination problem with lot R-2291. The question is which customers received product made from it.

Open lot R-2291 and its traceability report. It lists every move of that lot: the receipt, the quality location, and its consumption on WH/MO/00057 and any other order that used it. Expand the manufacturing order to reach the finished lot, B-0917, and from B-0917 to every delivery and customer it went to. A backward trace works the same way, from a finished lot to its components and their suppliers.

Run the trace on each affected supplier lot and the result is the recall list: finished lots, customers, delivery dates and quantities. Stock still on hand shows up in the same trace, so it can be moved to a quarantine location before anyone ships it. For plants with many products and multi-level batches, a saved search or a small custom report can list every customer delivery for a set of affected lots at once. The data is already in Odoo. The report saves the clicking.

What is standard, Enterprise and custom

Here is where each capability comes from.

CapabilityWhere it comes from
Lot tracking, expiry dates, FEFO removalStandard Inventory, Community and Enterprise
Formula BOMs with by-products and cost sharesStandard Manufacturing
Traceability report, lots on delivery slipsStandard Inventory
Quality control points and alertsQuality app (Enterprise)
Formula change orders and versionsPLM app (Enterprise)
SDS storage with file historyDocuments app (Enterprise)
Lot scanning at receipt and dispatchBarcode app (Enterprise)
Certificate of analysisCustom QWeb report
GHS labelsCustom label report, or your labeling software
UN number, hazard class, density conversion, retest dateCustom fields and logic
Electronic batch record with signaturesCustom work

None of this makes a plant compliant with any regulation. Odoo records what happened. Your QA procedures and regulatory advisors decide whether that record meets the rules you work under.

Our work in this sector

Our chemical sector experience so far is an Odoo version migration, not a new build. SF Dyes, a dye manufacturer, moved from Odoo 13 to 18 with us: every custom module was rewritten, QWeb reports were built for purchase orders, deliveries and production batches, and barcode scanning went live at receiving, production and dispatch. For a new build, the configuration above fits inside the plan on our Odoo for chemical manufacturing page. We use AI across configuration, development and testing to shorten delivery, and a plant with many formulas to clean up can take longer.

Frequently asked questions

Can Odoo print a certificate of analysis?

Not as standard. Quality checks, an Enterprise app, record each batch's measured results, and we build the COA as a custom QWeb report that prints them for the shipped lot, in your layout or a customer's required format.

Is lot traceability available in Odoo Community?

Yes. Lot tracking, expiration dates, FEFO removal and the traceability report are standard in Community and Enterprise. Quality control points, PLM, Documents and the Barcode app are Enterprise.

Can Odoo track retest dates as well as expiry dates?

Each lot carries expiry, best-before, removal and alert dates. Odoo has no separate retest-date field, so we use the alert date for retest reminders or add a custom field if you track both.

Does using Odoo make a chemical plant compliant?

No software does that on its own. Odoo keeps the lot, test and shipment records. Your QA procedures and regulatory advisors decide whether those records meet the rules you work under.

Octagotech Team

Certified Odoo Ready partner · San Francisco, New York, Ahmedabad and Rajkot

We configure Odoo Manufacturing, Inventory and Quality for batch plants, and say in the proposal which parts are standard, Enterprise or custom. About Octagotech, Odoo Ready partner.

Trace your next recall from one report

The first call takes 30 minutes.

Or email sales@octagotech.com