How aravindhprabu2005/odoo_cafe works
Odoo Café POS is a React client and Express API for café operations. Staff authenticate, open a shift, create and price orders, take payment, and send kitchen tickets; QR customers can browse a menu, place orders, and track status. Admins also manage venue and catalog data, discounts, employees, settings, and reports. The README documents the PostgreSQL/Supabase persistence layer and real-time sync, but the tree has no WebSocket implementation; the latter is therefore not mapped. Some route modules were not sampled, so their internal calls are not inferred.
Main entry points: db.js PostgreSQL store · axiosInstance.js HTTP client · App.js Application routes · orders.routes.js Order lifecycle
Components 22
React client
- Application routes
client/src/App.js - Sign-in state
client/src/context/AuthContext.js - POS workspace
client/src/pages/PosDashboard.js - Order creation
client/src/pages/CreateOrder.js - QR ordering
client/src/pages/SelfOrderCustomer.js - Reports view
client/src/pages/Reports.js - HTTP client
client/src/axiosInstance.js
POS operations
- Shift sessions
backend/src/routes/sessions.routes.js - Order lifecycle
backend/src/routes/orders.routes.js - Order items
backend/src/routes/orderLines.routes.js - Payments
backend/src/routes/payments.routes.js - Kitchen tickets
backend/src/routes/kds.routes.js - Self-order service
backend/src/routes/selfOrdering.routes.js
Management
- Catalog and venue
backend/src/routes/products.routes.js - Coupons and promos
backend/src/routes/promotions.routes.js - Reporting exports
backend/src/routes/reports.routes.js
API service
- Authentication
backend/src/routes/auth.routes.js
Persistence
- Domain schema
backend/src/db/schema/index.js - PostgreSQL store
backend/db.js
Other components
- Staff
- QR guest
- PostgreSQL / Supabase
Connections 28
- Staff → Application routes: uses
client/src/App.js - QR guest → Application routes: opens QR route
client/src/App.js - Application routes → Sign-in state: provides auth
client/src/App.js - Application routes → POS workspace: routes to POS
client/src/App.js - Application routes → Order creation: routes to ordering
client/src/App.js - Application routes → QR ordering: routes to QR order
client/src/App.js - Application routes → Reports view: routes to reports
client/src/App.js - Sign-in state → HTTP client: requests auth
client/src/context/AuthContext.js - POS workspace → HTTP client: requests POS data
client/src/pages/PosDashboard.js - Order creation → HTTP client: requests order data
client/src/pages/CreateOrder.js - QR ordering → HTTP client: requests menu and status
client/src/pages/SelfOrderCustomer.js - Reports view → HTTP client: requests reports
- HTTP client → Authentication: calls API
README.md - HTTP client → Order lifecycle: calls API
README.md - HTTP client → Self-order service: calls API
README.md - HTTP client → Reporting exports: calls API
README.md - Order lifecycle → PostgreSQL store: reads and writes
backend/src/routes/orders.routes.js - Order lifecycle → Coupons and promos: applies promotions
- Self-order service → PostgreSQL store: reads and writes
backend/src/routes/selfOrdering.routes.js - Reporting exports → PostgreSQL store: queries sales data
backend/src/routes/reports.routes.js - Shift sessions → PostgreSQL store: reads and writes
- Order items → PostgreSQL store: reads and writes
- Payments → PostgreSQL store: reads and writes
- Kitchen tickets → PostgreSQL store: reads and writes
- Catalog and venue → PostgreSQL store: reads and writes
- Coupons and promos → PostgreSQL store: reads and writes
- PostgreSQL store → Domain schema: uses definitions
backend/db.js - PostgreSQL store → PostgreSQL / Supabase: persists data
README.md