Product and variant catalog
Maintain reusable product identity, categories, brands, units, variants, lifecycle dates, recipes, serials, and medicine links.
Inventory
Separate warehouse and selling stock while retaining one traceable product and movement history.
Model products once, then hold quantities by branch, warehouse, division, variant, batch, or serial number. Procurement, receiving, transfers, valuation, and replenishment all use the same branch-scoped stock records.
What the Inventory module covers
The workspace is organized around complete operational responsibilities, not a collection of disconnected menu labels.
Warehouses and inventory divisions
Keep central stores, selling stock, departments, food courts, or product groups separate while retaining a shared product catalog.
Procurement and receiving
Create purchase orders, receive supplier quantities into the intended location, and preserve cost and source references.
Movement and replenishment
Transfer, issue, return, adjust, value, forecast, and reconcile stock through traceable movements and reviewed actions.
Records kept by the workspace
These are the principal operational records staff create, update, review, or hand to another connected module.
- Products, variants, units, categories, and brands
- Branch and inventory-division balances
- Purchase orders and supplier receipts
- Stock transfers and receiving records
- Movement ledger, valuation, batches, serials, and recipes
What the connected workflow is designed to improve
The module combines records, permissions, location scope, and shared services to support these practical operating results.
Clear stock ownership
Warehouse, selling, departmental, division, variant, batch, and serial quantities remain distinguishable so availability is not overstated at a terminal.
Traceable movement
Receiving, transfers, issues, sales, returns, and adjustments create a movement history that explains how each location reached its current balance.
Better replenishment decisions
Valuation, shortages, excess stock, forecasts, supplier history, and reviewed assistant recommendations support purchasing and redistribution decisions.
Included functionality
The module connects the following working capabilities through one tenant and branch model.
- Products, categories, brands, units, variants, serial or IMEI tracking, and recipes
- Multiple inventory divisions for warehouses, departments, food courts, or product groups
- Purchase orders, supplier receiving, stock transfers, and destination acceptance
- Movement ledger, valuation, cycle-count priorities, and controlled reconciliation
- Low-stock analysis, replenishment forecasts, supplier ranking, and reviewed assistant drafts
How work moves through the module
A typical operating sequence; permissions and branch configuration determine who performs each step.
- 1
Create the shared product record and assign it to the required inventory divisions
- 2
Receive opening stock or supplier deliveries into the correct warehouse or branch
- 3
Transfer, issue, sell, return, or adjust quantities through recorded stock movements
- 4
Review valuation, ledger differences, reorder needs, and replenishment decisions
Deployment, data ownership, and management oversight
The workspace is connected to the wider platform without removing tenant, location, department, or permission boundaries.
Deployment model
Branch teams can manage supported stock operations locally while hosted inventory provides central configuration and cross-branch oversight. Store, division, batch, variant, and serial ownership remain explicit in both environments.
Access and data scope
Product identity is tenant-wide while quantities remain scoped to the store, inventory division, variant, batch, or serial record that owns them. Warehouse stock is not automatically treated as terminal stock.
Management visibility
Review quantities, stock value, movement history, shortages, overstock, replenishment forecasts, transfer state, supplier performance, and ledger differences by branch or inventory owner.
Assign the workspace by responsibility
Module enablement makes the workspace available to the organization. User assignments and permissions still control its menus and actions.
Stock clerkWarehouse managerPurchasing officerInventory controller
Administrators can combine module access with branch, store, campus, facility, department, menu, and action permissions. A shared user may work across approved workspaces without receiving access to unrelated records.
Start with Inventory, then assign the right locations and people.
Hosted onboarding records the organization, first branch, business type, module selection, and owner account. Additional branches, roles, and permissions can be configured from administration.