Hospitality pay averages PLN 7,003. After summer, restaurants count hours, not just covers
On 28 August 2026 Horecanet.pl asked venues to close the summer books beyond the sales report. On 20 August Statistics Poland put average July pay in accommodation and food service at PLN 7,003.44 — the lowest among classified sections. For a restaurateur that is the moment to line up hours, no-shows and stores against what went through the till.
On 28 August 2026 Horecanet.pl wrote that by the second half of August many venues can already see the outline of a seasonal balance sheet. Teams have worked hundreds of hours. Equipment, the back of house and procedures have been through a load test. September is a decent moment to look at summer through more than the sales report.
The piece, prepared with Winterhalter Polska, asks plain questions. What did energy and water cost. How much chemical was used. How many glasses and plates need replacing. How much overtime did the team work. How many people left in the busiest weeks. Strong turnover can look cheering. Only lining it up with those lines shows whether the season paid.
On 20 August Statistics Poland released July wage figures. Average pay in the enterprise sector was PLN 9,509.02 gross, 6.8 per cent higher than a year earlier. In accommodation and food service it was PLN 7,003.44. That is the lowest among the classified sections. In July 2025 the same section stood at PLN 6,593.37.
In the venue the two stories meet on the same rota. A peak-hour shift costs more than a year ago. The till report still does not say how many of those hours went into overtime, empty tables and food that never reached a plate. A restaurant season close starts with that match, not with another turnover chart.
What GUS and the debt register said about hospitality
The GUS wage note of 25 August confirms the July figures. Real average pay in the enterprise sector rose 3.6 per cent year on year. Nominal wages rose in every section. Hospitality still sits more than PLN 2,500 below the rest of the economy.
Paid employment in the enterprise sector in July was 6,378.9 thousand full-time equivalents, 0.8 per cent lower than a year earlier — GUS said so in its labour-market round-up. In accommodation and food service headcount was 1.7 per cent higher than in July 2025. Analysts at mBank, quoted by Bankier.pl, linked the stronger wage rise in that section in part to a decent tourist season.
The GUS figures cover firms with at least ten people in work. They leave out mandate contracts and self-employment, both common on the restaurant floor. PLN 7,003.44 is therefore a picture of a payroll job in a larger firm, not a seasonal waiter’s rate. The floor is still hard. From 1 January 2026 the monthly minimum wage is PLN 4,806 gross and the minimum hourly rate on specified civil-law contracts is PLN 31.40, under a Council of Ministers regulation and the ministry note.
Cash flow looks worse once the view drops from payroll to invoices. On 31 July Bankier.pl covered a BIG InfoMonitor report. At the end of May 2026 overdue HoReCa liabilities stood at PLN 1.88 billion, 7.5 per cent lower than a year earlier. Hotels cut arrears by more than PLN 170 million, to PLN 689 million. Restaurants and other food-service outlets went the other way: up PLN 24 million, to almost PLN 902 million.
Over the year 401 firms dropped off the lists of unreliable payers. The report’s authors, quoted by Bankier.pl, wrote that the holidays promised occupancy but would also test many businesses against a jump in operating and labour costs. September is when that test shows up in the till — if someone actually lines the numbers up, rather than remembering that “summer was good”.
A garden restaurant and three versions of the same day
Picture a restaurant with a terrace and several dozen covers. The kitchen runs one shift on weekdays and two on Friday and at the weekend. From May to August seasonal waiters join a standing team. This is not a real client. It is a typical independent venue that has survived the season and now has to count it.
There is a fiscal till and a card terminal. The rota lives in a spreadsheet and a messenger chat. Reservations are taken on the phone, some arrive from a booking site, some sit on a pad by the bar. Takeaway goes through three delivery apps. Stores are a notebook by the cold room and the head chef’s memory of what came in on Friday.
In August the daily take looks fine. In September, when the terrace goes quiet, Saturday overtime, cancelled no-shows and Sunday product that guests did not eat have eaten what the till presented as a season. The owner holds three truths about the same day: the receipt, the list of people on shift, and what is left in the cold room. None of them matches the others without a manual reconciliation.
Two things would be enough in this story. First, a shift tied to the till day: who was in, how many hours, what that crew sold. Second, a reservation list marked for tables that stayed empty. The rest — chemicals, glass, a dishwasher breakdown — can be hung on that day once the day exists as a record, not as a memory of Saturday.
Hours on the rota and hours that turned into overtime
Horecanet.pl asks outright how much overtime the team worked and how many people left in the busiest weeks. In a terrace venue those questions become specific. A Friday night with a full garden; a Saturday when two people did not show. The kitchen stays an hour longer because the wash-up cannot keep up. Waiters close the room after midnight even though the rota ended earlier.
The cost of that hour does not appear on the receipt. It shows up later, in the wage bill and in fatigue that in September ends with the departure of someone the venue trained from June. GUS does not publish the price of a hospitality overtime hour. It does show that a job in this section is still the lowest among classified industries, and that July pay in the wider enterprise sector rose at its fastest pace since December. An hour left “for now” therefore costs more than a year ago, even if the contract rate did not move from week to week.
A spreadsheet rota holds as long as one person remembers who swapped a shift and who stayed after a breakdown. When seasonal staff rotate, that memory breaks. Pay is drawn from a different file than the crew list. The till does not know how many people served the same turnover.
A shared rota with hours against a given day closes that gap. A shift has a start, an end and a status: arrived, late, no-show, stayed over. Beside it sits till sales for the same date. The restaurateur can then see whether a PLN 18,000 Saturday needed twelve people, or nine plus three hours of overtime because someone was missing. That does not replace payroll. It gives payroll something to stand on.
A table booked, no guest in the chair
Horecanet.pl notes that a restaurateur cannot control whether every booking actually arrives. They can control whether they learn about an empty table before the shift opens, or only when the till is closed.
In the terrace example, bookings sit in three places. The phone, a portal, a slip of paper. The waiter does not know whether the 9 p.m. table still stands. The kitchen has prepped for the promised covers. When two tables of six fail to appear, the salads and the meat do not go back to the state they were in an hour earlier. The crew stays, because the rota was built on the forecast, not on who sat down.
No-shows cost more in summer, because a terrace table cannot be refilled the way a quiet weekday room can. The cost is not only the lost bill. It is the hours of people who came in for that forecast, and product that left the cold room too early.
A single table-booking calendar with an SMS or email reminder and a status of confirmed / unconfirmed / no-show does not abolish no-shows. It cuts the number of surprises after 6 p.m. A deposit, or a card held against larger tables, works where the venue is willing to ask. An off-the-shelf booking tool is often enough. The snag starts when that same table has to feed the staffing rota and the kitchen ticket, and the portal will not hand the record to the till.
The cold room, the recipe and what never reached a plate
In its post-season audit Horecanet.pl tells venues to count chemicals, glass and plates. In the kitchen the same logic applies to food. How much came in before the weekend. How much left the menu. How much went in the bin after a Sunday when rain kept the terrace empty.
Food cost — the share of food spend in take — is still worked out in many venues from the wholesaler’s invoice and from memory. The head chef knows the cod ran expensive. There is no figure that matches goods in, goods used and sales of that dish. High season hides it, because turnover is large. September uncovers it when July and August invoices meet a quieter room.
A notebook by the cold room is enough in a small site that orders twice a week from one supplier. When extra drops, a second wholesaler and “just in case” stock for communion or corporate bookings pile in during the season, the notebook stops saying what vanished between delivery and the plate.
A simple goods-in and usage record need not be a pharmaceutical warehouse. It is enough that a delivery has a date, lines and a week, and that menu dishes have a recipe with weights. Then one can ask how much cod went into two hundred portions, and how much to treat as waste. A spreadsheet will carry a dozen lines. On a menu that swells with summer extras, and with two people taking deliveries on alternate shifts, a shared list with use-by dates saves the morning guess about what to throw out.
App commission and a bill the dining-room till never sees
A fiscal till report does not include Pyszne, Glovo or Uber Eats commission. That money comes off the platform transfer, sometimes late, sometimes with an adjustment for a guest complaint the venue never saw. In high season the delivery share rises, because the terrace is full and the kitchen is working anyway. Margin on that channel looks like turnover. It is turnover minus a teens, sometimes more, of a per cent, and minus the packaging.
In the terrace example three apps live beside the till. The waiter does not know whether a takeaway ticket loaded the same shift that was running the room. The kitchen sees another docket. The owner sees a transfer every other week. In September, lining up the invoices, part of a “good summer” turns out to have been sales on which the venue paid commission and film.
A ready-made delivery channel makes sense when a venue has no online traffic of its own and does not want to run couriers. It stops adding up when the same meal can be sold from a website or from an in-house ordering system with collection, without a cut of every basket. Hooking one platform so that the order joins the same kitchen queue as the room is often a saner first step than building a fleet. What matters is that the app ticket lands on the same day as the receipt, rather than living in a separate console nobody opens at the shift close.
The same applies to ordering from a QR code at the table. A menu on the guest’s phone will not replace a waiter on a Saturday terrace. It can shorten the bar queue when the room is full, and give the kitchen a ticket without a slip that vanishes between tables. In the season close what counts is whether those tickets entered the same sales as the till, or sat in a separate app that nobody added up with August.
The seasonal waiter who left in August
Horecanet.pl goes back to the start of the season: when hiring began, how the advert was written, whether newcomers learned the stations quickly. Seasonal hospitality lives on people who stay a few months. Not every departure can be avoided. One can count how many weeks it took before a new person stopped asking where the second board is and how the terrace is closed.
In the example venue, induction is a story told at the pot-wash. Someone shows it once; the rest “will pick it up”. When two people who knew the garden leave in July, the next shift learns from people who have been there a month. Mistakes on tickets and a slower close do not show up as a recruitment cost. They show up as slower service and another Saturday of overtime.
A station list with a short opening and closing checklist does not sound like innovation. In a season when a dozen people pass through the venue, it is the difference between an hour of explaining and a quarter of an hour on the phone. An app in the waiter’s pocket that shows the table, the allergen and the booking status cuts questions to the floor. It does not replace the shift leader. It takes away some of the chasing that in August finishes at eight instead of half past.
A July breakdown and a day the service log never saw
In the Horecanet.pl piece a breakdown in July means something different from a breakdown in November. The price of a machine is visible at once. The cost of it sitting idle on the most profitable weekend of the year comes later. Time from the call to a return to work, parts on the shelf, hours in fallback mode — those lines get lost between the service number and the receipt.
In the terrace restaurant a dishwasher that dies on Saturday means hand-washing, a longer close and more breakages. The team remembers the evening. In the August accounts it remains a higher water and chemical bill and overtime, with no link to a specific call-out.
A log of service calls need not be a corporate CMMS. Date, machine, symptom, who rang, when it came back. If that record hangs on the till day, September shows whether a “weak weekend” was weak trade or a weekend without a washer. With several sites, or kit on lease, such a list starts to earn its keep sooner than in a single kitchen with one engineer the owner already has on speed dial.
Spreadsheet, off-the-shelf, a hook, or a built application
Not every venue needs new software after the season. Some need an hour with a pencil and a decision about what not to do in 2027.
A spreadsheet is enough when there is one site, one person drawing the rota and a handful of bookings a day. The cost of mess is then the owner’s time, not a coordinator’s wage. Off-the-shelf SaaS — a till with stock, a booking portal, a rota app — is reasonable when the venue’s process fits what the product already does. Integration makes sense when the till, bookings and delivery already exist and the missing piece is a bridge: the app order in the same queue as the room, rota hours against the sales-report date.
A built application starts to pay when the package forces the venue to change how it works. Two sites, different menus, one store. Or a terrace, a dining room and a food truck under the same firm, while the booking platform only handles tables. Or delivery commission is large enough that an in-house channel pays back in season, but has to land on the same kitchen as everything else. An off-the-shelf programme stops adding up when three systems require the same day to be typed in by hand.
No panel replaces the tax office or the fiscal till. JPK, VAT records and KSeF stay where the statute puts them. The point is that the venue’s day — people, tables, goods, app tickets — can be lined up before accounts close the month.
Where GESOFT fits
GESOFT builds panels and applications around a firm’s process, not a generic “restaurant in a box”. In the story above the point is not to rip out the till. It is that the rota, the booking, goods-in and the delivery ticket can meet on one date. Sometimes it is enough to add the missing piece to what the venue already runs. Sometimes it is cheaper to assemble one panel that collects those pieces.
The threads above yield functions, not a catalogue. A shift with hours and an attendance status next to till sales. A table calendar with a reminder and a no-show flag. A delivery intake with a date and a simple recipe. An order queue that takes both the room and the online channel. A service-call list on the day that looked different because a machine died. On the waiter’s phone: table, allergen, booking status, without a call to the floor.
If summer 2026 could be counted only because someone remembered the Saturdays, it is worth setting down before summer 2027 which figures should arrive on their own. Not for another login. So that September does not start with a guess about whether the season was good, or only loud.
Describe your project