Pāriet uz galveno saturu
Visi raksti
POSJul 11, 2026

How to take collection orders through your own restaurant website

To take collection orders through your own restaurant website, you need an online menu guests can order and pay from, a way for those orders to reach the kitchen at the right time, collection slots the kitchen can meet and a clear handover at the door. The ordering page can be a hosted page from your ordering or POS provider that your site links to, a widget embedded in your own pages, or a custom build using the provider's API.

Ordering on your own site keeps the order, the payment and the customer relationship with you, without a marketplace in between. The trade-off is that customers have to find your website, where a marketplace app would have put you in front of people already browsing for dinner.

Why take collection orders directly?

Marketplace apps can bring customers who would not otherwise find you, and they charge restaurants for that under their own terms. Direct collection orders avoid those charges, though you still pay card processing on each payment and any fees your ordering provider charges.

The bigger benefit is the relationship with the customer. Someone who orders directly can be recognised next time, earn rewards if you run a loyalty scheme and hear about a new menu if they have agreed to marketing.

What are the options for ordering on your website?

OptionHow it worksSuits
Hosted ordering pageYour provider hosts the menu and checkout, and your site links to itVenues that want to start quickly with little web work
Embedded widgetThe provider's ordering flow sits inside a page on your siteVenues that want guests to stay on their own domain
Custom build with an APIYour developers build menu and checkout pages against the provider's APIGroups with developers and specific design or app requirements

Whichever you choose, web orders should arrive in the same POS and kitchen workflow as dine-in orders. A separate tablet that pings with web orders is easy to miss on a busy night, and re-entering orders invites mistakes. Ask any provider to show you a test order travelling from the website to the kitchen before you commit.

How to set collection slots the kitchen can meet

Collection goes wrong when food is not ready at the promised time, or was ready long before and has gone cold. Plan capacity before you switch ordering on:

  • Limit orders per time slot based on what the kitchen can produce alongside dine-in covers
  • Set a minimum lead time, and lengthen it on busy nights
  • Give a manager a way to pause ordering or extend lead times during a rush
  • Time when orders reach the kitchen so food is finished close to the collection slot, if your system supports it
  • Stop taking orders a set time before the kitchen closes

What does the ordering page need to show?

Show prices, including any packaging charge, along with modifiers, the collection address and instructions, and the hours you take collection orders. Take payment online when the order is placed, so an order that is never collected has at least been paid for.

Allergen information has a specific legal requirement here. Ordering by phone or online counts as distance selling, and the FSA's technical guidance says businesses selling non-prepacked food this way must make mandatory allergen information available, free of charge, before the purchase is concluded and at the moment of delivery. That guidance covers England, Wales and Northern Ireland.

For collection, a practical approach is allergen details on the ordering page, a question at checkout asking about allergies, and written information with the order at handover, such as a label on the container. The FSA's best practice guidance recommends written allergen information both before the food is ordered and when it is delivered. This is general information, so check the FSA's current guidance for your situation.

How to run the collection handover

  • A clear collection point away from the dine-in queue, with a sign
  • Order numbers on the bag and the confirmation, checked against the customer's name
  • Hot and cold items bagged separately and sealed
  • A message to the customer when the order is ready, if your system can send one
  • A rule for orders still uncollected at closing time

How to get customers ordering direct

Put the order button at the top of your homepage and menu page, on your social profiles and in confirmation emails for table bookings. In the restaurant, a QR code at the till or on takeaway bags points regulars to the direct route. If customers have agreed to marketing, tell them when collection launches and when the menu changes.

How Tiquo handles collection orders

Tiquo's collection service is Order & Pick Up. Guests scan a QR code to browse your menu and order ahead, pay on their phone and collect at the counter when the order is ready. You choose which sublocations offer it, and Order to Table can run alongside it for guests already seated.

Orders come into the Tiquo POS alongside dine-in orders and use the same menus, so the team works from one list instead of a separate tablet. Payments run through Stripe, which Tiquo's payments are built on. Guests collect when the order is ready rather than at a booked time, so let them know how long orders usually take, for example in your menu descriptions or on a sign at the counter.

On your website, Tiquo's Website SDK adds passwordless customer login and a signed-in customer's profile, orders, bookings and wallet cards to sites built on Webflow, Framer, WordPress, Wix or plain HTML, without a build step. Its published features do not include a menu and checkout for collection orders, so if guests must be able to order from your own pages, ask Tiquo what would work for your build before you plan around it. Our guide to QR code ordering covers the in-venue side.

© 2026 Tiquo. "Tiquo" un Tiquo logotips ir Tiquo Ltd reģistrētas preču zīmes.

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

Vienota platforma viesnīcām, SPA, nodarbībām, pasākumiem, restorāniem un vēl daudz kam.

Tiquo Ltd
Londona, Apvienotā Karaliste

LinkedInTop Performer Spring

Mēs izmantojam sīkdatnes

Izvēlieties, vai atļaut analītikas un reklāmas sīkdatnes. Varat piekrist vai noraidīt to izmantošanu. Aizverot šo paziņojumu, jūs tās noraidāt.

Uzzināt vairāk