ILLUSTRATIVE SCENARIO · NOT A REAL CUSTOMER

EDIPRISM · EDI INTEGRATION

Road transport: shipper orders and TMS statuses

Illustrative road transport scenario: operations, data, system connectivity and buying criteria.

HOW INFORMATION FLOWS
01Partner softwareSource information
02Ediprism · adapted dataMapping and rules
03EDI with TMSData where it is used

Conceptual diagram. The actual flow is defined using your data, interfaces and partner specifications.

Before connecting the systems

An agency receives structured shipper orders, but dispatch re-enters collections, deliveries and references in the TMS. Amendments arrive later and statuses use separate channels. This scenario identifies an integration need. It does not describe an actual implementation or customer results.

Who needs the solution and what they must decide

The example agency needs usable TMS services from shipper orders and correctly referenced status responses. Connectivity must respect amendments after planning. Its purpose is removing repeated transfer, not removing operational decisions dispatch must retain.

Information exchanged

New and amended orders, shipper references, collection and delivery points and service data. Outbound information includes TMS milestones required by the customer. Review anonymised examples, specifications and availability of each field before mapping. Missing data or unavailable interfaces must be included in scope.

Proposed Ediprism integration

Create or update services from orders, retain customer references and map TMS events to required statuses. Return messages originate from confirmed milestones, not forecasts. Ediprism sits between third-party software and the business system. Define receipt, transformation, delivery and any required return flow. Confirm interfaces and available functions with the teams maintaining both systems.

Changes, retries and exceptions

Repeated orders, changes after assignment, incomplete addresses and out-of-sequence statuses require agreed update rules and dispatch intervention. Distinguish received messages, accepted records and confirmed responses. Identify who reviews cases that cannot be automated and which information is needed to resolve them.

Implementation approach

Begin with one shipper and representative stop structures. Test creation, amendment and resend before activating milestone returns. Dispatch would approve automatically applicable changes and those needing review because the service has already progressed.

Intended improvement and measurement

Observe copied addresses, duplicate services and enquiries about dates or unrecognised statuses using the same order sample. These are proposed checks for a hypothetical agency, not results achieved by a real carrier.

What to request in a comparable proposal

The proposal would separate incoming orders, updates and shipper responses. Identify references, stops, TMS permissions and vendor participation. This assesses Ediprism against dispatch tasks and exceptions with clear terms for subsequently adding another customer.

Before you choose a provider

Is this an actual customer case?

No. It is a fictional scenario explaining a possible application. No customers, testimonials or actual implementation results are attributed.

What must be confirmed for my business?

Software on both sides, available interfaces, partner specifications, data and operational scope. These establish a specific proposal.

What would the cost and timeline be?

They depend on scope and identified dependencies. This example does not imply a price, available connectors or universal delivery time.

Must I replace my software?

The proposal starts with existing systems. Interfaces, functions and permissions are reviewed; configuration or adaptation may be needed.

How much does integration cost?

Cost depends on partners, documents, interfaces, rules and tests. Separate implementation, adaptations, third-party costs and maintenance.

How long does implementation take?

Timing depends on scope, access and participant availability. There is no universal deadline for all systems and partners.

Who maintains the connection?

Agree responsibilities across Ecofin Cloud, your team, software vendor and partners, including changes and incidents.

Define your connection.

Review the partner, your system and the result you need. A proposal starts with that scope.

Assess my integration

Privacy preferences

The website works without measurement. Your preference is stored for 180 days.

Necessary preference

Stores your choice across pages. It is not used for tracking.

See technologies and retention