A licensed customs broker we work with told us a story last fall. A new client — a Shopify merchant doing about $4M a year in housewares from China — sent over their "tariff documentation" the day before their first entry filing. It was a Google Sheet with seven columns. Product name, SKU, HTS code, MFN rate, Section 301 rate, total duty, "notes." About 140 rows.
The broker spent forty-five minutes on it and sent back a list of fourteen questions. Where did the HTS codes come from? Which version of the HTSUS? Was there a CROSS ruling supporting any of these? What was the substantial transformation analysis on the products listed as "Vietnam origin"? Were there any Section 301 exclusions being claimed? Why did three of the rows have the same MFN rate as Section 301 rate (impossible — these are independent layers)?
The merchant didn't have answers to most of the questions. The broker filed the entries anyway, on the merchant's reasonable-care representation, but flagged the file as needing structural cleanup. Three weeks later one of those entries got pulled for a Customs and Border Protection valuation review. The merchant spent six weeks reconstructing documentation that should have been built before the first entry.
This is a piece about what the cleaned-up version looks like. Not in theory — in actual practice. The kind of file that, if a broker opens it five minutes before filing, the broker can sign off without sending fourteen questions back.
What a broker is actually checking for
Before we get to the format, it's worth being clear about what a customs broker is doing when they review your packet. A broker is not double-checking your math. A broker is checking five things:
Classification defensibility. Is the HTS code one a CBP officer would also reach? Is there a paper trail from the General Rules of Interpretation to the specific 10-digit subheading?
Valuation correctness. Is the dutiable value the right one — transaction value, with appropriate additions for assists, royalties, packing? If first sale, are the conditions actually met?
Origin substantiation. If origin is anything other than the country of manufacture, can substantial transformation be documented?
Special program eligibility. Is the right Section 301 list flagged? Is any active exclusion being claimed via the right 9903.88.xx code? Are AD/CVD orders cleared?
Reasonable care. Above all, can the importer demonstrate they took reasonable care to get the entry right? The "reasonable care" standard is the legal hook for importer responsibility under 19 U.S.C. § 1484.
A broker-ready packet answers all five questions before they're asked.
The format
Here is the template we use internally and have shared with brokers we work with. It fits on one page per SKU. It can live in a spreadsheet, a Notion database, an Airtable, or a workspace tool — the format matters less than the discipline.
SKU classification record (one per active product)
1. Product
- Description (the description that goes on the commercial invoice)
- SKU and internal product code
- Material composition, weight, dimensions
- Principal use
- Any special features that affect classification (e.g., Bluetooth, lithium battery, contains controlled substance)
2. Classification
- Candidate HTS code (10-digit)
- Source: USITC HTS URL, retrieval date, HTSUS revision number
- GRI reasoning: one paragraph on which rule applied and why
- Supporting CROSS rulings: ruling number, URL, brief note on what each ruling supports
- Alternative classifications considered, and why rejected
3. Origin
- Country of origin
- Country of export (if different)
- Substantial transformation analysis (if relevant)
- Supplier/manufacturer name and address
- Supporting documentation: supplier declaration, mill certificate, photos, etc.
4. Valuation
- Transaction value method (basic, first sale, computed, deductive, fallback)
- Goods value at FOB / CIF / EXW (specify Incoterm)
- Currency and exchange rate basis
- Statutory additions: assists, royalties, packing, commissions, proceeds of subsequent resale
- Freight and insurance: separately stated and provable
5. Duty layers (each with source URL and retrieval date)
- MFN rate from HTSUS
- Section 301 list and rate (with 9903.88.xx if exclusion claimed)
- Section 232 exposure
- AD/CVD case status (search ACCESS, search ITC DataWeb)
- Section 122 / IEEPA / other Chapter 99 layers
6. Shipment context
- Quantity and unit of measure
- Quota check
- PGA admissibility (FDA, FCC, CPSC, USDA, EPA — whichever apply)
- Importer of record bond status
- Country-specific entry requirements
7. Open questions
- Anything not resolved, flagged for broker or counsel
- Confidence rating (high / medium / low) on the classification
8. Disclaimer "Planning estimate. Final classification and duty determined at entry. Not legal advice."
Every cell has a source. Every source has a date. If something can't be sourced, it's flagged in section 7, not papered over with a guess.
A worked example
Let's run through what one of these records looks like for an actual SKU. Bluetooth wireless earbuds, no microphone, sourced from a factory in Shenzhen, FBA inventory destined for an Amazon warehouse in Riverside.
1. Product. Wireless Bluetooth earbuds, model XYZ-100, audio-only (no microphone), USB-C charging case, 5-hour battery life, plastic housing with silicone tips, 60g per pair packaged. Principal use: personal audio reproduction (podcasts, music) paired with smartphone or tablet. Contains lithium-ion battery (relevant for FCC, DOT hazmat documentation).
2. Classification. Candidate HTS: 8518.30.2000 ("Headphones and earphones, whether or not combined with a microphone, and sets consisting of a microphone and one or more loudspeakers: Other"). Source: hts.usitc.gov, Revision 29 (2025), retrieved [date]. GRI reasoning: GRI 1 — product is squarely described by 8518.30 based on principal function of audio reproduction; alternative classification at 8517.62.0090 (data transmission apparatus) was considered but rejected because principal function is audio output for the wearer, not data transmission. Supporting rulings: N331416 (Stealth gaming headset, same heading), G89845 (consumer headset, same heading at 4.9% rate), NY J86357 (component-level classifications consistent with 8518). Alternative considered: 8517.62.0090 — rejected per GRI 3(a), 8518 is the more specific heading.
3. Origin. China (Guangdong province, factory in Shenzhen). Supplier: [supplier name and address]. Supplier declaration on file. No substantial transformation in third country.
4. Valuation. Transaction value method (basic). FOB Shenzhen, $12.40 per unit, 5,000 units = $62,000 invoice value. Currency USD on invoice. No assists, royalties, or commissions. Freight separately invoiced at $1,800 ocean LCL. Insurance separately invoiced at $620.
5. Duty layers.
- MFN: 4.9% per HTS 8518.30.2000, USITC source URL captured, retrieval date noted.
- Section 301: List 3 applicability — confirmed via USTR Section 301 lookup tool with 8-digit HTS, current rate 25%, no active 9903.88.xx exclusion claimed (verified against November 2025 extension list).
- Section 232: not applicable (not steel, aluminum, copper, or auto).
- AD/CVD: ACCESS portal search returned no active orders for this HTS heading covering this product description. ITC DataWeb search consistent.
- Other Chapter 99: none currently applicable.
6. Shipment context. 5,000 pairs, NUMBER unit of measure. No quota. FCC Part 15 verification on file (wireless device requirement). Lithium battery DOT documentation on file. Importer of record bond active and current.
7. Open questions. Confidence: high on classification (multiple supporting rulings, clear principal-function argument); medium on Section 301 exclusion review (verify with broker that no exclusion request from Q3 2025 wave covers this product family); high on AD/CVD (no active orders in the heading).
8. Disclaimer. Planning estimate. Final classification and duty determined at entry. Not legal advice.
That's the entire SKU record. It fits in about 350 words. A broker can review it in two to three minutes and sign off.
The spreadsheet that fails review
By contrast, here's the row from the failed spreadsheet we opened with:
| SKU | Product | HTS | MFN | 301 | Total | Notes |
|---|---|---|---|---|---|---|
| XYZ-100 | Bluetooth earbuds | 8518.30 | 4.9% | 25% | 29.9% | China |
What's wrong with this row, beyond the obvious:
The HTS is 6-digit, not 10-digit. CBP doesn't classify at 6 digits. The duty rate at the 8-digit subheading might differ from the 6-digit shorthand.
There's no source URL or retrieval date for either rate.
There's no GRI reasoning or supporting CROSS ruling. If CBP asks why 8518.30 was chosen over 8517.62, there's no answer.
"China" as origin doesn't substantiate substantial transformation, supplier identity, or factory address.
There's no valuation detail — was this FOB or CIF? Are there assists or royalties?
No Section 301 exclusion check, no AD/CVD check, no PGA check, no bond status confirmation.
The "29.9%" total doesn't include MPF, HMF, or any other fees, and it implies (incorrectly) that the layers compound. They don't — MFN and Section 301 are both ad valorem on the same transaction value, so they're additive for percentage calculation, but they're calculated independently.
A broker reading this row sees seven issues. A CBP officer reviewing this entry sees most of the same issues. None of them are unfixable. All of them require the importer to reconstruct documentation under time pressure, which is the worst time to do it.
How to actually build the packet
Three operational suggestions, in increasing order of effort:
The minimum viable version. Start with an Airtable or Notion database, one row per active SKU, with the eight fields above as columns. Spend 20 minutes per SKU populating it. For SKUs you can't populate fully, mark them "needs review" rather than guessing. After the first 10 SKUs, the per-SKU time drops to about 5 minutes because most of the lookups are repeatable.
The middle path. Build the database, then commit to refreshing each SKU annually — once a year, re-pull the HTS source, re-check Section 301 status, re-confirm CBP CROSS for any new rulings on similar products. Tariff rates change. Rulings get superseded. A 2024 packet against 2026 entries is a paper trail that may no longer hold.
The serious version. Move the database into a workspace tool that captures source URLs and retrieval dates automatically as part of the workflow, exports a broker-ready summary on demand, and tracks the open-questions list across SKUs. This is what TariffsChart is designed to do — but the underlying discipline is what matters, not the specific tool.
The thing to recognize: the cost of building the packet up front is small compared to the cost of reconstructing it under audit pressure. Brokers can defend a well-documented entry. They cannot conjure documentation that doesn't exist.
The HS / HTS lookup and the landed-cost calculator both keep source URLs and retrieval dates by default, which means the packet builds itself as you work through each SKU. Export to share with a broker; keep internally as the audit trail.
Planning guide. Not legal advice. Reasonable care in import compliance is a legal standard with specific requirements; consult a licensed customs broker or trade counsel for entry-specific advice.
