Turning numbers into answers.

Overview

The daily business window for operators of 700+ active stores.

The Analytics Dashboard (Report Center) is a business data hub for restaurant owners — gathering scattered operating data into the one place an owner can actually read.

Constraints: the specification and accounting definitions were owned by the PM and benchmarked to industry standards — not to be deviated from. One web app had to serve both desktop and mobile reading postures.

Key trade‑off: we invested more engineering resources and polish time in UI readability than a typical reporting build — trading higher development cost for reports owners can read simply and clearly.

Company
Peblla
Platform
Responsive Web App
Year
2024
Team
Product Manager
Engineering
Data Team
Role
UI Design
Design System
Responsive Design

Problem

The answer to “how is my business?” was scattered across the POS, delivery platforms, and bank statements — and an owner’s window for data is five minutes before opening.

Approach

Numbers that carry their own answers — comparisons on by default, mismatches explained proactively, and one reading posture per device.

Results

The daily business window for operators of 700+ active stores — 724 weekly active as of April 2026.

Process

The scattered answer

One question, four places to look.

Restaurant owners answer the same question every day: how is my business actually doing? But the answer is scattered everywhere — sales data lives in the POS, delivery data on third-party platforms, deposits on bank statements, tips and refunds in yet other reports. Nobody has time to piece these fragments into a conclusion they can act on.

The core question: how do you let an owner with no data background understand today’s business in seconds, trace every dollar when needed — and trust every number on the screen?

Who it’s for

They don’t want data. They want answers.

The primary users are restaurant owners and franchisees — not data analysts, with zero report training. The time they have for data might be five minutes before opening, or a gap after the rush. What they want isn’t data — it’s answers: Is today better than yesterday? Did all the money come in? Which channel is growing?

The spec

A mature category — where presentation decides.

Reporting follows well-established standards in restaurant SaaS, so the specification came from two sources: industry conventions — a dedicated PM owned the reporting logic, benchmarked against Toast’s Settlement Time business-day definition, 3rd Party Excl./Incl. accounting toggles, and per-transaction fee granularity — plus the operating questions owners actually use these numbers to answer. The spec guarantees every page is correct; my work was making sure an owner “gets it in seconds” instead of drowning in it.

Solution

Four modules, to the rhythm of an owner’s questions.

01 Sales Overview — how is business today

Net Sales, Payments, and Refunds anchor the page as three top cards, defaulting to a comparison against yesterday — green-up / red-down percentages sit right beside the big numbers, so there’s no mental math and no remembering yesterday’s figures. Breakdowns fold into tabs inside each card: visual weight follows how often owners ask the question, not how complex the data is — without a reference point, a number is just a number.

The Sales vs Payment reconciliation area and Unclosed Orders put the gap between billed and collected right on the surface; third-party fees and refunds can cause mismatches, so the interface says so directly and offers an Excl./Incl. toggle instead of pretending the data is perfect. The Miscellaneous and Performance blocks round out taxes, tips, auto gratuity, and voided amounts — every restaurant-specific line item accounted for.

Three anchor cards with period-over-period indicators — the tone of the day, set in one look

02 Sales Summary — how is the rhythm

Sales by Day, Day of Week, and Time of Day charts read the rhythm; summary cards below cover the books — charts answer the rhythm, cards answer the totals. Date presets cover the frequent questions while a dual-calendar custom range serves deep reconciliation; and a “day” means the business day, not the calendar day — stores closing after midnight settle at 5 AM, with Settlement Time configurable.

Presets cover the frequent questions; the dual calendar serves deep reconciliation

03 Order / Transaction Details — where every dollar went

Every order’s full fee chain laid out transparently — amount, tips, auto gratuity, delivery fee, Dasher tips, transaction and additional fees, down to the final Net Total, with prepaid amounts and refunds accounted for, plus categorization and export — owners reconcile without digging through bank statements. Each transaction carries its business dimensions too, from dining type and channel to split payment and promotions; when data isn’t real-time, the page states the cutoff clearly rather than letting owners discover it.

Every dollar, from charged to deposited, readable in one row

04 Weekly Report — the week in review

Ten modules review the whole operation: Net Sales, Upsells, Third Party, Direct Delivery, Top Sales Items, channel distribution, sales & upsell trends, member analysis, Google / Yelp review sentiment, and off-premise geo distribution. The entire report is designed for mobile reading as a vertical card stream — where Toast sends an email digest, Peblla made it a complete report readable in one scroll on the phone.

The whole week, one thumb-scroll — sales performance on the left, customers & place on the right

Design system

One language for the whole reporting family.

Report Center isn’t one page — it’s a family of reports living on two breakpoints, and my most important output was the design system built to carry it: a metric card component (large value + period-over-period indicator, semantic colors unified globally — new metrics plug straight in), chart and table standards, notice banners (honesty information componentized), and responsive re-composition rules (each component’s desktop-to-mobile reflow, componentized). Adding a new report page means assembling components, not designing from scratch — the spec guarantees every page is correct, the design system guarantees every page speaks the same language: learn to read one report, and you’ve learned to read them all.

Impact

The value of a report is quiet.

Report Center is the business window Peblla merchants open every day, serving the operators of over 700 active stores — on a platform processing roughly $27.98M in monthly GMV across 920K orders.

A reporting product’s success shows in two quiet things: whether owners build the habit of checking daily, and whether calls to their Account Manager asking “the numbers don’t match” decline. A report that doesn’t read as a judgment turns every confusion into a phone call; one with clear hierarchy and consistent semantics absorbs those calls into the interface — report design quality shows up directly in the cost of human support.

724

Weekly active stores

Operators opening the dashboard as their daily window (Apr 2026)

$27.98M

Monthly platform GMV

As of Feb 2026 — every dollar traceable in the reports

920K

Monthly platform orders

Feb 2026 — every one of them traceable in the reports

Reflection

In a mature category, the designer’s value is the precision of presentation.

How do you measure the success of a report? Every store looks at its reports — “being used” is guaranteed, but it isn’t the same as “well designed.”

If I did this again, I’d instrument two metrics from day one: the frequency of Account Manager inquiries, and whether owners check in proactively every day. Where the specification follows industry consensus, a UI designer’s value isn’t inventing new logic — it’s the precision of presentation.

Next

Ordering Tablet