Designing Trustworthy In-Stock and Out-of-Stock Answers for Amazon Item Pages

Quick Overview

A product design question for Amazon product managers: design the service that tells shoppers on a product detail page whether an item and each of its variants can be bought. It tests stakeholder mapping, availability states, accuracy versus freshness trade-offs at high traffic, out-of-stock experiences, and success metrics with guardrails.

Designing Trustworthy In-Stock and Out-of-Stock Answers for Amazon Item Pages

Company: Amazon

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager at Amazon. Every product detail page, the page for one item where shoppers choose options such as size or color and add it to their cart, has to tell shoppers whether the item is in stock and can be bought. Design the stock availability service behind that answer. ```hint Wrong in both directions Work out what goes wrong when the page claims stock that is not really sellable, what goes wrong when it hides stock that is, and which people and Amazon surfaces besides the shopper rely on the same answer. ``` ### Clarifying Questions - Is the deliverable the shopper-facing experience on the page, the platform behind it that computes availability, or both? - Should it cover items that third-party sellers store and ship themselves, whose stock Amazon does not hold, as well as items in Amazon's own warehouses? - Should the service also produce the delivery date shown next to the stock status, or only whether the item can be bought? - Which marketplace is in scope, and does availability need to differ by the shopper's delivery address? ### What a Strong Answer Covers - The users of the service: shoppers, sellers, and the other Amazon surfaces and teams that reuse the availability answer - The harm from availability being wrong in each direction, and from vague states that leave shoppers with no next step - A prioritized design of availability states, answers specific to each variant and location, and the out-of-stock experience - How availability is computed and kept fresh for a very high-traffic page, with the accuracy, latency and fallback trade-offs a PM must decide - Success metrics with guardrails, such as stock-related order cancellations alongside page conversion ### Follow-up Questions - The page tells shoppers that only a few units are left. How do you keep that note accurate when many people view the item at the same moment, and should it be shown at all? - How should availability behave during a large sales event, when popular items can sell out within minutes? - Which mistake costs Amazon more, showing an item in stock that cannot ship or hiding one that could have sold, and how would you decide where to set the balance?

Overview: A product design question for Amazon product managers: design the service that tells shoppers on a product detail page whether an item and each of its variants can be bought. It tests stakeholder mapping, availability states, accuracy versus freshness trade-offs at high traffic, out-of-stock experiences, and success metrics with guardrails.

Amazon logo
Amazon
Oct 12, 2026
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are a product manager at Amazon. Every product detail page, the page for one item where shoppers choose options such as size or color and add it to their cart, has to tell shoppers whether the item is in stock and can be bought. Design the stock availability service behind that answer.

Clarifying Questions Guidance

  • Is the deliverable the shopper-facing experience on the page, the platform behind it that computes availability, or both?
  • Should it cover items that third-party sellers store and ship themselves, whose stock Amazon does not hold, as well as items in Amazon's own warehouses?
  • Should the service also produce the delivery date shown next to the stock status, or only whether the item can be bought?
  • Which marketplace is in scope, and does availability need to differ by the shopper's delivery address?

What a Strong Answer Covers Guidance

  • The users of the service: shoppers, sellers, and the other Amazon surfaces and teams that reuse the availability answer
  • The harm from availability being wrong in each direction, and from vague states that leave shoppers with no next step
  • A prioritized design of availability states, answers specific to each variant and location, and the out-of-stock experience
  • How availability is computed and kept fresh for a very high-traffic page, with the accuracy, latency and fallback trade-offs a PM must decide
  • Success metrics with guardrails, such as stock-related order cancellations alongside page conversion

Follow-up Questions Guidance

  • The page tells shoppers that only a few units are left. How do you keep that note accurate when many people view the item at the same moment, and should it be shown at all?
  • How should availability behave during a large sales event, when popular items can sell out within minutes?
  • Which mistake costs Amazon more, showing an item in stock that cannot ship or hiding one that could have sold, and how would you decide where to set the balance?