Related products that fill themselves, and a way to check they help
Most related product blocks are empty or out of date because someone has to fill them product by product. Rules can do the filling; a simple test tells you whether it was worth it.
We use necessary cookies to make this site work. With your permission we also use Google Analytics to understand how the site is used and Google Ads cookies to measure which of our ads lead to purchases. You can accept all cookies, reject the optional ones or choose which ones to allow. Cookie policy
Choose which cookies you allow. Necessary cookies are always on because the shop cannot work without them. You can change your choice at any time with the "Cookie settings" link.
Needed for the basket, checkout, login and security. They do not track you.
Google Analytics: how many people visit, which pages they read and how they found the site. It sets the _ga cookies and sends usage data to Google.
Google Ads: measures which of our ads lead to a purchase. It sets the cookies _gcl_au and _gcl_aw (90 days) and, when you buy, sends Google the order details and a hashed form of your contact details for matching. See our cookie and privacy policies.
Arrange Magento category products using sales, stock, margin and conversion signals. Review the proposed order, pin campaign products, preview the storefront and apply or revert the change. Numerical scoring works without external AI.
One-off payment, with 12 months of updates.
No subscription or automatic renewal. Keep using the versions included in your update period. Update and licence details
Composer package commercegears/module-ai-merchandising
The category order that worked at launch may now hide a strong seller behind unavailable products. AI Merchandising & Category Optimizer makes that review practical: collect the evidence, propose a new order, inspect the storefront and publish the arrangement your team chooses.
Analyse a category over 30, 60, 90 or 180 days using supported sales, revenue, refunds, salable stock, margin, views, conversion, cart and wishlist signals. Relevant child activity contributes to the parent. Missing costs and views are flagged rather than treated as evidence of poor performance.
The configurable numerical score works locally without an external AI request. Rules can move unavailable products down, give new products exposure and preserve pins. Findings help identify a hidden bestseller, a high-refund item or a heavily viewed product that deserves a content or price review.
The proposal shows current and proposed positions with Why here? explanations. Drag or move products, pin a campaign item and preview the first pages. A temporary signed link shows the proposal on your real Luma or Hyvä category page without caching the preview.
Approve & Apply writes normal Magento category positions and records the previous arrangement. History provides reversion for the latest live application. If category membership changed after analysis, a new analysis is required. Anchor-category application can add direct product assignments; reversion handles those additions.
Run single-category analysis, queue larger selections or enable nightly analysis for selected categories. Fresh proposals wait for review unless you explicitly enable auto-apply. The optional AI layer reviews a configured product summary and writes additional explanations; responses are validated and failures fall back to the numerical order.
Magento Open Source or Adobe Commerce 2.4.7–2.4.9, PHP 8.2–8.5, CommerceGears Core and AI Core. Product-view collection is needed for conversion signals; product costs are needed for meaningful margins. Luma and Hyvä storefront preview are supported.
Positions are global across store views, and the result is not personalised per shopper. Very large categories can make the proposal slow to render. The potential-uplift indicator is not a revenue forecast. Use a representative category and compare actual trading journeys after a reviewed change.
Read the AI Merchandising guide or open the admin demo to inspect the proposal, preview and history workflow.
Try the admin demo. Storefront examples are available on the Luma demo and Hyvä demo. Demonstration or offline-test data shows the workflow; evaluate AI matching and forecasts with your own representative catalogue.
No. Analysis creates a proposal. The storefront changes when an authorised user applies it; optional auto-apply is off by default.
The scoring and review workflow work without AI. The optional explanation/review layer uses your configured provider key and budget through CommerceGears AI Core.
No. Magento category positions are global. The analysis scope can vary, but applying writes positions shared by store views.
History lets you revert the latest live application to its previous positions. Revert newer applications first. Added direct assignments for anchor categories are also handled.
No. It is a placement-weighted score indicator. It does not predict or guarantee additional revenue.
Best sellers below the first page, products without sales or out of stock on the first page and products with low conversion are found and moved, with the reason for every position.
Nothing changes on the storefront until you click Approve & Apply. The previous positions are saved, and History restores them exactly with Revert.
The order comes from a transparent score with weights you set. Switch on the optional AI layer to have a model review the top products; any problem falls back to the score order.
All features
Live demo
A full Magento store with the module installed, on Luma and on Hyvä. The admin demo signs you in with one click.
Compatibility
| Magento | 2.4.6 – 2.4.9 |
|---|---|
| Platforms | Magento Open Source and Adobe Commerce (one price) |
| Storefront themes | Luma Blank Hyvä |
| PHP | 8.2 – 8.5 |
| Latest version | 2.0.5 |
| composer.json requires | php ~8.2.0||~8.3.0||~8.4.0||~8.5.0 ext-json * magento/framework ~103.0.6 commercegears/module-core ^2.0 free, installed by Composer with this module commercegears/module-ai-core ^2.0 free, installed by Composer with this module magento/module-backend * magento/module-catalog * magento/module-catalog-inventory * magento/module-config * magento/module-directory * magento/module-indexer * magento/module-sales * magento/module-store * magento/module-ui * magento/module-url-rewrite * magento/module-user * |
Installation
After you buy, create a Composer key in your account. Then, in the root of your Magento project:
01Add the repository and your key (once per project)
composer config repositories.commercegears composer https://repo.commercegears.com composer config --auth http-basic.repo.commercegears.com PUBLIC_KEY PRIVATE_KEY
02Install the module
composer require commercegears/module-ai-merchandising
03Enable it
bin/magento setup:upgrade bin/magento setup:di:compile bin/magento setup:static-content:deploy bin/magento cache:flush
The last three are only needed in production mode.
Prefer a zip? Every version you are entitled to can be downloaded from My modules. More about Composer access
User guide
The user guide has its own page: how to install AI Merchandising & Category Optimizer, what each option does and how to use it in your store. Written for version 2.0.5; a copy ships with the module.
Changelog
FAQ
Something else on your mind? The developers who wrote the module answer before and after you buy.
Ask a question →Already installed it? Open a support ticket
No. The module works fully without AI, with a score from your own sales data and the weights you set. The AI layer is optional: set up a key in CommerceGears > AI Providers & Costs and switch on Use AI in the AI Merchandising settings.
No. An analysis only creates a proposal. Nothing changes on the storefront until you click Approve & Apply. Nightly analyses also wait for your review, unless you switch on Auto-apply (off by default).
Yes. The previous positions are saved with every apply. History lists every apply with Revert, which restores the previous order exactly. Only the newest live order of a category can be reverted, so revert newer ones first.
An anonymised summary of the category and its top products. No customer data is sent, and costs and margins only when Share Margins with AI is switched on.
Magento must collect product views: Stores > Configuration > General > Reports > General Options > Enable Reports = Yes and Product View = Yes.
Fill in the Cost attribute (Advanced Pricing) for margins. Products without a cost show "margin unknown" and count as the category average.
No. Category positions are the same for all store views in Magento, so an applied order is used by every store view.
Magento Open Source and Adobe Commerce 2.4.6 to 2.4.9 with PHP 8.2 to 8.5 (Magento 2.4.6: PHP 8.2), Luma and Hyvä. Multi-Source Inventory is optional.
Support
From the blog
Most related product blocks are empty or out of date because someone has to fill them product by product. Rules can do the filling; a simple test tells you whether it was worth it.
Customers describe what they need, not always what your catalogue calls it. See 12 example searches and how semantic search works alongside Magento's existing results.
Bring selling, availability and margin into the category order. Review a proposed arrangement, protect campaign positions and keep a route back to the previous order.
See what may run out, what to buy and which slow movers deserve review. Forecasts run locally; optional AI explains the numbers rather than replacing them.
No sales can mean no demand, or no stock. Alert requests help separate the two, provided you treat them as interest rather than guaranteed orders.