1. I start by checking whether the business can really carry itself
Before I buy a restaurant, I ask these core questions first: Which sales are cleanly documented, which ongoing costs are fully visible, which contracts and obligations would transfer to me, what condition are the premises and equipment in, which team members are actually staying, and how will the handover of data, access, and open operations work? If I cannot get solid answers on those points, I do not buy on instinct. A strong location or a likable seller does not replace traceable records. What matters is not what is claimed in conversation, but what I can verify in reports, lists, contracts, and a handover plan that is organised enough to survive the first week of trading.
That is why I do not settle for one annual figure. I want the sales records shown in a way that lets me read the pattern: by month, by weekday, by lunch versus evening trade, ideally with visible fluctuations. For example, monthly revenue of 70,000 euros may sound decent, but it says very little if a strong December is hiding a weak summer. I also ask for food cost, labour cost, rent, utilities, leasing, transaction fees, repairs, and recurring outside services. If the records are incomplete, I do not romanticise that as flexibility. I treat it as a real risk to my start, because I would be taking over uncertainty, not just a dining room.
2. With revenue and costs, I ask about structure, not just an attractive total
I want to know what actually generates the revenue and how fragile it is. Does it mainly come from walk-ins, reservations, events, lunch business, or one unusually strong delivery partner? Is the menu broad while only ten items really carry the place? Are beverages selling well, or does the contribution margin depend almost entirely on the plate? Those questions show whether I am taking over a stable operation or just a short successful phase. I also ask whether unusual months were caused by building works, one-off events, or staffing gaps. Otherwise it is easy to mistake an outlier for a dependable average and pay for a level of performance the business does not usually deliver.
On the cost side, I do not only care about the amount. I care about the commitment behind it. Which expenses continue immediately when I take over, and which ones could realistically be renegotiated? I ask about energy, maintenance, POS costs, draught system servicing, grease trap, laundry, music licensing, waste disposal, marketing, and the small recurring charges that become heavy in total. One practical example: the rent may look manageable, but if refrigeration, ventilation, and dishwashing equipment are old, I may be facing major replacement spending soon after completion. In that case, the apparently low purchase price was only the opening number. That is why I separate ongoing costs, postponed costs, and one-off start costs very carefully in my decision.
How the ideas connect
The opening sections of this article, shown together.
What should you check before buying a restaurant?
You must verify documented revenue, visible ongoing costs, which contracts and obligations transfer, the condition and ownership of…
1. I start by checking whether the business can really carry itself
Before I buy a restaurant, I ask these core questions first: Which sales are cleanly documented, which ongoing costs are fully visible,…
2. With revenue and costs, I ask about structure, not just an attractive total
I want to know what actually generates the revenue and how fragile it is. Does it mainly come from walk-ins,…
3. I inspect inventory and equipment as future working tools, not decoration
I never buy a restaurant with only the dining room in mind. I ask very specifically: Which appliances, furniture, refrigeration units, storage racks, smallwares, and production tools are really included in the sale, what is leased, what is rented, what is defective, and what is only temporarily on site? With a coffee machine, draught system, POS hardware, or dishwasher, the difference between ownership and mere use often sits in the fine print. So I walk through kitchen, storage, front of house, terrace, and back rooms with a list in hand. Missing pieces, makeshift fixes, and signs of repeated repair go on that list immediately. Arguing later from memory usually costs more than doing one structured inspection properly at the start.
I also ask how old the key pieces of equipment are, when they were last serviced, and whether manuals, keys, security codes, and service records are complete. A typical handover example is a pizza oven that technically works, but only one person knows its quirks and spare parts take a long time to arrive. To me, that is not a side detail. It is production risk. For stock, I separate another question: which counted quantities are actually meant to transfer, and how are they being valued? An inventory count, for me, is not guessing. It means counting, checking, and labelling old stock, seasonal leftovers, or opened packs honestly. Anything less quickly turns into conflict about value and usability.
4. I have contracts reviewed professionally before I assume any security
The most important question is often not what I am buying, but what I will be tied to afterward. I review the lease, all amendments, durations, indexation clauses, service-charge rules, non-compete protections, permitted use, opening obligations, fit-out duties, and any landlord approvals required. Alongside that, I look at supplier contracts, leasing agreements, maintenance, phone, internet, music, waste, draught system, coffee systems, and any website or reservation services. I do not rely on the seller’s summary of these points. I have the documents read professionally. A contract can look commercially sensible at first glance and still contain operational commitments that become expensive in day-to-day life once I am the one carrying them.
I ask just as directly about obligations that are not visible in the furniture: deposits already taken for events, unredeemed gift vouchers, ongoing complaints, supplier bonus agreements, repairs not yet invoiced, or investments already promised to others. A simple example is a calendar full of Christmas parties that have been sold, while price, menu, and staffing need were badly calculated. I would not just be taking over revenue. I might be taking over loss-making dates. That is why I want a list of open matters with a clear cut-off date. If the business already works digitally, I also need to know who controls reservations, the till, reports, and guest data. Those access rights, responsibilities, and unresolved digital tasks should already be documented in full on the handover checklist before the transfer.
5. With the team, I do not just ask who is there, but who actually carries the place
I judge staffing need by function, not by a list of names. Who leads shifts, who knows purchasing and prep, who works reliably on the pass, who can handle reception, who covers weekends, who is only seasonal, and where does knowledge depend on a single person? I ask openly which employees are likely to stay, what hour models exist, and where immediate recruitment gaps may appear. A business can look fully staffed on paper and still be operationally under-resourced if key roles are leaving. The opposite can also be true: a small team that works well together may be more valuable than a long roster of casuals with weak reliability. That operational reality has to be visible before I buy, because replacing structure after takeover is always slower than people expect.
I also check how onboarding, shift planning, and permissions are organised. If I am taking over, I do not need a theoretically perfect setup in the first weeks. I need clear responsibilities. One example: the kitchen lead is staying, but nobody can adjust rotas cleanly or onboard new starters in a structured way. Then the bottleneck is not at the stove. It is in management. For my later everyday operation, it helps to think early about roles, shifts, and access in an organised way, much like giving the team a clear start to every working shift. That does not replace proper staff due diligence, but it shows whether the business can actually be handed over in a workable form instead of only looking complete during the sale.
6. Hidden burdens usually appear in the questions that no sales brochure answers
I always ask: Which problems are currently costing time, money, or nerves even though they do not appear in the sales file? That can include recurring technical faults, staff conflict, disputes with neighbours, complaints about noise, unclear storage routes, weak peak-time workflows, or a menu that has become too broad to execute well. Issues like that rarely show up first in the headline numbers, but they quickly reduce performance after takeover. For example, revenue may be respectable, yet service collapses every Friday because kitchen, pass, and payment station are arranged badly. Then I am not buying a functioning rhythm. I am buying daily friction that I will have to redesign before I can improve anything else.
Data access and system control matter just as much. Who has admin access to the till, reservation tools, online profiles, website, review platforms, social media, delivery services, email inboxes, and possibly accounting export settings? If passwords, roles, or contract ownership are unclear, a handover that looked smooth on paper can already stall on day one. I do not want to hear that it will surely be sorted out later somehow. I want a concrete list showing each system, the current owner, the access path, the contract status, the handover date, and the new responsible person. Only when these points are recorded properly do I consider the technical handover to be planned on a reliable basis.
7. In the end, I only decide with a handover plan and clear walk-away criteria
I only buy a restaurant once the handover is organised, not just the price discussed. I ask: From which date do I carry revenue and costs, which stock will be counted into the transfer, which reservations and events move over with the business, who informs the team, suppliers, and regular guests, and which days are set aside for stock count, keys, training, and system changeover? A clean transition prevents me from standing in service on the first evening with missing codes, unclear deliveries, and disappointed guests. What helps is a sequence with a fixed cut-off date, named responsibilities, a document list, and a protocol for open items. Anything still unclear by handover does not go onto my to-do list as hope. It goes into my purchase decision as risk.
My walk-away criteria matter just as much. If the sales records are not reliable, major contracts are not provided, the condition of costly equipment remains unclear, key staff are in fact leaving, or data access cannot be transferred properly, I stop the buying process. That is not harshness. It is self-protection for the future business and for the people who are meant to work there. A restaurant purchase works when I do not fall in love with the idea, but test the organisation: numbers, inventory, obligations, team, and handover. That is what creates a fair operator’s decision. Not charm, not a polished tour, and not a hopeful promise, but a business that can be taken over responsibly under clear conditions.
Putting it into practice
Later sections put the topic in the context of day-to-day operations.
5. With the team, I do not just ask who is there, but who actually carries the place
I judge staffing need by function, not by a list of names. Who leads shifts, who knows…
6. Hidden burdens usually appear in the questions that no sales brochure answers
I always ask: Which problems are currently [costing](/en/resources/build-hygiene-food-standards-into-costing/) time, money, or nerves…
7. In the end, I only decide with a handover plan and clear walk-away criteria
I only buy a restaurant once the handover is organised, not just the price discussed. I ask: From which date do I carry revenue and…