Scope 3 Freight Emissions

freya by TetriXX AI produces a CO₂e figure alongside the cost on the shipments it verifies, calculated to the GLEC Framework from the same verified line-level data, not from a spend-based estimate.

Invoice and shipment data already carry most of what the calculation needs: mode, distance, weight, often the carrier’s equipment detail. Where a shipment does not carry the volumetric detail GLEC requires, the gap is reported rather than estimated over. Emissions are a property of the audit rather than a separate product, and the baseline is one of the calibration deliverables.

Yes, for the transport part of it, which is usually the part hardest to defend. Freight falls in Scope 3 categories 4 and 9 of the GHG Protocol, upstream and downstream transportation and distribution, and it is the category most often reported from spend-based estimates, because the primary data sits scattered across carriers and forwarders rather than in any one system.

freya by TetriXX AI reports it from primary data instead. The CO₂e figure comes off the same verified invoice line as the cost, calculated to the GLEC Framework, so the emissions number and the financial number reconcile to the same shipment. Where a shipment lacks the detail GLEC requires, the gap is reported rather than estimated over, which is the difference between a figure an auditor can trace to a document and one they cannot.

What a sustainability team gets is a freight baseline built on evidence finance has already accepted. What finance gets is a carbon figure it does not have to commission separately. freya covers the freight you are invoiced for; it is not a whole-inventory carbon accounting platform, and the emissions work stops where the freight does.

For a calibration on your own data: details for one or two logistics providers (modalities, trade lanes, rate cards), and two to three months of invoices. That is enough to establish both the error profile and whether your invoice data supports continuous verification at all.

From a freya by TetriXX AI calibration you receive an integrated dashboard with your structured data fully accessible, a detailed calibration report with findings, recommendations and identified opportunities, and a GLEC-based CO₂e emissions baseline across the shipments whose data supports it. It runs under a signed NDA.

No. Messy data is the normal starting condition and handling it is most of the work: invoices as PDFs and scans that differ by provider and country, rate cards in inboxes.

What blocks an audit is missing data: an invoice that never carries the fields needed to match it to a contract. Which of the two you have is what a calibration establishes, before you sign anything.

Yes, REST endpoints and MCP servers, in addition to the platform UI and emailed intelligence reports. Teams that want to query verified freight data from their own tools or AI agents can do so directly.

The UI is one surface, not the product.

You do, and you can take it with you. The data in your environment is yours, it is exportable in full at any time, in structured form, and there is no lock-in mechanism holding it inside the platform.

This matters more in this category than in most software: the asset being created is verified line-level freight data, and a vendor that makes it hard to leave with is charging you twice.