Sample
What a defensible classification packet looks like.
Every CrossCode export includes the HTS code, the CBP ruling that supports it, the GRI rule applied, and the broker's approval decision — formatted for attachment to the entry file. Below is one line item from a sample packet, with each field explained.
CrossCode Classification Audit Packet
Invoice #INV-2024-1047 · exported 2024-03-14 09:22 UTC · reviewed and accepted by J. Martinez, CHB #123456
Laptop Computer, 14″, Intel Core i7, 16GB RAM, 512GB SSD
This packet constitutes the classification record for the referenced entry. Generated by CrossCode. Approved by licensed CHB on record.
The full 10-digit statistical suffix, not just the 6-digit subheading. CBP entries require the 10-digit number; stopping at 6 or 8 digits is one of the more common reasons a packet gets kicked back during a focused assessment.
Names the specific General Rule of Interpretation that drove the classification, not just the resulting code. An examiner can follow the reasoning step instead of taking the code on faith.
A ruling number from CBP's own CROSS database for a materially similar good. This is the single highest-value line in the packet — it shows the classification is consistent with how CBP itself has ruled, not just with the importer's interpretation.
The named, licensed customs broker who reviewed and accepted the code, with their CHB license number recorded elsewhere in the full packet. This is what makes the packet a broker work product rather than unreviewed software output.
The applicable duty rate at the time of classification, including any Section 301 or other trade-remedy add-ons — so the packet doubles as the record of what duty calculation the classification was based on.
Field values above are from a representative sample, not a real entry. Every code CrossCode returns is reviewed and either accepted or corrected by a licensed customs broker before the packet is finalized.