A full dining room can hide a messy business. One outlet sells more, another gives more discounts, and a third looks quiet because it trades fewer hours. Restaurant POS efficiency starts with knowing which difference deserves attention. A useful review connects the order, the stock movement, the member benefit and the payment before anyone changes a menu or blames a team.
For Singapore cafés and restaurant groups, Rewardly CommerceOS, LoyaltyOS and PaymentOS provide different views of that journey. Use five checks below to turn those records into a short action list. They complement the multi-outlet operating guide; they are not a readiness score, a promise of profit or a substitute for accounting advice.
Start with a fair comparison
Write down the dates, outlet, register and sales channel before reading a total. Compare equivalent trading days and note closures, promotions and opening hours. A lunch-focused office outlet and an evening neighbourhood restaurant can have different menus and prices for good reasons. A larger revenue total alone does not identify the better operation or explain the cause of a change.
Choose one question for each report and keep the supporting export with your review notes. IRAS record-keeping guidance explains that companies need records and source documents that explain their transactions; bank statements alone are insufficient. A POS export is useful evidence within that wider record set, rather than a complete accounting file or an automatic compliance guarantee.
1. Separate order activity from the headline sales total
CommerceOS sales reports let a manager examine Sales Summary alongside item, category and modifier breakdowns. Check whether an apparent increase came from more orders, a different product mix or a change in discounts and charges. Keep each report’s definitions visible: Sales Summary Customers and Shift Report Diners count different things, so they should not be treated as interchangeable measures of guest traffic.
In an illustrative café review, afternoon drinks sell well but a lunch set attracts fewer orders. The sensible next step is to check availability, service hours and staff feedback before running a blanket discount. Sales by Item identifies what sold; it does not prove what guests wanted but could not buy. An unavailable item can disappear from a bestseller discussion precisely when it needs attention.
Where costs are configured, the Cost of Goods Sold report adds another check. Read its cost-coverage indicator and incomplete-recipe warnings before comparing margins. Sales without a recorded cost are excluded from profit and margin calculations; incomplete recipes can understate cost. These are gross-profit measures for the costed sales, not the restaurant’s net profit after rent, labour and other operating expenses.
2. Explain the stock movement before placing the next order
A stock balance becomes useful when the team can explain how it changed. Review opening stock, receipts, sales, transfers, returns and manual adjustments against a physical count. Rewardly’s stock reports provide product movements and separate ingredient records. An unexplained variance calls for checking the receipt, unit or recipe mapping, rather than simply increasing the purchase quantity and carrying the error forward.
Central-kitchen production needs its own handover: ingredients are consumed when the configured batch is made, products leave on transfer, and the receiving outlet records what arrived. The subsequent outlet sale should not consume those same ingredients again in that setup. See the restaurant stock-control guide. Low-stock thresholds are documented for ingredients; do not assume every product or modifier has the same alert.

3. Check whether member benefits are being used as intended
LoyaltyOS separates member growth, reward issuance and redemption. The Voucher Efficacy report compares issued and redeemed vouchers using selected dates, outlets and programmes. Pair that with membership and loyalty activity before deciding that a campaign worked. A voucher issued is an invitation, a voucher redeemed is a recorded use, and neither figure on its own proves an additional visit or additional profit.
For example, an outlet-specific return voucher may see little use because guests cannot visit during its eligible hours. Review the offer’s conditions and ask the service team what customers found confusing before making it richer. CCS price-transparency guidance reinforces clear, accurate prices and discount conditions. Keep the customer-facing promise aligned with the configured benefit and the staff explanation.
Known-member records have limits. Rewardly POS and online guest sales do not all appear in the loyalty Sales Transactions ledger; use Orders for those sales. Member Insight can highlight behavioural segments for review, but a segment is not a prediction or permission to message someone. A merchant still checks eligibility, consent and campaign settings; this guide does not promise automatic recovery of every inactive guest.
4. Match payment records to provider and bank evidence
PaymentOS reports support review by date, outlet, register and source. Use the Payment Report for tender composition and the Discount Report to distinguish configured programme discounts from manual discounts. The PayNow Payout Report shows applicable transactions and fees. These views help the person handling receivables investigate a difference without treating every reduction from a sales total as missing revenue.
A sale date, a payment confirmation and a bank payout can belong to different moments. Compare the relevant provider statement, fees, refunds and timing with the records you selected. A custom tender entered by a cashier is not independent confirmation that a transfer arrived. Keep unmatched items on an exception list with an owner, supporting reference and next check, rather than silently forcing the totals to agree.
Payment costs also deserve like-for-like review. Ask which card categories, fixed charges, channels and settlement terms your quotation covers; a headline percentage cannot answer that. The existing merchant discount rate guide explains the quotation questions, while the integrated payments guide covers the checkout and closing workflow. Confirm the proposed configuration and services for each outlet.
5. Use AI-assisted reporting to investigate, then verify
Rewardly’s Smart Report Builder lets a manager select a sales report or ask a natural-language question, such as “total sales last week by outlet”. Set the date, outlet and source filters, then inspect the chart, data table and written analysis together. Ask a narrower follow-up when a result suggests a useful question; retain the export and the assumptions behind the comparison.
There are important boundaries. Hourly Sales in Smart Report Builder covers today, even when another date range is selected. Its Operation, Analytic, Forecast and Audit tabs are documented as not yet live. AInstein support guidance and Smart Import are separate tools: guidance does not change your menu or issue vouchers. An AI explanation suggests something to investigate; it does not establish causation or authorise an operational change.
Finish with one owned action, not another dashboard
Bring the outlet lead, stock or kitchen lead and person handling payments into the relevant part of the review. Choose a small, reversible action: correct a receiving record, clarify a voucher condition, check a missing product cost, or investigate an unmatched payment. Record who owns it and when to review the outcome. Avoid changing prices, rewards and opening hours together if you want to understand what helped.
CommerceOS supplies the sales and operating context, LoyaltyOS makes member-benefit activity reviewable, and PaymentOS supports the payment-side check. Their value comes from a connected process with clear definitions and responsible people. For a new outlet, rehearse the same review using that outlet’s menu, hours and fulfilment model; copying a dashboard does not make two businesses operationally identical.
Book a Rewardly walkthrough with a sample trading week and one question your team struggles to answer. Ask to see the report filters, cost coverage, loyalty conditions, payment evidence and export in the proposed setup. The goal is a practical decision you can explain and verify, with the right modules, permissions, hardware and support confirmed before deployment.



