Distinguish the offer, code and applied reward
A Lexoh promotion defines a reward and the conditions under which it may apply to eligible activity. A promotion code identifies an offer for redemption through a supported workflow. Creating a promotion, distributing its code and applying its reward are separate steps.
Use the promotion types and redemption channels available in your installation. The final result also depends on the linked pricing, eligible record, validity rules and usage state. An active label or readable QR code alone does not establish eligibility.
A pricing reward does not by itself authorize entry, reserve a parking space or confirm a payment. Verify access permissions, capacity and transaction status through the relevant controls. Measure campaign results from recorded activity rather than assuming that distributing an offer increases loyalty.
Find the right promotion and its current scope
Open Promotions from the configuration navigation available to your role. Search using the campaign name and review any site, organization, status or date filters. A filtered or permission-limited list may not contain every promotion.
Open the record and compare its reference, name, linked pricing, reward values and status with the intended campaign. A descriptive name such as Welcome offer does not define eligibility. Check the saved rules and distinguish promotion status from the status of each code.
Before changing an existing offer, inspect issued codes and prior redemptions. Confirm whether edits affect already distributed codes, current sessions or only future activity. Preserve the previous settings and transaction evidence; do not assume a renamed or recreated promotion retains the same reference or history.
Set up the offer before distribution
- Define the audience, eligible site or pricing rule, reward and campaign owner. State the intended customer outcome in plain language, including exclusions.
- Select the supported reward type and enter its value with the correct unit and currency. Confirm whether a value means a percentage, fixed reduction, invoice adjustment or another benefit.
- Configure any code or QR requirement and the supported redemption point. Verify whether the customer presents the code at a kiosk, in a customer flow or through an operator; a phone camera reading the QR is not a redemption test.
- Set the start and end date, time and time zone. Check whether boundaries are inclusive and whether eligibility is evaluated at entry, checkout, payment or redemption. Test a session that crosses the end of the offer.
- Check usage limits, eligible records and interaction with other promotions. Confirm whether limits apply to a code, customer, credential, transaction or campaign, and whether a total campaign cap is available.
- Save and reopen the promotion. Review the stored settings and arrange a controlled test using an equivalent test code. Inactive status can help prevent distribution of a live offer, but it does not demonstrate that a redemption will succeed after activation.
Check the reward calculation and qualifying activity
Review only the reward types offered by the form. For a voucher, confirm the eligible charge, maximum reduction, residual-value handling and permitted uses. A promotional voucher is not automatically a stored-value gift card. An invoice credit is not automatically a refund to a payment card.
For percentage or fixed reductions, verify the calculation base, rounding, fees, taxes and order of other adjustments in the configured pricing. For free-parking or partner rewards, confirm the covered duration, eligible charge or partner redemption procedure before describing the benefit to customers.
| Explicit example rule | Expected result before excluded taxes or fees |
|---|---|
| Fixed CAD 5 reduction | CAD 20 − CAD 5 = CAD 15 remaining. |
| 20% reduction | CAD 20 × 20% = CAD 4 reduction; CAD 16 remaining. |
| CAD 25 voucher, reduction capped at the eligible base | CAD 20 reduction; CAD 0 remaining. The extra CAD 5 is not assumed to become cash or a reusable balance. |
| CAD 5 first, then 20% of the reduced base | (CAD 20 − CAD 5) × 80% = CAD 12 remaining. |
| 20% first, then CAD 5 | CAD 20 × 80% − CAD 5 = CAD 11 remaining. |
Confirm the calculation in a controlled transaction
These examples specify their own assumptions; they are not Lexoh defaults. Taxes and other fees are excluded from the example base. The last two rows illustrate why stacking order matters, not that combining rewards is supported. Compare the actual adjustment and final payable amount with the intended rule.
Define what counts toward a frequency reward
If First, Nth or Every Nth is available, establish the counting scope and the qualifying event. A ticket, visit, paid transaction and customer are different units. Check treatment of cancellations, refunds, multiple credentials and counter resets. First in a campaign does not necessarily mean the customer’s first visit ever.
Test threshold boundaries
For an illustrative counter starting at 1, Nth with N = 5 matches 5 once; Every Nth with N = 5 matches 5, 10 and 15. Test immediately before, at and after a threshold, and verify the installation’s counter behavior. Multiple thresholds also require a priority or combination check.
Verify code status, usage and presentation
When the promotion supports codes, use the available creation or generation control and verify the saved reference, status and usage settings. Confirm accepted characters, case sensitivity and uniqueness in the actual form. Use an identifier suited to the campaign without putting customer details into it.
A unique code value, a one-use limit and a validity period are independent properties. A limited-time offer can still permit repeated use, and a one-use code can remain unused until it expires. Verify exactly when usage is consumed and what happens after an abandoned or failed transaction, cancellation or refund.
Use the QR output produced by the supported workflow. Do not construct a QR from an assumed PRO[CODE] payload or assume every phone, scanner and redemption screen accepts the same format. Test the actual reader and workflow. A QR image can be copied; it does not by itself verify the holder’s identity or enforce a use limit.
If the interface shows Used, Used Date or Used by Access Card, confirm whether they describe the first use, latest use or another event. A credential reference is not proof of the person who presented it. For repeat-use codes, review available redemption records rather than treating a single status or date as a complete history.
For a one-use offer, test successful redemption and a second attempt with a dedicated test code. Confirm handling of simultaneous attempts and disconnected equipment before relying on a shared limit across readers. Printing or emailing the same code twice does not create two independent entitlements.
Check delivery separately from redemption
Use only distribution channels enabled for the installation. Verify the intended recipients, approved campaign terms and available sending or printing settings. Include the benefit, eligible location or pricing, validity and time zone, usage restrictions, redemption steps and support contact.
Email or SMS
If sending controls are available, confirm the address or phone number and preview the actual message and code destination. Test with a controlled recipient before wider distribution. A queued or sent status is not proof of delivery, opening or redemption; inspect the available delivery result separately.
Printed material
Confirm the supported output and printer. Inspect the final print for legible terms, an intact QR and enough clear space around it, then test it on the intended reader. Enlarging, cropping or reusing a screenshot can change readability. A copied code retains the original code’s usage rules.
Corrections and campaign closure
Check whether disabling a code or promotion affects already issued copies, active sessions or queued messages. It cannot remove a printed sheet or a delivered message. Preserve the records needed to explain prior adjustments before following the supported retirement or deletion procedure.
Test edge cases and review campaign results
- Record an expected result for an eligible case, an ineligible pricing rule, dates before and after validity, an inactive code and a repeat attempt. Use a controlled workflow so tests do not consume codes intended for customers.
- Compare the base charge, reward, remaining amount and resulting transaction or invoice. Verify frequency thresholds and stacking only where supported. Retain the relevant references and the tested configuration.
- If redemption fails, check promotion and code status, linked pricing, time zone, eligibility, previous usage and the reader’s accepted format. Preserve the error and inspect the transaction before issuing a replacement or trying again.
- Track distribution, successful redemption, adjustments, reversals and net results separately. For example, 20 distinct redeemed codes out of 100 distinct issued codes is a 20% code-redemption rate for that cohort. It is not necessarily a delivery rate, a customer conversion rate or proof of additional revenue.
- Review the campaign with its owner after pricing or eligibility changes. Update customer-facing terms and templates together, and check what happens to existing codes. Keep operational verification separate from claims about marketing performance.