Real-time product data sync for shops and marketplaces

Friday, 17:00: a popular item has just sold out in your shop. But the export to bol.com and Amazon only runs at 03:00 tonight. For ten hours you keep selling stock across three channels that no longer exists.

Monday you start cancelling. And every cancellation pushes your pre-fulfilment cancel rate towards the threshold above which Amazon takes away your Buy Box and eventually your account. Meanwhile a price your supplier raised yesterday still sits stale in your feed, and Google flags your ad as disapproved over a price mismatch. None of this is your mistake. It is the gap between two exports.

The nightly window: where your money leaks away

A nightly import feels safe because it is predictable. But by definition it creates a blind window of hours in which your storefront and your warehouse disagree. According to industry analyses from the likes of Silk Commerce and Boomi, that is the leading cause of overselling: not bad software, but the time between two synchronisations.

Three things happen at once inside that window. You sell stock that no longer exists. The price on your landing page differs from the price in your feed. And your cancellations pile up towards the hard thresholds marketplaces enforce. The fact that the window is quiet and invisible is exactly what makes it expensive: you only see the damage once the orders are already in.

Batch versus real-time: it is a risk question, not a speed question

The reflex is to assume batch is simply too slow and that faster is always better. That is not quite right. A real-time stock synchronisation is in fact more dangerous than a nightly export the moment there is no quality gate in between. A bad supplier line, a price of zero euros, a DIM_MM of 620x820x450 that comes in as 6208204 by accident, then goes live on your shop and all your marketplaces within seconds.

So the question is not batch or real-time. The question is: how do you get real-time speed with a safe brake on it.

What marketplaces really demand from you in 2026

The thresholds are concrete and they are getting stricter. Amazon requires your pre-fulfilment cancel rate to stay under 2.5%, meaning at least 97.5% of your orders without a seller-initiated cancellation. Go above that and you face warnings, loss of Buy Box eligibility and possible suspension. Every overselling cancellation counts.

In the first half of 2026 bol.com is replacing the performance score with the quality score as a factor for the buy block: a weighted average of five service standards (on-time delivery, cancellations, Track and Trace, returns, customer questions), measured over 22 weeks on a scale of 0 to 100. Bol expects at least 98% of orders to be delivered on time, and a product that is out of stock quickly loses its search position.

Google Merchant Center pre-emptively disapproves products the moment there is a price or availability mismatch between your feed and your landing page. Googlebot only restores the status once feed and page match again. Precisely the difference your nightly window produces.

How a safe, read-only real-time product data sync works

There is an important design difference between polling and pushing. With polling you ask every few minutes: has anything changed? That is slow and it loads your systems. With pushing you get a notification the moment something changes. Amazon SP-API explicitly recommends those push notifications: an event typically arrives within about a second. The Listings Items API also has a priority lane for critical price and stock updates, while bulk feeds land in the queue during peak. Send too many requests and you get a 429 error.

Just as important: where does the logic sit? We put no computation in your shop. The connector to your webshop is read-only on the source side and only writes the result back. Your WooCommerce or Magento stays clean, with no scripts you get to debug again at the next update. See our connectors for WooCommerce and Magento 2 (Shopify, Akeneo and other platforms we build on request).

Two-way sync: from supplier source to golden record

A good connection is more than a pipeline from A to B. Stock and orders run both ways: your supplier delivers stock and price, your channels feed back the sales that draw down your stock. In between there should be one clean truth. We consolidate every source into one clean golden record per product, and that record feeds your shop and all your marketplaces at the same time, each in the right feed format for Bol, Amazon and Google. That way the price on your landing page can no longer differ from the price in your feed, because it is literally the same value.

That golden record is also where enrichment lands. See how AI enriches your product data before it goes out, so you publish not only fast but also complete.

Speed counts for Google too, not just your feed

Real-time data is half the story. Your page also has to load fast. According to Google (web.dev), a good Largest Contentful Paint is 2.5 seconds or less, measured at the 75th percentile; between 2.5 and 4.0 seconds is needs improvement, above that poor. Current data on a slow page still sells badly.

And data quality hits you harder than many people think. Consumer research from Akeneo (2025, 1,800 consumers across 8 countries) shows that 40% of consumers have returned a product because of incorrect product information, and 53% abandoned a purchase because the data was wrong. The share dissatisfied with the completeness of product data has more than doubled since 2023: from 13% to 30%.

Where you can start today

You do not have to overhaul your entire setup at once, and you are not starting from zero. SyncRefine reads in your existing shop structure and builds on it. See how SyncRefine reads your sources in and syncs them out, and pick a channel where the nightly window hurts you most right now. Put the real-time product data connection with a quality gate on there, measure your cancellations and your feed disapprovals, and only expand once it stays quiet.