Straight answers, in full.

The layer that runs the truck visit from booking to gate-out. One record follows every truck through the gate, yard, dock and exit, on a portal, a tablet and a phone.

A carrier books in the Partner app, or your team books for them. Your rules check the booking and the carrier's authority and insurance. At the gate there is one guided check-in where AI reads the papers and the guard confirms. The dock captures load proof, a clock runs on dwell, and at the exit the trailer, plate and carrier are checked against what arrived.

It checks the person, not just the booking. The truck, carrier and driver are matched to the booking, the driver shows the one-time pass, the carrier is checked against FMCSA records, and the gate keeps photos and time stamps of who came and what left.

Seal, doors open, packing slip, count and the empty trailer, before, during and after loading. Each is photographed on the tablet and saved on the visit, next to the time loading started and finished.

Each site sets free time and rates. floDock counts elapsed units, shows the free units left and the chargeable units, builds a tier table and accrues the total. When the truck gates out the charge is frozen and does not change afterwards.

FMCSA for carrier authority, insurance and out-of-service status, and SafeCube for container tracking, both connected today. ERP and finance systems such as SAP, Oracle NetSuite and Microsoft Dynamics 365 connect through the same integration layer, and any other system that offers an API can be connected as well.

No. Teams use the phones and tablets they already have. Each site sets its own rules without a custom IT project.

Not right now. A short call with our team, then a walkthrough on your own sites, is the fastest way.