Connect your software to S.I.M.P.L.E.

Receive and share information through SIMPLE from your existing software. Edichemy adapts agreed exchanges so partner information can support planning, resource coordination and change management.

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.

Request a proposal for my case

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

Receive information to prepare the next step

Information from another participant can help organise work before the next stage begins. Identify the data needed, its provider, availability and where your team should use it. Edichemy adapts the agreed exchange to your software: updates can support planning, resource coordination or incident detection. Value depends on what participants actually share and the available interfaces; access to all chain information is not assumed.

Your team already records the information. Connect it next.

Pre-advice is in the TOS, an order in the TMS and shipment references in your operational application. Extra work begins when someone searches, checks and re-enters those facts elsewhere. Edichemy starts with that journey: available information, confirmation timing and the required exchange. Replacing all existing software is not the starting assumption.

Practical experience connecting to SIMPLE

The Ecofin Cloud team has already made a SIMPLE connection work. This experience informs assessment of your operation: reusable work, required adaptations and the response staff need. Edichemy turns that experience into a scope defined by systems, information and partners. A completed flow does not establish that every installation is identical, and no unverified deadlines, savings or certification are claimed.

A relevant workflow with a defined outcome

Identify your operational role and required exchange before pricing. A terminal and a transport operator may originate different facts. Scope should connect each requirement to its source, adaptation and expected response. SIMPLE documentation and actual interfaces determine implementation rather than a general claim of connectivity.

Include the response as well as sending

Information leaving an application does not establish destination acceptance. Define available confirmations, rejection recognition and ownership of missing references. Staff should understand what has been communicated and what remains pending without confusing a technical receipt with the business outcome the operation requires.

What we need from existing software

Review outbound and, where relevant, inbound interfaces. An API, supported export or other documented mechanism may be appropriate. Missing information and operations belong in project scope with an owner. Retaining software can require configuration and vendor participation; it does not imply a connection requiring no work.

A proposal you can compare

Name the workflow, information, external tasks, testing and maintenance terms. Request a valid sample, amendment and missing-required-field case, then use the same example for alternatives. Edichemy does not claim official SIMPLE certification or universal coverage of every requirement affecting the business.

Official framework source: SIMPLE · API y manuales

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.

Which software can connect my TOS or TMS to SIMPLE?

Edichemy is designed to connect existing operational software to the SIMPLE workflows your business needs. It builds on the Ecofin Cloud team’s connection experience and defines interfaces, adaptations and responses in a proposal for your case.

Does Edichemy replace SIMPLE?

No. It connects agreed workflows from your software to SIMPLE rather than replacing the platform or its access procedures.

Can we retain our TOS or TMS?

That is the starting point. Assessment confirms interfaces, operations and adaptations for your software version.

Can it send and receive?

Both directions may be included where interfaces and permissions support them. Each must be explicitly scoped.

Does this cover every obligation?

Verify the relevant requirements and contracted workflows. Installing an integration layer does not establish complete compliance.

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