Overview & architecture
Components, data flow and operating model of VeloStack.
VeloStack is an open-source PIM and middleware for item master data and orders in bicycle retail. Production runs on PostgreSQL 15, development on SQLite.
Components
| Component | Responsibility |
|---|---|
| FastAPI app | VeloConnect, REST, MCP, web UI |
| Importer | VeloConnect proxy, CSV/Excel, BIDEX |
| Grouping | Build models and variants |
| Mapping | Supplier → BIDEX → product group |
| Dispatcher | Send orders with audit trail |
| MCP/REST | AI and API access |
Data flow
- Supplier delivers items via VeloConnect, CSV or Excel.
- Importer normalises and validates the data.
- Grouping builds models and size/colour variants.
- Mapping sets BIDEX codes and the own product group.
- ERP and marketplace read the catalog.
- Orders run through the dispatcher and are audited.
Tenants
Each manufacturer and retailer is its own tenant. Isolation uses a tenant ID in all relevant tables and a SQLAlchemy event hook as a row filter. Roles: admin, manufacturer, retailer; per tenant additionally admin/editor/viewer.
Federation
Multiple VeloStack instances can communicate via VeloConnect 1.6. Manufacturer instances deliver catalogs to retailer instances without sharing the same database.