gopal092003/inventory-order-management

Purpose and Runtime Entry Points

This is a full-stack inventory and order-management system: product and customer CRUD, multi-line-item orders, stock control, and operational dashboard metrics. The React/Vite SPA starts at frontend/src/main.jsx, composes routes in frontend/src/routes/AppRoutes.jsx, and is hosted in frontend/src/App.jsx. The FastAPI application is created in backend/app/main.py; Uvicorn serves it and exposes OpenAPI/Swagger.

Frontend Application Shell and Navigation

The browser client is organized around a dashboard layout, shared navigation, and feature pages rather than a server-rendered web app. frontend/src/layouts/DashboardLayout.jsx establishes the primary page frame; frontend/src/components/layout/Sidebar.jsx and frontend/src/components/layout/Navbar.jsx provide navigation. Routed feature screens represent the main user workflows: frontend/src/features/dashboard/Dashboard.jsx, frontend/src/features/products/Products.jsx, and frontend/src/features/orders/Orders.jsx.

Frontend API Boundary

Feature-local API modules call a centralized HTTP client, isolating backend URL/configuration and request behavior from UI components. frontend/src/api/client.js is the client boundary, with domain callers in frontend/src/features/products/api.js, frontend/src/features/customers/api.js, and frontend/src/features/orders/api.js. The frontend obtains its API base URL through VITE_API_BASE_URL; it does not directly access PostgreSQL.

FastAPI API and Layering

The backend follows route → service → persistence boundaries. Versioned REST endpoints are partitioned by business resource in backend/app/api/v1/products.py, backend/app/api/v1/customers.py, and backend/app/api/v1/orders.py; dashboard aggregation is exposed through backend/app/api/v1/dashboard.py. Application wiring, CORS, and exception integration belong in backend/app/main.py, while configuration and database-session setup are centralized in backend/app/core/config.py and backend/app/core/database.py.

Domain Model and Validation

SQLAlchemy entities persist the core relational model: customers, products, orders, and order line items in backend/app/models/customer.py, backend/app/models/product.py, and backend/app/models/order_item.py. Pydantic request/response contracts separate API payloads from ORM entities in backend/app/schemas/product.py, backend/app/schemas/customer.py, and backend/app/schemas/order.py. Orders form the principal transactional boundary: submitted line items must be inventory-valid and result in stock deduction.

Inventory and Analytics Services

Business logic that crosses resource boundaries is kept out of route handlers. backend/app/services/inventory_service.py governs inventory checks and updates used during ordering. backend/app/services/dashboard_service.py computes inventory, product, customer, and order summaries, including low-stock and recent-order data. Its output is consumed by the dashboard endpoint and rendered via frontend/src/features/dashboard/Dashboard.jsx.

Persistence, Delivery, and External Infrastructure

PostgreSQL is the system of record, configured through DATABASE_URL. Alembic manages schema evolution from backend/alembic/env.py and backend/alembic/versions/initial_migration.py; backend/app/db/seed.py supports initial data population. Local container orchestration is defined by docker-compose.yml, with independently containerized backend and frontend in backend/Dockerfile and frontend/Dockerfile. Target deployment boundaries are Vercel for the SPA, Render for FastAPI, and Render PostgreSQL; CI is executed by .github/workflows/ci.yml.