Inspect field names
Paste a CSV header or try synthetic example headers. Get a transparent inventory, not a compliance score.
Explore Inspect field namesTransport Compliance Control Plane · in development
Find transport data gaps before the next handoff.
Start with your ERP or TMS field names. See which transport data groups are visible and what still needs an owner, a value check or integration evidence.
Free local demo · no account · no server upload.
Paid Workspace, API and Embedded plans are not on sale yet.
ERPTMSWMSPARTNERS
PLANNED CONTROLLED DATA LAYERShipment Record
Ownership · mappings · provenance · versions
eFTIeCMRBORDERINVOICE
Reference architecture · not a claim of live connections
Availability first
Choose a tool you can use today.
Plan the integration
Describe one system landscape and receive an educational checklist of the next questions to resolve.
Explore Plan the integrationRepeatable workspace
Versioned mappings, approved ownership and operational rule profiles are being tested privately. Paid access is closed.
Explore Repeatable workspaceThe operational problem
Your transport data already exists. It just does not exist in one place.
Different definitions
A field called “delivery date” can mean a planned slot in one system and proof of delivery in another.
Missing ownership
A required carrier or consignee value may be absent, yet no one knows who should supply it.
Changing interfaces
Provider schemas, country requirements and partner workflows move on different schedules.
Five layers
Control the data before the handoff.
Product direction, not five released services. The free tools above are available today; provider connections, country adapters and paid access require separate release evidence.
Transport Data Readiness
Completeness, conflicts, ownership, source systems and versioned mappings.
Explore Transport Data ReadinessCompliance Preflight
Contextual rules by country, mode, role and stage; not a legal conclusion.
Explore Compliance PreflightIntegration & Interoperability
Provider-neutral models, contracts, test fixtures and change monitoring.
Explore Integration & InteroperabilityNetwork & Partner Readiness
Find the missing field, identify its owner and capture a reviewed response.
Explore Network & Partner ReadinessEvidence & Regulatory Operations
Explain what was checked, against which source, at what time and with which limitations.
Explore Evidence & Regulatory OperationsBuilt for software teams
Keep regulatory complexity outside your core product.
A TMS or ERP should not need a new hard-coded branch for every country, provider and regulatory version.
- One integration contract for a defined workflow
- Versioned mappings and preflight rules
- Conformance tests and evidence before rollout
TMS / ERP↓Stable contract↓eFTI Compliance↓Country / version / provider profile
EU readiness
One EU regulation does not mean one technical rollout.
Country requirements, Gate implementations and adapter testing are separate dimensions. The initial public view makes unverified coverage explicit.
FinlandReview requiredTechnical & adapter evidence not yet published
PolandReview requiredTechnical & adapter evidence not yet published
BelgiumReview requiredTechnical & adapter evidence not yet published
SlovakiaReview requiredTechnical & adapter evidence not yet published
Evidence boundary
Readiness backed by evidence — not green badges.
RuleRule versionSourceSource systemField ownerEvidenceValidation timeReview status
A result only means something when its scope and missing evidence are visible. The public tools on this site are educational demos; production validation awaits a tested software release.
Software direction
Start with a verifiable data check.
01Select a workflow
02Inspect field names in the browser demo
03Identify unresolved owners and conflicts
04Review explicit limitations
05Follow the software release status