Stock That Leaves Without a Sale
Staff meals, the manager's table, a complimentary bottle, guest amenities. Every hotel moves stock that is never sold, and every hotel that does not account for it thinks its food cost is worse than it is. The movement is well handled here. The one dimension you will want — a department — is not on it.
A hotel kitchen issues food to four destinations. Guests who pay, which is a sale. Staff who eat, which is a payroll cost. The manager's table and complimentary covers, which are marketing. And the bin, which is waste. Only the first one is revenue, all four consume stock, and a food-cost percentage that treats the last three as if they were the first will read three or four points worse than reality — every month, permanently, and nobody will be able to explain why.
This is one of the easier problems in hospitality to fix and one of the most commonly left unfixed, because fixing it requires deciding in advance where each kind of consumption should land.
The instrument: a checkout adjustment
Stock leaves this system by exactly two paths. It is sold, or it is checked out on an adjustment. There is no third route, which is a genuine strength — every unit that leaves a store leaves through a door that records something.
A checkout adjustment is more substantial than a quantity change. It carries a reference number, a warehouse and location, an item and quantity, a reason, an optional file attachment, a status that moves through submission and approval to being applied, and the users who submitted, approved and applied it. It also carries a debit and a credit account, so an issue posts to the general ledger against accounts you choose rather than disappearing into a generic bucket.
That last point is what makes accurate food cost possible. A staff-meal issue can debit a staff-welfare expense account rather than cost of sales. A complimentary bottle can debit marketing. Waste can debit a wastage account that somebody has to look at. Do that consistently and your cost of sales starts describing what guests actually ate.
The dimension that is missing
Here is where a hotel controller will stop and ask a question this system cannot answer as asked. A hotel is a set of departments — rooms, food and beverage, bar, conferencing, laundry, spa — and hotel accounting is departmental. The uniform system of accounts the industry runs on exists to produce a contribution figure per department.
There is no department on an adjustment, and no department on an expense. An adjustment carries a project. An expense carries a category, a vendor, an expense account and a project. Neither carries a department, so the natural question — what did food and beverage consume this month — has no natural field to answer it.
Departments do exist as records in the system, and they are used in HR, on assets, on purchase orders, on budgets, on tickets and on projects. They are simply not on the two documents that record spending. That asymmetry is the thing to design around, and it is better to know about it while you are setting up than to discover it when you are asked for a departmental P&L.
What carries a department
- Employees — so payroll cost is departmental.
- Budgets — so you can budget by department.
- Purchase orders — so a commitment is departmental.
- Assets — so equipment is attributable.
- Projects and tickets — so work is attributable.
What does not
- Expenses — category, vendor, account and project only.
- Stock adjustments — project only, no department.
- POS sales — a counter, which is a proxy at best.
- Which means actual departmental spend is not directly reportable.
- And a departmental contribution statement has to be assembled from a convention you impose yourself.
The workaround, and how to choose it
Two conventions work. Pick one, apply it everywhere, and write it down — the failure mode is a hotel that uses both, half-heartedly, and can reconcile neither.
You want departmental cost across both stock and expenses
Use a project per department
Create a standing project for each department — "F&B — operations", "Rooms — operations" — and code every adjustment and every expense to it. This is the only field that appears on both documents, which makes it the only route to a combined picture. The cost is that your project list now mixes real projects with cost centres, so name them so the distinction is obvious at a glance.
You want physical accountability for stock, not just cost
Use a warehouse location per consuming area
Model the main kitchen, the bar store, the pool bar and housekeeping as locations, transfer stock to them, and let each area hold what it holds. You get per-area stock and per-area counts, which is a real operational gain. It does not by itself give you departmental cost, so pair it with the project convention rather than choosing between them.
You only need accurate food cost, not full departmental reporting
Use the expense accounts on the adjustment
The simplest option and often enough. Staff meals debit staff welfare, complimentary covers debit marketing, waste debits wastage. Cost of sales then reflects guests only, which is the number the kitchen is judged on. No project convention needed.
You want a departmental P&L in the system
Accept that you are assembling it
Revenue by outlet comes from per-counter sales reporting, payroll cost is departmental through employees, and stock and expenses come through the project convention. Three sources, one spreadsheet, monthly. It is honest work rather than a report you open, and pretending otherwise during setup is how a controller ends up disappointed in month three.
What this does to your food cost
Worth showing with numbers, because the size of the distortion is usually a surprise.
Six points of food cost, which is the difference between a kitchen that looks out of control and one that is running normally. None of it required better buying — only issuing to the right account.
The cheapest six points of food cost you will ever find are the ones you were never spending. They were sitting in cost of sales because nobody told the issue where to go.
Making it happen at the store door
The accounting is the easy half. The hard half is that a storeman at six in the morning issuing bread to the staff canteen has to make a coding decision, and will not, unless the decision has already been made for him.
-
Write the destinations down before you start, and keep the list short
Guest F&B, staff meals, complimentary, waste, housekeeping amenities, maintenance consumables. Six is manageable. Fifteen becomes a guessing game and everything lands in the first one on the list.
-
Fix the account for each destination once
Each destination gets one debit account, decided by the accountant, not by whoever is issuing. Print it and stick it inside the store door.
-
Make the reason field a real sentence
The reason is captured on every adjustment and it is what makes a month-end review possible. "Staff lunch, 38 covers" is worth ten times "issue".
-
Issue daily, not weekly
A staff-meal issue raised once a week is a guess about the week. Raised daily against a headcount, it is a number. Daily also means the store balance is right when somebody counts it.
-
Use the approval step
An issue is submitted, then approved, then applied — and nothing moves until it is applied. For internal consumption that gap is useful: a head chef approving the staff-meal issue is the person best placed to notice that 38 covers became 61.
-
Review the non-guest issues monthly, by destination
Staff meals should be roughly headcount times days times a rate. Complimentary should be roughly what the general manager remembers authorising. When either is not, that is the finding.
Two related absences worth naming
The first: there is no recipe or bill of materials. Issuing three kilos of beef and receiving forty portions of stew is not something the system models — the beef leaves as beef. Theoretical food cost, portion yield and the gap between what a menu should have consumed and what the store actually issued are therefore not computable here. This affects the whole F&B story, and it is described in more detail in the cost-control article.
The second: there is no cover or meal count entity. The 38 staff covers in the example above is a number you know from a canteen register, not from the system. That matters because the control on staff meals is cost per cover, and the denominator lives outside. A custom field on the adjustment is the practical place to record it, so at least the number sits next to the issue it explains.
The one thing to set up this week
If you do nothing else from this article: create the expense accounts for staff meals, complimentary and wastage, and tell your storeman which one each kind of issue uses. That is an hour of work and it is the difference between a food-cost percentage you can act on and one you argue about.
What we do and do not do
What AWRA OpsHub does today
- Every unit that leaves a store leaves through a recorded door — sold, or checked out on an adjustment. There is no untracked exit.
- Checkout adjustments with a reference number, warehouse, location, item, quantity, reason and file attachment.
- Debit and credit accounts on the adjustment, so consumption posts where you decide rather than into a generic bucket.
- A submit, approve, apply lifecycle, with the acting user recorded at each step and no stock movement until it is applied.
- Project attribution on both adjustments and expenses — the one field that appears on both.
- Locations within a warehouse, so kitchen, bar store and housekeeping can each hold and be counted separately.
- Batch-aware issuing that takes the earliest expiry first, so an issue does not quietly leave old stock behind.
What it does not do
- No department on an expense or on a stock adjustment. Departments exist and are used on employees, budgets, purchase orders, assets, projects and tickets — but not on the two documents that record spending.
- No departmental profit and loss. Assembling one means combining per-counter revenue, departmental payroll and a project convention for stock and expenses, in a spreadsheet.
- Adjustment types are check-in and check-out only. There is no "issue to department" or "transfer to consumption" type — the meaning lives in the reason and the accounts.
- No recipe or bill of materials, so theoretical food cost, portion yield and the gap between menu and store are not computable.
- No cover or meal count, so cost per cover needs its denominator recorded by hand, ideally as a custom field on the issue.
- No cost dimension below a project — nothing lets you post a cost to a physical sub-location such as a floor or a specific outlet.
The department gap is the one to plan around, and the plan is a naming convention. A standing project per department, applied to every adjustment and every expense without exception, gets you most of the way; applied inconsistently it gets you nothing at all, because a partial convention is indistinguishable from no convention when you come to report on it.
Related reading
- F&B cost control: recipe cards, portions and menu engineering — the four habits, and the missing recipe layer in more detail.
- Housekeeping stock: linen, amenities and the par level nobody sets — amenities as a cost per occupied room.
- The invoice you raise every month by hand — the revenue side of the same departmental picture.
- Bar stock control: the tightest ship in the house — where internal consumption does the most damage per shilling.
See stock issues, approvals and account coding
Checkout adjustments with reasons, attachments and an approval lifecycle, posting to the accounts you choose, with locations and batch-aware issuing underneath.
Explore inventory managementFrequently asked questions
How do we take stock out for staff meals without it counting as a sale?
Issue it as a checkout adjustment. The adjustment carries a reason, a warehouse and location, an approval lifecycle and — the important part — its own debit and credit accounts, so a staff-meal issue can debit a staff-welfare expense account rather than cost of sales. That single choice is what stops your food-cost percentage absorbing costs that belong to payroll.
Can we see what the food and beverage department consumed this month?
Not directly. There is no department field on a stock adjustment or on an expense, even though departments exist and are used on employees, budgets, purchase orders, assets, projects and tickets. The workaround is a standing project per department coded onto every adjustment and every expense, because project is the one field both documents share. It has to be applied without exception — a partial convention reports no better than none.
Can the system produce a departmental profit and loss for a hotel?
Not as a report you open. You would assemble it from three sources: revenue by outlet from per-counter sales reporting, payroll cost by department through employee records, and stock and expenses through the project convention above. That is a monthly spreadsheet, and it is worth being clear about during setup rather than discovering it when the first departmental pack is due.
How much difference does correct attribution actually make to food cost?
Commonly five or six points. On a hotel issuing 1.84m of food against 4.2m of F&B revenue, staff meals, complimentary covers, recorded waste and housekeeping amenities can easily account for 250,000 of that — moving the food-cost figure from 43.8% to 37.8% without a single change to buying. The difference is entirely in where the issue was coded.
Can we calculate theoretical food cost against what we actually issued?
No. There is no recipe or bill of materials, so three kilos of beef leaves the store as three kilos of beef and never becomes forty portions of stew in the system's view. Theoretical cost, portion yield and the variance between what the menu should have consumed and what the store issued are not computable here. If that gap is the centre of your cost control, plan on maintaining recipes outside the system.
Is there an approval step before stock is issued internally?
Yes. An adjustment is submitted, then approved, then applied, with the acting user recorded at each stage, and no stock moves until it is applied. For internal consumption that gap is genuinely useful — the head chef approving a staff-meal issue is the person most likely to notice that 38 covers has quietly become 61.
Where do we record how many staff meals were served?
In a custom field on the adjustment, in practice. There is no cover or meal-count entity, so the denominator for cost per cover lives outside the system — usually a canteen register. Putting it on the issue as a custom field at least keeps the count next to the cost it explains, which is what makes the monthly review possible.
