Chuyển đến nội dung chính
Tất cả bài viết
OperationsMay 27, 2026

Digital cloakroom tickets: running a coat check without paper tickets

Digital cloakroom tickets replace the torn paper ticket with a record. Each item gets a tag with a unique number, and staff link that tag to the person who handed the item over, usually by finding them in the venue's customer records. At collection, staff scan or look up the tag, and the system shows whose item it is and whether it has been collected.

The approach suits members' clubs, hotels and event venues with a staffed coat check, especially where the same members come back week after week.

How does a traditional coat check work?

The classic system uses paired tickets or numbered hangers. One half of the ticket goes on the hanger, the guest keeps the other, and the numbers match. It costs little and staff learn it quickly. The weak points show up late in the night: a guest who has lost the ticket and can only describe a black coat, tickets that end up on the wrong hanger, a rush when everyone leaves at once, and no record of who left what once the tickets are gone. Paper tickets also run out and need reordering, and numbered hangers only work while every hanger keeps its number.

What makes a cloakroom ticket digital?

A digital system keeps the physical tag and changes what it is attached to:

  • Each tag has a unique number, so two items can't share one.
  • The tag is linked to a named person in your customer records, not just to a matching paper stub.
  • Each tag has a status, such as in use or returned, and staff can see every tag in use.
  • The link is a record, so it can be looked up later if something goes wrong.

Members get the most from it, because staff can find them by name or from their membership card, so there is no ticket to lose. Walk-in guests need a record too, so decide whether staff create one at drop-off or hand them a numbered stub to keep.

How to choose cloakroom tags

Tags take the handling that paper tickets used to, so choose them to last and to read quickly: a clear number, a shape that hangs securely on your rails and a material that suits the look of the room. Keep spares, because tags get lost and damaged.

A tag with a QR code as well as a printed number lets staff scan it instead of typing the number, which saves mistakes at the end of a long night. If the tags show your logo, check that the number stays easy to read from a few feet away.

How to set up a cloakroom for busy nights

Plan capacity from the arrival peak. Say 300 guests arrive between 7pm and 8pm and 60% of them check a coat. That's 180 items in an hour, or three a minute, and departures can bunch even more tightly at the end of an event. A few practical choices make the difference at those peaks:

  • Separate drop-off and collection points where you can, so the two queues don't block each other.
  • Number the rails in zones so staff go straight to the right section.
  • Put more staff on the end of the night than the start.
  • Decide what you accept, such as bags, umbrellas and luggage, and whether you refuse valuables.
  • Keep an unclaimed-items log with the tag number, date and a description.
  • Train everyone who might cover the cloakroom on the process, so a break or a sudden queue doesn't leave one person stuck.

If you charge for the cloakroom, take payment at drop-off, so collection is just a scan and a hand-over. Hotels can use the same tag model for luggage held before check-in or after check-out, which poses the same question: who handed this over, and can the person collecting it prove it's theirs?

Lost tags, disputes and liability notices

Agree the lost-tag process before you need it. Ask the guest to wait until the rush has passed, check identification and a description against what is left, and record who collected what. With a digital system, a member's coat can be found through their profile, and a guest's item can be narrowed down from the tags still in use.

The same list helps at closing, because the tags still in use tell you what's left on the rails. For a member's item you know whose it is and can get in touch the next day, and for a guest's item you have the tag number to go on when someone calls about it.

If you display a sign saying items are left at the owner's risk, know its limits. Under the Consumer Rights Act 2015, a notice that tries to exclude or restrict a trader's liability to a consumer is a consumer notice, and an unfair one is not binding on the consumer. The rules cover spoken announcements as well as written signs. A sign doesn't replace a careful process, and the wording is worth checking with an adviser. This is general information, not legal advice.

How Tiquo's cloakroom management works

Tiquo's Cloakroom Management records each numbered tag against the customers it belongs to. Every tag has its number on the front and a QR code on the back. In the Tiquo app, staff scan the tag's QR code or type its number, choose the customer, or more than one customer if a couple or group share a tag, and assign it to the sublocation where the item is stored. When the item goes back to its owner, staff mark the tag returned, or lost if it has gone missing.

Under Settings > Cloakroom, the Tags In Use table lists every tag currently assigned, with the customer, sublocation and status, and you can filter it by sublocation, which is the list to check at closing. A customer's active tags also show on their profile. The same page has a tag designer for previewing shape, material (black, red, blue or white plastic, stainless steel or brass), font and a one-colour logo for laser etching. Ordering tags from it is marked as coming soon.

Members can carry a Tiquo digital membership card in Apple Wallet or Google Wallet, and scanning its QR code opens their profile, so staff can find the member, and the tags held for them, without a paper ticket.

© 2026 Tiquo. "Tiquo" và logo Tiquo là thương hiệu đã đăng ký của 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

Quản lý khách sạn, spa, lớp học, sự kiện và nhà hàng trên cùng một nền tảng.

Tiquo Ltd
London, Vương quốc Anh

LinkedInTop Performer Spring

Chúng tôi sử dụng cookie

Bạn có thể chấp nhận hoặc từ chối cookie dùng cho phân tích và quảng cáo. Đóng thông báo này cũng đồng nghĩa với việc từ chối các cookie đó.

Tìm hiểu thêm