Meta AdsCriticalItems ineligible for delivery in the targeted market

How to Fix “Currency not supported in target country” in Meta Commerce Manager

Each catalog country accepts a defined currency set. Publishing symbols, lowercase codes or a currency the market does not support makes the price unusable and the item undeliverable there.

Free, no signup

Scan your feed for this error for free

Paste your product feed URL (XML, CSV or JSON). The audit checks Currency not supported in target country along with 25+ other pre-channel rules.

Why this happens

Technical root cause

Multi-market stores keep one base currency in the database and convert at render time. The feed inherits the base currency — or an ambiguous symbol like $ — which does not resolve to the target market's ISO code.

Meta Commerce Manager reports it as Currency not supported in target country and applies: Items ineligible for delivery in the targeted market.

Native CMS friction

  • Shopify

    Markets convert prices in the storefront only; the product export stays in the shop currency.

  • VTEX

    Currency is bound to the trade policy, so a feed built from the default policy can carry the wrong code.

  • WooCommerce

    Multi-currency plugins store alternate prices in meta keys that no standard export reads.

Fixing it manually

  1. 1

    List the countries assigned to the catalog and the currency each one accepts.

  2. 2

    Replace symbols and localized names with uppercase ISO 4217 codes.

  3. 3

    Build a separate feed per market when prices genuinely differ by country.

  4. 4

    Reupload and confirm the country availability panel no longer flags currency.

The IRONFEED automated solution

One rule, applied to every product on every export. No spreadsheets, no re-uploads.

Rule syntax
IF currency NOT IN allowed_currencies(target_country)
  SET price = convert(price, target_currency) + ' ' + target_currency
  ELSE SET currency = upper(iso_currency(currency))

Run automatic linter checks before Meta Commerce Manager crawls your feed. IRONFEED validates every export against the channel spec, so this error is caught in Feed Review instead of in your channel dashboard.

Start free trial See how mapping rules work

Attribute requirements

Meta Commerce Manager attribute requirements for Currency not supported in target country and the matching IRONFEED transformation
AttributeMeta Ads requirementAccepted formatIRONFEED transformation
priceRequired; currency must be valid for the target countryAmount plus uppercase ISO 4217 codePer-market currency standardizer
override countryOptional; country-specific price overridesISO 3166-1 alpha-2 country plus priceGenerated per market feed

Frequently asked questions

Yes, through country overrides or separate feeds per market — not by mixing currencies in the same price column.

No. Meta enforces the currencies each country supports for commerce.

Related Feed Issues & Fixes

Other critical errors affecting catalog performance on Google, Meta, TikTok, and Mercado Libre.

Meta AdsWarning

Pixel and catalog price/currency mismatch

The pixel reads the rendered storefront price (already localized) while the catalog carries the raw database price. Different rounding, currency symbols or decimal separators put the two out of sync even when the underlying amount is identical.

View Fix & Rule
Meta AdsCritical

Invalid URL in link or mobile_link

Tracking parameters are appended by string concatenation, which produces double question marks, unencoded spaces or duplicate UTM keys. Some exports also emit a path without the domain.

View Fix & Rule
Mercado LibreCritical

Moneda no coincide con el site local de Mercado Libre

Regional sellers keep one base currency internally and expect conversion at publish time. The integration passes the base amount through, and locale formatting adds separators the API does not accept.

View Fix & Rule

Looking for a different error?

Browse all Meta Ads errors See every platform