WATR: Water ordering and delivery platform

Who it is for

If you deliver water by tanker, your office phone never stops. Customers order by phone, then call again to ask where the tanker is. The office hunts for each driver, and a text that fails to send is lost. In WATR the customer, the driver and the office see the same order, each in their own app or dashboard.

How a working day runs

The customer opens a new order and picks the quantity in cubic meters and the water type: drinking, filtered or non-drinking. They choose the earliest delivery or a day and time slot, then pin the address on the map. They pay the driver in cash on delivery and can add a discount code. The driver's app receives the order with the address, route and next stop. The customer follows the tanker on the map, and a text tells them it is on its way. The current order sits on the home screen, and every order under My Orders. The office sees every driver and order on its dashboard and spots a late order before the customer calls.

What makes the difference

• Every text enters a send queue that retries when delivery fails and records the result of each attempt.
• Customer app, driver app and dashboard read one tanker position, so the office sees what the customer sees.
• A customer who picks a recurring order gets a reminder message to reorder from the app without calling the office.
• Before confirming, the customer sees the price, tax, discount and total, so they know what they will pay the driver.

How it is built

We built the customer and driver apps in Flutter, since both follow the same order on one map. Firebase holds the order and the tanker's live position, and the operations dashboard reads the same picture. Cloud Functions run server-side work that should not depend on a phone, such as sending texts. A send queue with retry resends failed texts and logs the result, and Maps draws the route.