How it works
Separate a voucher from a discount code and a payment. A redemption needs server-side validation and duplicate protection; a marketing email must not be treated as proof of available credit.
Make newsletter registration voluntary and keep marketing choices separate from a receipt request. Use the selected guest contact only for the purpose that was actually agreed.
A practical example
A guest uses part of a voucher and receives an updated balance. A repeated request should not redeem the same amount twice.
Scope and readiness
Live voucher sale, tax treatment, refunds and consumer terms vary by country and payment arrangement. The pilot is not a substitute for issuer approval or production financial reconciliation.
IQ Order is in pilot development. Test payments do not move money. Live payment, tax and POS connections, mail services and physical devices need their own provider access and acceptance. Public marketing pages do not grant access to administration.
From the first menu to a connected visit
- Select your menus, service areas, ordering channels and staff roles.
- Run a complete visit using fictional guests and clearly labeled test payments.
- Validate the selected country, providers and physical devices before production.
Questions before your pilot
What should I know about Restaurant vouchers and customer loyalty?
Prepare vouchers, redemption rules and loyalty actions alongside checkout and promotions. Keep the value, redemption history, expiry terms and any remaining balance understandable.
What is the scope and what still needs validation?
Live voucher sale, tax treatment, refunds and consumer terms vary by country and payment arrangement. The pilot is not a substitute for issuer approval or production financial reconciliation.
Explore related workflows
Restaurant promotions and newsletter marketing · Restaurant payments, receipts and POS integrations · Restaurant operations and multi-site controls