Stock & Inventory Process Improvement
Improving KAPPTURE / K-Stock processes around counts, depletion locations, PAR levels, transfers, verification and reconciliation between physical operations and financial records.
Overview
Stock in hospitality and event operations is both a system and a behaviour. This work looked at how counts, transfers, PAR levels and verification actually run — and where the process was creating discrepancies the software then faithfully reported.
The Problem
When cellar stock, outlet stock, transfers and sales depletions are not held to the same location model, variance appears everywhere and is explained nowhere. Event operations make this worse: temporary outlets, rushed transfers and incomplete counts.
Requirements
- A location model that matches how stock actually moves
- Count processes that can be completed under operational pressure
- PAR levels that mean something to the people replenishing
- Transfer and depletion paths that can be reconciled
- A verification step that classifies issues instead of dumping them into a spreadsheet
My Role
Reviewed systems configuration and operating process, identified failure points, and worked with operational stakeholders on a tighter control loop. No supplier, customer or commercial stock figures are included here.
Approach
- Map the physical flow: main cellar → outlet → sales/depletion → count → variance
- Separate configuration issues (wrong depletion location, missing PAR) from behavioural ones (uncounted transfers)
- Put verification in the path so discrepancies are classified while context still exists
- Report outstanding and completed checks, not only a final variance percentage
System / Architecture
Stock control is a loop, not a list. Cellar and outlet balances only mean something if transfers, depletions and counts share locations. Variance is the output of that loop, not a separate report.
Implementation
- Process review of counts, transfers and event stock control
- Attention to PAR levels and depletion locations in the system
- Verification workflow for controller submissions
- Reporting that shows what is still open, not only what was theoretically counted
Challenges
- Event time pressure vs count quality
- Temporary outlets that do not match the standing location list
- Transfers that happen operationally before they happen in the system
- Keeping the control useful without turning it into extra admin
Outcome
Stock became a reconcilable process: locations, movements, counts and exceptions. Discrepancies are still expected; they are no longer unexplained by default.
- Clearer ownership of outlet vs cellar stock
- Variances treated as a process signal, not a surprise at period end
- Better operational visibility during events
Technologies
What I Learned
- Most 'system' stock errors are process errors stored in a system
- PAR and depletion location are configuration with operational consequences
- Verification has to happen close to the count, not weeks later
Future Improvements
- Closer coupling between verification tooling and the stock system of record
- Better event-specific location handling
- Shorter cycle from outstanding submission to reviewed variance