One Stock for the Shop and the Website: How Not to Sell the Last Item Twice
Shared stock for your shop and website: sync speed, holding an item during checkout, safety stock, sizes and colors, returns, branches and offline outages.
Written with AI assistance and fact-checked against sources
Friday, 11:40. One shirt in size M is left on the shelf. A customer in the shop tries it on and decides to buy. At that exact minute, another customer on the shop's website puts the same shirt in the cart, fills in an address and clicks "Pay". Both pay. Only one of them will get a shirt, and the other will get an apologetic phone call, a refund and maybe a one-star review.
This happens when the POS and the online store manage two separate stocks, or one stock that updates too slowly. This guide breaks the problem into parts: how fast sync needs to be, how to hold an item for a customer in the middle of checkout, how much stock to "hide" from the website, what to do about sizes and colors, returns, multiple branches, in-store pickup, and what happens when the internet in the shop goes down.
In short
- One stock for the shop and the sales website works only if every sale updates the other side within seconds, not once an hour and not once a night.
- When a customer on the website clicks pay, the item should be held for them for a few minutes. That way the POS in the shop doesn't sell it at the same time.
- Safety stock: show less on the website than you really have for items that sell out fast. One or two units are usually enough.
- Every size and color has its own stock count. A website that counts "shirt" and not "black shirt, M" will sell sizes you don't have.
- Decide in advance: which branch the website sells from, when a returned item goes back into stock, and what to do when the internet in the shop goes down.
What actually happened to the shirt
To see where the problem is, let's follow the shirt on a timeline from the start. Suppose the website receives a stock update from the POS once every 15 minutes:
| Time | In the shop | On the website | What the stock shows |
|---|---|---|---|
| 11:30 | Stock update from the POS | 1 in shop, 1 on website | |
| 11:38 | Customer adds to cart and fills in details | 1 in shop, 1 on website | |
| 11:40 | The shop customer pays at the register | 0 in shop, still 1 on website | |
| 11:41 | The online customer pays on the website | 0 in shop, 0 on website | |
| 11:45 | Stock update from the POS | Minus 1. You sold something you don't have |
There is no bug here. There is a gap between the moment something sells on one side and the moment the other side knows about it. The rest of this guide is about narrowing that gap.
Sync speed: seconds, minutes or once a night
There are three main ways a POS and a website talk about stock:
- Instant update: the POS sends the website a message the moment something sells (in technical terms: a webhook). The website knows within seconds.
- Periodic check: the website or a sync tool asks the POS every few minutes "what changed?". Simple to build, but there is a window of minutes when the stock is wrong.
- File or manual update: you export a stock file from the POS and upload it to the website, once a day or once a week. Fine for a catalog that barely changes. Not for items that sell out.
| Update method | How long stock is inaccurate | Fits |
|---|---|---|
| Instant update | Seconds | A shop selling the same items in both channels |
| Check every 5 to 15 minutes | Up to a quarter of an hour | A large catalog with deep stock, dozens of units of each item |
| Daily file | Up to a full day | Pre-order products, or a website that is mostly a catalog |
Rule of thumb: the fewer units of each item, the faster the sync needs to be. In a grocery with 40 bottles of the same brand of oil, a 10-minute gap does almost no harm. In a boutique with 2 units of each size, it's the difference between a sale and an apology.
Ask the POS vendor: "How many seconds until the website knows about a sale in the POS? And what happens if the website is unavailable at that moment, is the message sent again?" A good answer includes a number and a retry mechanism. "It updates automatically" is not an answer. (At KupaLi, for example, the answer is about 5 seconds.)
Reserving during checkout: the minutes when the item is "held"
Even sync in seconds doesn't solve the moment when two people buy the same item in the same minute. For that there's a hold, or reservation: when a customer on the website starts to pay, the item comes off available stock for a few minutes. If the payment goes through, the item is sold. If not, it returns to stock.
This is how it looks on common platforms:
- WordPress with WooCommerce: WooCommerce is the store plugin for WordPress, and it has a setting called Hold stock, in minutes. An order that isn't paid by the end of the time is cancelled and the stock returns. The default in the code is 60 minutes.
- Wix: you choose when stock goes down: when the order is created, or only after payment is received. Wix itself warns that with the second option new customers may buy a product that is already out of stock.
- A custom-built site, or a WordPress site without WooCommerce: there is no default. The developer has to build the reservation, or get it from the POS API.
Note: the website's reservation protects the item only from other buyers on the website. The POS in the shop doesn't know about it, unless the integration passes the reservation to it too.
How long to hold
- Too short (a minute or two): a customer who types card details slowly, or goes through bank verification, will lose the item midway.
- Too long (an hour): an item someone abandoned in a cart blocks the shop. In a boutique, an hour of "sold out" on the last item is a sale that didn't happen.
- Usually works: 10 to 15 minutes. Enough for a normal payment, and short enough that an abandoned item returns quickly.
And if it still sells twice
It will happen once in a while, even with everything set up right: an employee sold in the POS without scanning, or the connection dropped for a moment. What matters is that it doesn't surprise you:
- The integration should send an alert. When a POS sale meets an item that is already reserved or sold on the website, someone should get a notification, not find out while packing.
- Call the website customer the same day. Not an automatic email. Offer another size, another color, a similar item, or a full refund right away.
- Refund quickly. A customer who got a refund within an hour remembers the service. A customer who waits a week mostly remembers the wait.
Safety stock: show a little less in the online store than you have
The cheapest way to reduce double sales is not to show the last unit on the website. If there are 2 shirts in M, the website shows 1. If there is 1, the website shows "sold out" or "available in store".
WooCommerce already has this: a setting called Out of stock threshold decides at what quantity the product is shown as "sold out". Set it to 1, and the last unit stays for the shop. On other platforms, or on a custom site, you can ask the developer to calculate the stock sent to the website as "POS stock minus X".
How much to hold back? It depends on the item:
| Item type | Recommended safety stock | Why |
|---|---|---|
| A single item or the last one in a size | 1 | The highest risk, and the item sells in the shop anyway |
| An item that sells fast in the shop (several a day) | 1 to 2 | While the website customer pays, the shop keeps selling |
| An item with deep stock and a slow rate | 0 | The risk is negligible |
| An item sold only on the website | 0 | Nobody competes for the same unit |
The price of safety stock: once in a while the website will show "sold out" on an item you still have. In a boutique this usually pays off, because the last unit sells in the shop anyway, and a customer who sees "sold out" is less disappointed than a customer who paid and got nothing.
Sizes and colors: every variant is a separate stock
One shirt in three colors and five sizes is not one product. It is 15 stock rows. Wix explains this explicitly: a hat in two sizes requires stock management for each of them. Both in the POS and on the website, every combination of size and color needs its own quantity.
Three mistakes that keep recurring in integrations:
- The website counts at the product level. The POS knows that 0 are left in M and 4 in L. The website sees "4 shirts" and sells M.
- Different variant names. In the POS it's "M", on the website "Medium", in the supplier's file "Med". The integration doesn't know it's the same thing, and creates a new variant or doesn't update at all.
- A variant added on one side only. A new color arrived, someone added it in the POS and forgot the website (or the reverse). Its stock exists in only one system.
The solution is for every variant to get a fixed identifier, usually a barcode or SKU, and for the integration to match by that identifier, not by name. We covered this in the post Products and prices in the POS and on the website, and building SKUs in Barcodes for a small business: a catalog without duplicates.
Returns: when an item goes back into stock
A return is a sale in reverse, so it needs to update stock exactly like a sale. The question is when.
- A shop return of a shop purchase: the item is on the counter, you see it's fine, and you return it to stock in the POS. The website updates as with any sale.
- Cancelling a website order before shipping: the item never left the warehouse. Return it to stock immediately.
- A return of a website order after shipping: this is the easiest place to make a mistake. Under the Consumer Protection Law (חוק הגנת הצרכן), a customer who bought remotely can cancel within 14 days, and usually returns the product at their own expense. Between the cancellation notice and the moment the parcel arrives, several days pass. If stock goes back up as soon as the customer cancels, the website may sell an item that is still on its way to you.
- A shop return of a website purchase: the customer arrives with the shirt they ordered. The employee has to find the order, check the item, and return it to the stock of the branch where they're standing. How to do this without mixing up receipts and credits: Customers, orders and returns: shop and website in one picture.
The rule: an item goes back into stock when it is physically in the shop and checked, not when the customer says they're returning it. A damaged item doesn't go back into sellable stock at all. Record it separately, so your stock count matches what's on the shelf.
Multiple branches: which stock the online store sells from
With one branch there is no question. With two or more, you need to decide:
| Option | How it works | Advantage | Disadvantage |
|---|---|---|---|
| One branch sells to the website | The website sees only the stock of a main branch or warehouse | Simple, clear who packs | An item that's only in the other branch shows as "sold out" on the website |
| The sum of all branches | The website sees all the stock together | You sell more | You need to decide who packs, and move goods between branches |
| A dedicated warehouse for the website | A separate stock allocated only to online | No conflict with the shops | Split stock, more goods sitting idle |
For a business with two or three branches, the safest start is usually one branch selling to the website. Once the routine works, you can expand to the sum of branches, with a clear rule: the order goes to the branch that has all the items, and if there isn't one, to the main branch.
In-store pickup
In-store pickup (click and collect) sounds simple: the customer orders on the sales website and comes to collect. In practice there are three moments when stock has to move:
- At order: the item is held for the customer at the branch they chose. It's no longer available on the website or in that branch's POS. If you physically put it aside, on an "orders" shelf, employees won't sell it by mistake.
- At pickup: the item leaves the shop. If the customer pays only at pickup, this is the moment the sale is recorded in the POS.
- When the customer doesn't show up: set a time, for example 48 hours, and send a reminder. After that time the item goes back on the shelf and into stock. Without such a rule, the orders shelf fills with items nobody will collect.
What happens when the internet in the shop goes down
A cloud POS with an offline mode keeps selling when the network drops, and saves the sales on the device. The problem: until the connection returns, the website doesn't know about these sales. If the outage lasts an hour on a busy day, the website shows stock from an hour ago.
What to do:
- Backup internet. A hotspot from a phone, or a router with a SIM, puts the POS back on the network within a minute, and sync continues.
- Restore the connection, then check. When the sales reach the server, check whether items went negative, meaning they sold both in the shop and on the website. Treat them like a double sale: call the website customer the same day.
- In a long outage, protect the last items. If it's clear the network won't return soon, mark items with one or two units left as "sold out" on the website until everything syncs.
How to test offline mode before choosing a POS, and what happens to card payments without internet: Online or offline POS: what happens when the internet goes down.
A 20-minute test before you go live
Before you open the integration to customers, run these tests with one real product, set up with a stock of 2:
- Sell one unit in the POS. Count how many seconds until the website shows 1.
- Add the last unit to the cart on the website and start to pay. Check that the POS sees it's reserved, or at least that the website doesn't let a second person buy it.
- Abandon the payment. Measure after how many minutes the item returns to stock.
- Try to sell the reserved item in the POS. What happens? Who gets a notification?
- Change the stock of one size only. Check that only that size changed on the website.
- Make a return in the POS. Check that stock on the website went up.
- Disconnect the internet in the POS, sell a unit, and reconnect. Check that the sale reached the website.
If a test fails, it's better to find out now, with one product, than at noon on a Friday with a customer on the phone.
How it works in KupaLi
In KupaLi the stock of the shop and of the sales website is the same stock. Through the KupaLi API, which works with any programming language and any server, including a WordPress site:
- A sale, price change or stock update in the POS reaches the website within about 5 seconds.
- When a customer pays on the website, the item is held for them for 10 minutes (adjustable). If it still sells in the POS, the website gets a notification and can contact the customer.
- The website sees stock for each size and color.
- Every update sent to the website is signed, and each system has its own key, with permissions only for what it needs.
- Internet down? You keep selling with cash and cheques, and everything syncs when the connection returns. On all plans.
Don't have an online store yet? The Smart POS plan (₪119 per branch per month + VAT) includes an online store: customers pay at pickup or through a payment link that you send. Safety stock, in-store pickup from a specific branch or selling from several branches? We connect according to what the business needs.
Want to see how it works? Start 14 days free, no credit card. Looking for the full picture of connecting a POS to a website? Start with the complete buying guide, and before talking to a vendor, go through the questions to ask a POS company.
This information was checked in November 2026 and is general. Website platform settings change; before connecting, check the settings on your site with your developer.
This article is based on publicly available information. Found a mistake? Write to us at support@kupali.co.il and we will fix it.
What else do people ask?
How do you prevent a double sale of the same item in the physical shop and the online store?
Three things together: stock sync in seconds, a reservation of a few minutes when a website customer pays, and a safety stock of one unit on the website for items that sell out fast.
How often should stock sync between the POS and the website?
For items with only a few units, within seconds of every sale. For a catalog with deep stock and a slow rate, an update every few minutes can be enough. A daily file fits only a website that is mostly a catalog.
How long should an item be held for a customer paying on the website?
Usually 10 to 15 minutes. Less than that, a slow-paying customer loses the item. More than that, an abandoned cart blocks an item the shop could have sold.
What do I do if an item sells in the shop after a customer paid for it on the website?
Call the customer the same day, offer another size, color or a substitute item, and if they don't want one, refund immediately.
When does an item returned from a website order go back into stock?
When it physically arrives at the shop and is checked to be fine, not when the customer says they're cancelling. A damaged item is recorded separately and doesn't go back on sale.