Benjamin Olsen
All topics

Guide

Breakdance Product Meta: Product identifiers and categories where they help

Product identifiers and categories where they help. Learn when to use Product Meta, 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 product metadata such as SKU and taxonomy terms. 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: Product identifiers and categories where they help

Scenario: Product identifiers and categories where they help. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.

  1. Use the current product's real SKU and taxonomy data.
  2. Display only fields useful to the shopper and place them below primary purchase information.
  3. Test a product with no SKU and one with several categories.

Expected result

You should have product identifiers and categories where they help. 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 a blank label remains, handle the missing-field state. Do not hardcode metadata in a shared product template.

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 Product Meta 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