Emil DanielA display should be readable in the venue. A phone menu should be easy to explore. I design each for the way customers use it.
Discuss your menuWe start with what your business needs now. You receive a clear proposal explaining what is included and the ongoing management costs.
Management for systems with ordering, payments, bookings or integrations starts from 99 RON/month and is scoped to the project.
Products, prices and promotions in a layout designed to be read on screen. A discreet small computer runs the menu, and I handle the setup and updates agreed for the project.
130 g
130 g · Example price: RON 23
Select Soup of the Day for the RON22 offer. The regular price must be higher.
Select a dish on the display or add one from the menu.
Changes apply only to this example menu. Editing access and ongoing updates are agreed for each project.
Each guest orders on their own phone. Staff see the orders for their table.
Table ordering is an optional addition to the QR menu.
Guests open the menu in their browser and explore the dishes, descriptions and prices.
Interactive example — no orders are sent to a real restaurant.
Plant-based flavours, thoughtfully chosen.
Online payment, split bills and POS integration are scoped separately around the venue’s needs.
QR menus and table ordering have their own flow. For delivery or collection, explore the same restaurant on its website.
We define the scope before implementation: what the project should do, who uses it and what a correct result looks like.
We review the current process, materials and constraints. We choose the necessary features and separate options that can follow later.
I prepare the structure and examples with relevant content. You review the information, rules and direction before completion.
I build the agreed features and test primary journeys, errors and relevant screen sizes. I also check data exchange between applications in the available test environments.
We prepare the required domain, hosting or equipment. Launch follows approval; maintenance, updates and support are agreed for the project.
Your current menu, prices, serving sizes, allergen markers, available photos and details about displays and table service. You check and approve public information.
Deliverables, responsibilities, required materials, acceptance criteria and support. Accounts, licences, hosting, equipment and third-party fees are clarified before choosing the solution.
Budget and schedule depend on that scope and the available information. You do not need a technical specification for the first conversation.
Yes. With table ordering enabled, each guest can have their own basket and order. Staff see the orders associated with the relevant table; guests do not have to share a phone.
No. Ordering and requesting the bill are separate from payment. Online payment and POS integration are scoped separately.
We agree whether I manage changes or whether an editing interface is included. Rules for unavailable products, service hours and order amendments are defined with the venue.
We check its connections, resolution, position and the conditions in the venue. Compatibility cannot be assumed for every screen.
Not automatically. It opens the menu. Ordering, payment and other interactions are defined separately.
No, provided the menu keeps the same address. We update the content at that address, and the code can stay on the table.
Tell me what you would like to improve. You do not need a technical specification: briefly describe your business and the tools you use, and I will help clarify the solution.
emil@emildaniel.dev+40 774 861 042Message me on WhatsApp