← All insights

Pan-India Truck Tracking for Manufacturers and Supply Chains

In my work with manufacturers, I show how plants monitor inbound raw material and outbound finished goods across Indian corridors, including transporter trucks without GPS.

By Niraj · Updated 2026-09-11

In my work with plants, factories don't run on “driver said.” Production planning needs inbound ETAs. Finished goods need outbound proof of movement. When transporters can't offer consistent GPS access, I've watched plants fall back to manual follow-ups, overtime, stockouts, and penalties that never appear in the freight rate.

• 7.1% — auto industry contribution to GDP (NITI context) (NITI Aayog transport insights)
• 66% — freight still on road, plants depend on trucks (NITI Aayog)
• Gati Shakti — national programme to improve multimodal connectivity (GoI)

Practical rollout

I start with high-risk lanes: expensive materials, time-critical dispatches, chronic delay corridors. I track by vehicle number at indent. I share status with logistics and plant in one place. I expand once the rhythm is clear. I don't need a company-wide telematics program to get value in week one.

How Lorryman helps manufacturers

Pan-India tracking for shipments across the supply chain, including transporter trucks, without installing GPS on every vehicle.

Inbound is production. Outbound is revenue.

I've lived this on the road. A missing RM truck isn't a logistics anecdote. It's a line stop, a changeover, overtime, and a quality argument. A missing FG truck is a customer penalty and a distributor fight. Manufacturers feel road dependency because NITI-style freight mixes still put most tonne-kilometres on trucks. Gati Shakti and NLP improve the country. They don't tell me where today’s inbound is. That last mile of truth is a plant system, not a ministry dashboard.

Multi-plant networks make it worse. A visibility habit in one factory and a phone tree in another means the corporate logistics team can't compare anything. I standardise on vehicle-number tracking at indent across plants. Then I can talk about lanes, not personalities of coordinators.

Transporter GPS is a maybe. The trip is a must.

Some dedicated transporters will share feeds. I celebrate that. I don't build the company’s only process on it. The day a spot vehicle appears, and it will, I still need a picture. Dual-stack: consume a feed when offered; start a trip from RC when not. Plants that insist on “one telematics partner for India” discover India doesn't work that way.

I start with high-risk SKUs and chronic corridors. I don't boil the ocean in month one. Ten watched lanes that change overtime bills will fund the next fifty. Leadership likes proof more than a nationwide wallpaper of trucks they won't look at.

Who should sit on the same screen

Stores, production planning, finished-goods dispatch, and customer logistics. If only a transporter cell sees tracking, the plant will still call drivers. Shared objects change behaviour. I put the board in the morning meeting. I ask “what is stalled?” not “whom did we call?” Within a month the meeting shortens because the rumours are gone.

Auto and other manufacturing contexts in NITI notes exist to remind I that GDP-sensitive industries still ride trucks. I treat truck truth as a production input. Lorryman is the pan-India layer for transporter trucks I'll not instrument, including the ones that show up with an hour’s notice.

Governance without a programme office

I require RC on every indent. I require trip start before gate-out. I review exceptions twice a day on the top lanes. That's the whole PMO. If I need a steering committee to watch trucks, I have staffed the problem incorrectly. Visibility should be boring. Quiet and boring is actually what I want.

Manufacturers who get this right stop confusing freight rate with freight reliability. Reliability is a tracked trip. Rate is a bid. I need both. Only one of them currently lives in a WhatsApp group. I move it.

Stores see inbound as the line; dispatch sees outbound as the invoice

I've lived this on the road. A missing RM truck isn't a logistics anecdote. It's a line stop, a changeover, overtime, and a quality argument about which batch I ran instead. A missing FG truck is a customer penalty, a distributor fight, and a sales team that stops believing the plant. Manufacturers feel road dependency because Indian freight still puts most tonne-kilometres on trucks. Gati Shakti and the National Logistics Policy improve the country. They don't tell me where today’s inbound is. That last mile of truth is a plant system, not a ministry dashboard. I treat truck truth as a production input the way I treat a bill of materials. If stores can't see whether a coil or a resin tanker is moving, MRP is guessing. Guessing at a multi-plant network is how I buy buffer stock with working capital I thought I had saved on freight rate.

Outbound is a different desk with the same blindness. Finished goods sitting on a hired lorry I can't see are revenue I can't promise. Customer logistics will invent ETAs. Distributors will hold labour. Debit notes will arrive wearing a delivery clause. Pan-India tracking for manufacturers has to cover both directions on the same standard, or corporate logistics will compare nothing. A visibility habit in one factory and a phone tree in another means I'm measuring coordinator personalities, not lanes. I standardise on vehicle-number tracking at indent across plants. Then I can talk about corridors. Then a shutdown in one site and a dispatch peak in another can share a language. Without that language, “pan-India” is a slogan on a slide about GPS partners who don't cover the spot truck that showed up with an hour’s notice. I cover that truck or stop using the word network.

One plant on a board, one plant on a phone tree

Multi-plant networks fail in a boring way. The hero plant has a coordinator who lives on WhatsApp and looks effective. The quiet plant has fewer shouts and more surprises. Corporate asks for a dashboard. Each site sends a different screenshot. Nothing is comparable. I force one object: RC on every indent, trip started before gate-out, exceptions reviewed twice a day on the top lanes. That's the entire programme office. If I need a steering committee to watch trucks, I have staffed the problem incorrectly. Visibility should be boring. Quiet and boring is actually what I want. I put the board in the morning meeting. I ask what is stalled, not whom we called. Within a month the meeting shortens because the rumours are gone. Sites that refuse the standard aren't colourful. They're incomparable, and incomparable sites can't be managed as a network. A network is a standard, not a collection of local heroes.

Auto, steel, FMCG, and engineering plants all ride hired trucks for inbound and often for outbound. The commodity changes. The assignment pattern doesn't: a mix of dedicated transporters who might share a feed and market vehicles who won't. I don't build the company’s only process on the feed. I celebrate it when it exists. Dual-stack: consume a feed when offered; start a trip from RC when not. Plants that insist on one telematics partner for India discover that India doesn't work that way. Owners, permits, and same-day replacements don't sit inside one SIM farm. I sit inside the trip. The trip is what production and revenue actually depend on. The chassis is often someone else’s small business in a nagar I'll never visit. I honour that, and pan-India stops meaning a fantasy map of every lorry in the republic.

Transporter GPS is a maybe; the trip is a must

Some dedicated transporters will share feeds. Take them. I don't make reliability of a paint line depend on a password that expires when a vendor relationship cools. The morning a spot vehicle appears for a shortage, and it will, after a breakdown or a no-show, I still need a picture. I write that into the SOP: feed if present, RC trip always. Security at the gate shouldn't load a truck that's not on a trip. That sounds harsh. It's kinder than a line stop at 2 p.m. because nobody knew the replacement was standing. Lorryman is the pan-India layer for transporter trucks I'll not instrument, including the ones that show up with an hour’s notice. I use it as the always path. I use telematics as the extra on assets someone actually manages. Extras are welcome. Always paths keep factories open.

I start with high-risk SKUs and chronic corridors. I don't boil the ocean in month one. Ten watched lanes that change overtime bills will fund the next fifty. Leadership likes proof more than a nationwide wallpaper of trucks they won't look at. Chronic corridors are known in every manufacturing network: the lane that always dies at a particular check-post, the ghats that eat night runs, the city that holds gate-in until afternoon. I watch those first. I share the stalls with production planning, not only with a transporter cell. If only the transporter cell sees tracking, the plant will still call drivers. Shared objects change behaviour. Unshared objects become another report. Manufacturers already have enough reports. They need a morning question: what inbound will miss the shift, what outbound will miss the booking. I answer from a board. Then the network is real.

Who sits on the same screen at 8 a.m.

Stores, production planning, finished-goods dispatch, and customer logistics. If any of those desks is missing, I'll grow a parallel rumour. Stores will over-receive “just in case.” Planning will change over late. Dispatch will promise a buyer from a driver quote. Customer logistics will apologise in a different story. One screen doesn't mean one login for sixty people on day one. It means the object is the same when they look. I put it in the production meeting the way I put yesterday’s output. I ask for stalled trips before I ask for excuses. Within weeks the excuses change shape: they become requests to escalate a dwell, not performances of optimism. That's a healthier plant. It's also how corporate can compare sites without flying in to listen to coordinators compete at being busy on the phone. Busy phones aren't a KPI a COO can compare across states.

Customer logistics needs a translation, not a raw ping. I give them a sentence they can send: moving on corridor, stalled since a timestamp, RC changed at night and the new trip is live. I don't give them a pin hunt. The buyer doesn't care which nagar the owner lives in. The buyer cares whether to hold labour. Manufacturing companies that treat customer updates as a coordinator art form will keep losing to plants that treat them as a copy from a trip. Art forms don't scale across India. Copies do. I standardise the sentence book the way I standardise a quality alert. Then a plant in Gujarat and a plant in Tamil Nadu sound like one company when a distributor calls. Pan-India tracking is partly a writing problem. I write from the board. I stop writing from missed calls. Missed calls don't travel; sentences from a trip do.

Rate is a bid; reliability is a watched RC

Manufacturers who get this right stop confusing freight rate with freight reliability. Reliability is a tracked trip. Rate is a bid. I need both. Only one of them currently lives in a WhatsApp group in too many networks. I move it. Volume should drift toward transporters who can live with a trip on every assignment, dedicated or spot. Transporters who refuse a vehicle number are refusing the operating document of the load. That's not a partnership. It's a hope. Hopes don't keep a line running. Central procurement often protects a rate and forgets the plant’s overtime. I put overtime and debit notes next to the rate in the quarterly transporter review. Visibility makes that review possible. Without it I'm negotiating folklore. Folklore is how a cheap carrier becomes the expensive one after three line stops nobody can prove.

Governance without a programme office, restated for a COO: require RC on every indent; require trip start before gate-out; review exceptions twice a day on the top lanes; no location calls without a reason code. That's four rules. They travel across plants. They don't need a war room in Gurgaon. They need a plant head who won't load a nameless truck. If a site can't obey four rules, the problem isn't software. It's discipline. Software won't save an undisciplined gate. It will make a disciplined gate comparable to the next site. Comparability is the manufacturing prize. Pan-India truck tracking is how I buy it on hired capacity I'll never own. I own the trip. I leave the chassis to the owner. I run the country as a network of trips, not as a hope that every transporter bought the same box.

Shutdowns, peaks, and the hour’s-notice lorry

Shutdowns concentrate inbound. Peaks concentrate outbound. Both destroy dedicated-fleet fantasies because I'll hire extra market trucks I have never seen. Those weeks are when a no-device, vehicle-number layer earns its keep. Fitment calendars won't finish before the shutdown window. Driver WhatsApp groups will drown. The only stable object is the RC at the gate. I start those trips as if the factory’s month depended on them, because it does. Pre-build the indent fields so a contractor’s coordinator can type a number without a training festival. If peak requires a new vendor, the vendor still owes me a registration before loading. No registration, no load, no argument. Harsh in a sentence. Kind to the people who would otherwise work a second shift because a nameless lorry vanished into a corridor. Peak isn't an excuse to go blind. Peak is the exam.

After peak, don't drop the standard. Sites love returning to hero coordinators and phone trees when the crisis ends. I keep the four rules. I keep the morning stall question. I keep dual-stack. The next shortage won't send a meeting invite. Manufacturers who treat visibility as a project that ends will re-learn blindness every season. Manufacturers who treat it as master data, like a material code, will be bored, which is the correct emotional state for a control tower. Boredom means the network is comparable. Excitement means someone is hunting a driver. Choose boredom. Then pan-India isn't a conference adjective. It's how a coil in one state and a carton in another can be talked about in the same meeting without theatre. That meeting is the product. The map is only the evidence. I keep the meeting even when the peak is over.

What corporate should stop asking IT to do

I stop asking IT for one telematics partner who will cover every hired N3 in India. That request is how budgets disappear into a fitment graveyard. I ask IT to make the trip object available in the systems plants already open, or at least in one shared board everyone is allowed to see. I ask logistics to own assignment quality: the plate at the gate matches the trip. I ask production to staff from stalls, not from optimism. Those are role splits a COO can enforce. A single vendor to instrument the republic isn't a role split. It's a wish. Wishes are expensive in manufacturing because the line doesn't pause for them. The line pauses for missing RM. I see the RM. I see the FG. I see the replacement at 2 a.m. Then IT can still run telematics on the captive lot, where it belongs, without being blamed for a nagar they can't wire.

Track trucks without GPS on Lorryman