Automating Reasonable Care Documentation for HTS Classification
What changed: Separated API codes and duties from Researcher/GingerOS reasoning reports; removed numeric-confidence and automatic-compliance claims, and corrected statutory penalty limits.
Under 19 U.S.C. 1484, the importer of record must use reasonable care in providing classification, value and other information needed for CBP to assess duties and enforce the law. CBP's checklist asks about the resources and procedures used, including verification of automated classification systems. No report format or vendor alone satisfies the standard [1] [2].
In this post
- What Records Should the Workflow Preserve?
- Which GingerControl Product Supplies Which Record?
- How Should You Review Uncertain Classifications?
- How Do You Keep Research Connected to the Filed Entry?
- Does Better Documentation Determine the Penalty Tier?
- How Do You Start a Documentation Process?
- Frequently Asked Questions
- References
The AI classification and reasonable care documentation guide focuses on the reasoning and review evidence left behind by the tool.
What Records Should the Workflow Preserve?
Keep the product description and supporting specifications, candidate codes and relevant legal notes, the reasoning for the selected code, the source rulings reviewed, and the reviewer’s decision. Record changes to facts or conclusions and retain the approved version used for a particular entry. Distinguish a suggested code from an approved filing decision.
Which GingerControl Product Supplies Which Record?
The Classification Researcher, in GingerLite, asks for missing product facts and records GRI reasoning, Section and Chapter Notes and relevant CROSS rulings for one product per case. GingerOS supports company-wide classification and rechecks with reasoning in the customer’s workflow. The API takes English descriptions and returns a 10-digit code and U.S. duty layers effective when called, up to 120 items per batch by default. Your system must retain its input and response; the API does not return the research report.
How Should You Review Uncertain Classifications?
Review competing headings and the facts that would decide between them. Ask for missing specifications and record the reviewer’s conclusion. GingerControl does not show a numeric confidence score. Do not automatically approve a code because a software output appears confident, or treat an internal accuracy percentage as evidence that a particular entry is correct.
Turn these checks into trade compliance internal controls and SOPs with named owners, documented approvals and retained evidence.
How Do You Keep Research Connected to the Filed Entry?
Compare the approved code and origin with the entry actually filed. If a broker or reviewer changes a code, preserve the change and its reason. Recheck when product facts, the schedule or relevant rulings change. For a catalog, that is a GingerOS workflow; for day-to-day individual research, use GingerLite. AD/CVD scope is a separate check and is not calculated by GingerControl.
Does Better Documentation Determine the Penalty Tier?
No. The facts and culpability determine it. Under 19 U.S.C. 1592(c), revenue-affecting negligence is capped at the lesser of domestic value or twice the lawful duties, taxes and fees lost or potentially lost; gross negligence uses four times that loss with the same domestic-value cap. The 20% and 40% dutiable-value limits apply when the violation does not affect assessment; fraud has a domestic-value ceiling [3]. Records can support review and mitigation, but do not automatically keep a case in the negligence tier.
How Do You Start a Documentation Process?
Choose a representative set of your own products and check whether the facts, reasoning and approval can be retrieved. Define review responsibilities and triggers for changed products or rules. Pilot the workflow, test the research against qualified review and retain unresolved questions. Set sampling and review levels to your risks; there is no universal percentage that proves reasonable care.
Apply the reasonable care test for AI trade compliance before treating an AI-generated code as a defensible classification record.
Frequently Asked Questions
Does an API call produce a GingerControl reasoning report?
No. The API returns a code and current duty layers. The reasoning report comes from the Classification Researcher or a GingerOS classification workflow.
Does the Classification Researcher classify a whole catalog at once?
No. GingerLite research is one product per case. Catalog-wide batch classification belongs in GingerOS.
Does GingerControl give a numeric confidence score?
No. Review the candidate headings, product facts and reasoning rather than setting a threshold on an unpublished score.
Does an audit-ready report prove reasonable care?
No. It supports the review file. The importer’s conduct, product facts, procedures and verification still matter; CBP does not certify compliance merely from the presence of a report.
Which API date applies to duty layers?
The API returns the layers in force when called. The Tariff Calculator takes an entry date; its output should be stored with that date and the confirmed code and origin.
Can documentation prevent gross-negligence penalties?
Documentation can be relevant evidence, but cannot guarantee a culpability finding or a particular penalty. The statute and actual facts govern [3].
Does a correct code settle AD/CVD scope?
No. An order’s scope and producer or exporter details may require separate review. GingerControl does not calculate AD/CVD.
Can Trade Advisory help design the process?
Yes. Trade Advisory can help with classification review, SOPs and related compliance questions, quoted for the required scope. The importer and its authorized filer retain the entry decision.
References
- U.S. Code, 19 U.S.C. 1484: importer-of-record duties.
- CBP, Reasonable Care informed-compliance publication: classification procedures, consulted resources and verification of automated systems.
- U.S. Code, 19 U.S.C. 1592: culpability and statutory penalty limits.
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




