Overview
Every emission in the Logistics Emissions Calculator must be allocated to at least one organisation using CLIENT_KEY, SUPPLIER_KEY, or both.
CLIENT_KEY — a key, ID, code, or name for the organisation one step downstream of you. The organisation that contracted you to handle the shipment. This is the client you would typically report emissions back to.
SUPPLIER_KEY — a key, ID, code, or name for the organisation one step upstream of you. The organisation you contracted to handle the shipment. This is the supplier whose emissions performance you may want to analyse or compare.
These keys describe the commercial relationship, not necessarily who physically moved the goods. For example, if you contract a freight forwarder who then uses another carrier, your SUPPLIER_KEY should identify the freight forwarder because that is who you contracted directly.
At least one of CLIENT_KEY or SUPPLIER_KEY is required for every emission, whether created through CSV/Excel, the API, or another method. Emissions without either key will be rejected.
You can provide one or both keys, and the same organisation can appear as a client on some emissions and a supplier on others.
Required allocation keys
Your organisation can configure which allocation keys are mandatory when creating emissions:
CLIENT_KEY required
SUPPLIER_KEY required
Both CLIENT_KEY and SUPPLIER_KEY required
This allows the allocation requirements to reflect how your organisation uses the Logistics Emissions Calculator.
For example, an organisation primarily reporting emissions to customers may require CLIENT_KEY, while an organisation analysing its transport suppliers may require SUPPLIER_KEY. Freight forwarders or other intermediaries may require both.
Emissions that do not contain the key or keys required by your organisation's configuration will be rejected.
Your own fleet
If you operate your own fleet, create a key for it and use it as a SUPPLIER_KEY. This allows self-performed shipments to appear alongside externally contracted transport in the same reports and comparisons.
If you both own the goods and perform the transport yourself, the same key can be used as both the CLIENT_KEY and SUPPLIER_KEY.
Keys represent direct relationships
Allocations always describe organisations one step up or down the transport chain.
For example, if a shipper contracts a freight forwarder, who then contracts a carrier:
The shipper's SUPPLIER_KEY identifies the freight forwarder.
The freight forwarder's CLIENT_KEY identifies the shipper and its SUPPLIER_KEY identifies the carrier.
The carrier's CLIENT_KEY identifies the freight forwarder.
Which key should I use?
Ask two questions for each shipment:
Who contracted me? → use CLIENT_KEY
Who did I contract? → use SUPPLIER_KEY
You provide the transport service
Use CLIENT_KEY to identify the organisation you are handling the shipment for.
This applies whether you perform the transport yourself or subcontract it. It allows you to group emissions by client and create client-level emissions reports.
You buy the transport service
Use SUPPLIER_KEY to identify the organisation you contracted.
For example:
A shipment booked directly with a carrier uses that carrier's SUPPLIER_KEY.
A shipment booked with a freight forwarder uses the forwarder's SUPPLIER_KEY, even if they subcontract the transport.
A shipment moved by your own fleet uses the key assigned to your internal fleet.
This lets you analyse total logistics emissions, compare suppliers, and benchmark your own fleet against external providers.
You sit between the client and supplier
If you are a freight forwarder or another intermediary, use both:
CLIENT_KEY for the organisation that contracted you.
SUPPLIER_KEY for the organisation you contracted to perform the transport.
This allows the same emissions data to support both client reporting and supplier performance analysis.
Reporting and analytics
Once emissions are allocated, you can create reports for organisations in your directory and filter, group, or compare emissions using either key.
The platform does not permanently classify an organisation as a client or supplier. Its role is determined by how the organisation is allocated to each emission.
How to provide the keys
CSV/Excel imports: Add a CLIENT_KEY and/or SUPPLIER_KEY column and populate it with the identifier you use for the organisation. See the General CSV/Excel file specification for more information.
API: Provide the relevant key or keys when creating emissions. See the API documentation for implementation details.
Key values are your own identifiers and can use an existing ID, code, or name from your systems.
Important: Do not use personally identifiable information (PII), such as personal names or email addresses, as key values.