A configured drink can deplete liquor items by measured milliliter quantity.
Turn sold drinks into ingredient movement
Pour recipes map a drink to one or more liquor items and a measured milliliter quantity. When the configured drink sells, the sale transaction can deplete the associated liquor inventory automatically, keeping the finished menu item and the ingredient record connected.
Count bottles the way a bar sees them
Track standard bottle sizes, shelf labels, full spare bottles, and fractional levels for open bottles. A physical count sets the observed inventory and records the variance between the system quantity and the counted quantity in one accountable operation.
Put a cost against unexplained movement
Variance reporting summarizes count occurrences, bottle variance, and estimated cost value over a selected date range. Positive variance represents shrinkage, giving management a directional measure to investigate rather than leaving the discrepancy buried in an end-of-month stock adjustment.
Connect the bar to the service floor
Modifiers, floor and table context, kitchen or bar display stations, tips, staff permissions, customers, and reporting remain part of the broader restaurant operation. Bottle tracking and payment behavior require the appropriate module and merchant configuration and should be verified during rollout.
Close with a record that can be investigated
Compare the physical count, system quantity, bottle variance, and estimated cost value before turning a discrepancy into a narrative. The result is a directional control record for management review, not a guarantee of shrink prevention or real-time bottle telemetry.
Close a controlled bottle-count scenario
Configure a test drink recipe against a known bottle size and measured pour, then sell the drink and inspect its ingredient movement. Record full spare bottles and a fractional open bottle in a physical count. Review system quantity, observed quantity, variance, and estimated cost for the period. Investigate the directional result without treating variance as proof of theft or automatic telemetry. Assign a manager to explain and reconcile the exception record. Verify the same count on the hardware planned for the closing manager.
Open the restaurant demo, start a table check, then inspect bar stock, pours, and calculated variance. Availability can depend on enabled modules, hardware, payment setup, role, location, and rollout configuration.
Move from the feature to the operation
This capability shares customer, employee, product, location, transaction, and reporting context with the rest of LiftedPOS. The value is not a checked box. It is the handoff the operation no longer has to rebuild.


