Glossary
Understanding the nomenclature of Bambu is essential, particularly regarding the architecture and business logic terms.
D
Debt Balance
The aggregate sum of outstanding credits owed by a specific Customer. Can be negative, implying the customer has Store Credit (they overpaid their balance).
M
Multi-Tenant Organization
A system engineering phrase. It signifies that multiple different companies (Tenants) run off the identical codebase and server infrastructure.
P
Public Schema
The PostgreSQL database schema assigned by default to hold cross-business information like User accounts, API Keys, and Stripe Subscription profiles.
Point of Sale (POS)
The specific checkout terminal screen used primarily by cashiers to ring up sales rapidly.
Purchase Order (PO)
An official document an owner sends to a supplier outlining what physical inventory they wish to buy. In Bambu, POs are reconciled when tracking restocking expenses.
S
Schema Routing
The backend middleware procedure where Next.js parses the JWT Token to identify the user's tenantId, dynamically switching Prisma to query against business_{tenantId} instead of public.
Session Context
The cached metadata (roles, permissions, active business) injected into every Next.js API route via Redis headers.
Stale Cart
A POS checkout cart containing items that have unexpectedly fallen to 0 stock (because another cashier sold the last one while the current cashier was waiting for the customer).
T
Tenant
A single solitary business employing the SaaS. E.g., "Main Street Grocery" is one tenant. "First Ave Bakery" is a completely separate tenant.
Tenant Schema
A physical segmentation in the PostgreSQL database (CREATE SCHEMA business_abc;). Every single table relating to the operations of "Main Street Grocery" sits exclusively in their Tenant Schema.