Stripe
Plan checkout and subscription webhooks are present when Stripe is configured.
Restaurant operations platform / Early access
CrysoLabs Restaurant POS
Run cashier orders, kitchen status, menu inventory, staff access, and reports from one workspace.
CrysoLabs Restaurant POS connects the front counter, kitchen, manager dashboard, inventory, team access, billing, mobile analytics, and desktop customer display into a focused operating system for restaurants that want cleaner service workflows without claiming enterprise complexity before it is proven.
Problem
Restaurants need fewer handoffs during service.
- Cashier orders and kitchen updates are easy to lose during busy service.
- Menu, stock, staff roles, and daily reporting often live in separate tools.
- Owners need visibility without standing at the counter all day.
Product promise
A focused path from order entry to kitchen clarity.
- Enter dine-in, takeaway, delivery, or online-channel orders from the POS.
- Send orders to a kitchen display with live status updates and polling fallback.
- Manage menu items linked to inventory records and reduce stock on orders.
- Give owners and managers mobile access to orders, inventory, menu details, and analytics.
Workflow
Service workflow
This is the practical path verified from implementation, not a wishlist of future capabilities.
01
Create or onboard the restaurant workspace
02
Set restaurant settings and invite staff roles
03
Create inventory items and menu items
04
Enter a dine-in, takeaway, delivery, or online-channel order
05
Send the order to the kitchen display
06
Update kitchen status as food moves through preparation
07
Review sales, low-stock items, and reporting from dashboard or mobile
Verified features
What the product can honestly claim today.
Each feature below is backed by implementation evidence from schemas, server actions, routes, APIs, or client screens.
Core features
Cashier POS terminal
The POS screen supports searchable categories, item cards, cart quantity controls, table and customer fields, order channels, queued-order indicators, and a send-to-kitchen action.
Kitchen display workflow
Kitchen staff can view new, in-progress, and completed orders, update statuses, reconnect realtime events, and fall back to polling.
Menu-linked inventory
Menu items connect to inventory items; order creation validates menu ownership and decrements linked inventory stock.
Additional capabilities
Role-aware team access
Restaurant memberships, invitations, and roles separate admin, manager, cashier, kitchen, and staff responsibilities.
Owner dashboard and reports
The app calculates daily, weekly, and monthly sales, category sales, top-selling items, recent sales, low-stock alerts, and report exports.
Mobile management companion
The Expo app authenticates with secure token storage and exposes orders, inventory, menu images, settings, restaurant switching, and analytics screens.
Premium path
Reports and mobile analytics
Plans gate reports, mobile analytics, extended analytics, customer display, and desktop app access through entitlement checks.
Desktop customer display
The Electron shell can open, focus, fullscreen, and position a customer display window on connected screens.
Manual and Stripe billing paths
Subscriptions support Stripe checkout where configured and manual payment proof review with R2 storage.
Product screens
Cashier, kitchen, menu, and inventory views.
Screenshots are pulled from existing product assets and repository screenshots rather than stock imagery.
Integrations
Connected where the workflow needs it.
Cloudflare R2-style storage
Media and payment proof uploads are stored through R2 helpers when configured.
Realtime events
Order, menu, inventory, and dashboard updates publish through realtime helpers with polling fallbacks in key screens.
Electron desktop shell
The desktop app packages the POS web app with tray, updater, recovery, and display-window controls.
Current limitations
What we are not claiming yet.
These gaps are intentionally visible so the product pages stay accurate while the roadmap continues.
No verified shift closing, cash register, receipt printer, modifier, tax, loyalty, or purchase order workflow was found.
Offline support should not be marketed as a full guarantee; the code shows queued-order indicators, sync routes, and reconnect behavior.
Branch management is represented as multiple restaurant workspaces rather than a dedicated branch entity.
FAQ
Common product questions.
Is Restaurant POS self-service?
A demo-led setup is recommended because restaurant onboarding depends on menu, inventory, staff roles, devices, and service flow.
Does it support kitchen displays?
Yes. The kitchen display page handles new, in-progress, and completed order states with realtime and polling behavior.
Can we claim full offline POS operation?
Not yet. The code includes queued-order indicators, sync routes, and desktop recovery screens, but a full offline guarantee was not verified.