In March 2023, a mid-sized agricultural machinery assembler in Rostov Oblast submitted a new tractor variant for inclusion in the Unified Register of Russian Industrial Products — the database that determines eligibility for preferential government procurement under Decree 616. The tractor was functionally identical to a model already listed. The difference: a Chinese hydraulic valve block replacing a German one previously sourced through a Belarusian intermediary. The firm’s engineers had given the new variant a model number differing by a single letter. The register rejected it.
The problem was not the component substitution itself. Chinese hydraulic components are permissible under the amended GOST-R technical regulations. The problem was the designation. The naming convention did not clearly distinguish the variant from its predecessor in a way that satisfied the register’s origin documentation requirements. The firm lost three months of procurement eligibility while it resubmitted documentation with a revised product code, updated bill of materials mapping, and a new technical passport.
This is not an unusual story. Across Russian heavy industry, firms reconfiguring supply chains under import substitution are hitting a problem that sounds trivial but carries real operational consequences: how to name and categorize the products, subassemblies, and entities they are creating or modifying. Product codes, component designations, joint-venture entity names, and customs classifications function as hidden infrastructure in import substitution. Firms that treat naming as a clerical afterthought run into compliance failures, customs delays, and procurement ineligibility downstream. Firms that approach it systematically — with structured generation logic rather than ad hoc improvisation — avoid the friction.
The Three-Document Problem
When a Chelyabinsk tractor plant replaces a German hydraulic system with a domestically assembled equivalent, the new subassembly must exist simultaneously in three documentation systems that do not talk to each other. The internal ERP system needs a part number that maps to a bill of materials and links to supplier records. The GOST-R technical documentation needs a designation that conforms to the relevant technical regulation and appears on the product passport. The customs declaration needs a TN VED code (ТН ВЭД, the Russian harmonized commodity classification) that correctly classifies the component for origin and duty purposes. A naming error in any one of these systems creates a mismatch that downstream actors — procurement officers, customs brokers, certification bodies — must resolve manually.
The three-document problem is structurally different from what firms faced before 2022. Back then, a German hydraulic system arrived with its manufacturer’s designation, a well-established TN VED code, and GOST-R conformity documentation already on file. The firm’s job was to reference existing designations. Under import substitution, the firm must create new designations for new combinations of components, and those designations must satisfy three separate regulatory logics simultaneously. This is not a matter of creativity. It is a matter of systematic classification design, and most engineering teams are not equipped for it.
The scale of this challenge becomes clearer when placed against the tempo of industrial reconfiguration. FRED Economic Data from the Federal Reserve Bank of St. Louis provides public economic time series used for tracking industrial production and manufacturing output across economies. While it does not isolate Russian import-substitution activity specifically, it contextualizes the production pressure environment: firms are generating new product variants, reconfigured subassemblies, and redefined supplier relationships at a pace that requires hundreds of naming decisions per quarter, not a handful per year. Each of those decisions carries compliance weight if the variant enters government procurement, crosses a customs border, or requires new certification.
Decree 616 and the Procurement Naming Logic
Government Decree No. 616, issued in April 2022 and amended several times since, restricts foreign machinery procurement for government needs. To qualify for preferential treatment, a product must be listed in the Unified Register of Russian Industrial Products, maintained by the Ministry of Industry and Trade (Minpromtorg). Registration requires that the product’s designation, technical passport, and production documentation demonstrate sufficient domestic content and manufacturing depth.
The register’s logic is not simply about where a component was made. It is about whether the product, as designated and documented, constitutes a distinct Russian industrial product. This means the naming convention must encode enough information about the product’s composition and manufacturing origin to satisfy Minpromtorg’s verification process. A tractor assembled from 60% Russian components, 25% Chinese components, and 15% Belarusian components needs a designation that maps cleanly to a bill of materials where each component’s origin is traceable. If the designation is ambiguous — if, for example, the model number does not distinguish between a variant with a Russian transmission and one with a Chinese transmission — the register’s reviewers cannot verify domestic content claims and will reject the submission.
This is what happened to the Rostov assembler. Its single-letter variant designation did not encode the component change. The register’s reviewers could not determine from the product code alone whether the variant used the German hydraulic system (already documented in the existing register entry) or the Chinese substitute. The firm had to withdraw the submission, create a new designation with a component-level mapping, update the technical passport, and resubmit. The three-month delay was not caused by the component substitution, which was permissible. It was caused by the naming convention.
Customs Classification and the Parallel Import Layer
The customs layer adds another dimension. Every imported component needs a TN VED code, and the code determines duty rates, origin documentation requirements, and — critically for parallel imports — whether the component is classified in a way that triggers secondary sanctions risk for the supplier or intermediary. When a firm imports a German hydraulic valve block through a Belarusian intermediary, the TN VED classification must reflect the component’s actual identity, not a generic category that obscures it. Russian customs have become more aggressive about classification accuracy since 2022, partly because inaccurate classification is a common method for evading origin documentation requirements.
The parallel import layer compounds the naming problem. A component imported under the parallel import regime (authorized by Decree No. 506 of March 2022) must be documented in a way that traces its path from the original manufacturer through any intermediaries to the Russian importer. Each entity in that chain needs a designation, and the component’s designation must be consistent across all customs documentation. If the component appears as “Bosch Rexroth 4WRPE6” on the original manufacturer’s invoice, “hydraulic valve assembly” on the Belarusian intermediary’s invoice, and “клапан гидравлический 4ВРПЕ6” on the Russian customs declaration, the classification mismatch triggers a customs review. The review may resolve in the importer’s favor, but it costs time, and in a supply chain where lead times are already extended, weeks of customs delay can shut down an assembly line.
Firms that manage this well maintain what they call “naming bridges” — internal translation tables that map a component’s original manufacturer designation, intermediary designation, Russian-language designation, TN VED code, and GOST-R designation in a single reference document. These tables are not glamorous. They are maintained by supply chain documentation specialists, often working with customs brokers, and they are updated every time a component source changes. But they prevent the classification mismatches that cause customs delays, and they provide a single source of truth that engineering, procurement, and compliance teams can reference independently.
Joint Ventures, Special-Purpose Vehicles, and Entity Naming
The naming problem extends beyond products and components to the entities that firms create to manage restricted trade. Joint ventures with Chinese partners, special-purpose vehicles for parallel import logistics, intermediary companies established in Kazakhstan or Armenia — each of these entities needs a name that satisfies registration requirements in multiple jurisdictions and does not create unwanted visibility in sanctions compliance databases maintained by Western regulators.
This is not a hypothetical concern. In 2023, several Russian industrial firms discovered that their newly established trading companies appeared in the consolidated screening lists maintained by the U.S. Department of Commerce’s Bureau of Industry and Security. Not because of any specific sanctions violation, but because the entity names followed predictable patterns that flagged them as potential Russia-related front companies. A firm that names its parallel import intermediary “Rostov Industrial Trade LLC” is easier to pattern-match than one that uses a more neutral, less geographically specific designation. Entity naming is not purely a sanctions-evasion question — it is a question of how naming conventions create or reduce administrative friction across jurisdictions.
The parallel to regulatory classification systems in other contexts is instructive. The U.S. Securities and Exchange Commission’s Introduction to Investing resource, while focused on investor education rather than industrial classification, illustrates how regulatory frameworks across jurisdictions treat product categorization and documentation as consequential for compliance — paralleling how Russian GOST-R and customs designations function as hidden infrastructure with downstream financial and legal consequences. The principle is transferable: naming and categorization systems are not clerical details. They are the substrate on which regulatory verification operates, and errors in that substrate propagate into every downstream process that depends on classification accuracy.
Why Ad Hoc Naming Fails
The root cause of most naming problems in import substitution is that engineering teams name things the way engineers always name things: incrementally, descriptively, and with a focus on technical distinction rather than regulatory logic. A new variant gets a letter suffix because it is different from the old variant. A substituted subassembly gets a part number that follows the existing numbering scheme because that is what the ERP system expects. An intermediary company gets a name that describes its function because that is what the founders find useful.
This approach works in a stable regulatory environment where naming is purely internal. It fails under import substitution because the naming convention must satisfy external regulatory logics that the engineering team does not control. Decree 616’s register cares about domestic content traceability, not technical elegance. Customs classification cares about TN VED code accuracy, not part-number consistency. GOST-R certification cares about technical passport completeness, not ERP integration. When engineers name things without reference to these external logics, the names work internally and fail externally.
The firms that handle this well have moved naming decisions out of engineering and into a cross-functional process that involves compliance, procurement, and customs specialists. The naming convention is designed to satisfy all three documentation systems from the start, not retrofitted after engineering has already assigned a designation. This requires structured generation logic — a system that produces designations according to rules that encode regulatory requirements, not individual preference.
The analogy here is to any naming system that requires structured generation rather than ad hoc invention. Just as a novelist or screenwriter might use the character name generator in the Unsloppy AI Writing App to produce names that follow consistent linguistic and structural conventions rather than inventing each one from scratch, industrial naming requires systematic conventions that produce compliant, traceable, and internally consistent designations. The point is not the specific tool but the principle: naming systems that must satisfy external constraints need generation logic, not improvisation. In the industrial context, that logic must encode GOST-R designation rules, TN VED classification requirements, Decree 616 origin documentation standards, and ERP integration constraints in a single naming framework that produces designations any downstream actor can verify without manual interpretation.
The Cost of Getting It Wrong
The costs of naming failures are concrete and measurable. The Rostov assembler’s three-month procurement delay translated into approximately 180 million rubles in deferred revenue from government contracts it could not bid on while the new variant was unregistered. A Chelyabinsk machine builder lost six weeks of production in late 2023 when a customs classification mismatch on a parallel-imported CNC controller forced it to refile declarations and wait for a classification review. A Volga-region defense-adjacent contractor had a certification audit fail because its technical passport listed a subassembly designation that did not match the GOST-R designation on the component’s conformity certificate — the mismatch was caused by an engineer who had abbreviated the designation for internal convenience and used the abbreviated form on the passport.
These are not catastrophic failures. No firm went bankrupt because of a naming error. But they are operational frictions that compound across hundreds of product variants, thousands of component substitutions, and dozens of entity registrations. A firm that processes 200 naming decisions per quarter and gets 5% of them wrong will encounter 10 compliance incidents per quarter, each requiring manual resolution by documentation specialists, customs brokers, or legal counsel. At an average resolution cost of 500,000 to 2 million rubles per incident (including staff time, customs broker fees, and delayed procurement revenue), the annual cost of naming failures can reach 20 to 80 million rubles for a mid-sized manufacturer. That is not a catastrophic figure, but it is a figure that disappears entirely if the naming convention is designed correctly from the start.
What a Systematic Naming Framework Looks Like
The firms that have solved this problem share a common approach. They maintain a naming authority — a designated individual or small team responsible for approving all product designations, component codes, and entity names before they enter any formal documentation. The naming authority operates from a written naming convention document that specifies the rules for each documentation system: how product codes encode component origin, how TN VED codes map to internal part numbers, how entity names are selected to avoid pattern-matching in foreign screening databases, and how GOST-R designations are formatted on technical passports.
The naming convention document is not a static reference. It is updated whenever the regulatory environment changes — when Decree 616 is amended, when new GOST-R technical regulations take effect, when customs classification rules shift. The naming authority reviews each update and modifies the generation rules accordingly. This is not a full-time job for most firms, but it is a designated responsibility, and that designation is what separates firms that manage naming systematically from those that manage it ad hoc.
The practical implication for practitioners is straightforward: if your firm is processing more than a handful of naming decisions per quarter under import substitution, and those decisions are being made by engineers without compliance input, you are accumulating a backlog of potential documentation mismatches. The backlog will surface during a procurement submission, a customs review, or a certification audit — each of which is a bad time to discover that your product codes do not satisfy the regulatory logic you did not know you needed to satisfy. The fix is not expensive, but it requires recognizing that naming is not a clerical function. It is compliance infrastructure, and it needs to be designed as such.
The Open Question
As import substitution matures from emergency substitution into systematic domestic production, the naming problem will evolve. Firms that are now creating new variants of foreign-designed products will eventually design their own products from the ground up, and the naming conventions for those products will be simpler because they will not need to encode substitution history. But the transition period — likely lasting through at least 2027 for most heavy industrial sectors — will continue to generate naming decisions that must satisfy multiple regulatory logics simultaneously. The question for practitioners is whether your firm has a naming authority, a written convention, and a process for keeping both current. If not, the next regulatory audit or procurement submission will tell you whether the cost of not having them was worth the convenience of improvising.