What should a product page say when an item is temporarily out of stock?

Separate a pause in stock from a promise to sell

A product page can remain useful when a current item sells out. Customers may need its dimensions, compatible accessories or a way to compare it with another model. The first question, however, is whether the shop is accepting an order for that exact item today. Google Merchant Center distinguishes ‘out of stock’, where the item is not available for purchase, from ‘backorder’, where the retailer accepts orders for an existing item that will ship later. A preorder concerns an item not yet released. Those are operational states, not interchangeable marketing labels. The shop must choose the state its fulfilment team can actually honor, then make the purchase control, wording and product data reflect that decision.

If no order can be placed, put a clear ‘Out of stock’ message near the product name, selected variant and buying control. A grey button alone can be ambiguous: perhaps the customer has not selected a size, the delivery address is unsupported, or the page is broken. Google’s landing-page requirements allow explicit text such as ‘Sold out’ or an inactive buy control, and require availability to be clear for online purchase. A customer-oriented page should state the reason in text as well as visually. Keep the price and product details truthful; do not use a fake low price to attract visits. If one size remains available while another does not, say so at the variant level rather than declaring the whole product available.

Treat a return date as a commitment needing evidence

A restock date should come from a checked supplier, purchase order or receiving plan, not a date generated because a template has a blank field. If the merchant has no reliable date, ‘Restock date not confirmed’ is a useful answer. The page can offer a stock alert without implying that signing up reserves a unit. Explain what will trigger the alert, which channel will be used, and whether the customer must order when notified. If an alert list collects contact details, put the actual purpose next to the field and retain only what is needed. A customer who needs an item this week can then decide to choose an alternative instead of waiting on a vague promise.

If the business accepts backorders, the buying path becomes a different contract. Show that the item is not ready to ship, give the expected shipping date that the shop can support, and explain what happens if the date changes. Google’s Merchant Center guidance requires an availability date for backorder and preorder product data and says the expected date should be visible on the landing page. That rule applies when the shop uses those Merchant Center statuses; it is not a reason to invent an exact date. A shop unable to provide a defensible shipping expectation should reconsider accepting payment for a backorder. At checkout, repeat the status next to the line item so the delay cannot disappear after the customer leaves the product page.

Help the customer compare real alternatives

A substitute is useful only if it meets the customer’s constraints. For an unavailable charger, compatibility and connector type matter more than a visually similar product photo. For clothing, size and color availability matter. Show a small set of actually purchasable alternatives with the specific difference that might change the buying decision. Do not label a substitute ‘equivalent’ unless the claim has been checked against product specifications. Keep the original item’s page available for people who need to review its details, but avoid steering every stockout visitor to a generic catalogue that makes them repeat their search. An alternative link should take the buyer to a real product page where its own stock state can be checked.

A store with branches may have an in-store unit while online delivery is unavailable. Say which channel has stock, when that status was last checked, and whether the unit can actually be reserved or purchased. Do not quietly show ‘in stock’ on an online offer merely because a shelf somewhere contains one unit. Google says product availability must align with the destinations and delivery locations represented in product data; landing pages must state restrictions such as store pickup only. The customer also needs the real branch and pickup conditions before traveling. If staff cannot verify branch inventory reliably, present it as an enquiry route rather than a guaranteed pickup. This is a commercial clarity decision, not merely a data-feed setting.

Keep one availability decision across surfaces

The visible page is only one copy of availability. A shop may also have a feed to Merchant Center, structured data in the HTML, a search-result card, a wishlist message and a checkout service. Google explicitly requires availability to match across the landing page, structured data, checkout and submitted product data for Merchant Center offers. Its product structured-data documentation lists `OutOfStock`, `InStock` and `BackOrder` among supported availability values. Map the shop’s internal state to each external vocabulary deliberately. A single field labeled ‘available’ may be too crude if the business distinguishes online stock, pickup stock and backorders. Document those mappings so a future catalogue update does not revive a buy button for an item that cannot be fulfilled.

Build a short change path for a stockout event. When sellable quantity reaches zero, the product service should stop accepting a normal immediate-ship order for that variant; the page should update its message; cached listing cards should eventually reflect the new state; and external product data should be refreshed through the store’s actual integration. Checkout must make the final decision with current stock, because a buyer may have opened the page before the last unit sold. The page can remain informative even when the order is refused. Log the state change and verify the product identifier, variant and sales channel. Without those identifiers, a team can update the wrong color or mark a physical store empty when only the online allocation is exhausted.

A worked stockout decision

Consider a fictional Hong Kong homeware shop selling a lamp in black and white. The white variant runs out online, while black remains available and a white display unit exists in one branch but is not for sale. The correct page lets the shopper keep viewing white’s specifications, labels white as unavailable for online purchase, and leaves black available only if its own quantity supports orders. The branch display unit must not become a pickup promise. The shop may offer a notification for white after verifying that it can send alerts, and it may suggest black with the color difference stated plainly. It should not silently switch the cart to black when the customer had selected white.

The team checks four points before releasing this change: the product page with white selected, the catalogue card for white, the final checkout attempt and the submitted external product data. The expected result is that no normal order for white can complete, while black can still complete if its stock remains. The team also tests a stale browser tab opened just before the stockout. It should receive a specific stock message at checkout rather than a mysterious payment failure. If a supplier later confirms a restock, the shop records the source and revises the page only to the confidence level justified by that evidence. A purchase order is evidence of an order placed, not necessarily of delivered stock.

Review the customer promise after replenishment

When stock arrives, do not flip every surface to ‘in stock’ from an unverified receiving note. Check the sellable quantity, variant, damaged or reserved units, and the channel to which units are allocated. Then verify the page, purchase control, checkout and external product data again. If a stock alert was offered, send only to people who requested that particular alert through the intended channel, and make clear that availability can change before they complete an order. The practical standard is simple: at every step, the shopper should know whether the exact item can be bought, what delay applies if orders are accepted, and what evidence supports any stated return date.