Stock is held in one place, and the shops and marketplaces copy it.
VertaStream connects your warehouse system, your ERP and everywhere you sell. An item that sells stops being offered everywhere else: in your own shop in under two seconds, on the marketplaces as soon as they accept the update. The sync runs in real time and is sized for catalogues with tens of thousands of items and dozens of suppliers.
Your warehouse system
VertaStream engine
Shops & marketplaces
Every stock movement reaches your own shop in under two seconds, and the marketplaces at the speed they accept updates.
Updated in seconds, not once an hour
Every stock movement goes out the moment it happens, not with an import once an hour. Your own shop shows it in under two seconds, and each marketplace as soon as it accepts the update.
Several warehouses, nothing sold twice
VertaStream splits stock across your warehouses and the places you sell, using reservation rules. Each one gets a buffer sized to how fast it accepts updates, so one marketplace cannot sell a quantity that is already reserved elsewhere.
Supplier files, cleaned up
XML and CSV files from dozens of suppliers arrive in different formats and land in one catalogue: normalised, deduplicated, attributes mapped.
Orders reach the right warehouse
VertaStream routes every order to the warehouse or supplier that will fulfil it, and records a full audit trail from checkout to dispatch.
The safety net and the answers.
VertaStream moves the data and VertaPilot enters it. VertaShield holds back suspect changes before they reach the shops and marketplaces, and VertaScope shows what each item and each place you sell earns.
VertaShield
A check before the change, a record after it.
- A supplier file that would zero the stock on 40,000 items does not go through. The sync stops and the change waits for confirmation before it reaches the shops and marketplaces.
- Every price and stock change is kept, so a bulk update that went wrong can be rolled back to how things were a minute earlier.
- Every action is recorded with the person, the time, and the value before and after it.
- If a supplier stops sending files or a marketplace starts refusing requests, you hear about it the same day rather than at month end.
VertaScope
Margins by shop and marketplace, turnover, and stock that is not moving.
- Which items have not sold, which warehouse they are sitting in, and how much money is tied up in them.
- What is left on the same product in each shop and marketplace after they deduct their fees.
- How fast each item turns over, by season, so restocking is a decision rather than a guess.
- Which products search engines have indexed and which they have not.
Our work up close.
Automotive parts distribution
Problem
The client ships car parts from five warehouses across Germany, Poland and the Netherlands. Each warehouse kept its own stock list, and the online shop was updated by a file import once a night. By morning the numbers were already wrong: customers were ordering parts that had been sold the previous afternoon, and someone had to call them back to apologise.
Solution
We connected all five warehouses to VertaStream. Stock now moves as events. A part leaves a shelf in Hamburg and the shop knows about it in under half a second. Even in the slowest five per cent of cases it takes under 1.4 seconds. Reservation rules hold a small buffer for each shop and marketplace so two customers can never claim the same part, and every order is routed to the warehouse that can actually ship it.
Results
Home goods retail
Problem
One warehouse, a shop and two marketplaces, and no agreement between them. On busy weekends the same lamp was sold on Shopify, Amazon and bol.com within the same hour. The team spent Mondays cancelling orders and writing apologies, and the cancellation rate on both marketplace accounts was climbing towards the two per cent ceiling bol.com allows before it restricts a seller.
Solution
VertaStream now owns the stock and lends it to the shop and the marketplaces rather than the other way round. Each of them gets an allocation with a small buffer held back during peak hours, and the moment something sells anywhere, VertaStream stops offering it everywhere else immediately. The shop follows within a second, bol.com usually within fifteen minutes, Amazon as soon as its feed queue allows. The Monday morning cancellation ritual stopped completely.
Results
Fashion e-commerce
Problem
A catalogue of more than 100,000 products fed by 38 suppliers, each sending data in its own format and its own idea of what a product name is. The old platform needed hours to import a single feed, duplicates piled up, and adding a supplier meant writing another one-off script that only one person understood.
Solution
We rebuilt the whole thing on a platform where this size is normal. Supplier feeds are normalised and deduplicated on arrival, attributes are mapped automatically, and the whole catalogue rebuilds inside VertaStream in six minutes. Each shop and marketplace then receives the changes as fast as its own API allows. Adding a new supplier is now configuration, not a development project.
Results
The first step is a short conversation.
We reply within 24 hours. A detailed brief is not needed beforehand.