ID — Bahasa Indonesia

Muhamad Irga

Purwokerto, Central Java

Updated

BPI Inventory — Stock & Asset Lending

A Filament inventory application for stock, incoming and outgoing goods, physical items, and capital-asset loans and returns by organisational unit.

See the service: ERP for Village Enterprises & Small Business

Screenshots

BPI Inventory dashboard with stock levels and asset lending records
Main application view · Open image for full resolution

Overview

What this system does.

BPI Inventory separates consumable-inventory management from capital assets available for lending. Its reference data covers items, categories, physical items, room locations, suppliers, organisational units, and users, while stock is recorded through incoming- and outgoing-goods transactions.

Capital assets have their own workflow, from lending and issue through return, so the location of each unit can be tracked. The administration interface is built entirely with Filament and Livewire on Laravel 11, with SweetAlert action notifications.

Feature inventory

Highlights

12 capabilities verified against the project source.

  • Item and inventory-category reference data
  • Physical-item records per item
  • Room placement and organisational units
  • Supplier reference data
  • Incoming-goods transactions
  • Outgoing-goods transactions
  • Capital-asset lending
  • Capital-asset issue records
  • Capital-asset returns
  • Data search and filtering through administration tables
  • User management and application settings
  • Inventory dashboard

Tech stack

Built with 5 technologies.

  • Laravel 11
  • Filament 3
  • Livewire 3
  • SweetAlert
  • MySQL

Common questions

What people usually ask.

Why separate consumables from capital assets?

Because they answer different questions. Consumables need a stock balance; a capital asset needs to be findable — who has it, in which room, under which unit — which is a lending workflow, not a quantity.

What is a physical item here?

An individual unit of an item, tracked separately so a specific piece of equipment can be issued, returned, and located rather than being one of an anonymous count.

What is it built with?

Filament and Livewire on Laravel 11, with the whole administration interface generated from the resource definitions rather than hand-built screens.

Same field

Need something like this?

Send a short brief and I’ll come back with scope, approach, and an honest timeline.