Architecture and Connectivity
Overview
EDIconnect acts as a translation and routing layer between Azuvio / CRMconnect (orders, invoices, warehouse) and external trading partners.
Trading Partner
│
│ AS2 / SFTP / API / VAN
▼
┌─────────────┐
│ EDIconnect │ ← format translation (XML ↔ EDIfact)
│ Gateway │ ← validation (XSD)
└──────┬──────┘
│
▼
CRMconnect Core
(Orders, WMS, Finance)
Transport Protocols
AS2 (Applicability Statement 2)
Recommended for high-volume retail partners (Carrefour, Metro, Kaufland, Profi etc.).
AS2 is the recommended protocol for large partners (Carrefour, Metro, Kaufland). Certificate exchange is done once at onboarding and remains valid for years — once configured, it operates automatically without manual intervention.
| Parameter | Value |
|---|---|
| AS2 ID | EDIconnectAS2 |
| AS2 URL | https://as2.ediconnect.ro/ |
| Protocol | HTTPS |
| Port | 443 |
| MDN | Synchronous or asynchronous |
| Encryption | AES-128 / AES-256 |
| Signature | SHA-256 |
EDIconnect public certificate — import this into your AS2 software (Mendelson, SEEBURGER, OpenText, Drummond etc.) to validate signed messages from EDIconnect:
Send your own public certificate to the EDIconnect onboarding team to complete the exchange.
SFTP
Supported on request. Contact the EDIconnect onboarding team for connection details.
REST API
For modern partners with HTTP/JSON or HTTP/XML support.
For the REST API, the X-EDI-DocumentType header must be identical to the value of the <DocumentType> field in the XML message body. For example: if you are sending an original invoice, both must contain O. A mismatch causes a 422 error.
| Parameter | Value |
|---|---|
| Base URL | https://edi.azuvio.io/api/v1 |
| Authentication | Bearer token (OAuth 2.0) |
| Accepted formats | application/json, application/xml |
See the API Reference for details on available endpoints.
VAN (Value Added Network)
Supported on request. Contact the EDIconnect onboarding team for details on available VAN providers.
Message Flow
Inbound (Partner → CRMconnect)
- Message is received via the transport protocol
- Syntactic validation (EDIfact) or schema validation (XSD)
- Business rule validation (mandatory fields, GLN verification)
- Translation into the internal CRMconnect format
- Routing to the target module (Purchase Order →
purchase, Receiving Advice →warehouse) - Sending acknowledgement (CONTRL / HTTP 200)
Outbound (CRMconnect → Partner)
- A business event is triggered (e.g.: shipment created → DESADV)
- Internal data is mapped into the EDI message
- Format generation (XML or EDIfact according to partner configuration)
- Encapsulation in interchange envelopes (UNA/UNB/UNG/UNH or equivalent)
- Delivery via the configured transport protocol
- Recording of the delivery acknowledgement