JaazbiaKHAN
Back to all work

Odero · Vendor ordering app, iOS

Making confident purchasing simple

What is Odero?

Odero is a mobile app that helps restaurant owners order ingredients and supplies from vendors quickly and efficiently. It streamlines ordering by surfacing trusted vendors, making it easy to reorder frequently used products, and keeping order tracking simple.

The goal of the design was a clear, accessible interface that lets owners place orders confidently without slowing down their daily operations.

Most of the time we’ll end up wasting, like, three or four hours just gathering the quotes every month.

Taha · Cafe owner, Lucknow
Role
UX/UI Designer
Timeline
2026
Scope
3 red routes, iOS
Tools
Figma

About the project

Odero at a glance — three red routes on iOS

Process

Five stages of design

The process focused on understanding what restaurant owners actually do each morning, then building an interface simple enough to survive that. Research, synthesis, preparation, design, prototype — each stage narrowing what the product needed to be.

  1. 01

    Problem space

    • Secondary research
    • Primary research — interviews
  2. 02

    Synthesis

    • Affinity map
    • Personas
    • Empathy mapping
    • JTBD
  3. 03

    Preparation

    • HMW questions
    • Identifying red routes
    • User flow of red routes
  4. 04

    Design

    • Competitive analysis
    • Wireframes
  5. 05

    Prototype

    • Interactive prototype
    • Usability testing

Interviews

Four owners, four different systems

I interviewed four restaurant owners and managers across different cuisines, a mix of fast-food and dine-in, varying years of experience, and — crucially — different ordering channels. Between them they were using apps, WhatsApp, phone calls and paper vendor ledgers, often all at once.

Who I interviewed

Participants: four restaurant owners and managers

  • Different cuisines
  • A mix of fast-food and dine-in
  • Varying years of experience
  • Different ordering channels — apps, WhatsApp, calls, vendor ledgers

Affinity maps

  • Ordering is manual and time-consuming
  • Quality assurance is a must
  • Owners want simplicity
  • A lack of tools in the market
  • Delivery issues
  • The importance of relationships
  • Time pressure and operational load
  • Frequency of restock
  • A need for order accuracy
  • Aquib

    Franchisee owner
    Halifax, Canada

  • Asim

    Restaurant manager
    Toronto, Canada

  • Taha

    Cafe owner
    Lucknow, India

  • Mohammad

    Restaurant owner
    Toronto, Canada

  • “Hardest part? I would say keeping up track — what’s going in and what’s going out.”
  • “They just offload the pallet, and my team has to unpack everything. That’s extra labour for us.”
  • “Most of the time we’ll end up wasting, like, three or four hours just gathering the quotes every month.”
  • “If everything — rates, quantities, suppliers — was in one place, it would save me a lot of stress.”
  • “Mostly phone and WhatsApp for ordering; emails are used occasionally for price changes.”

The original names have been changed.

Ten themes came out of the affinity mapping, but they pointed at one thing: ordering is manual and time-consuming, and the tools on the market do not fit how these businesses actually run.

Personas

Two ways of being overwhelmed

The four interviews resolved into two distinct personas, each with their own goals, motivations and ordering habits — and each overwhelmed in a different way.

The hands-on owner

“Even though I have staff, I have to do the micromanagement.”

Runs a small, quality-focused cafe where ingredients matter. Coordinates staff and deliveries himself, and compares vendor prices by hand. He tracks orders through WhatsApp and a ledger.

The structured multi-unit manager

“Sometimes it’s way too much to handle.”

Runs a busy quick-service restaurant where demand changes rapidly, handling inventory, purchasing, staffing and customer experience simultaneously. He uses digital systems, but nothing feels unified.

Empathy maps

Empathy maps for both personas.

Jobs to be done

Four jobs the product had to do

Framing the findings as jobs rather than features kept the focus on what owners were trying to achieve, not what a screen might contain.

  • JTBD 1

    Main job: Assess stock levels across locations quickly

    Related jobs

    • Verify low-running items before they disrupt operations
    • Align ordering decisions with real inventory conditions

    Why — need statement

    Reduce the time required to verify stock levels across multiple locations.

  • JTBD 2

    Main job: Convey order details clearly to vendors

    Related jobs

    • Confirm quantities and branch to prevent wrong deliveries
    • Track vendor commitments to avoid last-minute surprises

    Why — need statement

    Reduce the number of communication errors when coordinating orders with vendors.

  • JTBD 3

    Main job: Monitor ingredient prices regularly

    Related jobs

    • Compare vendor rates to choose the best option
    • Adjust order quantities based on price fluctuations

    Why — need statement

    Increase the visibility of price fluctuations for frequently purchased ingredients.

  • JTBD 4

    Main job: Anticipate delivery arrival accurately

    Related jobs

    • Plan kitchen prep based on expected stock arrival
    • Coordinate staff tasks around incoming deliveries

    Why — need statement

    Increase the predictability of delivery arrival times for daily kitchen planning.

  • Assess stock levels across locations quickly — reduce the time needed to verify stock across multiple sites.
  • Convey order details clearly to vendors — reduce communication errors when coordinating orders.
  • Monitor ingredient prices regularly — increase visibility of price fluctuations on frequently bought items.
  • Anticipate delivery arrival accurately — make daily kitchen planning predictable.

Framing

How might we

  1. HMW help operators verify stock levels across locations without delays or confusion?
  2. HMW ensure order details between restaurants and vendors remain accurate and mistake free?
  3. HMW give restaurant owners clearer insights into pricing and delivery so they make confident purchasing decisions?

Design

Getting in without friction

Restaurant owners are not signing up at a desk. They are doing it between deliveries, on a phone, often with one hand. Sign-in needs no password — a phone number and a one-time code — with Gmail and Apple ID as alternatives.

Sign-in screens and the low-fidelity wireframes for all three red routes
Sign-in, and the low-fidelity wireframes for all three red routes.

Design system

One accent, three alert states

Odero runs on a single warm yellow against greys, with green, orange and red reserved strictly for order states. Manrope carries headings and body at four sizes. Keeping the palette this tight means a colour on screen always means something — which matters when someone is scanning an order at speed.

The colour palette and icon set
The splash screenThe component library in Figma

The component library.

Red routes

Three journeys, designed end to end

Three journeys carry nearly all the value in the product, so those are the ones I designed completely rather than spreading effort across every screen.

Place an order confidently

Order a product by choosing the best vendor, with confidence.

The route runs from the home page through product search to a page that puts the product and the vendor side by side — average price, reliability, delivery window — so the comparison happens in one place rather than across four phone calls. Review, place, confirm.

Red route one — product-led vendor ordering.

Validate before ordering

Avoid ordering when stock or delivery confidence is low.

The most useful thing an ordering app can do is sometimes tell you not to order. Inventory signals flag items whose stock data has not been verified recently, and the user is warned about potential delivery delays before committing — letting them delay the order rather than discover the problem at service.

Red route two — validating stock and delivery confidence first.

Learn from past decisions

Make better future decisions using past data.

Order history leads into reliability scores built from what actually happened: how often a vendor delivered on time, how far prices drifted, how consistent they have been over six months. It turns a year of invoices into something an owner can act on.

Red route three — order history, vendor reliability and reordering.

Usability testing

Two rounds, ten participants

I ran two rounds of usability testing with ten participants from the restaurant industry — five in the first round, and a different five in the second.

Odero screens used in testing

Participants

  • Conducted two rounds of usability testing
  • 10 total participants from the restaurant industry
  • 5 participants in round 1
  • A different set of 5 participants in round 2

What worked well

  • Users appreciated the clean UI, colour palette and intuitive flow
  • Reported high confidence while completing tasks

Key frustration

  • The vendor comparison chart felt visually overwhelming

User preference

  • Preferred simple vendor cards over dense data charts

Behaviour insight

  • Users relied on quick scanning rather than detailed analysis when making decisions

What worked

  • Users appreciated the clean UI, the palette and the intuitive flow
  • They reported high confidence while completing tasks

What did not

  • The vendor comparison chart felt visually overwhelming
  • Users preferred simple vendor cards over dense data charts

The behavioural insight mattered more than either. Users were scanning quickly rather than analysing. They were not reading the comparison chart at all — so the detail I had added to help them decide was the thing slowing them down.

The result

The finished screens

All three red routes, start to finish.

Outcome

What it added up to

  • Three red routes designed end to end for iOS
  • Two personas and four jobs-to-be-done drawn from four interviews
  • A component library and a tightly scoped design system
  • An interactive prototype tested across two rounds with ten industry participants
  • Vendor comparison reworked from charts into scannable cards

Reflection

What I took away

The thing I keep coming back to is that people did not want more information. They wanted less of it, arranged better. I had built a vendor comparison chart because the research said owners compare prices manually and it takes hours — which was true. But the fix was not to automate the analysis. It was to make the answer scannable.

Interviewing owners across four very different operations also kept me honest. A cafe owner in Lucknow and a franchisee in Halifax have almost nothing in common operationally, but both described the same underlying problem: no single place where rates, quantities and suppliers live together.

Thank you for reading.

Happy to walk through the prototype and the research — get in touch any time.