Seller Operations Hub for Amazon Marketplace Merchants: Design and Success Metrics

Independent businesses sell their products in Amazon's store alongside Amazon's own retail listings. Design a platform or dashboard for these third-party sellers, and explain how you would measure whether it succeeds. Answer in two parts. ### Clarifying Questions - Which sellers are we designing for: brand-new sellers, established small and mid-sized businesses, large brands, or sellers who rely on Amazon to store and ship their inventory? - Is this a redesign of the tools sellers already use, or a new product focused on one particular job? - What is Amazon's main goal here: growing seller sales, retaining sellers, improving what shoppers experience, or reducing seller support costs? - Should we design for desktop, mobile, or both? ### Part 1 — Design the seller platform Choose the sellers you will serve, identify their most important jobs and pain points, and design the platform or dashboard: its main modules, what the home view shows, and what the first version includes. ```hint Start from decisions List the decisions a seller makes each day or week, such as restocking, repricing or fixing a listing, and let those decisions shape the home view rather than the data that happens to be available. ``` #### What This Part Should Cover - A chosen seller segment with reasons, and its key jobs across listings, pricing, inventory, advertising, fulfillment and account health. - Prioritized pain points and the features that address them, with a clear first-version boundary. - A home view that surfaces what needs attention and why, not a wall of reports. ### Part 2 — Define success metrics Explain how you would measure whether the platform succeeds, for sellers and for Amazon. ```hint Usage is not success A seller can spend hours in a dashboard without selling more. Decide which metric shows the platform changed seller outcomes, and which ones would reveal harm to shoppers or to sellers' margins. ``` #### What This Part Should Cover - One primary metric tied to seller outcomes, with the reasoning behind it. - Adoption and engagement metrics for the platform, kept separate from seller business outcomes. - Guardrails for shopper experience, seller profitability and support load. - How causal impact would be measured, given that sellers compete with each other. ### What a Strong Answer Covers - A consistent line from the chosen segment to its pain points, the features and the metrics. - Awareness that the marketplace has three parties, sellers, shoppers and Amazon, whose interests can conflict. - Real trade-offs, such as automation versus seller control and simplicity versus depth. - Edge cases and risks: new sellers without history, seasonal sellers, delayed data and seller distrust of recommendations. ### Follow-up Questions - How would the design differ for a seller with a handful of products versus one managing thousands? - If the platform's pricing suggestions raise a seller's sales but erode their margin, how would you detect and handle it? - Many sellers already pay for outside analytics tools. How would you decide what to build into the platform and what to expose through APIs?