---
title: "Languages"
description: "Beelocity deals with language in two separate places, and telling them apart saves a lot of confusion."
---
> Documentation Index
> Fetch the complete documentation index at: https://docs.beelocity.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Languages
Beelocity deals with language in two separate places, and telling them apart saves a lot of
confusion. **The language you read the screens in** is a property of *you*. **The language a
document prints in** is a property of *that document* — and it follows the customer or supplier it
is addressed to, not you.
They are set in different places, on purpose, and changing one never changes the other.
## The language you read
Your language lives on your account, so it follows you to any computer you sign in on. You choose it
from the menu under your name, in the top-right corner: open it, choose **Language**, and pick one.
The screen retypes itself immediately — there is nothing to save and nothing to reload.
If you have never chosen, Beelocity starts from your browser's language and falls back to English.
All three languages are offered, and each of them is complete. A language only appears in that menu
once it is: a half-translated screen is harder to work with than one in a language you did not pick.
### What's new, in your language too
The **Releases** page lists what changed in each version of Beelocity, and it is written in all three
languages. Open it from the footer of any page.
Releases published before Beelocity was translated stay in English. When you open one of those, the
page tells you so in a line above the notes — you are not missing a setting, and there is nothing to
switch.
### This guide, in your language too
The guide you are reading is written in all three languages. The **Docs** link — in the footer of any
page, and in the menu under your name — opens it in the language you read the screens in, so there is
no right version to go looking for.
To move between them while reading, use the language menu in the bar at the top of every page. It
keeps you where you are: the page you were reading comes back in the language you picked, not the
front page of the guide.
## The language your documents print in
An invoice is read by the customer it is sent to, so it is written in *their* language — not in
yours. A French-reading salesperson sending an invoice to an Arabic-speaking customer sends an
Arabic invoice, and that is correct.
Beelocity works that out per document, in this order:
1. **The choice you made when printing**, if you made one — the print dialog offers all three.
2. **The customer's or supplier's own preferred language**, from their partner record.
3. **Your organization's document language**, from Document Settings.
4. **English**, as the floor.
So the usual way to get an Arabic invoice is not to change anything at print time: set the customer's
preferred language once on their partner record, and every document you ever send them arrives in
it. See [Printing and Sharing Documents](printing-documents.html) for the print dialog itself.
## Which is which, at a glance
| | Where you set it | Who it follows | What it changes |
|---|---|---|---|
| **Interface language** | The menu under your name | You | Menus, buttons, column headings, help |
| **Document language** | The partner record, or Document Settings | The person receiving the document | The words printed on invoices, delivery notes, quotations and statements |
The two are independent, and both are worth setting. Changing your own language does **not** change
what your customers receive, and setting a customer's language does not change what you see.
## Numbers and dates
Dates are written the way Algeria writes them — `25/03/2026` — on every screen, in all three
languages. Figures follow your language: `1 234,56` in French, `1.234,56` in Arabic and `1,234.56`
in English — all three group the thousands, and each groups them the way its own readers do. If you
would rather pin the figures to one style regardless of language, Preferences has a number-format
setting that does exactly that.
Arabic uses the same digits everyone else does — `0` to `9` — because that is what an Algerian
invoice, price tag and bank statement are written with.
## What is never translated
Anything **you** typed. Product names, partner names, notes, codes and document numbers are yours
and render exactly as you wrote them, in whatever language you wrote them in. A product called
*Ciment CRS 42,5* stays *Ciment CRS 42,5* on an Arabic screen.
There is one addition you control, and it changes nothing above: for the catalog text your
**customers** read — product names and descriptions, category names, the labels on options like
sizes and colours — you can supply your own renderings in the other document languages, and
Beelocity selects among them where a customer-facing surface asks for a language. Your staff keep
seeing your text exactly as typed; a language you have not filled in falls back to it; and nothing
is ever translated for you — every word a customer reads is one you (or someone on your team)
wrote. See [Translating your catalog](../products/managing-products.html#translating-your-catalog).
Source: https://docs.beelocity.com/en/getting-started/languages/index.mdx