Industry · Pet
Pet food traceability in Odoo MRP: from ingredient lot to finished bag
When a supplier calls about a bad lot of chicken meal, you need to know which batches used it and who received them. Here is how Odoo Manufacturing, Inventory and Quality answer that from one report, and what Odoo does not do for you, label compliance included.
Key takeaways
- Model each formula as a bill of materials, with the bulk batch and the packaging step on separate levels.
- Track lots on every ingredient and finished product from the first receipt. Traceability cannot be backfilled.
- Lots, expiry dates and FEFO are in Community. Quality checks and PLM formula control are Enterprise.
- The traceability report follows a lot back to its ingredients and forward to every delivery.
- Odoo stores label data and prints labels through a custom report. It does not check AAFCO or state compliance.
Pet food and treat makers run a batch process with a retail product at the end. Ingredients arrive in totes and bags with supplier lot numbers. A formula turns them into a batch, the batch becomes bags with a best-by date, and the bags go to distributors, stores and, more and more, straight to consumers. Every step is a place where the lot trail can break, usually at a clipboard or a spreadsheet.
A recall is where that break costs the most. When an ingredient supplier reports a problem lot, you need to know quickly which batches used it, which finished lots came out and who received them. US rules for animal food already expect records one step back (who supplied each ingredient) and one step forward (who received each product), and many facilities also need a written recall plan under the FSMA animal food rule. Your regulatory lead decides what applies to your plant. The ERP's job is to make the records complete.
This article walks through how we set up Odoo MRP for that job: formulas, lots, expiry, quality checks, the recall trace, co-packers and labels. The same pattern runs in other batch plants; our chemical and batch manufacturing page covers the version with certificates of analysis and hazard documents.
Formulas as bills of materials
Each formula is a bill of materials (BOM) with components in the units you buy them in: kilograms of chicken meal, brown rice and fish oil, grams of vitamin premix. The BOM is written for a reference batch size, say 2,000 kg, and a manufacturing order scales every component to the quantity you actually make.
We recommend modeling two levels. The first BOM makes the bulk product, kibble or treats in kilograms, as one batch. The second is the packaging BOM: bulk product, bag, label and any insert, producing finished bags of one size. Splitting them means one batch can fill 5-pound, 15-pound and 30-pound bags, and each finished lot still points back to the batch it came from.
By-products fit on the same BOM when your process makes them. Fines that go back into a later batch as rework, for example, get their own lot, so the rework is traceable too. Decide the costing method before the first batch is posted; FIFO is a common choice for lot-driven food production, and changing it later means revaluing inventory.
Formula changes need control. On Community, you keep one active BOM per formula and archive the old versions. On Enterprise, the PLM app runs changes as engineering change orders: a new version is drafted, approved by QA, then made active, and earlier versions stay on file. If you use formulation software for nutrient balancing or least-cost formulation, keep it. Odoo does not balance nutrients. It takes the approved formula and runs production from it.
Lot tracking from ingredient to finished bag
Traceability in Odoo starts with one setting, Lots & Serial Numbers, and one decision per product: track by lots. Turn it on for every ingredient, the bulk product and every finished SKU. Track packaging too if a bag or label defect would matter in a recall.
After that, the trail builds itself, as long as every step records lots:
- Receiving. Each ingredient receipt records the supplier's lot number, or your own lot if you relabel, and its expiry date.
- Batching. The manufacturing order for the bulk product lists which ingredient lots were consumed. Odoo proposes lots by your removal strategy, and the operator confirms or changes them before the order is closed.
- Packaging. The packaging order consumes the bulk lot and produces a finished lot, which is the code printed on the bag.
- Shipping. Every delivery records which finished lots went to which customer.
The one rule we hold to in scoping: lots are recorded from the first receipt after go-live, and opening stock is loaded by lot. Traceability cannot be backfilled for stock that went in without one.
Agree a lot code format before go-live too. A code that carries the plant, line and production date is easier for a distributor to read over the phone than a system sequence.
Expiry dates and FEFO
With expiration dates switched on in the Inventory settings, each lot carries four dates: expiry, best before, removal and alert. On each product you set the shelf life in days from production, and how many days before expiry the best-before, removal and alert dates fall, so a finished lot gets its dates when it is created. For ingredients, you enter the supplier's dates at receipt.
Set the removal strategy to first-expiry-first-out (FEFO) for ingredients and finished goods. Odoo then proposes the earliest-expiring lot in production and in picking, and warns before an expired lot is consumed or shipped. The alert date gives purchasing and sales time to act on slow-moving lots before they become write-offs.
The best-by date printed on the bag should come from the lot, not from someone with a date stamp. That is a label question, covered below.
Quality checks at receiving and in production
Even without the Quality app, a warehouse can keep incoming goods apart until they are released. A three-step receipt (input, then quality control, then stock) puts every ingredient delivery in a quality location first, and that works on Community.
The Quality app, which is Enterprise, adds the checks themselves. Control points trigger on the operations you choose:
- Receiving: confirm the supplier's certificate of analysis is attached, and record measurements such as moisture against your limits.
- In production: measurement checks at set steps, for example moisture after the dryer or kibble density, with the tolerance on the check.
- Before release: a pass or fail step for your metal detection check or retained sample.
A failed check can raise a quality alert on that lot, and you decide whether it moves on to stock, goes back to the supplier or is scrapped. Measured values stay on the check with the lot, which is what a custom certificate of analysis report prints from.
Running a recall trace
Here is what a recall trace looks like in Odoo, using a hypothetical ingredient lot:
- Open the ingredient lot, say chicken meal lot CM-0412, and open its traceability report.
- Downstream, the report lists every manufacturing order that consumed the lot, the bulk lots those orders produced, the packaging orders that used them and the finished lots that came out.
- Follow each finished lot to its deliveries: customer, date and quantity. Export that list for your recall notices.
- Move remaining stock of the affected lots to a quarantine location outside your sellable stock, or scrap it, so it cannot be picked.
- Record returns against the original deliveries, so returned bags come back into the same lots.
The same report works backward from a customer complaint: start from the lot code on the bag and trace upstream to every ingredient lot and supplier.
Run a mock recall before go-live. Do it during user acceptance testing, then on a schedule. If the trace needs anything outside Odoo to finish, you have found the gap while it is still cheap to fix.
Co-packers and subcontracting
Many pet food brands make some or all of their products at a co-packer. Odoo's subcontracting flow handles this in both editions. The finished product gets a subcontracting BOM that names the co-packer. A purchase order to the co-packer creates a matching subcontract manufacturing order in the background, and receiving the finished goods consumes the components on record.
Traceability then depends on who owns the ingredients:
- You supply the ingredients. Components are sent to the co-packer, or shipped straight from your suppliers with the dropship-to-subcontractor route. At receipt you record which ingredient lots were used and the finished lot, so the trail is complete in your database.
- The co-packer buys its own ingredients. Those lots are not in your Odoo. You record the co-packer's finished lot, and your contract should require the co-packer to trace ingredient lots on request within a set time.
Labels: what Odoo stores and what it does not check
A pet food label carries regulated content: the product name, a guaranteed analysis (minimum crude protein and fat, maximum crude fiber and moisture), an ingredient statement in descending order by weight, and often a calorie statement and feeding directions. Odoo can hold all of it as fields on the product, added with Studio on Enterprise or a small module on Community. It can print it too. Standard label printing covers product and lot barcode labels, and a full bag or case label with that content is a custom report, as a PDF or in the format your thermal printers take. The lot code and best-by date on the label come from the finished lot.
What Odoo does not do is check the content. It does not calculate the guaranteed analysis from the formula, and it does not validate a label against AAFCO model regulations, state feed laws or FDA requirements. Those values come from your lab and your nutritionist, and label approval stays with your regulatory lead. What Odoo can do is control change: store the approved label text on the product, and change it only through the same approval as a formula change, which is a PLM change order if you run Enterprise.
Community or Enterprise for a pet food plant
| Capability | Community | Enterprise |
|---|---|---|
| Formula BOMs, by-products, manufacturing orders | Included | Included |
| Lot tracking and the traceability report | Included | Included |
| Expiry dates and FEFO removal | Included | Included |
| Subcontracting for co-packers | Included | Included |
| Three-step receipt with a quality location | Included | Included |
| Quality control points and alerts | Not included | Included |
| PLM formula change control | Not included | Included |
| Shop Floor tablets and the Barcode app | Not included | Included |
| Studio (custom fields without code) | Not included | Included |
| Full Accounting | Invoicing only | Included |
For most pet food plants, Quality is the deciding app: the checks and their results on each lot are what a customer audit or a certificate request draws on. Our Odoo MRP guide and the Community vs Enterprise comparison cover the rest of the trade-off.
Common questions
Does Odoo check pet food labels for AAFCO compliance?
No. Odoo stores the label data and prints labels through a custom report, with the lot code and best-by date taken from the finished lot. It does not calculate the guaranteed analysis or validate a label against AAFCO, state or FDA requirements; that stays with your lab and your regulatory lead.
Is lot traceability available in Odoo Community?
Yes. Lot tracking, expiry dates, FEFO removal, the traceability report and subcontracting all work in Community. Quality checks, PLM change control, Shop Floor and Studio are Enterprise.
Can Odoo trace pet food made by a co-packer?
Yes, with subcontracting. At receipt you record the finished lot and, if you supplied the ingredients, which ingredient lots were used. If the co-packer buys its own ingredients, you record its finished lot and rely on its records for the ingredient trace.
Where to start
If you are scoping Odoo for a pet food or treat plant, gather your formula count, one recent batch record and the ingredient lot you would least like to trace by hand. Bring them when you book a discovery call. Our manufacturing consulting work sets up BOMs, lots and costing in standard Odoo before anything custom is built, at one fixed price agreed before kickoff. For the store side of a pet business, read Odoo for pet stores, and for the whole picture, Odoo for the pet industry.
Making pet food or treats?
Bring your formula count and one batch record to a 30-minute scoping conversation.
Book a discovery callKeep going
Related case, pages and articles
From 3-day planning cycles to same-day scheduling
A custom-parts manufacturer with 85 staff moved 340 BOMs, 12 work centers and its planning from spreadsheets into Odoo MRP in 14 weeks.
From the clinic to the kitchen
Pet retail, vet clinics, pet food makers and subscription sellers on one Odoo database.
Odoo for the pet industryBatch plants that mix and fill
Formulas as BOMs, lots with expiry and FEFO, quality checks and custom COA reports.
Odoo for chemical manufacturingMRP your planners trust
BOMs, routings, work centers, costing and replenishment, set up before any custom code.
Odoo manufacturing consulting IndustryOdoo for pet stores: one POS across locations
Shared stock, loyalty, autoship, click-and-collect and the end-of-day close.
Trace one lot with us
The first call takes 30 minutes.
Or email sales@octagotech.com- USA +1 917 254 9416
- India +91 8153897751