Current behaviour:
The "Redeem a Voucher" section on Soda only accepts the voucher code itself. If a customer or venue enters the purchase reference number instead, the voucher doesn't appear, even though both numbers relate to the same purchase.
Issue raised:
Venues have reported attempting to redeem using the purchase reference number rather than the voucher code, causing the voucher to not appear in the "Redeem a Voucher" section. This causes confusion, as both numbers appear to relate to the same purchase, with no clear indication of which one is needed in this context.
Suggested improvement:
Allow the "Redeem a Voucher" section to accept both the voucher code and the purchase reference number as valid search inputs.
Where a purchase reference number relates to multiple voucher codes (e.g. a multi-voucher purchase), entering the reference number should present each associated voucher code via a dropdown, allowing the venue to select the correct one to redeem.
Why this matters:
This is a recurring point of confusion for venues/customers, leading to support queries and a poor user experience when a voucher appears to be missing/invalid due to the wrong number being entered, rather than an actual issue with the voucher itself. Supporting both identifiers would remove this friction without requiring any change to how codes are currently generated or displayed.
