Lunchub
A week of lunch orders that turns itself into kitchen labels and delivery sheets.
A corporate lunch platform: staff order a week ahead, the company holds the limit, the kitchen gets its reports.
Who it is forCompanies that arrange meals for their staff, and the catering kitchens serving them.
Discuss a projectThe task
When a company feeds its staff, the order lives in chats and spreadsheets: someone collects preferences, someone else checks who pays for themselves and who the employer covers. Before the week starts, the catering kitchen needs to know how many portions to cook and which addresses they go to. Every slip in that chain is a portion cooked for the wrong person or delivered to the wrong door.
Solution
We built a web platform with three workspaces — employee, company and provider — on Strapi with PostgreSQL and a Next.js client. An order is one record per week: each day carries its own set of products with quantities, a delivery office, a comment and a flag that closes the day for editing. The company manages branches, offices, staff, connected providers and the daily spend limit; the provider manages categories, dishes, products, main and additional menus, and hidden items. On schedule the system pulls the week's orders, renders a PDF label for every portion, builds XLSX sheets split by office, kitchen and delivery, and mails the files out.
Outcome
Instead of compiling everything by hand, the kitchen receives a finished set: portion labels carrying the address and the person's name, and tables broken down by office, kitchen and delivery. The company can see who it pays for and who pays their own way, and sets the daily limit from its own workspace without going back to a developer.
Capabilities
- 01Weekly order broken down by day: dishes, quantities, delivery office, comment, and a lock that closes a day for editing
- 02Daily spend limit set by the company, plus a flag for who pays — the employer or the employee
- 03Employee self-payment through LiqPay: invoice creation, callback handling and payment status verification
- 04Provider workspace: categories, dishes and products, main and additional menus, hidden items, image uploads
- 05Menu transfer from one provider to another, carrying categories, dishes and products while de-duplicating identical items
- 06Scheduled report generation: PDF labels via Puppeteer and XLSX sheets by office, kitchen and delivery, sent out by email
Roles
- employee
- company
- provider
- system administrator
Industry
corporate catering and lunch deliveryScreens
A similar task at your company?
This system was built around one client's process. Describe yours and we will tell you what carries over from what you see here and what has to be built anew.