Benjamin Olsen
All topics

Guide

Breakdance Cart Cross Sells: Relevant add-ons for products already in the cart

Relevant add-ons for products already in the cart. Learn when to use Cart Cross Sells, follow a practical setup, and diagnose common problems.

2 min read · Updated 30 September 2026

Practice recipe based on public documentation; the Breakdance extension is not installed here.

What it does and when to use it

Displays products suggested alongside items in the cart. Use it for the specific job described below. If a simpler native element can deliver the same outcome, prefer the simpler structure and fewer competing styles.

Before you start

This is a Breakdance catalogue recipe for use with a compatible Breakdance Elements for Oxygen extension. It is not a guarantee of availability in your version. Check the installed element list and official reference before following the steps. Exact control labels can differ; this recipe has not been executed on this site. WooCommerce and appropriate product, cart or checkout data are required. Use staging and a sandbox gateway for purchase-flow tests.

Worked example: Relevant add-ons for products already in the cart

Scenario: Relevant add-ons for products already in the cart. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.

  1. Assign genuine cross-sell products in WooCommerce.
  2. Show the recommendations near the cart without distracting from checkout.
  3. Test a product with assigned cross-sells and one without them.

Expected result

You should have relevant add-ons for products already in the cart. Verify the result on the frontend using the same content or object described in the steps. A correct builder preview alone does not establish that links, data or interactions work for visitors.

Troubleshooting

If irrelevant products appear, review WooCommerce assignments and the element's query behavior. Cross-sells are cart complements; upsells suggest alternatives on a product page.

Checks before publishing

Use real text and assets rather than a perfect placeholder. Check a long label, narrow screen and empty-data state before publishing.

  • Compare desktop and narrow-screen layouts using actual content.
  • Follow every destination and operate interactive controls with a keyboard where applicable.
  • Check an empty or unavailable-data state when the element depends on a provider.

Official reference and version notes

Official Cart Cross Sells reference provides the current provider information. This is independent, AI-assisted documentation on Benjamin Olsen’s website; examples are clearly identified as practice recipes.

Check extension element visibility in Oxygen. An element may be hidden where a native equivalent exists.

Explore more topics