Interactive Prototype Mon 4:05 PM
STEP 0/17
Press Next Step to walk the client through a full order β€” or just tap around inside the phones yourself.Everything is live: an order placed in the Customer phone appears instantly in the Rider, Vendor and Admin phones.
READY
Customer AppAndroid Β· end users
WashWala4:05 β–ͺ β–« πŸ”‹
Rider AppAndroid Β· pickup & return riders
WashWala Rider4:05 β–ͺ β–« πŸ”‹
Vendor AppAndroid tablet Β· laundry shops
WashWala Partner4:05 β–ͺ β–« πŸ”‹
Admin / OpsAndroid + web Β· your client's team
WashWala Ops4:05 β–ͺ β–« πŸ”‹

What the client is looking at

Every order is offered to the shop first. Until the shop taps Accept (2-minute timer), the pickup job sits in PENDING_VENDOR and no rider can be dispatched β€” so you never send a rider to a shop that is full, closed, or doesn't do that service. Reject opens a reason sheet, the customer is told instantly and offered nearby alternatives.

After acceptance: one order = two separate rider jobs. Job 1 (Pickup) ends the moment the bag is scanned in at the shop. Two days later the vendor taps Mark Ready, which creates Job 2 (Return) β€” usually assigned to a different rider. Watch the Rider phone auto-switch accounts at step 14 to show exactly that. COD is collected on the return leg, so the cash ledger settles against the delivery rider, not the pickup rider.