Skip to main content
GullySystem
Travel and transport · Software for delivery companies

Track every parcel from pickup to proof of delivery and the cash collected.

Delivery companies collect parcels, sort them in a hub and send riders and drivers out on runs. The software holds bookings, manifests, run sheets, scans, proof of delivery, cash on delivery and customer invoices on one waybill record. Failed attempts and rider payouts are both read from those same entries.

At a glance

A delivery business sells a promise about one parcel at a time. Pick it up, scan it, sort it, carry it, hand it over and prove that it happened. Volume makes each step a small job, and every handover between rider, hub team and dispatcher is a place where a waybill can lose its trail.

Most firms hold this across a booking sheet, a rider group chat and a separate invoice file, so a consignor asking about one parcel starts a search. Our scoping session follows one day of parcels through all three.

How the work runs today

Dispatchers take bookings from shops, platforms and walk-in senders by phone, web form or file upload. Pickup runs collect the parcels. A hub team scans each waybill, sorts by destination zone and loads roll cages, so that a rider leaves with a bundle that matches the printed run sheet. Riders on scooters, bicycles and vans deliver in sequence and capture a signature, photo or code.

Some parcels come back. It happens daily. The consignee was out. The address was wrong. Or the parcel was refused. Dispatchers book a redelivery or return it to the consignor, and the sender wants an answer the same day.

At shift end, riders hand over the cash they collected on delivery. Accounts reconcile that cash with the manifest, remit it to the consignor, and invoice business customers on their agreed rate card with fuel surcharge. Rider pay depends on drops completed, distance and attempts. Cash handling takes care.

Where it breaks

What goes wrong for delivery companies without a proper system.

Parcel status lives in several tools

The booking sheet, the hub scan list and the rider chat each show a different stage. Answering one query from a consignor means checking all three. That takes minutes.

Failed deliveries are handled by phone

A refused or missed parcel is reported by a rider call. The reason, the redelivery slot and the message to the consignor are rarely on record. Senders then ring.

Cash collected does not match run sheets

Cash on delivery is counted at shift end and compared with paper. A short float is hard to trace to a waybill or a rider. Blame spreads.

Customer rate cards are applied by hand

Each business customer has its own volumetric weight bands, remote-area zones and surcharges. Terms differ. Invoices are built from memory of those terms.

Rider pay is calculated at month end

Drops, attempts, distance and fuel allowance are added from run sheets. Disputes arise because the count lives in several files. Nobody agrees.

What the software does

What we would build for delivery companies.

Named the way your team already talks about the work. We start with whichever part the audit shows is costing you most.

Booking and pickup requests

Take orders by form, file upload or phone, assign a pickup run, and give each parcel its own waybill number, barcode and label.

Hub scanning and sorting

Scan parcels in and out of the hub, group them by zone and roll cage, and show which waybills are missing from a manifest or a load.

Run sheets and route assignment

Build a run for each rider or van with stops in order, and watch drops complete through the day against the printed run sheet.

Proof of delivery and failed attempts

Capture a signature, photo, safe-place note or code at the door, and record the reason and redelivery step when a parcel is not handed over.

Cash on delivery reconciliation

Match cash and payments collected against each manifest, and list the remittance owed to every consignor.

Customer rate cards, invoices and rider pay

Price parcels by zone and volumetric weight band for each customer, add fuel surcharge, raise invoices, and work out what each rider earned from completed drops.

Before you talk to a supplier

A requirements checklist for delivery companies.

What to cover, which reports to ask for and what to put to every vendor, ready to print or save as a PDF.

Open the checklist
Ready product

A product already built for delivery companies.

It is adapted to how your business works before it goes live, and anything your trade needs that it lacks is added then.

Delivery Company Management Software

Bookings, tracking codes, hub scanning, run sheets, proof of delivery, failed attempts, cash on delivery, customer billing and rider pay for delivery companies.

See the product
Solutions inside

The business modules delivery companies use most.

Each one is also available on its own, or inside a system built for you.

Connections

Tools delivery companies often connect.

How it works

How the work runs from Bengaluru for your city.

  1. 1

    The audit, by call

    A screen-share and a look at the sheets, Tally reports and WhatsApp groups your team uses. No travel needed.

  2. 2

    A written proposal

    Scope, what we build first and the cost, agreed in writing before anything starts.

  3. 3

    Build in short rounds

    Working screens shared every few weeks. Your team tests them from your own office.

  4. 4

    Go-live, in person when it helps

    For data migration and training we can come to your city. Travel is agreed in advance.

  5. 5

    Support online

    Fixes, changes and hosting handled remotely by the same team that built it.

Common questions

Questions delivery companies ask before they call.

Does it plan the shortest route between stops?

It builds runs by zone and sequence and shows progress. Automatic route optimisation can be connected to a mapping service during implementation, as an added quotation item.

Can business customers see where their parcels are?

Yes. Every waybill carries a tracking code. Status updates reach consignors and consignees through email, SMS or whichever messaging app your firm already uses.

Can it work with a marketplace or shop platform that sends us orders?

Orders can be brought in by file or by a connection to the platform. Which route is used turns on what the platform exposes, and we settle it while building the link.

Is it for a firm with three riders?

Possibly not yet. A shared sheet and a messaging group can cope at that size. The pain begins when volume, cash on delivery, redeliveries and customer rate cards multiply.

What happens in the free technology audit?

We look at the software, spreadsheets and WhatsApp groups your business runs on today and write down what works, what slows your team down and what is missing. A demo login, a screen-share or a few screenshots are enough to start. You get a report ordered by priority, and there is no obligation to hire us afterwards.

How much will the software cost?

We don’t publish a price, because it depends on what the system has to do. The audit settles the scope, and the cost goes into a written proposal before any work starts.

Category

Part of these wider groups.

Talk to us

Tell us how your business runs today.

A few lines on your spreadsheets, software and WhatsApp groups is enough. We reply the same working day.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements