Language and region

Manage → Settings → Money & region, the Region block.

There are three fields, and they are not in the same state. The screen is straightforward about it:

"The language applies to published pages and to messages shown to shoppers; timezone and units are stored only — nothing reads them yet."

Language — this one does something

It does two things, and both are observable:

It reaches the published page's lang attribute. That is how browsers and search engines know what language the page is in. It affects whether a browser offers to translate the page, how a screen reader pronounces it, and how search engines classify it.

It picks the language of the messages shoppers see. Text the storefront generates — as opposed to text you typed — follows this setting.

Note what it does not do: it does not translate your content. Product names, button labels, articles — all stay exactly as you wrote them. This is a setting that declares what language the page is in, not a translation engine.

About the value

The server validates the shape of a language code rather than checking it against a fixed list. vi, en, fr, pt-BR are all accepted.

Which means you can set a language the admin interface has no translation for. The published page declares it correctly, and generated messages fall back to a language that does exist. That is deliberate: declaring the truth beats being blocked.

Timezone and Weight unit — nothing reads them

These two are stored and nothing else. No part of the product reads them today: no timestamp shifts to the timezone you pick, and nothing displays weight in the unit you choose.

Filling them in does no harm, and when a feature does use them your values will already be there. But do not expect them to change anything today — and if you see a timestamp in the wrong timezone, this field is not why.

This page says so because the screen says so. A setting that looks live and is not is the worst kind of silence.

Your language versus the store's language

Do not confuse the two:

• The site language here decides what the published page declares and what language shoppers see messages in.
• Your interface language — what you see in the editor and the Manage screens — is a setting on your account, not on the site.

A Vietnamese agency can perfectly well build an English store: Vietnamese admin interface, site declaring en.

The rest of Settings

The same Settings screen also holds:

• General — store name, description (used for previews and SEO), support email and phone, and the site ID.
• Money & region — see Currency and price display.
• Address — where the business is based.
• Social — Facebook, Instagram, TikTok, YouTube links.
• Policies — returns, shipping, privacy. "Shown to customers in the footer and at checkout."
• API keys — see API keys.
• Webhooks — see Webhooks.
• Danger zone — deleting the site. You have to retype the site's name to confirm.

The site ID

General carries the Site ID with a copy button: "Used to identify this site in support requests and API calls."

When reporting a problem to somebody, sending this along is the fastest way for them to find the right store.