Company Site Buy on CodeCanyon
Documentation Menu
CodeCanyon-ready documentation

Professional product documentation for Ready eCommerce Bundle

Ready eCommerce Bundle is a Laravel + Flutter multi-store grocery marketplace solution. This upgraded documentation is designed to help buyers install, configure, run, update, and maintain the complete product with confidence.

Start Installation Support & Contact
One install.zip installs Website + Admin Panel Responsive Bootstrap 5 layout Searchable structured sections
Ready eCommerce Bundle landing page preview
Product Stack Laravel + Flutter

Website and Admin Panel install together, with a companion mobile app.

Documentation Scope End-to-End Setup

From server requirements and `.env` setup to updates and troubleshooting.

Submission Ready CodeCanyon Friendly

Structured headings, cleaner UX, and clearer technical guidance.

Last Refresh June 16, 2026

Reorganized for clarity, consistency, and a more professional presentation.

Introduction

Welcome to the Ready eCommerce Bundle documentation

This guide consolidates the original documentation into a single professional reference so customers can install the product faster, configure it correctly, and understand how the web app, admin panel, and Flutter app fit together.

What this documentation covers

  • Server and local environment preparation
  • One-step Laravel installation for both Website and Admin Panel
  • Database creation, migration, and optional demo data import
  • Flutter setup, Firebase/FCM integration, and store publishing
  • Product update workflow, troubleshooting, FAQ, and support guidance
Quick Facts
Product
Ready eCommerce Bundle
Author
RazinSoft
Web Installer
Website + Admin Panel
Support
CodeCanyon item support
Features

Features overview

Ready eCommerce Bundle is positioned as a complete grocery marketplace solution rather than a single storefront. The following feature areas are the ones buyers typically expect to understand before deployment.

Marketplace Architecture

Supports grocery, multi-store, and eCommerce workflows through a central web admin and a customer-facing storefront.

Admin Management

Use the Laravel admin panel to control catalog data, business settings, orders, promotions, users, and operational configuration.

Flutter Mobile App

The companion mobile app lets you deliver a native Android and iOS experience with Firebase notification support.

Payments & Checkout

Configuration support for payment gateways and purchase flows is included in the backend and mobile setup process.

Notifications & Messaging

Firebase and SMS-related settings can be configured to support customer communication and order-related notifications.

Update-Friendly Flow

The product includes an update path through the browser and server-side composer workflow for future releases.

Requirements

System requirements

Use the following baseline requirements before installation. Matching these versions or their compatible equivalents will reduce avoidable setup issues.

Web & Admin Requirements

Laravel stack
ComponentRecommendedNotes
PHP8.2.xEnable common Laravel extensions before installer launch.
Laravel10.xCore backend framework used by the product.
MySQL8.xCreate a dedicated database and user for production.
Composer2.7.x+Required for dependency install and updates.
Node.js / npmLatest LTSRecommended if frontend assets need rebuilding.
Web ServerApache / NginxPoint document root to Laravel `public/`.

Flutter App Requirements

Mobile stack
ComponentRecommendedNotes
Flutter SDK3.35.3Install from the official Flutter channel.
Dart3.5.0+Comes with Flutter SDK.
JDK21Set `JAVA_HOME` correctly for Android builds.
Android SDK35.0.0Install through Android Studio SDK Manager.
Android Studio2022.3+Install Flutter, Dart, and Gradle plugins.
XcodeLatest stableRequired only for iOS builds on macOS.

Required PHP extensions

Before starting the installer, make sure your server has the common Laravel requirements enabled, including `openssl`, `pdo`, `mbstring`, `tokenizer`, `json`, `xml`, `ctype`, `fileinfo`, `curl`, and `bcmath`.

Hosting tip

Shared hosting can work, but a VPS or managed cloud server generally gives better performance, control, and fewer extension-related issues.

Hosting Recommendation

Best server suggestions for production

Choose your production server based on expected traffic, order volume, and operational needs. A VPS or managed cloud server is strongly recommended over low-resource shared hosting for a Laravel marketplace with Website, Admin Panel, APIs, cron jobs, queues, and media uploads.

Production guidance

Start with a VPS that can handle Laravel, MySQL, storage, queues, and scheduled jobs reliably.

For most stores, the Standard / Medium Project plan is the best starting point. Upgrade when traffic, product count, image uploads, or concurrent orders increase.

Recommended baseline 2 vCPU / 4 GB RAM / 60 GB SSD Ubuntu LTS + Nginx + PHP-FPM + MySQL + SSL + cron scheduler
Starter

Small Project

Good for demos, early launch, or stores with light traffic and limited products.

CPU
1-2 vCPU
RAM
2 GB
Storage
40 GB SSD
Bandwidth
1-2 TB
Best forTesting, small catalog, low daily orders
Recommended

Standard / Medium Project

Best default choice for a real production launch with stable storefront and admin usage.

CPU
2 vCPU
RAM
4 GB
Storage
60-80 GB SSD
Bandwidth
2-4 TB
Best forProduction stores, regular orders, queues, cron jobs
Best Value

Business / High Traffic

Recommended when catalog size, customer activity, API usage, or order volume grows.

CPU
4 vCPU
RAM
8 GB
Storage
100+ GB SSD
Bandwidth
4-6 TB
Best forGrowing marketplaces, heavy uploads, active campaigns
High Performance

Enterprise / Large Scale

Use managed cloud infrastructure when uptime, scaling, and monitoring are critical.

CPU
8+ vCPU
RAM
16+ GB
Storage
200+ GB SSD
Bandwidth
Custom / scalable
Best forLarge teams, high traffic, load balancing, managed DB
DigitalOcean iconDigitalOceanBest overall VPS
Hostinger iconHostinger VPSBudget friendly
Namecheap iconNamecheap VPSCost effective
AWS iconAWSEnterprise scale
Production setup tip

Use Ubuntu LTS, Nginx, PHP-FPM, MySQL, Redis if queue/cache is needed, Certbot SSL, daily backups, and a properly configured cron job for Laravel scheduler.

Package

Package contents

After downloading the product from CodeCanyon, locate the web installer and mobile application source. The Website and Admin Panel are not separate web installations: both are deployed together from the same install.zip package.

Single Web Installation Package

install.zip installs the Website and Admin Panel together

Upload and install this archive once. The installer prepares the shared Laravel application, database, public Website, and protected Admin Panel in one guided process.

Website Admin Panel

install.zip

The complete Laravel web system containing both the Website and Admin Panel.

Flutter App

The companion Android and iOS source package, configured after the web system is online.

Documentation

Updated setup, publishing, and maintenance instructions.

Installation

Install the Website and Admin Panel together

Ready eCommerce Bundle uses one guided web installation. Upload install.zip to your server and complete the installer once; the process installs and configures both the public Website and the Admin Panel automatically.

One installer, two ready-to-use interfaces

What the installer deploys

The Website and Admin Panel share the same Laravel application, database, and configuration. Do not upload or install them separately.

WebsiteCustomer storefront
Admin PanelBusiness management
Before you begin

Connect the domain or subdomain to the target server directory, confirm the required PHP extensions are enabled, and keep your database details and CodeCanyon purchase code ready.

01
Upload package

Open File Manager and upload install.zip

Sign in to your hosting control panel, open File Manager, and navigate to the document root connected to your domain. Upload the provided install.zip file to this directory.

Open File Manager in cPanel
1A Open cPanel File Manager.
Select the installation ZIP file for upload
1B Select and upload install.zip.
Use the provided archive

Upload install.zip directly. You do not need separate Website and Admin Panel archives.

02
Extract files

Extract the archive into the domain root

After the upload reaches 100%, return to File Manager, select install.zip, and choose Extract. If the files are extracted inside a nested folder, move all extracted contents into the domain root.

Completed ZIP file upload in cPanel
2A Confirm the upload is complete.
Extract install ZIP in cPanel
2B Extract the installation archive.
Move extracted files to domain root
2C Move extracted files to the domain root when required.
03
Create database

Create a MySQL database and assign a user

From cPanel, open MySQL Database Wizard. Create a new database, create or select a database user, assign the user to the database, and grant all required privileges. Keep these credentials available for the installer.

Open MySQL Database Wizard in cPanel
3 Create the application database with MySQL Database Wizard.
04
Launch installer

Open your installation URL and pass the server checks

Open the domain connected to the extracted files, for example https://your-domain.com. Select Start Installation Process, review the directory permission check, and confirm every required PHP extension is enabled before continuing.

Do not continue with failed checks

If a required extension or folder permission is marked as unavailable, correct it in your hosting panel and refresh the installer before proceeding.

05
Application settings

Configure the shared Website and Admin Panel application

Enter the application name and base URL, select production as the environment, use public as the filesystem, and keep debug mode disabled for a live server. These settings apply to both interfaces.

Ready eCommerce Bundle application configuration fields
5 Complete the shared application settings.
06
Database connection

Enter the database credentials

Select MySQL and enter the host, port, database name, username, and password created in Step 3. The default MySQL port is usually 3306; the database host depends on your hosting provider.

Ready eCommerce Bundle database credential fields
6 Connect the installer to your database.
07
License verification

Verify your CodeCanyon purchase

Enter your email address, domain, CodeCanyon username, and valid Ready eCommerce Bundle purchase code. Submit the verification form to continue to final installation.

Ready eCommerce Bundle CodeCanyon purchase verification form
7 Verify the licensed purchase.
08
Complete installation

Finish once, then access both interfaces

Review the final confirmation and select Final Submission. The installer creates the database structure and completes the shared Laravel setup. After the success screen appears, use the links below to access the Website and Admin Panel.

Customer Websitehttps://your-domain.com
Admin Panel (default route)https://your-domain.com/admin
Installation complete

Your Website and Admin Panel are now installed together and connected to the same database. Sign in to the Admin Panel to complete business settings before launch.

After Installation

Production launch checklist

Complete these checks before allowing customers to use the Website.

  • Sign in to the Admin Panel and change the default administrator password.
  • Configure branding, business details, currency, timezone, mail, payments, and notifications.
  • Confirm the Website loads over HTTPS and test registration, checkout, and order management.
  • Remove the installation archive from the server after confirming the system works.
Environment

Environment setup

The web installer creates the core environment configuration for both the Website and Admin Panel. The `.env` file shown below is an advanced reference for administrators who need to review or update server-level settings after installation.

Minimum `.env` example 
APP_NAME="Ready eCommerce Bundle"
APP_ENV=production
APP_URL=https://your-domain.com

DB_DATABASE=your_database_name
DB_USERNAME=your_database_user
DB_PASSWORD=your_database_password

MAIL_MAILER=smtp
MAIL_HOST=smtp.gmail.com
MAIL_PORT=587
MAIL_USERNAME=your_email@example.com
MAIL_PASSWORD=your_mail_password
MAIL_ENCRYPTION=tls
MAIL_FROM_ADDRESS=no-reply@example.com

Configuration checklist

  • Set `APP_URL` to the final live domain for production.
  • Use a dedicated database user with the correct privileges.
  • Verify SMTP credentials before enabling transactional email flows.
  • Keep production secrets outside public repositories.
  • Review any payment, SMS, and Firebase keys from the admin settings panel after installation.
Database

Database setup

Create one empty MySQL database before opening the web installer. During installation, Ready eCommerce Bundle connects both the Website and Admin Panel to this same database and prepares the required tables automatically.

Create a database in phpMyAdmin
Example: creating a new database from phpMyAdmin.

Recommended database flow

  1. Create a dedicated database for the application.
  2. Create or assign a dedicated database user.
  3. Update `.env` with the database name, username, and password.
  4. Run migrations and any package-specific setup commands.
  5. Optionally load demo data for testing and evaluation.
Optional demo data command 
php artisan app:push-data
Configuration

Configuration guide

Once the application is installed, complete the business and service-level settings from the admin panel so the product can operate correctly in production.

General Settings

Application name, domain, branding, timezone, and localization preferences.

Mail Settings

SMTP host, port, encryption type, and sender identity for transactional messages.

Payments & SMS

Configure gateway credentials and any supported SMS provider details carefully.

Mobile Services

Set Firebase, FCM, and application package identifiers for Android and iOS.

Architecture

Folder structure

The downloaded CodeCanyon package keeps the installable web system and Flutter source separate. Upload only install.zip for the Website and Admin Panel installation.

Downloaded package layout 
Ready eCommerce Bundle-Package/
|-- install.zip              # Website + Admin Panel web installer
|-- flutter-app/             # Mobile application source
|   |-- android/
|   |-- ios/
|   |-- lib/
|   |-- assets/
|   |-- pubspec.yaml
|-- documentation/
|   |-- index.html
|   |-- assets/
Admin Panel

Admin panel overview

The admin panel is the operational center of Ready eCommerce Bundle. After installation, review every settings area before allowing real customer traffic.

Ready eCommerce Bundle admin screen example
Example screen from the original Ready eCommerce Bundle product flow.

Areas to review first

Catalog Setup

Products, categories, brands, units, and inventory-related settings.

Order Operations

Order review, status management, fulfillment, and customer communication.

User Management

Customers, administrators, and role-based operational access.

Business Settings

Payments, mail, notifications, branding, taxes, and delivery-related configuration.

Usage

User guide

The customer-facing experience should be tested from end to end after installation. Use the following journey as a practical QA checklist before launch.

1

Browse

Confirm customers can view home content, categories, offers, and product listings.

2

Cart

Verify cart operations, quantity updates, shipping logic, and pricing calculations.

3

Checkout

Test address selection, payment flows, and order placement success states.

4

Order Tracking

Ensure order history, status updates, and customer notifications work as expected.

Flutter

Flutter mobile app setup

The original documentation already included a detailed Flutter setup path. The streamlined workflow below preserves those steps while making them easier to follow.

Recommended setup sequence

  1. Install Git, Android Studio, VS Code, and JDK.
  2. Set `JAVA_HOME` and avoid directory paths with spaces where possible.
  3. Install Flutter, Dart, and Gradle plugins in Android Studio.
  4. Download and extract Flutter SDK to a clean local path.
  5. Run `flutter --version` and `flutter doctor` until all critical issues are resolved.
  6. Open the Flutter project, run `flutter pub get`, and launch on an emulator or a physical device.
Flutter quick commands 
flutter --version
flutter doctor
flutter pub get
flutter run
flutter build apk --release
flutter build ios --release
Flutter doctor setup screenshot
Use `flutter doctor` to confirm your machine is ready for Android and iOS builds.
Firebase

FCM and Firebase setup

Push notifications require project-level Firebase configuration for both Android and iOS. Keep the Firebase project identifiers aligned with your application package names and bundle IDs.

Android checklist

  • Create or select a Firebase project.
  • Add the Android application inside Firebase.
  • Place the generated `google-services.json` file in the Android app module.
  • Update Gradle files to load Google services and Firebase dependencies.
  • Confirm manifest-level notification configuration if your build requires it.

iOS checklist

  • Add the iOS app to the same Firebase project.
  • Place `GoogleService-Info.plist` in the iOS project.
  • Install iOS dependencies with CocoaPods.
  • Update `AppDelegate.swift` and notification permissions where needed.
  • Test token generation and foreground/background push behavior on a real device.
Typical Flutter Firebase packages 
firebase_core
firebase_messaging
Publishing

Store publishing guide

The original documentation included detailed Google Play and Apple App Store walkthroughs. This section keeps the practical checkpoints while presenting them in a cleaner review-friendly format.

Google Play Store

Android
  1. Create a Google Play Console developer account.
  2. Set up a Google Merchant account if your app uses paid products or in-app purchases.
  3. Create the application and complete the store listing.
  4. Upload screenshots, icon, descriptions, category details, and privacy policy.
  5. Complete content rating, policy declarations, and app signing requirements.
  6. Upload the Android release build and submit it for review.

Apple App Store

iOS
  1. Sign in to your Apple Developer account.
  2. Create the app in App Store Connect using the correct bundle identifier.
  3. Generate the required API key and record the Issuer ID and Key ID if your workflow uses them.
  4. Prepare metadata, pricing, age ratings, privacy content, and screenshots.
  5. Archive the iOS build, upload it through the correct Apple toolchain, and submit it for review.
Google Play listing setup example
Google Play listing preparation example.
Apple App Store Connect setup example
App Store Connect setup example.
Updates

Update guide

Before updating a live site, back up your project files and production database, and perform the update on a staging copy first whenever possible.

What an update preserves vs replaces

Preserved (never touched)Replaced (new release wins)
.env (all your config & keys)All application code (app/, routes/, resources/, …)
storage/ (uploads, logs, backups)vendor/ (shipped with each release)
public/storage symlink & public/uploadspublic/build compiled assets
Your database (migrations are additive)composer.lock, VERSION
Recommended

Option A — update.sh

Automated
  1. Upload & extract the new release zip somewhere outside the live folder, e.g. /home/user/releases/readyecommerce-v1.1.0.
  2. From the live project root, run the update script pointed at that release folder.
  3. It backs up the DB to storage/backups/, enters maintenance mode, rsyncs the new code over the install (preserving .env + storage/ + uploads), runs new migrations only, rebuilds caches, and brings the site back up.
Run update.sh 
./update.sh /home/user/releases/readyecommerce-v1.1.0
Manual path

Option B — manual overwrite

Advanced
  1. Back up your database and your .env.
  2. Run php artisan down.
  3. Copy the new release over the live folder, except: do not overwrite .env, and do not delete storage/ or public/storage / public/uploads.
  4. Run php artisan migrate --force.
  5. Run php artisan optimize:clear, then php artisan config:cache, php artisan route:cache, and php artisan view:cache.
  6. Run php artisan queue:restart.
  7. Run php artisan up.

Rollback

  1. Run php artisan down.
  2. Restore the previous release's files (keep your .env + storage/).
  3. Restore the DB backup from storage/backups/pre-update-*.sql: 
    mysql -u USER -p DBNAME < storage/backups/pre-update-....sql
  4. Run php artisan optimize:clear then php artisan up.

Seller checklist (before shipping a release)

  • Bump VERSION (build-release.sh persists the version you enter).
  • Keep migrations additive and idempotent — guard with Schema::hasTable() / Schema::hasColumn() so they are safe to run on populated production databases. Never rename or drop columns in a point release.
  • Run ./build-release.sh <version> and verify the zip contains vendor/ and .env.example, and does not contain .env, storage/installed, or any credentials.
  • Test ./update.sh from the previous release on a staging copy.
Help

Troubleshooting

If installation or runtime behavior is not working as expected, review these common problem areas first.

Confirm the Laravel writable directories have the correct permissions, especially `storage/` and `bootstrap/cache/`.

Double-check the database host, name, username, password, and privileges in the `.env` file, then verify the MySQL service is running.

Re-check your JDK, SDK, Android Studio plugins, accepted licenses, and environment variables. Resolve all critical items shown by `flutter doctor`.

Reconfirm SMTP or SMS credentials from the admin settings panel and test with valid provider credentials, correct ports, and encryption settings.
FAQ

Frequently asked questions

These are the most common questions customers tend to ask while setting up a marketplace product like Ready eCommerce Bundle.

Need a quick answer?

Open each question below for concise setup guidance. The first item is expanded by default so new buyers immediately understand the installation flow.

Yes. Use the same install.zip web installer in a compatible local PHP/MySQL environment. It still installs both the Website and Admin Panel together.

Your live document root should point to the Laravel public/ directory for a standard production setup.

Yes. The Flutter app requires its own SDK, Firebase setup, and store publishing configuration after the Website and Admin Panel installation is complete.

No. Upload and run install.zip once. The same installer deploys and configures both interfaces together in one installation process.

If your package includes the demo data workflow, use the documented command: php artisan app:push-data.

Yes. Follow the documented update process carefully and always back up your files and database before applying updates.

Check that the email, CodeCanyon username, domain, and purchase code are correct and match the product owner account.
Support

Support information

Support works best when the request includes enough technical context. Before contacting support, collect the details below so the team can identify the issue faster.

Include these details in your support request

  • Product version and purchase confirmation details
  • Server or hosting environment information
  • Exact error message or screenshot
  • Steps to reproduce the issue
  • Whether the problem is on web, admin, Android, or iOS

Official support channels

For item support, license-related help, and product questions, use the official channels below.

CodeCanyon Portfolio Contact RazinSoft Company Website
Latest updates

Release changelog

Track Ready eCommerce Bundle improvements, bug fixes, and production-ready updates in a clean release timeline.

3Recent releases
17+Fixes & improvements
StableProduction focused
Latest

Version 1.2.2

12 January 2026

01

What we updated

  • Adapted for Report Extension.
  • Fixed minor code errors.
  • Fixed minor UI issues.
  • Improved some SQL queries.
Improvement

Version 1.2.1

09 December 2025

02

What's new

  • Fixed minor code errors.
  • Optimized admin panel code for better stability.
  • Improved overall system performance.
Feature release

Version 1.2.0

19 November 2025

03

What's new

  • Added new feature: Guest Checkout.
  • Resolved message box issue.
  • Fixed outside message box overlapping issue.
  • Fixed design overlapping issue.
  • Resolved responsive issue on the message page.
  • Ensured coupon applies only once per order in POS draft flow.
  • Fixed date-wise order statistics issue in admin panel.
  • Corrected edit button showing wrong product details when switching pages in POS.
  • Fixed “Mark as Received” error in Purchase Details.
  • Created API for Shop Gallery.
Credits

Credits and third-party libraries

This documentation website uses the following third-party resources.

Library / AssetUsageWebsite
Bootstrap 5Responsive layout and UI componentsgetbootstrap.com
Bootstrap IconsInterface iconsicons.getbootstrap.com
Google FontsTypography: Outfit and JetBrains Monofonts.google.com
Original product screenshotsDocumentation illustration assetsIncluded with the product package