Work · Dayone

One dashboard for a bakery, its wholesale round, and its café

Dayone runs a central production kitchen, a wholesale bakery round, and a café, and was tracking orders, production and stock across Excel sheets. We prototyped the system end to end, from the owner's dashboard down to a driver confirming a delivery on their phone. Development has not started; these are the screens the build will follow.

Ask about this engagement All work

Prototype · pre-developmentFood productionWholesale distributionInventory

Dayone owner dashboard: today's sales at ₹69,650, profit at ₹41,790, 711 of 720 units produced, inventory and wholesale summaries, and tomorrow's unapproved production plan.

01Diagnose

Orders, production, stock and what each wholesale customer owed were tracked across separate Excel sheets, reconciled by hand. There was no single point where the owner could see today's sales, today's production and what needed buying before it ran out.

02Design

An owner dashboard reading sales, profit, production and inventory off one day's data, with tomorrow's plan flagged until approved
Wholesale order entry pre-filled from each shop's standing order, so staff only enter the exceptions
Production planning that nets orders and buffer against stock on hand, then checks the result against recipes and raw-material stock before it reaches the kitchen
Route loading sheets generated from confirmed orders, with a running vehicle total by product
A delivery screen built for a phone with unreliable signal, queuing a confirmation offline and syncing when the connection returns
Role-based screens for kitchen, order, delivery and café staff, with costs and margins removed from the underlying data those roles receive, not just hidden on screen

Wholesale order entry for ABC Store on a phone: five products pre-filled from the standing order, quantities adjustable with plus/minus, totalling ₹905 against a ₹4,820 outstanding balance within credit limit.

Production plan for Thursday: required, buffer and final-plan quantities per product beside a material feasibility check showing maida and chocolate short against kitchen stock. — The plan is exploded against recipes and checked against stock before it reaches the kitchen, so short ingredients are flagged rather than discovered mid-batch.

Raw material stock ledger showing days of cover per item, a purchase recommendation for maida, and an open stock audit recording a −6 kg variance without overwriting system stock. — A purchase recommendation weighs stock, average use and confirmed orders. The owner still approves the number before it becomes an order.

Delivery confirmation on a phone for XYZ Store, offline with two deliveries queued to sync, recording a doughnut shortfall against the vehicle and a UPI payment of ₹477. — Built for the route, not the desk: it holds a queued delivery offline and syncs once the driver's phone reconnects.

03Deliver

workflows prototyped

Counted from the prototype set, September 2026. Pre-development: no build has started.

Next case study

Self-serve booking, and an AI that isn’t allowed to guess

Appooppanthaadi

Read it

Start

Tell us what you’re trying to build

An idea, a stalled project, or a system that has outgrown its architecture. Send it over and we’ll tell you where we would start and whether we’re the right team for it.

Response time: Within one business day
First call: 30 minutes, no deck

Send us a brief hello@galenry.com

Prefer to write first? Send the brief and we’ll come back with questions before we come back with a proposal.