Conflicting price attributes: price, price range
What causes the "Conflicting price attributes: price [price], price range [price_range]" error and how to fix it.
This error means you've submitted both a fixed price and a price range for the same product, which Google can't reconcile. Fix it by submitting only one: a fixed price for a normal single-price product, or a price range only for genuinely variable-priced items.
What triggers it
This error fires when a single product is submitted with both a fixed price and a price_range, and Google has no way to know which one actually applies. It's almost always unintentional: a feed template, plugin, or export step populating both fields regardless of whether the product genuinely has a price range.
price_range exists for a narrow case: products whose price genuinely varies (for example by configuration) in a way a single price can't capture. For the overwhelming majority of products, a plain fixed price is correct and price_range shouldn't be submitted at all.
/tools's enrichment layer normalises price attributes per product so only the correct one is submitted, without touching your source platform's underlying pricing data.
Step by step
- Identify which attribute the product actually needs. Most products need a single fixed price. Only genuinely variable-priced items (rare: things like custom-configured products) need price_range at all.
- Remove the attribute that doesn't apply. If it's a normal product, drop price_range entirely and keep price. If it's a true variable-price item, drop the fixed price and keep price_range.
- Check your feed mapping for the source of the duplication. This error usually comes from a template or export rule that populates both fields by default rather than a merchant deliberately submitting both.
- Re-submit with a single, unambiguous price signal. Once only one of the two attributes is present, Google can resolve the price cleanly and the conflict clears on the next crawl.