KM Aggregation

Aggregation of marking codes is a key step in the digital marking system. It links marking codes applied to consumer packaging (bottles, cans, packs, etc.) with codes of group packaging (bundles, cartons, pallets, etc.) or transport packaging (boxes, pallets, etc.).

As a result of aggregation, an aggregation tree (or “nested structure”) is created, which stores relationships between all packaging levels:

Top-down:

• by pallet code, you can identify all group packages placed on that pallet;

• by group package code, you can identify all consumer packages contained within it;

Bottom-up:

• by consumer package code, you can identify the group package it belongs to;

• by group package code, you can identify the pallet it is placed on.

Why aggregation is needed

Aggregation enables end-to-end traceability and monitoring of marked goods across the logistics chain:

• when processing electronic documents (customs declarations, e-invoices, receipts, etc.), only group or transport package codes are scanned;

• during document processing, the system automatically “unpacks” the aggregation structure and registers the operation both for the aggregation code and for all nested packages.

Thus, aggregation at the production stage allows operations with marked goods to be performed using aggregation codes only, without scanning individual consumer packages. This simplifies inventory management and reduces the time required for shipment and acceptance of goods.

Supply chain participants can receive goods in aggregated packaging (by aggregation codes) and sell them either in aggregated form or as individual consumer units.

Aggregation report content

The aggregation report includes:

• general information (applicant, place of business activity, aggregation date and time);

• list of aggregation codes:

  • parent package code (aggregation code);

  • planned capacity (expected number of nested packages);

  • actual capacity (actual number of nested packages);

  • list of nested package codes.

Important notes:

• aggregation must be mono-product (i.e., refer to a single product / barcode);

• the manufacturer may update the aggregation structure by re-aggregating the relevant packages;

• the aggregation composition may change during circulation (e.g., when operations are performed with nested packages).

How to view aggregation composition

General aggregation data (product name and quantity) is publicly available via:

• the participant’s personal account;

• the Asl Belgisi mobile application for business;

• the public API of the marking system.

Detailed (code-level) composition is available only to the current owner of the respective marking codes.

How to verify aggregation

In the Asl Belgisi mobile application for business:

• scan the aggregation code;

• scan nested package codes (all or selectively);

• select “Verify”.

Large enterprises can implement aggregation verification in their own inventory systems using the public API of the marking system.

How to submit an aggregation report

1. Glossary

2. KM Aggregation Report Creation

3. Viewing Reports

4. General Principles of Aggregation Report Validation by the System

5. Disaggregation Status

Glossary

KM Aggregation Report Creation

To perform operations in the personal account of NIS “ASL BELGISI,” go to the “Code Operations” section and then to the subsection “Own Operations.” In the current section, click the button “Create Operation” → “KM Aggregation.”

The “KM Aggregation” operation can be performed only if the user has the “Document Creator – Aggregation” role activated. For more details on assigning roles, refer to the article: xTrace: User Profile - Assigning a Role to a User

In the "General Information" section, the following required fields marked with * must be filled out:

• Emitter's Place of Business Activity (POBA) – selected from the list of added locations

• Packaging Date – the date of aggregation formation

• Production Order Number – optional

In the "Aggregation Data" section, the following required fields marked with * must be filled out:

• Packaging Code – SSCC aggregation code or group packaging code

• Extract from parent packaging

• Maximum quantity per package – maximum capacity of the package

• Details of aggregated products (upload a .csv file) – upload a file containing the list of KI codes to be included in the aggregation

❗IMPORTANT: In the CSV file for the “Aggregation” report, the key and verification code (crypto tail) must not be included.

When uploading the file, the following conditions are checked:

• The file is in CSV format and not empty

• Each code is listed on a new line

• Only the following characters are used:
  ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789!”%&’*+-./_,:;=<>?()

• The codes in the file are unique (no duplicates)

Maximum number of packages placed directly into aggregates (first layer), by packaging type:

Viewing Reports

To view “KM Aggregation” operations in your personal account, go to the “Code Operations” section and set the filter in the “Operation Type” field.

The list displays reports with the following statuses:

• Under Review – The report is being checked by the system

• Partially Processed — The report contains invalid codes. The operation has been carried out only for valid codes; errors have been recorded for the remaining ones.

• Successfully Processed – The report was successfully processed

• Processed with Errors – The report was processed with errors. The reason is shown in the report interface

⚠️ To view service provider operations, go to the “Service Provider Operations” subsection.

General Principles of Aggregation Report Verification by the System

Through the user's personal account, creating an "KM Aggregation" is only possible for a single aggregation code.

All codes within the aggregation being formed must be single-commodity, meaning they must share the same GTIN.

Status: "Disaggregated"

"Disaggregation" refers to a breach of the integrity of a transport package.

The use of child codes within documents and operations leads to a change in the aggregate's state.

The table below shows the changes in aggregate state depending on the scenario of child code usage.

🟢 Formed (composition updated) 
🔴 Disbanded (codes unlinked) 
🔵 Operation over all codes (transfer / withdrawal / write-off)

When identification codes (ICs) nested within an aggregation are used in operations such as transfer/sale via ESF, retail sale, etc., the aggregation code loses its integrity and can no longer be used (it becomes disaggregated).

When a nested consumer code is moved to another KITU (while the originating KITU still contains other nested codes), the originating KITU is not disaggregated.