Flow meter
Counts every pulse at the pump outlet. The liter that left, not an estimate.
Track level in real time, release fueling by RFID card, and know the instant fuel leaves outside the normal flow — using the sensor already on your tank.
No proprietary hardware locking you in. The DP Core Board reader speaks the industry-standard sensors — and any 4–20 mA probe is on the list.
The reader's default input: bottom pressure turned into a stable level reading.
Non-contact measurement for aggressive products or foam.
Ultrasonic, pressure, capacitive — the industry current loop.
The common tank float on a resistive divider. Guaranteed compatibility.
Immersed probe reading the actual fuel temperature.
A contact sensor that flags the moment the tank is opened.
One reader, one level source — picked in software at setup, no board swap. The second input can take the temperature probe.
In a horizontal cylinder, a dished bottom or an odd shape, level does not turn into liters linearly. You measure real liters at several points and TankFlow fits the curve — true accuracy without an expensive sensor.
The flow meter counts liters at the pump outlet. Telemetry measures the level drop inside the tank. Both numbers sit side by side — and the gap between them is your proof that the measurement is honest.
Counts every pulse at the pump outlet. The liter that left, not an estimate.
Tank telemetry measures the same fueling from the inside, independently.
TankFlow detects product coming in and going out from the telemetry itself — with no one keying anything in. A withdrawal outside the normal flow becomes an alert and an audit record.
A level drop with no RFID fueling — possible theft or leak — detected, logged and classified.
Product coming in is born from the rising level, with volume and invoice reconciliation.
Days left to the minimum level — refill before you run dry.
The question nobody can answer without dipping the tank every day. TankFlow answers it on its own, because it already has the three legs of the equation — and whatever is left over is your alert.
opening + inflows + adjustments − outflows = expected variance = actual − expected A movement outside the automatic flow — an undetected delivery, consumption without a card — is entered as a signed record, with a reason that stays in the report. It is not about zeroing the variance: what remains is still the real alert.
Reports ready for audit and for management — on screen, by scheduled email, in CSV and PDF.
The period variance per tank, with the traffic light and every manual adjustment itemised.
Consumption by mass balance, daily rate and days to minimum.
By operator, card, vehicle, tank or client — with volume measured by the flow meter.
The tank's full timeline, exportable by date range in CSV and PDF.
The reader reuses the existing sensor and starts streaming as soon as it is provisioned. No server, no new network wiring.
Wire the reader to the 4–20 mA probe already in place — hydrostatic, radar or ultrasonic — or to the tank's resistive float.
Plug it in and connect. The device opens its own setup portal.
Scan the QR in the panel and telemetry starts flowing. Calibration and RFID in the browser.
Level, liters and temperature live, no page reload.
Energizes the pump by card, with time rules and daily limits.
Build a screen with the tanks you want, in the order you want, and leave it running on the control-room TV.
Send the wallboard as a link to people without a login — read-only, those tanks only, revocable at any time.
Refill and unaccounted loss are born from the telemetry.
Liters are counted at the pump outlet, not estimated. Level becomes the cross-check.
Plate, odometer and km/L for each vehicle, recomputed at every fueling.
Scan the vehicle QR, type the odometer, link it. No login, nothing to install.
Tank service records with photos and dates, alongside the asset sheet.
Refill before you run dry, based on real consumption.
Immersed PT100, with range alerts and future temperature correction.
Silences alerts while you work on the sensors.
Reconciliation, consumption and movements — by email, CSV and PDF.
Many clients and tanks per account, in PT, EN and JA.
Persistent queue and whitelist on the device: network drops, fueling goes on.
Calibration, commands and firmware updates from the panel.
The section above is about protecting the fuel. This one is about protecting the information — the part that shows up in the vendor questionnaire and often decides the contract.
Enforced at the data layer, not by a screen filter: one account cannot reach another’s data, even if the application slips.
The plaintext key is shown once, at setup. The platform keeps only the hash — not even support can recover it. Revocable at any time.
Who may fuel is evaluated by the same logic online and offline. Losing the network never becomes extra permission.
Wallboards and the attendant app open without a login, but each link only covers what was written into it. The platform keeps just the hash, and revoking takes effect immediately.
Your devices’ network passwords are stored encrypted (AES-256-GCM). Operator PINs and user passwords, hashed only.
Operator, manager and administrator see different surfaces. The tank owner, when granted access, sees only their own data.
Corporate login for authentication and encrypted traffic end to end, including between the readers and the cloud.
We match hardware and platform to your operation. No surprises, no fine print.
One monitoring point
Multiple tanks and clients
Operations at scale
Yes. The reader speaks any 4–20 mA probe — hydrostatic, radar, ultrasonic or capacitive — and the standard resistive float too. You do not replace the tank hardware.
With point-by-point calibration: you strap the real liters at several levels and the platform fits the level → liters curve. It works on horizontal cylinders, dished bottoms or any shape.
Yes. A level drop with no RFID fueling is automatically detected as an unaccounted loss, raises an instant alert (email, WhatsApp and push) and is logged for audit.
No. You wire the reader to the sensor, power it, point your phone at the QR and provision. Telemetry starts in minutes and the reader keeps working even offline.
The operator taps the card and the pump is energized, with time rules and daily limits per operator and per tank. Volume is measured by the flow meter at the pump outlet; without that sensor, it is estimated from the tank level drop.
Diesel, gasoline, ethanol and AdBlue/Arla32, among others. Reports include stock reconciliation, consumption, runout forecast, fueling and movements, exportable to CSV and PDF.
Yes. TankFlow is multi-tenant: you manage many clients and tanks in one account, with isolated data, in Portuguese, English and Japanese.
With a flow meter at the pump outlet, liters are counted pulse by pulse — measured, not estimated. Telemetry measures the same fueling from the tank level drop, independently, and both numbers sit side by side as a cross-check. Without the flow meter, volume still comes from the level drop.
Yes. You register the vehicle by plate and enter the odometer at each fueling; TankFlow computes km/L using the full-tank method and tracks the average per vehicle over time. An odometer lower than the previous one is flagged as suspect instead of producing negative consumption.
No. The Live Fueling app opens from a link — no login, nothing to install from an app store: the attendant scans the QR on the vehicle, checks the plate and types the odometer. The link is scoped to one client and the chosen tanks, only allows linking vehicle and odometer, and can be revoked at any time.
Yes. You build a wallboard with the tanks you want, in the order you want, and leave it live on the control-room screen. To show it to someone outside the account — the tank owner, the fuel supplier — generate a public link: whoever opens it sees only that wallboard, read-only, with no access to the rest of the account. The link can be revoked at any time.
Tell us how many tanks you have and which sensor you use. We come back with a demo in your scenario.