- Start by naming the transaction. An import classification review asks how the destination customs tariff classifies the goods. A US export-control review asks whether the item is subject to the EAR, whether it appears on the Commerce Control List, and what further transaction checks apply. Do not merge these into one “customs code” task.
- Create one product-facts record. Include the exact model or SKU, manufacturer, function, material, construction, technical specifications, software or firmware, encryption and wireless features, components, country of origin, destination, and intended use. Missing technical facts should produce a review flag rather than a confident code.
- Prepare the customs side first when needed for an import workflow. Use the HS Code Finder to organize candidate headings from product facts, then verify the full national code in the destination tariff database. Use the HS code vs tariff code guide to keep the six-digit starting point separate from national extensions.
- For the export-control field, ask the manufacturer or technical owner for a current ECCN or an EAR99 statement that identifies the exact model and version. Request the source and date, not only a code in an email subject line. A supplier's answer is useful evidence, but the exporter still needs a process appropriate to the transaction.
- If no reliable manufacturer answer is available, follow the BIS classification sequence: review the Commerce Control List in the order described by BIS, compare the item's technical characteristics with the entries and notes, or use an appropriate formal classification request. Do not search the HS number inside the Commerce Control List and treat a text match as a determination.
- If the review supports EAR99, record the basis and the product facts covered. Then continue with destination, end-user, end-use, and other applicable checks. EAR99 items can still be restricted in particular transactions, so the workflow must not stop at that label.
- Store the customs and export-control results in separate columns: HS candidate, verified national tariff code, ECCN or EAR99 status, evidence source, evidence date, reviewer, destination, end user, end use, and review notes. The CSV Catalog Checker can organize customs fields, but it does not assign ECCNs or determine export authorization.
- Before shipping, compare the catalog record with the commercial invoice and order data. Use the Commercial Invoice Generator for a draft and the Shopify shipping checklist for catalog consistency. Escalate unresolved export-control questions through BIS resources or a qualified export-compliance professional.
Guide
ECCN vs HS Code vs EAR99 for Ecommerce Sellers
Learn how ECCN, EAR99, HS and HTS fields differ, what evidence ecommerce sellers should keep, and when export-control review must remain separate.
Answer Summary
Preparation checklist
Keep customs classification and US export-control classification in separate catalog fields. They use different systems, sources, and decision rules.
Use product material, function, construction, and destination to prepare an HS code candidate, then verify the full national tariff code in the importing country.
Obtain an ECCN or EAR99 basis from the manufacturer, technical owner, a documented Commerce Control List review, or a formal classification route. Never derive it from an HS code.
After classification, review destination, end user, end use, and other applicable restrictions separately. A code by itself is not an export authorization.
Use this workflow
Required fields or decision table
Fields to prepare before the document draft
| Field or decision | What to prepare |
|---|---|
| Product identity | Keep the SKU, model, brand, manufacturer, product name, version, and a plain-language description together. A vague storefront title is not enough for either customs or export-control review. |
| Technical facts |
|
| HS code candidate | Use the product facts to prepare a six-digit international HS heading candidate, then verify the destination-specific extension. This field supports customs classification and tariff review; it does not answer US export-control questions. |
| HTS or national tariff code | Record the importing country's full national tariff code separately from the six-digit HS starting point. For US imports, verify the current HTSUS provision in the USITC Harmonized Tariff Schedule. |
| ECCN | If the item is described on the Commerce Control List, record the five-character ECCN, the source of the determination, the product version covered, and the date reviewed. Do not enter a guessed code to complete a marketplace field. |
| EAR99 status | Use EAR99 only when the available evidence supports that the item is subject to the EAR but is not described by an ECCN. Store who made the determination and what product facts were reviewed; EAR99 is not a synonym for unrestricted. |
| Destination, end user, and end use | Keep the ship-to country, consignee, intermediate parties, known end user, and intended end use outside the classification fields. These facts can change the required export review even when the product code is unchanged. |
| Evidence owner and review date | Name the manufacturer, supplier, internal technical owner, or qualified reviewer who supplied the ECCN or EAR99 basis. Record the document, version, date, and next review trigger so an old answer is not silently reused after a product change. |
| Change triggers | Flag a new chipset, encryption feature, wireless module, firmware capability, performance specification, component substitution, manufacturer revision, destination, end user, or end use for renewed review. |
Step-by-step preparation
How to prepare the draft
Ecommerce example
How this looks in a seller workflow
A US Shopify seller exports a Wi-Fi-enabled industrial sensor to a business customer overseas. For the destination customs declaration, the seller collects the sensor's function, construction, components, country of origin, and destination, prepares an HS candidate, and verifies the destination-specific tariff code. That customs record may support duty and document preparation, but it does not establish an ECCN.
For the US export-control record, the seller asks the manufacturer for the exact model's ECCN or EAR99 basis and the technical document date. Because the product includes wireless communication, firmware, and possible encryption, the seller does not copy an ECCN from a similar-looking sensor or infer one from the HS heading. If manufacturer evidence is missing or the specifications do not match, the record is marked for separate review.
The seller then reviews the destination, parties, end user, and intended industrial use using the applicable BIS process. The final catalog row keeps the customs code, export-control status, evidence source, and transaction checks in separate fields. A later firmware or radio-module change triggers renewed review even if the product name and HS candidate stay the same.
A simple cotton T-shirt illustrates the same discipline. The seller can prepare an apparel HS candidate from construction and fibre facts, but should not invent an ECCN merely because a software field asks for one. The seller first determines which US export rules apply to the actual transaction and retains the evidence used for that conclusion.
- Customs record: product facts, origin, destination, HS candidate, verified national tariff code, and tariff-source date.
- Export-control record: exact model, technical specifications, ECCN or EAR99 basis, evidence owner, source document, and review date.
- Transaction record: destination, consignee, end user, end use, screening outcome, exceptions or authorization references where applicable, and reviewer.
- Change control: repeat the relevant review after technical, software, destination, party, or use changes instead of reusing a stale code.
Verification checklist
Review the record before it enters a shipment or filing workflow
- The HS or HTS field and the ECCN or EAR99 field are stored separately and are not described as interchangeable.
- The product record identifies the exact SKU, model, manufacturer, version, function, and technical specifications used in the review.
- The HS candidate has been checked in the importing country's current tariff source rather than treated as a worldwide final code.
- The ECCN or EAR99 basis identifies its source, date, covered model or version, and responsible evidence owner.
- No ECCN was inferred from an HS, HTS, Schedule B, product title, another seller's listing, or marketplace suggestion.
- An EAR99 label is supported by a documented classification basis and is not presented as an automatic permission to export.
- Destination, end user, end use, and relevant party checks are recorded separately from product classification.
- Encryption, wireless, computing, aerospace, navigation, sensor, chemical, software, technology, or other sensitive characteristics have been escalated when the internal record is incomplete.
- Technical or transaction changes have a visible review trigger so a stale classification is not reused.
- The shipping documents use accurate product descriptions and catalog facts without claiming that TariffCatalog supplied a binding export-control decision.
Source-backed checks
What external guidance supports this workflow?
- BIS: Classify Your ItemOfficial BIS workflow for checking the Commerce Control List, understanding ECCNs, using EAR99 when appropriate, and distinguishing ECCNs from Schedule B and HTS numbers.
- BIS: Export Administration RegulationsOfficial access point for the current Export Administration Regulations and related regulatory resources.
- BIS: Part 774 and the Commerce Control ListOfficial Commerce Control List structure and ECCN entries. Technical characteristics and notes must be reviewed; an HS code is not the lookup key.
- BIS: Part 738 and the Commerce Country ChartOfficial destination-control framework used after classification. Product classification alone does not complete the transaction review.
- Trade.gov: ECCN and EAR99US government overview explaining ECCNs, EAR99, and the need to consider destination, end user, and end use.
- USITC: Harmonized Tariff ScheduleOfficial US tariff schedule for verifying US import classifications. It is a customs source, not an ECCN database.
Internal workflow links
Use the same catalog data in the next review step
Common mistakes
What to avoid
- Treating an HS, HTS, Schedule B, and ECCN as different names for the same code.
- Converting an HS code to an ECCN with a generic lookup table or copying the export-control code from a similar product.
- Entering EAR99 as a default value before checking whether the item is described on the Commerce Control List.
- Assuming EAR99 means the item can be exported to any destination, party, or end use without further review.
- Saving a manufacturer's code without the exact model, version, source document, or date it covers.
- Using storefront marketing copy instead of technical specifications for encryption, wireless, computing, sensor, software, or performance features.
- Treating classification as the final transaction decision and omitting destination, end-user, end-use, and party checks.
- Reusing an old determination after a chipset, firmware, component, feature, manufacturer, destination, or end-use change.
- Presenting an HS candidate generated by TariffCatalog as an ECCN determination or export authorization.
Editorial
Editorial review note
Written by the TariffCatalog Editorial Team for ecommerce document preparation workflows. The page is designed as a preparation checklist, not a filing outcome.
Maintained by Ryan Cole, with review focused on ecommerce catalog, document, and source-check workflow clarity.
Document requirements may be required differently by carrier, destination, shipment value, and product facts. Use the methodology, sources, and corrections pages to understand how the page is maintained.
Official source note
References to verify
Use official sources, carrier guidance, postal operator rules, and destination requirements to verify before filing or shipping.
USITC HTS
Use this official source when checking final classification, duty treatment, or customs requirements.
CBPUse this official source when checking final classification, duty treatment, or customs requirements.
EU TARICUse this official source when checking final classification, duty treatment, or customs requirements.
UK Trade TariffUse this official source when checking final classification, duty treatment, or customs requirements.
FAQ
Common questions
Are ECCN and HS codes the same?
No. HS codes support customs classification across international tariff systems, while ECCNs identify items described on the US Commerce Control List. They come from different legal systems and cannot be substituted for one another.
Is an ECCN the same as an HTS code?
No. An HTS code is a US import tariff classification. An ECCN is a US export-control classification under the Export Administration Regulations. A product catalog may need both fields, but each requires its own evidence and verification path.
Is EAR99 an ECCN number?
EAR99 is not one of the five-character ECCNs on the Commerce Control List. It is a designation commonly used for items subject to the EAR that are not described by an ECCN. The underlying review and transaction checks should still be documented.
How do I know if my product is EAR99?
Collect the exact model and technical facts, review the Commerce Control List in the sequence described by BIS, and obtain manufacturer or formal classification evidence when needed. Do not select EAR99 merely because a product appears ordinary or no code was supplied.
Do all ecommerce products need an ECCN?
Not every ecommerce catalog item will have an ECCN, and not every transaction is handled identically. A US exporter should determine whether the item and transaction are subject to the EAR, then document an ECCN or EAR99 basis where applicable.
Can I find an ECCN from an HS code?
No reliable one-to-one conversion exists. BIS states that ECCNs are distinct from Schedule B and HTS numbers. The HS field can support customs work, but ECCN review must use technical facts and the Commerce Control List process.
Does having an ECCN mean an export is allowed?
No. Classification is one part of the workflow. Destination, end user, end use, parties, and other applicable restrictions or authorization requirements must be reviewed separately for the actual transaction.
What product information is needed for an ECCN review?
Use the exact model, manufacturer, function, intended use, components, materials, technical performance, processors, power, wireless and encryption features, software or technology, and versioned technical documents. The necessary depth depends on the item and the relevant Commerce Control List entries.
Disclaimer
TariffCatalog provides informational tools and preparation workflows only. Verify final classification, rates, document requirements, and filing treatment with official sources or licensed professionals.