Multi-location retail chain
Three stores and one warehouse sell the same SKUs.
Best setup: One workspace, four branches
One catalog, easy transfers, single reporting view.
Use Case
Multi-workspace inventory management
When teams share catalog and transfers, keep one workspace. When they need strict separation — different catalogs, currencies, or user access — use separate workspaces.
Independent catalog
Each workspace owns its SKUs, barcodes, and item data
Isolated settings
Currency, custom fields, tags, and integrations are workspace-scoped
Separate user access
Invite only relevant users to each workspace
Clean reporting
Reports stay scoped to one workspace for accurate insights
RO
Retail Ops
3 branches
USD
Own integrations
SKU-R001 Running ShoeIn stock
SKU-R002 Casual TeeLow
SKU-R003 Winter JacketIn stock
WO
Wholesale Ops
2 branches
CAD
Own integrations
SKU-W001 Bulk Fabric RollIn stock
SKU-W002 Industrial ThreadIn stock
SKU-W003 Packing CrateLow
Each workspace is a fully independent environment
Branch vs workspace: know the boundary
A branch is a location inside a workspace. A workspace is a separate operational boundary. Branches do not isolate catalog, integrations, or billing — workspaces do.
Search branches...
Downtown Warehouse
City Center Store
Airport Kiosk
Westside Distribution
Uptown Retail
Branch = where stock is stored
Switch Workspace
TW
Test Workspace
OwnerDW
Demo Workspace
AdminAC
Acme Corp
StaffCreate New Workspace
Workspace = what data is shared
- •Branch answers: where is stock stored and who can access this location
- •Workspace answers: what data is shared and which operations are isolated
- •Transfers only work inside one workspace — if you split, stock cannot move between them
Quick decision: one workspace or many?
Need transfers between operations?
One workspaceShared item catalog?
One workspaceConsolidated reporting?
One workspaceStrict data separation?
Separate workspacesDifferent currency / accounting / fields?
Separate workspacesReal scenarios teams face
Different operation models
One business runs wholesale and retail — teams conflict on pricing and item structure.
Best setup: Two workspaces (Wholesale, Retail)
Clean operational boundaries and fewer accidental edits.
3PL client isolation
Client A must never see Client B data.
Best setup: Workspace per client
True isolation, clean permissions, safer audits.
Pilot line testing
Test a new catalog without disturbing current operations.
Best setup: New workspace for pilot
Fast testing with controlled blast radius.
Multiple currencies
Teams in different regions report in different currencies and accounting contexts.
Best setup: Separate workspaces by currency
Cleaner valuation, fewer reporting disputes.
Temporary project stock
A seasonal pop-up needs separate stock control for 3 months.
Best setup: Branch if shared, workspace if isolated
Structure matches whether data is shared or isolated.
What lives where
Workspace scope
- •Item catalog, SKUs, barcodes
- •Currency and number format
- •SKU rules and counters
- •Custom fields (max 4)
- •Tags and bundles
- •Accounting integrations
- •Reports and settings
- •Subscription usage and API limits
Branch scope
- •Zones
- •Quantities
- •Min/max overrides
- •Branch access per user (read/write/export)
- •Branch address and details
If your requirement is in the workspace column, splitting branches will not solve it.
Common mistakes and how to fix them
Workspace per store by default
No inter-store transfers, duplicate SKU maintenance across every location.
Fix: Use one workspace with branches unless strict isolation is required.
One workspace for unrelated operations
Teams collide on catalog, custom fields, and processes.
Fix: Split by operation model when teams need independent governance.
Tags as a privacy boundary
Sensitive data still visible to broader workspace users.
Fix: Use separate workspaces for strict data isolation.
Splitting too early without naming standard
Workspace sprawl and admin overhead.
Fix: Adopt a naming pattern like [Business Line] - [Region/Client] before creating workspaces.
FAQ
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 use one or many workspaces depending on how operations are managed.
When should I use separate workspaces vs 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 — for example, separate workspaces for retail and wholesale divisions, or for different client accounts in a 3PL setup.
Can I copy settings from an existing workspace?
Stocklyst does not auto-clone workspaces, but you can record your source settings (currency, SKU style, custom fields, tags) and apply the same configuration to a new workspace during setup.
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 data isolation and independent configuration, but cross-workspace views require external combining.
Structure your operations with the right workspace setup
Start with one workspace and branches. When you need strict isolation, create a new workspace in seconds.
Create account