Medicine Blocked at the Register via MDLP — Four Cause Types and a Full Unblocking Algorithm for Pharmacies

The customer is at the counter. The pharmacist scans the package, and instead of a receipt, the screen shows an error. The sale is blocked. According to market participants, the labeling error rate accounts for 1–2% of trade turnover. For a large pharmacy chain, that translates to millions of rubles worth of medicines sitting on shelves, unable to be sold.
Since June 1, 2025, a permissive authorization mode for the labeling of medicinal products (hereinafter — MPs) has been in effect across Russian pharmacies. Before every sale, the point-of-sale software sends a request to the Drug Movement Monitoring System (hereinafter — MDLP) and waits for authorization. If the system detects an issue, the cash register blocks the transaction. Bypassing the system is not an option: doing so is an administrative offense and, in certain cases, a criminal one.
This guide covers a full classification of blocking causes, step-by-step unblocking procedures for each situation, and clear instructions for pharmacists and pharmacy managers.

How the Notification Mode Worked

Prior to June 1, 2025, the labeling system operated differently. A pharmacy would scan the Data Matrix code on the packaging, the information was sent to the MDLP, and that was the end of it. A drug could be sold even if the system found no records of it or detected discrepancies.
This procedure had been in place since 2020 and was extended several times. The operator of the Chestny ZNAK system (CRPT) refined the infrastructure while market participants connected their IT systems and established document workflows. The transition to the permissive mode was repeatedly postponed.
The core flaw of the notification scheme: it could not stop the sale of a substandard or recalled drug. Violations were recorded after the fact, once the medicine was already in the buyer’s hands.

What Changed in June 2025

Federal Law No. 292-FZ dated August 8, 2024, introduced amendments to Article 57 of Federal Law No. 61-FZ dated April 12, 2010, «On the Circulation of Medicines» (hereinafter — FZ-61). The updated Article 57 established a direct ban on the sale of MPs in six specific cases. The application procedure and phased implementation timeline were set out in Government Decree No. 257 dated March 3, 2025 (hereinafter — PP No. 257).

Six Grounds for Blocking

Under Part 2 of Article 57 of FZ-61, the sale of MPs for medical use is prohibited in the following cases:

No.	Ground	Online from	Offline from
1	No record of identification means being applied	June 1, 2025	Not before March 1, 2026*
2	No record of introduction into civil circulation	June 1, 2025	Not before March 1, 2026*
3	Data entry into MDLP is blocked	June 1, 2025	September 1, 2025
4	Application suspended by order of the Ministry of Health	June 1, 2025	September 1, 2025
5	Civil circulation terminated	June 1, 2025	Not before March 1, 2026*
6	Shelf life has expired	June 1, 2025	Not before March 1, 2026*

*Extended checks are scheduled to take effect March 1, 2026; the exact date will be established by a separate Government Decree.

How the Verification Works Technically

When a Data Matrix code is scanned, the cash register sends a codes/check API request to the MDLP. The system checks the drug’s status, expiration date, and any active blocks, then returns the result. The full cycle takes up to 1.5 seconds.
To speed up data exchange, Chestny ZNAK has deployed a CDN (Content Delivery Network) — a network of geographically distributed servers. This reduces latency for cash registers across different regions.
If no response arrives within 1.5 seconds (no internet or a system outage), the software switches to a local database. This database is built by querying the MDLP and must be refreshed at least once every 2 hours during the pharmacy’s working hours (PP No. 257). Offline verification requires the Local Chestny ZNAK Module version 1.5.0 or higher, which the operator provides at no charge.

Diagnosing the Cause of the Block

When the cash register blocks a sale, a message appears on screen. The exact wording depends on the POS software, but the meaning is always the same: the sale is prohibited. The pharmacist’s task is to identify the cause within 3–4 minutes — either to fix it on the spot or escalate to the pharmacy manager.

Reading POS Software Messages

Modern systems (1C:Apteka, SmartApteka, and others) display a specific MDLP error code:

Error message	Most likely cause	First step
«Code not found»	Error in the CRPT database or incorrect scan	Check via the Chestny ZNAK mobile app
«Item not released for circulation»	Acceptance or manufacturer’s input is incomplete	Check the waybill status
«Shelf life expired»	The sell-by date has passed	Remove from sale
«Owner verification error»	The drug is registered under a different TIN or address	Initiate a correction in MDLP
«Product blocked»	Decision by Roszdravnadzor or the Ministry of Health	Isolate immediately

Three steps for rapid diagnosis:

Read and note the error code on the cash register.
Scan the same code with the Chestny ZNAK mobile app — it will show the drug name, manufacturer, expiration date, and current status. If the app shows «In circulation» with the correct owner but the register still blocks the sale, the problem is in the POS module settings.
Log into the MDLP personal account (mdlp.crpt.ru), find the drug by SGTIN code, and review its movement history: when it entered circulation, who transferred ownership rights, and whether acceptance was completed.

Classification of Causes and Unblocking Procedures

Type A. Technical Problems (Resolved by the pharmacy)

Online verification failure or no internet connection

The cash register receives no response from MDLP and displays a connection error or timeout.
Steps:

Check the internet connection.
In the POS software settings, review the CDN node list and select the server with the lowest latency.
Confirm that the Local Chestny ZNAK Module is installed and updated to version 1.5.0+.
If offline verification is permitted for this drug category, switch to it.
Log the outage — time and duration — in the pharmacy’s information system.

If the system is inaccessible, the pharmacy may operate using the offline database and must restore connectivity within a reasonable timeframe (Government Decree No. 1944).

Authorization token expired

All drugs at the register are blocked simultaneously. This almost always means the digital access key to MDLP has expired. Each register communicates with the system via a token generated in the Chestny ZNAK personal account, which has a limited validity period.
Steps:

Log into the Chestny ZNAK personal account with administrator credentials.
Go to «Permissive Mode» → «Tokens for Cash Registers (KKT).»
Check the expiration date of the current token.
Generate a new token if needed.
Update the token in the POS software (in 1C:Apteka: «Administration» → «IS MP Integration Settings»).

Drug not accepted into the pharmacy’s balance

The system shows the drug on the supplier’s balance, not the pharmacy’s: the acceptance process was not completed. In reverse acceptance, the pharmacy sent an acceptance notification (Document Type 701) but the supplier did not confirm the transfer.
Steps:

Check the status of acceptance documents in the inventory management system.
If the supplier has not confirmed the transfer within 1 business day, the pharmacy may use the KKT/RV pending registry mechanism, which allows the sale to proceed without supplier confirmation. This mechanism is valid for 14 calendar days under reverse acceptance.
If 14 days pass with no confirmation, contact the supplier. Selling without resolution may be treated as a violation.

Code scanning error

The code cannot be read or is scanned incorrectly: the packaging is damaged, the code is dirty, or the scanner is faulty.
Steps:

Clean the surface of the packaging.
Try a different scanner or adjust the scanning angle.
Enter the SGTIN manually if the software allows it.
If the code is entirely unreadable, proceed to the damaged code procedure (Type D).

Type B. Supplier Errors (Require a formal claim)

Drug not introduced into civil circulation

The manufacturer or importer did not complete the introduction of the drug into civil circulation in MDLP. Under Government Decree No. 815 dated May 31, 2025, this is the manufacturer’s responsibility: they must submit data to the Roszdravnadzor system before releasing each batch.
Steps:

Isolate the drug from the sales floor.
Document the block — take a screenshot and make a log entry.
Send a formal claim to the supplier specifying the SGTIN and batch number.
The supplier must contact the manufacturer or Registration Certificate (RC) holder to resolve the issue.
If the problem is not resolved within 3–5 business days, process a return.

Broken supply chain

According to MDLP, the drug is registered to another entity, not the current owner. Someone in the distribution chain failed to submit data on the transfer of ownership rights.
Steps:

Check who currently holds the drug in the MDLP personal account.
Contact the supplier to clarify the situation.
The supplier must restore the document chain.
Do not sell the drug until the issue is resolved.

Unconfirmed acceptance under direct acceptance

The supplier submitted shipment data (Document Type 601), but the pharmacy has not confirmed receipt.
Steps:

Complete the acceptance process in the pharmacy’s inventory management system.
Scan the codes of the received drugs.
Send the acceptance confirmation to MDLP (Document Type 701).
Wait for the status to update — this typically takes 5–10 minutes.

Type C. Regulatory Blocks (The drug cannot be sold)

Suspension by order of the Ministry of Health

The Ministry of Health has decided to suspend the use of a specific batch or an entire drug — for example, following adverse reaction monitoring.
Steps:

Immediately isolate all packages of the affected batch.
Verify the information on the official Roszdravnadzor website.
Prepare a withdrawal act.
Store the isolated product separately.
Await the official decision — either a lift of the suspension or a full recall.

Termination of civil circulation (Roszdravnadzor recall)

Roszdravnadzor has identified a batch with quality deviations — a substandard, counterfeit, or falsified drug. Under Part 1 of Article 57 of FZ-61, the sale of such drugs is strictly prohibited. The block takes effect instantly across all pharmacies in the country.
Steps:

Immediately remove the drug from the sales floor.
Prepare a withdrawal act specifying the batch number and quantity.
Place the items in a quarantine zone.
Notify the supplier.
Await instructions on returns or disposal.

Selling such a drug carries the risk of criminal liability.

Shelf life expired

MDLP automatically blocks drugs with an expired date. Ministry of Health Order No. 100n dated March 7, 2025, explicitly prohibits dispensing such products.
Steps:

Remove the drug from the sales floor.
Prepare write-off documents (Document Type 552, type 13 in MDLP).
Hand over for disposal in accordance with the established procedure.

Data entry blocked in MDLP

The system operator has blocked data entry for a specific code — for example, due to suspected duplication.

Steps:

Isolate the drug.
Contact CRPT technical support to determine the cause.
If authenticity is confirmed, request unblocking.
If counterfeiting is suspected, report it to Roszdravnadzor without delay.

Type D. Damaged Traceability Code

Physical damage to the code

The code is erased, damaged, or unreadable. Industry data suggests up to 0.5% of packages have print quality issues or physical damage to the code.
Steps:

Try reading the code using multiple methods — different angles, different scanners.
Check whether the human-readable portion (GTIN and serial number below the barcode) is still intact; if so, enter it manually.
If the code is completely unreadable, the product is treated as defective. Process a supplier return or write-off (Document Type 552).

Code not found in the system

The code scans correctly but MDLP cannot find it in the database. Possible causes: the manufacturer did not register the code in the emission system, a generation error occurred, or this is a counterfeit with a fabricated code.
Steps:

Isolate the drug.
Check other packages from the same batch.
Request information from the supplier.
If counterfeiting is suspected, report it to Roszdravnadzor.
Do not sell pending clarification.

Instructions for the Pharmacist

When a block occurs, follow this procedure:

Stay calm. A block does not mean the drug is defective. The cause may be purely technical.
Read the screen message. Note the error code.
Rescan. Changing the angle or wiping the package surface sometimes resolves the issue.
Explain to the customer. Suggested phrasing: «The state traceability system is currently unable to confirm the status of this specific package. Please give me a moment to look into it» — or: «There is a restriction on this package. I can offer you a different batch or an equivalent product.»
Offer an alternative: another package from the same batch, a product from a different manufacturer, or offer to call the customer back once the issue is resolved.
Call the manager if: it is a regulatory block, the same drug has been blocked repeatedly, there is a conflict with the customer, or the entire cash register is blocked.

Four things a pharmacist must never do:

Attempt to bypass the block (scan a different package’s code, sell without scanning).
Blame the system or the manufacturer in front of the customer.
Sell an expired drug or one recalled from circulation.
Conceal a block from the manager.

Two phrases that are strictly off-limits: «This is a fake drug» (you cannot make that claim without evidence) and «The software is just glitching — it’s nothing» (this undermines trust in the quality control system).

Instructions for the Pharmacy Manager

Daily checks

Monitor the Local Chestny ZNAK Module: the database must refresh every 2 hours. Track authorization token expiration dates for all registers and renew them before they lapse. Review acceptance document statuses in the MDLP personal account.
Monitor roszdravnadzor.gov.ru (the recalled medicines search service). When new recall notices appear, immediately check whether the listed batches are in stock.

Pre-sale verification

A proactive approach that prevents incidents: scan codes at the shelf-stocking stage, not at the point of sale. Staff stocking shelves scan each Data Matrix code using a data collection terminal (DCT) or the Chestny ZNAK app. Packages with issues are set aside for follow-up; only drugs with a confirmed status go on the shelves.

Claims management with the supplier

When supplier errors are identified:

Gather evidence: MDLP screenshots, copies of waybills, and the blocking log entry.
Send a written claim with the SGTIN, batch number, and a clear description of the problem. Set a resolution deadline of 3–5 business days.
If the issue is not resolved, process a return (Document Type 415 in MDLP). For a supplier with repeated violations, consider switching contractors.

Chestny ZNAK technical support

Phone: 8-800-222-15-23
Email: support@crpt.ru (subject line: «Permissive Mode»)
Personal account: markirovka.ru → Support

When contacting support, provide the organization’s TIN, the SGTIN of the affected drug, and error screenshots. Requests flagged «Permissive Mode» are handled with priority.

What to Do Right Now

For the pharmacy manager:

Verify technical readiness. Confirm that Local Chestny ZNAK Module version 1.5.0+ is installed and up to date, that the offline database refreshes every 2 hours, and that authorization tokens for all registers are active.
Train the team. Run a briefing on the blocking response procedure, prepare a quick-reference card with customer communication scripts, and designate an escalation contact.
Set up documentation. Create a blocking log, draft claim templates for suppliers, and designate a physical quarantine area for isolated drugs.
Set up monitoring. Subscribe to Roszdravnadzor alerts, bookmark the recalled medicines search page, and schedule a weekly inventory reconciliation with MDLP.
Roll out pre-sale verification. Start with the top 50 products by turnover.
Align with suppliers on the return procedure for problem goods, claim response timelines, and contact details for responsible persons.

For the pharmacist:

Learn the POS screen. Know where the blocking reason appears and what the error code looks like.
Install the Chestny ZNAK app on your work phone and practice scanning codes.
Memorize two customer scripts — a neutral one and one that offers an alternative.
Know the four situations that require calling the manager: regulatory block, recurring issue with the same drug, customer conflict, or a full register lockout.

Drugs blocked due to labeling errors become dead stock: they take up shelf space, require storage conditions, and generate no revenue. Getting to the root cause in 3–4 minutes — instead of several hours — means getting the product back into circulation and stopping the financial bleed.

Regulatory Base:

Federal Law No. 61-FZ dated April 12, 2010, «On the Circulation of Medicines» (as amended July 23, 2025)
Federal Law No. 292-FZ dated August 8, 2024, «On Amendments to Article 57 of FZ-61»
Government Decree No. 257 dated March 3, 2025, «On Approval of the Rules for Applying the Provisions of Part 2 of Article 57 of FZ-61»
Government Decree No. 1556 dated December 14, 2018, «On Approval of the Regulation on the MDLP» (as amended September 29, 2025)
Government Decree No. 1944 dated November 21, 2023, «On the Permissive Mode for the Sale of Labeled Goods»
Government Decree No. 815 dated May 31, 2025, «On the Procedure for Introducing Medicinal Products into Civil Circulation»
Ministry of Health Order No. 100n dated March 7, 2025, «On Approval of the Rules for Dispensing Medicinal Products»
Code of Administrative Offenses of the Russian Federation (CAO RF), Articles 6.33, 6.34, 15.12
Criminal Code of the Russian Federation (CC RF), Article 171.1

This page in Russian→