Keep feed language and currency consistent through the purchase path

Choose the supported market route deliberately

Google's language and currency guidance describes supported-language requirements, consistency through key landing-page and checkout elements, and separate routes for local currency or supported currency conversion. Check the current country and program guidance before designing the source.

Write a market-offer contract containing target country, submitted language, submitted currency and intended landing-page locale. Decide whether the merchant actually prices in the destination currency or uses an eligible conversion arrangement. These are different operating models, not interchangeable display choices. Record who owns price setting, translation and fulfillment readiness. A successful translation export does not establish that the business can accept and fulfill orders under the new market terms.

Bind the feed record to a stable locale path

Inspect the submitted URL in a fresh session. Check whether the intended language and currency survive redirects, consent choices and variant selection. A page that looks correct for an employee with saved preferences may show another offer to a first-time visitor or crawler.

Prefer an explicit, maintainable locale route supported by the commerce system rather than relying on a visitor's location to infer everything. Test what happens when a browser requests a different language or a user changes market. Keep the originally advertised configuration understandable. Do not assume that a language selector on the homepage fixes a product link that defaults to the wrong locale. Record the final product URL and the observed offer in the test evidence.

Check the price meaning as well as its currency code

Compare the numeric price and currency across the source, landing page and checkout route under the selected model. Confirm shipping information uses the appropriate currency relationship required for that route. A copied currency code without a corresponding pricing decision can turn a valid number into a materially different offer.

Review tax display and mandatory-charge questions with qualified owners for the target market. Do not treat an exchange-rate calculation as proof that the localized price is compliant or commercially approved. Inspect decimal separators, translated variant names and units, because localization transformations can change meaning while remaining syntactically valid. Include a product with a sale and one with several configurations to expose hidden fallback behavior.

Maintain completeness across the locale lifecycle

Create a checklist of purchase-critical text: variant options, availability, delivery choices, errors and checkout instructions. Identify untranslated or contradictory states instead of measuring translation readiness only by product-description coverage. A customer should not need another language to understand the material buying conditions.

After release, inspect representative processed offers and repeat the full path when the locale routing or pricing integration changes. Keep market-specific exceptions visible and avoid declaring global readiness from one successful country test. If a locale is retired, coordinate source targeting and links rather than allowing a silent redirect into a different offer. The acceptance result is a consistent tested market path; traffic and conversion outcomes require separate measurement.

Make the reasoning concrete.

A fictional ceramics shop submits French product text with EUR prices but uses a shared product URL. In a fresh session the page defaults to English and GBP, then switches again during checkout.

The team fixes the locale mapping and checks variant, sale and checkout states. It does not count a translated title as proof of a localized commercial experience.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Route

   Which supported language and currency model is being used?

2. URL

   Does a fresh visit preserve the intended locale and variant?

3. Price

   Do amount and currency retain the same approved meaning?

4. Critical text

   Can the customer understand all material purchase steps?

5. Maintenance

   Which routing or pricing change triggers a repeat test?

Watch for the wrong conclusion.

• Translating titles while leaving checkout in another language.
• Changing a currency code without approving the price.
• Testing only an employee session with saved locale preferences.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis, not Google instructions or measured business results. Sources support only the specifically attributed platform facts. Platform controls and eligibility can change; verify current account guidance before implementation.

• Google Merchant Center: Supported languages and currencies →Primary platform documentation · Supports: Supports language consistency, supported currency routes, currency-conversion distinctions and relevant shipping-currency requirements. Market-contract and path testing are original editorial analysis.