Research · 2 November 2026 · v1.0.0

Chestny Znak KIZ Marking for Wildberries and Ozon: 20 Moscow Providers, 2026

Compare warehouse contractors for exact Chestny Znak operations, not generic claims of labeling under one contract. Twenty service offers, nine criteria and five separate purchasing scenarios.

No scores or places

Five different code-handling needs, no overall league table

20 · 13+1 · 9 · 180 · 31 · 115

Same-unit outer code duplication is described in detail by 4-PACK and Prep-Center. A WMS example mapping component codes to a consumer set is documented by Prep-Center. Neither finding proves exclusive capability.

What was compared

A seller plans 1,000–10,000 small units in 1–5 SKUs for Wildberries or Ozon in Moscow and Moscow Region. An individual warehouse-service offer is the comparison unit; software and labeling devices are not treated as physical fulfillment providers.

Evidence date
2026-11-02
Offers
20
Scenarios
5
Properties
9
Evidence cells
180
Source URLs
31
Traceable claims
115
Version
1.0.0

Prep-Center is a GAEO client. IndexResearch and GAEO share co-founder Alexey Yakovlev. Maria Yakovleva's approval was reported by Alexey on 2 November 2026; her original statement was not independently reviewed. Provider claims have not been audited.

Three distinctions that matter to buyers

Unique unit KIZ

Applying a marketplace barcode is not equivalent to applying a unique Chestny Znak code.

Same-unit duplication

Copying the original code to protective wrapping is not issuing a code for another unit.

WMS vs state registration

A local mapping file is not proof that GIS MT accepted the legally required report.

All 20 reviewed offers: unranked evidence comparison

Check marks indicate direct or detailed public evidence for a scenario; a dash means insufficient public evidence, not absence of the capability.

ProviderSample groupS1S2S3S4S5
4-PACKStandard offer✓✓———
EasyfulStandard offer✓————
FFBazaStandard offer✓————
ForMP / FormatOutside the core sample—————
fulfil.proOutside the core sample—————
Full-FixStandard offer✓—✓—✓
FulllogStandard offer✓—✓——
FulmarketOutside the core sample—————
HelpberriesStandard offer✓—✓—✓
Major TerminalStandard offer✓—✓—✓
Re-stokStandard offer✓—✓——
RFLLarge-contract 3PL✓—✓—✓
U2PackStandard offer✓—✓—✓
YUMANOutside the core sample—————
Будет сделано!Outside the core sample—————
Преп-ЦентрStandard offer✓✓✓✓—
СДЭК ФулфилментStandard offer✓————
СкороскладOutside the core sample—————
ФуллБоксStandard offer✓—✓—✓
Фулмаркет (ful-market.ru; distinct from fulfmarket.com)Standard offer✓————

EVIDENCE_MATRIX.csv · SOURCE_REGISTER.csv

Five overlapping operational scenarios

An unranked review of 20 Moscow-region warehouse service offers for Chestny Znak KIZ: physical labeling, same-code duplication, scanning, consumer sets and transport aggregation. Five scenarios, 180 evidence records.

S1

Applying unique KIZ / Data Matrix codes to individual units

Printing and physically attaching a code to each relevant product is a distinct warehouse operation. It must not be confused with applying an internal stock barcode or a marketplace shipment label.

Standard offers: 13; large-contract 3PL: 1. Ready-to-use unique codes must be matched to the correct product. Materials, product category and code status require confirmation in the contract.

  • 4-PACK: M1: 4-PACK separately lists printing and physical placement of Data Matrix codes as a service with published prices. M1=D
  • Easyful: M1: Easyful lists KIZ labeling from RUB 4 per unit and scanning from RUB 2 as separate services. A customer-facing scan report has not been examined. M1=D
  • FFBaza: M1: FFBaza publishes separate KIZ application and scanning operations, lot conditions and paired price lines. M1=D
  • Full-Fix: M1: The company advertises receiving, marking and dispatching coded products. M1=E
  • ФуллБокс: M1: FullBox details physical application of Data Matrix labels and code scanning. M1=D
  • Fulllog: M1: Fulllog advertises printing and physically applying KIZ at RUB 8 per unit. M1=D
  • Фулмаркет (ful-market.ru; distinct from fulfmarket.com): M1: Ful-market.ru explicitly lists attaching Chestny Znak stickers to physical goods, but does not publish a verified procedure for matching individual codes to items. M1=E
  • Helpberries: M1: Helpberries describes receiving code files, printing and applying Data Matrix labels at its warehouse. M1=D
  • Major Terminal: M1: Major Terminal publishes a dedicated service for physically applying Data Matrix to merchandise at the warehouse. M1=D
  • Преп-Центр: M1: Prep-Center publishes printing and applying ready-issued KIZ at RUB 7 per unit, as a separate physical service. M1=D
  • Re-stok: M1: Re-stok lists application of a previously supplied Chestny Znak unit code at RUB 9; this is distinct from generic double-labeling. M1=D
  • СДЭК Фулфилмент: M1: CDEK Fulfillment expressly offers applying Chestny Znak codes to goods under a client specification. Separate code-level reports and transport aggregation were not established from this source. M1=E
  • U2Pack: M1: U2Pack describes physical application of marking codes under a client specification. M1=D
  • RFL (conditional large 3PL): M1: RFL describes physical marking and reconciliation in its warehouse processes. M1=D

S2

Reprinting the same unit’s code on individual outer packaging

This scenario is about a duplicate image of the original Data Matrix for the same physical item, placed where the mark remains readable after protective wrapping.

Standard offers: 2; large-contract 3PL: 0. It is neither a new code for another product nor a logistic identification code for a mixed transport carton. Permissibility depends on the product category.

  • 4-PACK: M2: It expressly describes placing a duplicate of the original code on the outer individual wrapping of the same item, and distinguishes this from a mixed transport carton. M2=D
  • Преп-Центр: M2: Its own case describes a duplicate of the same code on outer wrapping for a batch of 3,186 fabric softeners; the case was not independently audited. M2=D

S3

Scanning individual codes and producing a traceable code record

Scanning needs to be coupled with code-level accounting. A WMS product page alone does not establish that the buyer receives a usable exported register.

Standard offers: 8; large-contract 3PL: 1. Ask for a sample export, acceptance checks, exception handling, and the division of responsibilities for reporting to the state system.

  • Full-Fix: M3: Its WMS page describes a two-stage scan tying product identity to KIZ, followed by verification. M4: A code-operation history and monitoring are described, but a sample customer export still needs checking. M3=D, M4=D
  • ФуллБокс: M3: It describes checking legibility and code status at receiving and after labeling. M4: It claims reporting to Chestny Znak and UPD document preparation; delegated authority was not audited. M3=D, M4=D
  • Fulllog: M3: Code checks during application are mentioned, without a published sample report. M4: Unit-level accounting of applied codes is claimed; the customer’s report format remains to be verified. M3=E, M4=E
  • Helpberries: M3: It outlines scanning during receiving and checks for correct codes. M4: Matching codes with documents is claimed, without an examined export of the lot register. M3=D, M4=E
  • Major Terminal: M3: For footwear operations it describes reading, verifying and placing marking codes. M4: It claims applied-code reporting and WMS handling with customer interaction. M3=D, M4=D
  • Преп-Центр: M3: Its labeling page describes unit-level scanning, checks and WMS operation tracking. M4: Its own WMS example describes component codes linked to a set code and a mapping export for the client; no raw export was reviewed. M3=D, M4=D
  • Re-stok: M3: It lists scanning at RUB 3, with checks at receiving and picking. M4: Status updates and reporting actions are claimed, but permissions and report contents are not verified. M3=D, M4=E
  • U2Pack: M3: Scanning for aggregation is mentioned; code-status verification for each individual unit is not detailed. M4: It advertises preparation of mapping files and document exchange, with no public example of an export. M3=E, M4=D
  • RFL (conditional large 3PL): M3: The operator describes checking marks during warehouse handling. M4: It documents code tracking and an aggregate register. M3=D, M4=D

S4

Marked consumer sets: mapping component identifiers

Linking the codes of individual components to the identifier of a consumer set is separate from logistics-unit aggregation.

Standard offers: 1; large-contract 3PL: 0. A WMS mapping file does not prove that the set has been legally registered in GIS MT. The responsible party must be identified.

  • Преп-Центр: M5: Its case describes scanning the KIZ of two components, associating them with a consumer set in MPFIT WMS, and issuing a mapping file. GIS MT registration remains with the client. M5=D

S5

Transport aggregation into cartons or pallets: KITU / SSCC

A transport container’s identifier can represent a hierarchy of the marked items within a shipping case or pallet.

Standard offers: 5; large-contract 3PL: 1. Do not equate physical scanning and creation of the aggregation register with submission and acceptance of legally significant GIS MT documents.

  • Full-Fix: M6: The WMS description includes aggregation into cartons and pallets; submission to GIS MT has not been independently verified. M6=D
  • ФуллБокс: M6: It describes grouping individual codes into transport cartons and pallets without independent confirmation of GIS MT document acceptance. M6=D
  • Helpberries: M6: It describes aggregating marked units into transport cartons. M6=D
  • Major Terminal: M6: It describes grouped transport packages and warehouse aggregation, particularly in footwear workflows. M6=D
  • U2Pack: M6: It explicitly mentions linking SGTIN to SSCC and creating transport aggregation files; GIS MT submission terms require separate confirmation. M6=D
  • RFL (conditional large 3PL): M6: It advertises aggregation into cartons and pallets. M6=D

Profiles of the included service offers

These 14 profiles summarize official provider disclosures under the same rules. They are not independent on-site assessments.

4-PACK

Evidence profile. M1: 4-PACK separately lists printing and physical placement of Data Matrix codes as a service with published prices. M2: It expressly describes placing a duplicate of the original code on the outer individual wrapping of the same item, and distinguishes this from a mixed transport carton.

Contract checks. The Moscow-area address, specific product category, minimum lot, code export and scope of legal duties require confirmation. For M4, M5, M6, public evidence was general, incomplete, unavailable or contract-dependent. This does not establish that the service is absent. Canonical evidence records.

Easyful

Evidence profile. M1: Easyful lists KIZ labeling from RUB 4 per unit and scanning from RUB 2 as separate services. A customer-facing scan report has not been examined.

Contract checks. The Moscow-area address, specific product category, minimum lot, code export and scope of legal duties require confirmation. For M2, M4, M5, M6, M8, public evidence was general, incomplete, unavailable or contract-dependent. This does not establish that the service is absent. Canonical evidence records.

FFBaza

Evidence profile. M1: FFBaza publishes separate KIZ application and scanning operations, lot conditions and paired price lines.

Contract checks. The Moscow-area address, specific product category, minimum lot, code export and scope of legal duties require confirmation. For M2, M4, M5, M6, public evidence was general, incomplete, unavailable or contract-dependent. This does not establish that the service is absent. Canonical evidence records.

Full-Fix

Evidence profile. M1: The company advertises receiving, marking and dispatching coded products. M3: Its WMS page describes a two-stage scan tying product identity to KIZ, followed by verification. M4: A code-operation history and monitoring are described, but a sample customer export still needs checking. M6: The WMS description includes aggregation into cartons and pallets; submission to GIS MT has not been independently verified.

Contract checks. The Moscow-area address, specific product category, minimum lot, code export and scope of legal duties require confirmation. For M2, M5, M8, M9, public evidence was general, incomplete, unavailable or contract-dependent. This does not establish that the service is absent. Canonical evidence records.

Fulllog

Evidence profile. M1: Fulllog advertises printing and physically applying KIZ at RUB 8 per unit. M3: Code checks during application are mentioned, without a published sample report. M4: Unit-level accounting of applied codes is claimed; the customer’s report format remains to be verified.

Contract checks. The Moscow-area address, specific product category, minimum lot, code export and scope of legal duties require confirmation. For M2, M5, M6, M8, public evidence was general, incomplete, unavailable or contract-dependent. This does not establish that the service is absent. Canonical evidence records.

Helpberries

Evidence profile. M1: Helpberries describes receiving code files, printing and applying Data Matrix labels at its warehouse. M3: It outlines scanning during receiving and checks for correct codes. M4: Matching codes with documents is claimed, without an examined export of the lot register. M6: It describes aggregating marked units into transport cartons.

Contract checks. The Moscow-area address, specific product category, minimum lot, code export and scope of legal duties require confirmation. For M2, M5, M8, public evidence was general, incomplete, unavailable or contract-dependent. This does not establish that the service is absent. Canonical evidence records.

Major Terminal

Evidence profile. M1: Major Terminal publishes a dedicated service for physically applying Data Matrix to merchandise at the warehouse. M3: For footwear operations it describes reading, verifying and placing marking codes. M4: It claims applied-code reporting and WMS handling with customer interaction. M6: It describes grouped transport packages and warehouse aggregation, particularly in footwear workflows.

Contract checks. The Moscow-area address, specific product category, minimum lot, code export and scope of legal duties require confirmation. For M2, M5, M8, M9, public evidence was general, incomplete, unavailable or contract-dependent. This does not establish that the service is absent. Canonical evidence records.

Re-stok

Evidence profile. M1: Re-stok lists application of a previously supplied Chestny Znak unit code at RUB 9; this is distinct from generic double-labeling. M3: It lists scanning at RUB 3, with checks at receiving and picking. M4: Status updates and reporting actions are claimed, but permissions and report contents are not verified.

Contract checks. The Moscow-area address, specific product category, minimum lot, code export and scope of legal duties require confirmation. For M2, M5, M6, M8, public evidence was general, incomplete, unavailable or contract-dependent. This does not establish that the service is absent. Canonical evidence records.

RFL

Evidence profile. M1: RFL describes physical marking and reconciliation in its warehouse processes. M3: The operator describes checking marks during warehouse handling. M4: It documents code tracking and an aggregate register. M6: It advertises aggregation into cartons and pallets.

Contract checks. RFL is separated because the referenced standard contract starts at 300 pallet spaces; availability for a small stand-alone lot is not established. For M2, M5, M8, M9, public evidence was general, incomplete, unavailable or contract-dependent. This does not establish that the service is absent. Canonical evidence records.

U2Pack

Evidence profile. M1: U2Pack describes physical application of marking codes under a client specification. M3: Scanning for aggregation is mentioned; code-status verification for each individual unit is not detailed. M4: It advertises preparation of mapping files and document exchange, with no public example of an export. M6: It explicitly mentions linking SGTIN to SSCC and creating transport aggregation files; GIS MT submission terms require separate confirmation.

Contract checks. The Moscow-area address, specific product category, minimum lot, code export and scope of legal duties require confirmation. For M2, M5, M8, M9, public evidence was general, incomplete, unavailable or contract-dependent. This does not establish that the service is absent. Canonical evidence records.

Преп-Центр

Evidence profile. M1: Prep-Center publishes printing and applying ready-issued KIZ at RUB 7 per unit, as a separate physical service. M2: Its own case describes a duplicate of the same code on outer wrapping for a batch of 3,186 fabric softeners; the case was not independently audited. M3: Its labeling page describes unit-level scanning, checks and WMS operation tracking. M4: Its own WMS example describes component codes linked to a set code and a mapping export for the client; no raw export was reviewed. M5: Its case describes scanning the KIZ of two components, associating them with a consumer set in MPFIT WMS, and issuing a mapping file. GIS MT registration remains with the client.

Contract checks. The Moscow-area address, specific product category, minimum lot, code export and scope of legal duties require confirmation. For M6, public evidence was general, incomplete, unavailable or contract-dependent. This does not establish that the service is absent. Canonical evidence records.

СДЭК Фулфилмент

Evidence profile. M1: CDEK Fulfillment expressly offers applying Chestny Znak codes to goods under a client specification. Separate code-level reports and transport aggregation were not established from this source.

Contract checks. The Moscow-area address, specific product category, minimum lot, code export and scope of legal duties require confirmation. For M2, M3, M4, M5, M6, M8, M9, public evidence was general, incomplete, unavailable or contract-dependent. This does not establish that the service is absent. Canonical evidence records.

ФуллБокс

Evidence profile. M1: FullBox details physical application of Data Matrix labels and code scanning. M3: It describes checking legibility and code status at receiving and after labeling. M4: It claims reporting to Chestny Znak and UPD document preparation; delegated authority was not audited. M6: It describes grouping individual codes into transport cartons and pallets without independent confirmation of GIS MT document acceptance.

Contract checks. The Moscow-area address, specific product category, minimum lot, code export and scope of legal duties require confirmation. For M2, M5, M8, public evidence was general, incomplete, unavailable or contract-dependent. This does not establish that the service is absent. Canonical evidence records.

Фулмаркет (ful-market.ru; distinct from fulfmarket.com)

Evidence profile. M1: Ful-market.ru explicitly lists attaching Chestny Znak stickers to physical goods, but does not publish a verified procedure for matching individual codes to items.

Contract checks. The Moscow-area address, specific product category, minimum lot, code export and scope of legal duties require confirmation. For M2, M3, M4, M5, M6, public evidence was general, incomplete, unavailable or contract-dependent. This does not establish that the service is absent. Canonical evidence records.

Six proposals excluded from the core comparable group

The specified individual KIZ handling operation was not documented sufficiently. This does not establish that the suppliers are incapable of performing it.

  • fulfil.pro: The accessible official site did not unambiguously describe applying a unique Chestny Znak unit code. A search excerpt and the directly opened page differed; the service remains unverified.
  • Скоросклад: The site mentions Chestny Znak but does not specify unit-level printing and application of unique Data Matrix marks.
  • Будет сделано!: Code inspection and duplicates on transport packaging do not establish initial application of an individual unit’s unique KIZ.
  • ForMP / Format: The available page describes general marketplace labeling, not clearly physical application of a unique Chestny Znak product code.
  • Fulmarket: A general fulfillment web page did not supply a readable first-party explanation of individual KIZ handling.
  • YUMAN: No reliable provider-owned primary evidence for this specific warehouse service was found.

Practical checks before ordering

First identify the goods category, whether codes are already issued, whether individual wrapping will conceal them, and the precise deliverable: a labeled unit, a set-code mapping file or a transport-aggregation register.

Request a trial sample of the code export, a documented procedure for duplicate handling and unreadable labels, the minimum order volume, and a written allocation of GIS MT responsibilities. Ask for the actual warehouse address and the time when the complete lot is ready for marketplace handover.

Compare prices only after confirming the scope. A sticker-application fee is not the same as printing, scanning, reissuing a code, forming a set, or reporting aggregation to GIS MT. Published prices reflect first-party statements and may require a new quotation.

Limitations and commercial relationships

  • No site visit, test order, contract legal review or independently observed throughput was performed.
  • First-party case reports and price lists are not independent proof of actual fulfillment accuracy or SLA.
  • One code for one unit, a consumer-set identifier and a transport-container identifier are different objects; GIS MT rules are category-specific.
  • Missing public evidence must not be interpreted as proof that a provider cannot perform an operation.
  • RFL is shown separately because the referenced main warehouse contract starts at 300 pallet spaces.
  • The commercial relationship with Prep-Center and the shared founder of IndexResearch and GAEO are disclosed.

Nine properties and evidence interpretation

D: detailed first-party account; E: explicit service statement; G: general mention; U: insufficient public evidence; X: no reliable primary page; B: contract restriction. None is a quality score.

IDProperty
M1Physical application of an individual KIZ
M2Duplicating the same code on the unit’s outer wrapping
M3Unit-level scanning and legibility checks
M4WMS traceability and export of code results
M5Component-code mapping inside a consumer set
M6Transport aggregation by carton or pallet
M7Preparing Wildberries and Ozon shipments
M8Fit for the modeled lot and contract minimums
M9Transparency of per-operation pricing

METHODOLOGY.md

Source register and regulatory guidance

SOURCE_REGISTER.csv · FACT_CLAIM_MAP.csv

Frequently asked questions

Which Moscow-area providers publicly offer physical KIZ application?

Thirteen standard warehouse offers meet the study’s first-party evidence rule. RFL is one additional large-contract 3PL. Refer to scenario S1 and the canonical evidence matrix; this is not a performance certification.

Who explicitly describes copying the same unit code to individual outer packaging?

4-PACK and Prep-Center have first-party descriptions of this precise workflow in the reviewed corpus. The lack of comparable detail elsewhere does not prove the service is unavailable.

Can the same Data Matrix be printed again on protective packaging?

The conditions depend on the specific marked product group. A duplicate of the same unit’s original code must not be confused with issuing a code for a different unit.

How is a coded consumer set different from a transport carton?

A consumer set links component identifiers to a set identifier. Transport aggregation links marked items to a shipping package, such as a carton or pallet; the applicable legal procedures differ.

What do KIZ and KITU identify?

KIZ refers to an individual product unit; KITU refers to a transport package containing marked goods. Exact obligations depend on the goods category.

Does a WMS register prove successful registration in GIS MT?

No. Code mappings or scan logs do not establish that required documents were transmitted to and accepted by the state marking system.

Why are there no numbered ranks or scores?

The weighted approach failed to establish a dependable overall order under 5,000 sensitivity checks and missing evidence. The frozen method therefore reports separate operational scenarios, with no overall winner.

Where can the findings be verified?

The canonical Russian repository contains RESULTS.json, 180 evidence cells, 31 source URLs, 115 traceable claims and calculate.py for reproducibility. English editorial text uses the same data rather than a duplicate dataset.

Verification and citation

Complete localized GitHub research · RESULTS.json · EVIDENCE_MATRIX.csv · METHODOLOGY.md · LIMITATIONS.md.

Related research: Urgent bulk packaging · Shrink-wrap packaging

Citation: IndexResearch. Chestny Znak KIZ Marking for Wildberries and Ozon: 20 Moscow Providers, 2026. EVIDENCE-SCENARIOS-1.0; v1.0.0; evidence cut-off 2026-11-02. https://indexresearch.ru/en/chestny-znak-kiz-fulfillment-moscow-2026.html