Ibrasal Invest — Agricultural Commodity Export Platform

It is a full-featured agricultural commodity export platform built for the Nigerian market on Laravel 13 and PHP 8.3. It serves as a digital bridge between commodity producers, farm operators and export buyers, providing a structured online marketplace where agricultural products can be listed, discovered and ordered — and it goes well beyond a simple e-commerce tool by integrating farm management, crop and livestock tracking, inventory control, financial records and staff task management into the same platform.

Its primary users are agricultural exporters and commodity trading companies in Nigeria, farm operators who need to manage crops, livestock and field staff digitally, and export buyers seeking a structured platform for placing commodity orders. Secondary users include marketing and content teams managing the public website and blog, finance and operations staff tracking income, expenses and inventory, field workers using the staff portal for daily task management, and end customers placing orders and tracking fulfilment.

Two things. First, the entire transaction lifecycle — public product discovery, order placement, fulfilment tracking and customer receipt — is managed in one system with no third-party tools required. Second, unlike generic e-commerce tools it includes crop cycle tracking, livestock records, inventory management and staff task assignment, all purpose-built for agricultural operations and organised beneath each farm as the top-level unit.

There are four surfaces: the public website at /, the admin panel at /admin, the staff portal at /staff and the customer portal at /portal. All are served from one Laravel application using a single users table with a role column. Access is enforced at the middleware layer by AdminMiddleware, StaffMiddleware and CustomerMiddleware, each of which checks authentication and role on every request. Within the customer portal, queries are additionally scoped to the authenticated user's own ID so no buyer can see another's orders. Admin users are not granted staff portal access by default.

Yes — that is a core design goal. The admin panel includes a Page Builder with 15+ section types, a hero carousel manager, blog, services editor, team profiles, testimonials, stats, projects, banners, popups, galleries, a menu builder, a centralised media library and per-page SEO tools. Sections can be drag-sorted and toggled between published and draft. Global details such as the company phone number or social URLs live in a cached key/value settings store, so a single change in the admin panel propagates to every page with no code change or deployment.

English and French are supported out of the box via a session-based locale switcher in the public website header, positioning the platform for Francophone West African and European buyers. Translation strings live in per-locale directories under resources/lang/ and are accessed in templates through Laravel's translation helpers. Adding a further language means creating a new locale directory, copying and translating the English files, and adding the code to the switcher's options.

No third-party service is involved. A visitor opening the chat widget on any public page automatically creates a session-scoped conversation. Messages are stored in the platform's own database and the visitor's browser long-polls for new replies every few seconds, so admin responses sent from the /admin/chat inbox arrive in near real time. This requires no WebSocket server and no subscription, keeps the app deployable on standard hosting, and eliminates third-party data sharing. Admins can close resolved conversations and reopen them later.

Every order moves through a five-stage lifecycle — pending, confirmed, processing, shipped and delivered. As the shipment progresses, the admin appends tracking events, each with a timestamp, status label and physical location. Registered buyers log in to the Customer Portal, where they see their full order history, a visual tracking timeline showing each status transition with date and location, and a printable receipt containing the company header, order summary, line items and totals — all without contacting the company.

It runs on standard PHP and Laravel hosting — shared hosting, VPS, or cloud providers such as AWS or DigitalOcean — with no microservices, containerisation or real-time infrastructure required. Recommended production specification is PHP 8.3 (8.2 minimum), Composer 2, Node.js 22 LTS, MySQL 8.0+, and Nginx with PHP-FPM, from 2 GB RAM upwards. It is designed to upgrade in place as traffic grows: the synchronous queue can move to Redis with Laravel Horizon and Supervisor, file cache and sessions to Redis or the database driver, and a CDN can be placed in front of static assets. Performance work is already built in through eager loading, pagination on all list views, route, config and view caching, and a Tailwind JIT build that typically keeps CSS under 30 KB gzipped.

Role middleware guards every portal request and portal queries are scoped to the authenticated user's ID to prevent one customer reading another's data. CSRF protection applies to all state-changing requests, passwords are hashed with bcrypt and reset through Laravel's token-based flow, and every model uses explicit fillable arrays with all form input validated before persistence. Uploads are checked by MIME type and extension, stored outside the web root and never executed, with executable file types rejected. All database access uses parameterised Eloquent bindings rather than raw SQL, and Blade escapes output by default — unescaped rendering is limited to CMS content authored by authenticated administrators. The delivery guides also include a production hardening checklist covering debug mode, default credentials, firewall rules, TLS renewal and offsite backups.