This is a build-to-order module, not an instant download. After purchase we start with a scoping workshop to map your BOMs, HACCP plan, allergens, and receiving process, then design, build, and test the module against your target Odoo version. Typical lead time is one working week depending on the complexity of your product families and CCP requirements. You approve a written functional specification before development begins, and we install on your instance and validate with your data before go-live.

Every engagement includes a defined post-go-live support and bug-fix window with agreed response times, covering fixes to the functionality we delivered. You receive the full module source, so you own it outright. We also document an upgrade path so the module can move to future Odoo releases (for example from 18 to 19), and we offer ongoing support or version-migration work as a follow-on engagement when you need it.

The module is built and tested against Odoo 17, 18, or 19 — you tell us your version — and runs on both Community and Enterprise. We extend the standard Manufacturing (MRP) and Inventory apps rather than replace them, so you keep native work orders, stock moves, and reporting. If a specific feature depends on an Enterprise-only capability, we flag it during scoping and offer a Community-compatible alternative.

Odoo core gives you lots/serials, expiration dates, and basic upstream/downstream traceability reports, and that is a genuine foundation we build on. What it does not do is enforce FEFO at reservation, roll allergens up through the BOM with cross-contamination flags, gate work orders on HACCP critical-control-point checks, or produce a one-click recall dossier and affected-customer list formatted for a regulator. This module adds that food-safety layer using proper Odoo models, compute fields, automated actions, and QWeb reports.

Yes. All lot, allergen, expiry, and genealogy data is exposed over Odoo's standard XML-RPC and JSON-RPC APIs, so external systems can read and write it programmatically. During scoping we identify your integration points — GS1/allergen label printing, LIMS Certificate-of-Analysis capture, or pushing allergen data to an e-commerce channel — and either configure the API endpoints or build the connector as part of the engagement.

You select the affected lot — a supplier lot, an intermediate batch, or a finished-goods lot — and run the recall report. The module walks the full genealogy in both directions: backward to the raw materials and suppliers, and forward through every batch and work order to the finished lots and the specific customers who received them. It produces a QWeb PDF recall dossier and an affected-customer list, so a one-up/one-down trace that used to take days of spreadsheet work is completed in minutes and is ready for FSSAI, HACCP, or FDA submission.