Skip to content
Multi-branch ERP

ERP for multi-branch companies: one tenant, branch-scoped access, and owner-level reporting that doesn't wait for month end.

Every branch shares the same product catalog, customer list, and chart of accounts, but users only see the branches they're scoped to - all-branch, selected-branch, or none - so a manager can run their own location without ever seeing another one's numbers.

Updated

Why branch data drifts apart, and how scoping fixes it

The usual failure mode for a growing multi-branch business isn't a lack of data - it's data that lives in five different exports that don't agree with each other by the time someone tries to compare them.

Farexa keeps every branch on the same tenant: one product catalog, one customer list, one chart of accounts. What's scoped per branch is access and activity - who can see a given branch's sales and stock, and where a given sale or stock movement actually happened. A user is set to all branches, selected branches, or none, and that access applies everywhere automatically: list views, reports, dashboards.

That means an owner opens one dashboard and filters by branch instead of asking five managers to send their numbers in, and a branch manager works inside their own location without ever having visibility into another one's figures - not because someone remembered to hide it, but because the access model doesn't show it to them in the first place.

What you get

Branch-scoped user access

Each user is set to all branches, selected branches, or none - list views, reports, and summaries filter automatically to what they're allowed to see.

Shared catalog, branch-level stock

Products and customers are shared across the tenant, but stock, sales, and POS activity are tracked per branch, so counts never drift between locations.

Owner dashboards across every branch

Reports and dashboards filter by branch on demand, so an owner reads today's numbers across every location instead of waiting for someone to consolidate exports.

How multi-branch operations run

  1. Set up branches and scope access

    Create each branch once, then assign every user to all branches, selected branches, or none - the access model that actually maps to who should see what.

  2. Run daily sales and stock per branch

    POS, sales orders, and stock movement all record which branch they happened at, on the same shared product and customer records.

  3. Read consolidated or branch-filtered reports

    Dashboards and reports filter by branch instantly - an owner sees the whole group, a branch manager sees only their own.

Who this is for

  • Owners comparing branch performance

    Branch-filtered dashboards mean today's numbers per location are a filter, not a re-export.

  • Managers who should only see their own branch

    Branch-scoped access keeps a manager's view - and a manager's exports - limited to the branch they run.

  • Operations teams tracking stock across locations

    Shared products with branch-level stock counts mean a transfer between branches is visible everywhere, not reconciled after the fact.

Common questions

Can I limit a user to just one branch?

Yes. Every user is set to all branches, selected branches, or none, and every list view, report, and dashboard filters to that access automatically - it isn't a setting someone has to remember to apply.

Do branches share the same product catalog?

Yes. Products and customers are shared across the tenant, while stock, sales, and POS activity are tracked per branch, so a product exists once but its stock count is specific to each location.

Can an owner see every branch at once?

Yes. Reports and dashboards filter by branch, so an owner reads a consolidated view or drills into a single branch without exporting and merging spreadsheets.

How many branches can one tenant run?

There's no fixed cap in the platform itself - the practical limit is how you want to organize reporting and access, which the branch-scoping model is built to handle either way.

See your own branches in one workspace.

Book a walkthrough with your real branches and access levels - see the owner view and a scoped manager view side by side.