Forwarding Event and Milestone management
Events and milestones track the planned and actual progress of shipments and related transport activities. They provide operational dates for processes such as communication, invoicing and exception follow-up.
Templates and operational dates
Configure the event/milestone templates for the order type and mode of transport. These determine which milestones are created for the document. Keep the codes and date sources consistent with the voyage and section workflows that update them.
Review estimated, updated and actual dates separately. A changed ETA is a planning update, not confirmation of an actual arrival.
ETA Communicator
The ETA Communicator work brings voyage date updates together with events and milestones so linked forwarding documents can reflect changes in the sailing. This reduces the need to re-enter the same operational dates on every shipment.
Configure the voyage/call relationships and the event/milestone mappings used by your implementation. Test a changed arrival/departure date on a linked shipment and check the resulting milestone dates before using them for customer communication or billing.
Communication requires the appropriate recipient and handling setup. Updating an event date alone should not be treated as proof that a notification was delivered.