01.04SCM for Transporter · TMS
One multi-tenant system for Indian transporters: bookings, trips and hisab, billing and receivables, double-entry accounts that post themselves, fleet and workshop, a native e-way bill module on NIC — and a WhatsApp assistant your staff, drivers and customers already know how to use.
WhySound familiar?
From transport owners and their office teams. Composite quotes from discovery calls — the problems are real; the names are left out.
“Kahan hai gaadi?” — forty times a day.
Customers call to ask where the truck is. We call the driver, then call them back. The whole office lives on the phone.
Owner · fleet of 60≈ 3 hours a day on status calls
“The e-way bill expired at the check-post.”
The vehicle changed and nobody updated Part-B. The truck stood for six hours and we paid the penalty.
Dispatch headPenalty + detention, every few weeks
“We find out a lane lost money in March.”
Diesel, tolls, empty returns and driver advances sit in different registers. The CA tells us at year-end.
Owner · finance12 months blind on lane margin
HowWhat changes with SCM for Transporter
Product screens with illustrative data. In your walkthrough we load your own lanes, plants, outlets or SKUs.
01Status calls
Answered in seconds, without a call
02Expired e-way bills
Extensions filed before midnight, not after
03Year-end surprises
Losing lanes found in week one
FieldSCM for Transporter in the field
The workplace it runs in, the person who uses it on a phone, the team at the desk and the detail it reads.
Photographs are illustrative — real customer sites are not shown.
01Open the cockpit
This is the screen your owner opens first. Lane margins after empty returns, the cash you will have each Monday for the next quarter, who owes you and for how long, and which trucks are earning. Click through it — it works.
Illustrative figures from a transporter cost model on real Indian lanes — not customer data. In your walkthrough, these are your lanes.
02One trip, end to end
Follow a single consignment from booking to lane profit. At every step the record that comes next is drafted from the one before — your team reviews, it doesn’t re-type.
Consignments (LR / CN)
The rate master fills the freight; an e-way bill is generated from the LR on the NIC form EWB-01, with GSTIN and HSN look-ups.
Indents · placements
When the LR gets its vehicle, the e-way bill Part-B update is proposed — and AR-18 chases it if it is still pending two hours later.
Trip starts · advances · budgets
An LR with a vehicle becomes a trip-start draft. Driver advances inside budget go for approval on WhatsApp, with a PIN above the threshold.
GPS · geofences · milestones
GPS pings every two minutes. Delay against ETA, GPS offline, route deviation and detention risk raise alerts; the e-way bill extends itself while the goods still move.
POD / ePOD
The driver sends a POD photo on WhatsApp. OCR reads the LR number, stamp, signature and date, matches it, and unblocks billing. The e-way bill closes on delivery.
Customer bills · e-invoice
Delivered LRs with POD become a bill draft, grouped by the customer’s billing cycle; the invoice PDF goes out on WhatsApp.
Receipts · ageing · DSO
Receipts are offered against the oldest open bills. Reminders go 3 days before due, on the due date and at 15 / 30 / 45 days overdue — with the statement PDF.
Trip settlement (hisab)
A finished trip becomes a hisab draft: km, advances, fuel, FASTag, toll and expenses inside the trip window, onto the driver ledger.
Double-entry accounts
Each financial document posts one balanced journal entry when it is saved, with the vehicle’s cost centre. An unbalanced entry is refused.
Profitability · CFO analytics
Settlement cost is split across CNs by booking km, so every customer, lane and vehicle carries a margin you can defend.
03The WhatsApp assistant
The assistant recognises who is writing from your masters, checks what that role may see, and answers from the company’s own records. The language model only classifies the message — the numbers always come from the database.
Ask
Instruct
Under the hood
04Native e-way bill module
8 modules and 20+ screens on NIC’s e-way bill API v1.03, through your GSP, per GSTIN. The LR carries the bill’s number and expiry; the bill extends itself while GPS says the goods still move.
Illustrative bill
Sandbox first. A GSTIN goes live only when the server, the connection and the GSTIN’s credential all say Live. Until then every action is checked and recorded as simulated — nothing leaves the server.
05Operations digital twin
More than 45 screens: command center, a 12-pane video wall, live map, delays and exceptions, gate, detention, ePOD, driver desks, workshop, stores, documents, challans, P&L and the CFO cockpit — each view role-wise.
Illustrative wall. Panes without a connected data source show a “Sample data” pill in the product.
06Accounts & profitability
Each financial document posts one balanced entry when it is saved. Analytics run per company on the same records, and every run reconciles itself before a number reaches a screen.
Journal · posted on save
| Ledger | Cost centre | Dr | Cr |
|---|---|---|---|
| Sundry debtors · customer | — | 1,18,000 | |
| Freight income | HR55 AB 4021 | 1,00,000 | |
| Output GST | — | 18,000 | |
| Σ Dr = Σ Cr | 1,18,000 | 1,18,000 | |
Illustrative entry. An unbalanced entry, or one in a frozen period, is refused before the document saves.
14 analytics dashboards
07Alerts & Autopilot
Alerts go to the right role group on WhatsApp, deduped per window and grouped into digests. Autopilot drafts the next document — or, where you allow it, completes it. Every company starts with automation off.
| Code | Rule | When | To |
|---|---|---|---|
| AR-01 | Trip delay against ETA | every 30 min | operations, customer |
| AR-02 | Dispatch intimation | LR → In transit | customer |
| AR-03 | Delivery confirmation | LR → Delivered | customer |
| AR-04 | POD pending > 24 h | every 12 h | operations, driver |
| AR-05 | GRN pending > 5 days | daily 10:00 | accounts, customer |
| AR-06 | Approval waiting past SLA | every 30 min | management |
| AR-07 | Payment due in 3 days | daily 11:00 | customer, accounts |
| AR-08 | Overdue > 30 days, with statement | Mon, Thu 11:00 | customer, accounts |
| AR-09 | Vehicle idle > 24 h (digest) | daily 08:00 | operations, management |
| AR-10 | Breakdown / SOS | real time | operations, management, maintenance |
| AR-11 | GPS offline / route deviation | every 30 min | operations |
| AR-12 | Vehicle document expiry ≤ 15 days | daily 09:00 | operations |
| AR-13 | Detention risk | every 30 min | operations, management |
| AR-14 | Daily MIS digest | daily 09:00 | management |
| AR-15 | Unbilled > 7 days (digest) | daily 17:00 | accounts |
| AR-16 | E-way bill expiring | hourly | operations, driver |
| AR-17 | Party GSTIN not active | on GST status change | accounts |
| AR-18 | Part-B pending 2 h after vehicle | every 15 min | operations |
| AR-19 | E-way bill generated by others for our GSTIN | on generation | operations |
| AR-20 | Automatic extension: extended, refused, waiting | every 15 min | operations |
| AR-21 | E-way bill expired while LR on the road | hourly | management, operations |
| AR-22 | Cancel window closing (20 h, LR not started) | every 30 min | operations |
Try it: set any flow to Off, Draft or Auto. New records are stamped Made by autopilot.
08Module atlas
Every module gets the same engine: list, search, filters and paging; a detail page with audit history; validated forms with auto-saved drafts; Indian financial-year numbering; CSV import and export; role checks. Business rules live in 154 hook files.
28 modules
28 modules
19 modules
18 modules
13 modules
13 modules
4 modules
13 modules
9 modules
9 modules
9 modules
8 modules
8 modules
8 modules
6 modules
5 modules
5 modules
4 modules
2 modules
1 modules
118+ custom screens, by area
09Connectors
GPS, ULIP, NIC, e-invoice and GST on one scheduler that runs per company and never double-sends. Companies that keep an outside ERP connect through signed events and webhooks.
Device pull every 2 minutes; pings, geofences and trip milestones. Live positions on the map and on WhatsApp.
Vehicle and driver records verified in bulk, with a diff preview before anything changes.
Toll crossings every 30 minutes, mapped to the trip by vehicle and time.
Daily challan pull, linked to the driver on the vehicle at that time.
Through the company’s GSP connection, per GSTIN, sandbox or live.
An e-invoice queue for customer bills.
GSTIN checker, daily party GSTIN status, GSTR-1 export.
Direct Meta Cloud API; 25 templates per company.
OCR for POD photos; speech-to-text for voice notes.
Pluggable per company: DeepSeek by default, or Anthropic, Gemini, OpenAI.
Signed inbound ERP events and outbound webhooks, HMAC over timestamp and body.
Local disk or Google Cloud Storage; short-lived signed file links.
10Security & control
Each company is sealed off from every other. The detailed security review is available to customers under NDA.
The company comes from the token, never from the client. References to another company’s records are refused.
AES-256-GCM. Never returned, exported or audited with values.
Approvals follow the company’s levels; a PIN above the threshold; escalation past SLA.
Customers see a first name and masked number; drivers never see rates or margins. Only the last 4 of ID numbers are stored.
The model only classifies. A fixed action catalogue, typed parameters — numbers always come from the database.
Nothing leaves the server until the live switch, the company’s Go live, and a daily send limit all allow it.
Every record keeps its history; every WhatsApp instruction is confirmed and logged.
Tracking links carry no financials, expire within 7 days and can be revoked; file links last 15 minutes.
FAQQuestions we get about SCM for Transporter
SCM for Transporter is a multi-tenant transport SCM that runs the whole office on one engine: LR/CN, trip hisab, billing, GL, fleet, tyres, drivers, NIC e-way bill, GPS/ULIP, a WhatsApp desk and CFO analytics. Short, factual answers for buyers, procurement and the assistants people ask first.
In short. SCM for Transporter is a multi-tenant transport SCM that runs the whole office on one engine: LR/CN, trip hisab, billing, GL, fleet, tyres, drivers, NIC e-way bill, GPS/ULIP, a WhatsApp desk and CFO analytics. It is built for transport owners and their office teams. It exists to remove the problems those teams describe in almost every first conversation: three hours a day on “where is my truck” calls; and penalty and detention when a Part-B expires unnoticed. With SCM for Transporter, teams get anyone can ask on WhatsApp — truck location, LR status, POD, dues — in four languages, and every e-way bill generated from the LR on NIC, with a clock and an owner. It connects to NIC e-way bill, GPS / ULIP, WhatsApp desk, GL & billing and Tally export, is used by Owner · LR desk · accounts · drivers, and runs on web + whatsapp. Like every Autowhat AI product, SCM for Transporter goes live on one site, lane or process first, usually within weeks, on managed cloud, in your own VPC or on-premises, and shares one operational record with the other products, so the second deployment reuses the data and integrations of the first.
Transport owners and their office teams. A multi-tenant transport SCM that runs the whole office on one engine: LR/CN, trip hisab, billing, GL, fleet, tyres, drivers, NIC e-way bill, GPS/ULIP, a WhatsApp desk and CFO analytics.
three hours a day on “where is my truck” calls; penalty and detention when a Part-B expires unnoticed; lane margin known only at year-end, from the CA.
anyone can ask on WhatsApp — truck location, LR status, POD, dues — in four languages; every e-way bill generated from the LR on NIC, with a clock and an owner; margin per lane after the empty return, every Monday; every document posts its own entry.
It connects to NIC e-way bill, GPS / ULIP, WhatsApp desk, GL & billing, Tally export. Users: Owner · LR desk · accounts · drivers. Channel: Web + WhatsApp.
With a 30-minute working session on your own data — an engineer from the relevant sector, not a sales queue. The first wave is scoped in that call; most products go live on one site, lane or process within weeks and then scale.
On managed cloud, in your own VPC (AWS, Azure or GCP) or on-premises, with your keys. SOC 2 Type II and ISO 27001 controls, India data residency when required, and local or open-weight models when policy demands it. The data stays yours.
11See it on your lanes
LR to e-way bill to POD to bill to hisab to lane margin — on WhatsApp and in the office desk, with an engineer who builds it.
