Price, sale price and stock

Price

feed attribute: price

Required, a positive number, with the currency stated on the item or the feed — and it must match the landing page.

2 checks on this requirement2 of them commonly suppress a productenforced by Google Merchant Centerenforced by Meta

Google Merchant Center

Required attribute. Google also checks the submitted price against the price on your landing page and can disapprove a mismatch.

Meta

Required for a catalogue item, in the currency of the catalogue's country, and must match the product page.

What the requirement says

  • Price is required on every item. It should be the price a shopper pays, including any mandatory fees, in the currency of the country you are targeting.
  • Submit the number with its currency, e.g. '24.99 USD', or declare one currency for the whole feed and let it apply to every item.
  • The price in the feed has to match the price on the landing page at the moment it is checked — a mismatch is one of the most common causes of disapproval.
  • A product cannot be offered at zero. Free items, gifts and 'price on request' are not valid prices.

Why products lose visibility when it fails

  • No price at all is a required-attribute failure: the item cannot serve without one.
  • A price of 0, an empty string, 'free', 'TBD' or a value with stray symbols fails the requirement — the number cannot be read.
  • Currencies mixed across one feed produce inconsistent prices, which is why we check currency separately.
  • A price that drifts away from the landing page (a discount applied on the site but not in the feed) commonly causes disapproval.

The checks we run on it

Straight from the audit engine, with the basis each one is judged on. “Commonly suppresses” means the failure is the kind that stops a product serving, so it is weighted more heavily in your score.

CheckBasisRequirementWhat to do
Price missing
criticalcommonly suppressesprice_missing
requiredPrice is required.Submit the product price with its currency, e.g. 24.99 USD.
Price zero or not a number
criticalcommonly suppressesprice_zero_or_unparseable
requiredPrice must be a positive number with a currency.Correct the price in your store data.

Want to know which of your own products fail this requirement?

Audit my price free →

How to fix it in Shopify

  • Prices live on the variant: Admin → Products → variant → Price.
  • Bulk fix: Products → select products → Edit products → Price column, or Products → Export and edit the Variant Price column.
  • Shopify keeps the original price in Compare-at price: submit the price you actually charge as price, not the higher 'was' figure.
  • Markets and currency settings decide which currency a feed app exports; check the feed matches the country you target.

How to fix it in WooCommerce

  • Products → edit product → General → Regular price / Sale price.
  • Bulk fix through Products → Export / Import or the bulk-edit Regular price field.
  • WooCommerce stores the price without a currency; the store currency lives in WooCommerce → Settings → General and is what a feed should use.

Worth knowing

  • Thousand separators, currency symbols and non-breaking spaces inside the number are the usual reason a price 'looks fine' and still fails.
  • If you sell in several currencies, build a separate feed per country rather than mixing currencies in one file.

How FeedGuard checks it

  • We read the price as a number, rejecting thousands separators, currency symbols and non-breaking spaces the way the platform does, and flag a missing, zero or unparseable value.
  • Currency is judged separately: a price with no currency anywhere is reported against the currency requirement rather than double-counted here.

Every failure names the field and shows the value at fault, counted over up to 250 products per scan. A requirement that does not apply to an item is left out of both sides of the score rather than counted as a pass, and a requirement our source cannot see at all is excluded from the score and listed as “not checked from this source” with the reason. Where a value can be corrected without inventing anything, the row is fixed in the corrected CSV you can download; anything we would have to make up (a real barcode, a brand, a price, a category) is listed for you to supply instead.

What each kind of scan can see

A store scan reads the public catalogue the store itself publishes (Shopify's /products.json). A pasted feed URL or an uploaded CSV is the file the shopping platform reads, so every attribute can be judged against it. This is the difference that decides whether a check can run at all.

AttributeStore scan (Shopify)Your feed URL or CSV upload
price
read from the store
variant price
read from your file
read from your file

Read the engine's own rules for this requirement on the results page: every failing row links back to this guide. All 49 checks are listed on what we check.

Run the free audit on your store

Paste your store domain, paste your product feed URL, or upload a product CSV. You get a scored report of every requirement above, the products failing each one, the exact fields at fault, and a corrected CSV to download. No account, no card.

Run the free audit on your store

A store scan reads the public catalogue and skips the attributes it cannot see (barcodes and platform-only fields among them); a feed URL or CSV gets the full audit.

Other price, sale price and stock requirements

  • Sale price

    The discounted price, and it has to be below the regular price — otherwise it isn't a sale.

  • Availability

    Required, and only four values are accepted: in_stock, out_of_stock, preorder, backorder.

  • Condition

    Required for used or refurbished products, optional for new ones — and only three values are accepted.

  • Currency

    Every price needs a currency, and one feed has to use one currency throughout.