Empowering data quality with GraphTP

Dockflow offers several import methods, depending on your scale. For one-off shipments, you enter the data directly in the platform. For bulk imports, Dockflow provides an Excel template: add an internal reference plus a container number, booking reference or bill of lading, and Dockflow fills in the rest. For full automation, the Dockflow API connects your own systems directly. The steps are in the Dockflow knowledge base.

Yes. Dockflow supports full data export in Excel format. The shipment details, event histories and container insights available in the platform can be downloaded to Excel for further analysis, your own reporting or offline recordkeeping. That keeps the data accessible for operational teams and for external stakeholders who don’t work in Dockflow.

Dockflow cross-references each container’s events across sources before they reach your team. For a vessel arrival, for example, carrier data, terminal data and AIS vessel positions are compared: AIS vessel positions confirm vessel departures and arrivals, and terminal data corrects carrier data that is out of date. GraphTP, Dockflow’s data-conflict-resolution algorithm, resolves the conflicts that remain.

Dockflow tracks containers across 120+ ocean carriers, including long-tail lines. Carrier data is combined with AIS vessel positions, terminal data and Portbase; in Antwerp, release status comes from NxtPort Certified Pickup and T-Mining. TrakAssure and LoRaWAN IoT sensors add reefer temperature. Your own shipment data comes in through the Excel import or the Dockflow API, so everything sits in one platform.

Yes. When two sources report the same milestone with different times, GraphTP, Dockflow’s data-conflict-resolution algorithm, compares them and resolves the conflict. GraphTP also scores every tradeflow for data anomalies and flags milestones that contradict each other, such as events out of order or a carrier and terminal that disagree. Your team sees one status per milestone on the container’s timeline, instead of two conflicting updates to check by hand. More on container visibility.

Each milestone on a container’s timeline shows where its confirmation came from, such as port data or the carrier. Accuracy comes from checking sources against each other: AIS vessel positions confirm vessel departures and arrivals, and terminal data corrects carrier data that is out of date. Every milestone is time-stamped and kept in the container’s history, so you can look back at what happened and when.

Data quality directly affects timing, coordination, cost and customer satisfaction. Poor data leads to missed handoffs, inaccurate ETAs, surprise delays and more email and manual follow-up. With Dockflow, decisions such as planning a pick-up, scheduling a warehouse slot or informing a consignee rest on data that is always up to date, with free-time monitoring and alerts before charges hit.

RealCalc calculates CO2 on the GLEC framework, using the actual routes sailed. The same AIS vessel positions that confirm departures and arrivals give RealCalc the track the vessel actually sailed, so the emissions figure follows each shipment’s real route instead of a planned one. More on CO2 emissions.

Bad data often leads to delayed handovers, missed appointment slots and uninformed stakeholders. Dockflow checks sources against each other before an event reaches your workflows. If a carrier has not yet reported a vessel departure, AIS vessel positions can confirm it, so your plans follow what actually happened. No-code automations flag exceptions, so your team can act before a delay spreads.

Dockflow acts as a shared source of truth for the parties on a shipment: forwarders, consignees, customs brokers and warehouses. Through the white-label customer portal, under the forwarder’s brand, clients see the same milestones your team sees. Upload documents such as bills of lading to a shipment and share them with the partners on it, so nobody works from an older update.