Tanker

Tanker is two products on one operation. Households order potable water by tanker — address, volume, live tracking, reorder — in English and Arabic, priced in SAR. Riyadh Central runs the other half: a Next.js operations console for dispatch, fleet, customers, stations, and sales. Master data is synced from Alanazi Com. The console does not invent a second fleet.

Ordering a water tanker is still a phone call in many households. The customer cannot see the truck, and operations cannot see the exception. Orders, drivers, tankers, and stations lived in different tools. A premium water promise dies in that gap — on the doorstep and in the control room.

The customer job is recurring: teach the promise (watch every mile, delivered with trust), then make reorder one tap. The operator job is different. Riyadh Central opens on a live control room — active deliveries, orders today, a fleet map — then drops into dispatch. Platform orders (the app) and Alanazi Com orders are the same board with a different source, not two products. Rating tags exist so a bad delivery becomes a reason, not a vague star.

The customer app is photography-led onboarding, an EN/ع toggle, then a blue-and-white phone: order, order again, deliveries, a structured rating. The console is a dark operations shell — Riyadh Central, live badge, search across orders, drivers, and tankers. Overview is the control room and the fleet map. Dispatch splits the queue and the map. Orders, customers, drivers, tankers, stations, and sales each get a header with the numbers that matter, then the table or the cards. Arabic flips the whole shell, not just the strings.

Flutter customer app and a Next.js (React, TypeScript) admin on shared order and fleet APIs. The order lifecycle is one sequence on both sides: confirmed, searching, assigned, accepted, en route, arrived, delivering, delivered. Alanazi Com is the source for customers, drivers, tankers, stations, and water types; the console imports and reconciles, it does not fork them. EN/AR includes RTL layout on the dashboard. Invoices, ratings, and reorder all hang off the same order.

• EN/AR customer onboarding, order, reorder, and delivery history
• Structured delivery rating with tags
• Admin sign-in for company operations accounts
• Live control room: deliveries, orders, fleet map, suggested actions
• Map-first dispatch with exception and reassign
• Orders, customers, drivers, tankers, and water stations
• Sales and income with export
• Alanazi Com sync and an Arabic (RTL) overview

We did not build a public driver marketplace. The fleet stays the company’s, including third-party tankers assigned to stations. The household loop and the Riyadh console had to share one order before anything else was added.

Customer Flutter app for iOS and Android, and a Next.js operations console for Riyadh — SAR, English and Arabic, tanker photography on the customer side and a control-room shell for dispatch.

Households can order potable water, follow a delivery, and rate a named driver. Operators can see the same order on a map, assign a tanker, and reconcile customers, fleet, and stations with Alanazi Com. Utilization figures stay with operations.

A logistics product is won twice: reorder on the phone, and exceptions in the control room. I would have designed the sync states — last sync, nothing to import, station with no service area — at the same time as the happy-path map. A calm dashboard is mostly the unhappy path, labeled clearly.