Before classifying a new product, search the CBP CROSS (Customs Ruling Online Search System) database at rulings.cbp.gov for existing published rulings on similar merchandise to establish precedent.
Use an automated classification tool (such as Zonos Classify or Avalara cross-border) to generate a candidate HS/HTS number; document the AI classification confidence score and the product attributes used.
Compare the AI classification against any CROSS rulings found; if rulings conflict with the AI result, the ruling takes precedence for shipments covered by that ruling.
If no ruling exists and the commodity is high-value, restricted, or frequently audited, submit a binding ruling request to CBP via the CBP CROSS eRulings portal; include product samples, technical specifications, and a proposed HTS number with justification.
While awaiting the ruling (CBP targets 30 days but may take longer), use the AI classification for low-value shipments at the importer's risk; note that a pending ruling request does not protect against liquidated damages.
Once a binding ruling is issued, encode the ruling number in your entry filing system and apply it to all shipments of the same merchandise; audit entries to confirm the ruling HTS is consistently applied.
Known gotchas
A binding ruling is binding on CBP only for the specific importer, product, and facts described; variations in materials, manufacturing process, or country of origin may invalidate the ruling.
AI HS classifiers trained on global tariff schedules may return a 6-digit international HS code that does not map directly to a 10-digit US HTS Statistical Suffix; always verify the full 10-digit number against the USITC HTS schedule.
Misclassification — even unintentional — can result in underpaid duties subject to retroactive assessment with interest, and repeat misclassification may trigger a formal penalty action under 19 USC 1592.
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