Industries · Delivery & courier
Delivered first time,settled the same night.
We build courier systems that connect merchant orders, hub sorting, rider runs, delivery attempts, returns and cash on delivery — so every parcel and every dirham can be traced from pickup to merchant payout.
- Merchant orders
- Hub sorting
- Rider app
- Failed attempts
- Returns to merchant
- Cash on delivery
- Merchant settlement
- Tracking links
01Where courier margins go
The parcel is cheap. The second attempt isn't.
Courier businesses rarely lose money on the first run. They lose it on re-attempts, returns nobody chases and cash that takes days to reconcile.
01Failed attempts are logged as one word: “not available”
What happens
Riders mark a parcel as failed with no reason, no call record and no photo. The parcel goes back on tomorrow's run with the same address and the same phone number.
What it costs
Second and third attempts on parcels that were never going to be delivered, merchants who complain, and riders paid for drops that didn't happen.
With one system
Every failed attempt needs a reason, a call log and a location stamp. The customer gets a link to reschedule or correct the address before the parcel goes out again.
02COD cash is counted at the end of the shift, by hand
What happens
Riders return with cash and card-machine slips. A supervisor counts it against a printout of delivered parcels, and differences are written in a notebook.
What it costs
Shortages discovered days later, disputes with riders, and merchants waiting longer than they should for their money.
With one system
Each rider's expected cash is calculated live from delivered COD parcels. Hand-in is recorded against that figure, and any difference is flagged on the spot.
03Merchant settlements are built in a spreadsheet every week
What happens
Finance exports delivered parcels, deducts delivery fees, COD charges and returns by formula, then sends each merchant a statement by email.
What it costs
Late payouts, merchants who question every statement, and a finance team that spends its week rebuilding the same file.
With one system
Settlements are produced from parcel records: collected COD minus agreed fees and return charges, per merchant, with a statement every merchant can check line by line.
04Returns sit in the hub until someone notices
What happens
Parcels refused or undeliverable after the final attempt are put on a shelf. Merchants find out when their customer complains or their stock count is short.
What it costs
Shelves full of other people's stock, return fees that are never charged and merchants who lose trust in the service.
With one system
Return-to-merchant is a tracked flow with its own stage, reason, charge and pickup — and merchants see every return waiting for them.
05Sorting depends on the one person who knows the zones
What happens
Incoming parcels are sorted by an experienced supervisor who knows which areas each rider covers. When he's off, the morning is slow and runs are uneven.
What it costs
Late dispatch, riders crossing each other's zones, and some runs carrying twice as many drops as others.
With one system
Parcels are scanned in and allocated to zones and runs automatically from the address, with supervisors adjusting the balance on one screen.
06Merchants call to ask where their parcels are
What happens
Account managers relay merchant questions to the hub, who relay them to riders on WhatsApp.
What it costs
A support team that never catches up, and merchants who move volume to whichever courier answers faster.
With one system
A merchant portal shows every parcel, attempt, return and settlement live, so the team only handles real exceptions.
02Courier platform preview
What your courier system could look like.
From the morning sort to the night's cash hand-in and the weekly merchant payout — switch between the screens your hub, riders and finance would use. Every screen is designed per operation in discovery.
Illustrative interface with sample data — your system is designed around your zones, merchants and rider model.
Illustrative demo · sample dataPicture tonight's cash hand-in already reconciled?
Build your courier system03Solutions
Courier modules — built around your network.
Orders in without retyping
Merchant orders & pickups
Merchants create parcels by API, plug-in, bulk upload or portal. Each parcel gets an airway bill, label, COD amount and service type, and pickups are scheduled from the merchant's location.
- API, e-commerce plug-ins and CSV upload
- Labels and airway bills
- Service types and cut-offs
- Scheduled and on-demand pickups
Orders in without retyping
Merchant orders & pickups
Merchants create parcels by API, plug-in, bulk upload or portal. Each parcel gets an airway bill, label, COD amount and service type, and pickups are scheduled from the merchant's location.
- API, e-commerce plug-ins and CSV upload
- Labels and airway bills
- Service types and cut-offs
- Scheduled and on-demand pickups
Not every courier needs every module. We scope the ones your operation actually uses, and add the rest when you need them.
04AI inside the system
AI that cuts the second run.
A courier network produces thousands of addresses, attempt notes and cash records every day. AI in your courier system reads them, spots the patterns and drafts the next step — your team approves it.
AI suggests, drafts and flags; people decide. Rider deductions, settlement changes, refunds and bulk customer messages always wait for approval, and AI only sees the merchants, parcels and riders each user is permitted to see.
- 01
Address clean-up
Rider sees original tooThis order says “near the big mosque, villa with green gate”.Matches free-text addresses to known buildings, landmarks and past successful drops, suggests a zone and pin, and flags addresses too vague to dispatch so the customer can be asked before the run.
- 02
Failed-attempt prevention
Which of tomorrow's parcels are likely to fail?Looks at address quality, the customer's previous attempts, time windows and zone history, and lists parcels worth confirming by message before dispatch.
- 03
Customer messaging
Templates you approveA customer replies on WhatsApp asking to deliver after 6pm.Reads the reply, updates the delivery window on the parcel from your approved options and confirms back — anything outside the rules goes to the support team.
- 04
Cash difference checks
No automatic deductionsWhy doesn't tonight's hand-in match?Compares parcels marked as cash with card terminal batches and customer feedback, and points to the parcels most likely behind each difference for a supervisor to review.
- 05
Merchant account insights
Prepare notes for Marlin Sports' monthly review.Volumes, first-attempt success, failure reasons, returns and settlement disputes for the merchant, with suggestions grounded in their own data.
05A day with ORCHESTR
One courier day, from sort to settlement.
- 05:45Scan-in, auto-sortedParcels are scanned in and allocated to zones and runs; supervisors only rebalance the runs flagged as heavy.
- 08:00Runs in the rider appEach rider opens an ordered run with COD amounts, delivery windows and customer notes.
- 11:20Attempt logged, customer notifiedThe failed attempt is recorded with a reason and call log, and the customer gets a link to reschedule.
- 15:00Merchant checks the portalThe merchant sees every parcel's status, attempt and return in their portal.
- 20:30Hand-in against expected cashEach rider's expected cash is already calculated; hand-in takes a minute and differences are flagged immediately.
- 22:00Returns booked for pickupFinal-attempt parcels move to return-to-merchant with charges applied and pickups booked.
- Thu 10:00Settlement run approvedStatements are generated from parcel records; finance reviews exceptions and approves the payout run.
An illustrative day — every system is designed around how your team actually works.
06Integrations
Plugs into your merchants and your money.
Integrations depend on what each provider exposes — we confirm every connection in scoping before committing to it. Names are examples of categories we work with, not partnerships.
- E-commerce platforms
- ShopifyWooCommerceMagentoSalla / Zid (where available)Custom merchant APIs
- Messaging
- WhatsApp Business APISMS gatewaysEmail
- Maps & addresses
- Google MapsGeocoding and address services (via API)
- Payments
- Card terminals (batch exports)Payment linksBank transfer files
- Accounting
- Zoho BooksQuickBooksXeroERP exports
- Other carriers
- Partner courier APIs for out-of-area parcels (where available)
- Data
- Spreadsheets & exportsExisting databasesBI tools
07How we build your system
Built around your courier — not a template.
- 01
Understand your business
We spend a morning in your hub and a shift with riders: how parcels arrive, how the sort is done, how attempts are recorded and how cash comes back. - 02
Map your workflows
We map the parcel's whole journey — from merchant order to payout — including failed attempts, reschedules, returns and cash differences. - 03
Design your system
We design the hub screens, rider app, merchant portal and finance views around those flows, with permissions for each role. - 04
Build and integrate
Built in stages — usually parcels, the rider app and COD first — then settlement, merchant integrations and the portal. - 05
Test and launch
We migrate merchants, rate cards and zones, pilot with one hub and a group of riders, then roll out across the network. - 06
Support and improve
We support the system after launch and add zones, hubs, merchants and integrations as volumes grow.
08Why it matters
What changes for the courier business.
We don't quote savings we haven't measured. In discovery we baseline how your team works today, so improvements can be tracked against your own numbers.
Fewer wasted attempts
Bad addresses and unreachable customers are caught before the rider leaves, not after.Cash you can account for every night
Expected and handed-in cash are compared rider by rider, as it happens.Settlements merchants trust
Every payout is built from parcel records the merchant can see for themselves.Returns that don't pile up
Undelivered parcels move back to merchants with their charges applied.A sort anyone can run
Zones and runs are allocated from addresses, not from one person's memory.A support team that handles exceptions
Merchants and their customers get live answers from the system.
09Possible use cases
How different courier businesses could use it.
Examples of what we could build — not completed client projects.
High-volume COD across the emirates
Merchant plug-ins, address clean-up, a rider app with COD capture and weekly settlement for dozens of online stores.
Tight cut-offs, short windows
On-demand pickups, same-day runs with live tracking links and pricing by service level and distance.
Riders supplied to many brands
Riders, shifts, documents and pay across several client brands and platforms, with performance and cash per client.
Your own riders, your own customers
A delivery operation for one brand's online orders and store deliveries, connected to its e-commerce and stock.
FAQs
Courier questions, answered.
Logistics & automotive
01Can merchants send orders straight from their online store?
Yes. Merchants can connect through plug-ins for common e-commerce platforms where they're available, through an API we document for your network, by bulk upload, or by entering parcels in their portal. Each route ends in the same parcel record with its label and airway bill.
02How is cash on delivery handled?
Riders record cash or card at the doorstep in the app. The system knows how much each rider should be holding at any moment, records the hand-in against it, matches card terminal batches and flags differences for a supervisor to review.
03Can it work with freelance riders as well as our own staff?
Yes. Each rider has a type, documents, zones and pay rules — per drop, per shift or a mix. Freelance riders only see their own runs and earnings.
04Do customers get tracking and rescheduling?
If you want them to. Customers can receive a tracking link by SMS or WhatsApp showing their delivery window, with options to reschedule, add delivery notes or correct their address within the rules you set.
05How is this different from your logistics system?
Our logistics pages cover B2B transport — pallets, trucks, lanes and contract customers. A courier system is built for parcels: thousands of small drops, riders, zones, failed attempts, COD and merchant settlement. Some businesses run both, on shared customer and vehicle records.
06Can we hand parcels to other carriers for areas we don't cover?
Yes. Parcels can be handed to partner couriers, and where those couriers offer an API we pull their status back into the same parcel record. Where they don't, status can be updated by file or by your team.
07Will AI message our customers on its own?
Only within templates and rules you approve — confirming windows, sending reschedule links, answering where a parcel is. Anything unusual, and anything involving refunds or disputes, goes to your team.
08We already have a courier system. Do we have to replace it?
Not necessarily. Some couriers keep their existing system for labels and add settlement, COD reconciliation or a merchant portal on top. In discovery we'll tell you honestly whether extending or replacing makes more sense.
09How is a courier system priced?
It's quoted after a discovery call, based on modules, parcel volumes, hubs, the merchant integrations involved and the number of riders. Support and hosting are agreed separately, in writing.
Start here
Let's mapyour network.
Tell us how parcels, riders and cash move through your operation today. We'll show you how one system could connect hub, riders, merchants and finance.
- 01We get back to you to arrange a call.
- 02A focused conversation about how your courier runs today.
- 03If there's a fit, a written scope and quote — no obligation.