Create, Test, Redeem and Manage Coupon Codes

Before You Create the Offer

A coupon changes the amount collected and can be used across tills. Write the commercial rule first, obtain the owner's approval, then configure and test it with a controlled sale before publishing the code.

• Enable Marketing in Manage -> Features; the Marketing page and till coupon control depend on this switch.
• Write down the offer value, minimum bill, date window, total redemptions and per-customer rule before entering it.
• Decide whether Walk-in customers may use the offer. A per-customer limit needs an identified customer to be meaningful.
• Use a short code that is easy to read, type and print without confusing letters or spaces. Posnic trims it and stores it in uppercase.
• Choose a code not used by any outlet in the license. Code uniqueness is license-wide, not branch-only.
• For multiple outlets, agree where the code may be advertised. Current validation finds a matching code license-wide and does not reject it merely because checkout is in another branch.

Create a Coupon Step by Step

1. Open Manage -> Marketing -> Coupons.
2. Click New coupon.
3. Enter the Code and a staff-readable Description.
4. Choose Percentage off or Fixed amount off, then enter Value.
5. Enter Min spend when the bill must reach a threshold.
6. For a percentage offer, enter Max discount to cap the currency amount; 0 means no cap.
7. Set Valid from and Valid until for a timed offer, or leave them empty for no date boundary.
8. Set Total uses and Per customer. In either field, 0 means unlimited; Total uses 1 creates a one-use code.
9. Keep Active selected only when cashiers should accept the code.
10. Select Save and wait for Coupon saved.
11. Find the row in the Coupons table and verify Code, Value, Valid, Used and Status.
12. Run the controlled test matrix below before distributing or printing the code.

Understand Every Field

Check the Discount Maths

Posnic calculates the coupon against the bill basis, rounds the result to two decimals and never lets the coupon alone reduce the running bill below zero.

Redeem the Coupon on New Sale

Applying the code is a preview. When the cashier saves the sale, the server discards any client-supplied discount amount, validates the code again against the current bill, customer, dates and redemption counts, and calculates the discount itself.

1. Open New Sale, add every item and finish line edits or manual discounts first.
2. Select the correct named customer before applying a code with a Per customer limit or customer binding.
3. Place the cursor in Coupon, then type the code or scan a printed voucher barcode into that field.
4. Apply the code and read the status returned by Posnic.
5. Confirm the green summary shows the normalized code, discount and capped label when relevant.
6. Read Discount and Pay Total after applying it; do not calculate change from the original total.
7. If items, quantities, customer or other discounts change, clear the coupon and apply it again to refresh the preview.
8. Open PAY only after the final displayed total is correct, then complete payment normally.
9. Verify the saved receipt or sale record carries the code and expected discount.

Final-Save Revalidation and Stale Codes

The preview does not reserve a use. Another till can consume the final available use, a manager can switch the coupon off, or the bill can change before Save. If final validation fails or errors, Posnic removes the code and coupon value and allows the sale to continue at full price instead of failing the sale. The cashier must verify the final amount before collecting money.

• Never promise that an applied preview guarantees the discount until the sale is saved.
• For a last-use or one-time code, complete the tender promptly and verify the receipt.
• If the customer expected a discount but the saved sale is full price, preserve the Sale ID and escalate; do not create a duplicate sale.
• A coupon may be combined with loyalty redemption in the current calculation path; each is clamped against the running payable amount. Test and approve combined promotions before launch.

When a Coupon Is Rejected

Usage Counters and Redemption Records

A completed coupon sale creates a redemption record containing the coupon, code, customer when present, Sale ID, human sale reference, discount, bill total, currency, branch, date and operator context. The Coupons table's Used value is the running counter, while validation counts active redemption rows.

• Coupon booking is idempotent per sale, so retrying the same sale cannot count a second coupon redemption.
• Booking runs after the sale commits and is protected from failing the sale. If the receipt has a discount but Used did not move, keep the Sale ID and reconcile rather than repeating the transaction.
• Walk-in sales may use unrestricted coupons; their redemption record simply has no customer.
• Per-customer enforcement needs the saved customer ID, not a typed name or phone note.

Void a Coupon Sale

Cancelling a saved sale through the supported whole-sale void workflow marks its coupon redemption voided, records the void date and frees the use by reducing the coupon counter. The redemption row remains as audit evidence.

1. Open Sales History and find the exact original Sale ID.
2. Verify customer, items, total, coupon code and discount before cancelling.
3. Use the authorized whole-sale void action and complete any manager approval.
4. Confirm the sale is cancelled and its stock and payment consequences are handled.
5. Return to Coupons and verify Used decreased when the coupon still exists.
6. Retain the original Sale ID; do not delete and recreate a coupon to repair a counter.

Edit, Pause and Delete Safely

• Use Edit to correct an upcoming offer before launch. Changing a live offer changes what the same code will do on later sales.
• Turn Active off to pause acceptance while keeping the coupon and its counter visible.
• Codes are unique across the license, so another branch cannot create the same code while this record exists.
• Delete asks for confirmation and permanently removes the coupon definition. Historical redemption rows remain, but the coupon disappears from the management list.
• Do not delete a distributed or previously used coupon merely to stop it. Deactivate it so operators can still inspect the definition and Used count.
• If a deleted coupon's old sale is later voided, the redemption can be marked voided but there is no coupon row left whose counter can be reduced.

Multi-Branch Operating Rule

The create screen stores the current branch and currency on the coupon, and the list shows the current branch plus any license-wide records. However, code lookup and validation currently use license plus code and do not enforce branch ownership. Treat every coupon code as potentially redeemable at every outlet in the same license.

• Use a common promotion policy across outlets or encode the intended outlet clearly in the code and cashier instructions.
• Do not create two branch-specific coupons with the same code; license-wide uniqueness prevents it.
• Be especially careful with fixed-amount coupons when branches use different currencies because the saved currency is a display label, not a conversion rule.
• Test the code at every outlet where it should or should not be accepted before publishing it.

Permissions and Scope

Controlled Test Matrix