Preparing your design workspace

Loading the problem and your saved attempt…

Design an Inventory Tracking System

Model a small store's stock so receiving, selling, and count corrections keep quantities correct and explainable.

Design the classes for an in-memory inventory tracking system used by one small store. For this exercise, assume the following product facts. A store manager registers each product once with a unique SKU, a display name, and a reorder threshold.

Stock changes only through three kinds of movement: receiving a delivery adds units, recording a sale removes units, and recording a manual count correction sets the counted quantity and must carry a reason.

A sale that asks for more units than are on hand is rejected and changes nothing, and a quantity can never go below zero. The manager can read the current quantity of a SKU, list every product whose quantity is at or below its reorder threshold, and read the movements recorded for one SKU in the order they happened.

Everything runs in one process on one thread, and nothing has to survive a restart. Prices, payments, suppliers, purchase orders, reservations, and multiple stores are out of scope.

No code is required: produce the requirements, object model, method contracts, and one walkthrough, then extend the design in the follow-up.