Scan. Order. Pay. Enjoy.
A restaurant ordering system built around the way service actually works.
Scorpaq connects guest ordering with preparation, service and daily operational visibility so teams can see what is happening without adding unnecessary complexity.
Concept previewEarly Access — product in development
Restaurant Guest
Restaurant Guest
- Scan
- Browse
- Order
- Pay
No. The core guest journey works in a phone browser without an app download. No. Persistent guest account creation is not required for browse, order or payment.
Illustrative layout; example states only. No live product or customer data.
Ordering starts with the guest, but it does not end there.
Guests can begin from a table or a configured takeaway or pickup point. The service location stays with the order so the team can understand where it came from and how it should be fulfilled.
Keep kitchen and service in the same flow
Clear order states help the kitchen see what needs preparation and the service team see what is ready. Everyone follows the same operational progress without turning the guest journey into a separate system.
- Order received
- Preparing
- Ready
- Served or completed
See where service is slowing down
Track the time from order receipt to preparation, ready status and completion. This helps managers see where delays are forming without promising that software alone will make every service faster.
Availability changes the meaning of sales
A product with few sales may have been unavailable for part of the day. Keeping availability alongside sales data gives managers the context needed to interpret product performance more carefully.
Keep exceptions visible
Voids, comps, discounts and authorised changes are part of daily restaurant operations. Scorpaq keeps who made the change, why it happened, when it happened and its value available for review. It does not present this as accounting or fraud detection.
Understand more than sales alone
Sales, product cost, volume, contribution, service time, availability and exceptions provide a fuller operational view. When cost information is incomplete, Scorpaq should not present the result as definitive profitability.
Not another POS replacement
Scorpaq focuses on guest ordering, service operations and business performance. It is not positioned as a full POS, accounting, payroll, procurement or inventory ERP.
Explore restaurant ordering in context
Concept previewEarly Access — product in development
Operations overview
Service flow
- Received
- Preparing
- Ready
- Delivered
Attention
Review before drawing conclusions
Illustrative layout; example states only. No live product or customer data.
Operational context
Orders, attention items, operational visibility, revenue signals and intelligence, with honest data-quality boundaries.
Example situations to review
- Sales increased, but average order value fell.
- Your best-selling item was unavailable for an extended period.
- Evening service took longer than the recent average.
- Voids and comps increased noticeably.
- Cost information is missing for some high-selling items.
FAQ
Questions businesses ask
What does a restaurant ordering system do?
It connects guest ordering with preparation, service and the operational information managers need to follow the day.
The intended flow links the table or other service point to the order, preparation and service status. Teams retain responsibility for fulfilment and handling exceptions.
Can guests order from their own phone?
Yes. Guests can scan, browse and order in their mobile browser.
Guests enter through the business’s QR link and use the available menu in their browser. The service points and payment options depend on that business’s setup.
Can it support takeaway as well as dine-in?
Yes. Orders can retain table, takeaway or pickup context when those service locations are configured.
A table, room or pickup point must be configured before it can supply order context. The link identifies that point; it does not automatically detect where a guest physically moves.
Does Scorpaq replace a POS?
No. Scorpaq is not positioned as a POS replacement.
Scorpaq does not promise automatic synchronisation with an existing till, hotel system or accounting package. Any separate workflow and its limits should be assessed before a pilot.
Can managers see service delays?
They can review the time between key order and service stages to see where work is slowing down.
Compare receipt, preparation, ready and delivery timestamps to find which stage needs attention. A longer time identifies a place to investigate, not an automatic cause or a guaranteed service improvement.
Can unavailable products be tracked?
Yes. Availability context can be kept alongside product performance.
Availability needs to match the configured outlet or service area and the menu shown to guests. This is an operating control, not a promise of automatic stock synchronisation with another system.
Can voids and comps be reviewed?
Yes. Relevant exceptions can retain who, why, when and value information for review.
Review an exception with its recorded actor, reason, time and value where those details exist. Missing context should remain visible; a void or comp alone does not prove misconduct.