In this guide 6 sections
Omnichannel inventory means one stock ledger that every channel reads and writes. The shelf count, the till and the website all draw from it. Returns, reservations and transfers post as movements, and each channel follows a sync rule that decides how much stock it may sell.
Why three counts never agree
Your shelf says four. The till says five. The website says two. None of them is lying. Each one reads a different moment in the life of the same stock.
The till updates when the cashier scans. The website updates when an order is placed, or when an overnight file finally runs. The shelf changes when someone lifts a jacket and walks off with it. Gaps between those moments breed drift.
Add a click-and-collect shelf, a marketplace listing and a returns bin, and you have six places where a single jacket can be counted differently. Nobody has made a mistake. The system simply has no single place to hold the truth.
Where the drift comes from
Most mismatches trace back to a handful of events. A return is accepted at the counter but never put back on the shelf. A web order reserves a unit that a store customer then buys. A transfer leaves the warehouse and is counted at neither end for two days.
Unsynced orders are the quietest cause. A marketplace order drops in by email, someone keys it by hand next morning, and the same unit sells twice in between. The customer gets an apology. You lose the sale.
- Returns accepted but not restocked
- Reservations held for web carts and click-and-collect
- Transfers in transit between branches
- Marketplace orders keyed late
- Damaged or tester units still counted as sellable
One ledger, many views
The fix is not a faster sync. It is a single ledger where every change is a movement with a type, a quantity, a location and a time stamp. Sale, return, transfer out, transfer in, reservation, release, damage and count adjustment are the usual types.
Each channel reads a view of that ledger. The website sees available stock. The warehouse sees on-hand stock. The buyer sees stock plus incoming purchase orders.
Because every view comes from the same movements, a disagreement traces back to one line.
A sync rule for each channel
Not every channel should sell every unit. Many retailers hold back a small safety buffer on the website for the last pieces, so a till sale never collides with a web order. Others reserve a fixed quantity for a marketplace and release it if it has not sold by Friday.
Write the rule down for each channel. It names the locations that feed it, the buffer kept back, how quickly changes must reach it and what happens when stock goes negative.
Keep exceptions few. A rule nobody can recite at the stock desk will not be followed.
- Which locations feed the channel
- Safety buffer held back
- Maximum delay before a change reaches the channel
- Handling of negative stock
- Owner who approves changes to the rule
Count to prove it works
A ledger is only as honest as its last count. Pick one aisle each week. Count it blind, without looking at the system figure.
Post the difference as an adjustment with a reason code such as damage, return error or late transfer. After a month the codes show a pattern. If most variances come from returns, fix the returns desk.
If they come from transfers, fix the transfer note. Either way the next step is a small, named change at one desk, reviewed again after the following month’s blind counts.
Channel stock rule sheet
Rows on this single sheet cover each sales channel: store till, website, marketplace and click-and-collect. Columns list feeding locations, safety buffer, sync delay, negative stock handling and rule owner. A second block holds a weekly blind count log with aisle, counted figure, system figure, variance and reason code.
Open a blank worksheet to printQuestions owners ask
Do I need real-time sync between store and website?
Only for fast-moving or low-quantity items. A short delay is fine for deep stock. Set the delay per channel, and keep a buffer on the last few units of anything popular.
What is a stock reservation?
A reservation holds units for an order that is not yet picked or paid, such as a web cart or a click-and-collect request. It lowers available stock without lowering on-hand stock.
Can a spreadsheet act as the single ledger?
For one location and one channel, yes. Once two channels write to it at the same time, edits collide. The figures stop being trustworthy.
How do returns fit in?
A return is a movement. It restores stock only when the item is inspected and shelved, so give returns their own inspection status before they become sellable again.