The website shows one remaining piece. A colleague is holding that piece for a customer in the shop, while another has moved a similar variant into the window. No one has made an unreasonable decision, yet the stock position has become unclear. The issue begins with rules that exist in people’s heads instead of a shared process.
Before changing software, define what your shop means by available stock. Count physical pieces, but also identify which can actually be promised to a customer. Reservations, condition questions, display commitments and transfers need consistent treatment across the team.
At a glance
- Define what available stock means before changing software.
- Record sales, reservations, transfers and holds consistently.
- Resolve discrepancies at the product-variant level.
In this guide
- Give each quantity a clear meaning
- Write down the events that change availability
- A hypothetical last-item test
- Make reservations finite and visible
- Use a short reconciliation routine
- Keep buying decisions connected to real availability
Give each quantity a clear meaning
For your internal process, distinguish physical stock from stock available to sell. Physical stock describes what is present in the relevant location. Available stock reflects the units that can be committed under your shop’s rules. Your system may use different field names, so map the meaning before asking staff to follow it.
Do not create more statuses than the team can maintain. A small retailer may need only available, reserved and held, plus clearly identified locations. The important point is that every status has an owner, an entry rule and a way to return the item to normal availability when appropriate.
Write down the events that change availability
| Event | Required record | Follow-up question |
|---|---|---|
| Shop sale | Exact reference and variant sold | Has the shared availability updated? |
| Online order | Units committed to that order | Can the item be located and matched? |
| Customer reservation | Quantity, owner and agreed expiry | Who releases it if the reservation ends? |
| Condition hold | Item and reason it cannot be sold | Who resolves the question? |
| Location transfer | Source, destination and quantity | Which channel may offer it now? |
These are suggested operating fields, not instructions for a particular platform. Use your retail system’s documented functions and check the result in your actual setup. An integration being switched on does not prove that every variant, location or event is configured correctly.
A hypothetical last-item test
Suppose a shop has three units of one variant. One is reserved for an online order and one is held for a condition check. Only the remaining unit is available under the shop’s chosen rules. If the website displays three, the physical count may be correct while the selling promise is wrong.
Now imagine the final available unit sells at the counter. Check how that event reaches the website, who notices a failed update and what the team does while the issue is resolved. This hypothetical exercise tests the workflow without asserting how any specific software behaves or how quickly it synchronises.
Make reservations finite and visible
A reservation needs the item, quantity, customer or order reference, responsible colleague and agreed end point. Keep customer information within the shop’s appropriate records and access practices. A sticky note beside the till is easy to lose and may not inform the person preparing an online order.
At the end point, confirm whether the reservation becomes a sale, is extended by agreement or is released. Do not let a forgotten hold quietly reduce availability for weeks. Equally, do not release a genuine commitment because someone cannot immediately find the note.
Use a short reconciliation routine
Choose a regular moment to review exceptions: negative stock, unfulfilled orders, expired reservations, condition holds and recent transfers. Count the affected references physically. You do not need to recount the entire shop every time a single line is uncertain; target the discrepancy and broaden the review if the evidence shows a wider issue.
When correcting a quantity, record why. A silent adjustment may make today’s number look right while leaving the same mistake ready to recur. Repeated confusion between two variants suggests an identity or labelling problem. Repeated missed transfers suggest a handover problem. Match the fix to the pattern you can document.
Keep buying decisions connected to real availability
Before reviewing Toodobem’s catalogue for the next order, distinguish sold stock from reserved or held stock. Clarify product identities through the trade contact page when necessary. The buying decision improves when it starts from a stock position the whole team can explain.
Inventory discipline is successful when a colleague can locate the promised piece, identify it correctly and hand it over without discovering a competing commitment. A shared definition of availability makes that ordinary outcome repeatable across both channels.
