Deliver orders with your own riders

If your customers are nearby, paying a courier for every drop is the expensive way to do it. Integrated couriers typically charge ₹40–₹80 per delivery; a shop’s own rider costs ₹15–₹25 for the same trip — and the person at the door works for you.

This guide covers setting up self-delivery end to end.

Before you start

• The staff who will deliver need a phone that can install the QuicShop Rider app, and a phone number you can reach them on. The number is how they sign in.
• Each branch that dispatches orders should have its coverage area and operating hours configured, otherwise it won’t be offered as a fulfilling store.
• Rider accounts are counted separately from staff accounts. Growth includes two; extra riders are ₹299/month each, on any plan.

1. Register your riders

Go to Settings → Riders in the Seller Console and add each rider:

• Name — as you’d refer to them internally
• Phone — the number they’ll sign in with
• Branch — the store (or stores) they deliver from

A rider attached to your Jayanagar branch will only appear when you’re assigning an order that Jayanagar is fulfilling. If someone covers two locations, attach both.

2. Get the rider signed in

The rider installs the QuicShop Rider app and enters the phone number you registered. They receive an OTP and they’re in.

They never get Seller Console access. The app shows them their own assigned trips and nothing else — no orders belonging to other riders, no customer list, no settings.

3. Assign an order

Open the order in the Seller Console. For orders being fulfilled by your own fleet, you’ll see Assign Rider on the fulfilment group, listing the riders attached to that branch.

Pick one and they get a push notification. They can accept or decline. If they decline, the trip returns to you for reassignment — nothing is lost and the customer sees no change.

You can reassign at any point before the order is picked up.

4. The delivery itself

The rider moves the trip through each stage in the app:

1. Picked up — they have the order and are leaving the store
2. En route — the customer’s order page starts showing the live map
3. Delivered — they complete proof of delivery and collect cash if the order is COD

Your proof-of-delivery policy decides what the app asks for: an OTP the customer reads out, a photo of the handover, or a signature. If the policy allows any of the three, the rider picks whichever suits the doorstep.

If the delivery can’t be completed, the rider marks it failed with a reason — customer not available, refused, address not found, or damaged at pickup.

5. Return pickups

Riders handle returns the same way. A reverse trip is assigned, the rider collects from the customer, captures proof of pickup, and marks it returned to the branch.

What the customer sees

A tracking page for their order showing the rider’s name, a masked contact number, and the live map once the rider is en route. If your policy uses OTP delivery, their code is on that page too.

The rider never sees the customer’s full phone number, and the customer never sees the rider’s.

Checking how it’s going

Reports → Delivery shows delivery performance across your branches.

Known limits

• Location updates stop when the app isn’t in the foreground. If the rider locks their phone or switches to another app, the customer’s map pauses until they open it again. Tell your riders to keep the app open on a trip.
• Push notifications need to be provisioned for your store before go-live. Until that’s done, the app falls back to polling — assignments appear within about 30 seconds, and an active trip refreshes about every 15 seconds.
• A failed own-fleet delivery does not automatically raise a return. If a rider marks a delivery failed and the goods come back, create the return manually.
• Rider payouts and ratings aren’t part of QuicShop. Pay your riders however you already do.