F
Fand_igor

Unified Food Service Panel with Website and Mobile App

I am currently working on a project for a unified food service panel that combines a website, mobile app, internal control panel, backend API, warehouse and procurement circuit, and integrations with external order channels. The project idea was born from market analysis and implementation practice: in most cases, the cash register, website, mobile app, SEO, internal operations, and additional services exist separately and are poorly connected.

I decided to gather all this into one product so that businesses can manage key processes from a single window, rather than building infrastructure from disjointed solutions. I initially planned the project not as a local site for one point, but as the basis for a scalable system that can be developed for coffee shops, restaurants, small chains, bakeries, and other food service formats.

What the project solves

  • combines the customer and internal circuits of an establishment into one system;
  • unites a website, mobile app, internal panel, operations circuit, and marketing foundation in one product;
  • allows for centralized management of menus, orders, stock, procurement, and points of sale;
  • forms a unified API for the website, internal panel, and bot integrations;
  • reduces dependence on fragmented services where the cash register, website, app, and promotion live separately;
  • eliminates process fragmentation and gives businesses a unified management center;
  • creates an architectural base for further development into a SaaS product for food service.

Current project status

  • the project is in active development;
  • the backend is already formed as a working API application on Laravel;
  • the client website is already assembled as a separate frontend;
  • the internal panel for personnel is separated into a discrete application and is developing as an independent circuit;
  • the architecture is pre-prepared for further scaling by roles, points, sales channels, mobile app, and additional modules.

What has already been implemented

  • a unified backend on Laravel 10 with an API-first approach and api/v1 versioning;
  • a separate client frontend for ordering and a separate internal panel for management;
  • authorization through OTP, password, and Sanctum;
  • user profile, password change, and request for phone number change;
  • menu catalog with categories, items, images, modifiers, and sizes;
  • support for additional item parameters, including sizes and modifiers;
  • order placement via the website;
  • order history and viewing order details;
  • order chat between the system and the user;
  • a separate circuit for simplified ordering via bot;
  • warehouse block with ingredients, recipes, and write-off of remains;
  • procurement requests and delivery acceptance;
  • administrative methods for working with orders, warehouse, procurement, and statistics;
  • registries of points of sale, languages, translations, loyalty levels, and legal entities;
  • activity log, employee work sessions, social network linking, and impersonation;
  • basic circuit for bot management, configuration storage, and statistics.

Technical highlights of the project

  • the architecture is divided into controllers, services, models, events, and background tasks;
  • business logic is moved to separate services, not mixed with the HTTP layer;
  • API is protected through Sanctum, middleware, rate limiting, and API keys;
  • menu is given separate protection through API key with possible restrictions by IP and endpoint;
  • a multi-point operation model is established: a menu can be available only in certain points, ingredients and remains are linked to a specific location, procurement and orders take location_id into account, and orders include an entry channel, e.g., site, bot, or point;
  • a separate layer of rights and roles is provided for customers, baristas, managers, and administrators;
  • multi-language support is implemented through language and translation tables;
  • project configuration was designed with feature flags for sequential enabling of new capabilities;
  • bot tokens are stored in encrypted form;
  • the project is built as a unified integration point for the site, panel, bots, future mobile app, and external channels.

Architectural development idea

The project has already moved beyond a typical coffee shop site. I am developing it as a platform base where business logic can be consistently expanded without rewriting the core and without scattering key processes across different services.

  • the ordering site handles the customer scenario;
  • the mobile app should provide the same unified product in a mobile format;
  • the internal panel covers personnel operational work;
  • the backend API unites all external and internal channels;
  • the bot circuit allows for connecting additional ordering and communication scenarios;
  • multi-point architecture allows for scaling the solution for multiple locations;
  • feature flags provide the ability to enable new modes sequentially, without breaking the main circuit;
  • one system can gradually gather the operational part, the customer channel, and digital promotion.

In the current configuration, further development toward the following is already envisioned:

  • online payment;
  • delivery;
  • loyalty program;
  • a more developed multi-location mode;
  • mobile application;
  • a wider administrative panel;
  • expansion to other food service formats.

My role

My role in the project spans from initial idea and architectural development to practical implementation of key system parts.

  • I conceptualize the product itself as a platform, not as a set of separate screens;
  • I analyze the market and problems of existing fragmented solutions;
  • I design the backend architecture and API structure;
  • I define the data model, entities, and scaling vectors;
  • I implement the backend using Laravel;
  • I develop the client and internal frontend circuits;
  • I design the integration between the site, internal panel, and bots;
  • I form the basis for further expansion into a full unified system for managing a food service business in one window.

Technologies

  • PHP
  • Laravel 10
  • Laravel Sanctum
  • MySQL
  • Vue 3
  • Vue Router
  • Axios
  • Ant Design Vue
  • Bootstrap 5
  • API-first architecture

Practical value of the project

  • shows that I can not only create separate modules but also design a coherent product;
  • demonstrates that I can see the market problem of fragmentation and turn it into a systemic solution;
  • exhibits systemic thinking in an applied subject area;
  • reflects work with architecture, roles, rights, orders, warehouse, procurement, and multi-point logic;
  • shows that I can build a system with future development in mind, not just for the current task;
  • emphasizes the ability to connect a product idea, backend, frontend, and integration circuit in one model.