Retailers
Pull supplier data cleanly into your ERP. Instead of building a custom export path for every manufacturer, speak VeloConnect + BIDEX once — and map product groups onto the structure you already have.
Open Source (AGPL-3.0) · PIM & Middleware
Your own PIM. Your VeloConnect middleware.
VeloStack is an AGPL-3.0 licensed PIM and middleware for both sides of bicycle specialist retail: for retailers pulling supplier data into their ERP — and for manufacturers and suppliers publishing their own catalog to a standard. One tool, two directions.
Who it's for
Manufacturers · Suppliers
Publish your own catalog to a standard: models with variants, BIDEX product groups, EAN-compliant item IDs. Retailers integrate it directly into their ERP and other systems — no more maintaining a custom format per ERP.
Inside
VeloStack & marketplace
Features
What VeloStack does- 01
VeloConnect 1.1–1.6 + BIDEX
Server and client for VeloConnect 1.1–1.6: TextSearch, GetItemDetails, Order, documents (1.3), stock transmit (1.4) and sale transmit (1.6). BIDEX BikeData V1.6 as export and import format.
// Protocol - 02
Model → Variant
Flat supplier items are aggregated into models with size and colour variants. Local grouping via VariantParentNumber, AI fallback as backup.
// Grouping - 03
Product group mapping
Two-step: supplier classification → BIDEX code (global) → your own product group (per dealer). Every retailer keeps their structure.
// Mapping - 04
Size / colour follow-up
ERP-proprietary requests (GetVariantAttributes, GetItemAttribute) are supported — including VariantParentNumber and EAN-compliant IDs.
// ERP - 05
Dual SKU
Consumer SKUs and B2B order numbers kept in sync. Trade SKUs are resolved to consumer SKUs via prefix match.
// SKU - 06
Self-hosted
FastAPI + PostgreSQL 15 (prod), SQLite (dev), no cloud dependencies. Runs on any Proxmox VM or Docker host. No vendor lock-in.
// Infra - 07
Multi-Tenant + OIDC
Separate instances for manufacturers and retailers with their own identity management. Each tenant gets its own credentials, data and roles.
// Architecture - 08
MCP Server (54 tools)
54 tools for catalog management, mapping, sync, quality assurance and documents. Streamable HTTP, OAuth 2.1 authorization server, usable directly from Claude or any MCP client.
// AI - 09
Order Dispatch (7 channels)
Place orders via VeloConnect, REST, email, CSV, Excel, PDF or noop; transport inline or SFTP. Audit trail with HMAC-SHA256 and verify endpoint.
// Dispatch - 10
BIDEX as source of truth
77 attribute codes and 386 values (incl. RAL colours, frame heights), 1,711 synchronised manufacturers, tenant attribute profiles and automatic BIDEX web service sync.
// Master data - 11
Inventory, documents & ERP
Locations, levels, movements, reservations and push webhooks; PDF delivery notes and invoices; connectors for Shopware, Odoo, REST and IMAP.
// Operations - 12
REST API v1
OpenAPI/Swagger, bearer tokens with read/write scopes, OIDC JWT and automatic tenant scoping for integrations outside VeloConnect.
// API
Source
Access on requestVeloStack is licensed under AGPL-3.0-or-later. The source code currently lives in a private repository; we grant access to retailers, developers and ERP partners on request.
Open source, AGPL-3.0.
Three hundred thousand variants.
One standard.
// VeloStack · In production since 2026
Workflow
In three steps- 01
Connect the supplier
Enter VeloConnect credentials or import a CSV/Excel export. Catalog sync with ModelYear filter.
- 02
Group & map
Local grouping by VariantParentNumber. BIDEX code → product group per dealer.
- 03
Query from the ERP
Your ERP queries articles, inventory and catalogues via VeloConnect 1.1–1.6 — or use the MCP server for AI-powered management.
- 04
Connect Odoo 20
Odoo provides demand from draft purchase orders. VeloStack selects the supplier and dispatch route, writes the confirmed order back and updates supplier prices — via the standard API, without Odoo code.
Odoo is a trademark of Odoo S.A. VeloStack is not an official Odoo product and is not affiliated with Odoo.