Coupon codes
Each coupon is a code a customer or cashier enters, validated centrally rather than trusted.
Farexa Promotions defines coupons with real rules — a code, a percentage or fixed discount, a minimum order, a usage cap, and a validity window — that the POS and sales checkout validate, so a discount follows the offer rather than the mood.
A discount is only as good as the control around it. Give cashiers a promotion with no rules and you get discounts that outlive the campaign, get applied below the minimum order, or run past the usage limit. Farexa makes a coupon a real object: a code, a discount type — percentage or fixed — and a value, a minimum order amount, a maximum usage count, and a start and end date. The checkout enforces every one of those, so the offer behaves the way you set it, not the way the queue pressures the cashier.
Because coupons validate against the same rules everywhere, the promotion you run at the counter is the promotion your sales orders honour — there's no second, looser version living in someone's head. Usage is counted as it's redeemed, so a capped offer stops when it's supposed to, and a validity window means an expired campaign simply stops working rather than needing to be manually switched off.
Offers you want the public to see can be published, so a promotion isn't only an internal code but something a customer can encounter — while the enforcement stays server-side, on the same rules, wherever the coupon is used.
Each coupon is a code a customer or cashier enters, validated centrally rather than trusted.
Set the discount as a percentage or a fixed amount, with the value you choose.
Require a minimum spend before a coupon applies, so discounts don't undercut small baskets.
Set a maximum usage count; redemptions are counted, so a capped offer stops when it's reached.
Start and end dates mean an expired campaign stops working on its own, without manual cleanup.
Publish offers so customers can encounter them, while enforcement stays on the same server-side rules.
The counter and sales checkout validate coupons against their rules, so the discount follows the offer.
One coupon, one set of rules, whether it's redeemed at the counter or on an order.
The code, whether the discount is a percentage or a fixed amount and its value, a minimum order amount, a maximum usage count, and a start and end date. The checkout enforces all of them, so the offer behaves as configured.
Yes. Coupons carry a validity window, so an expired campaign simply stops working — you don't have to remember to switch it off. Usage caps work the same way: once the maximum redemptions are reached, the coupon stops applying.
Enforced. The POS and sales checkout validate a coupon against its rules server-side, so a cashier can't apply an expired code, ignore the minimum order, or exceed the usage cap.
Yes. Offers can be published so customers encounter them, while the enforcement of the discount stays on the same server-side rules wherever the coupon is used.
Yes. There's one coupon with one set of rules, honoured whether it's redeemed at the POS counter or applied to a sales order — no looser second version.
Book a walkthrough and set up a coupon with your own rules, then watch the checkout honour them and stop when it should.