Vendor Dashboard Design for PIM System

PIM Product Management System
Main Idea
A dashboard where vendors can:
- Update current items uploaded by admin manually or in bulk via Excel.
- Download items or upload new items for admin approval.
- Updates and new entries must be approved first by admin (individually or in bulk).
- Vendors can register as users and must be approved and assigned to a vendor from the predefined list.
- Products are assigned to specific vendors, and each vendor can only see and manage their own products.
Feature List
User Management
• - Permissions
• - Roles
• - Users
• - Vendor Management
Product Data Fields
• - Product Name (Arabic)
• - Product Name (English)
• - Description (Arabic)
• - Description (English)
• - Brand (From brand list)
• - Group (From group list)
• - Product ID (Number)
• - International Barcode GTIN/EAN (Number)
• - Category (From list)
• - Sub Category (From list)
• - Sub Sub Category (From list)
• - Usage Instructions (English, Arabic) (Textarea)
• - Main Image (Photo)
• - Additional Images (Photo)
• - Product Video (File)
• - Selling Points (1-4) (Text)
• - Warnings & Precautions (Textarea)
• - Meta Title, Description, Keyword (Text)
• - Size Volume, Product Form, Country of Origin (From list)
• - Symptoms, Health Condition, Age Group, Size, Skin Type (From list)
• - Active Ingredients 1-3 (Text)
• - Pack Type, Dose Potency, Alternatives/Substitutes, Product Use Type, Gender (From list)
• - Branded, Generic, Wasfaty, Prescription Require (Checkbox)
• - Updated At, Deleted At (Datetime)
• - Created By
Master Data
• - Brand Management
• - Group Management
• - Category Management
• - Sub Category Management
• - Sub Sub Category Management
Dashboard & Reports
• - Dashboard with Ajax DataTables
• - User Registration with Admin Approval and Two-Factor Authentication via Email
• - Audit Logs View and Export
• - CSV Import and Export for Products, Brands, and All Categories
• - API Endpoints for:
• - - Fetching Product Data
• - - Receiving Updates

*sample attached* :
how to Deployment it :

Extract the archive and put it in the folder you want
Run cp .env.example .env file to copy example file to .env
Then edit your .env file with DB credentials and other settings.
Run composer install command
Run php artisan migrate --seed command.
Notice: seed is important, because it will create the first admin user for you.
Run php artisan key:generate command.
If you have file/photo fields, run php artisan storage:link command.
And that's it, go to your domain and login:

Default credentials
Username: admin @ admin.com
Password: password