Merchant delivery and dispatch Design concept
Wasl
A Kuwaiti dispatch workspace and driver app connecting merchant orders, local areas, current assignments and delivery evidence.
We designed Wasl for a delivery team serving Hawalli, Salmiya and Kuwait City. The workspace supports assigning the right available driver; the app gives that driver the location and detail needed for the next task.
Client in the design study
Wasl Merchant Delivery — fictional client
Hawalli, Salmiya and Kuwait City
Project brief
A fictional delivery team needs Arabic dispatch and a driver app with clear next tasks and delivery evidence.
Design scope
- Local-map dispatch workspace
- Arabic driver app
- Identity and delivery-evidence journey
01 / The project challenge
The project challenge
A merchant may be waiting for collection while new requests need different timing or vehicles. A map alone hides access notes and pickup status; a list alone hides geographic context. The brief called for location alongside assignment decisions and separate states for merchant readiness, driver movement and parcel collection. Delivery also needed explicit evidence instead of a colored pin suggesting that work was complete.
02 / The solution we designed
The solution we designed
A detailed local map sits beside tasks filtered by area and state, with driver cards showing current assignments. A dispatcher reviews shipment type, pickup point and merchant notes before assigning. Mobile presents one primary task and next destination, supporting pickup, arrival notes and delivery evidence. Requested windows and team updates are shown without unsupported guaranteed travel times. Order reference and merchant name remain consistent across workspace and app.
03 / The experience
The experience
A Safat Store request travels from Hawalli to Salmiya. The dispatcher checks readiness and requested delivery time and assigns Khaled, who is working near the collection point. His app shows the merchant and loading-entrance note. He records collection before moving to the customer address, then records the recipient and delivery note on arrival. The completed record includes time and evidence, so the dispatcher need not call every party or infer delivery solely from vehicle location.
04 / What it could do
What it could do
Area-aware dispatch
Review order location, state and shipment readiness before assignment.
One task record
Connect merchant, collection point, destination and access notes.
Driver app
Show current task, next destination and collection and delivery actions.
Delivery evidence
Record recipient, time and notes instead of relying on a pin color.
05 / A typical journey
A typical journey
Ready
Capture the merchant order, shipment type and requested timing.
Assign
Choose a driver after reviewing area and current work.
Move
Record pickup and review destination and access details.
Deliver
Retain recipient, time and final update in the task history.
06 / Inside the interface
Inside the interface
Explore the Arabic web interfaces and companion app. The screens share a consistent identity and Kuwaiti sample workflows.
Explore the screens.
Open any screen to explore the complete project gallery.
07 / Design direction
Design direction
Deep blue with limited orange highlights gives Wasl a local operational identity. Natural street networks and Arabic neighborhood labels make the map useful context rather than an anonymous grey grid. Desktop has practical dispatch density; mobile uses large actions and a clear current destination. Location does not crowd out loading or delivery notes, and text accompanies icons so states remain understandable.
Discuss a similar idea
