How pulindu-theekshana/inventix works
InventiX is a mobile inventory and ordering product for grocery businesses, with customer and supplier roles. The main customer workflow is to review stock, choose a supplier, draft a restock message, and submit an order; uploads, delivery tracking, reports, and supplier tools are other documented product areas. Frontend-to-backend writes go through the backend, while display reads may use Supabase directly. Sampled routes establish some service calls; several other links are documented only at a high level, so those are shown as unverified where useful.
Main entry points: customer Customer routes · client.ts HTTP client · useOpenRestock.ts Restock flow · supabase.py Supabase data
Components 23
Mobile app
- Customer screens
frontend/app/(customer) - Supplier screens
frontend/app/(supplier) - Sign-in screens
frontend/app/(auth) - Restock flow
frontend/src/hooks/useOpenRestock.ts - Restock draft
frontend/src/stores/restockDraftStore.ts - HTTP client
frontend/src/api/client.ts - Ordering API
frontend/src/api/ordering.ts - Supplier API
frontend/src/api/suppliers.ts - Auth state
frontend/src/stores/authStore.ts
Backend feeds
- Customer routes
backend/app/feeds/customer - Supplier routes
backend/app/feeds/supplier - Shared routes
backend/app/feeds/shared
Business logic
- Order handling
backend/app/feeds/customer/ordering/service.py - Stock handling
backend/app/feeds/customer/stocks/service.py - Stock uploads
backend/app/feeds/customer/uploads/service.py - Inventory and order rules
backend/app/domain - Forecasting and ranking
backend/app/ml
Data and jobs
- Scheduled jobs
backend/app/jobs - Auth and role checks
backend/app/dependencies.py - Supabase data
backend/app/core/supabase.py - Messaging integrations
backend/app/integrations
Other components
- Customer
- Supplier
Connections 26
- Customer → Customer screens: uses
README.md - Supplier → Supplier screens: uses
README.md - Customer screens → Restock flow: opens restock
frontend/app/(customer)/stocks/index.tsx - Restock flow → Supplier API: searches suppliers
frontend/src/hooks/useOpenRestock.ts - Restock flow → Ordering API: generates message
frontend/src/hooks/useOpenRestock.ts - Restock flow → Restock draft: saves draft
frontend/src/hooks/useOpenRestock.ts - Ordering API → HTTP client: sends requests
frontend/src/api/ordering.ts - Supplier API → HTTP client: sends requests
- Customer screens → HTTP client: calls backend
README.md - Supplier screens → HTTP client: calls backend
README.md - Sign-in screens → Auth state: uses session
- HTTP client → Customer routes: HTTP requests
README.md - HTTP client → Supplier routes: HTTP requests
README.md - Customer routes → Stock handling: calls stock service
backend/app/feeds/customer/stocks/routes.py - Customer routes → Stock uploads: calls upload service
backend/app/feeds/customer/uploads/routes.py - Customer routes → Order handling: calls order service
backend/app/feeds/customer/ordering/routes.py - Supplier routes → Supabase data: uses data
- Shared routes → Auth and role checks: requires identity
backend/app/dependencies.py - Customer routes → Auth and role checks: role-gated
backend/app/dependencies.py - Supplier routes → Auth and role checks: role-gated
backend/app/dependencies.py - Order handling → Supabase data: reads and writes
- Stock handling → Supabase data: reads and writes
- Stock uploads → Supabase data: reads and writes
- Scheduled jobs → Forecasting and ranking: recalculates
- Customer routes → Inventory and order rules: uses rules
- Order handling → Messaging integrations: sends messages