AFMS vendor portal

From pickup request to reset,
in one shared record.

AFMS gives tank owners, vendor dispatchers, drivers, and back-office teams one shared workflow from request creation through scheduling, dispatch, at-tank proof, invoice or credit closeout, and reset.

Schedule a Demo Talk to a dealer about portal access Explore product details

AFMS vendor portal showing dispatcher queue with Acknowledged, Dispatched, Pickup Complete status rows and mobile app with QR scan, gallons, photo and signature capture

Dispatcher queue · field proof · closeout

Requested

→

Acknowledged

→

Dispatched

→

Pickup Complete

→

Reset / Ready

1-second updates

QR-first iOS and Android app

Offline store-and-forward

Photos and signatures

Audit-ready closeout

Full lifecycle

More than a monitor. More than a pickup portal.

The AFMS portal is the operating flow that connects tank context, request ownership, dispatch, field execution, proof, and closeout.

RequestedPickup demand exists from sensor context or manual entry.

AcknowledgedA responsible party has received the request and owns it, but a pickup window is not yet confirmed.

Scheduled / DispatchedThe pickup window exists and truck / driver ownership is visible.

Pickup CompleteCore field work is done and gallons are captured.

Invoice / Credit PendingOperational work is done, but financial closeout is still open.

ClosedNo further operational action is pending.

Reset / ReadyThe cycle is cleared and the asset is ready for the next request.

Dispatch with ownership

Move past “someone saw the alert”

AFMS helps dispatch teams move from floating alerts into true ownership. Every request has a responsible party, a timeline, and a status that everyone can see.

At-tank execution

Built for drivers, not extra paperwork

The QR-first iOS and Android app helps drivers confirm the right asset, preserve route context, and complete the stop in a few taps.

End-to-end proof

The workflow doesn’t end at pickup complete

Before and after state stays attached to the same record

AFMS can capture before and after state, gallons, photos, signatures, timestamps, and exception notes at the tank.

Closeout that includes the back office

AFMS supports invoice or credit closeout so financial references can stay tied to the operational record before the request resets.

No. It is a shared workflow for tank owners, vendor dispatchers, drivers, and closeout teams.

Acknowledged / Pending Scheduling. That step shows the request is owned before a pickup window is committed.

Before and after state, gallons, photos, signatures, timestamps, and exception notes.

Yes. The field layer is designed around offline store-and-forward.

It should not. The deeper AFMS story includes invoice or credit closeout and reset / ready status.

By role

Value by role

Dispatcher / vendor admin

Cleaner queue ownership and scheduling visibility.

Driver / technician

Faster at-tank workflow with less paperwork.

Site manager

Cleaner proof and fewer update calls.

Back office

Invoice or credit closeout tied to the service record.

Schedule a Demo Find dealer

See it live

From floating alerts to full dispatch ownership — in one demo.

Schedule a walkthrough of the vendor workflow, connect with an authorized dealer, or explore the safety and compliance layer.

Schedule a Demo Find dealer Safety and compliance

From pickup request to reset,in one shared record.