TankSpotter.
Field to office.
Connected by SaaS.
Anviam worked across TankSpotter’s web and mobile applications, connecting field workflows, IoT data and office administration through a multi-tenant SaaS platform for propane and fuel operations.
From field activity
to office visibility.
- React.js frontend
- Node.js / Next.js
- PostgreSQL
- AI routing & Mapbox
Conceptual workflow illustration · Not a product screenshot
Connected Software for Field, Fleet and Fuel Operations
- The productA SaaS platform for propane and heating-oil field operations.
- Anviam's contributionWeb, mobile, IoT, routing, forms, analytics and multi-tenant access.
- The purposeConnect field execution with dispatch and management visibility.
One SaaS Platform Connecting the Office, Field and Connected Assets
Anviam worked on TankSpotter's web and mobile applications for propane, heating oil and fuel-service operations, spanning multi-tenant SaaS, IoT integration, synchronisation, fleet workflows and AI route optimisation.
Product Context
The public platform presents field service, safety documentation, dispatch, training and sales tools. This case study focuses on Anviam's supplied scope, not every current module or release.
Users and Responsibilities
Office administrators coordinate work, dispatchers organise deliveries, and drivers and technicians complete field tasks. IoT sources contribute asset data; the web panel brings operational information together.
Keeping Field Operations, Data and Decisions Connected
Engineering needs of the confirmed scope, not a reconstruction of production incidents.
One Operational Picture
Web, mobile and IoT updates can arrive at different times. Clear status, ownership and timestamps keep a pending synchronisation from being mistaken for a completed job.
Flexible Forms With Reliable Records
Dynamic forms capture the right information for each workflow while preserving validation, attachments and the form version used for a completed record.
Routing With Operational Constraints
A useful route accounts for more than distance: driver assignment, stop priority and vehicle constraints, with dispatcher review of proposed changes.
Access Across SaaS Tenants
Role permissions and tenant boundaries stay coherent across screens, APIs, files, dashboards and connected-device data.
Delivery Across Web, Mobile, Data and AI
Technology and functional scope supplied directly for this case study.
Web and Mobile Apps
The SaaS web application and mobile app, including synchronisation with the web admin panel.
React, Node.js / Next.js and PostgreSQL
React.js frontend, Node.js / Next.js backend and PostgreSQL for data.
IoT and Operational Sync
IoT data integrated with the web admin panel, and mobile workflows synchronised with office administration.
AI Routing, Mapbox and SaaS
AI route optimisation, Mapbox, fleet, fuel delivery, safety, dynamic forms, dashboards, roles and multi-tenancy.
The mobile framework, framework versions, hosting topology, hardware vendors and optimisation model were not supplied and are not inferred.
Fuel Delivery, Field Service and Connected SaaS Capabilities
Public platform features and Anviam's supplied implementation scope, distinguished below.
Dispatch and Work Orders
Public platform: schedule work, assign technicians and follow operational status.
Fuel Orders and Delivery
Public workflow: requests reach the office, drivers receive jobs, and completion updates the dashboard.
Forecasting and Route Planning
Public routing pages: upcoming deliveries, map-based stop selection, driver assignment and route order.
AI Route Optimisation and Mapbox
Confirmed scope. Exact objectives, algorithms and benchmark results are not supplied.
Dynamic Forms and Field Evidence
Confirmed dynamic-form work; store listings describe photos, signatures and tank/regulator details.
Safety and Maintenance Records
Public safety pages: inspection documentation, management alerts and issues converted into jobs.
IoT-to-Admin Sync
Confirmed scope: connected-device information synchronised with the web admin panel.
Mobile-to-Web Sync
Confirmed scope: mobile records and workflows synchronised with office administration.
Multi-Tenant Roles and Analytics
Confirmed scope: role-based access, multi-tenant SaaS and analytical dashboards.
From Fuel Demand to Dispatch, Delivery and Office Visibility
Based on public delivery and routing pages and the supplied IoT scope. Customer ordering belongs to the separate Custom Fuel App workflow.
Identify delivery demand
Review a request or scheduled delivery, with asset data where configured.
Review in the office
Assess the work with customer, tank and delivery context.
Plan the route
Group stops on the map and review the proposed sequence.
Assign driver and vehicle
Allocate the job and check vehicle and workload constraints.
Notify the driver
The job reaches the driver's app and calendar.
Navigate and perform
Follow navigation and complete the delivery or field task.
Capture forms and evidence
Record job details, quantities and supporting information.
Synchronise completion
Submit the record and confirm office status reflects it.
Review exceptions and analytics
Assess outstanding issues and dashboard information.
Multi-Tenant SaaS With Field and IoT Integration
Engineering considerations for the confirmed stack, rather than an independently inspected architecture.
Tenant isolation and role-based access
Organisation and role boundaries enforced at the API and data layer as well as the interface, with tenant scoping reviewed across PostgreSQL queries, files, background work and analytics.
Synchronisation and conflict handling
Local changes, submitted data, accepted updates and failures are kept distinct. Stable identifiers and deliberate retry behaviour avoid duplicated jobs or overwritten records.
IoT identity and freshness
Devices associated with the correct tenant and asset. Event timestamps are preserved, and stale or missing readings are communicated rather than presented as current.
Dynamic form versioning
Form definitions separated from submissions, preserving the fields, validation context and attachments of historical records when templates change.
Mapbox and AI routing
Routing objectives, input constraints and dispatcher override behaviour defined explicitly. Map rendering, navigation and optimisation are separate responsibilities.
Operational analytics
Dashboard measures and refresh semantics defined, distinguishing an operational count from a validated business outcome, with consistent tenant filters across reports.
Delivered Capability Across the Operational Chain
The supplied scope demonstrates work across web, mobile, data, SaaS permissions, IoT integration and AI-enabled routing, connecting mobile activity and device inputs with the administrative view.
Useful measures include sync failures, duplicate submissions, route feasibility, dispatcher overrides, form completeness and job status latency. No fuel savings, safety improvement, ROI, uptime or delivery-speed figure is claimed.
A Connected Office and Field Experience
Fleet, forms, dashboards and delivery workflows brought together in one multi-tenant SaaS product.
Safety Records, Privacy and SaaS Data Boundaries
Software supports documentation and review; operational compliance depends on applicable requirements, configuration, procedures and qualified personnel. No audit or certification is claimed.
Propane Safety Documentation
The safety page references NFPA 54/58 as product positioning, not verified conformity. Code editions and local requirements need expert review.
Traceable Forms and Field Records
Timestamps, authorship, form versions, attachments and controlled amendments. Digital paperwork alone does not prove an inspection was done correctly.
Location and Workforce Privacy
Limited collection of driver location, addresses, signatures and photos, with defined purposes and retention.
Tenant and Role Boundaries
Role-based and multi-tenant scope is confirmed; least privilege and organisation separation assessed across APIs, data and media.
Connected-Device and Provider Security
Device identity, credentials, transport protection, third-party processing and incident handling.
Offline and Retention Boundaries
Public pages advertise use without cellular signal; offline maps, local encryption and sync guarantees were not verified.
Why Anviam for Your Fuel and Field-Service SaaS?
Combine connected application development with domain workflows spanning dispatch, fleet operations, IoT and field documentation. See our enterprise software & SaaS and IoT development services.
Talk Through Your Project- Web and mobile experience for office teams and field users, plus the sync between them.
- Multi-tenant SaaS delivery with organisation boundaries and role-based access.
- Modern stack: React.js, Node.js / Next.js and PostgreSQL.
- IoT-connected operations with identity, freshness and access planned.
- AI routing and Mapbox alongside real dispatch constraints and human review.
- Dynamic field workflows connected to office records.
- Operational dashboards linking application data with management visibility.
- Propane and fuel context: drivers, technicians, tanks and delivery operations.
- Evidence-led acceptance criteria for sync, routing and record completeness.
Sources and evidence
Project scope supplied by Anviam. Public pages reviewed 16 October 2026; current modules may extend beyond the original engagement. No authenticated application, source code, device feed, route model or control audit was inspected, and store privacy disclosures are developer-provided.