RKR Product Dependencies: Selling with requirements and "Add what's missing" for PrestaShop

/ You decide what needs to be done.

/ What happens when it is not fulfilled?

For guests, who have no history, group, or expenditure to verify, you decide whether to treat them as "requirement not met" (the recommended course of action) or as "met."

/ Server-side blocking: cannot be bypassed from the browser

In addition to the on-screen notification, the module checks each item saved in the shopping cart on the server. If a product arrives in the cart through another channel, it is removed, and the customer is notified. This check does not affect the order or payment process, so as not to disrupt the purchase.

/ "Add what's missing": from the notice to the sale

Instead of leaving the customer with a "you can't buy this" message, the notification displays the missing products with their image, name, and price, along with a button to add them to the cart. The requirements are recalculated on the server, and each product is checked to ensure it's active, orderable, in stock, and matches the correct combination. If a required product has options, the customer is taken directly to its product page. If something is unavailable, the customer is clearly informed.

/ Notices in your words, in every language

Each rule can have its own title and message per language, using the rich editor. If you don't write them, the general messages from the "Messages" tab are used. You can insert the product name, the missing products, categories, or groups, the minimum spend, the customer's total spending, and their name. The notification appears on the product page and in the shopping cart, and in listings, a "Requirements" badge with its explanation appears, which can be placed in 9 positions. When a purchase is rejected, the customer sees a dialog box detailing what's missing instead of a generic error message.

/ Test before opening to the public

The simulator evaluates any product against any customer or guest and shows you the results rule by rule. It's the fastest way to validate a configuration and assist a customer who says, "I can't buy." Each rule can have start and end dates, and rules outside of those dates are ignored. From the list, you can activate, deactivate, duplicate, or delete multiple rules at once.

/ Measure how many sales you recover

/ Make the ad look like it's from your store.

There are 23 design themes with live preview, 9 animation effects (pulse, zoom, shake, glow, bounce, appear, flash, side entrance, and light sweep), and adjustments for colors, borders, typography, and shadows. If you need more, add your own CSS or reset the styles with a button. The effects respect the visitor's "reduce motion" preference.

/ Multi-store, multiple languages and migration

Each rule can be used for one store or for all stores. The text is written by language, and the module includes translations into Spanish and English. Export your rules to JSON (with settings and messages) or CSV and import them into another store in two steps: first a simulation, then confirmation. Importing is done by reference, so re-importing updates rather than duplicates, and rules with products that don't exist in the target store are ignored without breaking anything.

/ Try it with sample data

A button installs 5 sample rules built with your own catalog and about 60 days of simulated statistics, all marked as a demo. Removing it only removes that: your actual settings and rules remain untouched.

/ It installs in one minute.

Upload the ZIP file and open "Product Dependencies" in the REQUIRE MODULES menu. This section has three subsections: rules, statistics, and simulator. The default settings are already working; create your first rule, test it in the simulator, and view the product details. A user guide is included within the module. Tested on PrestaShop 1.7.8 (back-office), 8.2 with the Classic theme, and 9.0 and 9.2 with Hummingbird.