Checking stock over WhatsApp: what happens when your system does not answer
What happens when a customer asks whether something is in stock
Today what happens is that somebody leaves the chat, opens the system, looks, and comes back. In between, the customer waits.
Checking stock over WhatsApp automatically removes that round trip, and it also brings a more uncomfortable question: what do you answer when the number is not available. That second part is what decides whether the automatic reply helps you or lands you in trouble.
Stockouts are not rare. A University of Chile thesis on stockout detection in retail cites a global average of 8.3%, and 15.7% in the Chilean market, with losses estimated at 3.9% of the retailer's sales. Which means "there is less than they asked for" is routine, not an exception.
Stock is checked at confirmation, not at display
It is a difference of seconds and it changes everything.
If stock is read when the product appears in the conversation, the number is already stale by the time the customer decides. If it is read before the order is confirmed, the answer describes the moment the commitment is made.
That is the only point where the check is worth anything: not when you show, when you close.
There is less than they asked for: who decides
The customer decides, item by item.
The easy way out is to quietly trim the order and mention it later. That turns a small annoyance into a complaint, because the customer finds out when there is nothing they can do about it.
The right move is to say how much there is of each thing and wait for the answer. Sometimes they take what is there. Sometimes they swap the product. Sometimes they would rather wait. All three are their decisions.
Your system does not answer: what exactly gets said
It says availability is unknown, and it waits.
It does not say there is stock. It does not say there is none. Both are lies with different price tags: one leaves you an order you cannot fulfil, the other loses you a sale you could have made.
| System state | What gets answered |
|---|---|
| Answers and there is stock | The order is confirmed |
| Answers and there is less | How much there is gets reported and the customer decides |
| Does not answer | Availability is reported as unknown and it waits |
| The product is discontinued | It stops being offered, without breaking old orders |
Where the price in the reply comes from
From the catalogue synced with your system, not from an estimate.
An invented price has one ugly property: the customer keeps it. It stays written in the chat, with a date and a time, and comes back as a complaint when the invoice does not match.
When the number comes out of the catalogue, the conversation repeats what is already loaded. If your price list changes, the answer changes with it.
An order remembers the price on the day of the sale
Prices move. Closed orders do not.
Every order stores the product's name and price as they were on the day it was sold. If you update the list next week, today's order still says what was sold and for how much.
That is what makes an order from three months ago a document rather than a photo that keeps shifting on its own.
Discontinued products do not vanish from history
When a product leaves your catalogue, it stops being offered in conversation.
What does not happen is that it gets erased backwards. An old order still resolves to the product that was actually sold, even if you no longer carry it.
Delete the product and its history with it, and you lose half the answers to "what did we sell this customer last year?".
Searching by what the customer meant
Your customers do not know your catalogue codes, and they have no reason to.
They write "something waterproof for the rain" and expect somebody to understand. Catalogue search works on that description and lands on the right product, in whatever language they wrote it.
That is what avoids the "we could not find that product" when the product is there under another name.
How often to sync
It depends on your provider more than on you.
The frequency is picked from a short list, and the floor of that list comes from the request limit your system tolerates. You can go all the way down to switching automatic sync off and syncing by hand only.
Three things that help more than raising the frequency:
- Sync now, for right after you have touched a price list.
- An alert when a sync fails, or when products stop arriving.
- A preview before switching it on: seeing which products come in and how they map.
Key takeaways
- The moment to check stock is when the order is confirmed, not when the product is shown.
- If there is less than requested, the decision is the customer's, item by item.
- If the system does not answer, availability is reported as unknown. Never assumed.
- The price comes from the catalogue, and the order stores it as it was on the day of the sale.
- Discontinued products stop being offered without breaking history.
- Stockouts are routine: 8.3% as a global average, per the University of Chile thesis cited above.
Frequently asked questions
- Can I check stock over WhatsApp without changing my management system?
- Yes, if your system exposes an API. The connection is made from the panel by picking the provider and entering your credentials; you keep working where you always work. The first one supported today is Dux Software, widely used in Argentina, and the rest get added one at a time.
- How often does the stock in the reply get updated?
- According to the sync frequency you choose, whose minimum depends on your provider's request limit. On top of that, an order's stock is verified at the moment of confirming it, which is the number that actually matters.
- What if my system is down exactly when somebody wants to buy?
- Availability is reported as unknown and the customer is asked to wait. We would rather give an uncomfortable answer than confirm an order you cannot fulfil afterwards.
- Can the customer decide when there is less than they asked for?
- Yes. How much there is of each item is reported and their answer is awaited, instead of trimming the order unilaterally.
- Is there a limit on catalogue products?
- There is no item cap and no per-plan limit. What bounds the sync is your own provider's request limit, which is where the frequency floor comes from.
Related posts
Get twice the output from your team without asking more of them
It answers WhatsApp, Instagram and web. It learns your business, takes the orders, and hands off to a person when it matters. You see every action noted in the chat.
Free Pro trial. No credit card required.