Booking
Booking to bilty
LR and e-way bill flow from one booking record without retyping.
TransportOS
Built for how Indian transport runs: attached vehicles alongside owned, bilty that flows into the e-way bill, and driver advances that reconcile themselves.
Execution
Trip execution
Track vehicle, driver, POD, tolls, expenses, advances and settlement against one trip.
Margin
Trip P&L
See freight earned, every cost line, and net margin by route, party, vehicle and driver.
The problem
Tuesday, 6:40 AM, at a transport office
At month end, the honest answer to “does Vapi–Hyderabad make money?” is: probably.
Nine tonnes to Hyderabad
The quote comes from a laminated rate chart. The bilty is handwritten, then retyped into the e-way bill portal. The ₹8,000 advance goes in a diary, and the POD gets lost in a WhatsApp group.
Trip-Level Visibility: Low
Trip P&L
LeakHighP&L risk
- Trip marginUnknown
- Cost capturedProfitable
- VisibilityHidden
?Margin leak
Where Fleet Money Leaks
Transport profits leak when booking, bilty, settlement, tolls and billing live in separate registers.
- Late billingCash stuck
- Trip expensesMissed cost
- DetentionUnbilled
- Excel settlementAlways debated
Two leaks nobody sees
If the trip is not costed end to end, these losses stay invisible.
- 1Trips close late, so invoices go out late and working capital gets stuck.
- 2Detention, tolls and route costs disappear unless captured against the trip.
See the module map
Booking, bilty, e-way bill and trip P&L in one flow.
How it works
How TransportOS works
Booking → Vehicle assignment → Bilty/LR → E-way bill → In transit → POD → Settlement → Invoice → Payment → Trip P&L
Booking & Bilty
OthersRates from a laminated chart; bilty retyped.
CovixyRate from master; bilty feeds the e-way bill.
Trip Execution
OthersWhiteboard, phone calls and a diary.
CovixyGPS, FASTag and POD attached to the trip.
Settlement
OthersA diary and an argument.
CovixyAdvance, fuel, tolls and detention totalled.
Trip P&L
OthersA guess at month end.
CovixyMargin per trip the moment settlement closes.
Profitable
Trip-level P&L shows freight earned, fuel, tolls, driver cost, hire, detention and final margin.
Modules
What's in the system
Booking, dispatch, bilty and e-way bill, GPS/FASTag, driver settlement, vehicle compliance, billing and trip P&L.
Module 01
Booking & Rates
Rates by party, route, material, vehicle and weight slab, so a quote is a lookup, not a recollection.
- Rate master with version history
- Off-rate quotes need a reason
- Party outstanding shown at booking
Module 02
Dispatch & Vehicles
One board for owned and attached vehicles: status, driver, last GPS ping and document expiry.
- Owned and attached on one board
- Hire rate captured at assignment
- Red flag on expiring documents
Module 03
Bilty / LR & E-way Bill
Bilty laid out like the paper form; the same record generates the e-way bill and the invoice.
- GST fields auto-filled from masters
- EWB generated from bilty data
- Part-B updated in three clicks
Module 04
GPS & FASTag
Vendor-agnostic GPS by JSON webhook; FASTag tolls mapped to the trip by vehicle and time.
- Works with any GPS supplier
- Trip playback with long halts
- Toll cost per route as a line item
Module 05
Driver Settlement
Per-driver ledger of advances, expenses, tolls, bhatta and detention. A calculation, not a negotiation.
- Receipt photos from the driver's phone
- Detention from GPS halt hours
- Running balance across trips
Module 06
Vehicle Compliance
Fitness, permit, insurance, PUC and road tax expiry per vehicle, plus fuel efficiency by vehicle and driver.
- Alerts at [60/30/7] days
- Grid coloured by days-to-expiry
- km/litre by vehicle and driver
Module 07
Billing & Receivables
Invoice from settled trips with the LR attached, e-invoice IRN where applicable, and receivables ageing by party.
- The invoice goes out the day settlement closes.
Dashboards
The Dashboards
Four views: owner, dispatcher, trip P&L and route profitability, built to be read in 30 seconds.
Built to be used
The bilty screen matches the paper form. A trained clerk enters a bilty in under [90] seconds.
Speed
Bilty matches the paper form
Field order follows the layout your clerk already knows.
Works on a ₹[8,000] phone
Tested on mid-range Android phones on real 4G networks.
Offline-tolerant
POD and expense photos queue on the phone and upload when signal returns.
Keyboard-first
Booking and bilty entry work without touching the mouse.
Access Roles
Strict Access Roles
A booking clerk sees rates but not margin. A dispatcher sees vehicles but not the party ledger.
System Audits
Audit trail on every record
Who edited a settled trip, when, and the previous value. Branch users can't see other branches' data.
Integrations
Connects to your tools
Keep the systems that already work. If it exposes an API, it can usually be connected, and we quote the cost first.
FASTag
Toll transactions mapped to the trip by vehicle and time.
Tally
Invoices, receipts and expense vouchers; accounts stay in Tally.
E-invoicing (IRP)
IRN and signed QR at billing, where turnover requires it.
GPS telematics
Vendor-agnostic JSON webhook: position, ignition, speed, halts.
WhatsApp & SMS
Bilty PDF to party, POD to consignee, dispatch alerts.
E-way bill portal
Generate, update Part-B, extend and cancel from consignment data.
Financial Impact
What it's worth.
Your return comes from faster billing, calculated settlement, billed detention and fewer penalties.
Critical Impact
Faster Billing
Invoices go out the day settlement closes, not four days later.
By scope
Settlement Time Saved
A calculated driver ledger replaces hours of diary reconciliation.
By scope
Detention Billed
Detention hours from GPS billed to the party instead of forgotten.
By scope
Toll & Fuel Visibility
Toll and fuel cost per route as a real line item.
By scope
Penalties Avoided
EWB and document expiries flagged before a truck is detained.
By scope
Potential impact
We model payback using trips, vehicles and billing data.
Custom /mo
Target audience
Who it's for.
Made for fleets with trip sheets, settlement, branches and attached vehicles.
The Ideal Profile
Perfect Fit
- [20–200] vehicles, owned, attached or a mix
- Full-truckload or part-load road freight
- Multiple branches or booking offices
- On Tally and want to stay there
- Trip sheets and settlement on paper or Excel
Not Recommended
Misaligned
- Under [10] vehicles — spreadsheets plus Tally will do
- Pure last-mile parcels — see Courier Aggregator ERP
- Need to be live in three weeks
Implementation Flow
Getting it running.
| Stage | What happens | Duration | Need from you |
|---|---|---|---|
| Operations review | We walk your process, gate to invoice | 20 minutes free | Whoever knows the operation best |
| Scoping | Screen-by-screen specification, integration list, data audit, fixed scope and price | [N] weeks [₹X / free] | [X] hours across your team, access to current records |
| Build | [Milestone structure], working screens at each milestone | [N] months | Review and sign-off at each milestone |
| Data migration | Parties, vehicles, drivers, rates, open balances | [N] weeks | Your existing data, however messy |
| Parallel run | Old and new side by side | [N] weeks | Patience. This is the hard part. |
| Go-live and training | On-site, on your floor, in your language | [N] days | [X] hours per user |
| Support | [AMC scope and response commitments] | Ongoing |
Alternatives
Compared with the rest
When a product TMS is better: standard full-truckload, owned vehicles, one branch, and live next month. Buy the product.
Covixy ERP
Custom-built for transport booking, dispatch and settlement workflows.
Product TMS
LOZICS, Cargo365, Fretron class: faster to start, but their process.
Odoo + Fleet
Configurable within Odoo's model; fleet needs customisation.
Excel + Tally
Already running; settlement and trip P&L stay manual.
| Feature | Covixy | Product TMS | Odoo | Excel |
|---|---|---|---|---|
| Process fit | Exact | Their process | Odoo's model | DIY |
| Attached vehicles | Built for it | Often weak | Customisation | Manual |
| E-way bill | From bilty data | Usually yes | Partner module | Re-entry |
| FASTag / GPS | Any vendor | Their partner | Custom | None |
| Trip-level P&L | Native | Varies | Customisation | Not practical |
| Code ownership | You | No | Partner-dep. | N/A |
| Year-1 cost | [₹X] | [₹X] | [₹X] | ~₹0 |
FAQ
Objections, answered.
The objections we actually get.
My staff won't use it.
The likeliest failure. We lay screens out like your paper forms, train on your floor and keep the first release small. You decide whether the old register gets put away.
We tried software before.
55–75% of ERP projects miss their objectives. The reason is usually scope creep, unassessed data migration or a vendor who vanished, and our stages address all three.
What if you disappear?
You own the code and the database, and it runs in your hosting, so another developer can pick it up. [Repository access, escrow, handover documentation.]
Can we start with one part?
Yes. The usual first release is booking → bilty → e-way bill, which removes double entry on day one. Settlement and trip P&L follow.
Next step
Twenty minutes, and an honest answer
We'll walk your process and tell you whether to build, configure, or buy something off the shelf. If it's the third one, we'll name the product.
Submit an Enquiry
Share how your operation runs today and where it hurts. We'll review it and reply with a clear recommendation.
- Takes about 3 minutes
- Written reply within 1 business day
Book a Discovery Meeting
Walk us through your process on a call. Twenty minutes, no slides, and a straight answer at the end.
- 20-minute video or on-site call
- Pick a slot that suits your team
No sales pitch. If an off-the-shelf product fits better, we'll name it.