Multi-location retail chain
Three stores and one warehouse sell the same SKUs.
Best setup: One workspace, four branches
One catalog, easy transfers, and a single reporting view.
Operations Structure
Know when one workspace is enough and when operations need a hard split.
Keep one workspace when teams share catalog, transfers, and inventory truth. Split into separate workspaces when operations need hard boundaries for data, currency, settings, or client isolation. The expensive mistake is treating branches and workspaces as the same thing.
Shared stock truth when it belongs together
Keep one workspace when teams need the same catalog, transfers, and reporting view.
Hard separation when it does not
Split into separate workspaces when teams need different catalogs, currencies, settings, or client boundaries.
Cleaner permissions
Invite only the users who should work inside a given operational boundary instead of using visibility workarounds.
Reporting that matches the real operation
Keep reporting consolidated when inventory is shared, or isolated when the business genuinely needs hard boundaries.
01 — Branch versus workspace
Use branches when inventory truth is shared. Use workspaces when it is not.
A branch answers where stock is stored. A workspace answers which teams share catalog, settings, transfers, and reporting. If the requirement is in the workspace column, adding more branches will not solve it.
- Branches are for location-level stock, users, and zone visibility inside one shared operating environment.
- Workspaces are for separate catalogs, settings, integrations, and reporting boundaries.
- Transfers only work inside one workspace. If you split, stock cannot move directly between those environments.
Branch = where stock is stored
Workspace = what data is shared
02 — Quick decision
Decide based on whether stock should stay shared.
If the team needs one inventory truth, stay inside one workspace. If the team needs hard separation, split. The fastest decision usually comes from answering these five questions.
Need transfers between operations?
One workspaceShared item catalog?
One workspaceConsolidated reporting?
One workspaceStrict data separation?
Separate workspacesDifferent currency, accounting, or custom fields?
Separate workspaces03 — Isolation proof
What should stay shared and what should stay separate
This is the practical check for whether you should split the environment or keep locations together inside one operating model.
Workspace scope
- Item catalog, SKUs, and barcodes
- Currency and number format
- SKU rules and counters
- Custom fields, bundles, and tags
- Accounting integrations
- Workspace reports and settings
- Subscription usage and API limits
Branch scope
- Zones
- Quantities
- Min/max overrides
- Branch access per user
- Branch address and location details
If the requirement sits in the workspace list, changing branches will not fix it.
04 — Real scenarios
How operators usually make the call
The correct structure depends on whether inventory truth is shared. These are the patterns that show up most often in real operations.
Different operation models
One business runs wholesale and retail and the teams conflict on pricing and item structure.
Best setup: Two workspaces
Clean boundaries and fewer accidental edits.
3PL client isolation
Client A must never see Client B data.
Best setup: Workspace per client
True isolation, safer permissions, cleaner audits.
Pilot line testing
You want to test a new catalog or workflow without disturbing current operations.
Best setup: New workspace for pilot
Fast testing with a controlled blast radius.
Multiple currencies
Teams in different regions report in different currencies and accounting contexts.
Best setup: Separate workspaces by currency
Cleaner valuation and fewer reporting disputes.
Temporary project stock
A seasonal pop-up needs separate stock control for three months.
Best setup: Branch if shared, workspace if isolated
The structure should follow whether inventory truth is shared or not.
05 — Common mistakes
The structure mistakes that create rework later
Most structure problems come from over-splitting too early or trying to use branches for isolation that should live at workspace level.
Workspace per store by default
You lose inter-store transfers and duplicate SKU maintenance across every location.
Fix: Use one workspace with branches unless strict isolation is genuinely required.
One workspace for unrelated operations
Teams collide on catalog structure, custom fields, and process expectations.
Fix: Split by operation model when teams need independent governance.
Using tags as a privacy boundary
Sensitive data is still visible to broader workspace users.
Fix: Use separate workspaces when the requirement is hard isolation.
Splitting too early without naming standards
Workspace sprawl adds admin overhead and decision confusion.
Fix: Set a naming pattern before creating multiple workspaces.
06 — FAQ
Frequently asked questions
What is a workspace in Stocklyst?
A workspace is an independent operational environment with its own catalog, settings, users, reports, and integrations. A single business can run one or many workspaces depending on how operations are structured.
When should I use separate workspaces instead of branches?
Use branches when operations share products, need transfers between locations, and want consolidated reporting. Use separate workspaces when operations need strict data isolation, different currencies, or independent catalog governance.
Can one company have multiple workspaces?
Yes. One legal business can run multiple workspaces for operational separation, such as wholesale and retail divisions or separate client accounts in a 3PL setup.
Can I copy settings from an existing workspace?
Stocklyst does not auto-clone workspaces, but teams can mirror the same settings pattern manually when they want similar currency, SKU, custom field, or tag rules.
What do I lose by splitting into separate workspaces?
Separate workspaces cannot transfer stock between each other, share a catalog, or produce consolidated in-app reports. You gain hard isolation, but cross-workspace views require external combining.