01
Check delivery
The shopper sets a location and the app confirms whether it falls inside the delivery zone.
Zone check→
Case study · Wine Tonight
Wine, bookedto a slot.
A mobile app for ordering wine by the pack and having it delivered — confirm the address is in the delivery zone, browse curated selections, pick a delivery date and time, and check out, all from the phone.
What we shipped
Delivery-zone checkCurated packsCart & checkoutDelivery date & slotGuest browsingOrder history
01 — The product
From an address to a booked delivery
The app confirms the delivery zone up front, presents wine as curated packs rather than an endless grid, then walks a clean path through cart, a chosen delivery slot and payment — with a guest able to browse before committing to an account.
Delivery zone, checked first
A location check confirms an address is serviceable before the shopper invests any time, with clear delivered and not-delivered states rather than a failure at checkout.
Packs, not a wall of bottles
Wine is browsed as curated packages grouped by style — red, white, low and medium alcohol — each showing its bottle count and the wines included, so choosing is a shortlist, not a search.
Delivered to a slot
Alcohol delivery is scheduled, so checkout includes a delivery date and a chosen time slot instead of pretending an order can arrive the instant it is placed.
02 — The problem
Why does ordering wine for delivery need its own app?
A generic store grid gets three things wrong for wine, and each one loses the sale at a different point. The app is shaped around fixing all three.
Will you even deliver here? Alcohol delivery is bound to a zone. Asking that question first — with a real serviceable check — beats letting a shopper fill a cart only to be turned away at the end.
Choosing a bottle is intimidating. Faced with hundreds of labels, most shoppers stall. Curated packs by style, each listing the bottles inside, turn an open-ended search into a confident pick.
It arrives when someone is home. Wine delivery is scheduled, not instant, so the flow has to make picking a delivery date and time slot feel like a normal step, not an afterthought bolted onto checkout.
3
things a generic store grid gets wrong for wine — each one loses the sale at a different point.
03 — Goals & challenges
What Wine Tonight had to get right
A wine app lives or dies on the order in which it asks things. The build followed the same logic the shopper does.
Goals
Ask things in the right order
- Gate on the delivery zone first. Never let a shopper build an order the app can't fulfil.
- Turn the catalogue into packs. Curated selections by style, not an endless product grid.
- Make delivery a booking. A date and time slot as a first-class checkout step, not an afterthought.
- Let guests look before they commit. Browsing works before an account does.
Challenges
Why it was hard
- Alcohol delivery is bound to a zone, so serviceability has to be checked before anything else, not at checkout.
- Faced with hundreds of labels, most shoppers stall — the catalogue had to guide, not just list.
- Wine delivery is scheduled, not instant, so a date-and-slot step had to feel native to checkout, not bolted on.
- Guest browsing and a full account path had to sit side by side without forking the experience.
04 — The ordering path
How does an order actually flow?
02
Browse packs
Curated packages by style are browsed and sorted, each showing its bottle count.
Catalogue→
03
Open a pack
A pack reveals the bottles it includes, its stock state, and an add-to-cart or buy-now.
Pack detail→
04
Cart & checkout
The basket is reviewed and the shopper moves into a clean, staged checkout.
Checkout→
05
Pick a slot
A delivery date and a time slot are chosen, turning the order into a booked appointment.
Delivery slot→
06
Pay & confirm
Payment completes the order and a thank-you screen confirms the booked delivery.
Confirmed✓
keep scrolling — the deal glides left →
05 — Generic store vs Wine Tonight
What changes when the app is built for wine
A generic store grid gets three things wrong for wine — this is what changes when the app is shaped around fixing them.
Ordering wine
A generic store app
In Wine Tonight
Can it reach me?
Found out at checkout
Delivery-zone check before you browse
What to buy
Scroll a huge grid
Curated packs by style with bottle counts
When it arrives
Vague ‘soon’
A chosen delivery date and time slot
Browsing first
Sign up to look
Guest browsing before an account
After the order
An email receipt
Order history with per-order detail
06 — How we built it
How did we design and build it?
A wine app lives or dies on the order in which it asks things — the build followed the same logic as the shopper.
Gate on the delivery zone
Serviceability firstThe location check was designed as the first real interaction, so the app never lets a shopper build an order it cannot fulfil — the delivered and not-delivered states set the tone before anything else.
Turn a catalogue into packs
Guided choosingInstead of an endless product grid, wine was organised into curated packs by style, each opening to the bottles it contains, so choosing feels guided rather than overwhelming.
Make delivery a booking
First-class stepThe date-and-time-slot step was built into checkout as a first-class stage, because scheduled delivery is how alcohol actually moves and hiding it causes failed drop-offs.
Let guests look before they commit
Guest & accountGuest browsing and a full account path were designed side by side, so a first-time shopper can explore packs and a returning one can reorder from their history.
08 — What we shipped
The scope, in one panel
Every number in this panel is delivered scope — what was designed, built and handed over on the wine retail build for Wine Tonight. It leaves out traffic, conversion and revenue on purpose: those figures belong to the client, and we don’t publish numbers we cannot stand behind.
3
Problems solved before payment — zone, choice, schedule
6
Steps from delivery check to confirmed order
4
Pack styles — red, white, low and medium alcohol
1
Guest path before an account is required
- Industry
- Wine retailAlcohol delivery
- Platform
- Mobile appCustomer-facing
- Users
- CustomerGuest & account
- What we did
- UI/UX designProduct + mobile build
07 — Cart to confirmation
The back half of the order
From a reviewed basket to the slot that turns an order into an appointment, and the screen that confirms it.
Thank you. Confirmation that the order is placed and a delivery slot is booked.
09 — Visual design
The look, and why
A warm amber the colour of the product itself carries the accents, a near-black ink keeps labels and prices legible, and a soft mist grounds the packs without competing with the bottles.
Colour
Amber
#C1922E
Deep
#8A6A1E
Body
#5A5248
Mist
#F7F3EA
Typography
Wine, booked to a slot
From an address to a booked delivery
Curated packages grouped by style, each showing its bottle count and the wines included.
RED · WHITE · LOW ALC · MEDIUM ALC
10 — Transferable
What does a scheduled-delivery app need to get right?
Wine forced these decisions, but the pattern carries to anything delivered locally on a schedule.
01
Gate on serviceability first
Confirm the address can be served before a shopper invests any time — a zone check up front beats a refusal at checkout.
02
Turn a catalogue into a shortlist
Curated packs by style, each listing what's inside, turn hundreds of labels into a confident pick instead of an open-ended search.
03
Make scheduled delivery a booking
A delivery date and time slot belongs in checkout as a first-class step, not an afterthought — that's how alcohol actually moves.
04
The pattern travels beyond wine
A delivery-zone gate, a curated catalogue and scheduled-slot checkout carry to groceries, meal kits, flowers and anything else delivered locally on a schedule.
FAQ
Building a wine delivery app
What does the Wine Tonight app do?
It lets a shopper order wine for delivery from their phone. It checks that their address is inside the delivery zone, presents wine as curated packs grouped by style, and walks them through cart, a chosen delivery date and time slot, and payment — with guest browsing before an account and an order history afterward.
How long does it take to build a wine or alcohol delivery app?
An ordering-and-delivery app at this shape — serviceability check, a curated catalogue, cart, scheduled-slot checkout and payment — is a multi-phase build rather than a few weeks. What moves the timeline most is the delivery-zone logic, the payment integration, and any age or licence verification a market requires. We phase it so browsing and cart ship before the scheduling and payment layer.
Why check the delivery area before browsing?
Because alcohol delivery is bound to a serviceable zone, and a shopper who fills a cart only to be refused at checkout rarely comes back. Confirming the address up front, with clear delivered and not-delivered states, respects the shopper's time and protects the conversion.
Can the same approach sell things other than wine?
Yes. The pattern — a delivery-zone gate, a curated catalogue, and scheduled-slot checkout — carries to groceries, meal kits, flowers and anything else that is delivered locally on a schedule. The catalogue and any compliance step change; the flow does not.
Let's build
Selling something you deliver on a schedule?
Tell us how your business actually works and we'll tell you honestly what it takes to build — the zone check, the catalogue, the booked slot. No deck, no pitch.