Dairy subscription · Food & grocery
Milkrun
The first good thing every morning.
A morning dairy and essentials subscription delivered by 7 am.


The idea
Bringing back the wholesomeness of the morning milkman with modern subscription technology. Farm-fresh cow and buffalo milk, curd, paneer, and bakery essentials delivered quietly before dawn.
Features a calendar-first UX where users can modify quantities, pause for vacation, or add eggs for tomorrow until 10 PM tonight.
- 01
The 10 PM Cutoff Clock
Clear countdown timer giving households total control to tweak tomorrow’s order until bedtime.
- 02
Vacation Mode
Effortless drag-to-pause calendar range that prevents unwanted deliveries while travelling.
- 03
Bottle Return Ledger
Transparent tracking of returned glass bottles with environmental waste credits.
The problem
Many urban households still buy milk through a local vendor with no price record and no way to check quality. The packet or can arrives, the family trusts it, and the only complaints channel is a phone call. Subscription delivery apps replaced the vendor with a screen, but they often treat milk like any other grocery order, with a long cutoff window, a surprise deposit and little proof of what is in the bottle.
Milkrun is a concept dairy subscription for Bengaluru neighbourhoods. The idea is simple: pick your milk, set a repeat pattern, and change tomorrow's order until 10 pm tonight. Delivery is promised by 7 am in returnable glass bottles, and every batch can be traced to a farm and a lab report.
Who it is for
- Household customerA repeat order that adjusts to guests and travel, a wallet that never goes negative, a clear bottle deposit, and a way to see where the milk came from.
- Delivery runnerA route sorted by building, a checklist of items and empties for each stop, proof at the door, and a view of the day's earnings.
- Dairy operationsOvernight demand, farm intake, lab quality, route plans and bottle stock in one view, with the power to hold a batch.
- Studio client in food or D2CA reference for subscription calendars, wallet logic and a physical-return loop.
What we built
Every side of Milkrun, live.
Each one opens the real build in a new tab. On a laptop the apps sit in a phone frame; on a phone they run full screen.
Interactive monthly subscription calendar, 10 PM cutoff countdown, and bottle wallet.
Customer app
Interactive monthly subscription calendar, 10 PM cutoff countdown, and bottle wallet.
Open /app ↗Early-morning doorstep route manifest, empty bottle pickups, and photo delivery proof.
Delivery app
Early-morning doorstep route manifest, empty bottle pickups, and photo delivery proof.
Open /driver ↗Dairy Ops
PROD BUILDNightly demand aggregation, milk procurement batching, and crate route logistics.
Dairy Ops
Nightly demand aggregation, milk procurement batching, and crate route logistics.
Open /ops ↗Website
PROD BUILDFarm-to-glass testing reports, farm sourcing transparency, and subscription plans.
Website
Farm-to-glass testing reports, farm sourcing transparency, and subscription plans.
Open /home ↗Brand book
PROD BUILDVintage dairy typography, gentle pastoral illustrations, and packaging standards.
Brand book
Vintage dairy typography, gentle pastoral illustrations, and packaging standards.
Open /brand ↗In detail
Surface by surface
Customer app · /app
The customer app has a welcome flow (phone and OTP, service area, preferences), a home screen with a cutoff clock, a month calendar with day editor, plans, a product shop, an away mode for travel, a wallet with top-up, withdrawal and monthly statements, a bottles screen, household members and a trace screen. A morning view shows the delivered card and a proof page. A scanner screen reads a batch code, though the scan itself is simulated in the prototype.
Delivery app · /driver
In the code this is the runner app under /runner, not /driver. It has a today view, a load checklist for the crates, a route list and map, a stop detail with an item checklist, an empties counter, an issue sheet and a proof step, then a done page and an earnings page. The proof photo is chosen from sample images, not taken with a camera.
Dairy Ops · /ops
The ops dashboard has an overview, farms, quality, routes and bottles pages. It charts litres by product and trips per route, shows a plant timeline, lists farm cards, and lets an operator hold a batch through a dialog. Quality results and bottle counts come from generated sample data.
Website · /home
The website covers how it works, farms and individual farm pages, the products list, a quality page, the bottle loop, a public batch trace page, runner recruitment, FAQ, about and legal pages. A subscription calendar demo and a night-to-morning scroll animation explain the timing without a signup.
Brand book · /brand
The brand section is built from the same code: a Grass Green, Milk White, Butter Gold and Morning Sky palette, bottle cap colours that appear in the product data, and illustration pieces such as a sunrise sky and a skyline silhouette used across the screens.
Why it works this way
Design and product decisions
A 10 pm cutoff with a timeline behind it
Edits for a delivery date close at 10 pm the night before, with a reminder at 9:45 pm and a closing state from 8 pm. The code then lays out the night: packing at 1:30 am, loading at 4:15 am, the round starting at 4:50 am and delivery by 7 am. A fixed cutoff lets the dairy plan, and the countdown lets the customer trust it.
Four ways to repeat an order
A subscription can be daily, every alternate day, on chosen weekdays, or custom with a different quantity per weekday. Away mode skips a date range and shows what will be removed before confirming. Households rarely drink the same amount every day, so the calendar had to match that.
Milk comes first when the wallet runs short
When the basket locks and the available balance does not cover everything, lines are sorted: milk subscriptions first, other subscriptions second, one-off extras last, cheapest first within each group. Whatever fits is kept and the rest is dropped, so the household still gets milk. The wallet is never allowed to go negative.
An honest deposit and a bottle ledger
Glass bottles carry a deposit of 25 rupees for the 200 ml size and 50 for the 500 ml and 1 litre sizes, held in the wallet and refunded for bottles returned once the household has no active glass subscription. A ledger tracks bottles with you, bottles returned for life, and two free breakages a year, with milestones at 25, 50, 100 and 250 returns.
Engineering notes
Under the hood
Next.js with pure business rules
The calendar, wallet and bottle logic are plain TypeScript functions that take state and return the next state plus a list of transactions, with an error type that fires if the balance would fall below zero. That keeps the rules testable apart from the screens.
India time handled by hand
A time module converts everything to Indian Standard Time with a fixed 5.5 hour offset and builds ISO strings ending in +05:30. This avoids a household seeing a different cutoff because of a device time zone.
Generated sample data in JSON
Batches, lab results, customers, subscriptions, wallet transactions and stops are generated JSON files, joined with curated TypeScript for products, farms, cows and hubs. Batch codes are derived from farm code, session and date so a trace page can look them up.
Local details
Built for India
Wallet top-ups in UPI terms
Top-ups are labelled as UPI payments, and auto top-up is labelled UPI Autopay, with a threshold and an amount the customer sets. Withdrawals go back to the original UPI. These are labels on simulated transactions; there is no payment integration.
Indian milk types and quality tests
Products include A2 Gir cow milk, and the lab report template defines 22 tests covering fat, solids-not-fat, protein, freezing point and adulterants such as urea, detergent, starch, formalin, boric acid and antibiotic residue. The explainers are written in plain words for a buyer worried about adulteration.
Neighbourhood hubs
Four Bengaluru hubs (HSR, Indiranagar, Jayanagar and Malleshwaram) and routes named for areas such as Koramangala and Bellandur. Onboarding asks for a service area first, since coverage is the first question for any hyperlocal service.
What this is, and is not
Milkrun is a front-end prototype with sample data. There are no real farms, lab certificates, riders or payments, the batch scanner returns a fixed code, and the delivery photo comes from sample images. Prices, deposits and the sorry credit are illustrative. A production service would need cold-chain handling, food licensing, a payment partner with wallet compliance, a real routing and dispatch backend, and lab data fed from actual testing.
Last updated 2026-11-07
Brand system
Building something like Milkrun? Let's talk.
We'll walk you through this build on a call and map what yours would need.