DEV Community: Aadarshkumar

How I’d Structure an AD/CVD Compliance Workflow as a Data Problem

Aadarshkumar — Wed, 26 Aug 2026 11:20:43 +0000

AD/CVD compliance isn't just an HTS-code lookup. A useful software workflow needs to connect product attributes, HTS classification, AD/CVD orders, written scope, case numbers, rates, country, and current regulatory information. The goal is to turn scattered trade data into something applications can actually use.

If you're building software for procurement, logistics, landed-cost calculation, or international trade, there's an easy assumption to make:

HTS code → duty rate

That's useful, but it isn't the complete picture.

A product imported into the U.S. can also be subject to Antidumping (AD) or Countervailing Duties (CVD).

That creates a much more interesting data problem.

Don't model AD/CVD as a boolean

A system that stores:

product_id: 12345
hts: XXXXXXXX
ad_cvd: true

isn't giving the compliance team much to work with.

A better record might need to associate the product with:

Product
├── HTS classification
├── Country of origin
├── Manufacturer
├── Exporter
├── AD/CVD case
├── Order
├── Written scope
├── Applicable rate
├── Effective/current status
└── Source + verification date

The reason is simple: an HTS number can help identify a potentially relevant AD/CVD order, but it doesn't automatically prove that the merchandise is covered.

The written scope has to be evaluated against the actual product.

This is one of the most important distinctions covered in this AD/CVD compliance guide for importers.

Product data becomes important

A generic description like:

Steel component

may not contain enough information for meaningful scope analysis.

Depending on the order, relevant attributes could include:

Material
Dimensions
Physical characteristics
Chemical composition
Manufacturing process
Product configuration
Country of origin
Exclusions

So if you're designing the underlying schema, product specifications shouldn't be treated as irrelevant metadata.

They may be critical to the compliance decision.

A practical processing pipeline

A software workflow could look something like:

Product Data
     ↓
HTS Classification
     ↓
Potential AD/CVD Discovery
     ↓
Scope Evaluation
     ↓
Case Identification
     ↓
Rate Verification
     ↓
Current Status
     ↓
Compliance Record

The output should ideally be more informative than:

AD/CVD = YES

It could instead return the relevant case, order, rate, scope information, supporting source, and verification date.

That gives downstream systems something they can actually use.

Why APIs can help

For a company managing hundreds or thousands of imported products, manually researching every potential AD/CVD issue isn't particularly scalable.

Structured trade data can potentially feed:

Landed-cost calculators
Procurement platforms
ERP systems
Supplier-management tools
Customs workflows
Internal compliance dashboards

The API shouldn't be treated as a replacement for legal or compliance judgment.

It's a way to make relevant data easier to retrieve and integrate.

Don't forget that the data changes

Another problem is treating the rate as a permanent product attribute.

AD/CVD proceedings can change over time. Administrative reviews and other actions can affect duty collection and applicable rates.

That means a production system should think about data freshness and source tracking, not just data retrieval.

For example:

Rate: X%
Source: Government proceeding
Verified: YYYY-MM-DD
Case: XXXXX

is considerably more useful than storing:

Rate: X%

Final thought

The interesting part of AD/CVD compliance from a software perspective isn't simply finding a tariff number.

It's connecting:

product → classification → scope → case → rate → current status

and keeping that information usable as part of a larger workflow.

If you're building software around international trade, procurement, or landed costs, that's a much more useful way to think about AD/CVD than treating it as another column in an HTS table.

Further reading: AD/CVD duties and compliance guide

Why Product Classification Is an Automation Problem

Aadarshkumar — Fri, 14 Aug 2026 10:29:19 +0000

Product classification sounds like a lookup problem.

For a small catalog, it might be.

For thousands of products, it's a data and workflow problem.

A product can have an international HS code, but that doesn't necessarily mean the same complete classification should be used everywhere. In the U.S., HTS is used for imports and Schedule B for exports. They share the six-digit HS foundation but can differ beyond that.

That creates an interesting automation challenge.

A classification system may need to process:

Product descriptions
Materials
Technical specifications
Intended use
Supporting documents
Previous classification decisions
Country-specific requirements

Simply matching product names to codes isn't reliable enough for complex catalogs.

A better workflow can combine automated analysis with human review: software handles repetitive processing and organization, while specialists validate important classification decisions.

The distinction between the underlying classification systems is explained in HS Code vs HTS Code vs Schedule B.

The real engineering challenge isn't just generating a classification.

It's building a system where classifications are searchable, reviewable, auditable, and maintainable over time.

That's where product classification starts looking less like a lookup table and more like a serious data-management problem.

Why Tariff Updates Are Becoming a Data Problem for U.S. Importers

Aadarshkumar — Tue, 11 Aug 2026 05:24:01 +0000

When people hear about a new U.S. tariff, the first question is usually: How much is the duty?

For companies managing international trade, that is only part of the problem.

The harder question is: Which products are affected, and what tariff treatment should be applied to each one?

The 2026 USTR Section 301 tariff action affecting 60 countries and economies is a good example of this challenge. Different tariff treatments, country-of-origin rules, product classifications, and potential exclusions can turn a regulatory announcement into a fairly complicated data-management task.

Tariff compliance depends on connected data

An importer doesn't normally work with tariff rates in isolation.

A compliance team may need to connect:

Product → HTS classification → Country of origin → Tariff treatment → Duty calculation → Landed cost

If one part of that chain is outdated, the final calculation can also be wrong.

For a company managing a few products, manually checking this information may be manageable. For organizations handling thousands of SKUs across multiple suppliers and countries, it becomes much harder.

Why automation matters

This is where trade compliance software becomes interesting from a technology perspective.

Instead of asking a compliance professional to repeatedly search regulatory sources, update spreadsheets, and manually recalculate costs, a centralized system can help organize classification, tariff, and regulatory information.

The objective isn't simply automation for its own sake.

The real benefit is reducing the gap between a regulatory change being announced and the company's operational data reflecting that change.

That matters because tariff changes can influence more than customs entries. Procurement teams may need to reassess suppliers, finance teams may need updated landed costs, and commercial teams may need to reconsider pricing.

The 2026 Section 301 update illustrates the problem

The latest USTR action includes 10% and 12.5% tariff treatments for affected economies, with specific treatment for certain trading partners and exclusions that importers need to evaluate.

That means businesses shouldn't simply update a single global tariff value.

They need to understand the relationship between product data, origin, classification, and the applicable tariff treatment.

Borderline Genius provides a detailed breakdown of the 2026 USTR Section 301 tariff changes, including the affected economies, rates, and implementation details.

For trade compliance teams, the broader takeaway is simple: tariff monitoring is increasingly a data problem as much as a regulatory problem.

The companies that can keep product, classification, tariff, and cost data synchronized will have a much easier time responding when trade rules change.

How AI is Transforming Trade Compliance Workflows

Aadarshkumar — Fri, 07 Aug 2026 12:07:06 +0000

Exploring how automation and intelligent systems help businesses manage complex global trade requirements.

Global trade involves thousands of rules, regulations, and data points that businesses must manage before moving products across borders.

For many organizations, trade compliance is still handled through manual processes, spreadsheets, and disconnected systems. This creates challenges around accuracy, speed, and scalability.

Technology is changing this process.

AI-powered trade compliance software helps businesses automate complex workflows such as product classification, regulatory checks, documentation management, and trade data organization.

One major challenge in international trade is product classification. Incorrect HS codes can impact tariffs, customs clearance, and shipment timelines. Intelligent systems help teams improve classification accuracy by using structured trade data and automated workflows.

Modern compliance platforms also help businesses:

Monitor regulatory updates
Identify potential compliance risks
Manage import and export requirements
Improve operational visibility

For developers and technology teams, trade compliance is an interesting example of how software can solve complex real-world problems involving large datasets, changing rules, and global operations.

As businesses expand internationally, scalable automation becomes essential for managing compliance efficiently.

Borderline Genius is building AI-powered solutions that help organizations simplify classification, tariff management, and global trade compliance workflows.

How AI Automation Is Improving Trade Compliance in Global Logistics

Aadarshkumar — Mon, 03 Aug 2026 12:22:27 +0000

International logistics depends on thousands of decisions happening behind the scenes. From product information and documentation to customs requirements and tariff calculations, every shipment requires accurate data processing.

One of the biggest challenges in global trade operations is product classification. Freight forwarding teams need to determine the correct HS codes, understand regulatory requirements, and prepare accurate documentation before shipments reach customs.

Traditionally, this process has involved manual research, spreadsheets, and multiple reference sources. As shipment volumes grow, these workflows become difficult to maintain.

The Data Challenge Behind Customs Classification

HS code classification is a data-heavy process. Teams need to analyze product descriptions, compare classification rules, and consider country-specific regulations.

The difficulty is not only finding information but also applying the right logic consistently.

Common problems caused by manual processes include:

Different classification decisions for similar products
Longer processing times for complex shipments
Increased chances of documentation errors
Delays caused by missing compliance information

For logistics companies operating globally, these small inefficiencies can create significant operational challenges.

Where AI Fits Into Trade Compliance

AI-powered systems are changing how businesses handle classification and compliance tasks. Instead of depending entirely on manual searches, intelligent platforms can analyze product details, identify relevant classification information, and support faster decision-making.

Similar to other industries adopting automation, trade compliance technology focuses on reducing repetitive work while helping experts make better decisions.

AI can support areas such as:

Automated HS and ECCN code classification
Regulatory requirement analysis
Tariff and duty visibility
Document preparation workflows
Compliance risk identification

The goal is not to remove human expertise but to combine it with technology for better accuracy and efficiency.

Building Scalable Logistics Software

For developers and technology teams, logistics is an interesting example of how AI can solve complex real-world problems. Trade compliance involves structured data, changing regulations, and decision-making processes that require both automation and domain knowledge.

As global supply chains become more connected, software solutions that improve accuracy and reduce operational friction will continue to play an important role.

The future of logistics is not only about moving goods faster. It is also about making smarter decisions before those goods move.

Explore how AI-powered software for freight forwarders is helping modern logistics teams improve classification and trade compliance workflows.

Why Classifying a Machine Part Is Not as Simple as Calling It a Part

Aadarshkumar — Thu, 30 Jul 2026 13:11:47 +0000

A product description such as “machine part” sounds specific enough until someone actually has to assign an HS code to it.

That is where classification gets complicated.

A gearbox, mounting bracket, filter, bolt, motor, or replacement component may all be described internally as “parts,” but the Harmonized System does not classify goods based on the terminology used by a manufacturer or buyer.

The real question is: what is the article under the HS rules?

This distinction matters because the classification can affect customs duty, import requirements, regulatory controls, and the supporting documentation needed for a shipment.

Start With the Article, Not the Part Number
One common mistake in product classification is starting with the company’s internal product description.

A catalogue might call something a “pump assembly component” or “equipment spare part.” That description does not automatically make it a part for tariff classification purposes.

The first question should be whether the article is already described by a heading in its own right.

For example, an article that is itself a pump, motor, fastener, lock, or fitting may have to be considered under its own heading before the classifier even considers whether it belongs with a particular machine.

This is one reason product classification requires more than searching a database for similar words.

The Role of Section and Chapter Notes
The legal notes are often where the classification decision becomes clear.

For machinery and electrical equipment covered by Section XVI, Note 2 provides an important framework for determining how parts should be treated.

In simplified terms, the classifier needs to determine whether the component:

Is already covered by a heading in its own right
Is excluded or redirected by a Section or Chapter Note
Qualifies as a part of general use
Is solely or principally used with a particular machine
Falls into a residual parts provision
That sequence prevents a common mistake: jumping directly from “this belongs to a machine” to “therefore it must use the machine’s HS code.”

It does not necessarily work that way.

Parts of General Use Can Change the Entire Classification
Fasteners and other common hardware are a good example.

A bolt manufactured specifically for a piece of industrial equipment does not automatically become a classified “part” of that equipment.

Articles such as certain screws, bolts, nuts, washers, springs, locks, fittings, chains, and similar products can fall within the concept of parts of general use.

Their relationship with the final machine may therefore be less important than the fact that the HS specifically treats the article as a general-use product.

This is why a product’s material, construction, and physical characteristics need to be captured accurately during classification.

Parts and Accessories Are Not Always the Same Thing
Another issue is the assumption that a part and an accessory are interchangeable terms.

They are not.

Learn about Medium’s values
A component may be integral to the operation of an article, while an accessory may perform a supporting, adapting, or enhancing function without being essential to the basic operation.

The distinction becomes particularly important when dealing with classification provisions outside the machinery chapters.

So when a product team says, “This is just an accessory,” the classifier still needs to establish what the article actually does and how the relevant HS provisions treat it.

What About an Unassembled Product?
There is another layer that is easy to overlook.

A shipment may contain multiple components that have not yet been assembled. That does not automatically mean the goods should be classified as separate parts.

GRI 2(a) can extend a heading covering a complete article to an incomplete or unfinished article when it has the essential character of the complete article. It can also cover complete articles presented unassembled or disassembled.

That means the physical presentation of goods at the time of import can matter.

Simply shipping an article in several pieces does not necessarily change its tariff identity.

Classification Requires Better Product Data
This is where many businesses run into operational problems.

A classifier cannot reliably determine the correct HS code when the product record contains only:

“Spare part for machine.”

Useful classification data may instead include:

What exactly is the component?
What material is it made from?
What does it do?
What machine does it connect to?
Is it used exclusively or principally with that machine?
Is it capable of being used elsewhere?
Is it a complete article presented in an unassembled condition?
What technical specifications support the description?
The quality of the final classification is heavily influenced by the quality of the information provided at the beginning.

Why This Matters at Scale
For a company handling hundreds or thousands of SKUs, classification decisions cannot remain buried in individual emails or in the memory of one experienced classifier.

The reasoning needs to be documented.

A strong product classification record should capture not only the final HS code but also the facts and legal reasoning behind the decision.

That makes classifications easier to review, update, defend, and apply consistently across similar products.

For businesses dealing with complex international trade requirements, understanding the broader HS classification challenges, compliance risks, and role of technology in product classification is equally important.

For a deeper look at the challenges involved in modern HS classification and how technology can support the classification workflow, see this guide to HS classification and AI-powered classification.

The biggest lesson is simple: “part” is a commercial description, not a classification conclusion.

A reliable HS classification process starts with the actual article, applies the relevant legal notes and interpretation rules, and records the evidence supporting the final decision.