For importers · February 16, 2026
Certificate or declaration: how to understand what your product needs
How the forms of conformity confirmation differ, and who chooses the right one.
Part of the goods does not fall under technical regulations. No permit document is issued for them, but the platform still asks for confirmation — and the refusal letter serves as that.
The refusal letter is the most underrated document on the list. It is often considered a “weak replacement for a certificate”, although it solves a different task: to prove that no document is needed at all.
What the platforms ask for in other cases — in the article on documents for Wildberries and Ozon.
A good refusal letter reads like a short expert opinion: what the product is, what the code is, which regulations were considered and why the product does not fall under them. A bad one reads like a note “not subject” without a single reference.
The document has no validity period: it reflects the state of regulation on the date of issue. But the product lists change, so a letter older than two or three years should be updated — especially if new regulations have appeared in your category.
This is where the main misunderstanding lies. A refusal letter is not a state document. It is not issued by Rosaccreditation, it is not entered in a state register and it has no single approved form. It is the conclusion of a certification body that the product does not fall under mandatory conformity confirmation.
Two practical consequences follow from this.
During customs clearance, permit documents are required depending on the HS code (TN VED): if the code falls into the list of goods for which conformity documents are needed, the inspector will ask for them. In this situation the refusal letter serves as the reasoning why your particular product does not fall under the requirement, although the code formally matches.
This works when the item in the list is described more broadly than your product. A classic example: the code covers a group of products, some of which are intended for children and require documents, while your products are for adults and do not fall under the regulation.
What the letter will not do: it will not cancel the requirement if the product really falls under a regulation. An attempt to “close” with a refusal letter a product that needs a declaration is not a trick but a violation, which is revealed at the first check.
Like other documents, a refusal letter comes in two kinds, and the number of times it can be used depends on this.
| For a batch | For serial production | |
|---|---|---|
| What it is tied to | A specific delivery, contract, invoice | The products of a certain manufacturer |
| When it is convenient | A one-time purchase | Regular deliveries of one range |
| Term | Lives together with the batch | Usually up to a year, set by the issuing organization |
| Risk | It cannot be attached to the next delivery | If the product changed, the letter is no longer about it |
For marketplaces a letter for a series is requested more often: a card lives long, and batches change.
There are situations in which a refusal letter does not close the question, even if everything is formally correct.
And separately: if you yourself are not sure whether the product falls under a regulation or not, a refusal letter is not a way to remove the uncertainty. It records a conclusion, it does not replace the analysis. How this analysis works was explained in the article on product lists and in the material on choosing the document form.
Since there is no register, the responsibility for the choice lies fully with you. The minimum check before payment:
The last item filters out most: an organization that issues letters in an hour based on the code alone does not analyze the product — it prints a template.
For importers · February 16, 2026
How the forms of conformity confirmation differ, and who chooses the right one.
Marketplaces · July 1, 2026
What the platforms require when you create a product card, and why cards get blocked.
HS code (TN VED) · February 23, 2026
Why the lists matter more than the code, and how to check whether your product falls under the regulation.