TERMINALS · EDITORIAL BUYING GUIDE

Terminal EDI integration: from incoming pre-advice to TOS registration

Pre-advice becomes operationally useful when the TOS recognises its unit, service and corresponding order. Mailbox receipt does not guarantee that result. Define what creates a record, what updates one and how unknown references are handled.

Explore the related solution Assess my case
THREE POINTS YOUR PROPOSAL SHOULD COVER
01Unit and serviceSource information
02Creation or updateMapping and rules
03Unknown referenceData where it is used

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

Unit and service: define the operational meaning

Start by describing unit and service through an example from your operations.

Pre-advice does not mean a completed gate movement. Define its meaning for your terminal and the TOS record required: a forecast, request or unit information. Preserve that distinction so the integration does not automatically turn an intended activity into an executed event that operations has not confirmed.

Creation or update: establish the actual scope

Reviewing creation or update separates available functions from remaining work.

Match unit, order, service and partner using the keys the TOS needs. The same container may participate in different operations over time. Its number alone could attach pre-advice to the wrong visit where the destination requires more context to identify the intended terminal transaction correctly.

Unknown reference: identify evidence of completion

For unknown reference, distinguish sending information from actually using it.

Check what happens when an operator changes pre-advice before arrival. The TOS may permit some updates while requiring review for others. Apply rules according to the operational state of the existing record, rather than treating the latest message as though no previous information or decision existed.

Pre-advice needs to reach the TOS before operations need it

EDI pre-advice still creates work if staff copy the data or search for the corresponding order. Review scope: EDI integration for terminals and depots.

Operator EDI and SIMPLE connectivity need defined scopes

If you also need S.I.M.P.L.E., reuse available information without treating the exchanges as identical. Review scope: EDI integration for terminals and depots.

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. For multiple operators, test similar references belonging to different partners. Identification needs enough context to prevent cross-assignment. This exposes a risk that a demonstration using only one account and unit would not reveal before deployment, even if every individual document is structurally valid.

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. Test an expected unit, an unknown service reference and an amendment to the same pre-advice. Verify what operations sees and how rejection reaches the responsible person. The intended outcome should be understandable to terminal staff, not only to the developer responsible for translating the incoming message.

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 unit and service, creation or update and unknown reference. 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. Collect pre-advice, its amendment and a description of the operational record required, excluding sensitive information. Add the available TOS interface and mandatory references. This sequence supports a terminal-focused proposal that addresses actual registration instead of offering only message receipt without the missing operational connection.

Where Ediprism fits

Ediprism is EDI integration software between your business systems and third-party applications. Ediprism can adapt partner pre-advice to an available TOS interface. Assessment should confirm permitted creation and amendment operations and mapping ownership. Terminal applications should not be assumed to expose identical functions or accept changes at every operational stage simply because they all manage similar physical activity.

Initial cost, continuity and later changes

Separate implementation, third-party services and maintenance. Identify receipt and TOS registration as parts of the quoted pre-advice workflow. Scope movement reporting or relevant SIMPLE exchanges separately if required. Their operational relationship does not establish identical requirements, available data or implementation work; each flow needs its own documented trigger and intended result.

Pre-advice needs to reach operations

Information from a shipping line or operator only adds value when matched to the equipment, services and orders the terminal manages. We assess where the data belongs and which operational decisions depend on it before defining the connection.

From confirmed movement to outgoing message

Outbound communication matters too: an event should be sent when the agreed milestone occurs, using the correct references. We define its source, the relationship between TOS and partner statuses, and the handling of corrections or retries.

SIMPLE as an additional flow

S.I.M.P.L.E. connectivity is assessed against data and events available in your system. Shipping-line exchanges and platform reporting are not automatically the same flow: each requires its own scope, requirements and checks.

What we review before quoting

Identify existing software, the partner and its documentation, inbound and outbound flows and available interfaces. This enables agreement on test scenarios, exception ownership and readiness criteria. The proposal should reflect adaptations needed for the specific exchange.

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. Check how the TOS represents pre-advice needing review. The owner should distinguish received information from an operationally ready record. Integration must respect that state rather than resolve a missing reference by creating an apparently complete operation using approximate information the business has not approved.

References that help investigate exceptions

Users reporting differences need to locate the corresponding message and operation. For investigation, staff need the operator reference and corresponding TOS record. Agree how amendments and the applied version are retained. This context supports resolution without treating a transmission log as the complete history of an operational activity, particularly when several messages concern the same unit or visit.

Distinguish objectives from verified capabilities

A business need describes the result sought but does not prove the system has every required function. Define the first pre-advice using the new route and treatment of previously registered items. Operations needs this boundary to check duplicates and pending records. Cutover cannot rely solely on enabling a connector while an uncoordinated earlier process continues entering the same information into the TOS.

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 connect messages, external references and TOS record types, including approved amendment rules. This lets operations understand behaviour and supports later partner changes without reconstructing implementation decisions from code when the original project participants are unavailable or no longer responsible for the connection.

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 exercise to evaluate the proposal before buying

Assessment scenario; not results from an actual customer.

Use initial pre-advice, an amendment and a service reference absent from the TOS. Terminal staff should define the record expected after each message and required review. An intermediate-screen entry is insufficient if it cannot yet be related to the intended unit operation.

Ask which keys distinguish visit, unit and service. Include a similar reference from another partner where relevant. Amend a record after its operational status changes and establish when the actual interface permits updating or requires an exception.

Acceptance evidence can link incoming message, TOS record and response shown to the owner. Include mapping maintenance and behaviour documentation. Scope separate exercises for movements or SIMPLE if required: validating pre-advice does not establish the entire terminal lifecycle or every future exchange, even where these workflows share some source information.

Reference documentation

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

GS1 · Estándares EDI ↗

Before you choose a provider

How do I apply this guide to my case?

Identify your software, partner and intended result. Assessment should review unit and service, creation or update, unknown reference 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