HS Code Lookup Workflow for Importers: A Practical 2026 Guide

An effective HS code lookup workflow starts with complete product facts, not a keyword search. It should suggest a code, show the reasoning and tariff evidence, identify the country-specific extension, calculate downstream duty implications, and send uncertain products to a human reviewer. The result should be stored against the SKU with its source, confidence, effective date, and approval history.

What should an importer collect before looking up an HS code?

Start with a structured product record. A supplier’s short description such as “metal fitting” is rarely enough to classify an item defensibly.

Capture:

SKU and internal product name

Plain-language description

Material and composition

Primary function

How the product operates

Intended use

Dimensions, weight, and technical specifications

Whether it is a component, set, kit, or finished product

Packaging and presentation

Country of origin

Importing country

Supplier documents, photographs, drawings, and safety datasheets

UK guidance explains that commodity codes determine Customs Duty, import VAT, preferential rates, licensing requirements, quotas, and other trade measures. The classification process should therefore preserve the facts used to reach the decision rather than only saving the final number.

A practical n8n intake workflow can pull product data from an ERP, ecommerce platform, purchasing sheet, or supplier form. It can then reject incomplete records before they reach the classification step.

How does an HS code lookup workflow work?

A reliable workflow usually follows these seven steps:

1. Trigger a classification request.

• Start when a new SKU is created, a supplier changes a specification, or an importer adds a new country lane.

2. Validate the product record.

Check that required fields such as material, function, origin, destination, and technical description are present. Send incomplete records to procurement rather than guessing.

3. Create a structured classification brief.

Convert inconsistent supplier text into a standard summary. Include the product’s composition, use, operating principle, dimensions, packaging, and distinguishing features.

4. Search tariff and reference data.

Query the relevant tariff source or classification API. Keep the source, timestamp, country, tariff edition, and returned candidates with the record.

5. Generate a suggested classification.

The system can rank likely HS or tariff codes and explain which product facts support each candidate. This is a recommendation, not automatically a legally binding decision.

6. Apply confidence and exception rules.

Auto-approve only low-risk, high-confidence cases that match an existing approved pattern. Route composite goods, sets, chemicals, machinery, new materials, and conflicting results to a reviewer.

7. Publish the approved result downstream.

Write the code to the SKU master, commercial-invoice template, purchase-order data, customs-entry file, and landed-cost calculation. Schedule a review when tariff content or the product specification changes.

For UK imports, the first six digits come from the internationally harmonised HS, while the UK extends the code to a more specific national level. UK commodity codes are commonly 10 digits, so storing only an HS6 result may leave the declaration incomplete.

What should the workflow store for auditability?

A defensible record should contain more than the selected code. Store:

Field	Why it matters
SKU and version	Connects the classification to the exact product
Product facts	Shows what was known when the decision was made
Destination country	Tariff extensions differ by market
Country of origin	Supports duty and preference checks
Suggested code and alternatives	Preserves the decision context
Classification explanation	Makes review faster and more consistent
Tariff source and timestamp	Shows which data was used
Rulings or reference documents	Provides supporting evidence
Confidence score and exception flags	Separates routine cases from risky ones
Reviewer, date, and approval status	Creates accountability
Effective date and next review date	Prevents stale classifications

The UK government describes an Advance Tariff Ruling as a legally binding classification decision for goods imported into or exported from Great Britain. It is generally valid for three years and must be obtained before the relevant customs procedures are completed. The workflow should therefore store ruling references and alert the team before a review or renewal is due.

For US imports, the classification authority is US Customs and Border Protection, and prospective binding ruling requests need complete transaction facts. A global importer should keep separate country-specific outputs rather than treating one six-digit HS code as the complete answer everywhere.

When should an importer require human review?

Human review is appropriate when:

Two tariff headings appear plausible

The product combines multiple materials or functions

The item is sold as a set or kit

Classification depends on the product’s principal function

The product is a chemical, food, textile, machine, or regulated good

A new tariff measure may apply

The supplier description conflicts with technical documents

The suggested code differs from a previous approved code

The confidence score is low

A customs authority has issued a relevant ruling

The financial or compliance impact is material

The automation should make the reviewer faster, not remove accountability. Send a concise review packet containing the product facts, suggested codes, evidence, tariff impact, and a clear approve/change request.

A useful design is to separate recommendation from approval. The model or lookup service proposes a code; a named reviewer approves it; the system records both events.

How can the workflow calculate duties and landed cost?

After approval, pass the classification into the landed-cost calculation. At minimum, the calculation should account for:

Customs value

Customs duty rate

Import VAT or sales tax

Freight

Insurance

Brokerage and clearance charges

Surcharges or trade remedies

Origin-based preferences

Currency conversion

Allocation across units or SKUs

The UK Trade Tariff tool uses commodity codes to determine duty, import VAT, taxes, preferential rates, licensing, quotas, anti-dumping duties, and safeguarding measures. That means a workflow that only returns an HS code stops before the operational value is realised.

For importer teams, this is where a connected system such as Shipment Ledger can support repeatable shipment and landed-cost operations. The classification result should feed purchasing and finance systems while retaining the original evidence.

Do not silently overwrite a previously approved rate. Create a new effective-dated version and flag shipments or purchase orders that may be affected.

What does an n8n implementation look like?

A typical implementation can use these workflow stages:

1. Input: ERP, ecommerce catalogue, supplier form, spreadsheet, or email attachment.
2. Normalisation: n8n maps inconsistent field names into a standard product schema.
3. Document extraction: OCR or an AI step extracts facts from datasheets and invoices.
4. Validation: Missing or contradictory facts create an exception task.
5. Lookup: An API or tariff database returns candidate codes and supporting data.
6. Decisioning: Rules assign confidence and identify products requiring review.
7. Approval: A reviewer approves or edits the classification through an internal task or form.
8. Publication: The approved code updates the SKU master, invoice templates, and landed-cost calculations.
9. Monitoring: A scheduled job checks tariff changes, expiring rulings, and product-data changes.
10. Reporting: The workflow logs throughput, review time, overrides, and unresolved exceptions.

This is a good fit for a customer-floor automation rather than an isolated chatbot. Zaps Studio builds UK-led n8n automations for ops-heavy SMBs, with clients owning the n8n source, credentials, and documentation. Fixed-price workflow packages are typically $1,000–$3,000, with delivery taking 2–4 weeks after an audit. See the Zaps Studio pricing page for the current commercial route.

For examples of connected B2B workflows, review n8n workflow examples for B2B teams and five workflow automation quick wins. A classification workflow can sit alongside purchasing alerts, supplier-document handling, and shipment reconciliation.

Which HS code lookup tools should importers consider?

SimplyDuty suits occasional lookups, duty calculations, batch files, and lightweight API use; published pricing includes £0.10 per classification or duty call, but it is not a complete approval and audit system for complex enterprise classification. TariffWise and SimplyDuty should be evaluated on coverage, evidence quality, country support, and cost per reviewed SKU rather than headline lookup price.

Avalara Tariff Code Classification suits larger organisations needing broad country coverage, batch processing, and enterprise integration; pricing is generally quote-based, so implementation and content fees must be confirmed before comparison. Avalara is stronger as a trade-compliance platform than as a lightweight low-volume utility.

Descartes CustomsInfo suits organisations that need broad tariff content, customs references, and rulings within a wider Descartes environment; it may be excessive for a small importer with a narrow catalogue and simple lanes. Descartes is worth considering when document and compliance content are already central to the operating stack.

NetSuite, Odoo, Cin7, and Unleashed can hold product, purchasing, inventory, and costing data, but none should be assumed to replace specialist customs classification review. Their suitability depends on integration depth, country coverage, and whether tariff content is included.

Pricing varies because vendors charge by lookup, classification, tariff line, user, country, API credit, or managed service. A fair comparison should calculate the cost per reviewed SKU and include implementation, tariff-data access, reviewer time, and future maintenance.

Can AI classify products without customs specialists?

AI can improve intake, search, explanation, and exception routing, but it should not be treated as a universal legal classifier. A plausible code is not necessarily a defensible code.

Use AI to:

Extract product facts from documents

Rewrite supplier descriptions into classification-ready language

Identify missing information

Suggest candidate headings

Compare new products with approved classifications

Explain differences between candidates

Draft a reviewer summary

Detect changes in descriptions or tariff content

Keep a human in the loop for uncertain or high-impact cases. In Great Britain, an Advance Tariff Ruling provides legal assurance that an ordinary database suggestion cannot provide.

What does an importer automation project cost?

Typical 2026 bands are:

Implementation	Indicative price	Suitable for
Basic lookup utility	Free to about $20/month	Occasional searches and small catalogues
Self-serve classification software	About $49–$99/month	Guided classification and limited bulk work
Growing importer/API deployment	About $99–$1,500/month	API access, batch processing, integrations, and multiple countries
Enterprise trade-compliance platform	Custom quote	Large catalogues, ERP integration, audit controls, and managed support
Custom n8n workflow	About $1,000–$3,000	A connected workflow around existing systems
Broader importer system	About $3,000–$12,000	Multiple workflows, approvals, tariff monitoring, and landed-cost operations

These figures exclude customs-specialist review, tariff-data subscriptions, and changes to an importer’s ERP or finance stack. The workflow automation cost guide explains why build cost depends on data quality, system count, exception handling, and ownership requirements.

A sensible first phase is one product family, one destination country, and one approval route. Measure:

Percentage of records with complete product facts

Lookup success rate

Reviewer override rate

Average review time

Cost per approved SKU

Classification changes after tariff updates

Duty or VAT calculation exceptions

Time saved per shipment

Expand only after the workflow produces a reliable audit trail.

What should an importer do first?

Choose a product family with meaningful volume and recurring classification work. Export 20–50 representative SKUs, collect their documents, and have a customs specialist identify the facts and decisions that matter.

Then:

1. Define the product schema.
2. Identify the authoritative tariff source for each destination.
3. Agree on confidence and escalation rules.
4. Build a human approval step.
5. Store evidence and effective dates.
6. Connect approved codes to invoices and landed-cost calculations.
7. Test against known classifications.
8. Monitor changes before expanding the catalogue.

That approach avoids the common mistake of buying a lookup tool before defining the operational process around it. For a UK importer, the goal is not merely to find a six-digit HS code. It is to create a repeatable, reviewable, country-specific classification record that remains useful when the product, tariff, supplier, or shipment changes.