bbTRUCKLoading…
Skip to content
bbTRUCK logistics platform on a laptop and mobile phone

VeraTrace:
Freight Carbon Data
Scope 3 Estimates

Turn order and transport records into data for emissions estimates and Scope 3 reporting.

The Compliance Challenge

The Scope 3 Bottleneck: Top-Down Allocation vs. Order-Level Reality

An hourglass representing delayed annual accounting

THE TRAP

Top-Down Allocation (ISO 14064-1)

Annual organizational accounting manually split across orders. Delayed, inaccurate, and fails to capture real reduction efforts like dynamic routing.

Bottom-up primary data collection

DATA ORGANIZATION: VERATRACE

Start with Shipment and Transport Activity Data

Organizes available shipment, route, weight, and transport records to support order-level emissions estimates and Scope 3 data preparation. Data completeness and method applicability must be confirmed for each project.

Core Features of VeraTrace API

Order-Level|Transport Data

Organizes available order, route, weight, and transport records as inputs for shipment-level estimates.

Method Frameworks|by Intended Use

Prepare relevant data for transport-chain quantification under ISO 14083 or product carbon footprint work under ISO 14067.

Route and Payload|Data Context

Estimates use available route, cargo-weight, and transport-event data; gaps need to be addressed or reviewed.

Integration Planning

Assess ERP/WMS API connection options, fields, and data exchange scope during implementation planning.

METHODS AND DATA SCOPE

Calculation and Data Frameworks by Purpose

Actual data sources and verification scope are confirmed for each implementation.

bbTRUCK freight carbon data and method framework illustration

The illustration includes historical transport-service verification for BB TRUCK INC., covering 2023-05-01 to 2024-04-30. Current project periods, scope and evidence must be confirmed separately.

  • ISO 14083 is for transport-chain emissions quantification and reporting; transport models and data boundaries depend on the applicable use case.
  • ISO 14067 is for product carbon footprints; including transport results in a product footprint requires confirmation of life-cycle boundaries and allocation.
  • Organized transport data can support preparation of Scope 3 or related disclosures; it does not establish compliance with CBAM, CSRD, or other laws.
  • Route distance, weight, vehicle, factors, and GPS availability affect estimates. Missing data, substitute sources, and coverage must be confirmed for each project.
  • Calculated results are not third-party verification, product certification, a carbon-neutrality claim, or a legal compliance conclusion. Any required verification must be confirmed separately.

VeraTrace Frequently Asked Questions

What is VeraTrace?

VeraTrace is bbTRUCK’s freight carbon data service. It organizes shipment and transport activity data to support order-level emissions estimates and Scope 3 data preparation. Features, fields, and outputs are confirmed for each implementation.

What data sources are used for freight emissions estimates?

Inputs may include shipment records, cargo weight, vehicle or factor settings, route distance, and transport events. Complete GPS traces may be used where applicable. Sources depend on the shipment, system configuration, and data available.

What happens when GPS traces or shipment weights are missing?

An estimate may be unavailable or may require an agreed alternative source when required weight, distance, or route data is missing. Missing values should not be treated as measured results. Data-gap labels, follow-up, and handling are confirmed during implementation.

How do ISO 14083 and ISO 14067 differ?

ISO 14083 addresses quantification and reporting of greenhouse gas emissions from transport chains; ISO 14067 addresses the carbon footprint of products. Their purposes and boundaries differ, so the method should match the reporting purpose. Using a framework does not mean a report is certified or verified.

How is VeraTrace implemented and connected to an ERP or WMS?

Implementation planning can map ERP/WMS order fields, data sources, exchange methods, and update frequency before confirming API or other integration scope. Available endpoints, fields, and timing depend on both systems and project requirements.

What is included in the carbon data, and is it third-party verified?

Transport estimates depend on shipment, route, weight, vehicle, factor, and method data. Whether platforms, data transfer, or other emissions are included must be confirmed separately. Results can support audit preparation, but boundaries, evidence, and any third-party verification require project-specific confirmation. This page is not a legal compliance guarantee.