All BlueprintsLogistics
Delivery time slots
Delivery booking for one depot: a customer picks a window that can actually reach their address, each window carries only as many drops as a van can do that morning, and a window that fills up or can no longer be served stops being offered before somebody books into it.
What you’ll build.
Delivery slot booking. Customers see the windows that can reach their address and are still open, take the last place in one and watch it close behind them, and move to another window and watch the first reopen. If a van goes off the road they are told their window can no longer carry them. The depot sees how full every window is.
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.
Choosing a delivery window
You can show the windows available for an address, hold the one a customer picks through checkout, and stop offering a window that is full.
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.
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, 36 tasks.
Every sprint has a goal and a set of tasks. Open a sprint to see the tasks you will pick up.
Who you are delivering to
Somebody can make an account, come back to it, and give the address they want delivered to.
5 tasks
- A customer can register and land signed in
- Signing back in survives a closed laptop
- Signing out on a shared machine leaves nothing behind
- A customer saves an address, and is told which area it is in
- Depot accounts exist, and cannot be self-issued
The windows on offer
A customer sees the windows that can reach their address, each showing the places it has left.
5 tasks
- The depot says which windows it runs, and where to
- A window carries a different number of drops in each area
- A customer sees the windows that can reach their address
- A window nobody can serve is never offered
- A window leaves the list at the stroke of its cut-off
The last place
A customer takes a place in a window, and a window with no places left stops being offered.
5 tasks
- A customer takes a place in a window
- The last place taken closes the window
- Two customers, one place: one wins and one is told
- The product refuses what the list would never have offered
- The places left never disagree with the deliveries in the window
Both sides of the depot
The depot sees how full every window is. A customer sees only their own deliveries, because the product says so.
5 tasks
- The depot sees how full every window is
- The depot sees the drops inside one window
- A customer sees only their own deliveries
- Asking directly for somebody else's delivery is refused
- The depot books a delivery for somebody who rang up
Giving a place back
A delivery can be moved or cancelled, and the place it held goes back on offer.
5 tasks
- A customer cancels, and the place goes back on offer
- Moving a delivery never leaves the customer with nothing
- Cancelling the same delivery twice frees one place
- A place given up after the cut-off is not put back on sale
- The depot moves or cancels a delivery for a customer
A van off the road
A window that can carry less than it sold deals honestly with the deliveries already in it.
5 tasks
- Cutting a window's capacity stops it selling at once
- The depot sees which deliveries are over the line, and where they could go
- Nothing moves until somebody at the depot approves it
- A customer is told their window changed, in time to do something
- A delivery with nowhere to go is not lost
Somewhere a customer can reach
The product is on the internet at its own address, on the depot's clock, and the developer is not part of how it stays there.
6 tasks
- A stranger can reach it without you
- Nothing it needs lives only on your laptop
- The message about a changed window actually arrives
- The cut-off holds on a machine whose clock is not the depot's
- The front door explains itself
- A bad release can be undone in minutes
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, who it is for, and why a delivery window is a count rather than a slot.
How a delivery day actually works
Domain you will not have: rounds, drops, cut-offs, and why a window's capacity is a number somebody has to be able to change.
More logistics Blueprints.
Tool and asset checkout
A tool store for a small builder's yard. Every drill, ladder and transformer is an individual thing with a tag, the store can say who is holding it and since when, and what has not come back is on one screen before somebody needs it.
Returns handling
The returns desk behind a small shop. A customer asks to send something back and says why, the warehouse answers, a parcel turns up that may not match either, and somebody has to decide what happens to the goods and to the money before either can end up in the wrong place.
Fleet maintenance log
A servicing log for a small fleet: every van's history in one place, the next service worked out from how fast that van is actually being driven, and what is due soon and what is already overdue on the front page.
Build delivery time slots.
Start your free week. Adaeze runs your kickoff, and Lars reviews every pull request.