Maintain a product variant's customs and origin record

The customs and origin record brings together product-specific customs classifications, origin determinations, supplier declarations, market decisions, and compliance requirements. Use it for physical product variants. Digital products and services do not require a customs record.

After maintaining the record, you can check whether a physical variant is ready to ship to a destination country based on approved customs and origin data. The responsible roles remain accountable for the business and legal assessment of that data.

Prerequisites

You need:

read access to product variants and compliance data,
write access to the applicable customs and origin records,
a product variant with the Physical product capability,
compliance requirements and checks when a record must be approved,
Storage access when linking a supplier declaration file.

Open the product record

Open PIM > Variants & pricing > Variants.
Open a physical product variant.
Select Customs and origin.

Workspace shows this area only for physical variants. If it is missing, check the selected capabilities in the variant detail.

Distinguish the record types

Record type	Purpose
Product requirement	Links an existing compliance requirement to the product variant.
Customs classification	Stores the nomenclature, customs tariff code, and the country where the classification applies.
Origin determination	Stores non-preferential or preferential origin. Preference information belongs to a specific agreement.
Supplier declaration	Links the supplier, declaration type, file, checksum, and customs-specific metadata.
Market decision	Records whether shipping to a destination is allowed, restricted, or blocked.

Do not treat supplier declarations as contracts. Legally binding agreements remain in Contracts. Continue to attach general assessment evidence to the compliance check.

Create and approve drafts

New customs and origin records start as drafts. Create a new draft when a classification, origin, document, or market decision changes. Do not overwrite an approved state.

A revision becomes active only after a successfully closed compliance check for the same product variant confirms it. This keeps the check, its evidence, and the approved product state connected. Corrections create a new revision; the previous state remains traceable.

Check shipping readiness

Select a destination country in the product record.
Select Check readiness.
Resolve any displayed blockers.

For a physical variant, readiness requires at least:

an active customs classification that applies to the destination or globally,
an active non-preferential origin,
no active restricted or blocked market decision for the destination.

Preferential origin and supplier declarations remain visible in the record, but the first product increment does not interpret them as universal minimum requirements for every shipment.

Shipping decision

At the relevant shipping transition, Workspace checks the same approved data again. A blocker prevents the transition. After a successful decision, Workspace stores an immutable snapshot containing the used revisions, requirements, destination country, and result.

Later changes to the product record do not change this shipment evidence.

Verify the result

A dependable record meets these conditions:

The variant is marked as a physical product.
Applicable compliance requirements are linked.
Customs classification and non-preferential origin are active.
Supplier declarations reference the correct Storage object.
Destination-specific market decisions are current.
Readiness shows no blocker for the intended destination.

Common problems

Customs and origin is not available: The variant is not marked as a physical product.

Readiness reports a missing classification: Check the jurisdiction country, validity period, and approval status.

Readiness reports a missing origin: Preferential origin does not replace non-preferential origin. Maintain and approve a non-preferential state.

A draft remains inactive: Check that a successfully closed compliance check confirms this exact product variant and revision.