How febryannnn/nexwave-backend works
NexWave is a warehouse order batching and picker-routing system. WMS orders enter the API and are grouped into waves by a PPO batching service; waves are routed and assigned to pickers, who retrieve routes and report picking progress through the API. Managers also view active waves and shift summaries. The excerpts document key service interactions, but do not expose every API handler or the full model-loading and scheduled-cycle implementation, so uncertain wiring is omitted.
Main entry points: modal_app.py API and Scheduler · batching_service.py Wave Batching · schema.sql Warehouse Database · dispatcher.py Wave Assignment
Components 12
Order Batching
- Wave Batching
api/services/batching_service.py - PPO Model
models/ppo_batching_v10.zip
Routing Assignment
- Route Selection
api/ml/routing.py - Warehouse Navigation
api/ml/nav.py - Wave Assignment
api/services/dispatcher.py - Layout Data
dataset
Picker Operations
- API and Scheduler
modal_app.py
Data and Identity
- Warehouse Database
schema.sql - Supabase Auth
Other components
- WMS
- Manager
- Picker
Connections 17
- WMS → API and Scheduler: submits orders
- Manager → API and Scheduler: requests dashboard
- Picker → API and Scheduler: requests route
- Picker → API and Scheduler: reports picks
- API and Scheduler → Wave Batching: batches orders
- API and Scheduler → Wave Batching: processes due orders
- Wave Batching → PPO Model: chooses actions
- Wave Batching → Warehouse Navigation: measures distances
- Wave Batching → Warehouse Database: updates wave records
- API and Scheduler → Wave Assignment: assigns waves
- Wave Assignment → Route Selection: selects route
- Route Selection → Warehouse Navigation: compares routes
- Wave Assignment → Warehouse Database: reads and assigns
- Warehouse Navigation → Layout Data: loads layout
- API and Scheduler → Warehouse Database: reads and updates
- Warehouse Database → API and Scheduler: returns records
- API and Scheduler → Supabase Auth: verifies tokens