Consignment booking
Client, route, rate, expected dates and documents captured at booking.
Logistics · Transport & fleet
A transport business is a set of promises about where things will be. Linksoft builds logistics software that tracks each consignment, each trip and each rupee of cost against those promises — so profitability per trip stops being a guess made at year end.
Very few transport operators can say what a specific trip earned. The freight is known, but fuel is bought against a slip, maintenance is remembered rather than recorded, tyre and driver costs are averaged, and the demurrage argument is settled from memory. The result is a business that knows it is busy and hopes it is profitable.
The fix is unglamorous: attach every cost to a trip and every trip to a vehicle, at the time it happens. Once that is true, profitability per vehicle, per route and per client stops being an annual mystery and becomes a weekly report.
A consignment is booked, loaded, dispatched, delivered and proved — with a document at each step and a client asking about it in between. The system holds that chain as one record: booking reference, vehicle, driver, route, expected and actual dates, and proof of delivery captured on a phone at the point of handover rather than photographed and forwarded later.
Because it is one record, the answer to 'where is my consignment' is a lookup instead of two phone calls, and the client can be given their own view rather than being told to ring the office.
Vehicles carry their own record: fuel issued, maintenance performed and due, tyre history, documents and their expiry dates, and the trips they ran. Drivers carry theirs: licence and its expiry, trips, advances taken, and settlements. Both feed trip costing, and both generate the reminders that stop an expired document becoming a roadside problem.
Freight is billed per the client's agreed rate structure — per trip, per tonne, per kilometre, per container — with detention, demurrage and extra handling as documented lines rather than as a negotiation. Bills post into double-entry accounts, client balances age visibly, and FBR-compliant electronic invoicing issues from the same flow where the operator is registered for sales tax.
Modules are configured to your operation during scoping — you take what your business runs on and leave what it does not.
Client, route, rate, expected dates and documents captured at booking.
Vehicle, driver, route and status from dispatch through to delivery.
Delivery confirmation and documents captured on a phone at the point of handover.
Fuel, maintenance, tyres, documents and expiry reminders per vehicle.
Licences and expiries, trip history, advances and settlements.
Every cost attached to its trip, giving profitability per trip, vehicle, route and client.
Rate structures, detention and demurrage billed as documented lines.
Double-entry books posted from operations, with compliant e-invoicing from the same flow.
Logistics is on our owner-verified list of industries served, and the machinery is machinery we run: our textile system tracks goods received at the gate and dispatched to buyers with documentation attached, costs consumed against a specific order, and every movement posting into double-entry party ledgers automatically.
Trip costing is order costing with a vehicle in place of a production line. We would rather show you that working system and let you judge the transfer than describe a fleet client we do not have.
See the client register →A goods-transport system is in active development, modelled on how Pakistani transport actually works: the bilty book and the loading challan, the margin argued at the truck adda, branch-wise cash, wasooli against parties, the POD register that decides when a truck owner gets paid, and sales tax invoices filed with FBR. These are real screens from it, in the order the work happens.
Al-Rehmat Goods Transport, and every party, figure and consignment shown, is sample data we created for development. It is not a client and does not represent a live deployment.
Yes, provided costs are captured against the trip as they happen — fuel, maintenance share, driver advances, tolls and handling. That is the design goal: profitability per trip, vehicle, route and client as a report rather than an annual estimate.
Yes. Systems are mobile-ready as standard, so status updates and proof of delivery can be captured on a phone at the point of handover instead of arriving at the office days later.
Yes — fuel, maintenance history and what is due, tyre records, and every vehicle document with its expiry date and a reminder before it lapses.
Yes, where you want them to. A client-facing view showing only that client's consignments is a standard part of the build, and it removes a large share of the calls the office fields daily.
We can integrate an existing GPS provider's data where they expose an API, so vehicle position appears alongside consignment status. We do not sell tracking hardware — we connect what you already run.
Yes: rate structures per client, detention and demurrage as documented lines, bills posting into double-entry accounts, and client balances ageing visibly rather than being reconstructed at the end of the quarter.
We scope on-site, specify in writing, and tell you honestly whether custom software is the right answer — before any commitment.