01 /
Set up your restaurant.
Organise the outlet, menus and configured users, devices and operating areas during onboarding.
A practical operations model
Close to the floor. Connected to the bigger picture.
ThinkTable is designed around local restaurant workflows, with cloud-connected management and a device approach that fits daily service.
DESIGNED FOR THE FLOOR.
Local speed. Connected perspective.
Outlet-side Windows Edge operation and cloud management serve different roles within the ThinkTable architecture.
Service journey
A more connected day, from opening to close.
02 /
Take and prepare orders.
Teams take orders and support kitchen handoffs through the configured POS and preparation workflows.
03 /
Bill and close service.
Complete restaurant billing and supported payments based on the channels enabled for your outlet.
04 /
Keep stock and operations visible.
Manage inventory, procurement and costing capabilities according to the modules deployed.
05 /
Review the business.
Use reports and connected management experiences to see activity across restaurants.
How the system connects
Restaurant devices and cloud management, each with a role.
Rather than placing every action behind a constant internet connection, the architecture places an Edge controller at the restaurant to carry supported local operations.
- Windows Edge controller per outlet
- Android 8+ captain-device direction
- Kitchen display through a browser device
- Printer-agent support for local printing workflows
- Cloud sync designed around five-minute intervals
Technical illustration in words
Operational layers.
On sitePOS terminals · captain devices · printers · KDS
Outlet EdgeLocally managed supported restaurant traffic
SyncData exchange to the cloud, connectivity permitting
CloudOrdering, reporting and applicable shared management
This is a conceptual architecture explanation, not an actual UI screenshot or a service-level commitment.Connectivity
What happens when the internet drops?
Supported outlet-local workflows are designed to continue through the Edge setup. Services requiring remote connections, such as external payment or aggregator APIs, may be affected until connectivity returns.
Integration readiness
Third-party connectivity is specific to each rollout.
Availability varies by external provider, agreement, onboarding status and testing. We confirm what is working in your target deployment before making a commitment.
Talk through your installation
