Building and deciding each charge line, and sending the signed case to the supplier
- Cases built from portal, email, TMS and EDI
- The supplier's arguments before the supplier makes them
- Earlier rulings beside each decision
Inbound freight management that builds each routing guide violation from both sides' records, argues the supplier's side first, and leaves each charge to two named people.
See one routing guide case built screen by screen ↓A supplier ships a freight-collect order prepaid on its own carrier and adds the freight to its invoice, or sends the advance ship notice after the truck has left. Accounts payable holds the invoice, and an analyst pulls the purchase order, the load, the bill of lading, the notice and a rate into a spreadsheet and emails a chargeback.
That charge is built from the TMS alone. The routing request sits in the supplier portal, the desk's late reply in a mailbox, the notice's real send time in the EDI envelope, and the fuel table may be the wrong week's. The supplier holds the email that proves the buyer's miss and disputes, and good charges are lost with the weak ones. Nobody counts the desk's own misses, so suppliers stop trusting the program.
Built forInbound logistics analystsInbound transportation managersRouting desk coordinatorsAccounts payable teams
An analyst charges a supplier from the TMS alone, and the supplier answers with an email the analyst never saw.
Pieced together from five systems
Built-in controls
Each charge reaches the supplier with its evidence, after the buyer's own misses are found and dropped.
The inbound logistics analyst, the transportation manager and the routing desk use them to charge back a routing guide violation on evidence the supplier can open. The screens follow one off-routed cushion-fabric shipment.
demoThe shipper, its suppliers and carriers, the staff and every amount are sample data.
The analyst decides, the manager signs, the routing desk answers for its own replies, and accounts payable posts only what the supplier has seen.
Building and deciding each charge line, and sending the signed case to the supplier
The second signature, holds and releases, learned rules and settings
Answering routing requests within the one-business-day promise
Applying routing deductions in the payment run
Three findings a charge built from the TMS alone would have missed on this one case, before the routing charge was dropped.
The routing reply came 18 h 28 m after the one-day promise and 1 h 25 m after pickup, the morning after the supplier had chased it by email.
The first draft used 27.3% from the delivery week; the pickup week's 30.3% moved the draft from $836.30 to $822.20.
The notice named the supplier's own carrier and went out 3 h 00 m after pickup, so the $100.00 fee stood on its own.
demoSample data, from the working solution.
Each hands its work on by name; the analyst and the manager decide.
Reads the purchase order, its revisions and its freight terms.
Lines up the routing request, the desk's reply timed from its headers, the supplier's follow-up, the pickup and the ship notice.
Re-rates the shipment on the routed carrier's contract for the pickup date, to the cent.
Writes the buyer's points, and the same points as the supplier will read them.
Argues the supplier's side: late desk, PO change, wrong rate, gateway delay, a held notice, carrier availability.
Sends the signed case with fixed reply fields and reads the supplier's answer.
The manager, the buyer and accounts payable work from these screens around the open case.
demoSample data, from the working solution.
The agents read, rate and argue. Whatever touches a supplier's money or standing waits for a person, and loosening a control waits for two.
Inbound freight management is how a shipper that buys freight collect controls the carriers its suppliers use, through a routing guide and a routing desk. This solution enforces that guide: it builds each violation into a case both sides can read, and people decide each charge.
The guide sets the remedy: the extra freight over the routed cost, an administrative fee, and a fee for a late advance ship notice. The agents re-rate the routed carrier and draft each line; the analyst decides and the manager signs before the supplier sees it.
The routing log agent times the desk's reply from the email headers, the challenger argues that the miss excuses the shipment, and the analyst decides. The late reply is counted on the desk's own measure either way.
In the supplier portal: accept, or dispute by attaching a document and picking a code. The routing log agent compares the document with the records, and a note typed by the supplier goes to someone at the buyer to read.
No. The supplier gets a routed cost statement with the lane, the freight, the routed carrier, the pickup date and the amount. The contract rate and the fuel table stay internal.
It reads the TMS, the ERP, the EDI gateway, the supplier portal and the desk's email, and works the violations your vendor compliance program raises. Routing and booking stay in the TMS.
Every carrier bill re-rated against the contract before it is paid, with the working shown.
1-min demoFreight RFP ManagementRates that hold at tender: low bids checked against what each carrier accepted.
1-min demoDemurrage and Detention ManagementEvery billed day proved or disputed with its record, well inside 30 days.
1-min demoWe will rebuild one of your disputed routing cases with you from both sides' records, starting with the routing desk's reply.