Preflight contract
Expose readiness and blocking issues inside the existing TMS workflow.
For software vendors
Keep regulatory complexity outside your core TMS.
Offer customers a controlled path from operational records to country, eCMR and eFTI readiness while retaining the TMS as the system of work.
A vendor-first integration
The contract should survive provider changes.
Versioned rules
Separate customer data mappings from regulatory and provider profile updates.
Conformance evidence
Test signatures, amendments, negative cases and export, not just API connectivity.
Software integration path
Build a tested product surface.
A future SDK would need a defined workflow, country corridor, provider path, fixture data, acceptance criteria and explicit “not supported” states. No paid custom integration is offered here today.
Explore the developer contract See the proposed integration pack