- Assign a stable product and version identifier.
- Collect physical product evidence before accepting a code.
- Record all reasonable candidates and the legal path used to compare them.
- Save the current official source edition and date.
- Link origin, valuation, and additional-measure records without merging them into the classification conclusion.
- Retain broker input as advice or communication, not as an unexplained replacement for importer records.
- Version changes instead of overwriting prior decisions.
- Apply the retention period and retrieval method required for the importer’s role and records.
- Reopen the review after a trigger and document downstream corrections.
Guide
Importer HTS Classification Recordkeeping: What to Keep by SKU
Build an HTS classification file with product facts, origin, value, legal notes, rulings, broker communications, entry records, decision history, retention dates, and change controls.
Answer Summary
Preparation checklist
A bare HTS number does not explain what product was reviewed, which edition was used, or why the result was chosen.
Classification, origin, value, Chapter 99, AD/CVD, documents, and entry history should be linked but remain distinguishable.
Records need ownership, versioning, retention, and change triggers so later entries can be traced without silently rewriting history.
Required fields or decision table
Fields to prepare before the document draft
| Field or decision | What to prepare |
|---|---|
| Product master | SKU, model, description, material, function, construction, dimensions, composition, components, images, specification, and variant differences. |
| Supplier and origin | Manufacturer, producer, exporter, seller, factory, country-of-origin evidence, and changes over time. |
| Classification analysis | Candidates considered, legal notes, explanatory materials, ruling comparisons, why-not notes, final working code, status, and reviewer. |
| Source version | Official source URL, HTS edition/revision, lookup date, effective date, and downloaded evidence where appropriate. |
| Duty and measure layer | Base rate, Chapter 99, preference, Section 301/232, AD/CVD screening, and the source/date for each. |
| Valuation and transaction | Purchase order, invoice, payment, assists, packing, commissions, royalties, related-party facts, freight, and insurance records. |
| Entry and communication | Entry summary, broker instructions, corrections, requests, rulings, protests or decisions, and agency correspondence. |
| Governance | Owner, approver, retention end date, version, superseded record, affected SKUs/orders, and event/time recheck triggers. |
Step-by-step preparation
How to prepare the draft
Ecommerce example
How this looks in a seller workflow
A seller has one phone-accessory title covering plastic cases, leather folios, and battery cases. A spreadsheet stores one code for all variants.
The improved record separates the physical variants, candidate HTS analysis, origin, supplier, source revision, additional measures, invoices, and review status. The battery case is not allowed to inherit the passive case record merely because the marketplace parent listing is shared.
- Separate physical variants.
- Store candidate reasoning.
- Date official sources.
- Link origin/value/measure records.
- Version changes.
- Retain entry evidence.
Verification checklist
Review the record before it enters a shipment or filing workflow
- The record identifies the exact SKU/version.
- Product evidence supports the description.
- Competing candidates and legal notes are retained.
- Source revision and lookup date are present.
- Origin, value, and additional measures are separately supported.
- Broker and agency communications are linked.
- Approver and status are visible.
- Retention and retrieval rules are assigned.
- Changes preserve prior history and identify affected transactions.
Source-backed checks
What external guidance supports this workflow?
- 19 CFR Part 163Current CBP recordkeeping regulations and required-record framework.
- CBP recordkeeping publicationOfficial informed-compliance material on importer recordkeeping.
- USITC HTSOfficial current classification text and revision information.
- CBP CROSSOfficial customs rulings used for fact-pattern comparison and decision support.
Internal workflow links
Use the same catalog data in the next review step
- Create a Classification CasePaid workspace: keep product facts, candidates, risk findings, source evidence, and exports together.
- Run a Catalog ReviewPaid workspace: process repeated SKUs or platform CSV rows with server-side credits and review history.
- Export Reviewed RecordsPaid workspace: export reviewed fields for TariffCatalog, Shopify, WooCommerce, or Amazon workflows.
- Compare PlansCompare one-time and monthly credits for repeated customs-data work.
- Official SourcesOpen the government tariff, trade-remedy, origin, or recordkeeping source before filing.
- MethodologyReview the source, candidate, estimate-only, and correction boundaries used by TariffCatalog.
- CorrectionsReport an outdated source, unclear statement, or workflow problem for review.
Common mistakes
What to avoid
- Keeping only the code.
- Using one record for materially different variants.
- Omitting the source revision.
- Combining classification, origin, and value into one unsupported conclusion.
- Overwriting old decisions.
- Treating broker email as the whole file.
- Leaving retention ownership undefined.
- Failing to identify affected past and open transactions after a correction.
Editorial
Editorial review note
Written by the TariffCatalog Editorial Team for ecommerce document preparation workflows. The page is designed as a preparation checklist, not a filing outcome.
Maintained by Ryan Cole, with review focused on ecommerce catalog, document, and source-check workflow clarity.
Document requirements may be required differently by carrier, destination, shipment value, and product facts. Use the methodology, sources, and corrections pages to understand how the page is maintained.
Official source note
References to verify
Use official sources, carrier guidance, postal operator rules, and destination requirements to verify before filing or shipping.
USITC HTS
Use this official source when checking final classification, duty treatment, or customs requirements.
CBPUse this official source when checking final classification, duty treatment, or customs requirements.
EU TARICUse this official source when checking final classification, duty treatment, or customs requirements.
UK Trade TariffUse this official source when checking final classification, duty treatment, or customs requirements.
FAQ
Common questions
Is an HTS number alone enough?
No. Keep the facts, reasoning, source, status, and related transaction evidence.
Should competing candidates be retained?
Yes. They explain what was considered and why the working result was selected.
Why save the HTS revision?
It identifies the official text in force when the review was completed.
Should broker emails be kept?
Yes, as part of the communication trail, while retaining the importer’s own supporting records.
Can marketplace variants share one record?
Only when the physical and relevant classification facts are genuinely the same.
How long should records be retained?
Apply the current legal retention rule for the record and importer role; consult the official recordkeeping source.
What should happen after a code changes?
Version the decision, identify affected records and orders, update approved exports, and evaluate whether any correction path is needed.
Disclaimer
TariffCatalog provides informational tools and preparation workflows only. Verify final classification, rates, document requirements, and filing treatment with official sources or licensed professionals.