How-to
How to Capture What Customers Asked For That You Did Not Stock
Every store hears requests it cannot fill: a colour, a size, a variant, a feature, a brand you do not carry. POS never records them, because nothing was sold. Inventory never records them, because nothing was stocked. The request lives for a few seconds in the conversation and then it is gone. Capturing it is the difference between planning assortment on what sold and planning it on what customers actually asked for.
Why your systems cannot see unmet demand
POS records transactions. Inventory records stock. Neither has a field for 'the customer wanted the 8 GB variant in blue and we had the 6 GB in black'. Some retailers add a 'lost sale' button at the till; it is pressed rarely, without detail, and never for the customer who walked out before reaching the till. The only place the request exists in full is the conversation with the advisor.
What to track
- Requests for items not carried, by store and week, in the customer's words, grouped by product, variant, size and feature.
- Requests for items carried but out of stock at that store and that moment, which is a replenishment signal rather than an assortment one.
- Frequency and trend. One request is a curiosity; the same request in forty conversations across a region in a fortnight is a range gap.
- Whether the customer accepted an alternative, left, or gave a number to be called when the item arrives.
What changes when requests are captured
Category and merchandising teams receive a weekly list of what customers asked for and did not get, ranked by frequency, with the store and the conversation behind each entry. Brands selling through third-party retail see the same signal for their category. Store managers see which requests could have been filled from the store next door. And the customer who asked can be called when the item arrives, which turns a lost visit into a sale.
On the floor
A jewellery chain's conversations show a rising number of customers asking for lighter-weight designs in a specific price band, in the same words, across four cities. The category team had no such line. The request count justifies a trial range; the customers who asked are the first to be told it has arrived.
Frequently asked questions
Is this the same as a lost-sale button at the till?
No. The button captures a fraction of requests, without detail, and only for customers who reach the till. Captured conversations record every request, with the variant and the customer's words.
Can brands get this from retailers?
Brands with promoters in third-party retail can capture their own counter conversations with consent and see the requests for their category, without depending on the retailer's data.
How is customer privacy handled?
Requests travel without the customer's identity. A name and number are attached only when the customer gave them so they can be told when the item arrives.
Related reading
Where Borentis applies this
- Unmet Demand Signals: Demand for what you did not have.
- Brand Voice-of-Customer: The focus group hiding in plain sight.
- Walk-in Recovery: The customer who left is still yours.
Borentis is the Agentic Operating System for Customer Interactions, built for Indian retail floors: consented one-tap capture on the advisor's phone, every conversation scored against your playbook with the evidence behind every number, leads created when a number is heard, and coaching from your own best conversations.