Electronic Data Interchange (EDI) is the system-to-system exchange of business documents in a standard electronic format between business partners. Common EDI providers are SPS Commerce, True Commerce and CommerceHub. Once configured, InterFulfillment/Extensiv Warehouse Manager can efficiently populate orders and receipts into the portal over the API. We would handle the acknowledgement as well. We can then push back the ASN, inventory, and generate an invoice in the EDI portal.
This article answers a few basic EDI questions that should help you understand how to get started with establishing an EDI connection.
How do I start an EDI integration with Extensiv/InterFulfillment?
To set up an EDI integration, the following information needs to be sent to support@interfulfillment.com:
- Contact information for all parties involved including your EDI provider representative
- What are you looking to achieve with this connection? Try and articulate how this integration will work. What systems are involved? (ERP, Shopping Cart, Retailer, etc.)
- Which trading documents and format are required for the connection? Will you be using the Extensiv standard formats attached to this article? Will you be using your own? If using your own, please have samples and documentation.
- Who will be developing to whom? Is Extensiv/InterFulfillment needed to create a custom integration? Will you be using a third party or will you map to Extensiv/InterFulfillment?
- Is this is a retailer or non-retailer connection? Are you required to print specific labels, packing slips, etc.?
- What is the delivery method of the trading documents? Will you be using SFTP or FTP?
- Are there UCC-128 label requirements? If they are required, for which retailers? (Amazon, Walmart, Macy's, etc.)
Once this information is submitted to support@interfulfillment.com , our customer service department will complete the Extensiv EDI Survey and their Development Services team will reach out within 2–4 business days to schedule a scoping call.
Which EDI documents and formats are accepted?
In general, EDI is traditionally accepted in X12 format, which can include CSV, Tab-delimited, or XML. However, current trends are moving towards using an XML formatted EDI file, as this layout allows for the most flexibility and the least amount of development work.
We highly advise utilizing our XML file format since it is the most robust. XML allows for new tags to be added, as it contains the built-in saved element function for all EDI needs. All other files will require you or your customer to complete a gap analysis to confirm our standards meet all business needs.
Our standard file formats are listed below with the associated EDI transaction numbers. You will need to send these to your customer so they can complete a gap analysis to determine if our formats meet all of their unique business needs. If our formats do not meet their requirements, a custom developed parser is needed, which our EDI team can help with.
EDI Transaction Set |
X12 File | XML File | Flat File |
---|---|---|---|
846 – Stock Status (Export) |
Sample / No Spec |
N/A |
|
940 – Order > Create (Import) |
|||
943 – Receiver > Create (Import) |
|||
944 – Receiver > Received (Export) |
|||
945 – Order > Shipped (Export) |
|||
997 - Functional Acknowledgement (Export) |
N/A |
||
|
|
How long does an EDI integration take?
This all depends on the EDI file layouts and which party will be taking care of the development. If 3PL Central is required to create a custom integration, we typically quote 3–6 weeks for end-to-end testing with all parties to begin. Note: SLAs have temporarily been extended to 8–10 weeks.
Once testing begins, small changes or updates may be required before we will have user acceptance from all parties. If you are using one of our pre-wired third-party partners or you will be mapping to the 3PL Warehouse Manager layouts, testing can begin within a couple of business days.
Where can I get more information?
Any questions regarding EDI integrations that aren't here should be sent to support@interfulfillment.com.