Planning Use SEO page 415

Schedule B vs HTS code: what exporters and importers mix up

Planning Use only. Broker review required for Entry Use.

Schedule B and HTS codes both come from the Harmonized System family, but they are used in different jobs. Schedule B is used for U.S. export reporting. HTS is used for U.S. import classification and duty work. Mixing them can create bad catalog data.

quick answer

For schedule b vs hts code, use Schedule B for export reporting questions and HTS for import duty and Entry Use review. If a supplier gives a six-digit HS code or a Schedule B code, do not treat it as a complete U.S. import classification without product facts and review.

facts to collect before drafting

• Product name, commercial description, composition, function, and intended use.
• Whether the task is export reporting, import duty planning, ecommerce catalog cleanup, or broker preparation.
• Country of origin, destination market, supplier HS code, Schedule B code, HTS candidate, and invoice value.
• Photos, spec sheets, product page, BOM, labels, and any prior customs documents.
• Whether the product is a part, set, kit, retail article, food, textile, electronics item, or mixed-material product.
• Shipment timing, purchase order status, and whether the code will feed ERP, Shopify, freight forwarder, or broker data.
• Which source was used: Census Schedule B search, USITC HTS, supplier paperwork, or a broker record.

missing facts

Ask what the code will be used for. A Schedule B code may be fine for export reporting but too shallow for import duty planning. Missing origin, material, function, and use facts should stop the record from being treated as an Entry Use answer.

HTS candidate notes

Start import work in the USITC HTS, not with a Schedule B export code. Use the supplier or Schedule B number only as a clue. Then build HTS Candidates with product facts, CROSS precedent checks, and missing-fact notes.

authority sources

• USITC HTS
• CBP CROSS
• 19 CFR 177.2
• USTR Section 301 tariff actions
• CBP ruling program

Use official sources for the record. Export and import lookups can point to related headings, but the duty file still needs HTS-specific review.

planning path

Create a small code-source table: code received, source, use case, digits, product facts supporting it, and gaps. Mark whether the code is export-only, import-planning only, or ready for Broker review.

If a marketplace, supplier, or ERP field stores one "HS code," add a note explaining which use case the field is meant to serve. That prevents a Schedule B export value from silently driving U.S. import duty estimates.

Rejected code paths are useful. Keep the Schedule B number in the file as a clue, but record why it did or did not support the HTS candidate path.

Save the source date.

related planning questions

• schedule b vs hts code
• Schedule B code vs HTS code
• HS code vs HTS code
• U.S. import HTS code lookup
• product classification record

questions importers ask

Can a Schedule B code be used for U.S. import duty?

Use it only as a clue. Import duty work needs HTS review and product facts.

Why do the numbers look similar?

They share Harmonized System roots, but U.S. import and export systems are not the same operational use.

What should I give my Broker?

Give the product facts, supplier code, Schedule B code if present, HTS Candidates, missing facts, and source links.

internal links

• /hts-code-lookup
• /classification-record
• /duty-surprise-scan
• /reasonable-care-file

planning boundary

This Schedule B vs HTS page is a planning artifact. It is not an Entry Use classification, not a binding ruling, and not a legal opinion. The importer remains responsible for reasonable care and must obtain broker or customs authority review before filing.