Course (Part 416)

Course: Laravel - Build Multi Vendor Ecommerce Website

Lesson

Topic: Introduction to Building a Multi‑Vendor Ecommerce Website with Laravel

Learning Outcomes

• Understand Laravel's MVC pattern and where models, views, and controllers fit in a multi‑vendor ecommerce system.
• Recognize and implement Eloquent relationships (vendor ⇄ product ⇄ order) to model multi‑vendor data.
• Build simple Blade views and controllers to display products, vendor dashboards, and user pages.
• Create RESTful API endpoints for product and vendor data consumption (JSON responses).
• Apply best practices for environment setup, version upgrades, and production deployment.

Conceptual Explanation

Composition (12–15 sentences):

Building a multi‑vendor ecommerce website with Laravel begins by adopting Laravel’s MVC pattern to separate concerns and keep the codebase maintainable. Models represent the core data — users, vendors, products, and orders — and Eloquent ORM makes defining relationships and querying straightforward. Views use Blade templates to render dynamic product listings, vendor dashboards, and user interfaces while controllers coordinate requests, validation, and business logic. For instance, a Product model can hold fields like name, price, description and vendor_id and declare a belongsTo relationship to Vendor. Controllers such as ProductController fetch product collections and pass them to Blade views for listing or to API endpoints for JSON responses. APIs allow mobile apps or third‑party systems to fetch product and vendor data using simple routes in routes/api.php. As the platform grows, leveraging queues for background jobs (emails, image processing) and caching for frequently requested listings helps maintain performance. Payment gateway integrations, secure authentication (Sanctum/Passport), and role/permission handling (Spatie) are necessary for production readiness. Local development setup using Composer, PHP, and a database (MySQL) speeds iteration and testing with Tinker and Artisan. Keeping the Laravel version up to date reduces technical debt but requires checking upgrade guides and package compatibility. Automated tests and database migrations ensure schema consistency across team environments. Finally, a staged deployment workflow (backup, migrate, cache, workers) helps safely promote changes to a live server. With these foundations, you can extend the platform to support vendor commissions, product reviews, flash sales, and analytics.

Core examples (concise)

Product model example (Eloquent):

namespace App\Models;
use Illuminate\Database\Eloquent\Model;
class Product extends Model {
    protected $fillable = ['name','price','description','vendor_id'];
    public function vendor() {
        return $this->belongsTo(Vendor::class);
    }
}

Blade snippet to show product:

{{ $product->name }}
Price: ${{ $product->price }}
{{ $product->description }}
Vendor: {{ $product->vendor->name }}

Simple API route:

Route::get('/api/products', [ProductController::class, 'index']);

Bilingual (EN → বাংলা)

Key terms and Bengali translations

English	বাংলা (Bangla)
Model	মডেল
View (Blade)	ভিউ (ব্লেড)
Controller	কন্ট্রোলার
Migration	মাইগ্রেশন
Eloquent ORM	ইলোকুয়েন্ট ORM
Route	রুট
API	এপিআই
Queue	কিউ (ব্যাকগ্রাউন্ড কাজ)
Cache	ক্যাশ
Deployment	প্রোডাকশনে মোতায়েন

Short bilingual note:

English: Use migrations and seeders for consistent database setup across environments. — বাংলা: পরিবেশগুলোর মধ্যে ডেটাবেস একই রাখার জন্য মাইগ্রেশন এবং সিডার ব্যবহার করুন।

Important Notes

• Always keep .env out of version control and configure environment-specific variables on the server.
• Run automated tests after upgrading Laravel and before deploying to production.
• Use Eloquent relationships with eager loading (with()) to avoid N+1 query problems.
• Protect API routes with authentication (Sanctum/Passport) and use request validation.
• Queue long-running tasks to background workers and monitor workers on the live server.

Exercises

True / False

1. Laravel’s Blade templates can be used for API JSON responses.
   Answer

   False. Blade is intended for HTML views. APIs should return JSON (resources, response()->json()).

2. Eloquent's with('relation') performs eager loading to reduce database queries.
   Answer

   True. Eager loading reduces the N+1 query problem.

3. It is safe to commit the .env file to a public repository.
   Answer

   False. Never commit .env; it contains secrets and environment configuration.

Fill in the Blanks

1. To create a new migration you run: php artisan make:migration ________.
   Answer

   Example answer: create_products_table

2. Eloquent relationship type for "one product belongs to one vendor" is ________.
   Answer

   belongsTo

3. Use ________ to run queued jobs in Laravel (Artisan command).
   Answer

   php artisan queue:work

Multiple Choice (MCQ)

1. Which file defines API routes in a Laravel application?
   1. routes/web.php
   2. routes/api.php
   3. app/Http/routes.php
   4. config/routes.php
   Answer

   routes/api.php — API endpoints are defined there.

2. Which package is commonly used for roles & permissions in Laravel?
   1. Intervention Image
   2. Yajra Datatables
   3. Spatie Laravel Permission
   4. Socialite
   Answer

   Spatie Laravel Permission — handles roles and permissions.

Matching

Match the left column (Laravel concept) to the right column (purpose).

Matching table

Concept	Purpose
1. Migration	A. Template engine
2. Blade	B. Background tasks
3. Queue	C. Database schema versioning
4. Eloquent	D. ORM / ActiveRecord

Answer

1. Migration — C (Database schema versioning)
2. Blade — A (Template engine)
3. Queue — B (Background tasks)
4. Eloquent — D (ORM / ActiveRecord)

Descriptive

1. Explain in 3–4 sentences how you would model vendors and products using Eloquent.
   Answer

   Use two models: Vendor and Product. Vendor hasMany(Product::class) and Product belongsTo(Vendor::class) with a vendor_id foreign key in products. Create migrations to define the tables and add indexes on vendor_id; use eager loading when listing products with their vendor to avoid N+1 queries.

2. Describe the steps to secure an API endpoint that returns user order history.
   Answer

   Protect the route with authentication middleware (e.g., sanctum). Validate the request and check authorization so the authenticated user only accesses their own orders. Use API resources to format the response and rate limiting / throttling to prevent abuse.

Creative

Design a small feature: vendor commission calculation — describe model fields and where to compute commissions (controller, observer, or job).

Answer

Model: CommissionRate (vendor_id, percentage, flat_fee, effective_from). When an order is completed, dispatch a queued job (CalculateCommissionJob) that computes commission = order_total * percentage + flat_fee, stores a VendorPayout record, and notifies the vendor. Use an observer on Order::updated to trigger the job when status changes to completed.

Activities, Vocabulary, Homework, Practice Task

Activities

1. Activity A: Create a new Laravel project, scaffold authentication (Breeze), and add a Vendor model and migration.
   Answer

   Run composer create-project, install breeze, migrate, and php artisan make:model Vendor -m to create the model and migration.

2. Activity B: Implement Product listing view with eager loaded vendor names.
   Answer

   In ProductController@index use Product::with('vendor')->paginate(10) and pass to Blade to loop and display vendor->name.

Vocabulary

• Migration — database schema version control.
• Seeder — initial data inserter.
• Guard — authentication layer for different user types.
• Webhook — external callback from a payment gateway.

Definitions (short)

See above; practice by creating a migration and seeder pair for sample categories.

Homework

1. Implement a Product API that supports filtering by vendor_id and price range. Provide pagination and return results as JSON resources.
Answer

Route: GET /api/products?vendor_id=1&min=10&max=100. Controller: validate query, build query with whereBetween('price',[min,max]) and where('vendor_id',vendor_id), then return ProductResource::collection($query->paginate(15)).

Practice Task

Deploy a small Laravel app to a test server: prepare .env, run composer install, migrate, seed, and start queue worker. Document each command.

Answer

1. scp or git clone to server
2. composer install --no-dev --optimize-autoloader
3. cp .env.example .env and edit credentials
4. php artisan key:generate
5. php artisan migrate --force
6. php artisan db:seed --force
7. php artisan config:cache & route:cache & view:cache
8. php artisan queue:work (supervise with supervisor or systemd)

End of lecture sheet. Use the details elements above to reveal full answers and implementation guidance while self‑testing.