Trucks booked by phone, freight bills paid on trust
Indent to audited freight bill on one tracked workflow, with exceptions fixed after approval and customs declarations prepared for your broker.
What goes wrong today
A branch needs a truck, so someone calls three transporters and waits.
Acceptance, placement and gate-in run on phone calls and chat messages. Trucks leave half full and come back empty, and a breakdown or a wait at the consignee's dock is discovered when the customer calls.
Then the bill arrives. Freight, loading, unloading and detention are charged against a rate card that nobody checks line by line, and tax deductions and input-credit matching are done by hand at month end. For goods that cross a border, documents are re-keyed, HS codes are chosen from memory and container free time runs out unnoticed.
Why existing approaches fall short
- ERP shipping modules record the dispatch, but they do not run carrier acceptance, vehicle placement or a line-by-line bill check against the rate card.
- Tracking portals show a dot on a map without saying which order is at risk or what to do about it.
- Carriers are chosen by habit, because reliability by lane is never scored.
How FLX4 addresses it
-
TransNest puts indents, carrier acceptance, vehicle placement and gate-in on one workflow with SLA timers. Carriers are scored by lane, and tenders and spot bids are ranked on price and reliability. Load plans pack orders by weight and volume, pool part loads, consolidate multi-drop routes and look for return loads.
-
Trips are tracked with an ETA and its confidence. When a delay, breakdown or detention risk appears, an agent proposes a fix with the evidence it used, and nothing changes until the logistics head approves it. After delivery, the ePOD and gate logs settle detention, and each freight bill is checked charge by charge against the rate card, with contractor TDS and GSTR-2B matching in the same flow.
-
For cross-border legs, Tradix reads trade documents, suggests HS codes with citations, computes duty and prepares declarations for a licensed broker to file. It also tracks container free time and raises an alert before demurrage starts.
The loop, step by step
- 1 · Predict
Plan the load
Indents are grouped and packed by weight and volume. Route options weigh distance, tolls and past delays, and return loads are matched.
- 2 · Decide
Choose the carrier
Carriers are ranked by lane on price and reliability. At gate-in, documents are checked and a vehicle risk score passes, warns or blocks.
- 3 · Predict
Track and flag
The ETA updates with its confidence. Delay, detention and SLA-breach signals open an exception before the customer calls.
- 4 · Approve
The logistics head approves the fix
The agent proposes, for example, a new carrier and a revised ETA, with its evidence, and waits. A blocked vehicle needs a head-office override.
- 5 · Execute
Deliver and audit the bill
The ePOD closes the trip, detention is computed from the logs and the bill is checked line by line. Finance approves or disputes the excess with a reason.
- 6 · Learn
Score and remember
Carrier scorecards update, the decision and its outcome are recorded, and each trip's carbon is calculated on the GLEC method.
What it helps you work toward
Outcomes are measured against a baseline we agree with you in writing.
Overbilling caught before payment
Freight-bill excess flagged and disputed, per carrier per month
Fuller trucks
Truck fill by lane, from approved load plans against actual dispatches
Less detention
Detention hours per trip, by consignee and lane
Reliable carriers
Placement within the acceptance SLA and on-time delivery, by carrier and lane
Faster exception handling
Time from exception signal to approved action
What powers this solution
TransNest
See the late truck before your customer does, and pay only the freight your contract allows.
Explore TransNest →
Tradix
Customs declarations prepared from the documents you already have, and filed only by a licensed broker.
Explore Tradix →
PromiseNest
A delivery date your team can keep, with the evidence behind it.
Explore PromiseNest →Integrations
Road routing runs on a self-hosted map engine. GPS and telematics arrive through an inbound API with adapters for common payload formats, and device vendors are connected per deployment. Indents, SKUs and rates load from CSV or Excel. ERP posting (e.g. SAP), e-way bill, FASTag and KYC feeds are configured per deployment, and e-way bill numbers can also be entered or read from documents. Tradix prepares declarations for customs systems such as ICEGATE in India and Mirsal 2 in Dubai.
Bring us the decision behind this problem
In two weeks: the decision mapped, where money leaks, a baseline agreed in writing and a ninety-day plan with one target.
Read-only on day one. Your people approve every action. If the number does not move, you do not scale.