- Assign one stable product or SKU identifier.
- Collect the physical specification and manufacturing facts directly from source records.
- Identify producer and exporter legal entities, not only the marketplace supplier.
- Save the current HTS candidate and why it was selected.
- Download or link the full order and scope text; capture the date and case number.
- Match each inclusion, exclusion, threshold, or qualifier to a documented product fact.
- Add current CBP instructions and preserve the party/date match.
- Record unresolved questions and route them to the responsible qualified reviewer.
- Export the evidence summary with the shipment or purchasing approval record.
AD/CVD Scope Review Records: An Importer Preparation Checklist
Build an auditable AD/CVD scope-review file with product specifications, supplier identities, origin records, order language, rulings, deposit messages, and decision ownership.
Preparation checklist
A scope-review file is a comparison record, not a rate screenshot.
The strongest file ties legal wording to measurable product facts and named supply-chain parties.
Missing facts should remain visible as unresolved questions; they should not be converted into a low-risk conclusion.
Fields to prepare before the document draft
| Field or decision | What to prepare |
|---|---|
| Product specification |
|
| Manufacturing record | Identify production steps, plant, inputs, and operations that support origin and product-scope facts. |
| Supply-chain identities | Legal manufacturer, producer, exporter, seller, and importer names, with relationships and alternate trade names. |
| Classification record | Current HTS candidate, source date, supporting facts, competing candidates, and reviewer status. |
| Legal source set | Order, scope wording, amendments, administrative-review notices, relevant scope or circumvention rulings, and current implementation messages. |
| Entry evidence | Entry date, invoice, purchase order, quantity, value, origin declaration, and broker communication. |
| Decision note | Dated conclusion, assumptions, unresolved issues, owner, next review date, and reason for escalation or non-escalation. |
| Change triggers | Specification, manufacturing site, supplier party, origin, HTS, order language, or message changes that force a new review. |
How to prepare the draft
How this looks in a seller workflow
A seller imports two visually similar kitchen products from different plants. One uses cast aluminum and the other stamped steel, while both share a marketing title.
A single supplier declaration is not enough. Each SKU receives its own material, process, dimensions, plant, producer/exporter, origin, HTS candidate, and scope comparison. The records can then support a real difference or reveal that a review is still incomplete.
- Separate SKU variants.
- Separate producer/exporter entities.
- Map scope terms to measured facts.
- Keep source dates and case numbers.
- Escalate gaps before entry.
Review the record before it enters a shipment or filing workflow
- Every SKU has a physical specification.
- Origin and manufacturing site are supported.
- Producer/exporter names match official records.
- Scope language is retained in full.
- Relevant rulings and amendments are linked.
- The CBP message is current for the entry period.
- Assumptions and unresolved facts are explicit.
- Decision owner and next review trigger are recorded.
What external guidance supports this workflow?
- Commerce ACCESSOfficial case and proceeding search.
- CBP AD/CVD public messagesImplementation and cash-deposit messages searchable by case and other criteria.
- USITC AD/CVD HandbookOfficial overview of antidumping and countervailing duty investigations.
- USITC AD/CVD in the HTS FAQClarifies the boundary between the HTS and AD/CVD orders.
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.
What to avoid
- Saving only a rate screenshot.
- Using a sales title instead of technical facts.
- Combining different variants into one scope conclusion.
- Leaving producer/exporter identity blank.
- Dropping exclusions or technical qualifiers from the scope text.
- Failing to date the source set.
- Treating an unresolved gap as clearance.
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.
References to verify
Use official sources, carrier guidance, postal operator rules, and destination requirements to verify before filing or shipping.
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.
Common questions
What is an AD/CVD scope review?
It compares actual merchandise facts with the legal scope of an AD/CVD order.
Is a supplier declaration enough?
No. It can be evidence, but it should be checked against product, origin, party, and official-source records.
Why save product drawings or specifications?
Technical scope terms often depend on measurable construction, material, processing, or dimensions.
Should each SKU have a separate record?
Separate materially different variants and supply chains so facts are not silently inherited.
Do I need the producer and exporter names?
Yes, because instructions can be company-specific.
What is a scope ruling?
It is an official determination addressing whether particular merchandise falls within an order scope.
How often should the record be updated?
Update after relevant product, supplier, origin, classification, order, ruling, or instruction changes.
Disclaimer
TariffCatalog provides informational tools and preparation workflows only. Verify final classification, rates, document requirements, and filing treatment with official sources or licensed professionals.
