Schedule B Classification: U.S. Exporter Guide to AES Filing
Chen Cui Co-Founder of GingerControl What changed: Rebuilt Schedule B and AES guidance from Census/FTR sources; corrected the per-code threshold and permitted HTS alternative, and removed invented combined API outputs in all five languages.
Schedule B identifies goods exported from the United States for Census statistics and Electronic Export Information (EEI). Its ten digits share the international six-digit HS base, followed by U.S. export statistical detail. Classify the actual product, including materials, construction and function; a marketing name alone may not distinguish the correct provision [1–2].
For USPS international mail, check item-level HS mailing requirements separately from the ten-digit export code and EEI filing decision.
How do you find the correct export code?
- Collect the specifications and identify whether the goods are complete, unfinished, assembled or a set.
- Use Census's Schedule B search and current chapter text to identify candidates.
- Apply heading terms and Section/Chapter Notes under GRI 1 before moving to later rules when needed.
- Choose the appropriate ten-digit statistical subdivision and reporting units.
- Save the product facts, reasoning, source version and reviewer. Confirm ambiguous cases with Census or a qualified export adviser.
For composite goods, do not skip directly to essential character if a heading or Note already resolves classification. Search results are starting points; compare the actual provisions [2].
Can an HTS code be used in AES?
Often yes. Under 15 CFR 30.6(a)(12), an eligible ten-digit HTSUSA code may be reported instead of Schedule B, subject to HTS headnote exceptions [3]. Census's introduction says this is permitted for most Chapter 1–97 commodities. Check the current HTS export exclusions and AES-valid code list before reusing an import code. Schedule B numbers cannot replace HTS numbers on import entries [2].
| Classification | Main purpose |
|---|---|
| Schedule B | U.S. export statistical reporting |
| HTSUS | U.S. import classification and duty; eligible codes may also be used for exports |
| ECCN or EAR99 | Export-control classification for items subject to the EAR |
| Destination tariff code | Import requirements in the destination's own tariff system |
Matching six HS digits does not prove that every national ten-digit code is interchangeable.
When does the $2,500 AES threshold apply?
The low-value exemption generally applies to goods from one USPPI to one consignee on a single exporting conveyance, valued at $2,500 or less under an individual Schedule B or permitted HTS code. Combine multiple items under the same code as required; domestic and foreign-origin goods are assessed separately under the rule. It is not a blanket $2,500 total-invoice test [4].
For illustration, two different codes each valued at $2,000 may meet the low-value exemption; items with the same domestic/foreign status totaling $3,000 under one code do not. Mandatory reporting can apply regardless of value, including specified licensed or controlled exports and used self-propelled vehicles. Canada has a separate conditional exemption; goods merely passing through Canada to another destination are not covered by that exception. Review all applicable filing triggers before using an exemption [4].
Which 2026 version should your filing use?
As reviewed on October 12, Census's current 2026 page identifies codes for use after July 1, 2026. Check its add/delete list, obsolete-code notices and AES concordance for the shipment period [1–2]. Do not treat the January update or an old grace-period notice as proof that a code remains valid today. Update the source date in the product master and retain any correction record.
Where do GingerControl's tools fit?
Classification Researcher researches one product with GRI reasoning. Its confirmed markets are U.S. and Canadian ten-digit classification and EU eight-digit CN in beta; it has no confirmed Schedule B output. Export Control Classifier is a separate web tool for EAR/CCL analysis, returning an ECCN or EAR99 where appropriate; it does not cover ITAR or provide an API.
The enterprise Classification + Tariff Calculation API takes an English description and origin, returning a U.S. import code and current U.S. duty layers as JSON, with 120 items per batch by default. It gives no reasoning report, clarifying questions, Schedule B, ECCN or combined destination-country output. Researcher and custom GingerOS workflows can accept Chinese product descriptions. Keep the Census export code, export-control decision and destination import code as separate reviewed fields; confirm any custom integration scope before relying on it.
Frequently Asked Questions
What does Schedule B classify?
Goods exported from the United States for Census statistics and EEI, using a ten-digit export classification.
Is Schedule B the same as HTSUS?
Their first six HS digits align, but national statistical detail may differ. Some HTS codes are permitted for exports; verify the exceptions.
Does an invoice over $2,500 always require EEI?
Check the per-code rule and the other mandatory filing triggers. The invoice total alone does not resolve the low-value exemption.
Are all shipments to Canada exempt?
No. Licensing, commodity and routing exceptions apply under 30.36 and 30.2.
Can a six-digit HS code replace the required AES code?
No. When commodity-code reporting is required, use the valid ten-digit Schedule B or permitted HTS code and required description.
Which Schedule B version is current in October 2026?
The current Census 2026 page identifies codes for use after July 1; check its latest notices and AES-valid list for the shipment.
Does GingerControl's API return Schedule B and ECCN together?
No. Its confirmed output is a U.S. import code and current duty layers. EAR/CCL research is a separate web product.
What should a 3PL retain before filing?
Product specifications, the reviewed export code and version, value by code, filing or exemption basis, responsible parties and the filing/correction record.
References
Classifying SKUs one ruling at a time?
Hand this to GingerOS.
Pick a 30-minute slot on the next page with Chen Cui, our CEO. Bring one notice or one SKU list (an ERP export, a spreadsheet or an email will do) and see what GingerOS does with it.
Reviewed by Michael Weick, LCB / CCS
