Integrations
Connected to the systems you already run.
floDock reads from the outside world and writes back to it, so the visit record is never a silo.
Connected today
Container tracking by sea, joined to your yard bookingERP, finance and TMS
SAP
Oracle
Oracle NetSuite
Microsoft Dynamics 365
How it connects
Four ways in and out.
ERP and TMSSend the closeout of every visit to SAP, Oracle, NetSuite, Dynamics or your TMS, with the times, counts and proof attached.
Webhooks and APIsEvents leave floDock as they happen. Your own systems can read visits, appointments and carriers.
Email and alertsNotices to carriers and your team, drafted, approved and recorded on the visit.
Documents and photosBills of lading, seal photos and inspection images stay attached to the visit and travel with the closeout.Federal carrier register
FMCSA
Authority, insurance, out-of-service orders and fleet facts for every carrier, checked at booking and at the gate.
See carrier checks →Container tracking
SafeCube
Container, bill of lading and booking tracking by sea, joined to your yard booking so the port clock and the yard clock sit together.
See it on the screens →Questions
Straight answers, in full.
What does floDock connect to today?
FMCSA for carrier authority, insurance and out-of-service status, and SafeCube for container tracking. ERP, finance and TMS systems such as SAP, Oracle NetSuite and Microsoft Dynamics 365 connect through the same integration layer.
What if our system is not listed?
Any system that offers an API can be connected. floDock sends events as they happen and your systems can read visits, appointments and carriers.
What goes back to our ERP or TMS?
The closeout of every visit, with the times, counts and proof attached.
Are FMCSA and SafeCube partners of floDock?
No. floDock connects to their systems. Names and logos belong to their respective owners.
Who sets the connection up?
We map your ERP, TMS and carriers to the visit record with you during onboarding.