Los detalles del producto se muestran en inglés. Próximamente traducciones.
Datos rápidos
- Precio
- $499.00 USD
- Versiones de Odoo
- 17, 18, 19
- tiempo de configuración
- 20160 minutos
- Licencia
- Perpetuo único
- Idiomas
- 11 idiomas
Compra única
Production Batch & Lot Genealogy Traceability
Build-to-order Odoo module for full forward/backward lot genealogy — trace raw material to customer for recalls and audits.
$499.00USD
Sin pago ahora. Esto envía una solicitud de presupuesto a nuestro equipo; te responderemos por correo con precios y próximos pasos.
Características clave
Forward genealogy: from any raw-material or intermediate lot, expand every downstream MO, sub-assembly, finished-good lot and shipped customer delivery it ended up in
Backward genealogy: from any finished-good lot or serial, drill back through work orders and consumed components to every incoming supplier lot and receipt
Interactive OWL genealogy tree with expandable/collapsible nodes, colour-coded by product, lot state and quarantine flag, drillable straight to the source stock.move.line
Raw-material-to-finished-good traceability map spanning multi-level BOMs, phantom/kit BOMs, by-products and rework loops
One-click recall scope: select an affected input lot and instantly list every downstream lot, delivery order, invoice and customer contact in the blast radius
Recall worklist generation — export the impacted customer/quantity set to CSV/QWeb PDF and optionally raise follow-up activities per affected delivery
RMA and service-history unit traceability: from a returned serial, show its full build history plus prior repairs, warranty and field events
Automated action that watches quality checks (quality.check) and quarantines/blocks any lot whose upstream material fails, propagating the flag down the tree
Genealogy dossier: a branded QWeb report (PDF/HTML) reconstructing a lot's complete parentage and progeny for auditors and regulators
Computed traceability fields (parent lots, child lots, depth, consumed qty) via @api.depends, kept in sync on MO confirmation and delivery validation
XML-RPC/JSON-RPC endpoints so external MES/LIMS/supplier systems can query a lot's genealogy or recall scope programmatically
Security via ir.model.access.csv + record rules — per-plant and multi-company isolation so users only trace lots in their own warehouses
Search filters and grouping to answer 'which incoming lots reached customer X?' or 'which shipments contain component lot Y?' from the standard list view
Audit trail on genealogy queries and recall actions (mail.thread chatter) capturing who ran a trace and what scope was identified
Compatible with Odoo 17, 18 and 19, Community and Enterprise — extends native lot/serial and MRP models rather than forking them for clean upgrades
Sobre este producto
When a supplier defect surfaces or a regulator asks "where did every affected unit go?", stock-standard Odoo traceability leaves you clicking through stock.move.line records and exporting spreadsheets by hand. This build-to-order module gives regulated manufacturers a single, recall-ready genealogy layer on top of Odoo 17, 18 or 19 — reconstructing the complete parentage of any lot or serial in one view: from the raw-material lots you received, through every manufacturing order and work order that consumed them, to the finished-good lots and the exact customers who received them.
Por qué elegir Production Batch & Lot Genealogy Traceability
Forward genealogy: from any raw-material or intermediate lot, expand every downstream MO, sub-assembly, finished-good lot and shipped customer delivery it ended up in
Backward genealogy: from any finished-good lot or serial, drill back through work orders and consumed components to every incoming supplier lot and receipt
Interactive OWL genealogy tree with expandable/collapsible nodes, colour-coded by product, lot state and quarantine flag, drillable straight to the source stock.move.line
Raw-material-to-finished-good traceability map spanning multi-level BOMs, phantom/kit BOMs, by-products and rework loops
One-click recall scope: select an affected input lot and instantly list every downstream lot, delivery order, invoice and customer contact in the blast radius
Recall worklist generation — export the impacted customer/quantity set to CSV/QWeb PDF and optionally raise follow-up activities per affected delivery
ECOSIRE designs, builds, installs and supports this module for you. It is NOT an off-the-shelf apps.odoo.com download and there is no instant-download claim — after purchase our Odoo engineers scope your BOM structure, quality flows and regulatory context (FDA 21 CFR Part 11, EU 178/2002/FSMA, GMP, ISO 22000, medical-device UDI, or your own SOPs), then deliver a tested module in a typical 2–4 week window.
Technically, the module extends Odoo's native lot/serial tracking (stock.lot / stock.production.lot) and manufacturing (mrp.production, stock.move.line) rather than replacing it, so it stays upgrade-friendly and Community-and-Enterprise compatible. New models capture the genealogy graph with computed parent/child relations (@api.depends on move lines and MO consumption), traversed recursively to render an interactive forward-and-backward tree. Everything is locked down with ir.model.access.csv plus record rules for multi-company and per-plant isolation, exposed through OWL/XML views and a QWeb genealogy dossier report, and reachable over XML-RPC/JSON-RPC so your LIMS, MES or supplier portal can query trace paths programmatically. Automated actions can flag lots whose upstream material was later quarantined, so a recall scope is one click — not a two-day fire drill.
lo que obtienes
- Fully packaged Odoo module (__manifest__.py, models, security, views, QWeb reports, data) targeting your Odoo 17, 18 or 19 edition
- Installation and configuration in your environment — dev/staging first, then production — with your BOMs, lot/serial policies and warehouses wired in
- Configured recall workflow and QWeb genealogy dossier report matched to your regulatory framework (FDA Part 11, FSMA, GMP, ISO 22000, UDI or internal SOP)
- Security matrix (ir.model.access.csv + record rules) mapped to your roles, plants and multi-company structure
- XML-RPC/JSON-RPC integration guide and sample calls for connecting your MES/LIMS/supplier systems
- Admin and end-user documentation plus a recorded/live training session for your quality and warehouse teams
- Source code ownership and a Git repository handover so your team can maintain or extend the module
- A defined post-go-live support and warranty window covering bug fixes and Odoo point-release compatibility
¿Para quién es esto?
Quality & Compliance Manager
Owns audit readiness for FDA, FSMA, GMP or ISO 22000. Needs a defensible, exportable genealogy dossier for any lot on demand instead of assembling traceability by hand from stock moves before every audit.
Operations / Plant Manager
Runs multi-level manufacturing across one or more sites and needs recall scope identified in minutes, not days — knowing exactly which finished lots, shipments and customers a suspect raw-material lot touched.
Supply Chain & Recall Coordinator
Manages supplier-defect events and customer recalls. Wants a one-click list of affected deliveries, quantities and customer contacts, with follow-up activities auto-raised so nothing in the blast radius is missed.
ERP / IT Systems Owner
Maintains the Odoo instance and integrations. Values that the module extends native lot/serial and MRP models, ships clean security rules, exposes XML-RPC/JSON-RPC, and stays upgradeable across Odoo 17/18/19.
Descripción general de la instalación
Descargar desde ECOSIRE
Compre la licencia en ecosire.com y descargue el módulo ZIP Production Batch & Lot Genealogy Traceability desde el panel de su cuenta.
Subir a Odoo
Extraiga el ZIP en su carpeta de complementos personalizados de Odoo en el servidor (o cárguelo a través de Aplicaciones > Instalar desde archivo en Odoo.sh/runbot).
Instalar el módulo
Active el modo de desarrollador, abra Aplicaciones, haga clic en Actualizar lista de aplicaciones, busque Production Batch & Lot Genealogy Traceability y presione Instalar.
Configurar ajustes
Abra el nuevo menú, pegue su clave de licencia de ECOSIRE, conecte cualquier credencial externa (Shopify, Amazon, Stripe, etc.) y guarde.
Verificar y publicar
Ejecute la prueba de conexión integrada, sincronice sus primeros 10 registros y programe el cron recurrente. Póngase en contacto con el soporte si algo falla.
Cómo se compara Production Batch & Lot Genealogy Traceability
| Criterio | ECOSIRE | Construcción personalizada | Competidor | Odoo Nativo |
|---|---|---|---|---|
| Forward + backward genealogy in one interactive tree | Full multi-level forward and backward tree, drillable to source moves | Possible but you design and build the recursive traversal yourself | Often one direction or flat lists; varies by app | |
| One-click recall scope (affected lots, deliveries, customers) | Select an input lot, instantly list downstream lots, shipments and customers | Achievable if you build the blast-radius query and UI | Rarely bundled; usually extra configuration or absent | |
| Fit to your BOMs, plants and regulatory framework | Scoped and configured to your exact flows and compliance context | Fully bespoke, but on your time and engineering budget | Generic; you adapt your process to the app's assumptions | |
| Odoo 17 / 18 / 19, Community & Enterprise | Built and tested for your specific version and edition | Depends entirely on who builds it | Version-locked; upgrades often need a paid new build | |
| QWeb audit dossier + XML-RPC/JSON-RPC access | Branded genealogy report plus API endpoints for MES/LIMS | You build both from scratch | Sometimes a report; API access inconsistent | |
| Delivery model & timeline | Build-to-order, installed & supported, typically 2–4 weeks | Weeks to months; you own hiring and project risk | Instant download but generic and unsupported by you | |
| Ongoing support, warranty & source ownership | Support window, bug-fix warranty and full source/Git handover | Only what your internal team can sustain | Vendor SLA varies; source usually not handed over |
Preguntas frecuentes sobre Production Batch & Lot Genealogy Traceability
How long until the module is delivered and live?
This is a build-to-order module, not an instant download. After purchase, an ECOSIRE Odoo engineer scopes your BOM structure, lot/serial policies and regulatory context, then builds, tests and installs the module. Typical lead time is 2–4 weeks depending on the complexity of your manufacturing flows and integrations. We install on staging first for your sign-off, then promote to production.
What support and updates are included after go-live?
You get a defined post-go-live support and warranty window covering bug fixes and compatibility with Odoo point releases within your major version. Because we hand over the source and Git repository, your team can also maintain or extend it. Migrations to a new major version (e.g. 18 to 19) and net-new features are scoped as follow-on work, and extended support/SLA plans are available.
Does this work on Odoo Community or only Enterprise?
Both. The module extends Odoo's native lot/serial tracking (stock.lot) and manufacturing (mrp.production, stock.move.line), which exist in Community and Enterprise across Odoo 17, 18 and 19. We confirm your exact edition and version during scoping and target the build accordingly.
Will it break my existing lots, BOMs or stock moves?
No. It builds on top of Odoo's existing traceability data rather than replacing it — new genealogy models reference your current stock.move.line and MO consumption records, and computed fields backfill from historical moves. Nothing in your existing inventory, manufacturing or accounting flow is overwritten, and we validate on a staging copy of your database before touching production.
Can it connect to our MES, LIMS or supplier portal?
Yes. Genealogy queries and recall-scope lookups are exposed over Odoo's XML-RPC/JSON-RPC API, so external systems can request a lot's forward/backward trace or the affected-customer set programmatically. We provide an integration guide and sample calls, and can build a dedicated connector as an add-on if you need webhook or scheduled sync behaviour.
How is access to sensitive traceability data controlled?
Access is governed by ir.model.access.csv plus record rules scoped to your roles, plants and companies, so users only see and trace lots in their own warehouses. Recall actions and genealogy queries are logged via chatter (mail.thread) so you have an audit trail of who ran what trace — useful evidence for Part 11-style electronic-records requirements.
Módulos relacionados
Magento 2
una sola vez
3D Product Configurator & Customizer
A custom-built Magento 2 / Adobe Commerce extension that adds a real-time 3D product viewer with color, material, size, and per-component selectors, plus accurate per-option pricing. Built, installed, and supported by ECOSIRE on your store.
Construido a pedidoDesde $499.00
Solicitar presupuesto
Production Batch & Lot Genealogy Traceability
Build-to-order Odoo module for full forward/backward lot genealogy — trace raw material to customer for recalls and audits.
- Forward genealogy: from any raw-material or intermediate lot, expand every downstream MO, sub-assembly, finished-good lot and shipped customer delivery it ended up in
- Backward genealogy: from any finished-good lot or serial, drill back through work orders and consumed components to every incoming supplier lot and receipt
- Interactive OWL genealogy tree with expandable/collapsible nodes, colour-coded by product, lot state and quarantine flag, drillable straight to the source stock.move.line
- Raw-material-to-finished-good traceability map spanning multi-level BOMs, phantom/kit BOMs, by-products and rework loops