How Many Employees Should I Schedule Each Shift at My Bagel Shop?

Why the gross-profit method beats gut-feel scheduling

Most bagel shop owners build a Schedule from habit: last week's grid, the manager's hunch about a busy Friday, or a whiteboard that hasn't changed since the menu did. Those instincts feel efficient but they carry a hidden tax. Overstaff a slow open and you burn margin on idle aprons. Understaff a rush and you lose ticket speed, ticket size, and regulars who won't queue past the door. The gross-profit method replaces both failure modes with arithmetic that any owner can verify in under ten minutes.

The core idea is simple. Every Shift has two numbers that matter: the gross profit it generates and the labor cost it consumes. Gross profit — not revenue, not foot traffic — is what actually pays the crew. If a shift clears $540 in gross profit and you staff six people, each person needs to generate $90 of that margin just to break even on labor. If they clear $100 each, the shift nets $60 beyond the labor bill. If they clear $75 each, you are losing $90 on that shift before rent, utilities, and ingredients.

That $90 anchor is not pulled from thin air. It reflects the reality of a bagel shop's ticket economics. A typical transaction runs $8 to $14 — a couple of bagels, a spread, a coffee. With food costs around 25 to 30 percent, each transaction contributes roughly $6 to $10 in gross profit. An employee handling 10 to 15 transactions per hour across a busy shift generates $90 to $150 in gross profit per shift. The $90 floor is deliberately conservative: it assumes ordinary effort, ordinary traffic, and ordinary service. It is the baseline you refuse to dip below, not the ceiling you celebrate.

The contrast with common alternatives is stark. Foot-traffic-based scheduling tells you when the store is busy but says nothing about whether that busyness converts to margin. Fixed-crew scheduling — "we always run five on weekdays" — ignores that a rainy Tuesday and a sunny Friday can produce wildly different gross profits at the same hour. Sales-revenue-based scheduling is closer but still flawed because a high-revenue shift with heavy food cost can generate less gross profit than a moderate-revenue shift with a strong beverage mix. Gross profit is the only number that directly answers the question: does this Shift pay for the people standing in it?

For a Bagel shop, the method also forces honest conversations about which dayparts actually earn their coverage. The pre-dawn bake from 3 a.m. to 6 a.m. might generate modest gross profit but is non-negotiable because the product must exist by opening. The mid-morning trough from 10 a.m. to 2 p.m. might look dead on a sales tape yet still clear enough through coffee refills and half-dozen grab-and-go orders to justify two bodies. The gross-profit division makes those trade-offs explicit rather than leaving them to whoever writes the Schedule that week.

How to choose between the gross-profit method and scheduling software

The gross-profit method is a calculation. Scheduling software is a delivery mechanism. They are not competitors — they are two halves of the same workflow. The mistake owners make is buying software first and hoping it teaches them the arithmetic. The right order is to master the division with a calculator or spreadsheet, then choose a tool that executes it cleanly across the week.

Here is the decision logic in practice. If you run a single storefront with fewer than fifteen employees, the free PULSE Rep Scheduling Matrix or a manual spreadsheet is genuinely sufficient. You pull gross profit by shift and weekday from your POS, divide by the $90 anchor, and write the headcounts into a grid. The whole exercise takes thirty minutes per quarter. A paid tool adds little beyond push notifications and shift-trade requests, which a group chat can handle.

If you run multiple locations or a crew past twenty-five people, the calculus shifts. Per-location pricing models like Homebase or 7shifts become attractive because you pay per storefront, not per head. A Bagel shop with thirty part-timers across two units would pay roughly $50 to $70 per month on Homebase's paid tier versus $75 to $240 per month on a per-user platform like When I Work at $2.50 to $8 per person. Over a year, that difference runs $600 to $2,000 — real money for a small operator.

The second decision axis is whether you want coverage auto-suggested from live sales data. Deputy, 7shifts, and Workforce.com all integrate with point-of-sale systems and propose headcounts against projected sales. That is a genuine time-saver, but it only works if your POS connection is reliable and your sales forecasts are accurate. A bagel shop with steady, predictable weekday patterns — commuters from 6 a.m. to 10 a.m., a lull, a modest lunch — will find that a quarterly manual division captures the pattern just as well as a live feed. A shop with volatile catering orders or weather-dependent traffic might benefit from the automatic recalculation.

The third axis is compliance. Open a second unit or operate in a city with fair-workweek ordinances and the labor-law rails baked into Deputy or Workforce.com become valuable. Break rules, overtime flags, and predictive-scheduling mandates are not theoretical — they carry fines and legal exposure. A single-store owner in a small town can skip this entirely. A multi-unit operator in Seattle, New York, or Chicago cannot afford to.

Costs, timelines, and expected impact of switching to gross-profit scheduling

The direct cost of adopting the gross-profit method is effectively zero. You need a point-of-sale system that reports gross profit by shift and weekday — most modern POS platforms including Square, Toast, Clover, and Lightspeed all do this natively. You need thirty minutes to pull the trailing three-to-six-month averages. You need a calculator or spreadsheet. That is the entire upfront investment.

If you choose to add scheduling software on top, the timeline and cost vary by platform. The free PULSE Rep Scheduling Matrix runs in a browser tab with no login and no seat license — you can produce your first full-week headcount grid in under an hour. When I Work starts around $2.50 per user per month on the Essentials tier and climbs toward $8 per user per month with attendance and labor tracking bolted on. Homebase offers a genuinely free single-location tier with no employee cap, with paid tiers at roughly $24.95, $59.95, and $99.95 per location per month. Deputy sits around $4.50 per user per month for scheduling and $6 for the premium tier. 7shifts has a free Comp tier for one location, with paid plans from roughly $34.99 to $76.99 per location per month. Connecteam is free up to ten users, then roughly a retainer for up to thirty. Workforce.com runs about $4 per user per month. HotSchedules by Fourth is quoted case by case, typically north of $40 per location per month, and is aimed at enterprise groups.

The timeline to see impact is short. The first week you run the gross-profit division, you will likely find two things: overstaffed slow shifts and understaffed rush shifts. The overstaffing is the expensive problem. A single shift carrying one extra employee at $15 per hour for five hours costs $75 in labor against a shift that might only clear $540 in gross profit — that is 14 percent of the shift's margin gone before you pay for anything else. Eliminating one redundant body on three slow shifts per week saves roughly $225 per week, or $11,700 per year. That single adjustment often pays for any scheduling software you choose many times over.

The understaffed rush is the subtler cost. A Saturday morning that pulls $1,170 in gross profit with only ten employees — instead of the thirteen the division calls for — is not saving money. It is leaving money on the counter. Longer lines, slower service, and sold-out varieties push customers to the bakery down the street. The three extra bodies cost roughly $180 in labor for the shift but protect the full $1,170 in gross profit by keeping the line moving and the display case full. That is a 15 percent return on labor spend just by standing where the receipts ring.

The structural impact appears over a quarter. Once the Schedule tracks gross profit instead of habit, labor percentage — labor cost divided by revenue — typically drops two to four points. On a bagel shop doing $20,000 per month in revenue, that is $400 to $800 per month in recovered margin. On a $40,000-per-month operation, it is $800 to $1,600. Over a year, that is $5,000 to $19,000 depending on size. That is not a rounding error; that is the difference between a shop that breaks even and a shop that pays its owner.

Implementation and handoff details for your first gross-profit schedule

The implementation is a five-step process that any owner or manager can complete in a single afternoon. The first step is pulling the data. Open your POS reports and export gross profit by shift and by weekday for the trailing three to six months. If your POS does not break out gross profit by shift, export gross profit by hour and group the hours into your defined shifts — the pre-dawn bake, the morning rush, the mid-morning trough, the lunch window, the afternoon wind-down, and the close. Average each shift across the same weekday. A Tuesday open averaged over twelve weeks is far more stable than a single Tuesday's number.

The second step is the division. Take each shift's average gross profit and divide by your per-employee target. With the $90 anchor, a shift clearing $540 calls for six employees. A shift clearing $720 calls for eight. A shift clearing $1,170 calls for thirteen. Round to the nearest whole number, but round up when the remainder is 0.5 or higher — an extra body on a busy shift is cheaper than a stalled line on a busy shift.

The third step is overlaying the headcounts on the hourly sales tape. The division tells you how many bodies each shift needs in total; the hourly tape tells you when those bodies need to be present. A morning rush from 6 a.m. to 10 a.m. might call for thirteen employees across the shift, but those thirteen are not all needed at 6 a.m. The first three hours need the bakers and two counter hands; the 7 a.m. to 9 a.m. window needs the full thirteen; the 9 a.m. to 10 a.m. fade can bleed down to six. The Schedule should ramp up, hold, and ramp down to trace the receipts rather than park the whole crew in a flat block.

The fourth step is the handoff. Write the Schedule into whatever tool you use — the free PULSE matrix, a spreadsheet, or a paid platform. Publish it at least one week in advance so employees can plan around it. Communicate the reasoning plainly: "This shift generates $540 in gross profit, and our target is $90 per person, so we run six." That transparency converts the Schedule from a top-down decree into a shared yardstick. Employees who understand the math are far more likely to push for the schmear upgrade or the dozen instead of the half because they know it keeps their shift staffed.

The fifth step is the quarterly refresh. Re-pull the gross-profit averages every three months. Menu prices change, commuter patterns shift, and seasonal swings hit bagel shops hard — summer volume drops, holiday rushes spike, and back-to-school mornings change traffic entirely. The $90 anchor only needs revisiting once or twice a year, but the shift averages drift faster than owners expect. A quarterly refresh keeps the Schedule tracking real receipts instead of a stale snapshot from two seasons ago.

Related questions

What if a shift's gross profit swings wildly from week to week?

Use a trailing three-to-six-month average by shift and weekday to smooth the noise. Schedule to that baseline, then add a manual bump for known spikes like holidays, paydays, or weekend brunch. Do not let one exceptional week distort the entire average or you will overstaff every ordinary week to protect against a rare surge.

Can I use a different per-employee target for different shifts?

You can, but be cautious. A single flat anchor keeps the yardstick honest and prevents managers from quietly lowering the bar on shifts they want to overstaff. If a daypart genuinely has a different labor model — a self-serve grab-and-go window versus a made-to-order lunch line — a separate target is defensible. Write down the reason so the number stays a decision, not a habit.

How does this method handle the pre-dawn bake shift?

The bake shift is the exception that proves the rule. It generates modest gross profit but is non-negotiable because the product must exist by opening. Run the division, but treat the bake as a fixed cost with a minimum crew — typically two to three people — regardless of the quotient. The gross-profit method covers the front of house; the back of house gets a floor, not a formula.

Does the same method work for a bagel shop with catering or wholesale accounts?

Yes, but separate the revenue streams. Catering and wholesale orders have different gross-profit margins and different labor requirements than counter sales. Run the division on the counter business using the standard anchor, then add dedicated labor for catering prep and delivery based on the specific order volume. Mixing the two distorts both numbers.

What is the fastest way to test this method without changing my whole Schedule?

Pick one weekday with a stable pattern — a typical Tuesday, for example. Pull the last twelve weeks of gross profit for the morning shift, average it, divide by $90, and compare the quotient to your current headcount. If the numbers differ, adjust just that one shift for two weeks and watch the labor percentage. That single experiment will prove the method before you commit to a full rollout.

FAQ

How do I set the gross-profit-per-employee Shift target?

Look at your trailing gross profit and current staffing, then agree on the honest floor an average employee should produce on an average Shift. Many food-service operators land between $60 and $150 per Shift depending on ticket size and labor model. Set it with leadership so it is a shared yardstick, not a number one manager invented. Revisit it once or twice a year.

Why staff to gross profit instead of foot traffic or a fixed crew?

Foot traffic and "we have always run five people" do not pay the labor bill — gross profit does. Tying headcount to gross profit guarantees every scheduled employee is covered by real margin and forces the conversation about which Shifts actually earn their coverage. It also exposes the hidden cost of overstaffing slow periods.

What if my point-of-sale system does not report gross profit by Shift?

Export gross profit by hour and group the hours into your defined Shifts. Most modern POS platforms allow hourly gross-profit reports even if they do not pre-build shift-level views. Average each Shift across the same weekday over three to six months. The manual grouping takes about fifteen minutes per quarter.

How often should I recheck the numbers and re-run the division?

Re-pull your per-Shift gross-profit averages every quarter. Re-run the whole division whenever something structural moves — a menu-price change, a new POS, a Shift in your bake schedule, or a seasonal swing like summer commuter volume dropping off. The anchor itself only needs a look once or twice a year, but the Shift averages drift faster than owners expect.

Can I run a different per-employee target for different Shifts?

You can, but be careful about why. A single flat anchor keeps the yardstick honest and stops managers from quietly lowering the bar on the Shifts they want to overstaff. If a daypart genuinely has a different labor model — a self-serve grab-and-go window versus a made-to-order lunch line — a separate target is defensible, but write down the reason so the number stays a decision, not a habit.

Does the same method work for a Bagel shop as for any other restaurant?

Yes. The division is identical — gross profit on that Shift divided by your per-employee target gives the headcount. Whether you run a single counter or a small group of Bagel shops, the math is the same; you only swap the menu and the Shift averages. The $90 anchor may move with ticket size, but the arithmetic does not.

Sources

• Square: Gross profit reporting and shift-level analytics — squareup.com
• Toast: Restaurant labor management and sales reporting — toast.com
• Clover: Point-of-sale reporting and employee management — clover.com
• Lightspeed: Retail and restaurant POS reporting — lightspeedhq.com
• When I Work: Scheduling pricing and features — wheniwork.com
• Homebase: Scheduling and time clock pricing — joinhomebase.com
• Deputy: Demand-based scheduling and compliance — deputy.com
• 7shifts: Restaurant scheduling and POS integrations — 7shifts.com
• Workforce.com: Labor forecasting and wage-cost management — workforce.com
• Fourth: HotSchedules enterprise workforce management — fourth.com

Related on PULSE

• [How Many Employees Should I Schedule Each Shift at My Ice Cream Shop?](/knowledge/tl0072)
• [How Many Employees Should I Schedule Each Shift at My Watch and Jewelry Repair Shop?](/knowledge/tl0489)
• [How Many Employees Should I Schedule Each Shift at My Smoke and Vape Shop?](/knowledge/tl0496)
• [How Many Employees Should I Schedule Each Shift at My Tailor and Alterations Shop?](/knowledge/tl0491)
• [How Many Employees Should I Schedule Each Shift at My Acai Bowl Shop?](/knowledge/tl0453)
• [How Many Employees Should I Schedule Each Shift at My Bubble Tea Shop?](/knowledge/tl0452)