Product Classification Codes Need a Change Process

A product classification is added to the platform during setup. Months later, a shipment fails validation and the team discovers the code is no longer appropriate for the current filing.

Treating classification as a one-time text field leaves the business without a way to manage change.

Census publishes Schedule B resources, obsolete codes, and concordance files, and notes that its concordance files are subject to change at any time. This is a concrete example of why classification data needs maintenance. It does not mean the same US code can simply be reused as every destination's import classification. Census Schedule B resources.

Give the data an owner

Our recommendation is to name the person or authorized specialist responsible for classification decisions. Engineering can support validation and history, but should not infer a replacement classification because two descriptions look similar.

The operational record can distinguish the classification system, jurisdiction or purpose, code, description, effective period, and review source. Determine which of those fields the actual workflow needs.

Preserve history without freezing current work

Consider a hypothetical code change affecting a product with completed shipments and open requests.

Overwriting every historical record can obscure what was submitted at the time. Leaving every open request unchanged can preserve an obsolete assumption. Decide separately how historical evidence is retained and how uncompleted work is reassessed.

Make the reviewer, change reason, and affected records visible. A source update should trigger review, not an unapproved mass substitution.

Use a change-review checklist

• Which classification source changed, and when does it apply?
• Which products or open transactions may be affected?
• Who confirms the replacement or required action?
• Which integrations and test examples need updating?
• How will staff know which version informed a decision?

Begin with a small set of important products and verify that the records support an actual change. Review your cross-border workflow or explore Cross-Border Logistics.