How fmfizzy/laptoppos works
This is an offline Flask point-of-sale application focused on recording repair jobs and invoicing customers. Staff use its web interface to create and track repairs, prepare invoices, record payments, and review sales; invoices can also be printed as quotations. The sampled routes show the web controller performing database operations and rendering templates. The models define additional quotation data, but the excerpts do not establish its route-level workflow, so that wiring is omitted.
Main entry points: app.py Web workflows · base.html Shared page layout · templates Repair screens · sales.html Sales screen
Components 14
Web interface
- Repair screens
app/templates - Invoice screens
app/templates - Sales screen
app/templates/sales.html - Shared page layout
app/templates/base.html
Repair and billing
- Web workflows
app.py
Business records
- Repair records
app/models.py - Invoice and items
app/models.py - Customer records
app/models.py - Sales entries
app/models.py - Quotation records
app/models.py - Job numbering
app/models.py
Application runtime
- SQLite database
config.py - Flask setup
app/__init__.py
Other components
- Staff user
Connections 15
- Staff user → Web workflows: uses
- Web workflows → Flask setup: creates app
- Flask setup → SQLite database: initializes tables
- Web workflows → Customer records: creates and queries
- Web workflows → Repair records: creates and updates
- Web workflows → Job numbering: allocates numbers
- Web workflows → Invoice and items: creates and updates
- Web workflows → Sales entries: records and queries
- Web workflows → SQLite database: commits records
- Web workflows → Repair screens: renders
- Web workflows → Invoice screens: renders
- Web workflows → Sales screen: renders
- Repair screens → Shared page layout: extends
- Invoice screens → Shared page layout: extends
- Sales screen → Shared page layout: extends