Hotel inventory software: storerooms, recipes and purchasing in one record

Hotel inventory management software keeps one record of every item a hotel buys, holds and uses: a single item list, unit conversions from case to gram, main and sub stores, purchase approvals, recipe deduction at the point of sale, and a monthly value that reconciles to accounting. Its quality is decided by the item list, not the screens.

The count sheet says 42 kilos of tomatoes in the main store. The kitchen's recipe book points at a second tomato code, the supplier's invoice uses a third name, and the month-end figure is the sum of all three. Nothing in the software is broken; the item list was. This guide covers the parts of hotel stock control that decide whether the software works: the item list, unit conversions, stores, approvals, the point-of-sale link, the handover to accounting and the opening count. Each section gives you a rule you can apply before you configure or buy anything.

Why does hotel stock software fail at the item list?#

It fails there because the item list is the record every other number hangs from, and most lists are built by importing old spreadsheets and supplier catalogues, duplicates and all.

One physical item must have one code. Three spellings of the same tomato, the supplier's, the kitchen's and the accountant's, create three balances that are each wrong and none of which can be trusted at month end. Duplicates are not a data-entry annoyance. A recipe points at one of the three codes, purchasing history splits across two, so price comparison across months becomes meaningless, and a counter walking the store counts the same sack twice under two names.

Fix the naming rule before the import: category, generic name, specification, pack size. The rule belongs to one named person, usually the cost controller, who approves every new code. Decide granularity by asking what the recipe needs: if no recipe distinguishes two grades of olive oil, the storeroom should not either, because every extra code is a code someone must count and value.

Import the supplier catalogue as a draft list to be merged, never as the master. Suppliers name items for their own convenience, not for your kitchen. Merging is not deleting: choose the surviving code, move the purchase and issue history onto it, and retire the others so old documents still resolve. Finally, check the list against the physical store, not against the old system. Walk the shelves and tick each code against a real package. For a wider view of where stock control sits among the other systems, see what hotel software covers, department by department.

How do you handle buying by the case, issuing by the piece and cooking by the gram?#

Keep one base unit per item and store every other unit as a fixed conversion factor on that item, so the software converts once and nobody converts by hand at the storeroom door.

The base unit is usually the smallest unit the kitchen measures in: gram, millilitre, piece. Every balance, every count and every valuation is kept in that unit. The purchase unit (a case of 12, a 5 kg bag), the issue unit (piece, kilogram) and the recipe unit (gram) all point back to the base unit through a factor. Three units, one balance.

The factor must be exact and fixed. A case that sometimes holds 12 and sometimes 10 destroys the count, so the pack size is written on the purchase order line and checked at receiving, not assumed from the last delivery. Yield is not a conversion: a whole fish bought by the kilogram yields fillets at some percentage, and that yield belongs in a separate field on the item and in the recipe, never baked into the case-to-piece factor.

Convert at issue, not at count. Counters count what they see in the base unit; the software does the rest, with enough decimals that rounding never creates a phantom variance. Watch the unit change, too, because that is where suppliers catch hotels: a bag quietly moves from 5 kg to 4.5 kg at the same price per case, and the price per gram rises without a single invoice looking different.

Main store and sub stores: which locations should exist?#

Create a store for every place that holds stock behind a lock and has one person accountable for it, and no more.

The main store receives deliveries and holds the bulk. Sub stores, the kitchen, each bar, housekeeping and technical service, hold working stock for the shift or the week. Every movement from main store to sub store is a transfer document with a name and a time. That document is what makes a bar count mean something, because the bar's expected stock is what it received minus what it sold. For the beverage side of this, beverage cost control in hotel bars covers measures, par stock and the monthly count in detail.

Par stock per sub store sets the transfer quantity. Without a par level the bar hoards, the main store runs short, and two departments buy the same bottle twice. Housekeeping and technical stores follow identical rules with different items: linen, amenities, lamps, chemicals. Chemicals also need their own separation and labelling rule, which is a safety matter, not a software one.

Direct purchases, fresh bread or market produce that goes straight to the kitchen, must be allowed for named categories only, and recorded as a direct issue so the cost still lands on the outlet that used it. Do not create a store per floor, per shift or per manager. Each extra store is another count, another transfer and another place for a balance to drift.

How do you map request, approval, order and receiving onto screens?#

Map each step to one screen and one person, and keep the person who orders away from the person who receives and the person who approves.

The chain is requisition, approval, purchase order, receiving, invoice match, payment. Each step leaves a record with a name and a time, which is what turns a written procedure into something you can audit months later. Authority limits are set by amount and by category, so a kitchen requisition for produce and a technical requisition for a spare part do not follow the same route.

Receiving must capture the short delivery and the price difference at the door. A crate that arrives with 5.5 kg instead of 6 kg is a receiving note today and an unexplained variance at month end. The three-way match, order against receiving note against supplier invoice, is the control that catches both a supplier billing for goods that never arrived and a receiver signing for them.

What the software cannot do is judge quality. Temperature, freshness, damage and substitution stay with a person at the door, and the receiving screen only records that person's decision. Write the procedure down before configuring it: software configured around an unwritten procedure simply makes the confusion faster. The paper procedure itself is described in hotel purchasing and receiving: a procedure from order to storeroom.

When should a POS sale reduce stock?#

A sale should reduce stock only when the item sold points at a recipe whose ingredients are already in the item list, and only for the items the kitchen actually portions.

The chain is short and strict: the point-of-sale button points at a recipe, the recipe points at items and quantities, the items carry the base unit. Break any link and the deduction silently stops. Bottled and sealed goods, a beer, a sealed water, deduct by the piece with no recipe. Portioned food and poured drinks need a recipe, or they will never deduct at all. The recipe method itself is covered in standard recipes and portion cost.

Modifiers, complimentary items, voids and staff meals are the four holes in every deduction. Decide the rule for each before go-live: does a comp deduct, does a void before or after the kitchen fires, does a staff meal go on a staff account. Open items, a glass of wine, a scoop of ice cream, need a defined portion, because without one the software has nothing to multiply.

The deduction gives theoretical consumption. The monthly count gives actual consumption. The gap between them is waste, over-portioning, spoilage, theft or a wrong recipe, and the software's job is to make the gap visible, not to explain it. Expect the link to be explainable in month one, not exact. An exact figure in the first month usually means someone is adjusting the numbers by hand.

From stock to accounting: what passes and who checks it?#

What passes is value, not quantity: the month's issues valued at a stated cost, plus the closing stock value, and the accountant checks both against the ledger.

Choose the valuation method once, moving average or first-in-first-out, and state it. Changing it mid-year makes every month-on-month comparison meaningless, even when both months were correct. Cost of sales per outlet is opening stock plus purchases minus closing stock. Run it per outlet, not for the hotel as a whole, or a profitable restaurant can hide an expensive bar.

Transfers between outlets and free issues, comps and staff meals, must be valued too. Unvalued transfers make one outlet look profitable and the other look wasteful. The accountant owns the fiscal document for the delivery, the tax treatment and which e-document rules apply to the supplier and to the hotel. The stock system records that goods arrived; it does not decide the tax. Confirm your own case with your accountant.

Reconcile monthly: stock ledger against general ledger, with any difference written down and explained, not adjusted away. Split the signatures. The storekeeper counts, the cost controller values, the accountant reconciles, the food and beverage manager explains the variance. One person doing all four is a report nobody reads.

What does the opening count and the first monthly reconciliation require?#

A physical count on a closed day, taken against a frozen item list, valued and posted as the starting balance, with the first month treated as a calibration rather than a verdict.

Freeze the item list and every conversion factor before counting. A count taken against a list that is still changing cannot be reconciled to anything. Count in the base unit, with two people, on blind sheets that do not print the expected quantity. A counter who can see the system figure will confirm it.

Value the opening count and post it as the starting balance on day one. Everything afterwards is movement from that number. Expect the first month's variance to be large and mostly explainable by the list, the units and the recipes, not by the staff. Publishing it as a theft report destroys the cooperation you need in month two.

Set the rhythm: a full count monthly, spot counts weekly on high-value items, and an immediate count whenever a store's accountable person changes. Write the rules you chose on one page: valuation method, comps, direct purchases, par levels, approval limits. That page, not the software, is the system.

What to do next#

Before you compare a single product, take your current item list and count how many codes describe the same physical item. That number tells you more about whether stock software will work in your hotel than any feature list. The list fixes the units, the units fix the stores, the stores fix the workflow, the workflow feeds the recipes and the point of sale, and all of it ends in one value the accountant can reconcile. Start with the list, then the opening count, then the software.