All BlueprintsCommerce
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.
What you’ll build.
A waiting list for sold-out stock. Shoppers join the line and can leave it. When three come back in, the first three in line each get one held for them and are told once. A hold nobody claims passes to the next person on its own.
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.
Stock that cannot go negative
You can decrement stock on a sale and prove that a hundred simultaneous orders for ten items produce ten sales and ninety refusals.
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.
Notifications people do not mute
You can notify a user when an event concerns them, show an unread count that survives a refresh, and honour a preference that says stop.
Background jobs
You can hand work to a worker, tell the user it is in progress, and show the result when it lands — and say what happens to that work if the process dies halfway.
Email verification
You can issue a verification link, activate the account when it is followed, and explain what the link contains and why it cannot simply be a user id.
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, 35 tasks.
Every sprint has a goal and a set of tasks. Open a sprint to see the tasks you will pick up.
The shelf
The shop has things with a count, and a thing at zero reads as sold out rather than missing.
5 tasks
- The shop has a way in that a shopper does not
- The shop puts things on the shelf
- A shopper sees what is here and what is gone
- A shopper takes one and the count falls
- Two shoppers, one unit: one buys and one is told
A place in the line
Somebody asks to be told when a sold-out thing comes back, and can stop waiting whenever they like.
5 tasks
- Asking to be told, without making an account
- Asking twice does not make two places
- Stopping waiting takes one press and no account
- A place that has ended never comes back
- The shop sees who is waiting
Three units, fifty people
Stock coming back is held for the front of the line, and nobody else can buy what is being held.
5 tasks
- Stock coming back is an event, not a bigger number
- Three arrive, three are held, for the first three
- A held unit is not for sale
- The person at the front can take the one being held
- More stock than line
Telling them once
The person whose unit is held is told, once, and the message is still true when it is opened.
5 tasks
- The message that says one is yours until a time
- Nobody behind them is told anything
- A second delivery does not tell the same person twice
- Opening it late tells the truth
- The shop can see who was told and when
Nobody is watching
A hold nobody uses ends on its own and passes to the next person in line, with nobody pressing anything.
5 tasks
- A hold that is not used ends on its own
- The unit passes to the next person in line
- Repeating the work does not repeat the message
- The shop finds out when the line stops moving
- Taking it at the second it expires
An address that is really theirs
A place in the line belongs to somebody who can read the address it was asked from.
5 tasks
- A place is not offered anything until the address answers
- Where the position clock starts
- The confirmation has not arrived yet
- A confirmation cannot be guessed or used twice
- Somebody who never asked can make it stop
Where the shop actually is
The shop is on the internet at its own address, and the line keeps moving while the laptop is shut.
5 tasks
- A stranger can reach the shop without you
- The values that only existed on the laptop
- Messages genuinely leave, and point at the live shop
- The line keeps moving with nobody signed in
- A release that was wrong can be undone
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 two people who use it, and what finished means.
How a restock waitlist actually works
Domain you will not have: what the shop is really buying, the three ways stock gets released, and why the window and the batch size are one decision.
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.
Event ticketing with door check-in
Tickets for one event: they sell until the allocation runs out, every seat carries its own code, and the door admits each code once, whatever the signal is doing.
Build restock waitlist.
Start your free week. Adaeze runs your kickoff, and Lars reviews every pull request.