Pre-advice arrives. Registration starts again.
Staff find units, compare references and re-enter data in the TOS. Connectivity should reach the record operations needs, including amendments and exceptions.
SOFTWARE FOR LOGISTICS OPERATIONS
Edichemy connects your TOS, TMS, ERP or custom software to SIMPLE to receive and share available logistics-chain information. Use partner data to anticipate changes, plan resources and coordinate your team through your existing software.

The Ecofin Cloud team has already made a SIMPLE connection work. Edichemy uses that experience to define the journey your operation needs while retaining existing software.
Assess connectivity for my businessChoose an operation to see the information Edichemy uses, what it prepares and the repeated task you want to remove.
In your TOS
Your team already works with this information.
Edichemy uses your terminal record to prepare the exchange your operation needs to communicate.
Avoid finding and re-entering the same information in another form.
Illustrative example. Interfaces and rules are scoped for your terminal.
In your TMS
Your team already works with this information.
Connect service information to the shipper’s system while retaining the right references.
Reduce work moving orders and updates between applications.
Illustrative example. Permitted updates depend on your TMS interface.
In your systems
Your team already works with this information.
Edichemy helps prepare your freight information for the eFTI environment defined in the project.
Avoid rebuilding each transport’s information across several applications.
Preparing and connecting data does not establish certified eFTI-platform status.
Information to anticipate, plan and coordinate.
Staff find units, compare references and re-enter data in the TOS. Connectivity should reach the record operations needs, including amendments and exceptions.
Sharing quantities and statuses elsewhere creates work and uncertainty. Exchanges should start from confirmed facts and retain order, service or unit references.
SIMPLE and eFTI require specific workflow and data assessment. Edichemy starts from existing software, exposing reusable information, gaps and their owners.
SIMPLE connectivity and eFTI preparation, each with its own requirements and responsibilities.
Identify the exchange your business needs and connect source information. Scope adaptation, responses and existing-software vendor work.
Explore SIMPLE connectivityLocate transport information and confirmed sources. Define connectivity to the relevant eFTI environment, distinguishing data preparation from a certified platform.
Explore eFTI preparationFictional examples explaining the problem, proposed workflow and what your team would need to verify.
From incoming pre-advice to TOS information and the specifically scoped SIMPLE exchange.
Explore the application scenarioA TMS service with amendments and the statuses its shipper needs.
Explore the application scenarioStart with one dispatch to identify sources, gaps and eFTI preparation.
Explore the application scenarioWhat to request, compare and include in the proposal. Each guide leads to a concrete next step.
Compare operational outcomes, dependencies and the work required from your software vendor.
Read the guideFor terminals seeking to reuse TOS records and reduce repeated data entry.
Read the guideUnderstand implementation and maintenance costs beyond the initial price.
Read the guideDistinguish preparing information, connecting it and purchasing the relevant environment: related decisions with separate scopes.
Read the guideA practical starting point for operations and IT buyers requesting a useful proposal.
Read the guideQuestions about responses, pending records and corrections before purchasing integration.
Read the guideDecide around work between systems. Compare what operations still does after information is received or communicated.
Read the guideDefine testing, ownership and launch arrangements around operational continuity.
Read the guideFor carriers and operators seeking to communicate from existing records without rebuilding each job.
Read the guideClear answers about scope, existing software and your team’s work.
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.
No. It connects agreed workflows from your software to SIMPLE rather than replacing the platform or its access procedures.
That status is not claimed. This proposal covers data preparation and connectivity; participating environments and providers need identification and verification.
Edichemy focuses on operational logistics connectivity, with SIMPLE and eFTI preparation as key areas. Each exchange is scoped individually.
No. Evaluate their purposes and requirements separately. Shared source data does not make their workflows equivalent.
Tell us about your software and required exchange. We will review the journey to prepare a proposal your team can assess.
Discuss my operationWe can load Nalloo and Google Analytics to measure website usage. Choose either service or continue without tracking. Cookie information