Fix “Catalog item rejected: policy violation” on Meta Commerce Manager

The generic policy violation is Meta's vaguest diagnostic. The auto-reviewer applies multiple policies in parallel and surfaces a general rejection when more than one might apply, or when the specific reason isn't suitable for public surfacing. The detail view sometimes carries more information than the summary list.

The triage approach: check image policy first (the most common cause), then restricted-category placement (second most), then title/description content (third), then personal-attributes targeting (fourth). Each rules out a chunk of possibilities.

Image-policy causes typically present as overlay, watermark, generic, or low-resolution issues — the specific image violation is usually easier to spot than the generic rejection suggests. Pull a sample of rejected items and inspect their images first.

The auto-reviewer false-positive rate is high enough that appeals often succeed. If the violation isn't obvious after triaging the common causes, file an appeal with documentation. Account Quality → Restrictions → Appeal. Provide specific information about what the item is and why it should pass each policy. Generic appeals fail; specific ones succeed.

The Audit feature surfaces likely-violations across the catalog before submission, catching the policy issues that would otherwise trigger the generic rejection downstream. Proactive fix is faster than reactive appeal.