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.
Commercial entry
Start with a design-partner POC.
Choose one customer workflow, one country corridor and one provider path. Agree fixture data, acceptance criteria, observability and “not supported” states before a broader SDK or white-label commitment.
Explore the developer contract