Transport Emissions Evidence Platform

Evidence-backed transport emissions reporting for teams that need more than a PDF

Import shipment data, review evidence and data quality, and publish repeatable transport emissions packs your team can reuse across reporting cycles.

ISO 14083:2023 / GLEC v3.2 aligned · PDF, XLSX, JSON · EU-hosted

See Sample Evidence Pack Start Free in Lite

Book a Demo for Enterprise

Reusable workspaces

Multi-artifact exports

Evidence + quality review

Methodology traceability

Sample workflow

From raw shipment export to versioned evidence pack

Upload shipment export

Review mapping, quality, and evidence

Publish evidence pack

PDF

Executive summary for procurement and stakeholder review

XLSX

Shipment workbook for line-level checking and handoff

JSON

Machine-readable artifact for internal tools and integrations

One workspace state can publish PDF, XLSX, JSON, methodology, evidence register, quality review, and approval history together.

Pack outputs

What your team actually gets

Each published evidence pack combines executive outputs, structured data, methodology context, and review history from one workspace state.

View sample pack View JSON example View methodology example

Executive PDF summary

For customers, internal stakeholders, and procurement teams that need a clear human-readable deliverable.

Shipment workbook

CSV and XLSX exports for line-level review, downstream analysis, and operational handoff.

Machine-readable JSON

Structured artifact output for software integrations, internal tooling, and embedded workflows.

Methodology statement

A reusable explanation of scope, factors, assumptions, and reporting logic for defensible delivery.

Evidence register

A clear record of supporting evidence attached to the reporting workflow.

Quality report

Coverage, assumptions, defaults, and trust signals surfaced before publishing.

Audit trail

A versioned history of review, approvals, and publication actions.

Sample evidence pack

A reusable bundle for customers, procurement, and internal review

The pack is not a single document. It is a controlled export bundle that keeps executive output, supporting data, methodology, quality review, and publication history together.

Executive PDF summary
Shipment workbook (CSV/XLSX)
Machine-readable JSON
Methodology statement
Evidence register
Quality report
Audit trail

Methodology example

Explain what was calculated, what assumptions were used, and what changed

Use a methodology statement to describe scope, factor set, assumptions, evidence coverage, and output context without reconstructing the reporting logic later.

JSON example

Make pack outputs usable in software workflows

The machine-readable artifact is designed for retrieval, validation, and downstream workflow orchestration, not just file delivery.

{
  "workspace": "shipper-q2-review",
  "pack_status": "published",
  "artifacts": ["executive_pdf", "shipment_xlsx", "machine_json"],
  "quality_review": { "coverage": "91%", "defaults_flagged": true }
}

Workflow fit

Choose the workflow that fits your team

The same platform, configured for different reporting operations.

For 3PLs and forwarders

Manage recurring customer and subcontractor reporting from reusable workspaces instead of rebuilding each request from scratch.

See forwarder workflow

For enterprise shippers

Create defensible transport emissions packs for procurement, internal review, and supplier reporting workflows.

See shipper workflow

For consultants

Reuse one reporting system across clients, templates, and reporting cycles without fragmenting methodology and outputs.

See consultant workflow

For software teams

Embed workspaces, pack generation, artifact retrieval, and approval flows in your own logistics or procurement product.

See developer workflow

Works with your TMS export

Alpega TMSTIMOCOMTrans.eu

Build repeatable reporting operations, not one-off PDFs

Each capability is designed to make reporting easier to reuse, easier to defend, and less dependent on manual spreadsheet work or PDF-only delivery.

Reusable reporting workspaces

Use one workspace per customer, lane, or reporting cycle so your team stops rebuilding the same reporting process from scratch every time.

Evidence pack builder

Publish one controlled evidence pack that includes the executive PDF, structured data, methodology, evidence register, quality review, and audit trail instead of sending disconnected files.

Data quality and coverage

Review where outputs rely on primary data, defaults, or modeled assumptions before publication so your team can explain confidence and follow-up actions.

Methodology traceability

Reproduce the same reporting output later with the same methodology, factor set, and assumptions so your team can explain what changed and what did not.

Approvals and audit trail

Track who reviewed, approved, rejected, and published each pack version so reporting moves through a controlled process instead of email handoffs.

API and embedded workflows

Expose workspaces, packs, artifacts, and webhook tests through the v2 API so software teams can embed the workflow instead of recreating it.

From shipment export to evidence pack in 3 steps

No rebuild of your source systems. Start with the data you already have.

Shipment export
CSV · XLSX

Mapping · Quality
+ Evidence review

Evidence Pack
Ready to publish

Create or select a workspace

Start inside a reporting workspace for a customer, reporting period, or procurement cycle. Then upload the shipment export you already have.

Workspaces hold imports, calculations, evidence, approvals, and pack versions together

Run calculations and review trust signals

Map fields, calculate WTW and TTW emissions, review provenance, attach evidence, and inspect methodology, factor version, assumptions, and quality coverage before publishing.

The same workspace can be rerun and reviewed repeatedly as new evidence arrives

Generate and publish an evidence pack

Build a versioned evidence pack with the artifacts your audience needs: PDF, CSV, XLSX, machine JSON, methodology statement, evidence register, quality report, and audit trail.

PDF remains available, but now as one artifact inside a broader evidence-backed pack

You do not need a new TMS or ERP workflow to start. The platform works from existing transport exports.

🎉 Packaging for reporting maturity

Choose the operating model that fits your reporting workflow

Each tier matches a different reporting motion: occasional self-serve, recurring team workflows, or embedded/API-led delivery inside another product or process.

Lite Self-Serve

For occasional uploads and lighter reporting needs

Free beta

One workspace flow with the core exports needed to evaluate the product.

Single-workspace flow
Executive PDF summary
Shipment CSV and XLSX exports
Basic machine-readable JSON

Start Free in Lite

Pro Workspace

Recommended

For recurring team workflows and reusable reporting operations

Early access / pilot

Unlock evidence review, quality controls, approvals, and reusable versioned packs.

Reusable workspaces across reporting cycles
Evidence register and approvals
Quality review and assumption controls
Branded export bundles

Book a Demo

API & Embedded

For TMS, ERP, procurement, and software teams

Enterprise access

Use LogisticsAI as a reporting layer inside your own product or operational stack.

Workspace-centric v2 API
Artifact retrieval and signed delivery
Webhook testing and workflow orchestration
Embedded evidence-pack delivery

Request API Access

Lite is the fastest way to evaluate. Pro Workspace is the best next step for recurring team operations. API and Embedded is for software-led deployment and integration-heavy workflows.

Frequently Asked Questions

The core unit is now the reporting workspace. A workspace stores imports, calculation runs, evidence, quality review, approvals, and report pack versions so reporting can be repeated and defended later.

Each pack can include an executive PDF summary, shipment CSV or XLSX exports, machine-readable JSON, a methodology statement, an evidence register, a quality report, and an audit trail.

Yes. PDF remains available as the executive summary artifact inside the broader emissions evidence pack.

No. You can still upload CSV or XLSX exports from existing transport systems and work from the mapped shipment data you already have.

The platform stores assumptions, surfaces defaulted and modelled inputs in quality review, and keeps methodology and factor references attached to each report pack version.

Yes. Template bundles can control branding, artifact inclusion, machine schema flavor, methodology wording, evidence register layout, file naming, and title suffixes.

The platform is aimed at 3PLs, enterprise shippers, sustainability consultants, and software vendors that need repeatable, evidence-backed, and machine-readable reporting workflows.

Yes. Organisations can work from shared workspaces, keep evidence and approvals together, and generate versioned packs without rebuilding the reporting flow each time.

Run repeatable emissions reporting, not one-off PDFs

Create a workspace, review evidence and quality, and publish versioned packs from one workflow.

See Sample Evidence Pack Start Free in Lite

Workspace-firstMulti-artifact exportsMethodology traceabilityAudit-ready history