Menu
Present products, photos, video and preferences.
Dependencies: Can be used independently for menu browsing.
Combine what fits today. Features still in development are labeled before contracting.
Present products, photos, video and preferences.
Dependencies: Can be used independently for menu browsing.
Organize table requests for the team.
Dependencies: Can use an external menu. External bills are still being developed.
Route items and follow preparation and delivery.
Dependencies: Requires a configured catalog and service workflow.
Explore operational history and indicators.
Dependencies: Requires data from the modules in use.
Manage locations and corporate access.
Dependencies: Requires account and location structure.
Monthly prices on the Plans page are temporary references. Scope and final pricing still require commercial validation.
No. The current experience opens in the phone browser. The team uses the web version; a native app is a future delivery.
QR codes and static URLs allow menu browsing. Orders and service requests require an authorized visit. Secure NFC still needs physical validation before real use.
The restaurant chooses: kitchen, bar or direct waiter service. Categories set defaults and products can override them.
Compare the suggested combinations on the plans page. A proposal confirms scope, dependencies and availability; reports and groups are still planned.
The proposal can fit your usage. Specific integrations need assessment; we do not promise automatic compatibility with every POS.
We are validating the product locally. Hosting, content, NFC and operational requirements need validation before serving real customers.
Choose the combination closest to your operation and request a no-obligation proposal.