How to evaluate a tank monitoring system — a guide for fuel distributors

What you are actually evaluating

Most distributors evaluating a tank monitoring system are not evaluating the sensor. They are evaluating whether a platform can change the economics of their logistics operation — and whether it will integrate with the systems they already run.

The hardware is a means to an end. The end is a dispatch team that plans from level data rather than from a calendar or reactive customer calls. The evaluation criteria that matter are the ones that determine whether that outcome is achievable in your specific operation.

Connectivity and transmission frequency

The first practical question is whether the system will work at your customers' sites. Tank locations vary considerably: rural farms, urban workshops, industrial facilities, remote agricultural properties.

The leading connectivity approaches for tank monitoring are cellular — NB-IoT and LTE-M — and LoRaWAN. Cellular systems work in most locations without any on-site infrastructure. LoRaWAN requires a gateway within range.

Transmission frequency matters more than the marketing language around it. Most industrial tank monitoring systems transmit one measurement per day. This is sufficient for planning purposes: consumption models are built from historical daily data, and the planning horizon for most fuel distribution operations is one to five days. Ask specifically how often the sensor transmits and whether that frequency is configurable.

Battery life is a maintenance variable. Systems designed for industrial deployment typically carry battery life of five to ten years under standard transmission frequencies. Confirm the replacement process and whether your own field team can handle it.

Integration depth

A tank monitoring platform that cannot connect to your existing ERP, dispatch, or planning system creates a parallel workflow — which means it will not be used systematically. Integration depth is often the deciding factor in whether a deployment actually changes planning behaviour.

The relevant integration points for fuel and liquid distributors are:

• ERP systems: SAP, Microsoft Dynamics Navision, Microsoft Dynamics 365

• Dispatch and logistics systems: X-Oil, and sector-specific planning tools

• CRM and order management systems for customer-facing data

Ask whether the integration is pre-built or custom, what data flows in each direction, and what the implementation timeline and effort looks like for your specific system configuration.

Hardware requirements and installation

Industrial tank monitoring hardware needs to meet the conditions of the tanks being monitored. The relevant variables are:

• Tank type and geometry: Above-ground, below-ground, cylindrical, irregular

• Liquid type: Oil, diesel, lubricant, UCO, LPG — each has different measurement requirements

• Hazardous environment classification: Some installations require ATEX-rated hardware

• Installation access: Sensor installation should be achievable by your own field team without specialist technicians

Installation time per sensor is a real operational variable. Hardware designed for field deployment by non-specialists typically installs in under a minute per tank. If a system requires technician installation, factor the deployment cost and timeline into the evaluation.

The ROI framework

The business case for tank monitoring has two primary drivers: logistics cost reduction and revenue protection through improved service.

On the logistics side, the measurable improvement is the reduction in cost-per-litre delivered. The mechanism is higher tank utilisation at the point of delivery — fewer visits to tanks that are not ready — and the elimination of emergency deliveries, which carry a disproportionate cost due to sub-optimal routing.

For planning purposes, the baseline cost of an emergency delivery — a single-stop, reactive run — typically runs to €100–155 in vehicle and driver cost. Multiply that by the number of emergency deliveries in your current operation to size the addressable saving.

On the revenue side, distributors operating proactive delivery models — where they initiate contact based on level data rather than waiting for customer orders — consistently report higher customer retention. The structural reason is straightforward: a distributor who knows what is in a customer's tank before the customer does has a service advantage that is difficult to replicate through pricing alone.

Questions to ask before committing

A practical checklist for vendor evaluation:

1. How often does the sensor transmit, and is that configurable?

2. Which ERP and dispatch systems do you have pre-built integrations for?

3. What is the installation process and who performs it?

4. What is the battery life and replacement process?

5. Can you demonstrate the platform with data from an operation similar to mine?

6. What does the onboarding and deployment support look like?

7. What happens if a sensor goes offline — how is this detected and managed?

8. What is the typical amortisation period based on deployments in my vertical?