ONESOURCE joins screening and customs data—but an HS code is not an export-control classification

One product record can support two separate classifications

Thomson Reuters' current ONESOURCE Global Trade page describes a broad trade-automation environment using regulatory information and tools for import-export compliance, customs operations, automated customer and supplier screening, risk programs, duty opportunities, and analytics. A shared item master can help trade teams reuse descriptions, part attributes, composition, origin, technical information, suppliers, destinations, and prior decisions instead of rebuilding the product record for each transaction.

Reuse should not erase the decision boundary. Harmonized System and national tariff classifications organize goods for customs treatment, statistics, and duty purposes. Export-control classifications are applied under the relevant export-control regime to evaluate controlled characteristics, destinations, end users, end uses, and licensing consequences. Similar wording or the existence of a numeric code does not make the schemes interchangeable, and a screening result does not resolve either classification.

Preserve the rule set and technical basis behind every code

A defensible classification record should retain the exact item and version, complete description, composition and function, technical parameters, drawings or specifications used, jurisdiction, classification system and edition, proposed code, rationale, reviewer, date, source material, ruling or advisory input where applicable, confidence, unresolved questions, and approval. It should show whether a code came from the manufacturer, broker, supplier, internal classifier, authority decision, or inherited data and whether it was independently reviewed.

Transaction controls should then connect—not merge—the customs code, export classification, origin and preference record, restricted-party screening, ownership review, destination, end use and end user, license or exception analysis, filing data, holds, and release authority. A product change, regulatory update, new destination, software or technology transfer, or corrected technical specification may reopen one determination without invalidating all of the others. Historical decisions should remain reconstructable for the exact shipment and date.

Test the workflow with look-alike and changed products

A representative evaluation should classify two products with similar commercial descriptions but different controlled technical characteristics, a multi-function item, a software-enabled product, a spare part, and an item whose composition changes. The team should test different import and export jurisdictions, an inherited supplier code, a broker disagreement, a regulatory update, and a transaction that passes party screening but requires a separate end-use or license review. Users should see which determination changed, why, and who can release the transaction.

Thomson Reuters' official page supports the described global-trade automation, regulatory-information, customs, screening, risk, and analytics positioning, while the maintained record documents the broader classification and licensing scope. No content library, classification rule, item record, screening result, customs filing, integration, configured control, implementation, or customer outcome was independently tested here. Trade, customs, engineering, legal, procurement, logistics, and authorized release owners must make the jurisdiction- and transaction-specific decisions.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Trade Controls Brief will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.