Tams ERP
ERP-lite for a seed and fertilizer distributor, from stock to installments to financial reports

- YEAR
- 2026
- CATEGORY
- ERP / Finance
- STATUS
- Private session
- TECH STACK
- LaravelFilamentPHPMySQLTailwind CSS
Overview
Tams ERP is a custom system built for a distributor of seeds and fertilizers. It consolidates stock management, installment-based payments, employee payroll, and financial reporting into a single platform, replacing manual spreadsheet processes that had no shared source of truth.
The Problem
The distributor tracked inventory, customer payments, and company finances without a unified system. Payments were often made in installments across several transactions, so reconciling who owed what was difficult. Payroll and financial reporting were done by hand, which created a high risk of error and no single source of truth for decisions.
My Role
I was the sole developer across the full lifecycle, from requirements gathering and system design to implementation and deployment, and I worked directly with the client through iterative review cycles across five months. I delivered the system as an ERP-lite with 20+ Filament resources covering linked transactions: supplier installments per pool, automatic stock revalidation when a transaction is edited, customer installments accumulated into one pool per user, and delivery-based payroll that lands in the financial report at the same time as supplier installment payments.
Process
I started by mapping the daily flow of a seed and fertilizer distributor, then modeled it into entities that stay consistent with each other: supplier installment pools, stock levels, a customer installment pool per user, delivery-based payroll, and a unified financial report. I built it with Laravel and Filament as 20+ resources, then ran iterative review cycles with the client over five months.
Key Features
- 01Stock-driven transactions: inventory levels control what can be sold
- 02Automatic stock revalidation when a transaction is edited
- 03Supplier installments tracked per pool
- 04Customer installments accumulated into one pool per user
- 05Delivery-based employee payroll entered into the financial report
- 06Unified income and expense reporting
- 0720+ Filament resources
Challenges
The hardest requirement was linked transactions. Editing one transaction has to revalidate stock automatically, customer installments accumulate into a single pool per user, and supplier installment payments must land in the financial report at the same time as delivery payroll. Keeping all of that consistent in one pass is what made this an ERP-lite system rather than a simple ledger.
Outcome
The system is live and actively used by the client on an annual maintenance retainer. It removed the manual reconciliation of installment payments, a previously error-prone workflow, and gave the owner a consolidated view of company finances for the first time.
