Discount Exclusion Manager: setup and help

Upload the ZIP in Modules > Module Manager > Upload a module. Install it and click Configure. Open Sell > Discount Exclusions > Exclusion Groups to define protection. Use Settings > Configuration for cart messages and Settings > System Check for module checks.

Requires PrestaShop 1.6.1 or later and PHP 7.1 or later.

This revision uses exclusion groups and entity selectors. It does not provide the former Product IDs, Category IDs, Manufacturer IDs, or global Enable Module fields.

Installation and enablement attach the module to every shop. Disablement is also global because compiled cart-rule restrictions and native catalog-price relations can be shared. Select and review each group's shop associations deliberately.

Open Exclusion Groups and add a group.

The product selector can select specific products or build live rules by category, brand, supplier, name pattern, price range, and the other available product methods. It can also express exceptions inside a selection. Review the selector's preview rather than treating it as a comma-separated ID field.

Vouchers and catalog discounts have independent scopes. Selecting no items in a restricted scope means none. It does not silently mean all. Existing selected-but-empty scopes remain empty when reopened. Explicitly select All items if you need every item.

Groups combine protection as a union. There is no priority field and no allow rule that overrides another active group's exclusion. A product protected by any applicable active group remains protected for that group's selected discount scope.

For example, to protect a product from one promotion, choose that product under Excluded products, choose that voucher under Vouchers, and leave Catalog discounts with no selected rules if catalog protection is not required. Save, then check the summary reads the intended voucher and catalog scopes.

To protect a category or brand, create a product selection using that condition. Review its live matches and any descendant-category option offered by the selector. Do not assume the old flat-ID behavior or automatic inclusion of every descendant.

The module compiles supported exclusions into native cart-rule restrictions. PrestaShop 9.1 and later also provide runtime hooks for supported monetary shapes that cannot be represented safely by native restriction data.

The module does not require a CartRule override. Do not install an old override as a setup step.

Supported percentage rules can reduce only the eligible selection. A product protected from a voucher is removed from that voucher's monetary scope. Other manual specific prices or promotions can still apply to the product.

A voucher whose shape cannot be represented safely is disabled or rejected through the module's protection flow. Exclusion Groups can report that voucher protection is fail-closed, meaning the rule is prevented from applying until its shape or targeting is corrected and the policy is saved again.

Pure non-monetary rules use the native-safe path unless another protection condition blocks them. For example, a protected gift product is explicitly unsupported. Free-shipping and gift combinations are subject to the same protection checks.

If no eligible monetary products remain, the rule must not discount protected items. Depending on its compiled state and core behavior, it can be unavailable or report that it does not apply to the basket. Verify both the displayed message and the actual discount amount.

Catalog discounts targets Catalog Price Rules. The module removes the selected rules’ reductions from protected products.

Manual per-product specific prices, identified by a zero catalog rule ID, remain active. A protected item can therefore still have a manually configured discounted price. The base price remains unchanged. Other modules can still change prices.

The module records which prices it changed, so it can restore native behavior when protection is removed. Normal product, rule and selection changes are picked up straight away. Direct database changes and background catalog regeneration are picked up only by the scheduled maintenance task, so keep that task running.

After saving a policy, test a protected and an eligible product. Change a product so it enters or leaves a live selector, then confirm protection follows the new match after publication and reconciliation.

Open Settings > Configuration.

Save changes. Empty text fields intentionally use the module's translations instead of saving the same English sentence in every language.

Available template tokens are:

If a required token has no data, a sentence using it can be suppressed. If your excluded-products sentence already contains {excluded_products}, the renderer avoids repeating the same product names in a separate list.

A rule reduced to nothing uses a separate translated basket message. Individual optional message switches do not replace that blocked-basket explanation; the master switch controls all module messages.

The module registers Reconcile protected catalog prices with a 60-second schedule in the shared MPR cron system. Ensure that a server scheduler actually invokes the shared runner. Registration alone does not install your server crontab.

For a standalone runner, obtain the exact command from the installed module's getCronCommand() method. An administrator with shell access can print it after substituting the real shop path:

php -r 'require "/path/to/shop/config/config.inc.php"; $module = Module::getInstanceByName("mprdiscountexclusionmanager"); echo $module->getCronCommand(), PHP_EOL;'

The method returns a once-per-minute command shaped like:

* * * * * php /path/to/shop/modules/mprdiscountexclusionmanager/cron.php --token=YOUR_SHARED_CRON_TOKEN --max-seconds=300

Install the generated command under an account that can read the shop configuration and run its PHP environment. The script accepts --token, --max-tasks, --max-seconds, --context, and --run-task. Token validation is required for CLI too.

An HTTP alternative uses the module-generated cron URL, normally /module/mprdiscountexclusionmanager/cron?token=.... The token belongs to the shared MPR cron configuration, not to a separate exclusion-group field. Keep it private. The runner can execute due tasks across modules. Use one suitable shared schedule if you already have one.

Create a cart containing one protected product and one eligible product. Apply a supported voucher. Compare the discount amount with the eligible merchandise, then remove the eligible product and check the result again.

Test percentage and fixed-amount rules separately on supported cores. Test the exact product conditions, gifts, shipping actions, currencies, tax display, and partial-use options you use. Check an actual test order as well as the cart.

With cart notices enabled, the module renders through displayShoppingCart and displayShoppingCartFooter. JavaScript refreshes impact data after cart updates and tries to place messages near the voucher area. It also adds optional badges when it recognizes the theme's product rows.

The current template consumes mprdexclusion_impact. It renders theme-style article alerts using .mprdexclusion-cart-notice and state data. The former mprdexclusion_notice_text and mprdexclusion_excluded_names example is not the current template interface.

A theme override can be placed at:

/themes/your_theme/modules/mprdiscountexclusionmanager/views/templates/hook/cart-notice.tpl

Inspect the current template before customizing. The cart alert uses the theme's alert styling. Current useful selectors include .mprdexclusion-cart-notice and .mprdexclusion-line-badge. Do not rely on the old notice-text and excluded-list wrapper classes.

If a product is still discounted, check the group's active state, product preview, shop associations, and the separate voucher or catalog scope. Determine whether the discount comes from a manual specific price, which catalog protection deliberately leaves active.

If a voucher disappears, inspect the warning on Exclusion Groups. Review its reported unsupported shape, change the voucher or scope, and save the exclusion policy again. Do not reactivate a quarantined native voucher directly without resolving the policy.

If selection publication or reconciliation fails, inspect Settings > System Check, module diagnostics, and cron results. A stale or incomplete protection state can stop pricing or voucher application instead of allowing an unprotected discount.

If cart messages are absent, check the master and individual switches, hook placement, front JavaScript, and theme selectors. Financial protection and message display are separate paths.

To suspend one policy, set its Active switch to No and save. To stop the module, use Module Manager. Enable and disable operations apply globally in multishop. Disable restores native catalog behavior and reconciles voucher state while retaining definitions.

Before uninstalling, back up policies and review affected native rules. Uninstall checks that voucher restoration is possible, restores managed voucher and catalog state, unregisters cron tasks, and removes module configuration and tables. If restoring the protected discounts fails, uninstall stops. Resolve the reported failure before retrying; do not delete module tables or files manually.