Faster stock sync narrows the window in which two channels sell the same units. Only one reservation authority, or a deliberate split of stock, closes it.
You sell the same physical stock through more than one channel: an online store and a wholesale team, or a shop plus a marketplace or two. Someone has noticed that two channels can each sell the last units, and you are now looking at multi-channel inventory software that promises to keep the numbers in sync. The question that decides whether you oversell is which system accepts or refuses a promise, and how the other channels find out.
Synchronising totals copies a number from one place to another without deciding anything. Until the business defines what “available” means and names the one place where a promise is accepted or refused, a faster copy only shortens the time in which two channels can sell the same units.
Four words to keep separate
The published inventory process guide explains stock records in full, so the definitions here are short. On hand is what is physically in the building. Held is stock you have but cannot sell yet, such as units awaiting a quality check. Reserved is stock committed to orders you have already accepted. Available to promise is what remains for new orders once holds and reservations are subtracted, and it only means something under a declared policy.
A displayed quantity is a snapshot
When a channel shows 35 available, that figure was true at the moment it was sent. An order placed against it is a request. It becomes a commitment only when the system that owns the stock record has accepted it and recorded a reservation.
The time between one channel accepting an order and every other channel learning that availability has fallen is the oversell window. If your channels copy totals every fifteen minutes, the window is up to fifteen minutes long. Copy every minute and it is up to a minute. Two orders can arrive inside a minute, so the window shrinks and never closes. Closing it takes one place that makes every reservation decision, or a division of stock in advance so that channels never draw on the same units.
Three ways to decide, with one afternoon of orders
The example that follows is illustrative. A wholesaler holds 50 units of one item. Twelve are reserved for existing wholesale orders and three are held awaiting a quality check, so under its policy 35 are available to promise. Its online store and its wholesale team both see 35. During one afternoon the wholesale team enters an order for 25 and the online store takes an order for 20. Each request fits inside the 35 displayed. Together they need 45. Real policies add safety stock, incoming supply and channel priority rules; they are left out here.
Shared reservation authority
Every channel’s order asks one system to reserve stock and receives an answer: accept, partial or decline. The wholesale order reaches the authority first and reserves 25, leaving 10. The online order for 20 arrives next, and the authority applies the policy to 20 requested against 10 available. The policy might accept 10 and backorder 10, accept 10 and decline the rest, or decline the whole order. Whichever it is, the people who took the second order know immediately.
Step | On hand | Held | Reserved | Available |
|---|---|---|---|---|
Start of the afternoon | 50 | 3 | 12 | 35 |
Wholesale order for 25 reserved | 50 | 3 | 37 | 10 |
Online order for 20: 10 accepted, 10 backordered | 50 | 3 | 47 | 0 |
Online customer cancels; the accepted 10 released | 50 | 3 | 37 | 10 |
Every channel must wait for the authority’s answer before confirming an order, so the authority has to be available whenever any channel is trading.
Channel allocation
The 35 is split in advance, say 20 for wholesale and 15 for the online store, and each channel sells its share without asking anyone. The wholesale order for 25 is 5 short at entry. The online order for 20 is 5 short at entry. Nothing is oversold and nobody waits for a shared system. On this afternoon both shares were used up, so the total served is the same 35 either way. On a quieter day for the online store, the 15 would sit unsold while the wholesale team turned a customer away, and someone would need a rule for moving stock between shares.
Sync only
Each channel keeps its own count and copies the total to the others every fifteen minutes. Both orders are accepted, because both fitted the 35 each channel could see. The business has promised 45 units against 35 it can supply, and the first person to find out is whoever starts picking. Add both orders to the original 12 reserved and you get 57 reserved against 50 on hand with 3 still held. Available would be minus 10, except that no single system is holding those numbers together.
Hybrid
A hybrid allocates the bulk of the stock and keeps something shared: a small common pool either channel can draw on once its share is gone, or a per-channel buffer that is never offered for sale. It trades some stranded stock for some of the authority’s complexity, and the shared pool still needs a single owner.
What happens when the online customer cancels
Later that afternoon the online customer cancels the 10 units the store had accepted. Under the shared authority the reservation is released and the 10 return to available for every channel at once, as the last row of the table shows. Under allocation they return to the online share only, and the wholesale customer who was cut short stays short unless someone moves them across. Under sync only, the release depends on which figure overwrites which: if a stale copy from the wholesale system arrives a moment after the online store’s corrected total, the 10 disappear from view until the next count catches them.
Cancellations are one of several cases the deciding system has to handle. A channel may take a reservation and then fail to confirm its order, so the reservation needs a timeout or a manual release. An update may arrive out of order, so the system needs to know which message is newer rather than trusting whichever landed last. A channel’s own count will sometimes disagree with the authority’s, so someone needs a screen that shows the difference and a way to record which is right.
Questions to put to any multi-channel inventory vendor
Whether an integration is reliable comes down to what it does when something goes wrong, and an answer that amounts to “it syncs quickly” tells you nothing about that. Five questions get most of the way there. Where exactly is the reservation made, and does every channel go through it? What happens to a request that arrives during a delay or an outage, and does the channel know it is waiting? How is a cancellation returned, and how quickly does the released stock become promisable elsewhere? What happens when a channel rejects an update, for example because a listing has changed? And what does the person sorting out a conflict see: the orders holding the units and the reason the later request was cut short, or a single total that hides all of it?
When a fixed split or an existing system is enough
A small operation with two channels and steady demand can run a fixed allocation from a spreadsheet and a weekly rebalance, and should try that before buying anything. Many commerce and order management products make the reservation decision in one place perfectly well for a standard channel mix. If yours does, you have the authority already, and the remaining work is making sure every channel uses it. Before talking to any vendor, name which of the three designs your business is running today. If nobody can point to the place where a promise is decided inside the delay, the honest answer is sync only.
Where Keel fits
Keel is an operations platform shaped around how a business needs to work. For the wholesaler in the example, that means the promise rule, the reservation decision and the view of on hand, held and reserved stock live in one operational system that the team can see and change. When the online order for 20 is cut to 10, the person answering that customer sees the wholesale order holding the other 25 and the rule that produced the result. When the business changes its policy, perhaps giving wholesale priority during a launch, the rule and the screens people work in change together.
The channel integrations call the same reservation action the team uses, so a marketplace order and a wholesale order typed in by hand are judged by one rule. Keel supports tailored operator tools, workflows that combine human steps with processing, and business rules expressed in code. The implementation must define and test the reservation behaviour, what happens on delay or failure, cancellation handling, retries and reconciliation, and the authentication and mapping for each channel. Keel does not ship a ready-made connector for any particular store or marketplace, and nothing prevents overselling automatically; the policy your implementation defines does the deciding, and it has to be tested. Keel leads the implementation and agrees the handover with your team.
Keel is the right conversation when the availability policy, the channel mix or the operator experience needs to be your own and needs to keep changing. Bring one real sequence of conflicting orders and your current rule for what each channel may promise, and we will talk through who should own availability in your business and whether Keel fits.
