This article covers the file format used by Pledge to import externally calculated emissions data pertaining to shipment-level freight. This allows for the inclusion of emissions provided by suppliers, even when detailed shipment activity data is unavailable, enabling users to maintain a comprehensive view of their transport emissions inventory.

Before diving into the freight-specific fields, you are encouraged to first familiarise yourself with Pledge's general CSV/Excel file specification for importing data.

Pledge supports the import of externally calculated freight emissions data. Unlike emissions calculated by Pledge, which describe end-to-end multi-modal movements of freight—including pre-carriage, main carriage, port-to-port, and on-carriage movements—externally calculated emissions are imported at the shipment level with minimal required data, ensuring compatibility while recognising the limitations of third-party data.

Each shipment of cargo is represented as one line in the file, where pre-calculated CO₂e values are provided without requiring full shipment breakdown

For each shipment of cargo, the shipment must have a unique identifier (provided by you) in the SHIPMENT_ID field.

If shipment details such as weight, routing, or vehicle type are not provided, Pledge will mark the data source as "Undisclosed" to indicate that only emissions totals were supplied without detailed methodology.

When importing third-party calculated freight emissions, some shipment details may be incomplete. Pledge ensures transparency by handling missing data as follows:

You can find an empty template and other relevant sample files in our public repository.

Fields marked with a ✅ are mandatory.

​