ZeriPOS - Laravel POS & Inventory Management System

ZeriPOS is a complete Laravel-based Point of Sale (POS), inventory, sales, purchase, and business management system built for retail shops, boutiques, electronics stores, supermarkets, wholesalers, and single-branch businesses.
It helps businesses manage daily checkout operations, product variations, barcodes, stock adjustments, purchases, sales invoices, returns, expenses, customer balances, supplier credits, user roles, permissions, and advanced reports from one clean and organized admin panel.

• Fast POS Checkout: Barcode search, product search, customer selection, discount, tax, partial payment, hold sale, thermal print, SMS invoice, and email invoice support.
• Complete Inventory Control: Simple products, variable products, SKU, barcode, stock adjustment, stock logs, low-stock alerts, expiry tracking, and inventory valuation.
• Sales & Purchase Management: Sales invoices, purchase invoices, payment records, due tracking, customer balance, supplier credit, sales returns, and purchase returns.
• Advanced Reporting: Sales, purchases, returns, stock, adjustment, customer credit, profit/loss, expiry, short stock, and AI report agent support.
• Secure Role Access: Admin, manager, cashier, salesman, custom roles, permission management, and module-based access control.

ZeriPOS is designed for businesses that need a practical, easy-to-use, and scalable POS solution with strong inventory tracking and professional invoice management.

Live Interactive Demo

Test the live application dashboard and checkout workflows using the link below:

• ZeriPOS Live Demo: Click Here to View Demo

*Note: Staging login credentials for both Admin and Cashier are pre-filled or listed directly on the demo login page for easy access.

Key Features

• Modern Laravel POS System: Built with Laravel, Blade, Bootstrap, JavaScript, and MySQL/MariaDB for reliable retail operations.
• Fast POS Checkout: Optimized checkout screen for cashiers and salesmen with quick product search, barcode support, cart handling, customer selection, discount, tax, and payment processing.
• Multiple Invoice Options: Print standard invoices, thermal invoices, and professional invoice templates with email and SMS invoice support.
• Product Variation Engine: Manage simple products and variable products with size, color, SKU, barcode, purchase price, selling price, tax, discount, and product images.
• Inventory Management: Track stock movements, stock adjustments, stock logs, current stock, short stock, expiry dates, low-stock alerts, and inventory valuation.
• Purchase Management: Create supplier purchase invoices, manage purchase history, update stock, track due payments, handle purchase returns, and manage supplier credits.
• Sales Management: Create sales invoices, assign customers, record payments, manage due sales, print invoices, and track sales history.
• Return Management: Manage sales returns and purchase returns with stock updates, refund handling, credit generation, and return tracking.
• Customers & Suppliers: Maintain customer and supplier profiles, contact details, opening balances, credit balances, due reports, and transaction history.
• Expenses: Track business expenses with expense categories, payment methods, and expense reports.
• Role & Permission System: Manage Admin, Manager, Cashier, Salesman, and custom roles with module-based permission control.
• Reports & Analytics: Access sales, purchase, return, stock, adjustment, customer credit, profit/loss, expiry, short stock, and AI-assisted business reports.
• System Configuration: Configure business profile, invoice prefix, SMTP, SMS gateway, tax settings, barcode settings, invoice templates, and system preferences.

System Requirements

ZeriPOS Instructions

Modern Laravel POS, inventory, purchase, sales return, purchase return, reporting, and role-based access control system.
ZERI POS includes ZeriMIN Admin Panel under an Internal Zerithonlabs License. Buyers may use ZeriMIN only as part of ZERI POS and may not extract, resell, or reuse it separately.

Quick Start

1. Download All files & documentation from Codester.
2. Upload source ZIP to your server/local environment and extract it.
3. Create a MySQL database and database user for the application.
4. Install backend dependencies: composer install --no-dev --optimize-autoloader.
5. Build frontend assets: npm install && npm run build. On shared hosting without Node.js, build locally and upload the generated public/build folder.
6. Make storage and bootstrap/cache writable by the PHP/web server user.
7. Point your domain to the Laravel public/ directory. For local testing, run php artisan serve --no-reload.
8. Open <a href="https://your-domain.com/install">https://your-domain.com/instal...</a> in the browser and complete the installer. For local testing, open <a href="http://127.0.0.1:8000/install">http://127.0.0.1:8000/install</a>.###licode###.env, generates the app key, runs migrations/seeds, links storage, and creates the first admin user.
9. After installation, refresh default access permissions: php artisan db:seed --class=DefaultAccessSeeder --force.
10. Optional: insert default business catalog data: BUSINESS_SEED_TYPE=fashion php artisan db:seed --class=BusinessTypeCatalogSeeder --force.
11. Login with the admin email and password you entered during installation.

Do not include a real .env file in the distributable/main package. Ship .env.example only; the installer creates the real server .env.
DefaultAccessSeeder refreshes default permissions, roles, settings, and admin role permissions. Run it after installation or updates before first dashboard login.
For business catalog seed, replace fashion with one of: fashion, electronics, grocery, stationery_hardware, wholesale.

First Login And Admin Setup

Registration creates inactive users by default. New signup requires activation by admin.

Installer Admin Login

After a browser installer setup, login with the admin email and password entered in the installer form.

Manual Developer Seed Login

If you intentionally use the manual developer seed flow, use the seeded development admin account only for local/testing installs and change it immediately.
After login:

1. Change admin password immediately.
2. Review role-permission mapping from Master > Roles.
3. Update SMTP and company settings from Master > Settings.

Before First Sale Setup

Complete these dashboard setup steps before starting live sales. This prevents missing products, wrong prices, missing stock, and incorrect cashier permissions during POS use.

1. Configuration

Open the configuration/settings page and review shop and POS defaults.

2. Users, Roles, And Permissions

Open Users and prepare the staff accounts before handing over the POS counter.

3. Master Data

Open Master and create the reference data used by products, purchases, reports, and POS filters.

4. Suppliers

Open Supplier and add suppliers before creating products. Product setup requires a supplier, and purchase history depends on supplier linkage.

5. Products

Open Products > Add Product and create the sellable catalog.

6. Opening Stock

Stock must exist before POS can sell an item.

7. Customers

Open Customer and create customers if your business needs due sales, customer-wise reports, credit tracking, SMS invoices, or email invoices.

8. Barcode Settings

Open Products > Barcode Settings if you use barcode labels or scanner-based POS. Set label size, barcode size, font size, and print labels for products as needed.

9. Test POS Before Live Selling

If the test sale creates an invoice, prints correctly, and reduces stock, the store is ready for live selling.

FAQ

Q: Does this app support multi-store or multi-tenant mode?

A: Not by default in current codebase. It is designed as a single business instance monolith.

Q: Are permissions hardcoded?

A: No. Access is DB-driven. Route permissions are auto-synced and you can add custom permissions (for example dashboard capability permissions) and assign them from role management.

Q: Can I add custom reports?

A: Yes. Extend report definitions and query builders in Purchase report services/controllers.

Q: Which account should be used after fresh install?

A: Use the admin email and password created in the browser installer. Manual seeded development credentials should be used only when you intentionally run the developer seed flow.

Support

For project-specific support, customization, and issue reporting, contact ZerithonLabs.