Restaurant · Ordering
Leckaros: from menu to order
An ordering website connected to payment, kitchen and administration workflows.
- My contribution
- Web application development & integrations
- Public website
- leckaros.de ↗
Problem
A restaurant ordering system needs to carry the same order from the customer’s menu choices through payment and preparation. Delivery rules and product options are part of that flow.
Approach
Connected the menu, cart and checkout with server-side order checks, payment integrations and order-management screens. The application also includes kitchen-print views and accounting exports.
Built into the project
Customers can browse the menu and start a delivery or pickup order. Behind the public website, the implementation connects orders with payment state, kitchen views and accounting records.
How the workflow connects
Menu & options
Checkout
Payment status
Kitchen & orders
Built with
- Next.js
- TypeScript
- Supabase
- Stripe
- PayPal
RefurbX: a shop connected to stock
A clear first step
Start with one workflow.
A 15-minute introductory call with Khaldoon. Bring a recurring task or a process that keeps getting stuck. We’ll discuss the bottleneck and whether a focused pilot is worth exploring.
Book a 15-minute introductionNo project commitment. Scope and pricing are agreed before paid work starts.
Describe your workflowBring one example
An enquiry, order or recurring report. Describe the tools and handoffs involved.
Agree what needs to improve
Identify the bottleneck, the people involved and what a useful result would look like.
Decide on a small next step
If there is a fit, scope a pilot with its cost, responsibilities and success criteria before starting.
Before we work together
Will I speak to the person building the system?
Yes. You speak directly with Khaldoon. If a project needs other specialists, their roles are discussed as part of the scope.
Can I expect the same results as these projects?
The projects show what has been built. Your result depends on your process, data and team. We agree how to measure success before a pilot; no savings percentage is promised here.
Do I have to replace the tools I already use?
We first examine your existing workflow and integrations. Any proposed replacement, data access or ongoing service cost is discussed before implementation.