S.I.M.P.L.E. · EDITORIAL BUYING GUIDE

Connecting software to S.I.M.P.L.E.: prepare before requesting a proposal

To request a SIMPLE connection proposal, identify the applicable exchange and its source data. Your software name matters but does not show which events are available, how to obtain them or when they are confirmed. The proposal must cover the journey through to the platform response.

Explore the related solution Assess my case
THREE POINTS YOUR PROPOSAL SHOULD COVER
01Applicable workflowSource information
02Source data and interfacesMapping and rules
03Platform responseData where it is used

Conceptual diagram. The actual flow is defined using your data, interfaces and partner specifications.

Applicable workflow: define the operational meaning

Start by describing applicable workflow through an example from your operations.

A proposal for S.I.M.P.L.E. connectivity should begin with the workflow relevant to your activity. Identify your participant role, the information to exchange and the system holding its source. Pricing a generic connection before establishing these responsibilities leaves the required operational outcome and scope open to interpretation.

Source data and interfaces: establish the actual scope

Reviewing source data and interfaces separates available functions from remaining work.

Inventory the information available in the TOS or operational application. Distinguish exportable fields from information visible only on screen or entered manually. This difference determines whether configuration, an additional interface or software adaptation is needed before information can support the intended external exchange.

Platform response: identify evidence of completion

For platform response, distinguish sending information from actually using it.

Include the applicable documentation and its version in scope. Where access procedures or test environments apply, identify who requests them and who supplies credentials through a secure channel. The implementation schedule should expose these dependencies rather than treating external access as an automatic consequence of development.

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. Review scope: EDI software to connect with S.I.M.P.L.E..

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.

An example to frame the decision

Illustrative scenario, not attributed to an actual customer. A terminal receives operator pre-advice and enters part of it into the TOS. Movement information is later returned through another channel. A specific S.I.M.P.L.E.

exchange also needs operational data. Review scope: How an EDI integration is implemented.

The TOS keeps managing the terminal; integration brings data closer

Terminal teams need pre-advice in the correct record and movement reporting based on confirmed events. Do not put production data or credentials in a sales request. Documentation and anonymised samples can expose many initial dependencies. Test access is arranged later with authorised owners and permissions appropriate to verifying the agreed exchange, rather than becoming a prerequisite for submitting a general enquiry about feasibility.

Match equipment, orders and events

The TOS needs to recognise which unit or service a message represents. Identifiers, references and statuses are reviewed alongside rules for accepting orders or updating existing records.

Compare proposals using the same workflow

Give each provider the same incoming document, intended result and required response. Ask how it covers applicable workflow, source data and interfaces and platform response. Compare partner adaptation, existing-software tasks and acceptance criteria. Identify the effect of adding documents or changing specifications. A lower price may cover fewer stages; a broader project may include functions you do not yet need. Compare useful scope before comparing price, so the decision reflects the workflow your team actually needs.

Prepare the first discussion

Identify software name and version, partner and available documentation. Prepare your activity, required exchange, source software and available documentation for an initial discussion. Identify who can confirm missing information. Requesting a proposal with visible uncertainties is more useful than receiving a price based on assumptions that the business, software provider and integrator have not agreed.

Where Ediprism fits

Ediprism is EDI integration software between your business systems and third-party applications. Ediprism can be scoped as a layer above existing applications connecting applicable SIMPLE workflows without replacing operational software. Feasibility and scope require specific interfaces and requirements. This is not an assertion of official certification or a universal guarantee that every activity or obligation is covered automatically.

Initial cost, continuity and later changes

Separate implementation, third-party services and maintenance. Compare data extraction, exchange adaptation and response handling as separate quote components. Include your software vendor's work where an interface must be enabled. This prevents a proposal appearing to cover SIMPLE connectivity while actually accounting for only one of the stages the project needs.

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.

Choose the milestone that triggers communication

Planned and executed movements have different meanings. We define which TOS event triggers a message, which references it carries and how to prevent a planning change being reported as completed work.

Separate EDI exchanges from SIMPLE connectivity

Shipping-line, customer and S.I.M.P.L.E. flows are documented separately. We assess reusable TOS data and additional information needed for each destination without treating their models as equivalent.

What we need to assess the connection

Software identity and version, available interface documentation and an anonymised example exchange. Permissions, test environments and responsibilities are reviewed with the vendor or developer. Connectivity is confirmed by scope; brand compatibility is not claimed without verification.

A first flow with standalone value

For a limited phase, define one document, one partner and one useful operational result. The first phase may cover one applicable flow if its outcome is useful to operations. State included work and what continues through another route. This prevents a first connection being commercially interpreted as covering every SIMPLE requirement affecting the organisation when only a defined workflow has been assessed.

References that help investigate exceptions

Users reporting differences need to locate the corresponding message and operation. Ask who reviews documentation changes and assesses their effect on the connection. Not every revision requires rebuilding a workflow, but changes should not be assumed covered without analysis. Maintenance needs explicit ownership and an agreed procedure for approving adaptations, including any additional work involving the source software.

Distinguish objectives from verified capabilities

A business need describes the result sought but does not prove the system has every required function. During transition, agree the authoritative source of each value and who reviews pending responses. Make continuing manual work visible. Operations should understand the actual journey instead of assuming that adding a connector has removed every intervention point or resolved unavailable information in the source application.

Decide the next step

Identify the unresolved question and information needed to answer it: perhaps an ERP interface, amendment meaning or customer response. Handover should link requirements, source information and test evidence. This helps maintain the connection after interface or personnel changes. A statement about SIMPLE compliance does not replace identification of the particular workflows verified in your project and the limitations still relevant to their operation.

1. Identify the exchange

Capture the business need, partner specification and existing system. Confirm the result each document should produce and the data it requires.

2. Agree the solution and ownership

Define interfaces, mappings, validation and responses. Responsibilities across Ediprism, your team, software vendor and partner must be documented alongside prerequisites.

3. Test realistic scenarios

Agree inbound and outbound examples, amendments, retries and exceptions. Testing verifies final-system data and partner responses. Timing also depends on access and third parties.

4. Prepare go-live and continuity

Determine monitoring ownership, incident escalation and maintenance before operation. Version and specification changes need a review, testing and acceptance process.

A module in your existing software

A module may fit if it covers required documents, partners, versions and business rules. Ask what is included and what needs configuration or development. Check the effect of adding customers or changing specifications, since fit depends on scope and maintenance.

Custom integration development

This can fit when your team intends to build and maintain the workflow and understands the systems and partner requirements. Include interpretation, mapping, responses, tests and subsequent changes. The first transmission is not the whole project: identify incident ownership and documentation responsibilities.

An integration layer such as Ediprism

This is an option when you want to connect partner formats to existing systems while separating exchange adaptation from business logic. Assess Ediprism by message coverage, available interfaces and intended operational results. Scope should identify adaptations and ownership shared with your software vendor.

Compare offers on the same basis

Provide the same scenario to each provider: document, partner guideline, software and required result. Test an exchange with valid references and one missing required information. Acceptance criteria should explain how the response is shown and who resolves rejection. A message leaving your application does not establish that the relevant workflow has completed or that its contents have been accepted.

An exercise to evaluate the proposal before buying

Assessment scenario; not results from an actual customer.

Assess one SIMPLE workflow identified as relevant to your activity. Use source information the application can actually supply and mark a field still needing confirmation. Ask where it will come from, who validates it and what happens while it remains unavailable. Do not insert a demonstration value without exposing the unresolved operational dependency.

Trace extraction, adaptation and response handling. Ask what evidence each stage provides and how operations would locate rejection of the sample. Identify owners of access, test environments and any TOS-vendor involvement needed to continue. The exercise closes dependencies rather than certifying every platform-related obligation through one example.

Acceptance should refer to the agreed workflow and verified requirements. Retain inputs, expected outcomes and pending questions without credentials. If an offer claims wider coverage, request the same detail for additional exchanges instead of assuming all are included because the service mentions SIMPLE.

Reference documentation

Partner and system specifications define the project. These references describe the framework, not Ediprism compatibility or certification.

SIMPLE · API y manuales ↗

Before you choose a provider

How do I apply this guide to my case?

Identify your software, partner and intended result. Assessment should review applicable workflow, source data and interfaces, platform response using examples and available interface conditions.

How do I compare providers?

Provide both with the same document, system and intended result. Compare workflow coverage, interfaces, responses, implementation, support, changes and cost.

How much does integration cost?

Cost depends on partners, documents, interfaces, rules and tests. Separate implementation, adaptations, third-party costs and maintenance.

Define your connection.

Review the partner, your system and the result you need. A proposal starts with that scope.

Assess my integration

Privacy preferences

The website works without measurement. Your preference is stored for 180 days.

Necessary preference

Stores your choice across pages. It is not used for tracking.

See technologies and retention