Ownership and provenance
field_owner, source_system, source timestamp and conflict resolution.
Integration architecture
Integrate once. Observe every handoff.
A canonical internal record reduces repeated mapping work, but the defensible value is in ownership, lifecycle, schema change detection and traceable failures.
The pattern
From fragmented sources to scoped decisions.
ERP / TMS / WMS / EDI / partner→Canonical shipment graph→Versioned preflight→Provider / country output
The canonical model is an internal normalization layer, not a new proprietary transport standard. Adapters should follow relevant open and emerging specifications.
What an integration needs
More than a happy-path connector.
Change management
schema_version, mapping_version, contract tests and provider interface diff.
Observability
correlation ID, mapped payload, validation result, retries and dead-letter owner.
Operational control
Idempotency, asynchronous states and human review before a risky retry.