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