Language and terminology
Three languages - Azerbaijani, English, Russian - and the customer's own terms written into the interface.
There are two layers and they must not be mixed
The system's text sits in two layers. The first is the product's own strings - we translate those and they arrive with each release.
The second is the customer's own vocabulary: one company says "partner", another says "counterparty". That is terminology, not translation - and the company itself must decide it.
When the two are mixed, the customer's edit is lost at the next update. Here they are kept apart.
Glossary and application
The customer glossary is a separate table: which term is replaced by what, applied across the whole interface with one command.
When an update arrives the product's own text is refreshed while the company's glossary stays as it is and is applied again.
What this module adds
In the system this module opens the following items.
Related modules
Core
The foundation every module stands on: targets, signals, the metric store and permission groups - with no industry baked in.
Branding
The interface in your brand: name, logo, colours, email footer and login screen.
Report builder
When the ready-made reports are not enough you build the view yourself: source, filter, grouping and measures - saved under a name.
Most often asked
Can a fourth language be added?
Yes - the interface is built multilingual; a new language is translation work, not a code change.
Does each user pick their own language?
Yes, language is per user: a warehouse keeper works in Azerbaijani and a foreign buyer in English on the same database.
See this module with your own data
The demo database is full of real documents - not a mock-up. Send a request and we will walk through your scenario.