Collect structured product attributes — material composition, function, intended use, and end user — that map to the relevant HS chapter headings; avoid passing only a marketing product name to a classifier.
Call a classification API or AI-assisted tool (such as a customs broker platform or tariff database provider) with the product attributes; receive a suggested 6-digit HS code and optionally an 8- or 10-digit national tariff code.
Cross-reference the suggested code against the official national tariff schedule (e.g., USITC HTS for US imports, TARIC for EU imports) to confirm the duty rate, any quota restrictions, and required licenses.
For goods where classification is genuinely ambiguous, where duty rate differences between adjacent codes are material (several percentage points), or where the product is novel, file for a Binding Tariff Information (BTI) ruling with the relevant customs authority before commercial shipment.
Store the accepted HS code and its source (algorithmic suggestion, broker confirmation, or binding ruling) against the product SKU, and set a review trigger for regulatory schedule updates.
Implement a periodic re-classification review cycle, as HS schedules are updated on a five-year WCO cycle with interim national amendments.
Known gotchas
AI and automated classifiers achieve high accuracy on common goods but frequently mis-classify novel electronics, composite materials, or goods that span two HS chapters — human broker review is still necessary for high-value or high-volume SKUs.
A binding ruling only protects the specific importer and product described; it is not transferable to similar products or other importers, and it can be prospectively revoked by customs.
Using an unvalidated algorithmic classification on a formal customs entry without review exposes the importer to penalties for material mis-declaration, not just the tariff difference.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp