When to add condition to a Merchant Center feed
Condition distinguishes new, used and refurbished offers. A missing condition is not automatically an error for a new product, but used or refurbished inventory needs accurate treatment.
Reviewed October 4, 2026 · Independent guidance · Static feed check with contextual limitations
What does this issue mean?
Google’s accepted condition values describe the state of the offer rather than its stock status or packaging style. New is normally the default when the attribute is omitted. For used and refurbished items, omission can incorrectly describe what the shopper will receive. Feed presence checks cannot determine the actual physical condition.
Why this happens
A generic store export may leave condition blank for all products, or a custom field may cover only some collections. Resellers can mix new and preowned stock with the same manufacturer barcode. Inspect condition at the actual offer level and ensure the public page presents the same state.
How to diagnose and fix it
- Identify whether the affected offer is new, used or refurbished based on your actual inventory.
- Use the corresponding accepted enum instead of store-specific descriptions such as excellent or open box.
- Check used and refurbished offers for accurate public-page condition and any applicable Google requirements.
- Regenerate the feed and ensure the condition field remains consistent across future imports.
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
id,condition
CAMERA-USED,After review
id,condition
CAMERA-USED,usedFeed Doctor presents absent condition as an optimization reminder because it cannot infer physical state. Do not change every blank to new merely to make a report look cleaner.
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.
Scan your feed for this issue
Check all parsed products in an XML, CSV or TSV feed. Preview the score and issue samples free; unlock affected-product details and downloadable reports with a one-time payment. Conditional findings remain marked for review.
Check My FeedFrequently asked questions
Does this finding always mean my product is disapproved?
Feed Doctor presents absent condition as an optimization reminder because it cannot infer physical state. Do not change every blank to new merely to make a report look cleaner.
Can Feed Doctor fix condition automatically?
Only deterministic formatting changes are available in Fix & Export. Missing identifiers, prices, business facts and ambiguous values require manual action. Review every change and remaining finding before submitting a repaired feed.
Should I fix the exported file or my store?
Correct the source product or feed integration whenever possible. A downloaded file edit may be overwritten by the next scheduled export. Keep a backup and compare the exact affected IDs in a fresh feed snapshot.
Do I need to connect Google to scan a feed?
No. Feed Doctor accepts a Google-format XML, CSV or TSV file, or a public HTTPS feed URL. It checks the feed without accessing your Merchant Center account. Reports are private to your browser and expire after 7 days.
Related feed issues
- How to fix unsupported product condition values
- How to fix duplicate product IDs in a Google feed
- How to fix missing GTIN in Google Merchant Center
Official references: Google product data specification, Shopify Google & YouTube requirements, WooCommerce attribute mapping. Requirements can vary by product, country and account setup.