
Where Analytics fits
08 Retain is the operating context.
This page should not feel like an isolated feature sheet. It belongs to a role, a stage, a control, and an outcome in the Haultro operating spine.
The challenge
- ! Operational and finance teams rebuild the same totals from separate exports.
- ! A credible-looking demo number is dangerous when a real endpoint fails.
- ! Current device state gets mislabeled as historical uptime.
- ! Revenue is overstated when void or unpaid records are silently treated as collected cash.
- ! Teams need the source period and limitations beside each result.
What it does
- ✓ Report route, stop, pickup, service-event, and fill-reading totals for a bounded date range.
- ✓ Report billed revenue, recorded disposal fees, maintenance labor, and maintenance parts.
- ✓ Show current device status, battery, signal, firmware, and real fill-reading battery trends.
- ✓ Calculate pickup weekday patterns and prediction accuracy from recorded values.
- ✓ Preserve explicit no-data and API-failure states instead of generating plausible substitutes.
- ✓ Use existing SLA, anomaly, client-health, and enterprise rollup workspaces for their governed records.
Inside the module
What your team can work with.
Analytics · Connected to the work on the groundClaim-safe reporting
A missing endpoint is not a KPI
The production client no longer catches report failures and replaces them with deterministic demo values. Users see real tenant records, a true empty state, or an explicit error.
Operational totals retain the selected source period.
Financial labels distinguish billed revenue from recorded costs.
Current device status is not described as historical uptime.
Unavailable AI or report providers remain visibly unavailable.
Connected across the platform
One source of truth.
Routing & dispatch
Routes, stops, pickups, and service events feed the bounded operations report.
Disposal & weight
Recorded weight-ticket disposal fees feed the financial cost view.
Billing & invoicing
Non-void invoice totals provide billed revenue; the report does not relabel it as collected cash.
Maintenance
Recorded labor and part costs contribute to the current financial report.
How it works
Adopting analytics.
Choose the period
Select a bounded date range for operational or financial evidence.
Query tenant records
The API aggregates only records inside the authenticated organization scope.
Label the measure
Haultro distinguishes current snapshots, billed totals, recorded costs, and stored prediction scores.
Act on what exists
Review the source-backed result or the explicit empty or unavailable state; no generated substitute is shown.
Standards & compliance
Built in, not bolted on.
FAQ
Questions, answered.
Where do the report numbers come from?
Operations use route, stop, pickup, service-event, and fill-reading records. Financial reports use invoices, contracts, weight tickets, maintenance labor, and maintenance parts. Device health uses current device records and real battery readings.
Is billed revenue the same as collected cash?
No. The financial report labels non-void invoice totals as billed revenue. Payment operations and accounting records are used when a cash or ledger question requires that distinction.
Does device health show historical uptime?
No. The current report shows a present online-rate snapshot and labels it that way because the schema does not contain a complete historical status-transition table.
Can I build and schedule arbitrary reports?
Not in the current production contract. Haultro ships the source-backed report families above; saved custom builders and scheduled PDF or CSV email delivery are not advertised as active.
What happens when an API or AI provider fails?
The interface shows an error or unavailable state. Production does not replace the failed result with mock revenue, utilization, recommendations, or device data.
Get started
See analytics on your routes.
We'll tailor a demo to your fleet and the business you run.