Software to connect your operations to SIMPLE
If you need a provider to communicate operational data to S.I.M.P.L.E., identify what your software supplies and which workflow the solution covers. Ediprism acts as an adaptation layer between source data and the required exchange. Proposals should specify applicable flows, source-system events and result verification, enabling a defined connection rather than a generic compliance promise.
From existing data to the SIMPLE API
The Spanish logistics platform provides an integration API. Ediprism is positioned as the layer that obtains source-system data, adapts it to the required exchange and coordinates communication. Receiving EDI and communicating with SIMPLE are separate stages of an end-to-end flow.
What your system needs to provide
First identify the operation, references and events to communicate. Check whether the information exists, when it is confirmed and how it can be obtained. Missing data or interfaces become part of the scope before automation is promised.
What compliance means for your case
Requirements must be identified for your activity, contract or process. Technical connectivity alone does not demonstrate compliance with all business obligations. The proposal should state included flows, acceptance requirements and exclusions.
How the integration is accepted
Access conditions and the applicable environment are checked, data is tested and destination responses reviewed. Handling incomplete information, rejections and unavailability, as well as responsibility for specification changes, must be defined.
Reference documentation
Exchange details must be checked against the applicable official documentation.
SIMPLE API and manuals ↗Before you choose a provider
Does SIMPLE replace my ERP or TOS?
This integration aims to use your existing system and communicate the required data to the platform. Feasibility depends on available interfaces and data.
Does every EDI user need SIMPLE?
Using EDI does not imply this obligation. The requirement applicable to the specific activity or contract must be identified.
Is this an official or certified solution?
No official affiliation or certification is claimed. This is an independent integration with scope to be verified.
What determines the quote?
Required flows, source data, adaptations, connection conditions and testing. The review should distinguish implementation from maintenance.
Must I replace my software?
The proposal starts with existing systems. Interfaces, functions and permissions are reviewed; configuration or adaptation may be needed.
Which formats and protocols are supported?
Scope identifies formats, versions, protocols and partner guidelines. Available capabilities and required adaptations must be confirmed.
How much does integration cost?
Cost depends on partners, documents, interfaces, rules and tests. Separate implementation, adaptations, third-party costs and maintenance.
Who maintains the connection?
Agree responsibilities across Ecofin Cloud, your team, software vendor and partners, including changes and incidents.
Does SIMPLE connectivity establish full business compliance?
No. Connectivity covers the specified exchange. Applicable obligations and individual requirements need separate identification.