Global end-to-end container import automation and standardization for ocean carriers and their customers
By fully automating import processes, ocean carriers save manual labor time and unnecessary costs. Furthermore, upselling can open up additional revenue channels and increase customer satisfaction.
Flowfox automates and standardizes global import processes such as container releases, container reuses, drop-off changes, drop-off assignments, and C/H instructions.
Forwarders / BCOs
Process automation and real-time feedback and status updates save freight forwarders and BCOs time and money. Containers arrive faster at the BCO and unnecessary disputes and claims with ocean carriers are eliminated.
Cost savings per container for ocean carriers
Cost savings per container for forwarders
Challenges addressed by Flowfox
Manual import processes
Manual processes done by emails produce a high workload, lead to errors as well as result in unnecessary costs, a lot of waiting time and intransparency for the Importing Party and the Ocean Carrier.
Unknown drop-off depots and dates lead to poor equipment control and unnecessary empty repositionings. Additionally, terminals often are not aware of the next mode of transport and the pick-up date before the container discharge, leading to unnecessary costs.
Lack of security
Sensitive data like PINs are transferred via unencrypted emails and can be stolen easily. The current email processes also open up opportunities for attacks through infected PDF files, which in the worst case can lead to a total system failure. Additionally, Ocean Carrier’s employees are at risk of blackmailing if they have access to the PINs.
Local systemic integrations forced by customer demand or regulatory lead to huge implementation efforts and IT resources investments.
Claims and Disputes
Incorrect or late container releases or invoices result in unnecessary disputes on invoices and claims for wasted journeys or plant shutdowns.
Importers are tired of the current import process due to claims, disputes, delays and enormous manpower requirements.
API First: We are not good at shipping containers across oceans but we develop API first and can integrate very quickly and securely with existing systems.
Integrations can be built either via API or also an EDI/email automation based middleware which communicates with our API.
The local container import processes differ slightly to strongly. This is due to a variety of reasons such as regulation, local infrastructure via port community systems or shipping agencies, where simply different processes have been established.
Flowfox does not only support DCSA to develop new standards and use the standards published by DCSA, but we also abstract the local layer, so that especially for shipping company customers a consistent and automated process is created.