← All disapproval codes
warning availability mismatch

Availability mismatch with landing page

What this means

Your catalog says in_stock but Meta's crawler found out_of_stock on the landing page (or vice-versa). The product gets de-prioritized.

Why this happens

Slow feed refresh — your storefront updated availability hours ago, but the catalog still has the old value.

How to fix it

  1. Increase feed refresh frequency to hourly for fast-moving SKUs, or use Meta's API for real-time updates.
  2. Add structured data (schema.org/Offer with availability) to landing pages.
  3. Make sure availability values match exactly (in_stock, out_of_stock, etc.)

Common pitfalls