Real time stock
control.

Through the recipe. You define the measurements for each dish, and when the POS records a sale the linked ingredients are depleted by those quantities and the cost per plate is recalculated. That gives you a theoretical usage figure — what the recipes say should have been consumed — which you can hold against actual usage from your counts. The gap between the two is the number worth looking at, and it is a prompt to investigate over-portioning, unrecorded waste or a stale recipe rather than a verdict on any of them. The quality of that signal depends on your recipes being kept current and your yields being entered honestly: if a recipe is out of date, the depletion calculated from it will be out of date too.

It does not, and we would rather you did not rely on it that way. Vertex records the batch and lot detail you enter, tracks expiry dates against it and surfaces what is closest to its date — an eighteen-hour window on one batch, three days on another — so items needing attention are visible before service rather than after. That is a record-keeping and prompting tool to support the process you already run. It does not inspect your stock, judge whether something is fit to serve, manage allergen information or implement HACCP, and it makes no determination about your obligations under local food-safety law. Deciding what your controls should be, following them and confirming your position remains yours, together with your food-safety adviser or environmental health officer. The records are also only as good as what gets entered — a delivery received without being logged will not show up in expiry tracking.

Both are recorded as movements with someone's name attached. A transfer is raised as a stock request from one venue to another, carries an 'In Transit' state while it is moving and takes a digital signature on receipt, so a difference between what was sent and what arrived is attributable to a point in the chain instead of surfacing as an unexplained shortfall weeks later. Adjustments require a reason code — breakage, wastage, promotional or returned — and pass through a manager approval gate before they land. The point of that workflow is an auditable trail and fewer silent write-offs, not a claim that stock stops going astray; what you get is a record of who moved what, when, and why they said they did it.

Yes. Counting the shelf is a manual job your team performs — Vertex organises and records it rather than doing it for you. The system builds a guided count order that groups the count sheet by kitchen area or storage unit so a counter works through one room at a time instead of criss-crossing the building, the numbers are entered on a tablet during the stocktake, and the result is reconciled against the system figure straight away. What comes back is a variance report broken down by category with the financial impact attached, which is usually where shrinkage and unrecorded waste become visible. The count itself, its frequency and its honesty are still yours to own.

The ledger tracks what you owe and to whom: supplier balances, invoice amounts, due dates and settlement status, so an outstanding invoice sits next to the stock it paid for rather than in a separate pile. Purchase and invoice records are entered and maintained in Vertex, and stock data can be exported from the monitor view. What this page does not claim is an integration — there is no supplier EDI feed, no ordering connection into a distributor's system and no accounting-package sync described here — so treat the ledger as your own record of supplier activity, and check with us about anything you need to move into another system before you plan a workflow around it.