To add a badge to specific products on Shopify, define the audience before designing it. A five-product promotion should not drift onto fifty, and an existing collection should not be duplicated as a manual list.
This guide covers product, collection, and tag targeting in LumenCanvas, the current plan boundary for advanced conditions, match calculations, and positive and negative product tests.
TL;DR
- Hand-pick products for a small, stable set. It is the clearest first test and avoids a rule matching more products than you intended.
- Use a collection when merchandising already defines the group. The badge then follows products represented in that indexed collection instead of a duplicate manual list.
- Use a tag for an operational flag you maintain consistently. Choose a specific tag such as launch-2026 rather than a vague label that is reused for unrelated work.
- Calculate, test, preview, and verify before widening the audience. A match count and editor preview are planning checks; the published storefront is the final evidence.
Choose product, collection, or tag targeting
Use the source of truth your team already maintains: specific products for an approved short list, a collection for a merchandising set, or a tag for a durable catalog flag. Every extra condition creates another way to exclude the wrong item.
| Targeting method | Use it when | Maintenance risk | First verification |
|---|---|---|---|
| Specific products | The set is small and stable | New products need manual selection | Compare the picker with the brief |
| Collection | A collection represents the promotion | Membership can change | Open one member and one non-member |
| Tag | A stable tag marks eligible products | Typos or reuse change the audience | Inspect two opposite test products |
Choose the rule that already has a reliable owner instead of creating a second catalog system.
Add a badge to specific Shopify products first
For a controlled first campaign, open the label editor, go to Products, and choose Specific products under Apply to. Use the product picker to select the exact items, then review the selected count. This mode is useful for a short launch list, a correction on one product, or a small promotion whose membership is approved outside Shopify.
Specific-product targeting is available on Free. The current contract allows up to 50 manually selected products per label on Free and Starter; Pro removes that plan cap. Use a collection or tag when the list changes frequently.
Target Shopify badges by collection
Choose Products matching conditions, then select the campaign collection. Collection targeting is available on Free and suits seasonal, new-arrival, or other maintained sets. The collection remains the catalog source of truth instead of being copied into the badge configuration.
Check how Shopify maintains the collection. Manual and automated collections can change for different reasons; LumenCanvas reads indexed membership rather than replacing Shopify's collection logic. Record one member and one non-member for the storefront test.
Target Shopify product labels by tag
Tags are useful when your catalog process already applies a stable operational flag. In Products matching conditions, enter the intended product tags as a comma-separated list. Tag targeting is available on Free, and matching is case-insensitive in LumenCanvas. Within that tag condition, a product carrying at least one entered tag can satisfy the condition.
Prefer a precise tag such as spring-launch-2026 over a reused word such as featured. Confirm who removes it and when. A tag is a targeting input, not evidence that a discount or policy claim is true.
Decide whether all or any conditions must match
All conditions requires every configured condition; Any condition requires only one. With Summer collection plus clearance tag, All matches their intersection, while Any matches both groups. That switch can turn a small campaign into a much larger one.
Write the rule as a sentence
Write the rule in plain language using AND or OR before touching the switch. Keep the label in Draft if that sentence is ambiguous. All is the narrower starting point; use Any only for genuine alternatives.
Know the current LumenCanvas plan boundary
Each condition has a minimum plan. Free includes all-products, specific-products, collection, and tag targeting. Starter adds vendor, minimum or maximum price, created-after date, and published-after date conditions. Pro adds product-type and discounted-product conditions. Mixed rules need the highest tier; LumenCanvas fails closed rather than silently dropping a paid condition and widening the audience.
| Plan | Targeting available | Important boundary |
|---|---|---|
| Free | All products, specific products, collection, tag | Manual selection is capped at 50 products per label |
| Starter | Free methods plus vendor, price, created date, published date | Product type and discount remain unavailable |
| Pro | Starter methods plus product type and discount | A truthful offer and live-theme check are still required |
Plan names describe the current feature contract, not a promise that pricing or limits will never change.
Calculate matches before you publish
Calculate matches reports matching indexed products against the indexed total. Zero can reveal a typo or empty index; a large result can expose Any condition, a broad tag, or changed collection. It is a scope check, not storefront proof, and it does not measure campaign performance.
- Write down the expected order of magnitude before calculating. A five-product launch should not surprise you with hundreds of matches.
- Run Calculate matches and compare the result with the campaign brief, collection membership, or tag audit.
- Use Test rule with a known product and read the per-condition result instead of guessing which clause failed.
Check product-index freshness
Calculations use LumenCanvas's local product index. If Settings shows Not synced, Syncing, or Failed, resolve it before trusting a count; a genuinely empty store can show Ready with zero. After a bulk catalog change, wait for sync and calculate again.
Test a matching and non-matching product
Choose two products before publishing: one that must display the badge and one that must not. Prefer similar templates so the test isolates targeting. Never assume exclusion works because the positive case passed.
- Select the expected matching product in the preview and run Test rule. Confirm the overall result and each condition.
- Select the expected non-matching product and run the same test. Confirm which condition excludes it.
- Recalculate the total after changing All to Any, editing a tag, or changing the selected collection.
- Keep the element in Draft if the test result, match count, product data, or plan gate is not what the campaign owner expected.
Preview desktop and mobile without treating preview as proof
Use the relevant Product page and Product listing previews, then switch between desktop and mobile. Check for covered details, collisions, unreadable wrapping, or competition with price and purchase controls. Preview the actual matching product.
Preview is not a guarantee of pixel-identical placement on every Shopify theme. Theme markup and responsive behavior affect the final page. Keep text concise and readable, and never use color alone for eligibility.
Publish, verify the storefront, and keep a rollback
- Confirm the LumenCanvas app embed is enabled and saved on the live theme. App embeds are controlled through the theme editor and do not require editing theme code.
- Save the label as Active only after its copy, plan availability, match count, positive test, negative test, desktop preview, and mobile preview pass.
- Open the live matching product in a fresh storefront session and verify the badge, price or claim, placement, and any linked destination.
- Open the live non-matching product and verify that no stale or misplaced copy of the badge appears on its product page or relevant listing.
- Record the campaign owner and review date. Recheck after collection rules, tags, prices, themes, or product templates change.
Stop or roll back when evidence disagrees
Switch the element back to Draft if targeting, storefront layout, the offer, or a plan gate disagrees with the campaign. Do not remove a condition merely to force publication. Correct the data or rule, sync, calculate matches, and repeat the positive and negative rule tests and desktop and mobile previews while in Draft. Once they pass, save as Active, then verify the matching and non-matching products on the live storefront. Return to Draft if either live check fails.
Frequently asked questions
Can I add a badge to only one Shopify product?
Yes. Choose Specific products, select it, run positive and negative checks, then verify the live theme after activation.
Should I target a Shopify collection or a product tag?
Use the source your team already maintains: a collection for a merchandising group or a tag for a stable catalog flag.
Why is my LumenCanvas match count zero?
Check index status, collection or tag data, All versus Any, and the per-condition Test rule result.
Are collection and tag targeting available on the Free plan?
Yes. Vendor, price, and date need Starter; product type and discount need Pro under the current contract.
Does a correct preview guarantee the badge will appear on every theme?
No. The active theme is the final test. Check matching and non-matching products on desktop and mobile.
Shopify sources and further reading
- Shopify Developers: Product object fields and relationships
- Shopify Developers: Collection object and product membership
- Shopify Developers: Products query and supported search filters
- Shopify Developers: Theme app extension and app embed configuration
Start with one narrow targeting rule
A reliable Shopify product label targeting workflow repeats the same checks: define, calculate, test both sides, preview, and verify. Review the LumenCanvas product page for the current workflow, or use the product labels vs badges guide to choose the right storefront element before targeting it.
Ready to test one controlled audience? Install LumenCanvas, keep the first label in Draft while checking its rules and desktop and mobile previews. Once those checks pass, save it as Active, then verify matching and non-matching products on the live storefront. Return it to Draft if either live check fails.