Zum Hauptinhalt springen
Alle Artikel
POSMay 31, 2026

How to Manage Restaurant Inventory: A Complete Guide

Beyond Counts and Alerts

A basic inventory system records quantities and warns when an item runs low. More detailed records help with the decisions that follow: what to reorder, which stock to use first and how much a sale should deduct.

An item can carry a physical location, owner, variants and sell-by date, along with rules for deducting stock when it sells. For example, selling a 125ml glass at the bar can deduct the corresponding amount from a bottle without a manual adjustment.

Knowing Who Owns What

Many restaurants own all their stock. Venues that also hold consigned wine, member-owned products or supplier-consigned stock need to record ownership for each entry. Otherwise, staff have to check spreadsheets or member accounts during reconciliation. Recording ownership lets the same wine sit in the cellar under different owners and be priced or billed accordingly.

Tracking Variants and Variant Quantities

A bottle of wine might be sold whole, as a 25cl carafe or as a 125ml glass. Each serving has its own price but draws from the same stock. Set the deduction for each variant so that every sale reduces the bottle inventory by the correct amount.

Ingredient-Level Deduction with Recipes

For a dish, cocktail or charcuterie board, stock needs to decrease at the ingredient level. A recipe records the quantity of each ingredient used, so selling a carbonara deducts the specified amounts of bacon, pasta and other ingredients. The same approach works for bundles and other products made up of several items.

Expiry, Spoilage, and Sell-By Dates

Fresh produce, draught beer and wine with a drinking window can go to waste if they sit too long. Sell-by dates on stock entries help flag items approaching expiry and mark expired stock as unavailable for sale.

Inventory Linked Across Sublocations

A venue may sell a product from multiple locations while keeping it in one place. Wine from a central cellar, for example, may be sold at the bar, restaurant or private dining room. Linking those sales locations to a shared stock entry keeps every sale in the same count.

When Inventory Shares a Database with the Rest of the Platform

When inventory shares a database with the POS, CRM and booking system, a sale can update the order, customer record and stock together. Configured recipes and variant quantities determine the ingredient or fractional deductions.

This reduces work such as:

  • Reconciling POS and stock reports
  • Entering delivery data more than once
  • Moving inventory and purchasing data between spreadsheets
  • Exporting stock figures for finance
  • Combining stocktake CSVs before upload
  • Checking member accounts for consigned stock

The Bottom Line

Tiquo’s inventory features sit on the same platform as its POS, CRM and booking system. Stock Ownership records who owns each entry. Variant Quantities and Recipes control deductions for servings and ingredients. Sell-By Dates flags approaching expiry and removes expired stock from sale. Shared inventory lets several sublocations sell from one stock pool.

FAQs

Does Tiquo handle restaurant inventory?

Yes. Inventory is part of the platform alongside the POS, CRM and booking system. It includes stock counts and low-stock alerts, plus ownership, sell-by dates, recipes, variant deductions and shared inventory across sublocations.

Does Tiquo deduct ingredients automatically when a dish is sold?

Yes. The Recipes feature records the quantity of each ingredient to deduct when a product sells. A carbonara sale, for example, can deduct the specified amounts of bacon, pasta and parmesan. Recipes also work for cocktails, bundles and other composite products.

Does Tiquo track sell-by dates and stock expiry?

Yes. Sell-by dates can be set per stock group. Tiquo flags approaching expiry and marks stock past its date as unavailable for sale.

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.

© 2026 Tiquo. "Tiquo" und das Tiquo-Logo sind eingetragene Marken von Tiquo Ltd.

GDPR · CCPA · PCI DSS · ICO · Cyber Essentials Certified · EU–US DPF · SOC 2 Type II (in progress) · ISO 27001 (in progress)

Security & Operational

  • 99.99% SLA Uptime
  • AES-256 encryption at rest
  • TLS 1.3 in transit
  • AES-256 / TLS 1.3
  • Perfect Forward Secrecy (PFS)
  • HTTP Strict Transport Security (HSTS)
  • 99.999999999% (11 nines) data durability
  • Automated backups
  • DDoS protection
  • Web Application Firewall (WAF)
  • Zero Trust posture
  • Role-Based Access Control (RBAC)
  • Principle of Least Privilege
  • Secret scanning in CI
  • SBOM generation
  • Dependency supply-chain controls
  • 24/7 infrastructure monitoring
  • GDPR Article 22 safeguards
  • Data Protection Impact Assessments (DPIAs)
  • Records of Processing Activities (ROPA)
  • SAML 2.0 SSO
  • EASIE SSO
  • OAuth 2.0 / OpenID Connect (OIDC)
  • SCIM 2.0 provisioning
  • MFA / 2FA enforcement
  • Responsible disclosure / bug bounty programme

Privacy, Data Protection & Statutory Obligations

  • ICO Registered
  • UK Modern Slavery Act 2015 compliant
  • UK Public Interest Disclosure Act 1998 compliant
  • EU Article 27 Representative appointed (Paris, France)
  • Swiss FADP Article 14 Representative appointed
  • UK GDPR compliant
  • EU GDPR/DSGVO compliant
  • UK Data Protection Act 2018 compliant
  • Swiss revFADP compliant
  • CCPA / CPRA compliant (California)
  • VCDPA compliant (Virginia)
  • CPA compliant (Colorado)
  • CTDPA compliant (Connecticut)
  • TDPSA compliant (Texas)
  • OCPA compliant (Oregon)
  • MCDPA compliant (Montana)
  • FDBR compliant (Florida)
  • ICDPA compliant (Iowa)
  • ICDPA compliant (Indiana)
  • TIPA compliant (Tennessee)
  • DPDPA compliant (Delaware)
  • NJDPA compliant (New Jersey)
  • NHDPA compliant (New Hampshire)
  • NDPA compliant (Nebraska)
  • MCDPA compliant (Minnesota)
  • MODPA compliant (Maryland)
  • KCDPA compliant (Kentucky)
  • RIDTPPA compliant (Rhode Island)
  • Canada PIPEDA compliant
  • Quebec Law 25 compliant
  • Alberta PIPA compliant
  • British Columbia PIPA compliant
  • Singapore PDPA compliant
  • Hong Kong PDPO compliant
  • Brazil LGPD compliant
  • Japan APPI compliant
  • Australia Privacy Act / APPs compliant
  • India DPDPA 2023 compliant
  • Thailand PDPA compliant
  • Malaysia PDPA 2010 (as amended 2024) compliant
  • New Zealand Privacy Act 2020 compliant
  • South Africa POPIA compliant
  • UAE PDPL compliant
  • Mexico LFPDPPP compliant
  • Kenya Data Protection Act 2019 compliant
  • Ghana Data Protection Act 2012 compliant
  • Nigeria NDPA 2023 compliant
  • Indonesia PDP Law 2022 compliant
  • Philippines Data Privacy Act 2012 compliant

Global Fiscal & E-Invoicing

  • EN 16931 - EU e-invoicing core standard
  • UBL 2.1 - Universal Business Language
  • Austria - RKSV
  • Belgium - Peppol BIS 3.0 (B2B)
  • Czechia - fiscalization
  • Croatia - Fiscalization 2.0
  • Denmark - Peppol BIS 3.0 (B2B)
  • France - NF525 / LNE / Infocert, Factur-X / PDP, E-Reporting
  • Germany - KassenSichV / TSE, DSFinV-K, GoBD, E-Rechnung B2B (XRechnung / ZUGFeRD)
  • Hungary - Online Szamla
  • Italy - Scontrino, FatturaPA (via SDI)
  • Lithuania - i.SAF / i.MAS
  • Norway - Peppol BIS 3.0 (B2B), SAF-T
  • Poland - KSeF
  • Portugal - ATCUD/QR, SAF-T PT
  • Slovakia - eKasa
  • Slovenia - fiscalization (davcno potrjevanje)
  • Spain - FacturaE, SII, VeriFactu, TicketBAI
  • Sweden - SKVFS (certified cash registers)
  • Argentina - ARCA (Q4 2026)
  • Australia - Peppol PINT A-NZ (Q4 2026)
  • Brazil - NFe, NFCe, NFSe (Q4 2026)
  • Chile - SII Chile (Q4 2026)
  • Colombia - DIAN (Q4 2026)
  • Finland - Finvoice, TEAPPSXML (Q4 2026)
  • Japan - JP PINT (Peppol) (Q3 2026)
  • Malaysia - Peppol Malaysia (Q4 2026)
  • Mexico - CFDI (Q4 2026)
  • New Zealand - Peppol PINT A-NZ (Q4 2026)
  • Peru - SUNAT (Q4 2026)
  • Romania - Peppol (RO e-invoice) (Q4 2026)
  • Saudi Arabia - ZATCA (Q4 2026)
  • Singapore - Peppol BIS 3.0 (Q4 2026)
  • United Arab Emirates - Peppol (5C) (Q4 2026)

Standards & Frameworks

  • Cyber Essentials Certified
  • SOC 2 Type II - audit in progress
  • ISO/IEC 27001 - audit in progress
  • NIST Cybersecurity Framework - aligned
  • NIST Privacy Framework - aligned
  • NIST SP 800-53 / 800-63 / 800-63B - aligned
  • NIST AI Risk Management Framework - aligned
  • CIS Critical Security Controls / CIS Benchmarks - aligned
  • OWASP ASVS & OWASP Top Ten - aligned
  • ISO 25010 (quality) - aligned
  • ISO 31000 (risk) - aligned
  • ITIL - aligned
  • W3C Web Standards - aligned
  • OpenAPI Standard - aligned
  • DevSecOps practices - aligned
  • ePrivacy Directive - aligned
  • EU Whistleblowing Directive (2019/1937) - aligned

Payments Compliance

  • PCI DSS Level 1
  • PSD2 / Strong Customer Authentication
  • 3D Secure (3DS)
  • EMVCo Level 1 & 2
  • AML / KYC controls
  • Sanctions screening (OFAC, UN, EU, HMT)

International Data Transfer Mechanisms

  • EU-US Data Privacy Framework
  • EU Standard Contractual Clauses (Decision 2021/914) - Modules 2 & 3
  • UK International Data Transfer Agreement (IDTA) + ICO Addendum
  • Swiss FDPIC-recognised transfer mechanisms
  • APEC Cross-Border Privacy Rules (CBPR)

Accessibility Compliance

  • ADA (Americans with Disabilities Act) - aligned
  • European Accessibility Act (EAA) 2025 - aligned
  • WCAG 2.2 - aligned
  • EN 301 549 - aligned
  • WAI-ARIA - aligned

Eine Plattform für Hotels, Spas, Kurse, Veranstaltungen und Restaurants.

Tiquo Ltd
London, Vereinigtes Königreich

LinkedInTop Performer Spring

Wir verwenden Cookies

Sie können Cookies für Analysen und Werbung akzeptieren oder ablehnen. Wenn Sie diesen Hinweis schließen, werden diese Cookies abgelehnt.

Mehr erfahren