ERP for Cold Chain Distribution: Temperature, FEFO, and Lot Tracking

Distributing frozen and fresh products has one enemy that does not show up in sales reports: temperature going out of range. Meat, fish, ice cream, dairy, cut vegetables, vaccines, and some medicines can lose quality or even become unsafe after a few hours at the wrong temperature. The problem is that damage is often discovered only at the end of the chain, when a customer rejects goods or files a claim, and by then it is hard to trace where things went wrong.

Cold chain businesses therefore need a system that records not only stock quantities but also shelf life, lots, temperature, and the trail of every movement. This article covers system requirements for distributors, cold storage warehouses, food producers, and modern retail suppliers: from goods receipt, storage, and FEFO picking to refrigerated delivery, claims handling, and product recalls.

Summary

• The cold chain requires lot, expiry date, and temperature history records connected to stock transactions
• The FEFO principle (first expired, first out) must be enforced by the system, not just by warehouse staff discipline
• Temperature sensors and data loggers are valuable when their data is linked to lots, locations, and vehicles rather than standing alone
• Temperature excursions need a clear workflow: quarantine, quality evaluation, release or discard decision, and documentation
• Reports on shrinkage, claims, and energy cost per line help calculate true margins
• Implementation is best staged, starting with lot and expiry tracking before full sensor integration

Why generic systems often fall short

Many distributors use a basic accounting or inventory system that only knows quantities per warehouse. For dry goods, that may be enough. For the cold chain, there are several gaps:

• Stock is not separated by lot and expiry date, so older goods get left at the back of the rack
• Temperature data sits in a sensor app or paper log that is not connected to the goods being stored
• There is no quarantine status, so goods under quality review can be shipped
• Deliveries are recorded as warehouse issues without vehicle, loading temperature, or arrival time
• Customer claims are handled over chat with no link to lot and delivery history

The result is unexplained shrinkage, claims that are hard to substantiate, and reputational risk if a problem product reaches consumers.

Core cold chain processes and their system needs

Goods receipt

When goods arrive from a supplier or production, the system needs to record lot number, production date, expiry date, and temperature on receipt. Many companies set limits: goods outside temperature tolerance or with too little remaining shelf life are rejected, or accepted under quarantine. Receipt forms in a mobile app or on a scanner speed up recording and reduce typos.

Storage by temperature zone

Cold chain warehouses usually have several zones: frozen, chilled, cool, and ambient. The system should know the zone of every rack location and prevent goods from being stored in the wrong one. Cold room capacity is limited, so visibility of occupancy per zone helps plan receipts. Warehouse location basics are covered in a warehouse management system for growing businesses.

FEFO picking

FIFO (first in, first out) is not always right for products with a shelf life. Two lots arriving on different days can have reversed expiry dates. FEFO ensures the lot expiring soonest ships first. A good system proposes lot and location on the pick list and warns or blocks when a picker scans a different lot. Some customers, such as modern retail chains, also require a minimum remaining shelf life on arrival, so the system needs to check rules per customer. Lots are discussed in more depth in lot, batch, and expiry tracking with ERP.

Loading and delivery

Each delivery should be linked to a vehicle, driver, route, and the reefer box temperature at loading. The time the door is open during loading and unloading is a weak point. GPS and vehicle temperature data, where available, should be stored with the delivery note. Fleet integration is covered in fleet and transport management with GPS and ERP.

Handover to the customer

Electronic proof of delivery with photo, signature, time, and temperature at handover reduces disputes. A driver app helps a lot, especially if it works in areas with weak signal; see mobile apps for field teams.

Temperature data: from paper logs to connected monitoring

Many warehouses still record temperature manually two or three times a day. That is better than nothing, but it misses excursions at night or during power cuts. More reliable options:

• Data loggers that record temperature periodically and are downloaded when needed
• Connected sensors that send data regularly and trigger alerts when temperature goes out of range
• Vehicle sensors connected to the GPS device

The key is not just installing sensors but linking their data to context: which location, which lot is stored there, and who must act. Alerts sent to a chat group without a clear owner are often ignored. A realistic discussion of sensors is in IoT and sensors for small businesses.

Handling temperature excursions

Excursions will happen: a compressor fails, the power goes out, a door is left open, a vehicle gets stuck in traffic. What sets mature companies apart is the handling workflow.

• Detection: a sensor or manual check finds the temperature out of range
• Quarantine: the system flags affected lots so they cannot be picked for delivery
• Evaluation: the quality team assesses the duration and size of the excursion based on data and product specifications
• Decision: release, downgrade, return to supplier, or destroy, with recorded approval
• Corrective action: the cause is recorded and followed up, for example a refrigeration maintenance schedule

All these steps should leave an audit trail. Relevant internal control principles are in audit trails and internal control in ERP, while quality inspection is covered in quality control with ERP.

Recalls and traceability

When a supplier announces a problem with a particular lot, a distributor must answer quickly: when was the lot received, where was it stored, which customers was it shipped to, and how much is left. With lot records from receipt to delivery, this can be answered in minutes rather than days. One step back and one step forward traceability is a practice many regulators and large customers expect.

For pharmaceuticals and medical devices, regulators publish specific distribution guidelines, including temperature control and documentation. Detailed requirements differ by product type and can change, so make sure you refer to the latest official rules and consult your responsible technical person. System needs for this sector are also covered in ERP for pharmacies and pharmaceutical distributors.

Calculating true margins

Cold chain businesses have costs that do not appear in dry goods: electricity for cold rooms, equipment maintenance, refrigerated vehicles, insulated packaging, and shrinkage from expiry or damage. Without good data, all of this is mixed into overhead and per-product margins look better than reality.

Useful reports include:

• Shrinkage per product, per supplier, and per cause (expiry, temperature, physical damage)
• Customer claims per route and per driver
• Stock age and items nearing expiry, to promote or redirect earlier
• Cold room occupancy against capacity
• Refrigerated delivery cost per kilogram or per drop

Stock age data also helps purchase planning so you do not buy more than you can sell before expiry; see stock planning and reordering.

Features to look for

• Lot and expiry date tracking on every stock transaction
• FEFO rules and minimum remaining shelf life per customer
• Warehouse locations with temperature zone attributes
• Stock statuses: available, quarantine, rejected, damaged
• Mobile receipt and delivery forms with scanning
• Sensor data integration and alerts with assigned owners
• Electronic proof of delivery
• Forward and backward traceability reports
• Shrinkage and stock age reports

For distributors that also serve many stores and field sales, general distribution needs still apply; see system needs for distribution businesses.

Implementation roadmap

Stage 1: lots and expiry (1 to 2 months)

Clean up product master data including shelf life and temperature zone. Start recording lots and expiry dates at receipt and delivery. Apply FEFO on pick lists.

Stage 2: quality status and locations

Add quarantine status, a quality decision workflow, and rack locations per zone. Train warehouse staff to scan lots at every movement.

Stage 3: delivery and proof of delivery

Link delivery notes to vehicles and drivers, add a proof-of-delivery app, and record temperature at loading and handover.

Stage 4: sensors and analytics

Integrate warehouse and vehicle sensor data, create alert rules, and build shrinkage and margin reports per line.

Common mistakes

• Installing expensive sensors before lots and locations are recorded properly
• Applying FEFO only as a verbal instruction without system support
• Having no quarantine status, so problem goods get shipped
• Ignoring the minimum remaining shelf life required by retail customers
• Lumping electricity and shrinkage into overhead so per-product margins are misleading

Frequently asked questions

Do small businesses need a cold chain system?

At low volume, start with consistent lot and expiry recording and a simple temperature log. A fuller system becomes worthwhile as the number of SKUs, customers, or warehouses grows.

Must every product be tracked by lot?

For products with a shelf life or food safety risk, it is strongly recommended. Other products can still be managed by quantity only.

How often should temperature be recorded?

It depends on the product, customer requirements, and regulation. Shorter intervals give a more accurate picture, but make sure someone follows up on alerts.

Can we keep our old system?

Yes, if it can be extended or integrated. But if the old system does not support lots and quality status, the cost of patching is often higher than a planned switch.

Conclusion

The advantage of a cold chain business lies not only in good refrigeration equipment but in knowing the condition of every lot from receipt to the customer's hands. A system that links lots, expiry, location, temperature, and delivery helps reduce shrinkage, speeds up claims handling, and builds trust with large customers. Start with the data foundation, enforce FEFO through the system, then add sensors and analytics once the process is stable.