Keep branch scope server-owned
The API resolves organization and allowed branches from the authenticated principal; a browser-selected branch does not grant access.
LOADING
Opening the page…
LOADING
Opening the page…
In development / 2026 / Retail operations
A multi-branch retail workspace taking shape around identity, catalogue, SKU, pricing, and branch access.
Tenant identity, branches, SKU and pricing foundations
The Scent Bar Retail OS is being built for teams working across branches. Its current foundation covers people, branch access, product identity, barcodes, tax and effective-dated pricing.
A branch-specific catalogue needs dependable product identity, price rules, and access control before transactional retail flows can be built on it.
The current milestone covers identity, tenant and branch access, a catalogue and pricing records.
The API resolves organization and allowed branches from the authenticated principal; a browser-selected branch does not grant access.
Catalogue and pricing models exist; product/SKU records carry no authoritative inventory quantity yet.
Test harnesses cover row-level security, cross-tenant relations, duplicate codes, and price overlap; current runtime results remain open.
Organization and branch permissions are resolved by the API. Database rules keep product identities and time-bound prices consistent within tenant boundaries.
Next.js catalogue administration and product detail surfaces.
NestJS modules for identity, branches, catalogue, and pricing.
PostgreSQL tenant scope, row-level security, and catalogue migrations.
Outbox processing foundation with Redis/BullMQ integration.
Tests cover the workspace and catalogue rules. Fresh PostgreSQL migration, API and worker checks still need to run for this milestone.
In development. Inventory ledger, purchasing and point of sale are later milestones and are not presented as implemented.