/// movement operating system · india-first
Bilty to branch P&L.
One system.
No phone-call ops.
Bookings in a bilty book. Status on phone calls. To-Pay in a diary. Branch profit unknown until year-end. Dloter replaces that with digital LR/Bilty records, a live dispatch board, freight billing foundations, collections tracked to the rupee, and branch truth — on your own subdomain.
no credit card · yourfleet.dloter.com today · no gps hardware required — ever
unassigned2
in transit2
delayed1
exception1
driver workload
selvam2 LRraju1 LRvikram3 LR2 drivers free/// one consignment · five real states
Follow LR-1031. Scroll — the system carries it.
LR-1031 · CHN→BLR · to-pay ₹12,400
Booked (LR)
digital from second one
On dispatch board
bucket: unassigned
Driver assigned
from the board
In transit
status truth
Delivered ✓
pod + collections
● state 1 · Booked (LR)
A booking becomes a digital consignment
The bilty is born digital: LR-1031, consignor, consignee, packages, freight ₹12,400 marked To-Pay — recorded at booking, not reconstructed at month-end. GST-compliant documents come from the same record.
✓ LR created — complete record✓ to-pay ₹12,400 on the LR
● state 2 · On dispatch board
It lands on the dispatch board
Unassigned, in-transit, delayed, exception — four buckets your ops team actually runs, with driver workload beside them. Nothing waits in someone’s head or someone’s phone.
✓ bucket: unassigned✓ visible to the ops role
● state 3 · Driver assigned
Dispatch assigns the driver — and can reassign
Assignment happens on the board, against real workload. Reassignments are recorded moves, not overwritten memories.
✓ driver: selvam✓ reassignment tracked
● state 4 · In transit
In transit — status truth, not status theater
Your customer gets a tracking link that shows the real state of LR-1031. No invented ETA, no GPS dot we don’t have. They stop calling because the truth is one tap away.
✓ customer tracking link live✓ eta: none — by design
● state 5 · Delivered ✓
Delivered ✓ — POD recorded, money remembered
The driver records POD in the Dloter Business app. To-Pay ₹12,400 flows into collections — prepaid, To-Pay, credit and waivers, tracked to the rupee, feeding branch P&L.
✓ pod recorded✓ ₹12,400 → collections
// every state above is a shipped product state. nothing dramatized.
/// screenshots, not promises
The actual transport software.
Three chambers — captures from approved demo tenants with dummy data. Until each capture lands, its slot says exactly what will be shown.
delay surfaces itselfno eta column — by design
/// chamber 01 · movement
The board your ops team runs — instead of the phone.
Every LR sits in exactly one bucket. A late consignment moves itself to delayed; a delivery without POD holds in exception. Delays don’t hide in phone calls — they surface themselves.
proof: lgx ops pack 1 · dispatch buckets + driver workload · live
what your customer sees — status truth onlyeta visibly absent
/// chamber 02 · the tracking link
Your customer follows the LR without calling you.
One consignment record, two honest views: the full detail your team works, and a public tracking page showing real status and POD-after-delivery. No invented ETA. No GPS dot. Status truth earns more trust than theater.
proof: platform tracking · 14/14 live · pod-after-delivery
honest empty state — no invented margins
/// chamber 03 · branch truth
Branch P&L that would rather say “not enough data” than lie.
Freight, collections and costs roll up per branch. When costs are missing, the system shows an honest empty state instead of inventing a margin. Year-end stops being the first time you learn which branch makes money.
proof: lgx ops pack 1 · branch p&l + honest empty state · live
/// what’s live · what’s coming
Every ● below is running in production.
Everything else says so.
This grid is proof-mapped. If a cell says live, a production acceptance matrix stands behind it — and anything unshipped is labelled ◌ coming, on this very page.
Digital consignments & LR lifecycle
Bilty born digital — booked, dispatched, delivered, closed, with a complete record throughout.
ref: lgx 2.2 · 36-row matrix
Dispatch board buckets + driver workload
Unassigned / in-transit / delayed / exception, with per-driver load beside the board.
ref: lgx ops pack 1
Assign / reassign drivers
Assignment from the board, against workload; every reassignment is a recorded move.
ref: lgx ops pack 1
Branches & operating locations
Head office and branches with real scoping — each branch sees its own operation.
ref: branch scope slice 1 · 16/16
Branch P&L with honest “not enough data”
Per-branch roll-up that shows an empty state rather than an invented margin.
ref: lgx ops pack 1
Freight collections: prepaid / To-Pay / credit
Every rupee of freight has a state — including waivers, on the record.
ref: lgx-9
Customer tracking links — no fake ETA
Public status truth per consignment; POD visible after delivery. No GPS pretense.
ref: platform tracking 14/14
GST documents incl. delivery challan
GST-compliant documents generated from the consignment record itself.
ref: lgx 2.4
Roles: ops / finance / accounts / field / auditor / booking
Backend-enforced and UI-honest — each role sees exactly its own surface.
ref: enterprise ledger §3G
Driver POD via the Dloter Business app
Proof of delivery recorded by the driver on their phone, attached to the LR.
ref: mobile M4
Fleet compliance vault
RC / insurance / permit expiry tracking for your vehicles. Built — not yet live-accepted, so not claimed live.
status: rolling out — labelled until accepted
Route & rate tools
Route planning and rate cards — unclaimed until they ship and prove out.
status: planned
Online freight payment collection
Collecting freight online — held until the money path is proven end-to-end.
status: held until proven
the transport OS is one vertical of the same platform spine: the full logistics software surface →
/// the truth firewall
Claims transport software loves to ship.
Dloter’s firewall rejects them.
These rejections are product behavior, not marketing copy. The tracking page your customer sees is governed by the same rules.
- fake_etaan ETA renders only from a real source — none exists, so none renders. Ever.✕ REJECTED
- gps_theaterno GPS dot without GPS hardware — we don’t require it and we don’t fake it.✕ REJECTED
- fake_senta notification is never marked sent unless a live channel actually delivered it.✕ REJECTED
- silent_capabilityunshipped features never pose as shipped — the compliance vault on this page says “rolling out”, not “live”.✕ REJECTED
- status_truththe board, the LR record and the customer tracking link render only real dispatch state.✓ LIVE
- pod_evidence“delivered” means a POD is recorded — evidence attached, exception otherwise.✓ LIVE
full register: /proof — what’s live, what’s not, and how we decide
/// install sequence · transport
Your transport OS installs in a day.
Your bilty book retires at its own pace.
Register with an OTP and watch it assemble — subdomain, branches, roles, and a dispatch board waiting for its first LR. This sequence is real, not aspirational.
/// the honest comparison
Keep Tally for the books —
Dloter runs the operations beside it.
Tally is excellent accounting, and most transporters run it with Excel sheets and WhatsApp groups around it. That stack keeps the books — it doesn’t run the movement. Here is the honest, respectful difference:
| Tally + Excel + WhatsApp | Dloter — movement OS | |
|---|---|---|
| Where bookings live | Bilty book + Excel, typed into Tally later | Digital LR from the moment of booking — one record, start to close |
| Who sees status | Whoever answers the phone | Every role that needs it — ops board inside, tracking link outside |
| Collections tracking | To-Pay diary; month-end surprises | Prepaid / To-Pay / credit tracked to the rupee, waivers on record |
| Branch P&L | Known at year-end, if ever | Rolls up per branch — and says “not enough data” rather than invent margins |
| Customer tracking | They call you | A link with real status — no fake ETA, no GPS theater |
| Staff roles | One login, or full trust for everyone | ops / finance / accounts / field / auditor / booking — backend-enforced |
pricing: ₹0 to start · ₹999/month metered · never a percentage of your freight
Sourced, dated comparison — including where transport ERPs are stronger: vs transport ERPs →
Transporters ask. We answer straight.
What is bilty / LR software?
A bilty (lorry receipt, LR) is the consignment note of Indian road transport. Bilty software makes it digital: the LR is created at booking with consignor, consignee, packages and freight terms, then carries its own status through dispatch, transit, delivery and collection — instead of living in a carbon-copy book and a phone.
Can my customer track a consignment without calling me?
Yes. Every consignment gets a public tracking link showing its real status — booked, in transit, delivered — and the POD after delivery. It shows the truth from your operations, not an invented ETA or a GPS dot we don’t have.
Does it handle To-Pay and collections?
Yes. Every LR carries its freight terms — prepaid, To-Pay or credit — and Dloter tracks each rupee to its state, including waivers, feeding branch P&L. Online freight payment collection is not live yet, and is labelled “coming” on this page.
I run multiple branches. Does that work?
Yes. Head office plus operating locations are first-class: each branch operates its own bookings and dispatch within its scope, and branch-level P&L rolls up from real data — with an honest “not enough data” state when costs are missing.
What about GST documents?
GST-compliant documents — including the delivery challan — are generated from the consignment record itself, so the paperwork always matches the movement.
Do I need GPS devices?
No — and we don’t pretend to have GPS. Dloter shows status truth from your own operations: what your dispatch team and drivers actually record. If a tracking page ever shows a location dot or an ETA, it will be because a real source exists — never because it looks good.
/// begin
Put your fleet on a system that refuses to lie.
Start self-serve in minutes — or tell us about your fleet and a human walks you through the real dispatch board, on real (demo) LRs.
Start your fleet’s OS →