Multi-drop runs

Multi-drop runs: one truck, many drops, one booking per drop, and no route planner

If you searched for multi-stop trip planning, read this first. NShine ERP does not plan routes or sequence stops. What it does is record a truck’s many drops as separate bookings on the same vehicle and day, prove each one with its own POD, and bill each customer from their bookings. Built for city distribution, part-load and route-sales fleets.

*No credit card required

What a booking is, and is not

A booking has one pickup address and one drop-off address, with its own LR number, customer, consignee, material, vehicle, driver and dates. There is no list of stops on a booking and no waypoint field. A truck that leaves a depot and drops at eight shops is eight bookings, each with the same vehicle, driver and pickup date. That is the honest shape of it, and it works because each drop is a thing that gets billed, proved and argued over on its own.

  • One booking per consignment, not one booking per truck-day
  • The same vehicle, driver and date on all of them
  • A POD for each, matched to its own booking
  • One invoice per customer, picking all their bookings for the period

How a multi-drop day is run

A booking per drop

Each consignment gets its own LR with customer, consignee, drop-off address and amount. Enter them on the form or import the day’s manifest.

The day on the calendar

Booking Schedule shows every booking by month, planner or year, labelled with LR and vehicle; a busy truck shows its first few and "+ N more".

The truck’s load list

Filter the booking list by vehicle and date and you have the truck’s drops for the day, in cards or a table, with status on each.

A POD per drop

The driver sends a delivery photo at each shop on WhatsApp or the app; AI Inbox matches it to the right booking and flags a repeat image; you approve.

One invoice per customer

Pick a customer’s delivered bookings for the week or month on one invoice with tax, HSN, RCM and TDS; each booking shows the invoice number.

The manifest, imported

AI Data Import takes the customer’s consignment sheet, maps the columns, checks each row and creates the bookings on your confirm.

Bring one truck’s delivery sheet for a day

A 30-minute demo where we import it as bookings, attach PODs and raise the invoices. No credit card, no setup fee.

What it does not do

  • It does not plan a route or decide the order of drops; the dispatcher and the driver do that as they do today
  • It does not put several stops on one booking; each drop is its own booking
  • It does not optimise for distance, time or load; it has no map-based planner

If route optimisation is the centre of your business, say so on the demo and we will tell you whether the rest is worth it. For most distribution fleets the problem is not the order of the drops; it is proving each one and billing it without a week of reconciliation.

Why one booking per drop pays off

The customer pays against their consignment list, drop by drop. When each drop is a booking with its own POD, the invoice matches their list line for line, a disputed drop is one record with one photo, and a cancelled drop is one booking removed. The truck’s day is the sum of its bookings; its profit is revenue less fuel, driver pay and expenses across them.

Before and after

One line per truck in a register

A distribution fleet today.

  • Eight drops written as one trip
  • PODs in a group chat, matched at month-end
  • The customer disputes two drops; nobody can show them
  • Invoice built from the register, line by line

One booking per drop

The same fleet on NShine ERP.

  • Eight bookings on the same truck and day
  • A POD on each the minute it is sent
  • The disputed drop is one record with its photo
  • Invoice from the bookings; the list matches theirs

A multi-drop day

  1. Import the manifest or book each drop with the same vehicle, driver and date.
  2. Open the calendar or filter the list by vehicle to see the truck’s drops.
  3. The driver delivers and sends a photo at each stop; approve each in AI Inbox.
  4. Fuel slips from the same day become fuel entries with odometer.
  5. At period-end, invoice each customer from their delivered bookings.

What stops happening

Eight drops hidden inside one trip line

A disputed drop with no proof

A month-end reconciliation against the customer’s sheet

Trip counts argued with drivers on payday

Transport businesses that run on NShine ERP

Watch the product in action

A walkthrough of the transport management software, in your preferred language.

Frequently asked questions

Multi-drop fleets run on every plan

Plans are priced by bookings per month and own vehicles, with a free trial and no setup fee. Pick the one that fits, or book a demo first.

Ready to Take Control of Your Business?

Start your 7 day free trial today

No credit card | No commitment | Just try it and see