Importing retailers flat files

Reference 

• Full file template: download file template / see in Google Drive
• Data flow: from ERP to LNB
• Data types: retailers, buyers
• File naming: see retailers in the flat files automation instructions

File requirements

If a row does not meet all these constrains, it will be ignored:

• country must be valid (ISO 2-letters) 
• price list must be valid
• sales admin email must be valid
• sales rep email must be valid
• if buyer email column is provided, a "retailer name + retailer country + buyer email" combination must be unique in the file, only the first row will be processed
• if buyer email column is not provided, a "retailer name + retailer country" combination must be unique in the file, only the first row will be processed

File processing rules

Retailers and buyers can be sent along within one CSV file. Each row of the file carries a combination of a retailer(identified by its reference) and a buyer (identified by its email).  A CSV file can therefore contains the same retailer on multiple rows with a distinct buyer on each row.

Retailers import via CSV files works in "create or update" mode:

• Retailer matching
  • if the Reference column is provided, it is used for retailer matching
    • if the reference is registered in your Le New Black data, the related retailer is updated.
    • if not, the retailer is created
  • if the Reference column is not provided, then the Name+Country composite key is used for retailer matching
    • if the Name+Country combination is registered in your Le New Black data, the related retailer is updated
    • if not, the retailer is created
• Buyer matching
  • if the buyer email is registered in your Le New Black data, it is updated
  • if not, it is created

File schema / Main fields (full schema: see in Google Drive)