How crimac90/inventra works
INVENTRA is a SaaS inventory and sales-management application for liquor stores. The implemented user workflow in the supplied source centers on registration and account access, session-protected pages, subscription-status checks, and user/profile management through a React client and Django REST API. The README also describes inventory by PEPS lots, point-of-sale, branches, reports, and electronic invoicing; these are product capabilities, but the supplied tree does not show their implementation. The map distinguishes those documented capabilities from the sampled security and subscription runtime.
Main entry points: cliente.js API client · seguridad.js Security API · BarraLateral.jsx Module navigation · views.py Access handlers
Components 23
Web client
- Route map
INVENTRA/frontend/src/App.jsx - Session context
INVENTRA/frontend/src/sesion/ContextoSesion.jsx - Private routes
INVENTRA/frontend/src/sesion/RutaPrivada.jsx - API client
INVENTRA/frontend/src/api/cliente.js - Security API
INVENTRA/frontend/src/api/seguridad.js - Subscription API
INVENTRA/frontend/src/api/suscripciones.js - User management
INVENTRA/frontend/src/paginas/Usuarios.jsx - User profile
INVENTRA/frontend/src/paginas/Perfil.jsx - Workspace layout
INVENTRA/frontend/src/componentes/Disposicion.jsx - Module navigation
INVENTRA/frontend/src/componentes/BarraLateral.jsx
Security and access
- Access handlers
INVENTRA/backend/seguridad/views.py - Access serializers
INVENTRA/backend/seguridad/serializers.py - Verification email
INVENTRA/backend/seguridad/correo.py - Account and roles
INVENTRA/backend/seguridad/models.py
Subscriptions
- Subscription handlers
INVENTRA/backend/suscripciones/views.py - Subscription serializers
INVENTRA/backend/suscripciones/serializers.py - Plan modules
INVENTRA/backend/suscripciones/modulos.py - Plans and tenants
INVENTRA/backend/suscripciones/models.py
Persistence
- MySQL database
Other components
- Store user
- Inventory and sales
INVENTRA/backend - Branches and users
INVENTRA/backend - Reports and e-invoice
INVENTRA/backend
Connections 23
- Store user → Route map: uses
INVENTRA/frontend/src/App.jsx - Route map → Private routes: guards pages
INVENTRA/frontend/src/App.jsx - Session context → Security API: authenticates
INVENTRA/frontend/src/sesion/ContextoSesion.jsx - Session context → API client: checks token
INVENTRA/frontend/src/sesion/ContextoSesion.jsx - User management → Security API: manages users
INVENTRA/frontend/src/paginas/Usuarios.jsx - User profile → Security API: updates profile
INVENTRA/frontend/src/paginas/Perfil.jsx - Workspace layout → Module navigation: renders
INVENTRA/frontend/src/componentes/Disposicion.jsx - Module navigation → Subscription API: checks modules
INVENTRA/frontend/src/componentes/BarraLateral.jsx - Security API → API client: sends requests
INVENTRA/frontend/src/api/seguridad.js - Subscription API → API client: sends requests
INVENTRA/frontend/src/api/suscripciones.js - API client → Access handlers: calls API
- Access handlers → Access serializers: uses
INVENTRA/backend/seguridad/views.py - Access handlers → Account and roles: uses
INVENTRA/backend/seguridad/views.py - Access serializers → Verification email: sends messages
INVENTRA/backend/seguridad/serializers.py - Subscription handlers → Subscription serializers: uses
- Subscription handlers → Plans and tenants: uses
- Plans and tenants → Account and roles: associates tenant users
- Module navigation → Plan modules: shows availability
- Account and roles → MySQL database: persists accounts
- Plans and tenants → MySQL database: persists plans
- Store user → Inventory and sales: manages stock and sales
- Store user → Branches and users: manages locations
- Store user → Reports and e-invoice: uses reports and invoicing