Keep your software. Connect the information.

A layer between operations and external exchanges, from recorded information to the response your team needs.

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.

Incoming information, better coordination

Edichemy relates received data to your operation. Identify each participant’s available information and the planning decision it can support in your software.

Start with a recognisable task

Searching for references, copying pre-advice and rebuilding dispatch information explain a project better than format lists. Identify what must leave your system, what must return, when and for whom. The first scope should address daily work with an outcome operations can recognise.

Adapt meaning as well as fields

Similar field names may describe different things. A planned date is not a confirmed movement. Edichemy connects agreed sources, references and rules so information retains meaning at destination. Missing facts or decisions need an exception rather than an approximate substitute.

Include what happens after sending

Define the response or available outcome evidence. Distinguish communicated, accepted and pending information. Assign data correction and technical investigation ownership so operational users are not left between two suppliers without a clear route to resolve a problem.

A useful first phase with room to extend

Select a valuable flow and its test cases. Assess extensions against verified reusable work without assuming every future partner is identical. Continuity includes software changes, external rules and the people maintaining operational data.

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.

Is it only for SIMPLE?

Edichemy focuses on operational logistics connectivity, with SIMPLE and eFTI preparation as key areas. Each exchange is scoped individually.

What if we already have an EDI provider?

Review working stages and gaps. Retention can be assessed where interfaces and terms allow the missing journey to be connected.

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