:quality(75))
On November 12, 2024 Adobe shipped a fix to the Product Recommendations category filter: it now respects store-view boundaries. If you run a single store, this was never your problem. If you run several, it probably was.
What was wrong
Multi-store merchants configure different product assortments and pricing for different regions or brands. The category filter in Product Recommendations was not scoping its lookups to the active store-view, so recommendations could include products from a sibling store — items the customer in front of them could not actually buy.
Picture a retailer running European, US and Asian storefronts on different assortments. A shopper on one gets recommended something stocked only on another, clicks through, and hits a dead end.
What the fix does
The filter now interprets store-view context correctly, and recommendation queries are scoped to the active store-view. No cross-store contamination.
Applying it
It arrives through the standard Product Recommendations updates, so the job is making sure you are on the current version. The change is backward compatible and needs no configuration.
Afterwards, walk each store-view and check that what is recommended is genuinely purchasable there. It is a short test, and it tells you the fix has taken effect on your data rather than just in the release notes.
Recommendations only earn their place when what they surface is relevant and available. This one is worth confirming rather than assuming.