The webinar is over, but here is everything that matters.

How to comply with what Amazon, Inditex and your largest clients are already demanding without losing your composure or credibility.

Timeline

• Today: Amazon requires ISO 14083 + GLEC with a contractual deadline.
• 12–18 months: Level 2 mandatory for major retailers (Inditex, Mercadona, Coca-Cola).
• 2030: 4,000+ companies with SBTi must cut Scope 3 by 25% and pass the requirement down to their suppliers.

Who is this webinar for?

• Logistics operators that already report emissions but face growing demands for more detail, more frequency and less room for error.
• Companies with large clients (retailers, distribution) who have public Scope 3 reduction targets and need supplier data to meet them.
• Operators that participate or want to participate in tenders where emissions data is already an award criterion.
• Companies at any point on the ladder: from those with only Level 1 to those with one foot in Level 2 and unsure how to move forward.

The core problem

What holds logistics operators back:

• It is unclear what level each client demands. The first step is not calculating better, it is knowing what you are actually being asked.
• Activity data (weight x kilometers per shipment) is scattered across systems that do not talk to each other, or in the hands of an external provider that does not share it.
• The most painful mistake: using averages instead of weight x distance per shipment can make you report up to 90 times more emissions than real, and Amazon uses those numbers before its committee.
• The organizational problem: Sustainability says it belongs to Operations, Operations says it belongs to Sustainability, IT says it is not their responsibility. While nobody owns it, the client keeps waiting.
• When the client raises the bar, the number you used to give is no longer valid, and that conversation is very difficult.

The three levels of demand

Level 1: Total corporate footprint. Calculation of total company emissions (Scope 1, 2 and part of 3). GHG Protocol methodology, annual reporting, aggregated data. Required by sustainability reports, EcoVadis, CDP. The problem: the client does not know how much belongs to them.

Level 2: Emissions per client or per service. The client wants to know what share belongs to them, not your total. By transport mode, by route, by shipment type. Methodology: GLEC / ISO 14083. Required by Inditex, Mercadona, Coca-Cola, major retailers. Common mistake: dividing total footprint among shipments, works until the client raises the bar.

Level 3: Emissions per individual shipment + periodic reporting. Footprint per individual shipment. Monthly reporting. Contractually required methodology: ISO 14083 + GLEC Framework 3.0. Amazon sets it contractually with a start date. This is where Amazon is today. And where the market is headed.

Three questions that reveal where the gap is

Question 1: Do you know what level each client is asking for? Not the general level, the actual level, client by client. Most companies have not mapped this. The first step is not calculating better, it is knowing exactly what you are being asked and what you will be asked in 6 months.

Question 2: Is your activity data available? In plain terms: can you tell how much each shipment weighs and how many kilometers it travels? If that data does not exist or is scattered, that is the real bottleneck, even before methodology.

Question 3: Who manages this internally? The most frequent problem is not technical, it is organizational. While nobody has it assigned, the client keeps waiting.

Dcycle's differential value for logistics

• Correct calculation from the source: footprint per individual shipment using GLEC 3.0, the data Amazon needs, traceable, methodology-backed, not an estimate divided from the monthly total.
• Real-time AI: ask directly "what are my emissions for Amazon this month?" or "what do I need to do to reduce by 20%?" without exporting to Excel, without waiting for a report.
• The contrast that changes everything: the correctly calculated figure versus the rough estimate can differ by a factor of 10, 50 or up to 90. That is what is at stake with methodology.
• Full traceability: every number has its origin, its weight, its distance, its emission factor; the client sees everything in one place.
• Subcontracted fleet management: ISO 14083/GLEC covers it; the system manages subcontractor data or applies documented proxy factors.

The key mindset shift

It is not about reporting. It is about capturing data correctly from the source: the actual weight of the shipment, the actual kilometers traveled. Because you will need that same data for Amazon, for Inditex, for the next RFP and for the auditor.

A poorly calculated number is not a technical error. It is a credibility crisis with your client.