When you export someone else's product — a server, a router, a sensor, a software package — the fastest way to its ECCN is usually the manufacturer. Many publish classifications for their whole catalogue. But a published ECCN is a starting point, not a shield: under the Export Administration Regulations, the exporter is responsible for the classification it ships under.
Where manufacturers publish ECCNs
- Export or trade compliance pages. Many large technology and electronics manufacturers publish product classification lookups, where you enter a model or part number and see its ECCN, and often its CCATS number if BIS has classified it.
- Datasheets and product pages. Some list the ECCN alongside technical specifications.
- Commercial documents. Invoices, packing lists and order confirmations from larger suppliers often carry the ECCN.
- The supplier's compliance team. If nothing is published, ask. Request the ECCN, the paragraph and, for encryption items, whether a classification request or self-classification report covers it.
- Distributors. Authorised distributors often hold classification data for the lines they carry.
People often search for a brand name followed by "ECCN" — the published lookup, where one exists, is the place to start.
What a published ECCN covers — and what it does not
A manufacturer's ECCN describes the product as the manufacturer sells it. It does not automatically cover:
- Modified items — added functions, different firmware, changed encryption.
- Integrated items — a component built into your own system, where the system is classified as a whole (and the component may or may not keep its own ECCN when exported separately).
- Different variants — the same model name with different specifications, for example a higher-performance version that crosses a threshold.
- Software and technology that come with the product — manuals, source code and development know-how have their own classifications in product groups D and E.
When you can rely on it
In practice, exporters routinely use manufacturers' classifications, and doing so in good faith is reasonable — particularly where the manufacturer holds a BIS classification ruling (CCATS) for the item. Good practice is to:
- Check the classification against the entry. Open the ECCN on the Commerce Control List and confirm the item meets the paragraph. How to look up an ECCN shows how.
- Record the source — the page, document or email, and the date.
- Watch for red flags — an ECCN that does not match the item's function, a generic "EAR99" for a clearly technical product, or no paragraph given for an entry that has several.
When you must classify it yourself
- The manufacturer does not publish or provide an ECCN.
- You modified the product or integrated it into another.
- The published ECCN appears inconsistent with the entry's parameters.
- You export related software or technology.
- The product is your own.
Classifying from scratch follows the steps in how to find the ECCN for your product: ITAR first, then the category and product group, then the entry and the paragraph the item meets.
When sources disagree
If the manufacturer says 5A992.c and your own reading suggests 5A002, do not choose the more convenient answer. Ask the manufacturer how it reached its classification — for encryption items, whether the Cryptography Note applies and what filing was made. If the conflict remains, you can request a formal classification from BIS; see self-classification vs. a BIS classification request.
What to ask a supplier for
- The ECCN and the paragraph (for example 5A992.c, not just 5A992).
- The basis — self-classification, or a CCATS number.
- For encryption items, whether a § 740.17 filing covers the product.
- Whether the classification covers all variants and firmware versions you buy.
- The HTS code separately, if you also need it for customs — it is a different classification.
- Whether the item is subject to the ITAR in any configuration.
Keeping supplier classifications current
Supplier classifications change when products change and when the regulation changes — the advanced computing rules, for example, moved many servers and accelerators into new entries. Build a simple routine: refresh supplier ECCNs at least annually, when a new model or firmware ships, and whenever BIS publishes a rule affecting the category. Keep the dated source with each record.
Red flags in published ECCNs
- "EAR99" for a clearly technical product with networking, encryption or high performance.
- An entry with no paragraph where the entry has several.
- An ECCN from a different category than the product's function suggests.
- A classification older than a major rule change affecting the product.
Any of these is a reason to check the entry yourself — see ECCN lookup.
Checking a supplier's ECCN with ECCN.help
ECCN.help's Quick Search opens any entry by code so you can compare the paragraph with the product's specifications, free and without limit. To classify the item yourself — or to confirm a supplier's answer with your own reasoning on file — the ECCN.help Classification Workflow walks through the regulation step by step, rule-based and without AI, and records every answer that decided the result. See also common ECCN classification mistakes.
ECCN.help provides research and assistance, not legal advice.