API vs CSV File Drop

The most common interface with MYPOS Connect is for SalesOrders coming in to the system. This is typically sales from a website(s), an ERP system, a third party delivery system such as E-bay or Amazon, or third-party POS systems. 

The ideal method for interface to MYPOS Connect is always the API. However, as well as the API method for adding data we also offer a CSV file drop method where a CSV file can be uploaded. The CSV file can contain none, one or many sales orders and none, one or many customer details. 

IMPORTANT!! However, the CSV file drop method should be used only where an interface with the API is simply not feasible as the CSV file drop has a number of disadvantages which are reviewed below.

The ideal method for interface is always the API and this is because the API verifies data before it can be added, for example the length of a customers address or a postal code or phone number.

A CSV file can contain any data and, if that data is invalid then the whole CSV file will be excluded, and the issue will need to be resolved and the file resent. This adds administration to the sales order drop process which should be avoided where there is a high volume of orders.

For example:

A CSV file containing a product code that is invalid will be rejected. The CSV file will be returned to the sender for fix via email.

 vs.

 For the API, an invalid Product Code would only invalidate one sales receipt. Ideally the products were retrieved from the Products API in the first place so an invalid Product Code should be harder to have.

IF you are still looking at CSV File Drop as the only method then please read the attached and setup a call with the MYPOS Connect team to discuss access to the SFTP servers for secure file drop.