Warehouse loop in a TMS: consolidation planner, incoming BOLs from Google Drive, Telegram for the warehouse
The challenge
At a US logistics company warehouse consolidation lived in the dispatcher’s head: which loads are at the warehouse today, what goes with what, whether it fits a trailer by weight. The warehouse scanned original BOLs into Google Drive and the dispatcher searched for the file by hand and attached it to the load. The warehouse learned about arrivals and departures by phone.
What was built
We built a warehouse loop inside the existing TMS. The Planner shows warehouse loads as a Kanban by destination; the dispatcher builds trailers ahead of time, splits a load across several trailers (pallets and spots counted separately, 30 spots, 44,000 lbs with warnings), and a CARRIER OUT is created only when every load is physically at the warehouse. Google Drive is polled hourly: new BOL scans land in an inbox where one click assigns them to a load (with Undo), and the warehouse is reminded to scan. In the warehouse Telegram group the bot posts the morning arrivals, CARRIER OUT with the PDFs of all OUT BOLs and seal numbers, and CARRIER IN with the BOL from the load board.
Kanban by destination
loads at the warehouse and those en route to it, in destination columns: PRO, pallets, weight, days at the warehouse.
Trailer drafts
several trailers ahead of time, a load split between them; the remainder shows on the card.
Pallets and spots apart
trailer spots (30) are counted separately from pallets because pallets stack; weight limits are configurable.
Dispatch gate
a CARRIER OUT is created only when all loads on the trailer are in Warehouse status.
Incoming BOLs from Google Drive
hourly folder polling, dedup by file ID, one-click assignment, Undo, warehouse reminders.
Telegram for the warehouse
today’s arrivals, CARRIER OUT with OUT BOL PDFs and seals, CARRIER IN with the BOL; each event posts once.
The result
The dispatcher plans trailer loading a week ahead instead of “in the head”, the warehouse sees the day’s plan in Telegram, and nobody hunts for BOL scans in Drive anymore — they arrive in the system by themselves and wait for one click.
Tech stack
Have a similar challenge?
Discuss a projectNext case
CRM for an auto salvage yard
CRM for an auto salvage yard: donors, stock, sales, OEM →