Out-of-stock: the invisible cost and the SEO damage

The global retail industry loses about US$ 1.2 trillion a year to out-of-stocks alone, inside a total US$ 1.7 trillion hole of inventory distortion, according to IHL Group.^[1] But the number that hurts isn't in that abstract trillion — it's in your store, in the product that went viral in the ad and sent the customer to a page that says "unavailable".

The immediate cost: the customer won't wait

When they hit the stockout, the customer does one of four things — and only one of them keeps the sale with you.

The classic Corsten and Gruen study, which aggregated stockout research from around the world, mapped consumer behavior in front of a "sold out":^[2]

• Buys a substitute in your store — the only good outcome for you.
• Delays the purchase — maybe comes back, maybe forgets.
• Buys the same item at another store — around 36% of cases. You didn't lose a sale; you handed the customer to the competition.
• Gives up entirely — sale evaporated.

The perverse detail: whoever ended up at the competitor may not come back. The real cost of a stockout isn't the price of the sold-out item — it's the lifetime value of the customer who discovered the competitor also solves their problem. It's the same logic that moves the conversion rate: every bit of friction on the path to purchase pushes the customer toward the exit.

Out-of-stock is the worst of both worlds: you paid to attract the customer — media, SEO, time — and handed them on a platter to whoever had the product on the shelf.

Synthesis of the study "Stop Wasting Money on Out-of-Stocks" (Corsten & Gruen)

The SEO damage nobody sees

Here's the angle most stores ignore. A product that sells out doesn't just disappear from inventory — it has a URL that Google indexed, that may rank well, that may have links pointing to it. What you do with that page decides whether you preserve or destroy that SEO asset.

Google's own guidance is clear: for a temporarily sold-out product, keep the page live, don't return a 404 or redirect. Use the correct availability structured data and offer paths (notify me when it's back, similar items).^[3]

Schema.org and the availability signal

The Product structured data has an availability field — availability — that tells Google and Google Shopping whether the item is InStock or OutOfStock. The classic problem is divergence: the page shows "sold out" to the customer, but the JSON-LD still says InStock (or the reverse). That produces a wrong rich snippet, a warning in Merchant Center and, at the limit, a Shopping listing suspension for "incorrect availability".

"offers": {
  "@type": "Offer",
  "price": "199.90",
  "priceCurrency": "BRL",
  "availability": "https://schema.org/OutOfStock"  // must match the page
}

Keeping availability in sync with real inventory is part of having a well-configured Product Schema.org — and it's exactly the kind of thing that breaks silently in a theme change or an ERP integration.

Silent stockout: when the site lies about inventory

Worse than showing "sold out" is showing the wrong inventory. Both sides of that coin are expensive.

• Sells what it doesn't have: the site shows "buy", the customer pays, and at picking it turns out it ran out. Result: cancellation, refund, complaint — and the same reputation damage as a stuck order.
• Hides what it has: a desync between ERP and store marks a product as sold out while it's sitting in the warehouse. You lose the sale of an available item and never know.

The cause is almost always the same: inventory lives in the ERP/marketplace and is mirrored in the store by an integration or feed. When that feed lags, stalls or partially fails, the storefront starts telling a story that isn't true — with no 500 error, nothing visibly broken.

What to monitor

Correct inventory is an observability problem, not just an ERP one. Four signals are worth an alert:

1. % of product pages out of stock: a sudden jump (from 3% to 30% in a day) is almost never real sales — it's the feed or the inventory integration that broke.
2. Top sellers sold out: a stockout on your best-selling products is the most expensive. A dedicated alert for your top 20 pays for itself.
3. Schema × page divergence: the page says sold out and the JSON-LD saysInStock (or vice versa). A sign of a template/integration regression.
4. Indexed pages that went out of stock: URLs that rank and entered a stockout — they most deserve the "keep live + notify me when it's back" treatment.

The honest summary

Stockouts are treated as a purchasing problem, but they're also an SEO, conversion and reputation problem. The lost sale is the visible tip; beneath it are the customer who migrated, the ranking that decayed and the suspended Shopping listing. A well-run store doesn't avoid 100% of stockouts — that's impossible — but it knows about the stockout instantly, handles the page the right way, and doesn't let the site lie about what's on the shelf.