Quick Start

Get Sellino's web backend and both mobile apps running — the shortest path, with links to every detailed step.
Version: 1.0.0
Stack: Laravel 12 · Flutter · MySQL 8

Developed By: BugBuild Labs

What You're Setting Up

Sellino is one Laravel backend + database with three faces on top of it: the customer website (storefront) and admin panel, a Flutter Customer App, and a Flutter Seller App. Set up the backend first — everything else points at its API.

Web Backend

Laravel admin panel, customer storefront and the /api/v10 that powers both apps. Install this first.

Jump to setup →
Customer App

Flutter buyer app (Android & iOS). Point it at your API URL, rebrand, build.

Jump to setup →
Seller App Multi-vendor

Flutter merchant app for vendors/store owners. Same idea — API URL, chat key, rebrand, build.

Jump to setup →

Setup Order

Follow the three stages in order. Each app needs the backend's API to be live and reachable over HTTPS first.

Fastest path to a working store: finish stage 1 (backend + first admin login) and you already have a live website and admin panel. The mobile apps in stages 2–3 are added on top whenever you're ready.

Stage 1 · Web Backend (Laravel)

Install the Laravel source from the WebSourceCode folder onto your server. Full details are in the Web (Admin) guide — the steps below link straight to each one.

  1. Check server requirements

    PHP 8.3+, MySQL 8.0+, Composer, Node.js. The web installer verifies each item on its first screen.

  2. Create the database

    Make a MySQL database + user (cPanel wizard) and keep the name, user and password ready.

  3. Upload files & set environment

    Upload WebSourceCode, point the web root at public/, create .env and set writable permissions.

  4. Run the installer

    Open your domain, fill in the database details and create your first admin account — it migrates and seeds automatically.

  5. Log in to the admin panel

    Sign in at the randomized admin login slug, then set store name, currency, logo and payment gateways in Settings.

  6. Optional add-ons — Real-time chat, Push (Firebase), S3 storage

    Turn these on when you need them. Push is also required if you want the mobile apps to send notifications — the full Firebase procedure is in Common Setup.

Before the apps: confirm https://yourdomain.com/api/v10 is reachable over valid HTTPS — the Customer and Seller apps will connect to exactly this URL.

Stage 2 · Customer App (Flutter)

Build the buyer app from the CustomerAppCode folder. Full details are in the Customer App guide.

  1. Set up Flutter

    Install Flutter (stable) + Android Studio / Xcode, then run flutter doctor and fix any issues.

  2. Point it at your backend

    Run flutter pub get, then set kBaseUrl and kAppApiKey in lib/core/env/prod_env.dart (release) — base URL https://yourdomain.com/api/v10, key from Settings → API Security.

  3. Add Firebase (for push)

    Drop in google-services.json / GoogleService-Info.plist; iOS also needs the APNs key uploaded to Firebase. Full steps in Common Setup.

  4. Rebrand — name, id & icon

    Change the app name and package/bundle id from com.sellino.customer, then generate icons with dart run flutter_launcher_icons.

  5. Build & release

    Create a keystore + key.properties for Android; set your Team & bundle id in Xcode for iOS. Build the .aab / .ipa and publish.

Stage 3 · Seller App (Flutter) Multi-vendor

Build the merchant app from the SellerAppCode folder. Full details are in the Seller App guide.

  1. Set up Flutter

    Same toolchain as the Customer App, plus a seller/admin account on your backend to log in with.

  2. Point it at your backend + chat key

    Run flutter pub get, then set kBaseUrl, kAppApiKey and kReverbAppKey (must match the backend's REVERB_APP_KEY) in lib/core/env/prod_env.dart.

  3. Add Firebase (for push)

    Same Common Setup procedure as the Customer App — this app's own config files plus the shared iOS APNs key.

  4. Rebrand — name, id & icon

    Change the app name and id from com.sellino.seller, then regenerate the launcher icon.

  5. Build & release

    Wire up your own release keystore (don't ship the debug signing override), build and publish to the stores.

Go-Live Checklist

A quick pass before you open the doors to real customers:

  • Site served over valid HTTPS and the web root points at public/.
  • php artisan key:generate ran and APP_KEY is set (the installer does this).
  • Store name, currency, timezone, logo/favicon set in Settings.
  • Payment gateways switched to live keys (test keys only process test payments). Using Stripe or PayPal? Also set the charge currency, paste the Stripe webhook URL & signing secret, and make sure every currency has an exchange rate — a missing rate blocks international payments.
  • Scheduler cron added (schedule:run) if you use scheduled push campaigns, backups or nightly currency-rate updates.
  • Legal pages reviewed under Website → Pages — Privacy, Terms and Return & Refund ship with placeholder text.
  • Mail/SMTP configured so OTP and notification emails send.
  • Both apps point at the production API URL and were rebuilt after any config change.
  • Firebase push tested on a real Android and iOS device (iOS needs the APNs key).
  • Real-time chat (Reverb) kept running under Supervisor if you use live chat.

Need the detail behind any step? Open the Web (Admin), Customer App or Seller App guide from the tabs above — each Quick Start link jumps to the exact section.