> For the complete documentation index, see [llms.txt](https://orbit-b2b.gitbook.io/orbit-b2b-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://orbit-b2b.gitbook.io/orbit-b2b-docs/quotes-rfq/storefront-text.md).

# Storefront text translations

Every label your buyer sees on the Quote modal + customer detail page is editable per language under **Settings → Storefront Text**. The app ships with defaults for 6 languages and lets you translate to any language Shopify supports.

## Where to edit

In your Shopify admin → **Apps → Orbit B2B → Settings**.

The Storefront Text section has these Quote-related groups (alongside Global, Volume Pricing, Register Form):

* **Quote — Modal form** (button labels, form field labels, submit / cancel)
* **Quote — Detail page** (section headings, action buttons, author labels)
* **Quote — Status badges** (Pending / Replied / Negotiating / Accepted / Rejected / Expired / Cancelled)
* **Quote — Errors & notices** (validation messages, status notices)
* **Quote — Payment terms** (Due on receipt / Net 15 / Net 30 / Net 60 / Prepay 50% / Custom labels)

## Per-language editing

At the top of the Storefront Text section there's a language picker. Switch language → edit the value → Save.

* The primary locale value is required (English by default)
* Translations for other languages are optional — leaving one empty falls back to the primary locale

After Save, the app pushes the strings to a shop metafield (`shop.metafields.orbit_wholesale.app_settings_i18n`), and the storefront block reads them inline on every page load. Changes go live immediately, no theme deploy needed.

## Default translations included

Out of the box you get translations for:

* English (en) — primary
* Vietnamese (vi)
* French (fr)
* German (de)
* Spanish (es)
* Japanese (ja)

Any other language you publish in your Shopify store will fall back to English until you provide translations for it.

## Tip: brand-specific labels

You don't have to translate verbatim. Use the storefront text editor to match your brand voice:

* `Request a Quote` → `Get bulk pricing` or `Talk to sales`
* `Wholesale Team` (admin author label) → `Acme Wholesale` or `Your account manager`
* `Accept & checkout` → `Approve & pay`

The buyer sees whatever you set, so use language they expect.

## Multi-language storefronts

If your store sells in multiple countries with different Shopify markets:

1. Publish each language in **Settings → Languages**
2. The Storefront Text editor's language tabs now include each published language
3. Translate the values for each (or use the defaults if your language is in the list above)
4. Shopify's automatic locale routing serves the right strings to each buyer

## Next steps

* [Email translations](/orbit-b2b-docs/quotes-rfq/emails.md#default-translations)
* [Settings overview](/orbit-b2b-docs/settings/general.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://orbit-b2b.gitbook.io/orbit-b2b-docs/quotes-rfq/storefront-text.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.