A new employee does the work, but decisions still wait for the owner

In one restaurant, the owner can quickly check why more cheese was ordered or why the invoice price increased. They know the supplier agreements and who completed each task. When a record is missing, they recall the detail.

Across several locations, similar questions arrive at the same time. One manager needs approval for a substitute. Another sent a list without checking current stock. Head office has an invoice but cannot tell whether the delivery shortage was reported. An inventory variance could come from a transfer, waste or a wrong recipe.

Another employee can send orders, collect delivery notes and enter documents. They still cannot close a case if the owner must explain every price change, substitute or shortage.

The owner remembers another exception whenever a supplier, product or accounting method changes. A handover reveals the problem. The new employee knows the tasks but not the rules needed to finish them.

Before an order is sent, someone must calculate the quantity

“Send the order” describes only the final action. First, someone converts sales into ingredients, subtracts current stock, leaves the agreed buffer and rounds the result to supplier packs. A new employee can copy a list into an email. Without those rules, they cannot tell whether the list is correct.

Checking an invoice requires the purchase order, actual goods receipt and delivery note. Only then can the employee confirm the delivered quantity, agreed price and any reported shortage.

A report may show food cost two percentage points above target. The employee still has to check purchase prices, portions and unrecorded waste. When only the owner knows where to look, the report produces another question for the owner.

TaskSend the supplier order
Missing ruleWhere did the quantity come from? Which supplier? Which substitute?
ResultThe question returns to the owner

Knowing the software does not replace company rules

An employee can know the POS, inventory software and ERP, yet still need knowledge that is not on any screen.

The employee learns where to find the stock report. Later, they discover that the unit and date must change before export. The correct location is hidden behind an internal abbreviation. The same ingredient has one name in the POS and another on the invoice. The result must be matched with a spreadsheet, then checked against an old message.

Another document is filed correctly but does not show whether the supplier was told about a shortage. The new employee sees the difference. They do not know whether to wait for a credit note, change stock or assign the delivery elsewhere.

After a month, they may navigate every screen and still ask about each less common case. They know where to click, but not the rules the company uses to accept a result.

When someone finally learns the process, the company may depend on them

After several recruitment rounds and repeated onboarding, one person finally remembers the whole setup. They know which report to open, how to recognise products under different names and whom to call about each supplier.

Most questions stop reaching the owner while that person is available. The rules remain undocumented, so the company replaces dependence on the owner with dependence on one employee.

The problem returns during a long holiday, illness or resignation. Another recruitment starts. The next person learns the same abbreviations, exceptions and clicks. The company pays for hiring and onboarding while incorrect orders and late documents become more likely.

One person’s holiday or resignation should not force the company to reconstruct its supplier, reporting and invoice discrepancy process from the beginning.

The rules needed before an order is sent

One recurring supplier order reveals at least seven rules an employee needs:

  1. What triggers the order: sales, current stock, the delivery day or a manager’s decision?
  2. Which recipe, unit and safety stock determine the quantity?
  3. Which product and pack size come from each supplier?
  4. Which substitutes are accepted?
  5. Who confirms what actually arrived?
  6. Which discrepancies can the restaurant resolve, and which go to head office or the owner?
  7. Where are the decision, document and resolution recorded?

For a standard order, the employee needs the final quantity and supplier. When a discrepancy appears, they need the person who can approve it and a place to record the decision. The same logic applies to receiving and invoice checks.

The system calculates and compares. A person decides when no rule exists

A new supplier, unknown substitute or large discrepancy still needs a person. The system should send that case to the responsible person with the order, document and value of the difference.

Daily requirement calculations and order entry do not need a new decision. The system converts sales into ingredients, accounts for supplier packs and prepares the order. After delivery, it matches the goods receipt, delivery note and invoice, then identifies any price or quantity difference.

After receiving, the employee sees the exact issue, such as two missing packs. If the response is already defined, they close it. The owner receives only a case the company has not covered before.

We document the rules before the system goes live

Before configuration, we establish where the order quantity comes from and who confirms a delivery. We also check where delivery notes and invoices go, and who approves a price, quantity or substitute.

We then complete missing recipes and units. Supplier products, pack sizes and accepted substitutes are mapped. Sales, stock, orders and documents are connected so a new employee does not assemble an answer from several exports and conversations.

For 2-4 weeks, TasteMetrics prepares orders without sending them. The team checks quantities, prices and delivery dates while we correct the data and rules. Automatic sending starts after verification. A price change, unavailable product or delivery discrepancy creates a task for the responsible person.

Documenting ordering, receiving and discrepancy rules is part of TasteMetrics implementation. For the first conversation, one task that depends on a single person is enough.