Why a product with no price or a zero price is rejected

What the error means

A product with a missing price, or a price of zero, is rejected. There is no partial credit.

Why Google rejects it

Shopping is a commerce surface. An item with no price cannot be bought, so it cannot be listed.

How to fix it

1. Set a price above zero on every variant, not only the default one.
2. Check placeholder and coming-soon products, which frequently sit at zero.
3. Make sure the price on the page matches the price in the feed. A mismatch is a separate and very common rejection.

A typical case

Draft and coming-soon products published at $0.00 are the usual source. They sit in the catalogue invisible to shoppers but fully visible to Merchant Center. Delete the drafts or set real prices before the next sync.

Common causes

Price field is empty or malformed

The product record may omit price, contain text instead of a number and currency, or use an unsupported currency code. A value that looks acceptable in the storefront can still be malformed in the feed. Check the processed Merchant Center value and the source field mapping.

Default variant has no purchasable price

A product may show a starting price in the catalog but its submitted variant has no price, a zero placeholder, or an option that cannot be purchased. Inspect the exact item ID and variant in the feed, then test that selection through checkout.

Feed price differs from page or checkout

A sale, tax setting, currency conversion, or automatic discount can cause the feed, landing page, and checkout to show different amounts. Google requires the submitted amount and currency to match the page and checkout requirements. Compare one country and one variant at a time.

Price is a placeholder for unreleased stock

Coming-soon items and drafts may be published with a zero or token price so the page template can render. If the product cannot be bought at that amount, the feed is not describing a real offer. Keep unpublished products out of the channel until they have a valid offer.

Zero is used for a supported subscription case

A zero price is not universally invalid: Google's price specification says to submit price 0 for eligible physical goods subscription offers, where that value is ignored and subscription_cost carries the recurring amount. This is a narrow case with country and category limits, not a workaround for ordinary free or unpriced goods.

Fix it on your platform

On Shopify

1. Open the affected product and inspect the price for every variant, not just the first selection. Confirm that a public customer can purchase the selected variant at the submitted amount.
2. Check the Google & YouTube app or feed integration to see which price field it sends and when it syncs. Remove placeholder prices from products that are not ready to sell or exclude those products from the channel.
3. Review Shopify Markets and currency settings for the target country. The landing page, checkout, and product data must use an allowed and consistent currency and price for that market.
4. For a sale, confirm the current price and compare-at price are mapped to price and sale_price correctly. Do not encode member-only or cart-only amounts as the general product price.

On WooCommerce

1. Open the product's General pricing fields and inspect both regular and sale prices. For variable products, verify each variation has a valid price and that the feed includes the same purchasable variation.
2. Inspect the feed plugin's field mapping for price, sale price, currency, and any tax adjustments. Confirm that automatic discounts or currency plugins do not alter the shopper's amount after Google fetches the page.
3. Test checkout for the target country and compare the submitted amount with the visible product and cart price. Include required merchant charges through the appropriate shipping configuration rather than hiding them until checkout.
4. Exclude draft, coming-soon, or unavailable items from the active data source until the actual purchase price is set.

On other platforms

1. Check the catalog value sent to Merchant Center, including numeric formatting and ISO currency code. Compare it with the public product page and checkout for the same target country.
2. For price rules by region, use supported regional pricing features where available instead of changing price based on a visitor's IP address.
3. Map standard and sale price fields separately and make sure discounts are available as advertised. Do not submit a member-only amount as the general price.
4. If the item is a supported physical goods subscription, confirm eligibility and use the required subscription cost details. Do not reuse the zero-price exception for ordinary products.

How to confirm it is fixed

1. Compare the exact item and variant in Merchant Center with its public landing-page amount and checkout amount, including currency and target country.
2. Check that every purchasable variant has a valid amount and that no draft or coming-soon placeholder is included as a normal offer.
3. Resubmit or sync product data, then review the item in Merchant Center's Needs attention or Diagnostics after processing.
4. Run the price check to compare public catalog prices with product-page pricing signals on the store.
5. For a disapproval, use the review action shown in Merchant Center after the corrected feed and live page are available.

Other errors like this