Contact person: Business Client

Phone:Show

Email:Show

Location: Chalandri, Greece

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"We are a small food retail chain (ready-made meals, no tables, no waiters, no kitchen interaction) and we want to develop a very simple, web-based POS software customized for our needs.
This is NOT a restaurant system with tables, waiters, KDS, or complex operations. It is a single cash register per store, with a fixed menu and very basic day-to-day functions.

We are open to using an existing open-source POS as the base (e.g., OSPOS, WallacePOS), or any other modern framework you recommend — as long as the code is clean, maintainable, and easy to extend.

This project is Phase 1 (MVP). Functionality must stay minimal and stable.

⸻

Core Requirements (MVP)

1. POS UI (Single Terminal per Store)
– Simple, clean POS interface.
– Display menu items (products) grouped into categories.
– Add/edit menu items easily from the admin panel.
– No mobile devices, no tables, no kitchen printers. Just one terminal.

2. Multi-Store Environment
– Each store uses its own POS login.
– Franchisee can see ONLY their own store(s).
– Franchisor (HQ) has access to all stores’ data.
– Simple dashboard for daily/weekly/monthly sales per store and aggregated.

3. Access Levels
– Store cashier
– Store manager
– Franchisee
– Franchisor (HQ)

4. Basic Inventory (Very Simple Logic)
We do NOT need full warehouse management. Only:
– Starting stock for the day
– Received stock
– Sold quantity
– Remaining stock
A very lightweight “inventory snapshot”, not a full ERP.

5. API-Ready / Integrations
We do NOT need integrations in Phase 1, but the system must be prepared:
– Open API endpoints so that we can later connect local tax systems (we will handle this part separately).
– Open API endpoints for future integration with delivery platforms (eFood, Wolt).
– Optional but helpful: integration-ready structure for card terminals (Viva, Nexi, etc.) — no need to implement now.

6. Technology Requirements
– Web-based (PHP/Laravel, Node/MERN, or similar).
– Clean code, modular structure, clear documentation.
– Should run easily on a simple cloud server (Ubuntu).
– Database: MySQL or PostgreSQL preferred.

⸻

What We DON’T Need

To avoid misunderstandings, we do NOT need:
– Table management
– Waiters
– Kitchen display systems
– Complex stock workflows
– Mobile apps
– Multi-device syncing
– Complex accounting modules

⸻

Deliverables (Phase 1)

– Working POS (web-based) with admin panel
– Multi-store system with roles
– Basic inventory logic
– Simple sales reports
– User-friendly UI
– Installation guide + documentation
– Source code included
— Optional: Customer loyalty programs

⸻

Developer Requirements

– Experience with POS systems OR ERP-like systems
– Strong backend architecture skills
– Ability to work with open-source POS forks (optional but helpful)
– Clean coding standards, version control, documentation
– Communication skills and ability to collaborate asynchronously

⸻

Budget

We have a limited budget for Phase 1, but the project will expand in later stages (integrations, mobile dashboards, franchise modules, etc.).
Developers who can propose a structured MVP-first approach will be prioritized.

⸻

How to Apply

Please include:
1. A short description of relevant experience.
2. Links to similar POS or management systems you’ve built.
3. Proposed tech stack.
4. Rough cost & timeline for the MVP." (client-provided description)