The shift to unit-level tracking changes not only product marking rules but also warehouse automation requirements. The WMS must now track every Data Matrix code from receiving to shipment, and 1C must pass that data to the UPD and GIS MT without errors. We cover which processes to check in WMS and 1C, why discrepancies arise between systems, what fines businesses face for marking errors, and how to prepare a warehouse for the new requirements.
5 critical WMS and 1C integration mistakes before switching to unit-level labeling tracking from June 1
Five WMS and 1C integration mistakes: direct exchanges with no contract, manual statuses, no monitoring, poor reference data, and launching without business metrics.
- Main changes in marking accounting
- Why GTIN no longer fits individual unit tracking
- How unit-level tracking changes warehouse and WMS operations
- How the Marking Chain Between Chestny Znak, WMS and 1C Should Work
Blog
Operational Pain Matters More Than the Dictionary Definition
These materials connect WMS, TMS, 1C and construction to clear metrics: marketplace fines, stock accuracy, EPD and manageable integrations.
WMS
Receiving, picking, packing and shipment are examined through the lens of marketplace fine risk and SLA loss.
Slotting
A wrong bin turns into extra travel for the picker, lower productivity and picking errors.
TMS/ERP/Construction
EPD, EDI and GIS EPD are tied to an integration architecture without fragile point-to-point exchanges.
Main changes in marking accounting
Since June 1, 2026 companies in new product categories must switch to item-level tracking. Now, through EDI it's necessary to transmit not only the GTIN and product quantity, but also the Data Matrix code of the specific product unit.
If the WMS and 1C can't handle this kind of data, the warehouse will face UPD errors, rejections from Chestny Znak, and a halt to part of its shipments.
The New Rules Will Affect
- salmon and sturgeon caviar
- coffee, coffee drinks and chicory
- an expanded range of light-industry products
From November 1, 2026, the requirements will extend to dairy products with a shelf life over 40 days.
Discuss your challenge with an architect
Why GTIN no longer fits individual unit tracking
Previously, a GTIN was enough for the warehouse to track goods and pass data to 1C.
This code indicates the product type:
- for example
- a specific type of coffee
- milk
- clothing
For batch-and-variety accounting this was enough, because the system worked only with the quantity of goods. Since June 1, 2026 the situation changes - the law requires recording the movement of each specific unit of goods separately.
This uses a Data Matrix code with a unique serial number.
Even two identical packages of the same product get different codes.
For this reason, the role of accounting systems is changing
WMS must do more than track inventory; it must link each code to a specific warehouse operation. 1C passes the already compiled data into the universal transfer document and EDI.
If codes get lost, duplicated, or diverge between systems, Chestny Znak rejects the document and blocks the shipment.
How unit-level tracking changes warehouse and WMS operations
With bulk/lot-based accounting, the system works with goods at the item-master level: it passes GTIN and quantity without tying them to specific units. This method remains only for some product groups, gradually giving way to unit-level tracking. After the switch, warehouse logic becomes more granular - the WMS records Data Matrix codes on receipt and tracks them inside the warehouse until shipment.
1C uses this data to generate the UPD and send it via EDI. CRPT notes, that businesses run into the most problems specifically during the transition to item-level tracking. Organizations that previously tracked only product quantity are running into WMS errors, discrepancies in 1C and stuck UPDs due to incorrect handling of codes.
The table lists the key documents and requirements to check before switching to item-level tracking.
| Regulation / Source | What changes | What to check in WMS and 1C |
|---|---|---|
| CIS Government resolutions on mandatory marking of specific product groups | Item-level tracking becomes mandatory for some categories. The UPD must carry the code of every product unit. | Does the WMS support storing and passing codes for every unit of goods. Does 1C correctly generate a UPD with the full list of codes. |
| Official Chestny Znak Requirements | GIS MT checks the goods' owner, the code status, and the correctness of data transfer. | Does the system check codes before shipment. Does the warehouse see errors before the UPD is sent. |
| Federal Tax Service UPD format for marked products | Requirements for the composition of electronic documents and code transmission via EDI are changing. | Does 1C support the current UPD format. Are codes lost during exchange with EDI. |
| CRPT Methodological Guidelines on Item-Level Tracking | New requirements appear for receiving, aggregation, storage and shipment of marked goods. | Can the WMS handle aggregation, serialization and group packaging? |
| Chestny Znak API documentation | The systems must exchange data with GIS MT and check the status of marking codes. | Is there a direct chain configured: WMS → 1C → GIS MT? Does the system handle errors and rejections automatically? |
How the Marking Chain Between Chestny Znak, WMS and 1C Should Work
-
01
The warehouse must pass Data Matrix codes without loss at every stage - from goods receipt to withdrawal from circulation. Consider an example chain where WMS, 1C, EDI and Chestny Znak work without discrepancies.
-
02
Supplier ships units with Data Matrix codes
and sends the electronic UPD via EDI. The document already contains the list of marking codes for all shipped items.
-
03
Warehouse worker receives goods via WMS and data terminal
The system reads each code, checks its status via the Chestny Znak API, and assigns it to a specific unit of goods and storage bin.
-
04
WMS sends receipt data to 1C
1C receives the list of codes, updates stock, and links the marked goods to accounting documents.
-
05
During storage, the WMS tracks the movement of every code
The program records which box, pallet or bin holds each unit, and coordinates package breakdown and partial shipments.
-
06
During shipment, the WMS checks codes before order picking
The operator scans the item while the system checks that only valid, non-withdrawn codes go into the shipment.
-
07
1C generates the UPD and sends it via EDI to GIS MT
The document automatically receives the full list of marking codes for the shipped goods.
-
08
Chestny Znak checks the document and records code retirement
After a successful check, the system updates the Data Matrix codes' status and confirms the shipment operation.
WMS logistics and 1C: 5 integration mistakes when moving to unit-level marking tracking
Below we cover the problems that most often keep a warehouse from working properly with marking.
Mistake #1. WMS Stores GTIN But Not Data Matrix Codes
Many companies still work under the old scheme: WMS tracks SKUs, batches and GTINs, while Data Matrix codes effectively bypass the system. A worker may scan the code on receiving, but WMS doesn't link it to a specific unit of product. As long as the business uses aggregate (batch-level) accounting, this doesn't create serious problems. But under item-level tracking, 1C must receive from WMS an exact list of the codes that are in the warehouse and involved in shipment. If WMS doesn't store this data, the system can't correctly generate the UPD. The result is discrepancies with GIS MT, retirement errors and stuck documents.
Mistake #2. WMS and 1C Use Different Item Reference Data
Even if the warehouse stores the codes, failures often stem from discrepancies between the WMS and 1C. For example, one system works in units, the other in packages. Or 1C and the WMS use different GUIDs for the same product. As a result, marking codes lose their link to the product. The system starts creating duplicates, makes errors when aggregating packages, and generates incorrect UPDs. Such errors very often appear after a 1C update, manual changes to reference data, or WMS modifications.
Mistake #3. WMS and 1C Exchange Data With a Delay
WMS and 1C often exchange data with a delay: information updates once an hour, gets transferred via XML files, or is loaded manually. For item-level tracking this isn't enough, because the system must update Data Matrix code statuses quickly and without discrepancies between Chestny Znak, the warehouse, and 1C. In other words, the same Data Matrix code can get sent for shipment twice. Such a problem is often noticed too late - only after Chestny Znak rejects the UPD or the customer receives goods with marking errors.
Mistake #4. The Warehouse Doesn't Control Code and Packaging Aggregation
When working with marking, the warehouse must know which Data Matrix codes each box, pallet or transport package contains. In practice, though, many WMS record only the pallet or box code without keeping the link to its contents after the package is broken down. The result - the warehouse can't correctly process a partial shipment, and 1C starts passing incorrect data into the UPD.
Mistake #5. Warehouse uses unsuitable data terminals and scanners
Even if the WMS and 1C exchange data without errors, problems still arise when the warehouse uses unsuitable handheld terminals and scanners for reading Data Matrix codes. As a result, staff rescan the goods, lose data, or manually fix errors in 1C, which increases the number of discrepancies and slows down warehouse operations.
According to CRPT technical requirements, working with Data Matrix requires handheld terminals with a 2D scanner - standard linear scanners physically cannot read a two-dimensional code. When choosing equipment, pay attention to recognition speed, support for damaged codes, and offline operation.
Discuss your challenge with an architect
What Fines Businesses Face for Marking Violations
Now Chestny Znak, cash registers and EDI systems will automatically send violation data to government systems. If WMS, 1C or EDI submit incorrect marking code data, the system will issue a ruling without an inspector and send it through Gosuslugi.
This means any errors in data exchange between EDI, WMS and 1C significantly affect company costs. A lost code, a duplicate in the UPD, or a discrepancy can cause document rejection, fines and shipment problems. Fines for marking errors:
| Violation | Fine | Legal Provision |
|---|---|---|
| Manufacturing or selling unmarked goods | 50 000-300 000 ₽ | Art. 15.12 of the Administrative Offenses Code of the CIS |
| Incorrect or Incomplete Data Transmission to GIS MT | Up to 100,000 RUB | Art. 15.12.1 of the Administrative Offenses Code of the CIS |
| Sale of goods after their expiration date | 20,000 RUB per unit | Art. 14.6 of the Administrative Offenses Code of the CIS |
| Sale of tobacco products not registered in the marking system | Up to 50,000 RUB | New Article 15.12.2 of the CIS Administrative Offenses Code, introduced by Federal Law No. 506-FZ of 28.12.2025 |
| Large-Scale Turnover of Unmarked Products | Up to 300,000 RUB, compulsory labor, or imprisonment | Art. 171.1 of the Criminal Code of the CIS |
How WMS and 1C Mistakes Lead to Fines
-
WMS may fail to pass the expiration date of a specific marking code to 1C. As a result, the checkout sells an item the system already considers expired.
-
If there are several such codes, the fine is charged for each unit separately.
-
Another common problem is mismatched reference data between the WMS and 1C.
-
If the system sends an incorrect GTIN to Chestny Znak or loses some codes while generating the UPD, GIS MT records the data transfer as incomplete.
-
Another risk arises with batch data exchange.
-
When WMS and 1C update data with a delay, the same code can be sent for shipment twice. Chestny Znak will detect the repeated retirement and reject the document.
Checklist: how to check warehouse readiness
- Answer the questions below — every "no" answer means a risk of shipments stopping after June 1.
- Does the WMS save the code of each item after receipt? If the system stores only GTIN and quantity, 1C cannot correctly generate a UPD for unit-level tracking.
- Does the WMS pass marking codes to 1C without losses or duplicates? Even one lost or duplicated code can cause GIS MT to reject the UPD.
- Do WMS and 1C use the same item and packaging reference data? If the systems define the item master differently, marking codes start diverging between WMS and 1C.
- Do WMS and 1C exchange data immediately after warehouse operations? With delayed exchange, the same code can be sent for shipment twice.
- Does WMS track the nesting of pallets, boxes and individual items? Without aggregation control, the warehouse can't correctly process partial shipments of marked products.
- Does the warehouse use data collection terminals and scanners that support Data Matrix codes? Marking requires 2D-scanning devices — linear scanners won't work.
- Do the data terminals check for damaged or incomplete codes before passing them to the WMS? This helps catch errors before the UPD is generated and data is sent to Chestny Znak.
- Does 1C generate the UPD automatically with the full list of marking codes? Manually adding codes increases the risk of errors and discrepancies.
- Does the EDI system correctly transmit marked UPDs to GIS MT? Format or transmission errors can halt product retirement.
- Did the warehouse run a test shipment with unit-level tracking? The test helps find problems in WMS, 1C, EDI and marking settings in advance.
- Do staff have a clear procedure for code discrepancies? Without a ready scenario, the warehouse will fix data manually and waste time hunting for errors.
Case: How a Logistics Holding Moved a Warehouse to a 1C-Based WMS and Cut Shipping Errors
Situation: the RosLogistic holding ran into trouble after online order volume grew - order line count nearly doubled, and shipping accuracy dropped to 91%. The warehouse operated without location-based storage: staff placed goods in any free zone, and pickers assembled orders from paper lists. Finding one item took up to 20 minutes, and inventory counts took three days.
The old accounting system added extra difficulty: any change had to be approved through an outside contractor, with updates taking several days. What was done: the partner team implemented WMS built on 1C, connecting warehouse zones one by one - from receiving to shipping. The warehouse introduced address-based storage, split zones by ABC classification, and set up picking routes.
High-turnover items were placed near the shipping zone, and small-piece orders began to be picked using the cluster method. To handle marking, experts connected data terminals with 2D scanners. During receipt, the system immediately checks Data Matrix codes against the UPD and flags errors before the item reaches the warehouse. Control scales were also installed in the shipping zone to detect mis-picks faster.
Before launch, staff tested the WMS and data terminals in a separate warehouse zone, then gradually switched to the new solution without stopping core operations. Results after a few months: - Picking accuracy rose from 91% to 99.8%. Returns due to mis-picks dropped to 0.3%, and the company cut logistics losses by about 4.7 million rubles a year. - Receiving a truck with 33 pallets now takes about 45 minutes instead of two hours.
The system checks marking codes right during receiving and shows errors before goods are put away. - Order picking now takes 9 minutes instead of the previous 35-40. In one pass, staff assemble several orders at once. - Inventory count takes about eight hours instead of three days, because the WMS shows bins with discrepancies and helps check stock faster. - Useful warehouse load grew 25%. Address-based storage helped remove empty and unused zones.

