A transport management system that follows the load from booking to proof of delivery
Plan bookings on a schedule, assign own or hired vehicles, print the LR, track the truck, collect the POD from the driver and bill the customer, in one system.
*No credit card required
What dispatch needs from a TMS
A dispatcher's day is a list of loads and a list of trucks. The questions are always the same:
- Which vehicles are committed this week, and which are free?
- Has the LR gone out, and does it match what the customer asked for?
- Where is the truck on this load right now?
- Did the driver send the delivery proof, and for which stop?
- Can accounts bill this trip yet?
A transport management system turns each of those into a record instead of a message. In NShine ERP the TMS is the front half of a transport ERP: the bookings it records become the invoices, supplier charges, driver pay and vehicle profit in the back half, with no re-entry.
What the TMS changes for dispatch and accounts
Each row is a dispatch problem, what NShine ERP does instead, and where.
What happens today | What changes | Where in NShine ERP |
|---|---|---|
Vehicle availability is in someone's head | Bookings show on a schedule by month, planner or year, so committed trucks and gaps are visible to everyone. | Booking Schedule |
The LR is typed separately from the booking | The LR prints from the booking itself: LR number, consignor and consignee, vehicle, driver, material, container and seal numbers, E-Way bill. | Bookings, LR print and share |
Multi-stop loads are tracked on paper | A booking carries pickup and drop-off addresses and stops; proof of delivery is captured per stop. | Bookings (stops), AI Inbox (POD per stop) |
"Where is the truck?" means a phone call | Live Tracking shows active, stopped and offline vehicles with speed and last-seen time, from your telematics accounts and the driver phone. | Live Tracking |
POD photos arrive on WhatsApp and get lost | Each photo is matched to its booking with a confidence score, repeats are flagged, and it saves when you approve. | AI Inbox |
Accounts cannot tell which trips are billable | Each booking shows its payment status: Pending Invoice, Invoice Created, Partial Payment, Payment Received. | Booking list, Customer Invoice |
Hired trucks are settled outside the system | A market vehicle carries its supplier; the hire charge is a supplier invoice on the same booking with a last day of payment. | Vehicles, Supplier Invoice |
Who it is for, and what it is not
Built for
- Dispatch teams running own and hired trucks on daily loads
- Transporters who print lorry receipts and need POD for billing
- Brokers and commission agents booking market vehicles
- Fleets that want the booking to become the invoice without re-typing
Not what it does
- Not a GPS device. Tracking uses the telematics accounts you already have and the driver phone.
- Not a route optimiser. It records stops and schedules; it does not compute the fastest route.
- Not a load board. It runs the loads you already have.
- Not passenger transport software.
How dispatch runs a load
- Confirm the quotation, or go straight to a new booking.
- Fill the booking: paying customer, consignor, consignee, pickup and drop-off, material and load details.
- Assign the vehicle (own, or market with its supplier) and the driver; record the start odometer.
- Print or share the LR; the booking shows as Booked on the schedule.
- Watch the vehicle in Live Tracking; the status becomes In Transit.
- The driver sends the POD; it is matched to the LR and you approve it.
- Record the end odometer and any fuel or expense for the trip.
- Raise the customer invoice from the booking; the booking's payment status follows it.
What is included
The booking is the invoice
Billing comes from the booking fields, so there is nothing to re-type and the invoice ties back to the LR.
Own and hired vehicles
Market vehicles are linked to suppliers; their charges become supplier invoices on the same booking.
POD without chasing
Drivers send photos on WhatsApp or the app; each is matched to a booking and repeats are flagged.
A real schedule
Month, planner and year views show which vehicles are committed and when.
Tracking in the same login
Vehicle positions, speed and last seen from your telematics provider, without a second app.
Trip and vehicle results
Every booking carries its revenue and costs into the Vehicle Profit/Loss report.
Booking fields you get out of the box
Plus your own custom fields and forms.
Multi-stop pickup and drop-off addresses
Consignor and consignee separate from the paying customer
Container number and two seal numbers
E-Way bill number and valid date
Goods invoice number, date and value
Start and end odometer with trip distance
LR print and share
Booking status from Booked to In Transit
Excel import of bookings
TMS only vs TMS inside the ERP
A dispatch tool that stops at delivery
What stays open:
- Invoices built in another system from the TMS printout
- Hired-truck charges tracked in a notebook
- Driver pay per trip calculated by hand
- Profit per trip known only after the accountant finishes
NShine ERP
The same booking carries:
- The customer invoice and its receipts
- The supplier invoice for the hired truck
- Trip-based driver pay that flows into payroll
- Fuel, expense and maintenance cost for the vehicle P&L
Watch the product in action
A walkthrough of the transport management software, in your preferred language.
Frequently asked questions
See TMS plans for your fleet
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.