Receive SIMPLE information in your TMS to plan transport

For carriers and operators seeking to communicate from existing records without rebuilding each job.

In your TOS

Unit pre-advice
Unit
Already recorded by your team
Service
Its reference in the TOS
Movement
The fact confirming the operation

Your team already works with this information.

edichemy

Your system’s pre-advice, prepared for SIMPLE.

Edichemy uses your terminal record to prepare the exchange your operation needs to communicate.

  • Reuse information already in the TOS.
  • Adapt references and fields to the agreed flow.
  • Link the response to its source operation.
The work you want to avoid

Avoid finding and re-entering the same information in another form.

Explore SIMPLE connectivity

Illustrative example. Interfaces and rules are scoped for your terminal.

More context for dispatch

Partner updates can support transport planning. Specify the information dispatch needs, when it becomes useful and the TMS job it should relate to.

Start with the dispatch record

TMS references, collections, deliveries and statuses become confirmed at different times. Identify the required SIMPLE exchange and assess available service data rather than assuming completeness.

Retain links through amendments

Dates, units and references may change after planning. Define communicated amendments, validation and their relationship to the original record while respecting operational states and available interfaces.

Request a dispatch-focused proposal

Tell Edichemy your TMS, repeated work and required partner exchange. Assess available data, adaptations and responses to scope a workflow with clear intervention ownership.

Questions that help you decide.

Clear answers about scope, existing software and your team’s work.

Can Edichemy receive information as well as send it?

Scope may include receiving and sending. We define participant data, your team’s needs and how to use it in your software. Connectivity supports planning and coordination, subject to available data, permissions and interfaces.

DEFINE YOUR CONNECTION

Your next step,
with a clear scope.

Tell us about your software and required exchange. We will review the journey to prepare a proposal your team can assess.

Discuss my operation

Scope your Edichemy connection

Move from your required workflow to a clear purchasing scope.

S.I.M.P.L.E.Cost and scopeImplementationRequest a proposal