Component Approved Translated Unreviewed Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
administration BSD-2-Clause 92% 99% 106 1 36 225 1 13
applications BSD-2-Clause
essentials BSD-2-Clause 29% 100% 665 43
finance BSD-2-Clause 16% 100% 8,877 764
general BSD-2-Clause 6% 100% 1,971 186
hr BSD-2-Clause 15% 100% 4,798 263
index BSD-2-Clause 0% 1
inventory_and_mrp BSD-2-Clause 5% 98% 7,149 106 2,701 18,644 106 1,267
marketing BSD-2-Clause 6% 100% 2,363 152
Glossary Odoo Documentation Glossary
Glossary Odoo Main Glossary 6% 272
productivity BSD-2-Clause 14% 100% 3,629 276
sales BSD-2-Clause 13% 99% 4,339 24 535 3,695 24 374
services BSD-2-Clause 10% 100% 953 91
sphinx BSD-2-Clause
studio BSD-2-Clause 90% 75
websites BSD-2-Clause 20% 99% 1,746 2 85 684 2 151

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 Spanish (Latin America)
Language code es_419
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 363,966,079
08/22/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 44,780 788,886 5,584,660
Approved 17% 7,677 19% 153,065 19% 1,087,511
Waiting for review 82% 36,944 80% 632,438 80% 4,473,700
Translated 99% 44,647 99% 785,529 99% 5,561,412
Needs editing 0% 0 0% 0 0% 0
Read-only 1% 26 1% 26 1% 201
Failing checks 7% 3,580 11% 86,942 10% 594,928
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 1% 133 1% 3,357 1% 23,248
Last 12 months Previous

Activity in last 12 months

0 changes 5,010 changes 0 changes 2,585 changes 0 changes 4,033 changes 0 changes 3,082 changes 0 changes 48,486 changes 0 changes 835 changes 0 changes 1,488 changes 0 changes 1,247 changes 0 changes 1,134 changes 0 changes 1,461 changes 0 changes 2,104 changes 41,290 changes 1,824 changes
AugSepOctNovDecJanFebMarAprMayJunJul

Quick numbers

788 k
Hosted words
44,780
Hosted strings
99%
Translated
4
Contributors
and previous 30 days

Trends of last 30 days

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

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