This article's intention is to be sent to the entity configuring the EDI documents to know how to configure the correct item field data to be compatible with Cloud Retailer.
This article will discuss how Cloud Retailer processes EDI documents and how they should be configured for Cloud Retailer. Below is an example of a product, in an EDI file, that is using BO as the unit of measure code. There are instances where this code is used to define both a single unit and a case unit.
For Cloud Retailer, it is preferred that all products use one of two units of measure codes, CA to define a case unit and EA for everything else. This will ensure inventory accuracy when parsing these files into Cloud Retailer.
How does this process work?
When a supplier creates an order, the EDI file created is sent to Fintech for processing. Fintech will process the file before they send the EDI files to RITE. Cloud Retailer runs a process several times a day to scan for newly received EDI files and will parse all new files into separate POs. The POs created will assign a single unit or a case unit to each PO line item based on the data from the EDI files.