Offers and vouchers

Open Offers from the selected venue. Promotional banners and voucher demonstrations can open a detail view. The requested staff-meal voucher uses the exact wording Staff meal Voucher, DATE, and 8 hour shift meal voucher when that feature is completed.

Offer QR codes in the presenter are demonstrative. A QR code has no redemption value until a server redemption endpoint enforces eligibility and single-use rules.

What customers should see

Offers describes promotions for the selected venue or explicitly applicable venues. A customer can open an offer from the offers list, read its headline, validity period, restrictions and redemption instructions, and return to the venue. Artwork and promotional language are editorial content until an eligibility and redemption service validates the actual benefit.

Redemption is a separate operation

A rendered QR code or voucher image is not proof that an offer has been redeemed. Real redemption requires a server-generated identifier, eligibility policy, venue scope, expiry rules, replay/single-use protection where applicable and staff-authority checks. The presenter can show an example voucher but must not imply that it can be accepted at a till. Cross-promotions between restaurants require explicit rules so that venue staff cannot accidentally honor a discount unavailable at their site.

Staff meal and other special cases

The recorded staff-meal example calls for the labels Staff meal Voucher, DATE and 8 hour shift meal voucher. Exact approved wording does not establish tax, payroll, staff eligibility, working-time verification or redemption procedures. Those business rules need approval before a production redemption endpoint is enabled. A staff-only benefit must not be granted solely because a customer can reproduce its QR graphic.

Source and delivery state

The shared UI and browser presenter have promotional screens and sample journeys. The native offers provider does not yet have a real eligibility/redemption backend. WordPress editorial records can be used as display content, but their post IDs should not substitute for secure HSLG redemption identifiers. Before release test date boundaries, venue changes, cancelled scans, duplicate redemption and attempts to claim another user's offer.

Reporting errors

Record which venue and offer were displayed, the intended restriction, the displayed validity period and whether the test was a demo or connected backend. Do not put an actual active redemption secret into a public screenshot. If an offer has become invalid, display the reason when safe and retain a navigation route back to other content.