Skip to content
Interface language: English
Design / Signal

Out of stock: what to show instead of a dead end and artificial urgency

Explain unavailable variants, genuine alternatives and notifications without inventing a date or promising a reservation.

Article language: English

People on terraces with coloured panels and tables overlooking water and hills.
In this article

A product can disappear from stock without disappearing from a customer's life. Someone has saved the address, someone returns after a conversation, someone needs a part that fits a set they bought earlier. Removing the purchase button does not yet answer what happened or whether it is worth returning.

An availability message is part of the offer. It should explain the situation and leave an honest way forward. Otherwise the shop presents an attractive product and then shrugs. It can do much better, even when the next delivery date is unknown. Start by establishing what information is actually missing.

“Unavailable” can begin several different stories

An item may be temporarily out of stock while remaining on sale. It may be made after an order. The issue may concern only a selected colour or collection point. Finally, a model may have been discontinued and will not return. One word for all these situations saves space in the administration panel but does not help someone planning a purchase.

Start with what the company can confirm. Is there a delivery with a fixed date, preliminary information from a supplier, or only the catalogue manager's hope? Do not turn the last of these into a date on the page. A customer may make their own plans around it. When there is no confirmed date, say so plainly and show the available options.

Separate the stock count from the rule for accepting orders. Shopify can continue selling when an item is out of stock, when inventory tracking and continued sales are configured accordingly. Merely switching on that technical option does not explain fulfilment terms to a customer. The copy and button must describe the actual service.

Describe a state the shop cannot currently confirm separately. A connection error with the stock system does not prove that the product has run out. That message needs different wording and a different next step from a real stock shortage. If you use the last known information, agree when it may be shown and before which action the possibility of buying must be confirmed again.

Check the scope as well. Unavailability of one variant, one collection point and an entire fulfilment method may look similar on screen. The customer should know which choice they can change to continue. A label applying to the whole product may be too broad when another collection method or finish is genuinely available.

Record in the design whether each state allows an order, a request for a message, or only access to documentation. Do not guess from the colour of a label in the old shop. “Out” may previously have meant several informal rules known to staff. Those rules need to be identified and named before changing the interface, or the new page will simply present the old ambiguity more attractively.

For a product family, retain information about the chosen variant. An unavailable red model does not mean the entire collection is absent. Conversely, do not show a general “available” when the customer has selected a version they cannot order. Choosing product variants (in Polish) needs the same definition of status as the basket and subsequent fulfilment.

Do not change the selection without the buyer's agreement. You can show an available version alongside it and explain the difference. Do not substitute it beneath a button that referred to another item moments ago. Colour or dimensions may be conditions the customer cannot change. The system does not know the reason for the choice simply because it saw a click.

The button should say what can be done now

When purchasing is impossible, show that state with a short explanation. A grey button without text does not say whether a size has not been selected, stock has run out or a function is still loading. Do not make the visitor infer the answer from colour alone. Here, the wording has a very specific job.

If you accept an order for later fulfilment, name that arrangement before the action. A future tense buried in a long description is not enough when the main label resembles an ordinary purchase from current stock. Agree with the shop owner which details can be confirmed and where they must appear. The design should not invent sales terms on its own.

Google Merchant Center requires availability to match in product data, on the landing page and at checkout. This is a requirement of a particular product presentation system. In the shop design, keep the information consistent at the points the customer reaches in sequence, rather than fixing only the product-card message.

If you submit a product to Merchant Center as preorder or backorder, Google also requires the expected shipping date on the landing page. Agree that date with the person responsible for fulfilment and update it when it is no longer reliable. If you cannot provide one, check how the offer should be represented in that system rather than entering a guess. The offer data also requires availability_date: for preorder it indicates the day the product becomes available for delivery; for backorder, the shipping day. The availability date provided in the data should also be visible on the landing page.

“Soon” is not a date. It may be true, but without a range it does not answer someone who needs the product by a particular time. If the company can confirm only that it is waiting for information, show that. An honest absence of a date is clearer than a calendar that moves every week along with hope.

Here, evidence for promises in an offer (in Polish) is useful. For a promised date, identify its source and the person who updates it. There is no need to publish internal correspondence with a supplier. The team does need to know who can change the message and what happens when an earlier assumption is no longer current.

An availability notification is a separate function. Explain what the request concerns: a specific variant, the whole family or the ability to order. Someone choosing a small model should not receive a message only because the large version returned. Record the item of interest, rather than retaining only a contact address.

Aeneia conceptual photography

Also show the outcome of the request. Was it accepted? Which product does it concern? What will happen next? Do not call it a reservation if no item is set aside for that person. Receiving a message and being guaranteed stock are different outcomes requiring different actions by the shop.

If a notification does not require an account, do not introduce registration through the back door. Guest checkout (in Polish) and a request for a single message can have separate paths. Name the required information and the purpose of the function. An unexpected password form can turn a short request for a message into a task the customer never intended to start.

The next step depends on why the customer chose it

An alternative should fit more than the look of a thumbnail. If the customer needs a particular width, a larger model in the same colour does not solve the task. Show the relevant difference and let them decide. “Similar product” does not replace information about what is similar and what the recommendation does not establish.

You do not need a complex recommendation engine to help. A well-chosen link to a suitable category or collection may be enough. Keep the conditions the customer has already specified, provided they still make sense. Sending them to the beginning of the whole shop discards the work they did choosing a particular variant.

If an item is available only at a selected location, show the location and the conditions for receiving it. “Available” without context may suggest shipping anywhere. A separate design for delivery and collection (in Polish) can connect stock to a specific fulfilment path rather than relying on a general label.

A support contact should retain the subject. Someone asking about availability need not retype the entire product name and number if the page can safely pass them along. In the contact form (in Polish), let them confirm which model they mean. Do not hide the connection solely in data the customer cannot see.

For a discontinued model, explain its status and the role of any successor. A new version may differ in construction, size or accessory compatibility. Do not call it a replacement without confirming the important characteristics. Someone returning for another part of a set needs something different from someone beginning a new selection. When a person returns from an old order, also check what buy again means when the offer has changed (in Polish) before suggesting today's equivalent.

A discontinued model's page may still serve product owners. Instructions, version identification or accessory information remain useful regardless of sales. Decide whether to keep it based on the actual task and material, not an automatic rule that zero stock means deleting the address.

Do not send every such visit to a 404 page (in Polish). An absent product and absent content are different situations. If material is moved or removed, agree how the address will be handled as part of migration. A customer with an old link should receive as clear an explanation as possible of what happened to the item they sought.

When the product returns, the communication needs to catch up

Restoring stock does not end with enabling a button. Check the label in the list, the variant page, the purchase copy and notifications. If one still shows the old unavailability, the visitor receives contradictory answers. Establish which source each location uses and where information must be refreshed.

Decide what a person signed up for a notification will see if the product is discontinued rather than returning. Do not leave them waiting indefinitely because of an old promise. If you provide such communication, name the change and separate status information from a suggestion for another product. A new offer should not pretend to fulfil the condition concerning the previous version.

Retain the name and important characteristics in the confirmation itself. After several weeks, a recipient may not remember which option they selected. A short message identifying the item of interest helps restore context. There is no need to promise frequent updates if the function sends only one signal when availability returns.

Update the material leading to the product page. A campaign or a featured product on the home page may still encourage immediate purchase. If the offer's state has changed, inspect the path from the first message. Correct text beside a grey button does not remove a contradiction with the promise that brought the customer there.

Send a notification according to the condition promised at sign-up. If it concerned the ability to order a particular variant, that ability must be confirmed. A staff member merely correcting a number is not always a sufficient event. The shop owner should establish what availability means in the actual workflow and how to avoid an accidental message.

Urgency should be supported by the real state of the offer. “Last chance” or a countdown has meaning only when it reflects a real, confirmed situation. The design should also be able to say calmly that the product has returned. A customer waiting for a specific model does not need extra theatre to recognise a useful message.

In a test, use a change to one variant, a later date and complete discontinuation of the model. View the page as a person returning through a saved address. Check whether they understand what they can do now and whether the proposed path matches their earlier choice. A message open on an employee's computer does not replace that perspective.

Aeneia Design connects a shop's content and behaviour within an agreed scope. For the conversation, prepare the meaning of the statuses used and how they are updated. An unavailable product can then remain an understandable part of the offer, without the customer needing to ask whether “soon” means next week, next season or merely good intentions.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear