Branch management starts with the work between locations
Illustrative retailer: one legal seller has a central warehouse and two shops. Locations can share products while keeping stock movements and operating responsibilities distinct.
Map a location before choosing a company boundary
Illustrative retailer: one legal seller has a central warehouse and two shops. Locations can share products while keeping stock movements and operating responsibilities distinct.
Central warehouse → shop A
Illustrative plan: move ten units to shop A; it sells six, leaving four there. The stock operator owns the transfer and the shop lead owns the count.
Shop B access and reporting
Agree which products/prices are shared and whether B can view or move A stock. Test B ordinary-role permitted and denied actions before accepting the setup.
Separate legal seller
If a shop is a different legal company, use its own seller identity, books, currency/tax configuration and deliberate record permissions. A branch label does not create those controls.
Database and subscription
One Workspace database can contain configured locations/companies. A separate Workspace database has its own subscription; multiple databases can share one runtime. This does not imply a runtime for every database.
Connect branches through clear locations, stock movements and company responsibilities. Explore multi-company accounting and consolidation with Datrylo Accounting.