Booking, quotes and labels
Portal and app booking with zone pricing, printable labels and tracking IDs, plus CSV upload for bulk senders.
Solutions · Same-day courier
A courier company is paid for two things: collecting a parcel when it said it would, and proving where that parcel ended up. This model is for operators running their own riders and drivers on same-day, multi-drop work across one city, mostly for business senders: a dispatch desk that builds runs, a driver app that scans at every handover, and a custody record that settles any argument about a missing box.
Professional plan. Enterprise customization is quoted on scope.
A scan every time a parcel changes hands
Runs built from pickups and drops together
Photo, signature or code on each drop
V1
Portal and app booking with zone pricing, printable labels and tracking IDs, plus CSV upload for bulk senders.
Manual run building with a suggested stop order and reassignment between riders.
Pickup, handover and delivery scans, photo or signature proof and failed-attempt reasons.
A public tracking page, recipient notifications and a monthly statement per business account.
Operating loop
Business senders book from a web portal or through an API wired into their shop; occasional senders use the app. Each booking gets a pickup window, a price from zone and size band, and a tracking ID printed on a label the sender attaches before the rider arrives.
The afternoon’s pickups and drops land on one board. A dispatcher, helped by a sequencing suggestion they can overrule, groups them into runs by area, vehicle space and promised windows, then releases each run to a rider’s phone in stop order.
The rider scans each label at collection, again if the parcel is passed to another rider at a depot or swap point, and once more at the door. Every scan stamps who holds the parcel, where and when, so its whereabouts are never a guess.
At the door the app asks for whatever proof the sender chose: a photo showing the label, a signature, or a code the recipient reads out. A failed attempt gets a reason, then a second try or a return leg, and the sender sees the outcome on the same tracking page.
Roles
Ships dozens of parcels a day, usually through an integration with their online store. Wants bulk labels, a cut-off time they can rely on, and a downloadable proof for any delivery a customer later disputes.
Works a run with a phone in one hand and parcels in the other. Needs large scan targets, the next stop always on screen, scanning that works in basements and lifts, and a quick way to report a shuttered shop.
Watches the day’s board, moves stops between runs when a rider falls behind and fields calls from senders asking where things are. Needs late-risk flags and rider positions, not a map crowded with dots.
Gets a tracking link, an arrival window and, for valuable items, the code to give the rider. Wants to leave instructions or pick another day without having to phone anyone.
Hard parts
Riders lose coverage in stairwells and car parks. The app has to record scans, photos and signatures locally with device time and position, queue them, and sync without creating duplicates once the network returns.
A blurry picture of a door settles nothing. Require the label to be visible in the photo or a matching code, store position and time with each proof, and keep the files for at least as long as senders can raise a claim.
A scooter breaks down at 2 pm with fourteen parcels aboard. Dispatch must split that run across other riders, log the handover scans and send every affected recipient a new window in one action, not fourteen.
Prices built on declared size drift when senders under-declare. Capture real weight or dimensions at first scan where possible, and decide beforehand whether the gap is billed, absorbed or flagged on the sender’s account.
Nobody home, wrong address, parcel refused. Each case needs its own reason code, a limit on attempts, a place where the parcel waits and a rule for who pays the return leg, or the depot fills with unclaimed boxes.
Operator controls
City zones, daily cut-offs and the services sold in each, such as two-hour, same-day and next-morning, each with its own price grid.
Every live run with stops done, stops running late and the rider’s last position, plus drag-and-drop reassignment that writes the custody change to the log.
Search a tracking ID to see every scan, photo and signature, then open, settle or reject a loss or damage claim against the declared value.
Credit limits, negotiated rates, API keys, label formats and monthly invoicing for each business customer.
Revenue
Priced by zone, size band and speed, with surcharges for extra attempts, waiting at pickup or drops outside the core area.
Lower prices for business senders who commit to daily volume, billed monthly on account rather than paid per booking.
A fee for collecting payment at the door on the sender’s behalf, with collected cash reconciled per rider and remitted to senders on a fixed cycle.
Later
Worth adding when runs routinely pass twenty stops and dispatchers can no longer order them by eye.
Needed once parcels pass through a hub between collection and drop, not while riders go direct.
Earnings screens and payroll exports matter when riders become contractors paid per delivery rather than salaried staff.
Next decision
Not sure whether you are a city courier, a vehicle-hire service or a hub network? The parcel overview sets them side by side.
Open registerWhen customers book a whole vehicle and driver for a job, often bulky goods, the Lalamove-style model prices the trip rather than the item.
Open registerIf parcels travel through sorting hubs and linehaul trucks, the FedEx-style network suits you better than a one-city courier.
Open registerOur logistics development team can scope the rider app, dispatch board and sender portal with you, then ship them in working stages you own.
Open registerLive demo
Open each app or panel in a new tab and sign in with the demo login shown. The demos run on shared sample data, carry our demo product names, and show the ready-made product before any customization.
Senders
+91 9876543210 | User_321Couriers
+91 9876543211 | Driver_321Web Version
mxunzox.mimeld.comOwners
credentials given on a callArtifact register
Reference screens illustrate workflows, not a contracted feature list. Sample prices, data, and responses are demonstration content; confirm the current scope during a walkthrough.
Deployable Product Architecture
Software project collaboration / system register
Delivery team
Team collaboration around software project planning
Define
Assemble
Deliver
Review
Deployable Product Architecture
Growth strategy review / system register
Product delivery loop
Product growth team reviewing strategy and launch plans
Discover
Blueprint
Build
Operate
Deployable Product Architecture
Open office product team / system register
Product delivery loop
Open office product team for software delivery
Discover
Blueprint
Build
Operate
Deployable Product Architecture
Product leadership meeting / system register
Product delivery loop
Product leader presenting software strategy in a meeting
Discover
Blueprint
Build
Operate
Senders rarely leave a courier over price alone. They leave after a parcel goes missing and nobody can say who last held it. A scan at every change of hands, recorded even without signal, is the feature that keeps business accounts, and it has to be designed into the rider app before anything else.
The same record serves three people: the sender checking status, the dispatcher answering a call and the claims desk deciding whether to pay. Build it once, show it to all three, and most support questions answer themselves.
Consumer bookings are irregular and expensive to win. A handful of online shops sending every weekday give a courier predictable volume to plan runs around. That is why bulk labels, an API, monthly invoicing and a reliable cut-off belong in the first release, ahead of polish on the consumer app.
Some share of drops will fail: closed offices, wrong flat numbers, refusals. Decide the attempt limit, the holding period, who is told and who pays for the return before launch, and give each outcome a reason code. Those codes become the report that shows which senders and areas cost you most.
FAQ
A courier platform handles many small parcels for many senders inside one city, with a scan and a proof for each item. Freight software plans pallets and truckloads between businesses, where trips, driving hours and delivery notes matter more than a doorstep photo.
Whatever the sender and recipient will accept if a delivery is disputed: usually a photo showing the label at the address, a signature, or a one-time code. The platform stores the proof with time and position and ties it to the tracking ID.
Yes. A booking API, shop plug-ins or a CSV upload let merchants create parcels and print labels in bulk, then receive status updates back. Most courier businesses need this early because business volume arrives through integrations.
Usually not. With small runs, an experienced dispatcher and a suggested stop order are enough. Add an optimiser when run length or rider count makes manual planning the bottleneck.
They can, if the app records each collection against the parcel and rider, and the back office reconciles cash handed in before paying it out to senders. Without that ledger, cash shortfalls are hard to trace.
Primary sources
Dated official documentation, standards, and research that support the factual claims on this page.
The identifier standard many carriers and shippers use to label and track individual logistic units.
How browsers and web apps request device position, relevant to rider tracking and proof locations.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.