01 / Review the workflow
Maintain dishes, drinks, allergens and languages in one place. Guests open your menu without installing an app.
DataKG-NET / BUILT AROUND YOU
Digital QR menus for restaurants.
01Data02Workflow03Approval
KG-NET / Digital QR menus for restaurants
Keep your menu up to date
Planning, design and technology are considered together. Scope and price follow your actual requirements.
01Data02Workflow03Approval
KG-NET / DIGITAL DEVELOPMENT
From building blocks. To your system.
Content, design and interfaces work together. We build a digital presence that visitors can understand and your team can use.
Explore our services ↗Digital QR menus for restaurants
How it comes together.
Three perspectives on your project. Scroll through the process or select a step.
02 / Test interaction
Compare the demo with your daily tasks together.
Workflow03 / Support rollout
Review data, integrations and training before launch.
ApprovalWORKING TOGETHER
Clearly agreed. Clearly delivered.
A defined scope
Before work begins, we agree goals, content, responsibilities and integrations. You know what is included and what needs a separate plan.
Reviewable milestones
Structure, design and function are reviewed in clear stages. Decisions follow your requirements and feedback.
A clear handover
The agreed scope defines access, guidance and an understandable operation and maintenance plan. Ongoing support is agreed explicitly.
IN DETAIL
Digital QR menus for restaurantsLet’s talk ↗Digital QR menus for restaurants. Maintain dishes, drinks, allergens and languages in one place. Guests open your menu without installing an app.
What your system covers
Categories, product availability and price updates. Maintain dishes, drinks, allergens and languages in one place. Guests open your menu without installing an app.
Planning before development
We start by reviewing user roles, existing data, daily tasks and required integrations. Together we define the first release and features that can follow later. This gives you an agreed scope, practical priorities and a way to assess delivery against your business needs.
Working across your devices
Forms, tables and key actions are designed for desktop, tablet and phone. Keyboard interaction, clear labels and useful validation messages are part of the implementation. The demo illustrates core interactions; your final interface is adapted to your brand, workflows and actual data.
Integration and responsibilities
Integrations follow a review of documentation, access rights and technical limits. A demo does not establish approval for tax reporting, fiscal receipts, payment services or health data processing. Required providers, agreements, local requirements and responsibilities are defined before production launch.
Testing, rollout and training
Before launch we test agreed scenarios, access permissions, imports and failure cases. Your team receives practical training and usable documentation. Maintenance, backups and response times are defined in the offer. Discuss your requirements with us and compare the demo against your own daily workflows.
Digital menu without another app
Guests scan a QR code and open your menu in their browser. A stable address means table cards do not need replacing after every price change. We agree categories, product images, portions, prices and supported languages for your project. Your business provides allergens and mandatory information and reviews them before publication. We do not invent ingredients or claim automatic legal approval. Keep an alternative way to access the current menu during disruptions. Guest ordering additionally requires agreed table allocation, confirmation and staff handover. The QR demo shows a sample catalog and a simulated order checkout.
20 / QUESTIONS & ANSWERS
Decide with clarity.
How are interfaces selected?
We review documentation, permissions, data fields and operational limits. A stable supported API is preferable to unclear access.
Who decides in automated workflows?
Approval points are explicit. Purchases, sensitive changes and payments do not proceed unchecked on an Intelligent automation decision.
What happens if an API fails?
Errors are recorded and retries limited. Last known data carries a timestamp and missing data is not invented.
How is duplicate processing avoided?
Unique event identifiers and defined state changes help handle retries safely. Typical failure scenarios are tested.
Can barcode and QR workflows be integrated?
Yes, if scanners, identifiers and the target system align. We clarify whether a code represents a product, batch or process.
Where is Intelligent automation useful?
In bounded tasks such as suggestions or classification whose quality can be assessed. Data access and human review stay explicit.
How are secrets stored?
Tokens and keys belong in protected server-side storage. They are not exposed as browser data or unprotected text fields.
Can the system be extended later?
Modules and documented interfaces limit dependencies. Extensions are checked against the data model, permissions and existing workflows.
How does the project start?
We clarify the audience, existing systems, responsible people and intended outcome, then agree the scope.
What determines the price?
Scope, integrations, content, licences and support are considered separately. You receive an individual offer before delivery starts.
When is the schedule agreed?
After discovery and prioritisation we agree milestones. Approvals, access and external dependencies influence dates.
Who supplies content and access?
We agree which text, images and data you provide. Access should use roles, invitations or limited tokens wherever possible.
Can existing systems keep running?
Yes, subject to a technical review. We plan changes, backups and rollback paths to keep the transition controlled.
How are changes agreed?
Questions are collected in the project. Extensions get a defined scope and approval before additional implementation.
How is acceptance handled?
We agree concrete test cases and responsible people. Open issues are documented and release follows the agreed approval.
Is a handover session included?
Handover can include training, documentation and defined access rights. The scope and format are specified in the offer.
What happens after launch?
Support, updates and response times are agreed separately, making internal and KG-NET responsibilities clear.
How is personal data handled?
We limit access and review data flows, retention and processor arrangements. Legal approval remains with the controller and their advisers.
Can you work across borders?
We work with businesses in Austria, Germany, Switzerland and Serbia. Language, responsibilities and actual market needs are agreed together.
How are outcomes assessed?
We agree verifiable goals and identify the data source. Without connected measurement there are no invented metrics or guaranteed outcomes.
Explore a working example
Open a complete example website, explore its services and try the included software with sample data.
KG-NET Restaurant System
Table layout and order taking. Test the workflow in your browser and switch between desktop, tablet and phone. Your project is adapted to your content, user roles and integrations.
Open live demo: KG-NET Restaurant System ↗KG-NET QR Menu
Digital menu and demo cart. Test the workflow in your browser and switch between desktop, tablet and phone. Your project is adapted to your content, user roles and integrations.
Open live demo: KG-NET QR Menu ↗THE NEXT STEP
Your idea. A clear plan.
Tell us what you want to change. We will clarify goals, scope and the right approach, with an individual proposal.
KG-NET DIGITAL SOLUTIONS DOO BEOGRAD
Registered office and invoicing: Luneta Milovanovića 13, 11130 Kaluđerica, Srbija
PIB: 116021725 · MB: 22339117
Contact office: Takovska 45, 11000 Beograd, Serbia
+43 660 1206452 · info@kg-net.com
Monday–Friday 09:00–17:00 · Closed Saturday/Sunday (Belgrade office time)
Location on Google Maps