How I Organize My Restaurant’s Supply Chain

Plan backward from the menu

I organize my restaurant’s supply chain by starting with the menu, not with a supplier list. The practical answer is simple: first decide what I need to sell reliably, at what quality, on which days, and how much disruption I can absorb if one item fails. From there, I define which ingredients are critical, which are replaceable, and which only make sense seasonally. If, for example, I run a weekly special with fresh fish, two pasta dishes, and one prepared sauce, I do not need one general purchasing routine. I need three different sourcing approaches, because perishability, delivery timing, and fallback options are not the same.

That is why I separate products into A, B, and C items. A items are either high-turnover or especially sensitive, such as meat, fish, dairy, or a house dessert with a short shelf life. B items matter, but I can replace them more easily, for example certain vegetables or drink ingredients. C items are supporting products where small fluctuations rarely damage service. This changes my priorities immediately: A items get tighter ordering cycles, a second possible supplier, and stricter goods-receipt checks. C items can be bundled more calmly. That way I am not deciding from instinct, but from revenue impact, quality risk, and the real cost of running out.

Turn recipes and quantities into real purchasing needs

A supply chain stays unstable if I only order what feels low. I need a defensible answer to what my restaurant is actually going to use over the next few days. That is why I work with maintained recipes, ingredient quantities, and base recipes. If one pasta plate needs 120 grams of pasta, 160 grams of tomato sauce, and 25 grams of parmesan, I can connect sales volume and production demand much more cleanly. Bonzumo helps here in a concrete way: I can assign ingredients and quantities to products, use base recipes that account for yield and waste, and see calculated recipe costs. Understand what goes into every dish on your menu is useful here because it supports one shared, checkable basis instead of scattered assumptions.

For my team, that means I do not look only at the storeroom before a busy weekend. I look at the planned menu and the usual sales pattern together. If I expect to sell 80 portions of lasagna, I review the stored recipe, compare it with the stock we physically have, and then plan purchasing from that gap. The benefit is concrete: fewer emergency purchases, less overstock, and fewer arguments about why a core item suddenly disappeared. If one ingredient price rises sharply, I can also judge more soberly whether I should adjust portion size, selling price, or supplier mix. The crucial detail is maintenance: these calculations only help if ingredient quantities and purchase prices are kept current by the team responsible for them.

Manage suppliers by risk, not only by price

Many restaurants make the mistake of choosing suppliers almost entirely by the lowest purchase price. I care more about delivery reliability, quality consistency, complaint handling, pack sizes, and whether the ordering window fits my actual turnover rhythm. A cheap ten-kilo carton is not cheap if I regularly end up writing part of it off. So I rate suppliers by several criteria: on-time delivery, minimum order quantity, response speed, quality fluctuation, substitute options, delivery windows, and invoice discipline. Only after that do I compare price. In practice, that often protects margin better than a small nominal discount on paper.

Internally, I assign one main source and at least one fallback per product group. For example, I might use a regional supplier for fresh herbs, a wholesaler for dry goods, and a specialist for certain cheeses. Problems start when nobody on the team knows who is allowed to decide during a disruption. So I define which products may never be substituted without approval, which alternatives are acceptable, and at what price difference someone must escalate the decision. In Bonzumo, suppliers and procurement orders can be maintained within the inventory workflow, so I can prepare demand, stock, and planned orders in one context. The decision still belongs to us as operators, but the information no longer lives in chats, emails, and paper notes.

Set ordering rhythms, minimum stock, and realistic buffers

A good supply chain needs rhythm. I do not order everything every day, and I do not order everything on a rigid weekly cycle either. I set the rhythm by perishability, storage space, delivery windows, and actual sales patterns. Fresh lettuce, bread, or berries need tighter cycles than canned goods or dry pasta. From that, I define an ordering rhythm and a minimum stock level for each item group. Minimum stock is not an abstract number. It is my lower threshold for surviving until the next realistic delivery, plus a safety reserve. If deliveries come on Tuesday and Friday, my stock logic must look different from a business that gets supplied daily.

I keep that buffer deliberately tight enough to protect us without creating false comfort. A simple example: if I usually need 70 burger buns on a normal day and 140 on Saturdays, one generic stock cushion is not enough. Then I set separate thresholds for weekdays and peak days. The same applies to drinks when the terrace is open, during public holidays, or during a city event. The trap is obvious: buffers that are too large create spoilage and tie up cash; buffers that are too small create 86 lists and frustrated guests. So I review thresholds not only seasonally, but whenever the menu, opening days, weather dependency, or guest pattern changes in a noticeable way.

Control goods receipt, storage, and quality properly

The supply chain does not end when a delivery reaches the back door. It only works when goods receipt and storage are organized reliably. For every important delivery, I check at least the product, quantity, visible condition, date, pack size, and obvious temperature issues. For highly perishable food, a stock list alone is not enough. In Germany, food business operators must organize safe food and hygienic processes using HACCP-based procedures under Regulation (EC) No 852/2004, with practical guidance explained by the BfR on the HACCP concept and the BfR on food hygiene. A merchandise list does not prove food safety by itself.

Operationally, that means my team does not put away a delivery casually between two guest rushes. One person is responsible, there is a sequence, and there is a defined reaction to defects. If, for example, strawberries arrive bruised or yogurt cups are damaged, the goods are separated, documented, and the supplier is contacted immediately, instead of letting the issue reappear later as an unclear fridge problem. After that, I store products so that what needs to be used first is also easiest to reach first. One small detail helps a lot: I assign fixed storage zones by product type and supplier. That makes wrong placements easier to spot and lets us discuss complaints based on facts instead of vague memory about “the crate from yesterday.”

Check stock, identify shrinkage, and justify reorders

I can only control the supply chain if I regularly see what is really there. That is why stocktaking does not belong only at month-end. I use it as a tiered routine: fuller counts for key product groups, spot checks for sensitive positions, and additional counts before major orders. Bonzumo supports this with item information, stock movements, and inventory counting for recording and evaluating counted quantities. The honest limit matters: the system helps us capture and compare stock in a structured way, but it does not replace careful physical counting and it does not automatically explain every variance. For me, that is realistic rather than disappointing, because waste, spoilage, and posting errors always have operational causes.

So I never discuss differences as a vague “something is missing.” I check concrete causes. Were portions too generous? Was one crate opened and moved incorrectly? Was a special menu planned but never properly translated into demand? A practical example: if the recorded stock suggests we should still have six liters of cream but the count shows only two, the right reaction is not immediate blame. We first check the delivery note, production batches, spoilage, and posting mistakes. That is how reorders become justified instead of panicked. And if I notice the same products repeatedly becoming unclear, I change the process before I simply raise order volumes. Better discipline usually helps more than a bigger buffer.

Keep kitchen, service, and purchasing on the same page

Even the best supply chain breaks down if kitchen, service, and purchasing are not working from the same situation. I need one short, reliable daily alignment: what is running low, what is sold out, which prep changed, which delivery is delayed, and which substitute is approved for guests. That conversation cannot start only when the pass is already under pressure. Especially with components that affect several dishes, the kitchen needs early clarity on how long stock will last. If three dishes depend on the same base sauce, a small purchasing delay suddenly becomes a menu problem. Good supply chains are therefore also communication chains.

Bonzumo helps me here indirectly but usefully. Because sales, kitchen, and related operations work from one shared data basis, my team can follow the process where the issue actually arises instead of covering every gap with shouted updates. For production, the practical value is that orders can be visible by station and handled by service, kitchen, and bar in one coordinated flow. Give service, kitchen and bar a shared view of orders does not perform the purchasing decision for us, but it helps with the next operational question: how do we react cleanly when one item gets tight or one course has to be adjusted? The result is fewer misunderstandings, faster decisions, and fairer communication with both guests and staff.