Why Meta Dropped Products from Your Catalog

When Meta drops products from your catalog or stops running them in ads, it's almost always one of five things: the product went out of stock, it's missing a field Meta requires, its identifier is invalid, it isn't in the channel's product set, or your latest feed hasn't reached Meta yet. Work through them in that order.

Where to look: Meta's side and Renable's side#

A dropped product has two possible stories, and it helps to know which one you're in before you start fixing:

• The product left your Renable feed. If it's no longer in the channel's feed at all, Meta simply stops receiving it. This is a Renable-side cause — a product-set scope issue, an exclude rule, or the product dropping out of your source feed. A product is missing from my feed or ads walks through every one of these.
• The product is still in your feed, but Meta rejected or paused it. Here the product leaves Renable fine, and Meta drops it on its own side — out of stock, a missing or invalid field, or a policy problem.

Meta reports the second kind at the item level. Open your catalog in Meta Commerce Manager and go to its Issues tab, which sorts problems into errors (items that can't upload or appear in ads) and warnings, and lets you download a sample of the affected items. Meta moves and renames these views from time to time; its own guide is How to use the Issues tab in your catalog. Each reason below maps back to a Renable fix.

The product went out of stock#

The most common reason a product quietly disappears from your ads is that it went out of stock. An out-of-stock product usually stays in your feed but is marked unavailable, so Meta stops delivering it — it vanishes from ads without being removed from the catalog. That's the correct, expected behavior.

If the product is genuinely in stock and shouldn't have dropped, the availability value in your feed is mapping wrong — a missing or mismatched stock value reads as out-of-stock. Check how your feed's stock or availability field is mapped and correct it. See A field is empty or wrong.

The product is missing a field Meta requires#

Meta's catalog field reference lists nine fields as required for every product: an ID, title, description, availability, condition, price, link, main image, and brand. If one of those is missing or formatted wrong, the item may not upload to your Meta catalog, and the Issues tab names the field that's missing.

Renable calls out missing required fields before Meta ever sees them: the catalog's Mapping tab marks any required field still empty, and the channel's Fields tab warns on required fields with gaps. Fill or map the missing field, then publish. See Mapping your feed fields and A field is empty or wrong.

The product's identifier is invalid#

Meta's catalog fields include a barcode (GTIN — an EAN or UPC) and a manufacturer part number (MPN). Both are optional in Meta's reference, which notes that not every item has a GTIN and asks you to provide one only if you're sure it's correct — so a missing barcode is fine, but a wrong one is worth keeping out of the feed.

Renable helps here before the feed goes out: a barcode whose check digit doesn't match still imports, but the invalid value is dropped before the feed reaches Meta — so Meta never receives a broken barcode. You'll see it as a warning after an import. Fix it at the source or with a rule; the mechanics are in Feed runs, warnings, and tracing a value.

If a product has no valid identifier at all, add one — see Add Missing GTINs, Brands, and Identifiers.

The product isn't in the channel's product set#

A channel only exports the products in its product sets. If a product doesn't fall into any of the channel's sets, it never reaches the feed Meta reads — so it can't appear in your Meta catalog, and there's no error, it's simply out of scope. Open the channel, check its product sets, and confirm the product matches at least one. This is one of the five causes in A product is missing from my feed or ads.

Your latest feed hasn't reached Meta yet#

Two delays sit between fixing a product and Meta showing it again:

1. Publish. Renable only deploys the published version of a channel. If you corrected a field or a rule and left it in a draft, the live feed hasn't changed yet — publish it first.
2. Meta's fetch schedule. Even after your feed updates, Meta re-fetches on its own schedule (often hourly). Your fix won't appear in the Meta catalog until its next fetch.

Confirm your feed itself is current and flowing, then give Meta a fetch cycle. See Keep your feed fresh and, for pointing Meta at the feed and checking it picked up, Connecting a channel to Meta, Google, or TikTok.

Meta rejected the product for a policy reason#

Beyond missing data, Meta can drop a product because it fails a content or commerce policy — for example a disallowed image, a prohibited product type, or a landing page that doesn't line up with Meta's rules. These show in the catalog's Issues tab as items rejected for not complying with Meta's Advertising Policies or Commerce Policies, rather than as plain missing-field errors, and the fix depends on the exact policy. If you think an item was rejected by mistake, Meta lets you request a review. Start with Check your ads are eligible to deliver.

FAQ#

Meta dropped only some products in a set, not all of them — why?

That points to a per-product cause, not a feed-wide one: those specific products went out of stock, are missing a required field, or have an invalid identifier. A feed-wide problem — a publish that didn't happen, or a whole product set out of scope — would drop every product together, not a scattered few.

The product is still in my Renable feed but gone from Meta — where's the problem?

On Meta's side. If the product leaves your channel's feed correctly, the cause is out of stock, a rejected field, an invalid identifier, or a policy issue. Meta's item-level diagnostics name the reason; match it to the section above.

I fixed it, but Meta still isn't showing the product — what now?

Publish the change so it goes live, confirm the product is current in your feed, then wait for Meta's next fetch. Changes stay in a draft until you publish, and Meta picks up feed updates on its own schedule after that.

Or ask Aimée#

You don't have to check each cause by hand. Ask Aimée to trace one product end to end on the Renable side — its import state, which product sets and channels it belongs to, whether a rule excluded it, and how each field resolved — and she'll tell you exactly which step dropped it, or confirm it's leaving your feed correctly so you know the problem is on Meta's side. She can also wait for an import to finish and report back the real counts and warnings.