Guides
7 things worth knowing about coffee shop products
A coffee shop menu built as a production specification: station load per item, the milk bottleneck, bundling rules, and where labeling questions have to go.
What to take away
- A menu is a production specification first and a customer promise second. Write the specification, then decide what to call it.
- Score every candidate item by the station it loads, not by its ingredient cost. Two items with identical ingredients can have completely different effects on the morning.
- The steam wand is a single point of contention. Anything that queues behind it is competing with your busiest ninety minutes.
- Bundles should reduce decisions at the counter, not add them. A bundle that needs explaining costs more time than it sells.
- Nothing here states a labeling or food safety requirement. Those come from your local health department, and for allergens in particular, get the answer locally and in writing.
Score items by station, not by ingredient
Take every item you are considering and mark which station it occupies and for how long. Ingredient cost matters at the end of this exercise. Station time matters at the start, because station time is what runs out during the block that carries the day.
Menu items by station load
Item family
- Batch brewed coffee
- Brewer, then a pour
- Espresso only drinks
- Grinder and group head
- Milk drinks
- Steam wand, one at a time
- Blended and iced drinks
- Blender, ice, extra assembly
- Bought in pastry
- Display case only
- Assembled food
- Prep counter, sometimes toaster
Station it loads
- Batch brewed coffee
- No, once brewed
- Espresso only drinks
- Briefly
- Milk drinks
- Yes
- Blended and iced drinks
- Yes, and loudly
- Bought in pastry
- No
- Assembled food
- Yes
Blocks other work?
- Batch brewed coffee
- Waste if batch outlives hold
- Espresso only drinks
- Grinder contention when two ordered
- Milk drinks
- The whole peak queues here
- Blended and iced drinks
- Long assembly and noisy room
- Bought in pastry
- Waste decided the day before
- Assembled food
- Steals bar attention at worst hour
Where it hurts
- Batch brewed coffee
- Espresso only drinks
- Milk drinks
- Blended and iced drinks
- Bought in pastry
- Assembled food
| Item family | Station it loads | Blocks other work? | Where it hurts |
|---|---|---|---|
| Batch brewed coffee | Brewer, then a pour | No, once brewed | Waste if the batch outlives its hold window |
| Espresso only drinks | Grinder and group head | Briefly | Grinder contention when two are ordered together |
| Milk drinks | Steam wand, one at a time | Yes | The whole peak queues here |
| Blended and iced drinks | Blender, ice, extra assembly | Yes, and loudly | Long assembly and a noisy room |
| Bought in pastry | Display case only | No | Waste decided the day before |
| Assembled food | Prep counter, sometimes a toaster | Yes | Steals bar attention at the worst hour |
A menu is balanced when the peak items sit on different stations. A menu is fragile when your three best sellers all want the wand.
The wand is the constraint
Espresso extraction is short and can overlap with other work. Steaming milk cannot. One wand, one pitcher, one person's hands and eyes, plus a rinse between uses. That is why a latte heavy order slows a bar that handles black coffee without effort.
Two practical consequences. First, when you consider a new milk drink, you are not asking whether people will buy it. You are asking what it displaces. Second, a shop that wants to grow through the peak either buys wand capacity or designs demand away from it, and designing demand away from it is usually cheaper.
That second option is where a good cold offer earns its place. A cold brew poured from a tap does not touch the wand at all. Neither does a batch brewed cup. Those are not lesser products; they are the products that let the wand serve the people who came for it.
Deciding what not to sell
The list of things you have chosen not to offer is more useful than the list you offer. Write it down, with the reason beside each entry, and revisit it quarterly rather than at the counter when a regular asks.
Reasons that hold up:
Reasons to not sell an item
- Loads the station that is already the constraint
- Needs an ingredient nothing else uses
- Needs training that does not transfer
- Needs storage you do not have
- Needs a food handling step you lack
Reasons that do not hold up: another shop sells it, or somebody asked once.
Every ingredient that appears in exactly one item is a small liability. It has to be ordered, stored, rotated and eventually thrown away, and it earns only what that one item earns. Count them. A menu with many single use ingredients is expensive in ways the price list never shows.
Packages and bundles that actually help
A package is a way of removing a decision from the counter during the busiest part of the day. That is the whole benefit. If a bundle needs an explanation, it has added a decision instead of removing one.
Rules that hold up in practice:
Bundle rules that hold up
- Sayable in four words or fewer
- Uses existing ingredients and stations
- Exactly one variable, or none
- Visible where the decision happensthe queue
- Group orders need a pre-decided rule
Group orders need a specific rule of their own. A customer ordering for six people during peak is not a large sale but a stall.
Decide in advance how to handle him: a separate pickup time, a preorder route, or a defined pause in the counter queue while the bar catches up, because deciding in the moment always costs more.
Retail bags and subscriptions
Selling beans changes what the shop is. It adds stock that ages, a roast date that customers can read, and a promise about freshness that you now have to keep.
Before selling retail beans
- How much shelf will you give it?
- How will you rotate against roast date?
- Who explains grind, and for how long?
- What happens to bags past their window?
Subscriptions are the same product with an administrative tail: cutoffs, pauses, address changes, failed payments and the labor of packing. They are worth running only if somebody owns that tail. Attach it to the bar and it will be done badly during the exact hour it must not be.
Labeling, allergens and the questions to send elsewhere
This section names authorities. It states no rule, because the rules that apply to you depend on your jurisdiction, your premises and what you sell.
Where labeling questions go
Are you a chain of 20+ locations with same name and menu?
FDA menu labeling page applies
Check with your local authority
The FDA Food Code is a model that states and localities adopt in varying forms and on varying timelines. It is not automatically the law where you are. Read it to understand the vocabulary your inspector will use, then ask your local health department what your jurisdiction has actually adopted.
For allergens, the FDA's questions and answers on food allergens covers all labeled packaged food under federal rules. A made-to-order drink at a shared bar follows local rules instead.
Ask your health department directly what you must disclose and how, and get the answer in writing. This is one of the questions readers get sued over, so treat a peer's confident answer as a rumor.
Menu labeling has its own scope. The FDA page on menu and vending machine labeling describes requirements for restaurants and similar retail food establishments in chains of 20 or more locations with the same name and substantially the same menu.
For a single shop, check with your local authority. Do not infer an answer from that page.
Claims are a separate matter again. Words like organic, single origin or locally roasted are advertising claims. The Federal Trade Commission's advertising guidance for small businesses sets out the principle that a claim must be truthful and substantiated. Keep the paperwork that backs each word on the board.
Reviewing the menu on a schedule
Once a quarter, pull sales by item and sit them beside two other columns: the station each item loads and the number of ingredients unique to it. Then ask three questions in order.
- Which items sell well and load a station that is not the constraint? Protect and promote these.
- Which items sell poorly and carry unique ingredients? These are the cut list, unless one of them is the reason a group comes in.
- Which items sell well but sit on the wand during the peak? These are the design problem, and the answer is usually a faster version of the same idea rather than removal.
Do this on a schedule rather than when something feels wrong. Menus drift item by item, and drift is invisible until somebody counts. The scale and format decisions behind all of it are set out in how the shape of the shop sets its ceiling.
Common questions
How many items should a coffee menu have?
Few enough that a new barista can produce every one of them to standard within a few weeks, and few enough that the board can be read from the back of the queue. Beyond that the number matters less than the station spread.
Should seasonal drinks be on the menu at all?
They work when they reuse an existing station and an existing ingredient set, and they hurt when they add a syrup nobody else uses and a step nobody has practiced. Test one at a time, and count what it displaced rather than what it sold.
Is food worth adding?
It depends entirely on which station it lands on and at what hour. Bought in pastry loads only the display case, which is why so many shops start there. Assembled food loads a counter and a person, and during the peak that person was making drinks.
Who decides what I have to disclose about ingredients?
Your local health department, for your premises and your menu. For packaged goods you sell, federal labeling rules also come into play. Ask locally first, and take advice from a qualified professional before printing anything you would not want to defend.
