Fleet management for large supply partners
Large fleet operators running 40+ buses on SWVL's network had no dashboard to manage their vehicles and drivers. The Vendor Portal gave them a single surface to monitor fleet status, manage driver assignments, and track contract performance.
Large operators managed 40+ buses through SWVL ops manually.
Fleet partners operating 40 or more buses under contract had no self-serve tool. Fleet status, driver assignments, and performance data lived in spreadsheets and ops team calls, a high-touch process that didn't scale as SWVL's supply network grew.
Design lead, with Mahmoud Isaac (design) and Habiba (research).
UX strategy, interaction design, prototyping, and research alongside PM lead Ahmedyar. Ran discovery with supply partners directly to map the existing manual workflows before designing replacements.
A self-serve fleet dashboard that reduced ops dependency.
Vendors could monitor their active fleet, track driver assignments and availability, and see contract performance metrics without routing requests through SWVL's operations team.
SWVL's supply network was scaling. The tooling hadn't.
A large vendor partner running 50 buses under contract shouldn't need a phone call to know which drivers are on shift. The Vendor Portal was built to close that gap, and to make large-operator onboarding fast enough to support SWVL's expansion into new cities.
Map the manual workflow first. Replace the highest-friction parts.
Before designing anything, we ran discovery sessions with supply partners to document what they actually did today: which spreadsheets, which calls, which reports they built manually. The portal's first version was a direct replacement for those workflows, not a redesign of them.
-
Fleet status visibility
Vendors had no live view of which buses were active, idle, or unavailable. We built a fleet overview that showed status per vehicle in real time, with filters for zone, shift, and driver assignment.
-
Driver management
Driver-to-vehicle assignment was handled through ops team calls. We gave vendors a driver roster with assignment history, shift scheduling, and the ability to reassign directly, without involving SWVL operations.
-
Contract performance
Vendors couldn't see their own performance against contract terms (utilisation, on-time rate, rejection rate) without requesting a report. We surfaced these metrics on the portal home screen so vendors could self-monitor and flag issues early.
Reflections
B2B tooling for marketplace supply partners is a genuinely underdesigned space. The vendor is a power user who knows their workflow deeply, tolerates more density than a consumer, and cares about data accuracy above all else. Designing for them requires unlearning a lot of consumer UX instincts.
The discovery sessions with vendor partners were the most important work on this project. The gap between what the ops team believed vendors needed and what vendors actually did every day was significant. The design would have been wrong without closing that gap first.