# Google Merchant Center Disapproved Products Fix: CZ, SK, PL, HU

URL: https://sellersatlas.com/google-merchant-center-disapproved-products-fix
Last checked: 2026-10-30

Most disapprovals in a small CEE shop come from a short list of causes: the wrong currency or a price without VAT, a feed price that differs from the landing page, missing shipping, and invalid GTINs. Start with any account-level problem, then fix price and availability, then identifiers and images. This fix list for Google Merchant Center disapproved products follows that order for shops selling into Czechia, Slovakia, Poland and Hungary.

It sticks to what Google documents. Where we add checks from experience with CEE feeds, we label them that way.

## Triage first: what a disapproval actually costs you

Open **Products > Needs attention** in Merchant Center, then check the account's diagnostics. There are two kinds of problem here, and they need different fixes:

![Three ordered steps for fixing Merchant Center disapprovals, from account-level issues to identifiers and images.](https://sellersatlas.com/media/figures/1/89-W0Tl4voM.svg "Fix what can stop the whole account first.")


- **Item-level issues** hit single products, for example a missing GTIN or a price mismatch on one URL. The rest of the catalogue keeps serving.
- **Account-level issues**, such as a suspension for misrepresentation, take every product offline at once.

A sensible order of work:

1. Account-level and policy issues first, because they can stop everything.
2. Critical item issues next: price, availability and landing page.
3. Identifier and image issues last. A missing identifier usually limits performance rather than blocking the product. An invalid GTIN or an image that breaks the rules can still get the item disapproved, so don't leave these for too long.

Price mismatches belong near the top. Google says it [treats mismatched prices as critical errors that can lead to account suspension](https://support.google.com/merchants/answer/14916353?hl=en).

Expect a delay after you fix something. On its [mismatched product price page](https://support.google.com/merchants/answer/12159029?hl=en), Google says reviewing your website can take up to 12 hours after you request a check. It also says disapproved products are recrawled over the next few hours or days. Google does not publish a guaranteed re-approval time for other issue types. Don't assume a fix failed just because Diagnostics hasn't updated within the hour.

## Before you debug: the CZ, SK, PL, HU baseline

A large share of "mystery" errors in CEE feeds comes from wrong basic settings. Check these before you look at individual products.

![Table of target country, currency and example price value for Czechia, Slovakia, Poland and Hungary.](https://sellersatlas.com/media/figures/1/89-RWmccpK1.svg "Use the local currency shown on the landing page.")


### Currency and language per country

Google's [supported languages and currencies page](https://support.google.com/merchants/answer/160637) lists Shopping ads and free listings as available in all four markets. It also says the data source can use any supported language.

| Target country | Currency to submit | Example price value |
|---|---|---|
| Czechia | CZK | 1299.00 CZK |
| Slovakia | EUR | 49.90 EUR |
| Poland | PLN | 123.00 PLN |
| Hungary | HUF | 12990.00 HUF |

Submit each target country's local currency, the same one your landing page shows to shoppers there.

### VAT-inclusive prices

The [price attribute page](https://support.google.com/merchants/answer/6324371?hl=en) lists the countries where the submitted price must include VAT and match the landing page. That list includes Poland and Czechia. The format is a number plus an ISO 4217 code, with at most two decimals.

Slovakia is not named in that list. The general rule still applies: the feed price must match the price on the landing page. For a consumer shop, that is the price the shopper actually pays.

**Worked example.** A Polish shop's platform export holds a net price of 100.00 for a product. Poland's standard VAT rate is 23%, so the consumer price on the page is 123.00 PLN. The feed must carry `123.00 PLN`. If the export sends `100.00 PLN`, every product with that template gets a price mismatch, because the crawler sees 123.00 on the page.

### Multi-country setup

Google's [multi-country guide](https://support.google.com/merchants/answer/15404838) covers the basics. You add target countries to a data source, and the shipping service must use the same currency as the offer. Countries that share a language can share a data source. A data source does not create a campaign: you still need a Google Ads campaign covering the products in each country you want to advertise in.

For the attribute side, see our [product feed checklist for CEE channels](/product-feed-online-shop-cee-checklist) and the guide to [mapping Google, Heureka and Allegro feed fields](/product-feed-mapping-google-heureka-allegro).

## Account-level problems: misrepresentation, return policy and contact details

### Return policy

Return policies live under **Shipping and returns > Return policies**. According to [Google's return policy setup page](https://support.google.com/merchants/answer/14011730?hl=en), a policy covers these fields:

- policy URL
- countries
- whether you accept returns of defective and non-defective items
- exchanges
- product condition
- return window (a number of days, or lifetime)
- return method
- restocking fee
- refund timeframe

Each policy shows a status of Verified, Pending or Rejected. If you upload no policy, Google may infer one from your site and show it as applying "for most items".

One policy can cover several countries. For EU consumer sales, the return window you enter should be consistent with the [EU 14-day withdrawal right](/eu-14-day-withdrawal-right-webshop). If you offer longer, say 30 days, enter 30 days and make sure the return page says the same.

### Misrepresentation and site trust

Suspensions for misrepresentation are account-level. They are also the hardest to clear. Read Google's Misrepresentation policy in the current Shopping policies document and compare your site against it point by point. The checks we run in practice:

1. A shipping page, a returns page and a refund explanation that are easy to find from every product page.
2. Visible business contact details: legal entity name, address, email and phone.
3. Terms and payment information that match what checkout actually does.
4. The same return window in Merchant Center and on the site.

Our [EU compliance checklist for an online shop](/eu-compliance-checklist-online-shop) covers the legal pages most of these checks depend on. Once the site is fixed, request a review from the account issue in Merchant Center. Asking for a review on an unchanged site wastes time.

### Policy housekeeping

According to [PPC Land](https://ppc.land/google-merges-two-shopping-policy-sets-but-adds-zero-merchant-restrictions/), Google announced on 15 July 2026 that it would merge the Shopping ads and free listings policies into one document in September 2026. Google said the change adds no substantive new restrictions. Internal docs that link to the old separate policy documents may need updating.

## Price and availability mismatches

Google's [mismatched product price page](https://support.google.com/merchants/answer/12159029?hl=en) lists these causes:

- the website and Merchant Center were updated at different times
- wrong structured data on the landing page
- the price shown to users differs from the price bots crawl, for example a price loaded by JavaScript after page load
- wrong sale-price dates or time zones
- minimum order quantities or bulk pricing, where the total price must be submitted

### Fix path

Google [describes two routes](https://support.google.com/merchants/answer/14916353?hl=en):

1. Edit single products under **Products > Needs attention**.
2. Export the CSV, correct the values in the source data, then re-upload.

Then schedule the feed fetch to run right after price changes on the website. If your platform pushes price changes at 02:00, set the fetch for after that, not before. Google [recrawls disapproved products](https://support.google.com/merchants/answer/12159029?hl=en) and re-approves them once the landing page price matches.

### Automatic item updates

Under the **Products > Automations** tab, Google can [update price, sale price, availability and condition from your landing pages](https://support.google.com/merchants/answer/12157888?hl=en-GB). The setting is on by default and relies on schema.org markup. Google says it covers only sporadic problems, and it can pick the wrong figure when a page shows several strikethrough prices. It is a safety net, not a replacement for a feed that updates on schedule.

### Typical CEE checks

Google does not document these as separate causes. They are what we see most often in CZ, SK, PL and HU feeds:

- **VAT mismatch:** net prices in the platform export, gross prices on the page.
- **Rounding:** HUF and CZK prices rounded to whole units on the page but carrying decimals in the feed, or the reverse.
- **Omnibus price labels:** "lowest price in the last 30 days" shown as a second strikethrough, confusing the crawler and automatic updates.
- **Shared templates:** a CZ/SK template showing EUR on the Slovak page but CZK in structured data, or the other way round.
- **Sale timezones:** `sale_price_effective_date` written in UTC while the shop's sale starts at midnight Prague or Warsaw time.

> [!WARNING]
> Treat a large wave of price mismatches as an account risk, not a cosmetic issue. Google says unresolved price mismatches can lead to suspension. Find the shared cause, such as VAT, the template or the schedule, before you edit products one by one.

## GTIN, brand and MPN errors

Google [asks for a brand plus either a GTIN or an MPN](https://support.google.com/merchants/answer/6098295?hl=en). One-of-a-kind, handmade or vintage goods can set `identifier_exists` to `false`.

The [GTIN attribute page](https://support.google.com/merchants/answer/6324461?hl=en) sets these rules:

- GTINs have 8, 12, 13 or 14 digits (UPC, EAN, JAN, ISBN). Spaces and dashes are ignored.
- Don't submit invalid check digits, restricted prefixes (02, 04, 2), coupon prefixes (05, 98, 99) or guessed values. When in doubt, leave the GTIN out.
- Each variant needs its own GTIN.
- Own-brand or sole-seller products without a GTIN should use brand plus MPN.
- For bundles, a manufacturer-made bundle uses its own GTIN, and a bundle you put together uses the main product's GTIN. Books use the ISBN-13.

### Worked check-digit example

Take the first 12 digits of an EAN-13: `400638133393`. Multiply the digits by 1 and 3 alternately, starting from the left:

4×1 + 0×3 + 0×1 + 6×3 + 3×1 + 8×3 + 1×1 + 3×3 + 3×1 + 3×3 + 9×1 + 3×3 = 89

The check digit is (10 − 89 mod 10) mod 10 = **1**, so the valid GTIN is `4006381333931`. A feed value ending in any other digit is invalid. The same logic fits in a spreadsheet formula or a short script that runs before upload. GS1's online check-digit calculator does the same job for spot checks.

### Bulk fix

1. Export the Needs attention CSV and filter for identifier issues.
2. Fill in GTINs from the manufacturer's or distributor's price list. Never generate them yourself.
3. Validate every check digit.
4. Remove GTINs you can't confirm, and send brand plus MPN instead.
5. Re-upload and watch Diagnostics.

## Shipping settings: the Poland example and the CEE pattern

The [shipping attribute page](https://support.google.com/merchants/answer/6324484?hl=en) says shipping cost is required for Shopping ads and free listings in Czechia, Slovakia, Poland and Hungary, among other countries.

You can set shipping at account level in Merchant Center, or per product with the `shipping` attribute (up to 100 times per product). For delivery-speed estimates, Google needs a price plus both a maximum handling time and a maximum transit time.

Both are counted in business days:

- **Handling time** ends when the parcel goes to the carrier.
- **Transit time** ends on delivery.

The shipping service must use the [same currency as the offer](https://support.google.com/merchants/answer/15404838): a PLN offer needs a PLN shipping service.

### Poland: what to enter per service

Use your own contract or list rates here. Carrier prices change, and we compare them in [Packeta, InPost, GLS and DPD compared](/packeta-inpost-gls-dpd-cee-carriers).

| Service (example) | Country | Currency | Price | Max handling (business days) | Max transit (business days) |
|---|---|---|---|---|---|
| Parcel locker / pickup point | PL | PLN | your PLN rate, VAT included | your dispatch promise | carrier's stated maximum |
| Courier to door | PL | PLN | your PLN rate, VAT included | your dispatch promise | carrier's stated maximum |
| Free above threshold | PL | PLN | 0.00 PLN above your threshold | same as above | same as above |

Repeat the table for CZ (CZK), SK (EUR) and HU (HUF). A common gap is a shop that set up Czech shipping and then added Slovakia as a target country with no EUR shipping service. Every Slovak offer then lacks shipping. For setting thresholds, see [free shipping threshold by country](/free-shipping-threshold-by-country). For carrier choices, see [shipping setup for a small CEE webshop](/shipping-setup-small-cee-webshop) and [Hungary shipping with Foxpost, GLS and MPL](/hungary-webshop-shipping-foxpost-gls-mpl).

## Images and landing-page errors

### Images

The [image_link page](https://support.google.com/merchants/answer/6324350?hl=en) sets these rules:

- minimum 500 × 500 px, with around 1500 × 1500 recommended
- maximum 64 megapixels and 16 MB
- no promotional elements or overlays, watermarks, placeholder images, added logos or borders
- the product should fill 75–90% of the frame
- each variant should have its own image

Some older third-party guides still give lower minimums, so go by the live Google page. If you add "-20 %" badges to catalogue images, keep them off the image URL you send in the feed. Also check what image automations are switched on under the Automations tab.

### Landing page unavailable

This error means Googlebot could not load the product URL. Our usual checks, in this order:

1. The URL returns 200, not 404, 410 or a redirect to the homepage.
2. No geo-redirect sends visitors from outside the country to another store version.
3. A cookie or age wall does not hide the product content from crawlers.
4. Neither robots.txt nor a firewall or bot-protection rule blocks Google.
5. The page loads reliably and does not time out.

Search Console's URL inspection shows what Google actually receives for the URL.

## If you use a custom feed script: the Content API shutdown

Google's [Content API sunset page](https://developers.google.com/shopping-content/guides/sunset) gives the timeline:

- The sunset date was 18 August 2026.
- From 1 September 2026, requests from clients without an active extension began failing intermittently with HTTP 410 Gone.
- Full shutdown is set for early 2027, when all requests will fail.

If you connect through an ecommerce platform, Google says the platform partner handles the migration and you need to do nothing. Custom scripts must move to the Merchant API.

Symptoms to watch for now: a feed that updates on some days and not others, stale prices, and a sudden wave of price or availability mismatches with no change on the site. If a developer once built your connector, ask which API it calls. Our guide to [feed tools for WooCommerce, Shoptet and Shopify](/product-feed-tool-woocommerce-shoptet-shopify) covers ready-made options.

> [!IMPORTANT]
> Intermittent 410 errors are easy to miss because the feed still works part of the time. Check your script's logs for 410 responses before you spend hours on individual price mismatches.

## Decision table: error to cause to fix

| Message in Merchant Center | Most likely cause in a CEE shop | Fix | Where to fix | Official source |
|---|---|---|---|---|
| Missing or invalid GTIN | Guessed or mistyped EAN, wrong check digit | Use supplier GTIN or brand + MPN | Feed / platform | [GTIN](https://support.google.com/merchants/answer/6324461?hl=en) |
| Mismatched price (crawl) | Net vs gross VAT, JS-loaded price, feed out of date | Send VAT-inclusive price; fix markup; reschedule fetch | Feed + site | [Price mismatch](https://support.google.com/merchants/answer/12159029?hl=en) |
| Automatic update: mismatched price | Several strikethrough prices on the page | Clean up schema.org price and Omnibus label | Site; Products > Automations | [Auto updates](https://support.google.com/merchants/answer/14916353?hl=en) |
| Mismatched availability | Stock synced less often than the site changes | Raise feed frequency; check markup | Platform / feed | [Automatic updates](https://support.google.com/merchants/answer/12157888?hl=en-GB) |
| Missing shipping | Target country added without a service in its currency | Add a service per country in local currency | Shipping and returns | [Shipping](https://support.google.com/merchants/answer/6324484?hl=en) |
| Missing return policy | No policy uploaded | Create policy; match site text | Shipping and returns > Return policies | [Returns](https://support.google.com/merchants/answer/14011730?hl=en) |
| Image overlay or too small | Sale badges, supplier thumbnails | Clean image at 500 px+ | Image source / feed | [image_link](https://support.google.com/merchants/answer/6324350?hl=en) |
| Landing page unavailable | Geo-redirect, cookie wall, bot block | Serve 200 to Googlebot | Site / hosting | Search Console URL inspection |
| Misrepresentation suspension | Missing contact, returns or business details | Fix site, then request review | Site; account issues | Google Shopping policies |
| Feed not updating | Custom script still on Content API | Migrate to Merchant API | Connector | [Sunset](https://developers.google.com/shopping-content/guides/sunset) |

## Pre-flight checklist before every feed upload

Copy this into your feed SOP:

![Checklist of key checks to run before every Merchant Center feed upload.](https://sellersatlas.com/media/figures/1/89-BxFEZJKj.svg "A short version of the full 15-point list.")


1. Currency per target country: CZK, EUR (SK), PLN, HUF.
2. Price includes VAT and uses `number + ISO code` with at most two decimals.
3. Feed price equals the visible price and the structured-data price.
4. Sale price dates are set in the shop's own timezone.
5. Availability matches current stock.
6. Every GTIN has a valid check digit and no restricted or coupon prefix.
7. Brand is present for every product. Own-brand items use MPN, not invented GTINs.
8. Images are at least 500 × 500 px, with no overlay, watermark, logo or border.
9. Each variant has its own image and GTIN.
10. Product URLs return 200 to a crawler, with no geo-redirect or cookie wall.
11. A shipping service exists for each target country, in the offer's currency.
12. The return policy shows Verified and matches the returns page.
13. Business contact details are visible on the site.
14. Automatic item update settings have been reviewed under Automations.
15. The feed fetch is scheduled after site price changes, and the connector does not use the Content API.

**Monthly routine:** open Diagnostics, export the Needs attention CSV, group the rows by issue type, fix each group at its source, and request a review where Merchant Center offers one.

## When to stop fixing and ask for help

Use the review request in Merchant Center for account-level issues. If a suspension comes back after a review, go through the misrepresentation checks again against Google's current policy text, not an old bookmark. If your shop runs on a platform plugin, the plugin vendor's support can confirm how prices, VAT and currencies are exported. For WooCommerce shops, see [WooCommerce setup for Czechia and Slovakia](/woocommerce-czech-republic-slovakia-setup).

Comparison sites have their own rules. A product approved by Google can still fail on [Heureka, Zboží.cz, Árukereső and Compari feed requirements](/heureka-zbozi-arukereso-compari-feed-requirements).

## Frequently asked questions

### Why are my products disapproved with a mismatched price?

The price Google crawls on the landing page differs from the feed price. In CEE shops, the most common reasons are net prices in the export, a feed that updates later than the site, wrong structured data, or sale dates set in the wrong timezone.

### Which currency should I use for Slovakia, Czechia, Poland and Hungary?

Use EUR for Slovakia, CZK for Czechia, PLN for Poland and HUF for Hungary, matching what the landing page shows.

### Should the Merchant Center price include VAT?

Yes, for consumer prices. Google's price attribute page requires VAT-inclusive prices for countries including Poland and Czechia. In every case, the feed price must match the price on the landing page.

### Can I use one feed for CZ, SK, PL and HU?

You can add several target countries to one data source, but each offer has to carry the currency shown on the landing page for that country. In practice, most small shops run one data source per currency or store version. Each target country also needs a shipping service in the offer's currency and a Google Ads campaign that covers it.

### Do I have to set up shipping separately for each country?

Yes. Shipping cost is required in all four markets, and each shipping service has to use the same currency as the offer.

### How long does re-approval take after a fix?

For price mismatches, Google says a requested website review can take up to 12 hours, and disapproved products are recrawled over the next few hours or days. Google does not publish a fixed timeline for other issue types. Allow time for a recrawl before you change anything again.

### Do I need a GTIN to sell through Google in these countries?

Google asks for a brand plus either a GTIN or an MPN. Products that have a manufacturer GTIN should use it. Own-brand or sole-seller products without one can use brand plus MPN, and one-of-a-kind or vintage items can set `identifier_exists` to false.

### Is a return policy required in Merchant Center?

Google provides a return policy setup under Shipping and returns. If you don't upload a policy, it may infer one from your site and show it as applying "for most items". Setting your own policy, consistent with your returns page and the EU 14-day withdrawal right, gives you control over what shoppers see.

### My feed stopped updating after August 2026. Is it the Content API shutdown?

It may be if a custom script feeds Merchant Center. Since 1 September 2026, Content API requests without an extension have been failing intermittently with HTTP 410. Platform users are migrated by their provider.

## Key takeaways

- Fix in this order: account-level issues, then price and availability, then GTINs and images.
- Submit local currency per country (CZK, EUR, PLN, HUF) and VAT-inclusive prices that match the page.
- Shipping is required in all four markets, and each country needs a service in the offer's currency.
- Never guess GTINs: validate check digits, or use brand plus MPN for own-brand goods.
- If you use a custom feed script, check it for Content API 410 errors. They began on 1 September 2026, and full shutdown is in early 2027.
