Cold chain logistics is one of the most demanding environments for an ERP system. A temperature deviation of a few degrees over just a few hours can render a shipment of fresh produce unfit for consumption, trigger a product recall and expose the business to regulatory sanctions. Yet a significant proportion of food and pharmaceutical companies still manage their cold chain with manual probes, spreadsheets and paper-based traceability reconstructed after the fact.
The European Rapid Alert System for Food and Feed (RASFF) recorded 5,250 notifications in 2024, a 12% increase on 2023. Each notification represents an incident in which a food operator had to identify contaminated batches, withdraw products from the market and notify the health authorities. The ability to respond quickly with reliable data from the ERP makes all the difference between a managed incident and a media crisis.
This guide details the essential ERP features for cold chain operations and presents the vendors that offer them natively.
The Four Cold Chain Segments and Their Regulatory Requirements
Before evaluating an ERP, you need to map the temperature profiles of your products. EU and international regulations distinguish several segments, each with its own obligations.
Frozen products: storage and transport temperature must be maintained at a maximum of -18°C, in line with EU Regulation (EC) No 853/2004 laying down specific hygiene rules for food of animal origin. Any breach of this threshold constitutes a cold chain break in regulatory terms.
Chilled products: fresh meat, dairy products and cooked meats must be stored between 0°C and 4°C. EU and national food safety frameworks specify maximum temperatures by product category, and these must be documented in the company’s HACCP plan.
Controlled ambient: certain fruit, vegetables, beverages and dried charcuterie require a temperature range of 8°C to 15°C. Requirements are less stringent but must be documented in the company’s HACCP plan.
Pharmaceutical cold chain: biological medicines, vaccines, insulin and certain medical devices must be kept between 2°C and 8°C. This segment is governed by the EU Good Distribution Practice (GDP) guidelines of 2013, which are separate from the food framework.
A cold chain ERP must be capable of managing all four profiles simultaneously, with differentiated management rules, alerts and reports by product category.
The 5 Essential ERP Features for Cold Chain Management
1. ATP with Expiry Date Management (Use-by/Best-before) and FEFO Algorithm
ATP (Available-to-Promise) is the function that calculates in real time what a salesperson can commit to a customer, taking into account available stock, orders awaiting dispatch and batch expiry dates. In cold chain logistics, this feature must natively integrate the FEFO (First Expired, First Out) algorithm.
The distinction between FIFO and FEFO is fundamental in food manufacturing:
- In FIFO (First In, First Out), the ERP ships the oldest batch by receipt date. This logic suits non-perishable or long-shelf-life products.
- In FEFO (First Expired, First Out), the ERP ships the batch with the nearest use-by date (UBD) or best-before date (BBD). If a batch received this week has a shorter UBD than one received last month, FEFO dispatches it first.
FEFO is an implicit obligation under EU Regulation (EC) No 178/2002 on food safety, which requires operators not to place dangerous products on the market. An ERP that drives dispatches on FIFO logic in a fresh-produce context mechanically generates the risk of shipping products with expired or insufficient remaining shelf life.
Automatic expiry date alerts are the indispensable corollary of FEFO:
- 7 days before expiry: alert for commercial planning (promotional destocking, food donation)
- 3 days before expiry: automatic block on inclusion in new orders
- Day of expiry: block on order picking, batch placed in quarantine
2. Real-Time Temperature Monitoring via IoT
Integration between the ERP and IoT temperature sensors is the most technically complex link in the cold chain. The ERP does not generate temperature readings itself: it receives them from physical probes deployed in cold rooms, refrigerated trucks, loading docks and display aisles.
The most common integration protocols are:
- MQTT (Message Queuing Telemetry Transport): a lightweight protocol designed for connected devices, widely used by probe manufacturers such as Testo and Sensitech. It allows real-time transmission (frequency configurable from 1 to 15 minutes) without overloading the network.
- REST API: for cloud IoT platforms (AWS IoT, Azure IoT Hub) that aggregate data from multiple sensors before forwarding it to the ERP.
- Modbus / OPC-UA: for industrial cold rooms with Siemens or Schneider Electric PLCs, used mainly in large-scale warehouses.
The ERP must trigger an immediate alert the moment a temperature threshold is exceeded. A practical example: a refrigerated truck suffers a refrigeration unit failure. The temperature rises from 4°C to 12°C over two hours. The ERP receives the alert via MQTT, automatically identifies the batches on that truck, places them in provisional quarantine and triggers a quality decision process (destruction, return, sensory analysis, downgrading). Without this integration, the quality manager only discovers the cold chain break at delivery, when the carrier manually reports the incident.
All temperature data must be automatically recorded in the ERP with timestamps, sensor ID and the batch concerned. These records constitute the documentary evidence required by IFS Food v8 and BRC Global Standard auditors during certification.
3. End-to-End Batch Traceability
EU Regulation (EC) No 178/2002 requires “one step back, one step forward” traceability from all operators in the food chain. In practice, every business must be able to identify:
- Who supplied an ingredient or raw material (upstream traceability)
- Who received a product containing that ingredient (downstream traceability)
In cold chain logistics, this obligation is particularly critical because temperature breaks can affect many batches simultaneously. The ERP must generate, in under four hours (the timeline commonly required by retailers in their framework contracts), a complete traceability report showing:
- The source raw material batch(es)
- The production lines used and the time windows
- The finished product batches manufactured
- The customers delivered to, quantities and dates
The link with the WMS (Warehouse Management System) is essential here. Every batch movement in the warehouse — whether a pallet transfer, order picking or inter-zone temperature transfer — must be captured in real time and recorded in the ERP. A WMS disconnected from the ERP creates blind spots in traceability.
If the warehouse is outsourced to a third-party logistics provider (3PL), batch and temperature data must still flow back into the brand owner’s ERP. This contractual requirement must be specified at the logistics contract negotiation stage.
4. Cold Chain Break Incident Management and Product Recalls
Incident management is the feature that distinguishes a sector-specific ERP from a generalist one in cold chain logistics. Here is the process the ERP must be able to orchestrate:
Phase 1: detection and automatic quarantine. As soon as a cold chain break is detected (IoT alert, operator report, non-conforming analysis result), the ERP automatically blocks the affected batch: no order picking or dispatch can be triggered on that batch until a quality decision is made.
Phase 2: scope definition. The ERP identifies all batches potentially affected by the same break (same cold room over the same period, same truck, same raw material). It lists customers already supplied with those batches.
Phase 3: withdrawal or recall initiation. The ERP generates the required operational documents: customer return orders, notification letters, lists of batches to identify on shelves. It also produces the regulatory notification form for the RASFF system and the relevant national food safety authorities (DGCCRF/DGAL in France, FSA in the UK, BfR in Germany, EFSA at EU level).
Phase 4: incident closure and audit trail. All actions taken are recorded with timestamps and electronic signatures. This incident file constitutes the due-diligence evidence required by IFS, BRC audits and investigations by health authorities.
According to a Consumer Brands Association survey of multinational food companies, the average cost of a food product recall exceeds $10 million, with more than 50% of companies that suffered a major recall reporting costs above that threshold. An ERP that reduces the detection and scope-definition time for a recall from 72 hours to 4 hours can cut the number of affected batches — and the associated operational cost — by a factor of ten.
5. HACCP Documentation and IFS/BRC Reporting
The IFS Food v8 and BRC Global Standard private standards, required by European retailers to list their suppliers, mandate precise documentation of all critical control points (CCPs). For cold chain logistics, typical CCPs include:
- Incoming temperature of chilled raw materials
- Cold room storage temperature (positive and negative)
- Dispatch transport temperature
- Use-by date check at dispatch (compliance with the customer’s residual shelf-life contract)
The ERP must record every CCP reading with the technician’s ID, the timestamp and the result (conforming / non-conforming). In the event of a non-conformity, it automatically triggers a corrective action and records the resolution. This fully digital documentary flow, integrated in the ERP, replaces the paper binders that slow down audits and generate documentary non-conformities.
ERP Vendors with Recognised Cold Chain Modules
Aptean Food & Beverage
Aptean Food & Beverage is a vertical ERP designed exclusively for the food and beverage industry. It natively integrates FEFO management, bidirectional batch traceability, expiry date management (UBD/BBD) and a product recall module with automated workflow. Its IoT integration is open via REST API, compatible with the leading temperature monitoring platforms. Particularly well suited to mid-market companies (100 to 1,000 employees) in food and beverage manufacturing.
Infor CloudSuite Food & Beverage
Infor CloudSuite Food & Beverage is considered one of the most comprehensive solutions on the global market for this sector. It covers batch management with FEFO, real-time quality monitoring, end-to-end traceability and a product recall management module. Its native WMS module (Infor WMS) ensures traceability continuity between the ERP and the warehouse. Its main drawback is its high cost, which positions it more for larger mid-market and enterprise organisations (500 employees and above).
SAP S/4HANA with SAP EWM and SAP QM
SAP S/4HANA is the reference solution for large food and pharmaceutical groups. Cold chain is covered by two complementary modules: SAP EWM (Extended Warehouse Management) for batch management in the warehouse with FEFO, and SAP QM (Quality Management) for HACCP documentation, certificates of analysis and non-conformities. IoT integration runs through SAP IoT or certified third-party connectors. This solution is sized for large organisations with internal SAP teams or a dedicated systems integrator.
Microsoft Dynamics 365 with Sector Extensions
Dynamics 365 Supply Chain Management includes batch and expiry date management features, but cold chain verticalisation generally requires partner extensions such as those offered by To-Increase (Food & Beverage) or Aris. These extensions add native FEFO management, expiry date alerts and a HACCP module. Well suited to mid-market companies already committed to the Microsoft ecosystem.
Odoo (with Configuration and Third-Party Modules)
Odoo offers an Inventory module that supports batch management, expiry dates and the FEFO strategy. For a small food manufacturer with up to 100–150 employees, Odoo is a viable option provided you invest in the initial configuration (approximately 20 to 40 consulting days to activate and configure FEFO, expiry date alerts and traceability). IoT integration for temperature monitoring requires a third-party integration, as Odoo does not natively support MQTT or Modbus. A solution to avoid for operators under IFS or BRC standards without a significant customisation budget.
Recommended Architecture: ERP, WMS and IoT
In a cold chain warehouse, three systems must work in concert:
The ERP is the brain of the cold chain. It manages orders, batches, expiry dates, commercial traceability and quality processes (recalls, non-conformities, HACCP audits).
The WMS is the operational system of the warehouse. It drives pallet movements, enforces FEFO at the picking stage, manages storage locations by temperature zone and communicates every batch movement to the ERP in real time.
The IoT layer is the network of temperature sensors. It feeds readings to the WMS or directly to the ERP depending on the chosen architecture, triggering alerts when a threshold is exceeded.
For operators outsourcing their warehouse to a 3PL provider, a contractual clause must require that the provider’s batch and temperature data be exposed via API and fed back into the brand owner’s ERP. Without this clause, traceability breaks the moment pallets leave the principal’s site.
To go deeper on the choice between native ERP WMS and best-of-breed WMS, our guide Native ERP WMS vs Best-of-Breed vs 3PL: Decision Criteria and ROI covers the trade-offs by company size and logistics complexity.
Cold Chain ERP Implementation Checklist (10 Points)
Before starting a cold chain ERP project, run through this list to confirm your scope is well defined:
- Map temperature profiles: list all products with their regulatory temperature range (frozen, chilled, controlled ambient, pharmaceutical).
- Inventory existing IoT sensors: brand, model, communication protocol (MQTT, REST, Modbus), transmission frequency.
- Choose the stock management algorithm: FEFO is mandatory for perishable products; FIFO is only acceptable for products without an expiry date.
- Configure expiry date alerts: define thresholds (7 days, 3 days, 1 day before expiry) and the associated actions (email alert, order block, quarantine).
- Connect IoT sensors to the ERP or WMS: test the latency and reliability of the data feed (target: alert within 5 minutes of a threshold breach).
- Train warehouse operators on the mandatory entry of batch numbers for every movement (goods receipt, transfer, dispatch).
- Test end-to-end traceability on 3 pilot batches: simulate a recall and measure the time to reconstitute the scope.
- Configure the product recall report: target under 4 hours from detection to a complete list of customers to notify.
- Validate with the quality manager and HACCP coordinator before go-live: all CCPs must be documented in the ERP.
- Plan the annual certification audit (IFS or BRC) with ERP records as the primary documentary basis.
ROI of a Cold Chain ERP
The gains from a well-configured cold chain ERP materialise across three main levers.
Reduction in recall costs. The ability to define the scope of a recall within 4 hours rather than 72 hours mechanically reduces the number of affected batches and the volume of products to withdraw. A recall whose scope is controlled in the first few hours costs a fraction of one discovered late, where products have already been distributed across hundreds of outlets.
Reduction in expiry date waste. Automatic FEFO alerts and at-risk stock dashboards (batches with 7 days to expiry) enable preventive action: promotional destocking, food bank donations, reorientation to markets with lower residual shelf-life requirements. Based on field project feedback, companies that correctly activate FEFO and expiry date alerts in their ERP reduce losses from expired products by 20 to 30% in the first 12 months.
IFS/BRC compliance without major non-conformities. Passing an IFS or BRC audit with fully digitalised documentation in the ERP eliminates the most frequent documentary non-conformities (incomplete records, missing binders, illegible dates). Maintaining these certifications conditions access to retail markets, which typically represents 60 to 80% of revenue for mid-market food manufacturers.
To go deeper on ERP features specific to food manufacturing, our food industry ERP comparison: batch traceability, HACCP and IFS/BRC compliance covers six solutions with their strengths and limitations.
To understand how to integrate cold chain management into a broader supply chain strategy, our guide ERP and supply chain: WMS, TMS and demand planning covers the trade-offs between native ERP and best-of-breed logistics.
