I don’t understand who retires the codes when selling on Ozon: the marketplace or me
Truemark
On FBO, Ozon retires them, and on FBS and realFBS assume you have to retire them. The service checks statuses in Chestny ZNAK, not the account export.
Ozon · models FBS and realFBS · Chestny ZNAK
Selling marked goods on Ozon from your own warehouse? Then marking codes are your responsibility: enter the code when picking a posting, and at shipment withdraw it from circulation in Chestny ZNAK and return it to circulation on refusal or return. We go step by step through who actually retires codes on FBO, FBS and realFBS, which errors block order picking and how Truemark removes this routine: the Ozon integration already works.
Posting 0157-1123-1
How it works
One token to connect, two scans per order, one signing for hundreds of withdrawal documents, instead of hunting for postings by hand and exporting to Excel. The video shows the Wildberries integration. The Ozon integration already works in the same interface and with the same logic; the only differences are the marketplace’s terms.
The recording was made on the Wildberries integration: on Ozon only the marketplace’s terms differ, postings instead of assembly tasks.
The seller’s main question
It’s the first thing sellers ask, and it’s exactly where money is most often lost. We’ve laid it out honestly: what the marketplace rules say, what sellers see in practice and how to act so you don’t build a backlog of unwithdrawn codes.
The Knowledge Base has a caveat: if the marking code was passed at picking, “you don’t need to withdraw it from circulation yourself; we’ll withdraw the code via the receipt”, and on a return Ozon will put the code back with a return receipt. Separately mentioned are over-the-counter medicines: for them, the marketplace directly promises to withdraw codes on its side.
For regular product groups (clothing, footwear, perfume, dietary supplements), sellers get no retirement confirmation: Ozon doesn’t show them receipts with the marking code, and the codes remain registered in circulation. So sellers withdraw them themselves, by hand, from an order export from the account.
Responsibility for the data in Chestny ZNAK stays with the seller in any case: under FBS and realFBS, you are the owner of the goods at the moment of sale. Ozon itself warns that the presence of a code in the “Sales of marked goods” report doesn’t guarantee its withdrawal from circulation. Violating data reporting deadlines means up to ₽100,000 under Art. 15.12.1 of the Russian Code of Administrative Offenses.
Don’t guess: check the actual status of every code in Chestny ZNAK before filing a document, and withdraw from circulation what remains in circulation after shipment, no later than 3 business days, without waiting for delivery. If the code is already withdrawn, no repeat document is needed. Then there’s neither a delay nor double retirement. This exact check is in Truemark, for both Wildberries and Ozon: a withdrawal draft is assembled only for a code that Chestny ZNAK registers as in circulation and yours.
More than 2,500 companies mark their goods in Truemark, including

FBO · FBS · realFBS
The seller’s most frequent question: “Doesn’t Ozon retire the codes itself?” Sometimes yes, sometimes no, and the price of a mistake is fines and codes stuck in circulation. We’ve laid it out by working model, as it actually works.
Who it fits
Clothing and footwear, perfume, dietary supplements and sports nutrition, antiseptics and household chemicals, water and beverages, feed, medical devices, bicycles: if the goods are subject to marking in Chestny ZNAK, then when selling on Ozon under FBS and realFBS, the work with codes falls on the seller.
You make and mark the goods yourself and sell them on Ozon. The full cycle in one service: code orders, label printing, introduction into circulation, and on the marketplace, correct codes in postings and timely withdrawal from circulation.
You import ready marked goods and sell them on Ozon. Codes are applied before customs, and when selling under FBS you have to close circulation: either pass the code to the marketplace or file the withdrawal from circulation yourself at shipment.
You buy marked goods and resell them through Ozon. The code must be yours and in circulation: Ozon won’t accept a foreign or already retired code, and the posting picking will stall.
You sell on marketplaces and don’t want to deal with APIs, crypto tails and Chestny ZNAK regulations. You need one button in the browser, codes retired on time and no backlogs.
Sound familiar?
We’ve collected what marketplace sellers come to us with. All of it is closed in Truemark, with work in Chestny ZNAK and the integration with the Ozon account.
I don’t understand who retires the codes when selling on Ozon: the marketplace or me
Truemark
On FBO, Ozon retires them, and on FBS and realFBS assume you have to retire them. The service checks statuses in Chestny ZNAK, not the account export.
Ozon won’t accept the code at picking: “no ASCII 29 separator”, and the deadline is burning
Truemark
It’s almost always about the crypto tail or lost GS characters. Scanning with a 2D scanner in the service rules out such fixes; the breakdown is in the table below.
I’m afraid of sending someone else’s or a retired code, the goods got mixed up in the warehouse
Truemark
The status of each code is right in the posting list, and only your code in circulation goes into the withdrawal draft
I retire codes by hand from an account export: on a hundred orders that’s half a day
Truemark
Withdrawal documents are assembled with the posting number, date and price. You just sign them all at once.
Product returned, and I find out late and by hand
Truemark
Returns are tracked separately, and the code returns to circulation with the basis: the return request number
I don’t want write an Ozon Seller API integration just for marking
Truemark
You connect the account with an Ozon Seller API key, and marking runs on autopilot. No servers, no developers.
The integration works
The Ozon FBS integration is live and works the same way as the Wildberries integration: the same logic and the same interface. You connect the account with an Ozon Seller API key, and postings and codes appear in Truemark.
The integration works on the Opti and Maxi plans, and you can try it for free on the demo plan. If something goes wrong or something is missing, write to support.
The service fetches FBS postings and the codes already entered at picking from the Ozon account every 15 minutes, with no “Refresh” button. It determines which goods need a code not only by the Ozon flag but also by the National Catalog.
You open a posting, turn on the scanner and scan the codes from the goods. The code goes to Ozon whole, with the crypto tail and GS separators, with no manual copying or lost characters.
The service checks codes against Chestny ZNAK and shows the status right in the posting list: “In circulation”, “Withdrawn”, “No code” or “Foreign code” if the code is registered to another participant
As soon as Ozon accepts a posting (by the shipment act, or if there’s no act, by the date of handover to delivery), the service assembles a withdrawal draft (remote sale) with the shipment date, price and place of business. You sign it, one at a time or in a batch, with an electronic signature.
When Ozon marks a return as received, the return-to-circulation document is prepared in a couple of clicks: choose the return and enter the code. For toys and fur, where a withdrawal cancellation is needed instead of a return, the service prepares the cancellation.
Ozon labels print right from the service, in batches of up to 20 postings. Picked postings are added to a shipment and confirmed in Ozon right from the service, without switching between accounts.
Guide
The procedure in the Ozon account, step by step, as it is today. You can enter the code at any time before the posting is handed over to Ozon logistics: while it’s in the “Awaiting packaging” and “Ready to ship” statuses.
Section FBS → Orders from my warehouses, the tab “Awaiting packaging”. Ozon determines which postings need a code by the HS code in the product card.
The button is in the posting line or inside the order card. Check the order contents and click “Next”: the system will offer to enter additional information.
You need the full code: the identification code (GTIN and serial number) plus the crypto tail: the key and the verification code, including GS characters. For a set or multipack: if there’s a group code, enter it; if not, the codes of each item.
Ozon checks the code automatically right after entry. If the code is invalid or has an error, the order can’t be picked: you’ll have to deal with the reason first.
Click “Confirm”, then “Pick”: the posting moves to the “Awaiting shipment” tab. After handover to logistics, the code can no longer be added.
The code can be entered and scanned with the camera in the app Ozon Seller, or passed via Ozon Seller API: this is the path Truemark automates: scanning the code in the warehouse and passing it to the posting with no manual copying, with the code status in Chestny ZNAK visible in the posting list
The posting won’t pick
Ozon checks the code right after entry, and with any of these errors the order can’t be picked. We go through each one: what it actually means and how to avoid hitting it again.
!"%&'()*+,-./_:;=<>? are allowed. Check the keyboard layout and autocorrect in the editor\u001d; when passing via the API, serialize per RFC 8259 without double escapingChestny ZNAK
Under FBS and realFBS, withdrawal from circulation is the seller’s task: it’s filed with a “Withdrawal from circulation” document with the reason “Remote sale”. Ozon’s help recommends doing it after the “Delivered” status, but the marking rules count the deadline from shipment: data is filed no later than 3 business days after shipment and no later than the delivery date. Follow the rules. Below are the exact details the marketplace requires.
We reply within 1 business hour · we’ll suggest what to do with the codes already piled up
Working with fulfillment?
No need to move to a new warehouse or break an established process. If orders are picked and shipped by a fulfillment operator or in your accounting system, leave it that way. The service connects as a separate layer and handles only marking.
The service gets current order and posting states directly from the account, regardless of who physically picked the order. You see the real picture for every posting.
The operator keeps picking, labeling and shipping in their own mode. They don’t need to sign in to Truemark or change their usual processes.
As soon as a posting is handed over for delivery, the service assembles a withdrawal draft with the posting number, date and price. A refusal or return gives a return-to-circulation draft.
You sign in, select the drafts and sign with an electronic signature. Then the service sends everything to Chestny ZNAK and waits for the processing result.
For large sellers
The service is built for large volumes: everything done for one order can be done in a batch. The operator doesn’t open each card but works with the list.
You select the postings in a list and move them further along the cycle in one action. No need to open each order separately.
You print labels for the whole batch at once, not one by one. A ready print package, and you can start labeling.
You scan the posting label, then the marking code from the goods, and then the next one. The service guides you step by step and shows the result for each pair: what was accepted, what wasn’t and why.
You select all the document drafts and sign them at once. Then the documents travel through the account, from creation to confirmation from Chestny ZNAK.
Sales to legal entities
Most sales on Ozon go to regular buyers, and orders from companies are rare in the general flow. But if such an order comes, the rules are different: for orders within Russia from legal entities, the marking code must be entered for all goods subject to registration in Chestny ZNAK. There’s no choice of “pass it or not” here.
After the order is delivered, Ozon creates a UTD on the seller’s behalf and sends it to the buyer via EDI. After signing, the marking codes pass to the buyer’s balance: this isn’t a disposal but a transfer of ownership.
No “Withdrawal from circulation” is filed for such an order: the goods don’t leave the system, they change owner. A code retired by mistake would have to be returned to circulation for the UTD to go through correctly.
A code error costs more here: the order won’t pick, and if it goes through with a foreign code, the discrepancy surfaces on the buyer’s side, at UTD receipt
That the code is in circulation and belongs to you, that it’s linked to the very item that went to the buyer, and that the order doesn’t have a duplicate document. These are exactly the checks Truemark does automatically.
Truemark in numbers
Official Chestny ZNAK integrator since 2019; the service is 7 years old. Convenience comes first for us: the account has only what you need to work, with no extra steps or cluttered interface.
Why Truemark
The service’s strengths on one screen, with no fine print or asterisks.
Wildberries and Ozon FBS in one interface: entering the code, labels, withdrawal from circulation at shipment and returns
Picking and shipping can stay with fulfillment or in your own system. Truemark pulls current statuses from the account and covers only the Chestny ZNAK side.
Clothing, footwear, dietary supplements, perfume, water, feed and other categories, with no extra charge for connecting new groups
Sign in with an electronic signature and work right in the browser. No IT specialists or integrators needed.
Marking experts answer on any plan, with no separate subscription
A transparent plan: all functionality is included. Marking codes are paid directly to Chestny ZNAK: ₽0.61 per code.
Pricing
The cost of working with Chestny ZNAK is the same for all product groups. Marketplace integrations are included in plans starting with Opti: both Wildberries and Ozon FBS. You can try both for free on the demo plan: Ozon with no limit on postings, Wildberries up to 50 signed withdrawal documents. Marking codes are paid separately, directly to Chestny ZNAK: ₽0.61 per code including VAT.
A marking code costs ₽0.61 in Chestny ZNAK. Ordering, printing, aggregation, UTDs, marketplaces and 1C in Truemark cost from ₽0.017 per code on the Maxi plan paid annually. All product groups and support are included.
Truemark per code is the plan price divided by its code limit for the period. Codes are paid to Chestny ZNAK separately; Truemark does not resell codes.
For small companies
₽0.085per code
₽1,409 per month · ₽16,900 per year
Included
Handheld terminal license: ₽10,000 per device
Choose MiniFor growing businesses
₽0.056per code
₽2,325 per month · ₽27,900 per year
Everything in Mini, plus
Handheld terminal license free, the next one ₽5,000
Choose Opti₽0.017per code
₽4,159 per month · ₽49,900 per year
Everything in Opti, plus
Handheld terminal license free, the next one ₽5,000
Choose Maxi| What's included | Mini | Opti | Maxi |
|---|---|---|---|
| Every product group | included | included | included |
| Ordering codes, label printing, application and introduction into circulation | included | included | included |
| UTD shipping | included | included | included |
| Automatic aggregation without a scanner | included | included | included |
| UTD receipt via EDO Lite | with a terminal license | included | included |
| 1C integration | not included | included | included |
| Re-marking | not included | included | included |
| Wildberries, FBS | not included | up to 3,000 tasks a month | up to 30,000 |
| Ozon, FBS | not included | up to 3,000 shipments, 2 stores | up to 30,000, 5 stores |
| Stock marking | not included | not included | included |
| Handheld terminal app license | ₽10,000 | 1 free | 1 free |
| Employees with an MChD and their own signature | included | included | included |
| Invited employees, no signature needed | not included | up to 3 | up to 10 |
| Employee roles: “View” and “Change” by section | not included | not included | included |
Re-marking, stock marking and EDI can be bought separately from a plan. Training in Truemark costs ₽5,000 per hour, although the guides and interactive tours in the account are usually enough.
Marketplace workload
Marketplace integrations are priced by the number of assembly tasks (on Ozon, postings) processed in a month. The plan is issued for a company (INN).
The cost of a mistake
Responsibility for marking lies with the seller: it’s set out both in the law and in the marketplace’s offer.
For legal entities, from ₽50,000 to ₽300,000 with confiscation of the goods. For officials, from ₽5,000 to ₽10,000.
This includes late withdrawal of codes from circulation after a remote sale and unreported return data
Ozon has set out in its offer: if the marketplace is fined for missing marking or a missing HS code in the card, the costs are deducted from the seller
Criminal liability. Circulation of unmarked products on a large scale carries liability under Art. 171.1 of the Russian Criminal Code, up to imprisonment. You can check for free whether your goods are subject to mandatory marking in the marking requirement check service.
Two marketplaces
Marking rules on the marketplaces are similar but not identical: somewhere the code is always mandatory, somewhere the seller has a choice, while Chestny ZNAK deadlines and documents are the same. A short map of the differences is on the page marking for marketplaces; we bring the accounts into one service so you don’t have to keep two guides in mind.
Entering marking codes in two scans, label printing, withdrawal from circulation at shipment, returns and 30 days of history. Details on the page marking on Wildberries.
Postings and codes from the Ozon account, entering codes with a scanner, labels, shipments, withdrawal from circulation at shipment, returns and 30 days of history. The same logic and the same interface as for Wildberries.
Chestny ZNAK codes, documents and statuses in one place, regardless of which marketplace the sale happened on. No separate subscriptions per marketplace.
The plan is issued for an INN: it includes your legal entity’s Wildberries and Ozon accounts. Opti covers up to 3,000 assembly tasks a month and up to 2 Ozon stores, Maxi up to 30,000 and up to 5 Ozon stores, more on request.
FAQ
Didn’t find an answer? An expert replies in the account chat in 15 minutes on average. More answers in the knowledge base and blog.
Yes. If a product belongs to a product group subject to mandatory Chestny ZNAK marking (clothing, footwear, perfume, dietary supplements, water, feed and others), it has to be marked regardless of the sales channel, including on Ozon. The marketplace determines whether marking is needed by the HS code in the card, so it’s important to enter it correctly. You can check a specific product in the free marking requirement check service.
On FBO, the codes pass to Ozon under UPD-2 after receiving, and the marketplace itself enters the code on the receipt and withdraws it from circulation at sale. On FBS and realFBS, assume that you have to retire the codes: the seller is the owner of the goods at the moment of sale, and the document is a “Withdrawal from circulation” with the reason “Remote sale”. Ozon’s rules have a caveat that if the code was passed on, it will withdraw it via the receipt, but for regular product groups sellers don’t see such confirmation, and the codes stay in circulation. There’s only one reliable way: check the actual code status in Chestny ZNAK.
Don’t count on it. Ozon’s Knowledge Base has a caveat that if the code was passed on, the marketplace will withdraw it from circulation via the receipt, and for over-the-counter medicines it directly promises to do this on its side. But for regular product groups, sellers get neither a receipt with the code nor a retirement confirmation: the codes remain registered in circulation, and sellers withdraw them themselves. Under FBS, responsibility for the data in Chestny ZNAK is on the seller in any case, so the only reliable path is to check the actual status of each code in Chestny ZNAK and retire what remains in circulation.
For orders within Russia, the code is mandatory: from legal entities, for all goods subject to registration in Chestny ZNAK; from individuals, for over-the-counter medicines. For other marked goods sold to individuals, Ozon allows entering the code but doesn’t require it yet. Important: passing the code to the marketplace by itself doesn’t relieve you of the obligation to make sure the code is actually withdrawn from circulation: you need to check this in Chestny ZNAK.
In the account: FBS → Orders from my warehouses → “Awaiting packaging” tab → click “Enter additional info” for the posting, check the order data, enter the whole marking code (GTIN and serial number plus the crypto tail with GS characters), then “Confirm” and “Pick”. The code can also be entered or scanned with the camera in the Ozon Seller app, or passed via the Ozon Seller API.
You can enter the code at any time before the posting is handed over to Ozon logistics, while it’s in the “Awaiting packaging” and “Ready to ship” statuses. After handover to logistics, the code can no longer be added.
Ozon checks the code automatically right after entry, and with an error the order can’t be picked. Common causes: the code was entered without the crypto tail, it has a space or Cyrillic characters, by GTIN it belongs to another product group, the same code is already entered for another product in this order, or it lacks the ASCII 29 separator (the GS character). Each error explained: in the table above.
It means the code has no GS group separator (ASCII 29), or it was entered incorrectly. Separators split the parts of the code: the identification code from the crypto tail. In files, GS characters are written as the escape sequence \u001d, and when passing via the API they are serialized per RFC 8259, without double escaping. The most reliable way is not to edit the code by hand but to scan it with a 2D scanner.
The crypto tail is the cryptographic part of the marking code: the verification key and the verification code. Ozon requires the whole code: the identification code (GTIN and serial number) together with the crypto tail. If you copy only the identification code, the marketplace returns the error “The code has the wrong number of characters”.
No later than 3 business days after the day the goods are shipped from the warehouse and no later than the date of delivery to the buyer: that’s the deadline set by the marking rules for remote sales, for example clause 76 of the marking rules for light industry goods (Government Decree No. 1956). Ozon’s help recommends withdrawing the code after the “Delivered” status, but under the rules the countdown starts from shipment. A delay means the risk of a fine under Art. 15.12.1 of the Russian Code of Administrative Offenses.
A “Withdrawal from circulation” document with the reason “Remote sale” states: primary document type: other; primary document number: the order (posting) number; primary document date: the order (posting) date; address of the place of disposal: leave empty; unit price: the final price of the goods on the receipt, that is, the final price from the account.
The rule is simple: whoever withdrew the code returns it. If you retired the code yourself, you file a “Return in remote sale” document; the basis is the buyer’s return request number. Ozon’s return receipt works only where the marketplace actually withdrew the code from circulation (for example, for over-the-counter medicines). You can check what exactly happened to the code in Chestny ZNAK.
On FBO, the goods are at the Ozon warehouse: the codes pass to the marketplace under UPD-2 after receiving, and Ozon itself enters the code on the receipt and withdraws it from circulation at sale. On FBS, the goods are at your warehouse: the marking code is entered when picking the posting, and withdrawal from circulation at shipment is the seller’s task. Responsibility for correct code statuses stays with the seller in both cases.
No, the rules for passing codes and withdrawing from circulation on realFBS Standard, Express and Comfort are the same as on FBS. A separate exception is over-the-counter medicines under the “realFBS for reservations” model: passing and withdrawing the code isn’t required there.
No. Ozon warns directly: the presence of a marking code in the report is not a guarantee of its withdrawal from circulation. The report (Analytics → Reports → Orders → Sales of marked goods) shows only which codes were entered in orders at shipment. The actual status of each code needs to be checked in Chestny ZNAK.
Ozon determines whether marking is needed by the HS code. Without it, the system won’t recognize the product as marked, won’t ask for the code at picking, and data on the movement of the goods won’t reach Chestny ZNAK, which violates the marking rules. If Ozon is fined because of this, it deducts the costs from the seller’s profit: the rule is set out in the agreement.
For circulation of goods without marking: Art. 15.12 of the Russian Code of Administrative Offenses, from ₽50,000 to ₽300,000 for legal entities, with confiscation. For violating the procedure and deadlines for reporting data to the system, including late withdrawal from circulation: Art. 15.12.1, up to ₽100,000. For circulation on a large scale: criminal liability under Art. 171.1 of the Russian Criminal Code.
Yes. The Ozon FBS integration launched in September 2026 and works: postings and codes come in from the account, codes are entered with a scanner, labels print from the service, and withdrawal documents are prepared on their own; you just sign them. The integration is included in the Opti and Maxi plans, and you can try it for free on the demo plan.
In the Ozon seller account, open Settings → Seller API and create a key for an external service with the Posting FBS, Warehouse, Product read-only and Returns read-only roles, or with the Admin role. Then in Truemark open the “Ozon” section and paste the Client-Id and API Key: the service checks the key and the seller’s INN and loads postings for the last 30 days. Ozon issues the key for 3 months; after that it has to be replaced in the section settings. Step by step with pictures in the article how to connect Ozon to Truemark.
Opti covers up to 3,000 assembly tasks (on Ozon, postings) a month, Maxi up to 30,000 a month. Ozon stores: up to 2 in Opti, up to 5 in Maxi. The free demo plan has no limit on Ozon postings. The plan is issued for a company (INN): the limit applies within the legal entity. For larger volumes, we’ll calculate terms individually on request.
Yes. Picking and shipping can stay with the fulfillment operator or in your accounting system: no need to change the process. Truemark gets current order statuses directly from the marketplace account and covers only the Chestny ZNAK side: it tracks shipments and returns and prepares withdrawal and return-to-circulation documents. You just sign them with an electronic signature.
Yes. The integrations with Wildberries and Ozon under FBS work in one Truemark account: Chestny ZNAK codes, documents and statuses are brought together in one place, and the plan is one, issued for the company (INN).
The Ozon integration already works: connect your account and try it for free on the demo plan. Code orders, introduction and withdrawal for remote sales, returns: all in one browser window.
An expert replies in English in the account chat in 15 minutes on average, 7 days a week. 7 days of full access for free, no card required.