Sales Revolution: setup and help

1. Upload and install mprsalesrevolution.zip through Modules > Module Manager.
2. Click Configure. You reach Sales Revolution > Dashboard.
3. Select your intended shop context and open Sales Revolution > Configuration.
4. Review recommendations, campaign, VAT and numbering settings before using the storefront.
5. Start with one product pair and test a theme placement that consumes pairs, such as the cart/modal recommendation block.
6. Configure the cron runner before relying on campaign automation.
7. Verify displayed products, actual cart prices and analytics with a test customer session.

The module provides Dashboard, Product Pairs, Recommendation Rules, Bundle Offers, Campaigns, Dynamic Discounts, Campaign Scheduler, Analytics, Configuration and System Check pages. License, Support and Update pages are also provided.

Some settings on these screens are saved but have no effect in the current version; the tables below say which ones.

Open Sales Revolution > Configuration. Click Save after changing fields.

Features and Display

You can find these settings across the Features, Display, Filtering and Algorithm tabs. A setting's presence does not mean every placement consumes it.

Stored fields without effect

The following fields are saved by the configuration form but do not change recommendations, display or tracking. Keep them at their defaults unless your own integration uses them.

The actual recommendation engine can use manual pairs, co-purchases, rules, similar products, co-view data and trending data. Different placements supply different algorithm lists. The product-footer cross-sell uses similar/trending results and a fallback, so adding a manual pair does not force that particular footer section to show it.

Start with little order history

Frequently-bought-together suggestions require stored co-purchase pairs that meet FBT Min Orders and FBT Lookback Period. The scheduled rebuild can populate pairs from valid historical orders; it cannot invent purchases for a new shop.

Start with an active Product Pair and test a cart or modal placement that consumes manual pairs. The product-footer cross-sell uses similar/trending results. If it has no usable product IDs, it tries other active products from the source product's default category in the current shop, with a shop cover image. If no usable cards remain, it returns no block. This fallback is specific to that placement and does not guarantee every recommendation block will be populated.

Product Pairs

Open Sales Revolution > Product Pairs and add a record. Select Source Product and Target Product. Choose Pair Type: cross-sell, upsell, accessory or bundle. The model defaults to cross-sell, Bidirectional off, Priority 0 and Active on.

Enable Bidirectional to create the relationship in both directions. Higher priority pairs are selected first in the pair path. Save and test a placement that consumes manual pairs. A pair type of bundle is a recommendation relationship, not proof of a bundle checkout discount.

Recommendation Rules

Open Recommendation Rules. Set Name, optional Description, Rule Type, Priority, Products Limit and Active. Use Product Conditions to choose source products, categories or manufacturers, with optional Min Price and Max Price. Use Recommendation Filters to choose the suggested set and its price range.

For example, target source categories 12 and 18, with prices from 50 to 200, and recommend products from manufacturer 4. The saved JSON keeps source filters under conditions, target filters under recommendations, and price bounds under _price_min and _price_max.

Rules affect recommendation paths that include the rules algorithm. They do not replace the explicitly selected similar/trending algorithm in every product section.

Bundle Offers

Open Bundle Offers to maintain Name, Active, Bundle Products, Discount Type, Discount Value, Minimum Quantity, Max Total Uses, Max Uses Per Customer, Start Date and End Date. The model defaults to a percentage discount, value 0, and provides bundle-price/usage calculations.

The current version stores bundles and shows a preview in the back office, but does not sell them in the storefront: no bundle button is shown and no bundle discount is applied in the cart. Do not advertise a bundle discount based on a saved bundle.

Open Sales Revolution > Campaigns. Enter Campaign Name, choose Campaign Type, Discount Type, Discount Value, Priority, Active, Stackable, Target Products, Start Date and End Date.

Supported campaign types are flash sale, scheduled, recurring, countdown, early bird, last chance and limited deal. Discount types are percent, amount and fixed price. The model defaults to scheduled, percent, discount 0, priority 0, active on and stackable off.

Select target products, categories or manufacturers explicitly. Campaigns use the selected included items; exclusions and selections covering all items are not applied.

Saving a manual campaign stores its record, scope and deal display data, but it does not change product prices. Real catalog discounts (native specific prices) are created only by Dynamic Discounts and Campaign Scheduler. Check the product and cart price before you publish a promotion.

Limited-deal fields

For a limited deal, configure:

For example, create a limited deal with a 15 percent discount, positive quantity limit 100, valid dates, and turn on Product Pages and Homepage. Confirm the actual price and both widgets separately.

Simulated Velocity

Simulated Velocity defaults off in manual campaign forms. It stores phantom units separately from real sold units. Available controls include Velocity Mode (default steady), Phantom Units (0), Drain Duration (24 hours), Min Interval (300 seconds), Max Interval (3600 seconds) and Acceleration Factor (0.80).

If you configure phantom units, progress is not solely a count of purchased units. Review that presentation deliberately. The example of 10 phantom units over 24 hours is a simulated-progress configuration, not real sales history.

In Configuration > Limited Deals:

In Configuration > Countdown Banner:

The Campaigns configuration tab also exposes Show Countdown, Show Badge, Show Original Price and Show Savings, all default on; Countdown Style defaults simple; Badge Color is #ff0000; Badge Text Color is #ffffff; Price Display defaults replace; Combine Discounts and Priority Over Specific Prices default off.

These global campaign fields are saved but have no effect in the current version. Display options come from each campaign and from the scheduler, and native PrestaShop rules decide how discounts stack, so Combine Discounts and Priority Over Specific Prices do not change stacking.

Dynamic Discounts

Open Sales Revolution > Dynamic Discounts for the automatic promo rotator. New rotators are inactive. Set Rotator Name, optional Promotion Name, target pool, discount bounds, quantity and duration before activating.

The form defaults are percent discount, Min Discount 10, Max Discount 50, Quantity Limit 3, Duration (hours) 24, Auto-drain (phantom units) on, Drain Rate (hours per unit) 8, Velocity Mode steady, Cooldown (hours) 72, Max Concurrent Deals 1, Product Cooldown (days) 14, and Min Price/Max Price 0.

Review auto-drain explicitly before activation. A new rotator can simulate claimed units. Configure its trigger and product pool, then verify the generated campaign and native specific prices.

Campaign Scheduler

Open Campaign Scheduler. Configure Name, Active, Loop Mode, Loop Count or Loop Until, and Campaign Name Template. New scheduler records are inactive and pending; the default loop mode is infinite.

Build the Phase Sequence with a category, subcategory choice, product count, discount type/value, duration, optional sales threshold and reroll rules for each phase. Review Display Settings and Status & History. Start only after checking the phases and cron runner. The scheduler creates real campaigns and synchronizes native prices.

Run the scheduler

The module provides a token-authenticated entry point. Use the module cron token from the back-office cron panel:

php modules/mprsalesrevolution/cron.php --token=YOUR_TOKEN --max-tasks=20 --max-seconds=55 --context=cron

https://example.com/modules/mprsalesrevolution/cron.php?token=YOUR_TOKEN&max-tasks=20&max-seconds=55&context=cron

The shared task metadata includes:

Check each task result separately: the overall success of the HTTP response does not mean every task completed. Turning off Enable Campaigns stops new campaigns and rotations; it does not remove discounts already created on products, so check their specific prices.

VAT / B2B Tax

Test address saving and actual tax calculation with your shop configuration before using these defaults. VIES availability and the shared validation package affect the result.

Order & Invoice Numbering

Supported token families include date parts {YYYY}, {YY}, {MM}, {DD}; primary counter {N} with padding such as {NNNNNN}; global and customer counters such as {GLOBAL_N} and {CUSTOMER_N}; and contextual values such as {CUSTOMER_REF}, {PRODUCT_REF}, {SHOP_ID}, {SHOP_NAME}, {CART_ID} and {COUNTRY} where available in that generation context. {DOC_TYPE} is for document formats, not order references. Order generation also refuses {ORDER_ID}, {INVOICE_ID} and {PAYMENT}.

Keep a counter and enough scope/date information for the selected reset mode. The settings validator can reject formats that would cause collisions. Test a new order and invoice before wider use.

Your theme must call the hook. Recommendations are not shown in the checkout summary or order confirmation, and deals are not inserted into category or search grids. The footer carousel shows recommendations rather than limited deals.

Default English headings include More From This Category, Complete your cart, Works Great Together and Recommended Products. Default titles are available in French, German, Spanish, Italian and Polish. The configuration form does not provide fields for editing these four titles.

Use Theme styles to refresh detected values, clear custom values and edit the shared styling controls. For theme CSS, existing classes include .mpr-product-crosssell, .mpr-product-crosssell__grid, .mpr-cart-recommendations, .mpr-cart-recommendations__slide, .mpr-deal-widget, .mpr-deal-progress, .mpr-countdown-bar and .mpr-countdown-bar__discount.

Check Dashboard and Analytics after clicking a recommendation and placing a test order. A conversion is recorded only when the order follows a recommendation click. Frequently-bought-together results need enough order history. Cached fragments reduce repeat work on later page views.

If a block is absent, check its working feature switch, theme hook, eligible products, images, stock/access rules and relevant campaign dates. Do not expect manual pairs in a placement that uses only similar/trending results.

If a campaign widget shows but prices do not change, look at the product's specific prices. A manually saved campaign does not create them; only Dynamic Discounts and Campaign Scheduler do. Check cron task results for stalled schedules. For overlapping promotions, test the cart price; the global stacking settings do not control it.

If VAT-address saving fails during VIES downtime, check Block When VIES Is Unavailable. If numbering settings are rejected, correct the required counter, reset discriminator or unsupported token before saving. Use System Check for module tables and infrastructure.

Before uninstalling, stop rotators/schedulers, end promotions and verify that generated native specific prices have been cleaned up while the module is still available. Turning off campaign rendering alone does not remove native discount rows. Back up module data and numbering records you need to retain.

Disable the module in Module Manager to stop its hooks. Uninstall removes module tables, cron registration, menu and theme integration. Generated catalog discounts remain after their module links are removed, so review catalog prices afterward. Uninstall does not reverse orders or already issued document references.

Requires PrestaShop 1.6.1 or later and PHP 7.1 or later.