By Tangenix · Published 2026-10-24 · Free template

Localized Price Display QA Sheet

Check that localized prices keep the intended currency, amount and billing interval, separating formatting from currency conversion and checkout.

Read this resource as Markdown

When to use this template

Use this when an existing software offer is displayed for readers in several locales and formatting might obscure the currency, decimal units or payment interval. Work from the actual approved offer.

Choose another approach when: The product has no approved price, you want an exchange-rate quote, or you intend to treat a language change as authorization to alter what a customer is charged.

Gather these inputs

• The approved amount, ISO currency, billing interval and actual checkout conditions.
• The intended locales and formatting options used by the website.
• Controlled formatting examples and a separate owner for any genuine currency conversion or regional offer.

Copy and adapt the template

Edit the text below and copy it into your own document. Edits stay in this browser field and are not submitted or saved by this page.

Worked example

Illustrative example, not a Crany customer result. Replace every example detail with facts you can verify.

Fictional formatting example: the same EUR1234.50 amount can appear as “EUR 1,234.50” in an en-US currency-code display and “1.234,50 EUR” in a de-DE display, with runtime-specific spacing. The currency and value remain EUR1234.50.
The QA checks the actual formatter output rather than assuming separators or replacing a symbol by hand. A Japanese-yen example must use that currency’s real formatting behavior instead of forcing a two-decimal style everywhere.
These are teaching inputs, not prices or exchange rates for Crany. A different localized display does not authorize a different checkout amount, regional discount or billing interval. The actual rendered page and checkout still require their own checks.

How to use it

1. Record the approved commercial facts before comparing localized strings.
2. Exercise explicit locale/currency formatting and inspect value, labels and rounding.
3. Compare the actual rendered explanation with checkout and keep conversion work separate.

Check before using it

• Formatting has not been mistaken for currency conversion.
• A separator, symbol or interval change has not silently changed the offer’s meaning.
• Examples preserve actual runtime spacing and currency-specific precision limits.

What to measure

Track ambiguous currency labels, incorrect value interpretation and checkout mismatches. Verify selected locale/runtime combinations and record any untested ones. This QA does not quote exchange rates, recommend prices or certify tax treatment.

Research and sources

MDN documents locale-sensitive number/currency formatting and currency-specific precision. This original offer-display matrix uses independent fictional amounts and requires actual runtime checks; it is not an exchange-rate service or a billing integration.

• MDN: Intl.NumberFormat — checked 2026-10-24. Locale-sensitive formatting with explicit currency and currency-specific precision; formatting is distinct from commercial currency conversion.

This original template and worked example were prepared with AI assistance. Source documentation supports the principles stated above; it does not endorse Crany or guarantee this template’s performance.

About Crany

Crany is an AI marketing co-founder in development for software founders and vibe coders, designed to strategize, execute approved marketing and improve based on results. This free resource is usable independently of the product. Join the public waitlist.