Skip to content
← Work

CASE STUDYConcept · Real client

Carmelo’s: from phone-only to ordering online.

Carmelo’s Mexican Grill in Sugar Land, Texas has loyal regulars and a website that can’t take an order. I designed and built a first-party ordering site, a menu the restaurant runs itself, and a staff app for the kitchen — as a working concept to pitch to the owners.

ROLE
Designer, product manager and developer (solo)
CLIENT
Carmelo’s Mexican Grill, Sugar Land TX — concept for a pitch
STACK
Next.js 15 · Payload 3 CMS · Postgres · Stripe · Tailwind v4 · Vercel
Google rating from 1,976 reviews
4.8
Ways to order on the current site
0
Dishes across 15 categories, run from the CMS
141
Heuristic reviews, each driving a redesign
2
Carmelo’s homepage with a red Order pickup buttonCarmelo’s menu on a phonePHONE → MENU → BAG → PICKUP

Why we’re doing this

Carmelo’s is a family restaurant with a following: 4.8 stars from 1,976 Google reviews, with reviewers singling out the fajitas, the burritos and the fact that it’s family owned. People already want the food. What they can’t do is order it the way they order everything else.

Today the restaurant’s own website is a brochure. To get food to go, you call the store, walk in, or use a third-party delivery app that takes a cut of every order and owns the customer relationship. The goal is simple: give Carmelo’s its own front door for orders, one the family controls.

The problem

Customers find the website, then hit a dead end. There’s no way to order, and the menu isn’t a reliable source of truth.

Current Carmelo’s homepage: a photo carousel and links to Dinner, Lunch, Breakfast, Kids and Family Packs menus, with no order button
BEFORE · HOMEPAGE — NO WAY TO ORDER
Current dinner menu page listing burritos with prices shown as a bare dollar sign
BEFORE · DINNER MENU — PRICES SHOW AS “$.”
  1. 01

    No online ordering

    Every to-go order is a phone call or a walk-in. Customers who won’t call go to a delivery app or go elsewhere.

  2. 02

    A menu you can’t trust

    Prices show as “$.” on the live menu. Dishes listed online sometimes don’t exist, and add-ons get swapped for something else.

  3. 03

    Orders that depend on hearing right

    Modifiers — no onions, extra queso, mojado — are taken by ear during the rush, when mistakes are most likely.

  4. 04

    Margin and customers lost to apps

    Third-party apps take a commission on each order and keep the customer’s details, not the restaurant.

The website brings people to the door, then gives them nothing to do but pick up the phone.

Who it’s for

I wrote the PRD around five people — three customers and the two people who run the store.

  • Lunch-break LuisOrders on his phone during a 30–45 minute break. Wants a two-tap reorder and an accurate pickup time.
  • Family-dinner FatimaFeeds 4–6 with family packs and kids’ plates. Cares about modifiers (no onions, mild salsa) and the total.
  • Weekend-breakfast BrianOrders breakfast tacos for a group and wants them ready Saturday morning.
  • Kitchen staffNeed orders with clear modifiers and pickup times, and a quick way to mark a dish sold out (“86 it”).
  • Owner / managerEdits menu, prices and hours, pauses online ordering on a slammed night, and handles refunds.

How I approached it

  1. 01

    Understand

    Audited the current site and menu, wrote the PRD and an admin/CMS spec: personas, goals, scope, non-goals.

  2. 02

    Structure

    Modelled the menu (categories, items, modifier groups, service windows) and the order lifecycle before any screen.

  3. 03

    Design

    Figma frames for the storefront, then heuristic reviews of the built pages, fixed one issue at a time.

  4. 04

    Systematize

    One token set and component library for the storefront; shadcn on the same tokens for the staff app.

  5. 05

    Scale

    A CMS the family runs without me: menu, prices, hours, 86 board and refunds — and one location ready to become several.

Deciding when the docs disagreed

The PRD was written before the visual design, so the two disagreed in places. I logged every conflict and settled it once, in the build plan, rather than letting it resurface screen by screen.

TOPICPRD SAIDDESIGN SAIDDECISION
Visual directionChile red, rounded, Fraunces/InterInk and cream, square corners, Barlow Condensed + DM SansDesign system wins; the PRD’s look was a pre-design guess
Data layerPrisma + PostgresPayload 3 on the same PostgresPayload owns menu, content and orders — one model, one admin
NavigationMenu · Catering · LocationMenu · Family packs · Location & hours · GalleryFigma — it matches how the restaurant already talks
Menu layoutLeft category railSticky category bar over scrolling sectionsSticky bar — works the same on a phone
Special instructions140 characters200 characters140, confirmed — enough for a note, short enough to read on a ticket

A menu the restaurant runs itself

The menu problem isn’t a design problem; it’s an ownership problem. Prices go stale and add-ons drift because nobody at the restaurant can edit the site. So the menu lives in Payload CMS, on the same Postgres database as the orders, and the storefront reads from it directly.

What the CMS models

  • Categories with service windows — breakfast 7–11 daily, lunch specials 11–3 on weekdays
  • Menu items with photos, dietary tags, price and a “from” flag when options change it
  • Modifier groups: required or optional, min/max, priced add-ons (“Make it mojado”)
  • Locations: hours, prep time and an online-ordering pause switch
  • Orders, payments, refunds and an audit log of every change

Why it fixes the drift

  • One source of truth: the price on the card is the price at checkout, re-checked server-side
  • Marking a dish sold out hides it everywhere in seconds — no stale listings
  • Add-ons are data, not prose, so they can’t be quietly swapped
  • Hours drive the storefront: the menu says when it’s closed and what’s next
  • Built for one store, modelled for more without a migration
Payload editor for Huevos revueltos with name, card label, description, category and price, plus tabs for photo, modifiers and availability
PAYLOAD · EDITING A DISH
Staff menu table listing dishes with category, price and availability for quick edits
STAFF APP · QUICK PRICE AND AVAILABILITY EDITS

Because the current site is missing most prices, 91 of the 141 prices in the concept are flagged in the CMS as placeholders to confirm with the owner, and the staff menu counts them. The flag is part of the pitch: the first job after a yes is a price pass with the family, in the same editor they’ll use from then on.

Payload CMS (menu · hours · 86 board)
        │
        ▼
Storefront ──▶ Bag ──▶ Checkout ──▶ Stripe (authorise only)
                                        │
                                        ▼
                          Order ──▶ Staff app: Live orders
                                        │  accept → capture payment
                                        ▼
                          Status page + SMS/email ──▶ Pickup

Ordering, end to end

The whole flow on a phone, from the homepage to a ready time. These are real screens from the working build, played in order. Pause it, or jump to any step.

Homepage on a phone: hero photo, open-now status and a red Order pickup button

Prototype · pickup order on a phone

Decisions that shaped the flow

  • Guest checkoutNo account wall. After the order, guests can add a password to save their details for a one-tap reorder.
  • Authorise, then captureStripe holds the amount when the order is placed and charges only when the kitchen accepts — so a declined order is never a refund.
  • Honest closed stateWhen the store is closed the menu says so at the top and on every card (“Opens 7 am”), instead of letting someone customise a burrito first.
  • Price on the buttonThe add button carries the running price, so options never surprise anyone at checkout.
  • Allergy routeAllergy questions go to a phone call before ordering — the honest answer for a kitchen without a certified allergen process.
Famous burrito detail on desktop with filling choices and prices
ITEM · REQUIRED AND OPTIONAL CHOICES, PRICED
Desktop checkout: details, pickup type and time, payment, tip and the order summary
CHECKOUT · ONE PAGE, FIVE NUMBERED STEPS

Heuristic review: the landing page

Once the pages worked, I reviewed them against Nielsen’s ten usability heuristics, with a second pass from an automated design detector. The landing page scored 25 of 36 (one heuristic didn’t apply): acceptable, but it sold the restaurant better than it sold an order.

PRIORITYFINDINGFIX
P1One order button, only at the top; dish cards said “Explore…” and the page ended on the galleryPriced dish cards that open the dish, a closing order band, a sticky “Order pickup” bar on phones
P1No signal colour: the order button and “View bag” were both ink, so nothing said “start here”A warm chile-red action colour used only for ordering, and a live open-now dot
P2Featured cards had no price and two separate tap targetsPrice on every card, one target per card
P2Every section used the same template, with filler “01–04” labelsDropped the numbering, one full-bleed photo moment, varied headline scale
P2No pickup reassuranceA three-item strip under the hero: ready time, where to pick up, how to pay
Redesigned homepage: hero photo, open-now status, red Order pickup button and pickup reassurance
AFTER · HOMEPAGE — ONE CLEAR ACTION

The menu is where people actually work, so I reviewed it as a tool, not a brochure. It scored 27 of 40. The worst problems were about honesty and distance: the page said “ASAP” while the store was closed, and on a phone the first dish sat about 900px down.

PRIORITYFINDINGFIX
P1Closed state contradicted (an ASAP chip) and announced only after customisingClosed note at the top and on each card; the sheet states the reason first
P1Too much above the menu on phonesA compact header with search inside the sticky bar; first dish above the fold
P215 categories in a strip with an icon-only “All” and no scroll cueLabelled “All 15 categories” button, edge fade, active tab kept in view
P2Dietary info lossy: one tag per card, no allergen noteAll dietary tags on cards and in the sheet, allergy line at the top
P3A generic sheet slogan; corn vs flour price buried in textPanel copy written from the menu itself
Menu page on desktop: sticky category bar, filters and the Popular row
AFTER · MENU — SEARCH, FILTERS, POPULAR
Burritos category shown as a carousel of photo-led cards with arrow buttons
AFTER · EVERY CATEGORY A CAROUSEL

Three directions for the menu card

The card is the most repeated thing on the site — 141 of them — so I explored it properly. I built three directions side by side, in both vertical and horizontal layouts, using real dishes and real photos.

  1. A

    Photo-led

    Big photo, the price painted on it like a menu-board tag, one red add button. The food does the selling.

  2. B

    Menu board

    Name, dotted leader, price — reads like the board at the counter. Calm and distinctive, but the photo plays second.

  3. C

    Compact

    Small square photo, one-line copy, the price is the add button. Fits the most dishes per screen.

Card study comparing the photo-led and menu-board card directions, vertical and horizontal
STUDY · A PHOTO-LED VS B MENU BOARD, REAL DISHES

A won. Carmelo’s photos are its strongest asset, and on a phone the photo is what stops the thumb. I then moved categories from a two-column list to carousels of A cards, floated each dish’s own label (“Our famous”, “Named for a regular”) onto the photo, and gave dishes without a photo a consistent placeholder tile so rows still line up.

Colour that means “order”

The first build was ink on cream: tasteful, and silent. The review showed nothing signalled where to act. I warmed the background to masa — the colour of fresh tortillas — and gave every order action a single chile red, so red always means “this moves your order forward.” The staff app and the Stripe payment form use the same values.

ROLETOKENVALUEUSED FOR
Pagemasa#f6eedfStorefront background
Surfacesurface#fffcf6Cards, sheets, inputs
Actionchile#b5301bEvery order button and selected control
Action hoverchile-deep#9c2814Hover and pressed states
Text, secondaryearth#6b5d4fDescriptions and captions

A homepage that knows what time it is

Carmelo’s menu changes through the day: breakfast until 11, lunch specials on weekdays until 3, then fajitas and enchiladas into the evening. The homepage now shows the meal that’s being served right now, straight from the store hours in the CMS — and when the store is closed, it previews the next meal and when it opens.

Time-of-day section previewed at lunch, afternoon and evening, each with its own dishes and prices
TIME OF DAY · LUNCH → AFTERNOON → TONIGHT

The kitchen side

An order is only as good as the ticket the kitchen sees. The staff app, built on shadcn with the same tokens, gives the team a live orders board, an order queue with accept, ready and refund actions, an 86 board to mark dishes sold out, and a menu table for quick price and availability changes. Statuses are colour-coded so a busy cook can read the board at a glance.

Live orders board with New, Preparing, Ready and Picked up columns; each new ticket shows items, modifiers and accept buttons for +10, +15, +20 or +30 minutes
LIVE ORDERS · ACCEPT WITH A READY TIME IN ONE TAP
  • Accept sets the promiseAccepting a ticket means picking +10, +15, +20 or +30 minutes. That becomes the customer’s ready time — and the moment the card is charged.
  • Nothing waits foreverAn order nobody accepts within 10 minutes cancels itself and the card hold is released, so a customer is never left wondering.
  • One trail per orderEvery order keeps a timeline (placed, accepted, ready, picked up, refunded) and its point-of-sale status.
Order detail with items and modifiers, customer, payment status, POS confirmation and a timeline ending in an automatic cancellation
ORDER DETAIL · PAYMENT, POS AND TIMELINE
86 board: every dish as a tile marked Available, grouped by category, with a search field
86 BOARD · TAP A DISH TO MARK IT SOLD OUT
Staff dashboard showing today’s orders, sales, prep time, open tickets and the latest orders
DASHBOARD · TODAY AT SUGAR LAND

What’s next

This is a working concept, not a launch. The next step is putting it in front of the owners, with the current site beside it.

For the pitch

  • Walk the owners through ordering on their own phones
  • Show the CMS: change a price, 86 a dish, pause ordering
  • Agree what success looks like before any launch

Before launch

  • Live Stripe keys, email and text receipts
  • Connect the real POS (the build uses a demo adapter)
  • Pull Google reviews into the homepage
  • Photograph the breakfast menu — most of it has no photos yet
NEXT CASE STUDY · SYSTEMSagUI →