RestroAIBuyer Guide
Ctrl+K
Docs Home
Docs/Start Here

Start Here: RestroAI CodeCanyon Buyer Guide

This page is written for non-developers and first-time buyers. Follow it in order: install, log in as admin, repair access if needed, set Mailpit/log mail, test sandbox payments, seed the demo restaurant, then explore restaurant modules.

Install to tenant activation flow diagram

What RestroAI Is

RestroAI is a restaurant POS SaaS platform. A central admin manages tenants, plans, subscriptions, payments, settings, roles, and guided demos. Each restaurant tenant gets its own workspace for setup, menu, POS, kitchen display, waiter PWA, QR ordering, inventory, customers, reservations, reports, and optional AI.

Central Admin
  • URL: /dashboard
  • Used for tenants, plans, subscriptions, payments, settings, roles, and demos.
  • Admin role should show all central modules.
Restaurant Tenant
  • URL pattern: /r/{tenant}
  • Used by restaurant owner, manager, cashier, waiter, kitchen, and host users.
  • Access is blocked until subscription payment is active.

First Install Checklist

  1. Upload files to your server or local XAMPP folder.
  2. Create the database and database user.
  3. Open the installer and complete server, database, mail, and admin account steps.
  4. Make sure the admin password and confirmation match.
  5. Finish installation and confirm storage/app/installed exists.
  6. Log in at /login.
Important: If you re-run installer files on a live site, back up the database first. Do not delete tenant databases unless you have a written data policy.

If Admin Logs In But Sees Nothing

Run the repair command below. It creates or updates the protected Admin role, assigns every central permission, assigns the role to the selected user, and clears the Spatie permission cache. 

php artisan auth:ensure-admin admin@ovion.tech
php artisan access:audit --fail-on-drift

Expected result: the dashboard shows RestroAI Central Command Center and the access health card says Admin access healthy.

Mailpit Or Log Mail

For local and demo testing, use Mailpit or the log mailer. Mailpit catches emails safely so password resets, staff invites, payment links, and reminders do not go to real customers. 

MAIL_MAILER=mailpit
MAIL_HOST=127.0.0.1
MAIL_PORT=1025
MAIL_ENCRYPTION=null
MAIL_USERNAME=null
MAIL_PASSWORD=null

Open the Mailpit inbox at http://127.0.0.1:8025.

Payment Sandbox

RestroAI blocks live credentials in this phase. Use the simulator first, then configure Stripe, PayPal, Razorpay, and Paystack sandbox credentials if you need real gateway testing.

  • Open Payment Sandbox from the central dashboard.
  • Create a sample payment request.
  • Pay through simulator success/failure/cancel/refund flows.
  • Use Mailpit/log mail to send payment links.

Demo Tenant

Use the demo tenant to inspect all modules without touching real restaurant records. Demo reset and refresh only affect records tagged in demo_record_references. 

php artisan demo:seed-restroai --tenant=restroai-demo
php artisan guided-demo:validate-restroai --tenant=restroai-demo
php artisan demo:refresh-restroai --tenant=restroai-demo --module=*
php artisan demo:reset-restroai --tenant=restroai-demo
Demo seed refresh reset safety flow

Recommended Module Order

Restaurant operations loop
  1. Platform/SaaS: create tenant, plan, subscription, and sandbox payment.
  2. Restaurant Setup: branches, floors, tables, stations, staff, receipt and tax settings.
  3. Menu: categories, items, variants, modifiers, branch pricing, QA, and publish.
  4. POS and KDS: shift, order, send to kitchen, pay, receipt, refund/void.
  5. Waiter PWA and QR: assigned tables, QR guest carts, waiter approval.
  6. Inventory: ingredients, recipes, receiving, stock movements, variance.
  7. Customers: profiles, loyalty, coupons, gift cards, reservations, waitlist, reminders.
  8. Reports and AI: charts, heatmaps, exports, evidence-backed AI insights.

Common Mistakes

Wrong Password Lockout

Use safer defaults and unlock a user with:

php artisan auth:unlock-user admin@ovion.tech
Admin Has No Menu

Run admin repair and access audit. Then clear app cache if your host caches config/views.

php artisan optimize:clear

Developer Notes

  • Central data lives in the landlord database.
  • Restaurant module data lives inside each tenant database.
  • Protected roles are registry-managed; do not manually delete Admin or tenant Owner.
  • Sandbox payment callbacks update central payment records, then subscription/order reconciliation services update linked records.
  • Guided demos can prefill and highlight UI, but real business mutations still require normal app confirmation.
<- Docs overview Next: Guided Demo Studio ->