Updated: 23.06.2025
The article outlines the main functional changes affecting users of the ASL BELGISI National Information System (NIS).
Changes to the public programmatic interaction interfaces (API) used for automated integration with the marking system are presented in a separate section: API and Technical Documentation.
1. Tax Residency Registration
As is: The user's tax residency country is not stored during registration.
To be: When registering a company that is not a tax resident of the Republic of Uzbekistan, the country of tax residency must be specified.
2. Email Confirmation
As is: The email address is not verified during user registration.
To be: The user must confirm the email address by following an activation link.
3. Access to Personal Account
As is: Only the head of the organization can access the personal account.
To be: The head of the organization can add users who will be able to work in the organization’s personal account (via authentication using an individual’s digital signature).
4. User Permissions
As is: All personal account users have equal rights (access levels).
To be: The head of the organization can define individual access rights for each user, restricting access to specific functions.
5. GCP Entry
As is: The manufacturer identifier (GCP) is entered manually by the company.
To be: The manufacturer identifier (GCP – Global Company Prefix), required for registering products in the catalog of marked goods, is entered by the marking system operator.
6. Emission Type and Marking Purpose
As is: The “Emission Type” is specified in the code issuance request. The method of market entry (production or import) is indicated in the code application/use report.
To be: The marking purpose is specified in the code issuance request (e.g., primary marking for production or import, marking of remaining stock, etc.).
7. Paid Marking
As is: The “Tariff” field is optional in the code issuance request.
To be: The request may include a “Consent to Paid Marking” parameter. If the value is set to “No,” the request must only contain products eligible for free code issuance; otherwise, the request will not be processed.
8. Link to Product Card
As is: The marking code is linked to the product card via the product code (GTIN).
To be: The marking code is linked both to the product code (GTIN) and to the specific product card registered by the code issuer. If several product cards are registered for the same foreign product by different importers, codes will be linked to the specific importer’s product card.
9. Product Card Validation
As is: The presence of the product card in the catalog of marked goods is checked asynchronously (after request registration).
To be: The presence of the product card is checked synchronously during the request. If the product is not in the catalog, the request will be rejected.
10. Packaging Serial Number Formation
As is: The packaging serial number (AI 21) is generated randomly.
To be: The first character of the serial number is a fixed value “U” (indicating the country of code issuance, required for international recognition processes). The total length and format of the codes remain unchanged.
11. Country of Origin
As is: The country of origin is stored only in the product card.
To be: The “Country of Origin” is specified in the code application/use report. It is validated against the catalog of marked goods and stored in the marking code data. The “Country of Origin” field in the catalog can contain multiple values.
12. Report for the "Household Appliances" Product Group
As is: No report on code application/use is required for this group.
To be: All product groups, including “Household Appliances,” must submit a report with used codes, country of origin, and additional data (production date, batch, and expiry date).
13. Label for “Household Appliances”
As is: Codes are exported as ready-made labels.
To be: Exported as a ready-made label using a unified template that contains only the DataMatrix code (no additional fields).
14. Report: Method of Market Entry
As is: The report does not include information about the market entry method.
To be: The method of market entry (production or import) must be specified in the report and must correspond to the product’s country of origin.
15. Assignment of “In Circulation” Status
As is: Based on primary documents.
To be: For goods produced in Uzbekistan, the “In Circulation” status is assigned automatically after processing the code application/use report. For foreign goods, it is assigned after information about release into free circulation (import) is received.
16. Transport Packaging Code (KITPU)
As is: The code can be specified without AI(00).
To be: The transport packaging code (KITPU) must include AI(00) and consist of exactly 20 digits (first two always “00”, followed by 18-digit SSCC). The SSCC must comply with GS1 standards and include an extension digit, GCP, serial number, and check digit.
17. Access to Marking Code Information
As is: Visible only to the current code owner.
To be: Authorized users can view basic information about any marking code via search (status, GTIN), regardless of ownership. Detailed information is still available only to the current owner.
18. Public API: Data Structure
As is: Provides owner and packaging composition data.
To be: Public information includes code status, packaging type, GTIN, product card ID, issuer, production date, batch, and expiration date. For group and transport packaging, only aggregate content is shown (product group and quantity). The list of nested codes (children) is available only to the current owner.
19. Primary Documents
As is: Can be downloaded only for certain operations (receipt, customs declaration, write-off act).
To be: Authorized users can view the contents of all documents received by the marking system (in JSON format).
20. Search by External Identifier
As is: External documents were assigned internal identifiers.
To be: Users can search for documents using external identifiers assigned by the source system (e.g., ASUTP order ID, facturaId for invoices).
21. Code Issuance by Service Provider
As is: Can be submitted by service providers.
To be: Code issuance requests can only be registered by trade participants. Other operations (validation, labeling, aggregation) may still be submitted by service providers.
22. Separation of Service Provider Operations
As is: Not separated.
To be: Operations submitted by service providers (code retrieval, validation, labeling, aggregation reports) are recorded in a separate registry.
23. Aggregated Import Code (AIC) for Medicines
As is: Formed by the importer.
To be: The importer must obtain the manufacturer's confirmation of rights transfer before forming an AIC. The transfer is formalized through a “Certificate of Transfer” (reverse acceptance) prior to placing the medicines into circulation in Uzbekistan.
Comments
Article is closed for comments.