TRANSNESTMove · Transport management & freight audit

See the late truck before your customer does, and pay only the freight your contract allows.

TransNest is transport management for Indian domestic road freight. It runs the trip from indent to audited bill: carrier selection, load and route planning, live tracking and ETA, exception handling, ePOD, and freight bill checks with contractor TDS and GSTR-2B. Built for manufacturers and distributors that run their own depot network.

Run the demo Discuss your freight and transport challenge

Flatbed truck carrying steel bars on a multi-lane Indian expressway

TransNest at a glance

1Reads

Indents with origin, destination, vehicle size and body, weight and volume (screen or CSV/Excel)
Rate cards, contracts, tenders and spot bids
GPS pings and telematics events (speed, braking, odometer, fuel) through the telematics API

2Decides

TransNest

Which carrier gets the indent, and whether an above-card rate is accepted
Whether a vehicle passes the gate-in risk check
How to recover a trip that has gone wrong, and whether to re-route trips already on the road

3Produces

Indent offers cascade to the next transporter when the acceptance window lapses
Placement, gate-in and dispatch recorded against the trip
ETA re-baselined; consignees updated by WhatsApp, SMS or email and the tracking link refreshed

↺ Learns Monthly vendor scorecards from trips, bills, claims and acceptance times back to 1 · Reads

The business problem

A breakdown at 1 pm, discovered at 6

It is 1 pm at the Nagpur mother depot. Twelve trucks left this morning. The branch raised the indents on WhatsApp and three transporters confirmed by phone. One truck has stopped on the highway near Sakoli with a clutch failure. Nobody at head office knows yet.
The Raipur sales depot finds out at 6 pm, when the truck misses its receiving slot. By then the only spare trucks are expensive, the 07:00 dispatch wave to distributors leaves without the stock, and someone agrees a spot rate on the phone with no record of why.
Three weeks later the transporter's bill arrives: full freight, plus detention for the hours the truck sat broken down. Accounts payable matches the total to the PO and pays it. Nobody compares each charge with the rate card, the gate logs or GSTR-2B.

Why the usual fixes fall short

Spreadsheets and WhatsApp groups record what happened. They cannot run an acceptance timer, rank a carrier or stop a truck with a lapsed permit at the gate.
ERP transport modules post the freight cost. They do not plan loads, predict delays, or audit a bill charge by charge against slabs and logs.
GPS dashboards show a dot on a map. They do not say which trip will miss its window, what the options are, or who signed off the fix.

Freight stays one of the largest costs you pay without checking line by line, and every exception is handled by whoever answers the phone first.

Freight costDetention, loading charges and spot premiums are paid as billed, because nobody checks each line against the contract and the gate logs.
Customer serviceLate trucks are discovered at the receiving dock, after the distributor orders they were meant to fill have already slipped.
Truck utilizationTrucks leave part-full and come back empty, because loads, routes and return legs are planned separately or not at all.
Tax & complianceContractor TDS, GSTR-2B matching, e-way bill numbers and vehicle documents are checked by hand, so mistakes surface at audit or at the gate.

In plain terms

What TransNest is, and how it fits

What it is: A transport management system with decision support, for domestic road freight in India.
Who uses it: Heads of logistics and their head-office transport desk, branch dispatchers, fleet managers, freight-payables teams in finance, transporters, drivers and consignees. Each has its own portal.
What it does: Runs the trip lifecycle from truck request to paid bill. It ranks carriers, plans loads and routes, tracks every vehicle and predicts arrival, tells consignees before they ask, proposes a fix or a re-plan when a trip goes wrong, checks every freight bill against the contract, and explains what each lane costs and emits.
How it fits your systems: Next to your ERP. Indents arrive on screen or by CSV/Excel upload. It works with SAP, Oracle, Tally and spreadsheets, your GPS vendor and FASTag feeds; connectors are configured per deployment. Nothing the agents propose is written until a named person approves it.
What is different: The numbers come from planning heuristics, rules and models trained on trip history. The language model explains and drafts; it never computes a price, a quantity or an ETA. Agent proposals and bill decisions leave a record: the evidence, the options, the approver and the outcome.

See it work

TransNest in action

A loaded truck breaks down 110 km out of Nagpur. Follow the delay from first signal to the audited freight bill, and choose the fix yourself.

A simulated scenario on representative data. You choose the option and give the approval; the numbers follow your choices.

End-to-end workflow

From data to decision to outcome

What goes in, what TransNest works out, what gets decided, what happens next, and how the result comes back.

InputsDATA

Indents with origin, destination, vehicle size and body, weight and volume (screen or CSV/Excel)
Rate cards, contracts, tenders and spot bids
GPS pings and telematics events (speed, braking, odometer, fuel) through the telematics API
Gate, dock and ePOD events from the branch, driver and consignee portals
Carrier bills, FASTag transactions and filed GSTR-2B values for matching

IntelligencePREDICT

Lane-level carrier scorecards and a price-plus-reliability ranking of bids
Load plans (bin-packing, SKU compatibility, LIFO loading) and route alternates on the India road graph
ETA, delay, cost and risk models trained on trip history
Exception signals, mid-journey re-plans and an agent that proposes a fix with the evidence it used
Lane cost variance broken into its causes: fuel, toll, detention, empty running and spot premiums

DecisionsDECIDE

Which carrier gets the indent, and whether an above-card rate is accepted
Whether a vehicle passes the gate-in risk check
How to recover a trip that has gone wrong, and whether to re-route trips already on the road
Which lanes run on owned vehicles and which on hired ones
Whether each bill line is paid or disputed

ExecutionEXECUTE

Indent offers cascade to the next transporter when the acceptance window lapses
Placement, gate-in and dispatch recorded against the trip
ETA re-baselined; consignees updated by WhatsApp, SMS or email and the tracking link refreshed
Approved bills posted to your ERP through the connector set up for your deployment

FeedbackLEARN

Monthly vendor scorecards from trips, bills, claims and acceptance times
Agent decision memory: what was proposed, who approved it, what happened
Trip actuals added to model training history, with an accuracy gate before any new model goes live
GLEC CO2e per trip, rolled into the BRSR export

Modules

Capabilities, organized by the work they do

21 modules in 5 groups. Open a module for its inputs, outputs, users and an example.

Buy capacity and place the truck5 modules Plan the load and the route4 modules Run the trip and handle exceptions5 modules Settle and recover4 modules Explain cost, carbon and performance3 modules

Buy capacity and place the truck

From a truck request to a compliant vehicle at the dock: who carries the load, at what rate, when it arrives and whether it may leave.

Indents & transport requestsRaise truck requests singly or in bulk, approve them, and get them accepted by a transporter against a clock.

Challenge: Indents raised on WhatsApp have no acceptance deadline, no audit trail and no fallback when a transporter goes quiet.
Inputs: Origin, destination, vehicle size and body, weight and volume, SKUs. Single entry or CSV/Excel upload.
Outputs: Approved indent, transporter offer, automatic cascade to the next transporter, SLA breach records. Indents can be grouped into one optimized transport request.
Used by: Branch dispatch raises; HO logistics approves deviations and builds requests; transporters accept.
Value: Every truck request has an owner, a deadline and a record, and every above-card rate has a named approver.
Works with: —
In action · illustrative: A branch uploads 40 indents for tomorrow. Those at card rate go straight to transporters; three quoted above card wait for L2 approval at HO. One transporter misses the acceptance window, and the offer moves to the next on the list.

Carrier intelligence & onboardingScore each transporter by lane on on-time delivery, cost, claims and route reliability, check its terms against the contract, and keep its documents current.

Challenge: Lanes go to the same transporter by habit, SLA breaches show up after the fact, and expired permits or insurance are discovered at the gate.
Inputs: Trip history, bills, claims, offer-acceptance timestamps, rate contracts and penalty clauses, onboarding documents and expiry dates.
Outputs: Monthly vendor scorecards (OTIF, cost, claims, reliability), lane leaderboards, a contract-checked transporter suggestion for each indent, early flags on carriers trending toward an SLA breach, and document-expiry alerts.
Used by: HO logistics, freight procurement; each transporter sees its own scorecard.
Value: Carrier decisions rest on lane-level evidence and the contract both sides signed.
Works with: GSTN, PAN, MSME and bank verification checks are configured per deployment.
In action · illustrative: On Nagpur to Raipur, one transporter accepts almost every offer but is often late; another is punctual but declines at month-end. The scorecard shows both patterns, and the suggestion weighs them. When the punctual carrier's on-time rate slips three weeks running, it is flagged before the monthly SLA review, with the trips behind it.

Tenders, spot bids & rate cardsBuy freight through tenders and spot bids, rank bids on price plus reliability, and keep versioned rate cards.

Challenge: Spot trucks are booked on the phone, and nobody can show later why a higher bid won.
Inputs: Lanes, volumes, bids, vendor scores, contract rates by vehicle size and weight slab.
Outputs: Ranked bids with the score shown, awarded contract rates, versioned rate cards that billing and planning both read.
Used by: HO logistics, freight procurement; transporters bid through their own portal.
Value: Freight rates and spot awards that can be explained to finance and to auditors.
Works with: —
In action · illustrative: Four carriers bid on a 180 km leg. The cheapest bid ranks last because its carrier scores poorly on reliability; the winner is above card, and the screen shows both numbers behind the ranking.

Vehicle placement & gate complianceCheck every vehicle and driver before gate-in, and stop the risky ones.

Challenge: Trucks with lapsed fitness, insurance or permits get loaded, and the risk only shows after a fine or an incident.
Inputs: Vehicle and driver details, documents, e-way bill number (entered, or read by OCR).
Outputs: A six-factor vehicle risk score; pass, warning or block at gate-in; an override workflow; dispatch.
Used by: Branch gate team; transporters submit vehicles; HO approves overrides.
Value: Non-compliant vehicles stop at the gate, and every exception has a named approver.
Works with: Vehicle and e-way bill numbers are entered or read by OCR from the documents; Vahan and e-way bill portal lookups are configured per deployment.
In action · illustrative: A vehicle with repeated breakdowns and a fitness certificate about to lapse scores in the block band. It cannot be loaded until HO approves an override and records the reason.

Dock appointments & yardBook receiving and loading slots, and see the state of the yard.

Challenge: Trucks queue at the gate while docks sit idle, and nobody can prove who missed the slot.
Inputs: Slot bookings, gate and dock events.
Outputs: Slot calendar, yard board, no-show penalties.
Used by: Depot and warehouse teams, transporters.
Value: Dock time is planned, and slot misses leave a record.
Works with: —
In action · illustrative: A transporter books the evening receiving slot at the Raipur depot. If it does not turn up, the no-show is recorded against it.

Plan the load and the route

Fewer trucks, fuller trucks, fewer empty kilometers, and routes chosen on time, toll and track record.

Load planning & consolidationPack orders into the fewest vehicles that respect weight, volume, SKU compatibility and drop order, and produce the paperwork for each load.

Challenge: Planners fill trucks by eye, so vehicles leave part-full, multi-drop loads are stacked in the wrong order, and manifests and invoices are typed up separately.
Inputs: Orders and SKUs with weight and volume, compatibility rules, drop sequence, vehicle sizes.
Outputs: Load plans with fill by weight and volume, LIFO loading sequence, LTL pools and multi-drop consolidations, each with its saving against separate trips. Each vehicle gets a lorry assignment and packing manifest, and the invoice and e-way bill data go to your ERP or GST connection.
Used by: HO planning, branch dispatch, warehouse loading teams.
Value: Fewer vehicles per tonne shipped, with the saving shown on each plan and no re-typing of load documents.
Works with: Packing uses first-fit-decreasing bin-packing and distance clustering, so every plan can be explained. E-invoice and e-way bill generation run through your ERP or GST connection, configured per deployment.
In action · illustrative: Three indents for Durg, Bhilai and Raipur go into one 32-ft vehicle, loaded so the Durg cartons sit at the door. The manifest lists cartons by drop, and the loading team works from it.

Route optimizationPlan routes for the day's vehicles together on distance, time, toll, delivery priority and past delay, with scored alternates for each trip.

Challenge: A dispatcher plans lane by lane and drivers pick their own roads, so toll and delay costs are only seen on the bill.
Inputs: Stop coordinates, delivery priorities and receiving windows, vehicle availability, the toll master with FASTag actual averages, traffic and weather signals, trip history.
Outputs: Route options and scored alternates, distance matrices, and multi-stop sequences planned across vehicles rather than one truck at a time.
Used by: HO planning, branch dispatch.
Value: Routes chosen on the cost of the trip as it is actually driven, for the fleet as a whole.
Works with: Self-hosted OSRM on the India road graph; Google Routes as a fallback with your key. Traffic and weather feeds are configured per deployment.
In action · illustrative: For Nagpur to Raipur, two alternates come back. The planner takes the one with the lower FASTag-actual toll, which is a few minutes slower. The Durg and Bhilai drops are sequenced together with the two other vehicles leaving that morning.

Backhaul, empty runs & fleet mixFind empty return legs, match them with loads, balance hubs, and set the mix of owned and hired vehicles lane by lane.

Challenge: Trucks come back empty because nobody sees the outbound and inbound plans together, and the split between owned and hired trucks is set once a year.
Inputs: Trips, locations, planned loads and returns, own-fleet running costs and hired rates by lane.
Outputs: Backhaul opportunities, empty-run reports by lane, hub balancing and reroute suggestions, and an owned-versus-hired recommendation per lane with its cost working.
Used by: HO logistics, fleet manager, finance.
Value: Empty kilometers become visible and, where a match exists, paid. Fleet spend follows each lane's volume pattern.
Works with: —
In action · illustrative: A truck delivering to Raipur on Thursday is matched with empty crates and returns going back to Nagpur. Steady daily volume on that lane favors owned vehicles, while a lane with sharp month-end peaks stays on hired trucks.

Vehicle planning & what-ifPlan vehicle needs from the demand forecast, and test disruptions before they happen.

Challenge: Truck shortages in peak season are discovered on the day, and nobody can say what a hub closure would cost.
Inputs: Demand forecast ranges (P10/P50/P90) from PlanningNest, lanes, capacity, scenario settings.
Outputs: Vehicle requirement plans, capacity gaps, cost-trend and seasonal outlooks; before-and-after comparisons for a hub disruption, cost shock or demand shift.
Used by: HO logistics, finance.
Value: Capacity is bought ahead of the peak instead of on the spot market during it.
Works with: Reads demand ranges from PlanningNest, running alongside in the same database.
In action · illustrative: The festival forecast shows a jump in volume to Raipur in one week. The plan flags the vehicle gap for that week early enough to tender for it.

Run the trip and handle exceptions

Know where every vehicle and trip stands, tell customers before they ask, and fix trouble with a named approver.

Live fleet tracking & driver scoringShow every vehicle on one map, and score how each one is driven and maintained.

Challenge: Dispatchers call drivers for locations and fleet status is scattered across calls and apps, so a problem is seen only after it has spread to other trips.
Inputs: GPS pings and telematics events (harsh braking, speeding, cornering, idling, odometer, fuel) through the telematics API, checkpoints, service history.
Outputs: Live map, stoppage and checkpoint alerts, turnaround time, driver behavior scores, fuel use by vehicle and lane, and service schedules from the kilometers actually run.
Used by: HO control desk, branch, fleet manager.
Value: One view of the fleet, with safety and maintenance planned from how vehicles are actually driven.
Works with: GPS and telematics vendors are connected per deployment; the ingest API normalizes the common payload formats.
In action · illustrative: A truck has been stationary for more than two hours, so a stoppage alert fires. A driver with repeated harsh braking on the Raipur lane is flagged for coaching, and a vehicle close to its service interval is booked into the workshop on its next idle day.

ETA intelligence & customer updatesPredict each trip's arrival with a confidence range, and tell the consignee before they have to ask.

Challenge: Customers call to ask where the truck is, and hear about a delay when it does not turn up.
Inputs: Live position, road-graph drive time, checkpoints, the trip history on that lane, receiving windows.
Outputs: An ETA with a confidence range refreshed every 15 minutes, early-delay flags against the receiving window, and proactive updates to consignees by WhatsApp, SMS or email, with a public tracking link and an OTP portal.
Used by: HO control desk, branch, sales teams, consignees.
Value: Delays are known while there is still time to act, and fewer people spend the day answering "where is it?"
Works with: ETA is road-graph drive time plus a gradient-boosting delay model trained on your trip history. WhatsApp, SMS and email senders are configured per deployment.
In action · illustrative: At the 15:00 refresh a truck's ETA moves past the Raipur receiving window. The trip is flagged on the control desk, and the depot manager gets the new ETA on WhatsApp with the tracking link before anyone picks up a phone.

Exception control tower & agentsBring every trip exception into one queue, and propose a fix with evidence for a person to approve.

Challenge: Breakdowns, shortages and SLA breaches arrive by phone, and the fix depends on who picks up.
Inputs: Delay, SLA and detention signals; trip, carrier and rate data; incident records and past decisions.
Outputs: Escalation queue, KPI bar and live map; agent proposals (reassign, adjust ETA, notify) that wait in the Action Center until approved.
Used by: HO control desk; HO logistics manager as approver.
Value: Exceptions are handled the same way every time, with the evidence and the approver on record.
Works with: Two agents work the queue: exception resolution and dispatch. Both retrieve evidence from rate cards, incidents, documents and past decisions, and every write they propose waits for approval.
In action · illustrative: A truck breaks down. The exception agent proposes moving the load to a spot vehicle, citing the rate card, the bid ranking and a similar past incident. Nothing changes until the HO logistics manager signs.

Mid-journey re-routingRe-plan the trips affected when a road closes, a truck breaks down or a priority order lands, across all the vehicles on the road at that moment.

Challenge: A route set at dispatch is stale by lunch, and the dispatcher re-plans by hand, one truck at a time, while deliveries slip.
Inputs: Live positions and ETAs, delivery priorities and receiving windows, carrier terms and rate cards, available vehicles and spot bids, route alternates.
Outputs: One re-plan for the affected trips (new road, new drop order, a load transfer or a spot vehicle), each change with its reasoning trace: what changed, what was weighed and why this plan.
Used by: HO control desk; HO logistics manager approves.
Value: Re-planning happens across the fleet in one pass, with the reasoning written down and a person signing it.
Works with: Draws on route optimization, ETA and carrier data. Every change waits in the Action Center for approval, unless your administrator has marked that rule as low-risk.
In action · illustrative: A closure on the main highway east of Nagpur puts four trucks behind schedule. The re-plan sends two by an alternate road, swaps the drop order on a third so the priority distributor is served first, and leaves the fourth unchanged. The desk reads the trace for each and approves the set.

Delivery, ePOD & detentionClose each trip with proof of delivery, and compute detention from the logs.

Challenge: PODs come back on paper weeks later, and detention claims cannot be checked.
Inputs: Trip events, photo ePOD from the driver's mobile web app, gate and dock timestamps.
Outputs: Trip state, photo ePOD, shortage and damage records, detention hours per stop, and an OTP portal for consignees.
Used by: Drivers, branch, consignees.
Value: Detention and shortage claims are settled from timestamps.
Works with: —
In action · illustrative: Gate logs show a truck spent under two hours at the dock, inside free time, so the detention line on its bill is flagged before payment.

Settle and recover

Pay the right amount, and recover what went wrong, from evidence the trip already captured.

Freight bill audit & payablesCheck every carrier bill charge by charge against the contract and the trip record before it is paid.

Challenge: Bills are paid on the total, so excess detention, wrong slabs and duplicate charges go through.
Inputs: Carrier bill (uploaded or read by OCR), rate card, detention logs, filed GSTR-2B values, FASTag transactions.
Outputs: Line-level flags, approve or dispute with reason codes, contractor TDS deduction, GSTR-2B match, FASTag toll reconciliation, split billing, COD reconciliation and a bill audit log.
Used by: Finance (freight payables); transporters see the outcome.
Value: You pay what the contract allows, with the reason for every deduction on record.
Works with: GSTR-2B values are imported from your GST return data. FASTag bank feeds and ERP posting are configured per deployment.
In action · illustrative: A transporter bills ₹58,400. Against the card (freight ₹48,000, loading ₹1,200, detention slab ₹3,600) the bill should be ₹52,800, so ₹5,600 is flagged and Finance disputes it with a reason code.

Claims & insuranceRun shortage and damage claims from the trip record to settlement.

Challenge: Claims stall because the evidence is split between the POD, photos and email.
Inputs: Shortage and damage records, ePOD photos, cargo-insurance details.
Outputs: Claim states, cargo-insurance claims, disputes and settlements.
Used by: Finance, HO logistics.
Value: Claims are raised from evidence the trip already captured.
Works with: —
In action · illustrative: A two-carton shortage logged at ePOD opens a claim against the transporter with the photo and the loading record attached.

Cold chain & proof of conditionShow that temperature-sensitive goods stayed in range, or exactly when they did not.

Challenge: Excursions surface when a customer rejects the load, with no record to settle the claim.
Inputs: Sensor readings (generic JSON or sensor-box formats) and the allowed band for the product.
Outputs: Excursion episodes, a verdict, and a proof-of-condition report per shipment.
Used by: HO logistics, quality, finance.
Value: Condition disputes are settled on recorded readings.
Works with: Sensor vendors are connected per deployment.
In action · illustrative: A pharma load briefly runs above its 2–8 °C band. The readings are grouped into one excursion episode and attached to the shipment's proof-of-condition report.

Reverse logistics & recallsMove returns, recalls and returnable assets back through the network.

Challenge: Returns and recalls run on email, and pallets and crates disappear between depots.
Inputs: Return requests, condition grade and disposition (entered by your team), batch numbers.
Outputs: Reverse shipments routed to the nearest qualified node, recall batch trace, pallet and crate custody ledger, and hand-off records for Stocki and SalesI.
Used by: HO logistics, branch.
Value: Recalls and returns move on the same tracked workflow as outbound freight.
Works with: Condition grades are entered by your team. Value-based grading and disposition decisions sit with ReturnNest.
In action · illustrative: A batch recall lists every depot and distributor that received the batch, and books reverse pickups from each.

Explain cost, carbon and performance

Know why a lane costs what it does and what it emits, and get answers in plain language with the sources shown.

Lane cost intelligenceExplain why a lane's cost moved, and compare lanes to find consolidation and savings.

Challenge: A cost spike is a red number on a monthly report, and finding the reason means a spreadsheet hunt through fuel, tolls, detention and route history.
Inputs: Freight bills, rate cards, fuel prices, FASTag toll actuals, detention and claims records, route and driver history, load fill.
Outputs: Cost variance per lane against the card and the lane's own history, broken into its causes (fuel, toll, detention, empty running, spot premiums), lane benchmarks, and consolidation recommendations.
Used by: HO logistics, finance.
Value: Cost reviews start from the reason, so the fix is a decision instead of an investigation.
Works with: The breakdown is computed from your own bills and trips; the language model writes the explanation from it and never computes a figure.
In action · illustrative: Nagpur to Jabalpur runs well above its usual cost per tonne this month. The breakdown shows most of it is spot premiums on Mondays, when the contracted carrier declines, plus detention at one consignee. The recommendation is to move the Monday load to Sunday night.

Carbon & ESG reportingAccount Scope-3 transport emissions per trip, score the greenest route, and export the results for BRSR.

Challenge: Transport emissions are estimated once a year from fuel spend, if at all.
Inputs: Trips, loads, distances, emission intensities.
Outputs: CO2e per trip and leg on the GLEC method (well-to-wheel and tank-to-wheel), greenest-route scoring, a BRSR export and an ESG report.
Used by: HO logistics, sustainability.
Value: Emissions reported from trip records instead of annual estimates.
Works with: —
In action · illustrative: Each trip is booked at its tonne-kilometers and CO2e, and the quarter's BRSR file is built from all of them.

Logistics copilotAsk about any lane, trip, carrier, bill or cost in plain language, and get an answer with its sources.

Challenge: Answers to simple questions sit across five screens and a spreadsheet, and a lane question can take an afternoon.
Inputs: Your question, answered by chaining TransNest's data tools across trips, GPS, contracts, bills, fuel and history.
Outputs: An answer with the trace of the tools it called and the records it used, so you can check the source.
Used by: HO logistics, finance, branch managers.
Value: Faster answers, with their sources shown.
Works with: The copilot reads. Changes go through the screens and their approvals.
In action · illustrative: "Why is Nagpur to Raipur over its card rate this quarter?" returns the share from detention, from spot awards and from toll changes, with the bills and trips behind each.

Intelligence and automation

What the intelligence actually does

Five levels, from seeing what is happening to learning from it.

Visibility

Every indent, placement, vehicle, trip and bill in one view per role, with acceptance timers, a live fleet map, driver scores and a control-tower queue of open exceptions.

Prediction

An ETA with a confidence range, refreshed every 15 minutes; delay, SLA-breach and detention risk per trip; carriers trending toward an SLA breach; cost variance per lane with its causes; vehicle needs ahead of peak weeks.

Decision

Carrier ranking on price plus reliability, load plans, route alternates scored on time, toll and past delay, mid-journey re-plans with a reasoning trace, the owned-versus-hired mix per lane, and the agent's proposed fix for an exception, with its evidence.

Execution

Approved actions are written inside TransNest: indents, cascades, placements, re-routes, ETAs, consignee updates and bill decisions. Posting to your ERP is configured per deployment.

Learning

Monthly vendor scorecards, an agent decision memory, and trip actuals added to model training history. A retrained model goes live only if it passes an accuracy gate.

Runs automatically

Indent offers cascade to the next transporter when the acceptance window lapses
ETA refresh, delay and SLA signals, consignee ETA updates, and detention computed from logs
Charge-by-charge bill checks, contractor TDS computation and GSTR-2B matching
Low-risk rules that your administrator marks as auto-execute

Always waits for a named person

Indents whose rate deviates from the card (L2 approver)
Every re-plan and every change the exception and dispatch agents propose (HO logistics)
Overrides of the vehicle risk gate at gate-in (HO)
Approving or disputing each freight bill (Finance)
High-risk rules routed to the Action Center (HO)

Business value

What it helps you work toward, and how we measure it

We agree the baseline with you in writing before a pilot starts. These are the outcomes we measure.

Pay only what the contract allows

Every bill line checked against the card, the award and the trip logs before payment.

Value of bill lines flagged and upheld on dispute each month, as a share of freight billed.

Late trips caught while there is time to act

Delays flagged from the ETA model, with options and an approver, before the receiving slot, and consignees told before they call.

Share of delayed trips flagged before their planned arrival, how far ahead, and inbound "where is it?" calls per 100 trips.

Fuller trucks, fewer empty returns

Loads consolidated and return legs matched as part of planning.

Average fill by weight and volume, and empty-kilometer share, against a baseline agreed in writing before go-live.

Carriers chosen on evidence

Lane scorecards and transparent bid ranking replace habit.

Share of indents placed with the top-ranked carrier; on-time and acceptance rates by lane.

Statutory checks without spreadsheets

Contractor TDS, GSTR-2B and BRSR come out of the same records the trips create.

TDS and GSTR-2B mismatches found before payment; share of trips covered in the BRSR export.

Illustrative example

A transporter bills ₹58,400 for a Nagpur to Raipur trip. TransNest reads the rate card: freight ₹48,000, loading ₹1,200 and a detention slab of ₹3,600 make ₹52,800. The ₹5,600 difference is flagged, Finance disputes it with a reason code, contractor TDS is computed on the approved amount, and the invoice is matched to GSTR-2B.

Enterprise readiness

Integration, control and deployment

ERP & system integration

CSV/Excel upload for indents and SKUs, a telematics ingest API that normalizes the common GPS payload formats, OSRM routing on the India road graph, HMAC-signed outbound webhooks, and read-only links to OpsNest and PlanningNest. Works with SAP, Oracle, Tally and spreadsheets, GPS and telematics vendors, FASTag feeds, the GST and e-way bill portals, Vahan, KYC checks and WhatsApp/SMS providers; connectors are configured per deployment.

Data sources & connectivity

Your records stay in your tenant. Tenant-identifying data is masked before any language-model call, and the model never computes a price, quantity or ETA.

Deployment & implementation

Containerized services on a cloud VM: API, workers, web app, routing engine, Postgres, Redis and object storage.

Configuration & business rules

Per-tenant module licenses, white-label settings, versioned rate cards and approval thresholds. India GST and contractor TDS, tax plugins for GCC VAT, Malaysia SST and Indonesia PPN, and Arabic, Bahasa and Thai locales.

Roles, access & approvals

Six roles with their own portals (branch, HO, finance, transporter, driver mobile web app, admin), plus an OTP portal for consignees.

Security, governance & audit

Every query is scoped to the tenant in the application, with a guard that blocks cross-tenant writes and database row-level security as a backstop.

Human oversight & exceptions

Agent changes are proposals until a person approves them. Maker-checker on indents, transport requests, gate overrides and bills; bill audit log and agent action ledger. Low-risk rules can be set to run automatically, and they are listed in the Action Center.

Scale & ongoing optimization

GPS ingest, ETA refresh and bill checks run on background workers, off the request path. Capacity is sized per deployment to your trip and ping volumes.

Straight answers

Questions about TransNest

Something else? Ask a specialist.

How do we start?

Read-only, on your own lanes, rate cards and recent freight bills. The first bill-audit findings and lane scorecards come from your data before anything writes back. Indents and masters load by CSV/Excel, and live tracking starts once your GPS vendor is connected.

Does it send WhatsApp updates to consignees?

Yes. ETA changes, delay alerts and the tracking link go out by WhatsApp, SMS or email through the provider you choose; senders are configured per deployment. Consignees can also check status in their own OTP portal.

Does it connect to SAP, our GPS vendor, FASTag and the e-way bill system?

It works with SAP, Oracle, Tally and spreadsheets, with GPS and telematics vendors through its ingest API, with FASTag bank feeds, and with the GST and e-way bill portals. Connectors are configured per deployment. Where no portal link is set up, the e-way bill number is entered or read by OCR from the document.

Will the AI reassign trucks on its own?

No. The exception and dispatch agents, and mid-journey re-plans, propose changes with their evidence and wait for an HO approver. Your administrator can let specific low-risk rules run automatically, and those rules are listed in the Action Center.

Can it handle more than road freight inside India?

Its depth is Indian domestic road freight. For shipments that cross a border it records multimodal legs, customs declarations with an HS-code lookup, Incoterms and landed cost. Customs preparation and trade compliance are the job of Tradix.

Next step

Discuss your freight and transport challenge

Freight is where service promises are kept or broken, and where money leaves without anyone checking the lines. TransNest keeps both on one record, with a named person signing every decision that changes it.

Talk to a specialist

Manufacturers and FMCG distributors in India that run their own depot network, with a head of logistics who wants control of carriers and a CFO who wants freight bills audited.

In the same loop