Stock that moves when you sell, not when you remember
Ingredients, warehouses, per-batch expiry, purchase orders, counts, waste and transfers — deducted first-in-first-out as orders complete.
SEE IT IN ACTION
Every sale is a stock movement. Every count is a variance you can explain.
OVERVIEW AND BENEFITS
A ledger, not a number
Stock on hand is the consequence of an append-only movement ledger — receipts, sales, waste, transfers and count corrections. That is what makes a variance investigable instead of just surprising.
FIFO by batch
The oldest batch is consumed first, so expiry is managed by the system rather than by a marker pen.
Counts that produce variance
A stock count records what was counted, what the system said, and the difference — per line.
Waste that is categorised
Spoilage, breakage and staff meals are logged distinctly, because they are different problems.
WHY IT MATTERS
The stock count nobody trusts is the one done once a month
When on-hand is typed rather than derived, every count is an argument. When it falls out of the ledger, the count is just a confirmation — and the variance points at something real.
1movement ledger behind every figure
0manual deductions after a sale
3waste categories, kept separate
Illustrative figures — replace with measured results before publishing.
PRODUCT DETAILS
Procurement to plate
The full path a raw ingredient takes, recorded at every hop.
Ingredients & categories
A stock catalogue with units, reorder thresholds and supplier links.
Warehouses
Multiple storage locations with per-location on-hand and transfers between them.
Purchase orders
Raise, approve and receive against suppliers, with prices captured on receipt.
Stock batches
Per-batch cost and expiry, consumed oldest-first.
Stock counts
Session-based counts with per-line variance and a correcting movement on completion.
Waste logs
Typed, attributed waste entries that reconcile against the ledger.
Counting is a session, not a spreadsheet
A count is opened, filled in as someone walks the store, and completed. Lines nobody reached stay uncounted rather than becoming zero.
Not counted is not zero:a blank line is skipped entirely, so a half-finished count never writes off the rest of the store.
Corrected against live stock:the adjustment is computed against on-hand at completion, so the ledger still sums to the figure on screen.
Reopen to fix:a completed count can be reopened and re-completed, and both passes stay in the ledger.
COMPARISON
Vestibel vs. a stock spreadsheet
Capability
Vestibel
Spreadsheets
Standalone POS
FIFO consumption by batch
Automatic deduction from recipes
Per-batch expiry tracking
Multi-warehouse with transfers
Count sessions with per-line variance
CUSTOMER STORIES
“
Vestibel gave us one guest record across rooms, restaurant and spa — check-in time is down 40% and we stopped losing restaurant charges entirely.
Dinesh Weerakoon · General Manager, The Banyan House
Placeholder story — no customer-story content exists yet.
A 30-minute walkthrough with your rooms, rates and outlets — no slides.
FAQ
FAQ
Menu items carry ingredient recipes. When the order completes, the ingredients are deducted first-in-first-out from the relevant warehouse, consuming the oldest batch first.
Yes. A count is a session you fill in as you walk the store. The correcting movement is calculated against live on-hand at completion, so trading during the count does not corrupt it.
Lines you never touched stay uncounted and are skipped entirely. Only what somebody actually counted produces an adjustment.
Yes. Stock is held per warehouse with transfers between them, so a main store and a bar store keep separate on-hand figures.
