If you select this repricing method, Price2Spy will prepare a CSV file containing the products which need to be repriced (along with their new prices), and upload it to the FTP location you have specified.

Since this is an indirect repricing method, your IT would have to prepare a process that will fetch this file and apply new prices within your own database.

The columns in this file are

• productName – product name as defined in your Price2Spy account
• productInternalId – product’s internal ID, as defined in your Price2Spy account (usually used for looking up product in your own database)
• productSku – product’s SKU, as defined in your Price2Spy account (sometimes used for looking up product in your own database)
• producLinkMyStorelId – (only applicable if you have integrated your Price2Spy with your own store, using ‘Link My Store’ feature) – in this case, this is the field you should use for looking up the product in your own database
• currentPrice – current price of your product, as known to Price2Spy
• suggestedPrice – new price, as defined in Price2Spy’s repricing module
• dateRepricingRequestSent – the timestamp when repricing file was generated
• opportunityId – this is the ID of the repricing rule which triggered this price change

If you choose this repricing method, Price2Spy will prepare a CSV file containing all products to be repriced, and send it to the email recipient you have specified.

Since it’s an indirect repricing method, it’s your responsibility to apply price changes within your own database.

Please see above for the specification of the CSV file containing repricing information