Settings

Settings stores each value as a single named row in the database.

Each row's default comes from the store's settings registry, so a setting you have never touched still has a sensible value, and changing one takes effect without a deploy.

Opening Settings lands you on Settings → Site, which holds the Branding form plus the general, business, currency, discounts, shipping and returns sections.

How a setting is stored

One row per named setting. The registry supplies the default; your row overrides it.

The consequence worth knowing is the one above: a settings change is data, not code. You do not wait for a deployment to rename the store or switch a rounding mode, and nobody needs to be on hand to ship it for you.

Branding

The Branding form sits at the top of Settings → Site and holds three fields:

• Site name
• Site description
• Site logo

The name and description are not only for the header. The same two values feed page titles and social metadata, so editing them here changes what a shared link looks like as well as what the storefront says.

Business and legal details

Four fields, used on invoices and receipts:

• Legal name
• Address
• Phone
• Tax ID

These are the details a customer's accountant will look for, so a blank one shows up as a gap on a document rather than as an empty admin field.

Currency and exchange rates

Four currency settings, and they are genuinely four different things:

• Base currency
• Display currency
• Payment currency
• Any additional currencies shoppers can switch to

Exchange rates run in one of three modes:

1. Manual rates only
2. Automatic daily ECB rates
3. Automatic, with manual overrides

The third mode is the practical one for most stores: rates keep themselves current, and you pin the pairs where you want a specific figure rather than the market's.

Converted prices round one of three ways:

Standard
Always up
Always down

Rounding always up is how you avoid converted prices that quietly undercut your base currency; rounding down is a deliberate choice to absorb the difference.

You can also show shoppers a conversion notice, so a converted price is labelled as one.

Two fields on this record are written by a scheduled job rather than by you — the fetched rates, and the time they were fetched. Both are hidden from the form, because a value the job overwrites on its next run is not something you should be able to edit and believe you have changed.

Support contacts

Two fields:

• Support email
• Support URL

Both are printed on invoices and receipts, alongside the legal name, address, phone and tax ID.

The other settings pages

Settings → Site is one page among several. The rest are:

• Appearance — the storefront theme and the admin theme
• Payments & Checkout
• Taxes
• Fulfillment
• SEO
• Notifications
• Alerts
• Integrations
• Developer
• AI

Under Access, there are also Users and Roles.

Language is not a setting

There is no locale field in Settings, and this is deliberate rather than missing.

The storefront's default language, and the languages a shopper can choose between, come from three places:

1. The market they are shopping in
2. Their own saved preference
3. Their browser language

A single store-wide language field would be wrong for any store selling into more than one market — which is the case this store is built around. Language belongs to the market, so you set it on the Markets page.

Where to look for a setting

If it describes your business — its name, its legal details, its currencies, how it rounds — it is on Settings → Site.

If it describes one system — payments, taxes, fulfillment, email, integrations — it has its own settings page named after that system.

If it describes one place you sell, it is not in Settings at all. It is on the market.

Settings holds what is true of the whole store; anything that can differ between the places you sell belongs to a market, not to a setting.

Related