Kosmos eSync helps businesses maintain data integrity by not storing data in the middle during synchronization

Just about every business and consumer has experienced an issue with data synchronization. The latest issue with Amazon really caught my attention. On Friday Dec-12-2014, Amazon UK sellers experienced a pricing glitch that affected up to 75 million products. Items ranging from smartphones and tablets to mattresses and TV’s, all sold for a penny. Some Amazon sellers that were unable to cancel the orders in time lost their entire inventory. Since Amazon was fulfilling orders directly, the orders were picked, packed and shipped out by Amazon as soon as the orders were placed. The Amazon sellers that were affected used a 3rd party application to automatically sync and update prices in Amazon in order to maintain competitive prices. The sellers that used the centralized data management application called RepricerExpress have lost thousands and some now claim they face potential bankruptcy as a result of the error. If you store data in a centralized data management application you should be aware that data integrity issues can happen. Storing data in a middleware application with other businesses can potentially introduce cross-contamination issues when trying to sync data. For example, an online toy store could display camping and hunting gear for sale on their website as a result of cross-contamination issues when syncing data with a application that stores data from multiple business accounts. Below is a diagram that outlines how a typical centralized data management tool works when syncing data between applications. First a copy of the data is stored in the centralized application before the data is sent to its destinations. Just like introducing too many chefs in the kitchen,...