Market

Google Shopping feeds for Denmark, Norway and Finland

Denmark, Norway and Finland each need their own Google Shopping feed in practice: three currencies (DKK, NOK, EUR), three languages, and prices that must match the country's storefront including VAT. This page sets out what Google requires per country, how to build three feeds from one catalog, and the formatting traps that Nordic store exports bring with them, from decimal commas to English copy in a Danish feed.

We connect your store, build the feed and keep it in sync. Updated 2026-10-27.

At a glance

  • Denmark sells in DKK, Norway in NOK and Finland in EUR; all three have the Google Shopping tab, and Danish, Norwegian and Finnish are supported feed languages.
  • Prices include VAT where the country requires it, and the same VAT-inclusive price must show on the landing page and at checkout.
  • One feed per country is the normal set-up: each has its own currency, language, landing pages and feed label in Merchant Center.
  • Textfinity builds a feed per market from one store and translates titles and descriptions into Danish, Norwegian or Finnish with AI configs, reviewed before use.

Google Shopping feed requirements for Denmark, Norway and Finland

CountryCurrencyFeed languageShopping tabTypical feed label
DenmarkDanish krone (DKK)DanishYesDK
NorwayNorwegian krone (NOK)NorwegianYesNO
FinlandEuro (EUR)FinnishYesFI
Sweden (for reference)Swedish krona (SEK)SwedishYesSE

Currencies, languages and Shopping tab availability from Google Merchant Center Help, Supported languages and currencies, checked 2026-10-27. Feed labels are your choice; country codes are the common convention.

One Nordic feed or one per country

A single feed can target several countries only when language, currency and landing pages are shared. Across the Nordics they rarely are: Danish shoppers pay in DKK on a Danish page, Norwegians in NOK, Finns in EUR. Google's currency conversion lets a SEK or EUR feed show converted amounts, but the shopper then lands on a page in another currency and language, which usually converts worse than a local listing.

The practical set-up is one feed per country, each a separate data source in Merchant Center with its own feed label, language and shipping settings. Campaigns select one feed label each, so budgets and bids stay per country.

Language: Danish, Norwegian and Finnish product data

Google expects title, description and variant values in the feed's language and the landing page in the same language; when most product data does not match the feed language, products can be disapproved. A Swedish or English catalog sent to Denmark unchanged is the most common Nordic feed problem.

Danish, Norwegian and Finnish are all target languages for Textfinity's AI configs. A translate config turns existing titles and descriptions into the target language; an enhance config rewrites them and translates in one pass. You review and accept the output before any feed uses it, and the original text is the fallback.

Nordic price formats in store exports

  • Decimal comma: exports often write 1 299,00 or 1299,00. Google wants a period decimal and a currency code: 1299.00 NOK.
  • Thousands separators: a space or a non-breaking space between thousands breaks naive number parsing; strip it before adding the currency.
  • Currency symbols: kr is used for both DKK and NOK, so never rely on the symbol; write the ISO code.
  • VAT: if the export holds net prices, compute the gross price in the feed so it matches the storefront.

Examples

Worked examples, by situation

Five Nordic set-ups, each with the rule that fixes it.

Fashion · Shopify Markets · Denmark

Danish market price in DKK

Before

Store default price: 599.00 SEK

After

price: 429.00 DKK
link: https://shop.example.com/da/products/linen-shirt

How we set it up

We build a Google Shopping feed with the market set to Denmark and language Danish; Textfinity reads the Danish market's price from Shopify, price gets the " DKK" suffix, and link is a replace from regexp ^(https://[^/]+)/ → \1/da/ on the product URL, because the market sets prices, not URLs. The feed URL is registered in Merchant Center with Denmark as target country and feed label.

Furniture · WooCommerce CSV · Norway · decimal commas

1 299,00 becomes 1299.00 NOK

Before

pris: 1 299,00
pris: 349,00

After

price: 1299.00 NOK
price: 349.00 NOK

How we set it up

We map price with replace from regexp, find ^(\d*)\s?(\d+),(\d{2})$ and replace \1\2.\3 NOK. calc is the wrong tool here: it reads 24,99 as 2499.

Electronics · net-price export · Norway

Gross price computed from net price

Before

net_price: 1000.00

After

price: 1250.00 NOK

Advanced transform on price

round(calc{[net_price] * 1.25}, 2) + " NOK"

How we set it up

We map price as an advanced expression with your VAT multiplier (1.25 for a 25% rate), plus an exclude filter if net_price is empty, because calc fails on a blank value. Google requires the VAT-inclusive price on the landing page and at checkout to match, so use the rate your shop actually charges, per product category if rates differ.

Beauty · Swedish store · Finland · 900 SKUs

Finnish titles and descriptions

Before

title: Återfuktande ansiktsserum med hyaluronsyra 30 ml

After

title: Kosteuttava kasvoseerumi hyaluronihapolla, 30 ml

How we set it up

We set up an AI config that translates title into Finnish and a second for description. The FI feed maps title with replace from AI config, the Swedish title as fallback, and links to the Finnish storefront.

Home goods · Denmark · small catalog

Only products the Danish shop actually sells

Before

620 products in the store, 410 shipped to Denmark

After

410 products in the DK feed

How we set it up

We add an include filter: the ships_to column includes DK (or is in google sheet list for a SKU list). The Swedish feed keeps the full range, so the two feeds come from the same shop with different filters.

Copy this plan

Plan: Denmark, Norway and Finland feeds

One store, three feeds, three feed labels.

  1. 01

    Connect the store

    Shopify brings markets and locales; other platforms connect with a CSV or Google-shaped XML export URL, one per language if the platform exports them separately.

    What we set up: We connect your Shopify store, or read your CSV or XML export URL.
  2. 02

    Create one feed per country

    Google Shopping template, market and language per feed, so each country gets its own currency, text and landing pages.

    What we set up: We create three feeds from the Google Shopping channel template, with the market set to Denmark, Norway and Finland.
  3. 03

    Translate titles and descriptions

    A translate or enhance AI config per language, reviewed and accepted before use.

    What we set up: We set up a translation AI config per language (Danish, Norwegian, Finnish) and map title with replace from AI config once you accept the generations.
  4. 04

    Fix price formats and VAT

    Period decimal, ISO currency code, VAT-inclusive amount matching the storefront.

    What we set up: We fix price with replace from regexp or an advanced expression, depending on what the export sends.
  5. 05

    Register the feeds in Merchant Center

    Add each feed URL as a file data source with its country as feed label and target country, then add shipping per country in Merchant Center.

    What we set up: We register each feed URL in your Merchant Center with you, with its market as feed label and target country.
  6. 06

    Set up campaigns per feed label

    One Shopping or Performance Max campaign per country, selecting the DK, NO or FI feed label. This step happens in Google Ads.

Customization tips

Make it yours

Translate the long tail, hand-check the top sellers

AI translation covers thousands of products quickly; native speakers should still read the 50 products that carry most of the spend, where a clumsy title costs the most.

Use the storefront's price, not a conversion

Many stores set Norwegian and Danish prices by hand rather than converting from SEK or EUR. Send the price the local storefront charges; a converted price that the checkout does not honor is a mismatch Google can disapprove.

Price comparison sites use the same feed work

Prisjakt runs prisjakt.no for Norway, and its listings also require local currency with VAT. Once the Norwegian feed is clean, a Prisjakt feed from the same catalog is mostly a template swap.

FAQ

Questions about google shopping feed denmark

Is Google Shopping available in Denmark, Norway and Finland?

Yes. Google lists all three as supported Shopping countries with the Shopping tab available, with DKK for Denmark, NOK for Norway and EUR for Finland, and Danish, Norwegian and Finnish as supported languages.

Can I use my Swedish Google Shopping feed for Norway?

Only with currency conversion and Swedish landing pages, which shows Norwegian shoppers SEK prices and Swedish text. For a local listing, create a Norwegian feed with NOK prices, Norwegian titles and Norwegian landing pages.

Do Nordic Google Shopping prices include VAT?

Google asks for a VAT-inclusive price where the target country requires it, and the same price must be shown on the landing page and at checkout. Consumer prices in Denmark, Norway and Finland are normally shown including VAT.

Which language should a Finnish Google Shopping feed use?

Finnish for Finnish-language landing pages. The feed language must match the landing page language, so a feed in Swedish should link to Swedish-language pages.

Set up for you

We'll set up Danish, Norwegian and Finnish feeds from your one store.

Send us your store URL. We set up a feed per country in Textfinity, translate titles and descriptions with AI for you to review, and register each feed in Merchant Center with you.

Have us set up my Nordic feedsOr email support@textfinity.io

Tell us your store and channels. We reply within 24 hours.