Frequently asked questions
We want to get data that is as up to date as possible. That is why most POS systems that integrate with us provide stock information at least once an hour. The more often, the better.
Yes please! Uploading stock lines for barcodes that have a quantity below 1 is a signal to our system to mark these products as out of stock immediately.
If you don't include out of stock products, we will only mark barcodes as out of stock once we haven't seen that barcode in any stock upload for more than 7 days.
Each store location will get a unique FTP password, also known as an 'Upload Key'. You upload a separate stock.csv file for each location.
Yes, we can only accept products which have a price set. We'll automatically discard rows in the CSV with an empty value or
0as the price.
Our general rule of thumb for pricing is this: What would you pay for this product if you went in store and bought one of this item right now?
- Include any applicable VAT
- Include time/date-base discounts in the price you send to NearSt whenever possible
- Don't include quantity-based discounts (2-for-1, etc.)
The NearSt FTP Gateway supports both active and passive mode FTP connections. Use the one that works best with your FTP client library, and consider that passive mode FTP connections potentially require firewall exceptions for more than only port 21.
Yes, we do support FTPS! Whenever possible, please enable TLS. This further protects your connection with our servers. We don’t currently support SFTP.
For FTPS, we support both TLSv1.2 and TLSv1.3.
When you upload your first file to our server, we’ll automatically create a file called
upload_log.txtthat shows information about your most recent upload.
You'll also be able to see processing information about the latest stock upload in our Partners dashboard.
Your CSV file should be UTF-8 encoded, using UNIX or Windows style returns. If it isn’t, we’ll try our best to convert it for you. In most cases this means you don’t have to worry about this.