Stop running stock from a Messenger thread
Overselling happens when size and quantity live in chat. Put inventory in the console. Keep WhatsApp for closing, not for counting.
The 2am call is two people sold the last M.
On Facebook and WhatsApp, stock is a feeling. You remember you had four. Three chats closed. The spreadsheet is a week behind. Someone already promised the same kurta in two threads.
That is not a discipline problem. It is a record problem. The place you take the order is not the place you decrement the unit.
Chat is a close. It is a bad warehouse.
Keep Messenger. Buyers will still ask if you have size M.
Do not let the answer live only in the thread.
A storefront with real variants — size, color, quantity — refuses the fourth M when three are gone. The console shows what is left before you type yes. Courier booking later uses the same line item, not a guess pasted into Pathao.
A spreadsheet can do this if you update it on every yes. You will not. Nobody does after 11pm.
What to move first
- Your top 20 SKUs. The ones that actually sell, with sizes.
- Quantity on hand. Count the shelf, not the last Facebook comment.
- The rule: if it is not in the catalog, do not promise it in chat.
Put the store link in the bio. When they message, send the product URL. The thread becomes which color, not let me check.
You can still close on WhatsApp after they see the page. The page held the stock.
What StoreOS does here
Products and variants live in the merchant console. The hosted shop (Starter or Enigma) or a custom storefront reads the same catalog.
COD and Pathao / Steadfast are how the unit leaves. They start on a paid plan, not on Free. Free is 50 products and a website builder. Load the catalog there. Upgrade when you book the first parcel. Prices are on the homepage.
This is not a Facebook replacement. It is a stock ledger that chat can point at.
GearHaat (gearhaat.com) and Sporty BD (sportybd.com) run a real catalog this way. We do not publish their order counts.