It is designed for vehicle importers and distributors who want to organise and centralise their product range and make it available, in a structured and up-to-date way, to the dealer network, internal systems and the brand's digital channels, including configurators.

CarData is built on a hierarchy of brand, model, generation, trim level and commercial version. Each commercial version can be linked to standard equipment, options, packs, prices, technical specifications and colour combinations.

Yes. CarData was designed for multi-brand environments, allowing a single importer group to manage several brands on the same platform, with appropriate separation of ranges and users.

No. CarData does not impose predefined limits on the number of brands, users or markets, so it can grow with each client's operation.

During implementation, the existing catalogue is typically loaded into CarData in a structured way by NiW's teams, working closely with the importer to ensure consistent information from day one.

Yes, whenever the manufacturer provides suitable interfaces or APIs. In those cases, range information such as specifications, equipment and list prices can be imported automatically into CarData, reducing manual configuration effort.

CarData supports integrated management of retail prices, dealer prices and option and pack prices per commercial version. All information is recorded, so price history can be consulted over time.

Yes. CarData supports the management of CO₂, WLTP and energy label information and integrates with the tyre database through the EPREL code, helping keep the environmental information communicated to the market consistent.

CarData manages model years, the start and end of sale dates for each version and the changeover between generations. This information is preserved over time, keeping the range and the channels that depend on it historically consistent.

CarData is the catalogue base that feeds the other applications in the NiW ecosystem, including DHVS, SFA, Accessories, Campaigns and the configurator, through services exposed for integration. Any change to the range is propagated consistently wherever the information is used.

Implementation is led by NiW's teams together with the importer and typically includes the initial catalogue load, configuration of the range structure, setting up integrations with manufacturer systems (where applicable) and supporting user adoption. Scope and timeline are adapted to each client.