Configure
Build menus, additions, pricing, taxes, currencies, restaurant availability, and delivery rules.
Product overview · Current beta build
Every part of your restaurant, in one connected system.
Sync connects your team’s workspace with your restaurant’s own customer ordering experience: menus, orders, tables, reservations, delivery, customers, and reporting in one bilingual system.
Actual beta interfaces · Illustrative restaurant data
See active tables, reservations, revenue, order performance, restaurant status, and sync health in one opening view.
One operational system
The whole product, at a glance.
Each area shares the same restaurant context, permissions, pricing, and operational data—so teams can move from setup to service and reporting without stitching together separate tools.
Menu & pricing
Products, additions, categories, taxes, discounts, and dual currency.
Orders
Delivery, dine-in, takeaway, payments, timelines, and receipts.
Service & delivery
Host Stand, tables, reservations, kitchen routing, drivers, and staff roles.
Customer ordering
Restaurant link and QR, branded menu, checkout, tracking, and accounts.
Business insight
Reports, customers, sales channels, campaigns, and exports.
How the system connects
One continuous flow, from setup to insight.
Sync is designed around the life of a real restaurant operation. Information entered at the beginning of the flow stays useful through service, fulfillment, customer follow-up, and management review.
Receive
Start from a customer order through your own link or QR, a reservation, a walk-in table, or direct staff entry.
Coordinate
Keep floor roles, table sessions, kitchen sections, order status, and staff permissions connected.
Fulfill
Collect payment, prepare receipts or kitchen tickets, assign delivery, and expose customer tracking.
Improve
Review performance, customers, products, expenses, channels, campaigns, and exported results.
The connecting idea: the same menu, price, role, order, and restaurant context moves through the operation instead of being recreated in separate tools.
01
Restaurant operations
Run service from one workspace.
The closed-beta build connects the restaurant floor with order creation and fulfillment. Teams can manage tables, seat walk-ins, create reservations, and build delivery, dine-in, or takeaway orders from the same product.
- Host Stand and reservations Service
- Pricing, taxes, discounts, and receipts Orders
- Kitchen-section routing and delivery views Fulfillment
A shared restaurant context keeps tables, order types, staff access, and pricing aligned.
02
Restaurant-owned customer experience
One configuration, both sides of the restaurant.
The customer ordering experience is not a separate product. It reads the same restaurant configuration your team manages in Sync, so what customers see follows how the restaurant actually runs. Customers usually arrive through the restaurant’s own link, QR code, or campaign and land on its page and menu.
- Restaurant availability and ordering modes Availability
- Menu, products, options, and prices Menu
- Delivery zones, fees, and order status Delivery
- Name, logo, cover, and restaurant link Identity
Interface illustration with sample data. The customer screens read the same menu, prices, availability, and order status the team manages.
More than order taking
The details around service matter too.
The current beta covers the setup before an order, the customer touchpoints around it, and the tools used to understand what happened afterward.
Setup & control
Configure the restaurant once.
Keep the operational rules that affect service in one managed context.
- Menus, categories, additions, and display order
- SYP and USD pricing with exchange-rate controls
- Taxes, discounts, delivery fees, and availability
- Restaurant visibility, hours, and service toggles
Around every order
Keep customers informed after checkout.
Customers follow their order and keep their records without ever seeing the management workspace.
- Public order status and delivery tracking
- Invoices, PDF receipts, ratings, and feedback
- Optional Telegram updates and restaurant replies
- Reservation details and confirmations
Relationships & growth
Turn activity into something useful.
Use operational history to understand demand and prepare more relevant follow-up.
- Customer records, order history, and segments
- Coupons, promotions, and campaign banners
- Top items and product-view analytics
- Filtered reports and CSV exports
Access follows the user’s role.
Not every team member sees or changes everything. Specialized kitchen and delivery workspaces stay focused, while owner and management roles receive broader operational controls.
03
Control and insight
See the operation behind every sale.
Owners and managers can review revenue, orders, customers, completion, expenses, and sales-channel performance. Date and currency controls keep the same reporting workspace useful across different restaurant contexts.
- Revenue, orders, payments, and expenses Reports
- Channel commission and price modeling Channels
- Customer records, segments, and order history CRM
Illustrative financial figures are shown here to demonstrate the reporting interface.
04
Offline workflows
Know what is ready, waiting, or needs attention.
Selected workflows stay usable on each supported device during connectivity loss. Valid cached pages can remain readable, supported changes queue locally and are reconciled with the server after reconnection, and Sync Center keeps pending work, retries, failures, and conflicts visible. Devices do not synchronize directly with one another while offline, and online-only actions wait for a connection.
Readable when preparedSupported cached information remains available with freshness context.
Queued when supportedSupported offline changes are saved and retried after the connection returns.
Protected when online-onlyActions not designed for offline use wait until a connection is available.
Visible when unresolvedConflicts and failed work remain visible for an authorized team member.
Delivery and protection boundaries
Strong systems, clear conditions.
Sync treats reliability and protection as operational systems, not blanket promises.
Notification delivery
Background push notifications on supported devices and browsers, with an in-app fallback when push isn’t available. Availability and background behavior depend on platform support, permissions, installation state, account configuration, and connectivity.
Security by design
Role-based access controls, authenticated sessions, encrypted network traffic, and permission boundaries help protect restaurant data. Additional security hardening is ongoing during closed beta.
Designed around the team
The right workspace for each responsibility.
Role-based access keeps each team member focused, while the same Sync workspace adapts across supported mobile, web, and desktop targets. Platform availability and packaging will be confirmed at public launch.
Restaurant roles
OwnerFloor managerWaiterCashierReceptionKitchenDelivery
Current build targets
AndroidiOSWeb / PWAWindowsArabic + English
Closed beta in Syria
Want to explore Sync with your restaurant?
Public access is not available yet. Join the waitlist and our team will review your request, reply within 24 hours, and plan team-assisted onboarding for accepted beta participants.
Sync is especially suited to restaurants that run in-house service and also take direct delivery or online orders, because that is where one connected system matters most. All restaurant types are welcome in the closed beta.
The waitlist is free and does not create an account or guarantee beta acceptance.