--- title: "Multi-country settings" description: "Configure country-specific presentation settings in Dashboard and verify language, payment, and user-facing outcomes separately." canonical: https://docs.ordering.co/docs/products/dashboard/settings/enterprise/multi-country/ --- # Multi-country settings Use **Multi-country settings** to review country-specific configuration that may affect number formatting, currency presentation, distance units, and a payment-currency setting. The source also describes country-specific language and local-service configuration. The screenshots are historical examples, not a current country list or a complete catalog of fields. Each screenshot opens at full size. The country name, field labels, choices, and values shown are examples; do not treat them as the configuration for another project or market. ## Current country-override contract The current Dashboard source identifies this route with the `multi_country` category and shows it only when the `multicountry` configuration flag is enabled. It requests the project country list first; after an enabled country is selected, it requests that country's eligible configuration records. Neither route nor flag proves that a country, field, value, storefront, language, or payment method is available in a deployment. Only records marked as replaceable by country are eligible for this override. The update must identify an existing country and eligible configuration. Its value can be null or must be 1–2,000 characters; when no override exists, the update path creates one. Extension hooks can react to the result, so a returned configuration value remains separate from any presentation or provider outcome. The source restricts country-override updates to an administrator at level 0. For a non-administrator, reads are limited to public, non-hidden records; a protected record is returned as `PROTECT`. These are source-defined access and redaction rules, not permission to inspect, copy, or change a production value. [![Historical Dashboard navigation with Multi-country settings selected](https://docs.ordering.co/img/help-center-import/a8c1385d4c31ed6ecdc4868e.png)](https://docs.ordering.co/img/help-center-import/7279fc4a72dc3683280a46fb.png) > **Country configuration is not a user-facing result** > > Selecting a country or changing a field does not by itself translate content, change a user’s account or session, make a storefront available in that country, make a currency acceptable for payment, capture a payment, or prove that a customer sees the intended presentation. ## Before you change a country setting - Confirm the intended country, operator authorization, and approved test scope. - Change one field at a time and keep the original value available to the authorized configuration owner. - Do not use a live country record, customer order, payment, or provider account to discover a setting’s behavior. - There is no page-level draft or **Save** step in the current source route: text, select, and password changes send a country-configuration update as the field changes. Do not edit a production value merely to inspect the interface. ## Choose the country In the historical interface, an operator selects a country first, then reviews the settings associated with that selection. Your Dashboard may return a different list, and the existence of a country in a selector does not establish country availability, customer access, localized content, or operational readiness. [![Historical Multi-country settings country selector](https://docs.ordering.co/img/help-center-import/b911cd137567e7eff60c904b.png)](https://docs.ordering.co/img/help-center-import/67ce25664950eec462d72d25.png) ## Example settings The following country-specific settings can appear in this area: | Setting | Intended configuration | Keep separate from configuration | | ------------------------------------ | ------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | **Decimal and Thousands Separators** | How decimal and thousands values are displayed. | The formatting of invoices, reports, storefront prices, or data exchanged with another system. | | **Currency Symbol and Position** | The currency symbol and whether it is shown before or after the amount. | Currency acceptance, authorization, amount calculation, tax treatment, or payment settlement. | | **Distance Units** | Whether distances are presented in kilometers or miles. | A driver’s location, travel calculation, route coverage, or delivery completion. | | **Stripe Currency Configuration** | A transaction-currency setting associated with Stripe in the historical screen. | Provider acceptance, payment authorization, capture, refund, settlement, or reconciliation. | The screen also illustrates a number of field choices. Those values are historical examples, not default values or recommendations for a country. Check each intended user-facing outcome in an approved test after the authorized configuration owner confirms the change. [![Historical Multi-country settings showing formatting, distance, currency-symbol, and Stripe currency controls](https://docs.ordering.co/img/help-center-import/99385d26cb2180cbb7c82c14.png)](https://docs.ordering.co/img/help-center-import/28b1de4cde80d3c930c2670e.png) ## Check presentation, language, and payment boundaries After an authorized change, validate one boundary at a time: 1. **Configuration:** The selected country and intended setting are returned in Dashboard. 2. **Presentation:** An approved test confirms how the relevant screen presents a number, symbol, or distance unit. 3. **Language:** A country-level setting is not treated as proof that content is translated, that a language selector is available, or that a customer’s language preference changed. 4. **Payment:** A currency selection is not treated as proof that a provider accepts that currency, that a payment can be created, or that any payment outcome completed. 5. **Account and session:** A country setting is not treated as proof that a user can access a channel, sign in, place an order, or retain a session. If your project does not return the country or field you need, do not add a substitute value from a screenshot. Resolve the requirement with the team responsible for the project’s country configuration. --- **Related guides:** [Settings categories](https://docs.ordering.co/docs/products/dashboard/settings/enterprise/) · [Countries and cities](https://docs.ordering.co/docs/products/dashboard/settings/enterprise/countries-cities/)