Cafe Sales Data: What Your First 30 Days Reveals

You think you know, but you do not

Every cafe owner has a mental model of their business. You know Saturday is the busiest day. You know the morning rush peaks around 9 AM. You know oat milk is popular. You know Mondays are slow.

After 30 days of actual sales and inventory data, you may find your mental model is partly right and partly wrong in ways that cost you money. The Saturday insight might hold, but the peak hour might be 10:30 AM, not 9 AM. Oat milk might be a bigger share of your milk drinks than you would guess, and you might be ordering it short every week. Mondays might not be slow at all: fewer transactions, but a higher average ticket because the morning crowd orders more expensive drinks.

The gap between perception and reality is not a failure of intelligence. It is a limitation of human pattern recognition. We remember the memorable moments (the Saturday rush, the time we ran out of cups) and forget the quiet signals (the consistent Tuesday afternoon uptick, the slow decline in drip coffee sales over six weeks).

Data does not have this bias. It records everything equally. And after 30 days, it has enough observations to separate real patterns from noise. If you have connected your Square sales to your ingredient usage, that separation is what a POS-to-ingredient layer is for.

The patterns that surprise owners

Your real peak hour

Ask any cafe owner when their rush happens, and they will give you a confident answer. But "rush" is a feeling, not a measurement. A period that feels busy because you were short-staffed might not actually be your highest-revenue hour.

After 30 days of hourly sales data, the peak hour becomes precise. And it often shifts by day of week. Weekday peaks might cluster between 8 and 10 AM (commuter-driven), while weekend peaks might push to 10:30 AM or later (brunch crowd). Some cafes discover a second peak between 2 and 3 PM that they never optimized for because it did not "feel" as busy as the morning.

Knowing your true peak hours by day of week changes prep timing and batch brewing schedules. If your real Saturday peak is 10:30 to 12:30, your opening barista should have all batch drinks prepped by 10:15, not by 8 AM when they currently feel the time pressure.

Which day has the highest waste

Waste does not distribute evenly across the week. One day consistently generates more waste than the others, and it is usually not the day you expect.

The pattern often looks like this: Sunday has the highest waste rate because it is the hardest day to predict. Weekend volume varies more than weekday volume. If you over-prepped based on Saturday's busy day, Sunday's slower afternoon means unused prep goes to waste. Or if Sunday closers are less experienced, over-portioning creeps up.

Another common pattern: Monday waste is high because weekend deliveries sometimes arrive with quality issues (dairy that sat in a warm truck, produce that is already turning). The waste is not operational; it is supply chain related.

You cannot fix waste patterns you do not see. Thirty days of count data, combined with sales data, makes the waste visible for the first time.

The modifier nobody is paying for

Modifiers are where margins hide. After 30 days of POS data with modifier tracking, you can see exactly how often each modifier is selected and whether you are charging for it.

A common discovery: oat milk turns out to be the default on most of your milk-based drinks, but the menu was designed around whole milk as the base. Say you charge an extra $0.75 for oat milk. If you ring it up every time, that modifier adds up. If you do not charge for it, or if staff frequently forget to ring it up, you are absorbing the extra ingredient cost per drink with no recovery. Run your own numbers on that gap and it usually surprises people.

Another thing to look for: how often "extra shot" gets ordered, and whether it is charged. Extra shot is almost always charged correctly because the POS prompts for it. But "light ice," which effectively gives the customer more milk at no charge, may happen more than you think on iced drinks and is never tracked as a modifier. That is a hidden cost you can only see once the data is in front of you.

The item that does not match its sales

Here is a pattern that only emerges when you connect sales data to count data: an item whose count-based consumption rate significantly exceeds its recipe-predicted consumption.

If your recipes say you should use 600 oz of oat milk per day based on sales, but your counts show you are actually depleting 800 oz per day, the 200 oz gap is waste, over-portioning, or unrecorded use. Maybe baristas are steaming extra and dumping it. Maybe the cold brew oat milk blend uses more than the recipe specifies. Maybe some drinks are being given away without being rung up.

A 33% gap between predicted and actual consumption on your highest-volume ingredient is worth investigating immediately. Say oat milk runs you around fifteen cents an ounce. At that price, a 200 oz daily gap is about $30 a day, or roughly $900 a month. Plug in your own oat milk cost and your own gap and the math is yours to check.

The reverse pattern also appears: items where count-based consumption is lower than recipe-predicted. This usually means the recipe is wrong (a recipe says 2 oz of vanilla syrup, but the actual pump dispenses 1.5 oz) or that counts are inaccurate (the item gets restocked between counts, making depletion appear lower). Either way, it is a reason to go back and check what each drink actually costs.

How external factors affect specific items

After 30 days, you start seeing correlations between external factors and specific product sales. Cold days drive more hot lattes and drip coffee. Warm days drive iced drinks and cold brew. Rainy days reduce foot traffic but increase average ticket (the people who do come in tend to linger and order more).

These correlations are not strong enough to act on after 30 days, but they become visible. After 90 days, they become reliable enough to adjust ordering. And after a full year, you have seasonal patterns that transform how you plan.

How to do a 30-day data review

Set aside 45 minutes. Pull up your sales reports, inventory consumption data, and count history. Work through these questions in order.

Sales questions:

• What are my top 10 items by volume? By revenue? Are they the same list?
• Which day of the week has the highest revenue? The highest transaction count? Are they the same day?
• What is my average ticket by day of week? Is there a day where customers spend more per visit?
• What is my hourly revenue distribution on weekdays vs. weekends?

Consumption questions:

• Which five ingredients have the highest daily consumption? Does this match my expectations?
• For my top ingredients, how does recipe-predicted consumption compare to count-based consumption? Where are the biggest gaps?
• Which ingredients show the strongest day-of-week variation? (Oat milk on Saturday vs. Tuesday, for example.)

Waste and efficiency questions:

• Which items have the highest waste rate (count depletion minus recipe prediction, as a percentage)?
• Is waste concentrated on specific days or spread evenly?
• Are my counts happening on schedule? How many were missed or late?

Supplier and cost questions:

• How much am I spending with each supplier per week? Is it trending up or down?
• Which supplier has the highest cost per transaction? The lowest?
• Are there items where the cost has changed significantly over the 30-day period?

If those questions turn into a habit, they are the same ones that power a handful of weekly reports worth reading every Monday.

Patterns compound over time

The first 30-day review reveals the obvious things. The gaps between perception and reality. The waste patterns. The modifier economics.

The second 30-day review (comparing month two to month one) reveals trends. Is oat milk consumption growing? Is average ticket increasing or decreasing? Are your waste reduction efforts showing results?

By the third month, you are comparing three data points per metric, which starts to show direction. You can start to say whether Saturday revenue is climbing month over month, or whether your oat milk waste is dropping since you adjusted portioning.

By six months, seasonal patterns emerge. The summer iced drink shift. The holiday slowdown or surge, depending on your location. The back-to-school bump or drop.

The cafe that has been tracking data for six months operates differently from the cafe running on instinct. Not because instinct is wrong, but because instinct plus data beats instinct alone. The data catches the things you would never notice, the slow trends, the small leaks, the hidden patterns. And catching those early is the difference between a cafe that gradually improves its margins and one that wonders why profitability never quite gets where it should be.

Start with 30 days. The patterns are waiting. When you are ready to act on them, here are five decisions that get better with data.