Why DCSA created a VGM standard

an article by Kristina Jumelet, VGM Standard Owner at DCSA

Verified Gross Mass (VGM) has been mandatory for nearly a decade, yet the way VGM data moves through the container shipping chain still often looks like the early days of digitalisation: emails, spreadsheets, portals, EDI messages, and one-off connections built partner by partner. That mismatch is where delays, rework, and preventable errors keep showing up.DCSA created the VGM Standard to close that gap with a shared, API-based way to exchange VGM declarations across the ecosystem, so the data can travel with the booking, in a consistent format, at the pace operations need.

VGM is your ticket on board, do not leave it behind

VGM is not a standalone compliance checkbox. It is intrinsically linked to booking and execution. Once your booking done, it is crucial to submit critical information to the carriers so that box keeps moving. Without VGM your container can make it to the terminal, but not the vessel.When VGM sits in side channels, every handover becomes a small project:

someone exports data, rekeys it, or maps it into a different template
someone else validates it differently
exceptions move to phone calls and follow-up emails
status becomes hard to track across parties

When VGM is exchanged through a patchwork of EDI messages, emails, and mismatched formats, inconsistencies creep in and communication slows down.A standardised API reduces that friction. It supports faster data transmission, fewer errors, and clearer handovers between shippers, forwarders, terminals, carriers, and intermediaries; whether an organisation produces VGM data, consumes it, or both.One shared model for how VGM moves between partiesThe DCSA VGM Standard is built around how the work actually happens in the network. It defines the exchange of VGM Declarations between parties acting in two generic roles: VGM Producers (the party that measures or collects VGM information) and VGM Consumers (the party that receives it for bookings relevant to their operations).That model deliberately fits the mix of actors involved:

Shippers, consolidators/NVOCCs, terminals and weighing facilities can act as VGM Producers
Carriers, terminals, and intermediaries can act as VGM Consumers
Intermediaries often play both roles as they receive, enrich, and pass data onwards

This is reflected in the standard’s core business processes:

Submitting VGM Declarations from Producer to Consumer
Retrieving VGM Declarations when a Consumer needs the latest data for a booking (optionally filtered by equipment)
Forwarding VGM Declarations when an intermediary receives VGM from one party and provides it to another

Push and pull, so integration fits real operating models

Organisations do not all integrate the same way. Some want near real-time updates. Others want to retrieve on demand, aligned to internal workflows.The VGM Standard supports both:

Push-style submission so VGM can be delivered as soon as it is available, without repeated polling
Pull-style retrieval so a party can request the latest VGM declarations when needed for planning and execution

That flexibility matters because the ecosystem is not a single platform. It is a network of systems, each with different constraints, SLAs, and maturity.

Practical benefits for adopters

For teams implementing and running the process day to day, the gains are concrete:

Lower integration overhead A shared API reduces bespoke mappings and partner-specific build work, especially where VGM currently requires parallel email/EDI processes.
Better data quality and fewer exceptions A structured, machine-readable exchange reduces manual handling and makes validation more consistent across parties.
Clearer handovers across the chain When VGM declarations can be submitted, retrieved, and forwarded in a consistent way, it becomes easier to maintain reliable operational visibility across shipper–forwarder–carrier–terminal interactions.
Faster cycle times Automating exchange reduces the waiting time created by inbox workflows, portal updates, and late corrections.

Open standards, built to be implementable

The DCSA VGM Standard is designed to be straightforward to implement and usable by organisations across the ecosystem. The VGM Standard follows the same approach as other DCSA data-exchange standards: a REST interface with an OpenAPI specification, intended to be within reach of most integration teams and technology partners.

This also matters for inclusivity across the market:
large carriers and digital platforms can integrate directly
shippers and manufacturers with internal IT teams can move quickly
less digitally mature actors (such as inland weighing facilities) can connect through the technology providers they already use

What next for DCSA's VGM Standard?

The VGM Standard is published and accessible to all: teams can integrate directly, and organisations with lighter digital setups can adopt through the technology partners they already rely on.DCSA provides the documentation and adoption materials needed to get started, including the standard specification and implementation guidance.If you’re considering implementing the DCSA VGM Standard, get in touch with DCSA to discuss the best starting point for your setup.