HuaRenCa
Back to Forum
Community

How to Set Up Restaurant POS Coupons: Discount Rules, Staff Permissions, and Stacking Limits

BOXER
BOXER

6 days ago

Running a restaurant in the U.S., coupons and discounts are one of the most direct tools for driving repeat customers. But the most common struggle for Chinese-owned businesses isn't "not knowing how to set up discounts"—it's that after setting them up, profits quietly shrink: cashiers casually give 10% off, takeout orders get dine-in coupons applied, membership discounts and coupons stack on top of each other, and only at month-end when you look at the reports do you realize the discount amount far exceeded expectations. The problem usually isn't that employees are "intentionally" doing this—it's that the restaurant POS system hands discount permissions to everyone without boundaries. Below, we break down how coupons should actually be managed, from setup logic to permission control.

  1. What's the difference between Coupon and Discount in a POS? The two differ in how they're triggered and controlled in the POS backend. A Discount is typically a price reduction a cashier actively selects at the checkout screen—it can be a percentage, a fixed amount, or a discount on specific items. A Coupon is a discount with a "voucher" attribute, often tied to usage conditions—minimum spend, validity period, one-time use, specific channels, etc. Simply put, a Discount is something the employee "gives," while a Coupon is something the customer "holds." When setting up, preset discounts (employee meals, Happy Hour) can be made into quick buttons that don't require a PIN; coupons distributed externally must be tied to unique codes and condition restrictions, so they don't become a "universal discount button" a cashier can invoke at will.

  2. How do you choose between percentage discounts and fixed-amount discounts? Percentage discounts suit membership tiers and time-based promotions—for example, 5% off for regular members, 10% off for premium members, automatic 10% off during lunch hours. But the risk is "indiscriminate profit dilution": if a percentage discount is open on the entire check long-term, the higher the average ticket, the greater the give-away, and customers won't order more because of it. Fixed-amount discounts ($5 off $50, $10 off $100) are better suited to raising average ticket—customers will add dishes or drinks to cross the threshold. A safer approach for Chinese restaurants: use percentages for membership benefits, use spend-threshold discounts for acquisition and raising average ticket, and neither should be opened unconditionally all day across the entire menu.

  3. Can coupons and membership discounts be used at the same time? This is where discount setup most easily "leaks money." Membership discounts (such as member pricing, points-redemption discounts) and coupons are two independent logics, and whether stacking is allowed must be explicitly configured in the rules engine of the restaurant's membership marketing system. There are three common safe approaches: mutual exclusion (using a coupon means no membership discount, or vice versa), priority selection (the system automatically picks the option more favorable to the customer, without stacking), and conditional stacking (only low-value coupons may be combined with member pricing; high-value coupons are mutually exclusive). If unsure, set it to mutual exclusion first, and once you have Discount Report data to support it, gradually open up controllable stacking scenarios.

  4. Which discounts should have a minimum spend? The core purpose of a minimum spend is to prevent "small orders eating big coupons." If a $5 off coupon can be used on an $8 order, the discount rate exceeds 60%—essentially giving it away. Three types of discounts especially need thresholds: spend-threshold coupons ($5 off $30, keeping the discount rate within 15%), large fixed-amount coupons ($10 off should have at least a $50 minimum spend), and new-customer first-order coupons (can be relaxed somewhat, but recommended not below 60% of the channel's average ticket). In the POS backend, minimum spend is usually calculated on the "pre-discount basket amount"—when setting it up, pay attention to whether it's before or after tax, to prevent customers from using tax and tips to reach the threshold.

  5. Should employees have manual discount permissions? Manual discounts are the number one source of internal shrinkage. Industry statistics show that about 29% of total shrinkage comes from internal employee behavior, and Void, Refund, and Discount are precisely the three most easily abused functions. A reasonable permission allocation is tiered limits: preset discounts (employee meals, time-based promotions) can be PIN-free because they've already been pre-approved by the owner; cashiers' manual discount ceiling should be kept within 10% off, with anything beyond requiring manager PIN authorization; custom-amount discounts (comps, giveaways) should only be open to manager-level roles and above, with a mandatory reason code. More importantly, one person, one account—don't have the whole store share a single cashier account, or the reports won't be able to trace "who approved this discount."

  6. How do you limit coupon reuse? Preventing reuse requires two gates in the POS backend: one use per order and a cumulative usage limit per customer. The former prevents the same coupon from being repeatedly applied to the same order; the latter binds the coupon to the customer's phone number or membership ID, limiting that customer to a total of N redemptions within the validity period. For publicly distributed paper or flyer coupons, if the system doesn't support binding to a customer, at least set a global maximum usage count, after which the coupon automatically becomes invalid. In addition, one-time coupons must be marked as used in the POS after redemption, to prevent the same code from being entered repeatedly.

  7. Should takeout and dine-in discounts be set up separately? Yes, and it's almost mandatory. The cost structures of dine-in and takeout are completely different: takeout orders already bear platform commissions or delivery costs, and if a high-value dine-in discount is applied on top, per-order profit may drop straight to zero. In the POS backend, coupons and discounts should be bound to Order Type: dine-in coupons can only be used for Dine-in, and takeout coupons only match Takeout or third-party platform orders. At the same time, the discount level for takeout channels is recommended to be one tier lower than dine-in, and prioritize "spend-threshold discounts" over "whole-check percentage discounts," because takeout average tickets are relatively concentrated, and spend-threshold discounts do more controllable damage to profit.

  8. Which Discount Reports should be checked monthly? Month-end reconciliation can't just look at the single number "total discount amount." The Discount Report should track at least five dimensions: ① total discount amount and discount rate (discount amount ÷ pre-discount sales, to judge whether overall give-away is out of control); ② usage count of each discount/coupon and the sales it drove (to judge which coupon actually brought incremental business and which was just a free give-away); ③ discount usage summarized by employee (whose time-based discount rate is noticeably high—the numbers will expose the problem before it surfaces); ④ discount distribution broken down by channel (dine-in/takeout); ⑤ discount amount broken down by coupon type and menu category, with particular attention to whether high-margin items are being over-discounted. If the POS supports it, comparing "post-discount sales" and "pre-discount sales" side by side is more telling of a promotion's real effect than looking at the discount amount alone.

The essence of coupon setup isn't "making more discounts"—it's putting four things into the same set of rules: who can give discounts, how much, under what conditions, and how to check afterward. For Chinese-owned businesses, a U.S. restaurant POS system with clear backend logic determines whether profits can be retained more than the discount level itself. Whether you're using a New York restaurant POS system or Los Angeles restaurant management software, spending an afternoon re-reviewing your Discount rules and permission boundaries will usually protect your bottom line better than sending out another round of coupons.

https://ratemypos.com/10058/

4
508
United States

Comments (4)

Your avatar
Sign in to comment
蓝天卫
蓝天卫6 days ago

One thing to keep in mind: many POS systems let cashiers stack discounts and coupons right at checkout by default. If you haven't set up mutual exclusion rules in advance, you may find your margins quietly eaten away when you reconcile at month-end. It's best to check the default stacking settings in your backend first.

邵继华
邵继华6 days ago

The article points out that delivery and dine-in promotions need to be set up separately, which is crucial. However, commission rates charged by delivery platforms vary widely from state to state—New York may have high commissions, while smaller cities in the Midwest are considerably lower. So delivery coupon discounts can't be applied uniformly; they need to be adjusted according to the actual local cost structure, otherwise it's easy to lose money.

一个玩笑而已
一个玩笑而已5 days ago

Manual discount permissions must be tightened up. Otherwise, there's no way to trace from the reports who specifically approved what, and the loopholes will only get bigger.

yyds68
yyds685 days ago

The suggestion to cap manual employee discounts at no more than 10% is quite practical. But I'd like to confirm: if the restaurant is very small, with only two or three cashiers, is it still advisable to set up a manager PIN? Would that affect checkout efficiency?