⚠️ This column is a sharing of the prompt creation process for free educational purposes, and is not any investment, legal, or financial advice. AI execution results may contain errors and independent verification is essential, and all responsibility for use is entirely attributed to the user. It cannot be used directly for business decision-making. [View all mandatory confirmation items below the 30-week timeline before use[]](https://www.notion.so/30-29f84ddcec3c80a1a87eda9883d81453?pvs=21)
Before starting, I inform you. All HTS codes used in this article are hypothetical examples for understanding the structure and have no relation to actual HTS classifications. In actual business, you must check the current official HTS.
HTS was an abbreviation for Harmonized Tariff Schedule. As the U.S. tariff classification system, each imported product receives a unique HTS code. Because the tariff rate is determined by this code, in other words, tariffs cannot be imposed without an HTS code.
However, before starting to design the HTS_Checklist.md file, one question arose. Since the HTS code is the most specific, why can't it be the standard instead of Product? Wouldn't it be more accurate to start with HTS?
Product is a general category like "Memory chips," and HTS was a specific 10-digit code like "8542.31.0010.”
I asked this question to Claude. "The HTS code is much more specific, what if we collect information based on this?" I asked using Sequential Thinking.
Claude started thinking. "1st thought: HTS codes are very specific. For example, 8542.31.0010 specifies exactly what product it is.", "2nd thought: There is no ambiguity compared to Product, and HTS codes clearly point to one product.",
"5th thought: However, the problem is that even just Memory chips alone can have multiple HTS codes.", "7th thought: For example, certain products receive different HTS based on capacity. 1GB or more, 4GB or more, 16GB or more each have different codes.”