All BlueprintsCommerce
Order lifecycle for a kitchen
The order board a small kitchen runs service on. An order moves from placed to cooking to out for delivery through the moves that are legal and no others, the customer watches it happen on their own phone, and a cancellation stops the kitchen rather than arriving after the pan is already hot.
What you’ll build.
A food order that moves in front of you. The customer watches it go from placed to cooking to out for delivery without refreshing. The kitchen and the rider each do their own job and cannot do each other's. Cancelling works until cooking starts, and every change is on the record with a name and a time.
What you’ll learn.
Each sprint is built around one skill. You show you have it in a pull request your team reviews, then explain it in a walkthrough.
Authentication
You can register and sign in a user, keep a request authenticated without asking for the password again, and explain where the credential lives in the browser and why there rather than somewhere else.
An order that moves through states
You can move an order through its states, refuse a transition that should not happen, and show the history of how it got where it is.
Roles and permissions
You can give users different roles and have the server refuse what a role may not do — not merely hide the button — and show the refusal working against a request the interface never offered.
Realtime updates
You can push a change from the server to an open page and have a second browser see it — and say what happens to a client that was disconnected while it changed.
Going live
Somebody who has never met you can open a URL and use the product — and you can say what is different about the copy running there, where its secrets come from, and what you do when a release turns out to be wrong.
The roadmap. 7 sprints, 30 tasks.
Every sprint has a goal and a set of tasks. Open a sprint to see the tasks you will pick up.
Everyone who touches an order
The kitchen, the riders and the customers are three kinds of person the system can tell apart, and a tablet stays signed in through a whole service.
4 tasks
- A customer can sign up and land signed in
- Coming back to the same account, and leaving it properly
- Kitchen and rider accounts exist, and nobody issues themselves one
- A tablet signed in at five is still signed in at midnight
The moves that are legal
An order exists, moves forward through the moves that are legal, and refuses everything else, including the second tap on a wet screen.
5 tasks
- A customer places an order and it lands on the kitchen's board
- An order moves forward through its stages
- A move that is not allowed is refused, and says what state the order is in
- Tapping start twice starts one order once
- The board is readable at arm's length and puts the waiting orders first
Who may move what
The kitchen can start cooking and cannot mark delivered, the rider the other way round, and the server is what refuses rather than a missing button.
4 tasks
- The kitchen's moves and the rider's moves are different moves
- A move nobody was offered is still refused
- Each role opens the one screen that is theirs
- A customer sees their own orders and nobody else's
The screen they watch
A customer watching on a phone sees each move as it happens, and a phone that was asleep catches up instead of showing something that stopped being true.
4 tasks
- The customer's screen changes the moment the kitchen moves the order
- New orders and rider pickups appear on the board without a reload
- A screen that was asleep catches up instead of lying
- A live connection carries only what its holder may see
Stopping the kitchen
A customer can cancel until the kitchen starts, a simultaneous cancel and start produces exactly one outcome by a rule decided in advance, and the one who lost is told something true.
4 tasks
- A customer can cancel while the kitchen has not started
- A cancelled order comes off the board while the kitchen is looking at it
- Cancel and start in the same instant produce exactly one outcome
- Whoever lost the race is told what actually happened
How it got here
Every move is kept with its time and the person who made it, and a week later anybody can read the whole story of an order including the moves that were refused.
4 tasks
- Every move is kept, with its time and the person who made it
- The customer's screen shows the whole evening, not one word
- A move that was refused is recorded too
- An order from last week can be found and read in full
Service starts at six
The board is on the internet at its own address, the live screens survive being there, and the person who built it is not part of how it stays up.
5 tasks
- The board answers at its own address, on somebody else's phone
- The live screens survive being on the internet
- Nothing the product needs to run is in the repository
- Somebody else can put a change live, and put it back
- When the board goes blank at seven on a Friday, somebody can say why
Read before you build. The best engineers do.
Senior engineers read the docs before they touch the code. Every Blueprint comes with short documents on the product and its world, the kind a team hands a new hire. Read them well and you ask sharper questions and walk into every review prepared.
What you are building
The product, the three people who use it, and what finished means.
How a kitchen actually runs service
Domain you will not have: the pass, the ticket rail, why an order sitting at placed is the expensive failure, and what cancelling costs at each stage.
More commerce Blueprints.
Corner shop storefront
A small shop sells online. The shelf shows what is genuinely there, a basket survives the tab it was made in, the shop never takes money for a tin it does not have, and the buyer can follow their order until they pick it up.
Food ordering with options
Ordering for one restaurant, where a dish is a set of choices rather than a price. A size replaces the base price, extras add to it, some extras only exist on some sizes, and the total the customer is charged is worked out from what they chose rather than taken from the browser.
Restock waitlist
A waiting list for what a small shop has run out of. People ask to be told when it returns, and when three come back the stock goes down the line in the order they asked: held long enough to act on, offered to nobody behind them until that window closes, and never offered to the same person twice.
Build order lifecycle for a kitchen.
Start your free week. Adaeze runs your kickoff, and Lars reviews every pull request.