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 24
applications BSD-2-Clause 0% 2
essentials BSD-2-Clause 0% 100% 939 29
finance BSD-2-Clause 0% 98% 10,485 168 2,506 19,659 168 69
general BSD-2-Clause 0% 97% 2,074 44 668 4,916 44 40
hr BSD-2-Clause 0% 99% 5,625 20 511 3,700 20 50
index BSD-2-Clause 0% 1
inventory_and_mrp BSD-2-Clause 0% 94% 7,314 398 8,554 60,617 398 494
marketing BSD-2-Clause 0% 96% 2,432 85 1,752 12,800 85 53
Glossary Odoo Documentation Glossary
Glossary Odoo Main Glossary 0% 81% 222 49 78 547 49 1
productivity BSD-2-Clause 0% 99% 4,242 8 232 1,347 8 118
sales BSD-2-Clause 0% 99% 5,033 28 623 4,337 28 99
services BSD-2-Clause 0% 100% 1,070 41
sphinx BSD-2-Clause 0% 52
studio BSD-2-Clause 0% 100% 773 22
websites BSD-2-Clause 0% 98% 2,177 23 561 4,611 23 28

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 Portuguese (Brazil)
Language code pt_BR
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 200,247,320
08/26/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 44,761 788,839 5,584,314
Approved 0% 0 0% 0 0% 0
Waiting for review 98% 43,909 97% 773,287 97% 5,471,331
Translated 98% 43,935 98% 773,313 97% 5,471,532
Needs editing 0% 0 0% 0 0% 0
Read-only 1% 26 1% 26 1% 201
Failing checks 2% 1,067 3% 31,380 3% 217,370
Strings with suggestions 1% 1 1% 1 1% 7
Untranslated strings 1% 826 1% 15,526 2% 112,782
Last 12 months Previous

Activity in last 12 months

0 changes 800 changes 0 changes 1,339 changes 0 changes 590 changes 0 changes 1,395 changes 0 changes 43,426 changes 0 changes 83 changes 0 changes 415 changes 0 changes 806 changes 0 changes 1,028 changes 0 changes 343 changes 0 changes 3,744 changes 41,290 changes 20,299 changes
AugSepOctNovDecJanFebMarAprMayJunJul

Quick numbers

788 k
Hosted words
44,760
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
+43%
—
Contributors
−100%
User avatar webhook:github

Resource updated
The “locale/pt_BR/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