ERP · HR, Payroll, Inventory & Sales
Payroll for 214 workers, every battery by serial number, and a dealer network — one system, three languages.
Problem
Payroll ran on Excel, across three ways of paying people — a fixed monthly salary, piece rate on what each worker makes, and target pay for sales — and the sheets carried floating-point errors like 26,062.068965517243. Attendance, leave, production, stock and dealer accounts lived in separate files, and accounting entries were typed into Tally a second time by hand. The factory floor has Bangladeshi workers and Chinese engineers, so the system had to work fully in Bangla, English and Chinese, and every salary, price and stock movement needed a record of who made it, who checked it and who approved it.
Build
An ERP for T.E Industrial, the battery manufacturer behind TE POWER in Jessore: HR and payroll for 214 workers, a serial-tracked battery inventory and a dealer sales platform, on one login, one database and one audit trail, with an Android app. It works in Bangla, English and Chinese. HR and Payroll are live; Inventory and Sales are built and opening in phases.
- Category
- ERP · HR, Payroll, Inventory & Sales
- Year
- 2026
- Applications
- 2
- Stack
- Next.js · React · TypeScript · PostgreSQL · Prisma · Tailwind CSS · Capacitor (Android)
In numbers
- modules across HR & Payroll, Inventory and Sales
- 70+
- employees in 16 sections on the payroll
- 214
- languages: Bangla, English and Chinese
- 3
- upazilas mapped for dealer territories
- 495



- Problem
- Build
- The system
- Delivered

Chapter 01
The client and the problem
Payroll ran on Excel, across three ways of paying people — a fixed monthly salary, piece rate on what each worker makes, and target pay for sales — and the sheets carried floating-point errors like 26,062.068965517243. Attendance, leave, production, stock and dealer accounts lived in separate files, and accounting entries were typed into Tally a second time by hand. The factory floor has Bangladeshi workers and Chinese engineers, so the system had to work fully in Bangla, English and Chinese, and every salary, price and stock movement needed a record of who made it, who checked it and who approved it.

Chapter 02
What we built
We built one platform in three parts that share a single database. In HR & Payroll, supervisors mark attendance on their phones and three salary engines — fixed and prorated, piece rate on the quantity QC accepts, and target — produce a salary sheet that moves from maker to checker to approver and then locks, so a past month can never change. Inventory gives every battery a serial and a QR label, keeps a stock ledger where corrections are reversals rather than edits, follows raw material from requisition to production against the bill of materials, and sends accounting vouchers to Tally. Sales maps all 64 districts and 495 upazilas, takes a dealer from onboarding to a credit limit, an order to the gate, and a battery to its warranty by scanning the QR code. Workers see their own pay and leave on their phones, in an installable web app or the Android app, and the whole interface follows SAP Fiori's design language, so it feels like the enterprise software it is.
Chapter 03
The system
2 applications, each with its own job, sharing one source of truth.
- 01Web ERP — HR, stock, sales
- 02Android app
Chapter 04
Delivered
Everything that shipped, in the client's hands.
- HR & Payroll — records, attendance, leave, and three salary engines: fixed, piece rate and target
- Salary sheet that goes maker → checker → approver, then locks for good
- Loans, bonuses, PF and gratuity, TA/DA, increments and final settlement
- Worker self-service — their own payslip, leave and requests to HR, on the phone
- Every battery serialised with a QR label; a stock ledger that can only be added to
- Raw material store, production against versioned bills of materials, and procurement
- Dealers, credit limits, orders, challans, ledger and collections across 64 districts
- Warranty registered by scanning the battery's QR code; Tally vouchers, Excel and PDF reports
Under the hood
Built to be trusted with money.
- 01
Money is never a floating-point number
Exact decimals everywhere and one rounding point. Every payslip line traces back to the attendance, production entry or approval that produced it.
- 02
Rules are settings, not code
Rates, multipliers, thresholds and rounding are set by the company, per section or per person. A locked month keeps the rules it was paid by, so rerunning it gives the same figures.
- 03
Whoever prepares it can't approve it
Separation of duties is checked by account across payroll, stock and sales, not left to good intentions.
- 04
Every change is audited
Who, what, the old value, the new value, when and why — for every change in the system.
- 05
An unset rule is never guessed
A piece rate nobody has set holds the row for review instead of paying zero, and the dashboard says how many people that affects.
- 06
Each person sees only their part
Supervisors see their own sections and sales officers their own territories, enforced on the server, not just hidden on the screen.
The screens
Every screen we shipped.
Screens show demo data, not the client’s records.
The screens
























Have something like this in mind?
Tell us what you are trying to build. We reply within one working day.
