New Feature: Product mappings has evolved into Recommendations
Product mappings is now Recommendations, and it does considerably more than pair one product with another. Each side of a recommendation can be specific products, a tag, or a collection, so a single rule can cover a whole slice of your catalogue and keep working as that slice changes.

What you can build. Pick what has to be in the cart, then pick what to recommend. Either side can be products, tags or collections, in any combination:
- Camera body → products tagged
camera-accessory. One rule picks up every accessory you tag, without you listing them. - Anything tagged
winter→ the Scarves & Gloves collection. A seasonal trigger pointing at a collection you already curate. - Anything in the Snowboards collection → one wax kit. A whole collection driving a single add-on.
Tag and collection recommendations are resolved live at checkout, so newly tagged products and collection changes are picked up with no edit from you.
Sell more of what you detect. Using the same tag on both sides is a
good rule, not a mistake: "anything tagged candles → recommend from
candles" shows a shopper the rest of your candles. The product that
triggered the recommendation is filtered out of its own results, so the
shopper only sees something new, and the component still fills to your
product count however much of the cart carries that tag. The same works
with a collection on both sides.
Nothing to redo. Your existing mappings carry over as recommendations and read as products to products, exactly as they behaved yesterday. A CSV exported before today still imports. Recommendations is in the same place in the navigation, and on a component it is the product source of the same name.
Where it runs. Products to products runs on every surface, including post-purchase. As soon as either side uses a tag or a collection, the recommendation runs on the Checkout Upsell extension only, because post-purchase and the legacy Checkout Components extension do not read product tags or collection membership. Components on those surfaces show their configured fallback, and the app tells you whenever that applies.
Plan availability. Recommendations are available on the Growth plan and above.
No action is needed on your end.