QwikPass
Implemented in the pilot buildCounter billing & invoices

Bill the guest. Record the restaurant payment. Issue the invoice.

Cashiers select items from the outlet menu, add customer details only when provided, record the payment method confirmed by staff and create a private invoice record.

At the counter

The restaurant owns the menu, payment method and invoice data.

Select the order

Use menu items, categories, prices, tax rates, optional SKU/HSN data and item availability configured by the organization.

Ask, do not require

Name and mobile remain optional for counter service. Digital delivery requires the guest’s chosen channel and applicable consent.

Confirm receipt

The guest pays through an outlet-enabled method. QwikPass records the staff confirmation; it does not independently verify counter receipt.

Issue once

A completed paid order receives an immutable private invoice record and remains in that outlet’s history.

Responsibility boundary

Generated from restaurant-supplied details.

Seller identity, GSTIN where applicable, address, item/tax settings, invoice fields and payment confirmation come from the restaurant. The restaurant remains responsible for accuracy, numbering, statutory wording, tax treatment and compliance. Final production templates require accountant and legal verification.

Requires production/provider activation

WhatsApp, SMS and transactional email

Private invoice links and browser-based pass updates exist in the pilot build. WhatsApp/SMS invoice delivery and mandatory login-email delivery require configured providers, approved templates, consent handling and failure/retry operations before they are described as live.

Configure the counter before the first shift.

Add the outlet menu, legal seller fields, payment methods and invoice format in pilot setup.

Open pilot setup Read the security controls