Interlin
Production accounting system for a sewing enterprise
Business systems · automation
How a workshop of 11 seamstresses and 1,200+ item passports stopped keeping records by hand.
Context
Interlin is a sewing enterprise. Part of the production data was recorded on paper and later re-typed into digital form — double work, delays and errors at every step.
Problem
Seamstress output, item passports, production limits and payroll all depended on manual data re-entry. Controlling limits and closing passports was nearly impossible in that scheme.
Solution
- 01
The production plan lives in Google Sheets and syncs into the system — the plan stays familiar while the data becomes live.
- 02
A Flask app with SQLite tracks operations, item passports, limits and history, with separate interfaces for workers and for the administrator.
- 03
Reporting, analytics and payroll export to Excel now come from live data instead of hand-copied tables.
Architecture
Google Sheets
production planSync layer
plan → systemFlask · Python
operations, passports, limitsSQLite
enterprise dataBrowser clients
worker & admin UIFLOW
- 01Plan in Google Sheetssync→ Flask · Python
- 02Flask · Python→ SQLite
- 03SQLite→ Workers · admin
Numbers
users — seamstresses
item passports in the database
Stack
- Python
- Flask
- SQLite
- Google Sheets
- nginx
- Raspberry Pi
- MikroTik
- VPN
- systemd
Outcome
- The classic chain of business analysis → information system → automation, running in a real workshop rather than a classroom project.
- The on-premise infrastructure — Raspberry Pi, MikroTik, VPN, systemd — is deployed and maintained.