Who asked: Dara Quinn, who runs wholesale at Hartwell Coffee Roasters, a fictional roastery.
Why: cafes order by email, and Dara retypes every order into a spreadsheet. A small web page will let cafes order directly; it needs an API behind it.
What you build: Order and OrderLine in EF Core with an OrdersContext; an OrderDto for responses; an OrderService that places, reads, cancels and lists orders; the registrations; and the endpoints GET /orders/{id}, POST /orders, POST /orders/{id}/cancel and GET /orders?customer=.
Done looks like: a cafe can place an order and get 201 with its location, read it back, cancel it once (204, then 409), and page through its orders; bad input gets a 400 with a message per field, and unknown orders get 404.
Hartwell Coffee Roasters sells beans to cafes, and its orders live in emails. You build the API its new ordering page will call, in six steps, each starting from the code you finished in the step before: an EF Core model, an OrderService, registrations and a GET endpoint, a validated POST, cancellation, and a paged list per customer. It runs on the same labelled stand-ins as this unit's lessons.