OpsLedger

A production and inventory system for a mid-size manufacturer that had outgrown spreadsheets and group chats.

The team had a working (if fragile) process. Replacing it with software that ignored exceptions would have made things worse. The system had to absorb how they already planned batches, handled shortages, and closed the day.

We sat with sales, stores, and the floor supervisor for two weeks. We mapped the real path of an order, including the shortcuts. Then we designed a data model around SKUs, batches, and locations — and a UI that a supervisor could use with gloves nearby.

A centralized operations app for orders, inventory, and floor status — with roles for sales, stores, and production.

• Order intake with live stock checks
• Batch and location-level inventory
• Production status visible to sales without a phone call
• Role-based access for sales, stores, and floor
• End-of-day close that replaces the spreadsheet ritual

• Laravel
• MySQL
• Blade
• Alpine.js

• Replaced weekly spreadsheet reconciliation with a live stock view
• Sales can see production status without interrupting the floor
• Shortages surface at order time instead of at dispatch
• The team kept their language — batches, locations, closes — inside the product

Interface frames — placeholders until production captures replace them.