Multilingual Software

Designing Business Software for English, Dari and Pashto

A practical guide to RTL layout, terminology, shared business data and printouts when building software for English, Dari and Pashto users.

BusinessOS Editorial Team Business software & operations

Multilingual business software has two separate responsibilities: interface language and business data.

Keep one operational data model

Customers, products, invoices and transactions do not need separate databases because the interface language changes. The system can store one business record while users work in different supported languages.

Design RTL instead of patching it

Dari and Pashto need right-to-left layout behavior. Navigation order, form spacing, tables, directional icons, breadcrumbs and mobile drawers all need testing in RTL mode.

Create a terminology glossary

Business terms should be translated consistently across modules. A glossary for inventory, finance, sales and workflow actions reduces confusion when several translators or developers work on the system.

Decide how printouts choose language

Receipts, invoices and quotations may follow the current user's language, a customer preference or a company-wide standard. The rule should be explicit.

Keep codes language-neutral where possible

Product codes, account numbers and document numbers are usually easier to integrate when their underlying identifiers are language-neutral, even when labels are translated.

Test with real content

RTL layouts should be tested with real Dari and Pashto sentences, long customer names, numbers, mixed Latin codes and tables. Placeholder text often hides layout problems.

Good multilingual software lets language change without changing the meaning of the workflow.

Related services

Continue from the guide into implementation.

Related BusinessOS products

See where this guidance connects to an operational system.

BusinessOS resources

Turn useful ideas into better operations.