Hyperlocal Margin Is Won or Lost in Minutes
A same-city parcel has no depot and no sort. It is a pickup, a ride across town, and a drop, usually promised within the hour. Each job earns little, so the business comes down to how fast a rider is assigned, how many drops share one trip, and how rarely a rider has to bring a parcel back.
The Parcel Lifecycle
Six states, most measured in minutes. The wait for a rider at pickup is where most of the delay comes from.
- State 01BookedSender or merchant books; price fixed by distance and vehicle.
- State 02AssignedNearest suitable rider accepts, usually inside two minutes.
- State 03Picked upParcel photographed and confirmed at the pickup point.
- State 04In transitRecipient gets a live tracking link and ETA.
- State 05DeliveredOTP, photo, or signature captured; COD collected.
- State 06ClosedFailed drops returned the same day; rider paid, merchant settled.
Courier-Specific Features, Not Generic Delivery Ones
Five Surfaces, Configured for Hyperlocal
Hyperlocal adds two surfaces food does not need: a dashboard for merchants who ship every day and a dispatcher console for live exceptions.
Instant quote by distance
Price shown before booking, set by distance, vehicle, and time of day.
Vehicle choice
Bike for small parcels, car or van for bulky ones, each with its own weight limit.
Instant or scheduled
Send now, or pick a window and pay less for a batched run.
Multi-stop bookings
One pickup, several drops across the city, priced as a single trip.
Live tracking link
Shared with the recipient, showing the rider on the map and a live ETA.
Cash on delivery
Declared amount collected at the door and credited to the sender's wallet.
Nearest-rider offers
Jobs offered by distance to pickup and vehicle type, with a short accept window.
Batched pickups
Several merchant orders collected in one stop and dropped in ETA order.
Pickup and drop proof
Parcel photo at pickup; OTP, photo, or signature at the drop.
In-app navigation
Turn-by-turn to each stop, with masked calling to sender and recipient.
COD collection
Cash or card taken at the door and reconciled against the rider's balance.
Earnings per job
Pay shown before accepting, including distance, waiting time, and COD handling.
Bulk and API booking
CSV upload, storefront plugin, or API, each creating the same delivery job.
Batch cut-offs
Orders collected at set times so one rider takes several at once.
Contract rates
Per-merchant pricing by distance band and vehicle, with volume tiers.
Webhooks and tracking
Every status pushed to the merchant's system so their support team has answers.
COD remittance
Collected amounts reported per order and paid out on the agreed cycle.
Monthly invoicing
Account billing with waiting-time and return charges itemised.
Auto-assign rules
Radius, vehicle, rider rating, and batch capacity decide who is offered a job.
Manual override
Reassign or split a batch from the live map when auto-assign stalls.
Zone demand view
Open jobs and online riders per zone, so surge or incentives go where they are needed.
Pickup delay alerts
Riders kept waiting at a merchant flagged with the time, which feeds waiting charges.
Failed-drop queue
Unreachable recipients and refusals routed back with a reason and a return decision.
Third-party overflow
Jobs pushed to a partner fleet when no own rider accepts within the window.
Assignment and ETA reporting
Time to assign, time to pickup, and on-time drops by zone and hour.
Rider productivity
Drops per hour, idle time, and acceptance rate by rider and vehicle.
Pricing rules
Base fare, per-km rate, vehicle multipliers, and peak surcharges changed without a release.
Rider pay rules
Per job, per km, waiting time, and incentives configured per city or fleet.
Service zones
City boundaries, no-go areas, and radius limits for each vehicle type.
Claims and liability
Lost or damaged parcels logged against the pickup photo and the job timeline.
Integrations
Most same-city volume comes from merchants shipping their own orders, so the merchant-side connectors matter more here than the consumer ones.
Where Hyperlocal Margin Actually Goes
Four levers the platform exposes as configuration. Every one of them is a rule your ops team changes, not a release.
Assignment time
Drops per rider hour
Vehicle mix
Return trips
Courier & Parcel FAQ
Questions specific to running hyperlocal courier and parcel delivery on DeliveryStack.
Still have questions? Contact our support team
Does it handle intercity or next-day courier? +
No. DeliveryStack is built for same-city pickup and drop: instant and scheduled jobs moved by riders within one service area. Hub sorting and line-haul between cities are outside its scope. Operators who need an intercity leg usually hand it to a partner carrier through the API.
Can we offer instant and scheduled delivery together? +
Yes. Instant jobs go straight to the nearest rider. Scheduled jobs are held until their window and batched with others going the same way, which is why they can be priced lower. Both run on the same fleet.
How do merchants send orders? +
Through the business dashboard, by CSV upload, from a storefront plugin, or through the delivery API. Merchants set pickup cut-offs, and their orders are grouped into batches at each cut-off. Every status is pushed back by webhook.
Can hyperlocal parcel run alongside food or grocery? +
Yes, and it is a common pairing. Parcel jobs fill the hours between meal peaks on a shared rider pool. Dispatch rules decide which riders see which job types, and settlement stays on one run.
How is rider pay calculated? +
Per job, per km, waiting time at pickup, COD handling, and incentives, in any combination, configured per city or fleet. Riders see the payout before they accept. Changing pay rules is admin configuration, not a release.
Launch Your Courier & Parcel Platform
Three steps from rate card to live same-city pickups.
Zones and pricing
Service area, vehicle types, per-km rates, and peak rules configured, with contract rates for your first merchants.
Riders and proof
Riders onboarded by vehicle, assignment radius set, and the proof required at pickup and drop agreed.
Pilot one zone
One zone, a handful of merchants, and instant bookings open, then add zones, batching, and the API.