TMS/ERP mapping
Pin source field, owner, source timestamp and mapping version for a defined transport workflow.
eCMR + eFTI Integration Pack · proposed
Keep your TMS. Connect eCMR and eFTI through one controlled layer.
One existing TMS or ERP record should feed the document workflow and the regulatory preflight without creating another system of record. This is the planned software bundle; the public scanner remains the only available self-service tool.
Bundle design
One workflow, several independently verified boundaries.
Existing TMS / ERP→Canonical shipment model→eCMR provider + signature handoff→eFTI preflight→Acceptance evidence
The canonical model is an internal mapping layer, not a new document standard. Existing eCMR and signing providers remain responsible for their own services; this product does not create a signature or certify an eFTI platform.
Planned modules
Make every handoff testable.
Provider-neutral eCMR
Test data exchange, participant rights, draft review, signature evidence and amendments against a named provider/version.
eFTI preflight
Report scoped dataset gaps and country/Gate dependencies without implying authority acceptance.
Acceptance tests
Keep fixtures, contract versions, failures, reviewer and evidence pack for a repeatable release decision.
Why this packaging
Funded logistics projects are a market signal, not our price list.
Italy’s MIT reported more than 1,200 firms starting logistics digitisation projects under a €157 million LogIN Business programme. The programme scope explicitly includes interoperable platforms and eCMR dematerialisation aligned with national eFTI work. Those figures cover a broad grant programme; they do not prove demand, a completed purchase or willingness to pay for this specific bundle.
Availability boundary
Design target, not a buy button.
No provider-specific adapter, signing integration, certified-platform connection or production eFTI submission is offered on this site. A future software release must pin the exact TMS/ERP, eCMR and signing provider versions, contract fixtures, security scope and acceptance evidence. There is no bespoke workshop or mandatory setup service attached to the proposed plan.
See the integration architecture