Customs Explorer
⌕

Customs Explorer

Origin API

DIGITAL CUSTOMS / ORIGIN INTELLIGENCE

Origin API.

Connecting Product Data, Rules of Origin & Customs Compliance.

Origin-related software integrations can help businesses organise product information, evaluate applicable origin rules and manage supporting evidence across customs workflows.

Preferential and non-preferential origin follow different legal frameworks. Reliable automation therefore requires the correct rules, accurate production data and appropriate human oversight.

01 Product Data
02 Origin Rules
03 Evidence & Controls
ORIGIN DATA WORKFLOW CONCEPTUAL MODEL
ENTERPRISE DATA SOURCES

Origin analysis starts with the underlying commercial and production information.

ERP / PLM Product records
Suppliers Origin evidence
Production Materials & processes
ORIGIN ASSESSMENT LAYER RULE-BASED

Origin Rules & Data Validation

Match product characteristics and production information against the applicable legal origin criteria.

Classification Rule Selection Evidence Review
Product-specific analysis Traceable inputs
ASSESSMENT Origin Determination Support

Documented evaluation against relevant origin rules.

COMPLIANCE Evidence & Exception Review

Supporting records, missing data and cases requiring investigation.

This diagram illustrates a possible software architecture. It is not an official EU customs API or an automated certificate of origin.

01
Collect

Gather product and supplier information

02
Evaluate

Apply the relevant origin criteria

03
Document

Retain supporting records and evidence

04
Review

Resolve exceptions and reassess changes

IMPORTANT DISTINCTION

Origin Assessment Is Not the Same as Origin Certification

A software tool may assist with origin calculations, rule selection and document management. It cannot independently establish the factual accuracy of supplier declarations, manufacturing operations or supporting evidence. The applicable legal rules determine whether origin is established and which proof, if any, may be issued or used.

02 / ORIGIN FRAMEWORKS

Two Origin Frameworks.
Different Legal Purposes.

Customs origin is not a single universal determination. Preferential and non-preferential origin serve different purposes and may apply different legal tests to the same product.

An origin-related software integration must identify the relevant legal framework before evaluating materials, manufacturing operations or supporting documents. A result obtained under one framework cannot automatically be reused under the other.

FRAMEWORK 01

Preferential Origin

Eligibility for preferential tariff treatment

Preferential origin determines whether goods qualify as originating under the rules of a particular preferential arrangement, potentially allowing reduced or zero customs duties when all relevant conditions are met.

LEGAL BASIS Applicable preferential agreement or autonomous preferential arrangement
KEY ASSESSMENT Agreement-specific product rules, originating materials and qualifying production
DOCUMENTARY CONTROLS Relevant proof of origin, supplier evidence and applicable verification requirements
FRAMEWORK 02

Non-Preferential Origin

Origin for general customs and trade-policy purposes

Non-preferential origin establishes the country of origin under the applicable non-preferential rules. It is relevant to measures such as certain trade-policy instruments, origin-related requirements and customs declarations.

LEGAL BASIS Union Customs Code, including Articles 59–61, and applicable supplementary provisions
KEY ASSESSMENT Wholly obtained goods or the applicable last substantial transformation criteria
DOCUMENTARY CONTROLS Manufacturing records, origin evidence and any required supporting documentation

What Changes Between the Two?

A robust origin workflow separates the purpose, applicable rules and evidence required for each assessment.

Assessment Preferential Origin Non-Preferential Origin
Main purpose Determine eligibility for preferential tariff treatment Determine origin for general customs and trade-policy purposes
Applicable rules Specific preferential agreement or arrangement UCC non-preferential origin provisions and relevant detailed rules
Product classification Used to identify the applicable product-specific origin rule May determine which product-specific non-preferential rules apply
Production analysis Qualifying operations, materials and other conditions under the arrangement Wholly obtained status or applicable substantial transformation criteria
Proof and evidence Proof required by the relevant arrangement and supporting records Supporting evidence and any applicable documentary requirements
Software output Arrangement-specific assessment with supporting evidence Non-preferential assessment with supporting evidence
02 / PRACTICAL SCENARIO

One Product.
Two Separate Assessments.

Consider an industrial component manufactured in the EU using materials sourced from several countries.

Its non-preferential origin must be assessed under the relevant non-preferential rules. Separately, preferential origin for export to a partner country depends on the specific arrangement and its product-specific rules.

The product may satisfy one framework without satisfying the other. Even preferential assessments under two different arrangements may produce different results.

An EU manufacturing location, an EU supplier or an existing origin statement does not by itself establish preferential origin for every destination.

ORIGIN ASSESSMENT MODEL ILLUSTRATIVE
INPUT Industrial Component EU production · International materials
PATH A Preferential

Selected agreement

Apply the relevant origin rule
PATH B Non-Preferential

UCC origin framework

Apply the relevant origin criteria

Independent assessments. Results depend on verified facts and applicable law.

What an Origin API Must Distinguish

Any software architecture designed to support origin analysis needs to preserve the legal context of each individual determination.

01

Origin Framework

Record whether the assessment concerns preferential or non-preferential origin.

02

Applicable Arrangement

Identify the relevant agreement or legal framework and its applicable version.

03

Product & Production Data

Connect classification, materials, suppliers and manufacturing operations.

04

Evidence & Review

Retain supporting documents, identify missing information and record reviews.

03 / RULES & DATA REQUIREMENTS

Origin Rules Need
Reliable Product Data.

An origin assessment is only as reliable as the legal rule selected and the underlying product, material and manufacturing information.

Origin-related software may help organise these inputs, evaluate defined criteria and identify missing evidence. However, the relevant rules differ by origin framework, product classification and, for preferential origin, the applicable arrangement.

Six Essential Data Categories

These categories provide a practical starting point for designing a traceable origin-assessment workflow.

01 / CLASSIFICATION

Product Classification

The relevant tariff classification helps identify applicable product-specific origin rules. Incorrect classification can lead to selection of the wrong rule.

HS HEADING PRODUCT DESCRIPTION
02 / MATERIALS

Bill of Materials

A structured BOM identifies components, quantities and material relationships. Depending on the rule, classification and originating status of individual materials may also be required.

COMPONENTS MATERIAL ORIGIN
03 / VALUATION

Material & Product Values

Some origin rules use value thresholds. Calculations must follow the definitions prescribed by the applicable rule rather than relying on arbitrary ERP cost fields.

MATERIAL VALUES RULE DEFINITIONS
04 / MANUFACTURING

Production Operations

Manufacturing location, processing stages and actual operations may be decisive. Simple assembly, packaging or other limited operations may be insufficient under applicable rules.

PROCESS STEPS PRODUCTION LOCATION
05 / LEGAL CONTEXT

Applicable Origin Rule

The assessment needs the correct legal framework, relevant agreement where applicable, product rule, definitions, exceptions and effective date.

RULE VERSION ARRANGEMENT
06 / EVIDENCE

Supplier & Supporting Evidence

Supplier declarations, production records and other relevant evidence support factual inputs. Documents must be assessed for their scope, validity and relevance.

DOCUMENTS VALIDITY

Common Types of Product-Specific Rules

Preferential arrangements can use different rules, sometimes with alternatives or combined conditions. The examples below describe rule categories, not criteria applicable to every product.

01

Change in Tariff Classification

A rule may require non-originating materials to undergo a specified change in tariff classification through production.

CLASSIFICATION-BASED
02

Maximum Non-Originating Material Value

A rule may limit the value of non-originating materials relative to a defined product value, using the prescribed calculation method.

VALUE-BASED
03

Specific Processing Operations

A rule may require particular manufacturing processes or transformations, rather than merely a change in value or classification.

PROCESS-BASED
04

Wholly Obtained Requirements

Certain products or circumstances require an assessment of whether goods are wholly obtained under the applicable provisions.

ORIGIN STATUS

These are illustrative categories. Cumulation, tolerances, insufficient processing and other conditions can materially affect preferential origin assessments.

03 / INTEGRATION ARCHITECTURE

From Enterprise Data
to a Traceable Assessment.

An ERP may contain product codes, quantities and purchase prices, but it does not necessarily contain all the information required to determine customs origin.

An origin-assessment layer must therefore normalise data, identify gaps and select the correct legal rule before attempting any automated evaluation.

Keep the product classification linked to the assessment.

Store the applicable arrangement and rule version.

Preserve source records and evidence references.

Flag incomplete or contradictory data for review.

ORIGIN DATA PIPELINE CONCEPTUAL
ERP Products & Costs
BOM Materials & Quantities
RECORDS Suppliers & Production
DATA PREPARATION

Normalise & Validate Inputs

Classification, material status, values, production details and evidence.

ORIGIN RULE ENGINE

Apply the Selected Legal Criteria

Evaluate available facts against the rule applicable to the product, framework and relevant arrangement.

RULE VERSION INPUT TRACE EXCEPTIONS
ASSESSMENT OUTPUT Documented Result Subject to evidence and review
EXCEPTION OUTPUT Review Required Missing or conflicting information

A calculation result is not an official origin certification or a guarantee of preferential treatment.

When Software Should Stop and Ask for Review

A reliable system must be able to return an unresolved result instead of manufacturing certainty from incomplete information.

!

Missing Classification

The relevant product-specific rule cannot be reliably selected.

!

Unverified Material Origin

Originating status cannot be assumed from a supplier’s location alone.

!

Incompatible Value Definitions

ERP cost fields may not correspond to the values required by the rule.

!

Unknown Production Operations

The available records may not establish which processing actually occurred.

!

Unclear Legal Framework

The arrangement, relevant rule or effective date has not been established.

!

Insufficient Supporting Evidence

Available documents do not adequately substantiate the facts being assessed.

04 / PROOF OF ORIGIN & VERIFICATION

Origin Evidence.
Verification & Trust.

Origin documentation supports customs compliance, but document existence, registration status and substantive origin eligibility are different questions.

The proof required for preferential treatment depends on the applicable arrangement. An integration may help capture, classify and review supporting records, but it cannot automatically establish the truth of every underlying origin claim.

Common Forms of Origin Evidence

Different preferential arrangements prescribe different proofs and conditions. The following categories must not be treated as interchangeable.

01 / MOVEMENT CERTIFICATE

EUR.1 Movement Certificate

EUR.1 is a preferential origin document used under arrangements that provide for it. Its availability, issuing procedure and acceptance depend on the applicable rules.

PRIMARY CONTROL Applicability, document details and relevant formal requirements
IMPORTANT LIMIT A certificate does not remove the possibility of subsequent origin verification
02 / EXPORTER DECLARATION

Origin Declarations & Statements

Some arrangements permit an exporter to make a declaration or statement on origin using prescribed wording and conditions, including relevant exporter authorisations or registrations.

PRIMARY CONTROL Wording, exporter eligibility, document scope and applicable conditions
IMPORTANT LIMIT The statement alone does not prove the accuracy of production data
03 / EXPORTER REGISTRATION

REX Registration

The Registered Exporter system supports origin self-certification in arrangements that use REX. Registration information may be checked through the relevant EU services, subject to their available data and conditions.

PRIMARY CONTROL Registration information and its relevance to the arrangement
IMPORTANT LIMIT A valid registration is not proof that a particular product originates
04 / SUPPLY CHAIN EVIDENCE

Supplier Declarations

Supplier declarations can provide evidence of originating status within the relevant EU framework. Their wording, scope, period and supporting records require appropriate review.

PRIMARY CONTROL Supplier identity, covered goods, origin information and validity period
IMPORTANT LIMIT A supplier declaration is not automatically the proof presented to importing customs

Four Questions That Must Remain Separate

A reliable origin integration distinguishes administrative checks from substantive evaluation of the goods.

01
DOCUMENT CHECK

Is the required information present?

Review document type, prescribed fields, declared goods, dates and other arrangement-specific formal requirements.

FORMAL
02
REGISTRATION CHECK

Is the relevant exporter status supported?

Where required, assess available information on registration or authorisation, including its relevance to the transaction.

ADMINISTRATIVE
03
ORIGIN ASSESSMENT

Do the goods meet the applicable origin rule?

Evaluate product classification, material status, manufacturing operations and any additional legal conditions.

SUBSTANTIVE
04
CUSTOMS VERIFICATION

Can the origin claim withstand official review?

Customs authorities may examine origin claims and supporting evidence under the procedures of the applicable arrangement.

OFFICIAL
03 / DIGITAL VERIFICATION

What Software Can Check.
And What It Cannot Confirm.

A document-management or origin-assessment integration can perform useful consistency checks without claiming to authenticate every certificate or determine the underlying facts independently.

Public registration checks, where available, must be distinguished from access to official customs verification channels. Their existence does not imply an unrestricted API or a universal electronic certificate register.

✓

Identify missing document fields and inconsistent references.

✓

Check registration data when an appropriate service is available.

!

Escalate unsupported origin claims and conflicting evidence.

!

Do not label an unverified origin claim as customs-approved.

EVIDENCE VERIFICATION MODEL CONCEPTUAL
DOCUMENT INPUT Origin Claim & Supporting Records Statement · Certificate · Supplier evidence
CHECK 01 Formal Completeness Fields, references and scope
CHECK 02 Available Status Data Where official services permit
CHECK 03 Evidence Consistency Products, suppliers and rules
REVIEW GATE Is the Evidence Sufficient?

Check results inform the assessment; they do not replace official verification.

CONTROL RESULT Checks Documented Reviewable evidence trail
EXCEPTION Further Review Missing or disputed evidence

No universal public EU API is assumed for verifying every origin document.

REX / IMPORTANT DISTINCTION

A Registered Exporter Is Not an Origin Guarantee

REX registration concerns the exporter’s ability to make origin statements under arrangements using the system. It does not establish that every product exported by that operator meets the applicable rules of origin.

✓

What a Registration Check May Support

Confirmation of available registration information, subject to the service, data visibility, applicable arrangement and relevant dates.

×

What It Does Not Establish

The accuracy of the bill of materials, supplier declarations, production operations or preferential origin of an individual shipment.

European Commission — Taxation and Customs Union

Evidence Should Remain Traceable

A useful integration links each origin claim to the supporting facts and documents available when the assessment was performed.

01

Document Identity

Record document type, issuer, references and relevant dates.

02

Product Coverage

Identify the goods, classifications and transactions covered by the evidence.

03

Legal Context

Preserve the relevant arrangement, rule and assessment date.

04

Verification History

Record checks performed, sources, results and unresolved exceptions.

05 / INTEGRATION CHALLENGES

Reliable Origin Automation
Requires More Than Rules.

Origin assessments depend on changing legal frameworks, accurate production data, supporting evidence and the correct interpretation of product-specific rules.

Software can structure these assessments and reduce repetitive work. But an automated result is only defensible when its inputs, rule version, assumptions and limitations remain visible and reviewable.

Six Challenges That Determine Reliability

These are not optional enhancements. Each can materially affect whether an origin-related integration is suitable for operational use.

01 / LEGAL MAINTENANCE

Changing Origin Rules

Preferential arrangements, product-specific rules, transitional provisions and related requirements can change. A static rules database can become unreliable without controlled legal maintenance.

REQUIRED CONTROL Versioned rules and effective dates
02 / INPUT QUALITY

Incomplete Enterprise Data

ERP and BOM records may lack verified material origin, appropriate value definitions, processing details or supporting evidence. Data availability must be tested before relying on automation.

REQUIRED CONTROL Validation and missing-data flags
03 / LEGAL COMPLEXITY

Cumulation & Exceptions

Cumulation, tolerances, insufficient processing and other conditions may alter an assessment. Their availability and application depend on the relevant legal framework.

REQUIRED CONTROL Explicit treatment of special rules
04 / SUPPLIER EVIDENCE

Document Scope & Validity

Supplier declarations and other records must correspond to the goods, period and origin conditions concerned. A stored document is not necessarily sufficient evidence.

REQUIRED CONTROL Document-to-product traceability
05 / EXTERNAL SERVICES

API Access & Availability

Official online tools do not necessarily provide public programmatic access. Access permissions, service conditions, maintenance and technical documentation must be verified independently.

REQUIRED CONTROL Confirmed access before development
06 / ACCOUNTABILITY

Responsibility & Review

Automated checks cannot replace all legal interpretation or official customs verification. Operators need defined responsibilities, review procedures and auditable decisions.

REQUIRED CONTROL Human oversight and audit history
02 / RULE VERSIONING

The Same Product.
A Different Assessment Date.

Origin rules must be evaluated within the legal framework applicable to the relevant transaction and date. Changes in agreements, protocols or detailed rules can affect the outcome.

A reliable system should preserve historical assessments rather than silently recalculating them under the latest rule set.

01

Record the arrangement and legal basis.

02

Preserve the applicable rule version and date.

03

Retain the input data used in the assessment.

04

Flag assessments potentially affected by legal changes.

RULE VERSION CONTROL ILLUSTRATIVE
PRODUCT RECORD Industrial Component Classification · BOM · Production evidence
HISTORICAL ASSESSMENT Rule Set A Applicable at assessment date A
LATER ASSESSMENT Rule Set B Applicable at assessment date B
AUDITABLE RECORD Preserve Each Assessment Context

Inputs, applicable legal criteria, evidence and review history remain linked.

A new rule version does not automatically invalidate every earlier origin determination.

Design for Evidence, Not Just Calculation

The system should expose the basis of each assessment and prevent unsupported conclusions from becoming operational decisions.

01

Explainable Results

Identify which legal criteria were evaluated and which inputs influenced the result.

02

Evidence Linking

Connect declarations, supplier records, BOM data and production evidence to the relevant assessment.

03

Exception Handling

Distinguish incomplete information, inconsistent records and unresolved legal conditions.

04

Controlled Updates

Test new rules, document changes and preserve historical versions before operational deployment.

04 / FEASIBILITY GATE

Before Building an Origin Integration

Confirm that the proposed functionality is technically and legally supportable. An attractive interface is not evidence that the underlying automation is feasible.

GO

Proceed with a Defined Scope

The applicable rules are identified, required data is available and the proposed controls can be tested.

HOLD

Resolve External Dependencies

API access, legal interpretation, data quality or document availability requires further confirmation.

NO-GO

Do Not Automate the Claim

Essential evidence is unavailable, a necessary interface is inaccessible or the proposed result cannot be substantiated.

A Practical Sequence for Development

Begin with a narrow, verifiable use case. Expand only when the previous stage has demonstrated reliable results.

PHASE 01

Define the Legal Scope

Select the origin framework, arrangement, product categories and intended output.

PHASE 02

Validate Data & Access

Confirm input availability, evidence quality and any required external service access.

PHASE 03

Test Against Known Cases

Compare results with independently reviewed examples, including exceptions and borderline cases.

PHASE 04

Deploy with Oversight

Monitor rule changes, preserve audit records and define escalation procedures.

CORE PRINCIPLE

Automation Should Make Uncertainty Visible.

An origin system is more trustworthy when it clearly identifies missing evidence and unresolved legal conditions than when it produces a definitive answer without a defensible basis.

06 / INTEGRATION STRATEGY & OFFICIAL RESOURCES

From Origin Rules
to Reliable Decisions.

A successful origin integration connects legal requirements, commercial data and supporting evidence without confusing an automated assessment with an official customs decision.

The most effective approach starts with a clearly defined scope, verifies external dependencies early and maintains a traceable record of every assessment.

Four Foundations for a Reliable Integration

Origin-related software should be designed around a verifiable decision process rather than an assumption that all checks can be performed through a single API.

01 / DEFINE

Define the Legal Scope

Identify the preferential arrangement, relevant product classification, applicable origin criteria and assessment date before implementing automated logic.

DELIVERABLE Documented rules and assumptions
02 / VALIDATE

Validate the Evidence

Review product records, bills of materials, supplier declarations, production details and relevant values. Missing or inconsistent evidence must trigger an exception.

DELIVERABLE Traceable and reviewable inputs
03 / CONNECT

Confirm Technical Access

Determine which official resources, databases or permitted interfaces are actually available. A public verification webpage is not necessarily a machine-to-machine API.

DELIVERABLE Verified access and integration scope
04 / GOVERN

Maintain Human Oversight

Preserve the rule version, source data, verification results and review history. Escalate cases involving uncertainty, insufficient evidence or disputed origin.

DELIVERABLE Auditable decisions and escalation
02 / CONCEPTUAL OPERATING MODEL

Connect Data. Preserve Evidence.

An origin assessment workflow should retain a clear boundary between enterprise information, assessment logic and any external verification services.

REFERENCE MODEL
INPUT LAYER

Enterprise Data

ERP · BOM · Supplier records

ASSESSMENT LAYER

Origin Logic

Applicable rules · Validation

CONTROL LAYER

Evidence Review

Exceptions · Human oversight

Official Resources & Available Checks

Consult relevant legislation, published guidance and permitted verification services where applicable.

Versioned Audit Trail

Preserve source references, assessment dates, evidence and decisions for subsequent review.

This diagram is an architectural illustration. It does not represent an existing Customs Explorer API, an official EU integration endpoint or authorised access to customs systems.

Official Resources & Legal References

Origin assessments should be grounded in the relevant legal texts and official guidance, including the provisions of the specific preferential arrangement.

Source and access distinction: Official information pages, legislative databases and online validation tools do not by themselves establish the existence of a public API. Technical access, credentials and permitted usage must be confirmed with the relevant provider. Consult current consolidated legislation and the applicable preferential arrangement.

CUSTOMS EXPLORER / ORIGIN API

Automate the Process.
Never Hide the Uncertainty.

Digital origin assessment can improve consistency, traceability and efficiency. Its reliability depends on accurate inputs, applicable legal rules, verified evidence and clearly defined responsibility.

LEGAL CONTEXT VERIFIED EVIDENCE HUMAN OVERSIGHT
Explore Customs APIs

Customs Explorer provides educational information about customs processes and digital integration. This page does not provide an official origin determination, a binding customs decision or access to an operational origin API.