Compliance, not just classification

UK customs record-keeping, done by the tool — not the inbox.

Customs records can carry multi-year retention obligations. Many importers manage classification evidence through shared drives and email archives, which fall apart the moment anyone asks "why did we pick that code?" TariffFlow replaces that with a artifact-signed, searchable, standard-format record for every case — built into the classification flow so there's nothing extra to maintain.

Open the signed example Case Pack

What HMRC expects in a customs classification record

A practical classification record connects the declared code to the goods, evidence, reasoning, date, and accountable reviewer. Check current HMRC guidance for the complete records your procedure needs.

01
The commodity code declared
The 10-digit code exactly as stated on the CDS / CHIEF entry.
02
The basis for classification
Which heading text supported it, which chapter or section notes were consulted, which GRI rule was applied, and any relevant published ruling examples considered.
03
The product description used to decide
Text description, datasheet, specification sheet, or image that the classifier worked from — not just the purchase-order line.
04
The date the decision was made
Tariff schedules and measures change. A dated record links the evidence snapshot to the transaction it supported.
05
Who made the decision
Either a named individual, a documented internal process, or an external advisor. "The system" isn't enough — there needs to be a traceable actor.

What fails in the typical setup

The shared-drive + inbox approach breaks at the worst possible moment.

Four ways a manual system collapses under a real HMRC query, or a broker query, or a post-merger compliance review:

HMRC emails to query a classification on a shipment from 18 months ago. Nobody on the team remembers why that code was chosen.
The original datasheet was an email attachment that's been cycled out of the inbox retention window.
The customs broker and the in-house team picked different codes on two shipments of the same product, and nobody has a record of the reasoning either way.
A later reviewer asks which GRI was applied. The team had a consultant advise once, but the reasoning was never written down.

The TariffFlow approach

Six things the record-keeping layer handles automatically.

Not bolt-on storage. Built into the classification flow. Every case you run produces a record, and the library is indexable from the first one.

One standard record per classification

Every plan can issue the same structured Case Pack. Reviewers learn the section order once and scan later packs the same way, while the final page count varies with the case.

Artifact-signed and verifiable

The issued PDF carries an embedded artifact signature and is recorded with a SHA-256 file hash for comparison. This checks file integrity; it is not a qualified signature or proof of professional approval.

Searchable library

Find any historical classification by product name, code, date, or free-text search across descriptions. No more inbox archaeology.

Broker handoff in one link

Create a read-only share link per case. The broker sees the case view without a TariffFlow account, and you can revoke access later.

Retention handled

Cases and saved products are retained until you delete them on every plan. Export your TariffFlow application data or delete it from Settings.

Reuse for repeat shipments

Save products to your library. Reclassify in one click when specs change. The fact sheet is reusable so you're not copy-pasting datasheets for every PO.

Questions

Record-keeping FAQ for UK importers.

How accurate is TariffFlow, and how do you measure it?: TariffFlow is evaluated against versioned plain-language and held-out-ruling fixtures, with source rulings excluded where needed to avoid leakage. Results vary by product and classifier release, and an evidence label is a review signal rather than a guarantee. See the AI disclosure for the current methodology, and independently verify every recommendation before declaration.
How long does HMRC require me to keep customs records?: Retention periods depend on the transaction and customs procedure, so check current HMRC guidance for your records. TariffFlow retains cases and saved products until you delete them on every plan; you remain responsible for choosing a retention period that meets your obligations.
What does HMRC expect to see in a classification record?: A useful classification record identifies the code used, the goods and source facts considered, the reasoning and GRI applied, relevant legal notes or published ruling examples, when the decision was made, and who reviewed it. A TariffFlow Case Pack brings the available case evidence together, but your team must add any declaration-specific records your procedure requires.
Is a saved ChatGPT / AI output enough?: A standalone chat answer usually does not preserve the product sources, tariff evidence, alternatives, measures, and review context together. TariffFlow creates a structured Case Pack and records the issued PDF's file hash. Its artifact signature verifies the issued file, not a named person's identity or professional approval.
Can I share a record with my broker or freight forwarder without giving them a login?: Yes. Every case has a read-only share link. The recipient sees the case recommendation, reasoning, evidence, and measures without an account. Revoke the link any time from the case's Share panel.
What happens if HMRC changes a commodity code?: Tariff data is refreshed and the Case Pack records the HMRC measures fetched for the selected code at classification time. It is a snapshot, not a promise that the code or measure was legally correct for your goods. Re-run and review the classification for a later shipment.
Does the Case Pack satisfy 'Binding Tariff Information' requirements?: No. A Case Pack is a classification record, not a binding ruling. If you need a decision HMRC is legally committed to for your goods, apply for an Advance Tariff Ruling (ATaR) through GOV.UK. Published rulings shown by TariffFlow are non-transferable comparison examples only.

Not legal advice. HMRC's guidance is authoritative — these answers summarise TariffFlow's reading of it for UK importers. Verify against your own compliance framework before declaring.

Build a defensible record when it matters.

Start with five complete classifications per billing period, no card required. Every plan includes the Case Pack and records workflow.

See the Case Pack structure

UK customs record-keeping, done by the tool — not the inbox.

What HMRC expects in a customs classification record

The commodity code declared

The 10-digit code exactly as stated on the CDS / CHIEF entry.

The basis for classification

Which heading text supported it, which chapter or section notes were consulted, which GRI rule was applied, and any relevant published ruling examples considered.

The product description used to decide

Text description, datasheet, specification sheet, or image that the classifier worked from — not just the purchase-order line.

The date the decision was made

Tariff schedules and measures change. A dated record links the evidence snapshot to the transaction it supported.

Who made the decision

Either a named individual, a documented internal process, or an external advisor. "The system" isn't enough — there needs to be a traceable actor.

The shared-drive + inbox approach breaks at the worst possible moment.

Four ways a manual system collapses under a real HMRC query, or a broker query, or a post-merger compliance review:

HMRC emails to query a classification on a shipment from 18 months ago. Nobody on the team remembers why that code was chosen.

The original datasheet was an email attachment that's been cycled out of the inbox retention window.

The customs broker and the in-house team picked different codes on two shipments of the same product, and nobody has a record of the reasoning either way.

A later reviewer asks which GRI was applied. The team had a consultant advise once, but the reasoning was never written down.

Six things the record-keeping layer handles automatically.

Not bolt-on storage. Built into the classification flow. Every case you run produces a record, and the library is indexable from the first one.

One standard record per classification

Every plan can issue the same structured Case Pack. Reviewers learn the section order once and scan later packs the same way, while the final page count varies with the case.

Artifact-signed and verifiable

Searchable library

Find any historical classification by product name, code, date, or free-text search across descriptions. No more inbox archaeology.

Broker handoff in one link

Create a read-only share link per case. The broker sees the case view without a TariffFlow account, and you can revoke access later.

Retention handled

Cases and saved products are retained until you delete them on every plan. Export your TariffFlow application data or delete it from Settings.

Reuse for repeat shipments

Save products to your library. Reclassify in one click when specs change. The fact sheet is reusable so you're not copy-pasting datasheets for every PO.

Record-keeping FAQ for UK importers.

How accurate is TariffFlow, and how do you measure it?

TariffFlow is evaluated against versioned plain-language and held-out-ruling fixtures, with source rulings excluded where needed to avoid leakage. Results vary by product and classifier release, and an evidence label is a review signal rather than a guarantee. See the AI disclosure for the current methodology, and independently verify every recommendation before declaration.

How long does HMRC require me to keep customs records?

Retention periods depend on the transaction and customs procedure, so check current HMRC guidance for your records. TariffFlow retains cases and saved products until you delete them on every plan; you remain responsible for choosing a retention period that meets your obligations.

What does HMRC expect to see in a classification record?

A useful classification record identifies the code used, the goods and source facts considered, the reasoning and GRI applied, relevant legal notes or published ruling examples, when the decision was made, and who reviewed it. A TariffFlow Case Pack brings the available case evidence together, but your team must add any declaration-specific records your procedure requires.

Is a saved ChatGPT / AI output enough?

A standalone chat answer usually does not preserve the product sources, tariff evidence, alternatives, measures, and review context together. TariffFlow creates a structured Case Pack and records the issued PDF's file hash. Its artifact signature verifies the issued file, not a named person's identity or professional approval.

Can I share a record with my broker or freight forwarder without giving them a login?

Yes. Every case has a read-only share link. The recipient sees the case recommendation, reasoning, evidence, and measures without an account. Revoke the link any time from the case's Share panel.

What happens if HMRC changes a commodity code?

Tariff data is refreshed and the Case Pack records the HMRC measures fetched for the selected code at classification time. It is a snapshot, not a promise that the code or measure was legally correct for your goods. Re-run and review the classification for a later shipment.

Does the Case Pack satisfy 'Binding Tariff Information' requirements?

No. A Case Pack is a classification record, not a binding ruling. If you need a decision HMRC is legally committed to for your goods, apply for an Advance Tariff Ruling (ATaR) through GOV.UK. Published rulings shown by TariffFlow are non-transferable comparison examples only.

Not legal advice. HMRC's guidance is authoritative — these answers summarise TariffFlow's reading of it for UK importers. Verify against your own compliance framework before declaring.