Deliver a continuous reconciliation between fuel received into storage tanks and fuel dispensed at pumps, flagging discrepancies that indicate theft or pilferage. Verified tank-level readings are compared against pump dispensing data continuously, so an unexplained discrepancy surfaces for investigation before losses accumulate.
Turn undetected shrinkage into a continuous tank-to-pump reconciliation that flags theft early.
01.
External Data Oracles anchor verified tank-level readings, so the fuel received into and held in storage is a trusted, continuously updated figure.
02.
Dispensing data from each pump is anchored alongside tank levels, giving a matched pair of received and sold volumes to reconcile.
03.
The Audit Logs module continuously compares tank input against pump output, so shrinkage is measured in real time rather than at a periodic stock check.
04.
The Notifications module flags any unexplained variance beyond tolerance, alerting the operator to possible theft before losses accumulate.
05.
Each flagged discrepancy carries its supporting tank and pump data, giving the operator an evidence trail to investigate the loss.
06.
By surfacing discrepancies early and continuously, the network turns slow, after-the-fact loss discovery into prompt, evidence-based intervention.
Follow a single reconciliation cycle from tank reading through pump comparison to a flagged discrepancy.
06:00:02
[SYS] Reading tank gauge TNK_14...
06:00:02
[CMD] anchorTank(tank: "TNK_14", litres: 18420)
06:00:03
[AUTH] Verifying gauge signature...
06:00:03
[OK] Tank level sealed for cycle.
Cerulea decomposes pilferage detection into modular contracts. Each layer anchors tank levels, captures pump output, reconciles the two, and alerts on discrepancy.
Tank-to-pump reconciliation is a horizontal capability. Here is how different actors in fuel retail put the shared ledger to work.
Catch shrinkage between tank and pump continuously, flagging theft or pilferage with evidence before losses accumulate rather than discovering them at a stock check.
Key Asset Types
Monitor reconciliation across many outlets from one record, spotting persistent losses and comparing shrinkage patterns network-wide.
Key Asset Types
Investigate flagged discrepancies with a supporting on-chain evidence trail, building loss-prevention cases on verified tank and pump data.
Key Asset Types
Whether you are bridging forecourt automation systems or reading directly from tank gauges and pump controllers, Cerulea routes both into one reconciliation ledger.
For outlets on legacy forecourt automation. Tank and pump data is translated into signed on-chain records through the API gateway automatically.
Forecourt Automation
Outlet Systems
Cerulea API Gateway
Reading Hashing & Signing
Cerulea Private Chain
Reconciliation Ledger
For tank gauges and pump controllers with edge connectivity. Each reading is signed by a device key and routed straight to the reconciliation contract.
Gauge / Pump Edge
Forecourt Hardware
Consortium Validators
Reading Consensus
Cerulea Ledger
Tank-to-Pump Record
Building pilferage detection with tank anchoring, pump capture, and continuous reconciliation from scratch requires specialised engineers and long integration cycles. Calculate your exact deployment speed using Cerulea.
Traditional Deployment
Solidity Coding & Audits
~ 11 Months
Visual Compilation
WASM Logical Artifacts
~ 4 Weeks
The legacy timeline reflects forecourt monitoring integration benchmarks. Wiring tank and pump feeds, building custom reconciliation logic, and shipping discrepancy alerting for an average outlet network takes a baseline of 7 months. Building the same architecture on Cerulea takes a baseline of 2 weeks, because Cerulea Studio visually translates your reconciliation and alert rules into pre-audited WebAssembly binaries and provisions the reconciliation ledger instantly.