
Facebook Catalog Products Rejected: Fix Commerce Manager
TL;DR
Facebook rejects catalog products for Commerce Policy mismatches, missing required attributes, incorrect categorization, or a domain that does not match the verified business. Fix the data feed, request manual review in Commerce Manager, and if approvals stay blocked, escalate under Article 20 of the DSA and the certified out-of-court dispute settlement body in your Member State.
What a Catalog Rejection Looks Like in Commerce Manager
Commerce Manager is the backend that feeds every surface where Facebook sells your products. Ads, Shops, Marketplace listings, and Instagram tagged posts all pull from the same catalog. When Facebook rejects a product, the listing either drops to "Not Available" in the catalog view or sits with a red "Rejected" badge under Issues. The effect is immediate: ads stop serving, product tags disappear, and Shop pages show a smaller inventory than the one you uploaded.
The notice tells you a reason category but not always the exact policy clause it maps to. That gap is why sellers often attempt several edits before the product goes through, often changing fields that were never the problem. A clean fix starts with reading the rejection reason as a category, then matching it to the specific policy requirement before you touch the feed.
The Most Common Rejection Reasons
Meta's Commerce Policies and Catalog requirements list several categories of rejection. The ones that drive most denials:
- Prohibited or restricted products: alcohol, weapons, adult products, dietary supplements, prescription drugs, animals, and digital goods are either entirely prohibited or geo-restricted. A product listed in a market where it is restricted is rejected automatically.
- Misleading claims: before and after images, weight-loss outcomes, medical claims, and exaggerated performance language all trigger rejection under the misleading content clause, even for otherwise policy-compliant products.
- Incorrect categorization: the Google Product Category or Facebook Product Category assigned to a product must match what the product actually is. A category mismatch flags the product for review and often ends in rejection.
- Missing required attributes: every product needs a title, description, image, availability, condition, link, and brand. Products with placeholder images or blank attributes are rejected.
- Domain mismatch: the product link must point to a domain that has been verified for the business. An unverified domain, or a link that redirects through a shortener, triggers rejection.
- Prior Commerce Policy strikes: accumulated strikes on the business account can cascade into blanket product rejections, where the catalog itself is flagged and new products fail review without a specific per-product reason.
Blanket rejections are the hardest case. If every new product is rejected without a specific reason, the block is at the account level, not the catalog level. Fixing individual products will not help. The appeal path there is different (covered below).
Step-by-Step: Fix and Resubmit
- Open Commerce Manager and go to Issues. From business.facebook.com, open Commerce Manager, select the affected catalog, then open the Issues tab. Each rejected product has a reason category attached.
- Match the category to the specific policy. Open Meta's Commerce Policies in a second tab. The reason category in Commerce Manager maps to a named policy section. Read that section before editing anything.
- Correct the source, not the product. If the catalog is fed from a data feed, Google Sheet, or your store's platform, fix the issue at the source. Editing the product in Commerce Manager will be overwritten at the next sync.
- Verify the domain for products with link rejections. Open Business Settings, then Brand Safety, then Domains. If the domain is not listed, add it and complete the DNS or meta-tag verification. Resync the catalog afterwards.
- Request manual review. In the Issues tab, select the corrected product and click "Request review". Meta does not publish a review timeframe for catalog appeals. Submit once and wait.
If manual review comes back with the same rejection and your correction addressed the stated reason, the dispute is substantive, not a correction issue. Submitting the same appeal again rarely helps. The in-app appeal form is designed for clear policy breaches, not for cases where the policy and the product status disagree.
Your Rights Under the DSA and GDPR
Article 17 of the Digital Services Act gives you the right to receive a statement of reasons for each content restriction, which covers a rejected catalog product. The statement must identify the specific policy and explain how it applies to your product. A generic "violates our policy" notice is not compliant with Article 17. You can request a detailed statement of reasons through the in-platform complaint channel.
Article 20 of the DSA requires online platforms to provide an internal complaint-handling system that produces a reasoned decision. For catalog rejections, that means the "Request review" flow in Commerce Manager has to deliver an actual decision on the merits, not an automated rerun.
When internal complaint handling is exhausted and the rejection stands, Article 21 opens a second route: a certified out-of-court dispute settlement body in your Member State. These bodies are certified by the national Digital Services Coordinator and review the dispute on the merits. Contact details for the certified body in your country are published by your national Digital Services Coordinator.
The GDPR adds a parallel route for data-related elements. Product descriptions, images, and business contact details in the catalog are data you control. You have the right of access under Article 15 and the right to rectification under Article 16, enforced through your national data protection authority.
When a Blanket Rejection Signals a Deeper Issue
A single product rejection is usually a feed-quality issue. A pattern of unrelated rejections across a clean catalog is something else. The usual culprits:
- The business account has an unresolved Commerce Policy strike that is cascading into product-level enforcement.
- The business manager itself is restricted, which silently blocks catalog operations even though Commerce Manager appears to load normally.
- The verified domain was dropped during a policy update and needs reverification before any catalog product with that domain can approve.
- The catalog is inherited from a disabled or memorialized account, and the ownership transfer never completed.
In each of these cases, fixing the individual products will not solve the root issue. The restriction operates at the account or business-manager level and needs to be resolved there before Commerce Manager will process new product approvals correctly.
When Professional Recovery Makes Sense
For a rejected product with a clear data issue, the in-app flow is usually enough. Fix the source feed, resubmit, move on. Where the picture changes is when rejections cascade without a specific per-product reason, when the business manager itself is restricted, or when the catalog is tied to an account that is already disabled. At that point you are no longer fixing a feed, you are disputing an account-level restriction.
Professional account recovery uses legal argument under the DSA and GDPR, reaches real human reviewers rather than the automated queue, and succeeds in the vast majority of cases. 96% of cases are resolved within 30 days, with some as fast as ten days. If the account cannot be restored, the money-back guarantee applies.
For the related account-level issues that often underlie blanket catalog rejections, see Facebook Business Manager Disabled: How to Reinstate It and Facebook Business Verification Rejected: How to Resubmit.