If you run a holding, a branch network or several warehouses, you define companies, branches and warehouses in one account. Users see only the part they are allowed to; stock, sales and finance records are written to the right company and warehouse. You don't install a separate program per company: it is one database with separate scopes.
Set scope up together with authorization. Once definitions are clear, the risk of selling from the wrong warehouse or seeing another branch's account movements drops.
Who is it for?
Multi-branch retail, distribution warehouses, businesses that split a production company from a sales company, and franchise-like networks. Central finance wants a consolidated view and branches want to manage their own stock. IT sets up the company, branch and warehouse structure once. With warehouse groups you can cluster physical warehouses logically.
How it works
Under company and system management you define companies, branches, warehouses, and warehouse groups. User sessions and records bind to those identities. List and document screens default to the user’s scope; authorized users may switch scope.
Example: a sales rep opens an order in branch A; warehouse B only sees its own transfers; central accounting accesses finance lists across companies. Stock vouchers carry warehouse identity; waybills and invoices progress in company/branch context. Business partners and master data sit on the same organization language.
Mobile field teams work with a selected warehouse and branch, so wrong-location movements become less likely. B2B buyers see catalog and orders by their account and company links. When syncing with Mikro or Logo, the mapping must use the right company and warehouse codes, or you get duplicates or the wrong stock location.
Before going live, check four things: are the companies defined, is the branch-warehouse tree right, which scope is each user assigned to, and is the default warehouse clear?
Branch-specific date, time, number and currency display
For teams with branches abroad or different local habits, every company and branch carries its own display format. On the company and branch screens, the Localization tab holds six settings next to the time zone:
- Date: formats such as
31.12.2026or12/31/2026 - Time: 24-hour (
14:05) or 12-hour (02:05 PM); the AM/PM marker follows the interface language (AM/PM, ÖÖ/ÖS) - Number: thousands and decimal separators (
1.234,56,1,234.56,1 234,56,1'234.56, or none) - Currency: symbol or code, before or after the amount (
1.234,56 ₺,$1,234.56,TRY 1.234,56) - Quantity decimal places and amount decimal places (0–4)
Users work in the format of the branch they signed in to: dates, quantities and amounts on orders, invoices, dispatch notes, finance vouchers, lists and reports appear that way. Data entry follows the same rule; a branch working in 1,234.5 style types quantities that way and the value is stored correctly. The setting applies the same way on Platform Web and Mobile; it is chosen on Platform Web.
A new branch takes its format from the company. When the company format changes, branches still matching the company's format move to the new one; branches with their own format stay as they are. The default is the Turkish format (31.12.2026, 14:05, 1.234,56 ₺, two decimals), so you can start without configuring anything.
Benefits
You manage many locations in one account. "This warehouse" is both a filter and a permission boundary. Because records are written with the right scope from the start, branch and warehouse breakdowns in reports can be trusted. A new branch needs only definitions, a license and roles. The center gets policy and a consolidated view, and branches keep working at their own pace. In an audit, "which company was this issued for?" is answered by the record.
Relation to modules and products
Stock, sales, purchasing, finance, POS and manufacturing work in a warehouse and branch context. Definitions live in Company and Business Partners. You manage scope on Platform Web and Mobile applies it. In system sync mappings, company and warehouse codes are critical. Document entry and list experience take their default filters from this scope.
FAQ
Does every company need its own account? In most scenarios, multi-company in one account is enough. If legal/isolation needs require it, evaluate a separate account; the default path is one account with separate scopes.
What is a warehouse group for? It helps cluster physical warehouses for reporting and operations.
Can a user switch company? Yes if permission and configuration allow it; otherwise they stay in a fixed scope.
Which company does sync write to? It writes according to company/warehouse codes defined in integration mapping. Mapping setup is required.
What does the display format cover? Display and data entry on Platform Web and Mobile screens. Stored values are independent of the format; e-Documents (UBL) are always produced in the standard format regulation requires. Print templates, exports, email content and the B2B portal are not covered by this setting.
Next step
Map your organization as company → branch → warehouse, then attach roles to that tree. Try Free to set the first scope, then lock action permissions with authorization.