What is measured in the tank?
Tank reading, unit, method, time, operator, capacity, product, and evidence.
Track tank levels, fuel receipts, issues, transfers, usage, reorder points, and book-to-physical variance in one configurable operating system.
Built for fleets, yards, construction sites, and facilities that need accountable fuel records alongside their telemetry, finance, or compliance systems.
Use Jodoo for configurable operational capture and follow-up; keep automatic measurement, finance, and regulated compliance in the systems that own them. Inspect the working tank records and dashboard, then adapt the fields, owners, tolerance, and replenishment rules to one real fuel operation.

Open the app, review the tank records, sites, inventory status, and replenishment views, then adapt the fields, owners, tolerance, and exception rules to one real fuel operation.
A fuel inventory management system records fuel held by site and tank, every receipt and withdrawal, the measured closing quantity, the resulting book-to-physical variance, and the owner of any replenishment or exception. It gives operations one auditable trail from tank reading to decision.
Reviewed July 29, 2026 by the Jodoo operations content team using the working app shown below.
A useful system must answer three different questions without mixing them into one quantity.
Tank reading, unit, method, time, operator, capacity, product, and evidence.
Opening balance plus receipts and transfers in, less issues, usage, and transfers out.
Reorder, confirm a delivery, correct a record, investigate variance, escalate risk, or close the period.
Record the site, tank, fuel type, reading time, measured quantity, method, and operator.
Capture deliveries, issues, transfers, returns, and adjustments with quantity, source, destination, and evidence.
Roll opening inventory forward with receipts and withdrawals using one agreed unit and cutoff time.
Compare measured closing inventory with expected closing inventory and apply a documented tolerance.
Assign unexplained loss or gain, missing readings, and delivery mismatches to a reviewer with a due date.
Use reorder status and days of supply to act, then retain the reading, evidence, decision, and closeout history.
| Record | Fields to capture | Decision supported |
|---|---|---|
| Tank and site master | Site, tank ID, fuel type, capacity, unit, reorder point, owner, active status | Identifies where fuel is held and which operating rule applies. |
| Physical reading | Reading time, measured volume, method, operator, evidence, water reading if required | Creates the physical closing quantity used in reconciliation. |
| Receipt or delivery | Supplier, delivery reference, ordered and received quantity, timestamp, tank, proof | Confirms what entered the tank and exposes delivery differences. |
| Issue or usage | Asset, vehicle, equipment, job, meter, operator, quantity, purpose, timestamp | Connects fuel leaving the tank to a responsible use. |
| Transfer or adjustment | Source, destination, quantity, reason, approver, linked records | Prevents internal movements and approved corrections from becoming unexplained loss. |
| Reconciliation result | Expected close, measured close, variance, tolerance, reviewer, status, closeout evidence | Turns a difference into an owned decision instead of a dashboard-only number. |
Use one tank and one measurement period. Enter the accepted opening balance, movements, measured closing quantity, and your operating tolerance.
The absolute variance exceeds 0.50%. Check readings, movements, units, timing, and evidence.
Download the CSV with formulas for expected closing inventory, quantity variance, variance percentage, and review status. Replace the sample row and copy the formulas downward.
Switch between working views below. Click any preview to open the Jodoo app and inspect the configurable fields and navigation.
Each alert needs a condition, a responsible owner, evidence, and a closeout rule.
| Signal | Example condition | Required action |
|---|---|---|
| Low stock | Measured or projected quantity is at or below the reorder point | Confirm demand, supplier lead time, requested quantity, owner, and delivery status. |
| Missing or stale reading | No accepted measurement by the site cutoff | Notify the site owner and keep the period open until a valid reading is recorded. |
| Delivery mismatch | Received quantity differs from the delivery or purchase record beyond tolerance | Hold confirmation, attach evidence, and route supplier or receiving follow-up. |
| Unexplained variance | Measured closing differs from expected closing beyond the operating tolerance | Check readings, movements, unit conversion, timing, and evidence before approval. |
| Unusual consumption | Usage rate deviates from the site, asset, hour, or distance baseline | Review the asset, operator, job context, idle time, and possible data error. |
| Possible leak or regulated event | A reading or reconciliation result meets the organization's escalation rule | Follow the applicable specialist monitoring, safety, environmental, and reporting procedure immediately. |
For underground storage tanks in the United States, inventory control can be part of regulated release detection. Follow the applicable EPA, state, and local requirements; do not rely on a configurable workflow alone as the compliance authority. Read EPA guidance
The implementation method can be manual entry, controlled import, API, or a validated integration. Define the approved source and destination before building the workflow.
Choose the source, unit, cutoff time, and evidence owner for each input.
Use forms, workflows, permissions, reminders, and dashboards around the operating decision.
Send confirmed status or references onward without creating competing inventory truth.
Important: “Connect” does not mean every source has a prebuilt native connector. Confirm the available export, API, authentication, field mapping, sync direction, frequency, and error ownership during implementation.
Start with system ownership and required measurement sources, then evaluate workflow flexibility.
| Requirement | What to verify | Jodoo fit or boundary |
|---|---|---|
| Field and mobile capture | Can operators record readings, deliveries, usage, transfers, evidence, and timestamps at the point of work? | Jodoo can configure forms, required fields, permissions, and mobile-accessible workflows. |
| Tank and site model | Can records separate site, tank, product, capacity, unit, status, and responsible owner? | Use linked Jodoo forms for site, tank, reading, movement, and exception records. |
| Reconciliation controls | Can the system calculate expected close, variance, tolerance, review status, and approval history? | Configure calculations and workflow for the agreed operating rule; validate regulated methods separately. |
| Replenishment workflow | Can low stock become an owned request with supplier, lead time, quantity, due date, and delivery status? | Jodoo fits configurable requests, approvals, reminders, and dashboards. |
| Automatic tank or vehicle data | Are ATG probes, dispenser controllers, fuel cards, GPS, CAN bus, or telematics required? | Use the specialist source system and integrate or import the approved data into Jodoo when useful. |
| Finance and compliance | Must the system own valuation, invoices, tax, leak detection, permits, or regulatory reporting? | Keep those records in accounting, ERP, environmental, or regulated fuel systems; use Jodoo for the operating handoff. |
(measured close − expected close) ÷ expected close × 100Shows whether physical fuel and the movement record agree.
usable fuel on hand ÷ average daily usageSupports replenishment timing without treating a static reorder point as the full forecast.
accepted readings ÷ scheduled readings × 100Separates missing operational data from true fuel variance.
received quantity − delivery record quantityHighlights supplier, meter, timing, or receiving differences.
fuel used ÷ miles, hours, output, or job unitConnects consumption to the operating measure that explains it.
exception closed time − exception opened timeMeasures how quickly unexplained differences and replenishment risks are resolved.
Map the opening reading, receipts, issues, transfers, measured close, variance rule, exception owner, replenishment action, and source system for one real tank before scaling.
A fuel inventory management system records fuel by site and tank, physical readings, receipts, issues, usage, transfers, expected stock, book-to-physical variance, replenishment, and exception ownership.
Calculate expected closing inventory as opening inventory plus receipts and transfers in, less issues, usage, and transfers out. Compare it with the measured closing quantity, apply a documented tolerance, and investigate differences before closeout.
Capture the site, tank, fuel type, capacity, unit, reading time and method, receipts, issues, transfers, asset or job use, reorder point, expected and measured stock, variance, evidence, reviewer, and status.
Yes. Jodoo can use linked site, tank, reading, movement, replenishment, and exception forms, with filtered views and dashboards by site, tank, product, status, owner, or date. Teams can access configured workflows from desktop or mobile devices.
No. Use ATG, dispenser, fuel-card, GPS, vehicle telematics, or other specialist systems when automatic measurement and equipment control are required. Jodoo can manage the surrounding records, review, ownership, and follow-up, and can import or integrate approved source data.
Not by itself. Keep regulated leak detection, environmental reporting, permits, valuation, invoices, tax, and accounting in the applicable specialist or system-of-record platform. Use Jodoo for configurable operational capture, approvals, exception handling, and dashboards.