Fix Inaccurate Availability Disapprovals in Google Merchant Center

Google’s shopping crawler audits every product landing page behind your ads. When the availability status it finds - in_stock, out_of_stock, or preorder - doesn’t match what you submitted in your feed, Google flags the product under its Misrepresentation policy. On Shopify, this gap appears more often than merchants expect: feed sync delays, inventory policy configuration, and third-party app pipelines can quietly diverge from your actual storefront state before you notice a single disapproval.

What Google means by “inaccurate availability”

Google defines inaccurate availability as any case where the availability attribute in your submitted product data does not accurately reflect what a shopper would encounter on your product page or in your cart. Its Misrepresentation policy states that product data must “match the information on your landing page,” and availability is one of the attributes Google verifies programmatically against your live storefront at crawl time.

The three accepted values are:

• in_stock - the item can be purchased and will ship within your stated timeframe
• out_of_stock - the item is currently unavailable for purchase
• preorder - the item can be purchased now but ships at a future date; the availability_date attribute is required alongside this value

Google’s AdsBot crawler and content verification systems periodically re-crawl your product pages after data is submitted. If your page shows “Sold out,” blocks the add-to-cart action, or replaces the purchase button with a “Notify me” prompt, but your feed still reports in_stock, the product will be disapproved. The reverse is also flagged: submitting out_of_stock for a product that is visibly purchasable on the page is treated as an equal violation.

Why it triggers a suspension on Shopify

Shopify and Google Merchant Center do not share inventory state in real time by default. The availability value Google evaluates depends on when your feed last synced, how Shopify’s inventory policy is configured per variant, and which integration method is in use. Several Shopify-specific patterns reliably produce these mismatches.

Feed sync lag. The Google & YouTube channel app and most third-party feed tools export product data on a fixed schedule - hourly, every six hours, or in some configurations daily. A product that sells out between sync cycles continues to report in_stock in the cached feed until the next export completes. For high-velocity SKUs, this window is wide enough to trigger disapprovals regularly.

Inventory policy set to “Continue selling when out of stock.” If this setting is active for a variant that has zero or negative inventory, Shopify treats the item as purchasable. But if a supplemental feed or a manual feed override separately declares that variant out_of_stock, the two values contradict each other and Google will flag the conflict.

Preorder products without availability_date. A merchant lists a product before it exists in shippable form, sets a future launch date in the description, but submits in_stock rather than preorder. Google’s crawler visits the page, finds no purchasable cart action or no machine-readable ship-date signal, and flags the mismatch.

Multi-location inventory. A product may be in_stock across all Shopify locations in aggregate but not available for online sale from the location fulfilling web orders. If the feed reflects total inventory rather than online-purchasable inventory, the submitted value will not match what a shopper can actually check out.

Draft or archived products in the feed. Products in Shopify’s draft or archived state can appear in some feed exports. Google crawls the URL, finds a 404 or a page with no purchasable state, and disapproves on availability grounds.

How to detect the issue on your store

Establish the exact scope of the problem before making any changes.

In Merchant Center Diagnostics:

1. Go to Products → Diagnostics in your Merchant Center account.
2. Filter by the inaccurate-availability issue type. Note each affected product ID and the availability value Google recorded at last crawl.
3. Click through to the affected product’s item detail to see what the crawl captured.

In Shopify Admin:

• Open each affected product under Products → [product name].
• Under Inventory, confirm the quantity on hand and the inventory policy (“Stop selling when out of stock” vs. “Continue selling when out of stock”).
• Check each variant individually - a single out-of-stock variant within a multi-variant product can trigger a disapproval for the parent item when availability is submitted at the item level rather than the variant level.

On your live storefront:

• Visit the product URL directly and attempt to add the item to cart as a shopper would. If checkout is blocked or the “Add to cart” button is absent, your feed value should be out_of_stock.
• Note JavaScript-rendered availability states: a “Notify me when available” widget that replaces the add-to-cart button signals a non-purchasable state to Google’s crawler even if the product page otherwise looks normal.

In your feed export:

• Download or preview your current feed file and search for the affected product IDs.
• Compare the availability value in the export against the storefront state you verified above. Any discrepancy is the source of the disapproval.

Step-by-step fix

1. Export the full affected SKU list. From Merchant Center Diagnostics, download every product flagged for inaccurate availability. Fix the entire list - not just the most recently flagged items - before requesting re-review.

2. Correct inventory settings in Shopify. For out-of-stock products: in each affected product, set “Stop selling when out of stock” and ensure inventory tracking is enabled with accurate quantities. For preorder products: confirm the expected ship date is communicated on the product page, and plan to add the availability_date attribute to the feed in the next step.

3. Update the feed availability values. If you are using the Google & YouTube channel app: edit and save the affected product in Shopify - this typically triggers a delta sync. Force a full re-sync from Sales channels → Google → Overview if that option is available in your account.

   If you are using a third-party feed tool (DataFeedWatch, Feedonomics, GoDataFeed, or similar):

   • Correct the availability mapping rule for the affected products.
   • Trigger a manual export or refresh.
   • Verify the corrected values appear in the exported file before proceeding to review.

4. Correct any supplemental feed overrides. If you have uploaded a supplemental feed in Merchant Center that manually overrides availability for specific SKUs, update those rows to reflect the current stock state and re-upload.

5. Validate in Merchant Center. Go to Products → Feeds → [your feed] → Processing and confirm the corrected availability values appear without new processing errors.

6. Request re-review. Once corrected values are confirmed live in the feed, go to Products → Diagnostics, select the affected products, and use the “Request review” option where it appears. For product-level disapprovals without an explicit review button, the feed refresh itself triggers a re-crawl automatically - expect resolution within 1-3 business days in typical cases.

What to include in your appeal

For most inaccurate-availability cases, a formal written appeal is not required. Correct the data, trigger a feed refresh, and Google’s automated systems handle re-approval. A written appeal becomes necessary only if the issue has escalated to an account-level Misrepresentation warning, or if product-level disapprovals persist beyond one week after the feed has been corrected.

When submitting a review request, include:

• A screenshot of the corrected product page showing the accurate availability state: the “Add to cart” button visible and functional for in_stock items, or a clear “Sold out” indicator for out_of_stock items.
• A screenshot of Merchant Center feed processing showing the corrected availability attribute value for the affected SKUs with no processing errors.
• A brief factual statement describing the root cause and what was changed. For example: “A scheduled-sync delay between Shopify inventory updates and our GMC feed caused the availability attribute to lag behind actual stock state. We have corrected inventory tracking settings and forced a full feed refresh.”
• Confirmation the fix is structural, not a one-time correction - for example, a reduced sync interval, real-time inventory webhooks, or a feed mapping rule correction that prevents recurrence.

Keep the appeal brief and evidence-based. Google’s review process responds to demonstrated compliance, not explanations of circumstances.

Edge cases & when to escalate

Multi-variant availability granularity. If only some variants of a product are out of stock, you can submit availability at the item level (reporting in_stock when at least one variant is purchasable) or at the variant level using distinct id and item_group_id values. Variant-level submission is more precise and reduces future mismatches from partial stockouts on high-variant products.

Preorder without a confirmed ship date. Google requires availability_date for all preorder products. If a ship date has not been confirmed, submit out_of_stock rather than preorder - a preorder listing without a date may itself trigger a separate policy issue.

Quote-request or contact-form products. Some Shopify merchants replace the add-to-cart button with a “Request a quote” or “Contact us” flow. Google treats these products as non-purchasable. Submit out_of_stock or exclude the product from your feed entirely until a standard checkout path is available.

Inventory management app conflicts. Third-party inventory tools that update Shopify inventory asynchronously can reintroduce availability mismatches after you have corrected them. Audit the full inventory update pipeline - not just the GMC feed export step - to ensure the source-of-truth value remains consistent end to end.

Escalation to account-level Misrepresentation. If Merchant Center Diagnostics shows an account-level Misrepresentation warning rather than individual product disapprovals, the enforcement threshold has elevated beyond product-level fixes. Correct all flagged products first, then submit the account-level reinstatement request. Fixing a handful of SKUs will not resolve an account-level flag on its own, and this level of review typically involves human assessment of your overall store compliance posture.

Frequently asked questions

Frequently asked questions

Does an inaccurate-availability warning suspend my entire account?

No - inaccurate availability is typically a product-level disapproval, not an account-level suspension. Individual products are removed from Shopping ads until the mismatch is corrected. However, a widespread or repeated pattern across many SKUs can escalate to a Misrepresentation policy review, which may result in account-level suspension. Fix all flagged products before the pattern escalates.

How quickly does Google re-approve products after the fix?

After correcting the availability value and submitting a feed refresh, Google typically re-approves products within 1-3 business days in most cases. Requesting a manual re-review via the Merchant Center Diagnostics tab can signal that changes have been made, though the automated re-crawl often processes the correction even without an explicit review request.

My Shopify product has unlimited inventory enabled - should I submit in_stock?

Yes. If Shopify's inventory policy is set to "Continue selling when out of stock" or inventory tracking is disabled entirely, the item is purchasable and should be submitted as in_stock. Use out_of_stock only when the item genuinely cannot be added to cart and completed through checkout. Submitting out_of_stock for an item that is actually purchasable is itself an availability mismatch.

What is the difference between preorder and out_of_stock in the feed?

preorder means the item can be purchased now for future fulfilment - use it when your Shopify product is live and buyable but ships after a future date. You must also include an availability_date attribute specifying the expected ship date. out_of_stock means the item cannot be purchased at all. Google verifies this via your cart: if a preorder item cannot actually be added to cart, it will be flagged as a mismatch.

Can feed apps like Google & YouTube or third-party tools cause this error?

Yes. Apps that cache or batch-export product data can lag behind real-time inventory changes. If a product sells out and Shopify updates inventory to zero, a feed cached several hours earlier will still report in_stock. Review your feed app's sync frequency, and for high-velocity SKUs consider switching to a shorter sync interval or a feed solution that supports real-time push exports via the Merchant API.

Do I need to submit a formal appeal for an availability disapproval?

For most cases, no. Correcting the data and triggering a feed refresh is sufficient - Google's systems re-crawl and re-approve automatically. A formal written appeal is only necessary if the issue has escalated to an account-level Misrepresentation warning, or if individual product disapprovals persist for more than a week after the feed has been corrected and refreshed.

Sources & references

Authoritative sources cited

1. Google Merchant Center policy: Misrepresentation (covers inaccurate availability) https://support.google.com/merchants/answer/6324448
2. Shopify Help: Getting started with inventory https://help.shopify.com/en/manual/products/inventory/getting-started-with-inventory