HS code importing from China starts with a named destination market and an exact product record. Keep product/version/SKU, product description, composition/material, function/use, packaging/set/part context, supplier-proposed code, official destination classification source, quotation/shipping record, and unknown fields separate. This article is general information, not customs, tax, legal, trade, origin, classification, valuation, shipping, import, or compliance advice.
A China supplier, marketplace listing, broker message, freight quote, pro forma invoice, or packing list may show a code or tariff term. That information can be useful as a source record. It does not by itself settle a destination-market classification, duty, tax, shipping outcome, or customs action. Before asking for a shipping quote, clarify the product record and the destination source that a qualified professional would need to review.
Key takeaways
- Treat HS code importing from China as a destination-market and exact-product-record question, not a supplier label.
- Keep product description, material, function, packaging/set/part context, supplier-proposed code, official source, quote, and unknown fields separate.
- Read a code in a supplier or shipping record as a stated record, not as a classification conclusion for a different product/version or market.
- Preserve issuer/source, date/version, stated product scope, attachment, and transaction scope for each supplier, quote, and official source.
- Use qualified customs, tax, legal, trade, origin, classification, valuation, shipping, import, or destination-market professionals for a classification or determination.
Contents
- Start with a destination market and exact product scope
- Separate product description material function and context records
- Keep supplier-proposed codes official sources and quotes distinct
- Read destination-market classification sources by jurisdiction
- Use the classification source-record table
- What official sources identify
- What this article does not determine
- Message template for classification-source clarification
- Practical classification source-record checklist
- FAQ
Start with a destination market and exact product scope
HS code importing from China begins with a named destination market and an exact product/version/SKU scope. Retain the product name, model, version, SKU, stated product description, material/composition details if supplied, stated function/use, packaging/set/part context, source date/version, and attachment reference. Where a source does not name a product version, market, material, function, context, or source date, preserve the absence as an unknown.
The World Customs Organization describes the Harmonized System as an international product nomenclature used as a basis for customs tariffs and trade statistics. [1] That is a framework description. It does not assign, validate, or determine a code, tariff classification, origin, valuation, duty, tax, fee, quota, measure, declaration, entry, shipping method, broker, document, or customs action for a China-made product.
A product specification sheet can hold the source wording for a product/version, material, function, and packaging context. It does not classify the product or determine a destination-market customs outcome.
Separate product description material function and context records
A product-description record captures the exact seller, factory, brand, buyer, or official wording used for the product. A composition/material record captures only material or composition language stated by its source. A function/use record captures stated functional language. A packaging/set/part context record captures whether the source describes a set, part, accessory, packaging, bundle, or another product relationship. Each record needs its own issuer/source/date, product/version scope, and attachment or reference.
Do not expand one record into another. A product name is not a material record. A material record is not a function record. A photo is not a packaging/set/part context conclusion. A source that mentions an accessory is not a classification decision.
The China factory quote guide can help retain supplier, product, quantity, pricing, inclusions, exclusions, and date/version fields. The EXW versus FOB quote guide can help separate stated commercial terms from product records. Neither guide assigns an HS, HTS, CN, TARIC, or tariff classification.
Keep supplier-proposed codes official sources and quotes distinct
A supplier-proposed-code record should retain the exact code wording if supplied, who supplied it, source/date, product/version scope, material/function/context fields stated alongside it, and its attachment or message reference. Record it as a proposal or stated field, not a validated destination classification.
An official destination-classification-source record should retain publisher, jurisdiction, title, URL or reference, source date/version if stated, and the scope named by the source. A quotation/shipping record should retain its issuer/source/date, destination market stated on the quote, product/version scope, proposed freight or service wording, document scope, and unknowns. Do not turn a shipping quote into an official classification source.
Destination-market source, product/version/SKU scope, product-description record, composition/material record, function/use record, packaging/set/part context record, supplier-proposed-code record, official destination-classification-source record, quotation/shipping record, and unknowns must remain distinct records. A supplier code is not an official source. An official source is not a product record. A freight quote is not an origin, valuation, duty, tax, or customs conclusion.
The import-compliance source-record guide can help separate destination market, product, role, official source, document, and unknown fields. It is general information, not customs or tax advice.
Read destination-market classification sources by jurisdiction
A destination-market source is only meaningful for the jurisdiction it identifies. Retain the official publisher, jurisdiction, source/date, exact product information supplied to that source, and any stated limits of the source. Do not apply a U.S. source to an EU market or an EU source to a U.S. market. Do not generalise either source to another destination market.
CBP’s tariff-classification publication is U.S.-specific non-binding guidance. [2] The European Commission identifies EU tariff-classification sources/tools. [3] These pages can help identify where a qualified professional may need to review a destination-specific classification question. They do not settle a code or customs decision for an exact product, material/composition, function/use, packaging/set/part context, transaction, or destination market.
A packaging inspection source guide can help retain packaging, label, outer-carton, mark, quantity, state, and report fields. It does not decide a product classification, origin, valuation, duty, tax, fee, shipping outcome, or customs action.
Use the classification source-record table
This table helps organise destination and product records before requesting a classification or determination from qualified customs professionals. It does not select a code, tariff, origin, valuation, duty, tax, fee, quota, measure, declaration, entry, shipping method, broker, document, or customs action.
| Classification source record | Source or stated field | Destination product/transaction scope | Unknown or question for qualified customs professional |
|---|---|---|---|
| Destination-market source | Named destination market and official source if supplied | Jurisdiction and transaction scope stated by source | Which destination market and transaction need review? |
| Product/version/SKU scope | Product name, model, version, SKU, and stated product field | Exact product scope named by source | Which version or SKU does the record cover? |
| Product-description record | Exact product wording, issuer/source/date, and attachment | Description scope as stated | What product details remain unstated? |
| Composition/material record | Source wording for material/composition and attachment | Material scope as stated | What material or composition record is missing? |
| Function/use record | Source wording for function/use and attachment | Function scope as stated | What stated function/use details are missing? |
| Packaging/set/part context record | Source wording for set, part, accessory, packaging, bundle, or relation | Context scope as stated | What context is not identified? |
| Supplier-proposed-code record | Stated code wording, source/date, product scope, and attachment | Supplier-stated scope | Whether qualified review needs a destination classification source |
| Official destination-classification-source record | Official publisher, jurisdiction, title, URL/reference, date/version, and stated context | Destination source scope as stated | Whether qualified review needs to interpret the source |
| Quotation/shipping record | Issuer/source/date, stated destination, product scope, commercial or shipping wording, and attachment | Quote or shipping scope as stated | What the quote or document does not establish |
| Unknown or missing field | Open question and requested source record | Field not supplied or not linked | Which qualified professional should review the question? |
What official sources identify
The World Customs Organization source in this article describes HS as an international product nomenclature used as a basis for customs tariffs and trade statistics. [1] CBP’s tariff-classification publication is U.S.-specific non-binding guidance. [2] The European Commission identifies EU tariff-classification sources/tools. [3]
The U.S. and EU sources do not generalise to other destination markets. None of these descriptions assigns, validates, or determines an HS, HTS, CN, TARIC, tariff classification, origin, valuation, duty, tax, fee, quota, measure, declaration, entry, shipping method, broker, document, or customs action for a particular product. This article does not quote code examples, rates, cost figures, threshold values, timelines, or product-specific classification rules.
What this article does not determine
This article is general information, not customs, tax, legal, trade, origin, classification, valuation, shipping, import, or compliance advice, and it does not assign, validate, or determine an HS, HTS, CN, TARIC, tariff classification, origin, valuation, duty, tax, fee, quota, measure, declaration, entry, shipping method, broker, document, or customs action for a product.
It does not select a code, tariff, origin, valuation, duty, tax, fee, quota, measure, declaration, entry, shipping method, broker, document, or customs action. It also does not determine product quality, product safety, supplier capability, compliance, cost, schedule, shipment, or delivery.
For a classification or determination, use qualified customs, tax, legal, trade, origin, classification, valuation, shipping, import, or destination-market professionals who can assess the exact product version/SKU, product-description record, material/composition, function/use, packaging/set/part context, official source, quote/document records, destination market, and transaction facts. The table helps organise the question. It does not replace professional advice.
Message template for classification-source clarification
Use a request that asks for product and source records without asking the supplier to make a customs or classification conclusion.
Hello [supplier contact],
We are organising product and source records for [product name, version/SKU, and destination market]. Please provide the exact product description, material or composition information, stated function or use, packaging/set/part context, any proposed code with its source/date, product documents, pro forma invoice or packing-list source records if available, and attachment references.
For each item, please identify the issuer/source/date, stated product or version field, and document or attachment reference. If a record does not state product version, material/composition, function/use, packaging/set/part context, code source, destination market, or document scope, please say so in writing.
Thank you.
This request collects source records. It does not select a code, tariff, origin, valuation, duty, tax, fee, quota, measure, declaration, entry, shipping method, broker, document, or customs action.
Practical classification source-record checklist
- Have you named the destination market and exact product/version/SKU scope?
- Are destination-market source, product/version/SKU scope, product-description record, composition/material record, function/use record, packaging/set/part context record, supplier-proposed-code record, official destination-classification-source record, quotation/shipping record, and unknowns separated into distinct fields?
- Does each supplier, quote, shipping, or official source retain its issuer/source/date, stated product scope, and attachment reference?
- Have you treated the WCO source as an international HS framework and the CBP and EU pages as destination-specific sources?
- Have you avoided generalising U.S. or EU sources to another destination market?
- Have you retained a supplier-proposed code, marketplace listing, product description, quote, pro forma invoice, packing list, shipping document, broker message, or logistics estimate as a bounded source record rather than a customs conclusion?
- Have you identified questions that need qualified customs, tax, legal, trade, origin, classification, valuation, shipping, import, or destination-market professionals?
- This article is general information, not customs, tax, legal, trade, origin, classification, valuation, shipping, import, or compliance advice, and it does not assign, validate, or determine an HS, HTS, CN, TARIC, tariff classification, origin, valuation, duty, tax, fee, quota, measure, declaration, entry, shipping method, broker, document, or customs action for a product.
- This article does not select a code, tariff, origin, valuation, duty, tax, fee, quota, measure, declaration, entry, shipping method, broker, document, or customs action.
FAQ
Does a China supplier’s proposed HS code settle the destination classification?
No. A supplier-proposed code is a source record with a stated product and transaction scope. It does not establish an HS, HTS, CN, TARIC, tariff classification, origin, valuation, duty, tax, fee, quota, measure, declaration, entry, shipping, or customs conclusion for an unstated product version, material/composition, function/use, packaging/set/part context, destination market, or transaction. Use qualified professionals for a classification or determination.
Can a quote or shipping document establish the code and landed cost?
No. A supplier-proposed code, marketplace listing, product description, quote, pro forma invoice, packing list, shipping document, broker message, or logistics estimate does not establish an HS, HTS, CN, TARIC, tariff classification, origin, valuation, duty, tax, fee, quota, measure, declaration, entry, shipping, or customs conclusion for an unstated product version, material/composition, function/use, packaging/set/part context, destination market, or transaction. This article does not calculate or estimate duty, tax, fee, quote, shipping, or landed cost.
Can this article classify a product or calculate duty?
No. This article is general information, not customs, tax, legal, trade, origin, classification, valuation, shipping, import, or compliance advice, and it does not assign, validate, or determine an HS, HTS, CN, TARIC, tariff classification, origin, valuation, duty, tax, fee, quota, measure, declaration, entry, shipping method, broker, document, or customs action for a product. Use qualified customs, tax, legal, trade, origin, classification, valuation, shipping, import, or destination-market professionals for a classification or determination.
References
- World Customs Organization, “What is the Harmonized System (HS)?”
- U.S. Customs and Border Protection, “Tariff Classification”
- European Commission, “Tariff classification of goods”
Next step
If you need help organising supplier and source records, share the destination-market source, exact product/version/SKU record, product description, material/composition, function/use, packaging/set/part context, supplier-proposed-code record, quote/shipping material, official destination source references, and attachment list with Yes Supplier. The review can help structure clarification questions. This article is general information, not customs, tax, legal, trade, origin, classification, valuation, shipping, import, or compliance advice. For a classification or determination, use qualified customs, tax, legal, trade, origin, classification, valuation, shipping, import, or destination-market professionals.