Introduction
CSV via FTP is the supported method for fully automated EDI ordering. Because customer data for small dealers can be inconsistent, we highly recommend Readysell hybrid EDI ordering over this approach. If you do, however, have the ability to reconcile data errors in your system after the order arrives, then CSV via FTP is a valid alternative.
Overview
Data specification
I’ve attached an example message called sample_order.csv. The formats include additional information including EZ-code, barcode and product description. We believe that it’s best to include this additional data as it can be used for validation or debugging purposes or to do manual matching to resolve data discrepancies (where required). The file is self-documenting and has 3 row types:
D = Description (describes the purpose of the rows below)
H = Header (header information, shown once per file)
L = Line (line information, repeats for each line)
Dates are expressed in ISO 8601 date format. OrderLineNumber is unique per customer ERP system, not per customer order. CustomerProductCode is usually the Office Brands EZ Code – but could be a customer’s own code if the product is set up manually. SupplierProductCode and Barcode will be included in the order where possible, but only CustomerProductCode is guaranteed.
Transport is via an FTP server at the supplier side. Customers will upload orders to the FTP server when they are placed.
Sample message
X