Yüklənir

Trade Declarations

A Trade Declaration records a company's supported classification or origin declaration for a product release or selected batch, in a target market and period. It preserves the declaring company, scheme, scheme edition, classification code, evidence, and review history.

For example, one approved release can carry different declarations for different target markets or scheme editions. A batch-specific origin statement concerns that batch rather than every item ever manufactured from the model.

Category, external classification, and origin

Actualog categories remain the product's source taxonomy. External classification codes are declarations or mapping outcomes, not replacement product identities or additional Actualog category branches.

Origin is explicitly declared when supported. A factory address, seller address, warehouse, or destination does not automatically establish origin. Local approval is not a guarantee of external acceptance.

Who prepares and reviews declarations

A Product Editor, Product Governance Manager, Company Administrator, or permitted declaration preparer creates a draft for the release-administering company. Approval requires Product Governance Manager, Company Administrator, or explicit declaration-approval delegation. A manufacturer/seller relationship does not automatically grant permission.

Create and review a declaration

  1. Open Logistic → Compliance → Trade Declaration, search existing records, and choose + Create new trade declaration.
  2. Select the release and, for a batch-specific declaration, a matching batch.
  3. Select the actual declaring company. Enter Target Market, Classification Scheme, Scheme Edition, and the genuine Classification Code.
  4. Enter Origin Country Code only when supported; the current form expects a two-letter code. Select applicable Reference Collection and Evidence Statement sources.
  5. Add applicability dates and create the draft.
  6. Apply Submit under Lifecycle decision. An authorized reviewer checks scope, edition, code, and evidence, then applies Approve or Reject with a reason.

Entity selectors use names; the classification code is the external scheme's actual code, not an internal record identifier.

Corrections, blockers, and maintenance

Create a new declaration using Supersedes Declaration to replace an earlier approved declaration for the same subject, market, and scheme. Approval preserves and withdraws the predecessor. Do not rewrite an approved record.

Competing approved declarations for the same scope and overlapping period block approval unless supported explicit supersession resolves them. Separate markets can have separate supported declarations.

Missing market/edition/code, mismatched batch, invalid origin format, incompatible Reference Collection, unsupported evidence or predecessor, invalid dates, and stale form versions can block the operation.

Review when schemes, evidence, markets, or manufacturing circumstances change. Refresh affected passport and channel drafts separately. A Trade Declaration alone neither publishes a passport nor submits a catalog listing.

Evidence statements · Production batches · Transport declarations · Catalog publishing