Documentation
The specification of the current Veloconnect version is available online here.
The documentation refers specifically to the XML schema reference for the XML schemas to be explained.
Note:
It is technically possible to implement Veloconnect independently using the documentation - however, experience shows that this is often time-consuming and error-prone.
We therefore recommend working with experienced integration partners who can ensure a stable and future-proof implementation.
Version information:
In development:
- VC 1.6 - Sales (B2X)
Transmission of detailed sales data to a market data service (e.g., ZIV MDS)
Goal: Industry-wide transparency regarding sales figures and demand trends
- VC 1.7 - Custom Bikes
Structured transmission of configured vehicles, including equipment packages, options, and surcharges
Goal: Uniform presentation of complex product configurations in merchandise management, web shop, and consulting system
Current versions:
- VC 1.6 - Sales (B2B)
Data transmission is voluntary and serves, among other things, to improve market demand analysis and availability planning.
Sales data transmission by dealers, consisting of- Item number
- Sales quantity
- Sales date
- Optional: Price, postal code, sales channel, frame number for bicycles
- VC 1.5 - Catalog
Structured product data with extended item information such as attributes and variant structures
Provision directly or via service providers (e.g., Bidex, DST, e-vendo)
- VC 1.4 - Stock (B2B, B2C)
Transmission of current stocks of individual retailers to manufacturers, marketplaces, or web shops
Enables, for example, a “Available near you” display on the manufacturer's website
- VC 1.3 - Receipts
Digital transmission of- Order confirmations
- Delivery notes
- Invoices including serial numbers
- VC 1.1 - Core
Basic B2B functions- Master data (description, GTIN/EAN, order number, prices)
- Availability query
- Orders (with immediate price and quantity comparison)
