Integration family

Exchange the right documents with your partners.

Orders, receiving, shipments and status updates: choose your partner’s document format, then configure transport and business rules. An AS2 receipt alone does not create an order.

Business documents

Identify the documents you need to receive and send

X12 940

Warehouse shipping order into WMS orders

View connection details
Direction
Inbound
Business objects
Warehouse shipping order into WMS orders
Protocol and version
ANSI X12 004010
Configuration
Client, warehouse and line mapping
Status
Message conversion available
Limitations
Non-each UOM or missing order number is rejected; no AS2/VAN transport included

X12 856

Advance ship notice

View connection details
Direction
Inbound
Business objects
Advance ship notice
Protocol and version
ANSI X12 004010
Configuration
Client and ASN mapping
Status
Message conversion available
Limitations
No AS2/VAN transport included

X12 945

Warehouse shipping advice

View connection details
Direction
Outbound
Business objects
Warehouse shipping advice
Protocol and version
ANSI X12 004010
Configuration
Client and shipment mapping
Status
Message creation available
Limitations
No AS2/VAN transport included

X12 214

Shipment status

View connection details
Direction
Outbound
Business objects
Shipment status
Protocol and version
ANSI X12 004010
Configuration
Events and status mapping
Status
Message creation available
Limitations
No AS2/VAN transport included

X12 997

Functional acknowledgment

View connection details
Direction
Outbound
Business objects
Functional acknowledgment
Protocol and version
ANSI X12 004010
Configuration
Received interchange and transaction
Status
Message creation available
Limitations
Message-level functional acknowledgment, separate from the AS2 transport receipt

Akanea PIVOT

Items, receiving, preparation, delivery and pallets

View connection details
Direction
ART/ENT/SOR inbound; CSTO/CPRE/CENT/CSOR/DEP outbound
Business objects
Items, receiving, preparation, delivery and pallets
Protocol and version
PIVOT EDI LOGISTIQUE V14 · fixed width
Configuration
Client dossier and depot-to-warehouse crosswalk
Status
Client and warehouse configuration required
Limitations
An active depot-to-warehouse mapping is required to accept the exchange

EANCOM DESADV

Despatch advice and parcel/pallet hierarchy

View connection details
Direction
Outbound
Business objects
Despatch advice and parcel/pallet hierarchy
Protocol and version
EANCOM D96A · EDIFACT
Configuration
Retailer profile, GLNs, dialect and partner options
Status
Generation implemented; active profile required
Limitations
Retailer variant must be qualified; AS2 only when a station is configured

Separation

Connect each document to its business processing

  1. Business object

    Order, ASN, shipment, status or acknowledgment.

  2. Format

    The profile creates or reads the expected message content.

  3. Transport

    The document travels through AS2, a file or the transport configured for that exchange.

  4. Receipt

    A 997 acknowledgment, MDN and transmission status each confirm a different stage.

AS2

Configure certificates and AS2 receipts

AS2 reception checks transport and produces its receipt; it does not automatically import the document into your orders. Asynchronous receipts remain pending: automatic reconciliation is not offered here.

AS2 partner station

Transport wrapper around an EDI message

View connection details
Direction
Inbound and outbound according to configuration
Business objects
Transport wrapper around an EDI message
Protocol and version
AS2 RFC 4130 · S/MIME over HTTP
Configuration
AS2-From, AS2-To, URL, certificate references and MDN mode
Status
Station implemented; active partner required
Limitations
An unconfigured addressing pair is rejected; certificates remain in the secret store

Transmission log

Message content, partner, status, error, linked references and attempts

View connection details
Direction
Inbound and outbound
Business objects
Message content, partner, status, error, linked references and attempts
Protocol and version
Cross-format log
Configuration
Partner and client scope
Status
Log and download of stored documents
Limitations
Download depends on a stored document; retry is limited to eligible DISPOR files sent over SFTP

Acknowledgments

Distinguish transport receipt from business processing

Transport level

  • AS2 addressing recognised
  • signature and encryption checked
  • Synchronous MDN validated; asynchronous MDN remains pending

Message level

  • syntax and transaction type recognised
  • business mapping accepted or rejected
  • 997 or application state according to configured processing

Operations

Handle errors without changing the original document

Check the transmission log before retrying

The log shows direction, format, flow, partner, status, errors and retry count. A document can be downloaded only when its contents were stored.

Available retry covers failed or pending outbound DISPOR carrier files with a linked carrier and configured SFTP. It resends the stored contents; it is not a general AS2 or EDI retry.

Plan your EDI exchange

Tell us the partner, document type, direction and required transport. We will define mapping, expected receipts and error handling.