Frequently asked questions about Tiedot

Tiedot is a system built for car dealerships. It brings vehicle data and the dealership's core workflows together in one environment.

It covers purchasing, vehicle appraisal, pricing, stock management, sales preparation and document handling. The larger plans add invoicing, the ledger and finance tasks.

The data gathered on a vehicle carries over from one step to the next, so nobody has to look it up again or re-enter it in several services. The features and data you get depend on the plan you choose and on what is available for that vehicle.

Tiedot is designed for dealerships and other motor trade organisations that handle vehicles as part of their daily business.

It suits a single-location dealership as well as a multi-location dealer group. Typical uses include purchasing, vehicle appraisal, pricing, stock management and sales preparation.

The features you use and the scope of the system depend on your dealership's needs and the plan you choose.

While vehicle data is an important part of Tiedot, Tiedot is a broader system for car dealerships.

Beyond checking a vehicle's data, you can use Tiedot for purchasing, appraisal, pricing, stock management, sales preparation and document handling. The larger plans add invoicing, the ledger and finance tasks.

Vehicle data is not left as a one-off check. It is put to work across the dealership's workflows.

Yes. Tiedot can be the shared environment for the whole dealership, with vehicle data and the core workflows in one system.

The scope of the implementation is set by your dealership's needs and the plan you choose. Tiedot supports purchasing, appraisal, pricing, stock management, sales preparation and documents. The larger plans add invoicing and the ledger.

Tiedot can also be implemented as part of the systems your business already runs.

Tiedot was built to make a dealership's daily work easier and to cut the need to look up the same data in several different places.

Data on the same vehicle is needed again and again, from purchase and appraisal through pricing and stock management to the sale. When it has to be fetched from different services and re-entered at every step, you waste time and the full picture gets harder to see.

Tiedot brings vehicle data and the dealership's workflows into one environment, so the essential data is available where it is needed.

Above all, Tiedot puts the essential vehicle data and the dealership's core workflows in one environment.

The data gathered on a vehicle supports purchasing, appraisal, pricing, stock management and sales preparation.

The data carries over from one step to the next, so you never have to rebuild the picture from separate services at every stage.

Tiedot cuts the need to look up and re-enter the same vehicle data at each stage of the dealership's work.

When vehicle data, equipment, history, pricing, stock management and documents all sit in one environment, you switch between services less often and no longer have to gather the same data twice.

That helps most when a vehicle is being appraised, priced, added to stock or prepared for sale.

Vehicle data shapes many of a dealership's decisions. The exact model structure, equipment, service history, vehicle history and market data can all affect how you appraise and price a car, and what is worth checking before you buy it.

Tiedot brings the available vehicle data into the dealership's workflows. The point is not a one-off lookup: the same data is there when you appraise the car, price it, add it to stock and prepare it for sale.

Tiedot gathers the available vehicle data into one environment, where it is used across the dealership's workflows.

Those workflows include appraisal, purchasing, pricing, stock management and sales preparation. The data available depends on the vehicle and on the plan you choose.

When you buy and price a car, you need to know as precisely as possible what the car is and how it compares with similar cars.

Model structure, equipment, service history, vehicle history and market data can all add essential detail to an appraisal. When that data sits in one environment, you can appraise the car as a whole without gathering it from several different services.

When vehicle data comes from several different services, you have to switch between systems and piece the full picture together yourself.

Tiedot brings the available vehicle data into one environment and makes it usable at every stage of the dealership's work. The data you looked at when buying the car then supports pricing, stock management and sales preparation too.

Yes. Tiedot also suits dealer groups and other multi-location organisations. Vehicles from different locations can be viewed and handled in a shared Tiedot environment.

Organisation administrators manage users and permissions, so each location uses the system the way your organisation needs. The scope of the implementation is set by the plan you choose and by your organisation's needs.

Yes. Locations within the same organisation can share one Tiedot environment. The stock at every location, for instance, can be viewed and handled in the same system.

Organisation administrators create users, such as the salespeople at each location, and set their permissions. Everyone then works in Tiedot day to day within one shared environment.

The scope of a Tiedot implementation is planned around your organisation's needs and the plan you choose. That planning can cover locations, users and permissions, the dealership workflows you need and any system integrations.

On the Tiedot Enterprise plan, we define the content and scope of the implementation with you.

Yes. Tiedot can be connected to your dealership's existing systems by arrangement. How the API and system integrations are built, and how far they go, depends on the systems in use and on your needs.

Tiedot's data can also be delivered into your own systems. The data included and the way it is delivered are agreed to fit your needs.

Planning an integration starts with a review of your current systems, needs and goals. From there, we define the system connections needed and the scope of the work.

We plan the work with you. The technical approach depends on the systems in use and on how Tiedot, or Tiedot's data, is meant to fit into the overall set-up.

Implementation starts with a review of your dealership's needs and current workflows. That is also where we decide which plan fits your business and which Tiedot features you need.

The scope of the implementation depends on the plan you choose and on your organisation's needs. Tiedot can be implemented for a narrower purpose or as a broader shared environment for the whole dealership.

We agree the details of the implementation with you.

Yes. Tiedot comes in plans of varying scope to suit different needs in the motor trade: Tiedot Lite, Tiedot Connect, Tiedot Pro and Tiedot Enterprise.

The right plan depends on what you want to use Tiedot for and how broad an environment your organisation needs. The focus can be on vehicle data, purchasing and appraisal, or more widely on the dealership's day-to-day workflows.

Tiedot Enterprise is designed for organisations with several locations and many users.

Tiedot's plans are designed for different needs in the motor trade.

Tiedot Lite is for checking vehicle data.

Tiedot Connect delivers Tiedot's vehicle data into the dealership's own systems.

Tiedot Pro is for broader day-to-day use across the dealership: purchasing, pricing, stock management, sales, invoicing and the ledger.

Tiedot Enterprise is for organisations with multiple locations and users that need a shared Tiedot environment, user management and, where required, system integrations.

The right plan always comes down to how your business will use Tiedot.

Tiedot is built for professional use in the motor trade, and access is controlled through user accounts and permissions. Organisation administrators manage users and their permissions to suit the organisation's needs.

Data security is considered throughout: in the Tiedot service itself, in how the system is used and in any integrations.