What does this section deal with ?
This section deals with the EDI server responses when your file is checked, validated prior to adding to the system. These are designed for customers of the warehouse to be advised of an issue with their EDI document.
If you are using the API then there are other responses you will receive prior to this which are API responses and not covered in this section.
What is the process
The process of checking and passing the information into the WMS is fully automated, there is only a need for the warehouse to become involved if the data sent has any issues identified in stage 3
Process
The EDI message is sent to the warehouse
File validation takes place (File check)
Failure is rejection of file and email sent to customer
Pass means stage 3
Order validation takes place (Item check)
Order is placed into warehousing either
Orders Held
Awaiting Picking
What do we check
As is normal industry practise we validate information we are sent to ensure that it meets the requirements, we have a multi tier approach
API validation (only if using the API)
Initial Message validation - failure at this point would have the message completely rejected.
Item validation - failure of something within the file which means the item will have to be manually dealt with.
It is not possible to code for every possible issue an inbound file may cause and sometimes error messages are not helpful, but they should be sent to the warehouse customer services to deal with further.
What do we notify you for ?
Noitifications are sent to the customer by the system (however the warehouse have to enter a valid single email address for each customer in order for you to receive it)
Initial receipt of the file notification (this is optional and normally not switched on)
Notification of any issues within the file or contents (you will always be sent this)
How do we know if the order is available in the WMS
Once the file is loaded into the warehouse system you can then request an orders processed report which confirmed what the orders received were and what was processed on them.
Examples of emails
These emails examples are sent by the EDI system to customers, it is fully automated
Example Email | |
|---|---|
Confirmation of Receiving. This is just our system saying we have something to process. At this point we have not checked or validated the information in the file. |  |
File Failure This is a complete failure of the file. The file will not be processed and is usually due to a complete failure of the information in the file. You should not resend, but contact the warehouse for assistance however most of the time you have to speak to your own developer to resolve this. |  |
Item Failure There is a problem with a line on your order or some details of the order header are incorrect. |  |
Using the API
This section deals with the EDI server responses when your file is checked, validated prior to adding to the system. These are designed for customers of the warehouse to be advised of an issue with their EDI document.
If you are using the API then there are other responses you will receive prior to this which are API responses and not covered in this section.