Start with your vocabulary
If your team says LR, bilty, outward, unload, OFD, and TBB, the product should speak that language. If demos only show last-mile courier dashboards, keep looking — see who iLogitix is for.
Buyer checklist
1. LR-first booking, not courier tracking
Look for PAID, TO_PAY, and TBB freight types, rate cards, and consignor/consignee flows — not only AWB-style parcel tracking.
2. Full lifecycle after the booking
Outward, unload, OFD, and delivery status should live on the same LR record so branches share one truth.
3. Digital POD tied to the booking
Photo or signature proof should attach to the LR — not sit forever in WhatsApp chats.
4. GST billing from the same data
TBB invoices with SGST/CGST or IGST should not require re-typing freight from a spreadsheet.
5. Branch-scoped roles
Ops staff need their branch’s work; leadership needs the network view. One shared spreadsheet cannot do both safely.
6. Isolation for each company
In cloud SaaS, each transport company should have clear data boundaries (tenant isolation), not a shared open database.
What to avoid
- Tools that only replace Excel for booking, then leave POD and billing elsewhere
- Shared “one big sheet” thinking with no branch permissions
- Vague “AI logistics” claims with no LR lifecycle demo
Dig into LR software, OFD & POD, and GST billing— or compare LR software vs Excel.
Related guides
- LR software vs Excel — When shared sheets stop scaling — and what a proper LR workflow should replace.
- Digital POD explained — How proof of delivery closes disputes, OFD loops, and billing — without paper slips.
- PAID, TO_PAY & TBB — The three LR freight types transporters use daily — and how software should handle each.
- GST billing overview — How TBB bookings become GST invoices (SGST/CGST or IGST) without re-keying from ops.