WMS for forwarders. Built by one.
Manhattan, SAP EWM, Logiwa — built for someone else's warehouse. Binsy was built inside a freight forwarding house, by a freight forwarder, for freight forwarders running 3PL. Different DNA shows.
Three of Infinity's customers arrive today. Three different process needs.
Generic WMS:“Pick one process. Make all customers use it.”
Cascadia creates the ASN. Binsy preps the floor.
Truck details · 3 SKUs declared · receiving mode pre-selected from the customer's subscription · bin pre-suggested by rule. By the time the truck rolls in, the foreman knows exactly what to scan and where to put it.
Three modes. The cargo picks.
Regulated samples need every piece scanned. Bulk commodities need none of it. Pallet electronics sit in the middle. Same warehouse floor — different mode per customer's cargo.
Same Binsy. Same receiving dock. Per-customer mode picked by what their cargo actually needs.
- →Every piece barcoded · unique
- →Per-SKU serial tracking
- →Pick-by-scan from REF-A-12-3
- →Full audit trail per piece
- →Pallets and boxes barcoded
- →Contents listed not scanned
- →Pick-by-pallet · don't unbox
- →Audit at container level
- →No piece/pallet tracking
- →Just totals · weight · volume
- →Pick-by-volume · simple
- →Tonnage-billed
Generic WMS: picks one mode at install time. The customer who needed a different model? They leave for someone else.
Receipt confirmed. You decide what Cascadia hears.
Goods Receipt Note generated. Email drafted with the actual quantities received and the one short carton flagged. Customer hears it from you — before they ask. The send is the gate.
Hi Marco — receipt confirmed for ASN-227. 23 of 24 pcs accepted, carton 17 flagged (1 vial short · photo attached). All bins logged · GRN PDF attached. Inventory live on your portal.
Receipt, putaway, label print, bin allocation — all Auto-eligible. Anything that goes to the customer — GRN, dispute notice, exception comm — never auto-sends. Same posture as FreighAi.
Pick by container. Or pick by order.
Sundara's pallets go out container-by-container — don't break units. Cascadia's shipment picks per-SKU from specific bins. Same Binsy. And the pick task only fires because FreighAi booked the JO — the platform-bridge made visible.
Dispatch by container — pallet/box-level pick, don't break units. Driver scans pallet barcode at gate.
- → 8 pallets · barcodes scanned
- → Single AWB · single manifest
- → Gate-out · 6 min
Dispatch by order — pick by SKU/qty from specific bins. Pack-station validates · labels print per piece.
- → Pick from REF-A-12-3 · 12 pcs
- → Pick from REF-A-12-4 · 9 pcs
- → 21 piece-labels · gate-out 11 min
Zero re-keys. The Order Request fires because FreighAi booked the JO. Labels print at booked weight · gate reweigh confirms before manifest leaves the dock.
The receiving flexibility you saw upstream isn't a one-side moat. Outbound flexes too — and both sides talk to FreighAi without re-keys.
Month-end? The cycle ran at 02:00.
Service Catalog defines every WMS service · binds it to a FreighAi charge type · the Monthly Billing Run sweeps everything overnight on the 1st. 45 customer invoices generated automatically. 1 skipped (no activity). 1 failed (manual review flagged). Your accountant's Friday-week is gone.
No month-end scramble.Binsy ran the cycle at 02:00 · 45 customer invoices generated · 1 skipped (no activity) · 1 failed (manual sweep flagged). Cascadia's charges flow into FreighAi as bound charge-types.
Multi-tenant SaaS. Multi-warehouse. Multi-mode.
The flexibility is the moat. The customer's process picks the mode. Binsy adapts; the operator doesn't.
Bound at install. One vendor owns both sides.
Any WMS can integrate with any TMS — that's table stakes. What's not table stakes: a co-designed service taxonomy where every WMS charge already exists as a FreighAi charge type at the data layer. Nothing to reconcile because there's nothing to reconcile across.
- STG-REF-001
- HND-IN-001
- HND-OUT-001
- VAS-QC-001
- VAS-KIT-001
- FRT-STORAGE-REF
- FRT-HNDL-IN
- FRT-HNDL-OUT
- FRT-VAS-QC
- FRT-VAS-KIT
Month-end reconciliation spreadsheet
Double-entry between WMS and accounting
Customer chasing a second invoice from a second entity
One vendor owns both sides. Service taxonomy is co-designed across Binsy + FreighAi at the data layer — not bolted on via reconciliation later.
Running a warehouse and a freight desk?
We pick one customer to start. Configure their receiving mode in the Service Catalog. Bind the charges to FreighAi. By week two their GRN is going out on the right tone under supervised approval — and the month-end billing run will sweep them without anyone touching it.