HS Code Typos: How They Happen and How to Catch Them Before Filing

The Harmonized System organizes goods into chapters, headings and subheadings. The first six digits are shared internationally, and individual countries add further digits for their own tariff schedules.

Because the structure is hierarchical, a wrong digit rarely produces nonsense. It tends to produce a different code that still looks valid. For example, 8471 and 8417 are both real headings, for very different goods.

A wrong code can delay clearance or change the duty owed, and it can prompt questions from customs that take time to resolve. Classification itself is a specialist decision, so confirm codes with a licensed customs broker.

The letter O for zero. The two keys sit close together, and in many fonts the characters look nearly identical. A code like 85O4 looks right on screen but isn't a number at all.

The letter I or a lowercase l for one. The same problem, especially when codes are copied out of a PDF and pasted into another system.

Transposed digits. Typing 8417 for 8471, or 6204 for 6402. The result is still a well-formed code, which is why this kind of error is so hard to spot.

Dropped or extra digits. A six-digit subheading typed with five digits, or a repeated keystroke adding one more. Codes are often written with dots or spaces, such as 8471.30, and stripping that punctuation by hand invites mistakes.

Leading zeros removed by spreadsheets. Codes in the early chapters, such as 0901 for coffee, lose their leading zero when a spreadsheet treats the cell as a number. 0901 becomes 901, which is no longer a valid code.

Copied from the wrong line. On an invoice with many lines, it's easy to take the code from the row above or below, especially after scrolling or when descriptions are similar. The code is valid; it's just attached to the wrong product.

Carried over from old records. A code saved in a product list from an earlier shipment, or taken from a supplier's export paperwork, may not be the right code for the destination country's tariff schedule.

Check the format. Every code should contain only digits once dots and spaces are removed consistently, and should be the length your system expects. This catches the letter O, the letter I and most dropped or extra digits.

Store codes as text. Format HS code columns as text in spreadsheets and import templates so leading zeros survive every import and export.

Compare against your product records. If you keep a list of products with codes your broker has confirmed, compare each invoice line against it. A mismatch isn't always an error, but it's always worth a look.

Read the code against the description. Check that each code makes sense for the goods described on the same line. This is the check that catches codes copied from the wrong line, which format checks can't.

Look for repeats and near-repeats. The same code on two lines with very different descriptions, or two codes that differ only by a swapped pair of digits, both deserve a second look.

Reconcile across documents. Compare the codes on the commercial invoice with any shown on the packing list or purchase order for the same shipment.

Send new codes for confirmation. Any product being classified for the first time, or any code that changed since the last shipment, should go to your customs broker before filing.

Automated checks are good at the mechanical part: confirming a code is well-formed, spotting characters that don't belong and flagging values that don't match the document. They don't get tired on the fortieth line of an invoice.

What they can't do is decide whether a product is classified correctly. A well-formed code can still be the wrong code. Classification depends on what the product is, what it's made of and how it's used, and that judgment belongs with a licensed customs broker.

The practical split is to let software catch typos and inconsistencies, and to send classification questions to people qualified to answer them.

The surest way to avoid typing errors is to type less. Extracting HS codes directly from a supplier's digital invoice removes the keyboard step where O and 0 get swapped.

Extraction isn't perfect either, so it helps when each extracted value comes with a confidence score and a check against the source document. Low-confidence or failed values then go to a person instead of straight into a filing.

The Lumen DocAI Logistics pack is live and reads commercial invoices, bills of lading, packing lists, arrival notices and purchase orders.

Every field gets a confidence score, and a second, independent AI pass checks each value against the document. It checks that HS codes are well-formed, that line items add up to the total, that quantity × unit price matches each line total and that net weight isn't above gross weight, and it flags an unsigned bill of lading.

When a code is missing or doubtful, it lists the issue and who owns the answer, and drafts a request to the supplier that a person approves before anything is emailed. Data goes out as CSV or Excel.

A well-formed code looks right; that doesn't make the classification right, so keep your broker in the loop. Clean digital PDFs work best today; scans and photos aren't reliably supported yet. The Free plan includes 25 documents a month with no credit card.