A restaurant stock count is useful when it helps your team decide what to buy, prepare and investigate before the next service. A number on a dashboard cannot tell you whether a missing tray was sold, spoiled or sent to another branch without the right records. For Singapore F&B operators, restaurant inventory management starts with a shared routine between purchasing, the kitchen and the outlet receiving the food.
The National Environment Agency’s food-waste guidance, updated in May 2026, prioritises preventing waste at source and provides industry guidebooks for minimisation and audits. That is established guidance, not a new announcement today. A practical application is to record why food leaves stock, so purchasing and preparation decisions can respond to evidence rather than a hurried estimate.
Choose the count that matches how you make and sell
Rewardly’s documented stock tools support two different models. Whole-item inventory counts sellable units, such as bottled drinks or packaged buns. Ingredients and recipes track the materials used to make an item, such as beans, milk and cups. CommerceOS supplies the selling workflow; StockOS supplies these stock records. Choose the appropriate model for each product before setting starting quantities. Having a recipe saved does not by itself switch ingredient deduction on.
Decide whether a product needs a shared count or a separate count at each outlet. A restaurant branch holding its own bottled drinks needs its own controlled quantity; otherwise changing the shared number can affect other branches. Check this setup before interpreting a sudden sold-out message as a supply problem. Keep ingredient units consistent between purchasing, recipes and counts. Counting a carton while the recipe uses individual packs creates a misleading comparison even when staff have counted carefully.
Investigate five common causes of a stock discrepancy
First, check units and recipe quantities: a wrong portion or pack conversion repeats its effect across many sales. Second, check missing or incomplete receipts: food on a shelf may not yet have been received into the correct outlet’s records. Compare the delivery with what arrived, rather than accepting the supplier’s ordered quantity as proof of delivery. These checks can explain a mismatch before anyone assumes the team has lost stock.
Third, record waste and non-sale usage. Spoilage, a preparation mistake or a staff tasting should not disappear into an unexplained adjustment. Fourth, check transfers: stock sent by a kitchen is different from stock received by a branch. A tray still travelling should not be treated as already available at the counter. Give someone responsibility for closing each handoff and documenting a shortage, return or damaged item.
Fifth, review voids and returns. Rewardly’s ingredient settings let you choose whether a void returns ingredients, records wastage or leaves the deduction unchanged. A cancelled order does not necessarily mean prepared food can be put back into usable stock. Rehearse the choice with your team and match it to what physically happened. A count adjustment corrects a balance; investigating the cause is what helps avoid the same surprise next week.
Keep central-kitchen production separate from outlet sales
When a central kitchen makes finished products, Rewardly’s documented flow is to make stock at the kitchen, send it and receive it at the outlet. The batch deducts ingredients at the kitchen; the outlet then sells its finished stock without deducting those ingredients again. This requires the relevant stock and recipe setup and a recent POS app. The central-kitchen guide explains the conditions. The wider multi-outlet POS guide covers menus, fulfilment and group operations.
A product transfer leaves the sending outlet when sent and raises receiving stock when receipt is recorded. If less arrives, record the actual amount and whether the remainder is still travelling, returned or lost. Both ends need their own tracked product count. The transfer workflow is for products; ingredients use separate outward and inward transactions. These distinctions help the receiving team resolve a short delivery without quietly inflating what is available to sell.
Read stock, rewards and payments as different evidence
Consider a fictional bakery that prepares a batch centrally and distributes it to two shops. One shop sells through its counter and online storefront; the other uses part of its stock for an eligible member offer. Before planning another batch, the manager checks product movements, the physical count and the recorded reason for any adjustment. This is an illustrative operating scenario, not a merchant result or a promise that the software measures every unrecorded loss.
LoyaltyOS helps define the member benefit, including voucher conditions and participating outlets. Before advertising a food reward, confirm eligible products, available stock, outlet restrictions and how staff will redeem it. Test the actual checkout journey. A reward still consumes something with a cost, and membership activity alone does not establish whether the offer is affordable. The digital voucher overview helps frame the customer promise; stock and cost review should inform its scope.
PaymentOS reports show money taken by payment type, while the Discount Report separates programme and manual discounts. Filter by outlet, source and date to review the relevant trading period. A payment total is not a stock count, and a discount is not proof of food waste. Use payment and discount exports alongside stock records and your own accounting costs. This keeps a busy sales day from masking a receiving problem or an offer that needs a closer cost review.
Build a repeatable weekly stock-review routine
Start with a small set of important ingredients and finished products. Choose a consistent cut-off, record receipts and transfers, count the physical stock and compare it with the same outlet and period in the system. Review the movements before entering a justified adjustment. Keep the reason and responsible staff member clear. Rewardly’s Stock Movement Report summarises product movements over a period, while ingredient history is reviewed in its own ledger; do not expect the product report to explain every ingredient variance.
Use the current-stock views for products and the configured low-stock threshold for ingredients. The ingredient threshold shows a badge; it does not send a notification, and products do not have an equivalent low-stock alert. Smart Report Builder can answer supported sales questions such as sales by outlet, with charts and commentary. Inspect its rows and filters. It is a separate sales tool, not an automatic stock-loss investigation, demand forecast or purchasing agent.
Make the next service easier to plan
The Singapore Department of Statistics release published on 5 October 2026 reported a 1.6% year-on-year fall in F&B services sales in August 2026. That is older sector context, not a measure of today’s demand or your restaurant’s performance. It reinforces a sensible management question: what can your own records explain before the next purchasing or promotion decision?
Use CommerceOS with the appropriate stock model to record the sale and its consumption, LoyaltyOS to deliver a clear member benefit, and PaymentOS to review receipts and discounts. Begin with one realistic service and one complete kitchen-to-counter handoff. Book a Rewardly demo and bring a sample recipe, transfer and stock discrepancy so your team can test the workflow that matters to your business.
