How to Manage Multiple Branches, Currencies and Languages Without Data Silos

Expansion starts with the operating model

Opening a second branch changes more than the address. It adds people, opening hours, services, resources, responsibilities and sometimes another currency or language. If every branch creates its own spreadsheets and accounts, management quickly loses a shared view.

The foundation is a clear data model: what belongs to the whole company, what belongs to a branch and who may change each type of information.

Shared data with branch-specific settings

In AVANTERRO, multiple branches can operate within one company. Branch contacts, opening hours and booking resources can reflect local operations. Online booking availability can be based on a specific person, place or other reservable resource.

Shared company data helps maintain a single customer and operational history. A branch can still have a different daily schedule from headquarters. Before launch, decide which services and processes must stay consistent and which may vary.

Working with more than one currency

A company has a base currency. Supported commercial documents can also carry their own currency and exchange rate. These values belong to the document so that a later company-setting change does not rewrite the history of an existing record.

This is useful for orders, invoices or receipts issued in another currency. It is not an automatic method for accounting for exchange-rate differences, VAT or cross-border supplies. Tax treatment, mandatory document details and accounting procedures must be verified for the relevant country and transaction.

Company language and customer language are different

AVANTERRO distinguishes a user’s interface language from the company’s default language. The company language provides a default for company documents and system communication. Customers can use the public booking experience in a supported language.

Before expanding, define:

• the working language of the internal team;
• the default language of company documents;
• the language customers see while booking;
• who owns the accuracy of industry-specific and legal wording.

Interface translation alone does not provide local legal compliance.

A practical pre-launch checklist

1. Data ownership

Assign responsibility for customers, services, price lists, employees and access. Avoid parallel lists with no clear owner.

2. Booking capacity

Configure branches, services, resources, opening hours and exceptions. Test the entire customer flow, including rescheduling and cancellation.

3. Roles and permissions

A branch manager may not need the same access as a company administrator. Test with real roles, not only the owner account.

4. Documents and currencies

Confirm the base currency, currencies used on documents and the handoff to accounting. Do not treat operational records as an accounting policy.

5. Migration

Move a small, verifiable sample first. Check customers, services, prices and relationships between records. Retire the old system only after exports and history have been reviewed.

Frequently asked questions

Can each branch have its own opening hours?

Yes. Branch availability and exceptions can follow the local operation.

Does multi-currency solve tax rules in every country?

No. Currency and exchange-rate fields support operational documents, but local accounting and tax obligations require professional review.

Must every branch use the same language?

No. User interface language, company default language and public booking language serve different needs.