Crusher Management System

The challenge

The client sold crushed stone to a steady stream of vehicles across several branches, and most of the paperwork lived on paper and in memory.

• Loose vehicle records. Truck volumes were checked by hand, so disputes over load size were hard to settle.
• Untracked credit. Customers bought on credit with no enforced limit or clear running balance.
• Scattered expenses. Spending, spare-part usage and wages were recorded separately, with no cap on any category.
• Manual payroll. Salaries were calculated by hand each month and never linked to the expense book.
• No branch separation. Owners could not compare branches or keep each branch’s data apart.
• They needed one system where every sale, rupee and spare part was traceable to a branch, a user and a date.

Our solution

We built one platform that follows a vehicle from the gate to the ledger. A truck is recorded, billed, and printed on a voucher, and any unpaid balance moves into the customer’s account.

• Branch isolation by default. Every operational record belongs to a branch, so each branch sees only its own data.
• Role-based control. A Super Admin oversees all branches, an Admin runs one branch, and an Accountant enters data without edit rights.
• Built-in guardrails. Credit limits and spending limits are enforced by the system rather than by policy documents.

Key features

The platform has 13 modules. These are the ones clients ask about most.

Technical approach

We chose a lightweight stack so the client could host the system on ordinary shared hosting with no build step or specialist servers.

• Backend: a plain PHP REST API using PDO and MySQL, with bearer-token authentication.
• Frontend: HTML, CSS and JavaScript with Bootstrap 5, jQuery AJAX and DataTables for fast, searchable lists.
• Branch scoping: list endpoints accept an optional branch filter that only the Super Admin can leave open, and every write requires an explicit branch.
• Consistent pattern: each module follows the same list, add and edit page structure, which kept the build predictable.
• Accountability: records show who created them to Admins and Super Admins, and hide that detail from Accountants.
• Built in phases: database schema first, then APIs, then screens, one module at a time, with a review before moving on.
• Ready for messaging: a notification service logs queued WhatsApp, SMS and in-app alerts, so a delivery provider can be added without changing the modules that raise alerts.

Results and impact

The system is live and in daily use. The bracketed figures below are placeholders — real numbers from the client will replace them once confirmed.

• Voucher time cut by [X] minutes, from vehicle entry to printed copy.
• Branches on one platform: [X], each with fully separate data.
• [X]% of credit sales now covered by an enforced customer limit.
• Payroll that took [X] hours each month now runs in bulk and posts to expenses automatically.
• Owners can see outstanding balances and branch expenses in one place.

Technology used

PHP, MySQL, PDO, REST API, Bootstrap 5, Bootstrap Icons, jQuery, DataTables, cPanel hosting, Let’s Encrypt SSL.