Back to all projects

CASE STUDY

Agribusiness

CRM Ubi Jalar

A web application connecting farmers’ sweet potato catalogs with buyer orders. Buyers explore products and promotions, farmers manage stock and orders, and administrators oversee products, promotions, and accounts.

TECHNOLOGIES USED

Laravel 10 / PHP 8.2 / MySQL / MariaDB / Blade / Bootstrap 5 / AdminLTE / Chart.js

Preview of CRM Ubi Jalar

PROBLEM

Several farmers manage products and orders, but each role needs different information. Buyers need clear prices and stock levels, farmers should only handle their own products and orders, and administrators need an overview across accounts.

MAIN FEATURES

  1. 01

    Catalog and promotional prices

    Buyers see images, prices, stock, the selling farmer, and active discounts for each product.

  2. 02

    Orders and history

    Orders retain the product, quantity, total, and status for buyers to review later.

  3. 03

    Farmer workspace

    Farmers manage their own products and promotions, review incoming orders, and complete them with stock updates.

  4. 04

    Cross-account admin panel

    Administrators manage users, products, and promotions and see an activity overview on the dashboard.

IMPLEMENTATION

I separated the application into buyer, farmer, and admin areas. Buyers browse the catalog, review product details and promotions, place orders, and check their history. Farmers manage products and promotions, see orders for their own products, and mark orders as completed. Administrators manage products, promotions, and users in a separate panel. Completing an order updates stock inside a database transaction to prevent the same change being applied twice.

RESULT

Each order remains linked to its product and the farmer who owns it. Buyers can revisit their orders; farmers handle orders for their own products, and stock updates when an order is completed. Administrators have a dashboard summarizing products, promotions, buyers, and farmers.

Need an application for a similar workflow?

Tell me who will use it, how the current process works, and which features are required. I’ll review the requirements before discussing the technical solution.

Talk About a Project