Product-feed audit example: when in-stock products are excluded from Shopping
Diagnostic finding: Anonymised product-feed review work identified a rule that marked some in-stock variants with excluded_destination = Shopping ads. Those variants were deliberately excluded from that destination even though their product and inventory data appeared otherwise sellable. The important first question was not “How do we switch the rule off?” but “Who owns this exclusion and what commercial purpose does it serve?”
Evidence status: This is a generalised methodology example informed by an actual feed review. Merchant identity, item examples, exact counts and performance metrics have been withheld. It is not a claimed client success story, and no campaign uplift or approved reinstatement is asserted. Keep this post in draft until the project owner approves anonymised public use.
Why can in-stock products be absent from Google Shopping ads?
Product eligibility depends on more than an in-stock flag. Merchant Center may accept a product for a destination while a feed field, rule or source-level selection excludes it from another destination. Exclusion may be intentional: for example, to prevent low-margin items entering paid campaigns or to honour a merchandising decision.
That is why a technical audit must reconcile feed data with the merchant’s commercial strategy before changing an exclusion rule.
What we inspect first
- Identify the affected destination. Confirm whether the problem concerns paid Shopping ads, free listings or both.
- Trace the exclusion field. Check whether
excluded_destinationcame from the source feed, a supplemental source, a feed rule or an integration. - Check the selection logic. Compare product groups, variants, labels, vendor and stock before assuming a mistake.
- Compare unaffected siblings. Look for sizes or colours in the same item group that remain included.
- Find the commercial owner. Ask whether the rule is tied to margin, returns, availability, advertising priorities or previous tests.
- Plan a controlled change. Test on a limited sample, watch product eligibility and confirm that the result matches the merchant’s intention.
Why the variant level matters
A parent product can look healthy while individual variants are suppressed. An audit that only counts parent products may therefore understate the scale of an issue. Variant-level comparisons can expose mixed treatment within the same product group.
Key dimensions to check include product ID, item group ID, variant description, stock, destination status, custom labels and the latest processing timestamp. Where permitted, advertising performance and margin data can help prioritise investigation, but correlation alone does not prove why the rule was introduced.
What should not be concluded from this finding?
- That all excluded products should immediately be activated.
- That the excluded products were necessarily eligible under every Google policy.
- That the suppression was a Merchant Center error rather than an intentional business rule.
- That restoring eligibility would automatically improve return on ad spend.
How an evidence-led feed audit is different
A useful audit does more than list missing attributes. It explains the source of a rule, affected inventory, potential commercial consequences, dependencies and safest next test. That makes the output actionable for marketers, ecommerce managers and developers.
Google Shopping and product data
Need to know why products have disappeared?
We can investigate the source feed, transformation rules, destination exclusions and Merchant Center diagnostics before recommending changes.
For the wider service, see Merchant Center and feed consultancy.
Background: Google Merchant Center: excluded destination attribute. Always verify current attribute requirements and account setup before applying any rule.