Who asked: Priya Raman, operations lead at Ridgeway Hardware, a fictional supplier of tools and fixings to builders.
Why: orders arrive by phone and email and are typed into a spreadsheet. Mistakes slip through: orders shipped before payment checks, coupons applied twice, the same SKU on three lines. Priya wants the rules in code that the new web shop and the phone desk can share.
What you build: Order and OrderLine with validation; a lifecycle from Draft to Submitted to Shipped (or Cancelled) that refuses illegal moves; optional coupon codes; a generic Store<T>; a StatusChanged event for the warehouse; shipping rules as functions; a sales report; and an OrderService that places an order end to end.
Done looks like: OrderService.Place turns a customer's lines and coupon into a stored, submitted order, or a clear failure message, and every status change appears in its log.
Ridgeway Hardware's order desk needs a small C# library for orders. You build it in eight steps, each one starting from the code you finished in the step before, and each one adding a skill from this level: records and validation, a status lifecycle with custom exceptions, optional coupons, a generic store, events, shipping rules passed as functions, a LINQ report, and a service that ties them together.