Last updated: 2026-11-15 · By the ZhiShuYun Research Team
EDI is the electronic document channel used to report product movement into Chestny ZNAK, and SPOT (СПОТ) is the shipment confirmation step that releases imported goods for sale. Both operate in the CRPT ecosystem: the importer typically holds the account, while the manufacturer supplies product data, codes and documents. Without SPOT confirmation, compliant goods can still be blocked from sale.
| EDI | Electronic data interchange for movement documents (receipts, transfers, withdrawals) in the marking system |
| SPOT | Shipment confirmation (СПОТ) required for imported goods before release for sale |
| Account holder | Usually the Russian importer or the manufacturer's Russian entity |
| Data needed | GTIN, code ranges, invoice and customs references, product descriptions |
| Timing | Confirmation must happen before goods are offered for sale; late steps stall the warehouse |
Every movement of marked goods — import receipt, transfer between warehouses, write-off, return — is reported as a document. EDI is how those documents flow automatically between the participant's systems and CRPT, instead of being typed into a web form.
For a foreign manufacturer the practical implication is data quality: GTIN, code ranges, quantities and invoice references must line up exactly with what the importer declares, or documents get rejected and goods stall.
SPOT is the confirmation step for imports. Before goods can be sold, the shipment must be confirmed in the system, tying the physical consignment to the registered codes. It closes the gap between customs clearance and legal sale.
Because SPOT sits at the end of the chain, errors upstream surface here. Missing code ranges, mismatched quantities and unregistered GTINs all appear as a failed confirmation rather than as an obvious data error.
The importer is the legal participant and holds the CRPT account. The manufacturer supplies the GTIN, prints or provides codes, and hands over consistent shipment data. Good practice is to exchange the code range list and invoice data before the vessel departs — fixing discrepancies after arrival is where most delays come from.
Electronic document exchange is how the marking system expects movements to be reported at scale. Manual web entry exists but does not scale and is discouraged for importers.
Usually the Russian importer or a Russian legal entity does. The manufacturer participates by supplying data and codes.
The goods cannot be legally sold. They may also be subject to penalties and forced re-labelling or return.
Before shipment. Reconciling code ranges and quantities after arrival is the single most common cause of delays.
It needs an EDI connection to CRPT, typically through a certified provider or an integrated platform. The choice depends on your importer's systems.
Fix the data upstream
SPOT confirmation fails at the end of the chain when the data was wrong at the start. Reconciling GTIN, quantities and code ranges before shipment prevents most of the delays that later look like customs or system problems.