Seller Plus module by categories, brands, and date ranges

v1.5.02026/11/07

Show part of the following product

• New carousel option: "Show part of the next product" (carousel tab). The edge of the next product is visible, so you can see there's more as you swipe. The arrows still advance through entire columns.
• If all the products fit on the screen, nothing will be visible.
• After updating, it comes off: the carousels look like before.

v1.4.12026/11/07

"Current Manufacturer" also works on hook carousels

• A carousel placed in a hook with Manufacturer: Actual used to display the best-selling items from a brand's entire store on its page; the brand name only appeared in shortcode carousels. Now it uses the brand name of the currently viewed page.
• Outside of a brand page, it remains the same as before (all brands), so as not to empty carousels that are already set up that way.

v1.4.02026/11/05

[sin destacar]

Two products per view on mobile, and columns per screen that are respected

• New option, "Maximum columns on screens < 576" , 2 by default. Below 576px the carousel had no adjustment and always displayed one product.
• "Maximum columns on screens >= 576" already does what it says. That section was using the value of 768 and the adjustment was useless.
• Upon updating, the carousels remain at their current resolution between 576 and 767 px: a factory setting of 1 retains the previously displayed value; any other value is preserved. The mobile device then displays two products, or one if the carousel requests a single column on the next screen.

v1.3.62026/11/05

No operational changes: a redundant check when reading the expiration of saved rows, which the PrestaShop Addons validator flagged as a PHPStan error.

v1.3.52026/10/27

Swiper is no longer included in the JS package of all pages

The module registered its copy of Swiper (143 KB) on all front pages as soon as there was an active carousel, even if that page did not display it; in a store with other carousels (easycarousels, RKR Relational) three copies ended up in the final JS, and PageSpeed counts it as blocking time.

• Swiper is only requested where a carousel is displayed , and if the page already has one (EasyCarousels, the theme, or another Rekire module), that one is used . The module's Swiper is only used when there isn't one, and only once.
• The carousel waits for Swiper to exist before starting (with a theme that loads the final scripts after the first painting, it said "Swiper is not defined").
• Native lazy image loading ( loading="lazy" ) instead of that of Swiper 8, which does not exist in Swiper 9+.

v1.3.42026/10/07

Fewer inquiries when painting the carousel on the cover

The ranking was already being saved, but assembling the eight products with ProductAssembler required about five queries per product —price, offer, taxes, stock, quantity in cart, and group discount—on each load. Measured on a copy of the Rekire website, the homepage went from 67 to 30 module queries (12.8 ms SQL to 5-8 ms) and the carousel hook from ~93 ms to ~30-50 ms.

Now, the pre-built data is reused, but only for anonymous visitors with empty carts . An identified customer, or one with items in their cart, follows the same path: their price and availability remain the same. The presenter, images, template, and hooks of other modules that depend on it are still calculated live for each visit.

The saved data becomes invalid as soon as any monitored element changes, with a single query per load: the modification date, price or product status, stock level, and current offers (these elements update immediately upon the start or end of a sale). This information also depends on the store, language, currency and exchange rate, country, product group and its discount, and the day. Unmonitored data (such as VAT rates or category discounts) expires after 5 minutes . This data is stored in var/cache/ /rkrselledplus/ and it is emptied when you clear the PrestaShop cache or uninstall it.

Optional setting, no display: The RKR_SELLED_PLUS_ROWS_TTL key in Configuration sets the expiration time in seconds ( 0 disables it). Nothing is saved when PrestaShop debug mode is active.

v1.3.32026/09/29

The settings screen is now a setting

Clicking "Configure" in the module used to display a banner with a link to the carousel list, and nothing else: no fields . Now, that screen also includes the three global settings—use only products from the order table, the number of minutes a ranking is saved, and the number of days of visit history—and these can be changed and saved right there. These are the same options and the same settings as the carousel list: it doesn't matter which of the two screens you access.

The PrestaShop Addons compatibility report requested it, returning "Attempts to access the module configuration page failed" in PrestaShop 9.0.0. Reproduced on a real 9.0.0 , in debug mode: the page opened, gave HTTP 200 and did not throw any error - it simply had nothing to configure.

Corrected

• The settings screen can no longer remain blank. If the link to the listing cannot be built— getAdminLink() returns an empty string outside of a back-office request, and the object that generates it may not exist—the screen displays a warning message instead of crashing. Previously, any failure there was simply seen as the settings "not opening."

Checked

Install, open the configuration with its fields and save in PrestaShop 1.7.6 , 1.7.8.11 , 8.2.8 , 9.0.0 , 9.1.5 and 9.2.0 .

v1.1.32026/03/17

• New Best Sellers Carousels by period, category and brand, in more than twenty positions of the theme or within your pages with a shortcode.