Guide
One Stock Figure Across Your Shop, Marketplace and Stores
Overselling across channels is rarely cured by a faster connection. One ledger, written reservation rules and a figure calculated for each channel give every order a true answer.
4-minute read5 November 2026
In Brief
- A last unit sold twice costs a cancellation, an apology and a mark against the seller. A faster sync publishes a wrong number sooner, so the cause sits in the rules.
- We see four actions: define available stock in writing, send movements to one ledger, write down the reservation rules, and publish a calculated figure to each channel.
- Thinqmesh connects the store, marketplaces, stock and accounts so an order moves without retyping. A first working store is live in four weeks, taking real orders by six.
A customer orders the last unit on a marketplace at the moment a store assistant sells it at the till. The website still shows two, because a carton was booked in before it was opened. Someone must now cancel an order and apologise. Most retailers read this as a synchronisation problem and ask for a faster integration. Our view is that speed is the smaller part. Stock is oversold when the business has not decided what available means or which system may say so.
Stock Is Several Numbers With One Name
A warehouse manager, a store manager and the person who runs the marketplace account can each give a correct answer that differs from the others. They are reading different quantities: units on hand, units committed to orders, units held back for damage or inspection, and units still incoming.
A faster connection publishes each of those errors sooner. A store balance that was already wrong, a return counted before inspection and a bundle sold on one channel without touching its components on another all reach the customer more quickly. The cost is a cancellation, a refund and a customer who may not return. The remedy is one agreed arithmetic, one ledger and one set of rules, with each channel receiving a figure calculated for it.
Four Actions That Give Every Channel a True Figure
Each action can be started in your current systems, and each one makes the later integration simpler.
Define Available Stock in Writing
On hand, committed, unavailable and incoming are different quantities, and available is what remains after every claim.
We agree the arithmetic with operations and the commercial lead, and give each quantity one name. A warehouse manager, a store manager and the marketplace owner then read the same number, and a dispute becomes a question about a specific claim on a specific unit.
Get started
- Write the four quantities and how available is calculated from them.
- Ask three people for the stock of one item and compare the answers.
Send Movements to One Ledger
Channels report a sale, a return or a receipt. One ledger calculates the balance and publishes it.
When two systems overwrite each other's balances, a sale can vanish from the record. We connect the store, marketplaces and stores so that each sends movements to the system that holds stock, and the stock and order status stay correct in every place without anyone retyping them.
Get started
- List every system that currently writes a stock quantity.
- Choose the one system that will own the balance.
Write the Reservation Rules on One Page
When a unit is reserved, when it lapses and when a return is sellable should be decided once.
We draft one page with operations that covers placed orders, cash on delivery, unpaid orders, failed deliveries, store collection, bundles and returns. A returned unit sits as unavailable until it has been inspected, and a bundle takes its availability from its scarcest component.
Get started
- Pull the last 100 orders cancelled for lack of stock and give each a cause.
- Draft the rule for the largest cause first.
Publish a Calculated Figure to Each Channel
The website, the marketplace and each store can carry a different buffer, set on the cost of a cancellation there.
A buffer is a commercial decision by class of item, based on how fast it sells and how accurate its count has proved. As counts improve, buffers fall, and more of your stock is offered for sale.
Get started
- Choose one fast-selling line and decide the buffer for each channel.
- Review the buffer monthly against cancellations.
How Thinqmesh Solves This
We begin with what happens after an order arrives, and most stores start on an established platform, with custom work kept for what the platform cannot do.
- Week 1
The Order Path Mapped, a Store Taking Shape
We follow an order through payment, stock, courier and accounts, and stand up the first working store on an established platform.
- Week 2
Stock and the Rules Connected
Orders and stock sync with your systems, and the reservation rules are set. We check what your accounting system allows before connecting it.
- Week 3
Payments, Couriers and Marketplaces
Payments, shipping, tracking and returns are connected, and marketplace listings and orders are managed beside your own store.
- Week 4
A First Working Store
The store is working and your team can update it. Connection of payments, couriers and accounts completes by week six, when the store takes real orders.
You finish with a store that takes real orders, stock and order status that stay correct across your channels, and analytics showing where customers drop off. The code and the data are yours.
