How aliozertekin/flask_inventory_system works
Project type and purpose
• This is a full-stack web application for Inventory, Order & Shipment Management.
• Backend: Flask (Python 3.13+), connects to Oracle Database (21c+) via cx_Oracle.
• Frontend: HTML/CSS/JavaScript templates served by Flask.
• Additional component: Serial-port integration for real-time inventory updates (PySerial).
File structure
• app.py: Flask app entry point, initializes routes and database connection.
• db/connection.py: Oracle connection setup.
• db/sql/: PL/SQL scripts for schema creation, installation, population, methods, triggers, views, packages.
• routes/: Flask view-functions grouped by feature (auth, customers, inventory, orders, shipments, etc.).
• modules/utilities.py: Shared helper functions.
• serial/: Scripts for machine simulation (simulate_machine.py) and serial receiver (receiver.py).
• static/: CSS (style.css), JavaScript (search.js), fonts.
• templates/: Jinja2 HTML pages for each view.
• images/: Screenshots for README.
Key architectural insights from README
• MVC pattern:
• Models & procedures in Oracle (tables, views, stored procedures, triggers).
• Controllers in Flask routes/.
• Views in templates/ + static assets.
• Real-time inventory updates via a long-running serial port listener that calls a PL/SQL procedure.
• Audit logging via database triggers.
• Client (browser) ↔ Flask ↔ Oracle interactions.
• Optional component: machine simulator to test serial feed.
Main components
a. Client web browser (UI layer)
• Requests HTML/JSON pages via HTTP(S).
b. Flask Application Server
• app.py and routes/*.
• Business logic, session/auth handling, input validation.
• Utilities module for shared code.
c. Oracle Database
• Core tables: PRODUCTS, STORES, CUSTOMERS, ORDERS, ORDER_ITEMS, SHIPMENTS, INVENTORY.
• Logging tables (e.g., ORDER_LOG, INVENTORY_LOG, AUDIT_LOG).
• Views (e.g., INVENTORY_VIEW, ORDERS_VIEW).
• Stored procedures & packages (ADD_INVENTORY, ADD_ORDER, etc.).
• Triggers for auditing and restock logic.
d. Serial Integration Service
• receiver.py: Listens on serial port, processes incoming data, calls ADD_INVENTORY.
• simulate_machine.py: Generates fake serial messages for testing.
e. External Clients / Services (optional)
• Barcode scanners or sensors sending data via serial port.
f. Static Assets CDN (or local folder)
• style.css, search.js, fonts.
Interactions and data flows
• Web flow: Browser → (HTTP) → Flask Routes → (cx_Oracle) → PL/SQL procedures / queries → Oracle DB → back to Flask → Browser.
• Real-time flow: Hardware device → Serial Port → receiver.py → cx_Oracle callproc(ADD_INVENTORY) → Oracle DB → Inventory updated → receiver logs/console.
• Simulator flow: simulate_machine.py → Local serial port emulator → receiver.py → same as real-time flow.
• Audit/logging: DB triggers fire on data changes to write to log tables.
Architectural patterns & design principles
• MVC separation of concerns (Templates, Routes/Controllers, DB Layer).
• Modularization: routes/ for endpoints, modules/ for helpers, db/sql/ for schema & logic.
• Event-driven processing for serial data.
• Use of stored procedures/packages to encapsulate business logic in DB.
• Triggers for cross-cutting concerns (audit, restock).