No invented facts
Do not substitute a title guess for a verified VIN, accident history, owner count or exact engine size.
Data quality & definitions
Know what a field
really means.
Good data decisions start with provenance, missing values and the difference between what a seller says and what a collector observes.
Buyer’s field guide
Provenance before assumptions.
| Data group | Look for | How to interpret it |
|---|---|---|
| Listing identity | Source name + source listing ID | A marketplace identifier describes an advert. It is not a universal vehicle identity. |
| Original URL | Source advert link, when available | An original advert may later expire or change. Do not infer that a missing link proves a sale. |
| Price & currency | Recorded asking price and its currency | Keep PLN, CHF, GBP and EUR distinct. Any converted amount needs its exchange-rate context. |
| Vehicle details | Make, model, year, mileage, fuel, power | Fields depend on source and enrichment. Missing or unparsed values must stay unknown. |
| Images | Available image URLs | Links can expire or change at the source. Image availability is not guaranteed. |
| Observation times | First seen, last checked, enrichment time | These are different events. First observed is not necessarily newly published. |
| Listing status | Observed active / removed / unavailable | A blocked or failed check must not be treated as a confirmed sale. |
| History | Retained price or status observations | Historical depth and the meaning of timestamps differ between sources. |
Plan for uncertainty
Build with missing values in mind.
Duplicates need context
One vehicle may appear on several sources or in a relisted advert. Ask about cross-source deduplication before counting unique vehicles.
Freshness is source-specific
Discovery, enrichment and availability checks are separate processes. Agree the freshness evidence your workflow needs.
A better sample request
Ask for evidence that fits your use case.
Tell us the source, country, category and required fields. Request a recent representative sample, field completeness, relevant observation timestamps and the proposed export cut or API route.
Validate the sample in your own workflow before committing to production. Access and permitted use should be agreed for your intended application.
Request a source-specific sample ↗Frequently asked questions
Data integrity & verification standards.
How is inventory deduplicated across multiple marketplaces?
We deduplicate listings using 17-character NHTSA VINs in the US, VRM registrations in the UK, and cryptographic hashes of composite attributes across European portals.
How frequently are delisted records updated?
Our daemon processes cycle through known active URLs every 24 to 48 hours to record removals and status transitions.
Are missing optional fields filled with estimates?
Never. We enforce strict data integrity: if a seller or portal does not provide an attribute, the column remains explicit NULL.