Project Overview
- Project Name: SIBIMA
- Company: PT Sibima Berkarya Mandiri
- Application Type: B2B Marketplace
- Launch Year: 2024 - PT Xeno Persada Teknologi
- Industry: Industrial & Trading
- Role: Web Frontend & Backend Developer
- Live: https://sibima.id
Background & Problem
The company needed a platform to market its products with low application fees while also enabling external vendors to sell their products.
Project Goals
- Provide an efficient and sustainable B2B procurement platform
- Connect manufacturers, distributors, and retailers in one ecosystem
- Help businesses find products at competitive prices
Solution & System Concept
- Centralized B2B marketplace for industrial and commercial products
- Multi-product and multi-brand catalog
- Supports procurement across multiple sectors, including industrial, marine, plantation, machinery, and spare parts
Features
- User authentication (login and registration)
- Product catalog and shopping cart
- Shipping fee calculation via third-party API
- Checkout process
- Virtual account payment integration via third-party API
- Admin dashboard
Technology Stack
- Backend: PHP with Laravel Framework (Admin Panel) and Lumen Framework (API Service)
- Frontend: JavaScript with Next.js Framework
- Database: MySQL
Challenges & Solutions
-
Challenge: Developing frontend and backend independently
Solution: Designed reusable APIs for both web and mobile clients and closely coordinated with the mobile frontend team to align requirements.
-
Challenge: Integration with payment and logistics service providers
Solution: Carefully studied API documentation and fully understood the integration flow before implementation.
-
Challenge: Migrating from a jQuery-based template to Next.js
Solution: Gradually rewrote and refactored features into the Next.js framework.
Results
- Frontend and backend services are reusable for both web and mobile platforms
- Payment and logistics service providers were successfully integrated
Lessons Learned & Improvements
- This was my first project at the company, and some parts of the codebase were not yet optimal or scalable. I learned the importance of better code structure and scalable architecture, which I continue to improve in subsequent projects.
Screenshots

