Marking of remaining stock will become available for goods specified in the Decree of the Government of the Russian Federation dated November 21, 2025, No. 1855.

✅ The document to be available: “Introduction into circulation. Remaining items” (LP_INTRODUCE_OST)

Submission of the “Introduction into circulation. Remaining items” document (LP_INTRODUCE_OST) in * .json format will be available for codes with the REMAINS emission type (Marking of remaining items).

For the description of the document, see True API documentation (it is published in a user account on the production environment and in the knowledge base of the “Integrators Register”).

March 31, 2026

Import from the Republic of Armenia will be available within the framework of mutual recognition of identification codes. This means that the marking system will ensure receipt, processing, and recognition of marking codes issued in the marking system of the Republic of Armenia and specified in the cross-border shipment document received from the Operator of the Republic of Armenia.

Import will be implemented as follows:

After successful processing of the “Acceptance of shipment from EEU” document (LP_ACCEPT_GOODS), the importer becomes the owner of the marking codes, and their status changes to In circulation.

✅ The document to be available: “Acceptance of shipment from EEU” document (LP_ACCEPT_GOODS) submitted in response to the “Shipment from EEU with IC recognition” document (EAS_CROSSBORDER)

Distinctive features that are planned to be implemented:

For the description of the documents, see True API documentation (it is published in a user account on the production environment and in the knowledge base of the “Integrators Register”).

A new process of export to the Republic of Armenia will be implemented under the mutual recognition of marking codes:

✅ The “Shipment to EEU” document (EAS_CROSSBORDER_EXPORT) will become available

Distinctive features that are planned to be implemented:

For the description of the documents, see True API documentation (it is published in a user account on the production environment and in the knowledge base of the “Integrators Register”).

Submission of information about aggregation and disaggregation of sets will become available. This will allow you to combine several non-identical goods units into a single package to sell them to the end consumer as a single product.

🔄 Documents to be modified:

Indication of the SET value (SIC) will become available in the following documents:

For the description of the documents, see True API documentation (it is published in a user account on the production environment and in the knowledge base of the “Integrators Register”).

The system will verify the presence and status of the permitting documents when introducing remaining stock into circulation. This will allow maintaining the relevance of permitting document details contained in the marking system for the codes.

🔄 The document to be modified: “Introduction into circulation. Remaining items” (LP_INTRODUCE_OST)

When remaining stock of units of goods (including those nested into the aggregate) is introduced into circulation, the system will verify the presence and status of the permitting document.

Verification will be performed sequentially:

Introduction into circulation will fail if a permitting document for at least one code:

For the description of the document, see True API documentation (it is published in a user account on the production environment and in the knowledge base of the “Integrators Register”).

If a lot number is specified when withdrawing from circulation within volume and grade accounting, the system will verify the presence of this lot number in the lot register. This will eliminate the possibility to indicate nonexistent lots and increase accuracy of control over goods tracking.

🔄 The document to be modified: “Withdrawal from circulation (volume and grade accounting)” (LK_GTIN_RECEIPT)

A lot number will be verified when forming a group package: it must be identical for all nested items. This will exclude the possibility of adding units of goods with different lot numbers and allow automatic assignment of the lot number to the formed group package.

🔄 The document to be modified: “Aggregation of packaging” (AGGREGATION_DOCUMENT)

The ability to generate a report on goods cards with a full dataset will be available. Using this report, you will be able to obtain all attributes contained in goods cards of the National catalog.

✅ The method to be available: “Obtaining information on goods cards” (dispenser/tasks)

In the “Obtaining information about goods cards” method (dispenser/tasks), the product-cards-construction value (Report on goods cards — mandatory attributes (Building materials)) will be added to the reportId parameter (Identifier of the export type).

For the method description, see the True API documentation (it is published in a user account on the production environment and in the knowledge base of the “Integrators Register”).

Starting April 1, 2026, marking of remaining stock will become unavailable in accordance with the Decree of the Government of the Russian Federation dated December 25, 2025, No. 2136.

❌ Document to be disabled: “Introduction into circulation. Remaining items” (LP_INTRODUCE_OST)

Starting April 1, 2026, ordering marking codes using the method of release of goods into circulation, REMAINS (Marking of remaining items), submitting the application report (UTILISATION) for such codes, and submitting the document, “Introduction into circulation. Remaining items” (LP_INTRODUCE_OST), will become unavailable.

You will be able to update important characteristics of the previously issued marking codes independently, without contacting the Technical Support Service.

✅ The document to be available: “Correction of information on codes” (CIS_INFORMATION_CHANGE)

By using the “Correction of information on codes” document (CIS_INFORMATION_CHANGE), you will be able to change the following:

Additionally, for meat products, the following data can also be updated:

For the description of the document, see True API documentation (it is published in a user account on the production environment and in the knowledge base of the “Integrators Register”).

You will be able to submit information about generation of group package in the “Aggregation of packaging” document (AGGREGATION_DOCUMENT) and about disaggregation of group package in the “Disaggregation of packaging” document (DISAGGREGATION_DOCUMENT).

This feature will allow you to combine several identical goods units into a single package for sale to the end consumer — not as separate items, but as a unified product.

🔄 The documents to be modified:

A simplified process of engine oils import from the Kyrgyz Republic to the Russian Federation is planned for implementation.

The following scheme will be implemented to import goods under the simplified process:

✅ The document to be available: “Acceptance of shipment from EEU” (LP_ACCEPT_GOODS) in response to the “Shipment from EEU” document (LP_SHIP_GOODS_CROSSBORDER)

Requirements for filling in parameters in the “Acceptance of shipment from EEU” document (LP_ACCEPT_GOODS) will be similar to those used when importing the goods from the Republic of Belarus.

For the description of the documents, see True API documentation (it is published in a user account on the production environment and in the knowledge base of the “Integrators Register”).

For canned foods, you will be able to obtain the virtual warehouse information via the True API export generation method. This will allow goods circulation participants to monitor stock levels and track movement of goods within the warehouse.

✅ Method to be available: "Obtaining information about virtual warehouse, including batch accounting" (dispenser/tasks)

When requesting a list of documents, it will be necessary to specify a date range for which data are requested, or to indicate additional filtering parameters.

This change is intended to improve the stability and performance of the method when processing large volumes of documents.

🔄 The method to be modified: "Method of receiving a list of documents loaded in TT GIS" (/api/v4/true-api/doc/list)

The logic of using the dateFrom (Document date, from) and dateTo (Document date, to) request string parameters will be changed as follows:

Additionally, the allowed date range between dateFrom and dateTo will be limited.

If these conditions are not met, the method will return an error.

For the description of the method, see True API documentation (it is published in the user account on the production environment and in the knowledge base of the “Integrators Register”).

Shipment information will be added to the virtual warehouse. This will allow you to track dairy products by specific shipment number.

🔄 The methods to be modified:

The following will be added to the "Method of obtaining the current balance in a warehouse" method (/warehouse/balance):

The following will be added to the "Method of getting a list of operations in a warehouse" (/warehouse/operations):

For the description of the methods, see True API documentation (it is published in a user account on the production environment and in the knowledge base of the “Integrators Register”).

Currently, dairy products are tracked through the system focused on the traceability of individual items (e.g., each bottle). Soon, batch-level accounting will be supported, enabling you to track entire batches of goods (for example, all the milk produced on a certain day from a single batch of raw materials).

Soon you will be able to:

These new features will allow you to:

✅ Methods to become available:

Import from the Republic of Armenia under the mutual recognition of identification codes will be available for the groceries. This means that the marking system will ensure the receipt, processing and recognition of the marking codes issued by the marking system of the Republic of Armenia and specified in the cross-border shipment document received from the Operator of the Republic of Armenia.

The import process will be implemented as follows:

After successful processing of the “Acceptance of shipment from EEU” document (LP_ACCEPT_GOODS), the importer becomes the owner of the marking codes, and their status changes to INTRODUCED (In circulation).

✅ The document to be available: “Acceptance of shipment from EEU” document (‘LP_ACCEPT_GOODS’) submitted in response to the “Shipment from EEU with IC recognition” document (‘EAS_CROSSBORDER’)

A new process of export to the Republic of Armenia will be implemented under the mutual recognition of marking codes for the groceries:

✅ The “Shipment to EEU” document (EAS_CROSSBORDER_EXPORT) will become available

Distinctive features that are planned to be implemented:

For the description of the documents, see True API documentation (it is published in a user account on the production environment and in the knowledge base of the “Integrators Register”).

In the near future you will be able to directly handle consumers feedback submitted via Chestny ZNAK mobile app, including:

How this will work:

This makes you the first to review and respond to consumer complaints — delivering significant advantages:

Access to this feature will be provided upon signing the agreement for handling consumer feedback. You may submit a connection request to Technical Support after the feature is launched.

✅ New methods to be available:

For the dairy products you will be able to submit information on shipment of goods to the Republic of Belarus by using the “Shipment to EEU” document (EAS_CROSSBORDER_EXPORT) in * .json format.

✅ Document to be opened: “Shipment to EEU” (EAS_CROSSBORDER_EXPORT)

Distinctive features that are planned to be implemented:

For description of the document, see True API documentation (it is published in a user account on the production environment and in the knowledge base of the “Integrators Register”).

Announced in v.430.0 dated June 19, 2025

For the dairy products, when correcting a shipment number, additional checks will be made in the “Correction of information on codes” document (CIS_INFORMATION_CHANGE).

🔄 Modifications in the document: “Correction of information on codes” (CIS_INFORMATION_CHANGE)

Correction of the IC shipment number will be available, provided that the following conditions are met:

For description of the document, see True API documentation (it is published in a user account on the production environment and in the knowledge base of the “Integrators Register”).

The ability to indicate the Republic of Belarus as a destination country will be closed when submitting information about export via the “Withdrawal from circulation” document (LK_RECEIPT, LK_RECEIPT_CSV, LK_RECEIPT_XML)

❌ The “Withdrawal from circulation” document (LK_RECEIPT, LK_RECEIPT_CSV, LK_RECEIPT_XML) will be closed for export to the Republic of Belarus

The ability to indicate information about the Republic of Belarus will be unavailable in the destination_country_code (Code of the destination country) and importer_id (INN (or analog) of the importer) parameters in the “Withdrawal from circulation” document type (LK_RECEIPT, LK_RECEIPT_CSV, LK_RECEIPT_XML).

To export goods to the Republic of Belarus, use the "Shipment to EEU" document (EAS_CROSSBORDER_EXPORT, EAS_CROSSBORDER_EXPORT_CSV).

🔄 Modified method: "Method of receiving information on goods item by goods GTIN" of version v4.

The "Method of receiving information on goods item by goods GTIN" of version v4 is being improved:

For description of the method, see True API document (it is published in a user account on the production environment and in the knowledge base of the “Integrators Register”).