Double brokering
A load re-brokered behind your back leaves a trail in the paperwork.
The carrier you booked is not the carrier at the dock. What comes back is a rate confirmation forwarded on, a pickup number requested from a phone nobody gave it to, and remittance details that changed after the load was covered.
The problem
What this is for
Double brokering is usually found after the cargo is gone, when two carriers invoice for one load or the real carrier calls about payment it never received. Everything needed to find it earlier is already in the correspondence: who the rate confirmation reached, who asked for the pickup number, and whether the bank details on the invoice match the ones on file.
The workflow
8 stages, and what runs where
Each stage names the module behind it. The chip says whether it runs on your network or ours.
- In your systems
- 3 stages
- At intake
- 1 stage
- On the platform
- 3 stages
- With a person
- 1 stage
- In your systems
The load is tendered
Your TMS posts the load, the carrier it went to, the lane and the rate. That record is what everything afterwards is compared against.
- In your systems
The rate confirmation carries a marker
A short code issued per load and given to the booked carrier alone. Nothing about it looks like a test, and no other party is ever told it.
- In your systems
Correspondence is forwarded in
Mail about the load arrives at an address you control and is posted with its headers intact. The headers are the evidence; the body is the context.
- At intake
The event is accepted or refused, in writing
Every message is recorded against the load, including the ones no rule fires on, so a quiet week is distinguishable from a broken integration.
- On the platform
The marker is watched
The code coming back from a party that was never given it is the strongest finding this analyzer has, and it floors the case at its top band on its own.
- On the platform
The message is read for the ordinary tells
A reply-to on a different domain from the sender, a domain registered last month, a lookalike of your own, remittance details in a body that never had them before.
- On the platform
A case opens against the load
One case per load per question, holding every finding and the message each came from. A second finding joins the case rather than paging your team twice.
- With a person
Somebody decides, and your system enforces it
If you wired one up, a webhook asks your TMS to hold the load while a person looks. The hold is released when the case closes, and a block is not.
What it runs on
Brokers, carriers, 3PLs, shippers, and factors, on the freight and logistics configuration. Verticals are settings over one platform, never separate products.
You supply the loads and the mail
Tenders, rate confirmations, pickup requests, and correspondence forwarded to an address you control.
We supply the marker and the rules
The per-load code, the message forensics, the case queue, and the record of what each finding was based on.
Your system keeps the escrow
Pickup numbers, driver checks and what a hold does at the gate stay in your stack. This asks; it does not enforce.
Why this shape
What the design buys
It looks before the cargo moves
The findings that matter arrive between tender and pickup, which is the window where a hold still costs less than a claim.
One marker beats a dozen heuristics
A code that only one party was given is evidence rather than a pattern, and it is the finding an analyst can act on without a second opinion.
The messages stay readable
Headers are kept, so a rule written next month can be run against the correspondence that arrived last month.
Limits
What it refuses
Stated here rather than found later. Each of these is enforced somewhere in the code, not only written on a page.
A marker only proves a leak
It says the code left the party that was given it. Whether that was fraud, a factoring desk, or a dispatcher forwarding mail is what a person decides.
Mail that never arrives is not read
Correspondence handled in a channel that does not reach the platform is correspondence it has no opinion about.
Nothing is said to the carrier
No reason, no score, and no notice ever reaches a counterparty from this platform. What your team says is your team's to decide.
Read next
Where to go from here
Freight and logistics
What the platform reads, and what comes back.
Carrier identity
The analyzer that asks who this carrier is in the first place.
What it costs
The shape of the pricing, and what is not yet rated.
The other analyzers
Carrier identity, Linked claims and Application fraud, on the same ledger and the same pipeline.