---
title: "INTERMODAL — Weight Fields on Bookings: Tare, Cargo & VGM — What, Why & How."
description: "Three weight fields on the intermodal booking - Tare weight, Cargo weight, and VGM - with auto-calculation, override support, rate card metrics, and dispatch to ferry and rail partners."
url: https://help.qargo.com/en/articles/676455-intermodal-weight-fields-on-bookings-tare-cargo-vgm-what-why-how
locale: en
updated: 2026-05-20
---

# INTERMODAL — Weight Fields on Bookings: Tare, Cargo & VGM — What, Why & How.

## Summary {#h_99d7fde1d3}

-   **What is this feature?**

    -   Three new first-class fields on every intermodal booking: _Tare weight_, _Cargo weight_, and _VGM_ (Verified Gross Mass). VGM is auto-calculated as Tare + Cargo, with the option to override the value manually. The same three values are available as cost-side rate metrics and are included in outbound booking dispatch to supported ferry and rail partners.
-   **Why does it matter?**

    -   SOLAS regulations require VGM on every loaded container shipped by sea, and modern intermodal booking messages (c-web, EDIGES) expect _tare_, _cargo_, and _VGM_ as separate fields. Without dedicated fields, weight data was never visible to planners or customer service - which blocked SOLAS-compliant ferry bookings, broke rail integrations that required the values up front, and prevented weight-based pricing for tank intermodal customers.
-   **How does it work?**

    -   When an intermodal booking is created or updated, _Tare weight_ is read from the resource (container or vehicle), _Cargo weight_ is the sum of goods weight across all linked orders, and _VGM_ is calculated as Tare + Cargo. The values are visible on the intermodal booking list and on the intermodal leg hover card, can be used in cost-side rate calculations, and are sent automatically in supported outbound integrations.

## Prerequisites {#h_2c78a6ff45}

-   A _Tare weight_ must be set on the relevant resource (container, trailer, or vehicle) for the auto-calculation to populate correctly. Bookings on resources without a tare weight will show a blank or zero value for _Tare weight_ and _VGM_ until the resource is updated.
-   Goods on the orders linked to the intermodal booking must have a _weight_ set so that _Cargo weight_ can be summed.

    -   Uses _actual loaded weight_ when available and falls back to _ordered weight_ so the value is populated for planning, not only after loading.
-   For the values to flow into outbound bookings, the relevant integration must already be configured (c-web for CLdN, P&O, SeaTruck, or EDIGES).

## Use Cases {#h_7a44b32ccd}

-   **SOLAS-compliant ferry dispatch**: ferry operators require VGM to be transmitted with every loaded container booking. With Tare, Cargo, and VGM as separate fields on the booking, dispatch payloads to c-web (CLdN), P&O, and SeaTruck now carry the values directly instead of being reverse-engineered, which removes a category of booking rejections caused by missing or incorrect weight data.
-   **EDIGES rail bookings**: rail operators using EDIGES expect _VGM_, _cargo weight_, and _tare weight_ in the booking payload. The new fields are populated automatically and included in outbound EDIGES messages, removing the need to complete bookings manually in partner portals.
-   **Tank intermodal pricing**: liquid bulk operators price by _tank tare + goods weight_, where the tare differs per tank. With _tare weight_, _cargo weight_, and _VGM_ available as cost-side rate metrics, these pricing rules can be configured directly in Qargo instead of being maintained outside the system.
-   **Customer service visibility before dispatch**: planners and customer service teams can now add the three weight columns to the intermodal booking list and the values are visible on the intermodal leg hover card, making it possible to spot bookings with missing or zero weight data before they are sent to the operator.

## Terminology {#h_b8fb8002f5}

| **Term** | **Definition** |
| --- | --- |
| _Tare weight_ | The empty weight of the container, trailer, or vehicle assigned to the booking. Read from the resource record. |
| _Cargo weight_ | The total weight of the goods on the orders linked to the intermodal booking. Calculated from actual loaded weight where available, otherwise from ordered weight. |
| _VGM (Verified Gross Mass)_ | The verified total weight of a loaded container: Tare weight + Cargo weight. Required by SOLAS regulations for vessel loading on ferry connections. |
| _Intermodal booking_ | The booking record that represents the intermodal leg of a transport - typically a ferry or rail movement managed by an external operator. |
| _EDIGES_ | A standardised electronic booking message format used by several European rail operators (Hupac, Kombiverkehr, Samskip, Novatrans, T3M, Mercitalia). |
| _c-web_ | The booking integration used by CLdN for ferry bookings. |

* * *

## Visualising the New Fields {#h_f601b96e71}

### On the intermodal booking {#h_6469ecefda}

The three new fields appear on every intermodal booking. They are populated automatically when the booking is created or updated:

1.  **OPEN** the intermodal booking from _Planning → Container booking_, or from the intermodal leg on an order.
2.  **VIEW** the Tare weight, Cargo weight, and VGM values in the booking detail panel. _Tare weight_ is read from the assigned resource, _Cargo weight_ is the sum of goods weight across the orders on the booking, and _VGM_ is calculated as Tare + Cargo.
3.  **OVERRIDE** the VGM value manually if the actual weighed VGM differs from the calculated value (for example, after physical weighing at a port). The override is preserved even if the underlying tare or cargo values change later.

![](https://help.qargo.com/media/66316a22bd70-image.png)

:::callout{tone="note"}
🧰 The auto-calculation depends on a **Tare weight being configured on the resource and goods weight being set on the orders**. Bookings on resources without a tare weight will show blank or zero values until the resource record is updated.
:::

### On the intermodal booking list {#h_bcea0398db}

The three values are shown as columns on the intermodal booking list

![](https://help.qargo.com/media/bdc92bb38ba7-image.png)

:::callout{tone="info"}
**📚 The columns are visible but not filterable or sortable.**
:::

### On the intermodal leg hover card {#h_7a358c78f2}

The same three values are displayed on the intermodal leg hover card that appears when hovering an intermodal leg on the order table. This makes the values visible without opening the booking itself.

* * *

## Cost-Side Rate Metrics {#h_a8b5fdfec9}

The three values are available as metrics in **_cost-side rate calculations_**, alongside the existing weight and dimension metrics.

### Available metrics {#h_ffc2c0e9f5}

Three new metrics are exposed in the metric picker on cost-side price-table dimensions and formula calculations:

-   _Tare weight_ - the tare value from the booking.
-   _Cargo weight_ - the summed goods weight from the booking.
-   _Verified gross mass_ - the VGM value (auto-calculated or overridden) from the booking.

These can be used to configure brackets (for example, up to 8t / up to 36.5t for VGM) or to drive formula-based cost calculations. The flow for adding the new metrics is identical to the existing weight metrics already used in cost rate cards.

::video{src="/media/video/2d5eda67c8ee-2026-05-20_15-50-34--1-.mp4"}

:::callout{tone="note"}
📚 Three new metrics available on **cost-side** rate cards only.
:::

* * *

## Outbound Integration Dispatch {#h_5d501d0767}

When an intermodal booking is dispatched to a supported partner, the three new fields are included in outbound updates automatically.

### Supported integrations {#h_da0ff6f665}

-   **c-web (CLdN)**: maps directly to the existing `<tareWeight>`, `<cargoWeight>`, and `<vgm>` elements in the c-web booking message.
-   **P&O**: the three fields are included in the booking dispatch payload.
-   **SeaTruck**: the _Cargo weight_ field is used directly.
-   **EDIGES**: the three fields are included in the EDIGES booking payload mappings.

:::callout{tone="info"}
🧰 No additional configuration is required for these integrations to start using the new fields once the integration itself is set up. The fields are populated and dispatched automatically.
:::

### External API {#h_a4ca231484}

Three new optional, read-only fields are exposed on `BookingDimensions` in the External API:

-   `BookingDimensions.tare_weight`
-   `BookingDimensions.cargo_weight`
-   `BookingDimensions.verified_gross_mass`

These are populated by Qargo's calculation and are not accepted as input.

* * *

## Troubleshooting {#h_63553ae598}

| **Issue** | **What to check** |
| --- | --- |
| Tare weight is blank or zero on the booking | Confirm that the resource (container, trailer, or vehicle) assigned to the booking has a _Tare weight_ configured on the resource record. The booking reads this value directly from the resource. |
| Cargo weight is blank or zero | Confirm that the goods on the orders linked to the booking have a _weight_ set. The system uses actual loaded weight when available and falls back to ordered weight - if neither is populated, the cargo weight cannot be summed. |
| VGM does not match the expected value after editing goods or resource | If the VGM was manually overridden, it does not recalculate when the underlying values change. The manual-override indicator on the VGM cell signals this state. Clearing the override allows the value to recalculate. |
| Tare / Cargo / VGM columns not visible on the booking list | The columns are not visible by default. Open _Edit columns_ on the intermodal booking list and enable them per saved view. |
| Sorting or filtering on the new columns has no effect | Filtering and sorting on Tare weight, Cargo weight, and VGM are not available in v1. The columns are visible-only at this stage. |
| Outbound booking still missing weight data at the partner | Confirm that the booking has tare and cargo populated in Qargo (see the checks above), and that the partner integration in use is one of the supported integrations listed in _Outbound Integration Dispatch_. |


## Related articles

- [INTERMODAL -  Manifest Generation: What, Why & How.](https://help.qargo.com/en/articles/567377-intermodal-manifest-generation-what-why-how.md)
- [RESOURCES — Container Standard Sizes — Overview](https://help.qargo.com/en/articles/681835-resources-container-standard-sizes-overview.md)
- [INTERMODAL - Intermodal planning](https://help.qargo.com/en/articles/133848-intermodal-intermodal-planning.md)
- [RATE CARD - Multimodal pricing condition configurations](https://help.qargo.com/en/articles/669575-rate-card-multimodal-pricing-condition-configurations.md)
- [INTERMODAL — Intermodal Departures Column on the Orders List — What, Why & How](https://help.qargo.com/en/articles/654005-intermodal-intermodal-departures-column-on-the-orders-list-what-why-how.md)
