How to utilize events
The most important events typically used by business users are around containers arriving at the destination port and at the inland destination ramp (if the container goes on rail at the inland destination). It is first best to consult your internal team on how you want to utilize the events.
Prior to having the cargo "available for pickup" at a port or rail ramp, both freight and customs have to be "released". A container will typically have certain amount of days (Last Free Day) of "free storage" before being charged a fee (Demurrage). A port provides up to 5 business days, and rail ramp provides 48 hours. Hence, buisness users usually need to get an estimate of when a container will arrive and be discharged at a port or rail ramp. The following four events help business users plan better for getting cargo released:
| Important events for cargo "release" workflows | Code |
|---|---|
| Estimated container discharge at destination port | ECDD |
| Container discharge at destination port | CDD |
| Estimated container discharge at destination port | ECDD |
| Container discharge at destination port | CDD |
| Estimated container arrival at inland ramp | ECAR |
| Container arrival at inland ramp | CAR |
| Estimated container arrival at inland destination | ECAD |
| Container arrival at inland destination | CAD |
Other important events are around the container departure from the origin port. These events help business users plan for the container's arrival at the destination port:
| Important events for around container departure from origin | Code |
|---|---|
| Estimated container arrival at origin port (first POL) - Gate in | ECGI |
| Estimated Vessel departure from origin port | EVDL |
| Vessel departure from origin port | VDL |
CAR vs CAD events
If the final inland destination is a rail ramp, then in most scenarios the "CAD" event and "CAR" event may be exactly the same. The scenarios where it won't be the same are:
- If the BOL has multiple containers, and one of the containers has arrived at the rail ramp, but the other containers have not yet arrived. Then the "CAR" event will be generated for the container that has arrived, but the "CAD" event will not be generated until all containers have arrived.
- Some sealines do not provide the "CAR" event for a container, but they may provide an overal BOL-level arrival (and estimated arrival) event. particularly for YangMing when there are multiple containers on a BOL, we do not get the "CAR" event for the containers, but they instead provide a "CAD" event on the BOL level. In that case, the "CAD" event is generated for the container and can be used as the "CAR" event if users know the final destination is a rail ramp.
Resources: