Dispatch needs usable orders and statuses returned to the customer
TMS integration follows the service: requester, collection and delivery points, customer reference and possible changes. It also needs a return path for confirmed milestones. Assess Ediprism against both directions and their responses, including new orders, amendments and retries. Commercial scope should reflect dispatch work to automate, not only transmission.
Create a service with the information it needs
Review the data the TMS requires to register an order: references, parties, collection and delivery points and other applicable information. Missing data needs an agreed enrichment or review process.
Return statuses from confirmed events
The status sent to your customer must correspond to an agreed TMS milestone. Codes are mapped between systems and rules define updates, corrections and destination rejections.
One TMS, multiple customers
Distinguish the system data model from shipper-specific requirements. This makes it possible to quote what can be reused and which adaptation is needed for a new partner.
What we need to assess the connection
Software identity and version, available interface documentation and an anonymised example exchange. Permissions, test environments and responsibilities are reviewed with the vendor or developer. Connectivity is confirmed by scope; brand compatibility is not claimed without verification.
Before you choose a provider
Does the system need changes?
It depends on available interfaces and the intended result. Configuring an import may be enough, or an interface may need adding. This is identified before agreeing the proposal.
How is it verified?
Through agreed creation, amendment, retry and error scenarios. Acceptance must confirm the destination-system result and any responses required by the partner.
What does my software need to connect?
An interface supporting required input or output, available permissions and documentation. The vendor confirms operations and necessary adaptations.
Does Ediprism directly modify the database?
That access is not assumed. Agree an appropriate interface with the system maintainer and document registration before implementation.
How is document registration confirmed?
Define destination responses or evidence. Distinguish file receipt from operational registration to detect pending work.
What about missing references or duplicates?
Agree retry detection, original-document references and incomplete-data handling, with update, rejection and intervention rules.
Who maintains the connection?
Agree responsibilities across Ecofin Cloud, your team, software vendor and partners, including changes and incidents.
How much does integration cost?
Cost depends on partners, documents, interfaces, rules and tests. Separate implementation, adaptations, third-party costs and maintenance.