How poisomn/boskepos works
BoskePOS is a hardware-store ERP/POS: staff sign in, access permission-gated screens, manage catalog and stock, record purchases, and complete sales through the POS. The React client calls a Django REST API; backend business logic owns transactional sales, purchasing, and stock updates. The README also identifies customer/supplier management, dashboard summaries, and business settings. Several backend views and frontend pages are listed but unsampled, so their detailed internals and some links are not asserted.
Main entry points: http.js HTTP client · AppRoutes.jsx App routing · services.py Purchase transactions · ProductsPage.jsx Inventory screens
Components 23
React client
- App routing
frontend/src/routes/AppRoutes.jsx - Authentication state
frontend/src/contexts/AuthContext.jsx - HTTP client
frontend/src/api/http.js - Auth service
frontend/src/services/authService.js - POS screen
frontend/src/pages/POS/POSPage.jsx - Inventory screens
frontend/src/pages/Inventory/ProductsPage.jsx - Dashboard screen
frontend/src/pages/Dashboard/DashboardPage.jsx - Sales screens
frontend/src/pages/Sales/SalesHistoryPage.jsx - Purchase screens
frontend/src/pages/Purchases/PurchasesPage.jsx - Inventory API service
frontend/src/services/inventoryService.js
Sales and purchasing
- Sales API
apps/sales/views.py - Sales transactions
apps/sales/services.py - Purchases API
apps/purchases/views.py - Purchase transactions
apps/purchases/services.py
Inventory
- Stock movement service
apps/inventory/services.py - Catalog and stock records
apps/inventory/models.py
Business records
- Customer management
apps/customers/views.py - Supplier management
apps/suppliers/views.py - Dashboard summaries
apps/dashboard/views.py - Business settings
apps/system_settings/views.py
API and identity
- Accounts API
apps/accounts/views.py
Other components
- Staff user
- PostgreSQL
Connections 32
- Staff user → App routing: uses
- App routing → POS screen: routes to
frontend/src/routes/AppRoutes.jsx - App routing → Inventory screens: routes to
frontend/src/routes/AppRoutes.jsx - App routing → Dashboard screen: routes to
frontend/src/routes/AppRoutes.jsx - App routing → Sales screens: routes to
frontend/src/routes/AppRoutes.jsx - App routing → Purchase screens: routes to
frontend/src/routes/AppRoutes.jsx - Authentication state → Auth service: requests identity
frontend/src/contexts/AuthContext.jsx - Auth service → HTTP client: sends requests
frontend/src/services/authService.js - Inventory screens → Inventory API service: calls
frontend/src/pages/Inventory/ProductsPage.jsx - Inventory API service → HTTP client: sends requests
frontend/src/services/inventoryService.js - POS screen → HTTP client: uses API
- Sales screens → HTTP client: uses API
- Purchase screens → HTTP client: uses API
- Dashboard screen → HTTP client: uses API
- HTTP client → Accounts API: REST requests
- HTTP client → Sales API: REST requests
- HTTP client → Purchases API: REST requests
- HTTP client → Inventory screens: REST requests
- Sales API → Sales transactions: dispatches
- Purchases API → Purchase transactions: dispatches
- Sales transactions → Stock movement service: applies stock movement
apps/sales/services.py - Purchase transactions → Stock movement service: applies stock movement
apps/purchases/services.py - Stock movement service → Catalog and stock records: updates records
apps/inventory/services.py - Sales transactions → Catalog and stock records: reads products
apps/sales/services.py - Purchase transactions → Catalog and stock records: reads products
apps/purchases/services.py - Purchase transactions → Supplier management: uses supplier model
- Inventory API service → Inventory screens: serves catalog calls
frontend/src/pages/Inventory/ProductsPage.jsx - Catalog and stock records → PostgreSQL: persists
- Customer management → PostgreSQL: persists
- Supplier management → PostgreSQL: persists
- Dashboard summaries → PostgreSQL: reads summaries
- Business settings → PostgreSQL: persists