How should we test a fuel ordering app with our existing dispatch software?

Test the handoff with one sample order in both systems. Check the customer, delivery address, fuel, amount and order status, then change one detail and follow it through again. Custom Fuel App sends orders to its office dashboard; confirm the separate steps your existing dispatch software would need before changing your routine.

Start where the order arrives

Custom Fuel App's published workflow puts incoming orders, customer messages and status updates in the office portal. [1] Its connected driver path uses Tank Spotter. [2] Start there. Ask to see how an order would reach the dispatch software you use today.

Bring the name and version of the software your office uses today. Sketch the order's path on paper. Mark where a person types something, where a file moves and where a connection would have to do the work.

Change the order during the walkthrough

In the demo, place a sample request. Then change its address before it goes to a driver. Compare both screens. Does the old address remain anywhere? Which person checks the change before a truck leaves?

Next, ask what happens when a handoff fails. Have the presenter show how your office would find it, correct it and confirm that the right order reached dispatch. Record any manual step as manual.

Agree where staff should check

Keep a short list: customer details, order details, driver assignment and completion status. Name the system your staff should check for each item. Have the office lead walk through the steps without help. Write down who checks a failed handoff and how they know it is fixed.

Does a connected Tank Spotter workflow prove another dispatch system connects?

No. Verify the proposed connection for your software separately. Ask for its scope and the remaining office work before agreeing to replace a process.

See Custom Fuel App. Bring your dispatch steps to the walkthrough.

Last reviewed: October 18, 2026
Author: The Custom Fuel App team