How to fix unsupported Google Shopping availability

Use the accepted English enum values in the feed even when your store and customers use another language. Keep the meaning consistent with actual purchasing conditions.

Reviewed October 4, 2026 · Independent guidance · Static feed check with contextual limitations

What does this issue mean?

The accepted values are in_stock, out_of_stock, preorder and backorder. Labels such as available, yes, sold out or a translated phrase are not the same machine-readable value. An exact formatting issue such as In Stock is different from an ambiguous business label whose intended state is unclear.

Why this happens

Feed integrations often export storefront labels, inventory counts, booleans or custom stock messages instead of Google’s enum. A number greater than zero is not sufficient to infer every store’s purchasing rules. Preorder and backorder also require attention to expected availability dates, which should be reflected on the public product page.

How to diagnose and fix it

1. Identify the source status and its intended purchasing meaning before mapping an unfamiliar label.
2. Use one of the four accepted values with underscores and the documented spelling.
3. Review preorder and backorder date requirements rather than converting them to in_stock to clear a validation flag.
4. Compare the regenerated attribute to the actual offer page and recheck the feed.

Before and after example

The examples are illustrative. Replace them with verified information for your own offer; copying an example identifier, amount or URL would introduce incorrect data.

Before

<g:availability>In Stock</g:availability>

After review

<g:availability>in_stock</g:availability>

Fix & Export can normalize exact accepted variants such as In Stock, but it will not guess whether available, 1 or yes means in_stock. Landing-page availability matching is not performed.

Shopify fix

Find the affected product and exact variant in your Shopify catalog, then identify which product field or Google & YouTube channel setting supplies availability. If a separate feed app generates your export, inspect its mapping instead of assuming the channel settings control that file. Change verified source data, save it, and obtain a fresh export.

Compare one affected variant and one previously correct offer before making a bulk change. Do not change stable IDs just to improve a report score. If the issue involves identifiers, verify whether the connector reads barcode, brand or manufacturer reference data. If it concerns a live page or shipping account setting, a feed-column edit alone may not resolve it.

WooCommerce fix

Open the relevant product or variation and inspect the attribute consumed by your Google feed integration. Google for WooCommerce can map product attributes into feed attributes; third-party feed generators may use different mappings. Check both the stored value and the exported result, especially when parent attributes are inherited by variations.

Update the source value or mapping deliberately and regenerate the feed. Keep product identity, currency and variant relationships consistent. Avoid editing only a downloaded snapshot if a scheduled exporter will replace that change. For an account or website issue, repair the effective configuration and public offer as well as reviewing the file.

Verify the repair before submitting

Keep the original feed as a backup and compare the same affected product IDs in the regenerated file. Confirm that the expected product count remains unchanged and that no unrelated fields disappeared. If you applied a bulk rule, inspect offers outside the original affected set as a control; an overly broad mapping can fix one problem while creating another.

Run a new static scan, then separately check live product information and your Merchant Center diagnostics. File format validation cannot determine every policy, account, image or website condition. Processing and recrawling take place in Google’s systems, so a corrected file is not an immediate promise of approval. Use the actual updated diagnostics to decide whether additional investigation is required.

Frequently asked questions

Related feed issues

• How to fix missing availability in a product feed
• How to fix missing price in a Google Shopping feed
• How to investigate a product page unavailable error

Official references: Google product data specification, Shopify Google & YouTube requirements, WooCommerce attribute mapping. Requirements can vary by product, country and account setup.