Project44

project44, through its Movement platform, is the multimodal visibility network that returns live location and predictive ETA for FTL, LTL, ocean, air, rail and parcel. Every shipment your team confirms is tracked without manual enrollment, and exceptions reach the right person before the customer calls. The head of customer service or transport usually switches it on; IT registers the client application in your Movement tenant.

What teams use it for

Enroll each shipment when it is confirmed

When a load is confirmed in Load Hub, a digital worker initializes tracking in project44: FTL by truck and driver, ocean by container or vessel, parcel by tracking number, rail by enrollment. The coordinator sees the shipment tracking in Tracking without entering the truck, container or tracking number in Movement. Cancelled loads are cancelled in project44 too.

Ocean, truck and parcel on one timeline

A container clears the port at Long Beach and the drayage leg starts. project44 pushes the status change to Cargofy by webhook, in a payload that mirrors the tracking history response. Cargofy writes it to the order's timeline in Tracking, under the ocean leg that just closed. When the parcel to the end buyer is scanned, the timeline gets a third leg. When the customer emails, the customer service rep reads the current position and predictive ETA across all legs next to the customer thread.

Act on ETA drift before the appointment slips

A truck from Atlanta to Charlotte slows in traffic, and project44's predictive ETA moves past the delivery appointment on the load. The digital worker compares the two, opens an exception on the shipment in Tracking and assigns it to the transport planner. The planner sees the new ETA beside the appointment and either rebooks the dock slot or warns the receiver from the same screen. The exception and the customer update stay on the shipment.

Hold a reefer load to its temperature

A reefer load from Atlanta to Miami reports trailer temperature through project44, and Cargofy reads the readings onto the shipment in Tracking. When a reading crosses the threshold set on the load, the digital worker opens an exception, notifies the customer service rep and logs the reading. The rep can call the carrier while the product can still be saved, and the log answers the claim question later.

Quote and book LTL from the same load

Where LTL rating and booking are enabled in your Movement tenant, an LTL order released into Load Hub can be priced in Sales from the quotes project44 returns for the lane. The planner picks a carrier and books it from Load Hub, and Cargofy writes the booking through project44. The booked shipment then tracks like any other in Tracking. The eBOL and related documents are found through document search and filed in Documents against the load.

How it fits your stack

Your TMS or Load Hub stays the record for the load; project44 stays the record for the carrier network. Cargofy reads location, status, tracking history, ETA, temperature and documents, and writes tracking initializations, updates and cancellations, plus LTL quotes and bookings where enabled. Setup is per installation: your admin registers a client application in your Movement tenant with OAuth 2.0 client credentials. Cargofy does not manage carrier connections inside project44, and YMS appointments and port intelligence are not part of the base tracking connection.

Who it is for

Shippers with an existing project44 subscription moving freight across several modes. Customer service watches Tracking, transport planners enroll shipments and clear exceptions, and the IT admin owns the client application. Brokers and 3PLs on Movement get the same timeline for the loads they run.