Deutsche Version

Back to overview

Extended Voucher Rules: Troubleshooting

Live Demo: Try this and other plugins live — no installation, no risk: demo.markus-michalski.net

Troubleshooting

Symptom: The customer sees a red error message although the code is valid.

Check: Which message appears? "only valid for first-time customers", "outside valid time window" and "cannot be combined with another already applied voucher" come from the module, see Storefront. Other messages come from the series' standard rules (validity period, user group, minimum order value, quota).

Solution: Check and adjust the active rules on the Extended Rules, Time Windows and Combinations tabs of the series.

Symptom: The voucher is not applied and no hint box appears.

Check: Is the voucher bound to a payment method, a delivery method or a minimum order value per payment/delivery method? Then it is reserved and only applied once the matching selection is made. Does the shop use a theme other than Apex? Then the module ships no hint box.

Solution: Select the matching payment or delivery method. For other themes, extend the checkout summary with the hint box, see Technical.

Symptom: A reserved voucher is not activated although the payment method matches.

Check: Is the selected payment method contained in "Allowed Payments"? Is there a minimum order value for the payment method that the basket value has not reached yet? The same for the delivery method? Does another rule (time window, first order, combination) apply? The rules are checked in sequence, see Technical.

Solution: Adjust the rule concerned. The voucher is checked again on the next basket recalculation.

Symptom: The time window applies at the wrong time or never.

Check: Is at least one weekday ticked? A window without a weekday never matches. Is the end before the start? Such a window never matches either. The weekday is determined with the PHP time zone, the time of day with the database server's time. If the two time zones differ, the window shifts.

Solution: Correct the window, or create two windows for periods across midnight. Align the PHP and database time zones. When entered as HH:MM (for example end 23:59), the window ends at second 00, so the time from 23:59:01 to 23:59:59 is not covered.

Symptom: "First Order Only" does not take effect.

Check: The check only runs if a user can be determined when the voucher is checked. Without a user, for example a visitor in the basket who is neither logged in nor has entered any data, the rule is not applied. All non-cancelled orders of this user in the current shop are counted.

Solution: The rule takes effect at checkout once the customer is logged in or has entered data as a guest. Earlier orders under a different user account are not taken into account.

Symptom: The combination block does not take effect.

Check: Is the combination entered on the Combinations tab? If "Valid with different Series" is set to "No" in OXID, all combinations are already blocked, so the block list is not the cause. If the option is "Yes", the module checks the block list in both directions on every redemption and every recalculation.

Solution: Check the entry on the Combinations tab and recreate it if necessary.

Symptom: The four tabs are missing on the voucher series.

Check: Is the module mmd_voucherrules active? Has the cache been cleared? Is a voucher series selected?

Solution:

vendor/bin/oe-console oe:module:activate mmd_voucherrules
vendor/bin/oe-console oe:cache:clear

Known limitations

• Time windows cannot be edited, only deleted and recreated, and they do not support periods across midnight.
• The first-order check is skipped if no user can be determined.
• The hint box is only shipped for the Apex theme.
• The limit "Max. combinable" counts distinct series of the other applied vouchers and shows the same message as a blocked combination.
• If an unexpected error occurs while checking the extended rules (for example a database error), the module writes an entry with the prefix mmd_voucherrules: to the OXID log and lets the voucher pass according to the standard rules.

FAQ

Does the module affect existing vouchers? No. Series without configured rules behave like standard OXID.

What happens when a new payment method is added? Series without a payment restriction apply to all payment methods, including new ones. Series with a selection apply only to the selected payment methods.

Does the module work in multishop setups? All rules are stored and read per shop (column OXSHOPID).

Can several time windows be created per series? Yes. The voucher is valid if at least one active window matches.

What if the customer redeems the blocked voucher first? The block applies in both directions, the order does not matter.

Is data lost on deactivation? No. The tables and entries are kept.