diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 685eb9166..af353345b 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-15.2\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-26 13:30+0000\n" +"POT-Creation-Date: 2023-12-19 07:46+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -529,7 +529,6 @@ msgid "Odoo static files live in each module's ``static/`` folder, so static fil msgstr "" #: ../../content/administration/install/deploy.rst:398 -#: ../../content/administration/upgrade.rst:122 msgid "Todo" msgstr "" @@ -841,8 +840,9 @@ msgstr "" #: ../../content/administration/install/online.rst:14 #: ../../content/administration/maintain/domain_names.rst:166 #: ../../content/administration/maintain/domain_names.rst:236 -#: ../../content/administration/maintain/supported_versions.rst:31 -#: ../../content/administration/upgrade/odoo_online.rst:3 +#: ../../content/administration/maintain/supported_versions.rst:29 +#: ../../content/administration/upgrade.rst:90 +#: ../../content/administration/upgrade.rst:307 msgid "Odoo Online" msgstr "" @@ -1930,9 +1930,10 @@ msgstr "" #: ../../content/administration/maintain/domain_names.rst:171 #: ../../content/administration/maintain/domain_names.rst:250 -#: ../../content/administration/maintain/supported_versions.rst:32 +#: ../../content/administration/maintain/supported_versions.rst:30 #: ../../content/administration/odoo_sh.rst:5 -#: ../../content/administration/upgrade/odoo_sh.rst:3 +#: ../../content/administration/upgrade.rst:120 +#: ../../content/administration/upgrade.rst:318 msgid "Odoo.sh" msgstr "" @@ -2952,7 +2953,7 @@ msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:293 #: ../../content/administration/odoo_sh/getting_started/settings.rst:77 #: ../../content/administration/odoo_sh/getting_started/settings.rst:113 -#: ../../content/administration/upgrade.rst:10 +#: ../../content/administration/upgrade.rst:3 msgid "Upgrade" msgstr "" @@ -2961,7 +2962,7 @@ msgid "Trigger a database upgrade." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:33 -msgid "For more information about the upgrade process, check out the :doc:`Odoo Online upgrade documentation <../upgrade/odoo_online>`." +msgid "For more information about the upgrade process, check out the :ref:`Odoo Online upgrade documentation `." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:39 @@ -3257,70 +3258,64 @@ msgstr "" msgid "The database uuid is currently accessible from the menu :menuselection:`Settings --> Technical --> System Parameters`, we advise you to use a `uuid generator `_ or to use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any other record by clicking on it and using the edit button." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:6 -#: ../../content/administration/upgrade.rst:208 +#: ../../content/administration/maintain/supported_versions.rst:7 msgid "Supported versions" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:8 +#: ../../content/administration/maintain/supported_versions.rst:9 msgid "Odoo provides support and bug fixing **for the 3 last major versions** of Odoo." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:11 +#: ../../content/administration/maintain/supported_versions.rst:12 msgid "Odoo releases intermediary versions called **Online versions** on the :doc:`Odoo Online ` hosting every two months. Odoo Online users can then benefit from the latest features of Odoo." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:15 +#: ../../content/administration/maintain/supported_versions.rst:16 msgid "Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade>` them regularly." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:16 +#: ../../content/administration/maintain/supported_versions.rst:17 msgid "Online versions are *not* released for Odoo.sh and On-Premise installations." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:17 +#: ../../content/administration/maintain/supported_versions.rst:18 msgid "Online versions are listed below as *SaaS*." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:20 -msgid "What's the support status of my Odoo?" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:22 msgid "This matrix shows the support status of every version." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:24 +#: ../../content/administration/maintain/supported_versions.rst:22 msgid "**Major releases are in bold type.**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:33 -#: ../../content/administration/upgrade/on_premise.rst:3 +#: ../../content/administration/maintain/supported_versions.rst:31 msgid "On-Premise" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:34 +#: ../../content/administration/maintain/supported_versions.rst:32 msgid "Release date" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:35 +#: ../../content/administration/maintain/supported_versions.rst:33 msgid "End of support" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:36 -msgid "Odoo saas~16.4" +#: ../../content/administration/maintain/supported_versions.rst:34 +msgid "**Odoo 17.0**" msgstr "" +#: ../../content/administration/maintain/supported_versions.rst:35 +#: ../../content/administration/maintain/supported_versions.rst:36 #: ../../content/administration/maintain/supported_versions.rst:37 -#: ../../content/administration/maintain/supported_versions.rst:61 -#: ../../content/administration/maintain/supported_versions.rst:62 -#: ../../content/administration/maintain/supported_versions.rst:63 -#: ../../content/administration/maintain/supported_versions.rst:79 -#: ../../content/administration/maintain/supported_versions.rst:80 -#: ../../content/administration/maintain/supported_versions.rst:81 +#: ../../content/administration/maintain/supported_versions.rst:41 +#: ../../content/administration/maintain/supported_versions.rst:65 +#: ../../content/administration/maintain/supported_versions.rst:66 +#: ../../content/administration/maintain/supported_versions.rst:67 +#: ../../content/administration/maintain/supported_versions.rst:83 +#: ../../content/administration/maintain/supported_versions.rst:84 #: ../../content/administration/maintain/supported_versions.rst:85 -#: ../../content/administration/maintain/supported_versions.rst:86 -#: ../../content/administration/maintain/supported_versions.rst:87 #: ../../content/administration/odoo_sh/getting_started/settings.rst:58 #: ../../content/administration/odoo_sh/getting_started/settings.rst:59 #: ../../content/administration/odoo_sh/getting_started/settings.rst:62 @@ -3352,161 +3347,172 @@ msgid "|green|" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:38 +#: ../../content/administration/maintain/supported_versions.rst:93 +msgid "November 2023" +msgstr "" + #: ../../content/administration/maintain/supported_versions.rst:39 -#: ../../content/administration/maintain/supported_versions.rst:44 -#: ../../content/administration/maintain/supported_versions.rst:45 -#: ../../content/administration/maintain/supported_versions.rst:50 -#: ../../content/administration/maintain/supported_versions.rst:51 -#: ../../content/administration/maintain/supported_versions.rst:56 -#: ../../content/administration/maintain/supported_versions.rst:57 -#: ../../content/administration/maintain/supported_versions.rst:68 -#: ../../content/administration/maintain/supported_versions.rst:69 -#: ../../content/administration/maintain/supported_versions.rst:74 -#: ../../content/administration/maintain/supported_versions.rst:75 -msgid "N/A" +msgid "November 2026 (planned)" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:40 -msgid "August 2023" +msgid "Odoo saas~16.4" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:42 -msgid "Odoo saas~16.3" +#: ../../content/administration/maintain/supported_versions.rst:43 +#: ../../content/administration/maintain/supported_versions.rst:48 +#: ../../content/administration/maintain/supported_versions.rst:49 +#: ../../content/administration/maintain/supported_versions.rst:54 +#: ../../content/administration/maintain/supported_versions.rst:55 +#: ../../content/administration/maintain/supported_versions.rst:60 +#: ../../content/administration/maintain/supported_versions.rst:61 +#: ../../content/administration/maintain/supported_versions.rst:72 +#: ../../content/administration/maintain/supported_versions.rst:73 +#: ../../content/administration/maintain/supported_versions.rst:78 +#: ../../content/administration/maintain/supported_versions.rst:79 +msgid "N/A" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:43 -#: ../../content/administration/maintain/supported_versions.rst:49 -#: ../../content/administration/maintain/supported_versions.rst:55 -#: ../../content/administration/maintain/supported_versions.rst:67 -#: ../../content/administration/maintain/supported_versions.rst:73 -#: ../../content/administration/maintain/supported_versions.rst:91 -#: ../../content/administration/maintain/supported_versions.rst:92 -#: ../../content/administration/maintain/supported_versions.rst:93 -msgid "|red|" +#: ../../content/administration/maintain/supported_versions.rst:44 +msgid "August 2023" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:46 +msgid "Odoo saas~16.3" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:47 +#: ../../content/administration/maintain/supported_versions.rst:53 +#: ../../content/administration/maintain/supported_versions.rst:59 +#: ../../content/administration/maintain/supported_versions.rst:71 +#: ../../content/administration/maintain/supported_versions.rst:77 +#: ../../content/administration/maintain/supported_versions.rst:89 +#: ../../content/administration/maintain/supported_versions.rst:90 +#: ../../content/administration/maintain/supported_versions.rst:91 +#: ../../content/administration/maintain/supported_versions.rst:95 +#: ../../content/administration/maintain/supported_versions.rst:96 +#: ../../content/administration/maintain/supported_versions.rst:97 +#: ../../content/administration/maintain/supported_versions.rst:101 +#: ../../content/administration/maintain/supported_versions.rst:102 +#: ../../content/administration/maintain/supported_versions.rst:103 +msgid "|red|" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:50 msgid "June 2023" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:48 +#: ../../content/administration/maintain/supported_versions.rst:52 msgid "Odoo saas~16.2" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:52 +#: ../../content/administration/maintain/supported_versions.rst:56 msgid "March 2023" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:54 +#: ../../content/administration/maintain/supported_versions.rst:58 msgid "Odoo saas~16.1" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:58 +#: ../../content/administration/maintain/supported_versions.rst:62 msgid "February 2023" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:60 +#: ../../content/administration/maintain/supported_versions.rst:64 msgid "**Odoo 16.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:64 -#: ../../content/administration/maintain/supported_versions.rst:95 +#: ../../content/administration/maintain/supported_versions.rst:68 +#: ../../content/administration/maintain/supported_versions.rst:99 msgid "October 2022" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:65 -msgid "October 2025 (planned)" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:66 -msgid "Odoo saas~15.2" +#: ../../content/administration/maintain/supported_versions.rst:69 +msgid "November 2025 (planned)" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:70 +msgid "Odoo saas~15.2" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:74 msgid "March 2022" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:71 +#: ../../content/administration/maintain/supported_versions.rst:75 msgid "January 2023" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:72 +#: ../../content/administration/maintain/supported_versions.rst:76 msgid "Odoo saas~15.1" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:76 +#: ../../content/administration/maintain/supported_versions.rst:80 msgid "February 2022" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:77 +#: ../../content/administration/maintain/supported_versions.rst:81 msgid "July 2022" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:78 +#: ../../content/administration/maintain/supported_versions.rst:82 msgid "**Odoo 15.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:82 +#: ../../content/administration/maintain/supported_versions.rst:86 msgid "October 2021" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:83 -msgid "October 2024 (planned)" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:84 -msgid "**Odoo 14.0**" +#: ../../content/administration/maintain/supported_versions.rst:87 +msgid "November 2024 (planned)" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:88 +msgid "**Odoo 14.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:92 msgid "October 2020" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:89 -msgid "November 2023 (planned)" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:90 +#: ../../content/administration/maintain/supported_versions.rst:94 msgid "**Odoo 13.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:94 +#: ../../content/administration/maintain/supported_versions.rst:98 msgid "October 2019" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:99 -msgid "|green| Supported version" +#: ../../content/administration/maintain/supported_versions.rst:100 +msgid "Older versions" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:101 -msgid "|red| End-of-support" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:103 -msgid "N/A Never released for this platform" +#: ../../content/administration/maintain/supported_versions.rst:104 +msgid "Before 2019" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:105 -msgid "🏁 Future version, not released yet" +msgid "Before 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:107 +msgid "Legend" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:109 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:111 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:113 +msgid "N/A Never released for this platform" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:116 -msgid "I run an older version of Odoo/OpenERP/TinyERP" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:118 -msgid "Odoo 12.0, 11.0, 10.0, 9.0, and 8.0 are not supported anymore, on any platform." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:120 -msgid "OpenERP 7.0, 6.1, 6.0 and 5.0 are not supported anymore, on any platform." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:122 -msgid "TinyERP 4.0, 3.0, 2.0 and 1.0 are not supported anymore, on any platform." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:124 msgid "Even though we don't support older versions, you can always `upgrade from any version `_." msgstr "" @@ -3675,7 +3681,6 @@ msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:6 #: ../../content/administration/odoo_sh/getting_started/status.rst:6 #: ../../content/administration/odoo_sh/overview.rst:5 -#: ../../content/administration/upgrade/odoo_sh.rst:8 msgid "Overview" msgstr "" @@ -4366,7 +4371,7 @@ msgid "Available for production and staging branches for valid projects." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:298 -msgid ":doc:`Upgrade - Odoo.sh <../../upgrade/odoo_sh>`" +msgid ":doc:`Upgrade documentation <../../upgrade>`" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:303 @@ -5908,954 +5913,511 @@ msgstr "" msgid "The documentation will help you go live with your Odoo.sh project in no time." msgstr "" -#: ../../content/administration/upgrade.rst:20 -msgid "An upgrade is switching to a newer version of Odoo (e.g., Odoo 14.0 to Odoo 15.0)." +#: ../../content/administration/upgrade.rst:5 +msgid "An upgrade is the process of moving your database from an older version to a newer :doc:`supported version ` (e.g., Odoo 14.0 to Odoo 16.0). Frequently upgrading is essential as each version comes with new and improved features, bug fixes, and security patches." msgstr "" -#: ../../content/administration/upgrade.rst:22 -msgid "An upgrade does not cover:" -msgstr "" - -#: ../../content/administration/upgrade.rst:24 -msgid "Changing :ref:`editions ` (i.e., Community to Enterprise edition)" -msgstr "" - -#: ../../content/administration/upgrade.rst:25 -msgid "Switching :ref:`hosting type ` (i.e., On-Premise to Odoo Online or Odoo.sh)" -msgstr "" - -#: ../../content/administration/upgrade.rst:27 -msgid "Migration from another ERP to Odoo" -msgstr "" - -#: ../../content/administration/upgrade.rst:29 -#: ../../content/administration/upgrade.rst:148 -#: ../../content/administration/upgrade.rst:259 -#: ../../content/administration/upgrade/faq.rst:81 -#: ../../content/administration/upgrade/faq.rst:92 -#: ../../content/administration/upgrade/faq.rst:119 -msgid "|assistance-contact|" -msgstr "" - -#: ../../content/administration/upgrade.rst:32 -msgid ":ref:`upgrade/sla`" -msgstr "" - -#: ../../content/administration/upgrade.rst:37 -msgid "Process workflow" -msgstr "" - -#: ../../content/administration/upgrade.rst:39 -msgid "The upgrade process in a nutshell:" -msgstr "" - -#: ../../content/administration/upgrade.rst:41 -msgid "You create a test upgrade request." -msgstr "" - -#: ../../content/administration/upgrade.rst:42 -msgid "Odoo processes the request automatically by running the database through an upgrade script, which takes between 20 and 120 minutes." -msgstr "" - -#: ../../content/administration/upgrade.rst:44 -msgid "Odoo delivers a test database." -msgstr "" - -#: ../../content/administration/upgrade.rst:45 -msgid "You test your database for possible discrepancies (see :ref:`upgrade/test-guidance`)." -msgstr "" - -#: ../../content/administration/upgrade.rst:46 -msgid "If there are any discrepancies, you report them to the Upgrade support team via the help portal (see :ref:`upgrade/test-assistance`)." -msgstr "" - -#: ../../content/administration/upgrade.rst:48 -msgid "We fix the issues and send you a new test database." -msgstr "" - -#: ../../content/administration/upgrade.rst:49 -msgid "Once you have completed the testing and are happy with the result, you decide on a date and time when you stop users from accessing Odoo, freeze all data entries, and create an upgrade request for the production upgrade." -msgstr "" - -#: ../../content/administration/upgrade.rst:52 -msgid "Odoo delivers the production database through the automated process." -msgstr "" - -#: ../../content/administration/upgrade.rst:53 -msgid "You restore it in your Production environment a few short hours later and continue working on the newly upgraded database (this is done automatically on Odoo Online)." -msgstr "" - -#: ../../content/administration/upgrade.rst:57 -msgid ":doc:`Upgrade process for Odoo Online `" -msgstr "" - -#: ../../content/administration/upgrade.rst:58 -msgid ":doc:`Upgrade process for Odoo.sh `" -msgstr "" - -#: ../../content/administration/upgrade.rst:59 -msgid ":doc:`Upgrade process for On-Premise `" -msgstr "" - -#: ../../content/administration/upgrade.rst:64 -msgid "Testing" -msgstr "" - -#: ../../content/administration/upgrade.rst:66 -msgid "This phase allows you to review an upgraded version of your database without affecting your production database in any way. We suggest that you run the test upgrade process at least once, but you can do it as many times as you need (one at a time)." -msgstr "" - -#: ../../content/administration/upgrade.rst:70 -msgid "Once you receive your upgraded test database, check that all data, processes, and functionality are still correct and working as expected." -msgstr "" - -#: ../../content/administration/upgrade.rst:73 -msgid "If you do find discrepancies, :ref:`report your issues ` and :ref:`request a new test database ` when the reported issues are fixed in the upgrade script." -msgstr "" - -#: ../../content/administration/upgrade.rst:77 -msgid "If you do not find any discrepancies, you can move on to the upgrade of your production database." -msgstr "" - -#: ../../content/administration/upgrade.rst:80 -msgid "A test database is only intended for testing and remains completely unrelated to your present or future production database. Any data you add, or changes you make, will not be reflected in your upgraded production database." -msgstr "" - -#: ../../content/administration/upgrade.rst:85 -msgid "Test databases are neutered and features are disabled to prevent them from having an impact on the production database:" -msgstr "" - -#: ../../content/administration/upgrade.rst:88 -msgid "The serial number of the database is modified (to prevent it from sending information as if it was the production database)." -msgstr "" - -#: ../../content/administration/upgrade.rst:90 -msgid "The :ref:`base URL of the database ` is reset to ``http://localhost:8069`` and the email domain to ``localhost``." -msgstr "" - -#: ../../content/administration/upgrade.rst:92 -msgid "Scheduled actions are disabled (the calendar synchronization, the bank statement synchronization, the planned automated actions, the fetching of incoming mail servers, etc.)." -msgstr "" - -#: ../../content/administration/upgrade.rst:94 -msgid "Outgoing mail servers are disabled by archiving the existing ones and adding a fake/non-working one." -msgstr "" - -#: ../../content/administration/upgrade.rst:96 -msgid "Payment providers and delivery carriers are reset to test environment." -msgstr "" - -#: ../../content/administration/upgrade.rst:97 -msgid "Accounting localization Electronic Data Interchange (EDI) services are disabled." -msgstr "" - -#: ../../content/administration/upgrade.rst:98 -msgid "A system parameter is set to tell the database has been neutered." -msgstr "" - -#: ../../content/administration/upgrade.rst:103 -msgid "Request a test database" -msgstr "" - -#: ../../content/administration/upgrade.rst:105 -msgid "Follow the instructions available per hosting type on the `website form `_ and select *Testing* purpose." -msgstr "" - -#: ../../content/administration/upgrade.rst:-1 -msgid "Selection of the \"Testing\" purpose in the upgrade form on Odoo" -msgstr "" - -#: ../../content/administration/upgrade.rst:115 -msgid "Test guidance" -msgstr "" - -#: ../../content/administration/upgrade.rst:117 -msgid "Every business and organization has its own operational needs and has to test its specific Odoo database individually. We recommend you look at `the test scenario `_ for further information." -msgstr "" - -#: ../../content/administration/upgrade.rst:122 -msgid "change link \"test scenario\" once the related doc is published" -msgstr "" - -#: ../../content/administration/upgrade.rst:127 -#: ../../content/administration/upgrade.rst:172 -msgid "Assistance" -msgstr "" - -#: ../../content/administration/upgrade.rst:129 -msgid "If you encounter an issue in the **test database**, please get in touch with Odoo Upgrade Support via the `Odoo Support page `_." -msgstr "" - -#: ../../content/administration/upgrade.rst:132 -msgid "Under the *Ticket Description* section, select *An issue related to my upgrade* ticket type." +#: ../../content/administration/upgrade.rst:13 +msgid "The Rolling Release process allows Odoo Online customers to upgrade their database directly from a message prompt sent to the database administrator as soon as a new version is released. The invitation to upgrade is only sent if no issues are detected during the automatic tests." msgstr "" #: ../../content/administration/upgrade.rst:0 -msgid "Selection of \"An issue related to my upgrade\" as Ticket Type in the support form on Odoo" +msgid "The upgrade message prompt on the top right of the database" msgstr "" -#: ../../content/administration/upgrade.rst:139 -msgid "If you choose another *Ticket Description* type, the request will be redirected to another team. This will slow down the processing and response time." +#: ../../content/administration/upgrade.rst:20 +msgid "It is strongly recommended to manually :ref:`test the upgrade first `. Clicking :guilabel:`I want to test first` redirects to `the database manager `_, where it is possible to request an upgraded test database and check it for any discrepancies." msgstr "" -#: ../../content/administration/upgrade.rst:142 -#: ../../content/administration/upgrade.rst:185 -msgid "Please provide as much detail as you can (i.e., videos and screenshots to illustrate your issue). This will avoid clarifying questions and speed up the resolution process significantly." +#: ../../content/administration/upgrade.rst:25 +msgid "It is **not** recommended to click :guilabel:`Upgrade Now` without testing first, as it immediately triggers the live production database upgrade." msgstr "" -#: ../../content/administration/upgrade.rst:146 -msgid "The purpose of the test phase is not to correct existing data or configurations in your database." +#: ../../content/administration/upgrade.rst:28 +msgid "If the Rolling Release process detects an issue with the upgrade, it will be deactivated until the issue is resolved." msgstr "" -#: ../../content/administration/upgrade.rst:153 -msgid "The production launch" +#: ../../content/administration/upgrade.rst:31 +msgid "An upgrade does not cover:" msgstr "" -#: ../../content/administration/upgrade.rst:155 -msgid "The production upgrade request is when you decide to upgrade your current database with all your production data (invoices, VAT returns, inventories, current orders) to a new version of your choice." +#: ../../content/administration/upgrade.rst:33 +msgid "Downgrading to a previous version of Odoo" msgstr "" -#: ../../content/administration/upgrade.rst:159 -msgid "After your :ref:`tests ` are completed to your satisfaction, submit the request to upgrade your production database via our `website form `_. Select *Production* purpose." +#: ../../content/administration/upgrade.rst:34 +msgid ":doc:`Switching editions ` (e.g., from Community to Enterprise)" msgstr "" -#: ../../content/administration/upgrade.rst:164 -msgid "Going into production without first testing may lead to:" +#: ../../content/administration/upgrade.rst:35 +msgid ":doc:`Changing hosting type ` (e.g., from on-premise to Odoo Online)" msgstr "" -#: ../../content/administration/upgrade.rst:166 -msgid "business interruptions (e.g., no longer having the possibility to validate an action)" +#: ../../content/administration/upgrade.rst:37 +msgid "Migrating from another ERP to Odoo" msgstr "" -#: ../../content/administration/upgrade.rst:167 -msgid "poor customer experiences (e.g., an eCommerce website that does not work correctly)" +#: ../../content/administration/upgrade.rst:40 +msgid "If your database contains a **custom module**, you must first upgrade its source code to be compatible with the new version of Odoo **before upgrading**." msgstr "" -#: ../../content/administration/upgrade.rst:174 -msgid "If you encounter issues or problems in the **production database**, please get in touch with **Odoo Support**:" +#: ../../content/administration/upgrade.rst:47 +msgid "Upgrading in a nutshell" msgstr "" -#: ../../content/administration/upgrade.rst:177 -msgid "Connect to our `Odoo Support page `_." +#: ../../content/administration/upgrade.rst:49 +msgid "Request an upgraded test database (see :ref:`obtaining an upgraded test database `)." msgstr "" -#: ../../content/administration/upgrade.rst:178 -msgid "Under the *Ticket Description* section, select the appropriate type related to your issue but **do not select** the option *An issue related to my upgrade*." +#: ../../content/administration/upgrade.rst:52 +msgid "Thoroughly test the upgraded database (see :ref:`testing the new version of the database `)." msgstr "" -#: ../../content/administration/upgrade.rst:182 -msgid "After upgrading to production, the support will be provided by the Support team instead of the Upgrade team." +#: ../../content/administration/upgrade.rst:55 +msgid "Report any issue encountered during the testing to Odoo via the `support page `__." msgstr "" -#: ../../content/administration/upgrade.rst:189 -msgid "If you choose *An issue related to my upgrade* as ticket type, the request will be redirected to another team than the support one and will slow down the processing and response time." +#: ../../content/administration/upgrade.rst:58 +msgid "(If applicable) : upgrade the source code of your custom module to be compatible with the new version of Odoo." msgstr "" -#: ../../content/administration/upgrade.rst:195 -msgid "Help" +#: ../../content/administration/upgrade.rst:61 +msgid "Once all issues are resolved and you are confident that the upgraded database can be used as your main database without any issues, plan the upgrade of your production database." msgstr "" -#: ../../content/administration/upgrade.rst:200 -msgid "Contact our upgrade service support" +#: ../../content/administration/upgrade.rst:64 +msgid "Request the upgrade for the production database, rendering it unavailable for the time it takes to complete the process (see :ref:`upgrading the production database `)." msgstr "" -#: ../../content/administration/upgrade.rst:202 -msgid "Should you have any more questions about the upgrade, do not hesitate to send a message to `Odoo Upgrade Team `_. We will be happy to answer it as soon as possible." +#: ../../content/administration/upgrade.rst:67 +msgid "Report any issue encountered during the upgrade to Odoo via the `support page `__." msgstr "" -#: ../../content/administration/upgrade.rst:210 -msgid "Please note that Odoo provides support and bug fixing only for the three last major versions of Odoo." +#: ../../content/administration/upgrade.rst:76 +msgid "Obtaining an upgraded test database" msgstr "" -#: ../../content/administration/upgrade.rst:213 -msgid "This is a factor to take into consideration before upgrading. If you are on an older version, we suggest you to prefer the most recent version to benefit from longer support (before having to upgrade again)." +#: ../../content/administration/upgrade.rst:78 +msgid "The `Upgrade page `_ is the main platform for requesting an upgraded database. However, depending on the hosting type, you can upgrade from the command line (on-premise), the `Odoo Online database manager `_, or your `Odoo.sh project `_." msgstr "" -#: ../../content/administration/upgrade.rst:218 -msgid ":doc:`maintain/supported_versions`" +#: ../../content/administration/upgrade.rst:84 +msgid "The Upgrade platform follows the same `Privacy Policy `_ as the other Odoo.com services. Visit the `General Data Protection Regulation page `_ to learn more about how Odoo handles your data and privacy." msgstr "" -#: ../../content/administration/upgrade.rst:223 -msgid "Service-level agreement (SLA)" +#: ../../content/administration/upgrade.rst:92 +msgid "Odoo Online databases can be manually upgraded via the `database manager `_." msgstr "" -#: ../../content/administration/upgrade.rst:225 -msgid "With Odoo Enterprise, upgrading a database to the most recent version of Odoo is **free**, including any support required to rectify potential discrepancies in the upgraded database." +#: ../../content/administration/upgrade.rst:95 +msgid "The database manager displays all databases associated with the user's account. Databases not on the most recent version of Odoo display an arrow in a circle icon next to their name, indicating that they can be upgraded." msgstr "" -#: ../../content/administration/upgrade.rst:228 -msgid "Information about the upgrade services included in the Enterprise Licence is available in the :ref:`Odoo Enterprise Subscription Agreement `. However, this section clarifies what upgrade services you can expect." +#: ../../content/administration/upgrade.rst:0 +msgid "The database manager with an upgrade button next to the name of a database." msgstr "" -#: ../../content/administration/upgrade.rst:233 -msgid "Upgrade services covered by the SLA" +#: ../../content/administration/upgrade.rst:102 +msgid "Click the **arrow in a circle** icon to start the upgrade process. In the popup, fill in:" msgstr "" -#: ../../content/administration/upgrade.rst:235 -msgid "Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or self-hosted (On-Premise) can benefit from upgrade services at all times for:" +#: ../../content/administration/upgrade.rst:104 +msgid "The **version** of Odoo you want to upgrade to, usually the latest version" msgstr "" -#: ../../content/administration/upgrade.rst:238 -msgid "the upgrade of all **standard applications**;" +#: ../../content/administration/upgrade.rst:105 +msgid "The **email** address that should receive the link to the upgraded database" msgstr "" -#: ../../content/administration/upgrade.rst:239 -msgid "the upgrade of all **customizations created with the Studio app**, as long as Studio is still installed and the respective subscription is still active; and" +#: ../../content/administration/upgrade.rst:106 +msgid "The :guilabel:`Purpose` of the upgrade, which is automatically set to :guilabel:`Test` for your first upgrade request" msgstr "" -#: ../../content/administration/upgrade.rst:241 -msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**." +#: ../../content/administration/upgrade.rst:0 +msgid "The \"Upgrade your database\" popup." msgstr "" -#: ../../content/administration/upgrade.rst:244 -msgid "Upgrade services are limited to the technical conversion and adaptation of a database (standard modules and data) to make it compatible with the version targeted by the upgrade." +#: ../../content/administration/upgrade.rst:112 +msgid "The :guilabel:`Upgrade in progress` tag is displayed next to the database name until completion. Once the process succeeds, an email containing a link to the upgraded test database is sent to the address provided. The database can also be accessed from the database manager by clicking the dropdown arrow before the database name." msgstr "" -#: ../../content/administration/upgrade.rst:248 -msgid "Upgrade services not covered by the SLA" +#: ../../content/administration/upgrade.rst:0 +msgid "Clicking the menu arrow displays the upgraded test database." msgstr "" -#: ../../content/administration/upgrade.rst:250 -msgid "The following upgrade-related services are **not** included:" +#: ../../content/administration/upgrade.rst:122 +msgid "Odoo.sh is integrated with the upgrade platform to simplify the upgrade process." msgstr "" -#: ../../content/administration/upgrade.rst:252 -msgid "the **cleaning** of pre-existing data and configurations while upgrading;" -msgstr "" - -#: ../../content/administration/upgrade.rst:253 -msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;" -msgstr "" - -#: ../../content/administration/upgrade.rst:254 -msgid "lines of **code added to standard modules**, i.e., customizations created outside the Studio app, code entered manually, and :ref:`automated actions using Python code `; and" -msgstr "" - -#: ../../content/administration/upgrade.rst:257 -msgid "**training** on using the upgraded version's features and workflows." -msgstr "" - -#: ../../content/administration/upgrade.rst:262 -msgid ":doc:`Upgrade FAQ `" -msgstr "" - -#: ../../content/administration/upgrade.rst:263 -msgid ":doc:`Odoo.sh documentation `" -msgstr "" - -#: ../../content/administration/upgrade.rst:264 -msgid ":doc:`Supported Odoo versions `" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:8 -msgid "FAQ" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:13 -msgid "Why upgrade" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:15 -msgid "You benefit from the latest features of the :ref:`new major version ` released by Odoo." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:17 -msgid "If you are in an :ref:`unsupported version `, you get a new version with support." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:23 -msgid "When to upgrade" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:25 -msgid "Whenever you want. You can make your upgrade request as soon as a new version is released or when your version turns unsupported, and you still wish to enjoy support." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:31 -msgid "Availability of the new version" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:33 -msgid "As soon as Odoo announces the release of a new major version, you can create a test upgrade request to try the latest version. Please note that at this point, the upgrade scripts will only have been tested with demo data. Please report any issue you might encounter while testing via the `Odoo Support page `_ and make sure to be happy with your test version before requesting the upgrade of your database in production." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:42 -msgid "Duration of the upgrade" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:44 -msgid "It is impossible to give time estimates for every upgrade request." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:46 -msgid "In general, the \"smaller\" the database, the quickest the upgrade request is completed. A single-user database that uses only CRM will be processed faster than a multi-company, multi-user database that uses Accounting, Sales, Purchase, and Manufacturing." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:50 -msgid "You can expect the time it takes for the platform to upgrade the test database to be similar to the production upgrade." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:56 -msgid "Duration of the upgrade project" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:58 -msgid "It depends on the user involvement (the time spent on testing, reporting problems, etc.) and the issues encountered that might need to be addressed by our technical team." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:61 -msgid "So, in a nutshell, what can impact your upgrade lead time?" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:63 -msgid "Source & targeted versions" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:64 -msgid "Installed apps" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:65 -msgid "Volume of data" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:66 -msgid "Amount of customization (models, fields, methods, workflows, reports, website, etc.)" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:67 -msgid "Installation of new apps or configuration changes after the start of the test phase" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:68 -msgid "User commitment" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:73 -msgid "Upgrade of the custom modules" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:75 -msgid "As stated in our :doc:`/legal/terms/enterprise`, section :ref:`charges_standard`, this optional service is subject to additional fees." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:78 -msgid "Depending on your situation, the custom code could be upgraded by our services, by one of our partners, or you can do it yourself." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:86 -msgid "Upgrade or Migration" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:88 -msgid "An upgrade is switching to a newer version of Odoo, while a migration reflects the change of :ref:`editions ` or change of :ref:`hosting type `." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:97 -msgid "Editions change (from Community to Enterprise)" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:99 -msgid "The upgrade always returns an Enterprise edition of Odoo, whether the database you sent was a community or enterprise edition. It is required to have an enterprise subscription to upgrade." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:103 -msgid "If you need assistance on this matter, please contact us via the `Odoo Support page `_." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:107 -msgid "`Editions `_" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:112 -msgid "Switching the hosting types (On-premise vs. Odoo Online vs. Odoo.sh)" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:114 -msgid "An upgrade does not cover a change of `Hosting types `_." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:116 -msgid "Open the following link to get :doc:`more information about how to change your hosting type <../maintain/hosting_changes>`." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:124 -msgid "The Upgrade Report" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:126 -msgid "When an upgrade request completes successfully (test or production), you receive an email notification about it that includes an 'Upgrade Report'. This report is also sent to you via the Discuss app. It contains valuable information regarding changes that occurred during the upgrade. While it serves as a guide to possible issues to look out for, it is not an exhaustive list. It remains imperative that you test the upgraded database thoroughly and report any discrepancies you might find, before you decide to upgrade your production database." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:136 -msgid "Custom views" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:138 -msgid "During the upgrade, some custom views might get disabled for technical reasons. Therefore they might have to be fixed after the upgrade. The :ref:`Upgrade Report ` that is generated after the upgrade is available in the Discuss app, and lists all the custom views that might be impacted by this." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:146 -msgid "Release Notes by version" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:148 -msgid "Open our `Release Note `_ page to get a summary of the new features and improvements made in each version." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:152 -msgid "How long is my test available for" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:154 -msgid "An Odoo Online test database is available for one month by default. We can extend this trial period upon request. For Odoo.sh or on-premise, there is no restriction." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:158 -msgid "How many tests to perform before upgrading to production?" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:160 -msgid "As many as needed. When you are comfortable with the database, run a last test upgrade 48 hours before requesting your production upgrade and test your workflows one last time." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:164 -msgid "How to/Where to report upgrade issues?" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:166 -msgid "If you encounter issues during the upgrade process, please contact the Odoo Support through the `Odoo Support page `_." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:169 -msgid "To report an issue discovered during the testing phase, please select **An issue related to my upgrade (test phase)**." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:171 -msgid "To report an issue discovered post-upgrade, please select **An issue related to my upgrade (production)**." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:175 -msgid "Upgrading to production" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:177 -msgid "Once you have completed testing and are happy with the result, you decide on a date and time when you stop users from accessing Odoo, freeze all data entries, and create an upgrade request for the production upgrade." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:182 -msgid "How is my data handled in the Upgrade Platform?" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:184 -msgid "The Odoo Upgrade platform uses the same Privacy Policy as the rest of Odoo.com services." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:186 -msgid "Your data is hosted on servers that follow our security guidelines, namely:" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:188 -msgid "SSL - All web connections to client instances are protected with 256-bit SSL encryption (HTTPS with a 2048-bit modulus SSL certificate), and running behind Grade A SSL stacks. All our certificate chains are using SHA-2 already." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:191 -msgid "Safe System - Our servers are running recent Linux distribution with up-to-date security patches, with firewall and intrusion countermeasures (not disclosed for obvious reasons)." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:194 -msgid "Servers are located at the same locations as our Cloud providers with the following services:" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:196 -msgid "Restricted perimeter, physically accessed by authorized data center employees only" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:197 -msgid "Physical access control with security badges or biometrical security" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:198 -msgid "Security cameras monitoring the data center locations 24/7" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:199 -msgid "Security personnel on-site 24/7" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:201 -msgid "The uploaded and migrated databases uploaded to the Upgrade platform are kept for up to 3 months and are permanently deleted following that period." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:204 -msgid "You can learn more about privacy and data handling at Odoo by visiting our `General Data Protection Regulation page `_." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:208 -msgid "Rolling Release (applicable to Odoo Online databases)" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:210 -msgid "This feature allows customers to upgrade their database directly from a message prompt sent to the database administrator as soon as the new version is released. Odoo first tests the upgrade to the next version. The rolling release upgrade option is displayed if the automated tests are successful. The message offers two options:" -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:215 -msgid "To 'Upgrade Now', which immediately triggers the upgrade of your live production database." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:217 -msgid "To take you to your `database manager `_ where you can `request an upgraded test database `_ and check the upgraded test database for any discrepancies." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:221 -msgid "When you choose to proceed with the production upgrade directly, make sure all users have saved their work and are logged out. The upgrade takes approximately 15 minutes. During this time your database is unreachable. If you notice any problem after the upgrade, please report it via the `Odoo Support page `_." -msgstr "" - -#: ../../content/administration/upgrade/faq.rst:227 -msgid "If you are using the Website or Studio app, we recommend you always do a test upgrade before upgrading your production instance." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:5 -msgid "Odoo databases can be manually upgraded directly from the main Odoo website. To upgrade an Odoo database, navigate to the `database manager `_ page and sign in." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:8 -msgid "The database manager page displays all of the Odoo databases associated with the user's account. Any databases that are not already on the most recent version of Odoo display an **arrow in a circle** icon next to the database name, indicating that the database can be upgraded." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:-1 -msgid "The database manager page with an upgrade button next to the name of a database." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:17 -msgid "If the database's version is **lower** than the latest major release: the database must be upgraded within two months. After these two months, an automatic upgrade is initiated." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:19 -msgid "If the database's version is **equal** to or **higher** than the latest major release: you can disregard the invitation to upgrade, as the database probably would not benefit from new features every two months." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:23 -msgid "If a database is *not* on the latest online version, its administrator should receive an invitation to upgrade on the database's dashboard, displayed as an **arrow in a circle**." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:-1 -msgid "Invitation to upgrade on the database dashboard." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:30 -msgid "Versions that are not supported anymore become deprecated and must be updated to avoid security issues. It is recommended to initiate the upgrade yourself and not wait for the automatic upgrade, as the former method allows you to request a test upgrade of the database to check for any discrepancies." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:36 -msgid "Test database" -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:38 -msgid "Click on the **arrow in a circle** icon to start the upgrade process. On the :guilabel:`Upgrade your database` pop-up, select the version of Odoo that the platform will be upgraded to. In the :guilabel:`Email to notify` field, enter an email address that will receive email notifications about the database upgrade." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:43 -msgid "There is also a :guilabel:`Purpose` section on the pop-up that is used to specify the reason for the upgrade. However, at this stage of the process, the only selectable option is :guilabel:`Test`, as Odoo requires users to create a test copy of the upgraded database before converting the actual database." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:-1 -msgid "The \"Upgrade your database\" pop-up." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:52 -msgid "After filling out the form, click the :guilabel:`Upgrade` button. The pop-up disappears and the database being upgraded shows a red :guilabel:`Upgrade in progress` tag next to its name. An email confirming that the upgrade is in progress is also sent to the email address specified on the pop-up." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:-1 -msgid "The \"Upgrade in progress\" tag next to the database name." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:61 -msgid "Once the upgrade is complete, a new test database appears on the `database manager `_ page. To access the test database, click the drop-down arrow (:guilabel:`⯆`) to the left of the main database's name. Doing so makes the test version appear below it. Finally, click the green :guilabel:`Connect` button on the right side of the test version's row to go to the database." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:-1 -msgid "A test database on the database manager page." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:71 -msgid "Except for being on the newer version of Odoo, the test database is an exact copy of the one being upgraded. It is important to do extensive testing in this database to ensure that the upgrade has not altered or corrupted any data, and that all workflows still proceed as expected." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:76 -msgid "Production database" -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:78 -msgid "After confirming the integrity of the new version, return to the `database manager `_ page. Once again, click on the **arrow in a circle** icon next to the database being upgraded. The :guilabel:`Upgrade your database` pop-up appears as before, except that there is now a :guilabel:`Production` option under the :guilabel:`Purpose` section." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:83 -msgid "Select the :guilabel:`Production` option and then click :guilabel:`Upgrade` to begin the upgrade process. As before, a notification email is sent to the email address provided and a red :guilabel:`Upgrade in progress` tag appears next to the name of the database." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:87 -msgid "The production database is then taken offline and will be upgraded automatically. The time it takes to upgrade the production database should be similar to the time that was necessary to upgrade the test database. Make sure to inform database users of the scheduled downtime." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:91 -msgid "After the upgrade is finished, the :guilabel:`Upgrade in progress` tag disappears and the database is upgraded to the version specified." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:10 -msgid "Odoo.sh is integrated with the upgrade platform to make the upgrade process easier." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:13 -msgid "The :guilabel:`Upgrade` tab is available in the branches view. It is only available for valid projects with a valid production build." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:-1 -msgid "Click on the upgrade menu" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:20 -msgid "The suggested upgrade steps on Odoo.sh are:" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:22 -msgid "On a :guilabel:`Development` branch, upgrade your custom modules to keep them compatible with the new version and thoroughly **test them**." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:24 -msgid "Switch that branch to the :guilabel:`Staging` branch, **upgrade** the last daily production backup and **test it**. Write upgrade scripts if necessary." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:26 -msgid "Trigger the production upgrade from your :guilabel:`Production` branch and sit tight." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:29 -msgid ":doc:`../../administration/upgrade`" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:30 -msgid ":doc:`Upgrade FAQ <../upgrade/faq>`" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:31 -msgid ":doc:`Introduction to Odoo.sh <../odoo_sh/overview/introduction>`" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:36 -msgid "Upgrade your custom modules" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:38 -msgid "The first step is to upgrade your custom modules to keep them compatible with the new version. Fork your :guilabel:`Production` branch in the :guilabel:`Development` stage, then go to the settings of your :guilabel:`Development` branch and select the Odoo version you target. If needed, modify your code to be compatible with the new version. Make sure to **test** your features are still working correctly." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:45 -msgid "Depending on your contract, the upgrade of your custom modules can be done by yourself, by your Partner or by Odoo (if you hold a subscription including maintenance of customizations)." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:51 -msgid "Upgrade your database on a staging branch" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:53 -msgid "Take the upgraded development branch and drag & drop it to :guilabel:`Staging`." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:55 -msgid "Go to the :guilabel:`Upgrade` tab and select the :guilabel:`target version`. Then, click on :guilabel:`Test Upgrade`." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:-1 +#: ../../content/administration/upgrade.rst:0 msgid "Odoo.sh project and tabs" msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:62 -msgid "The **latest production daily automatic backup** is sent to the `upgrade platform `_ to start the upgrade test process." +#: ../../content/administration/upgrade.rst:127 +msgid "The **latest production daily automatic backup** is then sent to the `upgrade platform `_." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:66 -msgid "You can follow the upgrade process by going to the :guilabel:`Upgrade` menu of your :guilabel:`Production` branch." +#: ../../content/administration/upgrade.rst:130 +msgid "Once the upgrade platform is done upgrading the backup and uploading it on the branch, it is put in a **special mode**: each time a **commit is pushed** on the branch, a **restore operation** of the upgraded backup and an **update of all the custom modules** occur. This allows you to test your custom modules on a pristine copy of the upgraded database. The log file of the upgrade process can be found in your newly upgraded staging build by going to :file:`~/logs/upgrade.log`." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:69 -msgid "When the upgraded backup is ready on the `upgrade platform `_, it is automatically downloaded back to your project." +#: ../../content/administration/upgrade.rst:138 +msgid "In databases where custom modules are installed, their source code must be up-to-date with the target version of Odoo before the upgrade can be performed. If there are none, the \"update on commit\" mode is skipped, the upgraded database is built as soon as it is transferred from the upgrade platform, and the upgrade mode is exited." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:72 -msgid "The branch is now in a **special mode**: each time a **commit is pushed** on the branch, a **restore operation** of the upgraded backup occurs, and an **update of all the custom modules** happens. This allows you to quickly iterate on your custom modules upgrade scripts. The log file of the upgrade process can be found at :file:`~/logs/upgrade.log` in your newly upgraded staging build." +#: ../../content/administration/upgrade.rst:150 +#: ../../content/administration/upgrade.rst:342 +msgid "On-premise" msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:78 -msgid "The **special upgrade mode** is automatically closed after 30 days." +#: ../../content/administration/upgrade.rst:152 +msgid "The standard upgrade process can be initiated by entering the following command line on the machine where the database is hosted:" msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:79 -#: ../../content/administration/upgrade/odoo_sh.rst:128 -msgid "It may happen that custom modules are no longer needed after an upgrade. Custom modules in the upgraded database are set to be updated. If the modules are missing in the code, the update fails, thus failing the whole process. An empty module with a manifest and possibly some custom upgrade script are necessary to clean up the database. The complete removal of the module has to be handled afterwards." +#: ../../content/administration/upgrade.rst:159 +msgid "The following command can be used to display the general help and the main commands:" msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:86 -msgid "Functionally test your upgraded database" +#: ../../content/administration/upgrade.rst:165 +msgid "An upgraded test database can also be requested via the `Upgrade page `_." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:88 -msgid "Now that the test upgraded database is available on your staging branch, **thoroughly test it** and make sure everything runs as it's supposed to. Once you are satisfied with the result, you are ready to upgrade your production database." +#: ../../content/administration/upgrade.rst:169 +msgid "For security reasons, only the person who submitted the upgrade request can download it." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:93 -msgid "Production upgrade" +#: ../../content/administration/upgrade.rst:170 +msgid "For storage reasons, the database's copy is submitted without a filestore to the upgrade server. Therefore, the upgraded database does not contain the production filestore." msgstr "" -#: ../../content/administration/upgrade/odoo_sh.rst:95 -msgid "Once you are happy with your testing, you can start the process on the :guilabel:`Production` branch." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:98 -msgid "On your :guilabel:`Production` branch, go to the :guilabel:`Upgrade` tab, select the :guilabel:`targeted version` and click on the :guilabel:`start Upgrade` button." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:-1 -msgid "View from the upgrade tab" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:105 -msgid "The actual process is **triggered as soon as you push a new commit** in your branch. Make sure you are pushing code that is compatible with the new version. For example by merging the code from your upgraded staging branch." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:110 -msgid "You can see the progress of the upgrade by going to the :guilabel:`Upgrade` tab of the main branch." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:-1 -msgid "View showing the progress of the upgrade" -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:118 -msgid "Your database is unavailable throughout the process." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:121 -msgid "If anything goes wrong, the platform automatically reverts the upgrade, the same as it would be for a regular update. In case of success, a backup is always made." -msgstr "" - -#: ../../content/administration/upgrade/odoo_sh.rst:124 -msgid "The update of your custom modules must be successful to complete the entire upgrade process. Make sure the status of your staging upgrade is :guilabel:`successful` before trying it in production." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:6 -msgid "Test upgrade request" -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:8 -msgid "There are two ways to create your upgrade request." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:11 -msgid "Upgrade request via command line" -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:13 -msgid "For technically-advanced users and partners, the upgrade process can be initiated via the following command line on the server where the database is hosted:" -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:16 -msgid ":command:`python <(curl -s https://upgrade.odoo.com/upgrade) test -d -t `" -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:19 -msgid "The above command creates the database dump, sends it to the upgrade platform, and initiates the automated upgrade process. During the upgrade, you can follow the live logs on your screen. Once the upgrade process is completed successfully, the upgraded database is restored onto the server (as a duplicate test database)." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:25 -msgid "Upgrade request via the Odoo Upgrade Portal" -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:27 -msgid "Download a recent copy of your database and select the option :guilabel:`pg_dump custom format (without filestore)`." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:29 -msgid "Upload this dump file at https://upgrade.odoo.com and select *Testing* as the aim. Odoo performs the automated upgrade process. Once it is completed, you receive an email with a link to download the upgrade database dump file." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:32 -msgid "Import the upgraded database into your on-premise environment and manually test all processes and workflows." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:36 -msgid "For security reasons, only the person who submitted the upgrade request is able to download it." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:37 -msgid "Any problem found during testing should be reported via the `helpdesk `_." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:39 -msgid "For storage reasons, the copy of your database is submitted without a filestore to the upgrade server. Therefore, the upgraded database does not contain the production filestore." -msgstr "" - -#: ../../content/administration/upgrade/on_premise.rst:41 +#: ../../content/administration/upgrade.rst:172 msgid "Before restoring the upgraded database, its filestore must be merged with the production filestore to be able to perform tests in the same conditions as it would be in the new version." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:43 +#: ../../content/administration/upgrade.rst:175 msgid "The upgraded database contains:" msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:45 -msgid "A `dump.sql` file containing the upgraded database." +#: ../../content/administration/upgrade.rst:177 +msgid "A `dump.sql` file containing the upgraded database" msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:46 -msgid "A `filestore` folder containing files that were extracted from in-database records into attachments (if there are any) and new standard Odoo files from the targeted Odoo version (like new images, icons, payment provider's logos, etc.). This is the folder that should be merged with the production filestore in order to get the full upgraded filestore." +#: ../../content/administration/upgrade.rst:178 +msgid "A `filestore` folder containing files extracted from in-database records into attachments (if there are any) and new standard Odoo files from the targeted Odoo version (e.g., new images, icons, payment provider's logos, etc.). This is the folder that should be merged with the production filestore in order to get the full upgraded filestore." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:52 -msgid "Upgrade your production database" +#: ../../content/administration/upgrade.rst:185 +msgid "You can request multiple test databases if you wish to test an upgrade more than once." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:54 -msgid "Once you have completed the testing successfully, you can proceed to upgrade your live database in production. Download your upgraded database from the link in the email and import it onto your live environment." +#: ../../content/administration/upgrade.rst:190 +msgid "When an upgrade request is completed, an upgrade report is attached to the successful upgrade email, and it becomes available in the Discuss app for users who are part of the \"Administration / Settings\" group. This report provides important information about the changes introduced by the new version." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:59 -msgid "Same as in the test phase, when requesting an upgrade for production purposes, the copy of your database is submitted without a filestore." +#: ../../content/administration/upgrade.rst:198 +msgid "Testing the new version of the database" msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:61 -msgid "Therefore, the upgraded database filestore must be merged with the production filestore before deploying the new version." +#: ../../content/administration/upgrade.rst:200 +msgid "It is essential to spend some time testing the upgraded test database to ensure that you are not stuck in your day-to-day activities by a change in views, behavior, or an error message once the upgrade goes live." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:65 -msgid "Custom modules (if applicable)" +#: ../../content/administration/upgrade.rst:205 +msgid "Test databases are neutralized, and some features are disabled to prevent them from impacting the production database:" msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:67 -msgid "The upgrade of a database that contains custom modules is a two-step process." +#: ../../content/administration/upgrade.rst:208 +msgid "Scheduled actions are disabled." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:69 -msgid "The standard upgrade is done when your upgrade request is completed." +#: ../../content/administration/upgrade.rst:209 +msgid "Outgoing mail servers are disabled by archiving the existing ones and adding a fake one." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:70 -msgid "Your custom modules also need to be upgraded to keep them compatible with the new version." +#: ../../content/administration/upgrade.rst:210 +msgid "Payment providers and delivery carriers are reset to the test environment." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:72 -msgid "Depending on your contract, the upgrade of your custom modules can be done" +#: ../../content/administration/upgrade.rst:211 +msgid "Bank synchronization is disabled. Should you want to test the synchronization, contact your bank synchronization provider to get sandbox credentials." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:74 -msgid "by yourself." +#: ../../content/administration/upgrade.rst:214 +msgid "Testing as many of your business flows as possible is strongly recommended to ensure they are working correctly and to get more familiar with the new version." msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:75 -msgid "by your Partner." +#: ../../content/administration/upgrade.rst:217 +msgid "Basic test checklist" msgstr "" -#: ../../content/administration/upgrade/on_premise.rst:76 -msgid "by Odoo (if you hold a subscription to 'Maintenance of Customizations')." +#: ../../content/administration/upgrade.rst:219 +msgid "Are there views that are deactivated in your test database but active in your production database?" +msgstr "" + +#: ../../content/administration/upgrade.rst:221 +msgid "Are your usual views still displayed correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:222 +msgid "Are your reports (invoice, sales order, etc.) correctly generated?" +msgstr "" + +#: ../../content/administration/upgrade.rst:223 +msgid "Are your website pages working correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:224 +msgid "Are you able to create and modify records? (sales orders, invoices, purchases, users, contacts, companies, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:226 +msgid "Are there any issues with your mail templates?" +msgstr "" + +#: ../../content/administration/upgrade.rst:227 +msgid "Are there any issues with saved translations?" +msgstr "" + +#: ../../content/administration/upgrade.rst:228 +msgid "Are your search filters still present?" +msgstr "" + +#: ../../content/administration/upgrade.rst:229 +msgid "Can you export your data?" +msgstr "" + +#: ../../content/administration/upgrade.rst:233 +msgid "Checking a random product in your product catalog and comparing its test and production data to verify everything is the same (product category, selling price, cost price, vendor, accounts, routes, etc.)." +msgstr "" + +#: ../../content/administration/upgrade.rst:236 +msgid "Buying this product (Purchase app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:237 +msgid "Confirming the reception of this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:238 +msgid "Checking if the route to receive this product is the same in your production database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:240 +msgid "Selling this product (Sales app) to a random customer." +msgstr "" + +#: ../../content/administration/upgrade.rst:241 +msgid "Opening your customer database (Contacts app), selecting a customer (or company), and checking its data." +msgstr "" + +#: ../../content/administration/upgrade.rst:243 +msgid "Shipping this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:244 +msgid "Checking if the route to ship this product is the same as in your production database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:246 +msgid "Validating a customer invoice (Invoicing or Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:247 +msgid "Crediting the invoice (issuing a credit note) and checking if it behaves as in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:249 +msgid "Checking your reports' results (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:250 +msgid "Randomly checking your taxes, currencies, bank accounts, and fiscal year (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:251 +msgid "Making an online order (Website apps) from the product selection in your shop until the checkout process and checking if everything behaves as in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:254 +msgid "This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:256 +msgid "If you face an issue while testing your upgraded test database, you can request the assistance of Odoo via the `support page `__ by selecting the option related to testing the upgrade. In any case, it is essential to report any problem encountered during the testing to fix it before upgrading your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:261 +msgid "You might encounter significant differences with standard views, features, fields, and models during testing. Those changes cannot be reverted on a case-by-case basis. However, if a change introduced by a new version breaks a customization, it is the responsibility of the maintainer of your custom module to make it compatible with the new version of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:267 +msgid "Do not forget to test:" +msgstr "" + +#: ../../content/administration/upgrade.rst:269 +msgid "Integrations with external software (EDI, APIs, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:270 +msgid "Workflows between different apps (online sales with eCommerce, converting a lead all the way to a sales order, delivery of products, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:272 +msgid "Data exports" +msgstr "" + +#: ../../content/administration/upgrade.rst:273 +msgid "Automated actions" +msgstr "" + +#: ../../content/administration/upgrade.rst:274 +msgid "Server actions in the action menu on form views, as well as by selecting multiple records on list views" +msgstr "" + +#: ../../content/administration/upgrade.rst:280 +msgid "Upgrading the production database" +msgstr "" + +#: ../../content/administration/upgrade.rst:282 +msgid "Once the :ref:`tests ` are completed and you are confident that the upgraded database can be used as your main database without any issues, it is time to plan the go-live day. It can be planned in coordination with Odoo's upgrade support analysts, reachable via the `support page `__." +msgstr "" + +#: ../../content/administration/upgrade.rst:287 +msgid "Your production database will be unavailable during its upgrade. Therefore, we recommend planning the upgrade at a time when the use of the database is minimal." +msgstr "" + +#: ../../content/administration/upgrade.rst:290 +msgid "As the standard upgrade scripts and your database are constantly evolving, it is also recommended to frequently request another upgraded test database to ensure that the upgrade process is still successful, especially if it takes a long time to finish. Fully rehearsing the upgrade process the day before upgrading the production database is also recommended." +msgstr "" + +#: ../../content/administration/upgrade.rst:296 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade.rst:298 +msgid "Users failing to adjust to the changes and new features" +msgstr "" + +#: ../../content/administration/upgrade.rst:299 +msgid "Business interruptions (e.g., no longer having the possibility to validate an action)" +msgstr "" + +#: ../../content/administration/upgrade.rst:300 +msgid "Poor customer experience (e.g., an eCommerce website that does not work correctly)" +msgstr "" + +#: ../../content/administration/upgrade.rst:302 +msgid "The process of upgrading a production database is similar to upgrading a test database with a few exceptions." +msgstr "" + +#: ../../content/administration/upgrade.rst:309 +msgid "The process is similar to :ref:`obtaining an upgraded test database `, except for the purpose option, which must be set to :guilabel:`Production` instead of :guilabel:`Test`." +msgstr "" + +#: ../../content/administration/upgrade.rst:314 +msgid "Once the upgrade is requested, the database will be unavailable until the upgrade is finished. Once the process is completed, it is impossible to revert to the previous version." +msgstr "" + +#: ../../content/administration/upgrade.rst:320 +msgid "The process is similar to :ref:`obtaining an upgraded test database ` on the :guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "View from the upgrade tab" +msgstr "" + +#: ../../content/administration/upgrade.rst:326 +msgid "The process is **triggered as soon as a new commit is made** on the branch. This allows the upgrade process to be synchronized with the deployment of the custom modules' upgraded source code. If there are no custom modules, the upgrade process is triggered immediately." +msgstr "" + +#: ../../content/administration/upgrade.rst:332 +msgid "The database is unavailable throughout the process. If anything goes wrong, the platform automatically reverts the upgrade, as it would be for a regular update. In case of success, a backup of the database before the upgrade is created." +msgstr "" + +#: ../../content/administration/upgrade.rst:336 +msgid "The update of your custom modules must be successful to complete the entire upgrade process. Make sure the status of your staging upgrade is :guilabel:`successful` before trying it in production." +msgstr "" + +#: ../../content/administration/upgrade.rst:344 +msgid "The command to upgrade a database to production is similar to the one of upgrading a test database except for the argument `test`, which must be replaced by `production`:" +msgstr "" + +#: ../../content/administration/upgrade.rst:351 +msgid "An upgraded production database can also be requested via the `Upgrade page `_. Once the database is uploaded, any modification to your production database will **not** be present on your upgraded database. This is why we recommend not using it during the upgrade process." +msgstr "" + +#: ../../content/administration/upgrade.rst:358 +msgid "When requesting an upgraded database for production purposes, the copy is submitted without a filestore. Therefore, the upgraded database filestore must be merged with the production filestore before deploying the new version." +msgstr "" + +#: ../../content/administration/upgrade.rst:362 +msgid "In case of an issue with your production database, you can request the assistance of Odoo via the `support page `__ by selecting the option related to the upgrade in production." +msgstr "" + +#: ../../content/administration/upgrade.rst:370 +msgid "Service-level agreement (SLA)" +msgstr "" + +#: ../../content/administration/upgrade.rst:372 +msgid "With Odoo Enterprise, upgrading a database to the most recent version of Odoo is **free**, including any support required to rectify potential discrepancies in the upgraded database." +msgstr "" + +#: ../../content/administration/upgrade.rst:375 +msgid "Information about the upgrade services included in the Enterprise Licence is available in the :ref:`Odoo Enterprise Subscription Agreement `. However, this section clarifies what upgrade services you can expect." +msgstr "" + +#: ../../content/administration/upgrade.rst:380 +msgid "Upgrade services covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:382 +msgid "Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or self-hosted (On-Premise) can benefit from upgrade services at all times for:" +msgstr "" + +#: ../../content/administration/upgrade.rst:385 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:386 +msgid "the upgrade of all **customizations created with the Studio app**, as long as Studio is still installed and the respective subscription is still active; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:388 +msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**." +msgstr "" + +#: ../../content/administration/upgrade.rst:391 +msgid "Upgrade services are limited to the technical conversion and adaptation of a database (standard modules and data) to make it compatible with the version targeted by the upgrade." +msgstr "" + +#: ../../content/administration/upgrade.rst:395 +msgid "Upgrade services not covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:397 +msgid "The following upgrade-related services are **not** included:" +msgstr "" + +#: ../../content/administration/upgrade.rst:399 +msgid "the **cleaning** of pre-existing data and configurations while upgrading;" +msgstr "" + +#: ../../content/administration/upgrade.rst:400 +msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;" +msgstr "" + +#: ../../content/administration/upgrade.rst:401 +msgid "lines of **code added to standard modules**, i.e., customizations created outside the Studio app, code entered manually, and :ref:`automated actions using Python code `; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:404 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:407 +msgid ":doc:`Odoo.sh documentation `" +msgstr "" + +#: ../../content/administration/upgrade.rst:408 +msgid ":doc:`Supported Odoo versions `" msgstr "" diff --git a/locale/sources/contributing.pot b/locale/sources/contributing.pot index 599a7aa13..31cc7734b 100644 --- a/locale/sources/contributing.pot +++ b/locale/sources/contributing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-15.2\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-09-12 05:05+0000\n" +"POT-Creation-Date: 2023-12-19 07:46+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -2168,7 +2168,7 @@ msgid "Alert blocks (admonitions)" msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:470 -msgid "Seealso" +msgid "See also" msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:476 diff --git a/locale/sources/developer.pot b/locale/sources/developer.pot index 1d57fe24b..0bd631128 100644 --- a/locale/sources/developer.pot +++ b/locale/sources/developer.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-15.2\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-26 13:30+0000\n" +"POT-Creation-Date: 2023-12-19 07:46+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -531,11 +531,6 @@ msgid "This is achieved with security rules based on `company_ids`, which contai msgstr "" #: ../../content/developer/howtos/company.rst:229 -#: ../../content/developer/howtos/provide_iap_services.rst:118 -#: ../../content/developer/howtos/provide_iap_services.rst:222 -#: ../../content/developer/howtos/provide_iap_services.rst:406 -#: ../../content/developer/howtos/provide_iap_services.rst:408 -#: ../../content/developer/howtos/provide_iap_services.rst:511 #: ../../content/developer/howtos/translations.rst:19 #: ../../content/developer/howtos/website_themes/building_blocks.rst:77 #: ../../content/developer/howtos/website_themes/building_blocks.rst:332 @@ -719,696 +714,6 @@ msgstr "" msgid "In the Driver, an event is released by calling the `device_changed` function from the `event_manager`. All callbacks set on the listener will then be called with `self.data` as argument." msgstr "" -#: ../../content/developer/howtos/provide_iap_services.rst:3 -msgid "Provide IAP services" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:5 -msgid "In-App Purchase (IAP) allows providers of ongoing services through Odoo apps to be compensated for ongoing service use rather than — and possibly instead of — a sole initial purchase." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:9 -msgid "In that context, Odoo acts mostly as a *broker* between a client and an Odoo App Developer:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:12 -msgid "Users purchase service tokens from Odoo." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:13 -msgid "Service providers draw tokens from the user's Odoo account when service is requested." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:18 -msgid "This document is intended for *service providers* and presents the latter, which can be done either via direct JSON-RPC2_ or if you are using Odoo using the convenience helpers it provides." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:23 -#: ../../content/developer/reference/frontend/javascript_reference.rst:17 -#: ../../content/developer/reference/frontend/services.rst:144 -#: ../../content/developer/reference/frontend/services.rst:182 -#: ../../content/developer/reference/frontend/services.rst:362 -#: ../../content/developer/reference/frontend/services.rst:408 -#: ../../content/developer/reference/frontend/services.rst:522 -#: ../../content/developer/reference/frontend/services.rst:612 -#: ../../content/developer/reference/frontend/services.rst:708 -#: ../../content/developer/reference/frontend/services.rst:759 -#: ../../content/developer/reference/frontend/services.rst:834 -msgid "Overview" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:28 -msgid "The Players" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:30 -msgid "The Service Provider is (probably) you the reader, you will be providing value to the client in the form of a service paid per-use." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:32 -msgid "The Client installed your Odoo App, and from there will request services." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:33 -msgid "Odoo brokers crediting, the Client adds credit to their account, and you can draw credits from there to provide services." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:35 -msgid "The External Service is an optional player: *you* can either provide a service directly, or you can delegate the actual service acting as a bridge/translator between an Odoo system and the actual service." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:43 -msgid "The Credits" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:45 -msgid "The credits went from integer to float value starting **October 2018**. Integer values are still supported." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:48 -msgid "Every service provided through the IAP platform can be used by the clients with tokens or *credits*. The credits are an float unit and their monetary value depends on the service and is decided by the provider. This could be:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:53 -msgid "for an sms service: 1 credit = 1 sms;" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:54 -msgid "for an ad service: 1 credit = 1 ad; or" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:55 -msgid "for a postage service: 1 credit = 1 post stamp." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:57 -msgid "A credit can also simply be associated with a fixed amount of money to palliate the variations of price (e.g. the prices of sms and stamps may vary following the countries)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:61 -msgid "The value of the credits is fixed with the help of prepaid credit packs that the clients can buy on https://iap.odoo.com (see :ref:`Packs `)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:64 -msgid "In the following explanations we will ignore the External Service, they are just a detail of the service you provide." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:70 -msgid "'Normal' service flow" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:72 -msgid "If everything goes well, the normal flow is the following:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:74 -msgid "The Client requests a service of some sort." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:75 -msgid "The Service Provider asks Odoo if there are enough credits for the service in the Client's account, and creates a transaction over that amount." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:78 -msgid "The Service Provider provides the service (either on their own or calling to External Services)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:80 -msgid "The Service Provider goes back to Odoo to capture (if the service could be provided) or cancel (if the service could not be provided) the transaction created at step 2." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:83 -msgid "Finally, the Service Provider notifies the Client that the service has been rendered, possibly (depending on the service) displaying or storing its results in the client's system." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:90 -msgid "Insufficient credits" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:92 -msgid "However, if the Client's account lacks credits for the service, the flow will be as follows:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:94 -msgid "The Client requests a service as previously." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:95 -msgid "The Service Provider asks Odoo if there are enough credits on the Client's account and gets a negative reply." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:97 -msgid "This is signaled back to the Client." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:98 -msgid "Who is redirected to their Odoo account to credit it and re-try." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:102 -msgid "Building your service" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:104 -msgid "For this example, the service we will provide is ~~mining dogecoins~~ burning 10 seconds of CPU for a credit. For your own services, you could, for example:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:107 -msgid "provide an online service yourself (e.g. convert quotations to faxes for business in Japan);" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:109 -msgid "provide an *offline* service yourself (e.g. provide accountancy service); or" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:110 -msgid "act as intermediary to an other service provider (e.g. bridge to an MMS gateway)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:116 -msgid "Register the service on Odoo" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:118 -msgid "complete this part with screenshots" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:120 -msgid "The first step is to register your service on the IAP endpoint (production and/or test) before you can actually query user accounts. To create a service, go to your *Portal Account* on the IAP endpoint (https://iap.odoo.com for production, https://iap-sandbox.odoo.com for testing, the endpoints are *independent* and *not synchronized*). Alternatively, you can go to your portal on Odoo (https://iap.odoo.com/my/home) and select *In-App Services*." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:129 -msgid "On production, there is a manual validation step before the service can be used to manage real transactions. This step is automatically passed when on sandbox to ease the tests." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:133 -msgid "Log in then go to :menuselection:`My Account --> Your In-App Services`, click Create and provide the information of your service." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:137 -msgid "The service has *seven* important fields:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:139 -msgid ":samp:`name` - :class:`ServiceName`: This is the string you will need to provide inside the client's :ref:`app ` when requesting a transaction from Odoo. (e.g. :class:`self.env['iap.account].get(name)`). As good practice, this should match the technical name of your app." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:144 -msgid ":samp:`label` - :class:`Label`: The name displayed on the shopping portal for the client." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:149 -msgid "Both the :class:`ServiceName` and :class:`Label` are unique. As good practice, the :class:`ServiceName` should usually match the name of your Odoo Client App." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:152 -msgid ":samp:`icon` - :class:`Icon`: A generic icon that will serve as default for your :ref:`packs `." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:155 -msgid ":samp:`key` - :class:`ServiceKey`: The developer key that identifies you in IAP (see :ref:`your service `) and allows to draw credits from the client's account. It will be shown only once upon creation of the service and can be regenerated at will." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:161 -msgid "Your :class:`ServiceKey` *is a secret*, leaking your service key allows other application developers to draw credits bought for your service(s)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:165 -msgid ":samp:`trial credits` - :class:`Float`: This corresponds to the credits you are ready to offer upon first use to your app users. Note that such service will only be available to clients that have an active enterprise contract." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:169 -msgid ":samp:`privacy policy` - :class:`PrivacyPolicy`: This is an url to the privacy policy of your service. This should explicitly mention the **information you collect**, how you **use it, its relevance** to make your service work and inform the client on how they can **access, update or delete their personal information**." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:186 -msgid "You can then create *credit packs* which clients can purchase in order to use your service." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:192 -msgid "Packs" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:194 -msgid "A credit pack is essentially a product with five characteristics:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:196 -msgid "Name: name of the pack," -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:197 -msgid "Icon: specific icon for the pack (if not provided, it will fallback on the service icon)," -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:198 -msgid "Description: details on the pack that will appear on the shop page as well as the invoice," -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:200 -msgid "Amount: amount of credits the client is entitled to when buying the pack," -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:201 -msgid "Price: price in EUR (for the time being, USD support is planned)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:205 -msgid "Odoo takes a 25% commission on all pack sales. Adjust your selling price accordingly." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:210 -msgid "Depending on the strategy, the price per credit may vary from one pack to another." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:220 -msgid "Odoo App" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:222 -msgid "does this actually require apps?" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:224 -msgid "The second step is to develop an `Odoo App`_ which clients can install in their Odoo instance and through which they can *request* the services you provide. Our app will just add a button to the Partners form which lets a user request burning some CPU time on the server." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:229 -msgid "First, we will create an *odoo module* depending on ``iap``. IAP is a standard V11 module and the dependency ensures a local account is properly set up and we will have access to some necessary views and useful helpers." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:233 -#: ../../content/developer/howtos/provide_iap_services.rst:248 -msgid "`coalroller/__manifest__.py`" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:243 -msgid "Second, the \"local\" side of the integration. Here we will only be adding an action button to the partners view, but you can of course provide significant local value via your application and additional parts via a remote service." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:261 -msgid "`coalroller/views/res_partner_views.xml`" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:286 -msgid "We can now implement the action method/callback. This will *call our own server*." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:289 -msgid "There are no requirements when it comes to the server or the communication protocol between the app and our server, but ``iap`` provides a :func:`~odoo.addons.iap.tools.iap_tools.iap_jsonrpc` helper to call a JSON-RPC2_ endpoint on an other Odoo instance and transparently re-raise relevant Odoo exceptions (:class:`~odoo.addons.iap.tools.iap_tools.InsufficientCreditError`, :class:`odoo.exceptions.AccessError` and :class:`odoo.exceptions.UserError`)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:296 -msgid "In that call, we will need to provide:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:298 -msgid "any relevant client parameter (none here)," -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:299 -msgid "the :class:`token ` of the current client that is provided by the ``iap.account`` model's ``account_token`` field. You can retrieve the account for your service by calling :samp:`env['iap.account'].get({service_name})` where :class:`service_name ` is the name of the service registered on IAP endpoint." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:305 -msgid "`coalroller/models/res_partner.py`" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:333 -msgid "``iap`` automatically handles :class:`~odoo.addons.iap.tools.iap_tools.InsufficientCreditError` coming from the action and prompts the user to add credits to their account." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:337 -msgid ":func:`~odoo.addons.iap.tools.iap_tools.iap_jsonrpc` takes care of re-raising :class:`~odoo.addons.iap.models.iap.InsufficientCreditError` for you." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:342 -msgid "If you are not using :func:`~odoo.addons.iap.tools.iap_tools.iap_jsonrpc` you *must* be careful to re-raise :class:`~odoo.addons.iap.tools.iap_tools.InsufficientCreditError` in your handler otherwise the user will not be prompted to credit their account, and the next call will fail the same way." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:351 -#: ../../content/developer/reference/frontend/javascript_reference.rst:876 -msgid "Service" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:353 -msgid "Though that is not *required*, since ``iap`` provides both a client helper for JSON-RPC2_ calls (:func:`~odoo.addons.iap.tools.iap_tools.iap_jsonrpc`) and a service helper for transactions (:class:`~odoo.addons.iap.tools.iap_tools.iap_charge`) we will also be implementing the service side as an Odoo module:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:358 -#: ../../content/developer/howtos/provide_iap_services.rst:448 -msgid "`coalroller_service/__manifest__.py`" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:368 -msgid "Since the query from the client comes as JSON-RPC2_ we will need the corresponding controller which can call :class:`~odoo.addons.iap.tools.iap_tools.iap_charge` and perform the service within:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:372 -#: ../../content/developer/howtos/provide_iap_services.rst:461 -msgid "`coalroller_service/controllers/main.py`" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:406 -msgid "for the actual IAP will the \"portal\" page be on odoo.com or iap.odoo.com?" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:408 -msgid "\"My Account\" > \"Your InApp Services\"?" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:411 -msgid "The :class:`~odoo.addons.iap.tools.iap_tools.iap_charge` helper will:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:413 -msgid "authorize (create) a transaction with the specified number of credits, if the account does not have enough credits it will raise the relevant error" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:416 -msgid "execute the body of the ``with`` statement" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:417 -msgid "if the body of the ``with`` executes successfully, update the price of the transaction if needed" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:419 -msgid "capture (confirm) the transaction" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:420 -msgid "otherwise, if an error is raised from the body of the ``with``, cancel the transaction (and release the hold on the credits)" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:425 -msgid "By default, :class:`~odoo.addons.iap.tools.iap_tools.iap_charge` contacts the *production* IAP endpoint, https://iap.odoo.com. While developing and testing your service you may want to point it towards the *development* IAP endpoint https://iap-sandbox.odoo.com." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:430 -msgid "To do so, set the ``iap.endpoint`` config parameter in your service Odoo: in debug/developer mode, :menuselection:`Setting --> Technical --> Parameters --> System Parameters`, just define an entry for the key ``iap.endpoint`` if none already exists)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:435 -msgid "The :class:`~odoo.addons.iap.tools.iap_tools.iap_charge` helper has two additional optional parameters we can use to make things clearer to the end-user." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:440 -#: ../../content/developer/reference/backend/reports.rst:198 -msgid "``description``" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:439 -msgid "is a message which will be associated with the transaction and will be displayed in the user's dashboard, it is useful to remind the user why the charge exists." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:446 -msgid "``credit_template``" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:443 -msgid "is the name of a :ref:`reference/qweb` template which will be rendered and shown to the user if their account has less credit available than the service provider is requesting, its purpose is to tell your users why they should be interested in your IAP offers." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:488 -msgid "`coalroller_service/views/no-credit.xml`" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:511 -msgid "how do you test your service?" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:514 -msgid "JSON-RPC2_ Transaction API" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:519 -msgid "The IAP transaction API does not require using Odoo when implementing your server gateway, calls are standard JSON-RPC2_." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:521 -msgid "Calls use different *endpoints* but the same *method* on all endpoints (``call``)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:523 -msgid "Exceptions are returned as JSON-RPC2_ errors, the formal exception name is available on ``data.name`` for programmatic manipulation." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:526 -msgid "`iap.odoo.com documentation`_ for additional information." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:529 -#: ../../content/developer/howtos/provide_iap_services.rst:775 -msgid "Authorize" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:533 -msgid "Verifies that the user's account has at least as ``credit`` available *and creates a hold (pending transaction) on that amount*." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:536 -msgid "Any amount currently on hold by a pending transaction is considered unavailable to further authorize calls." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:539 -msgid "Returns a :class:`TransactionToken` identifying the pending transaction which can be used to capture (confirm) or cancel said transaction (`iap.odoo.com documentation`_)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:0 -#: ../../content/developer/reference/backend/mixins.rst:0 -#: ../../content/developer/reference/frontend/framework_overview.rst:0 -#: ../../content/developer/reference/frontend/qweb.rst:0 -msgid "Parameters" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:545 -msgid "optional, helps users identify the reason for charges on their account" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:547 -msgid "optional, allows the user to benefit from trial credits if his database is eligible (see :ref:`Service registration `)" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:549 -msgid "optional, transaction time to live in hours. If the credit are not captured when the transaction expires, the transaction is cancelled. The default value is set to 4320 hours (= 180 days)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:0 -#: ../../content/developer/reference/backend/mixins.rst:0 -#: ../../content/developer/reference/frontend/assets.rst:0 -#: ../../content/developer/reference/frontend/framework_overview.rst:0 -#: ../../content/developer/reference/frontend/javascript_reference.rst:0 -#: ../../content/developer/reference/frontend/mobile.rst:0 -#: ../../content/developer/reference/frontend/qweb.rst:0 -#: ../../content/developer/reference/frontend/registries.rst:0 -#: ../../content/developer/reference/frontend/services.rst:0 -msgid "Returns" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:551 -msgid ":class:`TransactionToken` if the authorization succeeded" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:0 -msgid "raises" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:552 -msgid ":class:`~odoo.exceptions.AccessError` if the service token is invalid" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:553 -msgid ":class:`~odoo.addons.iap.models.iap.InsufficientCreditError` if the account does not have enough credits" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:554 -msgid "``TypeError`` if the ``credit`` value is not an integer or a float" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:577 -#: ../../content/developer/howtos/provide_iap_services.rst:855 -msgid "Capture" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:581 -msgid "Confirms the specified transaction, transferring the reserved credits from the user's account to the service provider's." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:584 -msgid "Capture calls are idempotent: performing capture calls on an already captured transaction has no further effect." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:589 -msgid "optional parameter to capture a smaller amount of credits than authorized" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:590 -#: ../../content/developer/howtos/provide_iap_services.rst:622 -msgid ":class:`~odoo.exceptions.AccessError`" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:610 -#: ../../content/developer/howtos/provide_iap_services.rst:817 -msgid "Cancel" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:614 -msgid "Cancels the specified transaction, releasing the hold on the user's credits." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:617 -msgid "Cancel calls are idempotent: performing capture calls on an already cancelled transaction has no further effect." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:640 -#: ../../content/developer/tutorials/getting_started/04_basicmodel.rst:134 -msgid "Types" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:642 -msgid "Exceptions aside, these are *abstract types* used for clarity, you should not care how they are implemented." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:647 -msgid "String identifying your service on https://iap.odoo.com (production) as well as the account related to your service in the client's database." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:652 -msgid "Identifier generated for the provider's service. Each key (and service) matches a token of a fixed value, as generated by the service provide." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:655 -msgid "Multiple types of tokens correspond to multiple services. As an exampe, SMS and MMS could either be the same service (with an MMS being 'worth' multiple SMS) or could be separate services at separate price points." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:659 -msgid "Your service key *is a secret*, leaking your service key allows other application developers to draw credits bought for your service(s)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:665 -msgid "Identifier for a user account." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:669 -msgid "Transaction identifier, returned by the authorization process and consumed by either capturing or cancelling the transaction." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:674 -msgid "Raised during transaction authorization if the credits requested are not currently available on the account (either not enough credits or too many pending transactions/existing holds)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:681 -msgid "Raised by:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:683 -msgid "any operation to which a service token is required, if the service token is invalid; or" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:684 -msgid "any failure in an inter-server call. (typically, in :func:`~odoo.addons.iap.tools.iap_tools.iap_jsonrpc`)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:689 -msgid "Raised by any unexpected behaviour at the discretion of the App developer (*you*)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:693 -msgid "Test the API" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:695 -msgid "In order to test the developed app, we propose a sandbox platform that allows you to:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:697 -msgid "Test the whole flow from the client's point of view - Actual services and transactions that can be consulted. (again this requires to change the endpoint, see the danger note in :ref:`Service `)." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:700 -msgid "Test the API." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:702 -msgid "The latter consists in specific tokens that will work on **IAP-Sandbox only**." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:704 -msgid "Token ``000000``: Represents a non-existing account. Returns an :class:`~odoo.addons.iap.tools.iap_tools.InsufficientCreditError` on authorize attempt." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:706 -msgid "Token ``000111``: Represents an account without sufficient credits to perform any service. Returns an :class:`~odoo.addons.iap.tools.iap_tools.InsufficientCreditError` on authorize attempt." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:708 -msgid "Token ``111111``: Represents an account with enough credits to perform any service. An authorize attempt will return a dummy transaction token that is processed by the capture and cancel routes." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:714 -msgid "Those tokens are only active on the IAP-Sanbox server." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:715 -msgid "The service key is completely ignored with this flow, If you want to run a robust test of your service, you should ignore these tokens." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:719 -msgid "Odoo Helpers" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:721 -msgid "For convenience, if you are implementing your service using Odoo the ``iap`` module provides a few helpers to make IAP flow even simpler." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:727 -msgid "Charging" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:731 -msgid "A *context manager* for authorizing and automatically capturing or cancelling transactions for use in the backend/proxy." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:734 -msgid "Works much like e.g. a cursor context manager:" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:736 -msgid "immediately authorizes a transaction with the specified parameters;" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:737 -msgid "executes the ``with`` body;" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:738 -msgid "if the body executes in full without error, captures the transaction;" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:739 -msgid "otherwise cancels it." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:741 -#: ../../content/developer/howtos/provide_iap_services.rst:781 -#: ../../content/developer/howtos/provide_iap_services.rst:823 -#: ../../content/developer/howtos/provide_iap_services.rst:861 -msgid "used to retrieve the ``iap.endpoint`` configuration key" -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:779 -msgid "Will authorize everything." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:821 -msgid "Will cancel an authorized transaction." -msgstr "" - -#: ../../content/developer/howtos/provide_iap_services.rst:859 -msgid "Will capture the amount ``credit`` on the given transaction." -msgstr "" - #: ../../content/developer/howtos/translations.rst:5 msgid "Translating Modules" msgstr "" @@ -1890,9 +1195,6 @@ msgstr "" #: ../../content/developer/howtos/website_themes/theming.rst:70 #: ../../content/developer/howtos/website_themes/theming.rst:120 #: ../../content/developer/howtos/website_themes/theming.rst:331 -#: ../../content/developer/reference/extract_api.rst:43 -#: ../../content/developer/reference/extract_api.rst:147 -#: ../../content/developer/reference/extract_api.rst:362 #: ../../content/developer/reference/frontend/assets.rst:301 #: ../../content/developer/reference/frontend/framework_overview.rst:263 #: ../../content/developer/reference/frontend/hooks.rst:43 @@ -2397,9 +1699,8 @@ msgid "Create a task." msgstr "" #: ../../content/developer/howtos/website_themes/forms.rst:75 -#: ../../content/developer/reference/extract_api.rst:121 -#: ../../content/developer/reference/extract_api.rst:201 -#: ../../content/developer/reference/extract_api.rst:484 +#: ../../content/developer/reference/extract_api.rst:183 +#: ../../content/developer/reference/extract_api.rst:284 msgid "Success" msgstr "" @@ -3778,7 +3079,7 @@ msgid ":option:`--addons-path `" msgstr "" #: ../../content/developer/howtos/website_themes/setup.rst:213 -#: ../../content/developer/reference/cli.rst:785 +#: ../../content/developer/reference/cli.rst:799 msgid "Comma-separated list of directories in which modules are stored. These directories are scanned for modules." msgstr "" @@ -4741,6 +4042,7 @@ msgstr "" #: ../../content/developer/reference/backend/views.rst:2324 #: ../../content/developer/reference/external_api.rst:866 #: ../../content/developer/reference/external_api.rst:1002 +#: ../../content/developer/reference/extract_api.rst:511 #: ../../content/developer/reference/frontend/services.rst:871 #: ../../content/developer/tutorials/web.rst:1320 msgid "``name``" @@ -5049,9 +4351,8 @@ msgstr "" #: ../../content/developer/reference/backend/data.rst:232 #: ../../content/developer/reference/backend/data.rst:242 #: ../../content/developer/reference/backend/views.rst:861 -#: ../../content/developer/reference/extract_api.rst:106 -#: ../../content/developer/reference/extract_api.rst:184 -#: ../../content/developer/reference/extract_api.rst:473 +#: ../../content/developer/reference/extract_api.rst:168 +#: ../../content/developer/reference/extract_api.rst:264 msgid "``id``" msgstr "" @@ -5770,7 +5071,7 @@ msgid "comma-separated list of group :term:`external identifiers`" msgstr "" #: ../../content/developer/reference/backend/data.rst:253 -#: ../../content/developer/reference/extract_api.rst:268 +#: ../../content/developer/reference/extract_api.rst:364 msgid "``page``" msgstr "" @@ -6084,6 +5385,8 @@ msgid "Routing" msgstr "" #: ../../content/developer/reference/backend/http.rst:64 +#: ../../content/developer/reference/extract_api.rst:74 +#: ../../content/developer/reference/extract_api.rst:220 msgid "Request" msgstr "" @@ -6092,9 +5395,8 @@ msgid "The request object is automatically set on :data:`odoo.http.request` at t msgstr "" #: ../../content/developer/reference/backend/http.rst:78 -#: ../../content/developer/reference/extract_api.rst:102 -#: ../../content/developer/reference/extract_api.rst:180 -#: ../../content/developer/reference/extract_api.rst:469 +#: ../../content/developer/reference/extract_api.rst:162 +#: ../../content/developer/reference/extract_api.rst:254 msgid "Response" msgstr "" @@ -6146,6 +5448,12 @@ msgstr "" msgid "Post a new message in an existing thread, returning the new mail.message ID." msgstr "" +#: ../../content/developer/reference/backend/mixins.rst:0 +#: ../../content/developer/reference/frontend/framework_overview.rst:0 +#: ../../content/developer/reference/frontend/qweb.rst:0 +msgid "Parameters" +msgstr "" + #: ../../content/developer/reference/backend/mixins.rst:84 msgid "body of the message, usually raw HTML that will be sanitized" msgstr "" @@ -6166,6 +5474,17 @@ msgstr "" msgid "extra keyword arguments will be used as default column values for the new mail.message record" msgstr "" +#: ../../content/developer/reference/backend/mixins.rst:0 +#: ../../content/developer/reference/frontend/assets.rst:0 +#: ../../content/developer/reference/frontend/framework_overview.rst:0 +#: ../../content/developer/reference/frontend/javascript_reference.rst:0 +#: ../../content/developer/reference/frontend/mobile.rst:0 +#: ../../content/developer/reference/frontend/qweb.rst:0 +#: ../../content/developer/reference/frontend/registries.rst:0 +#: ../../content/developer/reference/frontend/services.rst:0 +msgid "Returns" +msgstr "" + #: ../../content/developer/reference/backend/mixins.rst:93 msgid "ID of newly created mail.message" msgstr "" @@ -8702,6 +8021,7 @@ msgid "record for the current ``user``'s company" msgstr "" #: ../../content/developer/reference/backend/reports.rst:35 +#: ../../content/developer/reference/extract_api.rst:452 msgid "``website``" msgstr "" @@ -8851,6 +8171,11 @@ msgstr "" msgid "only useful as a mnemonic/description of the report when looking for one in a list of some sort" msgstr "" +#: ../../content/developer/reference/backend/reports.rst:198 +#: ../../content/developer/reference/extract_api.rst:491 +msgid "``description``" +msgstr "" + #: ../../content/developer/reference/backend/reports.rst:199 msgid "a small description of your format" msgstr "" @@ -9766,7 +9091,7 @@ msgid "when working on a failing test, it is common to add the debug flag, then msgstr "" #: ../../content/developer/reference/backend/testing.rst:534 -#: ../../content/developer/reference/extract_api.rst:504 +#: ../../content/developer/reference/extract_api.rst:523 msgid "Integration Testing" msgstr "" @@ -10717,7 +10042,7 @@ msgstr "" #: ../../content/developer/reference/backend/views.rst:612 #: ../../content/developer/reference/backend/views.rst:729 -#: ../../content/developer/reference/extract_api.rst:291 +#: ../../content/developer/reference/extract_api.rst:398 msgid "``name`` (optional)" msgstr "" @@ -12073,7 +11398,6 @@ msgstr "" #: ../../content/developer/reference/backend/views.rst:1468 #: ../../content/developer/reference/backend/views.rst:1478 -#: ../../content/developer/reference/extract_api.rst:378 msgid "``values``" msgstr "" @@ -13531,7 +12855,7 @@ msgid "Control the SSL security of the connection between Odoo and PostgreSQL. V msgstr "" #: ../../content/developer/reference/cli.rst:281 -msgid "Use the unaccent function provided by the database when available." +msgid "Try to enable the unaccent extension when creating new databases" msgstr "" #: ../../content/developer/reference/cli.rst:286 @@ -13663,455 +12987,467 @@ msgid "TCP port for long-polling connections in multiprocessing or gevent mode, msgstr "" #: ../../content/developer/reference/cli.rst:428 -msgid "enables the use of ``X-Forwarded-*`` headers through `Werkzeug's proxy support`_. Only enable this when running behind a trusted web proxy!" +msgid "enables the use of ``X-Forwarded-*`` headers through `Werkzeug's proxy support`_." msgstr "" -#: ../../content/developer/reference/cli.rst:432 +#: ../../content/developer/reference/cli.rst:431 +msgid "It ignores all ``X-Forwarded-*`` headers in case ``X-Forwarded-Host`` is missing from the request." +msgstr "" + +#: ../../content/developer/reference/cli.rst:434 +msgid "It always gets the real IP from the last entry of the ``X-Forwarded-For`` chain. Configure your web server accordingly using directives such as nginx's `set_real_ip_from `_ in case there are other trusted proxies along the chain that must be ignored." +msgstr "" + +#: ../../content/developer/reference/cli.rst:439 +msgid "``X-Forwarded-Proto`` and ``X-Forwarded-Host`` are used to update the request root URL, which in turn is used to update the ``web.base.url`` system parameter upon a successful admin authentication. This system parameter is used to generate all links for the current database; see :ref:`domain-name/web-base-url`." +msgstr "" + +#: ../../content/developer/reference/cli.rst:446 msgid "proxy mode *must not* be enabled outside of a reverse proxy scenario" msgstr "" -#: ../../content/developer/reference/cli.rst:438 +#: ../../content/developer/reference/cli.rst:452 msgid "Logging" msgstr "" -#: ../../content/developer/reference/cli.rst:440 +#: ../../content/developer/reference/cli.rst:454 msgid "By default, Odoo displays all logging of level_ ``info`` except for workflow logging (``warning`` only), and log output is sent to ``stdout``. Various options are available to redirect logging to other destinations and to customize the amount of logging output." msgstr "" -#: ../../content/developer/reference/cli.rst:447 +#: ../../content/developer/reference/cli.rst:461 msgid "sends logging output to the specified file instead of stdout. On Unix, the file `can be managed by external log rotation programs `_ and will automatically be reopened when replaced" msgstr "" -#: ../../content/developer/reference/cli.rst:454 +#: ../../content/developer/reference/cli.rst:468 msgid "logs to the system's event logger: `syslog on unices `_ and `the Event Log on Windows `_." msgstr "" -#: ../../content/developer/reference/cli.rst:457 +#: ../../content/developer/reference/cli.rst:471 msgid "Neither is configurable" msgstr "" -#: ../../content/developer/reference/cli.rst:461 +#: ../../content/developer/reference/cli.rst:475 msgid "logs to the ``ir.logging`` model (``ir_logging`` table) of the specified database. The database can be the name of a database in the \"current\" PostgreSQL, or `a PostgreSQL URI`_ for e.g. log aggregation." msgstr "" -#: ../../content/developer/reference/cli.rst:467 +#: ../../content/developer/reference/cli.rst:481 msgid ":samp:`{LOGGER}:{LEVEL}`, enables ``LOGGER`` at the provided ``LEVEL`` e.g. ``odoo.models:DEBUG`` will enable all logging messages at or above ``DEBUG`` level in the models." msgstr "" -#: ../../content/developer/reference/cli.rst:471 +#: ../../content/developer/reference/cli.rst:485 msgid "The colon ``:`` is mandatory" msgstr "" -#: ../../content/developer/reference/cli.rst:472 +#: ../../content/developer/reference/cli.rst:486 msgid "The logger can be omitted to configure the root (default) handler" msgstr "" -#: ../../content/developer/reference/cli.rst:473 +#: ../../content/developer/reference/cli.rst:487 msgid "If the level is omitted, the logger is set to ``INFO``" msgstr "" -#: ../../content/developer/reference/cli.rst:475 +#: ../../content/developer/reference/cli.rst:489 msgid "The option can be repeated to configure multiple loggers e.g." msgstr "" -#: ../../content/developer/reference/cli.rst:483 +#: ../../content/developer/reference/cli.rst:497 msgid "enable DEBUG logging for RPC requests, equivalent to ``--log-handler=odoo.http.rpc.request:DEBUG``" msgstr "" -#: ../../content/developer/reference/cli.rst:488 +#: ../../content/developer/reference/cli.rst:502 msgid "enable DEBUG logging for RPC responses, equivalent to ``--log-handler=odoo.http.rpc.response:DEBUG``" msgstr "" -#: ../../content/developer/reference/cli.rst:493 +#: ../../content/developer/reference/cli.rst:507 msgid "enables DEBUG logging of HTTP requests and responses, equivalent to ``--log-handler=odoo.http:DEBUG``" msgstr "" -#: ../../content/developer/reference/cli.rst:498 +#: ../../content/developer/reference/cli.rst:512 msgid "enables DEBUG logging of SQL querying, equivalent to ``--log-handler=odoo.sql_db:DEBUG``" msgstr "" -#: ../../content/developer/reference/cli.rst:503 +#: ../../content/developer/reference/cli.rst:517 msgid "Shortcut to more easily set predefined levels on specific loggers. \"real\" levels (``critical``, ``error``, ``warn``, ``debug``) are set on the ``odoo`` and ``werkzeug`` loggers (except for ``debug`` which is only set on ``odoo``)." msgstr "" -#: ../../content/developer/reference/cli.rst:508 +#: ../../content/developer/reference/cli.rst:522 msgid "Odoo also provides debugging pseudo-levels which apply to different sets of loggers:" msgstr "" -#: ../../content/developer/reference/cli.rst:513 +#: ../../content/developer/reference/cli.rst:527 msgid "``debug_sql``" msgstr "" -#: ../../content/developer/reference/cli.rst:512 +#: ../../content/developer/reference/cli.rst:526 msgid "sets the SQL logger to ``debug``" msgstr "" -#: ../../content/developer/reference/cli.rst:514 +#: ../../content/developer/reference/cli.rst:528 msgid "equivalent to ``--log-sql``" msgstr "" -#: ../../content/developer/reference/cli.rst:517 +#: ../../content/developer/reference/cli.rst:531 msgid "``debug_rpc``" msgstr "" -#: ../../content/developer/reference/cli.rst:516 +#: ../../content/developer/reference/cli.rst:530 msgid "sets the ``odoo`` and HTTP request loggers to ``debug``" msgstr "" -#: ../../content/developer/reference/cli.rst:518 +#: ../../content/developer/reference/cli.rst:532 msgid "equivalent to ``--log-level debug --log-request``" msgstr "" -#: ../../content/developer/reference/cli.rst:523 +#: ../../content/developer/reference/cli.rst:537 msgid "``debug_rpc_answer``" msgstr "" -#: ../../content/developer/reference/cli.rst:520 +#: ../../content/developer/reference/cli.rst:534 msgid "sets the ``odoo`` and HTTP request and response loggers to ``debug``" msgstr "" -#: ../../content/developer/reference/cli.rst:523 +#: ../../content/developer/reference/cli.rst:537 msgid "equivalent to ``--log-level debug --log-request --log-response``" msgstr "" -#: ../../content/developer/reference/cli.rst:527 +#: ../../content/developer/reference/cli.rst:541 msgid "In case of conflict between :option:`--log-level` and :option:`--log-handler`, the latter is used" msgstr "" -#: ../../content/developer/reference/cli.rst:533 +#: ../../content/developer/reference/cli.rst:547 msgid "Multiprocessing" msgstr "" -#: ../../content/developer/reference/cli.rst:537 +#: ../../content/developer/reference/cli.rst:551 msgid "if ``count`` is not 0 (the default), enables multiprocessing and sets up the specified number of HTTP workers (sub-processes processing HTTP and RPC requests)." msgstr "" -#: ../../content/developer/reference/cli.rst:541 +#: ../../content/developer/reference/cli.rst:555 msgid "multiprocessing mode is only available on Unix-based systems" msgstr "" -#: ../../content/developer/reference/cli.rst:543 +#: ../../content/developer/reference/cli.rst:557 msgid "A number of options allow limiting and recycling workers:" msgstr "" -#: ../../content/developer/reference/cli.rst:547 +#: ../../content/developer/reference/cli.rst:561 msgid "Number of requests a worker will process before being recycled and restarted." msgstr "" -#: ../../content/developer/reference/cli.rst:550 +#: ../../content/developer/reference/cli.rst:564 msgid "Defaults to *8196*." msgstr "" -#: ../../content/developer/reference/cli.rst:554 +#: ../../content/developer/reference/cli.rst:568 msgid "Maximum allowed virtual memory per worker in bytes. If the limit is exceeded, the worker is killed and recycled at the end of the current request." msgstr "" -#: ../../content/developer/reference/cli.rst:557 +#: ../../content/developer/reference/cli.rst:571 msgid "Defaults to *2048MiB (2048\\*1024\\*1024B)*." msgstr "" -#: ../../content/developer/reference/cli.rst:561 +#: ../../content/developer/reference/cli.rst:575 msgid "Hard limit on virtual memory in bytes, any worker exceeding the limit will be immediately killed without waiting for the end of the current request processing." msgstr "" -#: ../../content/developer/reference/cli.rst:565 +#: ../../content/developer/reference/cli.rst:579 msgid "Defaults to *2560MiB (2560\\*1024\\*1024B)*." msgstr "" -#: ../../content/developer/reference/cli.rst:569 +#: ../../content/developer/reference/cli.rst:583 msgid "Prevents the worker from using more than CPU seconds for each request. If the limit is exceeded, the worker is killed." msgstr "" -#: ../../content/developer/reference/cli.rst:572 +#: ../../content/developer/reference/cli.rst:586 msgid "Defaults to *60*." msgstr "" -#: ../../content/developer/reference/cli.rst:576 +#: ../../content/developer/reference/cli.rst:590 msgid "Prevents the worker from taking longer than seconds to process a request. If the limit is exceeded, the worker is killed." msgstr "" -#: ../../content/developer/reference/cli.rst:579 +#: ../../content/developer/reference/cli.rst:593 msgid "Differs from :option:`--limit-time-cpu` in that this is a \"wall time\" limit including e.g. SQL queries." msgstr "" -#: ../../content/developer/reference/cli.rst:582 +#: ../../content/developer/reference/cli.rst:596 msgid "Defaults to *120*." msgstr "" -#: ../../content/developer/reference/cli.rst:586 +#: ../../content/developer/reference/cli.rst:600 msgid "number of workers dedicated to :ref:`cron ` jobs. Defaults to *2*. The workers are threads in multi-threading mode and processes in multi-processing mode." msgstr "" -#: ../../content/developer/reference/cli.rst:589 +#: ../../content/developer/reference/cli.rst:603 msgid "For multi-processing mode, this is in addition to the HTTP worker processes." msgstr "" -#: ../../content/developer/reference/cli.rst:594 +#: ../../content/developer/reference/cli.rst:608 msgid "Configuration file" msgstr "" -#: ../../content/developer/reference/cli.rst:598 +#: ../../content/developer/reference/cli.rst:612 msgid "Most of the command-line options can also be specified via a configuration file. Most of the time, they use similar names with the prefix ``-`` removed and other ``-`` are replaced by ``_`` e.g. :option:`--db-template` becomes ``db_template``." msgstr "" -#: ../../content/developer/reference/cli.rst:603 +#: ../../content/developer/reference/cli.rst:617 msgid "Some conversions don't match the pattern:" msgstr "" -#: ../../content/developer/reference/cli.rst:605 +#: ../../content/developer/reference/cli.rst:619 msgid ":option:`--db-filter` becomes ``dbfilter``" msgstr "" -#: ../../content/developer/reference/cli.rst:606 +#: ../../content/developer/reference/cli.rst:620 msgid ":option:`--no-http` corresponds to the ``http_enable`` boolean" msgstr "" -#: ../../content/developer/reference/cli.rst:607 +#: ../../content/developer/reference/cli.rst:621 msgid "logging presets (all options starting with ``--log-`` except for :option:`--log-handler` and :option:`--log-db`) just add content to ``log_handler``, use that directly in the configuration file" msgstr "" -#: ../../content/developer/reference/cli.rst:610 +#: ../../content/developer/reference/cli.rst:624 msgid ":option:`--smtp` is stored as ``smtp_server``" msgstr "" -#: ../../content/developer/reference/cli.rst:611 +#: ../../content/developer/reference/cli.rst:625 msgid ":option:`--database` is stored as ``db_name``" msgstr "" -#: ../../content/developer/reference/cli.rst:612 +#: ../../content/developer/reference/cli.rst:626 msgid ":option:`--i18n-import` and :option:`--i18n-export` aren't available at all from configuration files" msgstr "" -#: ../../content/developer/reference/cli.rst:617 +#: ../../content/developer/reference/cli.rst:631 msgid "The default configuration file is :file:`{$HOME}/.odoorc` which can be overridden using :option:`--config `. Specifying :option:`--save ` will save the current configuration state back to that file. The configuration items relative to the command-line are to be specified in the section ``[options]``." msgstr "" -#: ../../content/developer/reference/cli.rst:623 +#: ../../content/developer/reference/cli.rst:637 msgid "Here is a sample file:" msgstr "" -#: ../../content/developer/reference/cli.rst:648 +#: ../../content/developer/reference/cli.rst:662 msgid "Shell" msgstr "" -#: ../../content/developer/reference/cli.rst:650 +#: ../../content/developer/reference/cli.rst:664 msgid "Odoo command-line also allows to launch odoo as a python console environment. This enables direct interaction with the :ref:`orm ` and its functionalities." msgstr "" -#: ../../content/developer/reference/cli.rst:660 +#: ../../content/developer/reference/cli.rst:674 msgid "Specify a preferred REPL to use in shell mode." msgstr "" -#: ../../content/developer/reference/cli.rst:666 +#: ../../content/developer/reference/cli.rst:680 msgid "Scaffolding" msgstr "" -#: ../../content/developer/reference/cli.rst:670 +#: ../../content/developer/reference/cli.rst:684 msgid "Scaffolding is the automated creation of a skeleton structure to simplify bootstrapping (of new modules, in the case of Odoo). While not necessary it avoids the tedium of setting up basic structures and looking up what all starting requirements are." msgstr "" -#: ../../content/developer/reference/cli.rst:675 +#: ../../content/developer/reference/cli.rst:689 msgid "Scaffolding is available via the :command:`odoo-bin scaffold` subcommand." msgstr "" -#: ../../content/developer/reference/cli.rst:683 +#: ../../content/developer/reference/cli.rst:697 msgid "the name of the module to create, may munged in various manners to generate programmatic names (e.g. module directory name, model names, …)" msgstr "" -#: ../../content/developer/reference/cli.rst:688 +#: ../../content/developer/reference/cli.rst:702 msgid "directory in which to create the new module, defaults to the current directory" msgstr "" -#: ../../content/developer/reference/cli.rst:693 +#: ../../content/developer/reference/cli.rst:707 msgid "a template directory, files are passed through jinja2_ then copied to the ``destination`` directory" msgstr "" -#: ../../content/developer/reference/cli.rst:697 +#: ../../content/developer/reference/cli.rst:711 msgid "This will create module *my_module* in directory */addons/*." msgstr "" -#: ../../content/developer/reference/cli.rst:702 +#: ../../content/developer/reference/cli.rst:716 msgid "Database Population" msgstr "" -#: ../../content/developer/reference/cli.rst:706 +#: ../../content/developer/reference/cli.rst:720 msgid "Odoo CLI supports database population features. If the feature is :ref:`implemented on a given model `, it allows automatic data generation of the model's records to test your modules in databases containing non-trivial amounts of records." msgstr "" -#: ../../content/developer/reference/cli.rst:717 +#: ../../content/developer/reference/cli.rst:731 msgid "list of models for which the database should be filled" msgstr "" -#: ../../content/developer/reference/cli.rst:721 +#: ../../content/developer/reference/cli.rst:735 msgid "population size, the actual records number depends on the model's `_populate_sizes` attribute. The generated records content is specified by the :meth:`~odoo.models._populate_factories` method of a given model (cf. the :file:`populate` folder of modules for further details)." msgstr "" -#: ../../content/developer/reference/cli.rst:726 +#: ../../content/developer/reference/cli.rst:740 msgid ":ref:`reference/performance/populate`" msgstr "" -#: ../../content/developer/reference/cli.rst:731 +#: ../../content/developer/reference/cli.rst:745 msgid "Cloc" msgstr "" -#: ../../content/developer/reference/cli.rst:735 +#: ../../content/developer/reference/cli.rst:749 msgid "Odoo Cloc is a tool to count the number of relevant lines written in Python, Javascript, CSS, SCSS, or XML. This can be used as a rough metric for pricing maintenance of extra modules." msgstr "" -#: ../../content/developer/reference/cli.rst:740 +#: ../../content/developer/reference/cli.rst:754 msgid "Command-line options" msgstr "" -#: ../../content/developer/reference/cli.rst:745 +#: ../../content/developer/reference/cli.rst:759 msgid "Process the code of all extra modules installed on the provided database, and of all server actions and computed fields manually created in the provided database." msgstr "" -#: ../../content/developer/reference/cli.rst:747 +#: ../../content/developer/reference/cli.rst:761 msgid "The :option:`--addons-path` option is required to specify the path(s) to the module folder(s)." msgstr "" -#: ../../content/developer/reference/cli.rst:750 +#: ../../content/developer/reference/cli.rst:764 msgid "If combined with :option:`--path`, the count will be that of the sum of both options' results (with possible overlaps). At least one of these two options is required to specify which code to process." msgstr "" -#: ../../content/developer/reference/cli.rst:757 +#: ../../content/developer/reference/cli.rst:771 msgid ":ref:`reference/cmdline/cloc/database-option`" msgstr "" -#: ../../content/developer/reference/cli.rst:762 +#: ../../content/developer/reference/cli.rst:776 msgid "Process the files in the provided path." msgstr "" -#: ../../content/developer/reference/cli.rst:765 +#: ../../content/developer/reference/cli.rst:779 msgid "If combined with :option:`--database`, the count will be that of the sum of both options' results (with possible overlaps). At least one of these two options is required to specify which code to process." msgstr "" -#: ../../content/developer/reference/cli.rst:772 +#: ../../content/developer/reference/cli.rst:786 msgid "Multiple paths can be provided by repeating the option." msgstr "" -#: ../../content/developer/reference/cli.rst:779 +#: ../../content/developer/reference/cli.rst:793 msgid ":ref:`reference/cmdline/cloc/path-option`" msgstr "" -#: ../../content/developer/reference/cli.rst:786 +#: ../../content/developer/reference/cli.rst:800 msgid "Required if the :option:`--database` option is used." msgstr "" -#: ../../content/developer/reference/cli.rst:791 +#: ../../content/developer/reference/cli.rst:805 msgid "Specify a configuration file to use in place of the :option:`--addons-path` option." msgstr "" -#: ../../content/developer/reference/cli.rst:800 +#: ../../content/developer/reference/cli.rst:814 msgid "Show the details of lines counted for each file." msgstr "" -#: ../../content/developer/reference/cli.rst:804 +#: ../../content/developer/reference/cli.rst:818 msgid "Processed files" msgstr "" -#: ../../content/developer/reference/cli.rst:809 +#: ../../content/developer/reference/cli.rst:823 msgid "With the :option:`--database` option" msgstr "" -#: ../../content/developer/reference/cli.rst:811 +#: ../../content/developer/reference/cli.rst:825 msgid "Odoo Cloc counts the lines in each file of extra installed modules in a given database. In addition, it counts the Python lines of server actions and custom computed fields that have been directly created in the database or imported. Finally, it counts the lines of code of Javascript, CSS, and SCSS files, and of QWeb views from imported modules." msgstr "" -#: ../../content/developer/reference/cli.rst:817 +#: ../../content/developer/reference/cli.rst:831 msgid "Some files are excluded from the count by default:" msgstr "" -#: ../../content/developer/reference/cli.rst:819 +#: ../../content/developer/reference/cli.rst:833 msgid "The manifest (:file:`__manifest__.py` or :file:`__openerp__.py`)" msgstr "" -#: ../../content/developer/reference/cli.rst:820 +#: ../../content/developer/reference/cli.rst:834 msgid "The contents of the folder :file:`static/lib`" msgstr "" -#: ../../content/developer/reference/cli.rst:821 +#: ../../content/developer/reference/cli.rst:835 msgid "The tests defined in the folder :file:`tests` and :file:`static/tests`" msgstr "" -#: ../../content/developer/reference/cli.rst:822 +#: ../../content/developer/reference/cli.rst:836 msgid "The migrations scripts defined in the folder :file:`migrations` and `upgrades`" msgstr "" -#: ../../content/developer/reference/cli.rst:823 +#: ../../content/developer/reference/cli.rst:837 msgid "The XML files declared in the ``demo`` or ``demo_xml`` sections of the manifest" msgstr "" -#: ../../content/developer/reference/cli.rst:825 +#: ../../content/developer/reference/cli.rst:839 msgid "For special cases, a list of files that should be ignored by Odoo Cloc can be defined per module. This is specified by the ``cloc_exclude`` entry of the manifest:" msgstr "" -#: ../../content/developer/reference/cli.rst:838 +#: ../../content/developer/reference/cli.rst:852 msgid "The pattern ``**/*`` can be used to ignore an entire module. This can be useful to exclude a module from maintenance service costs." msgstr "" -#: ../../content/developer/reference/cli.rst:840 +#: ../../content/developer/reference/cli.rst:854 msgid "For more information about the pattern syntax, see `glob `_." msgstr "" -#: ../../content/developer/reference/cli.rst:845 +#: ../../content/developer/reference/cli.rst:859 msgid "With the :option:`--path` option" msgstr "" -#: ../../content/developer/reference/cli.rst:847 +#: ../../content/developer/reference/cli.rst:861 msgid "This method works the same as with the :ref:`--database option ` if a manifest file is present in the given folder. Otherwise, it counts all files." msgstr "" -#: ../../content/developer/reference/cli.rst:853 +#: ../../content/developer/reference/cli.rst:867 msgid "Identifying Extra Modules" msgstr "" -#: ../../content/developer/reference/cli.rst:855 +#: ../../content/developer/reference/cli.rst:869 msgid "To distinguish between standard and extra modules, Odoo Cloc uses the following heuristic: modules that are located (real file system path, after following symbolic links) in the same parent directory as the ``base``, ``web`` or ``web_enterprise`` standard modules are considered standard. Other modules are treated as extra modules." msgstr "" -#: ../../content/developer/reference/cli.rst:862 +#: ../../content/developer/reference/cli.rst:876 #: ../../content/developer/reference/frontend/services.rst:662 msgid "Error Handling" msgstr "" -#: ../../content/developer/reference/cli.rst:864 +#: ../../content/developer/reference/cli.rst:878 msgid "Some file cannot be counted by Odoo Cloc. Those file are reported at the end of the output." msgstr "" -#: ../../content/developer/reference/cli.rst:868 +#: ../../content/developer/reference/cli.rst:882 msgid "Max file size exceeded" msgstr "" -#: ../../content/developer/reference/cli.rst:870 +#: ../../content/developer/reference/cli.rst:884 msgid "Odoo Cloc rejects any file larger than 25MB. Usually, source files are smaller than 1 MB. If a file is rejected, it may be:" msgstr "" -#: ../../content/developer/reference/cli.rst:873 +#: ../../content/developer/reference/cli.rst:887 msgid "A generated XML file that contains lots of data. It should be excluded in the manifest." msgstr "" -#: ../../content/developer/reference/cli.rst:874 +#: ../../content/developer/reference/cli.rst:888 msgid "A JavaScript library that should be placed in the :file:`static/lib` folder." msgstr "" -#: ../../content/developer/reference/cli.rst:877 +#: ../../content/developer/reference/cli.rst:891 msgid "Syntax Error" msgstr "" -#: ../../content/developer/reference/cli.rst:879 +#: ../../content/developer/reference/cli.rst:893 msgid "Odoo Cloc cannot count the lines of code of a Python file with a syntax problem. If an extra module contains such files, they should be fixed to allow the module to load. If the module works despite the presence of those files, they are probably not loaded and should therefore be removed from the module, or at least excluded in the manifest via ``cloc_exclude``." msgstr "" -#: ../../content/developer/reference/cli.rst:886 +#: ../../content/developer/reference/cli.rst:900 msgid "TSConfig Generator" msgstr "" -#: ../../content/developer/reference/cli.rst:890 +#: ../../content/developer/reference/cli.rst:904 msgid "When working on javascript, there are ways to help your editor providing you with powerful auto-completion. One of those ways is the use of a tsconfig.json file. Originally meant for typescript, editors can use its information with plain javascript also. With this config file, you will now have full auto-completion across modules." msgstr "" -#: ../../content/developer/reference/cli.rst:895 +#: ../../content/developer/reference/cli.rst:909 msgid "The command to generate this files takes as many unnamed arguments as you need. Those are relative paths to your addon directories. In the example below, we move up one folder to save the tsconfig file in the folder containing community and enterprise." msgstr "" @@ -14577,650 +13913,772 @@ msgstr "" msgid "Computed fields can not be added via ``ir.model.fields``, some field meta-information (defaults, onchange) can not be set either." msgstr "" -#: ../../content/developer/reference/extract_api.rst:5 +#: ../../content/developer/reference/extract_api.rst:3 msgid "Extract API" msgstr "" -#: ../../content/developer/reference/extract_api.rst:7 -msgid "Odoo provides a service allowing you to automate the processing of your invoices. The service scans your document using an Optical Character Recognition (OCR) engine and then uses AI-based algorithms to extract the fields of interest such as the total, the due date, or the invoice lines. More functional information can be found on the `demo page `_." +#: ../../content/developer/reference/extract_api.rst:5 +msgid "Odoo provides a service to automate the processing of documents of type **invoices**, **expenses** or **resumes**." msgstr "" -#: ../../content/developer/reference/extract_api.rst:11 -msgid "This service is a paid service. Each invoice processing will cost you one credit. Three different sized packs can be bought on `iap.odoo.com `_." +#: ../../content/developer/reference/extract_api.rst:8 +msgid "The service scans documents using an :abbr:`OCR (Optical Character Recognition)` engine and then uses :abbr:`AI(Artificial Intelligence)`-based algorithms to extract fields of interest such as the total, due date, or invoice lines for *invoices*, the total, date for *expenses*, or the name, email, phone number for *resumes*." msgstr "" #: ../../content/developer/reference/extract_api.rst:13 -msgid "You can either use this service directly in the Odoo Accounting App or through the API. The Extract API which is detailed in the next section allows you to integrate our service directly into your own projects." +msgid "This service is a paid service. Each document processing will cost you one credit. Credits can be bought on `iap.odoo.com `_." msgstr "" -#: ../../content/developer/reference/extract_api.rst:17 -msgid "Invoices" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:19 -msgid "The extract API use the JSON-RPC2_ protocol. The diffent routes are located at the following address: **https://iap-extract.odoo.com**." +#: ../../content/developer/reference/extract_api.rst:16 +msgid "You can either use this service directly in the Accounting, Expense, or Recruitment App or through the API. The Extract API, which is detailed in the next section, allows you to integrate our service directly into your own projects." msgstr "" #: ../../content/developer/reference/extract_api.rst:22 -msgid "Expected successful flow" +#: ../../content/developer/reference/frontend/javascript_reference.rst:17 +#: ../../content/developer/reference/frontend/services.rst:144 +#: ../../content/developer/reference/frontend/services.rst:182 +#: ../../content/developer/reference/frontend/services.rst:362 +#: ../../content/developer/reference/frontend/services.rst:408 +#: ../../content/developer/reference/frontend/services.rst:522 +#: ../../content/developer/reference/frontend/services.rst:612 +#: ../../content/developer/reference/frontend/services.rst:708 +#: ../../content/developer/reference/frontend/services.rst:759 +#: ../../content/developer/reference/frontend/services.rst:834 +msgid "Overview" msgstr "" #: ../../content/developer/reference/extract_api.rst:24 -msgid "Call :ref:`webservices/extract_api/invoice_parse` to submit your invoices (one call for each invoice). On success, you receive a `document_id` in the response." +msgid "The extract API uses the JSON-RPC2_ protocol; its endpoint routes are located at `https://extract.api.odoo.com`." msgstr "" -#: ../../content/developer/reference/extract_api.rst:25 -msgid "You then have to regularly poll :ref:`webservices/extract_api/invoice_get_results` to get the document's parsing status." +#: ../../content/developer/reference/extract_api.rst:30 +msgid "Version" msgstr "" -#: ../../content/developer/reference/extract_api.rst:26 -msgid "Once the result received, you can validate it by calling :ref:`webservices/extract_api/invoice_validate` and sending the expected values. This step is optional but greatly helps the system to improve." +#: ../../content/developer/reference/extract_api.rst:32 +msgid "The version of the Extract API is specified in the route." msgstr "" -#: ../../content/developer/reference/extract_api.rst:29 -msgid "These 3 routes are detailed in this :ref:`section `. The HTTP POST method should be used for all of them. A python implementation of the full flow can be found :download:`here ` and a token for integration testing is provided in the :ref:`integration testing section `." +#: ../../content/developer/reference/extract_api.rst:37 +msgid "The latest versions are:" msgstr "" #: ../../content/developer/reference/extract_api.rst:35 -msgid "Routes" +msgid "invoices: 122" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:36 +msgid "expenses: 132" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:37 +msgid "applicant: 102" msgstr "" #: ../../content/developer/reference/extract_api.rst:40 -msgid "``/iap/invoice_extract/parse``" +msgid "Flow" msgstr "" -#: ../../content/developer/reference/extract_api.rst:45 -msgid "Request a processing of the document from the OCR. The route will return a `document_id` you can use to obtain the result of your request." +#: ../../content/developer/reference/extract_api.rst:42 +msgid "The flow is the same for each document type." msgstr "" -#: ../../content/developer/reference/extract_api.rst:48 -#: ../../content/developer/reference/extract_api.rst:152 -#: ../../content/developer/reference/extract_api.rst:368 -msgid "Request Body" +#: ../../content/developer/reference/extract_api.rst:0 +msgid "Call :ref:`/parse ` to submit your documents (one call for each document). On success, you receive a `document_token` in the response." msgstr "" -#: ../../content/developer/reference/extract_api.rst:50 -#: ../../content/developer/reference/extract_api.rst:154 -#: ../../content/developer/reference/extract_api.rst:370 -msgid "``jsonrpc`` (required)" +#: ../../content/developer/reference/extract_api.rst:0 +msgid "You then have to regularly poll :ref:`/get_result ` to get the document's parsing status." msgstr "" -#: ../../content/developer/reference/extract_api.rst:51 -msgid "Must be exactly “2.0”." +#: ../../content/developer/reference/extract_api.rst:0 +msgid "Alternatively, you can provide a `webhook_url` at the time of the call to :ref:`/parse ` and you will be notified (via a POST request) when the result is ready." msgstr "" #: ../../content/developer/reference/extract_api.rst:52 -#: ../../content/developer/reference/extract_api.rst:156 -#: ../../content/developer/reference/extract_api.rst:372 -msgid "``method`` (required)" +msgid "The HTTP POST method should be used for all of them. A python implementation of the full flow for invoices can be found :download:`here ` and a token for integration testing is provided in the :ref:`integration testing section `." msgstr "" -#: ../../content/developer/reference/extract_api.rst:53 -msgid "Must be “call”." +#: ../../content/developer/reference/extract_api.rst:59 +msgid "Parse" msgstr "" -#: ../../content/developer/reference/extract_api.rst:54 -#: ../../content/developer/reference/extract_api.rst:158 -msgid "``id`` (required)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:55 -msgid "An identifier established by the client. It allows the client to keep track of which response goes with which request. This makes asynchronous calls easier." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:78 -#: ../../content/developer/reference/extract_api.rst:378 -msgid "``params``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:57 -msgid "``account_token`` (required)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:58 -msgid "The token of the account from which credits will be taken. Each successful call costs one token." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:60 -msgid "``version`` (optional)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:60 -msgid "The version will determine the format of your requests and the format of the server response. Some results can be unavailable in older versions. For the current version 1.2.0, send ‘120’. If not specified, the latest version will be used." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:64 -msgid "``documents`` (required)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:63 -msgid "The invoice must be provided as a string in the ASCII encoding. The list should contain only one string. If multiple strings are provided only the first string corresponding to a pdf will be processed. If no pdf is found, the first string will be processed. This field is a list only for legacy reasons. The supported extensions are *pdf*, *png*, *jpg* and *bmp*." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:78 -msgid "``user_infos`` (required)" +#: ../../content/developer/reference/extract_api.rst:61 +msgid "Request the processing of a document from the OCR. The route will return a `document_token`, you can use it to obtain the result of your request." msgstr "" #: ../../content/developer/reference/extract_api.rst:67 -msgid "Information concerning the person to whom the invoice is intended. This information is not required in order for the service to work but it greatly improves the quality of the result." +#: ../../content/developer/reference/extract_api.rst:213 +msgid "Routes" msgstr "" #: ../../content/developer/reference/extract_api.rst:69 -msgid "``user_company_vat`` (optional)" +msgid "/api/extract/invoice/2/parse" msgstr "" #: ../../content/developer/reference/extract_api.rst:70 -msgid "VAT number of the client." +msgid "/api/extract/expense/2/parse" msgstr "" #: ../../content/developer/reference/extract_api.rst:71 -msgid "``user_company_name`` (optional)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:72 -msgid "Name of the client’s company." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:73 -msgid "``user_company_country_code`` (optional)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:74 -msgid "Country code of the client. Format: `ISO3166 alpha-2 `_." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:75 -msgid "``user_lang`` (optional)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:76 -msgid "The client language. Format: *language_code + _ + locale* (ex: fr_FR, en_US)." +msgid "/api/extract/applicant/2/parse" msgstr "" #: ../../content/developer/reference/extract_api.rst:78 -msgid "``user_email`` (optional)" +#: ../../content/developer/reference/extract_api.rst:224 +msgid "``jsonrpc`` (required)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:78 -msgid "The client email." +#: ../../content/developer/reference/extract_api.rst:79 +#: ../../content/developer/reference/extract_api.rst:81 +#: ../../content/developer/reference/extract_api.rst:83 +#: ../../content/developer/reference/extract_api.rst:167 +#: ../../content/developer/reference/extract_api.rst:169 +#: ../../content/developer/reference/extract_api.rst:225 +#: ../../content/developer/reference/extract_api.rst:227 +#: ../../content/developer/reference/extract_api.rst:229 +#: ../../content/developer/reference/extract_api.rst:263 +#: ../../content/developer/reference/extract_api.rst:265 +msgid "see JSON-RPC2_" msgstr "" -#: ../../content/developer/reference/extract_api.rst:104 -#: ../../content/developer/reference/extract_api.rst:182 -#: ../../content/developer/reference/extract_api.rst:471 -msgid "``jsonrpc``" +#: ../../content/developer/reference/extract_api.rst:80 +#: ../../content/developer/reference/extract_api.rst:226 +msgid "``method`` (required)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:105 -msgid "A string specifying the version of the JSON-RPC protocol. It will be “2.0”." +#: ../../content/developer/reference/extract_api.rst:82 +#: ../../content/developer/reference/extract_api.rst:228 +msgid "``id`` (required)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:107 -msgid "The identifier you set in the request body." +#: ../../content/developer/reference/extract_api.rst:131 +#: ../../content/developer/reference/extract_api.rst:238 +msgid "``params``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:114 -#: ../../content/developer/reference/extract_api.rst:194 -#: ../../content/developer/reference/extract_api.rst:479 -msgid "``result``" +#: ../../content/developer/reference/extract_api.rst:88 +#: ../../content/developer/reference/extract_api.rst:238 +msgid "``account_token`` (required)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:109 -#: ../../content/developer/reference/extract_api.rst:189 -#: ../../content/developer/reference/extract_api.rst:476 -msgid "``status_code``" +#: ../../content/developer/reference/extract_api.rst:88 +msgid "The token of the account from which credits will be taken. Each successful call costs one token." msgstr "" -#: ../../content/developer/reference/extract_api.rst:110 -#: ../../content/developer/reference/extract_api.rst:190 -#: ../../content/developer/reference/extract_api.rst:477 -msgid "|STATUS_CODE|" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:111 -#: ../../content/developer/reference/extract_api.rst:191 -#: ../../content/developer/reference/extract_api.rst:479 -msgid "``status_msg``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:112 -#: ../../content/developer/reference/extract_api.rst:192 -#: ../../content/developer/reference/extract_api.rst:479 -msgid "|STATUS_MSG|" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:114 -msgid "``document_id``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:114 -#: ../../content/developer/reference/extract_api.rst:194 -msgid "Only present if the request is successful." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:116 -msgid "The API does not actually use the JSON-RPC error scheme. Instead the API has its own error scheme bundled inside a successful JSON-RPC result." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:119 -#: ../../content/developer/reference/extract_api.rst:199 -#: ../../content/developer/reference/extract_api.rst:482 -msgid "status_code" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:119 -#: ../../content/developer/reference/extract_api.rst:199 -#: ../../content/developer/reference/extract_api.rst:482 -msgid "status_msg" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:121 -#: ../../content/developer/reference/extract_api.rst:201 -#: ../../content/developer/reference/extract_api.rst:484 -msgid "0" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:122 -#: ../../content/developer/reference/extract_api.rst:203 -msgid "2" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:122 -#: ../../content/developer/reference/extract_api.rst:203 -msgid "An error occurred" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:123 -msgid "3" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:123 -msgid "You don't have enough credit" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:124 -#: ../../content/developer/tutorials/define_module_data.rst:183 -msgid "6" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:124 -msgid "Unsupported file format" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:125 -#: ../../content/developer/reference/extract_api.rst:204 -msgid "9" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:125 -#: ../../content/developer/reference/extract_api.rst:204 -msgid "Server is currently under maintenance. Please try again later." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:144 -msgid "``/iap/invoice_extract/get_results``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:149 -msgid "Request the results of the documents ids obtained with the :ref:`/parse ` route. Can either return the results or a \"request pending\" message." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:155 -#: ../../content/developer/reference/extract_api.rst:157 -#: ../../content/developer/reference/extract_api.rst:159 -#: ../../content/developer/reference/extract_api.rst:162 -#: ../../content/developer/reference/extract_api.rst:183 -#: ../../content/developer/reference/extract_api.rst:185 -#: ../../content/developer/reference/extract_api.rst:371 -#: ../../content/developer/reference/extract_api.rst:373 -#: ../../content/developer/reference/extract_api.rst:472 -#: ../../content/developer/reference/extract_api.rst:474 -msgid "|SAME_AS_PARSE|" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:164 -msgid "``params``:" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:161 +#: ../../content/developer/reference/extract_api.rst:91 +#: ../../content/developer/reference/extract_api.rst:233 msgid "``version`` (required)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:164 -msgid "``documents_ids`` (required)" +#: ../../content/developer/reference/extract_api.rst:91 +msgid "The version will determine the format of your requests and the format of the server response. You should use the :ref:`latest version available `." msgstr "" -#: ../../content/developer/reference/extract_api.rst:164 -msgid "The list of ``document_id`` for which you want to get the current parsing status." +#: ../../content/developer/reference/extract_api.rst:97 +msgid "``documents`` (required)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:94 +msgid "The document must be provided as a string in the ASCII encoding. The list should contain only one string. If multiple strings are provided only the first string corresponding to a pdf will be processed. If no pdf is found, the first string will be processed. This field is a list only for legacy reasons. The supported extensions are *pdf*, *png*, *jpg* and *bmp*." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:99 +msgid "``dbuuid`` (optional)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:100 +msgid "Unique identifier of the Odoo database." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:102 +msgid "``webhook_url`` (optional)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:102 +msgid "A webhook URL can be provided. An empty POST request will be sent to ``webhook_url/document_token`` when the result is ready." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:131 +msgid "``user_infos`` (optional)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:105 +msgid "Information concerning the person sending the document to the extract service. It can be the client or the supplier (depending on the ``perspective``). This information is not required in order for the service to work but it greatly improves the quality of the result." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:111 +msgid "``user_company_vat`` (optional)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:112 +msgid "VAT number of the user." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:113 +msgid "``user_company_name`` (optional)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:114 +msgid "Name of the user’s company." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:116 +msgid "``user_company_country_code`` (optional)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:116 +msgid "Country code of the user. Format: `ISO3166 alpha-2 `_." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:118 +msgid "``user_lang`` (optional)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:119 +msgid "The user language. Format: *language_code + _ + locale* (e.g. fr_FR, en_US)." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:120 +msgid "``user_email`` (optional)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:121 +msgid "The user email." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:122 +msgid "``purchase_order_regex`` (optional)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:123 +msgid "Regex for purchase order identification. Will default to Odoo PO format if not provided." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:131 +msgid "``perspective`` (optional)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:127 +msgid "Can be ``client`` or ``supplier``. This field is useful for invoices only. ``client`` means that the user information provided are related to the client of the invoice. ``supplier`` means that it's related to the supplier. If not provided, client will be used." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:158 +msgid "The ``user_infos`` parameter is optional but it greatly improves the quality of the result, especially for invoices. The more information you can provide, the better." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:166 +#: ../../content/developer/reference/extract_api.rst:262 +msgid "``jsonrpc``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:178 +#: ../../content/developer/reference/extract_api.rst:279 +msgid "``result``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:173 +#: ../../content/developer/reference/extract_api.rst:269 +msgid "``status``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:174 +#: ../../content/developer/reference/extract_api.rst:270 +msgid "The code indicating the status of the request. See the table below." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:175 +#: ../../content/developer/reference/extract_api.rst:271 +msgid "``status_msg``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:176 +#: ../../content/developer/reference/extract_api.rst:272 +msgid "A string giving verbose details about the request status." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:178 +msgid "``document_token``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:178 +#: ../../content/developer/reference/extract_api.rst:274 +msgid "Only present if the request is successful." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:181 +#: ../../content/developer/reference/extract_api.rst:282 +#: ../../content/developer/tutorials/getting_started/08_relations.rst:244 +msgid "status" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:181 +#: ../../content/developer/reference/extract_api.rst:282 +msgid "status_msg" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:183 +#: ../../content/developer/reference/extract_api.rst:284 +msgid "`success`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:184 +#: ../../content/developer/reference/extract_api.rst:285 +msgid "`error_unsupported_version`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:184 +#: ../../content/developer/reference/extract_api.rst:285 +msgid "Unsupported version" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:185 +#: ../../content/developer/reference/extract_api.rst:286 +msgid "`error_internal`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:185 +#: ../../content/developer/reference/extract_api.rst:286 +msgid "An error occurred" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:186 +msgid "`error_no_credit`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:186 +msgid "You don't have enough credit" msgstr "" #: ../../content/developer/reference/extract_api.rst:187 -msgid "Dictionary where each key is a document_id. For each ``document_id``:" +msgid "`error_unsupported_format`" msgstr "" -#: ../../content/developer/reference/extract_api.rst:194 +#: ../../content/developer/reference/extract_api.rst:187 +msgid "Unsupported file format" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:188 +#: ../../content/developer/reference/extract_api.rst:287 +msgid "`error_maintenance`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:188 +#: ../../content/developer/reference/extract_api.rst:287 +msgid "Server is currently under maintenance, please try again later" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:204 +msgid "The API does not actually use the JSON-RPC error scheme. Instead the API has its own error scheme bundled inside a successful JSON-RPC result." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:208 +msgid "Get results" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:215 +msgid "/api/extract/invoice/2/get_result" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:216 +msgid "/api/extract/expense/2/get_result" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:217 +msgid "/api/extract/applicant/2/get_result" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:234 +msgid "The version should match the version passed to the :ref:`/parse ` request." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:235 +msgid "``document_token`` (required)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:236 +msgid "The ``document_token`` for which you want to get the current parsing status." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:238 +msgid "The token of the account that was used to submit the document." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:256 +msgid "When getting the results from the parse, the detected field vary a lot depending on the type of document. Each response is a list of dictionaries, one for each document. The keys of the dictionary are the name of the field and the value is the value of the field." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:279 msgid "``results``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:196 -msgid "result keys are strings despite the fact that the document_ids given in the request body are integers." +#: ../../content/developer/reference/extract_api.rst:279 +msgid "``full_text_annotation``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:202 -#: ../../content/developer/tutorials/define_module_data.rst:183 -msgid "1" +#: ../../content/developer/reference/extract_api.rst:279 +msgid "Contains the unprocessed full result from the OCR for the document" msgstr "" -#: ../../content/developer/reference/extract_api.rst:202 -msgid "Not ready" +#: ../../content/developer/reference/extract_api.rst:288 +msgid "`error_document_not_found`" msgstr "" -#: ../../content/developer/reference/extract_api.rst:237 -msgid "``feature_result``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:239 -msgid "Each field of interest we want to extract from the invoice such as the total or the due date are also called features. An exhaustive list of all the extracted features can be found in the table below." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:241 -msgid "For each feature, we return a list of candidates and we spotlight the candidate our model predicts to be the best fit for the feature." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:243 -msgid "``selected_value``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:244 -msgid "The best candidate for this feature." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:246 -msgid "``words``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:246 -msgid "List of all the candidates for this feature ordered by decreasing score." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:258 -msgid "``candidate``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:260 -msgid "For each candidate we give its representation and position in the document. Candidates are sorted by decreasing order of suitability." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:262 -msgid "``content``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:263 -msgid "Representation of the candidate." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:265 -msgid "``coords``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:265 -msgid "``[center_x, center_y, width, height, rotation_angle]``. The position and dimensions are relative to the size of the page and are therefore between 0 and 1. The angle is a clockwise rotation measured in degrees." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:268 -msgid "Page of the original document on which the candidate is located (starts at 0)." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:280 -msgid "Feature name" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:280 -msgid "Specifities" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:282 -msgid "``SWIFT_code``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:282 -msgid "**content** is a dictionary encoded as a string." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:284 -msgid "It contains information about the detected SWIFT code (or `BIC `_)." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:287 -msgid "Keys:" +#: ../../content/developer/reference/extract_api.rst:288 +msgid "The document could not be found" msgstr "" #: ../../content/developer/reference/extract_api.rst:289 -msgid "``bic``" +msgid "`error_unsupported_size`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:289 +msgid "The document has been rejected because it is too small" msgstr "" #: ../../content/developer/reference/extract_api.rst:290 -msgid "detected BIC (string)." +msgid "`error_no_page_count`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:290 +msgid "Unable to get page count of the PDF file" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:291 +msgid "`error_pdf_conversion_to_images`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:291 +msgid "Couldn't convert the PDF to images" msgstr "" #: ../../content/developer/reference/extract_api.rst:292 -msgid "bank name (string)." +msgid "`error_password_protected`" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:292 +msgid "The PDF file is protected by a password" msgstr "" #: ../../content/developer/reference/extract_api.rst:293 -msgid "``country_code``" +msgid "`error_too_many_pages`" msgstr "" -#: ../../content/developer/reference/extract_api.rst:294 -msgid "ISO3166 alpha-2 country code of the bank (string)." +#: ../../content/developer/reference/extract_api.rst:293 +msgid "The document contains too many pages" msgstr "" -#: ../../content/developer/reference/extract_api.rst:295 -msgid "``city`` (optional)" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:296 -msgid "city of the bank (string)." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:298 -msgid "``verified_bic``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:298 -msgid "True if the BIC has been found in our DB (bool)." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:300 -msgid "Name and city are present only if verified_bic is true." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:302 -msgid "``VAT_Number``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:302 -#: ../../content/developer/reference/extract_api.rst:304 -#: ../../content/developer/reference/extract_api.rst:306 -#: ../../content/developer/reference/extract_api.rst:308 -#: ../../content/developer/reference/extract_api.rst:322 -#: ../../content/developer/reference/extract_api.rst:328 -msgid "**content** is a string" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:304 -msgid "``country``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:306 -msgid "``currency``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:308 -msgid "``date``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:310 -msgid "Format : *YYYY-MM-DD HH:MM:SS*" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:312 -msgid "``due_date``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:312 -msgid "Same as for ``date``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:314 -msgid "``global_taxes``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:314 -#: ../../content/developer/reference/extract_api.rst:320 -#: ../../content/developer/reference/extract_api.rst:324 -#: ../../content/developer/reference/extract_api.rst:326 -msgid "**content** is a float" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:316 -msgid "**candidate** has an additional field ``amount_type``. Its value is always percent." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:318 -msgid "**selected_values** is a list of candidates." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:320 -msgid "``global_taxes_amount``" +#: ../../content/developer/reference/extract_api.rst:317 +msgid "Common fields" msgstr "" #: ../../content/developer/reference/extract_api.rst:322 -msgid "``invoice_id``" +msgid "``feature_result``" msgstr "" #: ../../content/developer/reference/extract_api.rst:324 -msgid "``subtotal``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:326 -msgid "``total``" +msgid "Each field of interest we want to extract from the document such as the total or the due date are also called **features**. An exhaustive list of all the extracted features associated to a type of document can be found in the sections below." msgstr "" #: ../../content/developer/reference/extract_api.rst:328 -msgid "``supplier``" +msgid "For each feature, we return a list of candidates and we spotlight the candidate our model predicts to be the best fit for the feature." msgstr "" -#: ../../content/developer/reference/extract_api.rst:332 -msgid "``feature_result`` for the ``invoice_lines`` feature" +#: ../../content/developer/reference/extract_api.rst:333 +msgid "``selected_value`` (optional)" msgstr "" #: ../../content/developer/reference/extract_api.rst:334 -msgid "It follows a more specific structure. It is basically a list of dictionaries where each dictionary represents an invoice line. Each value follows a :ref:`webservices/extract_api/invoice_get_results/feature_result` structure." +msgid "The best candidate for this feature." msgstr "" -#: ../../content/developer/reference/extract_api.rst:359 -msgid "``/iap/invoice_extract/validate``" +#: ../../content/developer/reference/extract_api.rst:335 +msgid "``selected_values`` (optional)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:336 +msgid "The best candidates for this feature." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:338 +msgid "``candidates`` (optional)" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:338 +msgid "List of all the candidates for this feature ordered by decreasing confidence score." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:348 +msgid "candidate" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:350 +msgid "For each candidate we give its representation and position in the document. Candidates are sorted by decreasing order of suitability." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:355 +msgid "``content``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:356 +msgid "Representation of the candidate." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:361 +msgid "``coords``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:360 +msgid "``[center_x, center_y, width, height, rotation_angle]``. The position and dimensions are relative to the size of the page and are therefore between 0 and 1. The angle is a clockwise rotation measured in degrees." msgstr "" #: ../../content/developer/reference/extract_api.rst:364 -msgid "Route that validates the different features of an invoice. The validation step is an optional step but is strongly recommended. By telling the system if it were right or wrong for each feature you give an important feedback. It has no direct impact but it helps the system to greatly improve its prediction accuracy for the invoices you will send in the future." +msgid "Page of the original document on which the candidate is located (starts at 0)." msgstr "" -#: ../../content/developer/reference/extract_api.rst:375 -msgid "``documents_id`` (required)" +#: ../../content/developer/reference/extract_api.rst:379 +msgid "Invoices" msgstr "" -#: ../../content/developer/reference/extract_api.rst:376 -msgid "Id of the document for which you want to validate the result." +#: ../../content/developer/reference/extract_api.rst:381 +msgid "Invoices are complex and can have a lot of different fields. The following table gives an exhaustive list of all the fields we can extract from an invoice." msgstr "" -#: ../../content/developer/reference/extract_api.rst:378 -msgid "Contains the validation for each feature. The field ``merged_line`` indicates if the ``invoice_lines`` have been merged or not." +#: ../../content/developer/reference/extract_api.rst:385 +#: ../../content/developer/reference/extract_api.rst:489 +#: ../../content/developer/reference/extract_api.rst:509 +msgid "Feature name" msgstr "" -#: ../../content/developer/reference/extract_api.rst:380 -msgid "You don't have to validate all the features in order for the validation to succeed. However :ref:`/validate ` can't be called multiple times for a same invoice. Therefore you should validate all the features you want to validate at once." +#: ../../content/developer/reference/extract_api.rst:385 +#: ../../content/developer/reference/extract_api.rst:489 +#: ../../content/developer/reference/extract_api.rst:509 +msgid "Specifities" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:387 +msgid "``SWIFT_code``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:387 +msgid "``content`` is a dictionary encoded as a string." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:389 +msgid "It contains information about the detected SWIFT code (or `BIC `_)." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:392 +msgid "Keys:" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:396 +msgid "``bic``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:397 +msgid "detected BIC (string)." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:399 +msgid "bank name (string)." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:400 +msgid "``country_code``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:401 +msgid "ISO3166 alpha-2 country code of the bank (string)." msgstr "" #: ../../content/developer/reference/extract_api.rst:402 -msgid "``validation``" +msgid "``city`` (optional)" msgstr "" -#: ../../content/developer/reference/extract_api.rst:404 -msgid "A **validation** for a given feature is a dictionary containing the textual representation of the expected value for this given feature. This format apply for all the features except for ``global_taxes`` and ``invoice_lines`` which have more complex validation format." +#: ../../content/developer/reference/extract_api.rst:403 +msgid "city of the bank (string)." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:405 +msgid "``verified_bic``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:405 +msgid "True if the BIC has been found in our DB (bool)." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:407 +msgid "Name and city are present only if verified_bic is true." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:409 +msgid "``iban``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:409 +#: ../../content/developer/reference/extract_api.rst:411 +#: ../../content/developer/reference/extract_api.rst:413 +#: ../../content/developer/reference/extract_api.rst:420 +#: ../../content/developer/reference/extract_api.rst:422 +#: ../../content/developer/reference/extract_api.rst:424 +#: ../../content/developer/reference/extract_api.rst:428 +#: ../../content/developer/reference/extract_api.rst:430 +#: ../../content/developer/reference/extract_api.rst:432 +#: ../../content/developer/reference/extract_api.rst:440 +#: ../../content/developer/reference/extract_api.rst:446 +#: ../../content/developer/reference/extract_api.rst:448 +#: ../../content/developer/reference/extract_api.rst:450 +#: ../../content/developer/reference/extract_api.rst:452 +#: ../../content/developer/reference/extract_api.rst:491 +#: ../../content/developer/reference/extract_api.rst:493 +#: ../../content/developer/reference/extract_api.rst:495 +#: ../../content/developer/reference/extract_api.rst:499 +#: ../../content/developer/reference/extract_api.rst:511 +#: ../../content/developer/reference/extract_api.rst:513 +#: ../../content/developer/reference/extract_api.rst:515 +#: ../../content/developer/reference/extract_api.rst:517 +msgid "``content`` is a string" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:411 +msgid "``aba``" msgstr "" #: ../../content/developer/reference/extract_api.rst:413 -msgid "validation for ``global_taxes``" +msgid "``VAT_Number``" msgstr "" #: ../../content/developer/reference/extract_api.rst:415 -msgid "**content** is a list of dictionaries. Each dictionary represents a tax:" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:417 -msgid "``amount``" -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:418 -msgid "Amount on which the tax is applied." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:419 -msgid "``tax_amount``" +msgid "Depending on the value of perspective in the user_infos, this will be the VAT number of the supplier or the client. If perspective is client, it'll be the supplier's VAT number. If it's supplier, it's the client's VAT number." msgstr "" #: ../../content/developer/reference/extract_api.rst:420 -msgid "Amount of the tax." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:421 -msgid "``tax_amount_type``" +msgid "``qr-bill``" msgstr "" #: ../../content/developer/reference/extract_api.rst:422 -msgid "Indicates if the ``tax_amount`` is a percentage or a fixed value. The type must be specified using the literal string \"fixed\" or \"percent\"." +msgid "``payment_ref``" msgstr "" #: ../../content/developer/reference/extract_api.rst:424 -msgid "``tax_price_include``" +msgid "``purchase_order``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:424 -msgid "Indicates if ``amount`` already contains the tax or not." +#: ../../content/developer/reference/extract_api.rst:426 +msgid "Uses ``selected_values`` instead of ``selected_value``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:428 +#: ../../content/developer/reference/extract_api.rst:493 +msgid "``country``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:430 +#: ../../content/developer/reference/extract_api.rst:499 +msgid "``currency``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:432 +#: ../../content/developer/reference/extract_api.rst:495 +msgid "``date``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:434 +msgid "Format : *YYYY-MM-DD*" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:436 +msgid "``due_date``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:436 +msgid "Same as for ``date``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:438 +msgid "``total_tax_amount``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:438 +#: ../../content/developer/reference/extract_api.rst:442 +#: ../../content/developer/reference/extract_api.rst:444 +#: ../../content/developer/reference/extract_api.rst:497 +msgid "``content`` is a float" msgstr "" #: ../../content/developer/reference/extract_api.rst:440 -msgid "validation for ``invoice_lines``" +msgid "``invoice_id``" msgstr "" #: ../../content/developer/reference/extract_api.rst:442 -msgid "**lines** is a list of dictionaries. Each dictionary represents an invoice line. The dictionary keys speak for themselves." +msgid "``subtotal``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:485 -msgid "12" +#: ../../content/developer/reference/extract_api.rst:444 +#: ../../content/developer/reference/extract_api.rst:497 +msgid "``total``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:485 -msgid "Validation format is incorrect" +#: ../../content/developer/reference/extract_api.rst:446 +msgid "``supplier``" msgstr "" -#: ../../content/developer/reference/extract_api.rst:506 -msgid "You can test your integration by using *integration_token* as ``account_token`` in the :ref:`/parse ` request." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:508 -msgid "Using this token put you in test mode and allows you to simulate the entire flow without really parsing a document and without being billed one credit for each successful invoice parsing." -msgstr "" - -#: ../../content/developer/reference/extract_api.rst:510 -msgid "The only technical differences in test mode is that the document you send is not parsed by the system and that the response you get from :ref:`/get_results ` is a hard-coded one." +#: ../../content/developer/reference/extract_api.rst:448 +msgid "``client``" msgstr "" +#: ../../content/developer/reference/extract_api.rst:450 #: ../../content/developer/reference/extract_api.rst:513 -msgid "A python implementation of the full flow can be found :download:`here `." +msgid "``email``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:457 +msgid "``feature_result`` for the ``invoice_lines`` feature" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:459 +msgid "It follows a more specific structure. It is basically a list of dictionaries where each dictionary represents an invoice line. Each value follows a :ref:`latestextract_api/get_result/feature_result` structure." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:483 +msgid "Expense" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:485 +msgid "The expenses are less complex than invoices. The following table gives an exhaustive list of all the fields we can extract from an expense report." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:503 +msgid "Applicant" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:505 +msgid "This third type of document is meant for processing resumes. The following table gives an exhaustive list of all the fields we can extract from a resume." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:515 +msgid "``phone``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:517 +msgid "``mobile``" +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:525 +msgid "You can test your integration by using *integration_token* as ``account_token`` in the :ref:`/parse ` request." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:528 +msgid "Using this token put you in test mode and allows you to simulate the entire flow without really parsing a document and without being billed one credit for each successful **document** parsing." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:531 +msgid "The only technical differences in test mode is that the document you send is not parsed by the system and that the response you get from :ref:`/get_result ` is a hard-coded one." +msgstr "" + +#: ../../content/developer/reference/extract_api.rst:535 +msgid "A python implementation of the full flow for invoices can be found :download:`here `." msgstr "" #: ../../content/developer/reference/frontend.rst:5 @@ -17739,6 +17197,10 @@ msgstr "" msgid "The service system is organized around three ideas: services, service providers and widgets. The way it works is that widgets trigger (with *trigger_up*) events, these events bubble up to a service provider, which will ask a service to perform a task, then maybe return an answer." msgstr "" +#: ../../content/developer/reference/frontend/javascript_reference.rst:876 +msgid "Service" +msgstr "" + #: ../../content/developer/reference/frontend/javascript_reference.rst:878 msgid "A service is an instance of the *AbstractService* class. It basically only has a name and a few methods. Its job is to perform some work, typically something depending on the environment." msgstr "" @@ -24159,6 +23621,14 @@ msgstr "" msgid "bedrooms" msgstr "" +#: ../../content/developer/tutorials/define_module_data.rst:183 +msgid "6" +msgstr "" + +#: ../../content/developer/tutorials/define_module_data.rst:183 +msgid "1" +msgstr "" + #: ../../content/developer/tutorials/define_module_data.rst:184 #: ../../content/developer/tutorials/getting_started/04_basicmodel.rst:196 msgid "living_area" @@ -25125,6 +24595,10 @@ msgstr "" msgid "The ``name`` field is a :class:`~odoo.fields.Char` which will be represented as a Python unicode ``str`` and a SQL ``VARCHAR``." msgstr "" +#: ../../content/developer/tutorials/getting_started/04_basicmodel.rst:134 +msgid "Types" +msgstr "" + #: ../../content/developer/tutorials/getting_started/04_basicmodel.rst:138 msgid "**Goal**: at the end of this section, several basic fields should have been added to the table ``estate_property``:" msgstr "" @@ -26212,10 +25686,6 @@ msgstr "" msgid "price" msgstr "" -#: ../../content/developer/tutorials/getting_started/08_relations.rst:244 -msgid "status" -msgstr "" - #: ../../content/developer/tutorials/getting_started/08_relations.rst:244 msgid "no copy" msgstr "" diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index 87a7ea100..0aff4d93d 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-15.2\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-09 12:00+0000\n" +"POT-Creation-Date: 2023-12-19 07:46+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -120,7 +120,7 @@ msgid "The following financial :doc:`reports ` are availab msgstr "" #: ../../content/applications/finance/accounting.rst:127 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:365 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:418 msgid "Financial reports" msgstr "" @@ -157,10 +157,12 @@ msgid "Audit" msgstr "" #: ../../content/applications/finance/accounting.rst:139 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1073 msgid "General ledger" msgstr "" #: ../../content/applications/finance/accounting.rst:141 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1035 msgid "Trial balance" msgstr "" @@ -179,7 +181,7 @@ msgstr "" #: ../../content/applications/finance/accounting.rst:149 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:135 #: ../../content/applications/finance/fiscal_localizations/chile.rst:161 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:124 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:138 #: ../../content/applications/finance/fiscal_localizations/peru.rst:321 msgid "Partner" msgstr "" @@ -402,6 +404,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:21 #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:46 #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:12 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:36 #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:15 #: ../../content/applications/finance/accounting/get_started/vat_units.rst:22 #: ../../content/applications/finance/accounting/payments/batch.rst:15 @@ -419,7 +422,7 @@ msgstr "" #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:60 #: ../../content/applications/finance/accounting/taxes/cash_basis.rst:14 #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:17 -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:27 +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:20 #: ../../content/applications/finance/accounting/taxes/retention.rst:23 #: ../../content/applications/finance/accounting/taxes/vat_verification.rst:13 #: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:22 @@ -430,15 +433,15 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:29 #: ../../content/applications/finance/fiscal_localizations/chile.rst:290 #: ../../content/applications/finance/fiscal_localizations/chile.rst:332 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:20 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:21 #: ../../content/applications/finance/fiscal_localizations/germany.rst:58 #: ../../content/applications/finance/fiscal_localizations/italy.rst:8 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:8 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:6 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:36 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:620 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:726 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:847 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:40 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:650 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:766 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:906 #: ../../content/applications/finance/fiscal_localizations/peru.rst:25 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:6 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:6 @@ -448,7 +451,7 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:9 #: ../../content/applications/finance/payment_acquirers/authorize.rst:60 #: ../../content/applications/finance/payment_acquirers/mollie.rst:8 -#: ../../content/applications/finance/payment_acquirers/paypal.rst:141 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:146 #: ../../content/applications/finance/payment_acquirers/sips.rst:9 #: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:30 msgid "Configuration" @@ -1665,7 +1668,7 @@ msgid "Open the model you want to modify or click on :guilabel:`Create` to creat msgstr "" #: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:86 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:52 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:41 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:56 msgid "Type" msgstr "" @@ -1716,7 +1719,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:5 #: ../../content/applications/finance/accounting/payments/batch_sdd.rst:86 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:310 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:321 msgid "Customer invoices" msgstr "" @@ -1741,7 +1744,7 @@ msgid "Invoicing in most countries occurs when a contractual obligation is met. msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:35 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:234 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:284 msgid "Invoice creation" msgstr "" @@ -1914,8 +1917,8 @@ msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:5 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:164 #: ../../content/applications/finance/fiscal_localizations/chile.rst:198 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:165 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:190 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:192 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:186 #: ../../content/applications/finance/fiscal_localizations/peru.rst:69 #: ../../content/applications/finance/fiscal_localizations/peru.rst:242 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:127 @@ -2787,7 +2790,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:97 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:26 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:32 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:33 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:16 #: ../../content/applications/finance/fiscal_localizations/france.rst:182 #: ../../content/applications/finance/fiscal_localizations/india.rst:16 @@ -2795,9 +2798,8 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:16 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:34 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:14 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:66 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:98 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:122 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:71 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:115 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:15 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:16 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:14 @@ -2806,16 +2808,15 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:98 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:27 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:33 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:34 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:17 #: ../../content/applications/finance/fiscal_localizations/india.rst:17 #: ../../content/applications/finance/fiscal_localizations/italy.rst:18 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:17 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:35 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:15 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:67 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:99 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:123 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:72 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:116 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:16 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:17 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:15 @@ -3714,489 +3715,828 @@ msgid ":doc:`../fiscal_localizations`" msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:190 -msgid "`Odoo Tutorials: Accounting Basics `_" +msgid "`Odoo Tutorials: Accounting and Invoicing - Getting started [video] `_" msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:3 -msgid "Inventory average price valuation" +msgid "Average price on returned goods" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:5 -msgid "As stated in the :doc:`inventory valuation page `, one of the possible costing method you can use in perpetual stock valuation, is the average cost." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:9 +msgid "*Average cost valuation* (AVCO) is an inventory valuation method that evaluates cost based on the total cost of goods bought or produced during a period, divided by the total number of items on-hand. Inventory valuation is used to:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:10 -msgid "This document answers to one recurrent question for companies using that method to make their stock valuation: how does a shipping returned to its supplier impact the average cost and the accounting entries? This document is **only** for the specific use case of a perpetual valuation (as opposed to the periodic one) and in average price costing method (as opposed to standard of FIFO)." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:13 +msgid "reflect the value of a company's assets;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:14 +msgid "keep track of the amount of unsold goods;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:15 +msgid "account for monetary value in goods that have yet to generate profit;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:16 +msgid "report on flow of goods throughout the quarter." msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:18 -msgid "Definition of average cost" +msgid "Because |AVCO| uses the weighted average to evaluate the cost, it is a good fit for companies that sell only a few different products in large quantities. In Odoo, this costing analysis is *automatically updated* each time products are received." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:20 -msgid "The average cost method calculates the cost of ending inventory and cost of goods sold on the basis of weighted average cost per unit of inventory." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:22 +msgid "Thus, when shipments are returned to their supplier, Odoo automatically generates accounting entries to reflect the change in inventory valuation. However, Odoo does **not** automatically update the |AVCO| calculation, because :ref:`this can potentially create inconsistencies with inventory valuation `." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:24 -msgid "The weighted average cost per unit is calculated using the following formula:" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:28 +msgid "This document addresses a specific use case for theoretical purposes. Navigate :ref:`here ` for instructions on how to set up and use |AVCO| in Odoo." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:27 -msgid "When new products arrive in a warehouse, the new average cost is recomputed as:" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:32 +msgid ":ref:`Using inventory valuation `" msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:33 -msgid "When products leave the warehouse: the average cost **does not** change" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:36 -msgid "Defining the purchase price" +msgid ":ref:`Other inventory valuation methods `" msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:38 -msgid "The purchase price is estimated at the reception of the products (you might not have received the vendor bill yet) and reevaluated at the reception of the vendor bill. The purchase price includes the cost you pay for the products, but it may also includes additional costs, like landed costs." +msgid "To use average cost inventory valuation on a product, navigate to :menuselection:`Inventory --> Configuration --> Product Categories` and select the category that will be using |AVCO|. On the product category page, set :guilabel:`Costing Method` to `Average Cost (AVCO)` and :guilabel:`Inventory Valuation` to `Automated`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:45 -msgid "Average cost example" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:44 +msgid ":ref:`Inventory valuation configuration `" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:47 +msgid "Using average cost valuation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:49 +msgid "The average cost method adjusts the inventory valuation when products are received in the warehouse. This section explains how it works, but if the explanation is unnecessary, skip to the :ref:`return to supplier use case ` section." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 +msgid "Formula" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:58 +msgid "When new products arrive, the new average cost for each product is recomputed using the formula:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:60 +msgid "Avg~Cost = \\frac{(Old~Qty \\times Old~Avg~Cost) + (Incoming~Qty \\times Purchase~Price)}{Final~Qty}\n" +"\n" +"" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:63 +msgid "**Old Qty**: product count in stock before receiving the new shipment;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:64 +msgid "**Old Avg Cost**: calculated average cost for a single product from the previous inventory valuation;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:66 +msgid "**Incoming Qty**: count of products arriving in the new shipment;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:67 +msgid "**Purchase Price**: estimated price of products at the reception of products (since vendor bills may arrive later). The amount includes not only the price for the products, but also added costs, such as shipping, taxes, and :ref:`landed costs `. At reception of the vendor bill, this price is adjusted;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:71 +msgid "**Final Qty**: quantity of on-hand stock after the stock move." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:76 +msgid "When products leave the warehouse, the average cost **does not** change. Read about why the average cost valuation is **not** adjusted :ref:`here `." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 +msgid "Compute average cost" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:84 +msgid "To understand how the average cost of a product changes with each shipment, consider the following table of warehouse operations and stock moves. Each is a different example of how the average cost valuation is affected." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 msgid "Operation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 -msgid "Delta Value" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +msgid "Incoming Value" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 msgid "Inventory Value" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 msgid "Qty On Hand" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:48 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:101 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 msgid "Avg Cost" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:50 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:146 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:91 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:275 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 msgid "$0" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:50 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:146 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:91 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:275 #: ../../content/applications/finance/fiscal_localizations/france.rst:240 msgid "0" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 -msgid "Receive 8 Products at $10" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +msgid "Receive 8 tables at $10/unit" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 -msgid "+8\\*$10" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +msgid "8 * $10" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 msgid "$80" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 msgid "8" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 msgid "$10" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 -msgid "Receive 4 Products at $16" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +msgid "Receive 4 tables at $16/unit" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 -msgid "+4\\*$16" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +msgid "4 * $16" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 msgid "$144" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 #: ../../content/applications/finance/fiscal_localizations/france.rst:88 #: ../../content/applications/finance/fiscal_localizations/france.rst:111 msgid "12" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:54 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:84 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:86 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:103 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:105 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:121 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 msgid "$12" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 -msgid "Deliver 10 Products" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +msgid "Deliver 10 tables" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 -msgid "-10\\*$12" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +msgid "-10 * $12" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:84 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:103 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 msgid "$24" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:84 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:103 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:156 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 msgid "2" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:60 -msgid "At the beginning, the Avg Cost is set to 0 set as there is no product in the inventory. When the first reception is made, the average cost becomes logically the purchase price." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:103 +msgid "Ensure comprehension of the above computations by reviewing the \"Receive 8 tables at $10/unit\" example." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:64 -msgid "At the second reception, the average cost is updated because the total inventory value is now ``$80 + 4*$16 = $144``. As we have 12 units on hand, the average price per unit is ``$144 / 12 = $12``." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:106 +msgid "Initially, the product stock is 0, so all values are $0." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:68 -msgid "By definition, the delivery of 10 products does not change the average cost. Indeed, the inventory value is now $24 as we have only 2 units remaining of each ``$24 / 2 = $12``." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:108 +msgid "In the first warehouse operation, `8` tables are received at `$10` each. The average cost is calculated using the :ref:`formula `:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:73 -msgid "Purchase return use case" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:111 +msgid "Avg~Cost = \\frac{0 + 8 \\times $10}{8} = \\frac{$80}{8} = $10\n" +"\n" +"" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:75 -msgid "In case of a product returned to its supplier after reception, the inventory value is reduced using the average cost formulae (not at the initial price of these products!)." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:114 +msgid "Since the *incoming quantity* of tables is `8` and the *purchase price* for each is `$10`," msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:79 -msgid "Which means that the above table will be updated as follow:" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:115 +msgid "The inventory value in the numerator is evaluated to `$80`;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:86 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 -msgid "Return of 1 Product initially bought at $10" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:116 +msgid "`$80` is divided by the total amount of tables to store, `8`;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:86 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:105 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:121 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 -msgid "-1\\*$12" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 +msgid "`$10` is the average cost of a single table from the first shipment." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 +msgid "To verify this in Odoo, in the *Purchase* app, order `8` quantities of a new product, `Table`, with no previous stock moves, for `$10` each." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:122 +msgid "In the table's :guilabel:`Product Category` field in the :guilabel:`General Information` tab of the product form, click the :guilabel:`➡️ (arrow)` icon, to open an :guilabel:`External Link` to edit the product category. Set the :guilabel:`Costing Method` to `Average Cost (AVCO)` and :guilabel:`Inventory Valuation` to `Automated`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:127 +msgid "Then, return to the purchase order. Click :guilabel:`Confirm Order`, and click :guilabel:`Receive Products` to confirm receipt." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:130 +msgid "Next, check the inventory valuation record generated by the product reception by navigating to :menuselection:`Inventory --> Reporting --> Inventory Valuation`. Select the drop-down for `Table`, and view the :guilabel:`Total Value` column for the *valuation layer* (:dfn:`inventory valuation at a specific point in time = on-hand quantity * unit price`). The 8 tables in-stock are worth $80." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:0 +msgid "Show inventory valuation of 8 tables in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:141 +msgid "When the product category's :guilabel:`Costing Method` is set to :guilabel:`AVCO`, then the average cost of a product is also displayed on the :guilabel:`Cost` field, under the :guilabel:`General Information` tab, on the product page itself." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:146 +msgid "Product delivery (use case)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 +msgid "For outgoing shipments, :ref:`outbound products have no effect on the average cost valuation `. Although the average cost valuation is not recalculated, the inventory value still decreases because the product is removed from stock and delivered to the customer location." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +msgid "To demonstrate that the average cost valuation is not recalculated, examine the \"Deliver 10 tables\" example." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:157 +msgid "Avg~Cost = \\frac{12 \\times $12 + (-10) \\times $12}{12-10} = \\frac{24}{2} = $12\n" +"\n" +"" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:86 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:105 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:121 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +msgid "Because 10 tables are being sent out to customers, the *incoming quantity* is `-10`. The previous average cost (`$12`) is used in lieu of a vendor's *purchase price*;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:162 +msgid "The *incoming inventory value* is `-10 * $12 = -$120`;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:163 +msgid "The old *inventory value* (`$144`) is added to the *incoming inventory value* (`-$120`), so `$144 + -$120 = $24`;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:165 +msgid "Only `2` tables remain after shipping out `10` tables from `12`. So the current *inventory value* (`$24`) is divided by the on-hand quantity (`2`);" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:167 +msgid "`$24 / 2 = $12`, which is the same average cost as the previous operation." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:169 +msgid "To verify this in Odoo, sell `10` tables in the *Sales* app, validate the delivery, and then review the inventory valuation record by going to in :menuselection:`Inventory --> Reporting --> Inventory Valuation`. In the topmost valuation layer, delivering `10` tables reduces the product's value by `-$120`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:174 +msgid "**Note**: What is not represented in this stock valuation record is the revenue made from this sale, so this decrease is not a loss to the company." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:0 +msgid "Show how deliveries decrease inventory valuation." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:184 +msgid "Return items to supplier (use case)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:186 +msgid "Because the price paid to suppliers can differ from the price the product is valued at with the |AVCO| method, Odoo handles returned items in a specific way." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:189 +msgid "Products are returned to suppliers at the original purchase price, but;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:190 +msgid "The internal cost valuation remains unchanged." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:192 +msgid "The above :ref:`example table ` is updated as follows:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +msgid "Qty*Avg Cost" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +msgid "Return 1 table bought at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +msgid "-1 * $12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 #: ../../content/applications/finance/fiscal_localizations/france.rst:242 msgid "1" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:90 -msgid "Explanation: counter example" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:202 +msgid "In other words, returns to vendors are perceived by Odoo as another form of a product exiting the warehouse. To Odoo, because the table is valued at $12 per unit, the inventory value is reduced by `$12` when the product is returned; the initial purchase price of `$10` is unrelated to the table's average cost." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:92 -msgid "Remember the definition of **Average Cost**, saying that we do not update the average cost of a product leaving the inventory. If you break this rule, you may lead to inconsistencies in your inventory." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:208 +msgid "To return a single table that was purchased for `$10`, navigate to the receipt in the *Inventory* app for the :ref:`8 tables purchased in Exercise 1 ` by going to the :guilabel:`Inventory Overview`, clicking on :guilabel:`Receipts`, and selecting the desired receipt." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:96 -msgid "As an example, here is the scenario when you deliver one piece to the customer and return the other one to your supplier (at the cost you purchased it). Here is the operation:" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:213 +msgid "Then, click :guilabel:`Return` on the validated delivery order, and modify the quantity to `1` in the reverse transfer window. This creates an outgoing shipment for the table. Select :guilabel:`Validate` to confirm the outgoing shipment." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:105 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:121 -msgid "Customer Shipping 1 product" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:217 +msgid "Return to :menuselection:`Inventory --> Reporting --> Inventory Valuation` to see how the outgoing shipment decreases the inventory value by $12." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 -msgid "-1\\*$10" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:0 +msgid "Inventory valuation for return." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:227 +msgid "Eliminate stock valuation errors in outgoing products" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:229 +msgid "Inconsistencies can occur in a company's inventory when the average cost valuation is recalculated on outgoing shipments." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:232 +msgid "To demonstrate this error, the table below displays a scenario in which 1 table is shipped to a customer and another is returned to a supplier at the purchased price." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +msgid "Qty*Price" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +msgid "Ship 1 product to customer" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +msgid "-1 \\* $12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +msgid "Return 1 product initially bought at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +msgid "-1 \\* $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 msgid "**$2**" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:107 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 msgid "**0**" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:110 -msgid "As you can see in this example, this is not correct: an inventory valuation of $2 for 0 pieces in the warehouse." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:245 +msgid "In the final operation above, the final inventory valuation for the table is `$2` even though there are `0` tables left in stock." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:113 -msgid "The correct scenario should be to return the goods at the current average cost:" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:248 +msgid "Correct method" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:123 -msgid "**$0**" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:250 +msgid "Use the average cost to value the return. This does not mean the company gets $12 back for a $10 purchase; the item returned for $10 is valued internally at $12. The inventory value change represents a product worth $12 no longer being accounted for in company assets." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:126 -msgid "On the other hand, using the average cost to value the return ensure a correct inventory value at all times." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:255 +msgid "Anglo-Saxon accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:130 -msgid "Further thoughts on anglo saxon mode" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:257 +msgid "In addition to using |AVCO|, companies that use **Anglo-Saxon accounting** also keep a holding account that tracks the amount to be paid to vendors. Once a vendor delivers an order, **inventory value** increases based on the vendor price of the products that have entered the stock. The holding account (called **stock input**) is credited and only reconciled once the vendor bill is received." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:132 -msgid "For people in using the **anglo saxon accounting** principles, there is another concept to take into account: the stock input account of the product, which is intended to hold at any time the value of vendor bills to receive. So the stock input account will increase on reception of incoming shipments and will decrease when receiving the related vendor bills." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:263 +msgid ":ref:`Anglo-Saxon vs. Continental `" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:139 -msgid "Back to our example, we see that when the return is valued at the average price, the amount booked in the stock input account is the original purchase price:" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:265 +msgid "The table below reflects journal entries and accounts. The *stock input* account stores the money intended to pay vendors when the vendor bill has not yet been received. To balance accounts when returning products that have a price difference between the price the product is **valued at** and the price it was bought for, a *price difference* account is created." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 -msgid "stock input" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Stock Input" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 -msgid "price diff" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Price Diff" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +msgid "Receive 8 tables at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 msgid "($80)" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:150 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 msgid "Receive vendor bill $80" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:152 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +msgid "Receive 4 tables at $16" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 msgid "($64)" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 msgid "Receive vendor bill $64" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +msgid "Deliver 10 tables to customer" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +msgid "Return 1 table initially bought at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 msgid "**$10**" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:158 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 msgid "**$12**" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 msgid "Receive vendor refund $10" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 msgid "$2" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:163 -msgid "This is because the vendor refund will be made using the original purchase price, so to zero out the effect of the return in the stock input in last operation, we need to reuse the original price. The price difference account located on the product category is used to book the difference between the average cost and the original purchase price." +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:293 +msgid "Product reception" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:296 +msgid "Summary" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:298 +msgid "At product reception, Odoo ensures companies can pay for goods that were purchased by preemptively moving an amount matching the price of received goods into the :doc:`liability account `, **Stock Input**. Then, once the bill has been received, the amount in the holding account is transferred to *Accounts Payable*. Transfers into this account means the bill has been paid. **Stock Input** is reconciled once the vendor bill is received." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:305 +msgid "Inventory valuation is a method of calculating how much each in-stock product is worth internally. Since there is a difference between the price the product is **valuated at** and the price the product was actually **purchased for**, the **Inventory Valuation** account is unrelated to the crediting and debiting operations of the **Stock Input** account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:310 +msgid "To conceptualize all this, follow the breakdown below." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:313 +msgid "Accounts balanced at received products" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:315 +msgid "In this example, a company starts with zero units of a product, `table`, in stock. Then, 8 tables are received from the vendor:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:318 +msgid "The **Stock Input** account stores `$80` of credit owed to the vendor. The amount in this account is unrelated to the inventory value." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:320 +msgid "`$80` worth of tables came **in** (**debit** the *Inventory Value* account `$80`), and" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:321 +msgid "`$80` must be paid **out** for received goods (**credit** the *Stock Input* account `$80`)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:324 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:367 +msgid "In Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:326 +msgid "Odoo generates an accounting journal entry when shipments that use |AVCO| costing method are received. Configure a :guilabel:`Price Difference Account` by selecting the :guilabel:`➡️ (arrow)` icon next to the :guilabel:`Product Category` field on the product page." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:330 +msgid "Under :guilabel:`Account Properties`, create a new :guilabel:`Price Difference Account` by typing in the name of the account and clicking :guilabel:`Create and Edit`. Then set the account :guilabel:`Type` as `Expenses`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:-1 +msgid "Create price difference account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:338 +msgid "Then, receive the shipment in the *Purchase* app or *Inventory* app, and navigate to the :menuselection:`Accounting app --> Accounting --> Journal Entries`. In the list, find the :guilabel:`Reference` that matches the warehouse reception operation for the relevant product." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:-1 +msgid "Show accounting entry of 8 tables from the list." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:346 +msgid "Click on the line for 8 tables. This accounting journal entry shows that when the 8 tables were received, the `Stock Valuation` account increased by `$80`. Conversely, the **Stock Input** account (set as `Stock Interim (Received)` account by default) is credited `$80`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:-1 +msgid "Debit stock valuation and credit stock input 80 dollars." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:355 +msgid "Accounts balanced at received vendor bill" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:357 +msgid "In this example, a company starts with zero units of a product, table, in stock. Then, 8 tables are received from the vendor. When the bill is received from vendor for 8 tables:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:360 +msgid "Use `$80` in the **Stock Input** account to pay the bill. This cancels out and the account now holds `$0`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:362 +msgid "Debit **Stock Input** `$80` (to reconcile this account)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:363 +msgid "Credit **Accounts payable** `$80`. This account stores the amount the company owes others, so accountants use the amount to write checks to vendors." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:369 +msgid "Once the vendor requests payment, navigate to the :menuselection:`Purchase app --> Orders --> Purchase` and select the :abbr:`PO (Purchase Order)` for 8 tables. Inside the :abbr:`PO (Purchase Order)`, select :guilabel:`Create Bill`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:373 +msgid "Switch to the :guilabel:`Journal Items` tab to view how `$80` is transferred from the holding account, `Stock Interim (Received)` to `Accounts Payable`. :guilabel:`Confirm` the bill to record the payment to the vendor." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:-1 +msgid "Show bill linked to the purchase order for 8 tables." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:382 +msgid "On product delivery" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:384 +msgid "In the :ref:`above example table `, when 10 products are delivered to a customer, the **Stock Input** account is untouched because there are no new products coming in. To put it simply:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:388 +msgid "**Inventory valuation** is credited `$120`. Subtracting from inventory valuation represents `$120` worth of products exiting the company." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:390 +msgid "Debit **Accounts Receivable** to record revenue from the sale." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:-1 +msgid "Show journal items linked to sale order." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:398 +msgid "In the accounting journal entry invoicing a customer for 10 tables, the accounts **Product Sales**, **Tax Received**, and **Accounts Receivable** all pertain to the sale of the product. **Accounts Receivable** is the account where the customer payment will be received." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:402 +msgid "Anglo-Saxon accounting recognizes the cost of goods sold (COGS) once the sale is made. So, up until the product is sold, scrapped, or returned, costs of keeping the product in stock are not accounted for. The **Expense** account is debited `$120` to log the costs of storing 10 tables during this period of time." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:408 +msgid "On product return" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:410 +msgid "In the :ref:`above example table `, when returning 1 product to a vendor purchased at `$10`, a company expects `$10` in the **Accounts Payable** account from the vendor. However, **Stock Input** account must be debited `$12` because the average cost is `$12` at the time of the return. The missing `$2` is accounted for in the :guilabel:`Price Difference Account`, which is set up in the product's :guilabel:`Product Category`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:417 +msgid "Behavior of *price difference accounts* varies from localization. In this case, the account is intended to store differences between vendor price and *automated* inventory valuation methods." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:420 +msgid "Summary:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:422 +msgid "Debit **Stock Input** account `$10` to move the table from stock to stock input. This move is to indicate that the table is to be processed for an outgoing shipment." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:424 +msgid "Debit **Stock Input** an additional `$2` to account for the **Price Difference**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:425 +msgid "Credit **Stock Valuation** `$12` because the item is leaving the stock." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:-1 +msgid "2 dollar difference expensed in Price Difference account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:431 +msgid "Once the vendor's refund is received," +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:433 +msgid "Credit **Stock Input** account `$10` to reconcile the price of the table." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:434 +msgid "Debit **Accounts Payable** `$10` to have the accountants collect and register the payment in their journal." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:-1 +msgid "Return to get 10 dollars back." msgstr "" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:3 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:79 #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:87 #: ../../content/applications/finance/fiscal_localizations/chile.rst:145 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:215 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:247 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1008 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:38 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:41 msgid "Chart of accounts" msgstr "" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:5 -msgid "The **chart of accounts (COA)** is the list of all the accounts used to record financial transactions in the general ledger of an organization." +msgid "The **chart of accounts (COA)** is the list of all the accounts used to record financial transactions in the general ledger of an organization. The chart of accounts can be found under :menuselection:`Accounting-->Configuration-->Chart of Accounts`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:8 -msgid "The accounts are usually listed in the order of appearance in the financial reports. Most of the time, they are listed as follows :" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:11 -msgid "Balance Sheet accounts:" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:13 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:67 -msgid "Assets" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:14 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:79 -msgid "Liabilities" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:15 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:87 -msgid "Equity" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:17 -msgid "Profit & Loss:" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:19 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:91 -msgid "Income" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:20 -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:95 -msgid "Expense" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:22 -msgid "When browsing your chart of accounts, you can filter the accounts by number, in the left column, and also group them by :guilabel:`Account Type`." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:9 +msgid "When browsing your chart of accounts, you can sort the accounts by :guilabel:`Code`, :guilabel:`Account Name`, or :guilabel:`Type`, but other options are available in the drop-down menu :guilabel:`(⋮)`." msgstr "" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:-1 msgid "Group the accounts by type in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:30 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:17 msgid "Configuration of an account" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:32 -msgid "The country you select at the creation of your database (or additional company on your database) determines which **fiscal localization package** is installed by default. This package includes a standard chart of accounts already configured according to the country's regulations. You can use it directly or set it according to your company's needs." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:19 +msgid "The country you select during the creation of your database (or additional company in your database) determines which :doc:`fiscal localization package <../../fiscal_localizations>` is installed by default. This package includes a standard chart of accounts already configured according to the country's regulations. You can use it directly or set it according to your company's needs." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:38 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:24 +msgid "To create a new account, go to :menuselection:`Accounting-->Configuration-->Chart of Accounts`, click :guilabel:`Create`, and fill in (at the minimum) the required fields (:guilabel:`Code, Account Name, Type`)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:29 msgid "It is not possible to modify the **fiscal localization** of a company once a journal entry has been posted." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:41 -msgid "To create a new account, go to :menuselection:`Accounting --> Configuration --> Chart of Accounts`, click on :guilabel:`Create`, and fill out the form." -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:45 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:33 msgid "Code and name" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:47 -msgid "Each account is identified by its **code** and **name**, which also indicates the account's purpose." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:35 +msgid "Each account is identified by its :guilabel:`Code` and :guilabel:`Name`, which also indicate the account's purpose." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:54 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:43 msgid "Correctly configuring the **account type** is critical as it serves multiple purposes:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:45 msgid "Information on the account's purpose and behavior" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:57 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:46 msgid "Generate country-specific legal and financial reports" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:47 msgid "Set the rules to close a fiscal year" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:59 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:48 msgid "Generate opening entries" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:61 -msgid "To configure an account type, open the :guilabel:`Type` field's drop-down selector and select the right type among the following list:" +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:50 +msgid "To configure an account type, open the :guilabel:`Type` field's drop-down selector and select the corresponding type from the following list:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:65 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:54 msgid "Report" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:65 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:54 msgid "Category" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:65 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:54 msgid "Account Types" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:67 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 #: ../../content/applications/finance/accounting/reporting.rst:36 #: ../../content/applications/finance/fiscal_localizations/germany.rst:23 #: ../../content/applications/finance/fiscal_localizations/spain.rst:27 msgid "Balance Sheet" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:67 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 +msgid "Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:59 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:62 msgid "Receivable" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:69 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:68 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:71 msgid "Bank and Cash" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:71 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:60 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:74 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:77 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:80 @@ -4204,199 +4544,215 @@ msgstr "" msgid "Current Assets" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:73 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:62 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:86 msgid "Non-current Assets" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:75 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:64 msgid "Prepayments" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:77 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:66 msgid "Fixed Assets" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:79 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:68 +msgid "Liabilities" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:68 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:65 msgid "Payable" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:81 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:70 msgid "Credit Card" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:83 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:72 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:89 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:92 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:95 msgid "Current Liabilities" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:85 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:74 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:98 msgid "Non-current Liabilities" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:89 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:76 +msgid "Equity" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:78 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:101 msgid "Current Year Earnings" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:91 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:80 #: ../../content/applications/finance/fiscal_localizations/germany.rst:24 #: ../../content/applications/finance/fiscal_localizations/netherlands.rst:20 msgid "Profit & Loss" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:93 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:80 +msgid "Income" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:82 msgid "Other Income" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:97 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:84 +msgid "Expense" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:86 msgid "Depreciation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:99 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:88 msgid "Cost of Revenue" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:101 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:90 msgid "Other" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:101 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:90 msgid "Off-Balance Sheet" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:105 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:94 msgid "Assets, deferred expenses, and deferred revenues automation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:107 -msgid "Some **account types** display a new field **to automate** the creation of :ref:`assets ` entries, :ref:`deferred expenses ` entries, and :ref:`deferred revenues ` entries." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:96 +msgid "Some **account types** can **automate** the creation of :ref:`assets ` entries, :ref:`deferred expenses ` entries, and :ref:`deferred revenues ` entries. To **automate** entries, click :guilabel:`Setup` on an account line and go to the :guilabel:`Automation` tab." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:111 -msgid "You have three choices for the :guilabel:`Automation` field:" +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:101 +msgid "You have three choices for the :guilabel:`Automation` tab:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:113 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:103 msgid ":guilabel:`No`: this is the default value. Nothing happens." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:114 -msgid ":guilabel:`Create in draft`: whenever a transaction is posted on the account, a draft entry is created, but not validated. You must first fill out the corresponding form." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:104 +msgid ":guilabel:`Create in draft`: whenever a transaction is posted on the account, a draft entry is created but not validated. You must first fill out the corresponding form." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:116 -msgid ":guilabel:`Create and validate`: you must also select a **model**. Whenever a transaction is posted on the account, an entry is created and immediately validated." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:106 +msgid ":guilabel:`Create and validate`: you must also select a :guilabel:`Deferred Expense Model`. Whenever a transaction is posted on the account, an entry is created and immediately validated." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:120 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:110 #: ../../content/applications/finance/accounting/taxes.rst:14 msgid "Default taxes" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:122 -msgid "Select a **default tax** that will be applied when this account is chosen for a product sale or purchase." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:112 +msgid "In the :guilabel:`Setup` menu of an account, select a **default tax** to be applied when this account is chosen for a product sale or purchase." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:126 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:116 msgid "Tags" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:128 -msgid "Some accounting reports require **tags** to be set on the relevant accounts. By default, you can choose among the tags that are used by the *Cash Flow Statement*." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:118 +msgid "Some accounting reports require **tags** to be set on the relevant accounts. To add a tag, under :guilabel:`Setup`, click the :guilabel:`Tags` field and select an existing tag or :guilabel:`Create` a new one." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:132 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:123 msgid "Account groups" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:134 -msgid "**Account groups** are useful to list multiple accounts as *sub-accounts* of a bigger account and thus consolidate reports such as the **Trial Balance**. By default, groups are handled automatically based on the code of the group. For example, a new account `131200` is going to be part of the group `131000`." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:125 +msgid "**Account groups** are useful to list multiple accounts as *sub-accounts* of a bigger account and thus consolidate reports such as the **Trial Balance**. By default, groups are handled automatically based on the code of the group. For example, a new account `131200` is going to be part of the group `131000`. You can attribute a specific group to an account in the :guilabel:`Group` field under :guilabel:`Setup`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:140 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:132 msgid "Create account groups manually" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:143 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:135 msgid "Regular users should not need to create account groups manually. The following section is only intended for rare and advanced use cases." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:146 -msgid "To create a new account group, :ref:`developer mode ` and head to :menuselection:`Accounting app --> Configuration --> Account Groups`. Here, create a new group and enter the :guilabel:`name, code prefix, and company` to which that group account should be available. Note that you must enter the same code prefix in both :guilabel:`From` and :guilabel:`to` fields." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:138 +msgid "To create a new account group, activate :ref:`developer mode ` and head to :menuselection:`Accounting app-->Configuration-->Account Groups`. Here, create a new group and enter the :guilabel:`name, code prefix, and company` to which that group account should be available. Note that you must enter the same code prefix in both :guilabel:`From` and :guilabel:`to` fields." msgstr "" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:-1 msgid "Account groups creation." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:156 -msgid "To display your **Trial Balance** report with your account groups, go to :menuselection:`Accounting app-->Reporting-->Trial Balance`, then open the :guilabel:`Options` menu and select :guilabel:`Hierarchy and Subtotals`." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:146 +msgid "To display your **Trial Balance** report with your account groups, go to :menuselection:`Accounting-->Reporting-->Trial Balance`, then open the :guilabel:`Options` menu and select :guilabel:`Hierarchy and Subtotals`." msgstr "" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:-1 msgid "Account Groups in the Trial Balance in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:165 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:154 msgid "Allow reconciliation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:167 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:156 msgid "Some accounts, such as accounts made to record the transactions of a payment method, can be used for the reconciliation of journal entries." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:170 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:159 msgid "For example, an invoice paid with a credit card can be marked as :guilabel:`paid` if reconciled with its payment. Therefore, the account used to record credit card payments needs to be configured as **allowing reconciliation**." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:174 -msgid "To do so, check the :guilabel:`Allow Reconciliation` box in the account's settings, and save." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:163 +msgid "To do so, check the :guilabel:`Allow Reconciliation` box in the account's settings, and :guilabel:`Save`; or enable the button from the chart of accounts view." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:177 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:-1 +msgid "Allow reconciliation for accounts in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:170 msgid "Deprecated" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:179 -msgid "It is not possible to delete an account once a transaction has been recorded on it. You can make them unusable by using the **Deprecated** feature." +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:172 +msgid "It is not possible to delete an account once a transaction has been recorded on it. You can make them unusable by using the **Deprecated** feature: check the :guilabel:`Deprecated` box in the account's settings, and :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:182 -msgid "To do so, check the :guilabel:`Deprecated` box in the account's settings, and save." -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:185 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:177 msgid ":doc:`cheat_sheet`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:186 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:178 msgid ":doc:`../vendor_bills/assets`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:187 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:179 msgid ":doc:`../vendor_bills/deferred_expenses`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:188 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:180 msgid ":doc:`../customer_invoices/deferred_revenues`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:189 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:181 #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:123 #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:38 msgid ":doc:`../../fiscal_localizations`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:190 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:182 msgid "`Odoo Tutorials: Chart of accounts `_" msgstr "" -#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:191 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:183 msgid "`Odoo Tutorials: Update your chart of accounts `_" msgstr "" @@ -5822,7 +6178,6 @@ msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/manage`" msgstr "" #: ../../content/applications/finance/accounting/payments/multiple.rst:10 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:403 msgid ":doc:`/applications/finance/accounting/bank/reconciliation`" msgstr "" @@ -7510,7 +7865,7 @@ msgid "Odoo API key" msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:25 -msgid "You can create Odoo external API keys either :ref:`for a single database ` (hosting: Odoo Online, On-premise, and Odoo.sh) or :ref:`for multiple databases managed by a user ` (hosting: Odoo Online)." +msgid "You can create Odoo external API keys either :ref:`for a single database ` (hosting: Odoo Online, On-premise, and Odoo.sh) or :ref:`for all databases managed by a single user ` (hosting: Odoo Online)." msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:30 @@ -7518,7 +7873,7 @@ msgid "These API keys are personal and provide full access to your user account. msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:31 -msgid "You can copy the API key only at its creation, and you cannot retrieve it later." +msgid "You can copy the API key only at its creation. It is not possible to retrieve it later." msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:32 @@ -7530,11 +7885,11 @@ msgid ":doc:`/developer/reference/external_api`" msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:40 -msgid "One key per database" +msgid "Per database" msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:42 -msgid "To create a new API key valid for a single database, click on the user menu, then on :guilabel:`My Profile`. Under the :guilabel:`Account Security` tab, click on :guilabel:`New API key`, confirm your password, give a descriptive name to your new key, and copy the new API key." +msgid "To add an API key to a **single** database, connect to the database, enable the :ref:`developer mode `, click on the user menu, and then :guilabel:`My Profile` / :guilabel:`Preferences`. Under the :guilabel:`Account Security` tab, click on :guilabel:`New API Key`, confirm your password, give a descriptive name to your new key, and copy the API key." msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:-1 @@ -7546,11 +7901,15 @@ msgid ":ref:`api/external_api/keys`" msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:56 -msgid "One key for multiple databases (fiduciaries)" +msgid "For all databases (fiduciaries)" msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:58 -msgid "To create a new API key valid for all the databases of a single user **(the easiest for fiduciaries)**, navigate to `Odoo's website `_ and sign in with your administrator account. Next, open `your account security settings in developer mode `_, click on :guilabel:`New API Key`, confirm your password, give a descriptive name to your new key, and copy the new API key." +msgid "To add an API key to **all** databases managed by a single user at the same time **(the easiest method for fiduciaries)**, navigate to `Odoo's website `_ and sign in with your administrator account. Next, open `your account security settings in developer mode `_, click on :guilabel:`New API Key`, confirm your password, give a descriptive name to your new key, and copy the new API key." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:65 +msgid "Open the `database manager `_ to view all databases that will be linked to the single API key." msgstr "" #: ../../content/applications/finance/accounting/reporting/silverfin.rst:-1 @@ -7663,7 +8022,7 @@ msgstr "" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:121 #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:37 -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:109 +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:114 #: ../../content/applications/finance/accounting/taxes/retention.rst:70 msgid ":doc:`../taxes`" msgstr "" @@ -8286,7 +8645,7 @@ msgstr "" #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:63 #: ../../content/applications/finance/fiscal_localizations/chile.rst:14 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:25 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:27 #: ../../content/applications/finance/fiscal_localizations/peru.rst:6 msgid "Introduction" msgstr "" @@ -8680,134 +9039,126 @@ msgid "Fiscal positions (tax and account mapping)" msgstr "" #: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:5 -msgid "Default taxes and accounts are set on products and customers to create new transactions on the fly. However, you might have to use different taxes and record the transactions on different accounts, according to your customers' and providers' localizations and business types." +msgid "Default taxes and accounts are set on products and customers to create new transactions on the fly. However, depending on the customers' and providers' localization and business type, using different taxes and accounts for a transaction might be necessary." msgstr "" #: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:9 -msgid "**Fiscal Positions** allow you to create *sets of rules* to automatically adapt the taxes and the accounts used for a transaction." +msgid "**Fiscal positions** allow the creation of rules to adapt the taxes and accounts used for a transaction automatically." msgstr "" -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:-1 -msgid "Example: Belgian to Intra-Community tax mapping with Fiscal Positions in Odoo Accounting" +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:12 +msgid "They can be applied :ref:`automatically `, :ref:`manually `, or :ref:`assigned to a partner `." msgstr "" #: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:16 -msgid "They can be applied in various ways:" +msgid "Several default fiscal positions are available as part of your :ref:`fiscal localization package `." msgstr "" -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:18 -msgid ":ref:`automatically applied, based on some rules `" +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:25 +msgid "Tax and account mapping" msgstr "" -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:19 -msgid ":ref:`manually applied on a transaction `" -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:20 -msgid ":ref:`assigned to a partner, on its contact form `" -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:23 -msgid "A few Fiscal Positions are already preconfigured on your database, as part of your :ref:`fiscal localization package `." +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:27 +msgid "To edit or create a fiscal position, go to :menuselection:`Accounting --> Configuration --> Fiscal Positions`, and open the entry to modify or click on :guilabel:`New`." msgstr "" #: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:30 -msgid "Tax and Account Mapping" +msgid "The mapping of taxes and accounts is based on the default taxes and accounts defined in the product form." msgstr "" -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:32 -msgid "To edit or create a Fiscal Position, go to :menuselection:`Accounting --> Configuration --> Fiscal Positions`, and open the entry you want to modify or click on *Create*." +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:33 +msgid "To map to another tax or account, fill out the right column (:guilabel:`Tax to Apply`/ :guilabel:`Account to Use Instead`)." msgstr "" -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:35 -msgid "The mapping of taxes and accounts is based on the default taxes and accounts defined in the products' forms." +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:-1 +msgid "Example of a fiscal position's tax mapping" msgstr "" -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:38 -msgid "To map to another tax or account, fill out the right column (**Tax to Apply**/**Account to Use Instead**)." -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:40 -msgid "To remove a tax, rather than replacing it with another, leave the field **Tax to Apply** empty." -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:41 -msgid "To replace a tax with multiple other taxes, add multiple lines with the same **Tax on Product**." +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:-1 +msgid "Example of a fiscal position's account mapping" msgstr "" #: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:44 +msgid "To remove a tax, leave the field :guilabel:`Tax to Apply` empty." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:45 +msgid "To replace a tax with several other taxes, add multiple lines using the same :guilabel:`Tax on Product`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:49 msgid "The mapping only works with *active* taxes. Therefore, make sure they are active by going to :menuselection:`Accounting --> Configuration --> Taxes`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:50 -msgid "Automatic application" -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:52 -msgid "You can configure your Fiscal Positions to be applied automatically, following a set of conditions." -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:54 -msgid "To do so, open the Fiscal Position you want to modify and click on **Detect Automatically**. You can configure a few conditions:" -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:57 -msgid "**VAT Required**: The VAT number *must* be indicated in the customer's contact form." -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:58 -msgid "**Country Group** / **Country**: The Fiscal Position is applied to these countries." -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:-1 -msgid "Example of settings to apply a Fiscal Position automatically" -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:65 -msgid "Taxes on **eCommerce orders** are automatically updated once the visitor has logged in or filled out their billing details." -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:69 -msgid "The Fiscal Positions' **sequence** - the order in which they are arranged - defines which Fiscal Position to apply if the conditions are met in multiple Fiscal Positions." -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:72 -msgid "For example, if the first Fiscal Position targets *country A*, and the second Fiscal Position targets a *Country Group* that also comprises *country A*, only the first Fiscal Position will be applied to customers from *country A*." -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:79 +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:53 msgid "Application" msgstr "" -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:84 -msgid "Assign a Fiscal Position to a partner" +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:58 +msgid "Automatic application" msgstr "" -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:86 -msgid "You can manually define which Fiscal Position must be used by default for a specific partner." +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:60 +msgid "To automatically apply a fiscal position following a set of conditions, go to :menuselection:`Accounting --> Configuration --> Fiscal Positions`, open the fiscal position to modify, and tick :guilabel:`Detect Automatically`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:88 -msgid "To do so, open the partner's contact form, go to the **Sales & Purchase** tab, edit the **Fiscal Position** field, and click on *Save*." +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:64 +msgid "From there, several conditions can be activated:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:66 +msgid ":guilabel:`VAT Required`: the customer's VAT number must be present on their contact form." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:67 +msgid ":guilabel:`Country Group` and :guilabel:`Country`: the fiscal position is only applied to the selected country or country group." msgstr "" #: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:-1 -msgid "Selection of a Fiscal Position on a Sales Order / Invoice / Bill in Odoo Accounting" +msgid "Example of a fiscal position automatic application settings" msgstr "" -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:98 -msgid "Choose Fiscal Positions manually on Sales Orders, Invoices, and Bills" +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:75 +msgid "Taxes on **eCommerce orders** are automatically updated once the customer has logged in or filled out their billing details." msgstr "" -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:100 -msgid "To manually select which Fiscal Position to use for a new Sales Order, Invoice, or Bill, go to the **Other Info** tab and select the right **Fiscal Position** *before* adding product lines." +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:79 +msgid "The fiscal positions' **sequence** defines which fiscal position is applied if all conditions set on multiple fiscal positions are met simultaneously." msgstr "" -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:110 -msgid ":doc:`taxcloud` (decommissioning TaxCloud integration in Odoo 17+)" +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:82 +msgid "For example, suppose the first fiscal position in a sequence targets *country A* while the second fiscal position targets a *country group* that comprises *country A*. In that case, only the first fiscal position will be applied to customers from *country A*." msgstr "" -#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:111 +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:89 +msgid "Manual application" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:91 +msgid "To manually select a fiscal position, open a sales order, invoice, or bill, go to the :guilabel:`Other Info` tab and select the desired :guilabel:`Fiscal Position` before adding product lines." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:-1 +msgid "Selection of a fiscal position on a sales order, invoice, or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:102 +msgid "Assign to a partner" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:104 +msgid "To define which fiscal position must be used by default for a specific partner, go to :menuselection:`Accounting --> Customers --> Customers`, select the partner, open the :guilabel:`Sales & Purchase` tab, and select the :guilabel:`Fiscal Position`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:-1 +msgid "Selection of a fiscal position on a customer" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:115 +msgid ":doc:`taxcloud`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:116 msgid ":doc:`B2B_B2C`" msgstr "" @@ -10837,7 +11188,6 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:8 #: ../../content/applications/finance/fiscal_localizations/chile.rst:8 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:20 msgid "Below you can find videos with a general description of the localization, and how to configure it." msgstr "" @@ -10850,9 +11200,8 @@ msgid "`VIDEO WEBINAR ECOMMERCE `_. msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:17 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:23 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:24 #: ../../content/applications/finance/fiscal_localizations/germany.rst:61 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:57 msgid "Modules installation" msgstr "" @@ -10861,7 +11210,7 @@ msgid ":ref:`Install ` the following modules to get all the fea msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:28 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:34 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:18 #: ../../content/applications/finance/fiscal_localizations/france.rst:59 #: ../../content/applications/finance/fiscal_localizations/india.rst:18 @@ -10869,9 +11218,8 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:18 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:36 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:16 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:68 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:100 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:124 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:73 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:117 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:17 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:18 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:16 @@ -10927,7 +11275,7 @@ msgid "(optional) Allows the user to see Identification Type and AFIP Responsibi msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:47 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:144 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:137 #: ../../content/applications/finance/fiscal_localizations/peru.rst:43 msgid "Configure your company" msgstr "" @@ -12284,7 +12632,7 @@ msgid "Fiscal reports parameters." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:134 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:533 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:562 #: ../../content/applications/finance/fiscal_localizations/peru.rst:226 msgid "Multicurrency" msgstr "" @@ -13201,71 +13549,71 @@ msgid "Colombia" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:7 -msgid "Odoo's Colombian localization package provides accounting, fiscal and legal features in Colombia such as chart of accounts, taxes and electronic invoicing." +msgid "Odoo's Colombian localization package provides accounting, fiscal, and legal features for databases in Colombia – such as chart of accounts, taxes, and electronic invoicing." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:10 -msgid "In addition, we have a series of videos covering how to start from scratch, configuration, main workflows, and specific use cases." +msgid "In addition, a series of videos on the subject is also available. These videos cover how to start from scratch, set up configurations, complete common workflows, and provide in-depth looks at some specific use cases as well." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:14 -msgid "`Odoo Colombian localization videos `_." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:15 +msgid "`Smart Tutorial - Colombian Localization `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:25 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:26 msgid ":ref:`Install ` the following modules to get all the features of the Colombian localization:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:36 msgid ":guilabel:`Colombia - Accounting`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:36 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:37 msgid "`l10n_co`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:37 -msgid "Default :ref:`fiscal localization package `. This module adds the base accounting features for the Colombian localization: chart of accounts, taxes, withholdings, identification document type." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:40 -msgid ":guilabel:`Colombian - Accounting Reports`" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:38 +msgid "Default :ref:`fiscal localization package `. This module adds the base accounting features for the Colombian localization: chart of accounts, taxes, withholdings, and identification document type." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:41 -msgid "`l10n_co_reports`" +msgid ":guilabel:`Colombian - Accounting Reports`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:42 -msgid "Includes accounting reports for sending certifications to suppliers for withholdings applied." +msgid "`l10n_co_reports`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:43 -msgid ":guilabel:`Electronic invoicing for Colombia with Carvajal`" +msgid "Includes accounting reports for sending certifications to suppliers for withholdings applied." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:44 -msgid "`l10n_co_edi`" +msgid ":guilabel:`Electronic invoicing for Colombia with Carvajal`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:45 -msgid "This module includes the features that are required for the integration with Carvajal and generates the electronic invoices and support document related to the vendor bills based on |DIAN| regulations." +msgid "`l10n_co_edi`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:48 -msgid ":guilabel:`Colombian - Point of Sale`" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:46 +msgid "This module includes the features required for integration with Carvajal, and generates the electronic invoices and support documents related to the vendor bills, based on |DIAN| regulations." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:49 -msgid "`l10n_co_pos`" +msgid ":guilabel:`Colombian - Point of Sale`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:50 -msgid "Includes Point of Sale Receipt for Colombian Localization." +msgid "`l10n_co_pos`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:53 -msgid "When a database is created from scratch selecting :guilabel:`Colombia` as the country, Odoo automatically installs the base modules *Colombia - Accounting* and *Colombia - Accounting Reports*." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:51 +msgid "Includes Point of Sale receipts for Colombian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:54 +msgid "When `Colombia` is selected for a company's :guilabel:`Fiscal Localization`, Odoo automatically installs certain modules." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:58 @@ -13273,254 +13621,360 @@ msgid "Company configuration" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:60 -msgid "To configure your company information, go to the :menuselection:`Contacts` app and search for your company. Alternatively, activate :ref:`developer mode ` and navigate to :menuselection:`General Setting --> Company --> Update Info --> Contact`. Then, edit the contact form to configure the following information:" +msgid "To configure your company information, go to the :menuselection:`Contacts` app, and search for your company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:65 -msgid ":guilabel:`Company Name`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:66 -msgid ":guilabel:`Address`: Including :guilabel:`City`, :guilabel:`Department` and :guilabel:`Zip Code`." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:63 +msgid "Alternatively, activate :ref:`developer mode ` and navigate to :menuselection:`General Setting --> Company --> Update Info --> Contact`. Then, edit the contact form and configure the following information:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:67 -msgid ":guilabel:`Tax ID`: When it is a `NIT`, it must have the *verification digit* at the end of the ID followed by a hyphen (`-`)." +msgid ":guilabel:`Company Name`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:70 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:68 +msgid ":guilabel:`Address`: Including :guilabel:`City`, :guilabel:`Department` and :guilabel:`ZIP` code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:69 +msgid ":guilabel:`Identification Number`: Select the :guilabel:`Identification Type` (`NIT`, `Cédula de Ciudadanía`, `Registro Civil`, etc.). When the :guilabel:`Identification Type` is `NIT`, the :guilabel:`Identification Number` **must** have the *verification digit* at the end of the ID prefixed by a hyphen (`-`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:74 msgid "Next, configure the :guilabel:`Fiscal Information` in the :guilabel:`Sales & Purchase` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:72 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:147 -msgid ":guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company (:guilabel:`O-13` Gran Contribuyente, :guilabel:`O-15` Autorretenedor, :guilabel:`O-23` Agente de retención IVA, :guilabel:`O-47` Regimen de tributación simple, :guilabel:`R-99-PN` No Aplica)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:75 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:150 -msgid ":guilabel:`Gran Contribuyente`: If the company is *Gran Contribuyente* this option should be selected." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:77 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:152 -msgid ":guilabel:`Fiscal Regimen`: Select the Tribute Name for the company (:guilabel:`IVA`, :guilabel:`INC`, :guilabel:`IVA e INC`, :guilabel:`No Aplica`)" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:76 +msgid ":guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company (`O-13` Gran Contribuyente, `O-15` Autorretenedor, `O-23` Agente de retención IVA, `O-47` Regimen de tributación simple, `R-99-PN` No Aplica)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:79 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:154 -msgid ":guilabel:`Commercial Name`: If the company uses a specific commercial name, and it needs to be displayed in the invoice." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:173 +msgid ":guilabel:`Gran Contribuyente`: If the company is *Gran Contribuyente* this option should be selected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:81 +msgid ":guilabel:`Fiscal Regimen`: Select the Tribute Name for the company (`IVA`, `INC`, `IVA e INC`, or `No Aplica`)" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:83 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:177 +msgid ":guilabel:`Commercial Name`: If the company uses a specific commercial name, and it needs to be displayed in the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:87 msgid "Carjaval credentials configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:85 -msgid "Once the modules installed, the user credentials must be configured in order to connect with Carvajal Web Service. Navigate to :menuselection:`Accounting --> Configuration --> Settings` and scroll to the :guilabel:`Colombian Electronic Invoicing` section. Then, fill in the required configuration information provided by Carvajal:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:90 -msgid ":guilabel:`Username` and :guilabel:`Password`: Correspond to the username and password provided by Carvajal to the company." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:92 -msgid ":guilabel:`Company Registry`: Company's NIT number *without* the verification code." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:93 -msgid ":guilabel:`Account ID`: Company ID followed by `_01`." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:89 +msgid "Once the modules are installed, the user credentials **must** be configured, in order to connect with Carvajal Web Service. To do so, navigate to :menuselection:`Accounting --> Configuration --> Settings` and scroll to the :guilabel:`Colombian Electronic Invoicing` section. Then, fill in the required configuration information provided by Carvajal:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:94 -msgid ":guilabel:`Colombia Template Code`: Select one of the two available templates (:guilabel:`CGEN03` or :guilabel:`CGNE04`) to be used in the PDF format of the electronic invoice." +msgid ":guilabel:`Username` and :guilabel:`Password`: Username and password (provided by Carvajal) to the company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:96 +msgid ":guilabel:`Company Registry`: Company's NIT number *without* the verification code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:97 +msgid ":guilabel:`Account ID`: Company's NIT number followed by `_01`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:98 +msgid ":guilabel:`Colombia Template Code`: Select one of the two available templates (`CGEN03` or `CGNE04`) to be used in the PDF format of the electronic invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:101 +msgid "Enable the :guilabel:`Test mode` checkbox to connect with the Carvajal testing environment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:103 +msgid "Once Odoo and Carvajal are fully configured and ready for production, deactivate the :guilabel:`Test mode` checkbox to use the production database." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 msgid "Configure credentials for Carvajal web service in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:101 -msgid "Check the :guilabel:`Test mode` checkbox to connect with the Carvajal testing environment. Once Odoo and Carvajal are fully configured and ready for production, uncheck the :guilabel:`Test mode` checkbox to use the production database." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:106 -msgid ":guilabel:`Test mode` must be used **only** on replicated databases, **not** the production environment." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:110 -msgid "Report data configuration" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:112 -msgid "Report data can be defined for the fiscal section and bank information of the PDF as part of the configurable information sent in the XML." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:111 +msgid ":guilabel:`Test mode` must **only** be used on duplicated databases, **not** the production environment." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:115 -msgid "Navigate to :menuselection:`Accounting --> Configuration --> Settings` and scroll to the :guilabel:`Colombian Electronic Invoicing` section." +msgid "Report data configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:121 -msgid "Master data configuration" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:117 +msgid "Report data can be defined for the fiscal section and bank information of the PDF as part of the configurable information sent in the XML." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:120 +msgid "Navigate to :menuselection:`Accounting --> Configuration --> Settings`, and scroll to the :guilabel:`Colombian Electronic Invoicing` section, in order to find the :guilabel:`Report Configuration` fields. Here the header information for each report type can be configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:124 +msgid ":guilabel:`Gran Contribuyente`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:125 +msgid ":guilabel:`Tipo de Régimen`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:126 +msgid ":guilabel:`Retenedores de IVA`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:127 -msgid "Identification information" +msgid ":guilabel:`Autorretenedores`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:128 +msgid ":guilabel:`Resolución Aplicable`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:129 -msgid "Document types defined by the |DIAN| are available on the partner form as part of the Colombian localization. Colombian partners must have their :guilabel:`Identification Number` (VAT) and :guilabel:`Document Type` set." +msgid ":guilabel:`Actividad Económica`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:134 -msgid "When the :guilabel:`Document Type` is `NIT`, the :guilabel:`Identification Number` needs to be configured in Odoo, including the *verification digit*; Odoo splits this number when the data to is sent to the third party." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:130 +msgid ":guilabel:`Bank Information`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:139 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:135 +msgid "Master data configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:140 +msgid "Partner contacts can be created in the *Contacts* app. To do so, navigate to :menuselection:`Contacts`, and click the :guilabel:`Create` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:143 +msgid "Then, name the contact, and using the radio buttons, select the contact type, either :guilabel:`Individual` or :guilabel:`Company`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:146 +msgid "Complete the full :guilabel:`Address`, including the :guilabel:`City`, :guilabel:`State`, and :guilabel:`ZIP` code. Then, complete the identification and fiscal information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:150 +msgid "Identification information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:152 +msgid "Identification types, defined by the |DIAN|, are available on the partner form, as part of the Colombian localization. Colombian partners **must** have their :guilabel:`Identification Number` (VAT) and :guilabel:`Document Type` set." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:157 +msgid "When the :guilabel:`Document Type` is `NIT`, the :guilabel:`Identification Number` needs to be configured in Odoo, including the *verification digit at the end of the ID, prefixed by a hyphen (`-`)*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:162 msgid "Fiscal information" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:141 -msgid "The partner's responsibility codes (section 53 in the RUT document) are included as part of the electronic invoicing module, as it is required by the |DIAN|." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:144 -msgid "The required fields can be found under :menuselection:`Partner --> Sales & Purchase Tab --> Fiscal Information`:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:158 -#: ../../content/applications/finance/fiscal_localizations/egypt.rst:172 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:246 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:662 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:771 -msgid "Products" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:160 -msgid "In addition to adding general information (in the :guilabel:`General Information` tab) on the product form, either the :guilabel:`UNSPSC Category`, :guilabel:`Barcode`, or :guilabel:`Internal Reference` field must also be configured." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:164 +msgid "The partner's responsibility codes (section 53 in the :abbr:`RUT (Registro único tributario)` document) are included as part of the electronic invoicing module, as it is required by the |DIAN|." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:167 -msgid "If sales transactions include products with taxes, the :guilabel:`Value Type` field in the :guilabel:`Advanced Options` tab needs to be configured per tax. To do so, go to :menuselection:`Accounting --> Configuration --> Taxes`, and select the related tax." +msgid "The required fields can be found under :menuselection:`Partner --> Sales & Purchase Tab --> Fiscal Information section`:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:171 -msgid "Retention tax types (:guilabel:`ICA`, :guilabel:`IVA`, :guilabel:`Fuente`) are also included. This configuration is used to display taxes in the invoice PDF correctly." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:170 +msgid ":guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company (`O-13` Gran Contribuyente, `O-15` Autorretenedor, `O-23` Agente de retención IVA, `O-47` Regimen de tributación simple, or `R-99-PN` No Aplica)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:175 +msgid ":guilabel:`Fiscal Regimen`: Select the tribute name for the company (`IVA`, `INC`, `IVA e INC`, or `No Aplica`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:181 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:172 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:251 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:700 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:817 +msgid "Products" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:183 +msgid "To manage products, navigate to :menuselection:`Accounting --> Customers --> Products`, then click on a product." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:186 +msgid "When adding general information on the product form, it is required that either the :guilabel:`UNSPSC Category` (:guilabel:`Accounting` tab), or :guilabel:`Internal Reference` (:guilabel:`General Information` tab) field is configured. Be sure to :guilabel:`Save` the product once configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:194 +msgid "To create or modify taxes, go to :menuselection:`Accounting --> Configuration --> Taxes`, and select the related tax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:197 +msgid "If sales transactions include products with taxes, the :guilabel:`Value Type` field in the :guilabel:`Advanced Options` tab needs to be configured per tax. Retention tax types (:guilabel:`ICA`, :guilabel:`IVA`, :guilabel:`Fuente`) are also included. This configuration is used to display taxes correctly in the invoice PDF." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 msgid "The ICA, IVA and Fuente fields in the Advanced Options tab in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:178 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:209 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:91 msgid "Sales journals" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:182 -msgid "Once the |DIAN| has assigned the official sequence and prefix for the electronic invoice resolution, the sales journals related to the invoice documents must be updated in Odoo. To do so, navigate to :menuselection:`Accounting --> Configuration --> Journals`." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:211 +msgid "Once the |DIAN| has assigned the official sequence and prefix for the electronic invoice resolution, the sales journals related to the invoice documents **must** be updated in Odoo. To do so, navigate to :menuselection:`Accounting --> Configuration --> Journals`, and select an existing sales journal, or create a new one with the :guilabel:`Create` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:186 -msgid "Configure the following data in the :guilabel:`Advanced Settings` tab:" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:216 +msgid "On the sales journal form, input the :guilabel:`Journal Name`, :guilabel:`Type`, and set a unique :guilabel:`Short Code` in the :guilabel:`Journals Entries` tab. Then, configure the following data in the :guilabel:`Advanced Settings` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:188 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:220 msgid ":guilabel:`Electronic invoicing`: Enable :guilabel:`UBL 2.1 (Colombia)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:189 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:221 msgid ":guilabel:`Invoicing Resolution`: Resolution number issued by |DIAN| to the company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:190 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:222 msgid ":guilabel:`Resolution Date`: Initial effective date of the resolution." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:191 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:223 msgid ":guilabel:`Resolution end date`: End date of the resolution's validity." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:192 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:224 msgid ":guilabel:`Range of Numbering (minimum)`: First authorized invoice number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:193 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:225 msgid ":guilabel:`Range of Numbering (maximum)`: Last authorized invoice number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:196 -msgid "The sequence and resolution of the journal must match the one configured in Carvajal and the |DIAN|." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:228 +msgid "The sequence and resolution of the journal **must** match the one configured in Carvajal and the |DIAN|." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:200 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:232 msgid "Invoice sequence" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:202 -msgid "The invoice sequence and prefix must be correctly configured when the first document is created." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:205 -msgid "Odoo automatically assigns a prefix and sequence to the following documents." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:208 -msgid "Purchase journals" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:210 -msgid "Once the |DIAN| has assigned the official sequence and prefix for the support document related to vendor bills, the purchase journals related to their supporting documents need to be updated in Odoo. The process is similar to the configuration of the :ref:`sales journals `." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:217 -msgid "The :doc:`chart of accounts ` is installed by default as part of the localization module, the accounts are mapped automatically in taxes, default account payable, and default account receivable. The chart of accounts for Colombia is based on the PUC (Plan Unico de Cuentas)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:226 -msgid "Main workflows" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:229 -msgid "Electronic invoices" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:234 +msgid "The invoice sequence and prefix **must** be correctly configured when the first document is created." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:237 -msgid "The functional workflow taking place before an invoice validation does not alter the main changes introduced with the electronic invoice." +msgid "Odoo automatically assigns a prefix and sequence to the following invoices." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:240 -msgid "Electronic invoices are generated and sent to both the |DIAN| and customer through Carvajal's web service integration. These documents can be created from your sales order or manually. Go to :menuselection:`Accounting --> Customers --> Invoices` and configure:" +msgid "Purchase journals" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:244 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:242 +msgid "Once the |DIAN| has assigned the official sequence and prefix for the *support document* related to vendor bills, the purchase journals related to their supporting documents need to be updated in Odoo. The process is similar to the configuration of the :ref:`sales journals `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:249 +msgid "The :doc:`chart of accounts ` is installed by default as part of the localization module, the accounts are mapped automatically in taxes, default account payable, and default account receivable. The chart of accounts for Colombia is based on the PUC (Plan Unico de Cuentas)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:257 +msgid "Main workflows" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:260 +msgid "Electronic invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:262 +msgid "The following is a breakdown of the main workflow for electronic invoices with the Colombian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:265 +msgid "Sender creates an invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:266 +msgid "Electronic invoice provider generates the legal XML file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:267 +msgid "Electronic invoice provider creates the CUFE (Invoice Electronic Code) with the electronic signature." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:269 +msgid "Electronic invoice provider sends a notification to |DIAN|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:270 +msgid "|DIAN| validates the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:271 +msgid "|DIAN| accepts or rejects the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:272 +msgid "Electronic invoice provider generates the PDF invoice with a QR code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:273 +msgid "Electronic invoice provider sends invoice to the acquirer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:274 +msgid "Acquirer sends a receipt of acknowledgement, and accepts or rejects the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:275 +msgid "Sender downloads a :file:`.zip` file with the PDF and XML." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 +msgid "Electronic invoice workflow for Colombian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:287 +msgid "The functional workflow taking place before an invoice validation does **not** alter the main changes introduced with the electronic invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:290 +msgid "Electronic invoices are generated and sent to both the |DIAN| and customer through Carvajal's web service integration. These documents can be created from your sales order or manually generated. To create a new invoice, go to :menuselection:`Accounting --> Customers --> Invoices`, and select :guilabel:`Create`. On the invoice form configure the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:295 msgid ":guilabel:`Customer`: Customer's information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:245 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:296 msgid ":guilabel:`Journal`: Journal used for electronic invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:246 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:297 msgid ":guilabel:`Electronic Invoice Type`: Select the type of document. By default, :guilabel:`Factura de Venta` is selected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:248 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:299 msgid ":guilabel:`Invoice Lines`: Specify the products with the correct taxes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:250 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:301 msgid "When done, click :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:255 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:306 #: ../../content/applications/finance/fiscal_localizations/india.rst:117 #: ../../content/applications/finance/fiscal_localizations/india.rst:262 #: ../../content/applications/finance/fiscal_localizations/peru.rst:385 msgid "Invoice validation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:257 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:308 msgid "After the invoice confirmation, an XML file is created and sent automatically to Carvajal. The invoice is then processed asynchronously by the E-invoicing service UBL 2.1 (Colombia). The file is also displayed in the chatter." msgstr "" @@ -13528,148 +13982,148 @@ msgstr "" msgid "Carvajal XML invoice file in Odoo chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:264 -msgid "The :guilabel:`Electronic Invoice Name` field is now displayed in the :guilabel:`EDI Documents` tab with the name of the XML file. Additionally, the :guilabel:`Electronic Invoice Status` field is displayed with the initial value :guilabel:`To Send`. To process the invoice manually, click on the :guilabel:`Process Now` button." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:316 +msgid "The :guilabel:`Electronic Invoice Name` field is now displayed in the :guilabel:`EDI Documents` tab, with the name of the XML file. Additionally, the :guilabel:`Electronic Invoice Status` field is displayed with the initial value :guilabel:`To Send`. To process the invoice manually, click on the :guilabel:`Process Now` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:272 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:324 msgid "Reception of legal XML and PDF" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:274 -msgid "The electronic invoice vendor (Carvajal) receives the XML file and proceeds to validate its structure and information." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:326 +msgid "The electronic invoice vendor (Carvajal) receives the XML file, and proceeds to validate its structure and information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:277 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:329 msgid "After validating the electronic invoice, proceed to generate a legal XML which includes a digital signature and a unique code (CUFE), a PDF invoice that includes a QR code and the CUFE is also generated. If everything is correct the :guilabel:`Electronic Invoicing` field value changes to :guilabel:`Sent`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:282 -msgid "A ZIP containing the legal electronic invoice in XML format and the invoice in PDF format is downloaded and displayed in the invoice chatter:" +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:334 +msgid "A :file:`.zip` containing the legal electronic invoice (in XML format) and the invoice in (PDF format) is downloaded and displayed in the invoice chatter:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:-1 msgid "ZIP file displayed in the invoice chatter in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:288 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:341 msgid "The electronic invoice status changes to :guilabel:`Accepted`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:291 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:335 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:348 msgid "Credit notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:293 -msgid "The process for credit notes is the same as for invoices. To create a credit note with reference to an invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the invoice, click :guilabel:`Add Credit Note` and complete the following information:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:297 -msgid ":guilabel:`Credit Method`: Select the type of credit method." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:299 -msgid ":guilabel:`Partial Refund`: Use this option when it is a partial amount." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:300 -msgid ":guilabel:`Full Refund`: Use this option if the credit note is for the full amount." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:301 -msgid ":guilabel:`Full refund and new draft invoice`: Use this option if the credit note is auto-validated and reconciled with the invoice. The original invoice is duplicated as a new draft." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:305 -msgid ":guilabel:`Reason`: Enter the reason for the credit note." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:306 -msgid ":guilabel:`Reversal Date`: Select if you want a specific date for the credit note or if it is the journal entry date." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:308 -msgid ":guilabel:`Use Specific Journal`: Select the journal for your credit note or leave it empty if you want to use the same journal as the original invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:310 -msgid ":guilabel:`Refund Date`: If you chose a specific date, select the date for the refund." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:312 -msgid "Once reviewed, click the :guilabel:`Reverse` button." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:315 -msgid "Debit notes" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:317 -msgid "The process for debit notes is similar to credit notes. To create a debit note with reference to an invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the invoice, click the :guilabel:`Add Debit Note` button and complete the following information:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:321 -msgid ":guilabel:`Reason`: Type the reason for the debit note." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:322 -msgid ":guilabel:`Debit note date`: Select the specific options." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:323 -msgid ":guilabel:`Copy lines`: Select this option if you need to register a debit note with the same lines of invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:325 -msgid ":guilabel:`Use Specific Journal`: Select the printer point for your debit note, or leave it empty if you want to use the same journal as the original invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:328 -msgid "When done, click :guilabel:`Create Debit Note`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:331 -msgid "Support document for vendor bills" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:333 -msgid "With master data, credentials, and the purchase journal configured for support documents related to vendor bills, you can start using support documents." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:336 -msgid "Support documents for vendor bills can be created from your purchase order or manually. Go to :menuselection:`Accounting --> Vendors --> Bills` and fill in the following data:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:339 -msgid ":guilabel:`Vendor`: Enter the vendor's information." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:340 -msgid ":guilabel:`Bill Date`: Select the date of the bill." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:341 -msgid ":guilabel:`Journal`: Select the journal for support documents related to the vendor bills." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:342 -msgid ":guilabel:`Invoiced Lines`: Specify the products with the correct taxes." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 -msgid "Once reviewed, click the :guilabel:`Confirm` button. Upon confirmation, an XML file is created and automatically sent to Carvajal." +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:346 +msgid "The process for credit notes is the same as for invoices. To create a credit note with reference to an invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the invoice, click :guilabel:`Add Credit Note`, and complete the following information:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:350 -msgid "Common errors" +msgid ":guilabel:`Credit Method`: Select the type of credit method." msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:352 +msgid ":guilabel:`Partial Refund`: Use this option when it is a partial amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:353 +msgid ":guilabel:`Full Refund`: Use this option if the credit note is for the full amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:354 +msgid ":guilabel:`Full refund and new draft invoice`: Use this option if the credit note is auto-validated and reconciled with the invoice. The original invoice is duplicated as a new draft." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:358 +msgid ":guilabel:`Reason`: Enter the reason for the credit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:359 +msgid ":guilabel:`Reversal Date`: Select if you want a specific date for the credit note or if it is the journal entry date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:361 +msgid ":guilabel:`Use Specific Journal`: Select the journal for your credit note or leave it empty if you want to use the same journal as the original invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:363 +msgid ":guilabel:`Refund Date`: If you chose a specific date, select the date for the refund." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:365 +msgid "Once reviewed, click the :guilabel:`Reverse` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:368 +msgid "Debit notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:370 +msgid "The process for debit notes is similar to credit notes. To create a debit note with reference to an invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the invoice, click the :guilabel:`Add Debit Note` button, and enter the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:374 +msgid ":guilabel:`Reason`: Type the reason for the debit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:375 +msgid ":guilabel:`Debit note date`: Select the specific options." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:376 +msgid ":guilabel:`Copy lines`: Select this option if you need to register a debit note with the same lines of invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:378 +msgid ":guilabel:`Use Specific Journal`: Select the printer point for your debit note, or leave it empty if you want to use the same journal as the original invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:381 +msgid "When done, click :guilabel:`Create Debit Note`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:384 +msgid "Support document for vendor bills" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:386 +msgid "With master data, credentials, and the purchase journal configured for support documents related to vendor bills, you can start using *support documents*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:389 +msgid "Support documents for vendor bills can be created from your purchase order or manually. Go to :menuselection:`Accounting --> Vendors --> Bills` and fill in the following data:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:392 +msgid ":guilabel:`Vendor`: Enter the vendor's information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:393 +msgid ":guilabel:`Bill Date`: Select the date of the bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:394 +msgid ":guilabel:`Journal`: Select the journal for support documents related to the vendor bills." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:395 +msgid ":guilabel:`Invoiced Lines`: Specify the products with the correct taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:397 +msgid "Once reviewed, click the :guilabel:`Confirm` button. Upon confirmation, an XML file is created and automatically sent to Carvajal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:403 +msgid "Common errors" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:405 msgid "During the XML validation, the most common errors are related to missing master data (*Contact Tax ID*, *Address*, *Products*, *Taxes*). In such cases, error messages are shown in the chatter after updating the electronic invoice status." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:356 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:409 msgid "After the master data is corrected, it's possible to reprocess the XML with the new data and send the updated version, using the :guilabel:`Retry` button." msgstr "" @@ -13677,11 +14131,11 @@ msgstr "" msgid "XML validation errors shown in the invoice chatter in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:368 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:421 msgid "Certificado de Retención en ICA" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:370 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:423 msgid "This report is a certification to vendors for withholdings made for the Colombian Industry and Commerce (ICA) tax. The report can be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención en ICA`." msgstr "" @@ -13689,11 +14143,11 @@ msgstr "" msgid "Certificado de Retención en ICA report in Odoo Accounting." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:378 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:432 msgid "Certificado de Retención en IVA" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:380 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:434 msgid "This report issues a certificate on the amount withheld from vendors for VAT withholding. The report can be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención en IVA`." msgstr "" @@ -13701,11 +14155,11 @@ msgstr "" msgid "Certificado de Retención en IVA report in Odoo Accounting." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:388 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:443 msgid "Certificado de Retención en la Fuente" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:390 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:445 msgid "This certificate is issued to partners for the withholding tax that they have made. The report can be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención en Fuente`." msgstr "" @@ -16853,1290 +17307,1294 @@ msgstr "" msgid "Mexico" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:22 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:20 +msgid "A video on the Mexican localization is also available. This video covers how to implement this localization from scratch, including how to set up the configurations, how to complete common workflows, and provides an in-depth look at several specific use cases, as well." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:24 msgid "`Video webinar of a complete demo `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:27 -msgid "Odoo users in Mexico have access to a set of modules that allow them to sign electronic invoices according to the specifications of the |SAT| for `version 4.0 of the CFDI `_ , a legal requirement as of January 1, 2022." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:29 +msgid "The Odoo Mexican localization modules allow for the signing of electronic invoices, according to the specifications of the |SAT| for `version 4.0 of the CFDI `_, a legal requirement, as of January 1, 2022. These modules also add relevant accounting reports (such as: the |DIOT|, enables foreign trade, and the creation of delivery guides)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:32 -msgid "These modules also add relevant accounting reports (such as the |DIOT|, enable foreign trade, and the creation of delivery guides)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:36 +msgid "In order to electronically sign any documents in Odoo, ensure the *Sign* application is installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:39 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:43 msgid "Requirements" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:41 -msgid "Before making the necessary configurations to have the Mexican localization installed in Odoo, it is necessary to meet the following requirements:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:45 +msgid "It is necessary to meet the following requirements before configuring the Mexican localization modules in Odoo:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:46 -msgid "Be registered in the |SAT|, with a valid :abbr:`RFC (Registro Federal de Contribuyentes)`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:50 +msgid "Be registered in the |SAT|, with a valid |RFC|." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:47 -msgid "Have a `Certificate of Digital Seal `_ (CSD)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:49 -msgid "Choose a PAC (Proveedor Autorizado de Certificación / Authorized Certification Provider). Currently, Odoo works with the following |PAC|\\s: `Solución Factible `_, `Quadrum (formerly Finkok) `_ and `SW Sapien - Smarter Web `_." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:51 +msgid "Have a `Certificate of Digital Seal `_ (CSD)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:53 -msgid "Have knowledge and experience with billing, sales, and accounting in Odoo. This documentation contains only the necessary information to use Odoo." +msgid "Choose a PAC (Proveedor Autorizado de Certificación / Authorized Certification Provider). Currently, Odoo works with the following |PAC|\\s: `Solución Factible `_, `Quadrum (formerly Finkok) `_ and `SW Sapien - Smarter Web `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:59 -msgid ":ref:`Install ` the following modules to get the main features of the Mexican localization:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:57 +msgid "Have knowledge and experience with billing, sales, and accounting in Odoo. This documentation **only** contains the necessary information needed to use Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:69 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:61 +msgid "Installing modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:63 +msgid ":ref:`Install ` the following modules to get all the features of the Mexican localization. The :doc:`Accounting <../accounting>` and *Contacts* modules are required to be installed for this configuration:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:74 msgid ":guilabel:`Mexico - Accounting`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:70 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:75 msgid "`l10n_mx`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:71 -msgid "The default :doc:`fiscal localization package `, adds accounting characteristics for the Mexican localization, such as the most common taxes and the chart of accounts based on `the SAT account grouping code `_." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:76 +msgid "The default :doc:`fiscal localization package <../fiscal_localizations>`, adds accounting characteristics for the Mexican localization, such as: the most common taxes and the chart of accounts – based on `the SAT account grouping code `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:75 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:80 msgid ":guilabel:`EDI for Mexico`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:76 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:81 msgid "`l10n_mx_edi`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:77 -msgid "Includes all the technical and functional requirements to generate and validate :doc:`Electronics Documents `, based on the technical documentation published by the SAT. This allows you to send invoices (with or without addendas) and payment complements to the government." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:82 +msgid "Includes all the technical and functional requirements to generate and validate :doc:`Electronics Documents <../accounting/customer_invoices/electronic_invoicing>` — based on the technical documentation published by the |SAT|. This allows you to send invoices (with or without addedums) and payment complements to the government." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:82 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:86 msgid ":guilabel:`EDI v4.0 for Mexico`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:83 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:87 msgid "`l10n_mx_edi_40`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:84 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:88 msgid "Necessary to create XML documents with the correct specifications of the CFDI 4.0." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:87 -msgid "When you install a database from scratch by selecting :guilabel:`Mexico` as the country, Odoo automatically installs the following modules: :guilabel:`Mexico - Accounting`, :guilabel:`EDI for Mexico`, and :guilabel:`EDI v4.0 for Mexico`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:91 -msgid "The following modules are needed to add Mexico's Electronic Accounting. They require the :doc:`Accounting ` module to be installed." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:101 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:89 msgid ":guilabel:`Odoo Mexican Localization Reports`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:102 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:90 msgid "`l10n_mx_reports`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:103 -msgid "Adapts reports for Mexico's Electronic Accounting: Chart of Accounts, Trial Balance, and DIOT." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:91 +msgid "Adapts reports for Mexico's Electronic Accounting: Chart of Accounts, Trial Balance, and |DIOT|." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:105 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:93 msgid ":guilabel:`Mexico - Localization Reports for Closing`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:106 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:94 msgid "`l10n_mx_reports_closing`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:107 -msgid "Necessary to create the Closing Entry (Also known as the month 13th move)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:95 +msgid "Necessary to create the Closing Entry (Also known as the *month 13th move*)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:108 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:96 msgid ":guilabel:`Odoo Mexican XML Polizas Export`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:109 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:97 msgid "`l10n_mx_xml_polizas`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:110 -msgid "Lets you export XML files of your Journal Entries for a compulsory audit." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:98 +msgid "Allows the export of XML files of Journal Entries for a compulsory audit." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:111 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:99 msgid ":guilabel:`Odoo Mexican XML Polizas Export Edi bridge`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:112 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:100 msgid "`l10n_mx_xml_polizas_edi`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:113 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:101 msgid "Complements the module `l10n_mx_xml_polizas`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:115 -msgid "The following modules are optional. It's recommended to install them *only* if you meet a specific requirement. Make sure that they are needed for your business." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:104 +msgid "When installing a database from scratch and selecting :guilabel:`Mexico` as the country, Odoo automatically installs the following modules: :guilabel:`Mexico - Accounting`, :guilabel:`EDI for Mexico`, and :guilabel:`EDI v4.0 for Mexico`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:125 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:108 +msgid "The following modules are optional. It's recommended to install them *only* if meeting a specific requirement. Make sure that they are needed for the business." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:118 msgid ":guilabel:`EDI for Mexico (Advanced Features)`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:126 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:119 msgid "`l10n_mx_edi_extended`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:127 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:120 msgid "Adds the external trade complement to invoices: A legal requirement for selling products to foreign countries." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:129 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:122 msgid ":guilabel:`EDI v4.0 for Mexico (COMEX)`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:130 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:123 msgid "`l10n_mx_edi_extended_40`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:131 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:124 msgid "Adapts the module `l10n_mx_edi_extended` for CFDI 4.0." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:132 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:125 msgid ":guilabel:`Mexico - Electronic Delivery Guide`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:133 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:126 msgid "`l10n_mx_edi_stock`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:134 -msgid "Lets you create a \"Carta Porte\": a bill of lading that proves to the government you are sending goods between A & B with a signed electronic document." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:127 +msgid "Lets you create a *Carta Porte*: A bill of lading that proves to the government you are sending goods between A & B with a signed electronic document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:136 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:129 msgid ":guilabel:`Electronic Delivery Guide for Mexico CFDI 4.0`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:137 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:130 msgid "`l10n_mx_edi_stock_40`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:138 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:131 msgid "Adapts the module `l10n_mx_edi_stock` for CFDI 4.0" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:139 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:132 msgid ":guilabel:`Odoo Mexico Localization for Stock/Landing`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:140 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:133 msgid "`l10n_mx_edi_landing`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:141 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:134 msgid "Allows managing customs numbers related to landed costs in electronic documents." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:139 +msgid "After installing the correct modules, the next step is to verify that your company is configured with the correct data. To do so, go to :menuselection:`Settings --> General Settings --> Companies`, and select :guilabel:`Update Info` under your company name." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:143 +msgid "Enter the full :guilabel:`Address` in the resulting form, including: :guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and |RFC| (:guilabel:`VAT` number)." +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/mexico.rst:146 -msgid "After installing the correct modules, you must verify that the company is configured with the correct data. To do so, go to :menuselection:`Settings --> General Settings --> Companies` and select :guilabel:`Update Info` under your company name." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:150 -msgid "Enter your full :guilabel:`Address` in the resulting form including :guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and RFC (:guilabel:`VAT` number)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:153 -msgid "According to the requirements of the CFDI 4.0, the name of your main contact must coincide to your business name registered in the SAT without the legal entity abbreviation." +msgid "According to the requirements of the CFDI 4.0, the name of the main company contact **must** coincide with your business name registered in the |SAT|, without the legal entity abbreviation." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Requirements for a correct invoicing." +msgid "Main company contact requirements for a correct invoicing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:160 -msgid "From a legal point of view, a Mexican company must use the local currency (MXN). Therefore, Odoo does not provide features to manage an alternative configuration. If you want to manage another currency, let MXN be the default currency and use a :doc:`pricelist ` instead." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:154 +msgid "From a legal point of view, a Mexican company **must** use the local currency (MXN). Therefore, Odoo does not provide features to manage an alternative configuration. If you want to manage another currency, let MXN be the default currency and use a :doc:`pricelist <../../sales/sales/products_prices/prices/pricing>`, instead." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:165 -msgid "Next, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX) --> Fiscal Regime`, and select the regime that applies to your company from the drop-down list." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:159 +msgid "Next, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX) --> Fiscal Regime`, then select the regime that applies to your company from the drop-down list, and click :guilabel:`Save`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Fiscal regime configuration." +msgid "Fiscal regime configuration in the Accounting settings." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:172 -msgid "If you want to test the Mexican localization, you can configure the company with a real address within Mexico (including all fields), add `EKU9003173C9` as the :guilabel:`VAT` and `ESCUELA KEMPER URGATE` as the :guilabel:`Company Name`. For the :guilabel:`Fiscal Regime`, use :guilabel:`General de Ley Personas Morales`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:168 +msgid "If you want to test the Mexican localization, the company can be configured with a real address within Mexico (including all fields), and add `EKU9003173C9` as the :guilabel:`VAT` and `ESCUELA KEMPER URGATE` as the :guilabel:`Company Name`. For the :guilabel:`Fiscal Regime`, use :guilabel:`General de Ley Personas Morales`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:178 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:623 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:174 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:653 msgid "Contacts" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:180 -msgid "To create a contact that can be invoiced, go to :menuselection:`Contacts --> Create`. Then enter the contact's name, full :guilabel:`Address` including :guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and RFC (:guilabel:`VAT` number)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:176 +msgid "To create a contact that can be invoiced, go to :menuselection:`Contacts --> Create`. Then, enter the contact name, full :guilabel:`Address` including: :guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and |RFC| (:guilabel:`VAT` number)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:185 -msgid "As with your own company, all of your contacts needs to have their correct business name registered in the |SAT|. This also applies to the :guilabel:`Fiscal Regime` which needs to be added in the :guilabel:`MX EDI` tab." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:181 +msgid "As with your own company, all of your contacts needs to have their correct business name registered in the |SAT|. This also applies to the :guilabel:`Fiscal Regime`, which needs to be added in the :guilabel:`MX EDI` tab." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:192 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:188 msgid "Some additional configurations for factor type and tax objects need to be added to the sales taxes in order to properly sign invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:196 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:192 msgid "Factor type" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:198 -msgid "Go to :menuselection:`Accounting --> Configuration --> Taxes` then enable the :guilabel:`Factor Type` field in the :guilabel:`Advanced Options` tab for all records with the :guilabel:`Tax Type` set as :guilabel:`Sales`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:202 -msgid "This is pre-loaded in the default taxes. If new ones are created, you need to make sure to fill this field." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:194 +msgid "The *Factor Type* field is pre-loaded in the default taxes. If new taxes are created, you need to make sure to configure this field. To do so, go to :menuselection:`Accounting --> Configuration --> Taxes`, then enable the :guilabel:`Factor Type` field in the :guilabel:`Advanced Options` tab for all records, with the :guilabel:`Tax Type` set as :guilabel:`Sales`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Taxes configuration." +msgid "Factor Type Sales tax type configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:209 -msgid "Mexico manages two different kinds of 0% VAT: *0% VAT* and *VAT Exempt*. For the former, select the :guilabel:`Factor Type` :guilabel:`Tasa`. For the latter, use :guilabel:`Exento`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:204 +msgid "Mexico manages two different kinds of 0% VAT to accommodate two scenarios:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:213 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:206 +msgid "*0% VAT* set the :guilabel:`Factor Type` as :guilabel:`Tasa`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:207 +msgid "*VAT Exempt* set the :guilabel:`Factor Type` as :guilabel:`Exento`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:210 msgid "Tax object" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:215 -msgid "One requirement of the CFDI 4.0 is that the resulting XML file needs or does not need to break down the taxes of the operation. There are three different possible values that are added depending on specific configurations:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:212 +msgid "One requirement of the CFDI 4.0 is that the resulting XML file needs (or does not need) to break down the taxes of the operation. There are three different possible values that are added in the XML file:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:216 +msgid "`01`: Not subject to tax - this value is added automatically if your invoice line doesn't contain any taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:218 +msgid "`02`: Subject to tax - this is the default configuration of any invoice line that contains taxes." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:219 -msgid "`01`: Not subject to tax - your invoice must not contain any taxes." +msgid "`03`: Subject to tax and not forced to break down - this value can be triggered on-demand for certain customers to replace the value 02." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:220 -msgid "`02`: Subject to tax - your invoice contains taxes (default configuration)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:221 -msgid "`03`: Subject to tax and not forced to breakdown - your invoice contains taxes, and the contact configuration has the :guilabel:`No Tax Breakdown` checkbox activated." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:222 +msgid "To use the `03` value, navigate to :menuselection:`Contacts --> your customer's invoice --> MX EDI tab`, and activate the :guilabel:`No Tax Breakdown` checkbox." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Tax Breakdown SAT." +msgid "No Tax Breakdown option on the MX EDI tab of the customer's invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:228 -msgid "The :guilabel:`No Tax Breakdown` value applies only to specific fiscal regimes and/or taxes. Consult your accountant first if it is needed for your business before doing any modification." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:230 +msgid "The :guilabel:`No Tax Breakdown` value applies **only** to specific fiscal regimes and/or taxes. Consult your accountant first to see if it is needed for your business before making any modification." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:232 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:235 msgid "Other tax configurations" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:234 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:237 msgid "When registering a payment, Odoo will carry out the movement of taxes from the *Cash Basis Transition Account* to the account set in the :guilabel:`Definition` tab. For such movement, a tax base account will be used: (`Base Imponible de Impuestos en Base a Flujo de Efectivo`) in the journal entry when reclassifying taxes. **Do not delete this account**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:239 -msgid "If you create a new tax, you need to add the correct :guilabel:`Tax Grids` for it (`IVA`, `ISR` or `IEPS`). Odoo only supports these three groups of taxes." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:242 +msgid "If you create a new tax in :menuselection:`Accounting --> Configuration --> Taxes`, you need to add the correct :guilabel:`Tax Grids` for it (`IVA`, `ISR` or `IEPS`). Odoo **only** supports these three groups of taxes." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Taxes accounts." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:248 -msgid "To configure products, go to the :guilabel:`Accounting` tab, and in the :guilabel:`UNSPSC Product Category` field, select the category that represents that product. The process can be done manually or through :doc:`a bulk import `." +msgid "Tax accounts available for Odoo." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:253 -msgid "All products need to have a |SAT| code associated with them in order to prevent validation errors." +msgid "To configure products, go to :menuselection:`Accounting --> Customers --> Products`, then select a product to configure, or :guilabel:`Create` a new one. In the :guilabel:`Accounting` tab, and in the :guilabel:`UNSPSC Product Category` field, select the category that represents the product. The process can be done manually, or through :doc:`a bulk import <../../general/export_import_data>`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:257 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:303 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:259 +msgid "All products need to have an |SAT| code associated with them in order to prevent validation errors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:263 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:314 msgid "Electronic invoicing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:260 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:266 msgid "PAC credentials" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:262 -msgid "After you have processed your `Private Key (CSD) `_ with the |SAT|, you must register directly with the :ref:`PAC ` of your choice before you start creating invoices from Odoo." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:268 +msgid "After you have processed your `Private Key (CSD) `_ with the |SAT|, you **must** register directly with the :ref:`PAC ` of your choice before you start creating invoices from Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:267 -msgid "Once you created your account with any of these providers, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX)`. Under the :guilabel:`MX PAC` section, enter the name of your |PAC| with your credentials (:guilabel:`PAC username` and :guilabel:`PAC password`)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:273 +msgid "Once you've created your account with any of these providers, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX)`. Under the :guilabel:`MX PAC` section, enter the name of your |PAC| with your credentials (:guilabel:`PAC username` and :guilabel:`PAC password`)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "PAC credentials." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:275 -msgid "If you do not have credentials and want to test the electronic invoicing, you can activate the :guilabel:`Test Environment` checkbox and select :guilabel:`Solucion Factible` as the |PAC|. You do not need to add a username or password." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:280 -msgid ".cer and .key certificates" +msgid "Configuring PAC credentials from the Accounting settings." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:282 -msgid "You need to upload the `digital certificates of the company `_ within the section :guilabel:`MX Certificates`. Select :guilabel:`Add a line` and a window will open. Click on :guilabel:`Create`, and from there upload your digital certificate (:file:`.cer` file), your key (:file:`.key` file), and your password. To finish, click on :guilabel:`Save and Close`." +msgid "If you do not have credentials, but want to test the electronic invoicing, you can activate the :guilabel:`MX PAC test environment` checkbox, and select :guilabel:`Solucion Factible` as the |PAC|. You do not need to add a username or password for a test environment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:287 +msgid ".cer and .key certificates" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:289 +msgid "The `digital certificates of the company `_ must be uploaded within the :guilabel:`MX Certificates` section. To do so, navigate to :menuselection:`Settings --> Accounting --> Electronic Invoicing (MX)`. Under the :guilabel:`MX Certificates` section, select :guilabel:`Add a line`, and a window will open. Click :guilabel:`Create`, and from there, upload your digital :guilabel:`Certificate` (:file:`.cer` file), your :guilabel:`Certificate Key` (:file:`.key` file), and your :guilabel:`Certificate Password`. To finish, click on :guilabel:`Save & Close`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Certificate and key." +msgid "Certificate and key upload inputs." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:292 -msgid "If you still do not have one of the contracted |PAC|\\s and you want to test electronic invoicing you can use the following |SAT| test certificates:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:303 +msgid "If you still do not have one of the contracted |PAC|\\s and you want to test electronic invoicing, you can use the following |SAT| test certificates:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:295 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:306 msgid ":download:`Certificate `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:296 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:307 msgid ":download:`Certificate Key `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:297 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:308 msgid "**Password**: ``12345678a``" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:300 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:311 msgid "Workflows" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:305 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:316 msgid "The invoicing process in Odoo is based on `Annex 20 `_ version 4.0 of electronic invoicing of the |SAT|." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:312 -msgid "To start invoicing from Odoo, a customer invoice must be created using the :doc:`standard invoicing flow `." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:323 +msgid "To start invoicing from Odoo, a customer invoice must be created using the :doc:`standard invoicing flow <../accounting/customer_invoices>`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:315 -msgid "When the document is in draft mode, you can make any changes to it (add the correct :guilabel:`Payment Way` or :guilabel:`Usage` that the customer might require, for example.)" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:326 +msgid "While the document is in draft mode, changes can be made to it (the correct :guilabel:`Payment Way` or :guilabel:`Usage` that the customer might require can be added, for example.)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:318 -msgid "After you :guilabel:`Confirm` the customer invoice, a blue message appears stating: :guilabel:`The invoice will be processed asynchronously by the following E-invoicing service: CFDI (4.0)`. Pressing the :guilabel:`Process Now` button sends the document to be signed by the government. On success, the :guilabel:`Fiscal Folio` field appears on the document and the XML file is attached in the chatter." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:329 +msgid "After you :guilabel:`Confirm` the customer invoice, a blue message appears stating: :guilabel:`The invoice will be processed asynchronously by the following E-invoicing service: CFDI (4.0)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:325 -msgid "If you press :guilabel:`Retry` in the field :guilabel:`SAT status` of the invoice, you can confirm if the XML file is valid in the SAT." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:328 -msgid "If you are in a testing environment, you will always receive the message :guilabel:`Not Found`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:330 -msgid "To send the signed invoice to your client by mail, you can send the XML together with the PDF file directly from Odoo by clicking the :guilabel:`Send and Print` button. You can also download the PDF file to your computer by clicking the :guilabel:`Print` button and selecting the desired option." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:332 +msgid "Pressing the :guilabel:`Process Now` button sends the document to the government so it can be signed. After receiving the signed document back from the government, the :guilabel:`Fiscal Folio` field appears on the document, and the XML file is attached in the chatter." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:337 -msgid "While an invoice is a document type \"I\" (Ingreso), a credit note is a document type \"E\" (Egreso)." +msgid "If you click :guilabel:`Retry` in the :guilabel:`SAT status` field on the invoice, you can confirm if the XML file is valid in the |SAT|." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:339 -msgid "The only addition to the :doc:`standard flow for credit notes ` is that, as a requirement of the SAT, there has to be a relation between a credit note and an invoice through the fiscal folio." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:340 +msgid "If you are in a testing environment, you will always receive the message :guilabel:`Not Found`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:343 -msgid "Because of this, the field :guilabel:`CFDI Origin` adds this relation with a `01|`, followed by the fiscal folio of the original invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Creating a credit note." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:342 +msgid "To send the signed invoice to your client by mail, you can send both the XML and PDF files together, directly from Odoo, by clicking the :guilabel:`Send & Print` button. You can also download the PDF file to your computer, by clicking the :guilabel:`Print` button, and selecting the desired print option." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:350 -msgid "For the :guilabel:`CFDI Origin` field to be added automatically, use the button :guilabel:`Add Credit Note` from the invoice instead of creating it manually." +msgid "While an invoice is a document type \"I\" (Ingreso), a credit note is a document type \"E\" (Egreso)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:354 -msgid "Payment complements" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:352 +msgid "The only addition to the :doc:`standard flow for credit notes <../accounting/customer_invoices/credit_notes>` is that, as a requirement of the |SAT|, there has to be a relation between a credit note and an invoice through the fiscal folio." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:357 -msgid "Payment policy" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:356 +msgid "Because of this requirement, the field :guilabel:`CFDI Origin` adds this relation with a `01|`, followed by the fiscal folio of the original invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:359 -msgid "One of the additions of the Mexican Localization is the field :guilabel:`Payment Policy`. `According to the SAT documentation `_, there may be 2 types of payments:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Example CFDI Origin number." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:364 +msgid "For the :guilabel:`CFDI Origin` field to be automatically added, use the :guilabel:`Add Credit Note` button from the invoice, instead of creating it manually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:368 +msgid "Payment complements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:371 +msgid "Payment policy" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:373 +msgid "One addition of the Mexican localization is the :guilabel:`Payment Policy` field . `According to the SAT documentation `_, there may be 2 types of payments:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:377 msgid "`PUE` (Pago en una Sola Exhibición/Payment in a Single Exhibition)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:365 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:378 msgid "`PPD` (Pago en Parcialidades o Diferido/Payment in Installements or Deferred)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:367 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:380 msgid "The difference lies in the *Due Date* or *Payment Terms* of the invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:369 -msgid "To configure |PUE| invoices, you must select an invoice :guilabel:`Due Date` within the same month or choose a payment term that does not imply changing the due month (immediate payment, 15 days, 21 days, all falling within the current month)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:382 +msgid "To configure |PUE| invoices, navigatge to :menuselection:`Accounting --> Customers --> Invoices`, and either select an invoice :guilabel:`Due Date` within the same month, or choose a payment term that does not imply changing the due month (immediate payment, 15 days, 21 days, all falling within the current month)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Example of an invoice with the PUE requirements." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:377 -msgid "Some :guilabel:`Payment Terms` are already installed by default. You can check them in :menuselection:`Accounting --> Configuration --> Payment Terms`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:392 +msgid "Some :guilabel:`Payment Terms` are already installed by default, and can be managed from :menuselection:`Accounting --> Configuration --> Payment Terms`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:380 -msgid "To configure |PPD| invoices, you need to choose a :guilabel:`Due Date` after the first day of the following month (this also applies if your :guilabel:`Payment Term` is due in the following month)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:395 +msgid "To configure |PPD| invoices, navigate to :menuselection:`Accounting --> Customers --> Invoices`, and select an invoice with a :guilabel:`Due Date` after the first day of the following month. This also applies if your :guilabel:`Payment Term` is due in the following month." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Example of an invoice with the PPD requirements." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:387 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:404 msgid "Because the |PPD| policy implies that an invoice is not going to get paid at the moment, the correct :guilabel:`Payment Way` for the |PPD| invoices is :guilabel:`99 - Por Definir` (To define)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:392 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:409 msgid "Payment flow" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:394 -msgid "In both cases, the payment process in Odoo :doc:`is the same `, the main difference would be that payments related to |PPD| invoices trigger the creation of a document type \"P\" (Pago)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:398 -msgid "If a payment is related to a |PUE| invoice, it can be registered with the wizard and be associated with the corresponding invoice. Its status will be :guilabel:`In Payment` since the payment is effectively validated when it is bank reconciled." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:405 -msgid "While this process is the same for PPD invoices, the addition of the creation of an :doc:`electronic document ` means that some additional requirements are needed to correctly send the document to the SAT." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:409 -msgid "You need to confirm the specific :guilabel:`Payment Way` where you received the payment. Because of this, this field cannot be :guilabel:`99 - Por Definir` (To Define)." -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/mexico.rst:411 -msgid "If you are going to add a bank account to the customer in the :guilabel:`Accounting` tab of their contact, it needs to have a valid number." +msgid "In both cases, the payment process in Odoo :doc:`is the same <../accounting/customer_invoices>`, the main difference being payments related to |PPD| invoices trigger the creation of a document type \"P\" (Pago)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:415 +msgid "If a payment is related to a |PUE| invoice, it can be registered with the wizard, and be associated with the corresponding invoice. To do so, navigate to :menuselection:`Accounting --> Customers --> Invoices`, and select an invoice. Then, click the :guilabel:`Register Payment` button. The invoice status changes to :guilabel:`In Payment`, since the payment is effectively validated when it is bank reconciled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:422 +msgid ":doc:`../accounting/bank/reconciliation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:424 +msgid "While this process is the same for PPD invoices, the addition of the creating an :doc:`electronic document <../accounting/customer_invoices/electronic_invoicing>` means some additional requirements are needed to correctly send the document to the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:428 +msgid "From an invoice, you need to confirm the specific :guilabel:`Payment Way` where you received the payment. Because of this, the :guilabel:`Payment Way` field **cannot** be set as `99 - Por Definir (To Define)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:432 +msgid "If you are going to add a bank account number in the :guilabel:`Accounting` tab of a customer's contact card, it must have a valid account number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:436 msgid "The exact configurations are in the `Anexo 20 of the SAT `_. Usually, the :guilabel:`Bank Account` needs to be 10 or 18 digits for transfers, 16 for credit or debit cards." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:419 -msgid "If a payment is related to a signed invoice with the :guilabel:`Payment Policy` `PPD`, Odoo generates the corresponding payment complement automatically once you press :guilabel:`Process Now`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:440 +msgid "If a payment is related to a signed invoice with the :guilabel:`Payment Policy` `PPD`, Odoo generates the corresponding payment complement automatically, once you click :guilabel:`Process Now`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "CFDI (4.0) E-invoicing service process payment now message." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:426 -msgid "A payment in MXN cannot be used to pay multiple invoices in USD. Rather, the payment should be separated into multiple payments created using the :guilabel:`Register Payment` button on the corresponding invoices." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:449 +msgid "A payment in MXN **cannot** be used to pay multiple invoices in USD. Instead, the payment should be separated into multiple payments, using the :guilabel:`Register Payment` button on the corresponding invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:431 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:454 msgid "Invoice cancellations" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:433 -msgid "It is possible to cancel the EDI documents sent to the SAT. According to the `Reforma Fiscal 2022 `_, since January 1st 2022, there are two requirements for this:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:456 +msgid "It is possible to cancel the EDI documents sent to the |SAT|. According to the `Reforma Fiscal 2022 `_, since January 1st, 2022, there are two requirements for this:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:437 -msgid "With all cancellation requests, you have to specify a *cancellation reason*." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:460 +msgid "With all cancellation requests, you **must** specify a *cancellation reason*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:438 -msgid "After 24 hours have passed, the client must be asked to accept the cancellation." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:461 +msgid "After 24 hours have passed since the creation of the invoice, the client **must** be asked to accept the cancellation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:440 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:464 msgid "There are four different cancellation reasons. In Odoo, you can cancel invoices with the reasons *01 Invoices sent with errors with a relation*, and *02 Invoices sent with errors without a relation*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:444 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:467 +msgid "The following sections break down the process of canceling invoices for each cancellation reason in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:471 +msgid "Odoo has certain limitations to canceling invoices in the |SAT|: The reasons 03 and 04 (*Operation did not take place* and *Nominative transactions related to a global invoice*, respectively) are not currently supported by Odoo. For this, you need to cancel the invoice directly in the |SAT|, and press :guilabel:`Retry` in the :guilabel:`SAT Status field`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:477 msgid "01 - invoices sent with errors with a relation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:446 -msgid "This cancellation motive has to be used when a new invoice needs to substitute the original one, due to an error in any field." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:479 +msgid "This cancellation reason must be used when a new invoice needs to substitute the original one, due to an error in any field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:449 -msgid "Copy the :guilabel:`Fiscal Folio` of the *old invoice*" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:482 +msgid "Begin by navigating to :menuselection:`Accounting --> Customers --> Invoices`, and select the old invoice. Copy the :guilabel:`Fiscal Folio` from the old invoice. Then, navigate to the new invoice, and in the :guilabel:`CFDI Origin` field, add the value `04|` and paste the :guilabel:`Fiscal Folio` of the old invoice after the value. Finally, sign the new document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:450 -msgid "Paste it into the field :guilabel:`CFDI Origin` of the *new invoice*, followed by a `04|`" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:487 +msgid "Next, navigate back to the old invoice, and notice the :guilabel:`Substituted By` field is now available. Click the :guilabel:`Request EDI Cancellation` button on the old invoice, and then click :guilabel:`Process Now` in the blue section that appears. The invoice status changes to :guilabel:`Canceled`, and a confirmation is logged in the chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:451 -msgid "Sign the new document." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:492 +msgid "Now, the invoice should be canceled in the |SAT| as well. You can confirm this was done correctly, by pressing :guilabel:`Retry` in the |SAT| status field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:495 +msgid "If the document was canceled more than 24 hours after its creation, you may need to ask the client to accept the cancellation in their “Buzón Tributario” directly from the `SAT website `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:500 +msgid "The `04|` is only a code that helps Odoo to perform this process. It has no relation to the method 04 reason for cancellation." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Old invoice with CFDI Origin." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:456 -msgid "Go back to the *old invoice*, the field :guilabel:`Substituted By` should appear." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:457 -msgid "Click the :guilabel:`Request EDI Cancellation` button." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:458 -msgid "As if it were a regular invoice, a blue field then appears on the invoice. Click :guilabel:`Process Now`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:460 -msgid "The invoice status is moved to :guilabel:`Cancelled` and you receive a confirmation in the chatter." -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Invoice 01 properly canceled." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:466 -msgid "Now, the invoice should be canceled in the SAT too. You can confirm that this was done correctly by pressing :guilabel:`Retry` in the SAT status field." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:469 -msgid "If the document was canceled after 24 hours, it is possible that the client must be asked to accept the cancellation in their \"Buzón Tributario\"." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:473 -msgid "The `04|` is only a code that helps Odoo to perform this process. It has no relation to the method 04 reason for cancellation." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:477 -msgid "02 - invoices sent with errors without a relation" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:479 -msgid "This cancellation motive has to be used when an invoice was sent with an error in any field and does not need to be replaced by another one." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:482 -msgid "For this case, all that is required is to click on :guilabel:`Request EDI Cancellation`, and then press click the :guilabel:`Process Now` button." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Invoice 02 properly canceled." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:488 -msgid "As the field :guilabel:`Substituted By` does not exist, the SAT should detect automatically that the cancellation reason is 02." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:492 -msgid "Odoo has certain limitations to canceling invoices in the SAT: The reasons 03 and 04 (*Operation did not take place* and *Nominative transactions related to a global invoice*) are not currently supported by Odoo. For this, you need to cancel the invoice directly in the SAT and use a *Server Action*." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:498 -msgid "Payment cancellations" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:500 -msgid "It is also possible to cancel *Payment Complements*. For this, go to the payment and select :guilabel:`Request EDI Cancellation`. As with invoices, a blue button will appear. Select :guilabel:`Process now`, and the document will be sent to the SAT. After a few seconds, you can press :guilabel:`Retry` to confirm the current SAT status." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:505 -msgid "The payment moves their status to :guilabel:`Cancelled`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:508 -msgid "Just like invoices, when you create a new *Payment Complement*, you can add the relation of the original document by adding a `04|` plus the fiscal folio." +msgid "Invoice with the Substituted By field referencing the CFDI Origin invoice." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:512 -msgid "Invoicing special use cases" +msgid "02 - invoices sent with errors without a relation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:515 -msgid "CFDI to public" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:514 +msgid "This cancellation reason has to be used when an invoice was sent with an error in any field, and does not need to be replaced by another one." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:517 +msgid "For this case, navigate to :menuselection:`Accounting --> Customers --> Invoices`, and select the old invoice. From here, the only requirement is to click the :guilabel:`Request EDI Cancellation` button, and then click the :guilabel:`Process Now` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:521 +msgid "Because the field :guilabel:`Substituted By` does not appear when using this cancellation reason, the |SAT| should automatically detect that the cancellation reason is 02." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:525 +msgid "Payment cancellations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:527 +msgid "It is also possible to cancel *Payment Complements*. For this, go to the payment, via :menuselection:`Accounting --> Customers --> Payments`, and select :guilabel:`Request EDI Cancellation`. As with invoices, a blue button will appear. Click :guilabel:`Process now`, and the document will be sent to the |SAT|. After a few seconds, you can click :guilabel:`Retry` to confirm the current |SAT| status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:533 +msgid "Finally, the payment status is moved to :guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:536 +msgid "Just like invoices, when you create a new *Payment Complement*, you can add the relation of the original document, by adding a `04|` plus the fiscal folio in the :guilabel:`CFDI Origin` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:540 +msgid "Invoicing special use cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:543 +msgid "CFDI to public" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:545 msgid "If the customer you are selling goods or services to does not require an invoice, a *CFDI to Public* has to be created." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:520 -msgid "However, if you use the name `PUBLICO EN GENERAL`, an error will be triggered. This is a main change in the CFDI 4.0 that states that invoices with that specific name needs additional fields." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:548 +msgid "If you use the :guilabel:`Customer` name `PUBLICO EN GENERAL`, an error will be triggered. This is a main change in the CFDI 4.0 that requires invoices with that specific name to need additional fields, which Odoo does not currently support. So, for a *CFDI to Public* to be created, you need to add any name to your customer that is **not** `PUBLICO EN GENERAL`. (For example: `CLIENTE FINAL`)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:523 -msgid "Odoo currently does not support this. So for a *CFDI to Public* to be created, you need to add any name to your customer that is not `PUBLICO EN GENERAL`. (For example `CLIENTE FINAL`)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:526 -msgid "In addition to this, the zip code of your company, and the generic :guilabel:`RFC` ``XAXX010101000`` are needed. The :guilabel:`Fiscal Regime` of your customer must be `Sin obligaciones fiscales`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:553 +msgid "In addition to this, it is required that the :guilabel:`ZIP` code of your company is added, the generic |RFC| is set as `XAXX010101000`, and the :guilabel:`Fiscal Regime` of your customer must be set as: `Sin obligaciones fiscales`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "CFDI to Public Error." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:535 -msgid "The main currency in Mexico is MXN. While this is mandatory for all Mexican companies, it is possible to send and receive invoices and payments in different currencies. To do this, you can enable the use of :doc:`multicurrency `. And select :guilabel:`Mexican Bank` as the service in :menuselection:`Accounting --> Settings --> Currency`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:541 -msgid "This way, in the XML file of the document you get the correct exchange rate and the total amount both in the foreign currency and in MXN." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:544 -msgid "It is highly recommended to use :doc:`a bank account for each currency `." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Multi-currency configuration." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:551 -msgid "The only currencies that automatically update their exchange rate daily are USD, EUR, GBP, and JPY." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:555 -msgid "Down payments" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:557 -msgid "There can be cases where you receive a payment in advance from a customer, that needs to be applied to an invoice later. In order to do this in Odoo, it is required to properly link invoices to each other with the :guilabel:`CFDI Origin` field." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:561 -msgid "It is necessary to have the :doc:`Sales ` app installed." +msgid "CFDI to Public Customer field configuration." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:564 -msgid "`The official documentation for registration of down payments in Mexico `_." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:567 -msgid "First, navigate to the :menuselection:`Sales` app to create a product `Anticipo` and configure it: the :guilabel:`Product Type` must be :guilabel:`Service`, and use the :guilabel:`UNSPSC Category` `84111506 Servicios de facturación`." +msgid "The main currency in Mexico is MXN. While this is mandatory for all Mexican companies, it is possible to send and receive invoices (and payments) in different currencies. To enable the use of :doc:`multicurrency <../accounting/get_started/multi_currency>`, navigate to the :menuselection:`Accounting --> Settings --> Currencies`, and set :guilabel:`Mexican Bank` as the :guilabel:`Service` in the :guilabel:`Automatic Currency Rates` section. Then, set the :guilabel:`Interval` field to the frequency you wish to update the exchange rates." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:571 -msgid "Then, go to :menuselection:`Sales --> Settings --> Invoicing --> Down Payments` and add the product as the default." +msgid "This way, the XML file of the document will have the correct exchange rate, and the total amount, in both the foreign currency and in MXN." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:574 -msgid "Create a sales order with the total amount, and create a down payment (either using a percentage or fixed amount). Then, sign the document, and :guilabel:`Register the Payment`." +msgid "It is highly recommended to use :doc:`a bank account for each currency <../accounting/bank/foreign_currency>`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:577 -msgid "When the time comes for the customer to get the final invoice, create it again from the same sales order. In the :guilabel:`Create Invoices` wizard select :guilabel:`Regular Invoice` and uncheck :guilabel:`Deduct down payments`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:578 +msgid "The only currencies that automatically update their exchange rate daily are: USD, EUR, GBP, and JPY." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:581 -msgid "Then, copy the :guilabel:`Fiscal Folio` from the first invoice and paste it into the :guilabel:`CDFI Origin` of the second invoice, adding the prefix `07|`. Sign the document." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Multi-currency configuration in the Accounting settings." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:584 -msgid "After this, create a credit note for the first invoice. Copy the :guilabel:`Fiscal Folio` from the second invoice and paste it in the :guilabel:`CFDI Origin` of the credit note, adding the prefix `07|`. Sign the document." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:586 +msgid "Down payments" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:588 -msgid "With this, all electronic documents are linked to each other. The final step is to fully pay the new invoice. At the bottom of the new invoice, you can find :guilabel:`Outstanding credits` in the credit note, add it as payment. Finally, register the remaining amount with the :guilabel:`Register Payment` wizard." +msgid "There can be cases where you receive a payment in advance from a customer that needs to be applied to an invoice later. In order to do this in Odoo, it is required to properly link invoices to each other with the :guilabel:`CFDI Origin` field. To do so, it is necessary to have the :doc:`Sales <../../sales>` app installed." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:594 -msgid "External trade" +msgid "`The official documentation for registration of down payments in Mexico `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:596 -msgid "The external trade is a complement to a regular invoice that adds certain values in both the XML and PDF, according to `SAT regulations `_." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:597 +msgid "First, navigate to the :menuselection:`Sales` app to create a product `Anticipo` and configure it. The :guilabel:`Product Type` must be :guilabel:`Service`, and use the :guilabel:`UNSPSC Category` must be: `84111506 Servicios de facturación`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:600 -msgid "This adds certain mandatory fields to invoices with a foreign customer, such as:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:602 -msgid "The specific address of the receiver and the sender" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:603 -msgid "The addition of a :guilabel:`Tariff Fraction` that identifies the type of product" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:601 +msgid "Then, go to :menuselection:`Sales --> Settings --> Invoicing --> Down Payments`, and add the *Anticipo* product as the default." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:604 -msgid "The correct :guilabel:`Incoterm` (International Commercial Terms), among others." +msgid "Create a sales order with the total amount, and create a down payment (either using a percentage or fixed amount). Then, sign the document, and :guilabel:`Register the Payment`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:606 -msgid "This allows the correct identification of exporters and importers, in addition to expanding the description of the merchandise sold." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:607 +msgid "When the time comes for the customer to get the final invoice, create it again from the same sales order. In the :guilabel:`Create Invoices` wizard, select :guilabel:`Regular Invoice`, and uncheck :guilabel:`Deduct down payments`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:609 -msgid "Since January 1st, 2018, it is a requirement for taxpayers who carry export operations of A1 type. While the current CFDI is 4.0, the external trade is currently on version 1.1" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:611 +msgid "Then, copy the :guilabel:`Fiscal Folio` from the first invoice, and paste it into the :guilabel:`CDFI Origin` of the second invoice, adding the prefix `07|` before the value. Then, sign the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:612 -msgid "In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended` and :guilabel:`l10n_mx_edi_extended_40` have to be installed." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:615 +msgid "After this, create a credit note for the first invoice. Copy the :guilabel:`Fiscal Folio` from the second invoice, and paste it in the :guilabel:`CFDI Origin` of the credit note, adding the prefix `07|`. Then, sign the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:616 -msgid "Before installing, make sure first that your business needs to use this feature. Consult your accountant first if needed before doing any modification." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:619 +msgid "With this, all electronic documents are linked to each other. The final step is to fully pay the new invoice. At the bottom of the new invoice, you can find the credit note in the :guilabel:`Outstanding credits` - add it as payment. Finally, register the remaining amount with the :guilabel:`Register Payment` wizard." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:625 -msgid "While the CFDI 4.0 requirements ask you to add a valid zip code in your contact, the external trade complement adds as a mandatory field the :guilabel:`City` and the :guilabel:`State`. All three fields must coincide with the `Official SAT Catalog `_ or you will receive an error." +msgid "External trade" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:630 -msgid "Add the :guilabel:`City` and :guilabel:`State` in the company's contract, not in the company itself. You can find your company's contact in :menuselection:`Accounting --> Customers --> Customers`" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:627 +msgid "The external trade is a complement to a regular invoice that adds certain values in both the XML and PDF, to invoices with a foreign customer according to `SAT regulations `_, such as:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:634 -msgid "The fields :guilabel:`Locality` and :guilabel:`Colony Code` are optional and can be added in the company directly in :menuselection:`Settings --> General Settings --> Companies`. These two have to coincide with the data in the SAT." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:631 +msgid "The specific address of the receiver and the sender" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Optional External Trade Company fields." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:632 +msgid "The addition of a :guilabel:`Tariff Fraction` that identifies the type of product" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:641 -msgid "The contact data for the foreign receiving client must have the following fields completed to avoid errors:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:633 +msgid "The correct :guilabel:`Incoterm` (International Commercial Terms), among others (*certificate of origin* and *special units of measure*)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:644 -msgid "The entire company :guilabel:`Address`, including a valid :guilabel:`ZIP` code and the foreign :guilabel:`Country`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:636 +msgid "This allows the correct identification of exporters and importers, in addition to expanding the description of the merchandise sold." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:639 +msgid "Since January 1, 2018, external trade is a requirement for taxpayers, who carry export operations of type A1. While the current CFDI is 4.0, the external trade is currently on version 1.1" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:642 +msgid "In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended` and :guilabel:`l10n_mx_edi_extended_40` have to be installed." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:646 -msgid "The format of the foreign :guilabel:`VAT` (tax identification number, for example: Colombia `123456789-1`)" +msgid "Before installing, make sure your business needs to use this feature. Consult your accountant first, if needed, before installing any modules." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:648 -msgid "In the :guilabel:`MX EDI` tab, you need to address if the customer receives goods for a period of time temporarily (:guilabel:`Temporary`) or permanently (:guilabel:`Definitive`)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:655 +msgid "To configure your company contact for external trade, navigate to :menuselection:`Accounting --> Customers --> Customers`, and select your :guilabel:`Company`. While the CFDI 4.0 requirements ask you to add a valid :guilabel:`ZIP` code in your contact, the external trade complement adds the requirement that your :guilabel:`City` and the :guilabel:`State` must also be valid. All three fields must coincide with the `Official SAT Catalog `_, or you will receive an error." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:650 -msgid "If you create this contact based in another from Mexico, make sure that you delete any information in the field :guilabel:`Fiscal Regime`. Do not use :guilabel:`No Tax Breakdown` either." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:662 +msgid "Add the :guilabel:`City` and :guilabel:`State` in the company's *contact*, not in the company itself. You can find your company's contact in :menuselection:`Accounting --> Customers --> Customers`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:666 +msgid "The fields :guilabel:`Locality` and :guilabel:`Colony Code` are optional and can be added in the company directly in :menuselection:`Settings --> General Settings --> Companies`. These two fields have to coincide with the data in the |SAT|." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Required External Trade Customer fields." +msgid "Optional external trade company fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:658 -msgid "In the resulting XML and PDF, the :guilabel:`VAT` is automatically replaced by the generic VAT for abroad transactions: `XEXX010101000`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:674 +msgid "To configure the contact data for a foreign receiving client, navigate to :menuselection:`Accounting --> Customers --> Customers`, and select the foreign client's contact. The contact must have the following fields completed to avoid errors:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:664 -msgid "All products involved with external trade must fill four fields, two of them exclusive to this feature." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:678 +msgid "The entire company :guilabel:`Address`, including a valid :guilabel:`ZIP` code and the foreign :guilabel:`Country`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:667 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:680 +msgid "The format of the foreign :guilabel:`VAT` (tax identification number, for example: Colombia `123456789-1`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:682 +msgid "In the :guilabel:`MX EDI` tab, you need to address if the customer receives goods for a period of time temporarily (:guilabel:`Temporary`) or permanently (:guilabel:`Definitive`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:686 +msgid "If the new contact was created by duplicating another existing contact from Mexico, make sure to delete any carried over information from the :guilabel:`Fiscal Regime` field. In addition, do not enable the :guilabel:`No Tax Breakdown` option. Selecting this option hides mandatory fields that are required for external trade contact configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Required external trade customer fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:696 +msgid "In the resulting XML and PDF files, the :guilabel:`VAT` is automatically replaced by the generic VAT for abroad transactions: `XEXX010101000`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:702 +msgid "All products involved with external trade have four fields that are required, two of them exclusive to external trade." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:705 msgid "The :guilabel:`Internal Reference` of the product is in the :guilabel:`General Information` tab." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:668 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:706 msgid "The :guilabel:`Weight` of the product must be more than `0`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:669 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:707 msgid "The `correct `_ :guilabel:`Tariff Fraction` of the product in the :guilabel:`Accounting` tab." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:671 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:709 msgid "The :guilabel:`UMT Aduana` corresponds to the :guilabel:`Tariff Fraction`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Required External Trade Product fields." +msgid "Required external trade product fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:677 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:716 msgid "If the UoM code of the :guilabel:`Tariff Fraction` is `01`, the correct :guilabel:`UMT Aduana` is `kg`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:679 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:718 msgid "If the UoM code of the :guilabel:`Tariff Fraction` is `06`, the correct :guilabel:`UMT Aduana` is `Units`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:683 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:722 msgid "Invoicing flow" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:685 -msgid "Before creating an invoice, it is important to take into account that external trade invoices require to convert the amounts of your product into USD. Therefore, we need to have :doc:`multicurrency enabled ` and activate USD in the :guilabel:`Currencies` section. The correct :guilabel:`Service` to run is :guilabel:`Mexican Bank`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:691 -msgid "With the correct exchange rate set up in :menuselection:`Accounting --> Settings --> Currency`, the only fields left are :guilabel:`Incoterm` and :guilabel:`Certificate Source` in the :guilabel:`Other Info` tab. The latter is optional." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "External Trade Other Info." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:698 -msgid "Sign the invoice with the same process as a regular one: Press the :guilabel:`Process Now` button." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:701 -msgid "Delivery guide" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:703 -msgid "A `Carta Porte `_ is a bill of lading: a document that states the type, quantity, and destination of goods being carried." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:706 -msgid "On December 1st, 2021, version 2.0 of this CFDI was implemented for all transportation providers, intermediaries, and owners of goods. Odoo is able to generate a document type \"T\" (Traslado) which, unlike other documents, is created in a delivery order instead of an invoice or payment." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:710 -msgid "Odoo can create XML and PDF files with or without ground transport and can process materials that are treated as *Dangerous Hazards*." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:713 -msgid "In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended`, :guilabel:`l10n_mx_edi_extended_40`, :guilabel:`l10n_mx_edi_stock` and :guilabel:`l10n_mx_edi_stock_40` have to be installed." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:717 -msgid "In addition to this, it is necessary to have the :doc:`Inventory ` and :doc:`Sales ` apps configured." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:722 -msgid "Odoo does not support Carta Porte type \"I\" (Ingreso), air, or marine transport. Consult your accountant first if this feature is needed before doing any modifications." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:728 -msgid "Odoo manages two different types of CFDI:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:724 +msgid "Before creating an invoice, it is important to take into account that external trade invoices require to convert the amounts of your product into USD. Therefore, :doc:`multicurrency <../accounting/get_started/multi_currency>` **must** be enabled and *USD* **must** be activated in the :guilabel:`Currencies` section. The correct :guilabel:`Service` to run is :guilabel:`Mexican Bank`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:730 -msgid "**No Federal Highways**: It is used when the *Distance to Destination* is `less than 30 KM `_." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:732 -msgid "**Federal Transport**: It is used when the *Distance to Destination* exceeds 30 KM." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:734 -msgid "Other than the standard requirements of regular invoicing (The RFC of the customer, the UNSPSC code...), if you are using *No Federal Highways*, no external configuration is needed." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:737 -msgid "For *Federal Transport*, several configurations have to be added to contacts, vehicle setups, and products. Those configurations are added to the XML and PDF files." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:741 -msgid "Contacts and vehicles" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:743 -msgid "Like with the external trade feature, the address in both your company and your final customer has to be complete. The zip code, city, and state must coincide with the `Official SAT Catalog `_" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:748 -msgid "The field :guilabel:`Locality` is optional for both addresses." +msgid "Then, with the correct exchange rate set up in :menuselection:`Accounting --> Settings --> Currency`, the only fields left are :guilabel:`Incoterm` and the optional :guilabel:`Certificate Source` in the :guilabel:`Other Info` tab." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Delivery Guide Contacts." +msgid "External trade Other Info tab of a product." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:738 +msgid "Finally, sign the invoice with the same process as a regular invoice, and click the :guilabel:`Process Now` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:742 +msgid "Delivery guide" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:744 +msgid "A `Carta Porte `_ is a bill of lading: a document that states the type, quantity, and destination of goods being carried." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:747 +msgid "On December 1st, 2021, version 2.0 of this CFDI was implemented for all transportation providers, intermediaries, and owners of goods. Odoo is able to generate a document type \"T\" (Traslado), which, unlike other documents, is created in a delivery order instead of an invoice or payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:751 +msgid "Odoo can create XML and PDF files with (or without) ground transport, and can process materials that are treated as *Dangerous Hazards*." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:754 -msgid "The origin address used for the delivery guide is set in :menuselection:`Inventory --> Configuration --> Warehouses Management --> Warehouses`. While this is set as the company address by default, you can change it according to your correct warehouse address." +msgid "In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended`, :guilabel:`l10n_mx_edi_extended_40`, :guilabel:`l10n_mx_edi_stock` and :guilabel:`l10n_mx_edi_stock_40` have to be installed." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:758 -msgid "Another addition to this feature is the :guilabel:`Vehicle Setups` menu found in :menuselection:`Inventory --> Settings --> Mexico`. This menu lets you add all the information related to the vehicle used for the delivery order." +msgid "In addition to this, it is necessary to have the :doc:`Inventory <../../inventory_and_mrp/inventory>` and :doc:`Sales <../../sales/sales>` apps installed, as well." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:762 +msgid "Odoo does not support Carta Porte type document type \"I\" (Ingreso), air, or marine transport. Consult your accountant first if this feature is needed before doing any modifications." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:768 +msgid "Odoo manages two different types of CFDI:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:770 +msgid "**No Federal Highways**: Is used when the *Distance to Destination* is `less than 30 KM `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:772 +msgid "**Federal Transport**: Is used when the *Distance to Destination* exceeds 30 KM." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:774 +msgid "Other than the standard requirements of regular invoicing (The |RFC| of the customer, the UNSPSC code, etc.), if you are using *No Federal Highways*, no external configuration is needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:777 +msgid "For *Federal Transport*, several configurations have to be added to contacts, vehicle setups, and products. Those configurations are added to the XML and PDF files." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:781 +msgid "Contacts and vehicles" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:783 +msgid "Like the external trade feature, the :guilabel:`Address` in both the company and the final customer must be complete. The :guilabel:`ZIP` code, :guilabel:`City`, and :guilabel:`State` must coincide with the `Official SAT Catalog for Carta Porte _`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:788 +msgid "The field, :guilabel:`Locality`, is optional for both addresses." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Delivery guide contact configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:795 +msgid "The origin address used for the delivery guide is set in :menuselection:`Inventory --> Configuration --> Warehouses Management --> Warehouses`. While this is set as the company address by default, you can change it according to your correct warehouse address." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:799 +msgid "Another addition to this feature is the :guilabel:`Vehicle Setups` menu found in :menuselection:`Inventory --> Settings --> Mexico`. This menu lets you add all the information related to the vehicle used for the delivery order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:803 msgid "All fields are mandatory to create a correct delivery guide." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:806 +msgid "The fields, :guilabel:`Vehicle Plate Number` and :guilabel:`Number Plate`, must contain between 5 to 7 characters." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:809 +msgid "In the :guilabel:`Intermediaries` section, you must add the operator of the vehicle. The only mandatory fields for this contact are the :guilabel:`VAT` and :guilabel:`Operator Licence`." +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Delivery Guide Vehicle Configurations required fields." +msgid "Delivery guide vehicle configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:767 -msgid "In the :guilabel:`Intermediaries` section, you need to add the operator of the vehicle. The only mandatory fields for this contact are the :guilabel:`VAT` and :guilabel:`Operator Licence`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:819 +msgid "Similar to regular invoicing, all products must have a :guilabel:`UNSPSC category`. In addition to this, there are two extra configurations for products involved in delivery guides:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:773 -msgid "Like with regular invoicing, all products must have a :guilabel:`UNSPSC category`. In addition to this, there are two extra configurations for products involved in delivery guides:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:776 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:822 msgid "The :guilabel:`Product Type` must be set as :guilabel:`Storable Product` for stock movements to be created." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:778 -msgid "In the :guilabel:`Inventory` tab, the field :guilabel:`Weight` should have more than 0." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Delivery Guide Product Configurations." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:784 -msgid "Sales and inventory flow" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:786 -msgid "To create a delivery guide, first, you need to create and confirm a sales order. This generates a :guilabel:`Delivery` smart button. Press it and :guilabel:`Validate` the transfer." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:789 -msgid "After the status is set to :guilabel:`Done`, you can edit the transfer and select the :guilabel:`Transport Type` (either :guilabel:`No Federal Highways` or :guilabel:`Federal Transport`)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:793 -msgid "If your delivery guide has the type :guilabel:`No Federal Highways`, you can save the transfer and then press :guilabel:`Generate Delivery Guide`. The resulting XML can be found in the chatter." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:797 -msgid "Other than the :guilabel:`UNSPSC` in all products, delivery guides that use :guilabel:`No Federal Highways` do not require any special configuration to be sent to the government." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:800 -msgid "If your delivery guide has the type :guilabel:`Federal Transport`, the tab :guilabel:`MX EDI` appears. In there, write a value in :guilabel:`Distance to Destination (KM)` bigger than `0`, and select the :guilabel:`Vehicle Setup` used for this delivery." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Delivery Guide MX EDI tab configuration." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:808 -msgid "Dangerous hazards" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:810 -msgid "Certain values in the :guilabel:`UNSPSC Category` are considered in the `official SAT catalog `_ as dangerous hazards. These categories need additional considerations when creating a delivery guide with :guilabel:`Federal Transport`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:815 -msgid "In the product, the fields :guilabel:`Hazardous Material Designation Code (MX)` and :guilabel:`Hazardous Packaging (MX)` must be filled with the correct code from the |SAT| catalog." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:818 -msgid "In the vehicle setup, the data from the :guilabel:`Environment Insurer` and :guilabel:`Environment Insurance Policy` has to be filed too." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Delivery Guide environment required fields." -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/mexico.rst:824 -msgid "After this, continue with the regular process to create a delivery guide." +msgid "In the :guilabel:`Inventory` tab, the field :guilabel:`Weight` should have more than `0`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:827 -msgid "Customs numbers" +msgid "Creating a delivery guide of a product with the value `0` will trigger an error. As the :guilabel:`Weight` has been already stored in the delivery order, it is needed to return the products, and create the delivery order (and delivery guide) again with the correct amounts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:829 -msgid "A *customs declaration* (Pedimento Aduanero) is a fiscal document that certifies that all contributions to the fiscal entity (the |SAT|) has been paid, for the import/export of goods." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:832 -msgid "According to the `Annex 20 `_ of CFDI 4.0, in documents where the invoiced goods come from a first-hand import operation, the field :guilabel:`Customs Number` needs to be added to all lines of products involved with the operation." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Delivery guide product configuration." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:836 -msgid "For this, the module :guilabel:`l10n_mx_edi_landing` has to be installed, in addition to the :doc:`Inventory `, :doc:`Purchase ` and :doc:`Sales ` apps configured." +msgid "Sales and inventory flow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:838 +msgid "To create a delivery guide, first, you need to create and confirm a sales order from :menuselection:`Sales --> Sales Order`. This generates a :guilabel:`Delivery` smart button. Click it, and :guilabel:`Validate` the transfer." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:842 -msgid "Do not confuse this feature with external trade. The customs numbers are directly related to importing goods, while the external trade complement is related to exporting. Consult your accountant first if this feature is needed before doing any modifications." +msgid "After the status is set to :guilabel:`Done`, you can edit the transfer, and select the :guilabel:`Transport Type` (either :guilabel:`No Federal Highways` or :guilabel:`Federal Transport`)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:849 -msgid "In order to track the correct customs number for a specific invoice, Odoo uses :doc:`landed costs `. Go to :menuselection:`Inventory --> Configuration --> Settings --> Valuation`. Make sure that :guilabel:`Landed Costs` is activated." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:846 +msgid "If your delivery guide has the type :guilabel:`No Federal Highways`, you can save the transfer, and then click :guilabel:`Generate Delivery Guide`. The resulting XML can be found in the chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:854 -msgid "First, a *service*-type product called `Pedimento` has to be created. In the :guilabel:`Purchase` tab, check :guilabel:`Is a Landed Cost` and select a :guilabel:`Default Split Method`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:850 +msgid "Other than the :guilabel:`UNSPSC` in all products, delivery guides that use :guilabel:`No Federal Highways` do not require any special configuration to be sent to the government." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:857 -msgid "After this, we need to configure the *storable products* that holds the customs numbers. We need to make sure that the product category has the following configuration:" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:853 +msgid "If your delivery guide has the type, :guilabel:`Federal Transport`, the tab :guilabel:`MX EDI` appears. There, enter a value in :guilabel:`Distance to Destination (KM)` bigger than `0`, and select the :guilabel:`Vehicle Setup` used for this delivery." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:860 -msgid ":guilabel:`Costing Method`: Either :guilabel:`FIFO` or :guilabel:`AVCO`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:861 -msgid ":guilabel:`Inventory Valuation`: :guilabel:`Automated`" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Delivery guide MX EDI tab configuration." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:862 -msgid ":guilabel:`Stock Valuation Account`: :guilabel:`115.01.01 Inventario`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:863 -msgid ":guilabel:`Stock Journal`: :guilabel:`Inventory Valuation`" +msgid "Dangerous hazards" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:864 +msgid "Certain values in the :guilabel:`UNSPSC Category` are considered in the `official SAT catalog `_ as *dangerous hazards*. These categories need additional considerations when creating a delivery guide with :guilabel:`Federal Transport`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:869 +msgid "First, select your product from :menuselection:`Inventory --> Products --> Products`. Then, in the :guilabel:`Accounting` tab, the fields :guilabel:`Hazardous Material Designation Code (MX)` and :guilabel:`Hazardous Packaging (MX)` must be filled with the correct code from the |SAT| catalog." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Delivery guide hazardous material product required fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:877 +msgid "In :menuselection:`Inventory --> Settings --> Mexico --> Vehicle Setup`, the data from the :guilabel:`Environment Insurer` and :guilabel:`Environment Insurance Policy` has to be filed, as well. After this, continue with the regular process to create a delivery guide." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Delivery Guide environment insurer required fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:886 +msgid "Customs numbers" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:888 +msgid "A *customs declaration* (Pedimento Aduanero) is a fiscal document that certifies that all contributions to the fiscal entity (the |SAT|) has been paid for, including the import/export of goods." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:892 +msgid "According to the `Annex 20 `_ of CFDI 4.0, in documents where the invoiced goods come from a first-hand import operation, the field, :guilabel:`Customs Number`, needs to be added to all lines of products involved with the operation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:896 +msgid "To do so, the module :guilabel:`l10n_mx_edi_landing` must be installed, in addition to the :doc:`Inventory <../../inventory_and_mrp/inventory>`, :doc:`Purchase <../../inventory_and_mrp/purchase>` and :doc:`Sales <../../sales/sales>` apps." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:901 +msgid "Do not confuse this feature with external trade. The customs numbers are directly related to importing goods, while the external trade complement is related to exporting. Consult your accountant first if this feature is needed before doing any modifications." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:908 +msgid "In order to track the correct customs number for a specific invoice, Odoo uses :doc:`landed costs <../../inventory_and_mrp/inventory/management/reporting/integrating_landed_costs>`. Go to :menuselection:`Inventory --> Configuration --> Settings --> Valuation`, and make sure that the :guilabel:`Landed Costs` feature is activated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:913 +msgid "Begin by creating a *service*-type product called, `Pedimento`. In the :guilabel:`Purchase` tab, activate :guilabel:`Is a Landed Cost`, and select a :guilabel:`Default Split Method`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:916 +msgid "Then, configure the *storable products* that hold the customs numbers. To do so, create the storable products, and make sure the :guilabel:`Product Category` has the following configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:919 +msgid ":guilabel:`Costing Method`: Either :guilabel:`FIFO` or :guilabel:`AVCO`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:920 +msgid ":guilabel:`Inventory Valuation`: :guilabel:`Automated`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:921 +msgid ":guilabel:`Stock Valuation Account`: :guilabel:`115.01.01 Inventario`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:922 +msgid ":guilabel:`Stock Journal`: :guilabel:`Inventory Valuation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:923 msgid ":guilabel:`Stock Input Account`: :guilabel:`115.05.01 Mercancías en tránsito`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:865 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:924 msgid ":guilabel:`Stock Output Account`: :guilabel:`115.05.01 Mercancías en tránsito`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Storable products configurations." +msgid "Storable products general configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:871 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Storable product category configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:935 msgid "Purchase and sales flow" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:873 -msgid "Create a :guilabel:`Purchase Order`, and confirm the order. This should trigger a :guilabel:`Receipt` smart button. Validate the receipt too." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:937 +msgid "After you configure your product, follow the standard :doc:`purchase flow <../../inventory_and_mrp/purchase>`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Customs Number Purchase." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:940 +msgid "Create a purchase order from :menuselection:`Purchase --> Orders --> Purchase Order`. Then, confirm the order to display a :guilabel:`Receipt` smart button. Click on the :guilabel:`Receipt` smart button to :guilabel:`Validate` the receipt." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:879 -msgid "Go to :menuselection:`Inventory --> Operations --> Landed Costs` and create a new record. Add the transfer that you just created, and both the product `Pedimento` and :guilabel:`Customs number`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:944 +msgid "Go to :menuselection:`Inventory --> Operations --> Landed Costs`, and create a new record. Add the transfer that you just created, and both: the product `Pedimento` and :guilabel:`Customs number`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:882 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:947 msgid "Optionally, you can add a cost amount. After this, validate the landed cost. Once :guilabel:`Posted`, all products related to that receipt have the customs number assigned." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:886 -msgid "You can only add the Pedimentos number once, so be careful when associating the correct number with the transfer(s)." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:951 +msgid "You can only add the *Pedimentos* number **once**, so be careful when associating the correct number with the transfer(s)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Customs number Inventory." +msgid "Customs number on a landed costs Inventory record." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:892 -msgid "Now, create a sales order and confirm it. This should trigger a :guilabel:`Delivery` smart button. Validate it." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:958 +msgid "Now, create a sales order, and confirm it. This should trigger a :guilabel:`Delivery` smart button. Validate it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:895 -msgid "Finally, create an invoice from the sales order and confirm it. The invoice line related to your product has a customs number in it." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:961 +msgid "Finally, create an invoice from the sales order, and confirm it. The invoice line related to your product has a customs number in it. This number should match the customs number added in the *Landed Costs* record you created earlier." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 msgid "Customs number on confirmed sales order product." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:902 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:970 msgid "Electronic accounting" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:904 -msgid "For Mexico, `Electronic Accounting `_ refers to the obligation to keep accounting records and entries through electronic means and to enter accounting information on a monthly basis through the SAT's website." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:972 +msgid "For Mexico, `Electronic Accounting `_ refers to the obligation to keep accounting records and entries through electronic means, and to enter accounting information on a monthly basis, through the |SAT| website." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:909 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:977 msgid "It consists of three main XML files:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:911 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:979 msgid "The updated list of the chart of accounts that you are currently using." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:912 -msgid "A monthly trial balance, plus a closing entry report also known as *Trial Balance Month 13*." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:913 -msgid "Either optional or for a compulsory audit, an export of the journal entries in your general ledger." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:916 -msgid "The resulting XML files follow the requirements of the `Anexo Técnico de Contabilidad Electrónica 1.3 `_." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:919 -msgid "In addition to this, you can generate the `DIOT `_: A report of vendor's journal entries that involves IVA taxes that can be exported in :file:`.txt` file." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:924 -msgid "In order to use these reports, the modules :guilabel:`l10n_mx_reports`, :guilabel:`l10n_mx_reports_closing`, :guilabel:`l10n_mx_xml_polizas` and :guilabel:`l10n_mx_xml_polizas_edi` have to be installed, as well as the :doc:`Accounting `." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:929 -msgid "You can find all of those reports in :menuselection:`Accounting --> Reporting --> Mexico`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:932 -msgid "The specific characteristics and obligations of the reports that you send might change according to your fiscal regime. Always contact your accountant before sending any documents to the government." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:937 -msgid "Catálogo de cuentas (chart of accounts)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:939 -msgid "The :doc:`chart of accounts ` in México follows a specific pattern based in SAT's `Código agrupador de cuentas `_." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:943 -msgid "You can create any account as long as it respects |SAT|'s encoding group, This pattern is `NNN.YY.ZZ` or `NNN.YY.ZZZ`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:947 -msgid "Some examples are `102.01.99` or `401.01.001`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:949 -msgid "When you create a new account in :menuselection:`Accounting --> Configuration --> Chart of Accounts`, if you follow this pattern, you get the correct grouping code in :guilabel:`Tags`, and your account appears in the COA report." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:953 -msgid "Once you created all your accounts, and made sure that you put the correct :guilabel:`Tags` in them." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:956 -msgid "You cannot use any pattern that ends a section with a 0 (such as `100.01.01`, `301.00.003` or `604.77.00`). This triggers errors in the report." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:959 -msgid "Once all is set up, you can go to :menuselection:`Accounting --> Reporting --> Mexico --> COA` and press the button :guilabel:`SAT (XML)`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:963 -msgid "Balanza de comprobación (trial balance)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:965 -msgid "The trial balance reports the initial balance, credit, and total balance of your accounts, provided that you added their correct encoding group." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:968 -msgid "This report can be generated monthly, and an XML file version is created if you go to :menuselection:`Accounting --> Reporting --> Mexico --> Trial Balance` and press the button :guilabel:`SAT (XML)`. Select the month you want to download beforehand." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Trial Balance Report." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:976 -msgid "Odoo does not generate the *Balanza de Comprobación Complementaria*." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:978 -msgid "An additional report is the *Month 13*: a closing balance sheet that shows any adjustments or movements made in the accounting to close the year." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:980 +msgid "A monthly trial balance, plus a closing entry report, also known as: *Trial Balance Month 13*." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:981 -msgid "In order to be able to generate this XML document, you have to go to :menuselection:`Accounting --> Accounting --> Miscellaneous --> Journal Entries` and create a new document. Here, you can add all amounts that you want to modify, and you can balance the debit and/or credit of each one." +msgid "Either optional, or for a compulsory audit, an export of the journal entries in your general ledger." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:985 -msgid "After this is done, press :guilabel:`Mark as Closing Entry`, and the report found in :menuselection:`Accounting --> Reporting --> Mexico --> Trial Balance Month 13` contains the total amount of the year, plus all the additions of the journal entry." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:984 +msgid "The resulting XML files follow the requirements of the `Anexo Técnico de Contabilidad Electrónica 1.3 `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:989 -msgid "You can generate the XML file by pressing the button :guilabel:`SAT (XML)`." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:987 +msgid "In addition to this, you can generate the `DIOT `_: A report of vendor's journal entries that involve IVA taxes that can be exported in a :file:`.txt` file." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Trial Balance Month 13 Setup." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:995 -msgid "Pólizas (general ledger)" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:992 +msgid "In order to use these reports, the modules :guilabel:`l10n_mx_reports`, :guilabel:`l10n_mx_reports_closing`, :guilabel:`l10n_mx_xml_polizas` and :guilabel:`l10n_mx_xml_polizas_edi` have to be installed, as well as the :doc:`Accounting <../accounting/get_started>`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:997 -msgid "By law, all transactions in Mexico must be recorded digitally. Because Odoo automatically creates all the underlying journal entries of your invoicing and payments, you can export your journal entries to comply with SAT's audits or tax refunds." +msgid "You can find the *Chart of accounts*, *Trial Balance Month 13*, and *DIOT* reports in :menuselection:`Accounting --> Reporting --> Mexico`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:1001 -msgid "This XML file is created in :menuselection:`Accounting --> Reporting --> Audit Reports --> General Ledger`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1005 -msgid "You can filter by period or by journal, according to your current needs." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1007 -msgid "After you press :guilabel:`XML (Polizas)`, a wizard appears. In here, you can select between four types of :guilabel:`Export type`." +msgid "The specific characteristics and obligations of the reports that you send might change according to your fiscal regime. Always contact your accountant before sending any documents to the government." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:1010 -msgid "For :guilabel:`Tax audit` or :guilabel:`Audit certification`, you need to write the :guilabel:`Order Number` provided by the |SAT| for :guilabel:`Return of goods` or :guilabel:`Compensation`, you need to write your :guilabel:`Process Number`, also provided by the |SAT|." +msgid "The :doc:`chart of accounts <../accounting/get_started/chart_of_accounts>` in México follows a specific pattern based on |SAT|'s' `Código agrupador de cuentas `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "Types of Polizas." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1014 +msgid "You can create any account, as long as it respects |SAT|'s encoding group: the pattern is `NNN.YY.ZZ` or `NNN.YY.ZZZ`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:1018 -msgid "If you want to see this report without sending it, use `ABC6987654/99` for :guilabel:`Order Number` and `AB123451234512` for :guilabel:`Process Number`." +msgid "Some examples are `102.01.99` or `401.01.001`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1022 -msgid "DIOT report" +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1020 +msgid "When a new account is created in :menuselection:`Accounting --> Configuration --> Chart of Accounts`, with the |SAT| encoding group pattern, the correct grouping code appears in :guilabel:`Tags`, and your account appears in the *COA* report." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:1024 -msgid "The DIOT (Declaración Informativa de Operaciones con Terceros / *Informative Declaration of Operations with Third Parties*) is an additional obligation with the |SAT|, where we give the current status of our creditable and non-creditable payments, withholdings and refunds of VAT from your vendor bills." +msgid "Once you create all your accounts, make sure the correct :guilabel:`Tags` are added." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1029 -msgid "Unlike other reports, this is uploaded to a software provided by the |SAT| that contains the A-29 form. In Odoo, you can download the records of your transactions in a :file:`.txt` file that you can upload to the form, avoiding direct capture of this data." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1027 +msgid "You cannot use any pattern that ends a section with a 0 (such as `100.01.01`, `301.00.003` or `604.77.00`). This triggers errors in the report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1033 -msgid "This file contains the total amount of your payments registered in vendor bills, broken down into the corresponding types of IVA. The :guilabel:`VAT` and :guilabel:`Country` is mandatory for all vendors." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1030 +msgid "Once everything is set up, you can go to :menuselection:`Accounting --> Reporting --> Mexico --> COA`, and click the :guilabel:`SAT (XML)` button to generate an XML file containing all of your accounts, which will be ready to upload to the |SAT| website." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:1037 -msgid "To get the report, go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions with third parties [DIOT]`. Select the month that suits you, and press :guilabel:`DIOT (TXT)` to download the :file:`.txt` file." +msgid "The trial balance reports the initial balance, credit, and total balance of your accounts, provided that you added their correct :ref:`encoding group `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1040 +msgid "This report can be generated monthly, and a corresponding XML file is created, if you go to :menuselection:`Accounting --> Reporting --> Mexico --> Trial Balance`, and click the :guilabel:`SAT (XML)` button. Select the month you want to download beforehand." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "DIOT Example." +msgid "Trial balance report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1045 -msgid "You need to fill the field :guilabel:`L10N Mx Type of Operation` in the :guilabel:`Accounting` tab of each one of your vendors to prevent validation errors. Make sure that your foreign customers have their country set up for :guilabel:`L10N Mx Nationality` to appear automatically." +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1049 +msgid "Odoo does not generate the *Balanza de Comprobación Complementaria*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1051 +msgid "An additional report is the *Month 13*: a closing balance sheet that shows any adjustments or movements made in the accounting to close the year." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1054 +msgid "To generate this XML document, navigate to :menuselection:`Accounting --> Accounting --> Miscellaneous --> Journal Entries`, and create a new document. Here, add all amounts to modify, and balance the debit and/or credit of each one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1058 +msgid "After this is done, click :guilabel:`Mark as Closing Entry`, and the report found in :menuselection:`Accounting --> Reporting --> Mexico --> Trial Balance Month 13`, contains the total amount of the year, plus all the additions of the journal entry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1062 +msgid "The XML file is generated by pressing the :guilabel:`SAT (XML)` button." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 -msgid "DIOT Example contact." +msgid "Trial Balance Month 13 setup." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "Trial Balance Month 13 report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1075 +msgid "By law, all transactions in Mexico must be recorded digitally. Since Odoo automatically creates all the underlying journal entries of your invoicing and payments, you can export your journal entries to comply with |SAT|'s audits and/or tax refunds." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1080 +msgid "You can filter by period, or by journal, according to your current needs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1082 +msgid "To create the XML, go to :menuselection:`Accounting --> Reporting --> Audit Reports --> General Ledger`, and click :guilabel:`XML (Polizas)`. Here, you can select between four types of :guilabel:`Export` types:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1086 +msgid ":guilabel:`Tax audit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1087 +msgid ":guilabel:`Audit certification`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1088 +msgid ":guilabel:`Return of goods`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1089 +msgid ":guilabel:`Compensation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1091 +msgid "For :guilabel:`Tax audit`, or :guilabel:`Audit certification`, you need to write the :guilabel:`Order Number` provided by the |SAT|. For :guilabel:`Return of goods`, or :guilabel:`Compensation`, you need to write your :guilabel:`Process Number`, also provided by the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1097 +msgid "If you want to see this report without sending it, use `ABC6987654/99` for :guilabel:`Order Number` and `AB123451234512` for :guilabel:`Process Number`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1101 +msgid "DIOT report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1103 +msgid "The DIOT (Declaración Informativa de Operaciones con Terceros / *Informative Declaration of Operations with Third Parties*) is an additional obligation with the |SAT|, where the current status of creditable and non-creditable payments, withholdings, and refunds of VAT from your vendor bills, are provided to the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1108 +msgid "Unlike other reports, the |DIOT| is uploaded to a software provided by the |SAT| that contains the A-29 form. In Odoo, you can download the records of your transactions as a :file:`.txt` file that can be uploaded to the form, avoiding direct capture of this data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1112 +msgid "The transactions file contains the total amount of your payments registered in vendor bills, broken down into the corresponding types of IVA. The :guilabel:`VAT` and :guilabel:`Country` is mandatory for all vendors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1116 +msgid "To get the |DIOT| report, go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions with third parties [DIOT]`. Select the month that suits you, and click :guilabel:`DIOT (TXT)` to download the :file:`.txt` file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "A Vendor Bill that is In Payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:-1 +msgid "DIOT (TXT) download button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1129 +msgid "You need to fill the field, :guilabel:`L10N Mx Type of Operation`, in the :guilabel:`Accounting` tab of each one of your vendors to prevent validation errors. Make sure that your foreign customers have their country set up for :guilabel:`L10N Mx Nationality` to appear automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "DIOT information on a vendor contact." msgstr "" #: ../../content/applications/finance/fiscal_localizations/netherlands.rst:3 @@ -20240,7 +20698,7 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:28 #: ../../content/applications/finance/payment_acquirers/mollie.rst:11 #: ../../content/applications/finance/payment_acquirers/ogone.rst:9 -#: ../../content/applications/finance/payment_acquirers/paypal.rst:93 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:98 #: ../../content/applications/finance/payment_acquirers/sips.rst:12 #: ../../content/applications/finance/payment_acquirers/stripe.rst:12 msgid ":ref:`payment_acquirers/add_new`" @@ -20252,7 +20710,7 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:51 #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:63 #: ../../content/applications/finance/payment_acquirers/mollie.rst:31 -#: ../../content/applications/finance/payment_acquirers/paypal.rst:162 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:167 #: ../../content/applications/finance/payment_acquirers/sips.rst:32 #: ../../content/applications/finance/payment_acquirers/stripe.rst:133 msgid ":doc:`../payment_acquirers`" @@ -20891,7 +21349,7 @@ msgid "To allow your customers to save their credit card credentials for future msgstr "" #: ../../content/applications/finance/payment_acquirers/ogone.rst:99 -#: ../../content/applications/finance/payment_acquirers/paypal.rst:90 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:95 msgid "Settings in Odoo" msgstr "" @@ -20912,10 +21370,14 @@ msgid "`Paypal `_ is an American online payment acquire msgstr "" #: ../../content/applications/finance/payment_acquirers/paypal.rst:9 +msgid "While PayPal is available in `over 200 countries/regions `_, only `a selection of currencies are supported `_." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/paypal.rst:14 msgid "Settings in PayPal" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:11 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:16 msgid "To access your PayPal account settings, log into PayPal, open the :guilabel:`Account Settings`, and open the :guilabel:`Website payments` menu." msgstr "" @@ -20923,155 +21385,155 @@ msgstr "" msgid "PayPal account menu" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:19 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:24 msgid "Note that for PayPal to work **in Odoo**, the options :ref:`Auto Return `, :ref:`PDT `, and :ref:`IPN ` **must** all be enabled." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:25 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:30 msgid "Auto Return" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:27 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:32 msgid "The **Auto Return** feature automatically redirects customers to Odoo once the payment is processed." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:29 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:34 msgid "From :guilabel:`Website payments`, go to :menuselection:`Website preferences --> Update --> Auto return for website payments --> Auto return` and select :guilabel:`On`. Enter the address of your Odoo database (e.g., `https://yourcompany.odoo.com`) in the :guilabel:`Return URL` field, and :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:35 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:40 msgid "Any URL does the job. Odoo only needs the setting to be enabled since it uses another URL." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:40 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:45 msgid "Payment Data Transfer (PDT)" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:42 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:47 msgid ":abbr:`PDT (Payment Data Transfer)` allows to receive payment confirmations, displays the payment status to the customers, and verifies the authenticity of the payments. From :menuselection:`Website preferences --> Update`, scroll down to :guilabel:`Payment data transfer` and select :guilabel:`On`." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:47 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:52 msgid "PayPal displays your **PDT Identity Token** as soon as :ref:`Auto return ` and :ref:`Payment Data Transfer (PDT) ` are enabled. If you need the **PDT Identity Token**, disable and re-enable :guilabel:`Payment data transfer` to display the token again." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:54 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:59 msgid "Instant Payment Notification (IPN)" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:56 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:61 msgid ":abbr:`IPN (Instant Payment Notifications)` is similar to **PDT**, but allows for more notifications, such as chargeback notifications. To enable **IPN**, go to :menuselection:`Website payments --> Instant payment notifications --> Update` and click :guilabel:`Choose IPN settings`. Enter a :guilabel:`Notification URL`, select :guilabel:`Receive IPN messages (Enabled)`, and :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:63 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:68 msgid "PayPal Account Optional" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:65 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:70 msgid "We advise not to prompt customers to log in with a PayPal account upon payment. It is better and more accessible for customers to pay with a debit/credit card. To disable that prompt, go to :menuselection:`Account Settings --> Website payments --> Update` and select :guilabel:`On` for :guilabel:`PayPal account optional`." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:71 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:76 msgid "Payment Messages Format" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:73 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:78 msgid "If you use accented characters (or anything other than primary Latin characters) for customer names or addresses, then you **must** configure the encoding format of the payment request sent by Odoo to PayPal. If you do not, some transactions fail without notice." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:77 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:82 msgid "To do so, go to `your production account `_. Then, click :guilabel:`More Options` and set the two default encoding formats as :guilabel:`UTF-8`." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:82 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:87 msgid "For Encrypted Website Payments & EWP_SETTINGS error, please check the `Paypal documentation `_." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:85 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:90 msgid "Configure your :ref:`Paypal Sandbox account `, then follow this `link `_ to configure the encoding format in a test environment." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:96 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:101 msgid "Credentials" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:98 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:103 msgid "Odoo needs your **API Credentials** to connect with your PayPal account. To do so, go to :menuselection:`Accounting --> Configuration --> Payment Acquirers` and :guilabel:`Activate` PayPal. Then, enter your PayPal account credentials in the :guilabel:`Credentials` tab:" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:102 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:107 msgid ":guilabel:`Email`: the login email address in Paypal;" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:103 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:108 msgid ":guilabel:`PDT Identity Token`: the key used to verify the authenticity of transactions;" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:104 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:109 msgid ":guilabel:`Use IPN`: enable for PayPal to work properly in Odoo." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:107 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:112 msgid "Save the :guilabel:`PDT Identity Token` for later use." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:109 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:114 msgid "To set the :guilabel:`PDT Identity Token`, switch to :ref:`developer mode ` and retrieve the token by following the configuration steps at :ref:`paypal/pdt`." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:113 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:118 msgid "The PayPal **Merchant ID** is not required in Odoo." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:115 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:120 msgid "If you are trying PayPal as a test, using a :ref:`PayPal Sandbox account `, change the :guilabel:`State` to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database rather than on your main database." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:120 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:125 msgid "Extra fees" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:122 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:127 msgid "You can charge **extra fees** to customers choosing to pay with PayPal in order to cover the transaction fees PayPal charges you. Once redirected to Paypal, your customer sees an extra amount applied to the order amount." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:126 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:131 msgid "To activate this option, go to :menuselection:`Accounting --> Configuration --> Payment Acquirers` and select :guilabel:`PayPal`. Then, go to the :guilabel:`Fees` tab and tick the :guilabel:`Add Extra Fees` box." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:131 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:136 msgid "You can refer to `Paypal Fees `_ to set up fees." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:133 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:138 msgid "`Traders in the EU `_ are not allowed to charge extra fees for paying with credit cards." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:138 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:143 msgid "Test environment" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:143 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:148 msgid "Thanks to PayPal sandbox accounts, you can test the entire payment flow in Odoo." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:145 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:150 msgid "Log into the `Paypal Developer Site `_ using your PayPal credentials, which creates two sandbox accounts:" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:148 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:153 msgid "A business account (to use as merchants, e.g., `pp.merch01-facilitator@example.com `_);" msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:150 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:155 msgid "A default personal account (to use as shoppers, e.g., `pp.merch01-buyer@example.com `_)." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:153 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:158 msgid "Log into PayPal sandbox using the merchant account and follow the same configuration instructions. Enter your sandbox credentials in Odoo (:menuselection:`Accounting --> Configuration --> Payment Acquirer --> PayPal` in the :guilabel:`Credentials` tab, and make sure the status is set on :guilabel:`Test Mode`. We recommend doing this on a test Odoo database rather than your main database." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:159 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:164 msgid "Run a test transaction from Odoo using the sandbox personal account." msgstr "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index f974aac76..93f3baa58 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-15.2\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-26 13:30+0000\n" +"POT-Creation-Date: 2023-12-19 07:46+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -2361,7 +2361,7 @@ msgid "In-App Purchase (IAP)" msgstr "" #: ../../content/applications/general/in_app_purchase.rst:5 -msgid "In-App Purchases (IAP) gives access to additional services through Odoo. For instance, it allows you to send SMS Text Messages or to send Invoices by post directly from my database." +msgid "In-App Purchases (IAP) gives access to additional services through Odoo. For instance, it allows you to send SMS Text Messages or to send Invoices by post directly from your database." msgstr "" #: ../../content/applications/general/in_app_purchase.rst:9 @@ -2369,11 +2369,11 @@ msgid "Buying Credits" msgstr "" #: ../../content/applications/general/in_app_purchase.rst:11 -msgid "Each IAP Service relies on prepaid credits to work and has its own pricing. To consult my current balance or to recharge my account, go to :menuselection:`Settings --> Odoo IAP --> View my Services`." +msgid "Each IAP Service relies on prepaid credits to work and has its own pricing. To consult your current balance or to recharge your account, go to :menuselection:`Settings --> Odoo IAP --> View my Services`." msgstr "" #: ../../content/applications/general/in_app_purchase.rst:19 -msgid "If I am on Odoo Online and have the Enterprise version, I benefit from free credits to test our IAP features." +msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free credits to test our IAP features." msgstr "" #: ../../content/applications/general/in_app_purchase.rst:23 @@ -2393,7 +2393,7 @@ msgid "IAP Portal" msgstr "" #: ../../content/applications/general/in_app_purchase.rst:40 -msgid "The IAP Portal is a platform regrouping my IAP Services. It is accessible from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, I can view my current balance, recharge my credits, review my consumption and set a reminder to when credits are low." +msgid "The IAP Portal is a platform regrouping your IAP Services. It is accessible from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, you can view your current balance, recharge your credits and set a reminder when your balance falls below a threshold." msgstr "" #: ../../content/applications/general/in_app_purchase.rst:48 @@ -2401,31 +2401,7 @@ msgid "Get notified when credits are low" msgstr "" #: ../../content/applications/general/in_app_purchase.rst:50 -msgid "To be notified when it’s time to recharge my credits, I’ll go to my IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and mark the Receive threshold warning option. Then, I’ll provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent to by email!" -msgstr "" - -#: ../../content/applications/general/in_app_purchase.rst:60 -msgid "IAP services available" -msgstr "" - -#: ../../content/applications/general/in_app_purchase.rst:62 -msgid "Different services are available depending on the hosting type of your Database:" -msgstr "" - -#: ../../content/applications/general/in_app_purchase.rst:64 -msgid "*Odoo Online*: only the IAP services provided by Odoo can be used (i.e. the SMS, Snailmail, Reveal and Partner Autocomplete features);" -msgstr "" - -#: ../../content/applications/general/in_app_purchase.rst:66 -msgid "*Odoo.sh and Odoo Enterprise (on-premise)*: both the services provided by Odoo and by third-party apps can be used." -msgstr "" - -#: ../../content/applications/general/in_app_purchase.rst:70 -msgid "Offering my own services" -msgstr "" - -#: ../../content/applications/general/in_app_purchase.rst:72 -msgid "I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity to get recurring revenue for an ongoing service use rather than — and possibly instead of — a sole initial purchase. Please, find more information at: :doc:`/developer/howtos/provide_iap_services`." +msgid "To be notified when it’s time to recharge your credits, you can go to your IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and check the Receive threshold warning option. Then, you can provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent by email!" msgstr "" #: ../../content/applications/general/users.rst:5 diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 3ac30c66b..d9ab111b6 100644 --- a/locale/sources/inventory_and_mrp.pot +++ b/locale/sources/inventory_and_mrp.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-15.2\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-26 13:30+0000\n" +"POT-Creation-Date: 2023-12-19 07:46+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -191,189 +191,615 @@ msgstr "" msgid "GS1 barcode nomenclature" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:5 -msgid "`GS1 nomenclature `_ consolidates multiple pieces of information in a single barcode. Each piece needs to follow a specific barcode pattern—which is a defined format of numbers, letters, special characters, and character length—to ensure proper interpretation of the barcode. By scanning the barcode on an unopened box, GS1 nomenclature can identify the product, lot number, number of units contained, and more." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:12 -msgid "`All GS1 barcodes `_" +msgid "`GS1 nomenclature `_ consolidates various product and supply chain data into a single barcode. Odoo takes in `unique Global Trade Item Numbers `_ (GTIN), purchased by businesses, to enable global shipping, sales, and eCommerce product listing." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:13 -msgid ":ref:`Odoo's default GS1 rules `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:14 -msgid ":ref:`Why's my barcode not working? `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:19 -msgid "Set up barcode nomenclature" +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:17 +msgid "Configure GS1 nomenclature to scan barcodes of sealed boxes and identify essential product information, such as |GTIN|, lot number, quantity information, and more." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:21 +msgid "|GTINs| are unique product identification that **must** be `purchased from GS1 `_ to use GS1 barcodes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:25 +msgid "`All GS1 barcodes `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:26 +msgid ":ref:`Odoo's default GS1 rules `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:27 +msgid ":ref:`Why's my barcode not working? `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:32 +msgid "Set up barcode nomenclature" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:34 msgid "To use GS1 nomenclature, navigate to the :menuselection:`Inventory app --> Configuration --> Settings`. Then under the :guilabel:`Barcode` section, check the :guilabel:`Barcode Scanner` box. Next, select :menuselection:`Barcode Nomenclature --> Default GS1 Nomenclature` from the default barcode nomenclature options." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:-1 -msgid "Choose GS1 from dropdown and click the internal link to see the list of GS1 rules." +msgid "Choose GS1 from dropdown and click the external link to see the list of GS1 rules." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:30 -msgid "To view and edit a list of GS1 *rules* and *barcode patterns* Odoo supports by default, click the :guilabel:`➡️ (External link)` icon to the right of the :guilabel:`Barcode Nomenclature` selection." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:33 -msgid "Opening the pop-up table provides an editable view of GS1 :guilabel:`Rule Names` available in Odoo. The table contains all the information that can be condensed with a GS1 barcode, along with the corresponding :guilabel:`Barcode Pattern`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:38 -msgid "After setting GS1 as the barcode nomenclature, :menuselection:`Barcode Nomenclatures` can also be accessed by first enabling :ref:`developer mode `. Navigate to :menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures` and finally, select :guilabel:`Default GS1 Nomenclature`." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:43 +msgid "The list of GS1 *rules* and *barcode patterns* Odoo supports by default is accessible by clicking the :guilabel:`➡️ (arrow)` icon to the right of the :guilabel:`Barcode Nomenclature` selection." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:46 -msgid "Use GS1 barcode" +msgid "In the :guilabel:`Open: Nomenclature` pop-up table, view and edit the GS1 :guilabel:`Rule Names` available in Odoo. The table contains all the information that can be condensed with a GS1 barcode, along with the corresponding :guilabel:`Barcode Pattern`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:48 -msgid "To build GS1 barcodes in Odoo, combine multiple pieces of information using the specified barcode pattern. The `application identifier `_ (A.I.) serves as the universal prefix for GS1 for barcode identification. Odoo uses regular expressions to describe barcode patterns concisely. Each barcode pattern begins with a required 2-4 digit :abbr:`A.I. (application identifier)`, which corresponds to the rule defined in the system's :ref:`barcode nomenclature list `. By including the appropriate :abbr:`A.I. (application identifier)` from the list, Odoo can accurately interpret GS1 barcodes. While most barcode patterns have a flexible length, some specific patterns, such as barcodes for dates, have defined length requirements." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:51 +msgid "After setting GS1 as the barcode nomenclature, the :menuselection:`Barcode Nomenclatures` settings can also be accessed by a hidden menu that's discoverable after enabling :ref:`developer mode `. Once enabled, navigate to the :menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures` menu and finally, select :guilabel:`Default GS1 Nomenclature`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:60 -msgid "Use the FNC1 separator (`\\x1D`) to end the barcode without needing to reach the maximum character length." +msgid "Use GS1 barcodes in Odoo" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:63 -msgid "Refer to the :ref:`GS1 nomenclature list ` to see a comprehensive list of all barcode patterns and rules to follow. Otherwise, the following section contains examples of how to generate a barcode for common items in a warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:62 +msgid "For product identification using GS1 barcodes in Odoo, businesses obtain a `unique GTIN `_ as an internationally distinct product identifier purchased from GS1. This |GTIN| is combined with specific product details following GS1's designated *barcode pattern*. The barcode pattern's arrangement of numbers and letters must adhere to GS1 conventions for accurate interpretation by global systems along the supply chain." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:68 -msgid "Product + quantity + lot" +msgid "Every barcode starts with a 2-4 digit `application identifier `_ (A.I.). This required prefix universally indicates what kind of information the barcode contains. Odoo follows GS1 rules for identifying information, as detailed in the :ref:`default GS1 rules list `. Including the relevant |AI| from the list enables Odoo to correctly interpret GS1 barcodes. While most barcode patterns have a fixed length requirement, certain ones, such as lots and serial numbers, have flexible length." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:70 -msgid "To build a GS1 barcode for a box that contains a product, number of units in it, and the lot number, the following barcode patterns are used:" +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:77 +msgid "For flexible-length barcode patterns not placed at the end of the GS1 barcode, use the FNC1 separator (`\\\\x1D`) to end the barcode." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:74 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:188 -msgid "Name" +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:80 +msgid "Example: The barcode pattern for lot numbers is 20 characters long. Instead of creating a 20-character lot number barcode, like `LOT00000000000000001`, use the FNC1 separator to make it shorter: `LOT001\\x1D`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:74 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:188 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:302 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:84 +msgid "Refer to the :ref:`GS1 nomenclature list ` to see a comprehensive list of all barcode patterns and rules to follow. Otherwise, refer to :ref:`this GS1 usage doc ` for specific examples of combining |GTIN| to product information and configuring the workflow." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:90 +msgid ":ref:`Lots workflow `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:91 +msgid ":ref:`Non-unit quantities workflow `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:96 +msgid "Create rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:98 +msgid "GS1 rules are a specific format of information contained in the barcode, beginning with an |AI| and containing a defined length of characters. Scanning GS1 barcodes from the :ref:`default GS1 list ` auto-fills corresponding data in the Odoo database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:103 +msgid "Adding GS1 barcode rules in Odoo ensures accurate interpretation of unique, non-standard GS1 formats." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:106 +msgid "To do so, begin by turning on :ref:`developer mode ` and navigating to the :guilabel:`Barcode Nomenclatures` list in :menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures`. Then, select the :guilabel:`Default GS1 Nomenclature` list item." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:110 +msgid "On the :guilabel:`Default GS1 Nomenclature` page, select :guilabel:`Add a line` at the bottom of the table, which opens a window to create a new rule. The :guilabel:`Rule Name` field is used internally to identify what the barcode represents. The barcode :guilabel:`Types` are different classifications of information that can be understood by the system (e.g. product, quantity, best before date, package, coupon). The :guilabel:`Sequence` represents the priority of the rule; this means the smaller the value, the higher the rule appears on the table. Odoo follows the sequential order of this table and will use the first rule it matches based on the sequence. The :guilabel:`Barcode Pattern` is how the sequence of letters or numbers is recognized by the system to contain information about the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:120 +msgid "After filling in the information, click the :guilabel:`Save & New` button to make another rule or click :guilabel:`Save & Close` to save and return to the table of rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:126 +msgid "Barcode troubleshooting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:128 +msgid "Since GS1 barcodes are challenging to work with, here are some checks to try when the barcodes are not working as expected:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:131 +msgid "Ensure that the :guilabel:`Barcode Nomenclature` setting is set as :menuselection:`Default GS1 Nomenclature`. Jump to the :ref:`nomenclature setup section ` for more details." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:134 +msgid "Ensure that the fields scanned in the barcode are enabled in Odoo. For example, to scan a barcode containing lots and serial numbers, make sure the :guilabel:`Lots & Serial Numbers` feature is enabled in :ref:`Odoo's settings ` and :ref:`on the product `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:138 +msgid "Omit punctuation such as parentheses `()` or brackets `[]` between the :abbr:`A.I. (Application Identifier)` and the barcode sequence. These are typically used in examples for ease of reading and should **not** be included in the final barcode. For more details on building GS1 barcodes, go to :ref:`this section `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:142 +msgid "When a single barcode contains multiple encoded fields, Odoo requires all rules to be listed in the barcode nomenclature for Odoo to read the barcode. :ref:`This section ` details how to add new rules in the barcode nomenclature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:146 +msgid "Test barcodes containing multiple encoded fields, piece by piece, to figure out which field is causing the issue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:150 +msgid "When testing a barcode containing the |GTIN|, lot number, and quantity, start by scanning the |GTIN| alone. Then, test the |GTIN| with the lot number, and finally, try scanning the whole barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:154 +msgid "After diagnosing the encoded field is unknown, :ref:`add new rules ` to Odoo's default list to recognize GS1 barcodes with unique specifications." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:159 +msgid "While the new field will be read, the information won't link to an existing field in Odoo without developer customizations. However, adding new rules is necessary to ensure the rest of the fields in the barcode are interpreted correctly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:166 +msgid "GS1 nomenclature list" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:168 +msgid "The table below contains Odoo's default list of GS1 rules. Barcode patterns are written in regular expressions. Only the first three rules require a `check digit `_ as the final character." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:173 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:166 msgid "Rule Name" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:74 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:188 -msgid "A.I." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:173 +msgid "Type" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:74 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:188 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:302 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:173 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:166 msgid "Barcode Pattern" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:74 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:188 -msgid "Field in Odoo" +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:173 +msgid "GS1 Content Type" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:76 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:190 -msgid "Product" +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:173 +msgid "Odoo field" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:76 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:190 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:306 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:175 +msgid "Serial Shipping Container Code" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:175 +msgid "Package" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:175 +msgid "(00)(\\\\d{18})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:175 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:180 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:183 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:186 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:189 +msgid "Numeric identifier" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:175 +msgid "Package name" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:168 msgid "Global Trade Item Number (GTIN)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:76 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:190 -msgid "01" +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:180 +msgid "Unit Product" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:76 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:190 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:306 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:168 msgid "(01)(\\\\d{14})" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:76 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:190 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:306 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:168 msgid ":guilabel:`Barcode` field on product form" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:79 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:335 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:337 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:340 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:342 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:344 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:346 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:348 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:350 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:352 -msgid "Quantity" +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:180 +msgid "GTIN of contained trade items" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:79 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:193 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:335 -msgid "Variable count of items" +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:180 +msgid "(02)(\\\\d{14})" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:79 -msgid "30" +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:180 +msgid "Packaging" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:79 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:335 -msgid "(30)(\\\\d{0,8})" +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:183 +msgid "Ship to / Deliver to global location" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:79 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:193 -msgid ":guilabel:`Units` field on transfer form" +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:183 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:186 +msgid "Destination location" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:81 -msgid "Lot Number" +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:183 +msgid "(410)(\\\\d{13})" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:81 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:320 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:186 +msgid "Ship / Deliver for forward" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:186 +msgid "(413)(\\\\d{13})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:186 +msgid "Source location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:189 +msgid "I.D. of a physical location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:189 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:17 +msgid "Location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:189 +msgid "(414)(\\\\d{13})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:191 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:45 msgid "Batch or lot number" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:191 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:194 +msgid "Lot" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:191 +msgid "(10) ([!\"%-/0-9:-?A-Z_a-z]{0,20})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:191 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:194 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:225 +msgid "Alpha-numeric name" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:194 +msgid "Serial number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:194 +msgid "(21) ([!\"%-/0-9:-?A-Z_a-z]{0,20})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:197 +msgid "Packaging date (YYMMDD)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:197 +msgid "Packaging Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:197 +msgid "(13)(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:197 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:200 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:203 +msgid "Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:197 +msgid "Pack date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:200 +msgid "Best before date (YYMMDD)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:200 +msgid "Best before Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:200 +msgid "(15)(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:200 +msgid "Best before date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:203 +msgid "Expiration date (YYMMDD)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:203 +msgid "Expiration Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:203 +msgid "(17)(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:203 +msgid "Expiry date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:171 +msgid "Variable count of items" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:208 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:211 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:213 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:215 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:217 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:219 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:221 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:223 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:43 +msgid "Quantity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:43 +msgid "(30)(\\\\d{0,8})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:208 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:211 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:213 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:215 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:217 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:219 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:221 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:223 +msgid "Measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:206 +msgid "UoM: Units" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:208 +msgid "Count of trade items" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:208 +msgid "(37)(\\\\d{0,8})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:208 +msgid "Qty in units for containers (AI 02)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:211 +msgid "Net weight: kilograms (kg)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:211 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:171 +msgid "(310[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:211 +msgid "Qty in kg" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:213 +msgid "Length in meters (m)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:213 +msgid "(311[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:213 +msgid "Qty in m" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:215 +msgid "Net volume: liters (L)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:215 +msgid "(315[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:215 +msgid "Qty in L" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:217 +msgid "Net volume: cubic meters (m\\ :sup:`3`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:217 +msgid "(316[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:217 +msgid "Qty in m\\ :sup:`3`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:219 +msgid "Length in inches (in)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:219 +msgid "(321[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:219 +msgid "Qty in inches" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:221 +msgid "Net weight/volume: ounces (oz)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:221 +msgid "(357[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:221 +msgid "Qty in oz" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:223 +msgid "Net volume: cubic feet (ft\\ :sup:`3`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:223 +msgid "(365[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:223 +msgid "Qty in ft\\ :sup:`3`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:225 +msgid "Packaging type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:225 +msgid "Packaging Type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:225 +msgid "(91) ([!\"%-/0-9:-?A-Z_a-z]{0,90})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:225 +msgid "Package type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:3 +msgid "GS1 barcode usage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:10 +msgid "GS1 barcodes provide a standardized format that barcode scanners can interpret. They encode information in a :ref:`specific structure recognized globally `, allowing scanners to understand and process supply chain data consistently." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:14 +msgid "Odoo *Barcode* interprets and prints GS1 barcodes, automating product identification and tracking in warehouse operations such as receiving, picking, and shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:17 +msgid "The following sections contain examples of how Odoo uses GS1 barcodes provided by the business to identify common warehouse items and automate certain warehouse workflows." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:21 +msgid "Odoo **does not** create GS1 barcodes. Businesses must purchase a unique Global Trade Item Number (GTIN) from GS1. Then, they can combine their existing GS1 barcodes with product and supply chain information (also provided by GS1) to create barcodes in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:26 +msgid "`Purchase GTINs `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:27 +msgid ":ref:`GS1 nomenclature `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:32 +msgid "Configure barcodes for product, quantity, and lots" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:34 +msgid "To build a GS1 barcode that contains information about a product, its quantities, and the lot number, the following barcode patterns and Application Identifiers (A.I.) are used:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:166 +msgid "Name" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:166 +msgid "A.I." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:166 +msgid "Field in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:168 +msgid "Product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:135 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:168 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:203 +msgid "01" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:139 +msgid "30" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:171 +msgid ":guilabel:`Units` field on transfer form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:45 +msgid "Lot Number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:143 msgid "10" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:45 msgid "(10)([!\"%-/0-9:-?A-Z_a-z]{0,20})" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:45 msgid ":guilabel:`Lot` on Detailed Operations pop-up" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:88 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:52 #: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:14 #: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:53 #: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:11 #: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:18 #: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_three_steps.rst:16 #: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:11 -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:42 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:44 #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:18 #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:18 #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:84 @@ -384,502 +810,225 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:17 #: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:14 #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:23 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:9 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:11 #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:15 msgid "Configuration" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:90 -msgid "To track products using lots, first enable the :ref:`Lots and Serial Numbers ` feature. To do so, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Next, under the :guilabel:`Traceability` heading, check the box for :guilabel:`Lots & Serial Numbers`." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:54 +msgid "First, :ref:`enable product tracking using lots ` by navigating to :menuselection:`Inventory app --> Configuration --> Settings`, and checking the box for :guilabel:`Lots & Serial Numbers` under the :guilabel:`Traceability` heading." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:95 -msgid "Then, set up the product barcode by navigating to the intended product form in :menuselection:`Inventory app --> Products --> Products` and selecting the product. On the product form, click :guilabel:`Edit`. Then, in the :guilabel:`General Information` tab, fill in the :guilabel:`Barcode` field with the 14-digit `Global Trade Item Number (GTIN) `_, which is a universal and unique identifying number from GS1." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:58 +msgid "Then, set up the product barcode by navigating to the intended product form in :menuselection:`Inventory app --> Products --> Products` and selecting the product. On the product form, click :guilabel:`Edit`. Then, in the :guilabel:`General Information` tab, fill in the :guilabel:`Barcode` field with the unique 14-digit `Global Trade Item Number (GTIN) `_, which is a universally recognized identifying number that is provided by GS1." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:103 -msgid "On the product form, omit the :abbr:`A.I. (application identifier)` `01` for GTIN product barcode pattern, as it is only used to encode multiple barcodes into a single barcode that contains detailed information about the package contents." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:66 +msgid "On the product form, omit the |AI| `01` for |GTIN| product barcode pattern, as it is only used to encode multiple barcodes into a single barcode that contains detailed information about the package contents." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:108 -msgid "To create a barcode for the product, `Fuji Apple`, enter the 14-digit GTIN `12345678901231` in the :guilabel:`Barcode` field on the product form." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:72 +msgid "To record the GS1 barcode for the product, `Fuji Apple`, enter the 14-digit |GTIN| `20611628936004` in the :guilabel:`Barcode` field on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:0 msgid "Enter 14-digit GTIN into the Barcode field on product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:116 -msgid "It is also possible to view a list of all products and barcodes. To access this list, go to :menuselection:`Inventory --> Configuration --> Settings`. Under the :guilabel:`Barcode` heading, click on the :guilabel:`Configure Product Barcodes` button under the :guilabel:`Barcode Scanner` section. Enter the 14-digit GTIN into the :guilabel:`Barcode` column, then click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:80 +msgid "To view a list of *all* products and their corresponding barcodes in the Odoo database, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Barcode` heading, click on the :guilabel:`Configure Product Barcodes` button under the :guilabel:`Barcode Scanner` section. Enter the 14-digit |GTIN| into the :guilabel:`Barcode` column, then click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:0 msgid "View the Product Barcodes page from inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:128 -msgid "Next, enable lots and serial number tracking on the product. Select the :guilabel:`Inventory` tab on the product form. Under :guilabel:`Tracking`, choose the :guilabel:`By Lots` radio button." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:92 +msgid "After activating tracking by lots and serial numbers from the settings page, specify that this feature is to be applied on each product by navigating to the :guilabel:`Inventory` tab on the product form. Under :guilabel:`Tracking`, choose the :guilabel:`By Lots` radio button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:-1 msgid "Enable product tracking by lots in the \"Inventory\" tab of the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:136 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:198 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:176 msgid "Scan barcode on receipt" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:138 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:103 msgid "To ensure accurate lot interpretation in Odoo on product barcodes scanned during a receipt operation, navigate to the :menuselection:`Barcode` app to manage the :ref:`receipt picking process `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:142 -msgid "From the :guilabel:`Barcode Scanning` dashboard, click the :guilabel:`Operations` button, then the :guilabel:`Receipts` button to view the list of vendor receptions to process. Receipts generated from :abbr:`POs (Purchase Orders)` are listed, but new receipt operations can also be created directly through the :menuselection:`Barcode` app using the :guilabel:`Create` button." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:107 +msgid "From the :guilabel:`Barcode Scanning` dashboard, click the :guilabel:`Operations` button, then the :guilabel:`Receipts` button to view the list of vendor receipts to process. Receipts generated from :abbr:`POs (Purchase Orders)` are listed, but new receipt operations can also be created directly through the :menuselection:`Barcode` app using the :guilabel:`Create` button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:147 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:112 msgid "On the list of receipts, click on the warehouse operation (`WH/IN`) and scan product barcodes and lot numbers with a barcode scanner. The scanned product then appears on the list. Use the :guilabel:`✏️ (pencil)` button to open a window and manually enter quantities for specific lot numbers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:153 -msgid "After placing a :abbr:`PO (Purchase Order)` for 50 apples, navigate to the associated receipt. Scan the product barcode, and Odoo will prompt for the lot number." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:118 +msgid "After placing a :abbr:`PO (Purchase Order)` for fifty apples, navigate to the associated receipt in the *Barcode* app." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:121 +msgid "Scan the barcode containing the |GTIN|, quantity, and lot number. For testing with a barcode scanner, below is an example barcode for the fifty Fuji apples in Lot 2." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:129 +msgid "50 Fuji apples in Lot0002" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:131 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:199 +msgid "2D Matrix" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:0 +msgid "2D matrix of GS1 barcode of 50 fuji apples with an assigned lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:134 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:202 +msgid "|AI| (product)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:136 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:204 +msgid "GS1 Barcode (product)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:137 +msgid "20611628936004" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:138 +msgid "|AI| (quantity)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:140 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:208 +msgid "GS1 Barcode (quantity)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:141 +msgid "00000050" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:142 +msgid "|AI| (lot)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:144 +msgid "GS1 Barcode (lot #)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:145 +msgid "LOT0002" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:146 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:210 +msgid "Full GS1 barcode" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:147 +msgid "01206116289360043 000000050 10LOT0002" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:149 +msgid ":ref:`If the configuration is correct `, `50/50` :guilabel:`Units` processed will be displayed and the :guilabel:`Validate` button turns green. Click the :guilabel:`Validate` button to complete the reception." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:0 msgid "Scan the barcode for a product on the reception picking page in the *Barcode* app." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:160 -msgid "Scan the lot number to process 1 of 50 apples. To avoid scanning 49 remaining barcodes, click the :guilabel:`✏️ (pencil)` button next to the desired lot number." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:160 +msgid "Configure barcode for product and non-unit quantity" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:0 -msgid "Scan lot number and click the pencil to edit quantities." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:167 -msgid "Doing so opens a mobile-friendly keypad page to specify received quantities. Use the keypad to specify the :guilabel:`Units` for the lot number. When finished, click :guilabel:`Confirm`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:0 -msgid "Change scanned quantities using pencil button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:174 -msgid "Repeat this process to specify additional lot numbers and quantities in this receipt. Once the :guilabel:`Units` are all accounted for, finish the reception by clicking the :guilabel:`Validate` button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:178 -msgid "Alternatively, scan the barcode containing the product, lot number, and quantity to complete the receipt operation in fewer steps." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:182 -msgid "Product + non-unit quantity" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:184 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:162 msgid "To build a GS1 barcode that contains products measured in a non-unit quantity, like kilograms, for example, the following barcode patterns are used:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:193 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:171 msgid "Quantity in kilograms" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:193 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:171 msgid "310[0-5]" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:193 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:340 -msgid "(310[0-5])(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:200 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:178 msgid "To confirm that quantities are correctly interpreted in Odoo, place an order in the *Purchase* app using the appropriate unit of measure (:guilabel:`UoM`) for the quantity of products to be purchased." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:205 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:183 msgid ":ref:`Simplify vendor unit conversions with UoMs `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:207 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:185 msgid "After the order is placed, navigate to the :menuselection:`Barcode` app to :ref:`receive the vendor shipment `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:211 -msgid "On the receipt in the *Barcode* app, receive an order for `52.1 kg` of peaches by scanning the barcode. If `52.1 / 52.1` :guilabel:`kg` appears on the page, this means the reception was processed without issue. Finally, press :guilabel:`Validate`." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:189 +msgid "On the receipt in the *Barcode* app, receive an order for `52.1 kg` of peaches by scanning the barcode containing the |GTIN| and quantity of peaches in kilograms." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:215 -msgid "Note: the :abbr:`A.I. (application identifier)` for kilograms, `310` + `1`, was used to represent `52.1` kg as a barcode: `000521`. This is because the `1` represents how many digits from the right to place the decimal point." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:197 +msgid "52.1 kg of Peaches" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:0 +msgid "2D matrix of GS1 barcode of 52.1 kg of peaches." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:205 +msgid "00614141000012" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:206 +msgid "|AI| (kg, 1 decimal point)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:207 +msgid "3101" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:209 +msgid "000521" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:211 +msgid "0100614141000012 3101000521" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:213 +msgid ":ref:`If the configuration is correct `, `52.1 / 52.1` :guilabel:`kg` will be displayed and the :guilabel:`Validate` button turns green. Finally, press :guilabel:`Validate` to complete the validation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:0 msgid "Scan barcode screen for a reception operation in the Barcode app." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:223 -msgid "For additional verification purposes, the quantities of received products are also recorded on the :guilabel:`Product Moves` report, accessible by navigating to :menuselection:`Inventory app --> Reporting --> Product Moves`." +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:222 +msgid "Verify product moves" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:227 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:224 +msgid "For additional verification, the quantities of received products are also recorded on the :guilabel:`Product Moves` report, accessible by navigating to :menuselection:`Inventory app --> Reporting --> Product Moves`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:228 msgid "The items on the :guilabel:`Product Moves` report are grouped by product by default. To confirm the received quantities, click on a product line to open its collapsible drop-down menu, which displays a list of *stock move lines* for the product. The latest stock move matches the warehouse reception reference number (e.g. `WH/IN/00013`) and quantity processed in the barcode scan, demonstrating that the records processed in the *Barcode* app were properly stored in *Inventory*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:-1 msgid "Reception stock move record for 52.1 kg of peaches." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:240 -msgid "Create rules" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:242 -msgid "If a supplier uses a GS1 barcode with a field not supported by Odoo's :ref:`default GS1 list `, Odoo will fail to interpret the entire barcode. To ensure the complete reading of the barcode, it is necessary to add the missing barcode to Odoo's list." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:248 -msgid "While the new field will be read, the information won't link to an existing field in Odoo without developer customizations. However, adding new rules is still useful to ensure the rest of the fields in the barcode are interpreted correctly." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:252 -msgid "Begin by turning on :ref:`developer mode ` and navigating to the :guilabel:`Barcode Nomenclatures` list in :menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures`. Then, select the :guilabel:`Default GS1 Nomenclature` list item." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:256 -msgid "On the :guilabel:`Default GS1 Nomenclature` page, select :guilabel:`Add a line` at the bottom of the table, which opens a window to create a new rule. The :guilabel:`Rule Name` field is used internally to identify what the barcode represents. The barcode :guilabel:`Types` are different classifications of information that can be understood by the system (e.g. product, quantity, best before date, package, coupon). The :guilabel:`Sequence` represents the priority of the rule; this means the smaller the value, the higher the rule appears on the table. Odoo follows the sequential order of this table and will use the first rule it matches based on the sequence. The :guilabel:`Barcode Pattern` is how the sequence of letters or numbers is recognized by the system to contain information about the product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:266 -msgid "After filling in the information, click the :guilabel:`Save & New` button to make another rule or click :guilabel:`Save & Close` to save and return to the table of rules." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:272 -msgid "Barcode troubleshooting" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:274 -msgid "Since GS1 barcodes are challenging to work with, here are some checks to try when the barcodes are not working as expected:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:277 -msgid "Ensure that the :guilabel:`Barcode Nomenclature` setting is set as :menuselection:`Default GS1 Nomenclature`. Jump to the :ref:`nomenclature setup section ` for more details." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:280 -msgid "Ensure that the fields scanned in the barcode are enabled in Odoo. For example, to scan a barcode containing lots and serial numbers, make sure the :guilabel:`Lots & Serial Numbers` feature is enabled in :ref:`Odoo's settings ` and :ref:`on the product `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:284 -msgid "Omit punctuation such as parentheses `()` or brackets `[]` between the :abbr:`A.I. (Application Identifier)` and the barcode sequence. These are typically used in examples for ease of reading and should **not** be included in the final barcode. For more details on building GS1 barcodes, go to :ref:`this section `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:288 -msgid "When a single barcode contains multiple encoded fields, Odoo requires all rules to be listed in the barcode nomenclature for Odoo to read the barcode. :ref:`This section ` details how to add new rules in the barcode nomenclature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:295 -msgid "GS1 nomenclature list" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:297 -msgid "The table below contains Odoo's default list of GS1 rules. Barcode patterns are written in regular expressions. Only the first three rules require a `check digit `_ as the final character." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:302 -msgid "Type" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:302 -msgid "GS1 Content Type" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:302 -msgid "Odoo field" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:304 -msgid "Serial Shipping Container Code" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:304 -msgid "Package" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:304 -msgid "(00)(\\\\d{18})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:304 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:306 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:309 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:312 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:315 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:318 -msgid "Numeric identifier" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:304 -msgid "Package name" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:306 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:309 -msgid "Unit Product" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:309 -msgid "GTIN of contained trade items" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:309 -msgid "(02)(\\\\d{14})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:309 -msgid "Packaging" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:312 -msgid "Ship to / Deliver to global location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:312 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:315 -msgid "Destination location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:312 -msgid "(410)(\\\\d{13})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:315 -msgid "Ship / Deliver for forward" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:315 -msgid "(413)(\\\\d{13})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:315 -msgid "Source location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:318 -msgid "I.D. of a physical location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:318 -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:15 -msgid "Location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:318 -msgid "(414)(\\\\d{13})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:320 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:323 -msgid "Lot" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:320 -msgid "(10) ([!\"%-/0-9:-?A-Z_a-z]{0,20})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:320 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:323 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:354 -msgid "Alpha-numeric name" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:323 -msgid "Serial number" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:323 -msgid "(21) ([!\"%-/0-9:-?A-Z_a-z]{0,20})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:326 -msgid "Packaging date (YYMMDD)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:326 -msgid "Packaging Date" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:326 -msgid "(13)(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:326 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:329 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:332 -msgid "Date" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:326 -msgid "Pack date" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:329 -msgid "Best before date (YYMMDD)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:329 -msgid "Best before Date" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:329 -msgid "(15)(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:329 -msgid "Best before date" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:332 -msgid "Expiration date (YYMMDD)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:332 -msgid "Expiration Date" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:332 -msgid "(17)(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:332 -msgid "Expiry date" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:335 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:337 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:340 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:342 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:344 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:346 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:348 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:350 -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:352 -msgid "Measure" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:335 -msgid "UoM: Units" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:337 -msgid "Count of trade items" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:337 -msgid "(37)(\\\\d{0,8})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:337 -msgid "Qty in units for containers (AI 02)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:340 -msgid "Net weight: kilograms (kg)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:340 -msgid "Qty in kg" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:342 -msgid "Length in meters (m)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:342 -msgid "(311[0-5])(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:342 -msgid "Qty in m" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:344 -msgid "Net volume: liters (L)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:344 -msgid "(315[0-5])(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:344 -msgid "Qty in L" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:346 -msgid "Net volume: cubic meters (m\\ :sup:`3`)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:346 -msgid "(316[0-5])(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:346 -msgid "Qty in m\\ :sup:`3`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:348 -msgid "Length in inches (in)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:348 -msgid "(321[0-5])(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:348 -msgid "Qty in inches" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:350 -msgid "Net weight/volume: ounces (oz)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:350 -msgid "(357[0-5])(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:350 -msgid "Qty in oz" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:352 -msgid "Net volume: cubic feet (ft\\ :sup:`3`)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:352 -msgid "(365[0-5])(\\\\d{6})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:352 -msgid "Qty in ft\\ :sup:`3`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:354 -msgid "Packaging type" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:354 -msgid "Packaging Type" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:354 -msgid "(91) ([!\"%-/0-9:-?A-Z_a-z]{0,90})" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:354 -msgid "Package type" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst:3 msgid "Process to Transfers" msgstr "" @@ -2780,274 +2929,371 @@ msgid "Planning" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:3 -msgid "How is the Scheduled Delivery Date Computed" +msgid "Scheduled delivery dates" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:5 -msgid "Providing the best possible service to customers is vital for business. It implies planning every move: manufacturing orders, deliveries, receptions, and so on. To do so, you need to configure lead time properly and coordinate scheduled dates." +msgid "Accurately forecasting delivery dates is vital for fulfilling customer expectations. In Odoo, the *Inventory* app allows for comprehensive lead time configuration, allowing coordination and planning of manufacturing orders, deliveries, and receptions." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:9 -msgid "By using lead times, Odoo provides end dates, the **Commitment Date**, for each process. On a sales order, for example, this is the date your customer will get the products he ordered." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:10 +msgid "Lead time types" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:13 -msgid "From the customers’ side, the commitment date is important because it gives them an estimation of when they will receive their products. The dates take all other lead times, such as manufacturing, delivery, or suppliers, into account." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:12 +msgid "Different lead times for different operations can impact various stages of the order fulfillment process. Here's a summary of the types of lead times in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 +msgid "Show graphic of all lead times working together." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:19 -msgid "How are Lead Times Calculated?" +msgid ":ref:`Customer lead time `: The default time frame for fulfilling customer orders. The customer lead time is the number of days from the date the sales order (SO) is confirmed to the date the products are shipped from the warehouse. This is also known as *delivery lead time*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:27 -msgid "As said above, there are several types of lead times. Each is calculated based on various indicators. Before going through the configuration, here is a brief summary of how lead times are calculated and what they are:" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:24 +msgid ":ref:`Sales security lead time `: moves the *scheduled delivery date* forward by a specified number of days. This serves as a buffer to allow the team ample time to prepare the outgoing shipment earlier, considering the possibility of delays in the fulfillment process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:32 -msgid "**Customer Lead Time**: the customer lead time is the default duration you set. Therefore, the expected date on the sales orders is today + customer lead time." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:29 +msgid ":ref:`Purchase lead time `: the number of days from the confirmation of a purchase order (PO) to the receipt of products. It provides insight on the time it takes for products to arrive at the warehouse, facilitating effective scheduling and planning of supplier deliveries." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:36 -msgid "**Sales Security Lead Time**: the purpose is to be ready shipping that many days before the actual commitment taken with the customer. Then, the default scheduled date on the delivery order is **SO delivery date - Security Lead Time**." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:34 +msgid ":ref:`Purchase security lead time `: advances the order deadline on a :abbr:`PO (Purchase Order)` by a specified number of days. This proactive approach of placing orders earlier mitigates the risk of vendor or shipping delays. Thus, for products that are set to replenish to order, the need appears on the *Replenishment report* earlier, according to the specified number of days." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:41 -msgid "**Purchase Security Lead Time**: margin of error for vendor lead times. When the system generates Purchase Orders for procuring products, they will be scheduled that many days earlier to cope with unexpected vendor delays." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:40 +msgid ":ref:`Manufacturing lead time `: the number of days needed to complete a manufacturing order (MO) from the date of confirmation. This lead time includes weekends (non-working hours in Odoo), and is used to forecast an approximate production date for a finished good." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:46 -msgid "**Purchase Delivery Lead Time**: this is the expected time between a PO being confirmed and the receipt of the ordered products. The **Receipt scheduled date - Vendor delivery date** is the default *PO Order By* date." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:45 +msgid ":ref:`Manufacturing security lead time `: moves the scheduled date of the :abbr:`MO (Manufacturing Order)` forward by a specified number of days. When used in conjunction with :ref:`replenish to order `, the security lead time makes the need appear earlier on the replenishment report." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:51 -msgid "**Days to Purchase**: number of days the purchasing department takes to validate a PO. If another RFQ to the same vendor is already opened, Odoo adds the line to the RFQ instead of creating a new one. Then, the specific date is set on the line." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:53 +msgid "Sales lead times" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:56 -msgid "**Manufacturing Lead Time**: this is the expected time it takes to manufacture a product. This lead time is independent of the quantity to produce and does not take the routing time into account." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:55 +msgid "Customer lead times and sales security lead times can be configured to automatically compute an *expected delivery date* on a :abbr:`SO (Sales Order)`. The expected delivery date ensures a realistic *delivery dates* setting for shipments from the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:61 -msgid "**Manufacturing Security Lead Time**: additional time to mitigate the risk of a manufacturing delay. In case of a *Replenish to Order*, the **Delivery Order scheduled date - Manufacturing Lead Time - Manufacturing Security Lead Time** is the default *Manufacturing Order* planned date." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:59 +msgid "Odoo issues a warning message if the set delivery date is earlier than the expected date, as it may not be feasible to fulfill the order by that time, which would impact other warehouse operations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:68 -msgid "Sales - Lead Times" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:63 +msgid "A :abbr:`SO (Sales Order)` containing a `Coconut-scented candle` is confirmed on July 11th. The product has a customer lead time of 14 days, and the business uses a sales security lead time of 1 day. Based on the lead time inputs, Odoo suggests a delivery date in 15 days, on July 26th." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:70 -msgid "In the *Sales* app, there is an option called *Delivery Date*. It allows seeing an additional field on the sales orders, *Expected Date*. This one is automatically computed based on the different lead times previously configured." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:0 +msgid "Set *Delivery Date* in a sales order. Enables delivery lead times feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 -msgid "View of the delivery settings to have the delivery lead time taken into account" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:71 +msgid "The following sections demonstrate how to automatically compute expected delivery dates." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:79 -msgid "If the set up *Delivery Date* is earlier than the the *Expected Date*, a warning message is displayed." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:74 +msgid "Customer lead time" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 -msgid "View of the error that occurs when trying to choose an earlier date than what calculated\n" -"by Odoo" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:76 +msgid "Set the customer lead time on each product form, by navigating to the products page. To do so, go to :menuselection:`Sales app --> Products --> Products`. From there, select the desired product, and switch to the :guilabel:`Inventory` tab. Then, under the :guilabel:`Customer Lead Time` field, fill in the number of calendar days required to fulfill the delivery order from start to finish." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:87 -msgid "But, for all of this properly working, it is still necessary to configure all the lead times that could occur." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:82 +msgid "Set a 14-day customer lead time for the `Coconut-scented candle` by navigating to its product form. Then, in the :guilabel:`Inventory` tab, type `14.00` days into the :guilabel:`Customer Lead Time` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:91 -msgid "Customer Lead Time" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:0 +msgid "Set *Customer Lead Time* on the product form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:93 -msgid "The *Customer Lead Time* is the time needed for your product to go from your warehouse to the customer place. It can be configured on any product by going to :menuselection:`Sales --> Products --> Products`. There, open your product form, go in the inventory tab, and add your *Customer Lead Time*." +msgid "Sales security lead time" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 -msgid "View of the customer lead time configuration from the product form" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:95 +msgid "*Sales security lead time* is set globally for the business in :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:103 -msgid "For example, product B is ordered on the 2nd of April but the *Customer Lead Time* is two days. In that case, the expected delivery date is the 4th of April." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:98 +msgid "On the configuration page, under the :guilabel:`Advanced Scheduling` heading, locate the box for :guilabel:`Security Lead Time for Sales`, and click the checkbox to enable the feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:108 -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:180 -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:217 -msgid "Security Lead Time" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:101 +msgid "Next, enter the desired number of calendar days. This security lead time is a buffer notifying the team to prepare for outgoing shipments earlier than the scheduled date." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:110 -msgid "In sales, *Security Lead Time* corresponds to backup days to ensure you are able to deliver the products in time. The purpose is to be ready shipping earlier in order to arrive on time." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:105 +msgid "Setting the :guilabel:`Security Lead Time for Sales` to `1.00` day, pushes the :guilabel:`Scheduled Date` of a delivery order (DO) forward by one day. In that case, if a product is initially scheduled for delivery on April 6th, but with a one-day security lead time, the new scheduled date for the delivery order would be April 5th." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:114 -msgid "The number of security days is subtracted from the calculation to compute a scheduled date earlier than the one promised to the customer." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:0 +msgid "View of the security lead time for sales configuration from the sales settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:117 -msgid "To set this up, go to :menuselection:`Inventory --> Configuration --> Settings` and enable the feature *Security Lead Time for Sales*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 -msgid "View of the security lead time for sales configuration from the sales settings" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:124 -msgid "For example, product B is scheduled to be delivered on the 6th of April but the *Security Lead Time* is one day. In that case, the scheduled date for the delivery order is the 5th of April." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:129 +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:115 msgid "Deliver several products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:131 -msgid "In many cases, customers order several products at the same time. Those can have different lead times but still need to be delivered, at once or separately. Fortunately, Odoo can help you handle these cases easily." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:117 +msgid "For orders that include multiple products with different lead times, the lead times can be configured directly from the quotation itself. On a quotation, click the :guilabel:`Other Info` tab, and set the :guilabel:`Shipping Policy` to:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:135 -msgid "From the *Other Info* tab of your *Sale Order*, you can choose between *When all products are ready* and *As soon as possible*. The first one is to deliver products at once, while the second is to deliver them separately." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:121 +msgid ":guilabel:`As soon as possible` to deliver products as soon as they are ready. The :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is determined by adding today's date to the shortest lead time among the products in the order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:140 -msgid "For example, products A and B are ordered at the same time. A has 8 lead days and B has 5. With the first option, the *Expected Date* is calculated based on the product with the most lead days, here A. If the order is confirmed on the 2nd of April, then the *Expected Date* is on the 10th of April." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:125 +msgid ":guilabel:`When all products are ready` to wait to fulfill the entire order at once. The :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is determined by adding today's date to the longest lead time among the products in the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 +msgid "Show *Shipping Policy* field in the *Other Info* tab of a quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:134 +msgid "In a quotation containing 2 products, `Yoga mat` and `Resistance band,` the products have a lead time of 8 days and 5 days, respectively. Today's date is April 2nd." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:137 +msgid "When the :guilabel:`Shipping Policy` is set to :guilabel:`As soon as possible`, the scheduled delivery date is 5 days from today: April 7th. On the other hand, selecting :guilabel:`When all products are ready` configures the scheduled date to be 8 days from today: April 10th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:144 +msgid "Purchase lead times" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:146 -msgid "With the second option, the *Expected Date* is calculated based on the product with the least customer lead days. In this example, B is the product with the least lead days. So, the *Expected Date* is on the 7th of April." +msgid "Automatically determining the dates on which to place orders from suppliers can help simplify the procurement process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:152 -msgid "Purchase - Lead Times" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:149 +msgid "Odoo calculates the supplier shipment *receipt date*, and :abbr:`PO (Purchase Order)` deadline, based on the required date the product is needed in the warehouse. By working backwards from the receipt date, vendor lead times and purchase security lead times are taken into account, in order to determine the :abbr:`PO (Purchase Order)` deadline." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:155 -msgid "Supplier Lead Time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:157 -msgid "The *Supplier Lead Time* is the time needed for a product you purchased to be delivered. To configure it, open a product from :menuselection:`Purchase --> Products --> Products` and add a vendor under the *Purchase* tab." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:154 +msgid "This deadline is the date by which the order should be confirmed, in order to ensure timely arrival by the expected receipt date." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 -msgid "View of the way to add vendors to products" +msgid "Visualization of PO deadline and receipt date used with vendor lead times." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:166 -msgid "By clicking on *Add a line*, a new window is displayed. You can specify the *Delivery Lead Time* there. If done so, the delivery day for every purchase of that product is now equal to *Date of the Purchase Order + Delivery Lead Time*." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:162 +msgid ":ref:`PO scheduling with reordering rules `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 -msgid "View of the delivery lead time configuration from a vendor form" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:165 +msgid "Vendor lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:167 +msgid "To set a vendor lead time for orders arriving in the warehouse from a vendor location, begin by navigating to a product form through :menuselection:`Purchase app --> Products --> Products`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:170 +msgid "Next, select the desired product, and switch to the :guilabel:`Purchase` tab. In the editable vendor pricelist, click the :guilabel:`Add a line` button to add vendor details, such as the :guilabel:`Vendor` name, :guilabel:`Price` offered for the product, and lastly, the :guilabel:`Delivery Lead Time`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:176 -msgid "It is possible to add different vendors and, thus, different lead times depending on the vendor." +msgid "Multiple vendors and lead times can be added to the vendor pricelist. The default vendor and lead time selected will be the entry at the top of the list." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:182 -msgid "The *Security Lead Time* for purchase follows the same logic as the one for *Sales*, except that you are the customer. Then, it is the margin of error for your supplier to deliver your order." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:180 +msgid "On the vendor pricelist of the product form, the :guilabel:`Delivery Lead Time` for the selected vendor is set to `10 days.`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:186 -msgid "To set up *Security Lead Time* for purchase, go to :menuselection:`Inventory --> Configuration --> Settings` and enable the feature." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:0 +msgid "Add delivery lead times to vendor pricelist on a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 -msgid "View of the security lead time for purchase from the inventory settings" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:187 +msgid "By setting the vendor lead time, the expected arrival date of the item is automatically determined as the date of the :abbr:`PO (Purchase Order)` confirmation, plus the vendor lead time. This ensures that warehouse employees are notified, if the products do **not** arrive within the expected timeframe." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:194 -msgid "Doing so, every time the system generates purchase orders, those are scheduled that many days earlier to cope with unexpected vendor delays." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:193 +msgid "On a :abbr:`PO (Purchase Order)` confirmed on July 11th, for a product configured with a 10-day vendor lead time, Odoo automatically sets the :guilabel:`Receipt Date` to July 21st. The receipt date also appears as the :guilabel:`Scheduled Date` on the warehouse receipt form, accessible from the :guilabel:`Receipt` smart button, located on the :guilabel:`PO (Purchase Order)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:198 -msgid "Manufacturing - Lead Times" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:0 +msgid "Show expected *Receipt Date* of the product from the vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:201 -msgid "Manufacturing Lead Time" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:0 +msgid "Show expected *Scheduled Date* of arrival of the product from the vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:203 -msgid "The *Manufacturing Lead Time* is the time needed to manufacture the product. To specify it, open the *Inventory* tab of your product form and add the number of days the manufacturing takes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 -msgid "View of the manufacturing lead time configuration from the product form" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:209 +msgid "Purchase security lead time" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:211 -msgid "When working with *Manufacturing Lead Times*, the *Deadline Start* of the *MO* is **Commitment Date - Manufacturing Lead Time**. For example, the MO’s deadline start date for an order having a commitment date on the 10th of July is June 27th." +msgid "*Purchase security lead time* is set globally for the business in :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:219 -msgid "The *Security Lead Time* for manufacturing allows generating manufacturing orders earlier to cope with the risk of manufacturing delays." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:214 +msgid "On the configuration page, under the :guilabel:`Advanced Scheduling` heading, locate the box for :guilabel:`Security Lead Time for Purchase`, and click the checkbox to enable the feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:223 -msgid "To enable it, go to :menuselection:`Manufacturing --> Configuration --> Settings` and tick *Security Lead Time*." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:217 +msgid "Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is set to account for potential delays in supplier deliveries." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 -msgid "View of the security lead time for manufacturing from the manufacturing app settings" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:221 +msgid "Setting the :guilabel:`Security Lead Time for Purchase` to `2.00` days, pushes the :guilabel:`Scheduled Date` of receipt back by one day. In that case, if a product is initially scheduled to arrive on April 6th, with a two-day security lead time, the new scheduled date for the receipt would be April 8th." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:230 -msgid "For example, a customer orders B with a delivery date scheduled on the 20th of June. The *Manufacturing Lead Time* is 14 days and the *Security Lead Time* is 3 days, so the manufacturing of B needs to start at the latest on the 3rd of June, which is the MO’s planned date." +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:0 +msgid "Set security lead time for purchase from the Inventory > Configuration > Settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:236 -msgid "Global Example" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:233 +msgid "Manufacturing lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:235 +msgid "Lead times can help simplify the procurement process for consumable materials and components used in manufactured products with bills of materials." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:238 -msgid "Here is a configuration:" +msgid "The :abbr:`MO (Manufacturing Order)` deadline, which is the deadline to begin the manufacturing process to complete the product by the scheduled delivery date, can be determined by configuring the manufacturing lead times and manufacturing security lead times." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:240 -msgid "1 day of security lead time for Sales" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 +msgid "Visualization of the determination of planned MO date manufacturing lead times." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:241 -msgid "2 days of security lead time for Manufacturing" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:247 +msgid "Manufacturing lead time" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:242 -msgid "3 days of manufacturing lead time" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:249 +msgid "Configure the manufacturing lead time directly on the product form, by navigating to :menuselection:`Manufacturing app --> Products --> Products`, and select the desired product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:243 -msgid "1 day of security lead time for Purchase" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:244 -msgid "4 days of supplier lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:246 -msgid "Let’s say that a customer orders B on the 1st of September and the delivery date is planned to be within 20 days (September 20th). In such a scenario, here is when all the various steps are triggered." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:250 -msgid "**September 1st**: the sales order is created" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:251 -msgid "**September 10th**: the deadline to order components from the supplier because of the manufacturing process (4 days of supplier lead time)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:254 -msgid "**September 13th**: the reception of the product from the supplier (1 day of security lead time for Purchase)" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:252 +msgid "In the :guilabel:`Inventory` tab of the product, specify the calendar days needed to the manufacture the product in the :guilabel:`Manufacturing Lead Time` field." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:256 -msgid "**September 14th**: the deadline start date for the manufacturing (19th - 3 days of manufacturing lead time - 2 days of security lead time for Manufacturing)" +msgid "Specify a 14-day :guilabel:`Manufacturing Lead Time` for a product directly in the :guilabel:`Inventory` tab of the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:259 -msgid "**September 19th**: the expected date on the delivery order form (1 day of security lead time for sales)" +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:0 +msgid "View of the manufacturing lead time configuration from the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:263 +msgid "Establish a :abbr:`MO (Manufacturing Order)` deadline, based on the *expected delivery date*, indicated in the :guilabel:`Scheduled Date` field of the :abbr:`DO (Delivery Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:266 +msgid "The :abbr:`MO (Manufacturing Order)` deadline, which is the :guilabel:`Scheduled Date` field on the :abbr:`MO (Manufacturing Order)`, is calculated as the *expected delivery date* subtracted by the manufacturing lead time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:270 +msgid "This ensures the manufacturing process begins on time, in order to meet the delivery date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:272 +msgid "However, it's important to note that lead times are based on calendar days. Lead times do **not** consider weekends, holidays, or *work center capacity* (:dfn:`the number of operations that can be performed at the work center simultaneously`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:277 +msgid ":ref:`Manufacturing planning `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:278 +msgid ":ref:`Configure automatic MO scheduling with reordering rules `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:282 +msgid "A product's scheduled shipment date on the :abbr:`DO (Delivery Order)` is August 15th. The product requires 14 days to manufacture. So, the latest date to start the :abbr:`MO (Manufacturing Order)` to meet the commitment date is August 1st." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:289 +msgid "Manufacturing security lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:291 +msgid "*Manufacturing security lead time* is set globally for the business in :menuselection:`Manufacturing app --> Configuration --> Settings`. Under the :guilabel:`Planning` heading, locate the box for :guilabel:`Security Lead Time`, and click the checkbox to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:295 +msgid "Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is set to account for potential delays in the manufacturing process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 +msgid "View of the security lead time for manufacturing from the manufacturing app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:303 +msgid "A product has a scheduled shipment date on the :abbr:`DO (Delivery Order)` set for August 15th. The manufacturing lead time is 7 days, and manufacturing security lead time is 3 days. So, the :guilabel:`Scheduled Date` on the :abbr:`MO (Manufacturing Order)` reflects the latest date to begin the manufacturing order. In this example, the planned date on the :abbr:`MO (Manufacturing Order)` is August 5th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:310 +msgid "Global example" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:312 +msgid "See the following example to understand how all the lead times work together to ensure timely order fulfillment:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:315 +msgid "**Sales security lead time**: 1 day" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:316 +msgid "**Manufacturing security lead time**: 2 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:317 +msgid "**Manufacturing lead time**: 3 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:318 +msgid "**Purchase security lead time**: 1 day" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:319 +msgid "**Vendor lead time**: 4 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:321 +msgid "The customer places an order for a manufactured product on September 1st, and the scheduled delivery date from the warehouse is on September 20th. Odoo uses lead times and automated reordering rules to schedule the necessary operations, based on the outgoing shipment delivery date, September 20th:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:-1 +msgid "Show timeline of how lead times work together to schedule warehouse operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:329 +msgid "**September 1st**: Sales order created, confirmed by salesperson." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:331 +msgid "**September 9th**: Deadline to order components to ensure they arrive in time when manufacturing begins (4-day supplier lead time)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:334 +msgid "**September 13th**: Scheduled date of receipt for components. Initially, it was set to 9/14, but the 1-day purchase security lead time pushed the date earlier by 1 day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:337 +msgid "**September 14th**: Deadline to begin manufacturing. Calculated by subtracting the manufacturing lead time of 3 days, and the manufacturing security lead time of 2 days, from the expected delivery date of September 19th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:341 +msgid "**September 19th**: :guilabel:`Scheduled Date` on the delivery order form indicates the updated expected delivery date, which was originally set as September 20th. But the sales security lead time pushed the date forward by a day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:345 +msgid "Odoo's replenishment planning maps a business' order fulfillment process, setting pre-determined deadlines and raw material order dates, including buffer days for potential delays. This ensures products are delivered on time." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products.rst:5 @@ -3183,23 +3429,23 @@ msgstr "" msgid "Reordering rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:7 msgid "Reordering rules are used to keep forecasted stock levels above a certain threshold without exceeding a specified upper limit. This is accomplished by specifying a minimum quantity that stock should not fall below and a maximum quantity that stock should not exceed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:11 msgid "Reordering rules can be configured for each product based on the route used to replenish it. If a product uses the *Buy* route, then a Request for Quotation (RFQ) is created when the reordering rule is triggered. If a product uses the *Manufacture* route, then a Manufacturing Order (MO) is created instead. This is the case regardless of the selected replenishment route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:17 msgid "Configure products for reordering rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:19 msgid "In order to use reordering rules for a product, it must first be correctly configured. Begin by navigating to :guilabel:`Inventory --> Products --> Products`, then select an existing product, or create a new one by clicking :guilabel:`Create`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:23 msgid "First, on the :guilabel:`General Information` tab, make sure that the :guilabel:`Product Type` is set to :guilabel:`Storable Product`. This is necessary because Odoo only tracks stock quantities for storable products, and this number is used to trigger reordering rules." msgstr "" @@ -3207,7 +3453,7 @@ msgstr "" msgid "Set the Product Type as Storable." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:29 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:31 msgid "Next, click on the :guilabel:`Inventory` tab and select one or more routes from the :guilabel:`Routes` section. Doing so tells Odoo which route to use to replenish the product." msgstr "" @@ -3215,7 +3461,7 @@ msgstr "" msgid "Select one or more routes on the Inventory tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:38 msgid "If the product is reordered using the :guilabel:`Buy` route, confirm that the :guilabel:`Can be Purchased` checkbox is enabled under the product name. This makes the :guilabel:`Purchase` tab appear. Click on the :guilabel:`Purchase` tab, and specify at least one vendor, and the price that they sell the product for, so that Odoo knows which company the product should be purchased from." msgstr "" @@ -3223,11 +3469,11 @@ msgstr "" msgid "Specify a vendor and price on the Purchase tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:47 msgid "If the product is replenished using the :guilabel:`Manufacture` route, it needs to have at least one Bill of Materials (BoM) associated with it. This is necessary because Odoo only creates manufacturing orders for products with a :abbr:`BoM (Bill of Materials)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:51 msgid "If a :abbr:`BoM (Bill of Materials)` does not already exist for the product, select the :guilabel:`Bill of Materials` smart button at the top of the product form, then click :guilabel:`Create` to configure a new :abbr:`BoM (Bill of Materials)`." msgstr "" @@ -3235,35 +3481,35 @@ msgstr "" msgid "The Bill of Materials smart button on a product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:58 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:60 msgid "Create new reordering rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:60 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:62 msgid "To create a new reordering rule, navigate to :menuselection:`Inventory --> Configuration --> Reordering Rules`, then click :guilabel:`Create`, and fill out the new line as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:63 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:65 msgid ":guilabel:`Product`: The product that is replenished by the rule." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:66 msgid ":guilabel:`Location`: The location where the product is stored." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:67 msgid ":guilabel:`Min Quantity`: The minimum quantity that can be forecasted without the rule being triggered. When forecasted stock falls below this number, a replenishment order for the product is created." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:70 msgid ":guilabel:`Max Quantity`: The maximum quantity that stock is replenished up to." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:71 msgid ":guilabel:`Multiple Quantity`: Specify if the product should be replenished in batches of a certain quantity (e.g., a product could be replenished in batches of 20)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:73 msgid ":guilabel:`UoM`: The unit of measure used for reordering the product. This value can simply be `Units` or a specific unit of measurement for weight, length, etc." msgstr "" @@ -3271,43 +3517,43 @@ msgstr "" msgid "The form for creating a new reordering rule." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:79 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:81 msgid "Reordering rules can also be created from each product form. To do so, navigate to :menuselection:`Inventory --> Products --> Products`, then select a product. Click on :menuselection:`Reordering Rules --> Create`, then fill out the new line as detailed above." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:83 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:85 msgid "Once a reordering rule has been created for a product, if its forecasted quantity is below the rule's minimum quantity when the scheduler runs, a replenishment order for the product is automatically generated. By default, the scheduler runs once each day." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:88 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:90 msgid "To manually trigger a reordering rule before the scheduler runs, select :menuselection:`Inventory --> Operations --> Run Scheduler`. Then, select the green :guilabel:`Run Scheduler` button on the pop-up that appears. Be aware that this also triggers any other scheduled actions." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:94 msgid "If the :guilabel:`Buy` route is selected, then an :abbr:`RFQ (Request for Quotation)` is generated. To view and manage :abbr:`RFQs (Requests for Quotation)`, navigate to :menuselection:`Purchase --> Orders --> Requests for Quotation`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:98 msgid "If the :guilabel:`Manufacture` route is selected, then an :abbr:`MO (Manufacturing Order)` is generated. To view and manage :abbr:`MOs (Manufacturing Orders)`, navigate to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:103 msgid "Set a preferred route for reordering" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:105 msgid "Odoo allows for multiple routes to be selected under the :guilabel:`Inventory` tab on each product form. For instance, it is possible to select both :guilabel:`Buy` and :guilabel:`Manufacture`, thus enabling the functionality of both routes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:107 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:109 msgid "Odoo also enables users to set a preferred route for a product's reordering rule. This is the route that the rule defaults to if multiple are selected. To select a preferred route, begin by navigating to :menuselection:`Inventory --> Configuration --> Reordering Rules`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:111 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:113 msgid "By default, the :guilabel:`Preferred Route` column is hidden on the :guilabel:`Reordering Rules` page. Enable it by selecting the :guilabel:`⋮ (three-dot)` option button on the right side of the page and checking the :guilabel:`Preferred Route` checkbox. Doing so reveals the :guilabel:`Preferred Route` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:116 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:118 msgid "Click inside of the column on the row of a reordering rule and a drop-down menu shows all available routes for that rule. Select one to set it as the preferred route." msgstr "" @@ -3315,10 +3561,107 @@ msgstr "" msgid "Select a preferred route from the drop-down." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:124 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:126 msgid "If multiple routes are enabled for a product but no preferred route is set for its reordering rule, the product is reordered using the selected route that is listed first on the :guilabel:`Inventory` tab of the product form." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:3 +msgid "Scrap inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:5 +msgid "In some cases, a product in inventory may be damaged or found to be defective. If it is not possible to repair or return the product, Odoo *Inventory* allows users to scrap it, ensuring that usable inventory counts remain accurate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:10 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:19 +msgid "Scrap orders can be viewed by navigating to :menuselection:`Inventory --> Operations --> Scrap`. Each scrap order shows the date and time the order was created, along with the product and quantity that was scrapped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:14 +msgid "To view the total quantity of each item scrapped, navigate to :menuselection:`Inventory --> Configuration --> Locations`. Remove the :guilabel:`Internal` filter from the :guilabel:`Search...` bar to display virtual locations. Finally, select the :guilabel:`Virtual Locations/Scrap` location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:19 +msgid "By default, scrapping a product removes it from physical inventory, and places it in a virtual location titled *Virtual Locations/Scrap*. A virtual location is **not** a physical space, but rather a designation in Odoo that is used to track items that are no longer in physical inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:23 +msgid "Learn more" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:25 +msgid "For more information about virtual locations, see the documentation about the different types of :ref:`locations `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:29 +msgid "Scrap from stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:31 +msgid "To scrap a product located in inventory, begin by navigating to :menuselection:`Inventory --> Operations --> Scrap`. On the :guilabel:`Scrap Orders` page, click :guilabel:`Create` to configure a new scrap order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:35 +msgid "On the scrap order, select the product being scrapped from the :guilabel:`Product` drop-down menu, then enter the quantity in the :guilabel:`Quantity` field. The :guilabel:`Source Location` defaults to the location where the product is stored, and the :guilabel:`Scrap Location` defaults to :guilabel:`Virtual Locations/Scrap`, but either of these can be changed by selecting a different location from their respective drop-down menus." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:-1 +msgid "A new scrap order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:45 +msgid "Finally, click :guilabel:`Validate` to scrap the product. The on-hand inventory count for the scrapped product updates to subtract the scrapped quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:49 +msgid "Scrap from a receipt, transfer, or delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:51 +msgid "It is also possible to scrap products during the receipt, transfer, and delivery operations. This can be necessary if any products are found to be defective when receiving them into inventory, transferring them from one location to another, or preparing them for delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:55 +msgid "To scrap a product during the receipt, transfer, or delivery operations, begin by navigating to the :menuselection:`Inventory` app. On the :guilabel:`Overview` page, select the :guilabel:`# TO PROCESS` button on the :guilabel:`Receipts`, :guilabel:`Internal Transfers`, or :guilabel:`Delivery Orders` card, depending on the type of operation the product is being scrapped from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:61 +msgid "For the :guilabel:`Internal Transfers` card to appear on the :menuselection:`Overview` page of the :menuselection:`Inventory` app, the :guilabel:`Storage Locations` setting must be enabled. To do so, navigate to :menuselection:`Configuration --> Settings`, then enable the checkbox next to :guilabel:`Storage Locations` under the :guilabel:`Warehouse` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:66 +msgid "Alternatively, a list of all delivery orders, receipts, and transfers can be viewed by navigating to :menuselection:`Inventory --> Operations --> Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:69 +msgid "Next, open a delivery order, receipt, or transfer from the corresponding page by clicking on it. A :guilabel:`Scrap` button appears at the top of the page. Click it to open the :guilabel:`Scrap` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:-1 +msgid "The scrap pop-up in the Inventory app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:78 +msgid "The :guilabel:`Scrap` button will only appear on a receipt that has been validated. This is because Odoo only allows products to be scrapped once they have been entered into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:81 +msgid "On the :guilabel:`Scrap` pop-up window, select the product being scrapped from the :guilabel:`Product` drop-down menu. Then, enter the quantity in the :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:84 +msgid "The :guilabel:`Source Location` defaults to the location where the product is stored, and the :guilabel:`Scrap Location` defaults to :guilabel:`Virtual Locations/Scrap`, but either of these can be changed by selecting a different location from their respective drop-down menus." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:88 +msgid "Finally, click :guilabel:`Done` to scrap the product. After doing so, the :guilabel:`Scrap` pop-up window disappears and a :guilabel:`Scraps` smart button appears in the top right of the page. Click it to view all of the scrap orders created from that operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/scrap_inventory.rst:-1 +msgid "The Scraps smart button." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:3 msgid "Selecting a replenishment strategy" msgstr "" @@ -3333,7 +3676,7 @@ msgid "Terminology" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:19 -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:54 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:56 msgid "Replenishment report and reordering rules" msgstr "" @@ -3349,47 +3692,47 @@ msgstr "" msgid "Reordering rules can be created and managed in the replenishment report, or from the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:31 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:33 msgid "Make to order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:33 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:35 msgid "*Make to order (MTO)* is a procurement route that creates a draft purchase order (or manufacturing order) each time a sales order is confirmed, **regardless of the current stock level**." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:38 msgid "Unlike products replenished using reordering rules, Odoo automatically links the sales order to the |PO| or |MO| generated by the |MTO| route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:41 msgid "Another difference between reordering rules and |MTO| is, with |MTO|, Odoo generates a draft |PO| or |MO| immediately after the |SO| is confirmed. With reordering rules, Odoo generates a draft |PO| or |MO| when the product's forecasted stock falls below the set minimum quantity." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:45 msgid "In addition, Odoo automatically adds quantities to the |PO| or |MO| as the forecast changes, so long as the |PO| or |MO| is not confirmed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:48 msgid "The |MTO| route is the best replenishment strategy for products that are customized, and/or for products that have no stock kept on-hand." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:56 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:58 msgid "To access the replenishment report, go to :menuselection:`Inventory app --> Operations --> Replenishment.`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:61 msgid "By default, the replenishment report dashboard shows every product that needs to be manually reordered. If there is no specific rule for a product, Odoo assumes the :guilabel:`Min Quantity` and :guilabel:`Max Quantity` stock are both `0.00`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:66 msgid "For products that don't have a set reordering rule, Odoo calculates the forecast based on confirmed sales orders, deliveries, and receipts. For products that have a set reordering rule, Odoo calculates the forecast normally, but also takes into account the purchase/manufacturing lead time and security lead time." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:72 msgid "Before creating a new reordering rule, make sure the product has a *vendor* or a *bill of materials* configured on the product form. To check this, go to :menuselection:`Inventory app --> Products --> Products`, and select the product to open its product form. The vendor, if configured, is listed in the :guilabel:`Purchase` tab, and the bill on materials, if configured, is found in the :guilabel:`Bill of Materials` smart button at the top of the form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:78 msgid "The :guilabel:`Product Type`, located in the :guilabel:`General Information` tab on the product form, **must** be set to :guilabel:`Storable Product`. By definition, a consumable product does not have its inventory levels tracked, so Odoo cannot account for a consumable product in the replenishment report." msgstr "" @@ -3397,99 +3740,99 @@ msgstr "" msgid "Replenishment report listing all items needing to be purchased to meet current needs." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:87 msgid "To create a new reordering rule from the replenishment report, go to :menuselection:`Inventory app --> Operations --> Replenishment`, click :guilabel:`Create`, and select the desired product from the drop-down menu in the :guilabel:`Product` column. If necessary, a :guilabel:`Min Quantity` and a :guilabel:`Max Quantity` can be configured in the corresponding columns on the :guilabel:`Replenishment` report page, as well." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:93 msgid "To create a new reordering rule from the product form, go to :menuselection:`Inventory app --> Products --> Products`, and select a product to open its product form. Click the :guilabel:`Reordering Rules` smart button, click :guilabel:`Create`, and fill out the fields." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:98 msgid "Replenishment report fields" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:100 msgid "The following fields are on the :guilabel:`Replenishment` report. If any of these fields are not visible, click the :guilabel:`⋮ (additional options)` icon on the far right side of the report, then click the checkbox next to a field to make it visible." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:102 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:104 msgid ":guilabel:`Product`: the product that requires a replenishment." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:105 msgid ":guilabel:`Location`: the specific location where the product is stored." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:104 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:106 msgid ":guilabel:`Warehouse`: the warehouse where the product is stored." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:107 msgid ":guilabel:`On Hand`: the amount of product currently available." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:108 msgid ":guilabel:`Forecast`: the amount of product available after all current orders (sales, manufacturing, purchase, etc.) are taken into account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:110 msgid ":guilabel:`Preferred Route`: how the product is procured, either :guilabel:`Buy`, :guilabel:`Manufactured`, :guilabel:`Dropship`, etc." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:110 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:112 msgid ":guilabel:`Vendor`: the company from which the product is acquired." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:111 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:113 msgid ":guilabel:`Bill of Materials`: the bill of materials for the product (if one is configured)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:112 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:114 msgid ":guilabel:`Trigger`: how the replenishment is created, either :guilabel:`Auto` (automatically, once the :guilabel:`On Hand` quantity goes below the :guilabel:`Min Quantity`) or :guilabel:`Manual` (only when the replenishment is requested)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:117 msgid ":guilabel:`Procurement Group`: the reference number for how the product is being acquired, such as a sales order, purchase order, or manufacturing order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:119 msgid ":guilabel:`Min Quantity`: the minimum amount of product that should be available. When inventory levels goes below this number, the replenishment is triggered." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:119 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:121 msgid ":guilabel:`Max Quantity`: the amount of product that should be available after replenishing the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:121 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:123 msgid ":guilabel:`Multiple Quantity`: if the product should be ordered in specific quantities, enter the number that should be ordered. For example, if the :guilabel:`Multiple Quantity` is set to `5`, and only 3 are needed, 5 products are replenished." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:124 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:126 msgid ":guilabel:`To Order`: the amount of product that is currently needed, and will be ordered, if the :guilabel:`Order Once` or :guilabel:`Automate Orders` button is clicked." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:126 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:128 msgid ":guilabel:`UoM`: the unit of measure used to acquire the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:127 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:129 msgid ":guilabel:`Company`: the company for which the product is acquired." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:129 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:131 msgid "By default, the quantity in the :guilabel:`To Order` field is the quantity required to reach the set :guilabel:`Max Quantity`. However, the :guilabel:`To Order` quantity can be adjusted by clicking on the field and, changing the value, and clicking :guilabel:`Save`. To replenish a product manually, click :guilabel:`Order Once`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:134 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:136 msgid "To automate a replenishment from the :guilabel:`Replenishment` page, click :guilabel:`Automate Orders` on the right-side of the line, represented by a :guilabel:`🔄 (circular arrow)` icon." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:137 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:139 msgid "When this button is clicked, Odoo will automatically generate a draft |PO|/|MO| every time the forecasted stock level falls below the set :guilabel:`Min Quantity` of the reordering rule." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:140 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:142 msgid "On the :guilabel:`Replenishment` page, a reordering rule or manual replenishment can be temporarily deactivated for a given period, by clicking the :guilabel:`🔕 (snooze)` icon on the far-right of the line." msgstr "" @@ -3497,7 +3840,7 @@ msgstr "" msgid "Snooze options to turn off notifications for reordering for a period of time." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:148 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:150 msgid "A |PO| or |MO| created by a manual replenishment has a :guilabel:`Replenishment Report` as the source document. A |PO| or |MO| created by an automated reordering rule has the |SO| reference number(s) that triggered the rule as the source document." msgstr "" @@ -3505,63 +3848,63 @@ msgstr "" msgid "Quote request list shows which quotes are directly from the replenishment report." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:157 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:159 msgid "Make to order (MTO) route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:159 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:161 msgid "Since the |MTO| route is recommended for customized products, the route is hidden by default." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:168 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:170 msgid "To activate the |MTO| route in Odoo:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:162 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:164 msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:163 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:165 msgid "Activate the :guilabel:`Multi-Step Routes` setting, located under the :guilabel:`Warehouse` section, and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:165 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:167 msgid "Then, go to :menuselection:`Inventory app --> Configuration --> Routes`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:166 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:168 msgid "Click on :menuselection:`Filters --> Archived` to show archived routes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:167 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:169 msgid "Select the checkbox next to :guilabel:`Replenish on Order (MTO)`, and click on :menuselection:`Action --> Unarchive`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:171 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:173 msgid "Activating the :guilabel:`Multi-Step Routes` setting also activates :guilabel:`Storage Locations`. If these features aren't applicable to the warehouse, disable these settings after unarchiving the |MTO| route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:175 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:177 msgid "To set a product's procurement route to |MTO|, go to :menuselection:`Inventory app --> Products --> Products`, click on the desired product to open its product form, and click :guilabel:`Edit`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:178 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:180 msgid "Then, click the :guilabel:`Inventory` tab, and in the :guilabel:`Routes` section of options, select :guilabel:`Replenish on Order (MTO)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:181 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:183 msgid "For products purchased directly from a vendor, make sure the :guilabel:`Buy` route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` route. Also, make sure a vendor is configured in the :guilabel:`Purchase` tab of the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:185 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:187 msgid "For products manufactured in-house, make sure the :guilabel:`Manufacture` route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` route. Also, make sure a bill of materials is configured for the product, which is accessible via the :guilabel:`Bill of Materials` smart button on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:190 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:192 msgid "Finally, when all configurations are complete, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:193 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:195 msgid "The |MTO| route cannot be selected alone. |MTO| **only** works if the :guilabel:`Manufacture` or :guilabel:`Buy` route is also selected." msgstr "" @@ -3954,11 +4297,11 @@ msgstr "" msgid "Integrating additional costs to products (landed costs)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:7 msgid "The landed cost feature in Odoo allows the user to include additional costs (shipment, insurance, customs duties, etc.) into the cost of the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:13 msgid "First, go to :menuselection:`Inventory --> Configuration --> Settings --> Valuation` and activate the :guilabel:`Landed Costs` feature. Odoo also gives the option to set a :guilabel:`Default Journal` in which the landed costs accounting entries will be recorded." msgstr "" @@ -3966,15 +4309,15 @@ msgstr "" msgid "Activate the landed cost feature in Inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:22 msgid "Add costs to products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:23 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:25 msgid "Receive the vendor bill" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:25 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:27 msgid "After a vendor fulfills a purchase order and sends a bill, click :guilabel:`Create Bill` on the purchase order to create a vendor bill in Odoo. If the vendor bill includes landed costs, such as custom duties, tick the box in the :guilabel:`Landed Costs` column on the vendor bill invoice line." msgstr "" @@ -3982,15 +4325,15 @@ msgstr "" msgid "Enable Landed Costs option on vendor bill line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:33 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:35 msgid "For charges that are always landed costs, create a landed cost product in Odoo. That way, the landed cost product can be quickly added to the vendor bill as an invoice line instead of manually entering the landed cost information every time a vendor bill comes in." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:37 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:39 msgid "First, create a new product in :menuselection:`Inventory --> Products --> Products --> Create`. Next, name the landed cost product. Then, set the :guilabel:`Product Type` to :guilabel:`Service`. A landed cost product must always be a service product type. After that, go to the :guilabel:`Purchase` tab and check the box next to :guilabel:`Is a Landed Cost`. Finally, click :guilabel:`Save` to finish creating the landed cost product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:45 msgid "If this product is always a landed cost, you can also define it on the product and avoid having to tick the box on each vendor bill." msgstr "" @@ -3998,7 +4341,7 @@ msgstr "" msgid "Option to define a product as a landed cost." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:52 msgid "Once the landed cost is added to the vendor bill (either by checking the :guilabel:`Landed Cost` option on the invoice line or adding a landed cost product to the bill), click the :guilabel:`Create Landed Costs` button at the top of the bill. Odoo automatically creates a landed cost record with the set landed cost pre-filled in the :guilabel:`Additional Costs` product lines. From here, decide which picking the additional costs apply to by clicking :guilabel:`Edit` and selecting the picking reference number from the :guilabel:`Transfers` drop-down menu. Finally, click :guilabel:`Save`." msgstr "" @@ -4006,15 +4349,15 @@ msgstr "" msgid "Use a warehouse transfer to cover a landed cost in the accounting journal." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:64 msgid "After setting the picking, click :guilabel:`Compute` on the landed cost record. Then, go to the :guilabel:`Valuation Adjustments` tab to see the impact of the landed costs. Finally, click :guilabel:`Validate` to post the landed cost entry to the accounting journal." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:66 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:68 msgid "The user can access the journal entry that has been created by the landed cost by clicking on the :guilabel:`Journal Entry`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:72 msgid "The product that the landed cost is applied to must have a product category set to a :abbr:`FIFO (First In, First Out)` or an :abbr:`AVCO (Average Costing)` method." msgstr "" @@ -4022,7 +4365,7 @@ msgstr "" msgid "Landed cost journal entry" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:78 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:80 msgid "Landed cost records can also be directly created in :menuselection:`Inventory --> Operations --> Landed Costs`, it is not necessary to create a landed cost record from the vendor bill." msgstr "" @@ -4050,107 +4393,107 @@ msgstr "" msgid "Automated inventory valuation is a method recommended for expert accountants, given the extra steps involved in journal entry configuration. Even after the initial setup, the method will need to be periodically checked to ensure accuracy, and adjustments may be needed on an ongoing basis depending on the needs and priorities of the business." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:33 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:35 msgid "Types of accounting" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:37 msgid "Accounting entries will depend on the accounting mode: *Continental* or *Anglo-Saxon*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:40 msgid "Verify the accounting mode by activating the :ref:`developer-mode` and navigating to :menuselection:`Accounting --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:41 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:43 msgid "In *Anglo-Saxon* accounting, the costs of goods sold (COGS) are reported when products are sold or delivered. This means that the cost of a good is only recorded as an expense when a customer is invoiced for a product. *Interim Stock Accounts* are used for the input and output accounts, and are both *Asset Accounts* in the balance sheet." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:48 msgid "In *Continental* accounting, the cost of a good is reported as soon as a product is received into stock. Additionally, a single *Expense* account is used for both input and output accounts in the balance sheet." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:55 msgid "Costing methods" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:57 msgid "Below are the three costing methods that can be used in Odoo for inventory valuation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:55 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:59 msgid "**Standard Price**: is the default costing method in Odoo. The cost of the product is manually defined on the product form, and this cost is used to compute the valuation. Even if the purchase price on a purchase order differs, the valuation will still use the cost defined on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:63 msgid "**Average Cost (AVCO)**: calculates the valuation of a product based on the average cost of that product, divided by the total number of available stock on-hand. With this costing method, inventory valuation is *dynamic*, and constantly adjusts based on the purchase price of products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:66 msgid "**First In First Out (FIFO)**: tracks the costs of incoming and outgoing items in real-time and uses the real price of the products to change the valuation. The oldest purchase price is used as the cost for the next good sold until an entire lot of that product is sold. When the next inventory lot moves up in the queue, an updated product cost is used based on the valuation of that specific lot. This method is arguably the most accurate inventory valuation method for a variety of reasons, however, it's highly sensitive to input data and human error." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:74 msgid "Changing the costing method greatly impacts inventory valuation. It's highly recommended to consult an accountant first before making any adjustments here." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:74 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:78 msgid "Configure automated inventory valuation in Odoo" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:80 msgid "Make changes to inventory valuation options by navigating to :menuselection:`Inventory --> Configuration --> Product Categories`, and choose the category/categories where the automated valuation method should apply." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:85 msgid "It is possible to use different valuation settings for different product categories." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:83 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:87 msgid "Under the :guilabel:`Inventory Valuation` heading are two labels: :guilabel:`Costing Method` and :guilabel:`Inventory Valuation`. Pick the desired :guilabel:`Costing Method` using the drop-down menu (e.g. :guilabel:`Standard`, :guilabel:`Average Cost (AVCO)`, or :guilabel:`First In First Out (FIFO)`) and switch the :guilabel:`Inventory Valuation` to :guilabel:`Automated`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:89 -msgid ":doc:`Using the inventory valuation `" +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:93 +msgid ":ref:`Using the inventory valuation`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:96 msgid "When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, changing the numerical value in the :guilabel:`Cost` field for products in the respective product category creates a new record in the *Inventory Valuation* report to adjust the value of the product. The :guilabel:`Cost` amount will then automatically update based on the average purchase price both of inventory on hand and the costs accumulated from validated purchase orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:102 msgid "When the :guilabel:`Costing Method` is changed, products already in stock that were using the :guilabel:`Standard` costing method **do not** change value; rather, the existing units keep their value, and any product moves from then on affect the average cost, and the cost of the product will change. If the value in the :guilabel:`Cost` field on a product form is changed manually, Odoo will generate a corresponding record in the *Inventory Valuation* report." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:108 msgid "On the same screen, the :guilabel:`Account Stock Properties` fields will appear, as they are now required fields given the change to automated inventory valuation. These accounts are defined as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:109 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:112 msgid ":guilabel:`Stock Valuation Account`: when automated inventory valuation is enabled on a product, this account will hold the current value of the products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:111 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:114 msgid ":guilabel:`Stock Input Account`: counterpart journal items for all incoming stock moves will be posted in this account, unless there is a specific valuation account set on the source location. This is the default value for all products in a given category, and can also be set directly on each product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:118 msgid ":guilabel:`Stock Output Account`: counterpart journal items for all outgoing stock moves will be posted in this account, unless there is a specific valuation account set on the destination location. This is the default value for all products in a given category, and can also be set directly on each product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:121 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:124 msgid "Access reporting data generated by inventory valuation" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:123 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:126 msgid "To start, go to :menuselection:`Accounting --> Reporting --> Balance Sheet`. At the top of the dashboard, change the :guilabel:`As of` field value to :guilabel:`Today`, and adjust the filtering :guilabel:`Options` to :guilabel:`Unfold All` in order to see all of the latest data displayed, all at once." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:128 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:131 msgid "Under the parent :guilabel:`Current Assets` line item, look for the nested :guilabel:`Stock Valuation Account` line item, where the total valuation of all of the inventory on hand is displayed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:132 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:135 msgid "Access more specific information with the :guilabel:`Stock Valuation Account` drop-down menu, by selecting either the :guilabel:`General Ledger` to see an itemized view of all of the journal entries, or by selecting :guilabel:`Journal Items` to review all of the individualized journal entries that were submitted to the account. As well, annotations to the :guilabel:`Balance Sheet` can be added by choosing :guilabel:`Annotate`, filling in the text box, and clicking :guilabel:`Save`." msgstr "" @@ -4162,43 +4505,43 @@ msgstr "" msgid "Using inventory valuation" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:7 msgid "*Inventory valuation* is a quintessential accounting procedure that calculates the value of on-hand stock. Once determined, the inventory valuation amount is then incorporated into a company's overall value." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:11 msgid "In Odoo, this process can be conducted manually— by warehouse employees physically counting the products— or automatically through the database." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:13 -msgid ":ref:`Inventory valuation configuration `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:16 -msgid "Understand the basics of inventory valuation" +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:15 +msgid ":ref:`Inventory valuation configuration`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:18 +msgid "Understand the basics of inventory valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:20 msgid "In order to understand how moving products in and out of stock affects the company's overall value, consider the following product and stock moves scenario below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:24 msgid "Receive a product" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:24 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:26 msgid "For example, consider an physical product, a simple *table*, which is categorized as `Office Furniture` in the product form's :guilabel:`Product Category` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:29 msgid "Navigate to the the product category itself by going to :menuselection:`Inventory app --> Configuration --> Product Categories`, and on the form, set the :guilabel:`Costing Method` as `First In First Out (FIFO)` and the :guilabel:`Inventory Valuation` field as `Automated`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:34 msgid "Alternatively access the :guilabel:`Product Categories` dashboard by clicking on the :guilabel:`internal link` arrow on the individual product's form, by hovering over the :guilabel:`Product Category` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:38 msgid "Next, assume 10 tables are purchased at a price of $10.00, each. The :abbr:`PO (Purchase Order)` for those tables will show the subtotal of the purchase as $100, plus any additional costs or taxes." msgstr "" @@ -4206,7 +4549,7 @@ msgstr "" msgid "Purchase order with 10 tables products valued at $10 each." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:45 msgid "After selecting :guilabel:`Validate` on the :abbr:`PO (Purchase Order)`, use the :guilabel:`Valuation` smart button to view how the value of inventory was impacted." msgstr "" @@ -4214,15 +4557,15 @@ msgstr "" msgid "Valuation smart button on a receipt." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:53 msgid ":ref:`Developer mode ` must be turned on to see the *Valuation* smart button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:54 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:56 msgid "The :doc:`consignment ` feature allows ownership to items in stock. Thus, products owned by other companies are not accounted for in the host company's inventory valuation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:58 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:60 msgid "The :guilabel:`Stock Valuation` dashboard then displays valuation of all products in the shipment, along with their quantities and valuation. In the example of 10 tables being purchased, the :guilabel:`Total Value` column of the dashboard would display a calculated valuation of $100." msgstr "" @@ -4230,7 +4573,7 @@ msgstr "" msgid "Stock valuation page depicting the products within a shipment." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:66 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:68 msgid "In Odoo, automatic inventory valuation records are also recorded in the *Accounting* app. To access these accounting entries, navigate to :menuselection:`Accounting --> Journal Entries`, and look for inventory valuation entries with the `STJ` prefix in the :guilabel:`Journal` and :guilabel:`Number` columns, respectively." msgstr "" @@ -4238,11 +4581,11 @@ msgstr "" msgid "Accounting entry for the inventory valuation of 10 tables." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:78 msgid "Deliver a product" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:78 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:80 msgid "In the same logic, when a table is shipped to a customer and leaves the warehouse, the stock valuation decreases. The :guilabel:`Valuation` smart button on the :abbr:`DO (Delivery Order)`, likewise, displays the stock valuation record as it does on a :abbr:`PO (Purchase Order)`" msgstr "" @@ -4250,11 +4593,11 @@ msgstr "" msgid "Decreased stock valuation after a product is shipped." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:87 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:89 msgid "The inventory valuation report" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:91 msgid "To view the current value of all products in the warehouse, go to :menuselection:`Inventory app --> Reporting --> Inventory Valuation`. The records in the table are organized by product, and selecting a product's drop-down menu displays detailed records with the :guilabel:`Date`, :guilabel:`Quantity`, and :guilabel:`Total Value` of the inventory." msgstr "" @@ -4262,19 +4605,19 @@ msgstr "" msgid "Inventory valuation report showing multiple products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:101 msgid "The :guilabel:`Inventory At Date` button, located in the top-left corner of the :guilabel:`Stock Valuation` dashboard, shows the inventory valuation of products available during a prior specified date." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:104 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:106 msgid "Update product unit price" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:108 msgid "For any company: lead times, supply chain failures, and other risk factors can contribute to invisible costs. Although Odoo attempts to accurately represent the stock value, *manual valuation* serves as an additional tool to update the unit price of products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:111 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:113 msgid "Manual valuation is intended for products that can be purchased and received for a cost greater than 0, or have product categories set with :guilabel:`Costing Method` set as either `Average Cost (AVCO)` or `First In First Out (FIFO)`." msgstr "" @@ -4282,11 +4625,11 @@ msgstr "" msgid "Add manual valuation of stock value to a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:119 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:121 msgid "Create manual valuation entries on the :guilabel:`Stock Valuation` dashboard by first navigating to :menuselection:`Inventory app --> Reporting --> Inventory Valuation`, and then click the little gray drop-down icon to the left of a product's name, to then reveal stock valuation line items below as well as a teal :guilabel:`+ (plus)` button on the right." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:124 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:126 msgid "Click the teal :guilabel:`+ (plus)` button to open up the :guilabel:`Product Revaluation` form, where updates to the calculation of inventory valuation can be made, by increasing or decreasing the unit price of each product." msgstr "" @@ -5201,6 +5544,90 @@ msgstr "" msgid "A receipt for stock received to one warehouse from another." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:3 +msgid "Locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:5 +msgid "A *location* is a specific space within a warehouse. This can be a shelf, room, aisle, etc. There are three types of locations in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:8 +msgid "*Physical locations* are spaces within a warehouse owned by the user's company. These can be a an area where items are stored like an aisle or shelf, or an area where operations take place, like loading and unloading bays." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:11 +msgid "*Partner locations* are the same as physical locations except that they exist within the warehouse of a customer or vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:13 +msgid "*Virtual locations* are locations that do not exist physically, but where items that are not in inventory can be placed. These can be items that have not yet entered inventory, like products that are on the way to a warehouse, or items that are no longer in inventory due to loss or other factors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:19 +msgid "In order to use locations, the :guilabel:`Storage Locations` setting must be enabled. To do so, navigate to :menuselection:`Inventory --> Configuration --> Settings`, scroll down to the :guilabel:`Warehouse` heading, and enable the :guilabel:`Storage Locations` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:24 +msgid "Create a new location inside a warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:26 +msgid "Starting from the :menuselection:`Inventory` app, select :menuselection:`Configuration --> Locations --> Create`. The new location form can then be configured as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:29 +msgid ":guilabel:`Location Name`: the name that will be used to reference the location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:30 +msgid ":guilabel:`Parent Location`: the location or warehouse that the new location exists within" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:31 +msgid ":guilabel:`Location Type`: choose the category that the location belongs to" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:32 +msgid ":guilabel:`Company`: the company that owns the warehouse that the location is inside of" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:33 +msgid ":guilabel:`Is a Scrap Location?`: check this box to allow for scrapped/damaged goods to be stored in this location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:35 +msgid ":guilabel:`Is a Return Location?`: check this box to allow products to be returned to this location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:37 +msgid ":guilabel:`Barcode`: the barcode number assigned to the location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:38 +msgid ":guilabel:`Removal Strategy`: the :ref:`strategy ` for how items should be taken from inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:-1 +msgid "The form for creating a new location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:46 +msgid "Create location hierarchies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:48 +msgid "The *Parent Location* setting on the new location form allows for a location to exist within a warehouse or another location. Every location can serve as a parent location, and every parent location can have multiple locations within it, allowing for the creation of a virtually infinite hierarchical structure." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:54 +msgid "Location hierarchy could be organized so that a shelf is located within an aisle, which is located within a room, which is located within the overall warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst:57 +msgid "To create the location hierarchy in the example above, set the warehouse as the parent of the room, the room as the parent of the aisle, and the aisle as the parent of the shelf. This can be adapted to a hierarchy of any magnitude." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouse_replenishment_transfer.rst:3 msgid "Transfer products between warehouses using replenishment" msgstr "" @@ -5369,31 +5796,31 @@ msgstr "" msgid "In Odoo, a **Warehouse** is the actual building/place in which a company's items are stocked. Multiple warehouses can be set up in Odoo and the user can create moves between warehouses." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:19 msgid "A **Location** is a specific space within the warehouse. It can be a sublocation of the warehouse (a shelf, a floor, an aisle, and so on). Therefore, a location is part of one warehouse only and it is not possible to link one location to multiple warehouses. In Odoo, as many locations can be configured as needed under one warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:24 msgid "There are three types of locations:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:24 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:26 msgid "The **Physical Locations** are internal locations that are part of the warehouses that the company owns. They can be the loading and unloading areas of the warehouse, a shelf, a department, etc." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:28 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:30 msgid "The **Partner Locations** are spaces within a customer and/or vendor's warehouse. They work the same way as physical locations, with the only difference being that they are not owned by the user's company." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:34 msgid "The **Virtual Locations** are places that do not exist, but in which products can be placed when they are not physically in an inventory yet (or anymore). They come in handy when recording lost products (**Inventory Loss**), or accounting for products that are on their way to the warehouse (**Procurements**)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:37 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:39 msgid "In Odoo, locations are structured hierarchically. Locations can be structured as a tree, dependent on a parent-child relationship. This gives more detailed levels of analysis of the stock operations and the organization of the warehouses." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:44 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:46 msgid "To activate locations, go to :menuselection:`Configuration --> Settings` and enable :guilabel:`Storage Locations`. Then, click :guilabel:`Save`." msgstr "" @@ -5401,20 +5828,20 @@ msgstr "" msgid "Enable the storage location feature in Odoo Inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:54 msgid "To manage several routes within the warehouses, also enable :guilabel:`Multi-Step Routes` and check :doc:`../../routes/concepts/use_routes`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:56 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:58 #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/stock_warehouses.rst:41 msgid "Create a new warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:58 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:60 msgid "To create a warehouse, go to :menuselection:`Configuration --> Warehouse Management --> Warehouses` and click on :guilabel:`Create`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:61 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:63 msgid "Then, fill out a :guilabel:`Warehouse Name` and a :guilabel:`Short Name`. The short name is five characters maximum." msgstr "" @@ -5422,11 +5849,11 @@ msgstr "" msgid "Short name field of a warehouse on Odoo Inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:71 msgid "The :guilabel:`Short Name` appears on transfer orders and other warehouse documents. Odoo recommends using an understandable one like \"WH/[first letters of location]\"." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:72 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:74 msgid "Now, go back to the :guilabel:`Inventory` dashboard. There, new operations related to the newly created warehouse have been automatically generated." msgstr "" @@ -5434,19 +5861,19 @@ msgstr "" msgid "Inventory app dashboard displaying new transfer types for the recently created warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:80 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:82 msgid "Adding a second warehouse will automatically activate the :guilabel:`Locations` setting." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:83 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:85 msgid "Create a new location" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:87 msgid "To create a location, go to :menuselection:`Configuration --> Warehouse Management --> Locations` and click on :guilabel:`Create`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:88 +#: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:90 msgid "Then, fill out a :guilabel:`Location Name` and a :guilabel:`Parent Location` and click :guilabel:`Save`." msgstr "" @@ -6280,302 +6707,345 @@ msgid "Storage Categories used in a variety of putaway rules." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:3 -msgid "What is a Removal Strategy (FIFO, LIFO, FEFO, Closest location)?" +msgid "Removal strategies (FIFO, LIFO, FEFO)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:5 -msgid "Usually, *Removal Strategies* are defined in picking operations to select the best products, optimize the distance for the worker, for quality control purposes, or to first move products with the closest expiration date." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:7 +msgid "For companies with warehouses, **removal strategies** determine which products are taken from the warehouse, and when. Removal strategies are typically defined for specific picking operations. This helps companies to select the best products, optimize the distance workers need to travel when picking items for orders, and account for quality control, such as moving products with expiration dates." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:9 -msgid "When a product movement needs to be done, Odoo finds available products that can be assigned to the transfer. The way Odoo assigns these products depends on the *Removal Strategy* defined in the *Product Category* or on the *Location*." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:13 +msgid "Usually, *Removal Strategies* are defined in picking operations to select the best products to optimize the distance for the worker, for quality control purposes, or to first move the products with the closest expiration date." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:14 -msgid "What happens inside the warehouse?" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:17 +msgid "When a product needs to be moved, Odoo finds available products that can be assigned to the transfer. The way Odoo assigns these products depends on the :guilabel:`Removal Strategy` defined in either the :guilabel:`Product Category` or the :guilabel:`Location` dashboards." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:16 -msgid "Imagine a generic warehouse plan, with receiving docks and areas, storage locations, picking and packing areas, and shipping docks. All products go through all these locations, but some rules, such as removal strategies, can have an effect on which products are taken for the pickings." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:21 +msgid "To change the :guilabel:`Removal Strategy`, go to :menuselection:`Inventory app --> Configuration --> Locations` or :menuselection:`Product Categories`. Click on a :guilabel:`Location` or :guilabel:`Product Category`, and then click :guilabel:`Edit`. Change the product category :guilabel:`Force Removal Strategy` or the location :guilabel:`Removal Strategy` by clicking on the drop-down menu and selecting the desired removal strategy. After selecting the new removal strategy, click :guilabel:`Save`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "Empty stock waiting for deliveries at the docks." +msgid "Change the Force Removal Strategy for either the Product Categories or Locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:24 -msgid "Here, vendor trucks unload pallets of goods at the docks. Then, operators scan the products in the receiving area with the reception date and, if the product has an expiration date, the expiration date. After that, products are stored in their respective locations." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:33 +msgid "What happens inside the warehouse?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:35 +msgid "Most warehouses share the same important areas: receiving docks and sorting areas, storage locations, picking and packing areas, and shipping/loading docks. While all products entering or leaving the warehouse might go through each of these locations at some point, removal strategies can have an effect on which products are taken, from where, and when." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:40 +msgid "In this example below, vendor trucks unload pallets of goods at the receiving docks. Then, operators scan the products in the receiving area, with the reception date and expiration date. After that, products are stored in their respective storage locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:45 +msgid "Not all products have expiration dates, but in this example, expiration dates apply." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "Products entering stock via the receiving area." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:32 -msgid "Next, several orders for the same product are made, but in this example, the goods weren't received on the same day and they don't have the same expiration date. In that situation, logically, sending those with the closest date first is preferred. Depending on the chosen removal strategy, Odoo generates a transfer with the products that fit the settings the best." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:51 +msgid "In Odoo, receive products by navigating to the :menuselection:`Inventory` application, and in the kanban view, click on either the :guilabel:`Receipts` heading or :guilabel:`# TO PROCESS` button. On the :guilabel:`Receipts` dashboard, find and click on the individual receipt which will open the warehouse intake form. Click :guilabel:`Edit`, and then enter the received quantity in the :guilabel:`Done` column. To finish, :guilabel:`Validate` to receive the products and register them in the Odoo database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:59 +msgid "Receiving products can also be done within the Odoo *Barcode* application. If using the *Barcode* app, scan the product(s), update the quantity, and finally, click :guilabel:`Validate`. After products are received in Odoo, the products can then be moved to their respective storage locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:64 +msgid "Continuing with the same example, below, imagine several sales orders are made for the products received earlier, that use expiration dates. In this example, the products weren't received on the same day, and they don't have the same expiration date. In this situation, logically, sending products with the closest expiration date is preferred, instead of products received first or last. Using the chosen removal strategy configured for those products (in this example, :ref:`FEFO `), Odoo generates a transfer for the products with the soonest expiration date to the picking area, then the packing area, and finally, to the shipping docks for delivery to the customer." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid ":alt: Products being packed at the packing area for delivery, taking expiration dates into\n" +msgid "Products being packed at the packing area for delivery, taking the expiration dates into\n" "account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:43 -msgid "To pick for delivery, the product's lot/serial number can be found on the transfer form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:46 -msgid "How does it work?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:49 -msgid "First In, First Out (FIFO)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:51 -msgid "When using a *First In, First Out* (FIFO) strategy, a demand for some products triggers a removal rule, which requests a transfer for the lot/serial number that has entered the stock first." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:54 -msgid "For example, imagine there are three lots of nails in the warehouse. Those three have the following lot numbers: :guilabel:`00001`, :guilabel:`00002`, :guilabel:`00003`, each with five boxes of nails in it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:58 -msgid ":guilabel:`00001` entered the stock on the 23rd of May, :guilabel:`00002` on the 25th of May, and :guilabel:`00003` on the 1st of June. A customer orders six boxes on the 11th of June. With the :abbr:`FIFO (First In, First Out)` removal strategy selected, a transfer is requested for the five boxes of :guilabel:`00001` and one of the boxes in :guilabel:`00002`, because :guilabel:`00001` entered the stock before the others. The box from :guilabel:`00002` is taken next because it has the oldest reception date after :guilabel:`00001`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:65 -msgid "So, for every order of a product with the :abbr:`FIFO (First In, First Out)` strategy selected, Odoo requests a transfer for the products that have been in the stock for the longest period." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:69 -msgid "Last In, First Out (LIFO)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:71 -msgid "Similar to :abbr:`FIFO (First In, First Out)`, the *Last In, First Out* (LIFO) strategy moves products based on the date they entered the stock. Here, a demand for some products triggers a removal rule that requests a transfer for the lot/serial number that has entered the stock most recently." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:76 -msgid "For example, imagine there are three lots of screws in the warehouse. Those three have the following numbers: :guilabel:`10001`, :guilabel:`10002`, and :guilabel:`10003`, each with 10 boxes of screws in it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:80 -msgid ":guilabel:`10001` entered the stock on the 1st of June, :guilabel:`10002` on the 3rd of June, and :guilabel:`10003` on the 6th of June. A customer orders seven boxes on the 8th of June. With the :abbr:`LIFO (Last In, First Out)` removal strategy selected, a transfer is requested for seven boxes of :guilabel:`10003` because that lot is the last one to have entered the stock." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:79 +msgid "To pick for delivery, the product's lot/serial number can be found on the transfer form. To learn more about picking and shipping, refer to either the :ref:`Two-step delivery ` or :ref:`Three-step delivery ` documentation." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:85 -msgid "Basically, for every order of a product with the :abbr:`LIFO (Last In, First Out)` strategy used, a transfer for the last lot to have entered the stock is requested." +msgid "How each removal strategy works" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:89 -msgid "The :abbr:`LIFO (Last In, First Out)` strategy is banned in many countries and can lead to only having old or obsolete products in the stock." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:87 +msgid "Removal strategies determine which products are taken from the warehouse when orders are confirmed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:93 -msgid "First Expire, First Out (FEFO)" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:90 +msgid "First In, First Out (FIFO)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:95 -msgid "The *First Expired, First Out* (FEFO) strategy is a bit different from the other two removal strategies. For :abbr:`FEFO (First Expired, First Out)`, the expiration date is important, not the date the product entered the stock." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:92 +msgid "When using a :guilabel:`First In, First Out (FIFO)` strategy, demand for a product triggers a removal rule, which requests a transfer for the lot/serial number that entered the stock first (and therefore, has been in stock for the longest time)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:96 +msgid "For example, imagine there are three lots of nails in the warehouse, and have the corresponding lot numbers: `00001`, `00002`, `00003`. Each lot has five boxes of nails in it." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:99 -msgid "For example, imagine there are three lots of six-egg boxes (in this specific case, don't forget to use :doc:`units of measure <../../management/products/uom>`). Those three lots have the following numbers: :guilabel:`20001`, :guilabel:`20002`, and :guilabel:`20003`, each with five boxes in it." +msgid "Lot `00001` entered the stock on May 23, lot `00002` on May 25, and lot `00003` on June 1. A customer orders six boxes on June 11." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:103 -msgid ":guilabel:`20001` entered the stock on the 1st of July and expires on the 15th of July, :guilabel:`20002` entered on the 2nd and expires on the 14th of July, and :guilabel:`20003` entered on the 4th and expires on the 21st of July. A customer orders six boxes on the 5th of July. With the :abbr:`FEFO (First Expired, First Out)` strategy selected, a transfer is requested for the five boxes of :guilabel:`20002` and one from :guilabel:`20001`. The transfer for all the boxes in lot :guilabel:`20002` is because they have the closest expiration date. The transfer also requests one box from :guilabel:`20001` because has the next closest expiration date after lot :guilabel:`20002`." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:102 +msgid "Using the :abbr:`FIFO (First In, First Out)` removal strategy, a transfer request will pick the five boxes from lot `00001` first, and then from the boxes in lot `00002`, since lot `00001` entered the stock first. The box from lot `00002` is taken next because it has the oldest receipt date after lot `00001`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 +msgid "The detailed operations for the transfer shows the nail lots to be removed." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:112 -msgid "Basically, for every sales order of a product with the :abbr:`FEFO (First Expired, First Out)` strategy, a transfer is requested for the product that has the nearest expiration date from the order date." +msgid "Last In, First Out (LIFO)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:117 -msgid "Closest Location" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:114 +msgid "Similar to the :abbr:`FIFO (First In, First Out)` method, the :guilabel:`Last In, First Out (LIFO)` removal strategy moves products based on the date they entered a warehouse's stock. Instead of removing the oldest stock on-hand, however, it targets the **newest** stock on-hand for removal." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:119 -msgid "The *Closest Location* strategy is completely different from the other removal strategies. It is not related to the date of entry in the warehouse, but rather the location of the product. It is commonly used for products that do not deteriorate with time." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:118 +msgid "Every time an order for products with the :abbr:`LIFO (Last In, First Out)` method is placed, a transfer is created for the lot/serial number that has most recently entered the stock (the **last** lot/serial number that entered the warehouse's inventory)." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:123 -msgid "The aim is to avoid making the warehouse worker take a long journey to the bottom of the stock when the product is also located at a near location. This method is only available if the :guilabel:`Storage Locations` setting is on. The closest location is actually the one that comes first in the alphabetic order." +msgid "In many countries, the :abbr:`LIFO (Last In, First Out)` removal strategy in banned, since it can potentially result in old, expired, or obsolete products being delivered to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:126 +msgid "For example, imagine there are three lots of boxes of screws in the warehouse, and have the corresponding lot numbers: `10001`, `10002`, and `10003`, each with 10 boxes of screws per lot." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:129 -msgid "Use removal strategies" +msgid "Lot `10001` entered the stock on June 1, lot `10002` on June 3, and lot `10003` on June 6. A customer orders seven boxes on June 8." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:131 -msgid "To differentiate some units from others, the units need to be tracked, either by *lot* or by *serial number*. To do so, go to :menuselection:`Inventory --> Configuration --> Settings`. Then, activate the :guilabel:`Storage Location`, :guilabel:`Multi-Step Routes`, and :guilabel:`Lots & Serial Numbers` settings." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:132 +msgid "Using the :abbr:`LIFO (Last In, First Out)` removal strategy, a transfer is requested for seven boxes of screws from lot `10003` because that lot is the last one to have entered the stock." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "Features to enable in order to properly use removal strategies." +msgid "The detailed operations shows which lots are being selected for the picking." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:141 -msgid "To work with the :abbr:`FEFO (First Expired, First Out)` strategy, also activate the :guilabel:`Expiration Dates` feature." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:140 +msgid "First Expired, First Out (FEFO)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:144 -msgid "Next, go to :menuselection:`Inventory --> Configuration --> Product Categories` to define the removal strategy on a product category." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:142 +msgid "While the :abbr:`FIFO (First In, First Out)` and :abbr:`LIFO (Last In, First Out)` methods target products for removal based on date of entry into the warehouse, the :guilabel:`First Expired, First Out (FEFO)` method targets products for removal based on their assigned expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:146 +msgid "Using the :abbr:`FEFO (First Expired, First Out)` removal strategy, every sales order that includes products with this removal strategy assigned ensures that transfers are requested for products with the expiration date soonest to the order date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:150 +msgid "As an example, imagine there are three lots of six-egg boxes. Those three lots have the following lot numbers: `20001`, `20002`, and `20003`, each with five boxes in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:153 +msgid "Lot `20001` entered the stock on July 1 and expires on July 15, lot `20002` entered on July 2 and expires on July 14, and lot `20003` entered on July 3 and expires on July 21. A customer orders six boxes on July 5." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:157 +msgid "Using the :abbr:`FEFO (First Expired, First Out)` method, a transfer is requested for the five boxes from lot `20002` and one from lot `20001`. All the boxes in lot `20002` are transferred because they have the earliest expiration date. The transfer also requests one box from lot `20001` because it has the next closest expiration date after lot `20002`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "Force removal strategy set up as first in first out." +msgid "The detailed operations for the transfer shows the lots to be removed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:152 -msgid "FIFO (First In, First Out)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:154 -msgid "As explained, a :abbr:`FIFO (First In, First Out)` removal strategy implies that products stocked first move out first. Companies should use this method if they are selling products with short demand cycles, such as clothes, and to ensure they are not stuck with outdated styles in stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:158 -msgid "In this example, there are three lots of white shirts. The shirts are from the :guilabel:`All/Clothes` category, where *FIFO* is set as the removal strategy. In the stock location (:guilabel:`WH/Stock`), the user can find the three lots available." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "View of the white shirt lots inventory valuation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:166 -msgid "Lot :guilabel:`000001` contains five shirts, :guilabel:`000002` contains three shirts, and :guilabel:`000003` contains two shirts." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:167 +msgid "Using removal strategies" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:169 -msgid "As seen above, :guilabel:`000001` entered the stock first. Now, create a sales order of six white shirts to check that those products from lot :guilabel:`000001` are the first ones to move out." +msgid "To differentiate some units of products from others, the units need to be tracked, either by :guilabel:`Lot` or by :guilabel:`Serial Number`. To do so, go to :menuselection:`Inventory --> Configuration --> Settings`. Then, activate the :guilabel:`Storage Locations`, :guilabel:`Multi-Step Routes`, and :guilabel:`Lots & Serial Numbers` settings. Click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:172 -msgid "On the delivery order linked to the picking, the oldest lot numbers should have been reserved thanks to the :abbr:`FIFO (First In, First Out)` strategy." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 +msgid ":alt: Traceability settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 +msgid ":alt: Warehouse settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:183 +msgid "To use the :abbr:`FEFO (First Expired, First Out)` removal strategy, the :guilabel:`Expiration Dates` setting needs to be activated as well. To enable this, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the checkbox next to :guilabel:`Expiration Dates`. Remember to click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:189 +msgid "Now, specific removal strategies can be defined on product categories. To do this, go to :menuselection:`Inventory app --> Configuration --> Product Categories`, and choose a product category to define the removal strategy on. In the :guilabel:`Force Removal Strategy` field, choose a removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 +msgid ":alt: Removal strategy on a product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:198 +msgid "To view all products with lots/serial numbers assigned to them, navigate to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. This reveals a page with drop-down menus of all products assigned lots or serial numbers, filtered by *product* by default. To change the category these products are filtered by, click :guilabel:`Product` (in the search bar, in the top right of the page) to remove the default filter, and select a new filter if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 +msgid "Click on Products, then Lots/Serial Numbers to display all the products with lots or serial\n" +"numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:209 +msgid "To view the serial numbers being selected for a sales order, go to the :guilabel:`Sales app` and select the sales order in question. In the sales order, click the :guilabel:`Delivery` smart button in the top right. In the :guilabel:`Operations` tab, click the :guilabel:`⦙≣ (Detailed Operations)` icon in the far right for the product in question. The :guilabel:`Detailed Operations` window appears, and displays the lot or serial numbers selected for that specific product for the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:217 +msgid "FIFO (First In, First Out)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:219 +msgid "The :abbr:`FIFO (First In, First Out)` removal strategy implies that products which enter a warehouse's stock first are removed first. Companies should use this method if they are selling products with short demand cycles, such as clothes, to ensure they are not stuck with outdated styles in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:224 +msgid "In this example, there are three lots of white shirts. The shirts are from the *All/Clothes* category, where *FIFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 +msgid "View of the lots of white shirts in the inventory valuation report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:232 +msgid "Lot `000001` contains five shirts, lot `000002` contains three shirts, and lot `000003` contains two shirts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:235 +msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`White Shirt`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (for this example, `6.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:242 +msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the oldest lot numbers will be reserved thanks to the :abbr:`FIFO (First In, First Out)` strategy. All five shirts from lot `000001` and one shirt from lot `000002` will be selected to be sent to the customer." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "Two lots being reserved for a sales order with the FIFO strategy." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:180 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:252 msgid "LIFO (Last In, First Out)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:182 -msgid "With a *LIFO* strategy, that's quite the opposite. In fact, the products that are received last move out first. :abbr:`LIFO (Last In, First Out)` is mostly used for products without a shelf life." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:254 +msgid "The :abbr:`LIFO (Last In, First Out)` removal strategy works in the **opposite** manner from the :abbr:`FIFO (First In, First Out)` strategy. With this method, the products that are received **last** are moved out first. This method is mostly used for products without a shelf life, and no time-sensitive factors, such as expiration dates." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:185 -msgid "In this example, let's use the white shirts again to test the :abbr:`LIFO (Last In, First Out)` strategy. First, open the product category via :menuselection:`Inventory --> Configuration --> Product Categories` and change the removal strategy to :abbr:`LIFO (Last In, First Out)`." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:259 +msgid "In this example, there are three lots of cinder blocks. The blocks are from the *All/Building Materials* category, where *FIFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "Last in first out strategy set up as forced removal strategy." +msgid "View of the lots of cinder blocks in the inventory valuation report." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:193 -msgid "Then, create a sales order for four white shirts and check that the reserved products are from lots :guilabel:`000003` and :guilabel:`000002`." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:267 +msgid "Lot `000020` contains three cinder blocks, lot `000030` contains five cinder blocks, and lot `0000400` contains four cinder blocks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:270 +msgid "To see how the :abbr:`LIFO (Last In, First Out)` strategy works, first navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`, and select a product category (for this example, the :guilabel:`All/Building Materials` category) to edit. This reveals a product category form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:275 +msgid "Once on the product category form, under the :guilabel:`Logistics` section, change the :guilabel:`Force Removal Strategy` to :guilabel:`Last In First Out (LIFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 +msgid "Last in first out (LIFO) strategy set up as forced removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:282 +msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`Cinder Block`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (for this example, `5.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:289 +msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the newest lot numbers will be reserved thanks to the :abbr:`LIFO (Last In, First Out)` strategy. All four cinder blocks from lot `0000400` and one cinder block from lot `000030` will be selected to be sent to the customer." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "Two lots being reserved for sale with the LIFO strategy." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:201 -msgid "Don't forget that the :abbr:`LIFO (Last In, First Out)` strategy is banned in many countries!" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:204 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:301 msgid "FEFO (First Expired, First Out)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:206 -msgid "With the :abbr:`FEFO (First Expired, First Out)` removal strategy, the way products are picked is not based on the reception date. In this particular case, they are dispatched according to their expiration date." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:303 +msgid "The :abbr:`FEFO (First Expired, First Out)` removal strategy differs from the :abbr:`FIFO (First In, First Out)` and :abbr:`LIFO (Last In, First Out)` strategies, because it targets products for removal based on **expiration dates** instead of their warehouse receipt dates. With this method, the products that are going to expire first are moved out first. This method is used for perishable products, such as medicine, food, and beauty products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:211 -msgid "For have more information about expiration dates, please have a look at :doc:`the related doc <../../management/lots_serial_numbers/expiration_dates>`." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:309 +msgid "Lots are picked based on their **removal date** from earliest to latest. Removal dates indicate how many days *before* the expiration date the product needs to be removed from stock. The removal date is set on the product form. Lots without a removal date defined are picked after lots with removal dates." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:214 -msgid "By activating the :guilabel:`Expiration Dates` feature, it becomes possible to define different expiration dates on the serial/lot numbers that will be used in :abbr:`FEFO (First Expired, First Out)`. These expiration dates can be set by going to :menuselection:`Inventory --> Products --> Lots/Serial Numbers`." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:315 +msgid "If products are not removed from stock when they should be, lots that are past the expiration date may still be picked for delivery orders!" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:319 +msgid "For more information about expiration dates, reference the :doc:`Expiration dates ` document." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:323 +msgid "First, go to :menuselection:`Inventory app --> Configuration --> Settings` and ensure :guilabel:`Expiration Dates` is enabled. Once the :guilabel:`Expiration Dates` setting is enabled, it's possible to define different expiration dates for individual serialized products, as well as for lot numbers containing many products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:328 +msgid "In this example, there are three lots of hand cream. The creams are from the *All/Health & Beauty* category, where *FEFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:332 +msgid "Lot `0000001` contains twenty tubes of hand cream, expiring on Sept 30, lot `0000002` contains ten tubes of hand cream, expiring on November 30, and lot `0000003` contains ten tubes of hand cream, expiring on October 31." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 +msgid "View the hand cream lot numbers and expiration dates in the inventory report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:340 +msgid "Expiration dates can be entered when validating the received products, or set on products by going to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Click :guilabel:`Create`, enter the serial number, and select the product from the drop-down menu. Next, select the expiration date in the :guilabel:`Dates` tab. Finally, click :guilabel:`Save`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 msgid "View of the removal date for 0000001." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:223 -msgid "Lots are picked based on their removal date, from earliest to latest. Lots without a removal date defined are picked after lots with removal dates." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:349 +msgid "To see how the :abbr:`FEFO (First Expired, First Out)` strategy works, first navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`, and select a product category (in this example, the :guilabel:`All/Health & Beauty` category) to edit. This reveals a product category form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:227 -msgid "Other dates are for informational and reporting purposes only. If not removed from the stock, lots that are past the expiration dates may still be picked for delivery orders!" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:230 -msgid "To use the :abbr:`FEFO (First Expired, First Out)` strategy, go to :menuselection:`Inventory --> Configuration --> Product Categories` and set :abbr:`FEFO (First Expired, First Out)` in the :guilabel:`Force Removal Strategy` field." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:354 +msgid "Once on the product category form, under the :guilabel:`Logistics` section, change the :guilabel:`Force Removal Strategy` to :abbr:`FEFO (First Expired, First Out)`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "View of the FEFO strategy being set up as forced removal strategy." +msgid "FEFO forced removal strategy set on the product category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:238 -msgid "For this particular case, the stock has hand cream. There are three lots of them." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:361 +msgid "Next, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`Hand Cream`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (in this example, `25.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:241 -msgid "**Lot / Serial No**" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:241 -msgid "**Product**" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:241 -msgid "**Expiration Date**" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:243 -msgid "0000001" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:243 -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:245 -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:247 -msgid "Hand Cream" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:243 -msgid "09/30/2019" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:245 -msgid "0000002" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:245 -msgid "11/30/2019" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:247 -msgid "0000003" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:247 -msgid "10/31/2019" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:250 -msgid "When a sales order for 25 units of Hand Cream is created, Odoo automatically reserves the lots with the closest expiration date, :guilabel:`0000001` and :guilabel:`0000003`." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:368 +msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the lot numbers expiring first will be reserved thanks to the :abbr:`FEFO (First Expired, First Out)` strategy. All twenty tubes of hand cream from lot `0000001` and five from lot `0000003` will be selected to be sent to the customer, detailed in the :guilabel:`Detailed Operations` tab in the sales order." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1 -msgid "Two hand cream lots reserved for sell with the FEFO strategy." +msgid "Hand cream lot numbers selected for the sales order." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping.rst:5 @@ -8122,10 +8592,6 @@ msgstr "" msgid "Odoo *Manufacturing* allows for both components and finished products to be scrapped within a manufacturing order. The specific type of item that can be scrapped during a manufacturing order depends on the stage of the manufacturing process." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:19 -msgid "Scrap orders can be viewed by navigating to :menuselection:`Inventory --> Operations --> Scrap`. Each scrap order shows the date and time the order was created, along with the product and quantity that was scrapped." -msgstr "" - #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:23 msgid "To view the total quantity of each item scrapped, navigate to :menuselection:`Inventory --> Configuration --> Locations`, then remove the :guilabel:`Internal` filter from the :guilabel:`Search...` bar to display all virtual locations. From the list, select the :guilabel:`Virtual Locations/Scrap` location." msgstr "" @@ -8486,95 +8952,95 @@ msgstr "" msgid "Use the Master Production Schedule" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:5 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:7 msgid "The Master Production Schedule (MPS) is a valuable tool to plan your production based on your demand forecast." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:11 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:13 msgid "Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` and activate the Master Production Schedule feature before hitting save." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:15 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:17 msgid "In the MPS settings, you can define the time range of your MPS (month/week/day) and the number of periods you want to display at all times." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:18 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:20 msgid "Now, go to :menuselection:`Planning --> Master Production Schedule` and click on *add a product*. You can now define your safety stock target (= the stock you want to have on hand at the end of the period) and the minimum and maximum quantities that must or can be replenished in each period." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:26 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:28 msgid "In the MPS view, you can decide which information you would like to display by clicking on *rows*. For instance, the *Actual demand* will show you which quantity of products has already been ordered for the period, or *Available to Promise*, what can still be sold during that same period (what you plan to replenish - what is already sold during the period). You can also decide to hide rows if you like." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:36 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:38 msgid "Estimate your demand and launch replenishment" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:38 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:40 msgid "The next step is to estimate the demand for the chosen period. This is done in the *Forecasted Demand* Row. You can easily, at any time, compare the demand forecast with the actual demand (= confirmed sales). The demand forecast for a finished product will impact the indirect demand for its components." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:46 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:48 msgid "Once the forecasted demand has been set, the quantity to replenish for the different periods will automatically be computed. The replenishments you are supposed to launch based on your lead times (vendor lead time or manufacturing lead time) are then displayed in green. You can now launch the replenishment by clicking on the replenish button." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:52 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:54 msgid "Depending on the configuration of the product (buy vs. manufacture), requests for quotations or manufacturing orders will be created. You can easily access those by clicking on the *Actual Replenishment* cell." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:59 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:61 msgid "In case you manually edit the *Suggested Replenishment* quantity, a small cross will appear on the left hand side of the cell. In case you want to go back to the automatically computed value given by Odoo, simply click the cross." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:65 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:67 msgid "Cells color signification" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:67 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:69 msgid "The cells, which are part of the *Suggested Replenishment* line, can take different colors depending on the situation:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:70 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:72 msgid "**Green**: quantity of products which should be replenished to reach the expected safety stock considering the demand forecast and the indirect demand forecast." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:72 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:74 msgid "**Grey**: replenishment order has already been generated, and its quantity still matches current data." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:74 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:76 msgid "**Red**: replenishment order has already been generated, and its quantity was too high considering current data." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:76 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:78 msgid "**Orange**: replenishment order has already been generated, and its quantity was too low considering current data." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:78 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:80 msgid "The *Forecasted stock* line can also contain red cells, which means the stock will be negative during the period in question." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:82 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:84 msgid "What if I have underestimated the demand?" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:84 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:86 msgid "You can still increase the demand forecast. It will impact the quantity to replenish. The cell will become orange, and you’ll be able to launch a new replenishment." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:89 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:91 msgid "What if I have overestimated the demand?" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:91 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:93 msgid "You can decrease the demand forecast. The cell will become red to inform you that you’ve ordered more than planned. If you’re still able to do it, you can cancel some RFQ or MO manually." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:96 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:98 msgid "What if I wrongly added a product to the MPS?" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:98 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:100 msgid "You can easily remove a product from the MPS by clicking the small bin on the right of its name." msgstr "" @@ -8622,39 +9088,39 @@ msgstr "" msgid "An example of a fully configured work center form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:35 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:37 msgid "Set standards for work center productivity" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:37 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:39 msgid "The :guilabel:`General Information` tab on the work center form allows for productivity goals to be assigned to a work center:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:40 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:42 msgid ":guilabel:`Time Efficiency`: used to calculate the expected duration of a work order at the work center; for example, if a work order normally takes one hour and the efficiency is set to 200%, the work order will take 30 minutes" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:43 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:45 msgid ":guilabel:`Capacity`: the number of operations that can be performed at the work center simultaneously" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:45 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:47 msgid ":guilabel:`OEE Target`: the target for efficiency at the work center" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:46 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:48 msgid ":guilabel:`Time before prod.`: setup time required before work can commence" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:47 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:49 msgid ":guilabel:`Time after prod.`: breakdown or cleanup time required after work is finished" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:48 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:50 msgid ":guilabel:`Cost per hour`: the cost of operating the work center for one hour" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:49 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:51 msgid ":guilabel:`Analytic Account`: the account where the cost of the work center should be recorded" msgstr "" @@ -8662,35 +9128,35 @@ msgstr "" msgid "The general information tab of the work center form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:56 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:58 msgid "Assign equipment to a work center" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:58 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:60 msgid "Using the :guilabel:`Equipment` tab, it is possible for specific pieces of equipment to be assigned to a work center. The following information will be displayed for each piece of equipment added:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:61 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:63 msgid ":guilabel:`Equipment Name`: the name of the piece of equipment" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:62 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:64 msgid ":guilabel:`Technician`: the technician responsible for servicing the equipment" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:63 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:65 msgid ":guilabel:`Equipment Category`: the category the equipment belongs to" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:64 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:66 msgid ":guilabel:`MTBF`: mean time between failures; the average time that the piece of equipment will operate before failing" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:66 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:68 msgid ":guilabel:`MTTR`: mean time to recovery; the average time it takes for the equipment to become fully operational again" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:68 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:70 msgid ":guilabel:`Est. Next Failure`: an estimate of when the next equipment failure will occur" msgstr "" @@ -8698,27 +9164,27 @@ msgstr "" msgid "The equipment tab of the work center form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:75 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:77 msgid ":guilabel:`MTBF`, :guilabel:`MTTR`, and :guilabel:`Est. Next Failure` are all calculated automatically based on past failure data, if any exists." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:81 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:83 msgid "Integrate IoT devices" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:83 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:85 msgid "The :guilabel:`IoT Triggers` tab enables the integration of :abbr:`IoT (Internet of Things)` devices with a work center:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:86 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:88 msgid ":guilabel:`Device`: specifies the IoT device to be triggered" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:87 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:89 msgid ":guilabel:`Key`: the security key for the device" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:88 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:90 msgid ":guilabel:`Action`: the IoT device action triggered" msgstr "" @@ -8726,19 +9192,19 @@ msgstr "" msgid "The IoT Triggers tab of the work center form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:95 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:97 msgid "Use case: configure an alternative work center" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:97 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:99 msgid "When a work center is at capacity, it cannot accept any new work orders. Instead of waiting for the work center to become available, it is possible to specify an alternative work center where surplus work orders should be carried out." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:101 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:103 msgid "Begin by creating a new work center. Configure the :guilabel:`Equipment` tab so that it has all of the same equipment as the main work center. This will ensure that the same tasks can be carried out at both work centers. Navigate to the main work center and include the new work center in the :guilabel:`Alternative Workcenters` selection field." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:106 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:108 msgid "Now, create a new manufacturing order that uses the main work center for one of its operations. The main work center will automatically be selected for the operation in the :guilabel:`Work Orders` tab. After confirming the manufacturing order, click the :guilabel:`Plan` button that appears at the top left of the form." msgstr "" @@ -8746,7 +9212,7 @@ msgstr "" msgid "Click the plan button to automatically select an available work center." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:115 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:117 msgid "If the main work center is at capacity, the work center selected for the operation will be automatically changed to the alternative work center." msgstr "" @@ -8754,27 +9220,27 @@ msgstr "" msgid "The alternative work center is automatically selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:123 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:125 msgid "Monitor work center performance" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:125 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:127 msgid "Performance for an individual work center can be viewed by selecting :menuselection:`Configuration --> Work Centers`, and clicking on a work center. A variety of metrics showing work center performance can be viewed at the top right of the form:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:129 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:131 msgid ":guilabel:`OEE`: overall effective efficiency, the percentage of time that the work center has been fully productive" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:131 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:133 msgid ":guilabel:`Lost`: the amount of time lost due to work stoppages" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:132 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:134 msgid ":guilabel:`Load`: the amount of time it will take to complete the current workload" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:133 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:135 msgid ":guilabel:`Performance`: the real duration of work time, shown as a percentage of the expected duration" msgstr "" diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index 4132e5791..de5c9ee1b 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-15.2\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-26 13:30+0000\n" +"POT-Creation-Date: 2023-12-19 07:46+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -334,42 +334,38 @@ msgid "Even after synchronizing the Odoo Calendar with the Outlook calendar, Out msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:106 -msgid "After one user syncs their Outlook calendar to the Odoo database, unwanted email notifications are unavoidable because the first synchronized user's events will be in the Odoo Calendar. If the Odoo database is shared amongst multiple users, and another user wants to sync their Outlook calendar with Odoo Calendar, Outlook will again pull the existing Odoo Calendar events during the sync and treat them as new events, causing Outlook to send email invitations to all event attendees." -msgstr "" - -#: ../../content/applications/productivity/calendar/outlook.rst:113 msgid "In summary, once a user synchronizes their Outlook calendar with the Odoo calendar:" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:115 +#: ../../content/applications/productivity/calendar/outlook.rst:108 msgid "Creating an event in Odoo causes Outlook to send an invitation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:116 +#: ../../content/applications/productivity/calendar/outlook.rst:109 msgid "Deleting an event in Odoo causes Outlook to send a cancellation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:117 +#: ../../content/applications/productivity/calendar/outlook.rst:110 msgid "Unarchiving an event in Odoo causes Outlook to send an invitation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:118 +#: ../../content/applications/productivity/calendar/outlook.rst:111 msgid "Archiving an event in Odoo causes Outlook to send a cancellation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:119 +#: ../../content/applications/productivity/calendar/outlook.rst:112 msgid "Adding a contact to an event causes Outlook to send an invitation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:120 +#: ../../content/applications/productivity/calendar/outlook.rst:113 msgid "Removing a contact from an event causes Outlook to send a cancellation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:123 +#: ../../content/applications/productivity/calendar/outlook.rst:116 msgid "Sync Odoo Calendar and Outlook" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:125 +#: ../../content/applications/productivity/calendar/outlook.rst:118 msgid "In the Odoo database, go to the :guilabel:`Calendar` module and click the :guilabel:`Outlook` sync button. The page will redirect to a Microsoft login page, and the user is asked to log in to their account, if they are not already, and grant the required permissions." msgstr "" @@ -377,19 +373,19 @@ msgstr "" msgid "The \"Outlook\" sync button in Odoo Calendar." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:133 +#: ../../content/applications/productivity/calendar/outlook.rst:126 msgid "The synchronization is a two-way process, meaning that events are reconciled in both accounts (Outlook and Odoo)." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:137 +#: ../../content/applications/productivity/calendar/outlook.rst:130 msgid "All users that want to use the synchronization simply need to :ref:`sync their calendar with Outlook `. The configuration of Microsoft's Azure account is only done once, as Microsoft Entra ID tenants' Client IDs and Client Secrets are unique, and represent an organization that helps the user to manage a specific instance of Microsoft cloud services for their internal and external users." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:144 +#: ../../content/applications/productivity/calendar/outlook.rst:137 msgid ":doc:`../mail_plugins/outlook`" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:145 +#: ../../content/applications/productivity/calendar/outlook.rst:138 msgid ":doc:`google`" msgstr "" @@ -623,7 +619,7 @@ msgid "View of the contacts’ status for Odoo Discuss" msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:97 -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:65 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:250 msgid ":doc:`team_communication`" msgstr "" @@ -632,76 +628,302 @@ msgid ":doc:`/applications/general/email_communication/email_servers`" msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:3 -msgid "Get Organized by Planning Activities" +msgid "Activities" msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:5 -msgid "When you plan activities you minimize the risk of uncertainties, as you provide clear directions for the course of your next action. In addition to that, you do not leave space for wasteful activities and reduce the chance of having overlapping actions between team members." +msgid "*Activities* are follow-up tasks tied to a record in an Odoo database. Activities can be scheduled on any page of the database that contains a chatter thread, kanban view, list view, or activities view of an application." msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:10 -msgid "Where do I see my schedule activities?" +msgid "Schedule activities" msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:12 -msgid "Access and manage your activities wherever you are in Odoo by the *Activities* menu." +msgid "One way that activities are created is by clicking the :guilabel:`Schedule Activity` button, located at the top of the *chatter* on any record. On the pop-up window that appears, select an :guilabel:`Activity Type` from the drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:17 +msgid "Individual applications have a list of *Activity Types* dedicated to that application. For example, to view and edit the activities available for the *CRM* application, go to :menuselection:`CRM app --> Configuration --> Activity Types`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:21 +msgid "Enter a title for the activity in the :guilabel:`Summary` field, located in the :guilabel:`Schedule Activity` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:24 +msgid "To assign the activity to a different user, select a name from the :guilabel:`Assigned to` drop-down menu. Otherwise, the user creating the activity is automatically assigned." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:27 +msgid "Lastly, feel free to add any additional information in the optional :guilabel:`Log a note...` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:30 +msgid "The :guilabel:`Due Date` field on the :guilabel:`Schedule Activity` pop-up window auto-populates based on the configuration settings for the selected :guilabel:`Activity Type`. However, this date can be changed by selecting a day on the calendar in the :guilabel:`Due Date` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:34 +msgid "Lastly, click one of the following buttons:" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:36 +msgid ":guilabel:`Schedule`: adds the activity to the chatter under :guilabel:`Planned activities`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:37 +msgid ":guilabel:`Mark as Done`: adds the details of the activity to the chatter under :guilabel:`Today`. The activity is not scheduled, it is automatically marked as completed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:39 +msgid ":guilabel:`Done \\& Schedule Next`: adds the task under :guilabel:`Today` marked as done, and opens a new activity window." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:41 +msgid ":guilabel:`Discard`: discards any changes made on the pop-up window." msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 -msgid "View of crm leads page emphasizing the activities menu for Odoo Discuss" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:20 -msgid "Plan activities" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:22 -msgid "Activities can be planned and managed from the chatter by clicking on *Schedule activity*, or through Kanban views." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 -msgid "View of crm leads and the option to schedule an activity for Odoo Discuss" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:31 -msgid "Set your activity types" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:33 -msgid "A number of activities types are available by default in Odoo (call, email, meeting, etc.). However, you can set new ones going to :menuselection:`Settings --> Activity types`." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 -msgid "View of the settings page emphasizing the menu activity types for Odoo Discuss" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:42 -msgid "If you need to create an activity type with an available calendar, make sure to create it with an *Action to Perform* set as *Meeting*." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:46 -msgid "Recommend next activities" +msgid "View of CRM leads and the option to schedule an activity." msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:48 -msgid "Odoo helps you to plan a flow of activities by allowing you to set *Recommended Next Activities*." +msgid "Depending on the activity type, the :guilabel:`Schedule` button may be replaced by a :guilabel:`Save` button, or an :guilabel:`Open Calendar` button." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:51 +msgid "Scheduled activities are added to the chatter for the record under :guilabel:`Planned activities`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:57 +msgid "Activities can also be scheduled from the kanban, list, or activities view of an application." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:61 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:63 +msgid "Select a record on which to schedule an activity. Click on the :guilabel:`🕘 (clock)` icon, then :guilabel:`Schedule An Activity`, and proceed to fill out the pop-up form." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "Kanban view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:70 +msgid "List view" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:72 +msgid "Select a record on which to schedule an activity. Click on the :guilabel:`🕘 (clock)` icon, then :guilabel:`Schedule An Activity`. If the record already has an activity scheduled, the clock icon may be replaced by a :guilabel:`📞 (phone)` or an :guilabel:`✉️ (envelope)` icon." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "List view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:80 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:82 +msgid "To open the activity view for an application, select the :guilabel:`🕘 (clock)` icon from the menu bar anywhere in the database. Select any application from the drop-down menu, and click the :guilabel:`🕘 (clock)` icon for the desired app." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "Activity menu drop down with focus on where to open activity view for CRM." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:90 +msgid "Select a record on which to schedule an activity. Move across the row to find the desired activity type, then click the :guilabel:`＋ (plus sign)`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "Activity view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:98 +msgid "Activity colors, and their relation to an activity's due date, is consistent throughout Odoo, regardless of the activity type, or the view." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:101 +msgid "Activities that appear in **green** indicate a due date sometime in the future." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:102 +msgid "**Yellow** indicates that the activity's due date is today." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:103 +msgid "**Red** indicates that the activity is overdue and the due date has passed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:105 +msgid "For example, if an activity is created for a phone call, and the due date passes, the activity appears with a red phone in list view, and a red clock on the kanban view." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:109 +msgid "View scheduled activities" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:111 +msgid "To view scheduled activities, open either the :menuselection:`Sales app` or :menuselection:`CRM app` and click the :guilabel:`🕘 (clock)` icon, located to the far-right side of the other view options." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:114 +msgid "Doing so opens the activities menu, showcasing all the scheduled activities for the user, by default. To show all activities for every user, remove the :guilabel:`My Pipeline` filter from the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:118 +msgid "To view a consolidated list of activities separated by the application where they were created, and by deadline, click the :guilabel:`🕘 (clock)` icon on the header menu to see the activities for that specific application in a drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:122 +msgid "The possibility to :guilabel:`Add new note` and :guilabel:`Request a Document` appear at the bottom of this drop-down menu, when the :guilabel:`🕘 (clock)` icon on the header menu is clicked." msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 -msgid "View of an activity type form emphasizing the field recommended next activities for Odoo\n" -"Discuss" +msgid "View of CRM leads page emphasizing the activities menu." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:55 -msgid "Once the respective activity is completed, select *Done & Schedule Next* and next steps are suggested to you." +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:130 +msgid "Configure activity types" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:132 +msgid "To configure the types of activities in the database, go to :menuselection:`Settings app --> Discuss --> Activities --> Activity Types`." msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 -msgid "View of an activity being schedule emphasizing the recommended activities field being\n" -"shown for Odoo Discuss" +msgid "View of the settings page emphasizing the menu activity types." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:64 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:139 +msgid "Doing so reveals the :guilabel:`Activity Types` page, where the existing activity types are found." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:141 +msgid "To edit an existing activity type, select it from the list, then click :guilabel:`Edit`. To create a new activity type, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:144 +msgid "At the top of a blank activity type form, start by choosing a :guilabel:`Name` for the new activity type." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 +msgid "New activity type form." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:152 +msgid "Activity settings" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:155 +#: ../../content/applications/productivity/studio/automated_actions.rst:134 +msgid "Action" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:157 +msgid "The *Action* field specifies the intent of the activity. Some actions trigger specific behaviors after an activity is scheduled." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:160 +msgid "If :guilabel:`Upload Document` is selected, a link to upload a document is added directly to the planned activity in the chatter." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:162 +msgid "If either :guilabel:`Phonecall` or :guilabel:`Meeting` are selected, users have the option to open their calendar to schedule a time for this activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:164 +msgid "If :guilabel:`Request Signature` is selected, a link is added to the planned activity in the chatter that opens a signature request pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:168 +msgid "The actions available to select on an activity type vary, depending on the applications currently installed in the database." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:172 +msgid "Default user" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:174 +msgid "To automatically assign this activity to a specific user when this activity type is scheduled, choose a name from the :guilabel:`Default User` drop-down menu. If this field is left blank, the activity is assigned to the user who creates the activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:179 +msgid "Default summary" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:181 +msgid "To include notes whenever this activity type is created, enter them into the :guilabel:`Default Summary` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:185 +msgid "The information in the :guilabel:`Default User` and :guilabel:`Default Summary` fields are included when an activity is created. However, they can be altered before the activity is scheduled or saved." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:190 +msgid "Next activity" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:192 +msgid "To automatically suggest, or trigger, a new activity after an activity has been marked complete, the :guilabel:`Chaining Type` must be set." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:196 +msgid "Suggest next activity" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:198 +msgid "In the :guilabel:`Chaining Type` field, select :guilabel:`Suggest Next Activity`. Upon doing so, the field underneath changes to: :guilabel:`Suggest`. Click the :guilabel:`Suggest` field drop-down menu to select any activities to recommend as follow-up tasks to this activity type." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:202 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:230 +msgid "In the :guilabel:`Schedule` field, choose a default deadline for these activities. To do so, configure a desired number of :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`. Then, decide if it should occur :guilabel:`after completion date` or :guilabel:`after previous activity deadline`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:207 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:235 +msgid "This :guilabel:`Schedule` field information can be altered before the activity is scheduled." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:209 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:237 +msgid "When all configurations are complete, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 +msgid "Schedule activity popup with emphasis on recommended activities." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:216 +msgid "If an activity has the :guilabel:`Chaining Type` set to :guilabel:`Suggest Next Activity`, and has activities listed in the :guilabel:`Suggest` field, users are presented with recommendations for activities as next steps." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:221 +msgid "Trigger next activity" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:223 +msgid "Setting the :guilabel:`Chaining Type` to :guilabel:`Trigger Next Activity` immediately launches the next activity once the previous one is completed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:226 +msgid "If :guilabel:`Trigger Next Activity` is selected in the :guilabel:`Chaining Type` field, the field beneath changes to: :guilabel:`Trigger`. From the :guilabel:`Trigger` field drop-down menu, select the activity that should be launched once this activity is completed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 +msgid "Schedule new activity popup with emphasis on Done and launch next button." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:244 +msgid "When an activity has the :guilabel:`Chaining Type` set to :guilabel:`Trigger Next Activity`, marking the activity as `Done` immediately launches the next activity listed in the :guilabel:`Trigger` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:249 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:98 msgid ":doc:`get_started`" msgstr "" @@ -806,8 +1028,12 @@ msgstr "" msgid "Internet of Things (IoT)" msgstr "" +#: ../../content/applications/productivity/iot.rst:17 +msgid "The Open Platform Communications (OPC) Unified Architecture (UA) protocol is now supported by the :abbr:`IoT (Internet of Things)` box. :abbr:`OPC (Open Platform Communications)` :abbr:`UA (United Architecture)` is an open standard that specifies information exchange for industrial communication on devices, between machines and between systems. This includes communication between information technology and operational technology. :abbr:`OPC (Open Platform Communications)` :abbr:`UA (United Architecture)` can be used with any software platform, on a wide variety of devices, and deployed securely. The :abbr:`IoT (Internet of Things)` box has entered the world of the Industry 4.0 standard and can be utilized in a wide variety of industries, and for things like building automation, packaging, utilities, etc." +msgstr "" + #: ../../content/applications/productivity/iot/config.rst:5 -#: ../../content/applications/productivity/mail_plugins/outlook.rst:6 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:10 msgid "Configuration" msgstr "" @@ -2733,160 +2959,160 @@ msgstr "" msgid "Outlook Plugin" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:8 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:5 +msgid "Outlook allows for third-party applications to connect in order to execute database actions from emails. Odoo has a plugin for Outlook that allows for the creation of an opportunity from the email panel." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:12 msgid "The Outlook :doc:`Mail Plugin <../mail_plugins>` needs to be configured both on Odoo and Outlook." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:13 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:17 msgid "Enable Mail Plugin" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:15 -msgid "First, you need to enable the *Mail Plugin* feature in your database. Go to :menuselection:`Settings --> General Settings --> Integrations`, enable *Mail Plugin*, and *Save* the configuration." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:21 -msgid "Install the Outlook Plugin" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:23 -msgid "Open your Outlook mailbox and select any email." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:19 +msgid "First, enable the *Mail Plugin* feature in the database. Go to :menuselection:`Settings --> General Settings --> Integrations`, enable :guilabel:`Mail Plugin`, and :guilabel:`Save` the configuration." msgstr "" #: ../../content/applications/productivity/mail_plugins/outlook.rst:25 -msgid "Click on the *More actions* button and select *Get Add-ins*." +msgid "Install the Outlook Plugin" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 -msgid "More actions button in Outlook" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:27 +msgid "Download (:menuselection:`Save Page As --> Web Page XML only`) the following XML file to upload later: `https://download.odoocdn.com/plugins/outlook/manifest.xml `_." msgstr "" #: ../../content/applications/productivity/mail_plugins/outlook.rst:31 -msgid "Select the *My add-ins* tab." +msgid "Next, open the Outlook mailbox, and select any email. After completing this, click on the :guilabel:`More actions` button in the upper right-side and select :guilabel:`Get Add-ins`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 +msgid "More actions button in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:38 +msgid "Following this step, select the :guilabel:`My add-ins` tab on the left-side." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 msgid "My add-ins in Outlook" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:37 -msgid "Under *Custom add-ins*, click on *+ Add a custom add-in*, and then on *Add from URL...*" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:44 +msgid "Under :guilabel:`Custom add-ins` towards the bottom, click on :guilabel:`+ Add a custom add-in`, and then on :guilabel:`Add from file...`" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 msgid "Custom add-ins in Outlook" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:43 -msgid "Enter the following URL `https://download.odoocdn.com/plugins/v15/outlook/manifest.xml` and press *OK*." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:51 +msgid "For the next step, attach the `manifest.xml` file downloaded above, and press :guilabel:`OK`. Next, read the warning and click on :guilabel:`Install`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 -msgid "Entering the add-in URL in Outlook" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:50 -msgid "Read the warning and click on *Install*." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 msgid "Custom add-in installation warning in Outlook" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:59 -msgid "Connect your database" -msgstr "" - #: ../../content/applications/productivity/mail_plugins/outlook.rst:61 -msgid "Open any email in your Outlook mailbox, click on the *More actions* button, and select *Odoo for Outlook*." +msgid "Connect the database" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:63 +msgid "Now, Outlook will be connected to the Odoo database. First, open any email in the Outlook mailbox, click on the :guilabel:`More actions` button in the upper right-side, and select :guilabel:`Odoo for Outlook`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 msgid "Odoo for Outlook add-in button" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:68 -msgid "The right-side panel can now display **Company Insights**. At the bottom, click on *Login*." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:71 +msgid "The right-side panel can now display **Company Insights**. At the bottom, click on :guilabel:`Login`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 -msgid "Logging in your Odoo database" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:75 -msgid "Only a limited amount of *Company Insights* (*Lead Enrichment*) requests are available as a trial. This feature requires :ref:`prepaid credits `." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 +msgid "Logging in the Odoo database" msgstr "" #: ../../content/applications/productivity/mail_plugins/outlook.rst:79 -msgid "If, after a short while, the panel is still empty, it is possible that your browser cookie settings prevented it from loading. Note that these settings also change if you are in \"Incognito\" mode on your browser." +msgid "Only a limited amount of **Company Insights** (*Lead Enrichment*) requests are available as a trial database. This feature requires :ref:`prepaid credits `." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:84 -msgid "To fix this issue, configure your browser to always allow cookies on Odoo's plugin page." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:83 +msgid "If, after a short while, the panel is still empty, it is possible that the browser cookie settings prevented it from loading. Note that these settings also change if the browser is in \"Incognito\" mode." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:86 -msgid "For Google Chrome, you can do so by following the guide at: `https://support.google.com/chrome/answer/95647 `_ and adding `download.odoo.com` to the list of `Sites that can always use cookies`." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:87 +msgid "To fix this issue, configure the browser to always allow cookies on Odoo's plugin page." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:90 -msgid "Once done, the Outlook panel needs to be opened again." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:89 +msgid "For Google Chrome, change the browser cookie settings by following the guide at: `https://support.google.com/chrome/answer/95647 `_ and adding `download.odoo.com` to the list of :guilabel:`Sites that can always use cookies`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:93 -msgid "Enter your Odoo database URL and click on *Login*." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:94 +msgid "Once this is complete, the Outlook panel needs to be opened again." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 -msgid "Entering your Odoo database URL" +#: ../../content/applications/productivity/mail_plugins/outlook.rst:96 +msgid "Now, enter the Odoo database URL and click on :guilabel:`Login`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:99 -msgid "Click on *Allow* to open the pop-up window." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 +msgid "Entering the Odoo database URL" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:102 +msgid "Next, click on :guilabel:`Allow` to open the pop-up window." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 msgid "New window pop-up warning" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:105 -msgid "If you aren't logged into your database, enter your credentials." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:108 +msgid "If the user isn't logged into the database, enter the credentials. Click on :guilabel:`Allow` to let the Outlook Plugin connect to the database." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:107 -msgid "Click on *Allow* to let the Outlook Plugin connect to your database." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 msgid "Allowing the Outlook Plugin to connect to a database" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:116 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:118 msgid "Add a shortcut to the plugin" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:118 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:120 msgid "By default, the Outlook Plugin can be opened from the *More actions* menu. However, to save time, it's possible to add it next to the other default actions." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:121 -msgid "In your Outlook mailbox, click on *Settings*, then on *View all Outlook settings*." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:123 +msgid "In the Outlook mailbox, click on :guilabel:`Settings`, then on :guilabel:`View all Outlook settings`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 msgid "Viewing all Outlook settings" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:127 -msgid "Select *Customize actions* under *Mail*, click on *Odoo for Outlook*, and then *Save*." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:130 +msgid "Now, select :guilabel:`Customize actions` under :guilabel:`Mail`, click on :guilabel:`Odoo for Outlook`, and then :guilabel:`Save`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:0 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 msgid "Odoo for Outlook customized action" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:133 -msgid "Open any email; the shortcut should be displayed." +#: ../../content/applications/productivity/mail_plugins/outlook.rst:137 +msgid "Following this step, open any email; the shortcut should be displayed." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:144 +msgid "Using the plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:146 +msgid "Now that the plug-in is installed and operational, all that needs to be done to create a lead is to click on the `O` [Odoo icon] or navigate to :guilabel:`More actions` and click on :guilabel:`Odoo for Outlook`. The side panel will appear on the right-side, and under :guilabel:`Opportunities` click on :guilabel:`New`. A new window with the created opportunity in the Odoo database will populate." msgstr "" #: ../../content/applications/productivity/studio.rst:6 @@ -3069,10 +3295,6 @@ msgstr "" msgid "Define on which records of the model the automated action should be applied. It works the same way as when you apply filters on a model." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:134 -msgid "Action" -msgstr "" - #: ../../content/applications/productivity/studio/automated_actions.rst:136 msgid "Determine what the automated action should do (server action). There are eight types of action to choose from." msgstr "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index 3a616086c..006cfcf25 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-15.2\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-26 13:30+0000\n" +"POT-Creation-Date: 2023-12-19 07:46+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -61,7 +61,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:13 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:12 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:16 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:13 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:17 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:12 #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:17 #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:9 @@ -737,7 +737,7 @@ msgid "Manage lost opportunities" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:5 -msgid "While working with your opportunities, you might lose some of them. You will want to keep track of the reasons you lost them and also which ways Odoo can help you recover them in the future." +msgid "Not all opportunities result in successful sales. In order to keep the pipeline up to date, lost opportunities need to be identified. Specifying the reason why an opportunity was lost provides additional insight that can prove useful for future opportunities." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:10 @@ -745,66 +745,126 @@ msgid "Mark a lead as lost" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:12 -msgid "While in your pipeline, select any opportunity you want and you will see a *Mark Lost* button." +msgid "To mark a lead as lost, open the :menuselection:`CRM` application, and select a lead from the pipeline, by clicking on its corresponding kanban card. Doing so reveals that lead's detail form." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:15 -msgid "You can then select an existing *Lost Reason* or create a new one right there." +msgid "Then, click :guilabel:`Lost`, located at the top of the lead's detail form." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:22 -msgid "Manage & create lost reasons" +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 +msgid "Buttons from the top of an opportunity record with the lost button emphasized." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:24 -msgid "You will find your *Lost Reasons* under :menuselection:`Configuration --> Lost Reasons`." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:21 +msgid "This opens the :guilabel:`Lost Reason` popup. From the drop-down, choose an existing lost reason. If no applicable reason is available, create a new one by entering it into the :guilabel:`Lost Reason` field, and clicking :guilabel:`Create`." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:26 -msgid "You can select & rename any of them as well as create a new one from there." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:25 +msgid "Additional notes and comments can be added below the lost reason designated in the :guilabel:`Lost Reason` field." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:30 -msgid "Retrieve lost opportunities" +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:28 +msgid "When all the desired information has been entered in the :guilabel:`Lost Reason` pop-up window, click :guilabel:`Submit`." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:32 -msgid "To retrieve lost opportunities and do actions on them (send an email, make a feedback call, etc.), select the *Lost* filter in the search bar." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 +msgid "Lost reasons popup with sample reasons." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:35 +msgid "Upon clicking :guilabel:`Submit`, the pop-up window disappears, and Odoo returns to the lead detail form, where a new red :guilabel:`Lost` banner is now present in the upper-right corner of the lead." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:39 -msgid "You will then see all your lost opportunities." +msgid "Create/edit lost reasons" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:41 -msgid "If you want to refine them further, you can add a filter on the *Lost Reason*." +msgid "To create a new lost reason, or edit an existing one, navigate to :menuselection:`CRM app --> Configuration --> Lost Reasons`." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:44 -msgid "For Example, *Too Expensive*." +msgid "To edit an existing reason, click on the reason that should be modified. When clicked, that reason becomes highlighted. Once highlighted, change the description of the selected lost reason by editing the :guilabel:`Description` field. When done, click :guilabel:`Save` in the upper-left corner." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:50 -msgid "Restore lost opportunities" +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:48 +msgid "To create a new lost reason, click :guilabel:`Create` in the upper-left corner of the :guilabel:`Lost Reasons` page. Doing so reveals a new blank line in the :guilabel:`Description` field. Then, proceed to type in the new lost reason in that new line. Once ready, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:52 -msgid "From the Kanban view with the filter(s) in place, you can select any opportunity you wish and work on it as usual. You can also restore it by clicking on *Archived*." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:54 +msgid "Retrieve lost opportunities" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:59 -msgid "You can also restore items in batch from the Kanban view when they belong to the same stage. Select *Restore Records* in the column options. You can also archive the same way." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:56 +msgid "To retrieve lost opportunities in Odoo *CRM*, open the :menuselection:`CRM app` to the main :guilabel:`Pipeline` dashboard. Then, click the :guilabel:`Filters` drop-down menu, located beneath the search bar." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:66 -msgid "To select specific opportunities, you should switch to the list view." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 +msgid "Search bar with lost filter emphasized." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:64 +msgid "From the :guilabel:`Filters` drop-down menu, select the :guilabel:`Lost` option. Upon selecting :guilabel:`Lost`, only the leads that have been marked as `Lost` appear on the :guilabel:`Pipeline` page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:68 +msgid "To filter leads by a specific lost reason, select :menuselection:`Filters --> Add Custom Filter`. Doing so reveals another drop-down menu with three fields." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:71 -msgid "Then you can select as many or all opportunities and select the actions you want to take." +msgid "In the top field drop-down menu, select :guilabel:`Lost Reason`. In the second field drop-down menu, select :guilabel:`Contains`. Then, in the third field of the :guilabel:`Add Custom Field` sub menu, type in the specific keyword(s). Lastly, click :guilabel:`Apply`. Upon clicking :guilabel:`Apply`, Odoo reveals all the lost leads with a reason that contains that specified keyword(s)." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:78 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 +msgid "Search bar with custom filter added for lost reason." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:81 +msgid "Restore lost opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:83 +msgid "To restore a lost opportunity, navigate to the main :guilabel:`Pipeline` dashboard on the *CRM* app, open the :guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option. Doing so reveals all the lost opportunities on the :guilabel:`Pipeline` page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:87 +msgid "Then, click on the kanban card of the desired lost opportunity to restore, which opens that lead's detail form." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:90 +msgid "From the lost lead's detail form, click :guilabel:`Restore` in the upper-left corner. Doing so removes the red :guilabel:`Lost` banner from the lead form, signifying the lead has been restored." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 +msgid "Lost opportunity with emphasis on the Restore button." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:98 +msgid "Restore multiple opportunities at once" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:100 +msgid "To restore multiple opportunities at once, navigate to the main :guilabel:`Pipeline` dashboard in the *CRM* app, open the :guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:103 +msgid "Next, select the list view option, which is represented by the three-line :guilabel:`☰ (list)` icon in the upper-right corner. Doing so places all the leads from the :guilabel:`Pipeline` page in a list form. With the list form chosen, select the checkbox to the left of each desired opportunity/lead to be restored." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:108 +msgid "Once the desired opportunities/leads have been selected, click the :guilabel:`⚙️ Action (gear)` drop-down menu at the top of the :guilabel:`Pipeline` page. From the :guilabel:`⚙️ Action (gear)` drop-down menu, select :guilabel:`Unarchive`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:112 +msgid "Doing so removes those selected lost opportunities from the :guilabel:`Pipeline` page because they no longer fit into the `Lost` filter criteria. To reveal these newly-restored leads, delete the `Lost` filter from the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 +msgid "Action button from list view with the Unarchive option emphasized." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:121 msgid ":doc:`../performance/win_loss`" msgstr "" @@ -2171,7 +2231,7 @@ msgid "Even though Worldline has recently acquired SIX Payment Services and both msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:19 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:16 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:20 msgid "Configure the Payment Method" msgstr "" @@ -2192,7 +2252,7 @@ msgid "Create a new payment method for the SIX payment terminal." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:37 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:40 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:44 msgid "Pay with a Payment Terminal" msgstr "" @@ -2228,19 +2288,23 @@ msgstr "" msgid "Please note MercuryPay only operates with US and Canadian banks, making this procedure only suitable for North American businesses." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:18 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:13 +msgid "Vantiv card readers should be purchased exclusively from Vantiv, as certain Vantiv terminals bought on Amazon do not include the correct encryption needed to be used with an Odoo database." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:22 msgid "First, go in the general settings of the POS app, and activate the Vantiv setting." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:24 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:28 msgid "Back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, go in the payments section and access your payment methods. Create a new payment method for Vantiv, select the payment terminal option Vantiv, and create new Vantiv credentials." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:32 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:36 msgid "To create new Vantiv credentials, fill in your merchant ID and password, then save. Make sure the credentials you just created are selected, then save the payment method." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:42 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:46 msgid "In your PoS interface, at the moment of the payment, select your Vantiv payment method and… that’s all." msgstr "" @@ -5731,63 +5795,75 @@ msgid "If any changes are made on a form in Odoo, include *Contacts* forms, reme msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:3 -msgid "Get paid to confirm an order" +msgid "Online payment order confirmation" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:5 -msgid "In general, online payments are considered as a fast and secure alternative to traditional payment methods. It is generally cheaper, easier and faster than other payment methods. It is particularly useful and efficient for international transactions. With Odoo Sales, you can use online payments to get automatic orders confirmation. Online payments are made instantly, so it's very convenient and saves lots of time in a basic sales process." +msgid "With Odoo *Sales*, online payments can be used to get automatic confirmation on orders." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:12 +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:8 msgid "Enable online payment" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:14 -msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and activate the **Online Payment** feature." +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:10 +msgid "Go to :menuselection:`Sales app --> Configuration --> Settings`, scroll to the :guilabel:`Quotations \\& Orders` heading, and activate the :guilabel:`Online Payment` feature by checking the box next to it, and clicking :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:-1 -msgid "How to enable online payment on Odoo Sales?" +msgid "How to enable online payment on Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:22 -msgid "There, you will have direct access to the **Payment Acquirers** page. It will allow you to select and configure your acquirers of choice. Before creating or modifying a payment acquirer, be sure to check out our documentation about how to be paid with payment acquirers such as :doc:`/applications/finance/payment_acquirers/paypal`, :doc:`/applications/finance/payment_acquirers/authorize`, and others in the :doc:`/applications/finance/payment_acquirers` documentation." +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:18 +msgid "After checking the box beside the :guilabel:`Online Payment` feature, a link to the :guilabel:`Payment Acquirers` appears beneath it. Click that link to reveal the entire :guilabel:`Payment Acquirers` page." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:-1 +msgid "Payment acquirers page in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:26 +msgid "On the :guilabel:`Payment Acquirers` page, payment acquirers can be selected and configured. Before creating (or modifying) a payment acquirer, be sure to review the documentation related to the ways payment acquirers can be used with Odoo, such as:" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:30 -msgid "If you are familiar with this documentation: :doc:`quote_template`; you can activate or not the **Online Payment** feature for each template you use, under their confirmation tab." +msgid ":doc:`../../../finance/payment_acquirers/paypal`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:31 +msgid ":doc:`../../../finance/payment_acquirers/authorize`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:32 +msgid ":doc:`../../../finance/payment_acquirers`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:35 +msgid "On quotation templates, the :guilabel:`Online Payment` feature is located under the :guilabel:`Confirmation` tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:38 +msgid "On standard quotations, the :guilabel:`Online Payment` feature is located under the :guilabel:`Other Info` tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:42 msgid "Register a payment" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:37 -msgid "After opening quotations from their received email, your customers will have different possibilities to make their online payments. For example:" +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:44 +msgid "After opening quotations from the email they receive, customers are presented with different options to make online payments, in the :guilabel:`Pay with` section." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:-1 -msgid "How to register a payment on Odoo Sales?" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:46 -msgid "By clicking on the **Customer Preview** button, you will be able to see what your customers will have to choose when it comes to payment." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:50 -msgid ":doc:`quote_template`" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:51 -msgid ":doc:`/applications/finance/payment_acquirers`" +msgid "How to register a payment on Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:52 -msgid ":doc:`/applications/finance/payment_acquirers/paypal`" +msgid "Clicking the :guilabel:`Customer Preview` smart button on the quotation form provides a preview of the quotation as the customer sees it, along with the various online payment options they can choose from." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:53 -msgid ":doc:`/applications/finance/payment_acquirers/authorize`" +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:57 +msgid ":doc:`quote_template`" msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:3 @@ -5935,15 +6011,15 @@ msgid "How to add optional products to your quotation templates on Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:3 -msgid "Use product variants on quotations and sales orders" +msgid "Product variants on quotations and sales orders" msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:5 -msgid "Product variants can be added to quotations and sales orders using the Product Configurator, Variant Grid Entry, or both." +msgid "Product variants can be added to quotations and sales orders using the *product configurator*, *variant grid entry*, or both." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:11 -msgid "To enable product variants on quotations and sales orders, go to :menuselection:`Sales --> Configuration --> Settings --> Product Catalog` and activate one or both of the :guilabel:`Product Configurator` and :guilabel:`Variant Grid Entry` settings. Finally, click :guilabel:`Save` to apply the settings." +msgid "To enable product variants on quotations and sales orders, go to :menuselection:`Sales app --> Configuration --> Settings`, and under the :guilabel:`Product Catalog` heading, activate one (or both) of the :guilabel:`Product Configurator` and :guilabel:`Variant Grid Entry` settings. Finally, click :guilabel:`Save` to apply the settings." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 @@ -5951,55 +6027,111 @@ msgid "Activating entry type settings." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:20 -msgid "After saving the settings, configure the product form. Head over to :menuselection:`Sales --> Products --> Products` and select any product (or click :guilabel:`Create` to create a new one). On the product form, click :guilabel:`Edit`, and then click on the :guilabel:`Variants` tab. Under :guilabel:`Sales Variant Selection`, choose either :guilabel:`Product Configurator` or :guilabel:`Order Grid Entry`. This selection determines which method is used to add the product to quotations or sales orders. Finally, click :guilabel:`Save` to apply the setting." +msgid "After saving the settings, it's time to configure the product form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:22 +msgid "To do that, navigate to :menuselection:`Sales app --> Products --> Products`, and select the desired product to configure (or click :guilabel:`Create` to open a blank product form, and create a new one)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:26 +msgid "On the product form, click :guilabel:`Edit`, and select the :guilabel:`Variants` tab. Click :guilabel:`Add a line` to add an attribute in the :guilabel:`Attribute` column, like `Color` or `Size`, for example." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:30 +msgid "Once the attribute is chosen, select the desired values to apply to that attribute in the :guilabel:`Values` column. To select the desired values, click into the blank field beneath the :guilabel:`Values` column." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:34 +msgid "Then, select an option from the drop-down menu that appears. Or, create a new value by typing in the new value, and click :guilabel:`Create` from the drop-down menu that appears beneath the new value." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:37 +msgid "When a product has *at least* two variants (one attribute with two values), the :guilabel:`Sales Variant Selection` option appears at the bottom of the :guilabel:`Variants` tab. That is the **only** way to make that option appear, so keep that in mind." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:41 +msgid "Under :guilabel:`Sales Variant Selection`, choose either :guilabel:`Product Configurator` or :guilabel:`Order Grid Entry`. This selection determines which method is used to add the product to quotations or sales orders." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:45 +msgid ":guilabel:`Product Configurator`: choose attribute values to add the matching product variant to the order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:47 +msgid ":guilabel:`Order Grid Entry`: add several variants at once from the grid of attribute values." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:49 +msgid "Once a selection is made, click :guilabel:`Save` on the product form to apply the setting." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 msgid "Sales variant selection." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:32 -msgid "The product must have at least two variants (one attribute with two values) created in order for the :guilabel:`Sales Variant Selection` option to appear. Click :guilabel:`Add a line` under :guilabel:`Attribute` to add attributes and values to this product and create product variants." +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:56 +msgid "Product configurator" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:37 -msgid "Use the Product Configurator" +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:58 +msgid "The *product configurator* appears on a quotation or sales order when products that have **both** variants configured are added, and the :guilabel:`Product Configurator` option is selected on the product form." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:39 -msgid "The :guilabel:`Product Configurator` appears on a quotation or sales order when products are added that have both variants configured and the :guilabel:`Product Configurator` option selected." +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:62 +msgid "The product configurator lets salespeople choose exactly which product variant to add to the quotation or sales order, using a format similar to online shopping. Color options display any HTML color codes set up in the :guilabel:`Color` attribute." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:42 -msgid "The :guilabel:`Product Configurator` lets salespeople choose exactly which product variant to add to the quotation or sales order using a format similar to online shopping. Color options display any HTML color codes set up in the :guilabel:`Color` attribute. Features with an additional cost will display the additional cost next to their name. Once the desired product variant attributes are selected, click :guilabel:`Add` to add the product variant to the quotation or sales order." +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:66 +msgid "Features with an additional cost display the additional cost next to their name. Once the desired product variant attributes are selected, click :guilabel:`Add` to add the product variant to the quotation or sales order." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 msgid "Product Configurator and Price Extras." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:52 -msgid "By default, the product variant attributes are displayed on the quotation or sales order in the :guilabel:`Description` column, but the :guilabel:`Product Variant` column can be added through the additional options menu (3 vertical dots icon)." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:57 -msgid "Use Variant Grid Entries" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:59 -msgid ":guilabel:`Variant Grid Entries` appear on a quotation or sales order when products are added that have both variants configured and the :guilabel:`Order Grid Entry` option selected. Grid entry can streamline the process of creating large, varied quotations by letting salespeople enter exact quantities of each product variant all at once." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:64 -msgid ":guilabel:`Variant Grid Entry` displays a grid of every variant available for the selected product. Choose the exact quantities of each product variant for a quotation or sales order by typing in the number or using the arrows. :guilabel:`Not Available` is displayed when a particular variant has been deactivated in the database. Once all the product variants and their quantities have been set, click :guilabel:`Confirm` to add them to the quotation or sales order." +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:74 +msgid "By default, the product variant attributes are displayed on the quotation or sales order in the :guilabel:`Description` column, but a dedicated :guilabel:`Product Variant` column can be added, via the additional options menu (represented by the :guilabel:`⋮ (3 vertical dots)` icon, on the far-right side of the columns, in the :guilabel:`Order Lines` tab)." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 -msgid "Variant Grid Entry pop-up." +msgid "Product variant column option in order lines tab of quotation." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:74 -msgid "Each product variant appears as an individual line item on the quotation or sales order, because each of these items has its own stock." +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:83 +msgid "Just click the checkbox next to :guilabel:`Product Variant`, and that column appears in the :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:87 +msgid "Variant grid entries" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:89 +msgid "*Variant grid entries* appear on a quotation or sales order when products that have both variants configured are added, and the :guilabel:`Order Grid Entry` option is selected on the product form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:92 +msgid "The grid entry feature streamlines the process of creating large, varied quotations by letting salespeople enter exact quantities of each product variant all at once." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:95 +msgid "The :guilabel:`Choose Product Variants` pop-up form that appears, displays a grid of every variant available for that specific product." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:98 +msgid "From the :guilabel:`Choose Product Variants` pop-up form, choose the exact quantities of each product variant for a quotation or sales order by typing in the number or using the arrows in each column. The :guilabel:`Not Available` warning is displayed when a particular variant has been deactivated in the database." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:103 +msgid "Once all the product variants and their quantities have been set in the pop-up form, click :guilabel:`Confirm` to add them to the quotation or sales order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 +msgid "Variant Grid Entry pop-up form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:110 +msgid "Each product variant appears as an individual line item on the quotation or sales order with the chosen quantity from the :guilabel:`Choose Product Variants` pop-up form, because each of these items has its own stock." msgstr "" #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:-1 diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index e8a86dbfa..47d76accb 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-15.2\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-26 13:30+0000\n" +"POT-Creation-Date: 2023-12-19 07:46+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1583,6 +1583,162 @@ msgstr "" msgid "**As a non-Odoo Online user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a 50 Unsplash requests per hour restriction." msgstr "" +#: ../../content/applications/websites/website/mail_groups.rst:3 +msgid "Mail groups" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:5 +msgid "The **mail groups** feature allows website visitors to have a public discussion by email. They can join a group to receive emails from other group members (i.e., website users who have subscribed to the group) and send new ones to all group members." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:9 +msgid "To activate the feature, :ref:`install ` the :guilabel:`Website Mail Group` (`website_mail_group`) module." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:13 +msgid "The **mail groups** feature is not to be confused with the :doc:`../../marketing/email_marketing/mailing_lists` in the Email Marketing app." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:19 +msgid "Configuring mail groups" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:21 +msgid "To configure mail groups, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:23 +msgid "Configure a custom email alias domain by accessing the **General settings**, scrolling down to the :guilabel:`Discuss` section, enabling the :guilabel:`Custom Email Server` feature, and entering the :guilabel:`Alias domain` (e.g., `@mycompany.com`)." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:26 +msgid "Go to :menuselection:`Website --> Groups --> Mailing List Groups`, then click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:27 +msgid "Specify a :guilabel:`Group Name`, the :guilabel:`Email Alias`, and a :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:28 +msgid "Enable :guilabel:`Moderate this group` and specify the :guilabel:`Moderators` if you wish to :ref:`moderate messages ` from this group. Alternatively, if the group is not moderated, you can define :guilabel:`Responsible users` who can manage the messages in the group." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:32 +msgid "In the :guilabel:`Privacy` tab, define who can subscribe to the mail group:" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:34 +msgid ":guilabel:`Everyone`: to make the mail group public so anyone can subscribe to it;" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:35 +msgid ":guilabel:`Members only`: to only allow users defined as members to subscribe to the mail group;" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:36 +msgid ":guilabel:`Selected group of users`: to only allow users from the :guilabel:`Authorized group` to subscribe to the mail group." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:39 +msgid "If the mail group is moderated, you can automatically notify authors when their message is pending moderation by enabling :guilabel:`Automatic notification` in the :guilabel:`Notify Members` tab and writing the :guilabel:`Notification message`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:42 +msgid "If you wish to send out guidelines to new subscribers, enable :guilabel:`Send guidelines to new subscribers` and write them in the :guilabel:`Guidelines` tab. This is particularly useful when the mail group is moderated." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:47 +msgid "Using mail groups" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:50 +msgid "Subscribing/unsubscribing" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:52 +msgid "Based on the :ref:`configuration of the mail group `, users can subscribe to and unsubscribe from mail groups from the website page (`/groups` by default)." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:-1 +msgid "Mail group web page." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:58 +msgid "Internal users can also do this from :menuselection:`Website --> Groups --> Mailing List Groups`, using the :guilabel:`Join` and :guilabel:`Leave` buttons." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:62 +msgid "Sending messages" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:64 +msgid "To send messages to a mail group, website users can email the :ref:`mail group's email address `. Internal users can also create messages directly from Odoo. To do so, go to :menuselection:`Website --> Groups --> Mailing List Groups`, select the mail group, click the :guilabel:`Emails` smart button, and click :guilabel:`Create`. Then, fill in the fields and click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:71 +msgid "The list of messages can also be accessed by selecting the group from the `/groups` website page." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:73 +msgid "Group members can also unsubscribe from the group, access the mail group page, and send emails to the group using the URLs in the footer of any group email they have received." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:0 +msgid "URLs in the footer of a group email." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:82 +msgid "Moderating mail group messages" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:84 +msgid "If the :guilabel:`Moderate this group` feature has been enabled for the :ref:`mail group `, one of the :guilabel:`Moderators` must approve the group's messages before they are dispatched to the other members." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:88 +msgid "To moderate messages, go to :menuselection:`Website --> Groups --> Mailing List Groups`, select the mail group, and click the :guilabel:`To review` smart button. You can moderate messages using the buttons at the end of the message line or select a message to view its content and moderate it accordingly." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:0 +msgid "Moderation buttons in the message line." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:96 +msgid "The following actions are available:" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:98 +msgid ":guilabel:`Accept`: to accept the email and send it to the mail group members." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:99 +msgid ":guilabel:`Reject`: to reject the email. In the pop-up window that opens, click :guilabel:`Reject Silently` to reject the email without notifying the author, or specify an explanation for rejecting the message, then click :guilabel:`Send & Reject` to reject the message and send the explanation to the author." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:103 +msgid ":guilabel:`Whitelist`: to whitelist the author, i.e. automatically accept all of their emails. As a result, a :ref:`moderation rule ` is created for the author's email address with the status :guilabel:`Always allow`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:106 +msgid ":guilabel:`Ban`: to blacklist the author, i.e. automatically discard all their emails. In the pop-up window that opens, click :guilabel:`Ban` to ban the author without notifying them, or specify an explanation, then click :guilabel:`Send & Ban` to ban the author and send them the explanation. As a result, a :ref:`moderation rule ` is created for the author's email address with the status :guilabel:`Permanent ban`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:113 +msgid "Messages can also be moderated from the group's list of messages. Go to :menuselection:`Website --> Groups --> Mailing List Groups`, select the mail group and click the :guilabel:`Emails` smart button." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:120 +msgid "Whitelisting/Blacklisting authors" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:122 +msgid "You can whitelist or blacklist an author either directly :ref:`from a mail group message `, or by creating a moderation rule. To do so, go to :menuselection:`Website --> Groups --> List Moderation Rulings` and click :guilabel:`Create`. Then, select the :guilabel:`Group`, specify the author's :guilabel:`Email` and set the :guilabel:`Status` field." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:129 +msgid "You can also access the mail group's moderation rules by going to :menuselection:`Website --> Groups --> Mailing List Groups`, selecting the group, then clicking the :guilabel:`Moderations` smart button." +msgstr "" + #: ../../content/applications/websites/website/pages.rst:5 msgid "Pages" msgstr ""