Skip to main content

Duplicate and versioning shipment's emissions

Control how duplicate shipment's emissions are managed in your inventory.

Updated over a week ago

Overview

Auto-versioning lets you decide whether duplicate shipments (with the same shipment_id metadata) related emissions are saved as new versions or blocked as errors.

Auto-versioning enabled

When enabled:

  • Duplicate shipment's emissions are automatically stored as a new version of the existing emissions.

  • Each version is sequentially numbered, allowing you to track changes over time.

Example

If a shipment record includes shipment_id = 1234 and is sent again with updated details, the related emission will be stored as a new version of the existing emissions.

Auto-versioning disabled

When disabled:

  • Duplicate shipment's emissions with the same shipment_id trigger an error.

  • The duplicate is not saved in the inventory.

  • You must use a unique shipment_id (in metadata) or update/remove the duplicate record before uploading again.

How to enable or disable

You can configure auto-versioning either through the app or API:

  • Enable via API: Set the auto_versioning flag to true in your API request in the Emissions API (see API reference guide) or Configuration API (see API reference guide).

  • Enable via app settings: Set the global configuration in your organisation settings here.

Did this answer your question?