How to Manage Restaurant Inventory: A Complete Guide

Beyond Counts and Alerts

The basic version of inventory management is a list of items, a quantity field, and a notification when something runs low. That is enough to prevent the worst stockouts but does not move the margin much.

The systems that go further treat each item as a structured record with a physical location, an owner, a set of variants, a sell-by date, and rules that define what else gets deducted when it sells. That structure means a lot of what felt like necessary admin becomes work the system handles on its own. A 125ml glass sold at the bar can deduct the right fraction from a bottle's stock without anyone doing the maths. Sell-by dates automatically track which stock is still available for sale.

Knowing Who Owns What

For most restaurants, stock ownership is implicit: the restaurant owns everything in the building. For venues handling consigned wine, member-owned products, or supplier-consigned stock, ownership matters at the item level. A system that does not track ownership pushes that distinction into spreadsheets, member account systems, or staff memory, and reconciliation work follows. A system that tracks ownership at the stock-entry level lets the same wine sit in the cellar under two different ownerships and be priced or billed accordingly when it sells.

Tracking Variants and Variant Quantities

A single product often has several saleable forms. A bottle of wine can be sold as a full bottle, a 25cl carafe, or a 125ml glass, each with its own price and its own slice of the parent's stock. A system that handles variants properly attaches them to a single parent inventory, with each product variant configured to deduct its own fraction from the inventory, so selling a 125ml glass automatically takes the right portion from the bottle's inventory.

Ingredient-Level Deduction with Recipes

For dishes assembled from ingredients (a Carbonara, a cocktail, a charcuterie board), stock has to be deducted at the ingredient level, not the dish level. A system that handles this defines what gets deducted when a finished item sells, with a quantity per ingredient. Selling one Carbonara deducts the right portion of bacon, pasta, and the rest from the underlying stock. The same applies to cocktails, bundles, and any composite product.

Expiry, Spoilage, and Sell-By Dates

Perishables either earn their keep or quietly cost the venue money. Food, fresh produce, draught beer, and wine with a drinking window all degrade if they sit too long. A system that tracks sell-by dates per stock entry can flag at-risk items before they are wasted, and marks stock past its date as no longer available for sale.

Inventory Linked Across Sublocations

Many operations sell the same product from multiple locations while drawing from one inventory pool. A wine bottle stored in the central cellar might be sold at the bar, the restaurant, or in private dining, but the stock all sits in one place. A system that links inventory across those locations lets the same product appear for sale in everywhere that needs it while drawing from one shared stock entry, so every sale registers against the same inventory.

When Inventory Shares a Database with the Rest of the Platform

When inventory shares a database with the POS, the CRM, and the booking system, a sale at the POS deducts stock automatically (including ingredients via recipes and the right fraction via variant quantities), and the order, customer, and stock entry all reflect the change at once.

What disappears:

• Manual reconciliation between POS and stock reports
• Duplicate data entry on deliveries
• Spreadsheet bridges between inventory and purchasing
• Manual exports to share figures with finance
• Separate stocktake CSVs to merge before upload
• Cross-checking member account systems for consignment volumes
• "The system says ten, we have six" conversations

Each is hours per week of staff time.

The Bottom Line

Tiquo handles all of this in one inventory layer: Stock Ownership tracks who owns each entry, Variant Quantities handles fractional deductions per variant, Recipes deducts ingredients when finished items sell, Sell-By Dates flags items approaching expiry and removes expired stock from sale, and shared inventory across sublocations lets one stock pool feed multiple sales channels. All of it sits on the same platform as the POS, CRM, and booking system, so every sale, booking, and customer interaction reflects the same inventory state.

FAQs

Does Tiquo handle restaurant inventory?

Yes, Tiquo's inventory layer is built into the same platform as the POS, the CRM, and the booking system. Stock counts and low-stock alerts work out of the box, with deeper capabilities per product when needed: ownership, sell-by dates, recipes, variant-level deductions, and inventory linked across sublocations.

Does Tiquo deduct ingredients automatically when a dish is sold?

Yes, through the Recipes feature. Each product defines what else gets deducted when it sells, with a quantity per ingredient. Selling one Carbonara deducts the right portion of bacon, pasta, and parmesan from the underlying stock. The same applies to cocktails, bundles, and any composite product.

Does Tiquo track sell-by dates and stock expiry?

Yes, via per-stock-group sell-by dates. The system tracks which stock is still available for sale, flags items approaching expiry, and marks stock past its date as no longer sellable.

Can the same product be sold from multiple sublocations with shared stock?

Yes. Inventory in Tiquo can be linked across sublocations, so the same product can be sold from the bar, restaurant, and private dining while drawing from one shared stock entry. Every sale registers against the same inventory.