If you run a restaurant, cafe, or shop with hourly staff, your weekly schedule is a budget you rewrite every seven days — and it controls your largest controllable cost. Labor eats roughly 25 to 35 percent of every sales dollar in food service, and the difference between a schedule built on last month's sales data and one built on gut feel is often the difference between a profitable week and a week where overtime and overstaffing quietly erase your margin. The three names you will hear first are Homebase, 7shifts, and When I Work. All three publish schedules, track time, and message your team. What actually separates them is the pricing model, how deeply they connect to your point of sale, and whether they were built for restaurants specifically or for hourly work in general.
Here is the 2026 comparison by what matters to a small operator, not by marketing.
The Three Profiles
Homebase is the broadest bundle for single-location hourly businesses. Scheduling and time tracking come with hiring, onboarding, team messaging, and HR and compliance tools, with payroll and tip management as paid add-ons. Pricing is flat per location with unlimited employees: a free Basic plan for one location with up to 10 employees, then Essentials at $30, Plus at $70, and All-in-One at $120 per location per month. Payroll costs $49 per month plus $6 per employee paid. If your pain spans the whole employee lifecycle — you are constantly hiring, onboarding, and scheduling — Homebase keeps all of it in one login.
7shifts is the restaurant specialist. Everything in the product reflects how food service actually runs: tip pooling and tip management, POS integrations with Toast, Square, Clover, Lightspeed, TouchBistro, and others, labor cost visibility tied directly to projected sales, and scheduling templates that handle front-of-house and back-of-house together. Pricing is per location: a free Comp plan for a single location with a capped headcount, with paid tiers running roughly $30 to $40 per location per month at the entry level and stepping up toward $70 to $135-plus for multi-unit and enterprise features. If your core problem is labor cost control against volatile sales, 7shifts is purpose-built for exactly that.
When I Work is the flexible generalist with the strongest shift-swapping story. Its OpenShifts marketplace lets employees claim open shifts themselves, and multi-location scheduling with labor sharing suits retail chains, franchises, and businesses with seasonal or on-call rosters. Pricing is per user, not per location: Essentials at $2.50, Pro at $5, and Premium at $8 per user per month, with time tracking and attendance as an add-on rather than a built-in. If your team is small and stable, per-user pricing can be the cheapest of the three. If your roster is large, it usually is not.
The Pricing Math That Decides It
Do not compare headline prices — compare the pricing model against your headcount, because per-location and per-user behave very differently as you grow.
Per-location (Homebase, 7shifts) charges a flat fee per venue no matter how many people are on the roster. This favors businesses with large pools of part-time, seasonal, or high-turnover hourly staff — the classic restaurant and retail profile. Twenty-five employees cost the same as ten.
Per-user (When I Work) charges for each active person on the roster. This favors small, stable teams and punishes roster bloat. Run the numbers on your actual headcount:
- An 8-person boutique on When I Work Essentials: 8 × $2.50 = $20 per month. Cheaper than Homebase Essentials at $30 — though Homebase Basic would cover this team free at one location with up to 10 employees.
- A 25-person restaurant on When I Work Essentials: 25 × $2.50 = $62.50 per month, before the time-tracking add-on. Homebase Essentials covers the same team for a flat $30, and 7shifts' entry paid tier lands in a similar flat range.
- A 40-person roster with seasonal churn on When I Work Pro: 40 × $5 = $200 per month. The equivalent per-location plans cost a fraction of that.
The trap to watch is stale roster seats. On per-user pricing, every former employee still sitting in the system is a monthly charge, and businesses with high turnover can easily pay for 20 percent more seats than they have active staff. Audit the roster quarterly no matter which vendor you choose — but on per-user plans, that audit is money.
Also price the add-ons you will actually need, not just the base tier. Time tracking is an add-on on When I Work's base plans. Payroll on Homebase is $49 per month plus $6 per paid employee — real money for a 20-person team. Tip management on Homebase is $25 per location per month, while tip pooling is core to 7shifts. Build your comparison on the all-in monthly figure for your team size, not the starting price on the pricing page.
Features That Actually Differ
Once pricing is modeled, four capability gaps decide most choices.
1. POS-driven labor forecasting
The single most valuable feature a restaurant scheduler can have is a live view of labor cost as a percentage of projected sales while the schedule is still a draft. 7shifts built its reputation on this: it pulls sales history from your POS, forecasts demand by daypart, and shows whether next Tuesday's lineup lands at 28 percent or 36 percent of expected revenue before you publish. Homebase offers labor cost management at its All-in-One tier with POS integrations of its own. When I Work includes forecast tools even at Essentials, but its forecasting is labor-budget oriented rather than sales-driven — fine for retail coverage planning, less precise for a restaurant trying to staff to a labor percentage target.
If you run food service, confirm your exact POS is on the vendor's supported list before you buy. A scheduling tool that cannot read your sales data is just a pretty spreadsheet.
2. Tip pooling and tip management
Tips are where restaurant scheduling tools most visibly diverge from general ones. 7shifts handles tip pooling calculations natively as part of its restaurant workflow. Homebase pulls tips from your POS, calculates the pool, and pushes it to timesheets — but Tip Manager is a $25-per-location add-on. When I Work has no comparable tip-pooling depth. If you pool tips across servers, bussers, and bar — or split by hours, points, or role — this feature alone can settle the decision, because hand-computed tip pools are slow, error-prone, and a dispute magnet.
3. Shift swapping and multi-location coverage
When I Work's OpenShifts marketplace is the best answer to the eternal "can someone cover my Saturday?" problem: managers post open shifts, eligible employees claim them, and the schedule fills itself within the rules you set. Its labor-sharing features also let multi-location operators float staff between sites. Homebase and 7shifts both support shift swaps and drops with manager approval, but neither centers the self-service marketplace the way When I Work does. For retail chains, franchises, and seasonal operations where coverage flexibility matters more than sales-driven staffing precision, this is the differentiator.
4. Hiring, onboarding, and payroll in one place
Homebase is the only one of the three that tries to own the full lifecycle: job posts, applicant tracking, onboarding documents, time tracking, scheduling, HR compliance, and payroll. For a single-location operator who currently juggles a hiring tool, a scheduling app, and a separate payroll provider, consolidation has real value — fewer logins, one employee record, hours that flow straight into paychecks. 7shifts and When I Work take the opposite approach: they integrate with payroll providers like Gusto, ADP, and others rather than running payroll themselves. Neither approach is universally better. Consolidation is simpler; best-of-breed integrations let you keep a payroll provider you already trust.
The Fair-Workweek Factor
One compliance question should shape your shortlist before price does: are you in a predictive scheduling jurisdiction? As of 2026, Oregon enforces the only statewide predictive scheduling law, and roughly ten local jurisdictions — including San Francisco, Emeryville, Berkeley, Los Angeles city and county, Chicago, Evanston, Seattle, Philadelphia, and New York City — enforce their own fair workweek ordinances. Covered employers, typically larger retail, food service, and hospitality businesses, must post schedules 14 days in advance and pay predictability premiums when they change shifts inside that window.
Even if you are under the employee-count threshold today, growth can pull you into coverage mid-year, and several more cities keep exploring similar rules. When evaluating tools, ask three questions: can it post schedules the full 14 days out and timestamp when each employee could see theirs? Does it flag or log last-minute changes so you can compute predictability pay? Does it track the good-faith estimates and rest-between-shift rules some ordinances require? 7shifts markets restaurant-focused compliance tooling for exactly these ordinances, and Homebase offers HR and compliance features at its top tier — but verify the specific ordinance you operate under, because coverage thresholds and premium formulas differ city by city. A scheduling tool that cannot prove when a schedule was published is a liability in a fair-workweek city, not an asset.
Five Scheduling Mistakes That Quietly Raise Labor Cost
Software only helps if it fixes the habits that inflate your labor percentage. These are the five most expensive ones:
1. Scheduling from memory instead of sales history. The Tuesday lunch shift staffed for Friday dinner volume is the classic margin leak. Pull last year's same-week sales by daypart from your POS, staff to the forecast, and keep one on-call person instead of one extra body on the clock. Industry data consistently shows labor running 25 to 35 percent of revenue — if yours sits above that band week after week, the schedule is the first place to look, not wages.
2. Letting overtime creep past unnoticed. An employee picking up an extra shift here and a swapped shift there crosses 40 hours, and time-and-a-half quietly doubles the cost of those marginal hours. Set overtime alerts before the threshold — all three platforms support them — and require manager approval for any swap that pushes someone over.
3. Publishing late and changing often. Beyond the fair-workweek penalties in covered cities, chronic last-minute changes burn out your best people and drive the turnover that forces you to overstaff as insurance. Publish on a fixed day, honor availability you already approved, and track change frequency per manager.
4. Computing tip pools by hand. Role-weighted, hour-weighted tip splits across a dozen people are exactly the kind of arithmetic that produces a $40 error nobody catches until a server quits over it. Automate the pool, publish the math where staff can see it, and keep the records — tip disputes with no paper trail are unwinnable.
5. Paying for seats you do not need. On per-user plans, offboard departing employees the same week they leave. On per-location plans, resist tier upgrades for features you will not use — if you do not need onboarding documents and HR libraries, the middle tier's scheduling engine is the same one. Revisit the plan annually against actual headcount and feature usage.
The Bookkeeping Link — Turn Schedules Into Labor Intelligence
Scheduling software generates some of the most valuable financial data your business produces, but only if it reaches your books. Three connections matter.
First, labor cost as a percentage of sales is a weekly metric, not a monthly one. A month-end P&L tells you labor ran 34 percent; a weekly series tells you which weeks, which locations, and which dayparts broke the budget while there is still time to fix the next schedule. Export scheduled versus actual hours and pair them with POS sales weekly. If you want that trend visible at a glance instead of buried in spreadsheets, a dashboard view of your finances turns the weekly labor series into a chart you can read in seconds.
Second, time-clock data should flow into payroll without retyping. Every manual transcription from timesheet to paycheck is an error opportunity and an hour of admin. Whether you run payroll inside your scheduling platform or push approved hours to an external provider, the rule is the same: one system of record for hours, manager-approved, locked before export. Keep the approval audit trail — it is your evidence if a wage claim ever questions the hours.
Third, book labor where it belongs. Gross wages, employer payroll taxes, and benefits are separate lines, not one "payroll" blob; tips distributed through a pool have their own reporting path; and predictability premiums in fair-workweek cities are wage expense, not penalties. Clean categories let you see whether a rising labor percentage comes from headcount, overtime, wage rates, or compliance premiums — and each of those has a different fix. The bookkeeping guides in the docs walk through setting up a chart of accounts that keeps these lines distinct from day one.
Keep Your Labor Costs Visible Week After Week
The right scheduling tool pays for itself the first month it prevents one overstaffed week or one overtime surprise — but the tool is only half the discipline. Pair it with books that track labor as a share of revenue every week, and you will spot problems while they are still small. Beancount.io offers plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
