← Reading listCHECK PRODUCT ELIGIBILITY SEPARATELY FOR EACH INTENDED DESTINATION
Text

Merchant Center catalog operations workshop / 5 MIN READ

Check product eligibility separately for each intended destination

Build an item-by-destination matrix separating business intent, exclusions, eligibility and campaign selection.

Published by SNS Media Tech

AI-assisted research and analysis for the SNS Creative Fieldbook

Sources checked 2026-11-07

A product being present in Merchant Center does not establish that it is intended, eligible or selected to appear everywhere. Audit destination controls before interpreting missing delivery.

What you will leave with: Build an item-by-destination matrix separating business intent, exclusions, eligibility and campaign selection.

Use this when

  • An item appears in free listings but not in a Shopping campaign.
  • A team wants to restrict one marketing destination without misreporting stock.

Not a general channel-assortment lesson, a universal ad suppression recipe or a guarantee that eligibility produces impressions.

Write the intended destination policy first

Google documents excluded_destination as a way to prevent products appearing in selected marketing methods or features. The supported destinations have distinct effects, and some controls have caveats. Verify the current documentation for the exact destination and campaign type rather than treating one exclusion as a universal off switch.

Record the commercial intent for each affected item class: where the business wants it represented and where it does not. Separate a lasting assortment decision from a brief campaign pause or a true stockout. These situations may require different supported controls. The policy should name its owner and review date so a temporary media decision does not become an unexplained permanent catalog restriction.

Inspect the processed destination state

For representative items, compare source attributes, transformation rules and the processed product result. A connector or supplemental source may introduce an exclusion that is not obvious in the main spreadsheet. Record the actual source of the final value rather than asking every team to edit its own copy.

Build columns for intended inclusion, explicit exclusions, current eligibility, unresolved issues and country context. Leave unknowns visible. An item approved in one context may still have a problem elsewhere, and an enabled destination does not prove that all policy requirements are met. Use the account's current status evidence rather than translating a generic green indicator into an unsupported claim about every placement.

Trace the handoff into the advertising campaign

Once catalog eligibility is established, ask the media owner to check account links, product selection and applicable campaign filters. Inspect the exact item ID through the handoff. A product may be eligible yet intentionally outside a listing group or excluded by a merchandising label rule.

Keep this stage separate from auction and demand diagnosis. No impressions could reflect a configuration boundary, limited budget, low demand or other delivery conditions. Changing all of them simultaneously makes the cause difficult to identify. Resolve the earliest unsupported assumption first, capture the before state and change only the authorized scope. Do not falsify availability to make an advertising eligibility problem disappear.

Verify exclusions as carefully as inclusions

When a destination restriction is intentional, test that the chosen control covers the actual route in use. Read caveats for related campaign products and record any uncovered path requiring separate action. A control whose name resembles the desired outcome may have a narrower effect than expected.

After release, verify processed destination settings and the relevant campaign selection. Keep business intent and observed delivery in separate report fields. Absence of impressions is weak evidence that an exclusion is configured correctly because the item may simply have received no demand. Conversely, eligibility is not a commitment that the platform will display it. The acceptance condition is that the intended control and selection state are correct, with remaining delivery questions explicitly separate.

Make the reasoning concrete.

A fictional stationery merchant sees a notebook in free listings but not in paid Shopping. The catalog is accurate; a supplemental rule excludes Shopping ads for the notebook’s label group.

Change stock status

Opening: Mark the notebook unavailable and upload it again.

Hypothesis: The team creates a visible catalog change.

Risk: The stock fact becomes false and the destination rule remains unexplained.

Trace destination and selection

Opening: Inspect the processed exclusion and confirm whether the business still wants it.

Hypothesis: The owner can correct the actual restriction if authorized.

Risk: Eligibility still does not guarantee paid delivery.

The teams resolve the destination policy and campaign selection without altering truthful stock data. They report eligibility separately from later impressions.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

  1. Intent

    Where should this item be allowed to appear, and why?

  2. Source

    Which rule supplies the final destination control?

  3. Eligibility

    What does the current item status show for each context?

  4. Selection

    Does the intended campaign actually include this item?

  5. Caveat

    Which documented limitation affects the chosen exclusion?

Watch for the wrong conclusion.

  • Assuming free-listing visibility proves paid-campaign eligibility.
  • Using false stock values as media controls.
  • Treating zero impressions as proof an exclusion is correct.

Your next action

Trace one missing paid item from destination intent through processed settings and campaign selection.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis, not Google instructions or measured business results. Sources support only the specifically attributed platform facts. Platform controls and eligibility can change; verify current account guidance before implementation.