Help Center

Country Coverage

Availability: Coverage changes as new destinations and duty programs are added. Confirm the destinations you care about with your Altana team before you build a workflow around them.

Objective and outcome

A workspace is scoped to a single import destination, and what each lens can return depends on that destination. This page sets out what HS Classification and Duties support today, and where the coverage stops, so you know what to expect before you create a workspace rather than after.

The short version: classification and base duty coverage is broad, preference programs under trade agreements are not, and Section 232 is US only.

HS Classification

Classification is destination-scoped. Altana supports 152 import destinations, and classifies to each destination's own national tariff line rather than to a common depth. National line length varies by country, so a code returned for one destination will not be the same length as a code returned for another.

A product can be classified for more than one import destination, and each destination gets its own classification held separately on the product.

Supported import destinations

Several entries are territories or dependencies rather than sovereign states, which is why these are import destinations rather than countries.

  • Afghanistan
  • Albania
  • Algeria
  • Andorra
  • Angola
  • Anguilla
  • Antigua and Barbuda
  • Argentina
  • Armenia
  • Aruba
  • Australia
  • Austria
  • Bahamas
  • Bahrain
  • Bangladesh
  • Barbados
  • Belarus
  • Belgium
  • Bermuda
  • Bhutan
  • Bolivia
  • Bosnia and Herzegovina
  • Botswana
  • Brazil
  • Brunei
  • Bulgaria
  • Burundi
  • Cambodia
  • Canada
  • Cayman Islands
  • Chile
  • China
  • Colombia
  • Costa Rica
  • Croatia
  • Cuba
  • Cyprus
  • Czech Republic
  • Denmark
  • Dominica
  • Ecuador
  • Egypt
  • El Salvador
  • Estonia
  • Eswatini
  • Fiji
  • Finland
  • France
  • French Guiana
  • Germany
  • Gibraltar
  • Greece
  • Grenada
  • Guadeloupe
  • Guatemala
  • Guernsey
  • Guyana
  • Haiti
  • Honduras
  • Hong Kong
  • Hungary
  • Iceland
  • India
  • Indonesia
  • Ireland
  • Israel
  • Italy
  • Jamaica
  • Japan
  • Jersey
  • Jordan
  • Kazakhstan
  • Kenya
  • Kuwait
  • Kyrgyzstan
  • Latvia
  • Lebanon
  • Lesotho
  • Libya
  • Lithuania
  • Luxembourg
  • Madagascar
  • Malawi
  • Malaysia
  • Maldives
  • Malta
  • Martinique
  • Mauritius
  • Mayotte
  • Mexico
  • Moldova
  • Monaco
  • Montenegro
  • Montserrat
  • Morocco
  • Namibia
  • Nepal
  • Netherlands
  • New Zealand
  • Nicaragua
  • Nigeria
  • North Macedonia
  • Norway
  • Oman
  • Pakistan
  • Palau
  • Panama
  • Papua New Guinea
  • Paraguay
  • Peru
  • Philippines
  • Poland
  • Portugal
  • Puerto Rico
  • Qatar
  • Réunion
  • Romania
  • Russia
  • Rwanda
  • Saint Kitts and Nevis
  • Saint Lucia
  • Saudi Arabia
  • Serbia
  • Seychelles
  • Singapore
  • Slovakia
  • Slovenia
  • South Africa
  • South Korea
  • Spain
  • Sri Lanka
  • Suriname
  • Sweden
  • Switzerland
  • Taiwan
  • Tanzania
  • Thailand
  • Trinidad and Tobago
  • Tunisia
  • Turkey
  • Uganda
  • Ukraine
  • United Arab Emirates
  • United Kingdom
  • United States
  • Uruguay
  • Uzbekistan
  • Vanuatu
  • Venezuela
  • Vietnam
  • Zambia
  • Zimbabwe
Destinations outside the supported set. Classifying for a destination Altana does not support does not fail. It returns a 6-digit international code instead of a national tariff line. A returned code is therefore not by itself confirmation that the national line was resolved. Check the depth of the code you get back against what your filing requires.

Duties

The workspace's import destination carries through to the duty calculation, and Altana supports 122 import destinations for duty. How a rate is built depends on the destination.

DestinationHow the rate is calculated
United States, European Union, United Kingdom, China, Canada, Mexico A dedicated calculation for that jurisdiction, covering the programs specific to it. This is the deepest coverage Altana offers, and it is what the US duty stacking of base rate, Section 301, Section 232, IEEPA, and reciprocal tariffs runs on.
All other supported destinations A general calculation: the base rate, with antidumping, countervailing, and safeguard duties stacked additively on top, plus flags where a quota, prohibition, or import control applies to the code.

Base and most-favoured-nation duty is the part to rely on. It is well covered across the supported destinations, so classification plus landed base duty into a new market is a reasonable thing to build on today.

Preference programs under trade agreements

This is the significant gap, and it is worth understanding before you scope a project around duty savings.

Preference program coverage varies by destination and is uneven. Some destinations carry a substantial set of programs, while others carry very few or none. Notably, the ASEAN trade agreements are not covered for any destination, including ATIGA, RCEP, and the ASEAN+1 agreements. Where a preference program is not carried, a qualification claim against it returns an empty result rather than a rate.

An empty preference result means Altana holds no program data for that agreement and destination. It does not mean your product fails to qualify. Treat it as a coverage gap to raise with your Altana team, not as a determination.

What is United States only

  • Section 232. The material-level steel, aluminum, and copper measures, and the whole-good measures on timber and wood, apply to US imports. Section 232 is not evaluated for other destinations.
  • Non-preferential rules of origin as applied by the Country of Origin lens follow US rules. Origin determination for other destinations is in development.

Because Section 232 does not apply outside the US, it is not part of what a non-US workspace is working toward.

How to check a destination before you commit

  1. Create a small workspace for the destination with a handful of representative products rather than your full catalog.
  2. Run classification and check the code depth. If you get 6-digit codes back where you expected a national line, that destination is outside the supported set.
  3. Check the duty result for whether the programs you care about appear, and whether any preference program you intend to claim returns a rate or an empty result.
  4. Raise the gaps with your Altana team before scaling the workspace up. A missing preference program is a data scoping question, not a setting to switch on.

FAQ

Can one workspace cover several import destinations? No. A workspace is scoped to a single destination. Create a workspace per destination you import into.

Why is the HS code shorter for one destination than another? Because Altana classifies to each destination's own national tariff line, and national line length differs by country. A shorter code can also mean the destination is outside the supported set and fell back to the 6-digit international level.

What happens if I pick an unsupported destination? Classification returns a 6-digit international code rather than failing. Check the depth of what comes back before relying on it.

Is duty coverage as deep outside the United States? No. Six jurisdictions have a dedicated calculation. The rest run the general calculation, which covers the base rate plus antidumping, countervailing, and safeguard duties, with flags for quotas, prohibitions, and import controls.

Why did my preference claim come back empty? Most likely Altana does not carry that program for that destination. The ASEAN agreements are not covered for any destination. An empty result is a coverage gap, not a finding that your product does not qualify.

Does Section 232 apply to my non-US workspace? No. Section 232 is a US measure and is not evaluated for other destinations.

Is coverage growing? Yes. Destinations and duty programs are added over time, so confirm the current position with your Altana team rather than treating this page as fixed.