Digital Transformation in Cold-Chain Logistics: How Lider Gıda A.Ş. Brought 24,000 Liters a Day Under Control

Part 1: Executive summary

Cold-chain transport is the branch of logistics with the least tolerance for error. Cargo temperature must hold for the whole journey, and that protection depends on the trailer's refrigeration unit running without interruption. In cold chain, therefore, fuel is not merely a cost of movement — it is the cost of product safety.

Lider Gıda A.Ş. runs a large-scale operation in this field, managing a fleet of 750 tractor units and 470 refrigerated trailers from its main campus in Samsun. From 2 tanks and 2 pumps on site, an average of ~24,000 liters of fuel is dispensed each day — around 8.8 million liters a year.

The structure built in this project goes beyond classic station automation: fuel automation, RFID pairing of tractor and trailer, API integration with two separate telematics systems (Arvento and Seyir Mobil) and a real-time web-service link to the customer's own ERP all converge into a single data chain.

Part 2: Operational bottlenecks

Before the system was installed, all of that volume was managed by hand, on manual forms and paper records — producing three core problems that compound with scale.

1. Data lag. Because records were compiled at the end of the day, control always trailed reality. Across a 1,220-unit fleet, a single day of lag is an information gap that is hard to close.

2. Human error. Filling in forms by hand contradicts the scale itself. Entering hundreds of fills a day manually makes wrong plates, wrong quantities and missing records a permanent risk.

3. Untracked refrigeration engines — the real bottleneck. In cold chain the unit of measurement splits in two:

Unit	Consumption measure	Natural metric
Tractor units (750)	Kilometers	liters/100 km
Refrigerated trailers (470)	Operating hours	liters/hour

With trailer engines untracked, how much fuel went into hauling versus cooling was unknown. And because no record showed which tractor unit was pulling which trailer, attributing consumption between the two was impossible. This is the most common — and most cost-concealing — blind spot in cold-chain fleets.

Part 3: Technical architecture and hardware

Samsun campus automation

An advanced site automation system was installed:

Component	Count
Fuel storage tanks	2
Fuel pumps	2
Site automation system	1

Both tanks were placed under level monitoring and both pumps were automated through control units. Every fill is recorded automatically with vehicle, driver, quantity and time, and the drop in tank level is continuously reconciled against total fills.

RFID tractor-trailer pairing

This is the project's distinguishing hardware design. Tractor units were fitted with RFID identification, and at the moment of fuelling the system automatically pairs which tractor unit is pulling which refrigerated trailer.

The practical consequence: fuel consumed by a trailer is no longer an abstract "trailer expense" but a record that knows which tractor unit and which trip it belonged to. Even when the same trailer travels with different tractor units, consumption is booked to the right side.

Part 4: The power of dual integration

Two telematics systems, one data pool

To read vehicle data without error, API integrations were built with two separate tracking systems:

• Tractor units (750): odometer values pulled automatically from Arvento and Seyir Mobil.
• Refrigerated trailers (470): refrigeration engine hours read automatically, producing per-trailer consumption rates.

Why two systems? Large fleets accumulate different telematics providers over time; vehicle groups arrive under different contracts. Tying automation to a single provider means leaving part of the fleet outside the data. Here the integration spans both providers, so all 1,220 units sit in the same analysis pool.

Custom ERP integration

The collected data — tractor odometer, trailer engine hours, fill volume and the tractor-trailer pairing — is pushed into the in-house ERP developed by Lider Gıda through real-time web services.

This step is what makes the project's operational value permanent. As long as fuel data stays inside the automation, it is a report; once it flows into the ERP it becomes a direct input to cost accounting, trip profitability and customer pricing. Central management and accounting now run with no manual data entry.

Part 5: Operational gains

• A vast volume under control. A ~24,000-liter-a-day fuel process is recorded end to end, with tank level continuously reconciled against total fills.
• Real per-trailer consumption. "Fuel per operating hour" analysis produced clear consumption averages for the refrigeration units — a line previously managed by estimate, now measurable.
• Dual-metric fleet visibility. Liters/100 km for tractors, liters/hour for trailers — in the same view, tied to the same trip.
• Zero manual entry. Human error was eliminated and central management and accounting were automated.
• Full coverage. With two telematics providers integrated, no part of the fleet stays outside the data.

Note: This case study is based on verified scope, hardware and scale data. Savings and efficiency ratios measured after installation will be added as they are confirmed with the customer.

Conclusion

The Lider Gıda A.Ş. project shows that in a large cold-chain fleet, fuel control cannot be achieved by pump automation alone. Control emerges when automation of the supply point, tractor-trailer pairing, accurate measurement from both telematics sources and data flowing into the company's own ERP are built together. A 24,000-liter-a-day operation becomes transparent, reconciled and auditable only once that whole chain is closed.