Customs clearance imports questions often start with a request for one document list for products made in China. China origin does not identify the destination customs jurisdiction, product treatment, or source records for a specific transaction. Destination and jurisdiction, parties, product version, description and composition sources, origin sources, value and payment sources, transport records, documents, certificates, customs records, insurance sources, and unknowns can all matter in different ways.<\/p>\n
This article is general information, not customs, legal, tax, tariff, duty, classification, valuation, origin, licensing, product-safety, insurance, freight, carrier, shipping, regulatory, import, export, destination-market, logistics, delivery, or commercial advice. It does not identify, determine, interpret, recommend, select, classify, calculate, apply, file, declare, validate, or decide a destination country, customs jurisdiction, importer identity, party role, product classification, value, origin, document requirement, license, certificate, declaration, inspection, customs status, duty, tax, insurance, payment, entry, clearance, shipment, delivery, legal position, import result, or commercial decision. A qualified professional must determine a specific matter.<\/p>\n
Customs clearance imports cannot be planned with a universal China document list. Separate destination and jurisdiction, party and role, product version, product description, composition and use source, origin source, value and payment source, transport source, document and packing source, classification reference, certificate or license source, customs or declaration source, inspection and product-safety source, insurance source, and unknowns. Qualified destination-specific professionals can determine the transaction. This article does not identify a document, classification, declaration, or import action that applies.<\/p>\n
A sourcing file can have a product specification, invoice, packing source, transport message, and destination field without answering the same question. Keeping the original scope of each source visible makes later professional review more precise. It does not predict a customs result.<\/p>\n
U.S. Customs and Border Protection says its requirements can be specific to a commodity and can involve other U.S. government agencies.[1]<\/a> That statement concerns U.S. imports. It is not a destination-neutral rule for products from China.<\/p>\n The European Commission’s Access2Markets page is aimed at EU importers. It describes EU procedures and says readers should consult product-specific information.[3]<\/a> It does not provide a procedure for every country or a conclusion for a reader’s China shipment.<\/p>\n Those two source scopes illustrate the problem with a universal list. The destination record, product record, and transaction record remain separate. This article does not decide which jurisdiction applies, whether a product falls into a category, or whether a stated document is required, sufficient, current, or acceptable.<\/p>\n A China sourcing risk checklist<\/a> can help organize an operational question before specialist review. It does not identify a customs jurisdiction, classify goods, determine origin, choose a document, or decide a clearance outcome.<\/p>\n Start with the source that states the destination or jurisdiction, then retain the source date, version, party labels, addresses, contacts, product identifier, and any blank or conflicting fields. A buyer, seller, importer, consignee, exporter, representative, warehouse, contact, and address can appear in more than one record. Preserve the label as written instead of treating it as proof of a role or responsibility.<\/p>\n The article does not determine importer identity, party role, authority, customs jurisdiction, destination law, entry, clearance, payment, responsibility, or outcome. A destination field can be a useful source record without deciding an import question.<\/p>\n CBP’s U.S.-specific new-importer page gives examples of record categories in its own context. It refers to a detailed merchandise description, country of origin and manufacturer, composition, intended use, and pricing or payment information.[2]<\/a> These examples do not classify a product, determine origin, name a document, establish a license, or decide a requirement for a China shipment to another destination.<\/p>\n Keep a product description, SKU, revision, sample, specification sheet, material statement, composition source, stated use, manufacturer source, origin statement, test source, inspection source, label, carton mark, image, and price source tied to the record that contains it. Different versions may use similar names. A source in one file does not prove that it applies to another product, party, quantity, order, or destination.<\/p>\n A quotation, purchase order, sales contract, proforma invoice, commercial invoice, product source, specification sheet, test or inspection source, packing list, carton mark, label, product image, transport document, booking reference, carrier message, forwarder message, shipping instruction, insurance source, customs document, payment record, party\/address field, Incoterms label, origin statement, classification reference, destination requirement record, license\/certificate source, route label, or tracking record is only a source record in this article. It does not establish a complete agreement, importer identity, party role, classification, valuation, origin, document requirement, license, declaration, customs status, duty, tax, insurance, payment, entry, clearance, acceptance, legal effect, responsibility, or outcome for an unstated scope.<\/p>\n A quote, commercial invoice, payment record, Incoterms field, transport source, booking reference, carrier message, forwarder message, and route label can describe different parts of a transaction. Keep those records separate. A total price does not establish valuation, a payment line does not decide tax or duty, and a transport message does not determine customs status.<\/p>\n Destination\/jurisdiction, party\/role, product\/version, product description\/composition\/use source, origin source, value\/payment source, transport source, document\/packing source, classification reference, certificate\/license source, customs\/declaration source, inspection\/product-safety source, insurance source, and unknowns remain distinct source records. The article does not collapse a China-origin label into a destination customs or clearance conclusion.<\/p>\n The article does not identify a customs classification, calculate a value, determine origin, duty, tax, insurance, payment, entry, clearance, responsibility, legal effect, import result, or outcome. It also does not direct a reader to file, declare, classify, value, claim origin, obtain a license, arrange a certificate, use a broker, pay, insure, book, ship, pack, label, clear, import, deliver, or take another customs, legal, tax, transport, regulatory, or commercial action.<\/p>\n An import-duty planning article<\/a> can help keep a destination-market budget source separate from a supplier quote. It does not determine a duty, tax, classification, origin, customs treatment, valuation, payment, clearance, or import result.<\/p>\n The CBP Basic Importing and Exporting page and its importer tips page concern U.S. imports. In that U.S.-specific context, CBP describes commodity- and agency-specific requirements and gives examples of source categories.[1]<\/a> [2]<\/a><\/p>\nStart with destination and party sources<\/h2>\n
Keep product description composition use and origin records separate<\/h2>\n
Separate value payment transport and terms sources<\/h2>\n
Use official customs sources narrowly<\/h2>\n
| Discussion area<\/th>\n | Source or stated field<\/th>\n | Limited use in a professional discussion<\/th>\n | Unknown or question for qualified professional<\/th>\n<\/tr>\n<\/thead>\n |
|---|---|---|---|
| Destination and jurisdiction<\/td>\n | Stated destination, address, country field, message, unknown<\/td>\n | Preserves a destination source<\/td>\n | Applicable jurisdiction, treatment, requirement, action<\/td>\n<\/tr>\n |
| Party and role<\/td>\n | Buyer, seller, importer, consignee, representative, contact, address<\/td>\n | Shows labels in a source<\/td>\n | Identity, authority, role, responsibility, status<\/td>\n<\/tr>\n |
| Product and version<\/td>\n | Product name, SKU, revision, sample, image, quantity source<\/td>\n | Maps stated product scope<\/td>\n | Identity, scope, version, relationship to source<\/td>\n<\/tr>\n |
| Description composition and use<\/td>\n | Specification, material source, composition statement, stated use<\/td>\n | Keeps stated product information visible<\/td>\n | Classification, requirement, product treatment, action<\/td>\n<\/tr>\n |
| Origin source<\/td>\n | Origin statement, manufacturer source, product record, message<\/td>\n | Preserves a stated origin-related source<\/td>\n | Origin, treatment, claim, legal effect, outcome<\/td>\n<\/tr>\n |
| Value and payment source<\/td>\n | Quote, invoice, payment record, currency field, message<\/td>\n | Keeps commercial records separate<\/td>\n | Value, tax, duty, payment, legal effect, outcome<\/td>\n<\/tr>\n |
| Terms source<\/td>\n | Incoterms label, contract field, quote field, source version<\/td>\n | Identifies stated term language<\/td>\n | Scope, applicable term, legal effect, responsibility<\/td>\n<\/tr>\n |
| Transport source<\/td>\n | Transport document, booking reference, carrier or forwarder message<\/td>\n | Places a source in a transport discussion<\/td>\n | Carrier, booking, route, acceptance, action, outcome<\/td>\n<\/tr>\n |
| Document and packing source<\/td>\n | Packing list, carton mark, label, invoice, product source<\/td>\n | Maps stated record material<\/td>\n | Document role, completeness, packing, label, action<\/td>\n<\/tr>\n |
| Classification reference<\/td>\n | Product note, reference, prior source, unknown<\/td>\n | Keeps a classification-related record visible<\/td>\n | Classification, basis, jurisdictional treatment, action<\/td>\n<\/tr>\n |
| Certificate or license source<\/td>\n | Certificate, license image, statement, record, unknown<\/td>\n | Preserves a stated source<\/td>\n | Scope, issuer, requirement, validity, action<\/td>\n<\/tr>\n |
| Customs or declaration source<\/td>\n | Stated declaration, customs message, record, unknown<\/td>\n | Keeps a customs-related source visible<\/td>\n | Declaration, filing, customs status, clearance, outcome<\/td>\n<\/tr>\n |
| Inspection and product-safety source<\/td>\n | Test record, inspection record, product statement, label<\/td>\n | Maps stated product sources<\/td>\n | Product treatment, safety, requirement, action<\/td>\n<\/tr>\n |
| Insurance source<\/td>\n | Policy source, stated coverage, message, unknown<\/td>\n | Preserves a stated source<\/td>\n | Coverage, role, requirement, outcome<\/td>\n<\/tr>\n |
| Unknowns<\/td>\n | Missing destination, unclear product version, absent record, conflicting party<\/td>\n | Makes a gap visible<\/td>\n | Whether the gap matters and who should determine it<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nWhat qualified professionals still need to determine<\/h2>\nA record map does not decide a customs transaction. Qualified customs, legal, tax, trade, product-safety, dangerous-goods, regulatory, import, export, insurance, freight, carrier, and destination-market professionals may need to determine destination, party, product, classification, value, origin, licensing, document, transport, customs, tax, insurance, product-safety, and transaction issues from the actual facts.<\/p>\n The article does not determine whether a source is complete, accurate, binding, suitable, current, enforceable, sufficient, or accepted. It does not tell a reader whether to file, declare, classify, value, claim origin, obtain a license, arrange a certificate, use a broker, pay, insure, book, ship, clear, import, or deliver.<\/p>\n What a sourcing team can and cannot do<\/h2>\nYes Supplier can help organize product, sample, quality, packing, and operational shipment-record sources. Buyers can contact our team<\/a> for an operational sourcing conversation. That support does not provide customs, legal, tax, tariff, duty, classification, valuation, origin, product-safety, regulatory, licensing, insurance, freight, carrier, shipment, clearance, delivery, import-result, or outcome advice. It does not promise a document, classification, clearance, cost, time, customs result, import result, delivery, or result.<\/p>\n A sourcing coordinator can place a packing record beside the product version, inspection record, and invoice source it states. Qualified professionals must determine the significance of the records for a particular destination and transaction.<\/p>\n This article does not identify a required document, destination customs process, certificate, license, declaration, product classification, value, origin, duty, tax, insurance, entry, clearance, or import result. The CBP and European Commission pages have different jurisdictional scopes. Qualified destination-specific professionals can assess the actual product and transaction sources.<\/p>\n A commercial invoice is a source record. This article does not determine value, classification, origin, duty, tax, payment, document sufficiency, customs status, entry, clearance, legal effect, or outcome from an invoice or another isolated source. Qualified professionals can assess the transaction-specific records.<\/p>\n This article does not select a provider or determine a party’s authority, classification, customs status, duty, tax, declaration, entry, clearance, or outcome. A forwarder message is a source record. Qualified customs and destination-market professionals can assess the actual product and transaction facts.<\/p>\n [1] U.S. Customs and Border Protection: Basic Importing and Exporting<\/a><\/p>\n [2] U.S. Customs and Border Protection: Tips for New Importers and Exporters<\/a><\/p>\n |