Skip to main content

Filter by Base SKU and Full SKU

Written by Alex Bitca

Ecommerce accounts can filter by two SKU levels across Retently, so you can segment your data at the product level or at the exact variant level:

  • Base SKU matches the product itself (for example MX304). This is the filter previously labeled Product SKU; it was renamed for clarity and works exactly as before.

  • Full SKU matches the complete variant identifier, including attributes like size, color, or width encoded in your SKUs (for example MX304-CLF-SDL-37.5-W).

If the insight you're after lives at the variant level, Full SKU is the filter to use.


Where you can filter by SKU

Both filters are available on the following pages:

  • Dashboard: filter your widgets by a SKU to see how a specific product or variant affects your scores.

  • Feedback page: narrow the response list to a product or variant and read exactly what those buyers said.

  • Trends: build items that track a SKU over time and compare products or variants side by side on a chart.


When to use Full SKU

Use Full SKU whenever the difference you care about is encoded in the variant portion of your SKUs:

  • Do wide-fit buyers rate you differently than regular-fit buyers?

  • Does one colorway drive more negative feedback than the rest?

  • Is a specific size responsible for most sizing complaints?

For example, if your variant SKUs end in -W for wide and -M for medium, you can build two items inside a Trend: one with the rule Full SKU contains -W, another with Full SKU contains -M, and compare them side by side.


How SKU rules work

Wherever you apply the filter, the rule has the same shape:

  1. In the property filter, search for "sku" and choose Base SKU or Full SKU

  2. Pick a condition (such as is or contains)

  3. Enter the value. The value field suggests SKU values from your existing feedback as you type

SKU data comes from your connected Shopify store. These filters appear only on accounts with a store integration that supplies product data with feedback.

Did this answer your question?