Foodify - Restaurant Management SaaS with POS, KDS, QR Menu Ordering & Laravel Admin

Launch your own restaurant management platform with Foodify, built-in tools for POS billing, kitchen display, QR table ordering, delivery, multi-branch control, and subscription plans. Ideal for single outlets to growing chains, it simplifies operations & boosts revenue.

Basic Knowledge

To install, set up, and publish Foodify with your branding, it's necessary to possess fundamental knowledge in server-side configuration.

• IDE for Web development, we prefer VSCode.
• Real server related knowledge like apache or local machine server, we prefere to use a real server.
• Server related knowledge and we preferred cPanel in your server for quick installation
• Basic knowledge in PHP, NPM, Vue, Node and Laravel.
• Basic knowledge about firebase

Server Prerequisite

Foodify is dependent on PHP version 8.2 or higher and MySQL version 8.0 or later. Additionally, the following server configurations and PHP extensions are necessary. Before install, please make sure you have the components bellow enable on your server

• PHP 8.2 or Greater
• OpenSSL PHP Extension
• PDO PHP Extension
• Mbstring PHP Extension
• Tokenizer PHP Extension
• PHP JSON
• PHP cURL
• XML PHP Extension
• Ctype PHP Extension
• BCMath PHP Extension
• PHP Zip Archive
• Exif PHP Extension
• Fileinfo PHP Extension
• GD PHP Extension
• Intl PHP Extension
• Imagick PHP Extension

Typically, these extensions are enabled by default on most servers, but it is recommended that you confirm with your hosting provider.

Please proceed with caution and take great care in completing this task. Any errors made will not be the responsibility of our team.

cPanel Database Setup and File Configuration

Note: Remember! The script doesn't have any "install" folder or directory. The installation is controlled by a Controller.

Now Follow the steps below to setup the script:

1. Unzip the package you received after purchase and open the Source Code folder. You will find the web folder. In web folder there is the foodify.zip file. you need to upload foodify.zip file to your hosting web server using FTP or cPanel, then you need to unzip this file, you will find "foodify" folder. You need to move all files and folders in your domain's document root directory.
2. You will have these files and folders in your document root:

   

3. Make sure /bootstrap/cache, /storage/framework and /storage/logs folder have permission as 755 recursively. If you don't have 755 permission in these folders, you have to give permission manually. To give permission right click on the folder and click "Change permission" button, you will see the prompt to change permission like the second image below. Select the checkboxes you can see in the second image.

   

   

4. Before starting the installation, database must be configured for the application. For creating the database, the following ways must be maintained
   • From cPanel Go to MySQL Databases

     

   • Create a new database

     

   • Create a user for the database

     

   • Add a user to the database

     

   • Give privileges to the user

     

Installation

1. Run the install script path from any web browser (http://yourdomain.com/install) and click on “Check Requirements” button.

   

2. Now you can see your php extension list if it is already installed in all extension then you can see "Check Permissions" button. Now click on this button and go to next step

   

3. Now you will see the folders permission list if everything is ok then click “License Setup”

   

4. Provide your License Code, then click “Site Setup”
5. Provide your App name and Domain name as App Url, then click “Database Setup”

   

6. Provide your database information like Database Host, Database Port, Database Name, Database Username, and Database Password, then click “Final Setup”. Don't use # in your Database Password.

   

7. Now you will see the login information (Email : superadmin@example.com, Password : 123456) then click “Finish” to exit

   

8. Good Luck!!!

Tips Check our video tutorial! Watch Now

Foodify keeps configuration in two places, because one installation serves many restaurants.

System Settings belongs to the super admin and controls the whole platform. It covers Company, Site, Currencies, Mail, OTP, Notification, Analytics, Cookies, Theme, Role & Permissions, Languages and Payment Gateway (the gateway used to charge restaurants for their subscription).

Restaurant Settings belongs to each restaurant owner and applies only to their own restaurant. It covers My Restaurant, My Site, Pages, Currencies, Item Categories, Item Attributes, Taxes, Social Media, Sliders, Order Setup, Time Slots, Branches, Notification Alert, SMS Gateway and Payment Gateway (the gateways their customers pay with).

Tips Check our video tutorial! Watch Now

Landing Site Installation

The public marketing site — the one visitors see before they sign up — is a separate Nuxt 3 application. It is not part of the Laravel installation, and it is optional: if you already have a marketing site, you can point your sign-up buttons at the main app and skip this entirely.

Everything on the site — company name, logo, brand colours, plans, features, testimonials, FAQ, blog and CMS pages — is pulled from your Foodify backend through the landing API. You edit the content in the super admin panel, not in the code.

Prerequisite

• Node.js 18 or higher with npm.
• Your Foodify backend already installed and reachable over HTTPS.
• A domain or subdomain for the site, for example www.yourdomain.com while the app runs on app.yourdomain.com.

Step 1 — Install dependencies

Upload the landing folder to your server, then from inside it run:

npm install

Step 2 — Configure the environment

Copy .env.example to .env and fill in five values:

NUXT_ENV=production
NUXT_PUBLIC_API_URL=https://app.yourdomain.com/api/landing
NUXT_PUBLIC_API_KEY=your-api-key
NUXT_PUBLIC_BASE_URL=https://app.yourdomain.com
NUXT_PUBLIC_ASSET_BASE_URL=https://www.yourdomain.com

Step 3 — Build and run

npm run build
npm run preview

The build output lands in .output/. On a real server, keep it running with a process manager such as PM2 and put Nginx or Apache in front of it:

pm2 start .output/server/index.mjs --name foodify-landing

Tip To host the site on plain shared hosting with no Node process, run npm run generate instead. That produces static files you can upload — but the content is then frozen at build time, so you must regenerate after editing anything in the admin panel.

Step 4 — Check it works

1. Open the site. The header should show your company name and logo, not the defaults.
2. Scroll to the pricing section — your plans should be listed with the right prices.
3. Click Login. It must land on your main app, not back on the marketing site.

If the logo and plans are missing, the API URL or key is wrong. Open the browser console and look at the failing request.

Managing Landing Content

Once the site is running you never edit its code again. Everything is managed from Setup → Landing Settings in the super admin panel, and the site picks it up on the next page load.

Branding

The company name, logo, favicon and the two brand colours come from System Settings → Company and System Settings → Theme. The landing site reads them at runtime and applies the colours to buttons, links and highlights, so changing the theme colour in the admin panel re-brands the marketing site as well — no rebuild needed.

Pricing

The pricing section lists the same plans restaurant owners see when they subscribe, taken from Plans. A paid plan with no price for the selected billing cycle is hidden automatically, so a monthly-only plan will not appear under the yearly toggle. Keep the Short Tagline filled in — it is the line shown under the plan name on the card.

Note If you used npm run generate for static hosting, content changes will not appear until you run the command again and re-upload. With npm run build and a running Node process, they appear immediately.

Subscription Setup (Stripe)

Foodify charges restaurant owners for their plan through Stripe. This is separate from the gateways a restaurant's own customers pay with — those are configured by each restaurant owner under Restaurant Settings → Payment Gateway. The steps below are for you, the platform owner.

Important Until these steps are complete, restaurant owners cannot buy a paid plan. Every restaurant stays on the free plan.

Step 1 — Get your Stripe API keys

1. Create an account at dashboard.stripe.com and sign in.
2. Use the Test mode toggle while you are setting things up, and switch to live only when you are ready to take real money.
3. Go to Developers → API keys.
4. Copy the Publishable key (starts with pk_) and the Secret key (starts with sk_).

Step 2 — Save the keys in Foodify

1. Log in as super admin and go to System Settings → Payment Gateway.
2. Paste the publishable key into Stripe Public Key and the secret key into Stripe Secret Key.
3. Set Stripe Mode to Sandbox while testing, or Live for real payments.
4. Set Stripe Status to Enable.
5. Leave Stripe Webhook Secret empty for now — you will get it in the next step.
6. Click Save.

Step 3 — Create the webhook endpoint

Stripe needs to tell Foodify when a payment succeeds, a plan renews or a card fails. Without this, a restaurant can pay and still not receive their plan.

1. On the same System Settings → Payment Gateway page, find Stripe Webhook URL at the bottom and click Copy.
2. In your Stripe dashboard go to Developers → Webhooks and click Add endpoint.
3. Paste the copied URL into Endpoint URL.
4. Under Select events, choose Select all events (or at minimum the customer.subscription.*, invoice.* and checkout.session.* groups).
5. Click Add endpoint.

Warning Always use the URL from the Copy button. The path must end in /api/stripe/webhook. If you type it by hand and leave out /api, Stripe will still report 200 OK for every event, but plans and invoices will never be recorded — a failure that is very hard to spot.

Step 4 — Save the signing secret

1. Open the endpoint you just created in Stripe.
2. Under Signing secret, click Reveal and copy the value (starts with whsec_).
3. Back in System Settings → Payment Gateway, paste it into Stripe Webhook Secret and click Save.

Note This secret is what proves an incoming request really came from Stripe. Leaving it empty means anyone who knows your webhook URL could send fake payment events, so do not skip it.

Creating Subscription Plans

A plan decides what a restaurant can use and what it costs. Each paid plan exists in two places: the price lives in Stripe, and the features and limits live in Foodify. The two are linked by a Price ID.

Step 1 — Create the product and prices in Stripe

1. In your Stripe dashboard go to Product catalogue → Add product.
2. Give it a name that matches your plan, for example Standard.
3. Add a recurring price, set the amount and choose Monthly. Save it.
4. Add a second recurring price on the same product, set the yearly amount and choose Yearly.
5. Copy both Price IDs (they start with price_). You need one for monthly and one for yearly.

Careful Copy the Price ID, not the Product ID. A Price ID starts with price_; a Product ID starts with prod_.

Step 2 — Create the plan in Foodify

1. Go to Plans in the sidebar and click Add Plan.
2. Enter the Name and a Short Tagline.
3. Set Plan Type to Paid. The price fields appear.
4. Enter the Monthly Price and Annual Price. These must match the amounts you set in Stripe.
5. Paste the two Price IDs into Stripe Monthly Price ID and Stripe Annual Price ID.
6. Tick the Modules this plan unlocks — POS, QR table ordering, KDS, delivery, reports and so on.
7. Set the Limits: how many branches, menu items, moderators and online orders per month. Tick Unlimited where you do not want a cap.
8. Save.

As you type the annual price, Foodify shows how much a yearly subscriber saves compared with paying monthly, so you can price the discount deliberately.

What the modules and limits control

Each plan is built from two lists. Modules switch whole features on or off, and Limits cap how much of something a restaurant can create.

The free plan

Every new restaurant starts on the free plan. Set which plan that is under System Settings → Site → Default Plan. A free plan has no price and no Stripe Price IDs — only modules and limits. Keep it generous enough to be useful, but limited enough that growing restaurants have a reason to upgrade.

Tip Test the whole flow in Stripe test mode before going live. Use card number 4242 4242 4242 4242 with any future expiry and any CVC, buy a plan as a restaurant owner, and confirm the subscription appears under Subscription Report.

Firebase Push Notification Setup

Tips Check our video tutorial! Watch Now

How to configure multiple languages?

Translate your admin and website, follow these steps:

1. Login into the admin panel.
2. Go to System Settings -> Languages.
3. Click On Add Language.
4. Fill all field and add new language.
5. Click on the view icon of the new language low in from the list.
6. Select file from the dropdown option under Files tab and click get file content.
7. All the lebels and language objectives will appear in the bottom of the field.
8. Now update the value of all the input fields and click save.
9. You do not change any word under the curly bracket text {}, example {name}.
10. When all language is changed then run some command in your terminal or ssh panel.

Merchant Mobile App

Foodify ships with a Flutter merchant app that puts the restaurant in the owner's pocket — a live dashboard, online and POS orders through to delivery, sales reports with a payment breakdown, and branch switching in a tap.

Setting it up is a separate job from the web installation: you configure it in Flutter, then build and release it to the stores. That whole process has its own guide.

Guide Open the Merchant App documentation → — prerequisites, logo and icon, app name, license key, base URL, Firebase push and the Android/iOS build steps.

Key Features Detailed

Foodify is a complete restaurant management platform. One installation serves many restaurants, and each one gets its own branches, menu, staff, customer website and POS terminal.

Troubleshooting

If something is not working, the application log is the fastest way to find out why. It lives at storage/logs/laravel.log — open it and read the last entries.

php artisan config:clear
php artisan cache:clear
php artisan view:clear

npm install
npm run build

mysqldump -u USERNAME -p DATABASE_NAME > backup.sql

Changelog

Version 1.0 (14 February, 2026)

• - Initial Release