Where availability usually diverges
Availability mismatches often come from variant defaults, stale JSON-LD, feed exports that run on a schedule, preorder/backorder rules, or app snippets that do not update when inventory changes.
Visible stateCheck the product page near the purchase button, variant selector, and sticky cart bar.
Structured stateInspect Product/Offer availability and confirm it matches the selected or canonical variant.
Feed stateCompare the feed or catalog export against the page and inventory source.
Variant stateMake sure the default variant, URL variant, and displayed stock message describe the same offer.
Cache timingAccount for storefront cache, feed refresh timing, and theme app extension delay.
What ProductProof checks first
The free scan checks the public page and structured data availability signal. A paid audit can group repeated availability risks across products and templates.
Best first fix
Use the same inventory source for visible stock messages, schema availability, and feed exports. Rescan after inventory sync and cache clear.