What the client came with
The store ran everything in one Google spreadsheet: 21 sheets, 16 macros and tens of thousands of rows of history. The file no longer opened properly, and the numbers in it did not add up.
What we built
- Moving the whole history from the spreadsheet into a database
- ERP with orders, catalog and suppliers
- Financial accounting: payments, balance payments, debts
- Sales analytics
- A 103-step guided tour of the system
What’s inside the panel
- Orders with stages and assignees
- Catalog: models, fabrics, variants, prices
- Suppliers and purchasing
- Money: payments, outstanding debt, reconciliation
- Reports and exports
Details worth knowing
During the migration we found an error in the spreadsheet itself: the system showed an overpayment on 1567 orders, when in fact there were 137. The old spreadsheet was simply counting wrong.
Stack
- Laravel
- Filament
- MySQL
- Import from Google Sheets
Numbers verified against the project
How it looks
More from this niche
We’ll build a system like this around your process
Come without a spec — we’ll write it together on the first call.