Custom Software
Tender management for a shipper co-op that outgrew email blasts
Freightline emailed tenders to a list and hoped. We built tender management with preferred capacity, timers, and a clean hand-off into their TMS.
The operational problem
Every load went to the whole list. Preferred carriers stopped opening the mail. Backup carriers quoted late.
Service failed on the lanes they cared about most, while they overpaid spot on lanes they could have sequenced.
What was breaking down
- One BCC list for every tender
- No timer before falling to the next carrier
- Award details retyped into the TMS
How Striders Tech approached it
We sequenced capacity the way the co-op already thought about it: house carriers first, then backups, then spot — with a clock and a reason code.
What we built
- Lane-based preferred lists
- Timed fallback if a tender is not accepted
- Award payload into the existing TMS
- Reason codes when a house carrier declines
Results the team can measure
- House first on contracted lanes without manual policing
- Less noise for carriers who are not in the sequence
- Cleaner TMS because awards are not retyped
Who this case study is for
Shippers and co-ops whose “carrier strategy” currently lives in someone’s inbox rules.
Freightline Cooperative operates in freight. The work is a custom system designed around their process, not a generic template with extra fields bolted on.
What changed after the system went live
on contracted lanes without manual policing
for carriers who are not in the sequence
because awards are not retyped