Warehouse in TMS

Warehouse loop in a TMS: consolidation planner, incoming BOLs from Google Drive, Telegram for the warehouse

📅2026
⏱5 weeks
👥2 developers
Warehouse planner · Kanban by destinationChicago, IL3PRO 11588 plt · 9,400 lbsPRO 11626 plt · 7,100 lbsPRO 11714 plt · 3,900 lbsDallas, TX2PRO 114910 plt · 12,300 lbsPRO 11665 plt · 6,000 lbsAtlanta, GA3PRO 11537 plt · 8,800 lbsPRO 11593 plt · 2,400 lbsPRO 11749 plt · 11,000 lbsTrailer draft #2 · ChicagoSpots22 / 30Weight38,200 / 44,000PRO 1158 — 8 plt · PRO 1162 — 6 plt · PRO 1149 — 5 of 10 plt (split)✓ all loads at WarehouseCreate CARRIER OUTTelegram · Warehouse update🚚 CARRIER OUT — Swift Lines (PRO 55213)• 1158 Milwaukee, WI → Chicago, IL 📎 1158 OUT BOL.pdf• 1162 Madison, WI → Chicago, IL 📎 1162 OUT BOL.pdf🔒 Seal 004812 · 📥 arriving today: 3 loadsIncoming BOLs · Google Drive, hourlyscan_0931.pdfassign → PRO 1171scan_0932.pdfassign → PRO 1174scan_0930.pdfassigned · undo
1 h
BOL import cycle from Google Drive
1 click
to assign a scan to a load
0
warehouse calls asking “what’s coming?”

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.

1

Kanban by destination

loads at the warehouse and those en route to it, in destination columns: PRO, pallets, weight, days at the warehouse.

2

Trailer drafts

several trailers ahead of time, a load split between them; the remainder shows on the card.

3

Pallets and spots apart

trailer spots (30) are counted separately from pallets because pallets stack; weight limits are configurable.

4

Dispatch gate

a CARRIER OUT is created only when all loads on the trailer are in Warehouse status.

5

Incoming BOLs from Google Drive

hourly folder polling, dedup by file ID, one-click assignment, Undo, warehouse reminders.

6

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

PHPYii2MySQLGoogle Drive APITelegram Bot APIcron

Have a similar challenge?

Discuss a project

Next case

CRM for an auto salvage yard

CRM for an auto salvage yard: donors, stock, sales, OEM →