Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/ytabeloved/ordervista/llms.txt

Use this file to discover all available pages before exploring further.

Ordervista is a responsive web platform that digitalizes and simplifies every step of the restaurant order lifecycle — from customer browsing and cart checkout to kitchen command generation, status tracking, and management reporting. Built on React, Node.js/Express, and MySQL, it ships a RESTful API and a role-aware frontend that works seamlessly on desktop, tablet, and mobile.

Quickstart

Set up the backend and frontend locally in under 10 minutes.

User Roles

Understand what each role — Admin, Operator, and Customer — can do.

API Reference

Explore every REST endpoint with request/response examples.

Deployment

Deploy to Vercel, Render, and Aiven MySQL in production.

What Ordervista Does

Ordervista covers the complete operational loop of a restaurant:

Menu Management

Create categories and products with pricing, stock, and images.

Order Lifecycle

Handle online and in-person orders with real-time status updates.

Kitchen Commands

Auto-generate kitchen tickets (comandas) for every active order.

Receipts

Print operational vouchers for completed orders.

Reports & Dashboard

Filter sales, top products, and average ticket by date range.

Authentication

JWT-based login with bcrypt password hashing and role enforcement.

Get Up and Running

1

Clone the repository

Clone ytabeloved/ordervista and navigate into the project root.
2

Configure the backend

Copy .env.example in the backend/ folder, fill in your MySQL credentials and JWT secret, then run npm install && npm run dev.
3

Configure the frontend

Copy .env.example in the frontend/ folder, set VITE_API_URL, then run npm install && npm run dev.
4

Verify the API

Hit GET /api/health — if you see {"status":"ok","message":"OrderVista API running"} the stack is live and ready.
Ordervista uses free-tier hosting services (Vercel, Render, Aiven MySQL) in production. On first load, the backend and database may take 30–60 seconds to wake from sleep.

Build docs developers (and LLMs) love