What to request when buying SIMPLE connectivity

Compare operational outcomes, dependencies and the work required from your software vendor.

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.

Explore SIMPLE connectivity

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

Buy connectivity that supports planning

Describe both outgoing exchanges and information you need to receive. Explain which planning or coordination task depends on it so the proposal addresses your operation.

Start with repeated work

Describe an operation recorded internally and communicated elsewhere. Identify copied values, source and recipient. Express a useful outcome for your activity rather than an undefined connection to every platform function.

Use the same example for each supplier

Provide success, amendment and missing-data samples. Compare extraction, adaptation and response. Include software-vendor work so transmission-only proposals are not treated as equivalent to a complete journey from your management system.

Make tests understandable to operations

Staff should recognise references, communicated facts and pending differences. Acceptance goes beyond a sending confirmation. Ask who corrects missing information and what evidence links results to source records.

Define continuity

Scope documentation changes, software upgrades and new workflows. Handover should name owners and interfaces. Evaluate Edichemy against committed and verified scope instead of relying on a compatibility label.

Official framework source: SIMPLE · API y manuales

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