Do I earn enough to live on as a hospitality worker?

The honest short answer

Sometimes yes, but often only barely. I cannot honestly answer with a simple yes because whether a hospitality worker earns enough to live on depends above all on location, contracted hours, role, and how reliably those hours actually happen. In Germany, there are at least solid reference points: since 1 January 2026, the statutory minimum wage is 13.90 euros gross per hour, and tips must not replace wages, as the Federal Ministry of Labour and Social Affairs and section 107 of the Trade Regulation Act make clear. Whether that is enough to live on depends on having enough predictable hours and rent that does not swallow nearly everything.

That is why, as a restaurateur, I do not hide behind “it depends” and leave it there. If someone’s income only works because they constantly do overtime, grab last-minute extra shifts, or happen to get lucky on high-tip evenings, then I do not consider that stable enough for a real life. At that point I cannot look only at the till or the payroll total. I have to look at the whole working reality. A business that appears decent on paper but cuts hours, handles breaks unclearly, or keeps moving shifts around does not create a dependable income. My responsibility starts there, not only when the next recruitment round begins.

Which number actually helps you

A useful starting point is the Federal Employment Agency’s pay atlas. For restaurant service professionals in Germany, the 2025 median full-time gross monthly pay is 2,652 euros; the lower quartile is 2,275 euros and the upper quartile is 3,128 euros: BA Entgeltatlas for restaurant service professionals. The method matters: the median is the middle reported gross full-time wage among socially insured employees, so it is neither net pay, nor a personal entitlement, nor a tip figure: methodology of the BA pay atlas. That number does not answer your whole life, but it does show whether an offer sits roughly in the market or clearly below it.

I explain comparison figures like that openly to my team, because pay conversations go wrong quickly when people compare unlike things. If someone hears 2,652 euros gross, they should not confuse that with what lands in their bank account. If someone works part time, they should not simply halve the figure and assume their fixed costs also halve. A simple example shows why: two servers may have the same hourly wage, but one gets 40 predictable hours and the other swings between 22 and 34 each week. On paper, both jobs may look similar. In daily life, only one of those people can plan calmly. That is why I do not judge pay only by wage level, but also by guaranteed volume, seasonal gaps, shift stability, and how often someone ends up earning less than planned through no fault of their own.

An example from my restaurant routine

Take a fictional server in a neighbourhood restaurant with a busy lunch trade and long Fridays. They earn 14.80 euros gross per hour, are scheduled for 32 hours a week, and receive tips on top. At first glance, that looks reasonable because the hourly rate is above the statutory minimum. But if Mondays are often too quiet, two shifts a month get cancelled at short notice, and the person has to sacrifice private plans to fill weekend gaps, the same wage can quickly become too low for a dependable life. The problem is not only the euro amount. It is the lack of predictability in what actually reaches them at the end of the month.

As the operator, that is exactly where I need to calculate properly. I do not ask only, “What does this hour cost me?” I ask, “What income does this person realistically take home month after month with this shift pattern?” If I can see that someone regularly needs extra shifts just to cover rent, transport, and normal living costs, then my system is not balanced fairly. The answer might be a different minimum hours basis, a clearer weekly rhythm, or a real pay increase that matches responsibility. If one employee runs the terrace independently, handles complaints, and helps train new colleagues, they are no longer working at entry level. I should translate that growth into money and predictability, not only into praise after service.

How I decide whether pay is truly sustainable

When I judge whether pay is enough to live on, I look at four very concrete criteria. First: does the fixed income cover basic costs without relying on tips? Second: are the monthly hours stable enough that the person does not live in constant uncertainty? Third: does the pay match the real level of responsibility, such as lone shifts, cash handling, or section leadership? Fourth: is there development, so an entry role does not become a dead end forever? If the answer is no on two of those points, I do not pretend that team spirit or one strong weekend will solve the issue. At that stage the pay may not be disastrously low on paper, but it is too weakly organized in practice.

For employees, that means not judging your income by one unusually good month. Look at three to six months together. Were there unpaid waiting periods, unwanted minus hours, chaotic shift swaps, or sharply fluctuating tip levels? If yes, the job may feel lucrative on a busy Saturday and still fail to support everyday life consistently. One common trap is focusing only on the hourly rate. Fifteen euros sounds better than fourteen, but it helps little if you are repeatedly sent home early. A slightly lower rate with honest, fixed scheduling can be more liveable in reality. That is why every pay conversation should also be a conversation about how work is assigned and protected.

How I organize this fairly in the business

Fairness does not begin with the annual review. For me it starts in the shift plan. If shifts are constantly moved around by word of mouth, nobody can judge their likely income properly. That is why I keep shifts, roles, and actual working times traceable. In Bonzumo, I use shift planning, time tracking, and roles so it stays visible who was scheduled, what was actually worked, and what level of responsibility someone carried. That does not magically create higher wages, but it does create a fair basis for decisions. If someone regularly closes later than others, catches exceptions at short notice, or takes on more leadership, that should not disappear into memory. In daily operations, Give your team a clear start to every working shift is genuinely useful for that structure.

The practical benefit is simple: I do not discuss pay only by gut feeling or by who speaks the loudest. I can look at patterns. For example, if a colleague says they have effectively been carrying the late shift and the cash closing for months, I can review how their shifts were placed, what exceptions appeared in working times, and whether their system role still lags behind their real responsibility. That turns “I think I’ve been doing much more for a while now” into something reviewable. The result may be a higher hourly rate, a clearer internal shift allowance rule, or a different distribution of tasks. Software does not replace the conversation, but it does stop good people from being worn down by vague impressions that never get clarified.

What to raise in a pay conversation

If you are wondering whether your wage is enough to live on, do not walk into the conversation saying only, “I need more.” Bring the actual picture. State your hourly rate, your average monthly hours, the fluctuations, and the extra duties you now carry. A strong example would be: “I usually run the outdoor section alone four evenings a week, handle the final cash clarification, and regularly jump in at short notice. At the same time, in quiet weeks I lose planned hours.” That makes clear whether the issue is a low wage, too few reliable hours, or both at once. That distinction usually leads to a fairer decision faster than comparing yourself vaguely with colleagues.

In that kind of conversation, I also owe clear answers as the operator. If I cannot immediately promise more money, I should not hide behind general phrases. I need to say what the decision depends on: current revenue, a seasonal transition, a higher task level, or a change in deployment planning. Just as important is what would be unfair. It is not fair to point to tips, to treat real extra responsibility as if it were automatic, or to keep someone waiting for months with “soon.” If I promise development, I set the next review point and keep it. Anything else damages trust faster than a single euro can rebuild it.

When I have to act before anyone asks

There is a point where I should not wait for employees to bring up the topic themselves. If I can see that resignations, constant cover requests, and exhaustion keep hitting the same people, that is often also a pay problem. Then I do not review only revenue and labour costs. I review the team’s actual working reality. A business that constantly replans at short notice wears people down. A shared data basis from order to closing can help me structure shifts and responsibilities more cleanly, as described in Connect the work behind every successful service, but the leadership decision is still mine. Better process order has value only if it leads to fairer conditions for the people doing the work.

In the end, I answer the question like this: you earn enough to live on when your pay regularly covers your basic costs without wishful thinking, your hours are dependable, and your responsibility is visibly paid for. If it only works in strong weeks or only when tips happen to be generous, then it does not truly work. From my perspective as a hospitality operator, that is not an employee’s private weakness. It is an organizational warning sign. I then need to review prices, scheduling, roles, or the pay model itself. Good people do not stay because of big words. They stay because they can live from their work without trembling every month. That is the standard by which I judge whether my business is being run fairly.