VeloConnect & BIDEX
Versions, operations and the BIDEX data model.
VeloConnect is an XML-over-HTTP protocol between suppliers and ERP systems. VeloStack implements both server and client for versions 1.1 to 1.6.
Versions
| Version | Content | Status |
|---|---|---|
| 1.0 | Transaction, GetStatus, Rollback | partial |
| 1.1 | TextSearch, GetItemDetails, Order, Profile | active |
| 1.3 | Offer, DeliveryNote, Invoice | active |
| 1.4 | Stock transmit B2B/B2C | active |
| 1.5 | BIDEX catalog by URL | active |
| 1.6 | Sale transmit, federation | active |
Transport and auth
XML POST is preferred, GET is the fallback. Every request contains BuyersID, Credential, SellersID, TransactionID and IsTest. Status codes: 200 success, 411 auth failed, 415 unknown SellersID.
Operations
| Operation | Purpose | Since |
|---|---|---|
| TextSearch | Item search | 1.1 |
| GetItemDetails | Single item | 1.1 |
| GetItemDetailsList | Batch query | 1.1 |
| GetClassificationScheme | Product groups/BIDEX | 1.1 |
| CreateOrder | Order | 1.1 |
| GetProfile | Counterpart profile | 1.1 |
| Offer / DeliveryNote / Invoice | Documents | 1.3 |
BIDEX
BIDEX BikeData V1.6 is the shared language: Catalog → Model → Variant. Uniqueness is Model + Size + Color + Variant. VeloStack treats BIDEX as the source of truth with 77 attribute codes, 386 values and synchronised manufacturers.
Error patterns
| Code | Meaning | Action |
|---|---|---|
| 411 | Authentication failed | Check credentials and tenant |
| 415 | Unknown SellersID | Check the connection's seller ID |
| Empty response | No match or filter too narrow | Check search term and model year |