Planning Use SEO page 430

Reasonable-care file for tariff classification

Planning Use only. Broker review required for Entry Use.

A reasonable-care file is the record behind the classification decision. It should show what the importer knew, what it checked, what it could not confirm yet, and which sources shaped the review. The file does not move liability away from the importer. It makes the review trail easier to inspect.

quick answer

For tariff classification, a reasonable-care file should contain product evidence, Product Facts, Missing Facts, HTS Candidates, Authority Sources, rejected alternatives, duty-stack notes, and a review decision. Keep it Planning Use until broker or customs authority review is complete.

facts to collect before drafting

Product photos, invoice description, SKU, catalog page, spec sheet, and supplier code.
Materials, composition percentages, function, principal use, packaging, accessories, and set details.
Country of origin, manufacturing steps, and evidence for the origin claim.
Value facts, purchase terms, assists, and duty estimate already used by the business.
Prior entries, supplier explanations, broker notes, internal catalog fields, and related SKUs.
Any CBP ruling, tariff note, or source page that the team already relied on.

missing facts

Missing facts belong in the file, not in someone's inbox. If composition, function, origin, value, or supporting documents are absent, write that down and name the next source. A no-critical-missing-facts statement is fine only when the file explains why the remaining gaps do not affect the Planning Use path.

HTS candidate notes

List the strongest HTS Candidates and the facts supporting each one. Include rejected alternatives when they were plausible at first. A rejected path is useful when it explains why the importer did not simply accept a supplier code, marketplace field, or old catalog value.

authority sources

Use official sources as the file backbone. Blog posts, carrier tools, and marketplace exports can explain why a question came up, but they should not be the authority trail for the record.

planning path

Start the file before a code becomes operational data. Pull the supplier code, catalog field, invoice text, and product evidence into one page. Then write the candidate comparison, missing facts, source links, and review decision beside the duty-stack notes.

For repeat SKUs, keep version history. If the supplier changes material, packaging, origin, or included accessories, the old file should not silently cover the new product. That is where duty surprise often starts.

The file should be boring on purpose. A reviewer should be able to see the product, the facts, the gaps, the candidate paths, and the source trail without hunting through Slack messages or supplier folders. That is useful even when the review decision is to ask for more evidence.

Do not write the file as if it transfers responsibility. It does not. It shows the care taken before a decision was used. The importer still needs broker or customs authority review before Entry Use, and the record should say that plainly.

questions importers ask

Does a reasonable-care file remove importer responsibility?

No. It supports the review trail, but the importer still owns reasonable care.

What makes the file useful?

Specific product facts, visible missing facts, official source links, and notes on rejected alternatives.

When should the file be created?

Before the code is copied into a catalog, purchase order, or broker packet.

internal links

planning boundary

This page helps prepare a Planning Use record. It does not decide Entry Use, does not bind CBP, and is not legal advice. The importer remains responsible for reasonable care and must obtain broker or customs authority review before filing.

Turn this search into a file

Run a free Duty Surprise Scan, then build a Planning Use Classification Record when the Missing Facts matter.

Start scan today →