arrow_backPerno Store
Sell in the customer's language

Make localization part of store data—not a collection of hard-coded template strings.

Configure store languages and currencies, then maintain localized content across products, categories, menus, blog posts and public checkout communication.

translate
What you get

A consistent localized buying journey across discovery and fulfillment.

storefrontPerno Store
account_treePerno Orchestration
translateMultilingual commerce
Verified platform activity

Built on payment infrastructure already working in production.

A conservative snapshot of Perno's production footprint—not a forecast or an invented customer claim.

price_check
55k+

successful production payments recorded

account_balance
3

payment providers represented in live transactions

domain
5

specialist industry payment products

account_tree
976k+ PLN

processed payment value in the leading production currency

Live database snapshot for 30 October 2026. Values are rounded down and sandbox transactions are excluded. Different currencies are not combined.

Inspect the product evidence: See what we ship View supported PSPs Explore the API
Why change

A translated homepage is not a multilingual store if product and checkout context stay foreign.

check_circle

Navigation changes language but product data does not.

check_circle

Preview links open the platform domain instead of the localized store domain.

check_circle

Delivery and transactional labels remain inconsistent.

What you get

Localization across the parts customers actually touch.

language

Store languages

Enable the language variants supported by the storefront.

currency_exchange

Store currencies

Offer configured currencies and keep order currency explicit.

category

Catalog translations

Localize product, category and attribute content.

menu

Navigation translations

Maintain language-specific header and menu labels.

article

Localized editorial content

Publish blog and content pages for each audience.

link

Localized public URLs

Keep previews and customer routes on the real store domain and language path.

How it works

A consistent localized buying journey across discovery and fulfillment.

Step 01

Enable markets

Add the languages and currencies the store will support.

Step 02

Translate the journey

Complete catalog, navigation, content and fulfillment labels.

Step 03

Preview on-domain

Review the correct language on the actual storefront route.

Common uses

Create a coherent experience for every enabled market.

check_circlePolish and English store
check_circleItalian catalog
check_circleLocalized blog
check_circleCross-border checkout
check_circleTranslated delivery
check_circleLanguage-specific SEO
Questions

Multilingual commerce

Can customers change language and currency?add

Themes expose selectors when the corresponding store configuration is available.

Are order currencies mixed?add

No. Currency remains explicit on products, checkout and the resulting order.

Treat every language as a complete store journey, not a partial translation.