01
Feed generation or scheduled fetches lag behind live inventory
Product-data issue
Availability mismatches often appear when stock changes faster than product exports, variants use different defaults, or structured data does not match the visible purchase state.
What can cause it
These are investigation paths, not a claim about Google's hidden reason for your account or item status.
01
Feed generation or scheduled fetches lag behind live inventory
02
Variant-level stock is collapsed into one parent product value
03
Structured data contains a stale or differently mapped availability value
04
A product page is reachable but cannot actually be purchased
What MerchantProof examines
We inspect the sampled feed status and product or item-group identity.
We look for customer-facing stock messages and basic add-to-cart availability on the public destination.
We compare supported product markup with the visible page and record extraction limits explicitly.
Choose one inventory source of truth, then verify that feed generation, structured data and the customer-visible purchase state update from it consistently.
Evidence to prepare
Technical files are optional when they are unavailable. MerchantProof asks only for evidence it cannot collect safely from the public store itself.
MerchantProof Diagnostic
£99
£99 total · one-time · no subscription
MerchantProof does not continuously monitor inventory and cannot validate stock held only in a private system. The included rescan is a bounded point-in-time recheck.