Forkiva – Restaurant POS Management System icon

Forkiva – Restaurant POS Management System

Hot or Not
Forkiva – Restaurant POS Management System

Description

Complete Restaurant POS and Management Platform

Forkiva is a complete restaurant Point of Sale and operations management system for restaurants, cafés, coffee shops, fast-food businesses, food courts, and cloud kitchens. It brings sales, orders, tables, kitchen operations, menus, inventory, purchasing, reservations, customers, loyalty, and reporting into one modern platform.

Built with Laravel 12, Vue 3, Vuetify, and a modular architecture, Forkiva provides full source code that developers can customize and extend. It supports both single-location restaurants and multi-branch operations with branch-specific settings and access control.

Built for Daily Restaurant Operations

Process dine-in, takeaway, pickup, drive-thru, and catering orders from a fast and responsive POS interface. Manage live table availability, assign waiters, send orders to the kitchen, accept multiple payment methods, and track register sessions and cash movements from one connected workflow.

Control Menus, Recipes, and Inventory

Create branch-specific menus, nested categories, products, options, recipes, and ingredient mappings. Forkiva can automatically deduct ingredient quantities when products are sold, helping teams monitor stock levels, purchases, transfers, spoilage, and adjustments more accurately.

Flexible and Ready to Customize

The backend follows a modular Laravel structure, while the frontend uses reusable Vue components and a modern UI system. Full source code, installation documentation, user documentation, and a Postman API collection are included.

Suitable For

  • Restaurants and cafés
  • Coffee shops and bakeries
  • Fast-food restaurants and food courts
  • Cloud and virtual kitchens
  • Single-location businesses and multi-branch chains

What Is Included

  • Laravel backend source code
  • Vue 3 and Vuetify frontend source code
  • Step-by-step web installer
  • Installation and user documentation
  • Postman API collection
  • Future updates for the purchased item through the marketplace

Important: This item is a self-hosted web application. Hosting, domain, SSL certificate, third-party service fees, hardware, and optional add-ons are not included.

Features

Point of Sale and Orders

  • Modern and responsive restaurant POS interface
  • Dine-in, takeaway, pickup, drive-thru, and catering order types
  • Product search, categories, cart summary, and customer selection
  • Multiple payment methods and split payment support
  • Inclusive, exclusive, and compound taxes
  • Branch-specific fees and order-type tax rules
  • Discounts, vouchers, gift cards, and loyalty points
  • Waiter assignment and order lifecycle tracking
  • Register sessions, cash-in, cash-out, and reason tracking
  • Quick Pay buttons, numeric keypad, and payment calculator

Tables, Kitchen, and Reservations

  • Floor, zone, and table hierarchy
  • Interactive table viewer with live table statuses
  • Custom table shapes and capacities
  • Merge, split, assign, and transfer tables
  • Table QR-code ordering
  • Kitchen viewer for preparing and ready orders
  • Kitchen sound alerts and visual order notifications
  • Reservations, waitlist, table blocks, and reservation settings

Menus and Products

  • Multiple menus for breakfast, lunch, dinner, or custom service periods
  • Nested and translatable product categories
  • Products with branch pricing, images, translations, and tax settings
  • Product options and option values
  • Recipe builder with ingredients, quantities, and loss percentages
  • Online menu support

Inventory and Purchasing

  • Ingredient-level stock management
  • Units, costs, and low-stock alerts
  • Automatic ingredient deduction based on product recipes
  • Stock in, stock out, spoilage, adjustment, and transfer movements
  • Branch supplier management
  • Purchase orders with expected and received quantity comparison
  • Inventory analytics and movement history

Branches, Users, and Localization

  • Unlimited restaurant branches
  • Branch-specific currencies, time zones, payment types, and settings
  • Super Admin and branch administration hierarchy
  • Seven built-in operational roles with fine-grained permissions
  • Multi-language support with full RTL compatibility
  • Multi-currency support and live currency-rate integration
  • Light and dark themes with customizable colors

Customers, Promotions, and Loyalty

  • Customer profiles and purchase history
  • Discount and voucher management
  • Gift cards with analytics
  • Loyalty programs, tiers, rewards, promotions, gifts, and transactions
  • Detailed loyalty performance and customer reports

Reports and System Tools

  • Sales, payments, taxes, cash flow, ingredients, discounts, and loyalty reports
  • Revenue, average order value, top-selling product, and low-stock insights
  • Export module with export history and filter tracking
  • Email, in-app, and push notification services and templates
  • Browser printing and Qintrix direct printing integration
  • 58 mm and 80 mm thermal receipt templates
  • Database backup and restore
  • PWA support
  • Media manager, activity logs, and authentication logs
  • Private file storage configuration

Technology and Developer Experience

  • Laravel 12 and PHP 8.4 backend
  • Vue 3, Vuetify, Vite, Pinia, and TypeScript frontend
  • Clean modular monolith architecture
  • Full backend and frontend source code
  • Web-based installation wizard
  • Detailed documentation and Postman API collection

Requirements

Production Server Requirements

  • Linux-based shared hosting, VPS, cloud server, or dedicated server
  • PHP 8.4 or later
  • Apache 2.4+ or Nginx 1.20+
  • MySQL 8.0+ (recommended) or MariaDB 10.6+
  • Composer 2.5 or later
  • Node.js 22.x LTS or later
  • Yarn 1.22.x or a compatible npm version
  • Valid SSL certificate recommended for production use
  • Cron job access is required for Laravel Scheduler
  • SSH access is recommended for VPS and cloud deployments

Required PHP Extensions

  • ctype
  • curl
  • dom
  • fileinfo
  • filter
  • hash
  • intl
  • mbstring
  • openssl
  • pcre
  • pdo
  • pdo_mysql or the appropriate MySQL/MariaDB PDO driver
  • session
  • tokenizer
  • xml

Recommended: Enable the BCMath extension. It is included in the documented Linux installation setup and is recommended for reliable numeric and financial operations.

Cache Requirements

At least one supported cache driver must be available:

  • Redis — recommended for production
  • Predis
  • Filesystem cache

Redis is optional. Forkiva can operate using the filesystem cache when Redis is unavailable.

Laravel Scheduler

Forkiva uses Laravel Scheduler for automated background operations such as report generation, email processing, notifications, and system maintenance. The following command must run automatically every minute:

* * * * * cd /full/path/to/forkiva && php artisan schedule:run >> /dev/null 2>&1








  • Cron job access is required on both shared hosting and VPS environments.
  • The cron job must use the same PHP version as the Forkiva application.
  • The full project path and PHP binary path should be used.
  • Only one scheduler cron job is required for each Forkiva installation.

Queue Processing

  • A persistent queue worker is recommended for production environments.
  • Supervisor or an equivalent process manager is recommended on VPS and dedicated servers.
  • The queue process should restart automatically after server reboots or unexpected failures.

File and Directory Permissions

The web server must have write permission for the following Laravel directories:

  • storage/
  • bootstrap/cache/

The application must also be allowed to create logs, cache files, sessions, compiled files, uploaded media, exports, backups, and other generated application files.

Node.js and Browsershot Requirements

  • Node.js 22.x LTS or later
  • Puppeteer 23.0 or later
  • Required for Browsershot-based PDF and screenshot generation
  • Node.js and Yarn/npm are also required when rebuilding or customizing frontend assets

Frontend Build Requirements

  • Node.js 22.x LTS
  • Yarn 1.22.x or a compatible npm version
  • TypeScript-compatible development environment
  • Ability to execute Vite production builds

These tools are required for frontend development, customization, dependency installation, and asset rebuilding.

Production Configuration Requirements

  • A correctly configured Laravel .env file
  • Correct application URL and HTTPS configuration
  • Valid database connection credentials
  • A configured cache driver
  • Mail configuration for email notifications
  • Correct permissions for writable Laravel directories
  • Production mode with debugging disabled

For production environments, APP_ENV should be set to production and APP_DEBUG should be set to false.

Recommended Production Environment

  • Ubuntu 22.04 LTS or a similar modern Linux distribution
  • Nginx with PHP-FPM
  • MySQL 8.x or MariaDB 10.6+
  • Redis for cache and queue processing
  • Supervisor for persistent queue workers
  • Let's Encrypt or another valid SSL certificate
  • Automated backups and deployment workflow recommended

Shared Hosting Requirements

Forkiva can be installed on shared hosting using cPanel, Plesk, DirectAdmin, or a similar control panel, provided that the hosting plan supports:

  • PHP 8.4+
  • MySQL 8.0+ or MariaDB 10.6+
  • All required PHP extensions
  • Writable Laravel directories
  • Cron jobs running every minute
  • Application file extraction and database creation

Installation Options

  • Web-based installation wizard for standard installation
  • Manual Laravel and Vue installation for developers
  • Optional demo data during installation

Important: Buyers should confirm that their hosting provider supports PHP 8.4, the required extensions, cron jobs, and writable Laravel directories before purchasing or installing Forkiva.

Instructions

Installation Instructions

Forkiva is one Laravel application with an integrated Vue frontend. The web installer sets up the application when you use a complete, prebuilt release package. There is no separate frontend application to upload or run.

Before Installation

  • Confirm that your server supports PHP 8.4, the required PHP extensions, MySQL 8.x, and a domain document root pointing to a subdirectory.
  • Use a complete release package containing all enabled modules, Composer dependencies, and compiled browser assets in public/build/.
  • Create an empty database and a dedicated database user. Keep the host, port, name, username, and password ready.
  • Set up HTTPS. Make sure the web PHP process can write to storage/, bootstrap/cache/, and the application directory while the installer creates .env.

Step 1 — Download and Extract the Package

  1. Download and extract the purchased package on your computer.
  2. Locate the actual Forkiva application release ZIP. Do not upload the complete marketplace download if it also contains manuals or other files outside the application.

Step 2 — Upload the Application

  1. Open your hosting control panel and create a private application directory, such as /home/username/forkiva.
  2. Upload and extract the application ZIP in that directory.
  3. Confirm that its root contains artisan, Modules/, vendor/, resources/, and public/build/.
  4. Set the domain document root to the application's public/ directory.

Example:

/home/username/forkiva/          <-- application root
/home/username/forkiva/public/   <-- domain document root



Do not place the entire Laravel application directly in public_html/. If your host cannot point the domain to public/, ask the provider to configure it or use a compatible host.

Step 3 — Create the Database

  1. Create a new, empty MySQL 8.x database in the hosting panel.
  2. Create a dedicated user with a strong password and grant the privileges required to create and update tables in that database.
  3. Record the database host, port (usually 3306), name, username, and password.

Do not use a database that contains another application or an older Forkiva installation.

Step 4 — Open the Installer

Open this URL, replacing yourdomain.com with your actual domain:

https://yourdomain.com/installer



Step 5 — Check Server Requirements and Permissions

  1. Click Let’s get started.
  2. The System check verifies PHP, extensions, Composer dependencies, runtime folders, environment file access, the public storage link, configuration cache, and browser assets.
  3. Resolve every failed check and click Run checks again before continuing.

Ask your hosting provider to correct ownership or permissions if needed. Do not set the whole application to globally writable 777 permissions.

Step 6 — Configure the Application

In Configuration, enter the application name and public HTTPS URL. Choose supported and default countries, languages, timezone, and currencies. Review passkey and cache settings, then click Save & continue. Use the website URL without a path or trailing slash.

Step 7 — Configure the Database

Select the database engine and enter the host, port, name, username, and password for the empty database. Select Include sample data only if you want demonstration records. Click Verify & prepare database and keep the page open while its tasks run.

If preparation fails, use the wizard's retry path or contact the release provider. Do not bypass migration errors by editing database constraints or running broad seed commands manually.

Step 8 — Create the Administrator Account

Enter the first administrator's full name, username, email address, password, and password confirmation. Click Save administrator. Use this account to sign in; Forkiva does not require published default credentials.

Step 9 — Complete the Installation

  1. Review the public URL on the Launch step.
  2. Click Launch Forkiva and wait for completion.
  3. Click Open Forkiva and sign in with the administrator account you created.

The installer creates the public storage link, applies production environment settings, and locks the installer after a successful launch.

Step 10 — Configure Laravel Scheduler

Create a cron job that runs from the application root every minute. Replace the path and PHP command with those supplied by your host:

* * * * * cd /home/username/forkiva && /usr/local/bin/php artisan schedule:run >> /dev/null 2>&1



Step 11 — Configure Queue Workers

If your queue connection requires background workers, use Supervisor or another process manager to keep them running and restart them after a failure or reboot. Configure and monitor the workers for your deployment.

Step 12 — Configure Forkiva

After signing in, review the features available in your release:

  • Application name, logo, and appearance
  • Branches, currencies, languages, and timezone
  • Taxes, charges, and payment methods
  • Menus, categories, products, options, and inventory
  • POS registers, printers, users, roles, and permissions
  • Email, notifications, and enabled integrations

Production Security

  • Use HTTPS and a strong administrator password.
  • Keep APP_ENV=production and APP_DEBUG=false.
  • Keep .env, vendor/, and storage/ outside the public document root.
  • Restrict file permissions and configure automated backups.

Installation Verification

  • Forkiva loads and the administrator can sign in over HTTPS.
  • The POS loads products and categories, and an order can be completed.
  • Uploads and downloads work.
  • The scheduler runs every minute and queued jobs are processed.
  • Email, notifications, and enabled integrations work.
  • Receipts and PDFs work where enabled; their worker needs a compatible Node.js and Puppeteer Chrome runtime.

Developer Installation

Developers run both PHP and Vue commands from the single Laravel application root. In this source workspace it is backend/; a distributed source package may name it forkiva/. Use the directory containing both artisan and package.json.

Install dependencies

cd backend
composer install
yarn install --frozen-lockfile
yarn check:modules



For a new installation only, create the environment file and key:

cp .env.example .env
php artisan key:generate



Configure the database and other services in this one .env. Never overwrite an existing .env or regenerate an installed application's key.

Run locally

composer run dev



yarn dev is equivalent. Open the Laravel URL printed in the terminal, normally http://127.0.0.1:8000, and complete the installer. Vite's asset port is not the application URL. After the local installer sets production values, restore APP_ENV=local and APP_DEBUG=true in the local .env, then restart the development command.

Integrated Vue frontend

The Vue source is in resources/js/ and Modules/<Module>/resources/assets/js/ inside Laravel. There is no separate Forkiva/Frontend directory or frontend .env. The normal integrated browser client uses same-origin /api, so VITE_API_URL is not needed.

Use a Node.js version accepted by the current package.json (^22.13.0 or >=24.0.0). Build production assets from the Laravel application root:

yarn check:modules
yarn build



Deploy public/build/ with the matching Laravel release. Production users open the Laravel application at its public domain; do not run Vite or yarn dev as the production website. The installer sets APP_INSTALLED=true after success; do not set it manually to skip setup.

Important Notes

  • Follow the license terms that apply to your purchase and installation.
  • Hosting, domain, SSL certificate, server administration, and third-party service fees are separate.
  • Optional add-ons must be licensed and installed separately unless your release explicitly includes them.
  • For an existing Forkiva installation, preserve .env, APP_KEY, uploaded files, and database contents. Use the upgrade instructions instead of the new-installation wizard.
Authortenvoro
CategoryScripts & Code / PHP Scripts / POS
Price$89
Extended License$267
Likes1
First ReleaseJul 14, 2026
Last UpdateAug 26, 2026
Files included.php, .css, .html

External listing. code.market does not sell this product and does not process payment for it. Pricing, payment, delivery, licensing, refunds, and support are handled by the third-party merchant on its own website. We may earn an affiliate commission from a referral. Details.