Coffee shops & cafes Operations Questions
The questions that recur in coffee shops share one shape: the seat is the scarce asset and nobody prices it. Pastry waste runs 30 percent beside weekly stockouts of the same items. A chain opening nearby takes the afternoon crowd first, and the laptop policy has never been measured against revenue per seat-hour. The answers below cost the seat before the cup.
-
Pastry waste runs 30% while the same items stock out weekly. What is par-setting optimizing?
Nothing. Pars are static while demand is day-of-week and weather volatile. Waste and stockouts coexisting is the signature of no forecast model: set pars by day-of-week demand history (newsvendor logic for perishables), and bake to a two-batch schedule (open + mid-morning).
§5.2 Newsvendor, §2.1 demand pattern, A4
-
When a chain opens nearby, why do we lose the afternoon crowd first, not the morning one?
Morning is habit-locked (commute ritual, low involvement). Afternoon is discretionary (meetings, treats) and comparison-shopped. Your defensible core is the morning ritual. Deepen it (speed, recognition, subscriptions). The afternoon needs a distinct reason to exist (workspace terms, event programming).
§13 habit/behavioral, §1.1 OrderWinner, §2.3
-
When we raise drink prices, transaction count holds but average ticket falls. What are customers trading down from?
The add-ons: pastry attachment and size upgrades die first under price pressure. The drink is the habit, the extras are the elastic margin. Counter with bundle pricing (drink + pastry at a combined anchor) so the trade-down path leads to a designed option, not just less.
§2.3 price architecture, §13 anchoring, §1.3
-
Morning regulars visit daily but generate less margin than the weekend crowd we cannot retain. Which customer does the menu serve?
Neither deliberately. The menu evolved. Decide: if regulars are the annuity, optimize for speed and loyalty pricing, if weekend margin matters, build the weekend occasion (brunch items, family space). Serving both with one menu and one flow means each subsidizes the other's experience.
§1.1 focus, §8.2 yield, §2.1 segmentation
-
Does the laptop policy change revenue per seat-hour. Have we ever measured seat-hour revenue?
Measure it: seat-hour revenue is your true productivity metric (tables are the capacity resource). Laptop campers typically halve it at peak. Options: time-limited tables at peak, laptop-free zones, or minimums. You cannot choose without the per-seat-hour number.
§8.2 yield management, §4.2 capacity, §1.3
-
Why do mobile orders raise volume but degrade the in-store metrics that built the brand?
Because mobile demand jumps the same production line: baristas serve the queue screen instead of the counter guest. One bottleneck, two arrival streams, and the in-person customer watches drinks go to invisible people. Separate the flows (dedicated mobile station/pickup shelf) or throttle mobile slots at peak.
A3 bottleneck, §8.1 two-class queues, §8.2 blueprint
-
Why do fastest-ticket baristas have lowest greeting scores, and which predicts repeat visits?
Speed and warmth trade off at the individual level, but repeat visits track recognition (name, usual order) more than raw speed. Up to the wait threshold. Ideal: fast enough to respect the commute, warm enough to be a ritual. Staff the morning rush for throughput and train the 10-second recognition habit.
§6.3 SERVQUAL responsiveness vs empathy, §13, §2.3
-
Seasonal drinks outsell the core for two weeks, then underperform. Are we buying inventory for the spike or the plateau?
For the spike, if purchasing is driven by launch excitement, and the plateau then becomes waste. Buy for the plateau with spike coverage via flexible suppliers or smaller initial lots. Treat the launch curve as a newsvendor problem with a known decay.
§5.2 Newsvendor, §2.1 demand lifecycle, §13 recency bias
-
Read the kitchen labor budget as a confession: coffee business with food, or food business with coffee?
The budget confesses the truth your branding may deny: if food labor and COGS approach 40%+, you are a cafe-restaurant with food-level complexity and coffee-level ticket averages. Either grow average ticket to match the kitchen's ambition or simplify the kitchen to match the ticket.
§1.1 emergent strategy, §1.3, §10 layout/process choice
-
Why is loyalty redemption so low it functions as an unpaid discount, and what happens when friction drops?
Low redemption means the program is breakage-based: it works financially only because rewards expire unused. Dropping friction raises redemption and visit frequency. Test whether incremental visits cover the redemption cost. If yes, friction was costing you the actual point (frequency), if no, you had a quiet margin.
§13 behavioral, §2.3 loyalty design, §1.3
How these answers work
Each answer names the operational mechanism the question is circling, then states the directive that follows from the ontology in Part One of the book. Bracketed citations point to the ontology sections and axioms that produced the answer. Figures inside the questions describe each stipulated scenario. They are not industry benchmarks.
Related industries
- Bars & taverns operations questions
- Restaurants (independent) operations questions
- Catering companies operations questions
- Juice / smoothie / boba shops operations questions
- Food trucks operations questions
Keep reading
Scope of This Material
General information only. This page and the book it excerpts provide general operational information for business owners. They do not provide legal, tax, accounting, medical, financial, employment, or other professional advice, and they do not account for the facts of any particular business. Reading them creates no consulting or advisory relationship of any kind.
Decisions involving employee pay or employment terms, regulated professional practice, patient or client care, safety, licensing, or compliance obligations should be reviewed with a qualified professional licensed in the relevant jurisdiction. The material is provided as is, without warranty of any kind. World Consulting Group accepts no liability for any action taken or not taken in reliance on it. See the full disclaimer.
Reading the question that matches your situation is not the same as correcting the structure underneath it. World Consulting Group works with operators on the kinds of structural questions this book raises.
Talk to World Consulting Group