Pure360 Personalisation can load product data from a file which you place on an sFTP server.

For example, the following file could be used:

"id","color","curr","price","monthly_price","deal_code","img","url","stock","name","categories"
"54321","green","GBP","34.99","32.49","201802deals","http://example.com/image.jpg","http://example.com/prods/54321","1","Test Product","Mens>Formal Wear>Jackets"

The filename must contain ‘product_import’ to be recognised as a product file.

File formats supported: TSV, CSV. We recommend that data should be encoded as utf-8, however ucs-2 can also be used. If all the characters in your data can be represented in the first 127 characters, then you can use US-ASCII (sometimes called ANSI)

Note that:

• All files in the ftp directory which match the “allowed files pattern” will be retrieved, processed and deleted from the ftp server. Therefore, the FTP account used will require read, write and delete permissions.
• You must set a wildcard such as product_import*.csv to avoid confusion with other import processes which are reading from the same FTP server.
• Normally, empty fields in the import file will be loaded and will overwrite any existing data in the field. If you want to keep existing data when no data is supplied in the import file, you can set a mapping attribute of “ignore_blank”:true. This field will then only be loaded if non-blank data is supplied in the file.

Required Fields

Field	Description
product_id	using same coded values as will be used by Pure360 to capture data from the website.

Optional Fields

Field	Description
product_id	using same coded values as will be used by Pure360 to capture data from the website.
n	Name
qty	Quantity
img	Img URL
u	Product Page URL
up	Unit Price
curr	Currency, e.g. GBP or USD
ex.color	Item color (you can access any attribute of “ex” in this way)
cat	Separated list of categories for this product
related	Separated list of product ids related this product