Data quality tiers
We are committed to providing the most accurate data possible across all supported regions. However, data precision depends heavily on each country's infrastructure. To stay transparent, we categorize our data into tiers based on the quality of the available sources and our internal testing.
Our datasets range from countries with official, well-maintained address registries to regions where no central registry exists and precision is harder to guarantee. Because the data varies by region, we provide specific guidelines for each category to help you get the most out of your integration.
| Tier | Countries |
|---|---|
| A (best) | CZ, SK, PL, DE, SI |
| B | AD, AT, CH, DK, HU, IS, IT, LI, LU, NL |
| C | BE, CY, ES, GR, HR, PT, RS, XK |
| D (worst) | AL, BA, BG, IE, ME, MK, MT, RO |
Recommendations
Our recommendations focus on the correct correctionMode setting for each tier and how to react when a location is flagged as invalid.
Tiers with higher quality contain mostly complete lists of locations. Therefore, when an address is flagged as invalid in these tiers, it is highly probable that it does not exist.
On the other hand, in countries where database quality is lower, an invalid result does not automatically mean the address does not exist. The address might actually exist but not appear in our data. In these countries, rural regions are the most prone to having incomplete data. Because of this, we advise handling these cases with more leniency - for example, you probably should not block an order submission if the address is flagged as invalid in a lower tier.
Below are our recommendations for each tier.
| Tier | Recommended correctionMode | Validation strictness |
|---|---|---|
| A | full | Strict: Our best, most complete tier. If result is invalid, location likely does not exist. |
| B | format | Strict: Mostly complete dataset. Formatting fixes are recommended |
| C | suggestion | Moderate: More leniency is advised, as missing data is more common. Automatic fixes should not be used. Suggestions might help users to choose correct variant faster. |
| D | none | Lenient: Use only as an indicator that the location is entered correctly. Evaluating locations as incorrect is discouraged as missing data is common, especially in rural areas. |
Tier A
This tier offers the best data quality. You can evaluate the validity strictly (e.g., mark inputs as incorrect or show error messages) as the data is mostly complete and up-to-date. Our API is capable of fixing most common mistakes automatically.
Tier B
Quality is slightly lower than Tier A, but the data is still mostly complete. You should still be able to evaluate locations strictly. Only formatting corrections are suggested to provide the most relevant results.
Tier C
Quality is significantly lower than Tier A. We suggest only indicating whether the filled-out address is correct. You should be more lenient with validity checking as missing locations occur more easily.
Tier D
This represents our lowest data tier, with a significant drop in coverage - particularly in rural areas. High leniency is strongly advised. Validity checking should only be used to indicate whether an address is completely correct. Even if flagged as invalid, there is still a good probability that the address exists.