Branches, warehouses and users
How a branch, its warehouses and its staff fit together, and what your plan allows.
Stock, sales and users are all scoped to a branch. A branch has one or more warehouses, exactly one of which is the default that the register sells from. A user either belongs to one branch and works within it, or to none and sees all of them. Getting this structure right first means every later report already knows where things happened.
Open Organization → Branches and add a branch with its code and bilingual name. Each branch receives a permanent number used in its document numbering — it is never reused, even if the branch is later deleted.
A default warehouse is created with the branch. Add more only if stock genuinely sits in separate places — a back store, a second floor. The default cannot be deleted until another warehouse is promoted to take its place.
Per branch, you can override two company-wide settings: whether item images show on the register, and which payment methods it accepts.
Open Organization → Users to add staff. Give each person a name, a login (Latin letters and numbers only), a role, and — for anyone who should only see one branch — that branch. Leave the branch empty for owners and accountants who need the whole picture. Tick "Start on the cashier screen" for anyone who should open straight on the register.
The company's primary admin (marked on the Users list) is protected: only the platform's Super Admin can change their role, access, status or sessions, or delete them, and the primary admin must stay an active user with the Admin role. This keeps at least one person able to run the company.
Adding a branch, warehouse or user is checked against your plan's limits. The user limit counts active users only: you can keep any number of inactive users, and adding a user as active or reactivating one needs a free seat. If you reach one, the Pricing page shows what an extra seat or branch costs per month.
Good practice
- Name warehouses by what they physically are, not by branch again — the branch is already known.
- A user locked out after repeated failed logins is unlocked from their user page by anyone with the users permission.
- A user who has created or worked on any document (a sale, voucher, invoice, stock count…) cannot be deleted, so history always shows who did it. Deactivate them instead; an inactive user cannot sign in and does not use a seat.
- On a user's page, Check documents & deactivate runs the same check: if the user is on no document (for example after demo data was cleared) they are made inactive, freeing a seat, and can then be deleted. When the company has a user limit, the users list shows active seats used out of the limit, and how many users are inactive.