# Warehouse sync and ERP integration

URL: https://tnb-tech.com/en/services/warehouse-sync/

> Warehouse sync links your online store to your stock system: stock, prices and promotions arrive on a schedule, and orders go back without retyping.

The last unit sells over the counter and online in the same hour. Who gets it? Warehouse sync, the link between your online store and your stock system, decides by rule, not luck: the warehouse holds the stock and the prices, and the store sends every order back. It suits retailers with a physical shop, B2B wholesalers and large catalogues whose prices change often.

Connections like these have their own case studies. Warehouse software itself is a separate service: here we connect your store to the stock system you already run; there it is our own software. At Radans, a food distributor, the B2B store syncs with the stock system twice a day: products, categories, prices and promotions come in, and every order goes back. At Elektrokomers 68, an electrical-supplies trader, a catalogue and admin panel, built without an off-the-shelf CMS, are fed by an external stock system. For Zdradech, a metals trader, we wrote warehouse software built to run only on the company network.

We settle four things before go-live, not in the middle of an incident. The interval: as often as your stock moves — more often only adds load; at Radans, twice a day. The mapping: which warehouse code matches which product, and which field wins — price and stock from the warehouse, photos and text from the store. The window between runs: the store sells from the last known stock; on a mismatch, the warehouse wins. The failure: the store keeps the last good data, an alert shows us the record the run stopped on, and no catalogue is wiped over one failed run.

The data in the store and the warehouse stays yours, and both systems’ credentials are in your name. The terms for the connection’s code are set out in the quote. If your stock system changes its export, the people who wrote the connection adjust it, with no plugin vendor to wait for.

Every connection starts with an audit of what your stock system can export. If you have no store yet, online store development on the T&B platform builds one connected to the warehouse from day one. What moves the price is on the pricing page.

## What is included

- Audit of the stock system — What your stock system or ERP can export — an API, a regular file or the database itself — and how often, before we promise anything.
- Stock, prices and promotions — Products, categories, stock and promotions update on a schedule, and the store shows prices from the warehouse, not prices typed in by hand.
- Orders back to the warehouse — An order placed on the site goes back into the stock system on its own, with nobody retyping it. At Radans, every order does.
- SKU mapping — Which warehouse code matches which product when the two systems name them differently, and which field wins on a conflict. Documented, and yours.
- Schedule, watch, alert — How often the sync runs, what happens when a run fails, and who is told. The store carries on with the last good data.
- Catalogue and admin panel — Where synced products get their photos, descriptions and place in the catalogue, with access set by role for each member of staff.

## How it works

01. 01 The data — We look at what the warehouse exports: fields, format, frequency, who holds the truth.
02. 02 The mapping — We agree which field answers to which, and which one wins on a conflict.
03. 03 A parallel run — The sync runs alongside the manual process, and we compare the numbers item by item.
04. 04 The switch — The hand reconciliation stops; the schedule, the watch and the report stay.

## Results

- 2 × syncs a day — Radans — products, categories, prices and promotions; orders flow back automatically

## Questions and answers

**What happens when the last unit sells over the counter and online in the same hour?**
When the last unit sells over the counter and online between two sync runs, the warehouse wins: the count in the stock system stands, and the online order reaches it like any other. The sync runs on a schedule, so between runs the website sells from the last known stock, and a mismatch can happen. Who gets the last unit is decided where the stock count is — in the stock system.

**Will it work with the stock system we already have, or do we need a new one?**
You do not need a new stock system: warehouse sync works with any stock system or ERP you already run — through an API, a regular file or direct database access. We check what and how yours exports, and the connection starts from there. The stock system stays in charge: products are maintained there only and reach the store with the next run, which is how Radans works.

**How often does stock in the online store update from the warehouse?**
Stock in the online store updates from the warehouse on a schedule you choose. At Radans the sync runs twice a day. More often is not automatically better: the interval should follow how fast your stock and prices change, and every extra run puts load on both systems for the same number.

**How are products matched when the warehouse and the store name them differently?**
Products are matched through a mapping table: which warehouse code matches which product in the store, and which field wins on a conflict. A shirt in three sizes, for example, is one product with three variants in the store and three separate codes in the warehouse; the table ties them together. As a rule, price and stock come from the warehouse, photos and descriptions from the store. The table is agreed before go-live, documented, and yours.

**What happens if the sync stops?**
If the sync stops, the store keeps running on the last known data. We get an alert and can see which record the run stopped on; no catalogue is wiped because one run failed. That is why the schedule, the monitoring and the failure alert are part of the job.

**Can a B2B wholesale store show prices to business customers only?**
Yes — a B2B store for wholesale can show prices and take orders from business customers only. Radans, a food distributor, runs its store this way: full functionality and prices are visible to corporate customers only, and each of their orders reaches the warehouse without retyping. Prices can also differ per customer: they come from the stock system when it holds them, or are set in the store — we settle that in the data audit.

**Who owns the connection between our store and the warehouse if we switch developers?**
The data in your store and your warehouse stays yours, the SKU mapping is documented, and the credentials to both systems are in your name. The terms for the connection’s code are set out in the quote. If you switch developers, the new team starts from a documented mapping, not from scratch.

**How much does warehouse sync cost?**
The price of warehouse sync depends on what your stock system can export and how many fields have to be mapped. That is why the audit comes first; after it we quote the whole scope. Each connection — warehouse software, accounting, couriers, payments, ERP — is its own job and is quoted on its own; what moves the number is set out on the pricing page.