# Shipment details

> The shipment details page gathers everything Safecube knows about one shipment, its origin, destination, ETA, status, event timeline, vessel route, containers, teams and custom data, and the actions to share, archive or delete it.

The shipment details page opens when a shipment is selected in the [shipment list](/en/platform/shipment-views/shipment-list), the [Kanban](/en/platform/shipment-views/kanban), the [Calendar](/en/platform/shipment-views/calendar) or the search. It shows the data Safecube retrieved from the carrier for that shipment: its origin and destination, its dates and status, its event timeline, the route of the vessel, the containers of a bill of lading or booking, and the custom data of the workspace. The **Documents** block and the **Alerts timeline** section of the page are described in [Documents](/en/platform/workspace/documents) and [Alerts page](/en/platform/alerts/alerts-page).

## Who can act on a shipment

| Gesture | Minimum role |
| ------- | ------------ |
| Open the shipment details page, view the map | Viewer |
| Share the shipment | Viewer |
| Add the shipment to teams | Editor |
| Edit the additional data | Editor |
| Archive the shipment | Editor |
| Open the settings of a team from its name | Admin |
| Delete the shipment permanently | Admin |

## Header and shipment menu

The top of the page shows the type and the number of the shipment, for example "CT : MSCU1234566", the carrier, and the first two teams the shipment belongs to. When it belongs to more teams, a **+N** label opens the full list. An Admin opens the settings of a team by selecting its name.

A warning icon next to the number means the last update from the carrier failed; its tooltip gives the reason, as described in [Update frequency](/en/platform/container-tracking/update-frequency).

The **More options** button, on the right, opens the shipment menu. Each entry only appears for the roles allowed to use it:

- **Share shipment** creates a public link to the shipment, described in [Sharing and export](/en/platform/container-tracking/sharing-and-export);
- **Add team(s)** adds the shipment to teams, described in "Add the shipment to teams" on this page;
- **Archive shipment** moves the shipment to the Archives, described in [Shipment archiving](/en/platform/container-tracking/shipment-archiving);
- **Delete shipment** deletes the shipment and its data permanently.

## Origin, destination and status

The first card summarises the journey:

- **Origin**: the port of loading (POL) and, once the vessel has left, "Departed" with the departure date;
- the number of days left before arrival, and the status of the shipment, described in [Shipping statuses](/en/platform/container-tracking/shipping-statuses);
- **Destination**: the port of discharge (POD) and its ETA;
- a progress bar between departure and arrival.

Below, four tiles give the **ETA** (estimated time of arrival at the POD), the **ETD** (estimated time of departure from the POL), the **Vessel** of the latest event that names one, and the number of **Containers** with their size and type. A value the carrier did not share shows "-".

![Shipment details page of container MSCU1234567 in transit from Shanghai to Rotterdam, with the 2d Late status, the ETA, ETD, Vessel and Containers tiles, and the first three events of the event timeline](https://docs.safecube.ai/media/images/shared/shipment-details--in-transit.webp?v=7684cc9f)

## Read the event timeline

The **Event timeline** table lists the events shared by the carrier, with four columns: **Date**, **Description**, **Location** and **Vessel**.

- Three events are shown at first. **Show more** displays the others, **Hide** folds them again.
- An event whose date is still in the future is highlighted with a blue border and a tinted background. Past events have no highlight.
- When the carrier shares no event, the table reads "No results found".

![Shipment details page of bill of lading CMDU3456789, delivered from Shanghai to Felixstowe, with the Delivered status, its past events in the event timeline and its two containers](https://docs.safecube.ai/media/images/shared/shipment-details--delivered.webp?v=13b5bfa3)

## View the vessel route on a map

**View map**, next to the event timeline, opens a map of the shipment route:

- the grey line is the part of the route already covered;
- the blue line is the part still to come;
- a red line joins two points of the route between which the carrier gave no location; hovering it shows "Missing locations on this leg";
- the vessel icon is coloured according to the delay of the shipment: green on time, blue early, orange late, grey when the delay is unknown.

Hovering a port shows its name and its UN/LOCODE. Selecting the vessel opens its details: **IMO**, **MMSI**, **Call sign**, **Vessel type**, **ETA captain**, **Speed** and **Last position received**. When the route holds no position for the vessel, a label reads "Retrieving the vessel position…" and then "Vessel position" with the date of the position found.

![Map of a shipment route from Shanghai to northern Europe: the grey line covers the leg already sailed to Singapore, the orange vessel icon marks a late vessel near Singapore, and the blue line continues through the Suez Canal to the destination](https://docs.safecube.ai/media/images/shared/modal-shipment-map--default.webp?v=1ab5b873)

## Containers of a bill of lading or booking

When the shipment is a bill of lading or a booking holding several containers, the **Containers** section lists them with their **Container number**, **Last event**, **Location**, **Last date** and **Status**. The status of a container's last event is **Estimated**, **Planned** or **Actual**. Three containers are shown at first, **Show more** displays the others.

## Edit the additional data

The **Additional data** section shows the custom fields of the workspace and their value for the shipment, including the Kanban column. A field without value shows "-".

1. Select a value to edit that field only, or select **Edit** to edit every field of the section.
2. Type the new value. The Kanban column is chosen from a list.
3. Press Enter, or select outside the field, to save.

Editing requires the Editor role: the change of a Viewer is refused. Custom fields are created in Settings, by an Admin.

## Add the shipment to teams

1. Open **More options**, then **Add team(s)**.
2. In **Add teams to shipment**, choose one or more teams in **Access teams**.
3. Select **Add teams**.

The teams appear in the header. An Admin also sees **Team management**, which opens the team settings. Teams are described in [Teams](/en/platform/workspace/teams).

## Last updated

At the bottom of the page, "Last updated:" gives the date and time, in UTC, of the last update of the shipment data. The page does not refresh by itself, and has no refresh button: reload it to see newer data. How Safecube updates shipments is described in [Update frequency](/en/platform/container-tracking/update-frequency).

## Limits

- The shipment details page does not show the history of ETA changes; the difference between the first announced ETA and the final ETA is shown for archived shipments only, in the Archives.
- Which part of the map route is covered or to come is set by the route data, not by the dates of the event timeline: the two can differ.
- A shipment that Safecube is still identifying, or that is blocked, shows a progress checklist or a card explaining the cause instead of its data, as described in [Tracking issues](/en/platform/container-tracking/tracking-issues).
