How to fix unsupported product condition values

Use new, used or refurbished in the machine-readable feed. Map detailed merchandising labels only after confirming the real condition of the offer.

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

What does this issue mean?

Condition has a small accepted enum. Labels such as brand new, preowned, like new or renewed may be useful store descriptions but are not the exact submitted values. Mapping is a business decision when the terms imply different meanings; capitalization of an already accepted word is a narrower formatting problem.

Why this happens

Invalid values often come from exporting a storefront label or a supplier quality grade directly. A mixed catalog may require collection-specific mappings rather than one default. Physical condition and availability must also remain separate: out_of_stock is not a condition value, and refurbished does not tell shoppers whether the item can ship now.

How to diagnose and fix it

1. Review the source condition labels and identify their actual meaning for the offered inventory.
2. Map each supported business condition to new, used or refurbished according to the applicable Google guidance.
3. Normalize capitalization only when the underlying value is already an accepted enum.
4. Compare the final condition to the product page and verify that the next export retains the mapping.

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:condition>Used</g:condition>

After review

<g:condition>used</g:condition>

Fix & Export can normalize exact accepted words to lowercase. It will not guess whether open box, grade A or renewed should mean new, used or refurbished.

Shopify fix

Find the affected product and exact variant in your Shopify catalog, then identify which product field or Google & YouTube channel setting supplies condition. 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

• When to add condition to a Merchant Center feed
• How to fix unsupported Google Shopping availability
• How to fix missing product descriptions in Merchant Center

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