Hotel & Restaurant Inventory Management in Kenya (2026)
Hospitality sells perishables through many hands at thin margins — the 2026 guide to hotel and restaurant inventory in Kenya: stores, kitchens, bars, and the daily counts that decide whether the month makes money.
A hotel or restaurant runs the hardest inventory problem in ordinary business: perishable stock, consumed in un-weighable portions, handled by many people, sold at margins that a few careless percentage points erase. A hardware shop that loses 3% of stock has a bad quarter; a restaurant whose food cost drifts 3 points often has no profit at all. That is why hospitality inventory is not a back-office chore — it is the P&L, counted daily.
The flow: store → kitchen → plate
Everything hinges on one structural idea: the main store and the operating outlets (kitchen, bar, housekeeping) are separate locations, and stock moves between them only as recorded issues.
- Receiving: deliveries counted and weighed against orders — fresh produce especially, where invoiced weight and delivered weight part ways easily. Receiving against POs is the first gate.
- The main store: locked, one storekeeper accountable, everything in and out on record — the same no-open-doors rule factories live by.
- Issues to outlets: the kitchen requisitions for the day's expected covers; the bar draws against its par; housekeeping draws amenities — each issue recorded to its outlet.
- Outlet stock: what each outlet holds is its responsibility until sold, used, or returned — which is what makes outlet-level variance computable.
Food cost: the number the kitchen answers to
Food cost percentage — cost of food consumed ÷ food revenue — is hospitality's master metric. The system version beats the accountant's version because it is available weekly and decomposable: opening stock + purchases + issues − closing stock, per outlet, against the revenue the POS recorded. When the percentage drifts, recipe costing and portion discipline tell you whether the problem is the menu price, the portion, the waste bin, or the back door.
| Signal | Likely cause | First check |
|---|---|---|
| Food cost up, covers flat | Portions drifting, waste unrecorded, or leakage | Spot-weigh five plated dishes against recipe cards |
| Bar variance while food behaves | The classic — pours, spillage "policy", own bottles | Run the bar reconciliation nightly for a week |
| Store issues up, outlet sales flat | Outlets over-drawing and stockpiling (or worse) | Outlet closing counts vs their issues |
| Purchases up, issues flat | Store receiving generously or stock aging in the cold room | Receiving records vs supplier invoices; expiry walk |
Daily for the dangerous, weekly for the rest
Count the high-risk items daily — meats, bar stock, seafood, cooking oil — and the full store weekly. A ten-minute daily count of twenty dangerous items catches more leakage than a monthly count of everything, because variance found today has a one-day list of suspects.
POS integration: sales must consume stock
When the POS sells a chicken burger, the system should consume the recipe — bun, patty weight, cheese slice, garnish — from kitchen stock. That link (menu item → recipe → ingredients) is what turns "we sold well but made nothing" from a mystery into a report. It also feeds purchasing: consumption by ingredient, by day of week, is the ordering forecast fresh-produce procurement needs.
Beyond F&B
- Housekeeping stores: linen par levels per floor, amenities issued by occupancy, chemicals dosed and tracked — the quiet budget nobody audits until it doubles.
- Maintenance stores: spares and tools with custody — the generator's fuel follows the same arithmetic as any fleet.
- Assets: kitchen equipment, furniture, TVs — on a register with custodians and service schedules, verified on a rhythm.
The whole discipline — stores, recipes, bars, purchasing, and the daily counts — is what AWRA for hospitality runs as one system, with eTIMS-compliant billing on the front end.
Find your real food cost
One store, one kitchen, one bar, one week — issues, recipes, counts, and the variance report that pays for itself.
See AWRA for hospitalityFrequently asked questions
What food cost percentage should a Kenyan restaurant target?
Casual dining typically targets 28–35%; hotels with breakfast-inclusive rates and banqueting run blended numbers that need per-outlet decomposition to mean anything. The governance point is less the absolute target than the weekly trend and the explained variance — a stable 33% beats a mysterious 29%.
Do we really need to separate the store from the kitchen?
It is the single highest-leverage change in hospitality stock control. When the kitchen draws freely from the store, food cost is one undifferentiated number and accountability is nobody's. The requisition line between them is what makes kitchen variance and store variance separately visible — and separately ownable.
How do recipe cards work for a menu that changes daily?
Cost the stable core exactly (portions of protein, standard garnishes, bar recipes) and use batch costing for daily specials — the day's special is a small production run with issued ingredients and counted portions. Precision where the volume is, pragmatism where it isn't.
Can one system run multiple outlets — restaurant, bar, pool bar, banqueting?
Yes, and it should: each outlet is a location with its own issues, sales, and variance, rolling up to one food-and-beverage picture. Banqueting adds event-based issuing (provision for 200 covers, return what came back) — which is just the site-materials pattern with tablecloths.
