Define the operating boundary
A useful definition names the triggering event, required inputs, governing source, accountable owner, decision or action, exception path, evidence retained, and downstream handoff. Buyers should adapt those elements to their own population, jurisdictions, policies, systems, and control model before writing requirements.
The most important distinction is between a label and an operational capability. A provider may document origin, preference, and duty programs while depending on customer-supplied policy, licensed content, third-party data, integration partners, manual review, or services. The demonstration should expose those dependencies rather than hiding them behind a completed interface.
What a demonstration should prove
- Begin with representative source records and a named policy, standard, or controlled rule.
- Show the normal path, an ambiguous case, missing data, an exception, an override, and a material source change.
- Identify who can change rules, who can approve or reject, and how accountability is preserved.
- Trace every output back to inputs, versions, timestamps, user actions, and governing evidence.
- Export the resulting record and reconcile it with downstream systems and retained obligations.
Authority and operating context
Harmonized System or HS
The HS provides a common six-digit nomenclature for classifying traded goods. National and regional systems extend that structure for tariff, statistical, restriction, and administrative purposes. Tariff classification products must distinguish the common HS level from destination-specific national codes, rates, restrictions, rulings, explanatory materials, and audit evidence. HS classification is not export-control classification.
Union Customs Code or UCC
The UCC establishes core EU customs rules for status, representation, decisions, valuation, origin, guarantees, declarations, procedures, customs debt, controls, records, and electronic exchange, with substantial detail in related acts and systems. Customs automation must represent declarant roles, data, valuation, origin, procedure, guarantee, debt, decision, authority message, and record requirements across EU and national systems. A declaration connector alone does not establish substantive compliance.
Operating domains
Tariff and customs classification
The assignment and maintenance of Harmonized System and national tariff codes used for customs declarations, duty treatment, trade statistics, admissibility, and related border requirements. This is distinct from export-control classification such as ECCN or USML analysis.
Customs origin, valuation, declarations, and duty programs
The operational controls used to determine customs value and origin, assess preferential treatment, calculate duties and taxes, prepare and submit declarations, connect with brokers or authorities, reconcile records, and administer special procedures or duty programs.
Evidence and comparison limits
Official provider documentation can establish product positioning. Provider confirmation can clarify package or availability. Independent observation requires a disclosed scenario, environment, date, inputs, and reproducible result. None of those sources alone establishes buyer-specific legal, clinical, regulatory, quality, or operational fitness.
Buyer questions
- What exact outcome and evidence should origin, preference, and duty programs produce?
- Which source, version, and customer facts govern the workflow?
- Which decisions remain human and who is accountable for them?
- What is native, configured, integrated, service-delivered, or planned?
- How does a changed source affect open and historical records?