FAQ
Questions buyers usually need answered before purchase
This page answers the questions buyers usually ask about samples, documentation, licensing, custom scope and purchasing.
What is the difference between a sample and a full pack?
A sample is a trust and fit check. It should expose structure, naming and general shape, but not replace the full delivery package.
Do packs include documentation?
Yes. Each pack includes a README, validation notes and field guidance that make reuse practical.
Are Datacriterion packs raw public files or processed datasets?
They are processed datasets packaged from official public releases. The value is in normalization, validation, documentation and clearer evaluation paths, not in reselling untouched raw files.
What changes across Basic, Pro and Commercial?
The packaged files stay materially the same for the same product and horizon. What changes is the allowed user count and whether use is solo, internal-team or client-facing.
What changes across annual, five-year and ten-year packs?
Those are product horizons and coverage depth. They change the analytical span and ticket size of the pack, not the license rights.
How current are the packs and where does the data come from?
Each page shows its horizon and pack facts clearly. The live catalog currently uses official Census and Eurostat source systems, with coverage windows defined before packaging instead of being guessed afterward.
Can I use the data in client work or commercial products?
Commercial is the normal route when client-facing derived outputs are involved. Raw files still cannot be redistributed, resold or exposed as a substitute for the pack.
Can I ask for a custom scope or a bundle?
Yes, but custom requests should start only after the closest existing pack, sample or methodology path has been reviewed.
Will checkout live here or in an external store?
The evaluation layer lives here. Purchase can remain on this portal or hand off to an external store, but methodology and licensing stay visible either way.