Add an EDI connection to your account
Overview
The objective of this document is to guide you through the setup of your EDI connection, making sure that all the fields are clear and what they will be used for.
Electronic Data Interchange (EDI) setup instruction
Congratulations on making the decision to set-up an EDI connection with your supplier, using Cin7 Omni. With EDI, you benefit from real-time data communication between trading partners such as Walmart & Amazon. EDI is not just data transfer, it has specific standards that govern the exchange of electronic business documents (e.g., purchase orders, invoices, healthcare claims, etc.).
Note: To add a connection, contact your Cin7 Omni onboarding specialist or create a case with support.
When starting the setup, you will be presented with the following screen. Descriptions of what is required for each step are provided below.
Submit details for EDI integration
Steps |
Field |
Required |
Description |
||||||||
Step 1 |
Vendor Number |
Yes |
This is a unique EDI number generated by the Retailer for each of their Suppliers, to transact via EDI. CIN7 Omni will use the Vendor number to configure the EDI connection with the Retailer. |
||||||||
Step 2 |
Technical Contact Email Address |
Yes |
The Retailers’ technical contact in order to perform compliance testing. |
||||||||
Step 3 |
Additional Notes/Requirements |
No |
|
||||||||
Step 4 |
GS1 Prefix |
No |
As a Supplier, do you use GS1-purchased barcodes? If yes, please provide the first 7 digits of the barcode, referred to as the “prefix”. |
||||||||
Step 5 |
Product Setup |
Yes |
|
||||||||
Step 6 |
Workflow |
Yes |
|
If multiple workflows are required with the same retailer, each would require a separate EDI integration.
In the event that Cin7 Omni find that we have not integrated with the specific Retailer, Cin7 Omni will advise and the following may be required:
The EDI standard used to trade with this retailer. For example, EDIFACT or X12.
Required messages to be transmitted via EDI. For example, common messages include Purchase Order (850,) ASN (856,) Invoice (810.)
EDI examples of the required messages.
Technical considerations
Scenario |
Supported |
Note |
Build EDI integrations via APIs as a method of communication. |
No |
The required EDI file formats are not provided through this method. |
Support for non-standard trading systems, for example using XML standards. |
No |
|
Sending product catalogue to Retailers, for example PRICAT. |
No |
|
Using a 3rd party EDI Integrator (VAN) on behalf of the customer (supplier). |
Yes |
There may be additional costs from 3rd party suppliers to perform compliance testing. |