Cold-chain control in Odoo: temperature zones, FEFO, excursion logging, shelf-life alerts and compliance reports. Built and installed by ECOSIRE. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $499.00 USD; request a quote for a scoped proposal.
Manifeste de l'app
Conçu autour de votre flux de travail
Cold-chain control in Odoo: temperature zones, FEFO, excursion logging, shelf-life alerts and compliance reports. Built and installed by ECOSIRE.
Aucune configuration à faire vous-même — une app fonctionnelle conçue, installée et prise en charge par ECOSIRE.
Commencez par un prix de développement unique. Nous cadrons le projet avec vous au lancement.
ECOSIRE la développe, la configure et l'installe sur votre Odoo.
Vous êtes en ligne en 2–4 semaines environ, avec une période d’assistance après le lancement.
Cold Chain & Temperature-Controlled Logistics is a build-to-order Odoo module that ECOSIRE designs, develops, installs and supports for food, pharma and perishable-goods shippers. This is not an instant apps.odoo.com download — it is a custom-fit module built to your temperature ranges, product classes and regulatory obligations, then deployed into your own Odoo 17, 18 or 19 database within a 2–4 week lead time.
Standard Odoo Inventory tracks lots, expiry dates and FEFO removal, but it has no concept of a temperature zone, a monitored excursion, or an auditable cold-chain record that a food-safety or pharma inspector will accept. This module closes that gap. We extend stock.location with temperature-zone attributes (min/max °C, humidity, zone class such as frozen, chilled or ambient) so your warehouse map reflects reality, and we enforce that perishable products can only be reserved and picked from a compatible zone.
At the heart of the module is a new cold.chain.excursion model that logs every temperature deviation against a specific lot, shipment (stock.picking) or storage location, with the duration, peak temperature, responsible user and a corrective-action note. Compute fields built with @api.depends derive remaining shelf life, cumulative time-out-of-range and a pass/fail disposition, so quality teams stop guessing whether a pallet is still saleable. Automated actions (server actions on a scheduled ir.cron) raise activities and email alerts before product reaches its expiry or shelf-life threshold, and FEFO (First-Expiry-First-Out) removal is enforced at reservation time so the oldest safe stock always ships first.
Every record is locked down with proper ir.model.access.csv rights and record rules — warehouse operators log excursions, QA approves dispositions, and auditors get read-only visibility — so the data holds up under scrutiny. QWeb PDF reports produce cold-chain compliance certificates, temperature-log summaries and shipment condition reports you can hand to a customer or regulator. Ingestion of readings from IoT loggers or 3PL portals is available through Odoo's XML-RPC / JSON-RPC API or scheduled imports, so live sensor data flows into the same auditable record.
The module works on Odoo Community and Enterprise; where Enterprise-only apps (IoT, Quality, Field Service) are present we integrate with them, and where they are not we deliver equivalent functionality in Community-compatible code. You receive the full source, an installed and configured system, documentation, training and a post-launch support window — not a black box.
Ships chilled and frozen goods and must prove an unbroken cold chain to retailers and food-safety auditors. Needs FEFO enforcement, zone-based storage and excursion logs tied to each pallet and delivery.
Handles temperature-sensitive medicines and vaccines under GDP-style rules. Needs auditable excursion records, quarantine of out-of-range lots and compliance certificates a regulator will accept.
Runs multi-zone facilities for several clients and must report condition per client and per shipment. Needs zone-mapped locations, per-shipment disposition status and ingestion of logger data at scale.
Owns the pass/fail decision on temperature-controlled stock. Needs role-based rights to approve dispositions, release quarantined lots and pull compliance documentation on demand.
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| Temperature-zone storage locations | Locations carry min/max °C, humidity and zone class, enforced on reservation | Achievable but you design and maintain the data model yourself | Rarely modeled; most FEFO apps ignore temperature zones | |
| Temperature-excursion logging & disposition | Dedicated cold.chain.excursion model with computed time-out-of-range and pass/fail | Possible but requires bespoke modeling and compute logic | Prise en charge partielle | |
| FEFO enforcement for perishables | Enforced at reservation, tuned to your shelf-life rules per category | Build on top of Odoo's removal strategy yourself | Prise en charge partielle | |
| Expiry & shelf-life alerts (scheduled) | ir.cron server actions raise activities and emails before thresholds | Write and schedule your own crons and templates | Prise en charge partielle | |
| Cold-chain compliance documents (QWeb) | Branded certificate, temperature-log and shipment condition reports | Author QWeb templates from scratch | Non inclus | |
| Role-based security (ir.model.access.csv + record rules) | Operator / QA / auditor roles configured for defensible records | You define all access and record rules | Prise en charge partielle | |
| IoT / logger / 3PL ingestion (XML-RPC / JSON-RPC) | Integration built for your device or portal with sample scripts | Build and maintain the integration yourself | Non inclus | |
| Fit to your ranges, editions and regulations | Built to spec on Odoo 17/18/19, Community or Enterprise, with source handover | Fully bespoke but at full internal cost and timeline | Fixed feature set, take it or leave it | |
| Ongoing support & version upgrades | Post-launch support window plus upgrade services across 17/18/19 | Your own team owns all maintenance | Prise en charge partielle |
This is a build-to-order module, not an instant apps.odoo.com download. After we confirm your requirements — temperature ranges, product classes, editions and regulatory needs — ECOSIRE builds, configures and installs it in your Odoo database. Typical lead time is 2–4 weeks depending on scope and integrations. You approve the plan before we start development.
Every build includes a defined post-launch support and bug-fix window for the Odoo version you deployed on. During that window we fix defects, answer configuration questions and make minor adjustments. We also offer extended support and version-upgrade services to keep the module current as you move between Odoo 17, 18 and 19. You own the source, so you are never locked in.
It works on both. The core cold-chain features — temperature zones, FEFO, excursion logging, alerts and QWeb compliance reports — are delivered in Community-compatible code. Where you run Enterprise apps such as IoT, Quality or Field Service, we integrate with them; where you do not, we provide equivalent functionality so no feature depends on an Enterprise license you may not have.
Standard Odoo tracks lot expiry and can remove FEFO, but it has no notion of a temperature zone, a monitored excursion, or an auditable cold-chain record. We add temperature-attributed locations (extending stock.location), a dedicated cold.chain.excursion model with computed time-out-of-range and disposition, zone-compatibility enforcement, automated quarantine of failed lots and inspector-ready compliance reports — none of which core Odoo provides.
Yes. Readings can flow in through Odoo's XML-RPC / JSON-RPC API or scheduled imports, so data from data-loggers, sensors or a 3PL feed is written straight into the excursion record against the correct lot and shipment. We build the integration for your specific device or portal and hand over sample scripts as part of delivery.
That is the point of the module. Excursion records capture lot, shipment, location, duration, peak temperature, responsible user and corrective action, and are protected by ir.model.access.csv rights and record rules so operators, QA and auditors have appropriate, tamper-evident access. QWeb PDF certificates and temperature-log summaries give you the documentation to present to inspectors and customers.
We need your Odoo version and edition, your temperature ranges and product classes, your role structure and any logger or 3PL integration details. We hand over the full module source, an installed and configured system, security rules, branded compliance reports, documentation, staff training and a post-launch support window.
Cold-chain control in Odoo: temperature zones, FEFO, excursion logging, shelf-life alerts and compliance reports. Built and installed by ECOSIRE.