Playbook, electronics retailer
The allocation lands, the allocation goes, and nobody is told the next date
A shop with shelves can walk over and look. This one is answering about units it has been allotted by somebody upstream, in quantities it did not choose, against a production schedule nobody outside the factory sees. That is why the honest answer to when are you getting more is so often that nobody here knows, and why the dishonest answer is so tempting.
Why this is not the general answer
The handling pattern for stock availability holds across every trade. What follows is the part that does not.
- On a launch the shop receives an allocation it had no say in the size of, and when that is gone there is no reordering, only the next allocation, which arrives with no date attached to it.
- A back order is not a delayed parcel. It is a place in a queue behind a production line that publishes nothing, so any date offered is a supplier's guess passed along with a shop's name on it.
- Model designations differ by a single character between a regional variant, a storage size, a colour and a bundle, so a stock line read against the wrong suffix is a confident answer about a product the customer was not asking for.
- Open box, ex display and refurbished units are individual items with their own condition notes and sometimes their own guarantee terms, so in stock means exactly one, and it can be sold between the page loading and the question being typed.
How it arrives
- when are you getting more of these in
- am i in the queue for the next batch
- how many have you actually got left
- is that the version for here or an import
- is the ex display one still under guarantee
- will there be any in store on launch morning
What has to be indexed for this to work
| What your stock indicator means, and when it was last true | Whether it is live, whether it counts units already in baskets, and whether it covers the warehouse, the shops or both. Customers read a stock badge as a promise. Writing down what it actually measures is the only defence against being held to it. |
|---|---|
| The allocation and pre-order sequence for a launch | How your allocation is committed, how the queue is ordered, and what somebody beyond the allocation is told. If there is no date for the next delivery, that is the fact to publish, because the alternative is a member of staff inventing one. |
| The variant map for every line where a character changes the product | Region, storage, colour, bundle and generation, laid out so the difference is visible. This is the document that stops the assistant answering about a neighbouring model, which is the characteristic failure in a catalogue built from supplier codes. |
| How single units are described: open box, ex display, refurbished | What each grade means, what guarantee attaches to it, and the fact that each listing is one physical item rather than a line with a count behind it. Also whether they can be held, because that is the next question and the answer is usually no. |
The reply
I cannot see stock, so I would rather tell you how this works than guess a number. What we get at a launch is an allocation set by the manufacturer, and once it is committed there is no reordering, only the next allocation, which usually arrives without a date we can publish [1]. So if the site is showing this as unavailable, the honest position is that we do not currently know when the next batch lands. One thing worth checking before you wait: this model has a variant that differs by one character in the code, and the two are separate lines with separate availability, so it is worth confirming which one you actually want [2]. Ex display and open box units are single items rather than a stock line, so they go the moment somebody buys one. If you want to be told when the next batch is confirmed, leave your name and an email and I will pass that on.
It refuses to read stock and then spends the reply on the mechanism, because a customer who understands allocation stops treating the shop as evasive. The variant point is volunteered because it frequently turns an unavailable answer into an available one, which is the most useful thing in the message. The single unit rule is stated so nobody waits on an ex display item they think is a stock line. The offer at the end is a genuine handover rather than a subscription promise.
Where it stops
The trigger. The visitor wants a unit held, wants telling when stock lands, asks about a specific single item such as an ex display unit, or needs their variant confirmed before ordering.
I cannot see stock, hold anything or add you to a list. Leave your name, an email and the exact model you are after, including the variant if you know it, and somebody who can check will come back to you.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- Never state a quantity in stock, since the assistant reads documents rather than a stock system and the figure will be wrong before the customer finishes reading it.
- Never give a date for the next delivery of an allocated line, because the shop is not told one and the date will be quoted back when it passes.
- Never say an item is discontinued or will not return, which is a supply judgement and quietly sends a paying customer to a competitor.
- Never answer about a neighbouring variant when the customer named a code, since one character separates a regional model from a domestic one and the difference arrives as a plug that does not fit.
Questions
- Can we connect it to our stock system so it knows what is available?
- No. It reads material you point it at and cannot query a system, so live availability is outside it in every configuration. That is less of a loss than it sounds, because a live number quoted in a chat window is stale by the time somebody reaches a basket.
- What should it say when we genuinely have no date?
- That there is no date, and why. An allocation model is easy to understand once somebody explains it, and customers accept it far better than a soft estimate that passes. The failure here is invented reassurance, not honesty.
- How do we stop it answering about the wrong variant?
- Publish the variant map as its own document, with the character that changes spelled out. A catalogue built from supplier codes looks unambiguous internally and is a minefield from outside, and this is the one place a near miss costs a return.
Keep reading
- Everything for a electronics retailerCompatibility, warranty and returns on opened items answer well from your own terms. Firmware level setup advice does not.
- Handling stock availability in generalWhat an assistant can say about ranges, restock patterns and alternatives, and the damage one confident wrong stock answer does.
- A quantity and a model number is not enough paperwork hereAn asset register wants a serial per machine and a maker claim wants a dated proof of purchase. Cover bought at the till is billed elsewhere.
- Somebody signed for it, which is where the conversation startsSomebody signed for it, so this is a question about evidence. Damage has to be reported before the unit is powered on and registered.
- Some of these can be stopped and one of them never couldA code that has been revealed cannot be recalled, and a configured machine stops being cancellable the moment components are committed.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.