Four connected experiences
The customer-facing SSR Dailli app lets customers book dairy products, including recurring monthly milk bookings for daily doorstep delivery. The SSR Delivery app supports area-based assignments, pickup and delivery locations, and OTP confirmation at pickup and delivery. The SSR Distributors app supports ordering quantities based on demand, tracking amounts paid and outstanding, crates supplied, and empty crates held. A central web application receives orders and sends them to distributors.
Customer app: recurring demand
The recurring booking experience lets a customer arrange milk for a month, with daily delivery. This model creates a different need from a one-time cart checkout and must be easy to understand.
Delivery app: operational confirmation
Delivery agents are assigned areas and can see where products should be picked up and where they need to be delivered. OTP confirmation at pickup and at the destination is part of the described flow.
Distributor app: orders and accountability
Distributors order quantities based on demand and need visibility into payments, outstanding amounts, crates supplied, and empty crates held. These records are central to the distributor experience.
Central web application
The web application receives orders and routes them to distributors, connecting customer demand with the distribution side of the product.
Architecture first
I designed product architecture and core workflows across all four experiences. The original company Figma file is no longer accessible to me, so portfolio visuals created now should be clearly labelled reconstructions—not original design files or screenshots.
Outcome
A live product ecosystem spanning customer commerce, delivery, distributor operations, and central order routing. No numerical outcomes are claimed without verified data.
My contribution
Product architecture and core workflows across four experiences. UI reconstructions should be labelled separately if original source files remain unavailable.