Restaurants
Designed around table service, mixed kitchen/bar orders and check visibility.
- Product options and order notes
- Kitchen/bar station routing
- Service requests and check closure
A CONNECTED VENUE EXPERIENCE
From table to kitchen. One shared operation.
We are developing a shared journey for guests and teams, connecting menus, orders, service and checks.
In development · A presentation and design gallery. This site does not process real orders, collect payments or play music.
FROM TABLE TO OPERATIONS
The journey of a table.
The target guest journey keeps each step’s responsibility explicit. Guests can continue without an account; operations and finance are not treated as one transaction.
- 01
QR and table session
Confirm the venue, branch and table. Each device at the table continues with its own short-lived participant session.
- 02
Discover the menu
Categories, search, product information, options and availability. Venue confirmation remains important for allergen information.
- 03
Personal cart and price
Choose variants, modifiers and notes. The server calculates prices; stock or total changes require explicit approval of a new quote.
- 04
Submit the order
Track receipt and acceptance of the request. Accepted items are added to the check; submitting an order does not start payment.
- 05
Preparation and service
Kitchen and bar tasks reach the correct station. Item preparation and calls for staff are tracked through understandable states.
- 06
Participate in music
Suggest eligible tracks and vote within venue policy. Ranking is a recommendation; staff and licensing limits retain final control.
- 07
Live check
See items, the remaining amount, paid amounts and scopes reserved for payment. Viewing a check does not authorize collection.
- 08
Explicitly request the check
Start closing with a separate request. Payment options open only when the server grants access for that particular check.
- 09
Payment and reconciliation
Use an authorized provider flow; a verified notification confirms the outcome. Track receipts, POS and accounting records through controlled integration.
This journey describes the product target. Ordering, requesting the check, payment and provider actions are not enabled on this site.
Different venues. A shared operational language.
The same foundation adapts to different service styles. The aim is not to replace staff, but to create more room for hospitality and handling exceptions.
Cafés
A streamlined guest journey for drink options, quick preparation and an up-to-date menu.
- Variants and modifiers
- Product availability and menu publishing
- Personal carts and preparation tracking
Bars and social venues
Connects music participation with bar operations while retaining venue control and service responsibility.
- Suggestions, votes and moderation
- Bar station and shared check
- Staff responsibility for age and service checks
EXPLORE THE PRODUCT VISUALLY
Five applications. One connected experience.
12 original, approved target designs for the guest QR interface, MasaPass account, venue console, kitchen/bar KDS and platform administration. Not-yet-implemented screens also make the planned scope visible.
These are approved target designs, not screenshots of an operating product. Names, amounts, metrics and transactions shown are synthetic examples. Design approval does not establish implementation or production readiness.
12 design images
Guest
QR welcome and digital menu
A guest journey from table confirmation to product discovery, without mandatory membership.
Approved target designGuest
Table session and safe recovery
Clear states for invalid QR codes, session expiry and rejoining.
Approved target designGuest
Cart, order and live check
A personal cart, explicit price approval and ordering separate from collection.
Approved target designGuest
Service, check request and payment states
Service requests, a separate check request and safe guidance for uncertain payments.
Approved target designGuest
Music suggestions and votes
Participation through suggestions and votes, with venue policy and staff control.
Approved target designGuest
Recognition with MasaPass
Continue with an account or as a guest; new venue relationships require an explicit choice.
Approved target designMasaPass
Connected venues and privacy center
The planned account center for venue relationships, separate permissions and self-service.
Approved target designMasaPass
Account security and recovery
A design that makes session, shared-device and account-recovery states explicit.
Approved target designVenue
Venue operations overview
The target dashboard connects tables, orders and service within staff scope.
Approved target designVenue
Moderation, exceptions and recovery
Staff music decisions, manual mode and recovery after an exception.
Approved target designPlatform
Platform and integration management
Tenant and branch hierarchy, feature gates and connection visibility.
Approved target designKitchen / bar
Kitchen and bar work board
The target KDS experience for station ownership, items and partially ready orders.
Approved target designAN OPTIONAL ACCOUNT EXPERIENCE
MasaPass: recognition without losing control.
An optional platform account aims to reduce repeat forms at participating venues. Recognizing an account does not imply sharing information with a venue or enrolling in loyalty.
- The core QR, ordering and service journey does not require membership.
- A new venue relationship is created through an explicit choice after its scope and notice are shown.
- Each business uses its own relationship identity; other businesses’ histories do not become a shared guest profile.
- Loyalty, marketing and profile sharing are separate choices. Unlinking and withdrawing permissions are designed as separate journeys.
Approved target designMANAGED MUSIC PARTICIPATION
Contribute to the spirit of the venue.
A music experience is being designed around guest suggestions and votes, with diversity, quotas and staff moderation to protect the venue’s atmosphere.
- A suggestion or vote does not guarantee that a track will play next.
- Venue policy, cooldowns, repeat limits and moderation work together.
- Staff or the DJ retain final control; manual handling is the default without an authorized provider.
- Real playback integration can activate only after written provider permission and a valid venue license.
Approved target designFROM ORDER TO FINANCIAL OUTCOME
Each system should know its responsibility.
Ordering, checks, collection and accounting do not close under one ambiguous “success” label. The target keeps source ownership, pending transfers and recovery paths understandable.
Order ≠ collection
Accepting an order adds item charges to the check; it creates neither a payment intent nor provider collection. Requesting the check is a separate step.
Check and payment scope
Balances are designed to be reproducible from durable movements. Concurrent devices must not reserve the same amount twice.
Provider-controlled payment
The target uses hosted/redirect payment; card numbers and CVV do not enter the platform. A browser return alone is not proof of payment.
POS, ERP and reconciliation
Every connection defines its data authority and allowed actions. Pending transfers, failures and unexplained differences remain visible; a digital receipt is not assumed to replace a fiscal document.
This page activates no payment, POS, ERP or music connection. Commercial, legal and technical activation requirements must be verified separately for the relevant pilot and provider.
AN HONEST PRODUCT STATUS
Visible design. Explicit delivery gates.
Visual design, foundations present in code and an operating end-to-end product are different stages. The releases below describe planned scope, not delivery dates or available features.
Visual designs approved
The global target designs for five applications and the visual direction of this presentation site are backed by approval records.
Technical foundations developed
Domain, data, contract and verification foundations exist in the repository. Their presence does not mean guest journeys are live.
Product integrations in progress
Interface/API connections, provider prerequisites and controlled pilot verification advance through their respective delivery gates.
MVP · Planned pilot core
A dependable end-to-end table journey at one pilot branch.
- QR/table sessions, menu and personal carts
- Orders, kitchen/bar, service and live checks
- Explicit check requests and full/fixed-amount payment target
- Manual or explicitly authorized music handling
- Pilot POS connection, financial export and reconciliation
V1 · Planned commercial scope
Expand operations and business control after pilot verification.
- Reservations and advanced table operations
- Promotion rules and basic venue loyalty
- MasaPass privacy center and historical self-service
- Equal/item-based split payment and partial refunds
- Multi-branch, notifications and management workflows
V2 · Planned growth scope
New channels and deeper operations on a verified foundation.
- Takeaway and delivery
- Ingredient/recipe inventory and cost
- Segments, tiers and advanced loyalty
- Network rewards with separate enrollment and legal gates
- More integrations and advanced analytics
Trust starts in the unseen details.
These are product design and development principles, not certifications, declarations of legal compliance or measured service-level claims.
Business boundaries
Data and permissions are limited to business/branch scope. Negative tests must verify that another business’s records cannot be accessed.
Financial integrity
Amounts use minor currency units; order, payment and refund movements remain separate. Retrying a request must not create another collection.
Traceable actions
Sensitive changes require authorization, a reason and an audit trail. Domain records and event publication share a transaction boundary.
Honest failure states
A lost connection or uncertain payment is not displayed as success. Reconnection, status queries and controlled recovery are part of the product.
SSS / FAQ
Common questions
Short answers that distinguish the product target from what this site can do today.
Can I place a real order or make a payment here?
No. This is a product presentation and approved design gallery. It does not create orders, request checks, collect payments, create accounts or play music. Product journeys may activate separately after their integration and pilot gates are satisfied.
Are the images from an operating product?
No. The gallery contains original approved target designs, including screens not yet implemented. Names, orders, prices and metrics are synthetic examples, not customer or performance evidence.
Must guests install an app or create an account?
The target core table journey runs in a browser, without an app download or mandatory membership. MasaPass is optional for recognition, relationships and later account features.
Does ordering automatically start payment?
No. An accepted order adds charges to the check without initiating collection. The guest first makes a separate check request; payment options open only with server authorization and a current scope for that specific check.
Does a music vote guarantee that my track will play?
No. Suggestions and votes rank candidates. Venue policy, staff/DJ decisions and authorized provider usage limits apply. Automated playback also requires written provider permission and a venue license.
Does MasaPass share my history with other venues?
The target architecture separates each business relationship’s scope. Recognizing a global account does not share another business’s history; new relationships and profile sharing require explicit choices. Marketing and loyalty enrollment are separate decisions.
Which POS or payment providers are supported?
This site publishes no active provider list or certified-integration claim. Pilot connections are selected separately using a source-of-truth matrix, provider authorization, sandbox tests and reconciliation evidence.
When will it be ready, and what does it cost?
No verified general-availability date or commercial price list has been announced. The roadmap describes target scope. Delivery depends on real end-to-end verification, venue readiness and provider/legal gates.