Spotlight on HS2028 Revisions: Reclassification Risks for Automotive Sensors and Practical Countermeasures


Preparing Now for the Future of Automotive Business

Automotive competitiveness is no longer determined solely by engines or motors. With the advancement of ADAS (Advanced Driver Assistance Systems), autonomous driving, electrification, and connectivity, sensors have become core components that dictate a vehicle’s value.

On the front lines of global trade, however, it is no exaggeration to say that “no item is more prone to HS code fluctuation than sensors.” This volatility is highly likely to surface with the upcoming HS2028 revisions—which is the theme of this article.

In this post, we will look at the overall picture of the HS2028 revisions, delve into why automotive sensors are at the center of reclassification risks, identify where the “landmines” are hidden, and discuss how businesses should prepare from a practical perspective.


What Will Happen with the HS2028 Revisions?

HS revisions are often viewed as a “world for customs practitioners,” but in reality, they trigger a chain reaction affecting tariff costs, FTA rules of origin, internal master data, contract terms, and statistical data. Since the HS serves as the common foundation for global customs and statistical classification—with the framework of Chapters, 4-digit headings, and 6-digit subheadings harmonized internationally—changes at the 6-digit level have a simultaneous global impact.

HS2028 Timeline

The timeline for the HS2028 revision is as follows:

  • March 2025: Provisional adoption of 299 sets of amendments at the 75th session of the WCO (World Customs Organization) HS Committee.
  • Late December 2025: Formal adoption by the WCO Council.
  • January 2026: Official publication of the revised nomenclature.
  • January 1, 2028: HS2028 enters into force (simultaneous global implementation).

The Role and Limitations of Correlation Tables

The WCO maintains Correlation Tables that show the relationship between the current HS2022 and the new HS2028 codes. However, these tables are not a “plug-and-play” solution.

The WCO explicitly states that Correlation Tables are guides to assist implementation and have no legal binding force. More importantly, for items where views currently differ among countries, multiple patterns of correlation may be listed. In other words, for items with high classification volatility, the Correlation Table alone is insufficient for making a final determination.


Why “Automotive Sensors” Are Most Prone to Volatility in HS Revisions

Automotive sensors are particularly difficult to classify because they simultaneously straddle the following three boundaries:

1. Vehicle Parts vs. Electrical Machinery vs. Measuring Instruments

Just because a sensor is used in an automobile does not mean it is automatically classified as a vehicle part (such as heading 8708 in Chapter 87).

Under the Legal Notes of the HS, even if an item appears to be a “part or accessory” of a vehicle, there are provisions that prioritize classification under Electrical Machinery (Chapter 85) or Measuring Instruments (Chapter 90). Specifically, Note 2 to Section XVII (Vehicles, Aircraft, Vessels) explicitly excludes electrical machinery falling under Chapter 85 from the definition of “parts and accessories.”

This puts sensors in a precarious position from the start, as they almost invariably contain electrical/electronic elements and are designed for measurement or detection.

2. Semiconductor Devices vs. Finished Modules

While sensors often contain chips, they are imported and exported in various forms—ranging from “resin-sealed semiconductor elements” to “modules with housings” and “ECU-like units.”

Note 9 to Chapter 85 defines semiconductor-based transducers (including sensors) and stipulates that headings for semiconductor devices (8541 or 8542) should be prioritized if certain conditions are met. Consequently, even for the same application, the classification logic changes depending on the structure and form of the product at the time of import.

This directly impacts the automotive industry, where procurement types—buying “chips only,” “modules,” or “units”—often coexist within the same supply chain.

3. Diversity of Physical Principles: Radar, Optical, Ultrasonic, Inertial, etc.

Even under the umbrella of “sensors,” the candidate Chapters and headings vary depending on the underlying principle. Practical customs rulings show:

  • Radar systems may be classified under 8526 (Radar apparatus, etc.).
  • LiDAR sensors may be classified under 9015 (Surveying instruments, etc.).
  • Ultrasonic sensors for proximity may be classified under 9031 (Measuring or checking instruments, etc.).
  • Camera sensors may be classified under 8525 (Television cameras, etc.).

These cases demonstrate that sensors are judged not by their name, but by “what the device does,” “what principle it uses,” and “to what extent functions are integrated.” HS2028 is specifically designed to incorporate these technological advancements. Items on the borderline are naturally the most susceptible to the waves of reclassification.


Four Patterns of High Reclassification Risk for “Automotive Sensors”

  1. Pattern A: “Mini-Computers” (Sensor + Control + Communication)Radar, LiDAR, and surround-view cameras increasingly integrate signal processing, object detection, tracking, and in-vehicle network communication alongside the sensing element. This raises classification debates: is it a “measuring device,” “radio apparatus,” or “video apparatus”?
  2. Pattern B: Modules with Composite FunctionsIn the case of composite goods, the argument centers on which function gives the product its essential character under the General Rules for the Interpretation (GRI). The quality of technical documentation is decisive here.
  3. Pattern C: Designed for Vehicles, but Unlikely to be Classified as Vehicle PartsAs clearly indicated in Section XVII Note 2, items falling under Chapter 85 or 90 are excluded from the scope of vehicle parts. Treating them uniformly as vehicle parts increases the risk of audit findings.
  4. Pattern D: “Intermediate Forms” Between Chips and Finished ProductsSub-assemblies and PCBA (Printed Circuit Board Assemblies) exist in the “gray zone” between semiconductor-level sensors and housing-integrated measuring instruments. This intermediate form is the most volatile zone for classification.

Business Impact: Reclassification is More Than Just a Cost Issue

Changes in HS codes or their interpretation directly hit profitability in several ways:

  • Tariff Rates and Additional Duty Risks: A code change changes the applicable tariff rate. An increase leads to higher costs, while a decrease necessitates a change in pricing strategy. Furthermore, disputes can escalate into retroactive assessments and penalties.
  • Disruption of FTA Origin Determinations: Product Specific Rules (PSRs) in FTAs are designed based on HS Chapters, Headings, and Subheadings. A 6-digit revision shifts the very foundation of origin determination.
  • Customer Audits and Supplier Management: OEMs and Tier 1s demand consistency in compliance information, including HS codes. Because sensors involve high volumes and granular SKUs, any discrepancy leads to a massive surge in corrective and explanatory workload.
  • Master Data and System Updates: The HS code is a key field in PLM, ERP, customs, procurement, and export control systems. An HS revision should be managed as an IT systems project to be successful.

Practical Actions: “How to Protect Your Sensor Classification” for HS2028

To control reclassification risks, the following sequence is effective:

Step 1: Inventory Sensors by “Principle and Structure,” Not Just “Application”

Maintain data on:

  • Detection Principle: Electromagnetic waves, laser, ultrasonic, acceleration, pressure, temperature, etc.
  • Output: Analog, digital, or specific communication protocols.
  • Signal Processing: Does it perform internal measurement or object recognition?
  • Form: Semiconductor element, PCBA, module with housing, or unit.
  • Inclusions: Treatment of harnesses, brackets, mounts, and software.

Step 2: Maintain “Alternative Candidate Codes” for Current Codes

Since sensors often cannot be uniquely determined, document “candidate codes if contested” and the “reasons for the difference” as internal evidence based on Legal Notes and the GRI.

Step 3: Use Correlation Tables as an “Entry Point for Investigation,” Not a “Replacement List”

As the WCO explains, correlation tables are guides and may show multiple correlations for items with split views. For borderline items like sensors, treating the table as an automatic conversion tool is risky.

Step 4: Anticipate National Implementation Schedules

While the HS is global, each country implements it with its own extended digits (7th digit and beyond). For example, the USITC (U.S. International Trade Commission) is expected to publish a draft in February 2026 and submit a final report to the President in September 2026.

Step 5: Share “Classification Assumptions” with Customers and Brokers

Ensure alignment with external parties. Confirm if customers have specified codes, if the importer’s view is fixed, and what codes have been used in past declarations. Consider seeking Advance Rulings where necessary.


Conclusion: HS2028 Sensor Reclassification is a “Management Issue,” Not a “Technical Task”

With the official publication of HS2028 expected in January 2026 and its entry into force in January 2028, the window for preparation is narrowing.

Automotive sensors straddle three boundaries: vehicle parts vs. electronics, semiconductors vs. modules, and a diversity of physical principles. This makes them the “canary in the coal mine” for HS revision impacts. Treating this as a mere “customs clerical task” will lead to significant rework later.

The optimal solution is to begin building a foundation for classification based on technical data now, and to expand this into master data, contracts, origin determination, and cost management.


Would you like me to create any of the supplementary materials mentioned at the end of the blog, such as the “Inventory Questionnaire” or the “Classification Logic Map (Chapter 85/90/Vehicle Parts)”?

How to Build Audit-Ready HS Classification Documentation

A practical, business-friendly way to design and operate a “classification dossier” that holds up in post-clearance audits

In import and export operations, an HS code is not just a number. It affects duty rates, import controls, eligibility under rules of origin, statistical reporting, and even internal profitability management. That is why, in a customs audit, what gets tested is often not only the HS code you declared, but whether you can explain why you reached that conclusion, whether the logic is reproducible, and whether your internal controls are working.

This article explains how to build HS classification documentation that stays consistent regardless of who prepares it. The goal is not to “win an argument” about the HS code, but to demonstrate that you made a reasonable determination based on primary sources, and that you can prove it with evidence.


1. In audits, what matters is not just the result, but reproducibility and control

Post-clearance audits and similar reviews typically focus on documents, records, and transaction files. Auditors verify the consistency between the product’s actual characteristics and the declaration by reviewing documentation. WCO guidance on post-clearance audit places record examination at the core of the audit process.

In practice, companies that handle audits well are not those with a “super expert” who can explain everything verbally. They are the ones that do not rely on individual intuition alone and can still explain, years later, what they decided, why they decided it, and how the decision can be reproduced.


2. Fix the hierarchy of sources

GRI and legal notes at the top, explanatory materials next

A robust HS classification approach generally follows this order.

  1. General Rules for the Interpretation (GRI) and legal notes, such as Section Notes and Chapter Notes
  2. The heading and subheading wording
  3. WCO Explanatory Notes
  4. WCO Classification Opinions, advance rulings and administrative guidance by customs authorities, and relevant case law

The GRI framework makes clear that classification is based on the terms of headings and relevant notes, not on headings titles.
WCO also describes Explanatory Notes as guidance that clarifies coverage, includes and excludes, and practical identification points for headings.
Classification Opinions provide worked examples for specific products and are positioned alongside Explanatory Notes in terms of practical value.

If you lock this hierarchy into internal policy and standardize your dossier structure around it, your audit explanations become much stronger and faster.


3. The 10-piece “HS Classification Dossier” that performs in audits

Start by building this set

Audit strength is not about having a thick file. It is about having a file that covers all necessary issues, clearly. A practical approach is to compile one dossier per product, or per defined product family, with the following ten components.

1) Product identification sheet (cover page)

Include internal part number, product name, use, model/type, and photos.
Add country-specific declaration descriptions as used on invoices.
Record the HS version applied (for example, HS 2022), the decision date, and a version control number.

2) Core specification evidence

Catalogs, datasheets, drawings, bills of materials, photos of the product, packaging form, and set configuration.
This aligns with the type of materials commonly requested in advance ruling submissions. For example, Japan Customs indicates that supporting materials such as samples, photos, raw materials, and processing information can be relevant.

3) Materials and manufacturing process documentation

Material composition ratios, material certificates, and a process flow.
Explain where and how processing is performed.
Audits test the reality of the product, so the ability to explain materials and processing is a major advantage.

4) Classification memo (one-page conclusion plus detail)

Do not stop at the HS code. Explain the logic in a single path aligned to the GRI. A fixed template reduces individual variation.

5) Alternative classification analysis

List headings considered, “neighbor” headings, and any HS codes historically used internally.
Explain why alternatives were not adopted.
This is a common audit pressure point, and documenting it proactively shortens disputes.

6) Extracts of relevant legal text and notes

Include the relevant Section and Chapter Notes and the wording of the heading.
Audit discussions often move quickly, so having the key text extracted reduces friction and confusion.

7) Explanatory Notes and Classification Opinions reference memo

Summarize relevant passages without over-quoting.
WCO positions these as classification support materials.

8) Copies of advance rulings, decisions, and published guidance

Depending on the country and product, this can be your strongest evidence.

Japan: Advance classification rulings are described, and written answers are treated with respect in import examinations under the stated conditions.
EU: Binding Tariff Information (BTI) is positioned as a legal certainty instrument, generally binding across the EU and commonly described as valid for three years.
United States: CBP rulings issued under 19 CFR Part 177 can have binding effect as an official position within the regulatory framework.

9) Country-specific code mapping table (HS6 to national subdivisions)

Map HS6 to Japan statistical codes, the US HTS, EU CN, and other local subdivisions as needed.
Even if HS6 is the same, national subdivisions may change duty rates or regulatory requirements. Audits often become messy when teams mix “which country’s code” is being discussed, so a mapping table helps.

10) Change control log

Record when, why, who, and what changed.
Track specification changes, material changes, use changes, HS amendments, and updated authority guidance.
Audits look backward, so proving that the decision was reasonable at the time is often decisive.


4. How to write the classification memo

Audit-proof writing is short and follows the right sequence

A classification memo should work for customs readers and for internal audit teams. Fix the structure.

A. One-page conclusion summary

  1. Product overview (use, materials, function, configuration)
  2. Final HS code (HS6 and national subdivision)
  3. Which GRI was applied
  4. Key facts that determined the decision (for example, principal function, material ratio, set composition)
  5. Key sources (notes, Explanatory Notes, presence or absence of advance rulings)

B. Detail section in GRI order

GRI 1
Confirm heading wording and relevant notes
GRI 2
Check whether unfinished goods, unassembled goods, or mixtures are relevant
GRI 3
If multiple headings could apply, document the logic (more specific description, essential character, and so on)
GRI 4 to 6
Only add when needed, with a clear reason

This skeleton follows the structure of the GRI itself.


5. When you should seek an advance ruling

Do not do it “whenever uncertain”; decide by conditions

Advance rulings have a cost, so it is more realistic to prioritize them for high-risk cases.

Duty-rate differences are large and misclassification hits profit directly
Import controls or licensing requirements are involved
You have many similar products and internal practice is inconsistent
You have already received customs questions or comments in the past
It is a new product with no precedent

Japan Customs describes written advance rulings and explains the process and usage conditions for written responses.
The EU positions BTI as a tool for legal certainty.
CBP’s 19 CFR Part 177 sets the framework for requesting rulings and their effect.


6. Do not miss country-specific record retention periods

If you do not keep it, you cannot defend it

An HS classification dossier must be readily retrievable, just like accounting records and entry documents. Retention rules vary by jurisdiction, for example.

United States: Recordkeeping is generally five years (19 CFR 163.4).
EU: Records must generally be kept for at least three years (UCC Article 51).
Japan: Importers are indicated to retain certain documents, including import declarations, for seven years in specified cases.

Operationally, many global companies standardize to the longest requirement to reduce audit risk across regions.


7. Common failure patterns and how to fix them

The ways dossiers collapse in audits are predictable

Failure 1: Using the supplier’s HS code as-is

Fix
Treat supplier codes as references only. Always tie your conclusion to your own product facts and a GRI-based memo.
Record the supplier’s code and why you did not adopt it in the alternative classification analysis.

Failure 2: Deciding based only on keyword search results

Fix
Search is a starting point. Finalize using the legal notes and heading wording.
Use Explanatory Notes as a structured validation step, not as the only basis.

Failure 3: Mixing national subdivision codes across countries

Fix
Separate HS6 and national subdivisions in writing.
Include the country mapping table as a fixed dossier component.

Failure 4: Changes in product specifications are not reflected

Fix
Make the change control log mandatory.
Trigger reclassification when materials, use, or set configuration changes.


8. Conclusion

Audit-ready companies standardize “explainable classification”

What truly helps in audits is not heroic verbal explanation. It is having a standardized set: a GRI-ordered classification memo, evidence of the product’s real characteristics, a documented analysis of alternative headings, and a clear link to advance rulings or authoritative materials where available.

A practical shortest path looks like this.

  1. Build the 10-piece dossier for your top 20 items first
  2. Fix the memo template and write in GRI order
  3. Consider advance rulings for high-risk items
  4. Formalize retention and change control

Customs authorities make the final classification decision. The best a company can do is maintain a system where its determination was reasonable at the time, reproducible, and supported by evidence. Companies that achieve this typically reduce audit time and cost significantly.

Stop the Guesswork: How HSCF Turns HS Code Headaches into Trade Wins

Here is a polished, catchy, and approachable English version of your blog post. I have restructured it to grab the reader’s attention immediately and used formatting to make it highly scannable for busy trade professionals.


Do any of these scenarios sound a little too familiar in your daily trade operations?

  • The “Deadlock”: You’ve been staring at a product for an hour and just cannot finalize the HS code.
  • The “Knowledge Silo”: Everything grinds to a halt unless you ask your external customs broker or that one specific “guru” in the office.
  • The “FTA Time-Suck”: Origin work for FTAs or EPAs takes forever because verifying Tariff Shift (CTC) rules eats up your entire day.

Classification shouldn’t be a bottleneck. That’s why we built HSCF (HS Code Finder)—a decision-support tool that blends cutting-edge AI with expert-level trade know-how to take the weight off your shoulders.

Here is how HSCF is changing the game for trade compliance teams.


Think of HSCF as your digital trade consultant. By inputting product names, specs, or even photos, the system uses AI to replicate the expert thought process, providing you with high-probability HS code candidates and—more importantly—the logic behind them.


One of the biggest fears with AI is the “Black Box”—getting an answer without knowing why. HSCF solves this by being completely transparent.

  • Current & Future Ready: Based on HS 2022, with planned support for HS 2028.
  • Legal Backing: It doesn’t just give a number; it cites the General Rules of Interpretation (GRI), Section/Chapter notes, and WCO Explanatory Notes.
  • The “Why” and “Why Not”: It explains why a specific code was chosen and why other similar codes were excluded.

The Benefit: You get an “explainable” HS code that is ready for audits, customs inquiries, or Chamber of Commerce certifications.

Trade data is rarely perfect. HSCF is designed to handle the messy reality of the field.

  • Natural Language: Search using plain Japanese or English (e.g., “Rubber gasket for electric vehicles”).
  • Visual Search: Upload a smartphone photo, a technical drawing, or a spec sheet.
  • Instant Analysis: A single photo can produce estimated codes for Japan, the U.S., and the EU, along with confidence percentages.

In the real world, “HS6” is rarely enough. Different countries have different subheadings, and different trade agreements use different HS versions.

  • Destination Accuracy: Identify national subheadings (7th digit and beyond) to see applied tariff rates early.
  • Time Travel for FTAs: Using correlation tables, HSCF helps you identify the HS code version required at the time a specific FTA entered into force—a lifesaver for origin rule checks.

If the information is too vague, HSCF doesn’t just guess. It acts like a consultant by providing a Checklist of Missing Info.

It might ask:

“Is this material EPDM or PTFE?” or “Is the structure foamed or non-foamed?”

This makes gathering info from your engineering or design teams much faster and more professional.

HSCF is a support tool, not a final authority. We believe the final decision belongs to the compliance professional.

By providing a rock-solid rationale, HSCF becomes your best ally when:

  1. Discussing classifications with customs brokers.
  2. Defending your position during a customs audit.
  3. Standardizing internal compliance reviews.

HSCF turns HS classification from a “solitary headache” into a shared, systematic process. No more relying on one person’s intuition; instead, your whole team can work from a unified, AI-enhanced knowledge base.

If HS classification is slowing down your FTA utilization or pushing your compliance team to their limit, it’s time to remove the bottleneck.

Ready to see it in action?

HSCF is more than just a search bar—it’s the future of trade compliance.