Component Approved Translated Unreviewed Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
administration BSD-2-Clause 0% 99% 1,468 3 41 248 3 9
applications BSD-2-Clause 0% 2
essentials BSD-2-Clause 0% 100% 939 2
finance BSD-2-Clause 0% 98% 10,545 108 1,404 11,626 108 71
general BSD-2-Clause 0% 97% 2,069 49 804 5,905 49 3
hr BSD-2-Clause 0% 100% 5,645 31
index BSD-2-Clause 0% 1
inventory_and_mrp BSD-2-Clause 0% 94% 7,314 398 8,935 63,582 398 23
marketing BSD-2-Clause 0% 96% 2,432 85 1,752 12,800 85 8
Glossary Odoo Documentation Glossary
Glossary Odoo Main Glossary 0% 83% 230 44 70 498 44
productivity BSD-2-Clause 0% 99% 4,222 28 592 3,986 28 12
sales BSD-2-Clause 0% 97% 4,953 108 2,072 14,718 108 20
services BSD-2-Clause 0% 100% 1,070 2 821
sphinx BSD-2-Clause 0% 52
studio BSD-2-Clause 0% 100% 773 2
websites BSD-2-Clause 0% 98% 2,177 23 396 3,057 23 1

Summary

Project website www.odoo.com
Project reviewers52 User avatar cimaUser avatar ronmUser avatar mseaUser avatar paujUser avatar juauUser avatar madiUser avatar ngtoUser avatar petiUser avatar chwaUser avatar noplUser avatar anastasiia_odooUser avatar pagcUser avatar mfarUser avatar kwpaUser avatar lman_odooUser avatar wacmUser avatar Alina LisnenkoUser avatar hedsheferUser avatar cmd-odooUser avatar mapr-odooUser avatar GRCOodooUser avatar maan_odooUser avatar awt_odooUser avatar MichaelHadarUser avatar vladimir.uvid …
Language Russian
Language code ru
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 201,151,468
08/26/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 44,764 788,845 5,584,355
Approved 0% 0 0% 0 0% 0
Waiting for review 98% 43,892 97% 772,753 97% 5,467,734
Translated 98% 43,918 97% 772,779 97% 5,467,935
Needs editing 0% 0 0% 0 0% 0
Read-only 1% 26 1% 26 1% 201
Failing checks 1% 184 1% 4,201 1% 28,088
Strings with suggestions 1% 821 2% 18,988 2% 127,779
Untranslated strings 1% 846 2% 16,066 2% 116,420
Last 12 months Previous

Activity in last 12 months

0 changes 40,732 changes 0 changes 1,339 changes 0 changes 1,695 changes 0 changes 2,692 changes 0 changes 43,426 changes 0 changes 83 changes 0 changes 415 changes 0 changes 668 changes 0 changes 760 changes 0 changes 343 changes 0 changes 4,907 changes 7,933 changes 43,106 changes
AugSepOctNovDecJanFebMarAprMayJunJul

Quick numbers

788 k
Hosted words
44,763
Hosted strings
98%
Translated
4
Contributors
and previous 30 days

Trends of last 30 days

+1%
Hosted words
+1%
+1%
Hosted strings
+1%
−1%
Translated
+94%
—
Contributors
+100%
User avatar webhook:github

Resource updated
The “locale/ru/LC_MESSAGES/inventory_and_mrp.po” file was changed. 08/22/2026
User avatar webhook:github

String added in the repository
If products are allocated to specific orders, users can also click :guilabel:`Print Labels` to print an individual label for each unit of the allocated products. Each label displays the name of the product, its associated |SO|/|MO| number, and its customer (for |SOs|).
 
08/22/2026
User avatar webhook:github

String added in the repository
The printed report from an allocation report.
 
08/22/2026
User avatar webhook:github

String added in the repository
After allocating the desired units, click :guilabel:`Print` at the top to download a PDF of the allocation report for the allocated units. The report includes a scannable barcode at the top for the receipt or |MO|.
 
08/22/2026
User avatar webhook:github

String added in the repository
The user can now assign all 75 units from |MO| A to fulfill Customer B's delivery.
 
08/22/2026
User avatar webhook:github

String added in the repository
Because the company wants to prioritize Customer B's order, they want to ensure Customer B receives 75 units from |MO| A, which can guarantee faster delivery. To do so, they first open |MO| B's allocation report and assign 50 units to Customer A's |SO|. Odoo then recalculates |MO| A's allocation report, updating Customer A's previous quantity of 75 units to 25 units and Customer B's quantity to 75 units.
 
08/22/2026
User avatar webhook:github

String added in the repository
After confirming the |MOs|, the company uses the allocation reports for each |MO|. |MO| A's report lists the |SO| for Customer A with 75 reservable units, then Customer B's |SO| with 25 reservable units. |MO| B's report lists the |SO| for Customer A with 50 reservable units.
 
08/22/2026
User avatar webhook:github

String added in the repository
No stock exists for the *Chair*, so the company creates and confirms |MO| A to manufacture the product. Only 100 units of the *Chair* can be produced this week. So, another |MO| B is created to replenish the remaining 50 units next week.
 
08/22/2026
User avatar webhook:github

String added in the repository
The following example demonstrates how an allocation report is used to assign stock for a customer |SO| of higher priority.
 
08/22/2026
User avatar webhook:github

String added in the repository
To fulfill a component demand on an |MO|, navigate to the |MO|. The replenished components in the previous step are now marked as :guilabel:`Available` for production on this |MO|. Click :guilabel:`Produce` to manufacture the final product.
 
08/22/2026
Browse all changes for this language