A guest scans the code, chooses dinner and expects the restaurant to know what happens next. The useful measure of QR ordering is whether that journey feels clear: the right table receives the right dishes, staff can answer a question, and payment closes the correct bill. For Singapore restaurants and cafés, convenience should support the welcome customers came for.

This refreshed guide connects Rewardly CommerceOS table service, LoyaltyOS member benefits and PaymentOS payment review. Imagine a neighbourhood restaurant serving a couple who prefer different ways to order: one uses a phone while the other asks a server for help. This is an illustrative planning scenario, not a merchant case study. The aim is a workable service routine, with each enabled feature demonstrated before launch.

Choose how your restaurant serves

Begin with a service decision: do guests pay before preparation, or keep a table bill open until the meal ends? A counter café and a full-service restaurant can need different journeys, even if both display a QR code. Explain the chosen process at the table. Give staff a short answer for guests who ask whether their order has been received or payment is still due.

Rewardly’s online-ordering documentation describes phone-browser ordering through an outlet link or QR code, without a separate app download. Orders reach Order Management and configured kitchen screens. Confirm the enabled service mode, payment steps and supported member journey for your outlet. A digital menu that only displays dishes is different from a journey that submits an order.

Make the table identity dependable

Before printing table cards, check the dining-room plan. Rewardly groups tables into sections and links each table to its ordering identity. In full-service mode, the table can keep an open bill while additional rounds are prepared. Staff need a clear way to recognise the table and check its current order, especially when guests move seats or ask about an earlier round.

The table documentation distinguishes permanent table codes from codes generated for each sitting. Confirm which approach your outlet uses before laminating signs. A per-sitting code is printed from the POS and expires; a permanent code can support reusable cards. Turning off the static-code setting later does not retire cards already printed. Plan signage replacement deliberately when an old printed link should stop being used.

Keep a person available to help

Make it easy for a guest to ask for assistance, including someone without a charged phone or comfortable mobile access. Staff can take a table order in the POS, while guests using the supported QR journey place their own choices. Agree who checks questions about portions, ingredients or changes. A screen should not become a reason for the team to overlook a table.

Rewardly’s full-service workflow distinguishes items waiting for confirmation from rounds already sent to preparation. Staff can add another round to the table and send it to the kitchen. Rehearse one assisted order alongside one phone order so the team can recognise both. Do not assume two guests share a basket, or that every request can be changed after preparation starts; demonstrate those situations explicitly.

Illustration of restaurant colleagues checking table orders beside prepared dishes
AI-generated editorial illustration. People and screens are fictional.

Make membership useful without slowing dinner

Choose a benefit that staff can explain briefly. An illustrative restaurant might let an eligible member use a configured voucher against a qualifying meal. LoyaltyOS provides membership tiers and benefit rules, but a tier name alone does not establish what a customer earns. The linked programme and its conditions determine the benefit. Confirm member identification and earning or redemption in the exact ordering channel.

For table orders, Rewardly documents confirmation before applying a voucher or discount in the POS. Test an eligible basket and an excluded item, then check the remaining amount due. Keep expiry and other conditions visible before customers commit. The voucher redemption guide covers that decision in more detail. Avoid advertising that every QR order automatically receives every reward.

Close the correct bill confidently

At the end of the meal, staff should be able to find the open table order and explain what remains payable. Rewardly’s full-service POS supports settling the table and a split-bill workflow. Confirm the split method, supported payment options and treatment of benefits in your demonstration. Moving dishes or splitting a bill should not rely on staff guessing how rewards will be allocated.

PaymentOS reports group payments by method and let managers filter by outlet, date and order source, including online. Discount reports provide a separate view of programme and manual discounts. Use those records with the order details when reviewing a discrepancy. A report is useful evidence for investigation; it does not automatically resolve a disputed payment or prove that a campaign generated extra profit.

Protect the promise on the table card

As an operating habit, check that displayed cards open the intended restaurant and table journey, and replace damaged or altered signage. Tell staff how to respond when a guest is unsure about a link. ScamShield’s guidance, updated on 18 May 2026, provides ways to check suspicious links and seek assistance. This is established safety context, not a new warning about Rewardly or your restaurant.

The Food Services Industry Digital Plan announcement of 16 July 2025 includes staff skills and cybersecurity alongside digital solutions. Treat that older industry context as a reminder to brief the whole team. It does not establish funding eligibility for a Rewardly package, or show that a restaurant can operate without service staff.

Improve one service routine at a time

Start with a small seating area and rehearse a second order, a changed table, an ineligible benefit and a payment question. Record who handles each exception. Review order questions, corrections and staff feedback over comparable shifts before expanding. Those observations help identify friction; they are not proof of a revenue increase caused by QR ordering. Keep assistance available throughout the pilot.

Book a Rewardly walkthrough using your menu and a typical table visit. Ask to follow one order from phone or server through kitchen preparation, member eligibility and final payment. Use the QR-ordering overview for product scope and the lunch-rush checklist for a wider self-service pilot. Agree the service promise first, then configure CommerceOS, LoyaltyOS and PaymentOS around the routine your team can explain.