From f3c3505a79713947d9a20879c53fb98967d42e1e Mon Sep 17 00:00:00 2001 From: "Tiffany Chang (tic)" Date: Wed, 21 Aug 2024 11:48:12 +0000 Subject: [PATCH] [I18N] *: export latest terms As per usual, leave off developer.pot and contributing.pot since we don't translate them (not useful, can't really contribute to/dev in Odoo without knowing English) closes odoo/documentation#10826 X-original-commit: a64a614c7a6f771868d3a35532483050ee7cdd5f Signed-off-by: Tiffany Chang (tic) --- locale/sources/administration.pot | 205 +- locale/sources/essentials.pot | 404 +- locale/sources/finance.pot | 4170 ++++---- locale/sources/general.pot | 2193 ++-- locale/sources/hr.pot | 1717 +++- locale/sources/inventory_and_mrp.pot | 13254 ++++++++++++++----------- locale/sources/marketing.pot | 2989 +++--- locale/sources/productivity.pot | 3401 ++++++- locale/sources/sales.pot | 1911 +++- locale/sources/services.pot | 449 +- locale/sources/studio.pot | 303 +- locale/sources/websites.pot | 404 +- 12 files changed, 19379 insertions(+), 12021 deletions(-) diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 40ccb406e..0d286b4cd 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 13:30+0000\n" +"POT-Creation-Date: 2024-08-21 11:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -971,6 +971,26 @@ msgstr "" msgid "Your scheduled actions should be `idempotent `_: they must not cause side-effects if they are started more often than expected." msgstr "" +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:36 +msgid "How can I automate tasks when an IP address change occurs?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:38 +msgid "**Odoo.sh notifies project administrators of IP address changes.** Additionally, when the IP address of a production instance changes, an HTTP `GET` request is made to the path `/_odoo.sh/ip-change` with the new IP address included as a query string parameter (`new`), along with the previous IP address as an additional parameter (`old`)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:43 +msgid "This mechanism allows custom actions to be applied in response to the IP address change (e.g., sending an email, contacting a firewall API, configuring database objects, etc.)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:46 +msgid "For security reasons, the `/_odoo.sh/ip-change` route is accessible only internally by the platform itself and returns a `403` response if accessed through any other means." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:49 +msgid "Here is a pseudo-implementation example:" +msgstr "" + #: ../../content/administration/odoo_sh/advanced/submodules.rst:6 #: ../../content/administration/odoo_sh/getting_started/settings.rst:170 msgid "Submodules" @@ -1582,7 +1602,7 @@ msgid "**SPF and DKIM compliance**" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:403 -msgid "In case the domain of your users email addresses use SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize Odoo as a sending host in your domain name settings to increase the deliverability of your outgoing emails. The configuration steps are explained in the documentation about :ref:`SPF ` and :ref:`DKIM `." +msgid "In case the domain of your users email addresses use SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize Odoo as a sending host in your domain name settings to increase the deliverability of your outgoing emails. The configuration steps are explained in the documentation about :ref:`SPF ` and :ref:`DKIM `." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:410 @@ -2833,14 +2853,15 @@ msgstr "" #: ../../content/administration/supported_versions.rst:35 #: ../../content/administration/supported_versions.rst:41 #: ../../content/administration/supported_versions.rst:47 -#: ../../content/administration/supported_versions.rst:48 -#: ../../content/administration/supported_versions.rst:49 -#: ../../content/administration/supported_versions.rst:77 -#: ../../content/administration/supported_versions.rst:78 -#: ../../content/administration/supported_versions.rst:79 -#: ../../content/administration/supported_versions.rst:95 -#: ../../content/administration/supported_versions.rst:96 -#: ../../content/administration/supported_versions.rst:97 +#: ../../content/administration/supported_versions.rst:53 +#: ../../content/administration/supported_versions.rst:54 +#: ../../content/administration/supported_versions.rst:55 +#: ../../content/administration/supported_versions.rst:59 +#: ../../content/administration/supported_versions.rst:60 +#: ../../content/administration/supported_versions.rst:61 +#: ../../content/administration/supported_versions.rst:65 +#: ../../content/administration/supported_versions.rst:66 +#: ../../content/administration/supported_versions.rst:67 msgid "|green|" msgstr "" @@ -4120,7 +4141,7 @@ msgid "In you alias config (:file:`/etc/aliases`):" msgstr "" #: ../../content/administration/on_premise/email_gateway.rst:30 -#: ../../content/administration/on_premise/email_gateway.rst:45 +#: ../../content/administration/on_premise/email_gateway.rst:44 msgid "Resources" msgstr "" @@ -4136,16 +4157,16 @@ msgstr "" msgid "`Postfix virtual `_" msgstr "" -#: ../../content/administration/on_premise/email_gateway.rst:38 +#: ../../content/administration/on_premise/email_gateway.rst:37 msgid "For Exim" msgstr "" -#: ../../content/administration/on_premise/email_gateway.rst:47 +#: ../../content/administration/on_premise/email_gateway.rst:46 msgid "`Exim `_" msgstr "" -#: ../../content/administration/on_premise/email_gateway.rst:50 -msgid "If you don't have access/manage your email server, use :ref:`inbound messages `." +#: ../../content/administration/on_premise/email_gateway.rst:49 +msgid "If you do not have access/manage your email server, use :ref:`incoming mail servers `." msgstr "" #: ../../content/administration/on_premise/geo_ip.rst:3 @@ -4904,197 +4925,133 @@ msgid "End of support" msgstr "" #: ../../content/administration/supported_versions.rst:34 -msgid "Odoo saas~17.2" +msgid "Odoo saas~17.4" msgstr "" #: ../../content/administration/supported_versions.rst:36 #: ../../content/administration/supported_versions.rst:37 #: ../../content/administration/supported_versions.rst:42 #: ../../content/administration/supported_versions.rst:43 -#: ../../content/administration/supported_versions.rst:54 -#: ../../content/administration/supported_versions.rst:55 -#: ../../content/administration/supported_versions.rst:60 -#: ../../content/administration/supported_versions.rst:61 -#: ../../content/administration/supported_versions.rst:66 -#: ../../content/administration/supported_versions.rst:67 -#: ../../content/administration/supported_versions.rst:72 -#: ../../content/administration/supported_versions.rst:73 -#: ../../content/administration/supported_versions.rst:84 -#: ../../content/administration/supported_versions.rst:85 -#: ../../content/administration/supported_versions.rst:90 -#: ../../content/administration/supported_versions.rst:91 +#: ../../content/administration/supported_versions.rst:48 +#: ../../content/administration/supported_versions.rst:49 msgid "N/A" msgstr "" #: ../../content/administration/supported_versions.rst:38 -msgid "April 2024" +msgid "July 2024" msgstr "" #: ../../content/administration/supported_versions.rst:40 -msgid "Odoo saas~17.1" +msgid "Odoo saas~17.2" msgstr "" #: ../../content/administration/supported_versions.rst:44 -msgid "January 2024" +msgid "April 2024" msgstr "" #: ../../content/administration/supported_versions.rst:46 -msgid "**Odoo 17.0**" +msgid "Odoo saas~17.1" msgstr "" #: ../../content/administration/supported_versions.rst:50 -#: ../../content/administration/supported_versions.rst:105 -msgid "November 2023" -msgstr "" - -#: ../../content/administration/supported_versions.rst:51 -msgid "October 2026 (planned)" +msgid "January 2024" msgstr "" #: ../../content/administration/supported_versions.rst:52 -msgid "Odoo saas~16.4" -msgstr "" - -#: ../../content/administration/supported_versions.rst:53 -#: ../../content/administration/supported_versions.rst:59 -#: ../../content/administration/supported_versions.rst:65 -#: ../../content/administration/supported_versions.rst:71 -#: ../../content/administration/supported_versions.rst:83 -#: ../../content/administration/supported_versions.rst:89 -#: ../../content/administration/supported_versions.rst:101 -#: ../../content/administration/supported_versions.rst:102 -#: ../../content/administration/supported_versions.rst:103 -#: ../../content/administration/supported_versions.rst:107 -#: ../../content/administration/supported_versions.rst:108 -#: ../../content/administration/supported_versions.rst:109 -#: ../../content/administration/supported_versions.rst:113 -#: ../../content/administration/supported_versions.rst:114 -#: ../../content/administration/supported_versions.rst:115 -msgid "|red|" +msgid "**Odoo 17.0**" msgstr "" #: ../../content/administration/supported_versions.rst:56 -msgid "August 2023" +#: ../../content/administration/supported_versions.rst:75 +msgid "November 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:57 +msgid "October 2026 (planned)" msgstr "" #: ../../content/administration/supported_versions.rst:58 -msgid "Odoo saas~16.3" -msgstr "" - -#: ../../content/administration/supported_versions.rst:62 -msgid "June 2023" -msgstr "" - -#: ../../content/administration/supported_versions.rst:64 -msgid "Odoo saas~16.2" -msgstr "" - -#: ../../content/administration/supported_versions.rst:68 -msgid "March 2023" -msgstr "" - -#: ../../content/administration/supported_versions.rst:70 -msgid "Odoo saas~16.1" -msgstr "" - -#: ../../content/administration/supported_versions.rst:74 -msgid "February 2023" -msgstr "" - -#: ../../content/administration/supported_versions.rst:76 msgid "**Odoo 16.0**" msgstr "" -#: ../../content/administration/supported_versions.rst:80 -#: ../../content/administration/supported_versions.rst:111 +#: ../../content/administration/supported_versions.rst:62 +#: ../../content/administration/supported_versions.rst:81 msgid "October 2022" msgstr "" -#: ../../content/administration/supported_versions.rst:81 +#: ../../content/administration/supported_versions.rst:63 msgid "November 2025 (planned)" msgstr "" -#: ../../content/administration/supported_versions.rst:82 -msgid "Odoo saas~15.2" -msgstr "" - -#: ../../content/administration/supported_versions.rst:86 -msgid "March 2022" -msgstr "" - -#: ../../content/administration/supported_versions.rst:87 -msgid "January 2023" -msgstr "" - -#: ../../content/administration/supported_versions.rst:88 -msgid "Odoo saas~15.1" -msgstr "" - -#: ../../content/administration/supported_versions.rst:92 -msgid "February 2022" -msgstr "" - -#: ../../content/administration/supported_versions.rst:93 -msgid "July 2022" -msgstr "" - -#: ../../content/administration/supported_versions.rst:94 +#: ../../content/administration/supported_versions.rst:64 msgid "**Odoo 15.0**" msgstr "" -#: ../../content/administration/supported_versions.rst:98 +#: ../../content/administration/supported_versions.rst:68 msgid "October 2021" msgstr "" -#: ../../content/administration/supported_versions.rst:99 +#: ../../content/administration/supported_versions.rst:69 msgid "November 2024 (planned)" msgstr "" -#: ../../content/administration/supported_versions.rst:100 +#: ../../content/administration/supported_versions.rst:70 msgid "**Odoo 14.0**" msgstr "" -#: ../../content/administration/supported_versions.rst:104 +#: ../../content/administration/supported_versions.rst:71 +#: ../../content/administration/supported_versions.rst:72 +#: ../../content/administration/supported_versions.rst:73 +#: ../../content/administration/supported_versions.rst:77 +#: ../../content/administration/supported_versions.rst:78 +#: ../../content/administration/supported_versions.rst:79 +#: ../../content/administration/supported_versions.rst:83 +#: ../../content/administration/supported_versions.rst:84 +#: ../../content/administration/supported_versions.rst:85 +msgid "|red|" +msgstr "" + +#: ../../content/administration/supported_versions.rst:74 msgid "October 2020" msgstr "" -#: ../../content/administration/supported_versions.rst:106 +#: ../../content/administration/supported_versions.rst:76 msgid "**Odoo 13.0**" msgstr "" -#: ../../content/administration/supported_versions.rst:110 +#: ../../content/administration/supported_versions.rst:80 msgid "October 2019" msgstr "" -#: ../../content/administration/supported_versions.rst:112 +#: ../../content/administration/supported_versions.rst:82 msgid "Older versions" msgstr "" -#: ../../content/administration/supported_versions.rst:116 +#: ../../content/administration/supported_versions.rst:86 msgid "Before 2019" msgstr "" -#: ../../content/administration/supported_versions.rst:117 +#: ../../content/administration/supported_versions.rst:87 msgid "Before 2022" msgstr "" -#: ../../content/administration/supported_versions.rst:119 +#: ../../content/administration/supported_versions.rst:89 msgid "Legend" msgstr "" -#: ../../content/administration/supported_versions.rst:121 +#: ../../content/administration/supported_versions.rst:91 msgid "|green| Supported version" msgstr "" -#: ../../content/administration/supported_versions.rst:123 +#: ../../content/administration/supported_versions.rst:93 msgid "|red| End-of-support" msgstr "" -#: ../../content/administration/supported_versions.rst:125 +#: ../../content/administration/supported_versions.rst:95 msgid "N/A Never released for this platform" msgstr "" -#: ../../content/administration/supported_versions.rst:128 +#: ../../content/administration/supported_versions.rst:98 msgid "Even though we don't support older versions, you can always `upgrade from any version `_." msgstr "" diff --git a/locale/sources/essentials.pot b/locale/sources/essentials.pot index 90857fb57..430e91797 100644 --- a/locale/sources/essentials.pot +++ b/locale/sources/essentials.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 13:30+0000\n" +"POT-Creation-Date: 2024-08-21 11:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -903,31 +903,31 @@ msgstr "" msgid "Export and import data" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:5 +#: ../../content/applications/essentials/export_import_data.rst:8 msgid "In Odoo, it is sometimes necessary to export or import data for running reports, or for data modification. This document covers the export and import of data into and out of Odoo." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:9 +#: ../../content/applications/essentials/export_import_data.rst:12 msgid "Sometimes, users run into a 'time out' error, or a record does not process, due to its size. This can occur with large exports, or in cases where the import file is too large. To circumvent this limitation surrounding the size of the records, process exports or imports in smaller batches." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:16 +#: ../../content/applications/essentials/export_import_data.rst:19 msgid "Export data from Odoo" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:18 +#: ../../content/applications/essentials/export_import_data.rst:21 msgid "When working with a database, it is sometimes necessary to export data in a distinct file. Doing so can aid in reporting on activities, although, Odoo provides a precise and easy reporting tool with each available application." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:22 -msgid "With Odoo, the values can be exported from any field in any record. To do so, activate the list view (:guilabel:`≣ (four horizontal lines)` icon), on the items that need to be exported, and then select the records that should be exported. To select a record, tick the checkbox next to the corresponding record. Finally, click on :guilabel:`⚙️ Action`, and then :guilabel:`Export`." +#: ../../content/applications/essentials/export_import_data.rst:25 +msgid "With Odoo, the values can be exported from any field in any record. To do so, activate the list view (|list|), on the items that need to be exported, then select the records that should be exported. To select a record, tick the checkbox next to the corresponding record. Finally, click on |actions|, then :guilabel:`Export`." msgstr "" #: ../../content/applications/essentials/export_import_data.rst:-1 msgid "View of the different things to enable/click to export data." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:31 +#: ../../content/applications/essentials/export_import_data.rst:34 msgid "When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over window appears, with several options for the data to export:" msgstr "" @@ -935,51 +935,51 @@ msgstr "" msgid "Overview of options to consider when exporting data in Odoo.." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:38 -msgid "With the :guilabel:`I want to update data (import-compatable export)` option ticked, the system only shows the fields that can be imported. This is helpful in the case where the existing records need to be updated. This works like a filter. Leaving the box unticked, gives many more field options because it shows all the fields, not just the ones that can be imported." +#: ../../content/applications/essentials/export_import_data.rst:41 +msgid "With the :guilabel:`I want to update data (import-compatable export)` option ticked, the system only shows the fields that can be imported. This is helpful in the case where the :ref:`existing records need to be updated `. This works like a filter. Leaving the box unticked, gives many more field options because it shows all the fields, not just the ones that can be imported." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:42 +#: ../../content/applications/essentials/export_import_data.rst:46 msgid "When exporting, there is the option to export in two formats: `.csv` and `.xls`. With `.csv`, items are separated by a comma, while `.xls` holds information about all the worksheets in a file, including both content and formatting." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:45 +#: ../../content/applications/essentials/export_import_data.rst:49 msgid "These are the items that can be exported. Use the :guilabel:`> (right arrow)` icon to display more sub-field options. Use the :guilabel:`Search` bar to find specific fields. To use the :guilabel:`Search` option more efficiently, click on all the :guilabel:`> (right arrows)` to display all fields." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:49 +#: ../../content/applications/essentials/export_import_data.rst:53 msgid "The :guilabel:`+ (plus sign)` icon button is present to add fields to the :guilabel:`Fields to export` list." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:51 +#: ../../content/applications/essentials/export_import_data.rst:55 msgid "The :guilabel:`↕️ (up-down arrow)` to the left of the selected fields can be used to move the fields up and down, to change the order in which they are displayed in the exported file. Drag-and-drop using the :guilabel:`↕️ (up-down arrow)` icon." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:54 +#: ../../content/applications/essentials/export_import_data.rst:58 msgid "The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click on the :guilabel:`🗑️ (trash can)` icon to remove the field." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:56 +#: ../../content/applications/essentials/export_import_data.rst:60 msgid "For recurring reports, it is helpful to save export presets. Select all the needed fields, and click on the template drop-down menu. Once there, click on :guilabel:`New template`, and give a unique name to the export just created. Click the :guilabel:`💾 (floppy drive)` icon to save the configuration. The next time the same list needs to be exported, select the related template that was previously saved from the drop-down menu." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:63 +#: ../../content/applications/essentials/export_import_data.rst:67 msgid "It is helpful to know the field's external identifier. For example, :guilabel:`Related Company` in the export user interface is equal to *parent_id* (external identifier). This is helpful because then, the only data exported is what should be modified and re-imported." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:70 +#: ../../content/applications/essentials/export_import_data.rst:74 msgid "Import data into Odoo" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:72 -msgid "Importing data into Odoo is extremely helpful during implementation, or in times where data needs to be updated in bulk. The following documentation covers how to import data into an Odoo database." +#: ../../content/applications/essentials/export_import_data.rst:76 +msgid "Importing data into Odoo is extremely helpful during implementation, or in times where data needs to be :ref:`updated in bulk `. The following documentation covers how to import data into an Odoo database." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:76 +#: ../../content/applications/essentials/export_import_data.rst:81 msgid "Imports are permanent and **cannot** be undone. However, it is possible to use filters (`created on` or `last modified`) to identify records changed or created by the import." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:80 +#: ../../content/applications/essentials/export_import_data.rst:85 msgid "Activating :ref:`developer mode ` changes the visible import settings in the left menu. Doing so reveals an :menuselection:`Advanced` menu. Included in this advanced menu are two options: :guilabel:`Track history during import` and :guilabel:`Allow matching with subfields`." msgstr "" @@ -987,23 +987,23 @@ msgstr "" msgid "Advanced import options when developer mode is activated." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:88 +#: ../../content/applications/essentials/export_import_data.rst:93 msgid "If the model uses openchatter, the :guilabel:`Track history during import` option sets up subscriptions and sends notifications during the import, but leads to a slower import." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:91 +#: ../../content/applications/essentials/export_import_data.rst:96 msgid "Should the :guilabel:`Allow matching with subfields` option be selected, then all subfields within a field are used to match under the :guilabel:`Odoo Field` while importing." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:95 +#: ../../content/applications/essentials/export_import_data.rst:100 msgid "Get started" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:97 +#: ../../content/applications/essentials/export_import_data.rst:102 msgid "Data can be imported on any Odoo business object using either Excel (`.xlsx`) or :abbr:`CSV (Comma-separated Values)` (`.csv`) formats. This includes: contacts, products, bank statements, journal entries, and orders." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:101 +#: ../../content/applications/essentials/export_import_data.rst:106 msgid "Open the view of the object to which the data should be imported/populated, and click on :menuselection:`⚙️ (Action) --> Import records`." msgstr "" @@ -1011,11 +1011,11 @@ msgstr "" msgid "Action menu revealed with the import records option highlighted." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:108 +#: ../../content/applications/essentials/export_import_data.rst:113 msgid "After clicking :guilabel:`Import records`, Odoo reveals a separate page with templates that can be downloaded and populated with the company's own data. Such templates can be imported in one click, since the data mapping is already done. To download a template click :guilabel:`Import Template for Customers` at the center of the page." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:114 +#: ../../content/applications/essentials/export_import_data.rst:119 msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting` options. These options do **not** appear when importing the proprietary Excel file type (`.xls`, `.xlsx`)." msgstr "" @@ -1023,31 +1023,31 @@ msgstr "" msgid "Formatting options presented when a CVS file is imported in Odoo." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:122 +#: ../../content/applications/essentials/export_import_data.rst:127 msgid "Make necessary adjustments to the *Formatting* options, and ensure all columns in the :guilabel:`Odoo field` and :guilabel:`File Column` are free of errors. Finally, click :guilabel:`Import` to import the data." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:127 +#: ../../content/applications/essentials/export_import_data.rst:132 msgid "Adapt a template" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:129 +#: ../../content/applications/essentials/export_import_data.rst:134 msgid "Import templates are provided in the import tool of the most common data to import (contacts, products, bank statements, etc.). Open them with any spreadsheet software (*Microsoft Office*, *OpenOffice*, *Google Drive*, etc.)." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:133 +#: ../../content/applications/essentials/export_import_data.rst:138 msgid "Once the template is downloaded, proceed to follow these steps:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:135 +#: ../../content/applications/essentials/export_import_data.rst:140 msgid "Add, remove, and sort columns to best fit the data structure." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:136 +#: ../../content/applications/essentials/export_import_data.rst:141 msgid "It is strongly advised to **not** remove the :guilabel:`External ID` (ID) column (see why in the next section)." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:138 +#: ../../content/applications/essentials/export_import_data.rst:143 msgid "Set a unique ID to every record by dragging down the ID sequencing in the :guilabel:`External ID` (ID) column." msgstr "" @@ -1055,7 +1055,7 @@ msgstr "" msgid "An animation of the mouse dragging down the ID column, so each record has a unique ID." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:146 +#: ../../content/applications/essentials/export_import_data.rst:151 msgid "When a new column is added, Odoo may not be able to map it automatically, if its label does not fit any field within Odoo. However, new columns can be mapped manually when the import is tested. Search the drop-down menu for the corresponding field." msgstr "" @@ -1063,67 +1063,63 @@ msgstr "" msgid "Drop-down menu expanded in the initial import screen on Odoo." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:154 +#: ../../content/applications/essentials/export_import_data.rst:159 msgid "Then, use this field's label in the import file to ensure future imports are successful." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:157 +#: ../../content/applications/essentials/export_import_data.rst:162 msgid "Another useful way to find out the proper column names to import is to export a sample file using the fields that should be imported. This way, if there is not a sample import template, the names are accurate." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:162 +#: ../../content/applications/essentials/export_import_data.rst:170 msgid "Import from another application" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:164 +#: ../../content/applications/essentials/export_import_data.rst:172 msgid "The :guilabel:`External ID` (ID) is a unique identifier for the line item. Feel free to use one from previous software to facilitate the transition to Odoo." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:167 +#: ../../content/applications/essentials/export_import_data.rst:175 msgid "Setting an ID is not mandatory when importing, but it helps in many cases:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:169 -msgid "Update imports: import the same file several times without creating duplicates." -msgstr "" - -#: ../../content/applications/essentials/export_import_data.rst:170 -msgid ":ref:`Import relation fields `." -msgstr "" - -#: ../../content/applications/essentials/export_import_data.rst:172 -msgid "To recreate relationships between different records, the unique identifier from the original application should be used to map it to the :guilabel:`External ID` (ID) column in Odoo." -msgstr "" - -#: ../../content/applications/essentials/export_import_data.rst:175 -msgid "When another record is imported that links to the first one, use **XXX/ID** (XXX/External ID) for the original unique identifier. This record can also be found using its name." +#: ../../content/applications/essentials/export_import_data.rst:177 +msgid ":ref:`Update imports `: import the same file several times without creating duplicates." msgstr "" #: ../../content/applications/essentials/export_import_data.rst:179 -msgid "It should be noted that there will be a conflict if two or more records have the same name." +msgid ":ref:`Import relation fields `." msgstr "" #: ../../content/applications/essentials/export_import_data.rst:181 -msgid "The :guilabel:`External ID` (ID) can also be used to update the original import, if modified data needs to be re-imported later, therefore, it is a good practice to specify it whenever possible." +msgid "To recreate relationships between different records, the unique identifier from the original application should be used to map it to the :guilabel:`External ID` (ID) column in Odoo." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:185 +#: ../../content/applications/essentials/export_import_data.rst:184 +msgid "When another record is imported that links to the first one, use **XXX/ID** (XXX/External ID) for the original unique identifier. This record can also be found using its name." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:188 +msgid "It should be noted that conflicts occur if two (or more) records have the same *External ID*." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:191 msgid "Field missing to map column" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:187 +#: ../../content/applications/essentials/export_import_data.rst:193 msgid "Odoo heuristically tries to find the type of field for each column inside the imported file, based on the first ten lines of the files." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:190 +#: ../../content/applications/essentials/export_import_data.rst:196 msgid "For example, if there is a column only containing numbers, only the fields with the *integer* type are presented as options." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:193 +#: ../../content/applications/essentials/export_import_data.rst:199 msgid "While this behavior might be beneficial in most cases, it is also possible that it could fail, or the column may be mapped to a field that is not proposed by default." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:196 +#: ../../content/applications/essentials/export_import_data.rst:202 msgid "If this happens, check the :guilabel:`Show fields of relation fields (advanced) option`, then a complete list of fields becomes available for each column." msgstr "" @@ -1131,322 +1127,362 @@ msgstr "" msgid "Searching for the field to match the tax column." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:204 +#: ../../content/applications/essentials/export_import_data.rst:210 msgid "Change data import format" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:207 +#: ../../content/applications/essentials/export_import_data.rst:213 msgid "Odoo can automatically detect if a column is a date, and tries to guess the date format from a set of most commonly used date formats. While this process can work for many date formats, some date formats are not recognizable. This can cause confusion, due to day-month inversions; it is difficult to guess which part of a date format is the day, and which part is the month, in a date, such as `01-03-2016`." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:213 +#: ../../content/applications/essentials/export_import_data.rst:219 msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting` options." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:216 +#: ../../content/applications/essentials/export_import_data.rst:222 msgid "To view which date format Odoo has found from the file, check the :guilabel:`Date Format` that is shown when clicking on options under the file selector. If this format is incorrect, change it to the preferred format using *ISO 8601* to define the format." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:221 +#: ../../content/applications/essentials/export_import_data.rst:227 msgid "*ISO 8601* is an international standard, covering the worldwide exchange, along with the communication of date and time-related data. For example, the date format should be `YYYY-MM-DD`. So, in the case of July 24th 1981, it should be written as `1981-07-24`." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:226 +#: ../../content/applications/essentials/export_import_data.rst:232 msgid "When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to store dates. This maintains locale date formats for display, regardless of how the date is formatted in Odoo. When importing a :abbr:`CSV (Comma-separated Values)` file, use Odoo's :guilabel:`Formatting` section to select the date format columns to import." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:232 +#: ../../content/applications/essentials/export_import_data.rst:238 msgid "Import numbers with currency signs" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:234 +#: ../../content/applications/essentials/export_import_data.rst:240 msgid "Odoo fully supports numbers with parenthesis to represent negative signs, as well as numbers with currency signs attached to them. Odoo also automatically detects which thousand/decimal separator is used. If a currency symbol unknown to Odoo is used, it might not be recognized as a number, and the import crashes." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:240 +#: ../../content/applications/essentials/export_import_data.rst:246 msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, the :guilabel:`Formatting` menu appears on the left-hand column. Under these options, the :guilabel:`Thousands Separator` can be changed." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:244 +#: ../../content/applications/essentials/export_import_data.rst:250 msgid "Examples of supported numbers (using 'thirty-two thousand' as the figure):" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:246 +#: ../../content/applications/essentials/export_import_data.rst:252 msgid "32.000,00" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:247 +#: ../../content/applications/essentials/export_import_data.rst:253 msgid "32000,00" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:248 +#: ../../content/applications/essentials/export_import_data.rst:254 msgid "32,000.00" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:249 +#: ../../content/applications/essentials/export_import_data.rst:255 msgid "-32000.00" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:250 +#: ../../content/applications/essentials/export_import_data.rst:256 msgid "(32000.00)" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:251 +#: ../../content/applications/essentials/export_import_data.rst:257 msgid "$ 32.000,00" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:252 +#: ../../content/applications/essentials/export_import_data.rst:258 msgid "(32000.00 €)" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:254 +#: ../../content/applications/essentials/export_import_data.rst:260 msgid "Example that will not work:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:256 +#: ../../content/applications/essentials/export_import_data.rst:262 msgid "ABC 32.000,00" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:257 +#: ../../content/applications/essentials/export_import_data.rst:263 msgid "$ (32.000,00)" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:260 +#: ../../content/applications/essentials/export_import_data.rst:266 msgid "A :guilabel:`() (parenthesis)` around the number indicates that the number is a negative value. The currency symbol **must** be placed within the parenthesis for Odoo to recognize it as a negative currency value." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:265 +#: ../../content/applications/essentials/export_import_data.rst:271 msgid "Import preview table not displayed correctly" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:267 +#: ../../content/applications/essentials/export_import_data.rst:273 msgid "By default, the import preview is set on commas as field separators, and quotation marks as text delimiters. If the :abbr:`CSV (Comma-separated Values)` file does not have these settings, modify the :guilabel:`Formatting` options (displayed under the :guilabel:`Import` :abbr:`CSV (Comma-separated Values)` file bar after selecting the :abbr:`CSV (Comma-separated Values)` file)." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:273 +#: ../../content/applications/essentials/export_import_data.rst:279 msgid "If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a separator, Odoo does **not** detect the separations. The file format options need to be modified in the spreadsheet application. See the following :ref:`Change CSV file format ` section." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:281 +#: ../../content/applications/essentials/export_import_data.rst:287 msgid "Change CSV file format in spreadsheet application" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:283 +#: ../../content/applications/essentials/export_import_data.rst:289 msgid "When editing and saving :abbr:`CSV (Comma-separated Values)` files in spreadsheet applications, the computer's regional settings are applied for the separator and delimiter. Odoo suggests using *OpenOffice* or *LibreOffice*, as both applications allow modifications of all three options (from *LibreOffice* application, go to :menuselection:`'Save As' dialog box --> Check the box 'Edit filter settings' --> Save`)." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:289 +#: ../../content/applications/essentials/export_import_data.rst:295 msgid "Microsoft Excel can modify the encoding when saving (:menuselection:`'Save As' dialog box --> 'Tools' drop-down menu --> Encoding tab`)." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:293 +#: ../../content/applications/essentials/export_import_data.rst:299 msgid "Difference between Database ID and External ID" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:295 +#: ../../content/applications/essentials/export_import_data.rst:301 msgid "Some fields define a relationship with another object. For example, the country of a contact is a link to a record of the 'Country' object. When such fields are imported, Odoo has to recreate links between the different records. To help import such fields, Odoo provides three mechanisms." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:300 +#: ../../content/applications/essentials/export_import_data.rst:306 msgid "**Only one** mechanism should be used per field that is imported." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:302 +#: ../../content/applications/essentials/export_import_data.rst:308 msgid "For example, to reference the country of a contact, Odoo proposes three different fields to import:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:304 +#: ../../content/applications/essentials/export_import_data.rst:310 msgid ":guilabel:`Country`: the name or code of the country" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:305 +#: ../../content/applications/essentials/export_import_data.rst:311 msgid ":guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by the ID PostgreSQL column" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:307 +#: ../../content/applications/essentials/export_import_data.rst:313 msgid ":guilabel:`Country/External ID`: the ID of this record referenced in another application (or the `.XML` file that imported it)" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:310 +#: ../../content/applications/essentials/export_import_data.rst:316 msgid "For the country of Belgium, for example, use one of these three ways to import:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:312 +#: ../../content/applications/essentials/export_import_data.rst:318 msgid ":guilabel:`Country`: `Belgium`" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:313 +#: ../../content/applications/essentials/export_import_data.rst:319 msgid ":guilabel:`Country/Database ID`: `21`" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:314 +#: ../../content/applications/essentials/export_import_data.rst:320 msgid ":guilabel:`Country/External ID`: `base.be`" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:316 +#: ../../content/applications/essentials/export_import_data.rst:322 msgid "According to the company's need, use one of these three ways to reference records in relations. Here is an example when one or the other should be used, according to the need:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:319 +#: ../../content/applications/essentials/export_import_data.rst:325 msgid "Use :guilabel:`Country`: this is the easiest way when data comes from :abbr:`CSV (Comma-separated Values)` files that have been created manually." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:321 +#: ../../content/applications/essentials/export_import_data.rst:327 msgid "Use :guilabel:`Country/Database ID`: this should rarely be used. It is mostly used by developers as the main advantage is to never have conflicts (there may be several records with the same name, but they always have a unique Database ID)" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:324 +#: ../../content/applications/essentials/export_import_data.rst:330 msgid "Use :guilabel:`Country/External ID`: use *External ID* when importing data from a third-party application." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:327 +#: ../../content/applications/essentials/export_import_data.rst:333 msgid "When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` files with the :guilabel:`External ID` (ID) column defining the *External ID* of each record that is imported. Then, a reference can be made to that record with columns, like `Field/External ID`. The following two :abbr:`CSV (Comma-separated Values)` files provide an example for products and their categories." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:332 +#: ../../content/applications/essentials/export_import_data.rst:338 msgid ":download:`CSV file for categories `" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:334 +#: ../../content/applications/essentials/export_import_data.rst:340 msgid ":download:`CSV file for Products `" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:340 +#: ../../content/applications/essentials/export_import_data.rst:346 msgid "Import relation fields" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:342 +#: ../../content/applications/essentials/export_import_data.rst:348 msgid "An Odoo object is always related to many other objects (e.g. a product is linked to product categories, attributes, vendors, etc.). To import those relations, the records of the related object need to be imported first, from their own list menu." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:346 +#: ../../content/applications/essentials/export_import_data.rst:352 msgid "This can be achieved by using either the name of the related record, or its ID, depending on the circumstances. The ID is expected when two records have the same name. In such a case add `/ ID` at the end of the column title (e.g. for product attributes: `Product Attributes / Attribute / ID`)." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:351 +#: ../../content/applications/essentials/export_import_data.rst:357 msgid "Options for multiple matches on fields" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:353 +#: ../../content/applications/essentials/export_import_data.rst:359 msgid "If, for example, there are two product categories with the child name `Sellable` (e.g. `Misc. Products/Sellable` & `Other Products/Sellable`), the validation is halted, but the data may still be imported. However, Odoo recommends that the data is not imported because it will all be linked to the first `Sellable` category found in the *Product Category* list (`Misc. Products/Sellable`). Odoo, instead, recommends modifying one of the duplicate's values, or the product category hierarchy." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:360 +#: ../../content/applications/essentials/export_import_data.rst:366 msgid "However, if the company does not wish to change the configuration of product categories, Odoo recommends making use of the *External ID* for this field, 'Category'." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:364 +#: ../../content/applications/essentials/export_import_data.rst:370 msgid "Import many2many relationship fields" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:366 +#: ../../content/applications/essentials/export_import_data.rst:372 msgid "The tags should be separated by a comma, without any spacing. For example, if a customer needs to be linked to both tags: `Manufacturer` and `Retailer` then 'Manufacturer,Retailer' needs to be encoded in the same column of the :abbr:`CSV (Comma-separated Values)` file." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:370 +#: ../../content/applications/essentials/export_import_data.rst:376 msgid ":download:`CSV file for Manufacturer, Retailer `" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:373 +#: ../../content/applications/essentials/export_import_data.rst:379 msgid "Import one2many relationships" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:375 +#: ../../content/applications/essentials/export_import_data.rst:381 msgid "If a company wants to import a sales order with several order lines, a specific row **must** be reserved in the :abbr:`CSV (Comma-separated Values)` file for each order line. The first order line is imported on the same row as the information relative to order. Any additional lines need an additional row that does not have any information in the fields relative to the order." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:380 +#: ../../content/applications/essentials/export_import_data.rst:386 msgid "As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some quotations that can be imported, based on demo data:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:383 +#: ../../content/applications/essentials/export_import_data.rst:389 msgid ":download:`File for some Quotations `" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:386 +#: ../../content/applications/essentials/export_import_data.rst:392 msgid "The following :abbr:`CSV (Comma-separated Values)` file shows how to import purchase orders with their respective purchase order lines:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:389 +#: ../../content/applications/essentials/export_import_data.rst:395 msgid ":download:`Purchase orders with their respective purchase order lines `" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:392 +#: ../../content/applications/essentials/export_import_data.rst:398 msgid "The following :abbr:`CSV (Comma-separated Values)` file shows how to import customers and their respective contacts:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:395 +#: ../../content/applications/essentials/export_import_data.rst:401 msgid ":download:`Customers and their respective contacts `" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:399 +#: ../../content/applications/essentials/export_import_data.rst:405 msgid "Import records several times" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:401 +#: ../../content/applications/essentials/export_import_data.rst:407 msgid "If an imported file contains one of the columns: :guilabel:`External ID` or :guilabel:`Database ID`, records that have already been imported are modified, instead of being created. This is extremely useful as it allows users to import the same :abbr:`CSV (Comma-separated Values)` file several times, while having made some changes in between two imports." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:406 +#: ../../content/applications/essentials/export_import_data.rst:412 msgid "Odoo takes care of creating or modifying each record, depending if it is new or not." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:408 +#: ../../content/applications/essentials/export_import_data.rst:414 msgid "This feature allows a company to use the *Import/Export tool* in Odoo to modify a batch of records in a spreadsheet application." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:412 +#: ../../content/applications/essentials/export_import_data.rst:418 msgid "Value not provided for a specific field" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:414 +#: ../../content/applications/essentials/export_import_data.rst:420 msgid "If all fields are not set in the CSV file, Odoo assigns the default value for every non-defined field. But, if fields are set with empty values in the :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the field, instead of assigning the default value." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:419 +#: ../../content/applications/essentials/export_import_data.rst:425 msgid "Export/import different tables from an SQL application to Odoo" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:421 +#: ../../content/applications/essentials/export_import_data.rst:427 msgid "If data needs to be imported from different tables, relations need to be recreated between records belonging to different tables. For instance, if companies and people are imported, the link between each person and the company they work for needs to be recreated." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:425 +#: ../../content/applications/essentials/export_import_data.rst:431 msgid "To manage relations between tables, use the `External ID` facilities of Odoo. The `External ID` of a record is the unique identifier of this record in another application. The `External ID` must be unique across all records of all objects. It is a good practice to prefix this `External ID` with the name of the application or table. (like, 'company_1', 'person_1' - instead of '1')" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:430 +#: ../../content/applications/essentials/export_import_data.rst:436 msgid "As an example, suppose there is an SQL database with two tables that are to be imported: companies and people. Each person belongs to one company, so the link between a person and the company they work for must be recreated." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:434 +#: ../../content/applications/essentials/export_import_data.rst:440 msgid "Test this example, with a :download:`sample of a PostgreSQL database `." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:437 +#: ../../content/applications/essentials/export_import_data.rst:443 msgid "First, export all companies and their *External ID*. In PSQL, write the following command:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:443 +#: ../../content/applications/essentials/export_import_data.rst:449 msgid "This SQL command creates the following :abbr:`CSV (Comma-separated Values)` file:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:452 +#: ../../content/applications/essentials/export_import_data.rst:458 msgid "To create the :abbr:`CSV (Comma-separated Values)` file for people linked to companies, use the following SQL command in PSQL:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:459 +#: ../../content/applications/essentials/export_import_data.rst:465 msgid "It produces the following :abbr:`CSV (Comma-separated Values)` file:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:469 +#: ../../content/applications/essentials/export_import_data.rst:475 msgid "In this file, Fabien and Laurence are working for the Bigees company (`company_1`), and Eric is working for the Organi company. The relation between people and companies is done using the *External ID* of the companies. The *External ID* is prefixed by the name of the table to avoid a conflict of ID between people and companies (`person_1` and `company_1`, who shared the same ID 1 in the original database)." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:475 +#: ../../content/applications/essentials/export_import_data.rst:481 msgid "The two files produced are ready to be imported in Odoo without any modifications. After having imported these two :abbr:`CSV (Comma-separated Values)` files, there are four contacts and three companies (the first two contacts are linked to the first company). Keep in mind to first import the companies, and then the people." msgstr "" +#: ../../content/applications/essentials/export_import_data.rst:489 +msgid "Update data in Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:491 +msgid "Existing data can be updated in bulk through a data import, as long as the :ref:`External ID ` remains consistent." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:495 +msgid "Prepare data export" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:497 +msgid "To update data through an import, first navigate to the data to be updated, and select the |list| to activate list view. On the far-left side of the list, tick the checkbox for any record to be updated. Then, click |actions|, and select :icon:`fa-upload` :guilabel:`Export` from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:502 +msgid "On the resulting :guilabel:`Export Data` pop-up window, tick the checkbox labeled, :guilabel:`I want to update data (import-compatible export)`. This automatically includes the *External ID* in the export. Additionally, it limits the :guilabel:`Fields to export` list to **only** include fields that are able to be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:508 +msgid "The :guilabel:`External ID` field does **not** appear in the :guilabel:`Fields to export` list unless it is manually added, but it is still included in the export. However, if the :guilabel:`I want to update data (import-compatible export)` checkbox is ticked, it is included in the export." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:512 +msgid "Select the required fields to be included in the export using the :ref:`options ` on the pop-up window, then click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:516 +msgid "Import updated data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:518 +msgid "After exporting, make any necessary changes to the data file. When the file is ready, it can be :ref:`imported ` by following the same process as a normal data import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:522 +msgid "When updating data, it is extremely important that the *External ID* remain consistent, as this is how the system identifies a record. If an ID is altered, or removed, the system may add a duplicate record, instead of updating the existing one." +msgstr "" + #: ../../content/applications/essentials/in_app_purchase.rst:3 msgid "In-app purchases (IAP)" msgstr "" @@ -1564,7 +1600,7 @@ msgid ":doc:`Enrich your contacts base with Partner Autocomplete <../sales/crm/o msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:92 -msgid ":doc:`SMS essentials <../marketing/sms_marketing/essentials/sms_essentials>`" +msgid ":doc:`SMS Marketing <../marketing/sms_marketing>`" msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:97 @@ -1608,7 +1644,7 @@ msgid "The number of credits consumed depends on the length of the SMS and the c msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:121 -msgid "For more information, refer to the :doc:`SMS Pricing and FAQ <../marketing/sms_marketing/pricing/pricing_and_faq>` documentation." +msgid "For more information, refer to the :doc:`SMS Pricing and FAQ <../marketing/sms_marketing/pricing_and_faq>` documentation." msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:127 @@ -2101,30 +2137,94 @@ msgid "Several groups can be used at the same time. The first group that is sele msgstr "" #: ../../content/applications/essentials/search.rst:187 -msgid "Favorites" +msgid "Comparison" msgstr "" #: ../../content/applications/essentials/search.rst:189 +msgid "Certain reporting dashboards include a :guilabel:`Comparison` section in the drop-down menus of their :guilabel:`Search...` bars. This includes the :doc:`Overall Equipment Effectiveness <../inventory_and_mrp/manufacturing/reporting/oee>` report for the *Manufacturing* app, and the :doc:`Purchase <../inventory_and_mrp/purchase/advanced/analyze>` report for the *Purchase* app, among others." +msgstr "" + +#: ../../content/applications/essentials/search.rst:195 +msgid "The options in the :icon:`fa-adjust` :guilabel:`Comparison` section are used to compare data from two different time periods. There are two comparison options to choose from: :guilabel:`(Time Filter): Previous Period` and :guilabel:`(Time Filter): Previous Year`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:200 +msgid "For some reports, the :guilabel:`Comparison` section **only** appears in the :guilabel:`Search...` bar drop-down menu if one (or more) time periods have been selected in the :guilabel:`Filters` column. This is because, if no time period is specified, there is nothing to compare." +msgstr "" + +#: ../../content/applications/essentials/search.rst:205 +msgid "Additionally, some reports only allow use of the :guilabel:`Comparison` feature when the :icon:`fa-pie-chart` :guilabel:`(pie chart)` graph type, or the :icon:`oi-view-pivot` :guilabel:`(pivot)` view, is selected. A :guilabel:`Comparison` option can be selected even if another view is enabled, but doing so does **not** change the way data is displayed on the report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The Search... bar for the production analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:215 +msgid "To view data using one of the two comparisons, begin by selecting a time period in the :guilabel:`Filters` column of the :guilabel:`Search...` bar drop-down menu. Then, select either :guilabel:`(Time Filter): Previous Period` or :guilabel:`(Time Filter): Previous Year` in the :guilabel:`Comparison` section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:220 +msgid "With one of the :guilabel:`Comparison` options enabled, the report compares the data for the selected period, with the data for the same unit of time (month, quarter, year), one period or year prior. The way the data is displayed depends on the selected view:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:224 +msgid "The :icon:`fa-bar-chart` :guilabel:`(bar chart)` shows two bars, side-by-side, for each unit of time for the selected time period. The left bar represents the selected time period, while the right bar represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:227 +msgid "The :icon:`fa-line-chart` :guilabel:`(line chart)` is displayed with two lines, one representing the selected time period, and the other representing the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:229 +msgid "The :icon:`fa-pie-chart` :guilabel:`(pie chart)` appears as a large circle with a smaller circle inside. The larger circle represents the selected time period, while the smaller circle represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:232 +msgid "The :icon:`oi-view-pivot` :guilabel:`(pivot table)` is displayed with each column split into two smaller columns. The right column represents the selected time period, while the left column represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:237 +msgid "In the :guilabel:`Production Analysis` report of the :menuselection:`Manufacturing` app, data for the second quarter of 2024 is compared to data for the second quarter of 2023. :guilabel:`Q2` is selected in the :guilabel:`End Date` filter section of the :guilabel:`Search...` bar drop-down menu. In the :guilabel:`Comparison` section, :guilabel:`End Date: Previous Year` is selected." +msgstr "" + +#: ../../content/applications/essentials/search.rst:242 +msgid "The current year is 2024, so the larger circle shows data for the second quarter (Q2) of 2024. The smaller circle shows data for the second quarter (Q2) of 2023, which is the same time period, but one *year* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:246 +msgid "If :guilabel:`End Date: Previous Period` is selected instead, the smaller circle shows data for the first quarter (Q1) of 2024, which is the same time period, but one *period* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "The comparison view of the Production Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:256 +msgid "Favorites" +msgstr "" + +#: ../../content/applications/essentials/search.rst:258 msgid "Favorites are a way to save a specific search for future use, or as the new default filter for the view." msgstr "" -#: ../../content/applications/essentials/search.rst:192 +#: ../../content/applications/essentials/search.rst:261 msgid "To save the current view as a favorite, click the :guilabel:`🔽 (down arrow)` icon in the search bar, then select the :guilabel:`Save current search` drop-down menu to display the following options:" msgstr "" -#: ../../content/applications/essentials/search.rst:196 +#: ../../content/applications/essentials/search.rst:265 msgid "Filter name: name of the favorited search." msgstr "" -#: ../../content/applications/essentials/search.rst:197 +#: ../../content/applications/essentials/search.rst:266 msgid ":guilabel:`Default filter`: sets the favorited search as the default filter for the view." msgstr "" -#: ../../content/applications/essentials/search.rst:198 +#: ../../content/applications/essentials/search.rst:267 msgid ":guilabel:`Shared`: makes the favorited search available to all users. By default, the favorited search is only available to the user who created it." msgstr "" -#: ../../content/applications/essentials/search.rst:201 +#: ../../content/applications/essentials/search.rst:270 msgid "Once the options are set, click :guilabel:`Save` to save the favorited search." msgstr "" @@ -2132,10 +2232,10 @@ msgstr "" msgid "Saving a favorite search on the Sales Analysis report" msgstr "" -#: ../../content/applications/essentials/search.rst:207 +#: ../../content/applications/essentials/search.rst:276 msgid "Saved favorites can be accessed by clicking the :guilabel:`🔽 (down arrow)` icon in the search bar, then selecting the saved filter in the :guilabel:`Favorites` drop-down menu. To remove a saved favorite, click the :guilabel:`🗑️ (garbage can)` icon next to the favorited search." msgstr "" -#: ../../content/applications/essentials/search.rst:212 +#: ../../content/applications/essentials/search.rst:281 msgid "To view *all* favorited searches, first activate :ref:`developer-mode`, and navigate to :menuselection:`Settings app --> Technical --> User Interface: User-defined Filters`. From here, all favorited searches can be viewed, edited, archived, or deleted." msgstr "" diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index c63c0ee21..629c8afea 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 13:30+0000\n" +"POT-Creation-Date: 2024-08-21 11:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -131,8 +131,9 @@ msgstr "" #: ../../content/applications/finance/accounting.rst:135 #: ../../content/applications/finance/fiscal_localizations/austria.rst:28 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1206 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1205 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:418 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:712 msgid "Financial reports" msgstr "" @@ -151,13 +152,13 @@ msgid "Profit and loss" msgstr "" #: ../../content/applications/finance/accounting.rst:141 -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:363 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:360 msgid "Cash flow statement" msgstr "" #: ../../content/applications/finance/accounting.rst:143 #: ../../content/applications/finance/accounting.rst:182 -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:77 +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:61 #: ../../content/applications/finance/fiscal_localizations/thailand.rst:38 msgid "Tax report" msgstr "" @@ -171,12 +172,12 @@ msgid "Audit" msgstr "" #: ../../content/applications/finance/accounting.rst:147 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1076 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1075 msgid "General ledger" msgstr "" #: ../../content/applications/finance/accounting.rst:149 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1038 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1037 msgid "Trial balance" msgstr "" @@ -240,7 +241,7 @@ msgid "Product margins" msgstr "" #: ../../content/applications/finance/accounting.rst:175 -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:339 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:336 msgid "1099 report" msgstr "" @@ -354,56 +355,56 @@ msgid "To connect your bank account to your database, go to :menuselection:`Acco msgstr "" #: ../../content/applications/finance/accounting/bank.rst:37 -#: ../../content/applications/finance/accounting/bank.rst:135 -#: ../../content/applications/finance/accounting/get_started.rst:188 +#: ../../content/applications/finance/accounting/bank.rst:137 +#: ../../content/applications/finance/accounting/get_started.rst:186 msgid ":doc:`bank/bank_synchronization`" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:40 +#: ../../content/applications/finance/accounting/bank.rst:42 msgid "Create a bank account" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:42 +#: ../../content/applications/finance/accounting/bank.rst:44 msgid "If your banking institution is not available in Odoo, or if you don't want to connect your bank account to your database, you can configure your bank account manually." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:45 +#: ../../content/applications/finance/accounting/bank.rst:47 msgid "To manually add a bank account, go to :menuselection:`Accounting --> Configuration --> Banks: Add a Bank Account`, click on :guilabel:`Create it` (at the bottom right), and fill out the form." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:49 +#: ../../content/applications/finance/accounting/bank.rst:51 msgid "Odoo automatically detects the bank account type (e.g., IBAN) and enables some features accordingly." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:51 +#: ../../content/applications/finance/accounting/bank.rst:53 msgid "A default bank journal is available and can be used to configure your bank account by going to :menuselection:`Accounting --> Configuration --> Accounting: Journals --> Bank`. Open it and edit the different fields to match your bank account information." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:56 +#: ../../content/applications/finance/accounting/bank.rst:58 msgid "Create a cash journal" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:58 +#: ../../content/applications/finance/accounting/bank.rst:60 msgid "To create a new cash journal, go to :menuselection:`Accounting --> Configuration --> Accounting: Journals`, click on :guilabel:`Create` and select :guilabel:`Cash` in the :guilabel:`Type` field." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:61 +#: ../../content/applications/finance/accounting/bank.rst:63 msgid "For more information on the accounting information fields, read the :ref:`bank_accounts/configuration` section of this page." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:65 +#: ../../content/applications/finance/accounting/bank.rst:67 msgid "A default cash journal is available and can be used straight away. You can review it by going to :menuselection:`Accounting --> Configuration --> Accounting: Journals --> Cash`." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:69 +#: ../../content/applications/finance/accounting/bank.rst:71 msgid "Edit an existing bank or cash journal" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:71 +#: ../../content/applications/finance/accounting/bank.rst:73 msgid "To edit an existing bank journal, go to :menuselection:`Accounting --> Configuration --> Accounting: Journals` and select the journal you want to modify." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:77 +#: ../../content/applications/finance/accounting/bank.rst:79 #: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:28 #: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:21 #: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:24 @@ -421,14 +422,14 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:15 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:38 #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:15 -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:22 +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:22 #: ../../content/applications/finance/accounting/payments/batch.rst:11 #: ../../content/applications/finance/accounting/payments/batch_sdd.rst:20 #: ../../content/applications/finance/accounting/payments/follow_up.rst:14 #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:12 #: ../../content/applications/finance/accounting/payments/online.rst:21 #: ../../content/applications/finance/accounting/payments/pay_checks.rst:10 -#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:45 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:46 #: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:10 #: ../../content/applications/finance/accounting/reporting/budget.rst:11 #: ../../content/applications/finance/accounting/reporting/silverfin.rst:11 @@ -454,20 +455,20 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:256 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:532 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:28 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:764 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:763 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:21 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:34 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:583 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:701 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:585 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:759 #: ../../content/applications/finance/fiscal_localizations/germany.rst:58 #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:6 #: ../../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:40 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:653 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:769 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:909 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:652 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:768 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:908 #: ../../content/applications/finance/fiscal_localizations/peru.rst:34 #: ../../content/applications/finance/fiscal_localizations/peru.rst:700 #: ../../content/applications/finance/fiscal_localizations/philippines.rst:6 @@ -476,9 +477,9 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:6 #: ../../content/applications/finance/fiscal_localizations/spain.rst:6 #: ../../content/applications/finance/fiscal_localizations/thailand.rst:6 -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:6 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:8 #: ../../content/applications/finance/fiscal_localizations/united_states.rst:34 -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:647 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:644 #: ../../content/applications/finance/payment_providers/adyen.rst:17 #: ../../content/applications/finance/payment_providers/alipay.rst:12 #: ../../content/applications/finance/payment_providers/authorize.rst:9 @@ -491,7 +492,7 @@ msgstr "" msgid "Configuration" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:79 +#: ../../content/applications/finance/accounting/bank.rst:81 msgid "You can edit the accounting information and bank account number according to your needs." msgstr "" @@ -499,45 +500,45 @@ msgstr "" msgid "Manually configure your bank information" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:85 -#: ../../content/applications/finance/accounting/bank.rst:109 +#: ../../content/applications/finance/accounting/bank.rst:87 +#: ../../content/applications/finance/accounting/bank.rst:111 msgid ":doc:`get_started/multi_currency`" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:86 -#: ../../content/applications/finance/accounting/bank.rst:136 +#: ../../content/applications/finance/accounting/bank.rst:88 +#: ../../content/applications/finance/accounting/bank.rst:138 msgid ":doc:`bank/transactions`" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:91 +#: ../../content/applications/finance/accounting/bank.rst:93 msgid "Suspense account" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:93 +#: ../../content/applications/finance/accounting/bank.rst:95 msgid "Bank statement transactions are posted on the :guilabel:`Suspense Account` until the final reconciliation allows finding the right account." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:97 +#: ../../content/applications/finance/accounting/bank.rst:99 msgid "Profit and loss accounts" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:99 +#: ../../content/applications/finance/accounting/bank.rst:101 msgid "The :guilabel:`Profit Account` is used to register a profit when the ending balance of a cash register differs from what the system computes, while the :guilabel:`Loss Account` is used to register a loss when the ending balance of a cash register differs from what the system computes." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:104 +#: ../../content/applications/finance/accounting/bank.rst:106 msgid "Currency" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:106 +#: ../../content/applications/finance/accounting/bank.rst:108 msgid "You can edit the currency used to enter the statements." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:112 +#: ../../content/applications/finance/accounting/bank.rst:114 msgid "Account number" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:114 +#: ../../content/applications/finance/accounting/bank.rst:116 msgid "If you need to **edit your bank account details**, click on the external link arrow next to your :guilabel:`Account Number`. On the new page, click on the external link arrow next to your :guilabel:`Bank` and update your bank information accordingly. These details are used when registering payments." msgstr "" @@ -545,67 +546,67 @@ msgstr "" msgid "Edit your bank information" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:123 +#: ../../content/applications/finance/accounting/bank.rst:125 msgid "Bank feeds" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:125 +#: ../../content/applications/finance/accounting/bank.rst:127 msgid ":guilabel:`Bank Feeds` defines how the bank statements are registered. Three options are available:" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:127 +#: ../../content/applications/finance/accounting/bank.rst:129 msgid ":guilabel:`Undefined yet`, which should be selected when you don’t know yet if you will synchronize your bank account with your database or not." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:129 +#: ../../content/applications/finance/accounting/bank.rst:131 msgid ":guilabel:`Import (CAMT, CODA, CSV, OFX, QIF)`, which should be selected if you want to import your bank statement using a different format." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:131 +#: ../../content/applications/finance/accounting/bank.rst:133 msgid ":guilabel:`Automated Bank Synchronization`, which should be selected if your bank is synchronized with your database." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:141 +#: ../../content/applications/finance/accounting/bank.rst:143 msgid "Outstanding accounts" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:143 +#: ../../content/applications/finance/accounting/bank.rst:145 msgid "By default, payments are registered through transitory accounts named **outstanding accounts**, before being recorded in your bank account." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:146 +#: ../../content/applications/finance/accounting/bank.rst:148 msgid "An **outstanding payments account** is where outgoing payments are posted until they are linked with a withdrawal from your bank statement." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:148 +#: ../../content/applications/finance/accounting/bank.rst:150 msgid "An **outstanding receipts account** is where incoming payments are posted until they are linked with a deposit from your bank statement." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:151 +#: ../../content/applications/finance/accounting/bank.rst:153 msgid "These accounts should be of :ref:`type ` :guilabel:`Current Assets`." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:154 +#: ../../content/applications/finance/accounting/bank.rst:156 msgid "The movement from an outstanding account to a bank account is done automatically when you reconcile the bank account with a bank statement." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:158 +#: ../../content/applications/finance/accounting/bank.rst:160 msgid "Default accounts configuration" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:160 +#: ../../content/applications/finance/accounting/bank.rst:162 msgid "The outstanding accounts are defined by default. If necessary, you can update them by going to :menuselection:`Accounting --> Configuration --> Settings --> Default Accounts` and update your :guilabel:`Outstanding Receipts Account` and :guilabel:`Outstanding Payments Account`." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:165 +#: ../../content/applications/finance/accounting/bank.rst:167 msgid "Bank and cash journals configuration" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:167 +#: ../../content/applications/finance/accounting/bank.rst:169 msgid "You can also set specific outstanding accounts for any journal with the :ref:`type ` :guilabel:`Bank` or :guilabel:`Cash`." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:170 +#: ../../content/applications/finance/accounting/bank.rst:172 msgid "From your :guilabel:`Accounting Dashboard`, click on the menu selection ⋮ of the journal you want to configure, and click on :guilabel:`Configuration`, then open the :guilabel:`Incoming/Outgoing Payments` tab. To display the outstanding accounts column, click on the toggle button and check the :guilabel:`Outstanding Receipts/Payments accounts`, then update the account." msgstr "" @@ -613,11 +614,11 @@ msgstr "" msgid "Select the toggle button and click on outstanding Accounts" msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:180 +#: ../../content/applications/finance/accounting/bank.rst:182 msgid "If you do not specify an outstanding payments account or an outstanding receipts account for a specific journal, Odoo uses the default outstanding accounts." msgstr "" -#: ../../content/applications/finance/accounting/bank.rst:182 +#: ../../content/applications/finance/accounting/bank.rst:184 msgid "If your main bank account is added as an outstanding receipts account or outstanding payments account, when a payment is registered, the invoice or bill's status is directly set to :guilabel:`Paid`." msgstr "" @@ -1353,7 +1354,7 @@ msgid "Unrealized Currency Gains/Losses report once adjusted." msgstr "" #: ../../content/applications/finance/accounting/bank/reconciliation.rst:3 -#: ../../content/applications/finance/accounting/payments/batch.rst:52 +#: ../../content/applications/finance/accounting/payments/batch.rst:54 msgid "Bank reconciliation" msgstr "" @@ -1769,7 +1770,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:5 #: ../../content/applications/finance/accounting/payments/batch_sdd.rst:90 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:432 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:363 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:365 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:321 msgid "Customer invoices" msgstr "" @@ -1949,6 +1950,7 @@ msgid "115" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:109 +#: ../../content/applications/finance/accounting/get_started.rst:83 #: ../../content/applications/finance/accounting/taxes.rst:5 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:169 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:32 @@ -1962,7 +1964,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:121 #: ../../content/applications/finance/fiscal_localizations/spain.rst:33 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:116 -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:51 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:52 #: ../../content/applications/finance/fiscal_localizations/united_states.rst:234 msgid "Taxes" msgstr "" @@ -2117,7 +2119,7 @@ msgid ":doc:`payment_terms`" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:22 -#: ../../content/applications/finance/accounting/payments/batch.rst:67 +#: ../../content/applications/finance/accounting/payments/batch.rst:69 msgid ":doc:`../payments`" msgstr "" @@ -2530,26 +2532,30 @@ msgid "To specify a sales order's invoice and delivery addresses, first go to :m msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:19 -msgid "On quotations and sales orders, there are now fields for :guilabel:`Invoice Address` and :guilabel:`Delivery Address`. If the customer has an invoice or delivery address listed on their contact record, the corresponding field will use that address by default, but any contact's address can be used instead." +msgid "On quotations and sales orders, there are now fields for :guilabel:`Invoice Address` and :guilabel:`Delivery Address`. If the customer has an invoice or delivery address listed on their :ref:`contact record `, the corresponding field uses that address, by default, but any contact's address can be used instead." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:25 +msgid "For more information, refer to the documentation on :ref:`Contact Form Configuration `." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:30 msgid "Invoice and deliver to different addresses" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:27 +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:32 msgid "Delivery orders and their delivery slip reports use the address set as the :guilabel:`Delivery Address` on the sales order. By default, invoice reports show both the shipping address and the invoice address to assure the customer that the delivery is going to the correct location." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:31 +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:36 msgid "Emails also go to different addresses. The quotation and sales order are sent to the main contact's email, as usual, but the invoice is sent to the email of the address set as the :guilabel:`Invoice Address` on the sales order." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:36 +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:41 msgid "Reports, such as the delivery slip and invoice report, can be :doc:`customized using Studio `." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:38 +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:43 msgid "If :doc:`Send by Post ` is checked when you click :guilabel:`Send & Print`, the invoice will be mailed to the invoice address." msgstr "" @@ -4042,7 +4048,7 @@ msgid "Get started" msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:7 -msgid "When you first open your Odoo Accounting app, the *Accounting Overview* page welcomes you with a step-by-step onboarding banner, a wizard that helps you get started. This onboarding banner is displayed until you choose to close it." +msgid "When you first open your Odoo Accounting app, the :guilabel:`Accounting Dashboard` welcomes you with a step-by-step onboarding banner, a wizard that helps you get started. This onboarding banner is displayed until you choose to close it." msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:11 @@ -4066,7 +4072,7 @@ msgid "Step-by-step onboarding banner in Odoo Accounting" msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:28 -msgid ":ref:`accounting-setup-company`" +msgid ":ref:`accounting-setup-periods`" msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:29 @@ -4074,7 +4080,7 @@ msgid ":ref:`accounting-setup-bank`" msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:30 -msgid ":ref:`accounting-setup-periods`" +msgid ":ref:`accounting-setup-taxes`" msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:31 @@ -4082,28 +4088,28 @@ msgid ":ref:`accounting-setup-chart`" msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:36 -#: ../../content/applications/finance/accounting/get_started.rst:137 -msgid "Company Data" +msgid "Accounting Periods" msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:38 -msgid "This menu allows you to add your company’s details such as the name, address, logo, website, phone number, email address, and Tax ID, or VAT number. These details are then displayed on your documents, such as on invoices." +msgid "Define the **Fiscal Years**’ opening and closing dates, which are used to generate reports automatically, and set your **Tax Return Periodicity**, along with a reminder to never miss a tax return deadline." msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:-1 -msgid "Add your company's details in Odoo Accounting and Odoo Invoicing" +#: ../../content/applications/finance/accounting/get_started.rst:42 +msgid "By default, the opening date is set on the 1st of January and the closing date on the 31st of December, as this is the most common use." msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:46 -msgid "You can also change these settings by going to :menuselection:`Settings --> General Settings --> Settings --> Companies` and clicking on **Update Info**." +msgid "You can also change these settings by going to :menuselection:`Accounting --> Configuration --> Settings --> Fiscal Periods` and updating the values." msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:52 +#: ../../content/applications/finance/accounting/get_started.rst:149 msgid "Bank Account" msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:54 -msgid "Connect your bank account to your database and have your bank statements synced automatically. To do so, find your bank in the list, click on *Connect*, and follow the instructions on-screen." +msgid "Connect your bank account to your database and have your bank statements synced automatically. To do so, find your bank in the list, click :guilabel:`Connect`, and follow the instructions on-screen." msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:58 @@ -4111,87 +4117,79 @@ msgid ":doc:`Click here ` for more information about msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:60 -msgid "If your Bank Institution can’t be synchronized automatically, or if you prefer not to sync it with your database, you may also configure your bank account manually by clicking on *Create it*, and filling out the form." +msgid "If your Bank Institution can’t be synchronized automatically, or if you prefer not to sync it with your database, you can also configure your bank account manually by typing its name, clicking :guilabel:`Create your Bank Account`, and filling out the form." msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:64 -msgid "**Name**: the bank account's name, as displayed on Odoo." +msgid ":guilabel:`Name`: the bank account's name, as displayed in Odoo." msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:65 -msgid "**Account Number**: your bank account number (IBAN in Europe)." +msgid ":guilabel:`Account Number`: your bank account number (IBAN in Europe)." msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:66 -msgid "**Bank**: click on *Create and Edit* to configure the bank's details. Add the bank institution's name and its Identifier Code (BIC or SWIFT)." +msgid ":guilabel:`Bank`: click :guilabel:`Create and edit` to configure the bank's details. Add the bank institution's :guilabel:`Name` and its :guilabel:`Identifier Code` (BIC or SWIFT)." msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:68 -msgid "**Code**: this code is your Journal's *Short Code*, as displayed on Odoo. By default, Odoo creates a new Journal with this Short Code." +msgid ":guilabel:`Code`: this code is your Journal's :guilabel:`Short Code`, as displayed in Odoo. By default, Odoo creates a new Journal with this short code." msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:70 -msgid "**Journal**: This field is displayed if you have an existing Bank Journal that is not linked yet to a bank account. If so, then select the *Journal* you want to use to record the financial transactions linked to this bank account or create a new one by clicking on *Create and Edit*." +msgid ":guilabel:`Journal`: This field is displayed if you have an existing bank journal that is not linked yet to a bank account. If so, then select the :guilabel:`Journal` you want to use to record the financial transactions linked to this bank account or create a new one by clicking :guilabel:`Create and Edit`." msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:75 -msgid "You can add as many bank accounts as needed with this tool by going to :menuselection:`Accounting --> Configuration`, and clicking on *Add a Bank Account*." +#: ../../content/applications/finance/accounting/get_started.rst:76 +msgid "You can add as many bank accounts as needed with this tool by going to :menuselection:`Accounting --> Configuration --> Add a Bank Account`." msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:77 +#: ../../content/applications/finance/accounting/get_started.rst:78 msgid ":doc:`Click here ` for more information about Bank Accounts." msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:83 -msgid "Accounting Periods" -msgstr "" - #: ../../content/applications/finance/accounting/get_started.rst:85 -msgid "Define here your **Fiscal Years**’ opening and closing dates, which are used to generate reports automatically, and your **Tax Return Periodicity**, along with a reminder to never miss a tax return deadline." +msgid "This menu allows you to create new taxes, (de)activate, or modify existing taxes. Depending on the :doc:`localization package <../fiscal_localizations>` installed on your database, taxes required for your country are already configured." msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:89 -msgid "By default, the opening date is set on the 1st of January and the closing date on the 31st of December, as this is the most common use." +#: ../../content/applications/finance/accounting/get_started.rst:90 +msgid ":doc:`Click here ` for more information about taxes." msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:93 -msgid "You can also change these settings by going to :menuselection:`Accounting --> Configuration --> Settings --> Fiscal Periods` and updating the values." -msgstr "" - -#: ../../content/applications/finance/accounting/get_started.rst:99 +#: ../../content/applications/finance/accounting/get_started.rst:95 #: ../../content/applications/finance/fiscal_localizations/australia.rst:45 msgid "Chart of Accounts" msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:101 +#: ../../content/applications/finance/accounting/get_started.rst:97 msgid "With this menu, you can add accounts to your **Chart of Accounts** and indicate their initial opening balances." msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:104 -msgid "Basic settings are displayed on this page to help you review your Chart of Accounts. To access all the settings of an account, click on the *double arrow button* at the end of the line." +#: ../../content/applications/finance/accounting/get_started.rst:100 +msgid "Basic settings are displayed on this page to help you review your Chart of Accounts. To access all the settings of an account, click on the :guilabel:`Setup` button at the end of the line." msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:-1 msgid "Setup of the Chart of Accounts and their opening balances in Odoo Accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:111 +#: ../../content/applications/finance/accounting/get_started.rst:107 msgid ":doc:`Click here ` for more information on how to configure your Chart of Accounts." msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:115 +#: ../../content/applications/finance/accounting/get_started.rst:111 msgid "Invoicing onboarding banner" msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:117 -msgid "There is another step-by-step onboarding banner that helps you take advantage of your Odoo Invoicing and Accounting apps. The *Invoicing onboarding banner* is the one that welcomes you if you use the Invoicing app rather than the Accounting app." +#: ../../content/applications/finance/accounting/get_started.rst:113 +msgid "There is another step-by-step onboarding banner that helps you take advantage of your Odoo Invoicing and Accounting apps. The Invoicing onboarding banner is the one that welcomes you if you use the Invoicing app rather than the Accounting app." msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:121 +#: ../../content/applications/finance/accounting/get_started.rst:117 msgid "If you have Odoo Accounting installed on your database, you can reach it by going to :menuselection:`Accounting --> Customers --> Invoices`." msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:124 +#: ../../content/applications/finance/accounting/get_started.rst:120 msgid "The Invoicing onboarding banner is composed of four main steps:" msgstr "" @@ -4199,83 +4197,83 @@ msgstr "" msgid "Step-by-step onboarding banner in Odoo Invoicing" msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:129 +#: ../../content/applications/finance/accounting/get_started.rst:125 msgid ":ref:`invoicing-setup-company`" msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:130 +#: ../../content/applications/finance/accounting/get_started.rst:126 +msgid ":ref:`invoicing-setup-bank`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:127 msgid ":ref:`invoicing-setup-layout`" msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:131 -msgid ":ref:`invoicing-setup-payment`" +#: ../../content/applications/finance/accounting/get_started.rst:128 +msgid ":ref:`invoicing-setup-invoice`" msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:132 -msgid ":ref:`invoicing-setup-sample`" +#: ../../content/applications/finance/accounting/get_started.rst:133 +msgid "Company Data" msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:139 -msgid "This form is the same as :ref:`the one presented in the Accounting onboarding banner `." -msgstr "" - -#: ../../content/applications/finance/accounting/get_started.rst:145 -msgid "Invoice Layout" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started.rst:147 -msgid "With this tool, you can design the appearance of your documents by selecting which layout template, paper format, colors, font, and logo you want to use." -msgstr "" - -#: ../../content/applications/finance/accounting/get_started.rst:150 -msgid "You can also add your *Company Tagline* and the content of the documents’ *footer*. Note that Odoo automatically adds the company's phone number, email, website URL, and Tax ID (or VAT number) to the footer, according to the values you previously configured in the :ref:`Company Data `." +#: ../../content/applications/finance/accounting/get_started.rst:135 +msgid "This form allows you to add your company’s details, such as the name, address, logo, website, phone number, email address, and Tax ID or VAT number. These details are then displayed on your documents, such as invoices." msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:-1 -msgid "Document layout configuration in Odoo Invoicing" +msgid "Add your company's details in Odoo Accounting and Odoo Invoicing" msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:159 -msgid "Add your **bank account number** and a link to your **General Terms & Condition** in the footer. This way, your contacts can find the full content of your GT&C online without having to print them on the invoices you issue." +#: ../../content/applications/finance/accounting/get_started.rst:143 +msgid "You can also change the company's details by going to :menuselection:`Settings --> General Settings`, scrolling down to the :guilabel:`Companies` section, and :guilabel:`Update Info`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:151 +msgid "Use this button to create and link a bank account in Odoo. To add additional bank accounts, go to :guilabel:`Invoicing --> Configuration --> Add a Bank Account` and :ref:`configure the fields `." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:156 +msgid ":doc:`Synchronize ` your bank account(s) with your Odoo database to automatically update your bank transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:162 +msgid "Invoice Layout" msgstr "" #: ../../content/applications/finance/accounting/get_started.rst:164 -msgid "These settings can also be modified by going to :menuselection:`Settings --> General Settings`, under the *Business Documents* section." +msgid "Use this button to customize the :ref:`default invoice layout `." msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:170 -msgid "Payment Method" +#: ../../content/applications/finance/accounting/get_started.rst:167 +msgid "You can also change the invoice layout by going to :menuselection:`Settings --> General Settings`, scrolling down to the :guilabel:`Companies` section, and clicking :guilabel:`Configure Document Layout`." msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:172 -msgid "This menu helps you configure the payment methods with which your customers can pay you." +#: ../../content/applications/finance/accounting/get_started.rst:174 +msgid "Invoice Creation" msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:175 -msgid "Configuring a *Payment Provider* with this tool also activates the *Invoice Online Payment* option automatically. With this, users can directly pay online, from their Customer Portal." +#: ../../content/applications/finance/accounting/get_started.rst:176 +msgid "This button takes you to the invoice creation view, where you can create your first invoice." msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:181 -msgid "Sample Invoice" +#: ../../content/applications/finance/accounting/get_started.rst:179 +msgid "Add your **bank account number** and a link to your **General Terms & Condition** in the footer. This way, your contacts can find the full content of your GT&C online without having to print them on the invoices you issue." msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:183 -msgid "Send yourself a sample invoice by email to make sure everything is correctly configured." -msgstr "" - -#: ../../content/applications/finance/accounting/get_started.rst:186 +#: ../../content/applications/finance/accounting/get_started.rst:184 msgid ":doc:`bank`" msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:187 +#: ../../content/applications/finance/accounting/get_started.rst:185 msgid ":doc:`get_started/chart_of_accounts`" msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:189 +#: ../../content/applications/finance/accounting/get_started.rst:187 msgid ":doc:`../fiscal_localizations`" msgstr "" -#: ../../content/applications/finance/accounting/get_started.rst:190 +#: ../../content/applications/finance/accounting/get_started.rst:188 msgid "`Odoo Tutorials: Accounting and Invoicing - Getting started [video] `_" msgstr "" @@ -4425,9 +4423,9 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:286 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:288 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:292 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:403 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:417 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:424 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:406 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:420 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:427 msgid "$0" msgstr "" @@ -5007,12 +5005,12 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:208 #: ../../content/applications/finance/fiscal_localizations/chile.rst:361 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:247 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:258 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1011 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:260 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1010 #: ../../content/applications/finance/fiscal_localizations/romania.rst:65 #: ../../content/applications/finance/fiscal_localizations/spain.rst:24 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:38 -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:41 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:42 #: ../../content/applications/finance/fiscal_localizations/united_states.rst:115 msgid "Chart of accounts" msgstr "" @@ -5536,7 +5534,7 @@ msgid "Partial payment 2/2" msgstr "" #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:178 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:422 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:425 msgid "30" msgstr "" @@ -5792,77 +5790,65 @@ msgstr "" msgid "Exchange rate journal entry." msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:3 -msgid "VAT units" +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:3 +msgid "Tax units" msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:6 +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:6 msgid "This is only applicable to multi-company environments." msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:8 -msgid "A **VAT unit** is a group of VAT-taxable enterprises that are legally independent of each other but are closely linked financially, organizationally, and economically and therefore considered the same VAT-taxable enterprise. **VAT units** are not mandatory, but if created, constituent companies of the unit must belong to the same **country**, use the same **currency**, and one company must be designated as the **representative** company of the **VAT unit**. **VAT units** receive a specific **tax ID** intended only for **tax returns**. **Constituent** companies keep their **tax ID** used for **commercial purposes**." +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:8 +msgid "A **tax unit** is a group of VAT-taxable enterprises that are legally independent of each other but are closely linked financially, organizationally, and economically and therefore considered the same VAT-taxable enterprise. **Tax units** are not mandatory, but if created, constituent companies of the unit must belong to the same **country**, use the same **currency**, and one company must be designated as the **representative** company of the **tax unit**. **Tax units** receive a specific **tax ID** intended only for **tax returns**. **Constituent** companies keep their **tax ID** used for **commercial purposes**." msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:17 -msgid "Enterprise **A** owes €300.000,00 of VAT taxes and enterprise **B** can recover €280.000,00 of VAT taxes. They form up as a **VAT unit** so that the two amounts balance out and must conjointly only pay €20.000,00 of VAT taxes." +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:17 +msgid "Enterprise **A** owes €300.000,00 of VAT taxes and enterprise **B** can recover €280.000,00 of VAT taxes. They form up as a **tax unit** so that the two amounts balance out and must conjointly only pay €20.000,00 of VAT taxes." msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:24 -msgid "To configure a **VAT unit**, go to :menuselection:`Settings --> General Settings`, scroll down to the :guilabel:`Companies` section, and click :guilabel:`Manage Companies`. Select the company to serve the **representative** role, and in the :guilabel:`General Information` tab, fill in the mandatory fields for the .XML export when exporting the **tax report**: :guilabel:`Company Name`, :guilabel:`Address`, :guilabel:`VAT`, :guilabel:`Currency`, :guilabel:`Phone`, and :guilabel:`Email`." +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:24 +msgid "To create a **tax unit**, go to :menuselection:`Accounting --> Configuration --> Tax Units`, and click :guilabel:`New`. Enter a **name** for the unit, select a :guilabel:`Country`, the :guilabel:`Companies` to incorporate in the unit, the :guilabel:`Main Company`, and the :guilabel:`Tax ID` of the **constituent** company of that tax unit." msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:-1 -msgid "General information tab" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:35 -msgid "Then, click on the :guilabel:`VAT Units` tab, :guilabel:`Add a line`, and either select an existing **VAT unit**, or create a new one. Enter a **name** for the unit, :guilabel:`Country` of the constituent companies and tax report, the :guilabel:`Companies`, the :guilabel:`Main Company` that serves the **representative** role, and the :guilabel:`Tax ID` of the **VAT unit**." -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:-1 -msgid "VAT units tab" -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:45 -#: ../../content/applications/finance/accounting/taxes/avatax.rst:339 +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:30 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:340 msgid "Fiscal position" msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:47 -msgid "As transactions between constituents of the same **VAT unit** are not subject to VAT, it is possible to create a :doc:`tax mapping (fiscal position) <../taxes/fiscal_positions>` to avoid the application of VAT on inter-constituent transactions." +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:32 +msgid "As transactions between constituents of the same **tax unit** are not subject to VAT, it is possible to create a :doc:`tax mapping (fiscal position) <../taxes/fiscal_positions>` to avoid the application of VAT on inter-constituent transactions." msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:51 +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:36 msgid "Be sure a constituent company has been selected before, then go to :menuselection:`Accounting --> Configuration --> Fiscal Positions`, and :guilabel:`Create` a new **fiscal position**. Click the :guilabel:`Tax Mapping` tab, select the :guilabel:`Tax on Product` usually applied for **non-constituent** transactions, and in :guilabel:`Tax to Apply`, select the 0% tax to apply for **constituent** transactions." msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:57 +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:42 msgid "Do the same for the :guilabel:`Account Mapping` tab if required, and repeat this process for **each** constituent company on your database." msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:61 +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:46 msgid "Depending on your :doc:`localization package `, taxes may vary from the screenshot displayed." msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:0 -msgid "Tax mapping of fiscal position for VAT unit" +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:0 +msgid "Tax mapping of fiscal position for tax unit" msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:68 -msgid "Then, assign the fiscal position by opening the **Contacts** app. Search for a **constituent** company, and open the contact's **card**. Click the :guilabel:`Sales & Purchase` tab, and in the :guilabel:`Fiscal Position` field, input the **fiscal position** created for the **VAT unit**. Repeat the process for each **constituent** company card form, on each company database." +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:52 +msgid "Then, assign the fiscal position by opening the **Contacts** app. Search for a **constituent** company, and open the contact's **card**. Click the :guilabel:`Sales & Purchase` tab, and in the :guilabel:`Fiscal Position` field, input the **fiscal position** created for the **tax unit**. Repeat the process for each **constituent** company card form, on each company database." msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:74 +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:58 msgid ":doc:`../taxes/fiscal_positions`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:79 -msgid "The **representative** company can access the aggregated tax report of the **VAT unit** by going to :menuselection:`Accounting --> Reporting --> Tax Report`, and selecting the **VAT unit** in :guilabel:`Tax Unit`. This report contains the aggregated transactions of all **constituents** and the .XML export contains the name and VAT number of the **main** company." +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:63 +msgid "The **representative** company can access the aggregated tax report of the **tax unit** by going to :menuselection:`Accounting --> Reporting --> Tax Report`, and selecting the **tax unit** in :guilabel:`Tax Unit`. This report contains the aggregated transactions of all **constituents** and the .XML export contains the name and VAT number of the **main** company." msgstr "" -#: ../../content/applications/finance/accounting/get_started/vat_units.rst:-1 -msgid "VAT unit tax report" +#: ../../content/applications/finance/accounting/get_started/tax_units.rst:-1 +msgid "tax unit tax report" msgstr "" #: ../../content/applications/finance/accounting/payments.rst:5 @@ -6033,11 +6019,11 @@ msgstr "" msgid "Deposit multiple payments in batch" msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:20 +#: ../../content/applications/finance/accounting/payments/batch.rst:22 msgid "Register payments" msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:22 +#: ../../content/applications/finance/accounting/payments/batch.rst:24 msgid "Before performing a batch deposit, it is necessary to register each transaction's payment. To do so, open the corresponding customer invoice and click :guilabel:`Register Payment`. In the pop-up window, select the :guilabel:`Journal` linked to your bank account and :guilabel:`Batch Deposit` as the :guilabel:`Payment Method`, and click :guilabel:`Create Payment`." msgstr "" @@ -6045,11 +6031,11 @@ msgstr "" msgid "Registering a customer payment as part of a batch deposit" msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:31 +#: ../../content/applications/finance/accounting/payments/batch.rst:33 msgid "Add payments to a batch deposit" msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:33 +#: ../../content/applications/finance/accounting/payments/batch.rst:35 msgid "To add payments to a batch deposit, go to :menuselection:`Accounting --> Customers --> Batch Payments`, and click :guilabel:`New`. Next, select the :guilabel:`Bank` and choose :guilabel:`Batch Deposit` as the :guilabel:`Payment Method`." msgstr "" @@ -6057,7 +6043,7 @@ msgstr "" msgid "Filling out a new inbound batch payment form" msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:40 +#: ../../content/applications/finance/accounting/payments/batch.rst:42 msgid "Click :guilabel:`Add a line`. In the pop-up window, tick all payments to include in the batch deposit, then click :guilabel:`Select`." msgstr "" @@ -6065,15 +6051,15 @@ msgstr "" msgid "Selecting all payments to include in the batch deposit" msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:46 +#: ../../content/applications/finance/accounting/payments/batch.rst:48 msgid "Once done, click :guilabel:`Validate` to finalize the batch deposit." msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:49 +#: ../../content/applications/finance/accounting/payments/batch.rst:51 msgid "Click :guilabel:`Print` to download a PDF file to include with the deposit slip." msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:54 +#: ../../content/applications/finance/accounting/payments/batch.rst:56 msgid "Once the bank transactions are on your database, you can reconcile bank statement lines with the batch payment. To do so, go to the :guilabel:`Accounting Dashboard` and click :guilabel:`Reconcile Items` on the related bank account. Go to the :guilabel:`Batch Payments` tab to select a specific batch and click :guilabel:`Validate` to finalize the process." msgstr "" @@ -6081,11 +6067,11 @@ msgstr "" msgid "Reconciling the batch payment with all its transactions" msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:63 +#: ../../content/applications/finance/accounting/payments/batch.rst:65 msgid "If a specific payment could not be processed by the bank or is missing, remove the related payment before reconciling." msgstr "" -#: ../../content/applications/finance/accounting/payments/batch.rst:68 +#: ../../content/applications/finance/accounting/payments/batch.rst:70 msgid ":doc:`batch_sdd`" msgstr "" @@ -6509,7 +6495,7 @@ msgid ":doc:`/applications/essentials/in_app_purchase`" msgstr "" #: ../../content/applications/finance/accounting/payments/follow_up.rst:94 -msgid ":doc:`/applications/marketing/sms_marketing/pricing/pricing_and_faq`" +msgid ":doc:`/applications/marketing/sms_marketing/pricing_and_faq`" msgstr "" #: ../../content/applications/finance/accounting/payments/follow_up.rst:95 @@ -6922,58 +6908,58 @@ msgid "Isle of Man." msgstr "" #: ../../content/applications/finance/accounting/payments/pay_sepa.rst:33 -msgid "When paying a bill in Odoo, you can select SEPA mandates as a payment option. At the day's end, you can generate the SEPA file containing all bank wire transfers and send it to the bank." +msgid "When paying a bill in Odoo, you can select SEPA mandates as a payment option. At the end of the day, you can generate the SEPA file containing all bank wire transfers and upload it to your online banking interface to process the payments." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:36 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:37 msgid "By default, the file follows the SEPA Credit Transfer **'pain.001.001.03'** specifications. This is a well-defined standard among banks. However, for Swiss and German companies, other formats are used **'pain.001.001.03.ch.02'** for Switzerland and **'pain.001.003.03'** for Germany." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:40 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:41 msgid "Once the payments are processed by your bank, you can directly import the account statement in Odoo. The bank reconciliation process will seamlessly match the SEPA orders you sent to your bank with actual bank statements." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:48 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:49 msgid "Activate SEPA Credit Transfer (SCT)" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:50 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:51 msgid "To pay suppliers with SEPA, you must activate the **SEPA Credit Transfer** setting. To do so, go to :menuselection:`Accounting --> Configuration --> Settings --> Vendor Payments: SEPA Credit Transfer (SCT)`. By activating the setting and filling out your company data, you will be able to use the SCT option when paying your vendor." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:56 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:57 msgid "According to the localization package installed, the **SEPA Direct Debit** and **SEPA Credit Transfer** modules may be installed by default. If not, they need to be :ref:`installed `." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:60 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:61 msgid "Activate SEPA payment methods on banks" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:62 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:63 msgid "From the accounting dashboard, click on the drop-down menu (:guilabel:`⋮`) on your bank journal and select :guilabel:`Configuration`. Click the :guilabel:`Outgoing Payments` tab, and, if not already present, add :guilabel:`SEPA Credit Transfer` under :guilabel:`Payment Method`." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:66 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:67 msgid "Make sure to specify the IBAN account number (domestic account numbers do not work with SEPA) and the BIC (bank identifier code) in the :guilabel:`Journal Entries` tab." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:70 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:71 msgid "Registering payments" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:72 -msgid "You can register and vendor payments made with SEPA. To do so, go to :menuselection:`Accounting --> Vendors --> Payments`. When creating your payment, select :guilabel:`SEPA Credit Transfer` as the :guilabel:`Payment Method`." +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:73 +msgid "You can register any vendor payments made with SEPA. To do so, go to :menuselection:`Accounting --> Vendors --> Payments`. When creating your payment, select :guilabel:`SEPA Credit Transfer` as the :guilabel:`Payment Method`." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:76 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:77 msgid "The first time you pay a vendor with SEPA, you have to fill in the :guilabel:`Recipient Bank Account` field with the bank name, IBAN, and BIC (Bank Identifier Code). Odoo automatically verifies if the IBAN format is respected." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:80 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:81 msgid "For future payments to this vendor, Odoo will automatically suggest you the bank account, but it remains possible to select a new one." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:83 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:84 msgid "Once your payment is registered, do not forget to confirm it. You can also pay vendor bills from the bill directly using the :guilabel:`Register Payment` button at the top of a vendor bill. The form is the same, but the payment is directly linked to the bill and will be automatically reconciled with it." msgstr "" @@ -7475,8 +7461,8 @@ msgid "Each budgetary position can have any number of accounts from the chart of msgstr "" #: ../../content/applications/finance/accounting/reporting/budget.rst:32 -#: ../../content/applications/finance/fiscal_localizations/spain.rst:87 -#: ../../content/applications/finance/fiscal_localizations/spain.rst:126 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:120 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:159 msgid "Use case" msgstr "" @@ -8002,7 +7988,7 @@ msgid "Tax authorities in some countries require companies to **prove their post msgstr "" #: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:8 -msgid "To do so, Odoo can use the **SHA-256 algorithm** to create a unique fingerprint for each posted entry. This fingerprint is called a hash. The hash is generated by taking an entry's essential data (the values of the `date`, `journal_id`, `company_id`, `debit`, `credit`, `account_id`, and `partner_id` fields), concatenating it, and inputting it to the SHA-256 hash function, which then outputs a fixed size (256-bit) string of characters. The hash function is deterministic (:dfn:`the same input always creates the same output`): any minor modification to the original data would completely change the resulting hash. Consequently, the SHA-256 algorithm is often used, among others, for data integrity verification purposes." +msgid "To do so, Odoo can use the **SHA-256 algorithm** to create a unique fingerprint for each posted entry. This fingerprint is called a hash. The hash is generated by taking an entry's essential data (the values of the `name`, `date`, `journal_id`, `company_id`, `debit`, `credit`, `account_id`, and `partner_id` fields), concatenating it, and inputting it to the SHA-256 hash function, which then outputs a fixed size (256-bit) string of characters. The hash function is deterministic (:dfn:`the same input always creates the same output`): any minor modification to the original data would completely change the resulting hash. Consequently, the SHA-256 algorithm is often used, among others, for data integrity verification purposes." msgstr "" #: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:17 @@ -8434,7 +8420,7 @@ msgid "You can find additional information about VAT and its mechanism on this p msgstr "" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:20 -#: ../../content/applications/finance/accounting/taxes/avatax.rst:233 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:234 #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:32 msgid "Prerequisites" msgstr "" @@ -8814,7 +8800,7 @@ msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:109 #: ../../content/applications/finance/accounting/taxes.rst:124 #: ../../content/applications/finance/accounting/taxes.rst:268 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:397 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:400 msgid "Total" msgstr "" @@ -9247,7 +9233,7 @@ msgid "but we want to sell it at 10€, tax included, in our shops or eCommerce msgstr "" #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:99 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:573 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:575 msgid "eCommerce" msgstr "" @@ -9348,24 +9334,23 @@ msgid "*AvaTax* accounts for location-based tax rates for each state, county, an msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:25 -msgid "Some limitations exist in Odoo while using *AvaTax* for tax calculation:" +msgid "Some limitations exist in Odoo while using AvaTax for tax calculation:" msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:27 -msgid "*AvaTax* is **not** supported in Odoo's *Point of Sale* app, because a dynamic tax calculation model is excessive for transactions within a single delivery address, such as stores or restaurants." +msgid "AvaTax is **not** supported in Odoo's **Point of Sale** app, because a dynamic tax calculation model is excessive for transactions within a single delivery address, such as stores or restaurants." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:30 -msgid "*AvaTax* and Odoo use the company address and **not** the warehouse address." +msgid "AvaTax and Odoo use the company address, **not** the warehouse address." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:31 -msgid "Exercise tax is **not** supported. This includes tobacco/vape taxes, fuel taxes, and other specific industries." +msgid "Excise tax is **not** supported. This includes tobacco/vape taxes, fuel taxes, and other specific industries." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:35 -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:266 -msgid "Avalara's support documents: `About AvaTax `_" +msgid "Avalara's support documents: `About AvaTax `_" msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:39 @@ -9381,7 +9366,7 @@ msgid "Upon account setup, take note of the *AvaTax* :guilabel:`Account ID`. Thi msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:49 -msgid "Then, `create a basic company profile `_." +msgid "Then, `create a basic company profile `_." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:53 @@ -9393,23 +9378,23 @@ msgid "Collect essential business details for the next step: locations where tax msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:59 -msgid "`Add company information `_." +msgid "`Add company information `_." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:61 -msgid "`Tell us where the company collects and pays tax `_." +msgid "`Tell us where the company collects and pays tax `_." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:63 -msgid "`Verify jurisdictions and activate the company `_." +msgid "`Verify jurisdictions and activate the company `_." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:65 -msgid "`Add other company locations for location-based filing `_." +msgid "`Add other company locations for location-based filing `_." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:67 -msgid "`Add a marketplace to the company profile `_." +msgid "`Add a marketplace to the company profile `_." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:73 @@ -9449,7 +9434,7 @@ msgid "If this is an additional license key, ensure the previous connection can msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:104 -msgid "Copy this key to a safe place. It is **strongly encouraged** to backup the license key for future reference. This key cannot be retrieved after leaving this screen." +msgid "Copy this key to a safe place. It is strongly encouraged to back up the license key for future reference. This key **cannot** be retrieved after leaving this screen." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:108 @@ -9514,7 +9499,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:40 #: ../../content/applications/finance/fiscal_localizations/chile.rst:30 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:33 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:46 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:48 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:16 #: ../../content/applications/finance/fiscal_localizations/france.rst:187 #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:14 @@ -9527,7 +9512,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:15 #: ../../content/applications/finance/fiscal_localizations/thailand.rst:14 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:16 -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:14 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:16 #: ../../content/applications/finance/fiscal_localizations/united_states.rst:62 msgid "Name" msgstr "" @@ -9538,7 +9523,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:41 #: ../../content/applications/finance/fiscal_localizations/chile.rst:31 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:34 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:47 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:49 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:17 #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:15 #: ../../content/applications/finance/fiscal_localizations/india.rst:17 @@ -9550,7 +9535,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:16 #: ../../content/applications/finance/fiscal_localizations/thailand.rst:15 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:17 -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:15 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:17 #: ../../content/applications/finance/fiscal_localizations/united_states.rst:63 msgid "Technical name" msgstr "" @@ -9563,7 +9548,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:42 #: ../../content/applications/finance/fiscal_localizations/chile.rst:32 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:48 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:50 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:18 #: ../../content/applications/finance/fiscal_localizations/france.rst:64 #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:16 @@ -9576,7 +9561,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:17 #: ../../content/applications/finance/fiscal_localizations/thailand.rst:16 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:18 -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:16 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:18 #: ../../content/applications/finance/fiscal_localizations/united_states.rst:64 msgid "Description" msgstr "" @@ -9718,15 +9703,19 @@ msgstr "" msgid ":doc:`../../fiscal_localizations/brazil`" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:217 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:213 +msgid ":doc:`../../fiscal_localizations/united_states`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:218 msgid "Odoo AvaTax settings" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:219 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:220 msgid "To integrate the *AvaTax* :abbr:`API (application programming interface)` with Odoo, go to :menuselection:`Accounting app --> Configuration --> Settings` section. The :guilabel:`AvaTax` fields in the :guilabel:`Taxes` section is where the *AvaTax* configurations are made, and the credentials are entered in." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:224 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:225 msgid "First, tick the checkbox to the left of the :guilabel:`AvaTax` settings, to activate *AvaTax* on the database. This is a quick, convenient way to activate and deactivate *AvaTax* tax calculation on the Odoo database." msgstr "" @@ -9734,35 +9723,35 @@ msgstr "" msgid "Configure AvaTax settings" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:235 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:236 msgid "First, select the :guilabel:`Environment` in which the company wishes to use *AvaTax* in. It can either be :guilabel:`Sandbox` or :guilabel:`Production`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:239 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:240 msgid "For help determining which *AvaTax* environment to use (either :guilabel:`Production` or :guilabel:`Sandbox`), visit: `Sandbox vs Production environments `_." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:244 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:245 msgid "Credentials" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:246 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:247 msgid "Now, the credentials can be entered in. The *AvaTax* :guilabel:`Account ID` should be entered in the :guilabel:`API ID` field, and the :guilabel:`License Key` should be entered in the :guilabel:`API Key` field." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:251 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:252 msgid "The :guilabel:`Account ID` can be found by logging into the *AvaTax* portal (`sandbox `_ or `production `_). In the upper-right corner, click on the initials of the user and :guilabel:`Account`. The :guilabel:`Account ID` is listed first." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:256 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:257 msgid "To access the :guilabel:`License Key` see this documentation: :ref:`avatax/create_avalara_credentials`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:259 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:260 msgid "For the :guilabel:`Company Code` field, enter the Avalara company code for the company being configured. Avalara interprets this as `DEFAULT`, if it is not set. The :guilabel:`Company Code` can be accessed in the Avalara management portal." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:263 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:264 msgid "First, log into the *AvaTax* portal (`sandbox `_ or `production `_). Then, navigate to :menuselection:`Settings --> Manage Companies`. The :guilabel:`Company Code` value is located in the row of the :guilabel:`Company` in the :guilabel:`Company Code` column." msgstr "" @@ -9770,51 +9759,51 @@ msgstr "" msgid "AvaTax company code highlighted on the company details page." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:273 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:274 msgid "Transaction options" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:275 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:276 msgid "There are two transactional settings in the Odoo *AvaTax* settings that can be configured: :guilabel:`Use UPC` and :guilabel:`Commit Transactions`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:278 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:279 msgid "If the checkbox next to :guilabel:`Use UPC` is ticked, the transactions will use Universal Product Codes (UPC), instead of custom defined codes in Avalara. Consult a certified public accountant (CPA) for specific guidance." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:282 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:283 msgid "Should the :guilabel:`Commit Transactions` checkbox be ticked, then, the transactions in the Odoo database will be committed for reporting in *AvaTax*." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:286 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:287 msgid "Address validation" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:288 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:289 msgid "The *Address Validation* feature ensures that the most up-to-date address by postal standards is set on a contact in Odoo. This is important to provide accurate tax calculations for customers." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:292 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:293 msgid "The :guilabel:`Address Validation` feature only works with partners/customers in North America." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:294 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:295 msgid "Additionally, tick the checkbox next to the :guilabel:`Address validation` field." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:297 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:298 msgid "For accurate tax calculations, it is best practice to enter a complete address for the contacts saved in the database. However, *AvaTax* can still function by implementing a best effort attempt using only the :guilabel:`Country`, :guilabel:`State`, and :guilabel:`Zip code`. These are the three minimum required fields." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:302 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:303 msgid ":guilabel:`Save` the settings to implement the configuration." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:305 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:306 msgid "Manually :guilabel:`Validate` the address by navigating to the :menuselection:`Contacts app`, and selecting a contact. Now that the *AvaTax* module has been configured on the database, a :guilabel:`Validate` button appears directly below the :guilabel:`Address`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:309 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:310 msgid "Click :guilabel:`Validate`, and a pop-up window appears with a :guilabel:`Validated Address` and :guilabel:`Original Address` listed. If the :guilabel:`Validated Address` is the correct mailing address for tax purposes, click :guilabel:`Save Validated`." msgstr "" @@ -9823,89 +9812,89 @@ msgid "Validate address pop-up window in Odoo with \"Save Validated\" button and "Address\" highlighted." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:319 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:320 msgid "All previously-entered addresses for contacts in the Odoo database will need to be validated using the manually validate process outlined above. Addresses are not automatically validated if they were entered previously. This only occurs upon tax calculation." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:324 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:325 msgid "Test connection" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:326 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:327 msgid "After entering all the above information into the *AvaTax* setup on Odoo, click :guilabel:`Test connection`. This ensures the :guilabel:`API ID` and :guilabel:`API KEY` are correct, and a connection is made between Odoo and the *AvaTax* application programming interface (API)." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:331 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:332 msgid "Sync parameters" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:333 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:334 msgid "Upon finishing the configuration and settings of the *AvaTax* section, click the :guilabel:`Sync Parameters` button. This action synchronizes the exemption codes from *AvaTax*." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:341 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:342 msgid "Next, navigate to :menuselection:`Accounting app --> Configuration --> Accounting: Fiscal Positions`. A :guilabel:`Fiscal Position` is listed named, :guilabel:`Automatic Tax Mapping (AvaTax)`. Click it to open *AvaTax's* fiscal position configuration page." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:345 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:346 msgid "Here, ensure that the :guilabel:`Use AvaTax API` checkbox is ticked." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:347 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:348 msgid "Optionally, tick the checkbox next to the field labeled: :guilabel:`Detect Automatically`. Should this option be ticked, then, Odoo will automatically apply this :guilabel:`Fiscal Position` for transactions in Odoo." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:351 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:352 msgid "Enabling :guilabel:`Detect Automatically` also makes specific parameters, such as :guilabel:`VAT required`, :guilabel:`Foreign Tax ID`, :guilabel:`Country Group`, :guilabel:`Country`, :guilabel:`Federal States`, or :guilabel:`Zip Range` appear. Filling these parameters filters the :guilabel:`Fiscal Position` usage. Leaving them blank ensures all calculations are made using this :guilabel:`Fiscal Position`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:358 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:359 msgid "Should the :guilabel:`Detect Automatically` checkbox not be ticked, each customer will need to have the :guilabel:`Fiscal Position` set on their :guilabel:`Sales and Purchase` tab of the contact record. To do so, navigate to :menuselection:`Sales app --> Order --> Customers`, or :menuselection:`Contacts app --> Contacts`. Then, select a customer or contact to set the fiscal position on." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:364 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:365 msgid "Navigate to the :guilabel:`Sales and Purchase` tab, and down to the section labeled, :guilabel:`Fiscal Position`. Set the :guilabel:`Fiscal Position` field to the fiscal position for the customer." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:369 -#: ../../content/applications/finance/accounting/taxes/avatax.rst:430 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:370 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:431 #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:39 msgid ":doc:`fiscal_positions`" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:372 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:373 msgid "AvaTax accounts" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:374 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:375 msgid "Upon selecting the checkbox option for :guilabel:`Use AvaTax API` a new :guilabel:`AvaTax` tab appears. Click into this tab to reveal two different settings." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:377 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:378 msgid "The first setting is the :guilabel:`AvaTax Invoice Account`, while the second is, :guilabel:`AvaTax Refund Account`. Ensure both accounts are set for smooth end-of-year record keeping. Consult a certified public accountant (CPA) for specific guidance on setting both accounts." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:381 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:382 msgid "Click :guilabel:`Save` to implement the changes." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:384 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:385 msgid "Tax mapping" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:386 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:387 msgid "The *AvaTax* integration is available on sale orders and invoices with the included *AvaTax* fiscal position." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:390 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:391 msgid "Additionally, there is a :guilabel:`Tax Mapping` tab and :guilabel:`Account Mapping` tab in the :guilabel:`Automatic Tax Mapping (AvaTax)` fiscal position, where mapping for products can also be configured. To access :guilabel:`Fiscal Positions` navigate to :menuselection:`Accounting app --> Configuration --> Accounting: Fiscal Positions`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:396 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:397 msgid "Product category mapping" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:398 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:399 msgid "Before using the integration, specify an :guilabel:`Avatax Category` on the product categories. Navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`. Select the product category to add the :guilabel:`AvaTax Category` to. In the :guilabel:`AvaTax Category` field, select a category from the drop-down menu, or :guilabel:`Search More...` to open the complete list of options." msgstr "" @@ -9913,15 +9902,15 @@ msgstr "" msgid "Specify AvaTax Category on products." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:409 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:410 msgid "Product mapping" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:411 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:412 msgid "*AvaTax* Categories may be set on individual products, as well. To set the :guilabel:`Avatax Category` navigate to :menuselection:`Inventory app --> Products --> Products`. Select the product to add the :guilabel:`Avatax Category` to. Under the :guilabel:`General Information` tab, on the far-right, is a selector field labeled: :guilabel:`Avatax Category`. Finally, click the drop-down menu, and select a category, or :guilabel:`Search More...` to find one that is not listed." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:418 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:419 msgid "If both the product, and its category, have an :guilabel:`AvaTax Category` set, the product's :guilabel:`AvaTax Category` takes precedence." msgstr "" @@ -9929,19 +9918,19 @@ msgstr "" msgid "Override product categories as needed." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:426 -msgid "Mapping an :guilabel:`AvaTax Category` on either the *Product* or *Product Category* should be completed for every *Product* or *Product Category*, depending the route that is chosen." -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/avatax.rst:431 -msgid ":doc:`avatax/avatax_use`" +#: ../../content/applications/finance/accounting/taxes/avatax.rst:427 +msgid "Mapping an :guilabel:`AvaTax Category` on either the *Product* or *Product Category* should be completed for every *Product* or *Product Category*, depending on the route that is chosen." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:432 -msgid ":doc:`avatax/avalara_portal`" +msgid ":doc:`avatax/avatax_use`" msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:433 +msgid ":doc:`avatax/avalara_portal`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:434 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:258 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:163 msgid "`US Tax Compliance: Avatax elearning video `_" @@ -10158,7 +10147,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:1019 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:85 #: ../../content/applications/finance/fiscal_localizations/spain.rst:42 -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:272 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:269 msgid "Reports" msgstr "" @@ -10909,8 +10898,8 @@ msgstr "" #: ../../content/applications/finance/accounting/vendor_bills.rst:5 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:592 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:570 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:700 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:710 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:699 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:768 #: ../../content/applications/finance/fiscal_localizations/italy.rst:119 msgid "Vendor bills" msgstr "" @@ -11582,7 +11571,7 @@ msgid "Expenses" msgstr "" #: ../../content/applications/finance/expenses.rst:7 -msgid "Odoo **Expenses** streamlines the management of expenses. After an employee submits their expenses in Odoo, the expenses are reviewed by management and accounting teams. Once approved, payments can then be processed and disbursed back to the employee for reimbursement(s)." +msgid "Odoo **Expenses** streamlines the management of expenses. After an employee submits their expenses in Odoo, they are reviewed by management and accounting teams. Once approved, payments can then be processed, and disbursed back to the employee for reimbursement." msgstr "" #: ../../content/applications/finance/expenses.rst:12 @@ -11615,7 +11604,7 @@ msgid "Only two fields are required, the :guilabel:`Product Name` and the :guila msgstr "" #: ../../content/applications/finance/expenses.rst:40 -msgid "The *Sales* app is where specification on the units of measure are created and edited (e.g. units, miles, nights, etc.). Go to :menuselection:`Sales app --> Configuration --> Settings` and ensure `Units of Measure` is enabled in the `Product Catalog` section. Click on the :guilabel:`Units of Measure` internal link to :doc:`view, create, and edit the units of measure <../inventory_and_mrp/inventory/product_management/product_replenishment/uom>`." +msgid "The *Sales* app is where specification on the units of measure are created and edited (e.g. units, miles, nights, etc.). Go to :menuselection:`Sales app --> Configuration --> Settings` and ensure `Units of Measure` is enabled in the `Product Catalog` section. Click on the :guilabel:`Units of Measure` internal link to :doc:`view, create, and edit the units of measure <../inventory_and_mrp/inventory/product_management/configure/uom>`." msgstr "" #: ../../content/applications/finance/expenses.rst:50 @@ -11631,19 +11620,19 @@ msgid "Here are some examples for when to set a specific :guilabel:`Cost` on a p msgstr "" #: ../../content/applications/finance/expenses.rst:65 -msgid "**Meals**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an expense for a meal, they enter the actual amount of the bill and will be reimbursed for that amount. An expense for a meal costing $95.23 would equal a reimbursement for $95.23." +msgid "**Meals**: set the :guilabel:`Cost` to `0.00`. When an employee logs an expense for a meal, they enter the actual amount of the bill and will be reimbursed for that amount. An expense for a meal costing $95.23 would equal a reimbursement for $95.23." msgstr "" #: ../../content/applications/finance/expenses.rst:68 -msgid "**Mileage**: Set the :guilabel:`Cost` to `0.30`. When an employee logs an expense for \"mileage\", they enter the number of miles driven in the :guilabel:`Quantity` field, and are reimbursed 0.30 per mile they entered. An expense for 100 miles would equal a reimbursement for $30.00." +msgid "**Mileage**: set the :guilabel:`Cost` to `0.30`. When an employee logs an expense for \"mileage\", they enter the number of miles driven in the :guilabel:`Quantity` field, and are reimbursed 0.30 per mile they entered. An expense for 100 miles would equal a reimbursement for $30.00." msgstr "" #: ../../content/applications/finance/expenses.rst:72 -msgid "**Monthly Parking**: Set the :guilabel:`Cost` to `75.00`. When an employee logs an expense for \"monthly parking\", the reimbursement would be for $75.00." +msgid "**Monthly Parking**: set the :guilabel:`Cost` to `75.00`. When an employee logs an expense for \"monthly parking\", the reimbursement would be for $75.00." msgstr "" #: ../../content/applications/finance/expenses.rst:74 -msgid "**Expenses**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an expense that is not a meal, mileage, or monthly parking, they use the generic :guilabel:`Expenses` product. An expense for a laptop costing $350.00 would be logged as an :guilabel:`Expenses` product, and the reimbursement would be for $350.00." +msgid "**Expenses**: set the :guilabel:`Cost` to `0.00`. When an employee logs an expense that is not a meal, mileage, or monthly parking, they use the generic :guilabel:`Expenses` product. An expense for a laptop costing $350.00 would be logged as an :guilabel:`Expenses` product, and the reimbursement would be for $350.00." msgstr "" #: ../../content/applications/finance/expenses.rst:79 @@ -11654,579 +11643,948 @@ msgstr "" msgid "Set a tax on each product in the :guilabel:`Vendor Taxes` and :guilabel:`Customer Taxes` fields, if applicable. It is considered good practice to use a tax that is configured with :ref:`Tax Included in Price `. Taxes will be automatically configured if this is set." msgstr "" +#: ../../content/applications/finance/expenses.rst:88 +msgid ":doc:`expenses/log_expenses`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:89 +msgid ":doc:`expenses/expense_reports`" +msgstr "" + #: ../../content/applications/finance/expenses.rst:90 -msgid "Record expenses" +msgid ":doc:`expenses/post_expenses`" msgstr "" -#: ../../content/applications/finance/expenses.rst:93 -msgid "Manually create a new expense" +#: ../../content/applications/finance/expenses.rst:91 +msgid ":doc:`expenses/reimburse`" msgstr "" -#: ../../content/applications/finance/expenses.rst:95 -msgid "To record a new expense, begin in the main :menuselection:`Expenses` app dashboard, which presents the default :guilabel:`My Expenses` view. This view can also be accessed from :menuselection:`Expenses app --> My Expenses --> My Expenses`." +#: ../../content/applications/finance/expenses.rst:92 +msgid ":doc:`expenses/reinvoice_expenses`" msgstr "" -#: ../../content/applications/finance/expenses.rst:99 -msgid "First, click :guilabel:`New`, and then fill out the various fields on the form." +#: ../../content/applications/finance/expenses/approve_expenses.rst:3 +msgid "Approve expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:101 -msgid ":guilabel:`Description`: Enter a short description for the expense in the :guilabel:`Description` field. This should be short and informative, such as `lunch with client` or `hotel for conference`." +#: ../../content/applications/finance/expenses/approve_expenses.rst:5 +msgid "In Odoo, not just anyone can approve expense reports, only users with the necessary rights (or permissions) can. This means that a user **must** have at least *Team Approver* rights for the *Expenses* app. Employees with the necessary rights can review expense reports, approve or reject them, and provide feedback thanks to the integrated communication tool." msgstr "" -#: ../../content/applications/finance/expenses.rst:104 -msgid ":guilabel:`Category`: Select the expense category from the drop-down menu that most closely corresponds to the expense. For example, an airplane ticket would be appropriate for an expense :guilabel:`Category` named :guilabel:`Air Travel`." +#: ../../content/applications/finance/expenses/approve_expenses.rst:10 +msgid "Please refer to the :doc:`access rights documentation ` to learn more about managing users and their access rights." msgstr "" -#: ../../content/applications/finance/expenses.rst:107 +#: ../../content/applications/finance/expenses/approve_expenses.rst:14 +msgid "View expense reports" +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:16 +msgid "Users who are able to approve expense reports, typically managers, can easily view all expense reports they have access rights to. Go to :menuselection:`Expenses app --> Expense Reports`, to view the :guilabel:`All Reports` dashboard." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:20 +msgid "A list of all expense reports with a status of either :guilabel:`To Submit`, :guilabel:`Submitted`, :guilabel:`Approved`, :guilabel:`Posted`, or :guilabel:`Done` appears. Expense reports with a status of :guilabel:`Refused` are hidden, by default." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:-1 +msgid "Reports to validate are found on the Reports to Approve page." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:29 +msgid "Approve expense reports" +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:31 +msgid "Expense reports can be approved in two ways: :ref:`individually ` or :ref:`in bulk `." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:35 +msgid "Only reports with a status of :guilabel:`Submitted` can be approved." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:37 +msgid "It is recommended to display only :guilabel:`Submitted` reports by ticking the checkbox beside the :guilabel:`Submitted` filter, in the left column, under the :guilabel:`Status` section." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:40 +msgid "If a report is **not** able to be approved, the :guilabel:`Approve Report` button **does not** appear on the :guilabel:`All Reports` page." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:46 +msgid "Approve individual reports" +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:48 +msgid "To approve an individual report, navigate to :menuselection:`Expenses app --> Expense Reports`, and click on an individual report to view the report form." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:51 +msgid "From here, several options are presented: :guilabel:`Approve`, :guilabel:`Refuse`, and :guilabel:`Reset to draft`." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:54 +msgid "Click :guilabel:`Approve` to approve the report." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:59 +msgid "Approve multiple reports" +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:61 +msgid "To approve multiple expense reports at once, first navigate to :menuselection:`Expenses app --> Expense Reports` to view a list of expense reports. Next, select the reports to approve by ticking the checkbox next to each report being approved, or tick the checkbox next to the :guilabel:`Employee` column title to select all the reports in the list." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:66 +msgid "Next, click the :guilabel:`Approve Report` button." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:-1 +msgid "Approve multiple reports by clicking the checkboxes next to each report." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:73 +msgid "It is possible for team managers to view all the expense reports for just their team members." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:75 +msgid "To do so, while on the :guilabel:`All Reports` page, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` to the right of the search bar, then click :guilabel:`My Team` in the :icon:`fa-filter` :guilabel:`Filters` section." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:79 +msgid "This presents all the reports for only the manager's team." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:0 +msgid "Select the My Team filter." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:86 +msgid "Refuse expense reports" +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:88 +msgid "Expense reports can **only** be refused on the individual expense report, and **not** from the :guilabel:`All Reports` dashboard. To open an individual expense report, navigate to :menuselection:`Expenses app --> Expense Reports`, then click on an individual expense report to view the report form." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:93 +msgid "If more information is needed, such as a missing receipt, communicate any necessary information requests in the *chatter* of the report form. On the individual expense report, click :guilabel:`Send message` to open a message text box." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:97 +msgid "Type in a message, tagging the proper people, and post it to the *chatter* by clicking :guilabel:`Send`. The message is posted in the chatter, and the tagged people are notified, via email." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:102 +msgid "The only people that can be tagged in a message are *followers* of the specific report. To see who is a follower, click the :icon:`fa-user-o` :guilabel:`(user)` icon to display the followers of the expense report." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:0 +#: ../../content/applications/finance/expenses/approve_expenses.rst:-1 +msgid "Send messages in the chatter." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:110 +msgid "To refuse an expense report, click :guilabel:`Refuse`, and a :guilabel:`Refuse Expense` pop-up window appears. Enter a brief explanation for the refusal beneath the :guilabel:`REASON TO REFUSE EXPENSE` field, then click :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/finance/expenses/approve_expenses.rst:118 +msgid "Once the expense report is refused, the status changes to :guilabel:`Refused`, and the only button that appears in the top-left is :guilabel:`Reset to Draft`." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:3 +msgid "Expense reports" +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:5 +msgid "When expenses are ready to submit (such as, at the end of a business trip, or once a month), an *expense report* needs to be created. Open the main :menuselection:`Expenses app` dashboard, which displays the :guilabel:`My Expenses` dashboard, by default. Alternatively, navigate to :menuselection:`Expenses app --> My Expenses --> My Expenses`." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:10 +msgid "Expenses are color-coded by status. Any expense with a status of :guilabel:`To Report` (expenses that still need to be added to an expense report) is shown in blue text. All other statuses (:guilabel:`To Submit`, :guilabel:`Submitted`, and :guilabel:`Approved`) the text appears in black." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:17 +msgid "Create expense reports" +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:19 +msgid "First, select each desired expense to be added to the report on the :guilabel:`My Expenses` dashboard, by ticking the checkbox next to each entry, or quickly select all the expenses in the list by ticking the checkbox next to the :guilabel:`Expense Date` column title, if needed." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:23 +msgid "Another way to quickly add all expenses that are not on a expense report, is to click the :guilabel:`Create Report` button, *without* selecting any expenses, and Odoo automatically selects all expenses with a status of :guilabel:`To Submit` that are not already on a report." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:-1 +msgid "Select the expenses to submit, then create the report." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:32 +msgid "Any expense can be selected from the :guilabel:`My Expenses` list, except for expenses with a status of :guilabel:`Approved`." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:35 +msgid "The :guilabel:`Create Report` button is visible as long as there is a minimum of one expense on the list with a status of either :guilabel:`To Report` or :guilabel:`To Submit`." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:38 +msgid "When the :guilabel:`Create Report` button is clicked, all expenses with a status of :guilabel:`To Submit` that are *not* currently on another expense report appears in the newly-created expense report." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:42 +msgid "If all expenses on the :guilabel:`My Expenses` report are already associated with another expense report, an :guilabel:`Invalid Operation` pop-up window appears, stating :guilabel:`You have no expenses to report.`" +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:46 +msgid "Once the expenses have been selected, click the :guilabel:`Create Report` button. The new report appears with all the expenses listed in the :guilabel:`Expense` tab. If there is a receipt attached to an individual expense, a :icon:`fa-paperclip` :guilabel:`(paperclip)` icon appears between the :guilabel:`Customer to Reinvoice` and :guilabel:`Analytic Distribution` columns." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:51 +msgid "When the report is created, the date range for the expenses appears in the :guilabel:`Expense Report Summary` field, by default. It is recommended to edit this field with a short summary for each report to help keep expenses organized. Enter a description for the expense report, such as `Client Trip NYC`, or `Office Supplies for Presentation`, in the :guilabel:`Expense Report Summary` field." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:56 +msgid "The :guilabel:`Employee`, :guilabel:`Paid By`, and :guilabel:`Company` fields autopoulate with the information listed on the individual expenses." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:59 +msgid "Next, select a :guilabel:`Manager` from the drop-down menu to assign a manager to review the report. If needed, update the :guilabel:`Journal` field, using the drop-down menu." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:-1 +msgid "Enter a short description and select a manager for the report." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:66 +msgid "If some expenses are missing from the report, they can still be added from this report form. To do so, click :guilabel:`Add a line` at the bottom of the :guilabel:`Expense` tab." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:69 +msgid "An :guilabel:`Add: Expense Lines` pop-up window appears, displaying all the available expenses (with a :guilabel:`To Submit` status) that can be added to the report." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:72 +msgid "If a new expense needs to be added that does **not** appear on the list, click :guilabel:`New` to :doc:`create a new expense <../expenses/log_expenses>` and add it to the report." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:75 +msgid "Tick the checkbox next to each expense being added, then click :guilabel:`Select`." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:77 +msgid "Doing so removes the pop-up window, and the items now appear on the report." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:-1 +msgid "Add more expenses to the report before submitting." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:84 +msgid "Expense reports can be created in one of three places:" +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:86 +msgid "Navigate to the main :menuselection:`Expenses app` dashboard (also accessible, via :menuselection:`Expenses app --> My Expenses --> My Expenses`)" +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:88 +msgid "Navigate to :menuselection:`Expenses app --> My Expenses --> My Reports`" +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:89 +msgid "Navigate to :menuselection:`Expenses app --> Expense Reports`" +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:91 +msgid "In any of these views, click :guilabel:`New` to create a new expense report." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:96 +msgid "Submit expense reports" +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:98 +msgid "When an expense report is completed, the next step is to submit the report to a manager for approval. To view all expense reports, navigate to :menuselection:`Expenses app --> My Expenses --> My Reports`. Open the specific report from the list of expense reports." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:103 +msgid "Reports must be individually submitted, and **cannot** be submitted in batches." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:105 +msgid "If the list is large, grouping the results by status may be helpful, since only reports with a :guilabel:`To Submit` status need to be submitted; reports with an :guilabel:`Approved` or :guilabel:`Submitted` status do not." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:109 +msgid "The :guilabel:`To Submit` expenses are identifiable by the :guilabel:`To Submit` status, and by the blue text, while all other expense text appears in black." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:-1 +msgid "Submit the report to the manager." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:117 +msgid "The status of each report is shown in the :guilabel:`Status` column. If the :guilabel:`Status` column is not visible, click the :icon:`oi-settings-adjust` :guilabel:`(additional options)` icon at the end of the row, and tick the checkbox beside :guilabel:`Status` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:122 +msgid "Click on a report to open it, then click :guilabel:`Submit To Manager`. After submitting a report, the next step is to wait for the manager to approve it." +msgstr "" + +#: ../../content/applications/finance/expenses/expense_reports.rst:126 +msgid ":doc:`Approving <../expenses/approve_expenses>` expenses, :doc:`posting <../expenses/post_expenses>` expenses, and :doc:`reimbursing <../expenses/reimburse>` expenses are **only** for users with the appropriate :doc:`access rights documentation `." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:3 +msgid "Log expenses" +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:5 +msgid "Before expenses can be reimbursed, each individual expense needs to be logged in the database. Expense records can be created in three different ways: :ref:`manually enter an expense record `, :ref:`upload a receipt `, or :ref:`email a receipt ` to a preconfigured email address." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:13 +msgid "Manually enter expenses" +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:15 +msgid "To record a new expense, open the :menuselection:`Expenses app`, which displays the :guilabel:`My Expenses` page, by default." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:19 +msgid "This view can also be accessed from :menuselection:`Expenses app --> My Expenses --> My Expenses`." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:22 +msgid "Then, click :guilabel:`New`, and then fill out the following fields on the form that appears:" +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:24 +msgid ":guilabel:`Description`: Enter a short description for the expense. This should be concise and informative, such as `lunch with client` or `hotel for conference`." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:26 +msgid ":guilabel:`Category`: Select the expense category from the drop-down menu that most closely corresponds to the expense." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:28 msgid ":guilabel:`Total`: Enter the total amount paid for the expense in one of two ways:" msgstr "" -#: ../../content/applications/finance/expenses.rst:109 -msgid "If the expense is for one single item/expense, and the category selected was for a single item, enter the cost in the :guilabel:`Total` field (the :guilabel:`Quantity` field is hidden)." +#: ../../content/applications/finance/expenses/log_expenses.rst:30 +msgid "If the expense is for a single item/expense, and the category selected was for a single item, enter the cost in the :guilabel:`Total` field (the :guilabel:`Quantity` field is hidden)." msgstr "" -#: ../../content/applications/finance/expenses.rst:111 -msgid "If the expense is for multiples of the same item/expense with a fixed price, the :guilabel:`Unit Price` is displayed. Enter the quantity in the :guilabel:`Quantity` field, and the total cost is automatically updated with the correct total (the :guilabel:`Unit Price` x the :guilabel:`Quantity` = the total). Be advised, the word \"total\" does not appear, the total cost simply appears below the :guilabel:`Quantity`." +#: ../../content/applications/finance/expenses/log_expenses.rst:32 +msgid "If the expense is for multiples of the same item/expense with a fixed price, the :guilabel:`Unit Price` is displayed. Enter the quantity in the :guilabel:`Quantity` field, and the total cost is automatically updated with the correct total. The total cost appears below the :guilabel:`Quantity`." msgstr "" -#: ../../content/applications/finance/expenses.rst:118 -msgid "For example, in the case of mileage driven, the :guilabel:`Unit Price` is populated as the cost *per mile*. Set the :guilabel:`Quantity` to the *number of miles* driven, and the total is calculated." +#: ../../content/applications/finance/expenses/log_expenses.rst:38 +msgid "In the case of mileage driven, the :guilabel:`Unit Price` is populated as the cost *per mile*. Set the :guilabel:`Quantity` to the *number of miles driven*, and the total is calculated." msgstr "" -#: ../../content/applications/finance/expenses.rst:122 +#: ../../content/applications/finance/expenses/log_expenses.rst:42 msgid ":guilabel:`Included Taxes`: If taxes were configured on the expense category, the tax percentage and amount appear automatically after entering either the :guilabel:`Total` or the :guilabel:`Quantity`." msgstr "" -#: ../../content/applications/finance/expenses.rst:127 -msgid "When a tax is configured on an expense category, the :guilabel:`Included Taxes` value will update in real time as the :guilabel:`Total` or :guilabel:`Quantity` is updated." +#: ../../content/applications/finance/expenses/log_expenses.rst:47 +msgid "When a tax is configured on an expense category, the :guilabel:`Included Taxes` value updates in real time, as the :guilabel:`Total` or :guilabel:`Quantity` is updated." msgstr "" -#: ../../content/applications/finance/expenses.rst:130 +#: ../../content/applications/finance/expenses/log_expenses.rst:50 msgid ":guilabel:`Employee`: Using the drop-down menu, select the employee this expense is for." msgstr "" -#: ../../content/applications/finance/expenses.rst:131 -msgid ":guilabel:`Paid By`: Click the radio button to indicate who paid for the expense and should be reimbursed. If the employee paid for the expense (and should be reimbursed) select :guilabel:`Employee (to reimburse)`. If the company paid directly instead (e.g. if the company credit card was used to pay for the expense) select :guilabel:`Company`. Depending on the expense category selected, this field may not appear." +#: ../../content/applications/finance/expenses/log_expenses.rst:51 +msgid ":guilabel:`Paid By`: Click the radio button to indicate who paid for the expense, and should be reimbursed. Select either :guilabel:`Employee (to reimburse)` or :guilabel:`Company`. Depending on the expense category selected, this field may not appear." msgstr "" -#: ../../content/applications/finance/expenses.rst:136 -msgid ":guilabel:`Bill Reference`: If there is any reference text that should be included for the expense, enter it in this field." +#: ../../content/applications/finance/expenses/log_expenses.rst:54 +msgid ":guilabel:`Expense Date`: Using the calendar popover window that appears when this field is clicked, enter the date the expense was incurred." msgstr "" -#: ../../content/applications/finance/expenses.rst:138 -msgid ":guilabel:`Expense Date`: Using the calendar module, enter the date the expense was incurred. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows to navigate to the correct month, then click on the specific day to enter the selection." +#: ../../content/applications/finance/expenses/log_expenses.rst:56 +msgid ":guilabel:`Account`: Using the drop-down menu, select the expense account the expense should be logged in." msgstr "" -#: ../../content/applications/finance/expenses.rst:141 -msgid ":guilabel:`Account`: Select the expense account that this expense should be logged on from the drop-down menu." +#: ../../content/applications/finance/expenses/log_expenses.rst:58 +msgid ":guilabel:`Customer to Reinvoice`: If the expense is something that should be paid for by a customer, select the :abbr:`SO (Sales Order)` and customer that should be invoiced for this expense from the drop-down menu. All sales orders in the drop-down menu list both the :abbr:`SO (Sales Order)`, as well as the company the sales order is written for. After the expense is saved, the customer name disappears, and only the :abbr:`SO (Sales Order)` is visible on the expense." msgstr "" -#: ../../content/applications/finance/expenses.rst:143 -msgid ":guilabel:`Customer to Reinvoice`: If the expense is something that should be paid for by a customer, select the :abbr:`SO (Sales Order)` and customer that will be invoiced for this expense from the drop-down menu. All sales orders in the drop-down menu list both the :abbr:`SO (Sales Order)` as well as the company the sales order is written for, but after the expense is saved, the customer name disappears and only the :abbr:`SO (Sales Order)` is visible on the expense." +#: ../../content/applications/finance/expenses/log_expenses.rst:65 +msgid "A customer wishes to have an on-site meeting for the design and installation of a custom garden, and agrees to pay for the expenses associated with it (such as travel, hotel, meals, etc). All expenses tied to that meeting would indicate the sales order for the custom garden (which also references the customer) as the :guilabel:`Customer to Reinvoice`." msgstr "" -#: ../../content/applications/finance/expenses.rst:150 -msgid "A customer wishes to have an on-site meeting for a custom garden (design and installation) and agrees to pay for the expenses associated with it (such as travel, hotel, meals, etc.). All expenses tied to that meeting would indicate the sales order for the custom garden (which also references the customer) as the :guilabel:`Customer to Reinvoice`." +#: ../../content/applications/finance/expenses/log_expenses.rst:70 +msgid ":guilabel:`Analytic Distribution`: Select the account the expense should be written against from the drop-down menu for either :guilabel:`Projects`, :guilabel:`Departments`, or both. Multiple accounts can be listed for each category, if needed. Adjust the percentage for each analytic account by typing in the percentage value next to each account." msgstr "" -#: ../../content/applications/finance/expenses.rst:155 -msgid ":guilabel:`Analytic Distribution`: Select the account(s) the expense should be written against from the drop-down menu for either :guilabel:`Projects`, :guilabel:`Departments`, or both. Multiple accounts can be listed for each category if needed. Adjust the percentage for each analytic account by typing in the percentage value next to the account." +#: ../../content/applications/finance/expenses/log_expenses.rst:74 +msgid ":guilabel:`Company`: If multiple companies are set up, select the company the expense should be filed for from the drop-down menu. The current company automatically populates this field." msgstr "" -#: ../../content/applications/finance/expenses.rst:159 -msgid ":guilabel:`Company`: If multiple companies are set up, select the company this expense should be filed for from the drop-down menu. The current company will automatically populate this field." +#: ../../content/applications/finance/expenses/log_expenses.rst:76 +msgid ":guilabel:`Notes...`: If any notes are needed to clarify the expense, enter them in the notes field." msgstr "" -#: ../../content/applications/finance/expenses.rst:161 -msgid ":guilabel:`Notes...`: If any notes are needed in order to clarify the expense, enter them in the notes field." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:-1 +#: ../../content/applications/finance/expenses/log_expenses.rst:-1 msgid "A filled in expense form for a client lunch." msgstr "" -#: ../../content/applications/finance/expenses.rst:169 -msgid "Attach a receipt" +#: ../../content/applications/finance/expenses/log_expenses.rst:84 +msgid "Attach receipts" msgstr "" -#: ../../content/applications/finance/expenses.rst:171 -msgid "After the expense is created, the next step is to attach a receipt. Click the :guilabel:`Attach Receipt` button, and a file explorer appears. Navigate to the receipt to be attached, and click :guilabel:`Open`. The new receipt is recorded in the chatter, and the number of receipts will appear next to the :guilabel:`📎 (paperclip)` icon beneath the expense form. More than one receipt can be attached to an individual expense, as needed. The number of receipts attached to the expense will be noted on the paperclip icon." +#: ../../content/applications/finance/expenses/log_expenses.rst:86 +msgid "After the expense record is created, the next step is to attach a receipt. Click the :guilabel:`Attach Receipt` button, and a file explorer appears. Navigate to the receipt to be attached, and click :guilabel:`Open`." msgstr "" -#: ../../content/applications/finance/expenses.rst:-1 +#: ../../content/applications/finance/expenses/log_expenses.rst:90 +msgid "The new receipt is recorded in the *chatter*, and the number of receipts appears next to the :icon:`fa-paperclip` :guilabel:`(paperclip)` icon. Multiple receipts can be attached to an individual expense record, as needed." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:-1 msgid "Attach a receipt and it appears in the chatter." msgstr "" -#: ../../content/applications/finance/expenses.rst:183 -msgid "Create new expenses from a scanned receipt" +#: ../../content/applications/finance/expenses/log_expenses.rst:101 +msgid "Upload expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:185 -msgid "Rather than manually inputting all of the information for an expense, expenses can be created by scanning a PDF receipt." +#: ../../content/applications/finance/expenses/log_expenses.rst:103 +msgid "It is possible to have expense records created automatically, by uploading a PDF receipt. This feature requires the enabling of a setting, and the purchasing of :abbr:`IAP (in-app purchases)` credits." msgstr "" -#: ../../content/applications/finance/expenses.rst:188 -msgid "First, in the main :guilabel:`Expenses` app dashboard view (this view can also be accessed from :menuselection:`Expenses app --> My Expenses --> My Expenses`), click :guilabel:`Scan`, and a file explorer pops up. Navigate to the receipt to be uploaded, click on it to select it, and then click :guilabel:`Open`." +#: ../../content/applications/finance/expenses/log_expenses.rst:108 +msgid "Digitalization settings" msgstr "" -#: ../../content/applications/finance/expenses.rst:-1 +#: ../../content/applications/finance/expenses/log_expenses.rst:110 +msgid "To enable receipt scanning, navigate to :menuselection:`Expenses app --> Configuration --> Settings`, and tick the checkbox beside the :guilabel:`Expense Digitization (OCR)` option. Then, click :guilabel:`Save`. When enabled, additional options appear. Click on the corresponding radio button to select one of the following options:" +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:115 +msgid ":guilabel:`Do not digitize`: turns off receipt digitization." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:116 +msgid ":guilabel:`Digitize on demand only`: only digitizes receipts when requested. A :guilabel:`Digitize document` button appears on expense records. When clicked, the receipt is scanned and the expense record is updated." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:119 +msgid ":guilabel:`Digitize automatically`: automatically digitizes all receipts when they are uploaded." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:121 +msgid "Beneath these options are two additional links. Click the :icon:`fa-arrow-right` :guilabel:`Buy credits` link to purchase credits for receipt digitization. Click the :icon:`fa-arrow-right` :guilabel:`View My Services` link to view a list of all current services, and their remaining credit balances." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:126 +msgid "For more information on document digitization and :abbr:`IAPs (in-app purchases)`, refer to the :doc:`In-app purchase (IAP) <../../essentials/in_app_purchase>` documentation." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:130 +msgid "When the :guilabel:`Expense Digitization (OCR)` option is enabled, a necessary module is installed, so receipts can be scanned. Disabling this option uninstalls the module." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:133 +msgid "If, at some point, there is a desire to temporarily stop digitizing receipts, select the :guilabel:`Do not digitize` option. The reason this option is available is so the module is not uninstalled, allowing for digitization to be enabled in the future by selecting one of the other two options." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:139 +msgid "Upload receipts" +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:141 +msgid "Open the :guilabel:`Expenses app`, and from the :guilabel:`My Expenses` dashboard, click :guilabel:`Upload`, and a file explorer appears. Navigate to the desired receipt, select it, then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:-1 msgid "Create an expense by scanning a receipt. Click Scan at the top of the Expenses dashboard\n" "view." msgstr "" -#: ../../content/applications/finance/expenses.rst:198 -msgid "The receipt is scanned, and a new entry is created with today's date as the :guilabel:`Expense Date`, and any other fields it can populate based on the scanned data, such as the total. Click on the new entry to open the individual expense form, and make any changes needed. The scanned receipt appears in the chatter." +#: ../../content/applications/finance/expenses/log_expenses.rst:150 +msgid "The receipt is scanned, and a new expense record is created. The :guilabel:`Expense Date` field is populated with today's date, along with any other fields based on the scanned data, such as the :guilabel:`Total`." msgstr "" -#: ../../content/applications/finance/expenses.rst:204 -msgid "Automatically create new expenses from an email" +#: ../../content/applications/finance/expenses/log_expenses.rst:154 +msgid "Click on the new entry to open the individual expense form, and make any changes, if needed. The scanned receipt appears in the *chatter*." msgstr "" -#: ../../content/applications/finance/expenses.rst:206 -msgid "Instead of individually creating each expense in the *Expenses* app, expenses can be automatically created by sending an email to an email alias." +#: ../../content/applications/finance/expenses/log_expenses.rst:160 +msgid "Email expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:209 -msgid "To do so, first, an email alias needs to be configured. Go to :menuselection:`Expenses app --> Configuration --> Settings`. Ensure :guilabel:`Incoming Emails` is enabled." +#: ../../content/applications/finance/expenses/log_expenses.rst:162 +msgid "Instead of individually creating each expense in the **Expenses** app, expenses can be automatically created by sending an email to an email alias." msgstr "" -#: ../../content/applications/finance/expenses.rst:-1 -#: ../../content/applications/finance/expenses.rst:0 +#: ../../content/applications/finance/expenses/log_expenses.rst:165 +msgid "To do so, an email alias must first be configured. Navigate to :menuselection:`Expenses app --> Configuration --> Settings`. Ensure the checkbox beside :guilabel:`Incoming Emails` is ticked. The default email alias is *expense@(domain).com*. Change the email alias by entering the desired email in the field to the right of :guilabel:`Alias`. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:-1 +msgid "Te default email that populates the expenses email alias." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:175 +msgid "If the domain alias needs to be set up, :icon:`fa-arrow-right` :guilabel:`Setup your domain alias` appears beneath the :guilabel:`Incoming Emails` checkbox, instead of the email address field." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:-1 +#: ../../content/applications/finance/expenses/log_expenses.rst:0 msgid "Create the domain alias by clicking the link." msgstr "" -#: ../../content/applications/finance/expenses.rst:217 -msgid "If the domain alias needs to be set up, :guilabel:`Setup your domain alias` will appear beneath the incoming emails check box instead of the email address field. Refer to this documentation for setup instructions and more information: :doc:`/applications/websites/website/configuration/domain_names`. Once the domain alias is configured, the email address field will be visible beneath the incoming emails section." +#: ../../content/applications/finance/expenses/log_expenses.rst:183 +msgid "Refer to the :doc:`/applications/websites/website/configuration/domain_names` documentation for setup instructions and more information." msgstr "" -#: ../../content/applications/finance/expenses.rst:223 -msgid "Next, enter the email address to be used in the email field, and then click :guilabel:`Save`. Now that the email address has been entered, emails can be sent to that alias to create new expenses without having to be in the Odoo database." +#: ../../content/applications/finance/expenses/log_expenses.rst:186 +msgid "Once the domain alias is configured, the email address field is visible beneath the :guilabel:`Incoming Emails` feature on the :guilabel:`Settings` page in the **Expenses** app." msgstr "" -#: ../../content/applications/finance/expenses.rst:227 -msgid "To submit an expense via email, create a new email and enter the product's *internal reference* code (if available) and the amount of the expense in the email subject. Next, attach the receipt to the email. Odoo creates the expense by taking the information in the email subject and combining it with the receipt." +#: ../../content/applications/finance/expenses/log_expenses.rst:189 +msgid "Once the email address has been entered, emails can be sent to that alias to create new expenses, without having to be in the Odoo database." msgstr "" -#: ../../content/applications/finance/expenses.rst:232 -msgid "To check an expense categories internal reference, go to :menuselection:`Expenses app --> Configuration --> Expense Categories`. If an internal reference is listed on the expense category, it is listed in the :guilabel:`Internal Reference` column." +#: ../../content/applications/finance/expenses/log_expenses.rst:192 +msgid "To submit an expense via email, create a new email, and enter the product's *internal reference* code (if available) and the amount of the expense as the subject of the email. Next, attach the receipt to the email. Odoo creates the expense by taking the information in the email subject, and combining it with the receipt." msgstr "" -#: ../../content/applications/finance/expenses.rst:-1 +#: ../../content/applications/finance/expenses/log_expenses.rst:197 +msgid "To check an expense category's internal reference, go to :menuselection:`Expenses app --> Configuration --> Expense Categories`. If an internal reference is listed on the expense category, it is listed in the :guilabel:`Internal Reference` column." +msgstr "" + +#: ../../content/applications/finance/expenses/log_expenses.rst:-1 msgid "Internal reference numbers are listed in the main Expense Categories view." msgstr "" -#: ../../content/applications/finance/expenses.rst:240 -msgid "To add an internal reference on an expense category, click on the category to open the form. Enter the internal reference in the field. Beneath the :guilabel:`Internal Reference` field, this sentence appears: :guilabel:`Use this reference as a subject prefix when submitting by email.`" +#: ../../content/applications/finance/expenses/log_expenses.rst:205 +msgid "To add an internal reference on an expense category, click on the category to open the expense category form. Enter the :guilabel:`Internal Reference` in the corresponding field. Beneath the :guilabel:`Internal Reference` field, this sentence appears: :guilabel:`Use this reference as a subject prefix when submitting by email.`" msgstr "" -#: ../../content/applications/finance/expenses.rst:-1 +#: ../../content/applications/finance/expenses/log_expenses.rst:-1 msgid "Internal reference numbers are listed in the main Expense Products view." msgstr "" -#: ../../content/applications/finance/expenses.rst:249 -msgid "For security purposes, only authenticated employee emails are accepted by Odoo when creating an expense from an email. To confirm an authenticated employee email address, go to the employee card in the :menuselection:`Employees` app, and refer to the :guilabel:`Work Email`" +#: ../../content/applications/finance/expenses/log_expenses.rst:215 +msgid "If submitting an expense, via email, for a $25.00 meal during a work trip, the email subject would be `FOOD $25.00`." msgstr "" -#: ../../content/applications/finance/expenses.rst:258 -msgid "If submitting an expense via email for a $25.00 meal during a work trip, the email subject would be `FOOD $25.00`." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:261 +#: ../../content/applications/finance/expenses/log_expenses.rst:218 msgid "Explanation:" msgstr "" -#: ../../content/applications/finance/expenses.rst:263 +#: ../../content/applications/finance/expenses/log_expenses.rst:220 msgid "The :guilabel:`Internal Reference` for the expense category `Meals` is `FOOD`" msgstr "" -#: ../../content/applications/finance/expenses.rst:264 +#: ../../content/applications/finance/expenses/log_expenses.rst:221 msgid "The :guilabel:`Cost` for the expense is `$25.00`" msgstr "" -#: ../../content/applications/finance/expenses.rst:269 -msgid "Create an expense report" +#: ../../content/applications/finance/expenses/log_expenses.rst:224 +msgid "For security purposes, only authenticated employee emails are accepted by Odoo when creating an expense from an email. To confirm an authenticated employee email address, go to the employee card in the :menuselection:`Employees app`, and refer to the :guilabel:`Work Email` field." msgstr "" -#: ../../content/applications/finance/expenses.rst:271 -msgid "When expenses are ready to submit (such as at the end of a business trip, or once a month), an *expense report* needs to be created. Go to the main :menuselection:`Expenses` app dashboard, which displays a default :guilabel:`My Expenses` view, or go to :menuselection:`Expenses app --> My Expenses --> My Expenses`." +#: ../../content/applications/finance/expenses/post_expenses.rst:3 +msgid "Post expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:276 -msgid "Expenses are color coded by status. Any expense with a status of :guilabel:`To Report` (expenses that still need to be added to an expense report) the text appears in blue. All other statuses (:guilabel:`To Submit`, :guilabel:`Submitted`, and :guilabel:`Approved`) the text appears in black." +#: ../../content/applications/finance/expenses/post_expenses.rst:5 +msgid "Once an expense report is :doc:`approved <../expenses/approve_expenses>`, the next step is to post the expense report to the proper accounting journal." msgstr "" -#: ../../content/applications/finance/expenses.rst:280 -msgid "First, select each individual expense for the report by clicking the check box next to each entry, or quickly select all the expenses in the list by clicking the check box next to :guilabel:`Expense Date`." +#: ../../content/applications/finance/expenses/post_expenses.rst:9 +msgid "To post expense reports to an accounting journal, the user **must** have the following :doc:`access rights <../../general/users/access_rights>`:" msgstr "" -#: ../../content/applications/finance/expenses.rst:284 -msgid "Another way to quickly add all expenses that are not on an expense report is to click :guilabel:`Create Report` without selecting any expenses, and Odoo will select all expenses with a status of :guilabel:`To Submit` that are not already on a report." +#: ../../content/applications/finance/expenses/post_expenses.rst:12 +msgid "Accounting: *Accountant* or *Adviser*" msgstr "" -#: ../../content/applications/finance/expenses.rst:-1 -msgid "Select the expenses to submit, then create the report." +#: ../../content/applications/finance/expenses/post_expenses.rst:13 +msgid "Expenses: *Manager*" msgstr "" -#: ../../content/applications/finance/expenses.rst:293 -msgid "Any expense can be selected from the :guilabel:`My Expenses` list, regardless of status. The :guilabel:`Create Report` button is visible as long as there is a minimum of 1 expense with a status of :guilabel:`To Report` selected. When the :guilabel:`Create Report` button is clicked, only expenses with a status of :guilabel:`To Submit` that are *not* currently on another expense report will appear in the newly created expense report." +#: ../../content/applications/finance/expenses/post_expenses.rst:15 +msgid "Only expense reports with an *Approved* status can post the expenses to a journal. To view all expense reports, navigate to :menuselection:`Expenses app --> Expense Reports`. Next, to view **only** approved expense reports that need to be posted, adjust the filters on the left side, so only the :guilabel:`Approved` checkbox is ticked." msgstr "" -#: ../../content/applications/finance/expenses.rst:299 -msgid "Once the expenses have been selected, click the :guilabel:`Create Report` button. The new report appears with all the expenses listed in the :guilabel:`Expense` tab. If there is a receipt attached to an individual expense, a :guilabel:`📎 (paperclip)` icon appears next to the :guilabel:`Customer to Reinvoice` and :guilabel:`Analytic Distribution` columns." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:304 -msgid "When the report is created, the date range for the expenses appears in the :guilabel:`Expense Report Summary` field by default. It is recommended to edit this field with a short summary for each report to help keep expenses organized. Enter a short description for the expense report (such as `Client Trip NYC`, or `Repairs for Company Car`) in the :guilabel:`Expense Report Summary` field. Next, select a :guilabel:`Manager` from the drop-down menu to assign a manager to review the report. If needed, the :guilabel:`Journal` can be changed. Use the drop-down menu to select a different :guilabel:`Journal`." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:-1 -msgid "Enter a short description and select a manager for the report." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:316 -msgid "If some expenses are not on the report that should be, they can still be added. Click :guilabel:`Add a line` at the bottom of the :guilabel:`Expense` tab. A pop up appears with all the available expenses that can be added to the report (with a status of :guilabel:`To Submit`). Click the check box next to each expense to add, then click :guilabel:`Select`. The items now appear on the report that was just created. If a new expense needs to be added that does *not* appear on the list, click :guilabel:`New` to create a new expense and add it to the report." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:-1 -msgid "Add more expenses to the report before submitting." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:328 -msgid "Expense reports can be created in one of three places:" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:330 -msgid "Go to the main :menuselection:`Expenses` app dashboard (also accessed by going to :menuselection:`Expenses app --> My Expenses --> My Expenses`)" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:332 -msgid "Go to :menuselection:`Expenses app --> My Expenses --> My Reports`" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:333 -msgid "Go to :menuselection:`Expenses app --> Expense Reports`" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:335 -msgid "In any of these views, click :guilabel:`New` to create a new expense report." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:340 -msgid "Submit an expense report" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:342 -msgid "When an expense report is completed, the next step is to submit the report to a manager for approval. Reports must be individually submitted, and cannot be submitted in batches. Open the specific report from the list of expense reports (if the report is not already open). To view all expense reports, go to :menuselection:`Expenses app --> My Expenses --> My Reports`." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:347 -msgid "If the list is large, grouping the results by status may be helpful since only reports that have a :guilabel:`To Submit` status need to be submitted, reports with an :guilabel:`Approved` or :guilabel:`Submitted` status do not." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:351 -msgid "The :guilabel:`To Submit` expenses are easily identifiable not just from the :guilabel:`To Submit` status, but the text appears in blue, while the other expenses text appears in black." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:-1 -msgid "Submit the report to the manager." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:359 -msgid "The status of each report is shown in the :guilabel:`Status` column on the right. If the :guilabel:`Status` column is not visible, click the :guilabel:`Additional Options (two dots)` icon at the end of the row, and enable :guilabel:`Status`." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:363 -msgid "Click on a report to open it, then click :guilabel:`Submit To Manager`. After submitting a report, the next step is to wait for the manager to approve it." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:367 -msgid "The :ref:`expenses/approve`, :ref:`expenses/post`, and :ref:`expenses/reimburse` sections are **only** for users with the *necessary rights*." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:373 -msgid "Approve expenses" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:375 -msgid "In Odoo, not just anyone can approve expense reports— only users with the necessary rights (or permissions) can. This means that a user must have at least *Team Approver* rights for the *Expenses* app. Employees with the necessary rights can review expense reports, approve or reject them, and provide feedback thanks to the integrated communication tool." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:380 -msgid "To see who has rights to approve, go to the main :menuselection:`Settings` app and click on :guilabel:`Manage Users`." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:384 -msgid "If the *Settings* app is not available, then certain rights are not set on the account. Check the :guilabel:`Access Rights` tab of a user's card in the :menuselection:`Settings` app. the :guilabel:`Administration` section (bottom right of the :guilabel:`Access Rights` tab) is set to one of three options:" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:389 -msgid ":guilabel:`None (blank)`: The user cannot access the *Settings* app at all." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:390 -msgid ":guilabel:`Access Rights`: The user can only view the :guilabel:`User's & Companies` section of the *Settings* app." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:392 -msgid ":guilabel:`Settings`: The user has access to the entire *Settings* app with no restrictions." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:394 -msgid "Please refer to :doc:`this document ` to learn more about managing users and their access rights." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:397 -msgid "Click on an individual to view their card, which displays the :guilabel:`Access Rights` tab in the default view. Scroll down to the :guilabel:`Human Resources` section. Under :guilabel:`Expenses`, there are four options:" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:401 -msgid ":guilabel:`None (blank)`: A blank field means the user has no rights to view or approve expense reports, and can only view their own." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:403 -msgid ":guilabel:`Team Approver`: The user can only view and approve expense reports for their own specific team." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:405 -msgid ":guilabel:`All Approver`: The user can view and approve any expense report." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:406 -msgid ":guilabel:`Administrator`: The user can view and approve any expense report, as well as access the reporting and configuration menus in the *Expenses* app." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:409 -msgid "Users who are able to approve expense reports (typically managers) can easily view all expense reports they have access rights to. Go to :menuselection:`Expenses app --> Expense Reports`, and a list appears with all expense reports that have a status of either :guilabel:`To Submit`, :guilabel:`Submitted`, :guilabel:`Approved`, :guilabel:`Posted`, or :guilabel:`Done`. Expense reports with a status of :guilabel:`Refused` are hidden in the default view." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:-1 -msgid "Reports to validate are found on the Reports to Approve page." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:419 -msgid "When viewing expense reports, there is a panel of filters that can be enabled or disabled on the left side. The three categories that filters can be applied on are :guilabel:`Status`, :guilabel:`Employee`, and :guilabel:`Company`. To view only expense reports with a particular status, enable the specific status filter to display the expense reports with only that status. Disable the specific status filter to hide the reports with that status. To view expense reports for a particular employee and/or company, enable the specific employee name filter and/or company filter in the :guilabel:`Employee` and :guilabel:`Company` sections." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:427 -msgid "Reports can be approved in two ways (individually or several at once) and refused only one way. To approve multiple expense reports at once, remain in the list view. First, select the reports to approve by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all the reports in the list." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:433 -msgid "Only reports with a status of :guilabel:`Submitted` can be approved. It is recommended to only display the submitted reports by adjusting the status filter on the left side by only having the :guilabel:`Submitted` filter enabled." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:437 -msgid "If a report is selected that is unable to be approved, the :guilabel:`Approve Report` button **will not appear**, indicating there is a problem with the selected report(s)." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:440 -msgid "Next, click the :guilabel:`Approve Report` button." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:-1 -msgid "Approve multiple reports by clicking the checkboxes next to each report." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:446 -msgid "To approve an individual report, click on a report to go to a detailed view of that report. In this view, several options are presented: :guilabel:`Approve`, :guilabel:`Report in Next Payslip`, :guilabel:`Refuse`, or :guilabel:`Reset to draft`. Click :guilabel:`Approve` to approve the report." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:450 -msgid "If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief explanation for the refusal in the :guilabel:`Reason to Refuse Expense` field, and then click :guilabel:`Refuse`." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:-1 -#: ../../content/applications/finance/expenses.rst:0 -msgid "Send messages in the chatter." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:457 -msgid "Team managers can easily view all the expense reports for their team members. While in the :guilabel:`Expense Reports` view, click the drop-down arrow in the right-side of the search box, and click on :guilabel:`My Team` in the :guilabel:`Filters` section. This presents all the reports for the manager's team." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:-1 -msgid "Select the My Team filter." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:467 -msgid "If more information is needed, such as a missing receipt, communication is easy from the chatter. In an individual report, simply click :guilabel:`Send message` to open the message text box. Type in a message, tagging the proper person (if needed), and post it to the chatter by clicking :guilabel:`Send`. The message is posted in the chatter, and the person tagged will be notified via email of the message, as well as any followers." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:473 -msgid "The only people that can be tagged in a message are *followers*. To see who is a follower, click on the :guilabel:`👤 (person)` icon to display the followers of the expense." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:483 -msgid "Post expenses in accounting" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:485 -msgid "Once an expense report is approved, the next step is to post the report to the accounting journal. To view all expense reports, go to :menuselection:`Expenses app --> Expense Reports`. To view only the expense reports that have been approved and need to be posted, adjust the filters on the left side so that only the :guilabel:`Approved` status is enabled." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:-1 +#: ../../content/applications/finance/expenses/post_expenses.rst:-1 msgid "View reports to post by clicking on expense reports, then reports to post." msgstr "" -#: ../../content/applications/finance/expenses.rst:494 -msgid "Just like approvals, expense reports can be posted in two ways (individually or several at once). To post multiple expense reports at once, remain in the list view. First, select the reports to post by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all the reports in the list. Next, click :guilabel:`Post Entries`." +#: ../../content/applications/finance/expenses/post_expenses.rst:25 +msgid "The default :guilabel:`All Reports` dashboard displays all expense reports, except reports with a status of :guilabel:`Refused`." msgstr "" -#: ../../content/applications/finance/expenses.rst:-1 +#: ../../content/applications/finance/expenses/post_expenses.rst:28 +msgid "Expense reports can be posted to accounting journals in two ways: :ref:`individually ` or :ref:`in bulk `." +msgstr "" + +#: ../../content/applications/finance/expenses/post_expenses.rst:34 +msgid "Post individual reports" +msgstr "" + +#: ../../content/applications/finance/expenses/post_expenses.rst:36 +msgid "To post an individual report, navigate to :menuselection:`Expenses app --> Expense Reports`, and click on an individual report with a :guilabel:`Status` of :guilabel:`Approved`, to view the report form. In this view, several options are presented: :guilabel:`Post Journal Entries`, :guilabel:`Report In Next Payslip`, :guilabel:`Refuse`, or :guilabel:`Reset to Draft`." +msgstr "" + +#: ../../content/applications/finance/expenses/post_expenses.rst:41 +msgid "Click :guilabel:`Post Journal Entries` to post the report." +msgstr "" + +#: ../../content/applications/finance/expenses/post_expenses.rst:43 +msgid "The accounting journal the expenses are posted to is listed in the :guilabel:`Journal` field of the expense report." +msgstr "" + +#: ../../content/applications/finance/expenses/post_expenses.rst:46 +msgid "After posting the expenses to an accounting journal, a :guilabel:`Journal Entry` smart button appears at the top of the screen. Click the :guilabel:`Journal Entry` smart button, and the details for the journal entry appear, with a status of :guilabel:`Posted`." +msgstr "" + +#: ../../content/applications/finance/expenses/post_expenses.rst:53 +msgid "Post multiple reports" +msgstr "" + +#: ../../content/applications/finance/expenses/post_expenses.rst:55 +msgid "To post multiple expense reports at once, navigate to :menuselection:`Expenses app --> Expense Reports` to view a list of expense reports. Next, select the reports to approve by ticking the checkbox next to each report being approved." +msgstr "" + +#: ../../content/applications/finance/expenses/post_expenses.rst:60 +msgid "Only expense reports with a status of :guilabel:`Approved` are able to post the expenses to an accounting journal. If an expense report is selected that **cannot** be posted, such as an unapproved report, or the report has already been posted to a journal, the :guilabel:`Post Entries` button is **not** visible." +msgstr "" + +#: ../../content/applications/finance/expenses/post_expenses.rst:66 +msgid "To select **only** approved expense reports, adjust the filters on the left side, so that only the :guilabel:`Approved` checkbox is ticked. Next, tick the checkbox next to the :guilabel:`Employee` column title to select **all** the :guilabel:`Approved` reports in the list at once." +msgstr "" + +#: ../../content/applications/finance/expenses/post_expenses.rst:71 +msgid "Next, click the :guilabel:`Post Entries` button." +msgstr "" + +#: ../../content/applications/finance/expenses/post_expenses.rst:-1 msgid "Post multiple reports at a time from the Expense Reports view, with the Approved filter." msgstr "" -#: ../../content/applications/finance/expenses.rst:503 -msgid "To post an individual report, click on a report to go to the detailed view of that report. In this view, several options are presented: :guilabel:`Post Journal Entries`, :guilabel:`Report In Next Payslip`, :guilabel:`Refuse`, or :guilabel:`Reset to Draft`. Click :guilabel:`Post Journal Entries` to post the report." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:508 -msgid "If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief explanation for the refusal in the :guilabel:`Reason to Refuse Expense` field, and then click :guilabel:`Refuse`. Refused reports can be viewed by going to :menuselection:`Expenses app --> Expense Reports`, then adjusting the filters on the left so that only :guilabel:`Refused` is selected. This will only show the refused expense reports." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:515 -msgid "To post expense reports to an accounting journal, the user must have following access rights:" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:517 -msgid "Accounting: Accountant or Adviser" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:518 -msgid "Expenses: Manager" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:523 +#: ../../content/applications/finance/expenses/reimburse.rst:3 msgid "Reimburse employees" msgstr "" -#: ../../content/applications/finance/expenses.rst:525 -msgid "After an expense report is posted to an accounting journal, the next step is to reimburse the employee. To view all the expense reports to pay, go to :menuselection:`Expenses app --> Expense Reports --> Reports To Pay`." +#: ../../content/applications/finance/expenses/reimburse.rst:5 +msgid "After an expense report is :doc:`posted to an accounting journal <../expenses/post_expenses>`, the next step is to reimburse the employee. Just like approving and posting expenses, employees can be reimbursed in two ways: with cash, check, or direct deposit (:ref:`individually ` or :ref:`in bulk `), or :ref:`reimbursed in a payslip `." msgstr "" -#: ../../content/applications/finance/expenses.rst:-1 -msgid "View reports to pay by clicking on expense reports, then reports to pay." +#: ../../content/applications/finance/expenses/reimburse.rst:12 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:427 +msgid "Settings" msgstr "" -#: ../../content/applications/finance/expenses.rst:533 -msgid "Just like approvals and posting, expense reports can be paid in two ways (individually or several at once). To pay multiple expense reports at once, remain in the list view. First, select the reports to pay by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all the reports in the list. Next, click :guilabel:`Register Payment`." +#: ../../content/applications/finance/expenses/reimburse.rst:14 +msgid "Reimbursements can be paid via paycheck, check, cash, or bank transfer. To set up payment options, first configure the various settings by navigating to :menuselection:`Expenses app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/finance/expenses.rst:-1 -msgid "Post multiple reports by selecting them, clicking the gear, and then post the entries." +#: ../../content/applications/finance/expenses/reimburse.rst:18 +msgid "To reimburse employees for expenses :ref:`in their paychecks `, tick the checkbox beside the :guilabel:`Reimburse in Payslip` option in the :guilabel:`Expenses` section." msgstr "" -#: ../../content/applications/finance/expenses.rst:542 -msgid "To pay an individual report, click on a report to go to a detailed view of that report. Click :guilabel:`Register Payment` to pay the employee." +#: ../../content/applications/finance/expenses/reimburse.rst:21 +msgid "Next, set how payments are made in the :guilabel:`Accounting` section. Click the drop-down menu under :guilabel:`Payment Methods`, and select the desired payment option. Default options include paying by :guilabel:`Manual (Cash)`, :guilabel:`Checks (Bank)`, :guilabel:`NACHA (Bank)`, and others. Leaving this field blank allows for **all** available payment options to be used." msgstr "" -#: ../../content/applications/finance/expenses.rst:545 -msgid "A :guilabel:`Register Payment` pop-up appears, and the :guilabel:`Journal`, :guilabel:`Payment Method`, and :guilabel:`Payment Date` can be modified, if needed. When the selections are correct, click :guilabel:`Create Payment` to send the payment to the employee." +#: ../../content/applications/finance/expenses/reimburse.rst:26 +msgid "When all desired configurations are complete, click :guilabel:`Save` to activate the settings." msgstr "" -#: ../../content/applications/finance/expenses.rst:549 -msgid "To pay an individual report, click on a report in the list view to go to a detailed view of that report. Click :guilabel:`Register Payment` to pay the employee. A :guilabel:`Register Payment` pop-up appears, but when paying an individual expense report instead of several at once, more options appear in the pop-up. In addition to the :guilabel:`Journal`, :guilabel:`Payment Method`, and :guilabel:`Payment Date` fields, a :guilabel:`Recipient Bank Account`, :guilabel:`Amount`, and :guilabel:`Memo` field appear. Select the employee's bank account from the drop-down menu to directly deposit the payment to their account. When all other selections are correct, click :guilabel:`Create Payment` to send the payment to the employee." +#: ../../content/applications/finance/expenses/reimburse.rst:31 +msgid "Reimburse individually" msgstr "" -#: ../../content/applications/finance/expenses.rst:-1 -msgid "Different options appear when registering an individual expense report versus multiple\n" -"expense reports at once." +#: ../../content/applications/finance/expenses/reimburse.rst:33 +msgid "To reimburse an individual expense report, first navigate to :menuselection:`Expenses app --> Expense Reports`. All expense reports are presented in a default list view. Click on the expense report being reimbursed to view the report details." msgstr "" -#: ../../content/applications/finance/expenses.rst:564 -msgid "Re-invoice expenses to customers" +#: ../../content/applications/finance/expenses/reimburse.rst:38 +msgid "**Only** expense reports with a status of :guilabel:`Posted` can be reimbursed." msgstr "" -#: ../../content/applications/finance/expenses.rst:566 -msgid "If expenses are tracked on customer projects, expenses can be automatically charged back to the customer. This is done by creating an expense, referencing the :abbr:`SO (Sales Order)` the expense should be added to, and then creating the expense report. Next, managers approve the expense report, and the accounting department posts the journal entries. Finally, once the expense report is posted to a journal, the expense(s) appears on the :abbr:`SO (Sales Order)` that was referenced. The sales order can then be invoiced, thus invoicing the customer for the expense." +#: ../../content/applications/finance/expenses/reimburse.rst:40 +msgid "Click the :guilabel:`Register Payment` button in the top-left corner of the expense report, and a :guilabel:`Register Payment` pop-up window appears. Enter the following information in the pop-up window:" msgstr "" -#: ../../content/applications/finance/expenses.rst:574 +#: ../../content/applications/finance/expenses/reimburse.rst:44 +msgid ":guilabel:`Journal`: Select the accounting journal to post the payment to using the drop-down menu. The default options are :guilabel:`Bank` or :guilabel:`Cash`." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:46 +#: ../../content/applications/finance/expenses/reimburse.rst:96 +msgid ":guilabel:`Payment Method`: Select how the payment is made using the drop-down menu. If :guilabel:`Cash` is selected for the :guilabel:`Journal`, the only option available is :guilabel:`Manual`. If :guilabel:`Bank` is selected for the :guilabel:`Journal`, the default options are :guilabel:`Manual` or :guilabel:`Checks`." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:50 +msgid ":guilabel:`Recipient Bank Account`: Select the employee's bank account the payment is being sent to. If the employee has a bank account on file in the :ref:`Private Information tab ` of their employee form in the **Employees** app, that bank account populates this field, by default." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:54 +msgid ":guilabel:`Amount`: The total amount being reimbursed populates this field, by default. The currency, located to the right of the field, can be modified using the drop-down menu." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:56 +msgid ":guilabel:`Payment Date`: Enter the date the payments are issued in this field. The current date populates this field, by default." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:58 +msgid ":guilabel:`Memo`: The text entered in the :doc:`Expense Report Summary <../expenses/expense_reports>` field of the expense report populates this field, by default." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:-1 +msgid "The Register Payment pop-up window filled out for an individual expense report\n" +"reimbursement." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:66 +msgid "When the fields of the pop-up window are completed, click the :guilabel:`Create Payment` button to register the payment, and reimburse the employee." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:72 +msgid "Reimburse in bulk" +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:74 +msgid "To reimburse multiple expense reports at once, navigate to :menuselection:`Expenses app --> Expense Reports` to view all expense reports in a list view. Next, adjust the :guilabel:`STATUS` filters on the left side to only present expense reports with a status of :guilabel:`Posted`." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:79 +msgid "Adjusting the :guilabel:`STATUS` filters to only show :guilabel:`Posted` expense reports is not necessary, but removes the step of selecting each individual report in the list." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:82 +msgid "Tick the checkbox next to the :guilabel:`Employee` column title to select all the reports in the list. Once ticked, the number of selected expense reports appears at the top of the page (:guilabel:`(#) Selected`). Additionally, a :guilabel:`Register Payment` button also appears in the upper-left corner." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:-1 +msgid "Expense reports filtered by the status Posted, making the Register Payment button visible." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:91 +msgid "Click the :guilabel:`Register Payment` button, and a :guilabel:`Register Payment` pop-up window appears. Enter the following information in the pop-up window:" +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:94 +msgid ":guilabel:`Journal`: Select the accounting journal the payment should be posted to, using the drop-down menu. The default options are :guilabel:`Bank` or :guilabel:`Cash`." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:100 +msgid ":guilabel:`Group Payments`: When multiple expense reports are selected for the same employee, this option appears. Tick the checkbox to have only one payment made, rather than issuing multiple payments to the same employee." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:103 +msgid ":guilabel:`Payment Date`: Enter the date the payments are issued. The current date populates this field, by default." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:-1 +msgid "The Register Payment pop-up window filled out." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:110 +msgid "When the fields on the pop-up window are completed, click the :guilabel:`Create Payments` button to register the payments, and reimburse the employees." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:116 +msgid "Report in next payslip" +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:118 +msgid "If the *Reimburse in Payslip* option is activated on the *Settings* page, payments can be added to their next payslip, instead of issued manually." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:122 +msgid "Reimbursing expenses on payslips can **only** be done individually, on an expense report with a status of *Approved*. Once an expense report has a status of *Posted*, the option to reimburse in the following payslip does **not** appear." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:126 +msgid "Navigate to :menuselection:`Expenses app --> Expense Reports`, and click on the individual expense report being reimbursed on the following paycheck. Click the :guilabel:`Report in Next Payslip` smart button, and the expenses are added to the next payslip issued for that employee. Additionally, a message is logged in the chatter stating the expense is added to the following payslip." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:-1 +msgid "The Report in Next Payslip button, visible with an expense report status of Approved." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:135 +msgid "The status for the expense report remains :guilabel:`Approved`. The status only changes to :guilabel:`Posted` (and then :guilabel:`Done`), when the paycheck is processed." +msgstr "" + +#: ../../content/applications/finance/expenses/reimburse.rst:139 +msgid "Refer to the :doc:`Payslips <../../hr/payroll/payslips>` documentation for more information about processing paychecks." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:3 +msgid "Re-invoice expenses" +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:5 +msgid "If expenses are tracked on customer projects, they can be automatically charged back to the customer. This is done by :ref:`creating an expense `, referencing the sales order the expense is added to, and then :ref:`creating an expense report `." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:10 +msgid "Next, managers :ref:`approve the expense report `, before the accounting department :ref:`posts the journal entries `." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:13 +msgid "Finally, once the expense report is posted to a journal, the expenses appears on the specified :abbr:`SO (Sales Order)`. The :abbr:`SO (Sales Order)` is then :ref:`invoiced `, thus charging the customer for the expenses." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:18 +msgid "Approving expenses, posting expenses to accounting, and reinvoicing expenses on :abbr:`SOs (Sales Orders)` is **only** possible for users with the appropriate :doc:`access rights <../../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:23 +msgid "This document provides lower-level instructions for the creation, submission, approval, and posting of expenses. For fully-detailed instructions for any of these steps, refer to the following documentation:" +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:27 +msgid ":doc:`Log expenses <../expenses/log_expenses>`" +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:28 +msgid ":doc:`Expense reports <../expenses/expense_reports>`" +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:29 +msgid ":doc:`Approving expenses <../expenses/approve_expenses>`" +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:30 +msgid ":doc:`Posting expenses in accounting <../expenses/post_expenses>`" +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:33 #: ../../content/applications/finance/fiscal_localizations/india.rst:55 #: ../../content/applications/finance/fiscal_localizations/india.rst:195 msgid "Setup" msgstr "" -#: ../../content/applications/finance/expenses.rst:576 -msgid "First, specify the invoicing policy for each expense category. Go to :menuselection:`Expenses app --> Configuration --> Expense Categories`. Click on the expense category to open the expense category form. Under the :guilabel:`Invoicing` section, click the radio button next to the desired selection for :guilabel:`Re-Invoicing Expenses`. Options are :guilabel:`None`, :guilabel:`At cost`, and :guilabel:`Sales price`." +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:35 +msgid "First, specify the invoicing policy for each expense category. Navigate to :menuselection:`Expenses app --> Configuration --> Expense Categories`. Click on an expense category to view the expense category form. Under the :guilabel:`INVOICING` section, click the radio button next to the desired selection for :guilabel:`Re-Invoice Expenses`:" msgstr "" -#: ../../content/applications/finance/expenses.rst:582 -msgid ":guilabel:`Re-Invoicing Expenses`:" +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:40 +msgid ":guilabel:`No`: The expense category cannot be re-invoiced." msgstr "" -#: ../../content/applications/finance/expenses.rst:584 -msgid ":guilabel:`None`: Expense category will not be re-invoiced." +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:41 +msgid ":guilabel:`At cost`: The expense category invoices expenses at the cost set on the expense category form." msgstr "" -#: ../../content/applications/finance/expenses.rst:585 -msgid ":guilabel:`At cost`: Expense category will invoice expenses at their real cost." +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:43 +msgid ":guilabel:`Sales price`: The expense category invoices at the sales price set on the expense form." msgstr "" -#: ../../content/applications/finance/expenses.rst:586 -msgid ":guilabel:`At sales price`: Expense category will invoice the price set on the sale order." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:589 +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:48 msgid "Create an expense" msgstr "" -#: ../../content/applications/finance/expenses.rst:591 -msgid "First, when :ref:`creating a new expense `, the correct information needs to be entered in order to re-invoice a customer. Select the *sales order* the expense will appear on in the :guilabel:`Customer to Reinvoice` section, from the drop-down menu. Next, select the :guilabel:`Analytic Account` the expense will be posted to. After the expense(s) are created, the expense report needs to be :ref:`created ` and :ref:`submitted ` as usual." +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:50 +msgid "First, when :doc:`creating a new expense <../expenses/log_expenses>`, the correct information needs to be entered to re-invoice the expense to a customer. Using the drop-down menu, select the :abbr:`SO (Sales Order)` to add the expense to in the :guilabel:`Customer to Reinvoice` field." msgstr "" -#: ../../content/applications/finance/expenses.rst:-1 +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:54 +msgid "Next, select the :guilabel:`Analytic Distribution` the expense is posted to. Multiple accounts can be selected, if desired." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:57 +msgid "To add another :guilabel:`Analytic Distribution`, click on the line to reveal the :guilabel:`Analytic` pop-over window. Click :guilabel:`Add a line`, then select the desired :guilabel:`Analytic Distribution` from the drop-down field. If selecting more than one :guilabel:`Analytic Distribution`, the :guilabel:`Percentage` fields **must** be modified. By default, both fields are populated with `100%`. Adjust the percentages for all the fields, so the total of all selected accounts equals `100%`." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:65 +msgid "A painting company agrees to paint an office building that houses two different companies. During the estimate, a meeting is held at the office location to discuss the project." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:68 +msgid "Both companies agree to pay for the travel expenses for the painting company employees. When creating the expenses for the mileage and hotels, **both companies** are listed in the :guilabel:`Analytic Distribution` line, for 50% each." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:75 +msgid "Create an expense report" +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:77 +msgid "After the expenses are created, the expense report must be :ref:`created ` and :ref:`submitted `, in the same manner as all other expenses." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:80 +msgid "Once the expense report is submitted, a :icon:`fa-money` :guilabel:`Sales Orders` smart button appears at the top-center of both the expense report, and each individual expense record being reinvoiced." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:-1 msgid "Ensure the customer to be invoiced is called out on the expense." msgstr "" -#: ../../content/applications/finance/expenses.rst:603 -msgid "Selecting a :guilabel:`Customer to Reinvoice` when creating an expense is critical, since this is what causes the expenses to be automatically invoiced after an expense report is approved." +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:89 +msgid "Selecting the proper :abbr:`SO (Sales Order)` in the :guilabel:`Customer to Reinvoice` field is **critical**, since this is how expenses are automatically invoiced after an expense report is approved." msgstr "" -#: ../../content/applications/finance/expenses.rst:606 -msgid "The :guilabel:`Customer to Reinvoice` field can be modified *until an expense report is* **approved**, then the field is no longer able to be modified." +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:93 +msgid "The :guilabel:`Customer to Reinvoice` field can be modified *only* until an expense report is **approved**. After an expense report is approved, the :guilabel:`Customer to Reinvoice` field is no longer able to be modified." msgstr "" -#: ../../content/applications/finance/expenses.rst:610 -msgid "Validate and post expenses" +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:100 +msgid "Approve and post expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:612 -msgid "Only employees with permissions (typically managers or supervisors) can :ref:`approve expenses `. Before approving an expense report, ensure the :guilabel:`Analytic Distribution` is set on every expense line of a report. If an :guilabel:`Analytic Distribution` is missing, assign the correct account(s) from the drop-down menu, and then click :guilabel:`Approve` or :guilabel:`Refuse`." +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:102 +msgid "Before :doc:`approving an expense report <../expenses/approve_expenses>`, ensure the :guilabel:`Analytic Distribution` section is populated for every expense line." msgstr "" -#: ../../content/applications/finance/expenses.rst:618 -msgid "The accounting department is typically responsible for :ref:`posting journal entries `. Once an expense report is approved, it can then be posted. The :abbr:`SO (Sales Order)` is **only** updated *after the journal entries are posted*. One the journal entries are posted, the expenses now appear on the referenced :abbr:`SO (Sales Order)`." +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:105 +msgid "If an :guilabel:`Analytic Distribution` entry is missing, assign the correct accounts from the drop-down menu, then click :guilabel:`Approve`." msgstr "" -#: ../../content/applications/finance/expenses.rst:624 +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:-1 +msgid "The expense report with all the Analytic Distribution lines populated." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:113 +msgid "The :guilabel:`Approve` button **only** appears after an expense report has been :ref:`submitted `." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:116 +msgid "The accounting department is typically responsible for :doc:`posting journal entries <../expenses/post_expenses>`. To post expenses to an accounting journal, click :guilabel:`Post Journal Entries`. Once an expense report is approved, it can then be posted." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:120 +msgid "The :abbr:`SO (Sales Order)` is **only** updated *after* the journal entries are posted. Once the journal entries are posted, the expenses now appear on the referenced :abbr:`SO (Sales Order)`." +msgstr "" + +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:126 msgid "Invoice expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:626 -msgid "Once the :abbr:`SO (Sales Order)` has been updated, it is time to invoice the customer. After the expense report has been approved and the journal entries have been posted, click the :guilabel:`Sales Orders` smart button to open the :abbr:`SO (Sales Order)`. The expenses to be re-invoiced are now on the :abbr:`SO (Sales Order)`." +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:128 +msgid "After the expense report has been approved, and the journal entries have been posted, the :abbr:`SO (Sales Order)` is updated, and the customer can be invoiced." msgstr "" -#: ../../content/applications/finance/expenses.rst:-1 -msgid "After the expense report is posted to the journal entry, the sales order can be called up\n" -"by clicking on the sales order number." +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:131 +msgid "Select the expense report, and click the :icon:`fa-money` :guilabel:`Sales Orders` smart button to open the :abbr:`SO (Sales Order)`. The expenses to be re-invoiced now appear on the :abbr:`SO (Sales Order)`." msgstr "" -#: ../../content/applications/finance/expenses.rst:637 -msgid "More than one :abbr:`SO (Sales Order)` can be referenced on an expense report. If more than one :abbr:`SO (Sales Order)` is referenced, the :guilabel:`Sales Orders` smart button will list the number of :abbr:`SO (Sales Order)`'s. If multiple :abbr:`SO (Sales Order)`'s are listed, the :guilabel:`Sales Orders` smart button opens a list view of all the :abbr:`SO (Sales Order)`'s on the expense report. Click on a :abbr:`SO (Sales Order)` to open the individual :abbr:`SO (Sales Order)`." +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:136 +msgid "More than one :abbr:`SO (Sales Order)` can be referenced on an expense report. If more than one :abbr:`SO (Sales Order)` is referenced, clicking the :guilabel:`Sales Orders` smart button opens a list displaying all the :abbr:`SOs (Sales Order)` associated with that expense report. Click on a :abbr:`SO (Sales Order)` to open the individual :abbr:`SO (Sales Order)` details." msgstr "" -#: ../../content/applications/finance/expenses.rst:644 +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:141 msgid "The expenses are listed in the :abbr:`SO (Sales Order)` :guilabel:`Order Lines` tab." msgstr "" -#: ../../content/applications/finance/expenses.rst:-1 +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:-1 msgid "See the expenses listed on the sales order after clicking into it." msgstr "" -#: ../../content/applications/finance/expenses.rst:650 -msgid "Next, click :guilabel:`Create Invoice`, and select if the invoice is for a :guilabel:`Regular invoice`, a :guilabel:`Down payment (percentage)`, or a :guilabel:`Down payment (fixed amount)` by clicking the radio button next to it. Then, click :guilabel:`Create Invoice`. The customer has now been invoiced for the expenses." +#: ../../content/applications/finance/expenses/reinvoice_expenses.rst:147 +msgid "Next, click :guilabel:`Create Invoice`, and a :guilabel:`Create invoices` pop-up window appears. Select if the invoice is a :guilabel:`Regular invoice`, a :guilabel:`Down payment (percentage)`, or a :guilabel:`Down payment (fixed amount)`. Then, click :guilabel:`Create Draft Invoice`. Doing so creates a draft invoice for the customer. Click :guilabel:`Confirm` to confirm the invoice, and the customer is invoiced for the expenses." msgstr "" #: ../../content/applications/finance/fiscal_localizations.rst:5 @@ -12598,7 +12956,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:20 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:31 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:24 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:37 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:39 #: ../../content/applications/finance/fiscal_localizations/germany.rst:61 #: ../../content/applications/finance/fiscal_localizations/united_states.rst:53 msgid "Modules installation" @@ -12658,7 +13016,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:52 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:64 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:87 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:89 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:137 #: ../../content/applications/finance/fiscal_localizations/peru.rst:52 msgid "Configure your company" @@ -12699,7 +13057,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:79 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:205 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:255 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:257 msgid "Configure master data" msgstr "" @@ -13786,11 +14144,11 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:923 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:267 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:181 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:270 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:272 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:172 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:251 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:703 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:820 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:702 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:819 #: ../../content/applications/finance/fiscal_localizations/peru.rst:795 msgid "Products" msgstr "" @@ -13900,7 +14258,7 @@ msgid "l10n_ar Sales Journal Configuration." msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:1012 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:725 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:724 msgid "Invoicing flow" msgstr "" @@ -13909,75 +14267,43 @@ msgid "Once the configurations are all set, the *Liquidity Product Vendor Bill* msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:1021 -msgid "As part of the localization installation, financial reporting for Argentina was added to the :guilabel:`Accounting` dashboard. Access these reports by navigating to :menuselection:`Accounting --> Reporting --> Argentinean Reports`" +msgid "As part of the localization installation, financial reporting for Argentina is available in the :guilabel:`Accounting` dashboard. To access these reports, navigate to :menuselection:`Accounting --> Reporting --> Argentinean Statements`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 -msgid "Argentinean reports." +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1025 +msgid "To access the VAT book report, go to :menuselection:`Accounting --> Reporting --> Tax Report`, click the :icon:`fa-book` (:guilabel:`book`), and select :guilabel:`Argentinean VAT book (AR)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1030 -msgid "VAT reports" +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1029 +msgid "The VAT book report can be exported as a `.zip` file by selecting it in the dropdown menu in the top-left corner." msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:1033 -msgid "Sales VAT book" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1035 -msgid "This report records all the sales, which are taken as the basis for the accounting records to determine the VAT (Tax Debit). The :guilabel:`Sales VAT` book report can be exported as a `.zip` file using the :guilabel:`VAT BOOK (ZIP)` button at the top left, containing `.txt` files to upload to the AFIP portal." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 -msgid "Sales VAT book." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1045 -msgid "Purchases VAT book" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1047 -msgid "The :guilabel:`Purchases VAT` book report can be exported as a `.zip` file using the :guilabel:`VAT BOOK (ZIP)` button at the top left, which contains `.txt` files to upload to the AFIP portal." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 -msgid "Purchases VAT book." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1056 msgid "VAT summary" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1058 -msgid "Pivot table designed to check the monthly VAT totals. This report is for internal use and is not sent to the AFIP." +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1035 +msgid "This pivot table is designed to check the monthly VAT totals. This report is for internal use and is not sent to the AFIP." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 -msgid "VAT Summary." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1066 -msgid "IIBB - Reports" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1069 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1039 msgid "IIBB - Sales by jurisdiction" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1071 -msgid "Pivot table where you can validate the gross income in each jurisdiction. Affidavit for the corresponding taxes to pay; and therefore, it is not sent to the AFIP." +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1041 +msgid "This pivot table allows you to validate the gross income in each jurisdiction. It serves as an affidavit for the corresponding taxes due but is not submitted to the AFIP." msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 msgid "IIBB Sales by jurisdiction." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1079 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1048 msgid "IIBB - Purchases by jurisdiction" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1081 -msgid "Pivot table where you can validate the gross purchases in each jurisdiction. Affidavit for the corresponding taxes to pay; and therefore, it is not sent to the AFIP." +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1050 +msgid "This pivot table allows you to validate the gross purchases in each jurisdiction. It serves as an affidavit for the corresponding taxes due but is not submitted to the AFIP." msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 @@ -14619,10 +14945,6 @@ msgstr "" msgid "The main advantage of using ABA files is to improve payment and matching efficiency. This is achieved by consolidating numerous payments into one file for batch processing, which can be submitted to all Australian banks." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:427 -msgid "Settings" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/australia.rst:429 msgid "To enable **batch payments**, go to :menuselection:`Accounting --> Configuration --> Setting --> Batch Payment` and enable :guilabel:`Allow Batch Payments`." msgstr "" @@ -14783,9 +15105,9 @@ msgid "`Stripe Terminal `_" msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:540 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:93 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:96 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:150 -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:444 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:441 msgid "Payroll" msgstr "" @@ -15106,7 +15428,7 @@ msgid "When satisfied with the payslip, click :guilabel:`Create Draft entry` to msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:781 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:308 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:311 msgid "Pay employees" msgstr "" @@ -15398,8 +15720,8 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/austria.rst:64 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:85 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:325 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:99 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:292 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:101 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:294 msgid ":guilabel:`Phone`" msgstr "" @@ -15950,12 +16272,12 @@ msgid "Odoo supports the **Peppol BIS Billing 3.0 (UBL)** electronic invoicing f msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:415 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:200 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:202 msgid ":doc:`../accounting/customer_invoices/electronic_invoicing`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:420 -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:402 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:399 msgid "Cash discount" msgstr "" @@ -15968,7 +16290,7 @@ msgid "To apply the right tax amount and report it correctly in your VAT return, msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:429 -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:408 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:405 msgid ":doc:`../accounting/customer_invoices/cash_discounts`" msgstr "" @@ -16302,9 +16624,9 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:72 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:313 #: ../../content/applications/finance/fiscal_localizations/chile.rst:232 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1096 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:95 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:288 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1095 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:97 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:290 msgid ":guilabel:`Name`" msgstr "" @@ -16347,9 +16669,9 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:86 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:326 #: ../../content/applications/finance/fiscal_localizations/chile.rst:233 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1097 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:100 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:293 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1096 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:102 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:295 msgid ":guilabel:`Email`" msgstr "" @@ -16525,7 +16847,7 @@ msgid "The chart of accounts for Brazil is based on the SPED CoA, which gives a msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:218 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:267 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:269 msgid "You can add or delete accounts according to the company's needs." msgstr "" @@ -16620,9 +16942,9 @@ msgid ":guilabel:`Labor Assignment`: Defines if your services includes labor" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:305 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:282 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:284 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:174 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:656 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:655 #: ../../content/applications/finance/fiscal_localizations/philippines.rst:42 msgid "Contacts" msgstr "" @@ -16720,7 +17042,7 @@ msgid "Fiscal position configuration" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:375 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:355 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:357 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:311 msgid "Workflows" msgstr "" @@ -16810,7 +17132,7 @@ msgid ":doc:`Fiscal positions (tax and account mapping) <../accounting/taxes/fis msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:429 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:109 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:111 msgid "Electronic documents" msgstr "" @@ -16864,7 +17186,7 @@ msgid "All of the fields available on the invoice used to issue an electronic in msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:470 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:595 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:594 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:370 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:348 @@ -17254,7 +17576,7 @@ msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` :guilabel:`Email B msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:153 -msgid "In order to receive your SII documents, it's necessary to set up your own email server. More information on how to do this can be found in this documentation: :doc:`../../general/email_communication/email_servers`" +msgid "In order to receive your SII documents, it's necessary to set up your own email server. More information on how to do this can be found in this documentation: :doc:`../../general/email_communication`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:157 @@ -17351,7 +17673,7 @@ msgid "Digital certificate configuration." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:216 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:565 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:564 #: ../../content/applications/finance/fiscal_localizations/peru.rst:237 msgid "Multicurrency" msgstr "" @@ -17370,12 +17692,12 @@ msgid "Configuring partner contacts is also required to send :abbr:`SII (Servici msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:234 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:97 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:99 msgid ":guilabel:`Identification Number`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:235 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:98 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:100 msgid ":guilabel:`Taxpayer Type`" msgstr "" @@ -17599,7 +17921,7 @@ msgid ":guilabel:`Documents type 33` electronic invoice must have at least one i msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:423 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:924 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:923 msgid "Validation and DTE status" msgstr "" @@ -17707,34 +18029,34 @@ msgid "Once the invoice is accepted and validated by the :abbr:`SII (Servicio de msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 -msgid "SII Validation fiscal elements." +msgid "Fiscal elements and barcode printed in accepted invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:519 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:518 msgid "If you are hosted in Odoo SH or On-Premise, you should manually install the `pdf417gen `_ library. Use the following command to install it: :command:`pip install pdf417gen`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:524 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:523 msgid "Commercial validation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:526 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:525 msgid "Once the invoice has been sent to the customer:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:528 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:527 msgid ":guilabel:`DTE Partner Status` changes to :guilabel:`Sent`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:529 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:528 msgid "The customer must send a reception confirmation email." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:530 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:529 msgid "Subsequently, if commercial terms and invoice data are correct, an acceptance confirmation is sent; otherwise, a claim is sent." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:532 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:531 msgid "The field :guilabel:`DTE Acceptance Status` is updated automatically." msgstr "" @@ -17742,11 +18064,11 @@ msgstr "" msgid "Message with the commercial acceptance from the customer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:539 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:538 msgid "Processed for claimed invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:541 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:540 msgid "Once the invoice has been accepted by the :abbr:`SII (Servicio de Impuestos Internos)`, **it can not be cancelled in Odoo**. In case you get a claim for your customer, the correct way to proceed is with a credit note to either cancel the invoice or correct it. Please refer to the :ref:`chile/credit-notes` section for more details." msgstr "" @@ -17754,13 +18076,13 @@ msgstr "" msgid "Invoice Commercial status updated to claimed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:551 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:550 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:403 #: ../../content/applications/finance/fiscal_localizations/peru.rst:830 msgid "Common errors" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:553 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:552 msgid "There are multiple reasons behind a rejection from the :abbr:`SII (Servicio de Impuestos Internos)`, but these are some of the common errors you might have and how to solve them:" msgstr "" @@ -17820,27 +18142,27 @@ msgstr "" msgid "**Hint:** there are just five reasons why this error could show up and all of them are related to the *Caratula* section of the XML:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:585 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:584 msgid "The company's :abbr:`RUT (Rol Único Tributario)` number is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:586 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:585 msgid "The certificate owner :abbr:`RUT (Rol Único Tributario)` number is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:587 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:586 msgid "The :abbr:`SII's (Servicio de Impuestos Internos)` :abbr:`RUT (Rol Único Tributario)` number (this should be correct by default) is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:589 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:588 msgid "The resolution date is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:590 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:589 msgid "The resolution number is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:597 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:596 msgid "When a cancellation or correction is needed over a validated invoice, a credit note must be generated. It is important to consider that a :abbr:`CAF (Folio Authorization Code)` file is required for the credit note, which is identified as :guilabel:`Document Type` :guilabel:`61` in the :abbr:`SII (Servicio de Impuestos Internos)`. Please refer to the :ref:`CAF section ` for more information on the process to load the :abbr:`CAF (Folio Authorization Code)` on each document type." msgstr "" @@ -17848,16 +18170,16 @@ msgstr "" msgid "Creation of CAF for Credit notes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:609 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:665 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:608 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:664 msgid "Use cases" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:612 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:611 msgid "Cancel referenced document" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:614 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:613 msgid "In case you need to cancel or invalidate an invoice, navigate to :menuselection:`Accounting --> Customers --> Invoices` and select the desired invoice. Then, use the button :guilabel:`Add Credit Note` and select :guilabel:`Full Refund`, in this case the :abbr:`SII (Servicio de Impuestos Internos)` reference code is automatically set to :guilabel:`Anula Documento de referencia`." msgstr "" @@ -17865,11 +18187,11 @@ msgstr "" msgid "Credit note canceling the referenced document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:624 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:623 msgid "Correct referenced document" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:626 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:625 msgid "If a correction in the invoice information is required, for example the street name on the original invoice is wrong, then use the button :guilabel:`Add Credit Note`, select :guilabel:`Partial Refund` and select the option :guilabel:`Only Text Correction`. In this case the :guilabel:`SII Reference Code` field is automatically set to :guilabel:`Corrects Referenced Document Text`." msgstr "" @@ -17877,7 +18199,7 @@ msgstr "" msgid "Credit note correcting referenced document text." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:635 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:634 msgid "Odoo creates a credit note with the corrected text in an invoice and :guilabel:`Price` `0.00`." msgstr "" @@ -17885,15 +18207,15 @@ msgstr "" msgid "Credit note with the corrected value on the invoice lines." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:642 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:641 msgid "Make sure to define the :guilabel:`Default Credit Account` in the sales journal specifically for this use case." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:646 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:645 msgid "Corrects referenced document amount" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:648 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:647 msgid "When a correction on the amounts is required, use the button :guilabel:`Add Credit note` and select :guilabel:`Partial Refund`. In this case the :guilabel:`SII Reference Code` is automatically set to :guilabel:`Corrige el monto del Documento de Referencia`." msgstr "" @@ -17901,20 +18223,20 @@ msgstr "" msgid "Credit note for partial refund to correct amounts, using the SII reference code 3." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:657 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:656 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:368 msgid "Debit notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:659 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:658 msgid "In Chilean localization, debit notes, in addition to credit notes, can be created using the :guilabel:`Add Debit Note` button, with two main use cases." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:668 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:667 msgid "Add debt on invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:670 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:669 msgid "The primary use case for debit notes is to increase the value of an existing invoice. To do so, select option :guilabel:`3. Corrige el monto del Documento de Referencia` for the :guilabel:`Reference Code SII` field." msgstr "" @@ -17922,7 +18244,7 @@ msgstr "" msgid "Debit note correcting referenced document amount." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:678 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:677 msgid "In this case Odoo automatically includes the :guilabel:`Source Invoice` in the :guilabel:`Cross Reference` tab." msgstr "" @@ -17930,15 +18252,15 @@ msgstr "" msgid "Automatic reference to invoice in a debit note." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:686 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:685 msgid "You can only add debit notes to an invoice already accepted by the SII." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:689 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:688 msgid "Cancel credit notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:691 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:690 msgid "In Chile, debits notes are used to cancel a valid credit note. To do this, click the :guilabel:`Add Debit Note` button and select the :guilabel:`1: Anula Documentos de referencia` option for the :guilabel:`Reference Code SII` field." msgstr "" @@ -17946,47 +18268,47 @@ msgstr "" msgid "Debit note to cancel the referenced document (credit note)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:702 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:701 msgid "As part of the Chilean localization, you can configure your incoming email server to match the one you have registered in the :abbr:`SII (Servicio de Impuestos Internos)` in order to:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:705 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:704 msgid "Automatically receive the vendor bills :abbr:`DTE (Documentos Tributarios Electrónicos)` and create the vendor bill based on this information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:707 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:706 msgid "Automatically send the reception acknowledgement to your vendor." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:708 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:707 msgid "Accept or claim the document and send this status to your vendor." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:711 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:710 msgid "Reception" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:713 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:712 msgid "As soon as the vendor email with the attached :abbr:`DTE (Documentos Tributarios Electrónicos)` is received:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:716 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:715 msgid "The vendor bill maps all the information included in the XML." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:717 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:716 msgid "An email is sent to the vendor with the reception acknowledgement." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:718 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:717 msgid "The :guilabel:`DTE Status` is set as :guilabel:`Acuse de Recibido Enviado`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:721 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:720 msgid "Acceptation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:723 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:722 msgid "If all the commercial information is correct on your vendor bill, then you can accept the document using the :guilabel:`Aceptar Documento` button. Once this is done, the :guilabel:`DTE Acceptation Status` changes to :guilabel:`Accepted` and an email of acceptance is sent to the vendor." msgstr "" @@ -17994,11 +18316,11 @@ msgstr "" msgid "Button for accepting vendor bills." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:732 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:731 msgid "Claim" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:734 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:733 msgid "In case there is a commercial issue or the information is not correct on your vendor bill, you can claim the document before validating it, using the :guilabel:`Claim` button. Once this is done, the :guilabel:`DTE Acceptation Status` changes to :guilabel:`Claim` and a rejection email is sent to the vendor." msgstr "" @@ -18007,122 +18329,122 @@ msgid "Claim button in vendor bills to inform the vendor all the document is com "rejected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:744 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:743 msgid "If you claim a vendor bill, the status changes from :guilabel:`Draft` to :guilabel:`Cancel` automatically. Considering this as best practice, all the claimed documents should be canceled as they won't be valid for your accounting records." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:749 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:748 msgid "Electronic purchase invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:751 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:750 msgid "The *electronic purchase invoice* is a feature included in the `l10n_cl_edi` module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:753 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:752 msgid "Once all configurations have been made for :ref:`electronic invoices ` (e.g., uploading a valid company certificate, setting up master data, etc.), the electronic purchase invoices need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic purchase invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:759 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:758 msgid "Electronic purchase invoices are useful when vendors are not obligated to expedite an electronic vendor bill for your purchase. Still, your obligations require a document to be sent to the :abbr:`SII (Servicio de Impuestos Internos)` as proof of purchase." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:766 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:765 msgid "To generate an electronic purchase invoice from a vendor bill, the bill must be created in a purchase journal with the *Use Documents* feature enabled. It is possible to modify an existing purchase journal or create a new one in the following process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:770 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:769 msgid "To modify the existing purchase journal, or create a new purchase journal, navigate to :menuselection:`Accounting --> Configuration --> Journals`. Then, click the :guilabel:`New` button, and fill in the following required information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:774 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:773 msgid ":guilabel:`Type`: select :guilabel:`Purchase` from the drop-down menu for vendor bill journals." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:775 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:774 msgid ":guilabel:`Use Documents`: check this field so the journal can generate electronic documents (in this case the electronic purchase invoice)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:779 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:778 msgid "Generate an electronic purchase invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:781 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:780 msgid "To generate this type of document, it is necessary to create a vendor bill in Odoo. To do so, navigate to :menuselection:`Accounting --> Vendors --> Bills`, and click the :guilabel:`New` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:784 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:783 msgid "When all of the electronic purchase invoice information is filled, select the option :guilabel:`(46) Electronic Purchase Invoice` in the :guilabel:`Document Type` field:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:787 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:786 msgid "After the vendor bill is posted:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:789 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:788 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax Document) is automatically created and added to the chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:791 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:865 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:935 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:790 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:864 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:934 msgid "The :guilabel:`DTE SII Status` is set as :guilabel:`Pending to be sent`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:793 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:792 msgid "Odoo automatically updates the *DTE Status* every night using a scheduled action. To get a response from the :abbr:`SII (Servicio de Impuestos Internos)` immediately, click the :guilabel:`Send now to SII` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:798 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:745 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:797 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:744 msgid "Delivery guide" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:800 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:799 msgid "To install the :guilabel:`Delivery Guide` module, go to :menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - E-Invoicing Delivery Guide`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:805 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:804 msgid ":guilabel:`Chile - E-Invoicing Delivery Guide` has a dependency with :guilabel:`Chile - Facturación Electrónica`. Odoo will install the dependency automatically when the :guilabel:`Delivery Guide` module is installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:809 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:808 msgid "The *Delivery Guide* module includes the ability to send the :abbr:`DTE (Documentos Tributarios Electrónicos)` to :abbr:`SII (Servicio de Impuestos Internos)` and the stamp in PDF reports for deliveries." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:813 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:812 msgid "Once all configurations have been made for :ref:`electronic invoices ` (e.g., uploading a valid company certificate, setting up master data, etc.), delivery guides need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the :abbr:`CAF (Folio Authorization Code)` for electronic Delivery Guides." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:819 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:818 msgid "Verify the following important information in the :guilabel:`Price for the Delivery Guide` configuration:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:822 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:821 msgid ":guilabel:`From Sales Order`: delivery guide takes the product price from the sales order and shows it on the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:824 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:823 msgid ":guilabel:`From Product Template`: Odoo takes the price configured in the product template and shows it on the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:826 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:825 msgid ":guilabel:`No show price`: no price is shown in the delivery guide." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:828 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:827 msgid "Electronic delivery guides are used to move stock from one place to another and they can represent sales, sampling, consignment, internal transfers, and basically any product move." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:832 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:831 msgid "Delivery guide from a sales process" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:835 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:834 msgid "A delivery guide should **not** be longer than one page or contain more than 60 product lines." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:837 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:836 msgid "When a sales order is created and confirmed, a delivery order is generated. After validating the delivery order, the option to create a delivery guide is activated." msgstr "" @@ -18130,11 +18452,11 @@ msgstr "" msgid "Create Delivery Guide button on a sales process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:845 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:844 msgid "When clicking on :guilabel:`Create Delivery Guide` for the first time, a warning message pops up, stating the following:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:848 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:847 msgid "`No se encontró una secuencia para la guía de despacho. Por favor, establezca el primer número dentro del campo número para la guía de despacho`" msgstr "" @@ -18142,15 +18464,15 @@ msgstr "" msgid "First Delivery Guide number warning message." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:855 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:854 msgid "This warning message means the user needs to indicate the next sequence number Odoo has to take to generate the delivery guide (e.g. next available :abbr:`CAF (Folio Authorization Code)` number), and only happens the first time a delivery guide is created in Odoo. After the first document has been correctly generated, Odoo takes the next available number in the :abbr:`CAF (Folio Authorization Code)` file to generate the following delivery guide." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:861 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:860 msgid "After the delivery guide is created:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:863 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:862 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax Document) is automatically created and added to the :guilabel:`chatter`." msgstr "" @@ -18158,11 +18480,11 @@ msgstr "" msgid "Chatter notes of Delivery Guide creation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:871 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:870 msgid "The :guilabel:`DTE Status` is automatically updated by Odoo with a scheduled action that runs every night. To get a response from the :abbr:`SII (Servicio de Impuestos Internos)` immediately, press the :guilabel:`Send now to SII` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:875 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:874 msgid "Once the delivery guide is sent, it may then be printed by clicking on the :guilabel:`Print Delivery Guide` button." msgstr "" @@ -18170,27 +18492,27 @@ msgstr "" msgid "Printing Delivery Guide PDF." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:882 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:881 msgid "Delivery guide will have fiscal elements that indicate that the document is fiscally valid when printed (if hosted in *Odoo SH* or on *On-premise* remember to manually add the :guilabel:`pdf417gen` library mentioned in the :ref:`Invoice PDF report section `)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:888 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:887 msgid "Electronic receipt" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:890 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:889 msgid "To install the :guilabel:`Electronic Receipt` module, go to :menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - Electronic Receipt`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:895 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:894 msgid ":guilabel:`Chile - Electronic Receipt` has a dependency with :guilabel:`Chile - Facturación Electrónica`. Odoo will install the dependency automatically when the :guilabel:`E-invoicing Delivery Guide` module is installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:899 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:898 msgid "Once all configurations have been made for :ref:`electronic invoices ` (e.g., uploading a valid company certificate, setting up master data, etc.), electronic receipts need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:905 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:904 msgid "Electronic receipts are useful when clients do not need an electronic invoice. By default, there is a partner in the database called :guilabel:`Anonymous Final Consumer` with a generic :abbr:`RUT (Rol Único Tributario)` `66666666-6` and taxpayer type of :guilabel:`Final Consumer`. This partner can be used for electronic receipts or a new record may be created for the same purpose." msgstr "" @@ -18198,7 +18520,7 @@ msgstr "" msgid "Electronic Receipt module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:914 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:913 msgid "Although electronic receipts should be used for final consumers with a generic :abbr:`RUT (Rol Único Tributario)`, it can also be used for specific partners. After the partners and journals are created and configured, the electronic receipts are created in the standard way as electronic invoice, but the type of document :guilabel:`(39) Electronic Receipt` should be selected in the invoice form:" msgstr "" @@ -18206,15 +18528,15 @@ msgstr "" msgid "Document type 39 for Electronic Receipts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:926 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:925 msgid "When all of the electronic receipt information is filled, manually (or automatically) proceed to validate the receipt from the sales order. By default, :guilabel:`Electronic Invoice` is selected as the :guilabel:`Document Type`, however in order to validate the receipt correctly, make sure to edit the :guilabel:`Document Type` and change to :guilabel:`Electronic Receipt`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:931 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:930 msgid "After the receipt is posted:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:933 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:932 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax Document) is created automatically and added to the :guilabel:`chatter`." msgstr "" @@ -18222,35 +18544,35 @@ msgstr "" msgid "Electronic Receipts STE creation status." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:941 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:940 msgid "The :guilabel:`DTE Status` is automatically updated by Odoo with a scheduled action that runs every day at night. To get a response from the :abbr:`SII (Servicio de Impuestos Internos)` immediately, press the :guilabel:`Send now to SII` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:945 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:944 msgid "Please refer to the :ref:`DTE Workflow ` for electronic invoices as the workflow for electronic receipt follows the same process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:949 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:948 msgid "Electronic export of goods" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:951 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:950 msgid "To install the :guilabel:`Electronic Exports of Goods` module, go to :menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Electronic Exports of Goods for Chile`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:956 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:955 msgid ":guilabel:`Chile - Electronic Exports of Goods for Chile` has a dependency with :guilabel:`Chile - Facturación Electrónica`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:959 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:958 msgid "Once all configurations have been made for :ref:`electronic invoices ` (e.g., uploading a valid company certificate, setting up master data, etc.), electronic exports of goods need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:965 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:964 msgid "Electronic invoices for the export of goods are tax documents that are used not only for the :abbr:`SII (Servicio de Impuestos Internos)` but are also used with customs and contain the information required by it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:970 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:969 msgid "Contact configurations" msgstr "" @@ -18258,11 +18580,11 @@ msgstr "" msgid "Taxpayer Type needed for the Electronic Exports of Goods module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:977 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:976 msgid "Chilean customs" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:979 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:978 msgid "When creating an electronic exports of goods invoice, these new fields in the :guilabel:`Other Info` tab are required to comply with Chilean regulations." msgstr "" @@ -18270,11 +18592,11 @@ msgstr "" msgid "Chilean customs fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:987 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:986 msgid "PDF report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:989 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:988 msgid "Once the invoice is accepted and validated by the :abbr:`SII (Servicio de Impuestos Internos)` and the PDF is printed, it includes the fiscal elements that indicate that the document is fiscally valid and a new section needed for customs." msgstr "" @@ -18282,11 +18604,11 @@ msgstr "" msgid "PDF report section for the Electronic Exports of Goods PDF Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:998 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:997 msgid "eCommerce electronic invoicing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1000 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:999 msgid "To install the :guilabel:`Chilean eCommerce` module, go to :menuselection:`Apps, search for the module by its technical name `l10n_cl_edi_website_sale`, and click the :guilabel:`Activate` button." msgstr "" @@ -18294,27 +18616,27 @@ msgstr "" msgid "l10n_cl eCommerce module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1007 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1006 msgid "This module enables the features and configurations to:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1009 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1008 msgid "Generate electronic documents from the *eCommerce* application" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1010 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1009 msgid "Support for required fiscal fields in the *eCommerce* application" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1011 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1010 msgid "Effectively let the final client decide the electronic document to be generated for their purchase" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1014 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1013 msgid "Once all of the configurations are made for the Chilean :ref:`electronic invoice ` flow, the following configurations are required for the eCommerce flow to be integrated." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1018 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1017 msgid "To configure your website to generate electronic documents during the sale process, go to :menuselection:`Website --> Configuration --> Settings --> Invoicing` and activate the :guilabel:`Automatic Invoice` feature. Activating this feature allows electronic documents to be automatically generated when an online payment is confirmed." msgstr "" @@ -18322,15 +18644,15 @@ msgstr "" msgid "Invoice Policy and Automatic Invoice configurations." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1027 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1026 msgid "Since an online payment needs to be confirmed for the *automatic invoice* feature to generate the document, a payment provider must be configured for the related website." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1031 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1030 msgid "Review the :doc:`../payment_providers` documentation for information on which payment providers are supported in Odoo, and how to configure them." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1034 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1033 msgid "It is also recommended to configure your products so they are able to be invoiced when an online payment is confirmed. To do so, go to :menuselection:`Website --> eCommerce --> Products` and select the product template of the desired product. Then, set the :guilabel:`Invoicing Policy` to :guilabel:`Ordered quantities`." msgstr "" @@ -18338,12 +18660,13 @@ msgstr "" msgid "Invoice Policy configuration in Products." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1044 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1130 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1043 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1129 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:673 msgid "Invoicing flows" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1046 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1045 msgid "Clients from Chile will be able to select if they need an **invoice** or a **ballot** for their purchase with an extra step added during the checkout process." msgstr "" @@ -18351,7 +18674,7 @@ msgstr "" msgid "Option for EDI Documents for clients." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1053 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1052 msgid "If the customer selects the :guilabel:`Electronic Invoice` option, fiscal fields are required to be filled out, including the :guilabel:`Activity Description`, the :guilabel:`Identification Number` and their :guilabel:`DTE Email`." msgstr "" @@ -18359,23 +18682,24 @@ msgstr "" msgid "Fiscal fields required for an Invoice to be requested." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1061 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1060 msgid "If the client selects the :guilabel:`Electronic Receipts` option, they will be directed to the next step, and the electronic document will be generated for the *Consumidor Final Anónimo* contact." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1064 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1063 msgid "Clients from countries other than Chile, will have their electronic receipts automatically generated for them by Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1068 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1067 msgid "If a purchase through eCommerce requires an export, the customer will need to contact your company to generate an electronic export invoice (*document type 110*), which can be done from the *Accounting* app." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1073 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1072 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:655 msgid "Point of Sale electronic invoicing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1075 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1074 msgid "To install the :guilabel:`Chilean Module for Point of Sale`, go to the :menuselection:`Apps` application on the main Odoo dashboard, search for the module by its technical name `l10n_cl_edi_pos`, and click the :guilabel:`Activate` button." msgstr "" @@ -18383,47 +18707,47 @@ msgstr "" msgid "l10n_cl POS EDI module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1083 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1082 msgid "This module enables the following features and configurations to:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1085 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1084 msgid "Generate electronic documents from the *Point of Sale* application" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1086 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1085 msgid "Support the required fiscal fields for contacts created in the *Point of Sale* application" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1087 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1086 msgid "Effectively lets the final client decide the type of electronic document to be generated for their purchase" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1089 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1088 msgid "Print QR or 5-digit codes in tickets to access to electronic invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1091 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1090 msgid "To configure contacts with the required fiscal information, review the :ref:`partner information ` section, or directly modify a contact. Navigate to :menuselection:`Point of Sale --> Session --> Customers --> Details`, and edit any of the following fields:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1098 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1097 msgid ":guilabel:`Identification Type`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1099 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1098 msgid ":guilabel:`Tax Payer Type`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1100 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1099 msgid ":guilabel:`Type Giro`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1101 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1100 msgid ":guilabel:`DTE Email`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1102 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1101 msgid ":guilabel:`RUT`" msgstr "" @@ -18431,7 +18755,7 @@ msgstr "" msgid "Contact with fiscal information created from POS." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1108 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1107 msgid "To configure the products, navigate to :menuselection:`Point of Sale --> Products --> Products` and select a product record. In the :guilabel:`Sales` tab of the product form, it is necessary to mark the product as :guilabel:`Available for POS`, this makes the product available for sale in the *Point of Sale* app." msgstr "" @@ -18439,15 +18763,15 @@ msgstr "" msgid "Product with fiscal information created from POS." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1117 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1116 msgid "Optionally, the following features are available for configuration in the :menuselection:`Point of Sale --> Configuration --> Settings --> Bills & Receipts section`:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1120 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1119 msgid ":guilabel:`Use QR code on ticket`: this feature enables a QR code to be printed on the user's receipt so they can easily request an invoice after their purchase" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1122 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1121 msgid ":guilabel:`Generate a code on ticket`: this feature enables a 5-digit code to be generated on the receipt, allowing the user to request an invoice through the customer portal" msgstr "" @@ -18455,15 +18779,15 @@ msgstr "" msgid "Configuration to generate QR or 5 digit codes on tickets." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1132 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1131 msgid "The following sections cover the invoicing flows for the *Point of Sale* application." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1135 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1134 msgid "Electronic receipts: anonymous end user" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1137 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1136 msgid "When making a purchase as an anonymous user that does not request an electronic invoice, Odoo automatically selects :guilabel:`Consumidor Final Anónimo` as the contact for the order and generates the electronic receipt." msgstr "" @@ -18471,15 +18795,15 @@ msgstr "" msgid "Automatic contact selection of an anonymous end consumer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1146 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1145 msgid "If the client requests a credit note due to a return of their purchase, the credit note should be made using the *Accounting* app. See the :doc:`credit notes and refunds <../accounting/customer_invoices/credit_notes>` documentation for detailed instructions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1151 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1150 msgid "Electronic receipts: specific customer" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1153 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1152 msgid "When specific user makes a purchase that does not request an electronic invoice, Odoo automatically selects the contact for the order as the :guilabel:`Consumidor Final Anónimo`, and allows you to select or create the required customer contact with their fiscal information for the receipt." msgstr "" @@ -18487,16 +18811,16 @@ msgstr "" msgid "Selection of contact for the receipt." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1162 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1161 msgid "If the client requests a credit note because of a return of this type of purchase, the credit note and return process can be managed directly from the :abbr:`POS (Point of Sale)` session." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1166 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1165 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:260 msgid "Electronic invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1168 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1167 msgid "When clients request an electronic invoice, it is possible to select or create the required contact with their fiscal information. When the payment is being made, select the option :guilabel:`Invoice` to generate the document." msgstr "" @@ -18504,15 +18828,15 @@ msgstr "" msgid "Selection of invoice option at payment." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1177 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1176 msgid "For both the electronic receipts and invoices, if the product is not affected by taxes, Odoo detects this and generates the correct type of document for tax-exempt sales." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1181 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1180 msgid "Returns" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1183 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1182 msgid "For electronic receipts (not generated for the *Consumidor Final Anónimo*) and electronic invoices, it is possible to manage the process to return products sold in a :abbr:`POS (Point of Sale)` order by selecting the :guilabel:`Refund` button." msgstr "" @@ -18520,7 +18844,7 @@ msgstr "" msgid "Refund option in the POS application." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1191 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1190 msgid "Orders can be searched by the order status or by contact, and be selected for the refund to be based on the client's original order." msgstr "" @@ -18528,23 +18852,23 @@ msgstr "" msgid "Selection of order for the refund process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1198 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1197 msgid "When the return payment is validated, Odoo generates the necessary credit note, referencing the original receipt or invoice, partially or fully canceling the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1202 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1201 msgid "`Smart tutorial - Electronic invoicing for point of sale `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1209 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1208 msgid "Balance tributario de 8 columnas" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1211 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1210 msgid "This report presents the accounts in detail (with their respective balances), classifying them according to their origin and determining the level of profit or loss that the business had within the evaluated period of time." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1215 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1214 msgid "You can find this report in :menuselection:`Accounting --> Reporting --> Balance Sheet` and selecting in the :guilabel:`Report` field the option :guilabel:`Chilean Fiscal Balance (8 Columns) (CL)`." msgstr "" @@ -18556,19 +18880,23 @@ msgstr "" msgid "Chilean Fiscal Balance (8 Columns)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1228 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1227 msgid "Propuesta F29" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1230 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1229 msgid "The form *F29* is a new system that the :abbr:`SII (Servicio de Impuestos Internos)` enabled to taxpayers, and that replaces the *Purchase and Sales Books*. This report is integrated by Purchase Register (CR) and the Sales Register (RV). Its purpose is to support the transactions related to VAT, improving its control and declaration." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:1235 -msgid "This record is supplied by the electronic tax documents (DTE's) that have been received by the :abbr:`SII (Servicio de Impuestos Internos)`." +msgid "The *Propuesta F29 (CL)* report in Odoo covers the basic legal requirements as a first proposal for your final tax declaration." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:1238 +msgid "This record is supplied by the electronic tax documents (DTE's) that have been received by the :abbr:`SII (Servicio de Impuestos Internos)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1241 msgid "You can find this report in :menuselection:`Accounting --> Reporting --> Tax Reports` and selecting the :guilabel:`Report` option :guilabel:`Propuesta F29 (CL)`." msgstr "" @@ -18576,7 +18904,7 @@ msgstr "" msgid "Location of the Propuesta F29 (CL) Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1245 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1248 msgid "It is possible to set the :abbr:`PPM (Provisional Monthly Payments rate)` and the :guilabel:`Proportional Factor for the fiscal year` from the :menuselection:`Accounting --> Configuration --> Settings`." msgstr "" @@ -18584,7 +18912,7 @@ msgstr "" msgid "Default PPM and Proportional Factor for the Propuesta F29 Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1253 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1256 msgid "Or manually in the reports by clicking on the :guilabel:`✏️ (pencil)` icon." msgstr "" @@ -19230,99 +19558,99 @@ msgstr "" msgid "**RIMPE**: stands for *Regimen Simplificado para Emprendedores y Negocios*, the type of taxpayer qualified for SRI." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:39 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:41 msgid ":ref:`Install ` the following modules to get all the features of the Ecuadorian localization:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:49 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:51 msgid ":guilabel:`Ecuadorian - Accounting`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:50 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:52 msgid "`l10n_ec`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:51 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:53 msgid "The default :doc:`fiscal localization package <../fiscal_localizations>`, adds accounting characteristics for the Ecuadorian localization, which represent the minimum configuration required for a company to operate in Ecuador according to the guidelines set by the :abbr:`SRI (servicio de rentas internas)`. The module's installation automatically loads: Chart of Accounts, taxes, documents types, tax support types. Additionally, the generation of forms 103 and 104 are automatic." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:57 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:59 msgid ":guilabel:`Ecuadorian Accounting EDI`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:58 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:60 msgid "`l10n_ec_edi`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:59 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:61 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 SRI. The authorized documents are: Invoices, Credit Notes, Debit Notes, Withholdings and Purchase liquidations." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:64 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:66 msgid ":guilabel:`Ecuadorian Accounting Reports`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:65 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:67 msgid "`l10n_ec_reports`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:66 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:68 msgid "Includes all the technical and functional requirements to generate forms 103 and 104." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:67 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:69 msgid ":guilabel:`Ecuador - ATS Report`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:68 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:70 msgid "`l10n_ec_reports_ats`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:69 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:71 msgid "Includes all the technical and functional requirements to generate the ATS report XML file ready to be uploaded to the *DIMM Formularios*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:71 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:73 msgid ":guilabel:`Ecuadorian Website`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:72 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:74 msgid "`l10n_ec_website_sale`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:73 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:75 msgid "Includes all the technical and functional requirements to generate automatic electronic invoices from a Website sale." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:75 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:77 msgid ":guilabel:`Ecuadorian Point of Sale`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:76 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:78 msgid "`l10n_ec_edi_pos`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:77 -msgid "Includes all the technical and functional requirements to generate automatic electronic invoices from a PoS sale." +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:79 +msgid "Includes all the technical and functional requirements to generate automatic electronic invoices from a POS sale." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:81 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:83 msgid "When you install a database from scratch selecting `Ecuador` as the country, Odoo automatically installs the base module :guilabel:`Ecuadorian - Accounting`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:89 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:91 msgid "To configure your company information, go to the :guilabel:`Contacts` app and search the name given to your company or activate :ref:`developer mode ` and go to :menuselection:`Company --> Contact` and then edit the contact to configure the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:93 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:95 msgid "Check the :guilabel:`Company` option on top" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:96 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:98 msgid ":guilabel:`Address`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:102 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:104 msgid "Upload company logo and save" msgstr "" @@ -19330,59 +19658,59 @@ msgstr "" msgid "Populate company data for Ecuador in Odoo Contacts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:111 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:113 msgid "To upload your information for electronic documents go to :menuselection:`Accounting --> Configuration --> Settings` and search for :command:`Ecuadorian Localization`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:114 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:116 msgid "Configure the next information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:116 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:118 msgid ":guilabel:`Company legal name`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:117 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:119 msgid ":guilabel:`Use production servers`: check the checkbox if your company is going to do electronic documents in the production environment. If you want to use the testing environment for electronic documents then keep the checkbox unchecked." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:120 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:122 msgid ":guilabel:`Regime`: select if your company is in General Regular or is qualified as RIMPE." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:121 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:123 msgid ":guilabel:`Forced to keep accounting books`: check the checkbox if your company has this condition." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:123 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:125 msgid ":guilabel:`Default taxes for withholdings`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:124 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:126 msgid ":guilabel:`Issue withholds`: check the checkbox if your company is going to do electronic withholds." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:126 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:128 msgid ":guilabel:`Withhold consumibles`: put the code of the withholding for when you buy goods." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:127 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:129 msgid ":guilabel:`Withhold services`: put the code of the withholding for when you buy services." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:128 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:130 msgid ":guilabel:`Withhold credit card`: put the code of the withholding for when you buy with credit card" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:130 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:132 msgid ":guilabel:`Withhold agent number`: put the company withholding agent resolution number, if applicable for your company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:132 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:134 msgid ":guilabel:`Electronic Certificate File`: upload electronic certificate and password, then save it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:133 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:135 msgid ":guilabel:`Special tax contributor number`: if your company is qualified as a special taxpayer, fill out this field with it's corresponding tax contributor number." msgstr "" @@ -19390,19 +19718,19 @@ msgstr "" msgid "Electronic signature for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:141 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:143 msgid "When configuring the withholdings in the configuration menu, these suggested withholdings are only for domestic suppliers when no withholdings are setup on their *Taxpayer Type*. Moreover, the Credit Card withholding set up is always used when a Credit or Debit Card SRI Payment Metho is used." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:147 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:149 msgid "VAT withholding" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:149 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:151 msgid "This configuration only applies if you are qualified as a *Withholding Agent* by the SRI, otherwise skip this step. To configure your VAT withholding, go to :menuselection:`Accounting --> Accounting --> Configuration --> Ecuadorian SRI: Taxpayer Type SRI`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:153 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:155 msgid "You must configure the withholding percentage that applies for each type of taxpayer, specify the :guilabel:`Goods VAT Withholding` and the :guilabel:`Services VAT Withholding`." msgstr "" @@ -19410,71 +19738,71 @@ msgstr "" msgid "Taxpayer Type configuration for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:161 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:163 msgid "In the case that the :guilabel:`Taxpayer Type` is `RIMPE`, also configure the :guilabel:`Profit Withholding` percentage." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:165 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:167 msgid "Printer points" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:167 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:169 msgid "To configure your printer points, go to :menuselection:`Accounting --> Configuration --> Accounting: Journals`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:170 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:172 msgid "Printer points need to be configured for each type of electronic document that you need. For example: Customer Invoice, Credit Notes, and Debit Notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:173 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:175 msgid "For each printer point, you need to configure the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:175 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:177 msgid ":guilabel:`Journal Name`: in this format `[Emission Entity]-[Emission Point] [Document Type]`, for example: `001-001 Sales Documents`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:177 -msgid ":guilabel:`Type`: refers to the type of journal, select `Sales`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:178 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:212 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:239 -msgid ":guilabel:`Use Documents?`: this checkbox is automatically checked, leave it checked." -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:179 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:213 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:240 -msgid ":guilabel:`Emission Entity`: configure the establishment number." +msgid ":guilabel:`Type`: refers to the type of journal, select `Sales`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:180 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:214 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:241 -msgid ":guilabel:`Emission Point`: configure the printer point." +msgid ":guilabel:`Use Documents?`: this checkbox is automatically checked, leave it checked." msgstr "" #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:181 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:215 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:242 -msgid ":guilabel:`Emission address`: configure the address of the establishment." +msgid ":guilabel:`Emission Entity`: configure the establishment number." msgstr "" #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:182 -msgid ":guilabel:`Default income account`: configure the default income account." +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:216 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:243 +msgid ":guilabel:`Emission Point`: configure the printer point." msgstr "" #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:183 -msgid ":guilabel:`Dedicated Credit Note Sequence`: check the checkbox if *Credit Notes* are to be generated from this printer point - journal." +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:217 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:244 +msgid ":guilabel:`Emission address`: configure the address of the establishment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:184 +msgid ":guilabel:`Default income account`: configure the default income account." msgstr "" #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:185 +msgid ":guilabel:`Dedicated Credit Note Sequence`: check the checkbox if *Credit Notes* are to be generated from this printer point - journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:187 msgid ":guilabel:`Short Code`: This is the unique code for the sequence of accounting entries, enter a unique 5-digit code, for example: `VT001`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:188 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:190 msgid "Customer Invoice, Credit Notes and Debit Notes need to use the same journal as the :guilabel:`Emission Point`, and the :guilabel:`Entity Point` should be unique per journal." msgstr "" @@ -19482,37 +19810,37 @@ msgstr "" msgid "Configuring a printer point for Ecuador electronic document type of Customer Invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:196 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:198 msgid "In the :guilabel:`Advanced Settings` tab, check the :guilabel:`Electronic Invoicing` checkbox to enable it for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:203 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:205 msgid "Withholding" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:205 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:207 msgid "A Withholding Journal must be defined, go to go to :menuselection:`Accounting --> Configuration --> Accounting: Journals` where you need to configure the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:208 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:210 msgid ":guilabel:`Journal Name`: in this format `[Emission Entity]-[Emission Point] [Document Type]`, for example: `001-001 Withholding`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:210 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:237 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:212 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:239 msgid ":guilabel:`Type`: refers to the type of journal, select `Miscellaneous`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:211 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:213 msgid ":guilabel:`Withhold Type`: Configure Purchase Withholding." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:216 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:218 msgid ":guilabel:`Default account`: configure the default income account." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:217 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:243 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:219 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:245 msgid ":guilabel:`Short Code`: This is the unique code for the sequence of accounting entries, enter a unique 5-digit code, for example: `RT001`" msgstr "" @@ -19520,24 +19848,24 @@ msgstr "" msgid "Configuring withholding for Ecuador electronic document type of Withholding." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:225 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:251 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:227 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:253 msgid "In the :guilabel:`Advanced Settings` tab, check the :guilabel:`Electronic Invoicing` checkbox to enable the sending of electronic invoicing for the withholding." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:229 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:231 msgid "Purchase Liquidations" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:231 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:233 msgid "When using Purchase Liquidations, a specific journal must be created, go to :menuselection:`Accounting --> Configuration --> Accounting: Journals` and configure the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:235 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:237 msgid ":guilabel:`Journal Name`: in this format `[Emission Entity]-[Emission Point] [Document Type]`, for example: `001-001 Withhold`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:238 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:240 msgid ":guilabel:`Purchase Liquidations`: check the checkbox to enable purchase liquidations." msgstr "" @@ -19545,19 +19873,19 @@ msgstr "" msgid "Configuring purchase liquidations for Ecuador electronic document type of Withholding." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:260 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:262 msgid "The :doc:`chart of accounts <../accounting/get_started/chart_of_accounts>` is installed by default as part of the set of data included in the localization module, the accounts are mapped automatically in Taxes, Default Account Payable, Default Account Receivable." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:264 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:266 msgid "The chart of accounts for Ecuador is based on the most updated version of Superintendency of Companies, which is grouped in several categories and is compatible with NIIF accounting." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:272 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:274 msgid "In addition to the basic information in your products, you must add the configuration of the withholding code (tax) that applies." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:275 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:277 msgid "Go to :menuselection:`Accounting --> Vendors: Products` under the tab \"Purchase\"" msgstr "" @@ -19565,23 +19893,23 @@ msgstr "" msgid "Product for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:284 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:286 msgid "Configure the next information when you create a contact:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:286 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:288 msgid "Check the :guilabel:`Company` option on top if it is a contact with RUC, or check :guilabel:`Individual` if it is a contact with cedula or passport." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:289 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:291 msgid ":guilabel:`Address`: :guilabel:`Street` is a required field to confirm the Electronic Invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:290 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:292 msgid ":guilabel:`Identification Number`: select an identification type `RUC`, `Cedula`, or `Passport`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:291 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:293 msgid ":guilabel:`Taxpayer Type`: select the contact's SRI Taxpayer Type." msgstr "" @@ -19589,15 +19917,15 @@ msgstr "" msgid "Contacts for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:300 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:302 msgid "The :guilabel:`SRI Taxpayer Type` has inside the configuration of which VAT and Profit withholding will apply when you use this contact on Vendor Bill, and then create a withholding from there." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:305 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:307 msgid "Review your taxes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:307 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:309 msgid "As part of the localization module, taxes are automatically created with its configuration and related financial accounts." msgstr "" @@ -19605,35 +19933,35 @@ msgstr "" msgid "Taxes for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:314 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:316 msgid "The following options have been automatically configured:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:316 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:318 msgid ":guilabel:`Tax Support`: to be configured only in the IVA tax, this option is useful when you register purchase withholdings." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:318 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:320 msgid ":guilabel:`Code ATS`: to be configured only for income tax withholding codes, it is important when you register the withholding." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:320 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:322 msgid ":guilabel:`Tax Grids`: configure the codes of 104 form if it is a IVA tax and configure the codes of 103 form if it is a income tax withholding code." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:322 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:324 msgid ":guilabel:`Tax Name`:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:324 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:326 msgid "For IVA tax, format the name as: `IVA [percent] (104, [form code] [tax support code] [tax support short name])`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:326 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:328 msgid "For income tax withholding code, format the name as: `Code ATS [Percent of withhold] [withhold name]`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:329 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:331 msgid "Once the Ecuador module is installed, the most common taxes are automatically configured. If you need to create an additional one, you can do so, for which you must base yourself on the configuration of the existing taxes." msgstr "" @@ -19641,19 +19969,19 @@ msgstr "" msgid "Taxes with tax support for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:338 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:340 msgid "Review your Document Types" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:340 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:342 msgid "Some accounting transactions like *Customer Invoices* and *Vendor Bills* are classified by document types. These are defined by the government fiscal authorities, in this case by the SRI." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:343 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:345 msgid "Each document type can have a unique sequence per journal where it is assigned. As part of the localization, the document type includes the country on which the document is applicable; also the data is created automatically when the localization module is installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:347 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:349 msgid "The information required for the document types is included by default so the user does not need to fill anything there." msgstr "" @@ -19661,41 +19989,41 @@ msgstr "" msgid "Document types for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:357 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:359 msgid "Once you have configured your database, you can register your documents." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:360 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:362 msgid "Sales documents" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:365 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:367 msgid ":guilabel:`Customer invoices` are electronic documents that, when validated, are sent to SRI. These documents can be created from your sales order or manually. They must contain the following data:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:368 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:412 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:445 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:370 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:414 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:447 msgid ":guilabel:`Customer`: type the customer's information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:369 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:371 msgid ":guilabel:`Journal`: select the option that matches the printer point for the customer invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:370 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:372 msgid ":guilabel:`Document Type`: type document type in this format `(01) Invoice`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:371 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:491 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:529 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:373 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:493 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:531 msgid ":guilabel:`Payment Method (SRI)`: select how the invoice is going to be paid." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:372 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:492 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:530 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:374 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:494 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:532 msgid ":guilabel:`Products`: specify the product with the correct taxes." msgstr "" @@ -19703,48 +20031,48 @@ msgstr "" msgid "Customer invoice for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:379 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:381 msgid "Customer credit note" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:381 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:383 msgid "The :doc:`Customer credit note <../accounting/customer_invoices/credit_notes>` is an electronic document that, when validated, is sent to SRI. It is necessary to have a validated (posted) invoice in order to register a credit note. On the invoice there is a button named :guilabel:`Credit note`, click on this button to be directed to the :guilabel:`Create credit note` form, then complete the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:387 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:389 msgid ":guilabel:`Credit Method`: select the type of credit method." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:389 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:391 msgid ":guilabel:`Partial Refund`: use this option when you need to type the first number of documents and if it is a partial credit note." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:391 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:393 msgid ":guilabel:`Full Refund`: use this option if the credit note is for the total invoice and you need the credit note to be auto-validated and reconciled with the invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:393 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:395 msgid ":guilabel:`Full refund and new draft invoice`: use this option if the credit note is for the total invoice and you need the credit note to be auto-validated and reconciled with the invoice, and auto-create a new draft invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:397 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:399 msgid ":guilabel:`Reason`: type the reason for the credit note." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:398 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:400 msgid ":guilabel:`Rollback Date`: select the :guilabel:`specific` options." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:399 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:401 msgid ":guilabel:`Reversal Date`: type the date." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:400 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:433 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:402 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:435 msgid ":guilabel:`Use Specific Journal`: select the printer point 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/ecuador.rst:403 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:405 msgid "Once reviewed, you can click on the :guilabel:`Reverse` button." msgstr "" @@ -19752,21 +20080,21 @@ msgstr "" msgid "Add Customer Credit Note for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:409 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:411 msgid "When the :guilabel:`Partial Refund` option is used, you can change the amount of the credit note and then validate it. Before validating the credit note, review the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:413 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:446 -msgid ":guilabel:`Journal`: select the printer point for the customer Credit Note." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:414 -msgid ":guilabel:`Document Type`: this is the document type `(04) Credit Note`." -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:415 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:448 +msgid ":guilabel:`Journal`: select the printer point for the customer Credit Note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:416 +msgid ":guilabel:`Document Type`: this is the document type `(04) Credit Note`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:417 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:450 msgid ":guilabel:`Products`: It must specify the product with the correct taxes." msgstr "" @@ -19774,27 +20102,27 @@ msgstr "" msgid "Customer Credit Note for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:422 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:424 msgid "Customer debit note" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:424 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:426 msgid "The :guilabel:`Customer debit note` is an electronic document that, when validated, is sent to SRI. It is necessary to have a validated (posted) invoice in order to register a debit note. On the invoice there is a button named :guilabel:`Debit Note`, click on this button to be directed to the :guilabel:`Create debit note` form, then complete the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:429 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:431 msgid ":guilabel:`Reason`: type the reason for the debit note." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:430 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:432 msgid ":guilabel:`Debit note date`: select the :guilabel:`specific` options." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:431 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:433 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/ecuador.rst:436 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:438 msgid "Once reviewed you can click on the :guilabel:`Create Debit Note` button." msgstr "" @@ -19802,11 +20130,11 @@ msgstr "" msgid "Add Customer Debit Note for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:442 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:444 msgid "You can change the debit note amount, and then validate it. Before validating the debit note, review the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:447 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:449 msgid ":guilabel:`Document Type`: this is the document type `(05) Debit Note`." msgstr "" @@ -19814,27 +20142,27 @@ msgstr "" msgid "Customer Debit Note for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:455 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:457 msgid "Customer withholding" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:457 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:459 msgid "The :guilabel:`Customer withholding` is a non-electronic document for your company, this document is issued by the client in order to apply a withholding to the sale." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:460 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:462 msgid "It is necessary to have a validated (posted) invoice in order to register a customer withholding. On the invoice there is a button named :guilabel:`Add Withhold`, click on this button to be directed to the :guilabel:`Customer withholding` form, then complete the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:464 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:466 msgid ":guilabel:`Document Number`: type the withholding number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:465 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:467 msgid ":guilabel:`Withhold Lines`: select the taxes that the customer is withholding." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:467 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:469 msgid "Before validating the withholding, review that the amounts for each tax are the same as the original document." msgstr "" @@ -19842,41 +20170,41 @@ msgstr "" msgid "Customer withhold for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:475 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:477 msgid "Purchase Documents" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:478 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:480 #: ../../content/applications/finance/fiscal_localizations/romania.rst:130 msgid "Vendor bill" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:480 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:482 msgid "The :guilabel:`Vendor bill` is a non-electronic document for your company, this document is issued by your vendor when your company generates a purchase." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:483 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:485 msgid "The bills can be created from the purchase order or manually, it must contain the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:486 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:523 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:488 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:525 msgid ":guilabel:`Vendor`: type the vendor's information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:487 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:489 msgid ":guilabel:`Bill Date`: select the date of invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:488 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:490 msgid ":guilabel:`Journal`: it is the journal for vendor bills." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:489 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:491 msgid ":guilabel:`Document Type`: this is the document type `(01) Invoice`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:490 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:492 msgid ":guilabel:`Document number`: type the document number." msgstr "" @@ -19884,60 +20212,60 @@ msgstr "" msgid "Purchases for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:499 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:501 msgid "When creating the purchase withholding, verify that the bases (base amounts) are correct. If you need to edit the amount of the tax in the :guilabel:`Vendor bill`, click the :guilabel:`Edit` button. Otherwise, from the :guilabel:`Journal Items` tab click the :guilabel:`Edit` button and set the adjustment to go where you want." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:505 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:507 msgid "Purchase liquidation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:507 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:509 msgid "The :guilabel:`Purchase liquidation` is an electronic document that, when validated, is sent to SRI." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:509 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:511 msgid "Companies issue this type of electronic document when they purchase, and the vendor does not issue an invoice due to one or more of the following cases:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:512 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:514 msgid "Services were provided by non-residents of Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:513 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:515 msgid "Services provided by foreign companies without residency or establishment in Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:514 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:516 msgid "Purchase of goods or services from natural persons not registered with a RUC, who due to their cultural level or hardiness are not able to issue sales receipts or customer invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:516 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:518 msgid "Reimbursement for the purchase of goods or services to employees in a dependency relationship (full-time employee)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:518 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:520 msgid "Services provided by members of collegiate bodies for the exercise of their function." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:520 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:522 msgid "These types of electronic documents can be created from the :guilabel:`Purchase Order` or manually from the :guilabel:`Vendor Bills` form view. It must contain the following data:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:524 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:526 msgid ":guilabel:`Journal`: select the journal for the :guilabel:`Purchase Liquidation` with the correct printer point." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:526 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:528 msgid ":guilabel:`Document Type`: this is the document type `(03) Purchase Liquidation`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:527 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:547 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:529 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:549 msgid ":guilabel:`Document number`: type the document number (sequence), you will only have to do this once, then the sequence will be automatically assigned for the next documents." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:532 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:534 msgid "Once you review the information you can validate the :guilabel:`Purchase Liquidation`." msgstr "" @@ -19945,23 +20273,23 @@ msgstr "" msgid "Purchase liquidation for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:539 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:541 msgid "Purchase withholding" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:541 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:543 msgid "The :guilabel:`Purchase withholding` is an electronic document that, when validated, is sent to SRI." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:543 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:545 msgid "It is necessary to have an invoice in a validated state in order to register a :guilabel:`Purchase withholding`. On the invoice, there is a button named :guilabel:`Add Withhold`, click on this button to be directed to the :guilabel:`Withholding` form, then complete the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:549 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:551 msgid ":guilabel:`Withhold lines`: The taxes appear automatically according to the configuration of products and vendors, you should review if the taxes and tax support are correct, and, if it is not correct, you can edit and select the correct taxes and tax support." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:553 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:555 msgid "Once you review the information you can validate the :guilabel:`Withholding`." msgstr "" @@ -19969,76 +20297,77 @@ msgstr "" msgid "Purchase withhold for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:560 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:562 msgid "You can't change the tax support for one that was not included in the configuration of the taxes used on the :guilabel:`Vendor Bill`. To do so, go to the tax applied on the :guilabel:`Vendor Bill` and change the :guilabel:`Tax Support` there." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:564 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:566 msgid "A withholding tax can be divided into two or more lines, this will depend on whether two or more withholdings percentages apply." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:568 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:570 msgid "The system suggests a VAT withholding of 30% with tax support 01, you can add your VAT withholding of 70% in a new line with the same tax support, the system will allow you as long as the total of the bases matches the total from the :guilabel:`Vendor Bill`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:575 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:577 msgid "The :ref:`ATS Report module ` enables the following:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:577 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:579 msgid "Choose the SRI Payment Method in each payment method's configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:578 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:580 msgid "Customers can manually input their identification type and identification number during the eCommerce checkout process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:580 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:582 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:663 msgid "Automatically generate a valid electronic invoice for Ecuador at the end of the checkout process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:586 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:588 msgid "Website" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:588 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:590 msgid "To generate an invoice after the checkout process, navigate to :menuselection:`Website --> Configuration --> Settings` and activate the :guilabel:`Automatic Invoice` option found under the :guilabel:`Invoicing` section." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:593 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:595 msgid "The invoice's email template can be modified from the :guilabel:`Invoice Email Template` field under the :guilabel:`Automatic Invoice` option." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:597 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:599 msgid "The sales journal used for invoicing is the first in the sequence of priority in the :guilabel:`Journal` menu." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:601 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:603 msgid "Payment providers" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:603 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:605 msgid "To activate the payment providers that should be used to capture eCommerce payments, navigate to :menuselection:`Website --> Configuration --> Payment Providers` section and then click on the :guilabel:`View other providers` button under the :guilabel:`Activate Payments` heading. From here, each payment provider can be configured by selecting a provider record. Refer to the :doc:`payment provider <../payment_providers>` documentation for more information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:610 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:612 #: ../../content/applications/finance/payment_providers.rst:224 msgid "Payment methods" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:612 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:614 msgid "To activate one or more payment methods for a payment provider, click :guilabel:`→ Enable Payment Methods` within the :guilabel:`Configuration` tab of each provider." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:615 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:617 msgid "When configuring the payment method, it is **mandatory** to set the :guilabel:`SRI Payment Method` for each method. This field appears after you create and save the payment method for the first time." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:620 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:622 msgid "Adding the :guilabel:`SRI Payment Method` is necessary to generate correctly the electronic invoice from an eCommerce sale. Select a **payment method** to access its configuration menu and the field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:625 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:627 msgid ":doc:`Payment provider <../payment_providers>`" msgstr "" @@ -20046,15 +20375,16 @@ msgstr "" msgid "l10n_ec SRI Payment Method." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:632 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:634 msgid "eCommerce workflow" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:635 -msgid "Type and identification number" +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:637 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:676 +msgid "Identification type and number" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:637 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:639 msgid "The client who is making a purchase will have the option to indicate their identification type and number during the checkout process. This information is required to correctly generate the electronic invoice after the checkout is completed." msgstr "" @@ -20062,35 +20392,87 @@ msgstr "" msgid "Website checkout form." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:646 -msgid "Verification is done to ensure the *Identification Number* field is completed and has the correct number of digits. For RUC identification, 13 digits are required. For Cédula, 9 digits are required." +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:647 +msgid "Verification is done to ensure the :guilabel:`Identification Number` field is completed and has the correct number of digits. For RUC identification, 13 digits are required. For Cédula, 9 digits are required." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:650 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:651 msgid "After finishing the checkout process, a confirmed invoice is generated, ready to be sent manually or asynchronously to the SRI." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:654 -msgid "Financial Reports" +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:657 +msgid "Make sure the *Ecuadorian module for Point of Sale* (`l10n_ec_edi_pos`) is :ref:`installed ` to enable the following features and configurations:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:656 -msgid "In Ecuador, there are fiscal reports that the company presents to SRI. Odoo supports two of the main financial reports used by companies: **reports 103** and **104**." +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:660 +msgid "Choose the SRI payment method in each payment method configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:659 -msgid "To get these reports, go to the **Accounting** app and select :menuselection:`Reporting --> Statements Reports --> Tax Report` and then filter by `Tax Report 103` or `Tax Report 104`." +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:661 +msgid "Manually input the customer's identification type and identification number when creating a new contact on *POS*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:663 -msgid "Report 103" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:665 -msgid "This report contains information of income tax withholdings in a given period, this can be reported monthly or semi-annually." +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:666 +msgid "Payment method configuration" msgstr "" #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:668 +msgid "To :doc:`create a payment method for a point of sale <../../sales/point_of_sale/payment_methods>`, go to :menuselection:`Point of Sale --> Configuration --> Payment Methods`. Then, set the :guilabel:`SRI Payment Method` in the payment method form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:678 +msgid "The POS cashier can :ref:`create a new contact for a customer ` who requests an invoice from an open POS session." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:681 +msgid "The *Ecuadorian Module for Point of Sale* adds two new fields to the contact creation form: :guilabel:`Identification Type` and :guilabel:`Tax ID`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:685 +msgid "As the identification number length differs depending on the identification type, Odoo automatically checks the :guilabel:`Tax ID` field upon saving the contact form. To manually ensure the length is correct, know that the :guilabel:`RUC` and :guilabel:`Citizenship` types require 13 and 10 digits, respectively." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:691 +msgid "Electronic invoice: anonymous end consumer" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:693 +msgid "When clients do not request an electronic invoice for their purchase, Odoo automatically sets the customer as :guilabel:`Consumidor Final` and generates an electronic invoice anyway." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:697 +msgid "If the client requests a credit note due to a return of this type of purchase, the credit note should be made using the client's real contact information. Credit notes cannot be created to *Consumidor Final* and can be managed :ref:`directly from the POS session `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:702 +msgid "Electronic invoice: specific customer" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:704 +msgid "If a customer requests an invoice for their purchase, it is possible to select or create a contact with their fiscal information. This ensures the invoice is generated with accurate customer details." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:708 +msgid "If the client requests a credit note due to a return of this type of purchase, the credit note and return process can be managed :ref:`directly from the POS session `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:714 +msgid "In Ecuador, there are fiscal reports that the company presents to SRI. Odoo supports two of the main financial reports used by companies: **reports 103** and **104**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:717 +msgid "To get these reports, go to the **Accounting** app and select :menuselection:`Reporting --> Statements Reports --> Tax Report` and then filter by `Tax Report 103` or `Tax Report 104`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:721 +msgid "Report 103" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:723 +msgid "This report contains information of income tax withholdings in a given period, this can be reported monthly or semi-annually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:726 msgid "You can see the information needed to report, which includes base and tax amounts, but also includes the tax code within the parenthesis in order to report it to the SRI." msgstr "" @@ -20098,15 +20480,15 @@ msgstr "" msgid "Report 103 form for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:676 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:734 msgid "Report 104" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:678 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:736 msgid "This report contains information on VAT tax and VAT withholding for a given period, this can be monthly or semi-annually." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:681 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:739 msgid "You can see the information needed to report, which includes base and tax amounts, but also includes the tax code within the parenthesis to report it to the SRI." msgstr "" @@ -20114,51 +20496,51 @@ msgstr "" msgid "Report 104 form for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:691 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:749 msgid "ATS report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:693 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:751 msgid ":ref:`Install ` the *ATS Report* (`l10n_ec_reports_ats`) module to enable downloading the ATS report in XML format." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:697 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:755 msgid "The Ecuadorian *ATS Report* module depends on the previous installation of the *Accounting* app and the *Ecuadorian EDI module*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:703 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:761 msgid "To issue electronic documents, ensure your company is configured as explained in the :ref:`electronic invoice ` section." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:706 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:764 msgid "In the :abbr:`ATS (Anexo Transaccional Simplificado)`, every document generated in Odoo (invoices, vendor bills, sales and purchases withholdings, credit notes, and debit notes) will be included." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:712 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:770 msgid "When generating a vendor bill, it is necessary to register the authorization number from the invoice that the vendor generated for the purchase. To do so, go to :menuselection:`Accounting --> Vendors --> Bills` and select the bill. Then, enter the number from the vendor's invoice in the :guilabel:`Authorization Number` field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:718 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:776 msgid "Credit and debit notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:720 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:778 msgid "When generating a credit note or debit note manually or through importation, it is necessary to link this note to the sales invoice that is being modified by it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:724 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:782 msgid "Remember to add all required information to the documents before downloading the :abbr:`ATS (Anexo Transaccional Simplificado)` file. For example, add the *Authorization Number* and the *SRI Payment Method* on documents, when needed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:729 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:787 msgid "XML generation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:731 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:789 msgid "To generate the :abbr:`ATS (Anexo Transaccional Simplificado)` report, go to :menuselection:`Accounting --> Reports --> Tax Report` and choose a time period for the desired :abbr:`ATS (Anexo Transaccional Simplificado)` report, then click :guilabel:`ATS`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:735 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:793 msgid "The downloaded XML file is ready to be uploaded to *DIMM Formularios*." msgstr "" @@ -20166,7 +20548,7 @@ msgstr "" msgid "ATS report download for Ecuador in Odoo Accounting." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:742 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:800 msgid "When downloading the :abbr:`ATS (Anexo Transaccional Simplificado)` report, Odoo generates a warning pop-up alerting the user if a document(s) has missing or incorrect data. Nevertheless, the user can still download the XML file." msgstr "" @@ -20441,7 +20823,7 @@ msgid ":guilabel:`Product Type`: storable products, consumables, or services." msgstr "" #: ../../content/applications/finance/fiscal_localizations/egypt.rst:177 -msgid ":guilabel:`Unit of Measure`: if you also use Odoo Inventory and have enabled :doc:`Units of Measure <../../inventory_and_mrp/inventory/product_management/product_replenishment/uom>`." +msgid ":guilabel:`Unit of Measure`: if you also use Odoo Inventory and have enabled :doc:`Units of Measure <../../inventory_and_mrp/inventory/product_management/configure/uom>`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/egypt.rst:179 @@ -22006,24 +22388,37 @@ msgid "FPS bank account configuration." msgstr "" #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:61 -msgid "The account holder's country **must** be set to `Hong Kong` on their contact form." +msgid "The account holder's country must be set to `Hong Kong` on its contact form." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:64 -#: ../../content/applications/finance/fiscal_localizations/singapore.rst:33 -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:144 -#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:34 -msgid ":doc:`../accounting/bank`" +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:62 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:26 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:138 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:27 +msgid "The account holder's city is mandatory." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:63 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:27 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:28 +msgid "You could also include the invoice number in the QR code by checking the :guilabel:`Include Reference` checkbox." msgstr "" #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:67 -#: ../../content/applications/finance/fiscal_localizations/singapore.rst:36 -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:147 -#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:37 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:34 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:145 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:35 +msgid ":doc:`../accounting/bank`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:70 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:37 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:148 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:38 msgid "Bank journal configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:69 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:72 msgid "Go to :menuselection:`Accounting app --> Configuration --> Journals` and open the bank journal. Then, fill out the :guilabel:`Account Number` and :guilabel:`Bank` fields, located in the :guilabel:`Journal Entries` tab." msgstr "" @@ -22031,12 +22426,12 @@ msgstr "" msgid "Bank Account's journal configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:78 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:81 msgid "Issue invoices with FPS QR codes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:80 -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:158 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:83 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:159 msgid "When creating a new invoice, open the :guilabel:`Other Info` tab and set the :guilabel:`Payment QR-code` option to :guilabel:`EMV Merchant-Presented QR-code`." msgstr "" @@ -22044,159 +22439,159 @@ msgstr "" msgid "Select EMV Merchant-Presented QR-code option." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:87 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:90 msgid "Ensure that the :guilabel:`Recipient Bank` is configured, as Odoo uses this field to generate the FPS QR code." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:96 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:99 msgid "Ensure the :guilabel:`Hong Kong - Payroll` (`l10n_hk_hr_payroll`) module is installed before proceeding." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:100 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:103 msgid "Create employees" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:102 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:105 msgid "Go to the :menuselection:`Employees` app and click :guilabel:`New`. Then, configure the following fields:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:105 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:108 msgid "Under the :guilabel:`Work Information` tab" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:107 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:110 msgid ":guilabel:`Working Hours`: :guilabel:`HK Standard 40 hours/week` option **must** be selected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:109 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:112 msgid "Under the :guilabel:`Private Information` tab" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:111 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:114 msgid ":guilabel:`Surname, Given Name, Name in Chinese`: name of the employee." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:112 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:115 msgid ":guilabel:`Private Address`: address of the employee." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:113 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:116 msgid ":guilabel:`Bank Account Number`: employee's bank account number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:114 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:117 msgid ":guilabel:`Current Rental`: employee's rental records (if rental allowance is applicable)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:115 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:118 msgid ":guilabel:`Autopay Type`: :guilabel:`BBAN`, :guilabel:`SVID`, :guilabel:`EMAL`, etc." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:116 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:119 msgid ":guilabel:`Autopay Reference`: autopay reference number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:117 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:120 msgid ":guilabel:`Identification No`: HKID of the employee." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:118 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:121 msgid ":guilabel:`Gender`: gender of the employee." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:121 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:124 msgid "For the :guilabel:`Bank Account Number`, this account should be set as :guilabel:`Trusted` before further processing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:124 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:127 msgid "To achieve this, click on the right-arrow button next to :guilabel:`Bank Account Number` field. Set the :guilabel:`Send Money` to :guilabel:`Trusted` by clicking on the toggle." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:128 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:131 msgid "To populate the :guilabel:`Current Rental`, click on the :guilabel:`History` button. Then, click on :guilabel:`New`. Fill in the relevant details and save the rental record. Upon saving the record, the rental contract :guilabel:`state` will be visible (at the top-right corner) and can be set to :guilabel:`Running`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:133 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:136 msgid "Under the :guilabel:`HR Settings` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:135 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:138 msgid ":guilabel:`Volunteer Contribution Option`: select either :guilabel:`Only Mandatory Contribution`, :guilabel:`With Fixed %VC`, or :guilabel:`Cap 5% VC`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:137 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:140 msgid ":guilabel:`MPF Manulife Account`: account number, if applicable." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:142 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:145 msgid "Manage contracts" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:144 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:147 msgid "Once the new employee has been created, click the :guilabel:`Contracts` smart button on the employee record, or navigate to :menuselection:`Employees app --> Employees --> Contracts`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:148 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:151 msgid "Only **one** contract can be active simultaneously per employee, but an employee can be assigned consecutive contracts during their employment." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:151 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:154 msgid "The following are critical for setting up a contract:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:153 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:156 msgid ":guilabel:`Salary Structure Type`: set as :guilabel:`CAP57: Hong Kong Employee`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:154 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:157 msgid ":guilabel:`Contract Start Date`: start date of employment." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:155 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:158 msgid ":guilabel:`Working Schedule`: set as :guilabel:`HK Standard 40 hours/week` (from employee record)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:156 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:159 msgid ":guilabel:`Work Entry Source`: select either :guilabel:`Working Schedule`, :guilabel:`Attendances` or :guilabel:`Planning`. This field determines how the work entries are accounted for in the payslip." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:160 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:163 msgid ":guilabel:`Working Schedule`: the work entries are generated automatically based on the employee's working schedule." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:162 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:165 msgid ":guilabel:`Attendances`: the work entries are generated based on the check-in/out period logged in the *Attendances*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:164 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:167 msgid ":guilabel:`Planning`: the work entries are generated from planning shifts only." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:166 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:169 msgid "Under the :guilabel:`Salary Information` tab" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:168 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:171 msgid ":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for Full-time or Part-time employees, or :guilabel:`Hourly Wage` for employees who are paid hourly." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:170 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:173 msgid ":guilabel:`Schedule Pay`: the frequency of payslip issuance." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:171 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:174 msgid ":guilabel:`Wage`: :guilabel:`Monthly` or :guilabel:`Hourly` depending on the :guilabel:`Wage Type`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:173 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:176 msgid ":guilabel:`Internet Subscription`: this is an **optional** field to provide additional internet allowance on top of the current salary package." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:177 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:180 msgid "Timesheets do **not** impact work entries in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:179 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:182 msgid "Once all information has been setup, set the contract status to :guilabel:`Running` by clicking the :guilabel:`Running` button in the top-right of the page." msgstr "" @@ -22204,35 +22599,35 @@ msgstr "" msgid "Hong Kong employment contract." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:189 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:192 msgid "Generate payslips" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:191 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:194 msgid "Once the employees, and their contracts, are configured, payslips can be generated in the *Payroll* app." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:194 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:197 msgid "Odoo provides **four** different salary structures under CAP57 regulation:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:196 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:199 msgid ":guilabel:`CAP57: Employees Monthly Pay`: to process the monthly employee salary." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:197 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:200 msgid ":guilabel:`CAP57: Payment in Lieu of Notice`: to process final payment upon contract termination using :abbr:`ADW (Average Daily Wage)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:199 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:202 msgid ":guilabel:`CAP57: Long Service Payment`: applicable to employees with more than five years of service upon contract termination." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:201 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:204 msgid ":guilabel:`CAP57: Severance Payment`: applicable to employees with more than two years of service upon contract termination." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:204 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:207 msgid "Before running the payslips, the accounts used in the salary rule can be adjusted by navigating to :menuselection:`Payroll app --> Configuration --> Rules`." msgstr "" @@ -22240,126 +22635,126 @@ msgstr "" msgid "Hong Kong Salary Rules." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:211 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:214 msgid "Odoo can create pay runs in two ways: via :ref:`batch ` or :ref:`individual ` payslips." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:217 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:220 msgid "Batch payslips" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:219 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:222 msgid "This method of payslip generation is used for recurring payments, since multiple employee payslips can be managed at once. Go to :menuselection:`Payroll app --> Payslips --> Batches`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:222 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:246 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:494 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:514 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:225 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:249 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:497 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:517 msgid "Click on :guilabel:`New`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:223 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:226 msgid "Enter a :guilabel:`Batch Name` (e.g. `2024 - Jan`) and :guilabel:`Period` (e.g. `01/01/2024` - `01/31/2024`)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:225 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:228 msgid "Click on :guilabel:`Generate Payslips`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:226 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:229 msgid "Choose which :guilabel:`Salary Structure` to use for this batch. The department filter allows the batch to only apply to a specific group of employees." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:228 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:231 msgid "Click on :guilabel:`Generate`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:229 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:232 msgid "A :guilabel:`Payslips` smart button is created automatically." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:231 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:234 msgid "Next, click :guilabel:`Create Draft Entry` to generate a draft journal entry found in the :guilabel:`Other Info` tab of each payslip. A :guilabel:`Confirmation` pop-up window appears asking :guilabel:`Are you sure you want to proceed?`. Click :guilabel:`Ok` to create the journal entries." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:238 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:241 msgid "Individual payslips" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:240 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:243 msgid "Go to :menuselection:`Payroll app --> Payslips --> All Payslips`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:242 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:245 msgid "This method of payslip generation is commonly used to handle non-recurring payments (e.g. :guilabel:`CAP57: Payment in Lieu of Notice`, :guilabel:`CAP57: Long Service Payment` or :guilabel:`CAP57: Severance Payment`)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:247 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:250 msgid "Select an :guilabel:`Employee`. When selected, the :guilabel:`Contract` is filled out automatically." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:249 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:252 msgid "Add a pay :guilabel:`Period`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:250 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:253 msgid "Select a salary :guilabel:`Structure` (e.g. :guilabel:`CAP57: Employees Monthly Pay`)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:251 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:254 msgid "The :guilabel:`Worked Days & Inputs` tab automatically compute the worked days/hours and time off leaves that are applicable." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:253 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:256 msgid "Additional payslip items can be added at this time (e.g. :guilabel:`Commissions`, :guilabel:`Deductions`) under the :guilabel:`Other Inputs` section." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:255 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:258 msgid "Click on :guilabel:`Compute Sheet` button to generate the payslip lines. This button updates the :guilabel:`Salary Computation` tab." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:259 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:262 msgid "If the work entry for an employee was amended, click the :icon:`fa-cog` :guilabel:`(gear)` icon, then click :guilabel:`Recompute Whole Sheet` to refresh the payslip's :guilabel:`Worked Days & Inputs` tab." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:263 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:266 msgid "The :guilabel:`Salary Computation` tab shows the detailed breakdown of the computation, based on the salary rules configured for each structure type." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:266 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:269 msgid ":guilabel:`Rent Allowance`: amount derived from the employee's active rental record." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:267 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:270 msgid ":guilabel:`Basic Salary`: amount of base salary provided (after rent allowance deduction)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:268 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:271 msgid ":guilabel:`713 Gross`: net payable amount considering *Commission*, *Internet Allowance*, *Reimbursements*, *Back-pay*, *Deduction*, etc." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:270 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:273 msgid ":guilabel:`MPF Gross`: net payable amount from 713 gross after consideration of additional allowances, deductions, and end-of-year payment." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:272 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:275 msgid ":guilabel:`Employee Mandatory Contribution`: employee MPF Contribution." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:273 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:276 msgid ":guilabel:`Employer Mandatory Contribution`: employer MPF Contribution." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:274 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:277 msgid ":guilabel:`Gross`: net payable amount from MPF gross after consideration of MPF deductions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:275 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:278 msgid ":guilabel:`Net Salary`: final payable amount to be paid to the employee." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:278 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:281 msgid "There are no MPF contributions for the first month. Both employee and employer contribution starts on second month." msgstr "" @@ -22367,87 +22762,87 @@ msgstr "" msgid "Hong Kong Salary computation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:285 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:288 msgid "Under the :guilabel:`Other Inputs` section in :guilabel:`Worked Days & Inputs` tab, there are additional manual input types:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:288 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:291 msgid ":guilabel:`Back Pay`: additional salary payout can be included under this category." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:289 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:292 msgid ":guilabel:`Commission`: the commission earned during the period can be manually entered here." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:290 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:293 msgid ":guilabel:`Global Deduction`: a lump-sum deduction from the entire payslip." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:291 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:294 msgid ":guilabel:`Global Reimbursement`: a lump-sum reimbursement to the entire payslip." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:292 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:295 msgid ":guilabel:`Referral Fee`: the additional bonus offered for any form of business-related referral." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:293 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:296 msgid ":guilabel:`Moving Daily Wage`: to override the :abbr:`ADW (Average Daily Wage)` value used for leaves computation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:295 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:298 msgid ":guilabel:`Skip Rent Allowance`: if set, the rental allowance is excluded from the current payslip." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:297 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:300 msgid ":guilabel:`Custom Average Monthly Salary`: to override the average monthly salary used for end-of-year payment (rule is only applicable to payslips generated in December)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:299 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:302 msgid ":guilabel:`Lieu of Notice Period (Months)`: only applicable to :guilabel:`CAP57: Payment in Lieu of Notice` salary structure. By default, the final payout is set as 1-month. Use the :guilabel:`Count` field under the :guilabel:`Other Inputs` section to set a different notice period duration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:304 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:307 msgid "Once the payslips are ready, click on :guilabel:`Compute Sheet`, followed by :guilabel:`Create Draft entry` to generate a draft journal entry found in the :guilabel:`Other Info` tab of the payslip." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:310 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:313 msgid "Once the draft journal entries have been posted, the company can now pay the employees. The user can choose between **two** different *payment methods*:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:313 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:316 msgid "From the employee's payslip (:menuselection:`Payroll app --> Payslips --> All Payslips`), once the payslip's journal entry has been posted, click :guilabel:`Register Payment`. The process is the same as :doc:`paying vendor bills <../accounting/payments>`. Select the desired bank journal and payment method, then later reconcile the payment with the corresponding bank statement." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:317 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:320 msgid "For batch payments (:menuselection:`Payroll app --> Payslips --> Batches`), once all draft journal entries from the batch are confirmed, click :guilabel:`Mark as Paid` to post the payment journal entry. Then :doc:`create a payment <../accounting/payments>` in the *Accounting* app, and reconcile accordingly." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:323 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:326 msgid "Attendances and hourly wage" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:325 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:328 msgid "To configure the contract for an employee paid hourly using the *Attendances* app for hours tracking, navigate to :menuselection:`Payroll app --> Contracts --> Contracts`. Create a new :ref:`contract `. It is important to remember to set the :guilabel:`Work Entry Source` as :guilabel:`Attendances`, and :guilabel:`Wage Type` as :guilabel:`Hourly Wage`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:331 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:334 msgid "To record the hours logged by the employee using *Attendances* app:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:333 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:336 msgid "Go to :menuselection:`Attendances app`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:334 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:337 msgid "The employee can check-in/out, via the kiosk mode and the time will be logged automatically." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:335 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:338 msgid "In the :menuselection:`Payroll app`, review the attendance work entries generated from :menuselection:`Payroll app --> Work Entries --> Work Entries`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:337 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:340 msgid "Next, generate the :ref:`payslips ` and process the payment." msgstr "" @@ -22459,27 +22854,27 @@ msgstr "" msgid "Hong Kong Attendance Payslip." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:348 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:351 msgid "Time Off with Payroll" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:350 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:353 msgid "The work entry types and time off types are fully integrated between the *Time Off* and *Payroll* apps. There are several default time off types and work entry types specific to Hong Kong which are installed automatically along with the *Hong Kong - Payroll* module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:354 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:357 msgid "Go to :menuselection:`Payroll app --> Configuration --> Work Entry Types` and click :guilabel:`New`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:356 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:359 msgid "There are two checkboxes to be considered when setting up the work entry type:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:358 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:361 msgid ":guilabel:`Use 713`: Include this leave type as part of 713 computation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:359 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:362 msgid ":guilabel:`Non-full pay`: 80% of the :abbr:`ADW (Average Daily Wage)`." msgstr "" @@ -22487,148 +22882,148 @@ msgstr "" msgid "Hong Kong Work Entry Type." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:366 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:369 msgid ":ref:`Creating and configuring work entry types `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:369 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:372 msgid "Understanding 713 Ordinance" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:371 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:374 msgid "The *Hong Kong - Payroll* module is compliant with 713 Ordinance which relates to the :abbr:`ADW (Average Daily Wage)` computation to ensure fair compensation for employees." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:374 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:377 msgid "The ADW computation is as follows:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:379 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:382 msgid "Hong Kong ADW Formula." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:379 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:382 msgid ":abbr:`ADW (Average Daily Wage)` equals the total wage in a 12-month period, minus the wages of non-full pay, divided by the total days in a 12-month period minus the days of non-full pay." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:383 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:386 msgid "For 418 compliance, there is no automated allocation of the *Statutory Holiday* entitlement to the employees. As soon as 418 requirements are met, manually allocate the leaves, via the *Time Off* app." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:388 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:391 msgid "Before generating payslips, ensure the statuses are :guilabel:`Done` to validate the outcome." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:393 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:396 msgid "Period" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:394 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:397 msgid "Days" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:395 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:398 msgid "Wage" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:396 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:399 msgid "Commission" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:398 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:401 msgid "ADW" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:399 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:402 msgid "Leave Value" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:400 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:403 msgid "Jan" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:401 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:415 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:404 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:418 msgid "31" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:402 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:404 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:409 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:405 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:407 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:412 msgid "$20200" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:405 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:408 msgid "$651.61 ($20200/31)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:406 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:413 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:409 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:416 msgid "N/A" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:407 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:410 msgid "Feb" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:408 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:411 msgid "28" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:410 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:413 msgid "$5000" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:411 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:414 msgid "$25200" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:412 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:415 msgid "$769.49 ($45400/59)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:414 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:417 msgid "Mar (One Day Annual Leave)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:416 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:418 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:419 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:421 msgid "$20324.33" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:419 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:422 msgid "$730.27 ($65724.33/90)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:420 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:423 msgid "$769.49" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:421 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:424 msgid "Apr (One Day 80% Sick Leave)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:423 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:426 msgid "$20117.56" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:427 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:430 msgid "$584.22 ($730.27*0.8)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:430 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:433 msgid "Here is an example demonstrating the 713 logic:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:432 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:435 msgid "**Jan**: Generate a payslip with a monthly wage of $20200. The :abbr:`ADW (Average Daily Wage)` is always computed on a cumulative basis of the trailing 12-months." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:434 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:437 msgid "**Feb**: Generate a similar payslip, but add an :guilabel:`Other Input Type` for the :guilabel:`Commission`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:436 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:439 msgid "**Mar**: Apply for **one** full-paid annual leave in March. The salary compensation for the leave taken is based on :abbr:`ADW (Average Daily Wage)` thus far." msgstr "" @@ -22636,7 +23031,7 @@ msgstr "" msgid "Hong Kong March 713." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:443 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:446 msgid "**Apr**: Apply for a 1-day non-full pay leave in April. Since this is a non-full pay leave, the :abbr:`ADW (Average Daily Wage)` is computed accordingly." msgstr "" @@ -22644,55 +23039,55 @@ msgstr "" msgid "Hong Kong April 713." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:451 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:454 msgid "The value of :abbr:`ADW (Average Daily Wage)` is computed in the backend, and not be visible to the user." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:455 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:458 msgid "`HK 713 Ordinance `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:456 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:459 msgid "`HK 418 Ordinance `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:459 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:462 msgid "Generate reports" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:461 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:464 msgid "Before generating the below reports, setup the following in :menuselection:`Settings app --> Payroll`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:464 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:467 msgid "Configure the following in the :guilabel:`Accounting` section:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:466 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:469 msgid "Tick the :guilabel:`Payroll HSBC Autopay` checkbox." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:468 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:471 msgid ":guilabel:`Autopay Type`: Set as :guilabel:`H2H Submission`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:469 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:472 msgid "Select the :guilabel:`Bank Account` to use." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:471 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:474 msgid "Configure the following in the :guilabel:`HK Localization` section:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:473 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:476 msgid ":guilabel:`Employer's Name shows on reports`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:474 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:477 msgid ":guilabel:`Employer's File Number`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:475 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:478 msgid ":guilabel:`Manulife MPF Scheme`" msgstr "" @@ -22700,47 +23095,47 @@ msgstr "" msgid "Hong Kong Payroll Settings." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:482 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:485 msgid "IRD report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:484 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:487 msgid "There are a total of **four** IRD reports available:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:486 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:489 msgid ":guilabel:`IR56B`: employer's Return of Remuneration and Pensions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:487 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:490 msgid ":guilabel:`IR56E`: notification of Commencement of Employment." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:488 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:491 msgid ":guilabel:`IR56F`: notification of Ceasation of Employment (remaining in HK)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:489 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:492 msgid ":guilabel:`IR56G`: notification of Ceasation of Employment (departing from HK permanently)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:491 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:494 msgid "Go to :menuselection:`Payroll app --> Reporting`, and select one of the :guilabel:`IR56B/E/F/G Sheet` options:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:495 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:498 msgid "Fill in the relevant information for the IRD report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:496 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:499 msgid "Click on :guilabel:`Populate`, and the :guilabel:`Eligible Employees` smart button appears." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:497 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:500 msgid "The :guilabel:`Employee Declarations` status is :guilabel:`Draft` and changed to :guilabel:`Generated PDF` status once the schedule runs." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:499 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:502 msgid "Once the PDF is generated, the IRD form may be downloaded." msgstr "" @@ -22748,27 +23143,27 @@ msgstr "" msgid "Hong Kong IR56B report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:506 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:509 msgid "The scheduled action called *Payroll: Generate pdfs* can be manually triggered. It is set by default to run the PDF generation monthly." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:510 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:513 msgid "Manulife MPF sheet" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:512 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:515 msgid "Go to :menuselection:`Payroll app --> Reporting --> Manulife MPF Sheet`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:515 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:518 msgid "Select the relevant :guilabel:`Year`, :guilabel:`Month`, and :guilabel:`Sequence No.`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:516 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:519 msgid "Click on :guilabel:`Create XLSX`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:517 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:520 msgid "The *Manulife MPF XLSX* file is then generated, and available for download." msgstr "" @@ -22776,19 +23171,19 @@ msgstr "" msgid "Hong Kong Manulife Sheet." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:524 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:527 msgid "Odoo will not be developing further reports for other MPF trustee as there will soon be an eMPF platform setup by the local government." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:528 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:531 msgid "`eMPF `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:531 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:534 msgid "HSBC autopay report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:533 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:536 msgid "If *HSBC Autopay* is selected as the batch payment method, click on :guilabel:`Create HSBC Autopay Report`, and fill in the mandatory fields:" msgstr "" @@ -22796,7 +23191,7 @@ msgstr "" msgid "Hong Kong HSBC Autopay wizard." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:540 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:543 msgid "This creates an :file:`.apc` file format which can be uploaded to the HSCB portal for processing." msgstr "" @@ -25011,7 +25406,7 @@ msgid "In order to electronically sign any documents in Odoo, ensure the *Sign* msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:43 -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:554 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:551 msgid "Requirements" msgstr "" @@ -25428,26 +25823,26 @@ 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:" +msgid "One addition of the Mexican localization is the :guilabel:`Payment Policy` field. According to the SAT documentation, there are two types of payments:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:377 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:376 msgid "`PUE` (Pago en una Sola Exhibición/Payment in a Single Exhibition)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:378 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:377 msgid "`PPD` (Pago en Parcialidades o Diferido/Payment in Installements or Deferred)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:381 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:380 msgid ":doc:`../../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:383 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:382 msgid "The difference lies in the *Due Date* or *Payment Terms* of the invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:385 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:384 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 "" @@ -25455,11 +25850,11 @@ msgstr "" msgid "Example of an invoice with the PUE requirements." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:395 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:394 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:398 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:397 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 "" @@ -25467,43 +25862,43 @@ msgstr "" msgid "Example of an invoice with the PPD requirements." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:407 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:406 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:412 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:411 msgid "Payment flow" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:414 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:413 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:418 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:417 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:425 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:424 msgid ":doc:`../accounting/bank/reconciliation`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:427 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:426 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:431 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:430 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:435 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:434 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:439 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:438 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:443 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:442 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 "" @@ -25511,63 +25906,63 @@ msgstr "" msgid "CFDI (4.0) E-invoicing service process payment now message." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:452 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:451 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:457 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:456 msgid "Invoice cancellations" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:459 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:458 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:463 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:462 msgid "With all cancellation requests, you **must** specify a *cancellation reason*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:464 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:463 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:467 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:466 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:470 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:469 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:474 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:473 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:480 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:479 msgid "01 - invoices sent with errors with a relation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:482 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:481 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:485 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:484 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:490 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:489 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:495 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:494 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:498 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:497 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:503 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:502 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 "" @@ -25579,55 +25974,55 @@ msgstr "" msgid "Invoice with the Substituted By field referencing the CFDI Origin invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:515 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:514 msgid "02 - invoices sent with errors without a relation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:517 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:516 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:520 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:519 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:524 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:523 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:528 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:527 msgid "Payment cancellations" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:530 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:529 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:536 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:535 msgid "Finally, the payment status is moved to :guilabel:`Cancelled`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:539 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:538 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:543 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:542 msgid "Invoicing special use cases" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:546 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:545 msgid "CFDI to public" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:548 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:547 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:551 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:550 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:556 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:555 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 "" @@ -25635,19 +26030,19 @@ msgstr "" msgid "CFDI to Public Customer field configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:567 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:566 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:574 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:573 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:577 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:576 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:581 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:580 msgid "The only currencies that automatically update their exchange rate daily are: USD, EUR, GBP, and JPY." msgstr "" @@ -25655,91 +26050,91 @@ msgstr "" msgid "Multi-currency configuration in the Accounting settings." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:589 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:588 msgid "Down payments" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:591 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:590 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:597 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:596 msgid "`The official documentation for registration of down payments in Mexico `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:600 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:599 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:604 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:603 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:607 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:606 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:610 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:609 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:614 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:613 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:618 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:617 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:622 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:621 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:628 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:627 msgid "External trade" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:630 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:629 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 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:633 msgid "The specific address of the receiver and the sender" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:635 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:634 msgid "The addition of a :guilabel:`Tariff Fraction` that identifies the type of product" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:636 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:635 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:639 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:638 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:642 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:641 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:645 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:644 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:649 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:648 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:658 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:657 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:665 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:664 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:669 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:668 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 "" @@ -25747,23 +26142,23 @@ msgstr "" msgid "Optional external trade company fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:677 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:676 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:681 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:680 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:683 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:682 msgid "The format of the foreign :guilabel:`VAT` (tax identification number, for example: Colombia `123456789-1`)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:685 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:684 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:689 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:688 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 "" @@ -25771,27 +26166,27 @@ msgstr "" msgid "Required external trade customer fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:699 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:698 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:705 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:704 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:708 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:707 msgid "The :guilabel:`Internal Reference` of the product is in the :guilabel:`General Information` tab." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:709 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:708 msgid "The :guilabel:`Weight` of the product must be more than `0`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:710 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:709 msgid "The `correct `_ :guilabel:`Tariff Fraction` of the product in the :guilabel:`Accounting` tab." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:712 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:711 msgid "The :guilabel:`UMT Aduana` corresponds to the :guilabel:`Tariff Fraction`." msgstr "" @@ -25799,19 +26194,19 @@ msgstr "" msgid "Required external trade product fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:719 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:718 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:721 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:720 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:727 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:726 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:733 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:732 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 "" @@ -25819,63 +26214,63 @@ msgstr "" msgid "External trade Other Info tab of a product." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:741 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:740 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:747 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:746 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:750 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:749 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:754 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:753 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:757 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:756 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:761 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:760 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:765 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:764 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:771 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:770 msgid "Odoo manages two different types of CFDI:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:773 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:772 msgid "**No Federal Highways**: Is used when the *Distance to Destination* is `less than 30 KM `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:775 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:774 msgid "**Federal Transport**: Is used when the *Distance to Destination* exceeds 30 KM." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:777 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:776 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:780 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:779 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:784 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:783 msgid "Contacts and vehicles" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:786 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:785 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:791 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:790 msgid "The field, :guilabel:`Locality`, is optional for both addresses." msgstr "" @@ -25883,23 +26278,23 @@ msgstr "" msgid "Delivery guide contact configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:798 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:797 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:802 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:801 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:806 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:805 msgid "All fields are mandatory to create a correct delivery guide." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:809 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:808 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:812 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:811 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 "" @@ -25907,19 +26302,19 @@ msgstr "" msgid "Delivery guide vehicle configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:822 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:821 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:825 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:824 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:827 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:826 msgid "In the :guilabel:`Inventory` tab, the field :guilabel:`Weight` should have more than `0`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:830 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:829 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 "" @@ -25927,27 +26322,27 @@ msgstr "" msgid "Delivery guide product configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:839 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:838 msgid "Sales and inventory flow" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:841 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:840 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:845 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:844 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 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:848 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:853 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:852 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:856 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:855 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 "" @@ -25955,15 +26350,15 @@ msgstr "" msgid "Delivery guide MX EDI tab configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:865 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:864 msgid "Dangerous hazards" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:867 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:866 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:872 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:871 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 "" @@ -25971,7 +26366,7 @@ msgstr "" msgid "Delivery guide hazardous material product required fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:880 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:879 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 "" @@ -25979,59 +26374,59 @@ msgstr "" msgid "Delivery Guide environment insurer required fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:889 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:888 msgid "Customs numbers" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:891 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:890 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:895 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:894 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:899 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:898 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:904 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:903 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:911 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:910 msgid "In order to track the correct customs number for a specific invoice, Odoo uses :doc:`landed costs <../../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs>`. Go to :menuselection:`Inventory --> Configuration --> Settings --> Valuation`. Make sure that :guilabel:`Landed Costs` is activated." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:916 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:915 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:919 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:918 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:922 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:921 msgid ":guilabel:`Costing Method`: Either :guilabel:`FIFO` or :guilabel:`AVCO`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:923 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:922 msgid ":guilabel:`Inventory Valuation`: :guilabel:`Automated`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:924 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:923 msgid ":guilabel:`Stock Valuation Account`: :guilabel:`115.01.01 Inventario`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:925 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:924 msgid ":guilabel:`Stock Journal`: :guilabel:`Inventory Valuation`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:926 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:925 msgid ":guilabel:`Stock Input Account`: :guilabel:`115.05.01 Mercancías en tránsito`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:927 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:926 msgid ":guilabel:`Stock Output Account`: :guilabel:`115.05.01 Mercancías en tránsito`" msgstr "" @@ -26043,27 +26438,27 @@ msgstr "" msgid "Storable product category configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:938 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:937 msgid "Purchase and sales flow" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:940 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:939 msgid "After you configure your product, follow the standard :doc:`purchase flow <../../inventory_and_mrp/purchase>`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:943 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:942 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:947 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:946 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:950 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:949 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:954 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:953 msgid "You can only add the *Pedimentos* number **once**, so be careful when associating the correct number with the transfer(s)." msgstr "" @@ -26071,11 +26466,11 @@ msgstr "" msgid "Customs number on a landed costs Inventory record." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:961 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:960 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:964 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:963 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 "" @@ -26083,83 +26478,83 @@ msgstr "" msgid "Customs number on confirmed sales order product." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:973 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:972 msgid "Electronic accounting" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:975 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:974 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:980 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:979 msgid "It consists of three main XML files:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:982 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:981 msgid "The updated list of the chart of accounts that you are currently using." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:983 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:982 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:984 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:983 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:987 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:986 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:990 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:989 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:995 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:994 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:1000 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:999 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:1004 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1003 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:1013 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1012 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:1017 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1016 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:1021 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1020 msgid "Some examples are `102.01.99` or `401.01.001`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1023 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1022 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:1027 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1026 msgid "Once you create all your accounts, make sure the correct :guilabel:`Tags` are added." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1030 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1029 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 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1032 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:1040 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1039 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:1043 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1042 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 "" @@ -26167,23 +26562,23 @@ msgstr "" msgid "Trial balance report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1052 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1051 msgid "Odoo does not generate the *Balanza de Comprobación Complementaria*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1054 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1053 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:1057 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1056 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:1061 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1060 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:1065 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1064 msgid "The XML file is generated by pressing the :guilabel:`SAT (XML)` button." msgstr "" @@ -26195,59 +26590,59 @@ msgstr "" msgid "Trial Balance Month 13 report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1078 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1077 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:1083 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1082 msgid "You can filter by period, or by journal, according to your current needs." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1085 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1084 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:1089 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1088 msgid ":guilabel:`Tax audit`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1090 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1089 msgid ":guilabel:`Audit certification`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1091 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1090 msgid ":guilabel:`Return of goods`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1092 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1091 msgid ":guilabel:`Compensation`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1094 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1093 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:1100 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1099 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:1104 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1103 msgid "DIOT report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1106 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1105 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:1111 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1110 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:1115 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1114 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:1119 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1118 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 "" @@ -26259,7 +26654,7 @@ msgstr "" msgid "DIOT (TXT) download button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1132 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1131 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 "" @@ -27069,7 +27464,7 @@ msgid "The creation of the |GRE| delivery guide in Odoo **must** be sent directl msgstr "" #: ../../content/applications/finance/fiscal_localizations/peru.rst:670 -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:466 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:463 msgid "Required information" msgstr "" @@ -27947,16 +28342,11 @@ msgid "Go to :menuselection:`Contacts --> Configuration --> Bank Accounts` and s msgstr "" #: ../../content/applications/finance/fiscal_localizations/singapore.rst:25 -msgid "The account holder's country must be set to Singapore on its contact form." +msgid "The account holder's country must be set to `Singapore` on its contact form." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/singapore.rst:26 -#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:27 -msgid "You could also include the invoice number in the QR code by checking the :guilabel:`Include Reference` checkbox." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/singapore.rst:38 -#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:39 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:39 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:40 msgid "Go to :menuselection:`Accounting --> Configuration --> Journals`, open the bank journal, then fill out the :guilabel:`Account Number` and :guilabel:`Bank` under the :guilabel:`Journal Entries` tab." msgstr "" @@ -27966,12 +28356,12 @@ msgstr "" msgid "Bank Account's journal configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/singapore.rst:45 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:46 msgid "Issue invoices with PayNow QR codes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/singapore.rst:47 -#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:48 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:48 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:49 msgid "When creating a new invoice, open the :guilabel:`Other Info` tab and set the :guilabel:`Payment QR-code` option to *EMV Merchant-Presented QR-code*." msgstr "" @@ -27981,7 +28371,7 @@ msgstr "" msgid "Select EMV Merchant-Presented QR-code option" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/singapore.rst:53 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:54 msgid "Ensure that the :guilabel:`Recipient Bank` is the one you configured, as Odoo uses this field to generate the PayNow QR code." msgstr "" @@ -28050,22 +28440,26 @@ msgid "Tax Report (Modelo 115);" msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:51 -msgid "Tax Report (Modelo 303);" +msgid "Tax Report (Modelo 130);" msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:52 -msgid "Tax Report (Modelo 347);" +msgid "Tax Report (Modelo 303);" msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:53 -msgid "Tax Report (Modelo 349);" +msgid "Tax Report (Modelo 347);" msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:54 +msgid "Tax Report (Modelo 349);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:55 msgid "Tax Report (Modelo 390)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:56 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:57 msgid "You can access Spain-specific tax reports by clicking on the **book** icon when on a report and selecting its Spain-specific version: :guilabel:`(ES)`." msgstr "" @@ -28073,31 +28467,75 @@ msgstr "" msgid "Spain-specific tax reports." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:63 -msgid "TicketBAI" +#: ../../content/applications/finance/fiscal_localizations/spain.rst:64 +msgid "Modelo 130" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:65 -msgid "`Ticket BAI `_ or **TBAI** is an e-Invoicing system used by the Basque government and its three provincial councils (Álava, Biscay, and Gipuzkoa)." +#: ../../content/applications/finance/fiscal_localizations/spain.rst:67 +msgid "Change the percentage" msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:69 -msgid "Odoo supports the **TicketBAI (TBAI)** electronic invoicing format for all three regions of the **Basque Country**. To enable **TicketBAI**, set your company's :guilabel:`Country` and :guilabel:`Tax ID` under :menuselection:`Settings --> General Settings` in the :guilabel:`Companies` section." +msgid "If you wish to change the percentage computation of the box :guilabel:`[04]` under the :guilabel:`I` section and/or of the box :guilabel:`[09]` under the :guilabel:`II` section:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:72 +msgid "Activate the :ref:`developer mode `, go to :menuselection:`Accounting --> Reporting --> Tax Report`, and select the report :guilabel:`Tax report (Modelo 130)`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:74 -msgid "Then, :ref:`install ` the module :guilabel:`Spain -TicketBAI (l10n_es_edi_TBAI)`, go to :menuselection:`Accounting --> Configuration --> Settings`, and select a **region** in the :guilabel:`Spain Localization` section's :guilabel:`Tax Agency for TBAI` field." +msgid "Click the :icon:`fa-cogs` (:guilabel:`cogs`) icon to the right of :guilabel:`Report: Tax Report (Mod 130) (ES)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:78 -msgid "Once a region is selected, click :guilabel:`Manage certificates (SII/TicketBAI)`, then click :guilabel:`New`, upload the certificate, and enter the password provided by the tax agency." +#: ../../content/applications/finance/fiscal_localizations/spain.rst:76 +msgid "Click the box you wish to change, and in the pop-up window, click on the :guilabel:`percentage` line. In the new pop-up window, change the value in the :guilabel:`Formula` field to the percentage you wish to apply. Repeat this action if you wish to modify the other box as well." msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:82 +msgid "Report agriculture activity" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:84 +msgid "If you wish to have any amount input in the :guilabel:`II` section (from boxes :guilabel:`[08]` to :guilabel:`[11]`), you must change the **industry** of the corresponding contact to :guilabel:`Agriculture`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:88 +msgid "Go to the contact form (:menuselection:`Accounting --> Customers --> Customers` or :menuselection:`Accounting --> Vendors --> Vendors`, for example), and select a contact." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:90 +msgid "In the :guilabel:`Sales & Purchase` tab, set the :guilabel:`Industry` field to :guilabel:`Agriculture`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:93 +msgid "Repeat this operation for all contacts related to the **agriculture** industry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:96 +msgid "TicketBAI" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:98 +msgid "`Ticket BAI `_ or **TBAI** is an e-Invoicing system used by the Basque government and its three provincial councils (Álava, Biscay, and Gipuzkoa)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:102 +msgid "Odoo supports the **TicketBAI (TBAI)** electronic invoicing format for all three regions of the **Basque Country**. To enable **TicketBAI**, set your company's :guilabel:`Country` and :guilabel:`Tax ID` under :menuselection:`Settings --> General Settings` in the :guilabel:`Companies` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:107 +msgid "Then, :ref:`install ` the module :guilabel:`Spain -TicketBAI (l10n_es_edi_TBAI)`, go to :menuselection:`Accounting --> Configuration --> Settings`, and select a **region** in the :guilabel:`Spain Localization` section's :guilabel:`Tax Agency for TBAI` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:111 +msgid "Once a region is selected, click :guilabel:`Manage certificates (SII/TicketBAI)`, then click :guilabel:`New`, upload the certificate, and enter the password provided by the tax agency." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:115 msgid "If you are testing certificates, enable :guilabel:`Test Mode` in the :guilabel:`Spain Localization` section, which can be found under :guilabel:`Accounting` in the **Settings** app." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:89 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:122 msgid "Once an invoice has been :doc:`created <../../finance/accounting/customer_invoices>` and confirmed, a TicketBAI **banner** appears at the top." msgstr "" @@ -28105,15 +28543,15 @@ msgstr "" msgid "TicketBAI banner at the top of the invoice once sent." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:95 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:128 msgid "Odoo sends invoices through TicketBAI automatically every **24 hours**. However, you can click :guilabel:`Process now` to send the invoice immediately." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:98 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:131 msgid "When the invoice is **sent**, the status of the field :guilabel:`Electronic Invoice` changes to :guilabel:`Sent`, and the XML file can be found in the **chatter**. Under the :guilabel:`EDI Documents` tab, you can see the traceability of other generated documents related to the invoice (e.g., if the invoice should also be sent through the **SII**, it will appear here)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:104 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:137 msgid "The TBAI **QR code** is displayed on the invoice PDF." msgstr "" @@ -28121,59 +28559,59 @@ msgstr "" msgid "QR code of the TicketBAI on the invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:110 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:143 msgid "FACe" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:112 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:145 msgid "`FACe `_ is the e-Invoicing platform used by the public administrations in Spain to send electronic invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:115 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:148 msgid "Before configuring the :abbr:`FACe (General Entrance for Electronic Invoices)` system, :ref:`install ` the :guilabel:`Spain - Facturae EDI (l10n_es_edi_facturae)` module and other **Facturae EDI**-related modules." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:119 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:152 msgid "To enable FACe, go to :menuselection:`Settings --> General Settings`, click :guilabel:`Update Info` in the :guilabel:`Companies` section, then click :guilabel:`Update Info` and set the :guilabel:`Country` and :guilabel:`Tax ID` of your company. Next, add the :guilabel:`Facturae signature certificate` by clicking :guilabel:`Add a line`, uploading the certificate provided by the tax agency, and entering the provided password." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:128 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:161 msgid "Once you have :doc:`created <../../finance/accounting/customer_invoices>` an invoice and confirmed it, click :guilabel:`Send & Print`. Make sure :guilabel:`Generate Facturae edi file` is enabled, and click :guilabel:`Send & Print` again. Once the invoice is sent, the generated XML file is available in the **chatter**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:134 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:167 msgid "The file is **NOT** automatically sent. You have to send it yourself manually." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:137 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:170 msgid "You can send **FACe** XML files in batch through `the governmental portal `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:140 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:173 msgid "Administrative centers" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:142 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:175 msgid "In order for **FACe** to work with **administrative centers**, the invoice *must* include specific data about the centers." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:146 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:179 msgid "Make sure to have the :guilabel:`Spain - Facturae EDI - Administrative Centers Patch (l10n_es_edi_facturae_adm_centers)` module :ref:`installed `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:149 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:182 msgid "To add **administrative centers**, create a new **contact** to add to the **partner** company. Select :guilabel:`FACe Center` as the **type**, assign one or more **role(s)** to that contact, and :guilabel:`Save`. The **three** roles usually required are:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:153 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:186 msgid "Órgano gestor: :guilabel:`Receptor` (Receiver);" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:154 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:187 msgid "Unidad tramitadora: :guilabel:`Pagador` (Payer);" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:155 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:188 msgid "Oficina contable: :guilabel:`Fiscal` (Fiscal)." msgstr "" @@ -28181,15 +28619,15 @@ msgstr "" msgid "Administrative center contact form for public entities." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:161 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:194 msgid "If administrative centers need different :guilabel:`Codes` per role, you *must* create different centers for each role." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:163 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:196 msgid "When an electronic invoice is created using a partner with **administrative centers**, *all* administrative centers are included in the invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:165 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:198 msgid "You can add one contact with multiple roles or multiple contacts with a different role each." msgstr "" @@ -28643,7 +29081,7 @@ msgstr "" msgid "Go to :menuselection:`Contacts --> Configuration --> Bank Accounts` and select the bank account for which you want to activate PromptPay QR. Set the :guilabel:`Proxy Type` and fill in the :guilabel:`Proxy Value` field depending on the chosen type." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:138 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:139 msgid "The :guilabel:`Include Reference` checkbox doesn't work for PromptPay QR codes." msgstr "" @@ -28651,15 +29089,15 @@ msgstr "" msgid "PromptPay bank account configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:149 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:150 msgid "Go to :menuselection:`Accounting --> Configuration --> Journals`, open the bank journal, then fill in the :guilabel:`Account Number` and :guilabel:`Bank` under the :guilabel:`Journal Entries` tab." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:156 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:157 msgid "Issue invoices with PromptPay QR code" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:164 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:165 msgid "Ensure that the :guilabel:`Recipient Bank` is the one you configured, as Odoo uses this field to generate the PromptPay QR code." msgstr "" @@ -28995,162 +29433,304 @@ msgstr "" msgid "United Kingdom" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:8 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:10 msgid ":ref:`Install ` the :guilabel:`UK - Accounting` and the :guilabel:`UK - Accounting Reports` modules to get all the features of the UK localization." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:17 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:19 msgid ":guilabel:`UK - Accounting`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:18 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:20 msgid "`l10n_uk`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:19 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:21 msgid "CT600-ready chart of accounts" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:20 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:22 msgid "VAT100-ready tax structure" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:21 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:23 msgid "Infologic UK counties listing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:22 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:24 msgid ":guilabel:`UK - Accounting Reports`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:23 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:25 msgid "`l10n_uk_reports`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:24 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:26 msgid "Accounting reports for the UK" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:25 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:27 msgid "Allows sending the tax report via the MTD-VAT API to HMRC." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:-1 -msgid "Odoo uk packages" +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:28 +msgid ":guilabel:`UK BACS Payment Files`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:32 -msgid "Only UK-based companies can submit reports to HMRC." +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:29 +msgid "`account_bacs`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:30 +msgid "Allows generating :ref:`united-kingdom/BACS-files` for bill and invoice payments" msgstr "" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:33 +msgid "Only UK-based companies can submit reports to HMRC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:34 msgid "Installing the module :guilabel:`UK - Accounting Reports` installs all two modules at once." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:36 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:37 msgid "`HM Revenue & Customs `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:37 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:38 msgid "`Overview of Making Tax Digital `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:43 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:44 msgid "The UK chart of accounts is included in the :guilabel:`UK - Accounting` module. Go to :menuselection:`Accounting --> Configuration --> Accounting: Chart of Accounts` to access it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:46 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:47 msgid "Setup your :abbr:`CoA (chart of accounts)` by going to :menuselection:`Accounting --> Configuration --> Settings --> Accounting Import section` and choose to :guilabel:`Review Manually` or :guilabel:`Import (recommended)` your initial balances." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:53 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:54 msgid "As part of the localization module, UK taxes are created automatically with their related financial accounts and configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:56 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:57 msgid "Go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes` to update the :guilabel:`Default Taxes`, the :guilabel:`Tax Return Periodicity` or to :guilabel:`Configure your tax accounts`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:60 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:61 msgid "To edit existing taxes or to :guilabel:`Create` a new tax, go to :menuselection:`Accounting --> Configuration --> Accounting: Taxes`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:64 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:65 msgid ":doc:`taxes <../accounting/taxes>`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:65 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:66 msgid "Tutorial: `Tax report and return `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:69 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:70 msgid "Making Tax Digital (MTD)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:71 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:72 msgid "In the UK, all VAT-registered businesses have to follow the MTD rules by using software to submit their VAT returns." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:74 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:75 msgid "The **UK - Accounting Reports** module enables you to comply with the `HM Revenue & Customs `_ requirements regarding `Making Tax Digital `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:80 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:81 msgid "If your periodic submission is more than three months late, it is no longer possible to submit it through Odoo, as Odoo only retrieves open bonds from the last three months. Your submission has to be done manually by contacting HMRC." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:87 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:88 msgid "Register your company to HMRC before the first submission" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:89 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:90 msgid "Go to :menuselection:`Accounting --> Reporting --> Tax report` and click on :guilabel:`Connect to HMRC`. Enter your company information on the HMRC platform. You only need to do it once." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:94 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:95 msgid "Periodic submission to HMRC" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:96 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:97 msgid "Import your obligations HMRC, filter on the period you want to submit, and send your tax report by clicking :guilabel:`Send to HMRC`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:100 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:101 msgid "You can use dummy credentials to demo the HMRC flow. To do so, activate the :ref:`developer mode ` and go to :menuselection:`General Settings --> Technical --> System Parameters`. From here, search for `l10n_uk_reports.hmrc_mode` and change the value line to `demo`. You can get such credentials from the `HMRC Developer Hub `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:107 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:108 msgid "Periodic submission to HMRC for multi-company" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:109 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:110 msgid "Only one company and one user can connect to HMRC simultaneously. If several UK-based companies are on the same database, the user who submits the HMRC report must follow these instructions before each submission:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:113 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:114 msgid "Log into the company for which the submission has to be done." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:114 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:115 msgid "Go to :guilabel:`General Settings`, and in the :guilabel:`Users` section, click :guilabel:`Manage Users`. Select the user who is connected to HMRC." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:116 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:117 msgid "Go to the :guilabel:`UK HMRC Integration` tab and click :guilabel:`Reset Authentication Credentials` or :guilabel:`Remove Authentication Credentials` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:118 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:119 msgid "You can now :ref:`register your company to HMRC ` and submit the tax report for this company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:120 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:121 msgid "Repeat the steps for other companies' HMRC submissions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:123 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:124 msgid "During this process, the :guilabel:`Connect to HMRC` button no longer appears for other UK-based companies." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:130 +msgid "Bacs files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:132 +msgid ":abbr:`Bacs (Bankers' Automated Clearing Services)` files are electronic files used in the UK to process payments and transfers between bank accounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:135 +msgid "To enable the use of Bacs files, make sure the :ref:`UK BACS Payment Files ` module is installed, then:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:138 +msgid "Configure your Bacs Service User Number:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:140 +msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` and scroll down to the :guilabel:`Customer Payments` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:142 +msgid "Enter your :guilabel:`Service User Number` under :guilabel:`BACS` and manually save." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:144 +msgid "Configure your **bank** journal:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:146 +msgid "Go to :menuselection:`Accounting --> Configuration --> Journals` and select your **bank** journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:148 +msgid "In the :guilabel:`Journal Entries` tab, configure the :guilabel:`Account Number` and :guilabel:`Bank` fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:150 +msgid "In the :guilabel:`Incoming Payments` and :guilabel:`Outgoing Payments` tabs, make sure the :guilabel:`BACS Direct Debit` payment method is enabled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:153 +msgid "Configure the contacts for whom you wish to use Bacs files: Access the contact form and, in the :guilabel:`Accounting` tab, click :guilabel:`Add a line` and fill in the :guilabel:`Account Number` and :guilabel:`Bank` fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:158 +msgid "Bill payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:160 +msgid "To generate Bacs files for bill payments, set the :guilabel:`Payment Method` to :guilabel:`BACS Direct Debit` when :ref:`registering vendor payments `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:163 +msgid "Then, create a vendor batch payment:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:165 +msgid "Go to :menuselection:`Accounting --> Vendors --> Batch Payments`, and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:166 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:206 +msgid "Select the bank journal in the :guilabel:`Bank` field, set the :guilabel:`Payment Method` to :guilabel:`BACS Direct Credit`, and select a :guilabel:`BACS Processing Date`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:168 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:208 +msgid "Optionally, you can also:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:170 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:210 +msgid "select a :guilabel:`BACS Expiry Date`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:171 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:211 +msgid "enable :guilabel:`BACS Multi Mode` to process the payments on their individual date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:173 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:213 +msgid "Click :guilabel:`Add a line`, select the payments you want to include, click :guilabel:`Select`, then :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:176 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:216 +msgid "Once validated, the Bacs file is available in the chatter. You can also :guilabel:`Re-generate Export File` if you need a new Bacs file for that batch payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:-1 +msgid "Vendor Batch Payment view with generated BACS file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:183 +msgid "Invoice payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:185 +msgid "Before generating Bacs files for invoice payments, you must first create a **BACS Direct Debit Instruction**: Go to :menuselection:`Accounting --> Customers --> BACS Direct Debit Instructions` and click :guilabel:`New`. Select a :guilabel:`Customer`, their :guilabel:`IBAN`, and the :guilabel:`Journal` you wish to use." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:190 +msgid "To generate Bacs files for invoice payments, set the :guilabel:`Payment Method` to :guilabel:`BACS Direct Debit` when :ref:`registering invoice payments `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:194 +msgid "If you register the payment for an invoice linked to a subscription or via :menuselection:`Accounting --> Customers --> Payments`, you can select the :guilabel:`BACS Payment Type`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:198 +msgid ":guilabel:`Direct debit-first collection of a series`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:199 +msgid ":guilabel:`Direct debit single collection`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:200 +msgid ":guilabel:`Direct debit repeating collection in a series`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:201 +msgid ":guilabel:`Direct debit-final collection of a series`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:203 +msgid "Then, create a customer batch payment:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:205 +msgid "Go to :menuselection:`Accounting --> Customers --> Batch Payments`, and click :guilabel:`New`." +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/united_states.rst:15 msgid "The Odoo fiscal localization package for the United States follows the Generally Acceptable Accounting Principles (GAAP) accounting standards and rules used to prepare financial statements, as outlined by the Financial Accounting Standards Board (FASB) and adopted by the Securities and Exchange Commission (SEC)." msgstr "" @@ -29484,19 +30064,19 @@ msgid "View, edit, and sort accounts" msgstr "" #: ../../content/applications/finance/fiscal_localizations/united_states.rst:186 -msgid "Access the *Chart of Accounts* dashboard in Odoo by navigating to :menuselection:`Accounting app --> Configuration --> Accounting: Chart of Accounts`." +msgid "Access the *Chart of Accounts* dashboard in Odoo by navigating to :menuselection:`Accounting app --> Configuration --> Accounting: Chart of Accounts`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/united_states.rst:189 -msgid "From the :guilabel:`Chart of Accounts` dashboard, create new accounts by clicking the purple :guilabel:`New` button in the top-left corner of the dashboard and :ref:`filling in the corresponding form `. Search and sort through existing accounts by using specific :guilabel:`Filters` and :guilabel:`Group By` criteria, which are available in the mega menu under the :guilabel:`Search...` bar." +msgid "From the :guilabel:`Chart of Accounts` dashboard, create new accounts by clicking the :guilabel:`New` button in the top-left corner of the dashboard and :ref:`filling in the corresponding form `. Search and sort through existing accounts by using specific :guilabel:`Filters` and :guilabel:`Group By` criteria, which are available in the search drop-down menu." msgstr "" #: ../../content/applications/finance/fiscal_localizations/united_states.rst:195 -msgid "To filter accounts by category, click the :icon:`fa-caret-down` :guilabel:`(caret down)` icon to access the mega menu and look under the :guilabel:`Filters` column for individual selections. Clicking on a specific category will only show accounts that match that particular filter." +msgid "To filter accounts by category, click the :icon:`fa-caret-down` :guilabel:`(caret down)` icon to access the drop-down menu and look under the :guilabel:`Filters` column for individual selections. Clicking on a specific category will only show accounts that match that particular filter." msgstr "" #: ../../content/applications/finance/fiscal_localizations/united_states.rst:199 -msgid "To view all the available account types, remove all of the filters in the :guilabel:`Search...` bar, and then click the :icon:`fa-caret-down` :guilabel:`(caret down)` icon to access the mega menu. From there, select :guilabel:`Account Type` under the :guilabel:`Group By` column heading to list all of the account types in the table." +msgid "To view all the available account types, remove all of the filters in the search bar, and then click the :icon:`fa-caret-down` :guilabel:`(caret down)` icon to access the drop-down menu. From there, select :guilabel:`Account Type` under the :guilabel:`Group By` column heading to list all of the account types in the table." msgstr "" #: ../../content/applications/finance/fiscal_localizations/united_states.rst:-1 @@ -29532,7 +30112,7 @@ msgid ":ref:`Create a new account `" msgstr "" #: ../../content/applications/finance/fiscal_localizations/united_states.rst:229 -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:334 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:331 msgid ":doc:`../../essentials/search`" msgstr "" @@ -29545,86 +30125,90 @@ msgid "AvaTax" msgstr "" #: ../../content/applications/finance/fiscal_localizations/united_states.rst:246 -msgid "**Avalara AvaTax** is a cloud-based tax calculation and compliance software that integrates with Odoo for the United States and Canadian accounting localizations. Integrating AvaTax with Odoo provides real-time and region-specific tax calculations when items are sold, purchased, and invoiced in the database." +msgid "**Avalara AvaTax** is a cloud-based tax calculation and compliance software that integrates with Odoo for several localizations. Integrating AvaTax with Odoo provides real-time and region-specific tax calculations when items are sold, purchased, and invoiced in the database." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:252 -msgid "AvaTax is only available for integration with databases/companies that have locations in the United States and Canada. This means the fiscal position/country of a database can only be set to the United States or Canada. Reference this documentation for more information: :ref:`avatax/fiscal_country`." +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:251 +msgid "AvaTax is available for integration with databases/companies that have locations in the United States and Canada. Reference the :ref:`avatax/fiscal_country` documentation for more information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:258 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:255 msgid "Refer to the documentation articles below to integrate and configure an AvaTax account with an Odoo database:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:261 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:258 msgid ":doc:`AvaTax integration <../accounting/taxes/avatax>`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:262 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:259 msgid ":doc:`Avalara management portal <../accounting/taxes/avatax/avalara_portal>`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:263 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:260 msgid ":doc:`Calculate taxes with AvaTax <../accounting/taxes/avatax/avatax_use>`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:264 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:261 msgid "`US Tax Compliance: AvaTax elearning video `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:274 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:263 +msgid "Avalara's support documents: `About AvaTax `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:271 msgid "A number of :doc:`report selections <../accounting/reporting>` are readily available for the US localization, under the :menuselection:`Accounting app --> Reporting` drop-down menu:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:277 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:274 msgid ":ref:`Balance Sheet `: a \"snapshot\" of a company's financial position at a specific point in time, which contains an overview of a company's assets, liabilities, and equity." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:280 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:277 msgid ":ref:`Profit & Loss `: otherwise known as a *P&L statement* or *income statement*, provides a summary of a company's revenues, expenses, and profits/losses over a given period of time." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:283 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:280 msgid ":ref:`Cash Flow Statement `: shows how much cash and cash equivalents a company has received and spent in a given period." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:285 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:282 msgid ":ref:`Executive Summary `: an overview report that covers the key performance indicators of a company's financial position, such as revenue, profit, and debt." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:288 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:285 msgid ":ref:`Tax Report `: an official form filed for a tax authority that reports income, expenses, and other pertinent tax information. Tax reports allow taxpayers to calculate their tax liability, schedule tax payments, or request refunds for the overpayment of taxes. In Odoo, the tax report can be made monthly, every two months, quarterly, every 4 months, semi-annually, and annually." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:293 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:290 msgid ":guilabel:`Check Register`: a report that displays cash transactions (regardless of the journal) with their running balance after the transaction. Only visible with the *US - Accounting Reports* (`l10n_us_reports`) module installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:296 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:293 msgid ":ref:`1099 Report `: a CSV download of payments made to non-employees in a period to file electronically in a third-party service. Only visible with the *1099 Reporting* (`l10n_us_1099`) module installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:302 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:299 msgid "Depending on the type of report, certain filters are available at the top of the dashboard:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:304 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:301 msgid "a *date* filter, indicated by a :icon:`fa-calendar` :guilabel:`(calendar)` icon that precedes a date in *MM/DD/YYYY* format. Use this to select a specific date or date range for the report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:306 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:303 msgid "a :icon:`fa-bar-chart` :guilabel:`Comparison` filter, to compare reporting periods against each other" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:308 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:305 msgid "a *journal* filter, as indicated by a :icon:`fa-book` :guilabel:`(book)` icon and the default setting of :guilabel:`All Journals`. Use this filter to specify which journals should be included in the report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:311 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:308 msgid "an *entries type* filter, as indicated by a :icon:`fa-filter` :guilabel:`(filter)` icon, with the default setting of :guilabel:`Posted Entries Only, Accrual Basis`. Use this filter to determine which type of journal entries should be included in the report (e.g. posted or draft), along with the type of accounting method (e.g. accrual or cash basis)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:316 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:313 msgid "There are view options in this filter, as well, one that will :guilabel:`Hide lines at 0` for more relevant viewing, along with a :guilabel:`Split Horizontally` option to keep the report above the screen's fold, removing the need to scroll." msgstr "" @@ -29632,47 +30216,47 @@ msgstr "" msgid "Accounting method filter menu for reports, covering accrual vs. cash basis methods." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:324 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:321 msgid "a *decimal* filter, that by default, includes figures with cents, as indicated by the :guilabel:`In .$` setting. Use the other options in the drop-down menu to change figures in the report to whole numbers (:guilabel:`In $`), thousands (:guilabel:`In K$`), or millions (:guilabel:`In M$`) formats." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:328 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:325 msgid "a report *customization* filter, indicated by the :icon:`fa-cogs` :guilabel:`(gears)` icon. Use this filter to customize the current report's sections and line items, or build new reports, as desired." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:333 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:330 msgid ":doc:`Accounting reporting <../accounting/reporting>`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:341 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:338 msgid "The 1099 report, available by :ref:`installing ` the *1099 Reporting* (`l10n_us_1099`) module, includes payments that are made to non-employees across a given reporting period. Use the available CSV download from the report in Odoo to file 1099 payments electronically via a third-party service." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:346 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:343 msgid "To generate a 1099 report, navigate to :menuselection:`Accounting app --> Reporting --> Management: 1099 Report` to open a :guilabel:`1099 Report` wizard." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:349 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:346 msgid "First, enter the date range of the transactions to report in the :guilabel:`Start Date` and :guilabel:`End Date` fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:352 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:349 msgid "Then, edit the journal items that appear on the wizard. Click :guilabel:`Add a line` to add any items that are missing. Be sure to remove any items that should not be included in the report by clicking :icon:`fa-times` :guilabel:`(delete)` on the row." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:356 -msgid "Finally, once all necessary items are included in the 1099 report, click on the :guilabel:`Generate` button. Doing so, downloads a CSV file that groups transactions by the partner that received the payments." +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:353 +msgid "Finally, once all necessary items are included in the 1099 report, click on the :guilabel:`Generate` button. Doing so downloads a CSV file that groups transactions by the partner that received the payments." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:365 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:362 msgid "Navigate to the *Cash Flow Statement* (CFS) dashboard by going to :menuselection:`Accounting app --> Reporting --> Statement Reports: Cash Flow Statement`. From here, |CFS| reports can be generated using the various :ref:`filters ` that are available at the top of the dashboard." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:370 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:367 msgid "Odoo uses the *direct* cash flow method to compile cash flow statements, which measures actual cash inflows and outflows from the company's operations, such as when cash is received from customers or when cash payments are made to suppliers." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:374 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:371 msgid "By default, an account labeled with any of the three default :guilabel:`Tags` on the :guilabel:`Chart of Accounts` dashboard will be included in the report, which includes: :guilabel:`Operating Activities`, :guilabel:`Financing Activities`, and :guilabel:`Investing & Extraordinary Activities`." msgstr "" @@ -29680,19 +30264,19 @@ msgstr "" msgid "Examples of tagged accounts that are included in the Cash Flow Statement in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:383 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:380 msgid "Additionally, the cash flow statement in Odoo:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:385 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:382 msgid "is limited to the *Bank* and *Cash* journals to reflect money coming in or out; and" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:386 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:383 msgid "also contains *Expenses* accounts, to show the counterpart transactions versus *Bank* or *Cash* journal entries, while excluding |AR| and |AP| activity." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:390 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:387 msgid "Create a vendor bill for $100, as an operating expense (not |AP|). Doing so will **not** reflect a transaction on the cash flow statement. However, register a corresponding payment for $100, and the transaction **will** reflect on the cash flow statement as :guilabel:`Cash paid for operating activities`." msgstr "" @@ -29700,308 +30284,308 @@ msgstr "" msgid "Example of a bill registered as an operating expense as part of a cash flow statement." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:404 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:401 msgid "Cash discounts can be configured from :menuselection:`Accounting app --> Payment Terms`. Each payment term can be set up with a cash discount and reduced tax." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:413 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:410 msgid "Writing checks" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:415 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:412 msgid "Using checks is still a common payment practice in the US. Be sure the *US Checks Layout* (`l10n_us_check_printing`) module for the US localization is :ref:`installed `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:418 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:415 msgid "To enable check printing from Odoo, navigate to :menuselection:`Accounting --> Configuration --> Settings` and find the :guilabel:`Vendor Payments` section. From here, tick the :guilabel:`Checks` checkbox to reveal several fields for check configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:422 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:419 msgid "Select a :guilabel:`Check Layout` from the drop-down menu:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:424 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:421 msgid ":guilabel:`Print Check (Top) - US`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:425 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:422 msgid ":guilabel:`Print Check (Middle) - US`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:426 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:423 msgid ":guilabel:`Print Check (Bottom) - US`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:428 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:425 msgid "Next, choose whether or not to enable the :guilabel:`Multi-Pages Check Stub` checkbox." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:430 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:427 msgid "Optionally set a :guilabel:`Check Top Margin` and :guilabel:`Check Left Margin`, if required." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:432 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:429 msgid "Once all check configurations are complete, :guilabel:`Save` the settings." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:435 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:432 msgid "Some of the check formats may require pre-printed paper from a third party vendor, https://checkdepot.net/collections/odoo-checks is recommended." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:439 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:436 msgid ":doc:`../accounting/payments/pay_checks`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:446 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:443 msgid "The *Payroll* application is responsible for calculating an employee's pay, taking into account all work, vacation, and sick time, benefits, and deductions. The *Payroll* app pulls information from the *Attendances*, *Timesheets*, *Time Off*, *Employees* and *Expenses* applications, to calculate the worked hours and compensation for each employee." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:451 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:448 msgid "When using an external payroll provider, such as *ADP*, it is necessary to export the various payroll-related data, such as work entries, repayment of expenses, taxes, commissions, and any other relevant data, so the data can be uploaded into the payroll provider, who then issues the actual paychecks or directly deposits the funds into an employee's bank account." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:456 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:453 msgid "In order to export the payroll data, the work entries must first be validated and correct. Refer to the :doc:`work entries <../../hr/payroll/work_entries>` documentation for more information regarding validating work entries." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:460 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:457 msgid "Once work entries are validated, the information can be :ref:`exported to ADP `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:462 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:459 msgid "After payments have been issued to employees, payslips can be processed into batches, validated, and posted to the corresponding accounting journals to keep all financial records in Odoo current." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:468 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:465 msgid "It is important to have the *Employees* application installed, and all employee information populated. Several fields in both the :ref:`employee records `, as well as in an :ref:`employee contracts `, are necessary to properly process the employee's pay. Ensure the following fields are filled out in their respective places." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:477 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:474 msgid "Employee records" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:479 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:476 msgid "In each employee record, there is various information the *Payroll* application requires to properly process payslips, including various banking, tax, and work information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:482 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:479 msgid "Navigate to the :menuselection:`Employees app` and select an employee record to view the sections of the employee form that directly affect *Payroll*:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:485 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:482 msgid ":guilabel:`Work Information` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:487 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:484 msgid ":guilabel:`Work Address`: indicates where the employee is located, including the state, which affects the tax calculations." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:489 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:486 msgid ":guilabel:`Working Hours`: determines how pay is calculated, and determines if an employee earns overtime." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:492 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:489 msgid ":guilabel:`Private Information` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:494 -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:528 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:491 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:525 msgid ":guilabel:`SSN No`: the last four digits of the employee's Social Security Number (SSN) appears on payslips." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:496 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:493 msgid ":guilabel:`Bank Account Number`: the bank account associated with the NACHA payment file." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:498 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:495 msgid ":guilabel:`HR Settings` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:500 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:497 msgid ":guilabel:`Federal Tax Filing Status`: the tax status an employee uses for Payroll tax calculations, which can be different from their state status." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:502 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:499 msgid ":guilabel:`State Tax Filing Status`: the tax status an employee uses for their state portion of the Payroll tax calculation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:504 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:501 msgid ":guilabel:`W-2 Form`: a US tax form indicating the summary of wages, taxes, and benefits paid to an employee during a tax period (typically one year)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:506 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:503 msgid ":guilabel:`W-4 Form`: an IRS form that helps outline the amount of federal taxes to withhold for an employee, which is paid to the IRS by the company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:512 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:509 msgid "Employee contracts" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:514 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:511 msgid "Additionally, there is information that is found in an employee contract that also affects the *Payroll* application." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:517 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:514 msgid "Navigate to the :menuselection:`Employees app --> Employees --> Contracts` and select a contract record to view the sections of a contract that directly affect *Payroll*:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:520 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:517 msgid ":guilabel:`General Information`:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:522 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:519 msgid ":guilabel:`Salary Structure Type: United States: Employee`: defines when the employee is paid, their working schedule, and the work entry type." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:524 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:521 msgid ":guilabel:`Work Entry source`: determines how work entries are calculated." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:526 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:523 msgid ":guilabel:`Salary Information` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:530 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:527 msgid ":guilabel:`Wage type`: determines how the employee is paid, wether a Fixed wage (salary) or Hourly wage." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:532 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:529 msgid ":guilabel:`Schedule Pay`: defines how often the employee is paid, either :guilabel:`Annually`, :guilabel:`Semi-annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, :guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, :guilabel:`Weekly`, or :guilabel:`Daily`. In the US, Semi-monthly (24 payments a year) or bi-weekly (26 payments a year) are the most common." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:536 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:533 msgid ":guilabel:`Wage, Yearly, and Monthly cost`: used to show the total cost of an employee. It is recommended to populate the :guilabel:`Yearly` wage first, as it auto-populates the other fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:539 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:536 msgid ":guilabel:`Pre-tax benefits`: populate this section according to the employee's selections. Pre-tax benefits decrease the gross wage, which lowers the base amount that is taxed. These are displayed at the beginning of the payslip." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:542 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:539 msgid ":guilabel:`Post-tax benefits`: these benefits are deductions made *after* taxes are calculated. These appear towards the end of the payslip before the net amount is displayed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:546 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:543 msgid ":doc:`Employees documentation <../../hr/employees/new_employee>`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:551 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:548 msgid "Export work entries to ADP" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:556 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:553 msgid "In order to create a report that can be uploaded to ADP, there are some initial configuration steps that must be completed first." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:559 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:556 msgid "First, ensure the *United States - Payroll - Export to ADP* (`l10n_us_hr_payroll_adp`) module is :ref:`installed `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:562 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:559 msgid "Then, the company **must** have an *ADP Code* entered in the company settings. To do so, navigate to :menuselection:`Payroll app --> Configuration --> Settings`. Enter the :guilabel:`ADP Code` in the :guilabel:`US Localization` section." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:566 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:563 msgid "Next, work entry types **must** have the correct ADP code listed in the *External Code* field for each work entry type that is being referenced." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:569 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:566 msgid "Lastly, every employee **must** have an *ADP Code* entered on their employee form. To do so, navigate to :menuselection:`Employees app`, select an employee record, and open the :guilabel:`HR Settings` tab. Enter the :guilabel:`ADP Code` in the :guilabel:`ADP Information` section." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:573 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:570 msgid "The :guilabel:`ADP Code` code is how ADP identifies that particular employee, and is typically a six-digit number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:577 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:574 msgid ":ref:`payroll/new-work-entry`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:578 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:575 msgid ":doc:`../../hr/employees/new_employee`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:581 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:578 msgid "Export data" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:583 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:580 msgid "Once :doc:`work entries <../../hr/payroll/work_entries>` have been verified, the information can be exported to a CSV file, which can then be uploaded into ADP." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:586 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:583 msgid "To export the data, navigate to :menuselection:`Payroll app --> Reporting --> United States: ADP Export`, then click :guilabel:`New`. Next, enter the :guilabel:`Start Date` and :guilabel:`End Date` for the work entries using the calendar pop-over." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:590 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:587 msgid "Then, enter a :guilabel:`Batch ID` in the corresponding field. The recommendation for this field is to enter the date in a `YY-MM-DD` format, followed by any other characters to distinguish that specific batch, such as a department name, or any other defining characteristics for the batch." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:594 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:591 msgid "Enter a :guilabel:`Batch Description` in the corresponding field. This should be short and descriptive, but distinct from the :guilabel:`Batch Name`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:597 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:594 msgid "Ensure the correct company populates the :guilabel:`Company` field. Change the selected company with the drop-down menu, if needed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:600 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:597 msgid "Lastly, add the employee's work entry information to the list. Click :guilabel:`Add a line` and an :guilabel:`Add: Employee` pop-up window loads. The list can be :doc:`filtered <../../essentials/search>` to more easily find the employees to add to the list." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:605 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:602 msgid "Process the data export in multiple groups instead of in one large group that contains all employees. This helps to meaningfully differentiate the batches and makes processing more tenable, overall. The most common ways to group employees is by department, or by wage type (hourly or salaried)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:610 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:607 msgid "Select the employees to add to the list by ticking the box to the left of their name. Once all desired employees have been selected, click the :guilabel:`Select` button in the lower-left corner, and the employees appear in the list." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:614 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:611 msgid "To create the CSV file, click the :guilabel:`Generate` button in the top-left corner." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:619 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:616 msgid "ACH - electronic transfers" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:621 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:618 msgid "Automated Clearing House (ACH) payments are a modern way to transfer funds electronically between bank accounts, replacing traditional paper-based methods. |ACH| payments are commonly used for direct deposits, bill payments, and business transactions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:626 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:623 msgid "Receive ACH payments: payment provider integration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:628 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:625 msgid "|ACH| payments are supported by *Authorize.net* and *Stripe* payment integrations in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:631 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:628 msgid ":ref:`Setting up Authorize.net for ACH payments (Odoo) `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:632 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:629 msgid "`Authorize.net's ACH payment processing for small businesses documentation `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:634 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:631 msgid ":doc:`Setting up Stripe for ACH payments (Odoo) <../payment_providers/stripe>`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:635 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:632 msgid "`Stripe's ACH Direct Debit documentation `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:640 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:637 msgid "Send payments: NACHA files" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:642 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:639 msgid "Odoo can generate a National Automated Clearing House Association (NACHA) compatible |ACH| file to send to a company's bank. For each individual *Bank* journal that the company wishes to pay vendors with, a |NACHA| configuration section needs to be filled out on the Odoo database." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:649 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:646 msgid "First, navigate to the :menuselection:`Accounting app --> Configuration --> Journals`. Open the bank journal and click into the :guilabel:`Outgoing Payments` tab." msgstr "" @@ -30009,31 +30593,31 @@ msgstr "" msgid "NACHA (National Automated Clearing House Association) configuration settings on Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:657 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:654 msgid "The following |NACHA| configuration information is normally provided by the company's financial institution once they have been approved to send payments via their account." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:660 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:657 msgid "Under the section labeled, :guilabel:`NACHA configuration` are the fields required to generate a |NACHA| compatible |ACH| file to send to a company's bank. First, enter the routing number of the financial institution in the field labeled, :guilabel:`Immediate Destination`. This information is widely available on the Internet and generally varies by bank location. This number is usually provided during the initial account setup." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:666 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:663 msgid "Next, enter the registered name of the financial institution in the field called, :guilabel:`Destination`. This information will be provided by the bank or credit union." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:669 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:666 msgid "Following the :guilabel:`Destination` field is the :guilabel:`Immediate Origin` field. Enter the 9-digit company ID or Employer Identification Number (EIN) into this field. This information is provided by the financial institution." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:673 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:670 msgid "Next, enter the :guilabel:`Company Identification` number, which is a 10-digit number made from combining the 9-digit company ID or Employer Identification Number (EIN), along with an additional number at the start of the sequence. This number is often a `1`. Check with the financial institution should this first number differ to verify that it is correct, as this number is provided for |ACH| approved accounts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:679 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:676 msgid "Enter the :guilabel:`Originating DFI Identification` number next, which should contain an assigned 8-digit number from the financial institution." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:683 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:680 msgid "Enter the numerical values in this section *exactly* as the company's financial institution (e.g. bank or credit union) has provided them, otherwise risk failing a successful |NACHA| configuration in Odoo." msgstr "" @@ -30041,39 +30625,39 @@ msgstr "" msgid "NACHA settings with the standard entry class code drop-down menu highlighted." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:691 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:688 msgid "There are two options for the next field: :guilabel:`Standard Entry Class Code`. Select the drop-down menu to the right of the field and pick either :guilabel:`Corporate Credit or Debit (CCD)` or :guilabel:`Prearranged Payment and Deposit (PPD)`. Again, this information will be provided by the financial institution. By default :guilabel:`Corporate Credit or Debit (CCD)` is selected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:696 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:693 msgid "Finally, the last option is for :guilabel:`Generated Balanced Files`. Tick the checkbox to the right of the field to enable :guilabel:`Generated Balanced Files`. Consult the company's accountant or financial advisor to make an informed decision for this field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:700 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:697 msgid "Manually save the configuration by clicking the :icon:`fa-cloud-upload` :guilabel:`(cloud upload)` icon, or navigate away from this screen to auto-save. The configuration is now complete." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:706 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:703 msgid "Create batch payment" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:708 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:705 msgid "Now, record each payment in Odoo using the |NACHA| payment method." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:711 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:708 msgid ":ref:`Register Payments in Odoo `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:714 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:711 msgid "Be aware of the cut-off time for same-day payments. Either the file needs to have a future date associated with each payment or the file needs to be sent prior to the cut-off, if the dates included in it match today's date. Consult the financial institution for the exact cut-off time for their processing of same-day payments." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:719 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:716 msgid "Once all the payments to be included in the |NACHA| |ACH| file have been made, a batch payment needs to be made from the :icon:`fa-cog` :guilabel:`Action` menu." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:722 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:719 msgid "To create the batch payments, access the payments page, by navigating to :menuselection:`Accounting --> Vendors --> Payments`. Select all the payments that should be included in the |NACHA| |ACH| file, by ticking the checkboxes to the far-left of the rows." msgstr "" @@ -30082,11 +30666,11 @@ msgid "On the payments screen, the action menu is highlighted with create a batc "selected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:732 -msgid "All payments in the batch must share the same payment method." +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:729 +msgid "All payments in the batch **must** share the same |NACHA| payment method." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:734 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:731 msgid "Next, navigate to the batched payment (:menuselection:`Accounting --> Vendors --> Batch Payments`). Click into the payment just created and then click into the :guilabel:`Exported File` tab. The generated file is listed with the :guilabel:`Generation Date`. Click the :icon:`fa-download` :guilabel:`(download)` button to download the file." msgstr "" @@ -30094,15 +30678,15 @@ msgstr "" msgid "The exported file tab highlighted in the batch payment with the download circled." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:743 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:740 msgid "If any adjustments need to be made, click the :guilabel:`Re-generate Export File` button to recreate a new |NACHA| |ACH| file." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:747 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:744 msgid ":doc:`../accounting/payments/batch`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_states.rst:748 +#: ../../content/applications/finance/fiscal_localizations/united_states.rst:745 msgid ":doc:`Europe's direct debiting <../accounting/payments/batch_sdd>`" msgstr "" @@ -30128,14 +30712,14 @@ msgid "Go to :menuselection:`Contacts --> Configuration --> Bank Accounts` and s msgstr "" #: ../../content/applications/finance/fiscal_localizations/vietnam.rst:26 -msgid "The account holder's country must be set to Vietnam on its contact form." +msgid "The account holder's country must be set to `Vietnam` on its contact form." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:46 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:47 msgid "Issue invoices with Vietnamese QR banking QR codes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:54 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:55 msgid "Ensure that the :guilabel:`Recipient Bank` is the one you configured, as Odoo uses this field to generate the Vietnamese QR banking QR code." msgstr "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index cfd329ae6..35e598ee0 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 13:30+0000\n" +"POT-Creation-Date: 2024-08-21 11:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -177,8 +177,7 @@ msgid "Overview of a new company's form in Odoo." msgstr "" #: ../../content/applications/general/companies.rst:67 -#: ../../content/applications/general/companies.rst:120 -msgid "Activate the :ref:`developer mode ` to set social media accounts and company-specific email system parameters. See this documentation on :doc:`../marketing/social_marketing` and :ref:`email_servers/outbound`." +msgid "Activate the :ref:`developer mode ` to set social media accounts and company-specific email parameters. See this documentation on :doc:`../marketing/social_marketing` and :doc:`email_communication`." msgstr "" #: ../../content/applications/general/companies.rst:71 @@ -237,35 +236,39 @@ msgstr "" msgid "Add a branch to a company with branches and add a line highlighted." msgstr "" +#: ../../content/applications/general/companies.rst:120 +msgid "Activate the :ref:`developer mode ` to set social media accounts and company-specific email system parameters. See this documentation on :doc:`../marketing/social_marketing` and :doc:`email_communication`." +msgstr "" + #: ../../content/applications/general/companies.rst:124 msgid "Branches also have a :guilabel:`Parent Company` set on the branch form in :ref:`developer mode `. Accounting and fiscal localizations for the branch are set on the :guilabel:`Parent Company`. To do so, select the company from the *company selector* in the top menu, and go to :menuselection:`Settings app --> Accounting --> Fiscal Localization`." msgstr "" #: ../../content/applications/general/companies.rst:130 -msgid "Adding a branch to a company triggers an upsell, should the database be in the *Standard* or *One App Free* pricing plans. Adding one or more branches constitutes a multi-company database, and needs to be moved to the *Custom* pricing plan." +msgid "If the database is on the standard *Paid* pricing plan, adding a branch to a company triggers an upsell. Since adding one or more branches turns the database into a multi-company setup, it will need to switch to the *Custom* pricing plan. This does not affect databases on the *One-app free* plan." msgstr "" -#: ../../content/applications/general/companies.rst:134 +#: ../../content/applications/general/companies.rst:135 msgid "For more information on pricing, see `Odoo's pricing `_ page." msgstr "" -#: ../../content/applications/general/companies.rst:139 +#: ../../content/applications/general/companies.rst:140 msgid "Employee access" msgstr "" -#: ../../content/applications/general/companies.rst:141 +#: ../../content/applications/general/companies.rst:142 msgid "Once companies are created, manage the employees' :doc:`Access Rights ` for *Multi Companies*." msgstr "" -#: ../../content/applications/general/companies.rst:144 +#: ../../content/applications/general/companies.rst:145 msgid "To access the *Access Rights*, navigate to :menuselection:`Settings app --> Users section --> Manage Users`." msgstr "" -#: ../../content/applications/general/companies.rst:147 +#: ../../content/applications/general/companies.rst:148 msgid "From the :guilabel:`Users` page, select a user from the list to modify. Then, either change the fields for :guilabel:`Allowed Companies` or :guilabel:`Default Company`." msgstr "" -#: ../../content/applications/general/companies.rst:150 +#: ../../content/applications/general/companies.rst:151 msgid "Multiple companies can be set for :guilabel:`Allowed Companies`, and *only one* can be set as the :guilabel:`Default Company`." msgstr "" @@ -274,40 +277,40 @@ msgid "View of an user form emphasizing the multi companies field under the acce "in Odoo." msgstr "" -#: ../../content/applications/general/companies.rst:158 +#: ../../content/applications/general/companies.rst:159 msgid "If an administrator has multiple companies activated on the database, and is editing a record, the editing occurs on the record's related company." msgstr "" -#: ../../content/applications/general/companies.rst:162 +#: ../../content/applications/general/companies.rst:163 msgid "If editing a sale order issued under `JS Store US`, while working on the `JS Store Belgium` environment, the changes are applied under `JS Store US` (the company from which the sale order was issued)." msgstr "" -#: ../../content/applications/general/companies.rst:166 +#: ../../content/applications/general/companies.rst:167 msgid "When creating a record, the company taken into account is:" msgstr "" -#: ../../content/applications/general/companies.rst:168 +#: ../../content/applications/general/companies.rst:169 msgid "The current company selected in the company selector, in the upper-right hand of the screen (the one that is highlighted/active)" msgstr "" -#: ../../content/applications/general/companies.rst:171 -#: ../../content/applications/general/companies.rst:175 +#: ../../content/applications/general/companies.rst:172 +#: ../../content/applications/general/companies.rst:176 msgid "**OR**" msgstr "" -#: ../../content/applications/general/companies.rst:173 +#: ../../content/applications/general/companies.rst:174 msgid "No company is set (because none is set on the product and contact forms, for example)" msgstr "" -#: ../../content/applications/general/companies.rst:177 +#: ../../content/applications/general/companies.rst:178 msgid "The company set is the company linked to the document (the same as if a record is being edited)" msgstr "" -#: ../../content/applications/general/companies.rst:180 +#: ../../content/applications/general/companies.rst:181 msgid "Document format" msgstr "" -#: ../../content/applications/general/companies.rst:182 +#: ../../content/applications/general/companies.rst:183 msgid "To set document formats according to each company, *activate* and *select* the respective company, and, under the :menuselection:`Settings app --> Companies section`, click on :guilabel:`Configure Document Layout` and edit the information as needed." msgstr "" @@ -315,72 +318,72 @@ msgstr "" msgid "View of the settings page emphasizing the document layout field in Odoo." msgstr "" -#: ../../content/applications/general/companies.rst:190 +#: ../../content/applications/general/companies.rst:191 msgid ":guilabel:`Company Details` can be edited on the document layout. By default, this field is populated from the company information listed, when navigating here: :menuselection:`Settings app --> Companies section --> Manage Companies`, and select a company from the list." msgstr "" -#: ../../content/applications/general/companies.rst:197 -#: ../../content/applications/general/multi_company.rst:77 +#: ../../content/applications/general/companies.rst:198 +#: ../../content/applications/general/multi_company.rst:79 msgid "Inter-company transactions" msgstr "" -#: ../../content/applications/general/companies.rst:199 +#: ../../content/applications/general/companies.rst:200 msgid "First, activate the :ref:`developer mode `. Then, make sure each one of the companies is properly set in relation to:" msgstr "" -#: ../../content/applications/general/companies.rst:202 +#: ../../content/applications/general/companies.rst:203 msgid ":doc:`Chart of Accounts <../finance/accounting/get_started/chart_of_accounts>`" msgstr "" -#: ../../content/applications/general/companies.rst:203 +#: ../../content/applications/general/companies.rst:204 msgid ":doc:`Taxes <../finance/accounting/taxes>`" msgstr "" -#: ../../content/applications/general/companies.rst:204 +#: ../../content/applications/general/companies.rst:205 msgid ":doc:`Fiscal Positions <../finance/accounting/taxes/fiscal_positions>`" msgstr "" -#: ../../content/applications/general/companies.rst:205 +#: ../../content/applications/general/companies.rst:206 msgid ":doc:`Journals <../finance/accounting/bank>`" msgstr "" -#: ../../content/applications/general/companies.rst:206 +#: ../../content/applications/general/companies.rst:207 msgid ":doc:`Fiscal Localizations <../finance/fiscal_localizations>`" msgstr "" -#: ../../content/applications/general/companies.rst:207 +#: ../../content/applications/general/companies.rst:208 msgid ":doc:`Pricelists <../sales/sales/products_prices/prices/pricing>`" msgstr "" -#: ../../content/applications/general/companies.rst:209 +#: ../../content/applications/general/companies.rst:210 msgid "Next, navigate to :menuselection:`Settings app --> Companies section --> Manage Companies`. Then, select the desired company from the list. On the company form, select the :guilabel:`Inter-Company Transactions` tab, on the individual company's detail form." msgstr "" -#: ../../content/applications/general/companies.rst:213 +#: ../../content/applications/general/companies.rst:214 msgid "With the respective company activated and selected, choose one of the following :guilabel:`Rule` options:" msgstr "" -#: ../../content/applications/general/companies.rst:216 +#: ../../content/applications/general/companies.rst:217 msgid ":guilabel:`Do not synchronize`: do not synchronize any inter-company transactions." msgstr "" -#: ../../content/applications/general/companies.rst:217 +#: ../../content/applications/general/companies.rst:218 msgid ":guilabel:`Synchronized invoice/bills`: generates a bill/invoice when a company confirms a bill/invoice for the selected company." msgstr "" -#: ../../content/applications/general/companies.rst:219 +#: ../../content/applications/general/companies.rst:220 msgid ":guilabel:`Synchronize Sales Order`: generates a drafted sales order using the selected company warehouse, when a sales order is confirmed for the selected company. If, instead of a drafted sales order, it should be validated, enable :guilabel:`Automatic Validation`.\\*" msgstr "" -#: ../../content/applications/general/companies.rst:222 +#: ../../content/applications/general/companies.rst:223 msgid ":guilabel:`Synchronize Purchase Order`: generates a drafted purchase order using the selected company warehouse, when a purchase order is confirmed for the selected company. If, instead of a drafted purchase order, it should be validated, enable :guilabel:`Automatic Validation`.\\*" msgstr "" -#: ../../content/applications/general/companies.rst:225 +#: ../../content/applications/general/companies.rst:226 msgid ":guilabel:`Synchronize Sales and Purchase Order`: generates a drafted purchase/sales order using the selected company warehouse, when a sales/purchase order is confirmed for the selected company. If, instead of a drafted purchase/sales order, it should be validated, enable :guilabel:`Automatic Validation`.\\*" msgstr "" -#: ../../content/applications/general/companies.rst:230 +#: ../../content/applications/general/companies.rst:231 msgid "\\* The given option needs to be selected, so :guilabel:`Automatic Validation` appears in the configuration." msgstr "" @@ -388,27 +391,27 @@ msgstr "" msgid "View of the settings page emphasizing the inter company transaction field in Odoo." msgstr "" -#: ../../content/applications/general/companies.rst:238 -msgid "Products **must** be configured as :guilabel:`Can be sold` and shared between the companies. See :doc:`../inventory_and_mrp/inventory/product_management/product_tracking/type`." +#: ../../content/applications/general/companies.rst:239 +msgid "Products **must** be configured as :guilabel:`Can be sold` and shared between the companies. See :doc:`../inventory_and_mrp/inventory/product_management/configure/type`." msgstr "" -#: ../../content/applications/general/companies.rst:242 +#: ../../content/applications/general/companies.rst:243 msgid ":guilabel:`Synchronize invoice/bills`: an invoice posted on `JS Store Belgium`, for `JS Store US`, automatically creates a vendor bill, and generates a drafted purchase/sales order using the selected company warehouse, when a sales/purchase order is confirmed for the selected company. If, instead of a drafted purchase/sales order, it should be validated, enable :guilabel:`Automatic Validation`." msgstr "" -#: ../../content/applications/general/companies.rst:248 +#: ../../content/applications/general/companies.rst:249 msgid ":guilabel:`Synchronize sales/purchase order`: when a sale order for `JS Store US` is confirmed on `JS Store Belgium`, a purchase order on `JS Store Belgium` is automatically created (and confirmed, if the :guilabel:`Automatic Validation` feature was enabled)." msgstr "" -#: ../../content/applications/general/companies.rst:253 +#: ../../content/applications/general/companies.rst:254 msgid "Remember to test all workflows as a user *other* than the administrator." msgstr "" -#: ../../content/applications/general/companies.rst:256 +#: ../../content/applications/general/companies.rst:257 msgid ":doc:`Multi-company Guidelines <../../developer/howtos/company>`" msgstr "" -#: ../../content/applications/general/companies.rst:257 +#: ../../content/applications/general/companies.rst:258 msgid ":doc:`../finance/accounting/get_started/multi_currency`" msgstr "" @@ -1314,7 +1317,139 @@ msgid "Accessing the technical menu" msgstr "" #: ../../content/applications/general/email_communication.rst:5 -msgid "Email communication" +msgid "Communication in Odoo by email" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:7 +msgid "Communication in Odoo related to records such as CRM opportunities, sales orders, invoices, ... have a discussion thread called **chatter**, often displayed on the right side of the record." +msgstr "" + +#: ../../content/applications/general/email_communication.rst:10 +msgid "On the chatter, you can send direct emails or Odoo notifications to the followers of a document (depending on their notification preferences), log internal notes, send WhatsApp messages or SMSes, and schedule activities." +msgstr "" + +#: ../../content/applications/general/email_communication.rst:14 +msgid "If a follower replies to a message, the reply updates the chatter, and Odoo relays it to the followers as a notification. All emails - outgoing and incoming - appear in the same chatter." +msgstr "" + +#: ../../content/applications/general/email_communication.rst:20 +msgid "Odoo Online and Odoo.sh users" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:22 +msgid "On Odoo Online and Odoo.sh, outgoing and incoming emails work out of the box, **nothing needs to be done**. Everything is already configured on your subdomain." +msgstr "" + +#: ../../content/applications/general/email_communication.rst:25 +msgid "By default, outgoing emails use the following :ref:`notification email address ` `notifications@company-name.odoo.com`." +msgstr "" + +#: ../../content/applications/general/email_communication.rst:31 +msgid "Using another domain" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:33 +msgid "If you prefer not to have outgoing emails sent from Odoo's subdomain `@company-name.odoo.com` but instead :ref:`from your own domain `, **additional configuration will be necessary** on the domain and within Odoo. This introduces an extra layer of complexity and necessitates technical knowledge (mainly regarding DNS and mail protocols)." +msgstr "" + +#: ../../content/applications/general/email_communication.rst:38 +msgid "By adding a domain and configuring the administration access rights, you can also access the :ref:`new domain alias ` page to configure the alias of your companies. If only one domain is configured, this domain will be shared by all companies on the database." +msgstr "" + +#: ../../content/applications/general/email_communication.rst:42 +msgid "If you want to keep using Odoo's mail server, you will have to :ref:`configure the SPF and DKIM `." +msgstr "" + +#: ../../content/applications/general/email_communication.rst:45 +msgid "If :ref:`you want to use your own mail server `, you will have to follow the mail server provider's specific documentation." +msgstr "" + +#: ../../content/applications/general/email_communication.rst:48 +msgid "For incoming emails, after adding your own domain, :ref:`replies from customers will come back to your domain `, and you will need to use one of the three possible ways to get the emails back into Odoo (using either :ref:`incoming mail server `, :ref:`redirection/forwarding ` or :ref:`DNS MX record `). Everything is covered in the :doc:`Manage inbound messages documentation `." +msgstr "" + +#: ../../content/applications/general/email_communication.rst:59 +msgid "On-premise users" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:61 +msgid "If you are on-premise, you will have to completely configure your outgoing and incoming emails:" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:63 +msgid "For outgoing emails, you will need :ref:`to use an SMTP server and a custom domain `." +msgstr "" + +#: ../../content/applications/general/email_communication.rst:65 +msgid "For incoming emails, set the frequency at which you fetch new emails low enough for responsiveness but high enough in order not to stress your system or provider. Due to this reason and the simplicity of this configuration, we usually advise on using incoming mail servers. To use an SMTP server, check out the :ref:`\"Use a custom domain for inbound messages\" documentation `." +msgstr "" + +#: ../../content/applications/general/email_communication.rst:74 +msgid "Using a third-party provider's mail server" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:76 +msgid "Odoo's documentation also covers several popular mail servers. As they require specific authorizations and configuration, they add a layer of complexity. For this reason, using Odoo's outgoing mail server is recommended." +msgstr "" + +#: ../../content/applications/general/email_communication.rst:80 +msgid ":doc:`Outlook documentation `" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:81 +msgid ":doc:`Gmail documentation `" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:82 +msgid ":doc:`Mailjet documentation `" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:85 +msgid "Every provider has its own limitations. Research the desired provider *before* configuring it. For example, Outlook and Gmail might not be suitable for large marketing campaigns." +msgstr "" + +#: ../../content/applications/general/email_communication.rst:89 +msgid ":doc:`Activities <../essentials/activities>`" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:90 +msgid ":doc:`Discuss app <../productivity/discuss>`" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:91 +msgid ":doc:`Digest emails `" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:92 +msgid ":doc:`Email Marketing app <../marketing/email_marketing>`" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:93 +msgid ":doc:`Email templates `" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:94 +msgid ":ref:`Expense creation using an email alias `" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:95 +msgid ":ref:`Helpdesk ticket creation using an email alias `" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:96 +msgid ":ref:`Lead creation using an email alias `" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:97 +msgid ":ref:`Project task creation using an email alias `" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:98 +msgid ":doc:`Technical mail getaway for on-premise users <../../administration/on_premise/email_gateway>`" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:100 +msgid ":ref:`Technical start of Odoo database with an outgoing mail server configured from the command-line interface `" msgstr "" #: ../../content/applications/general/email_communication/azure_oauth.rst:3 @@ -1355,15 +1490,15 @@ msgid "Now, click on :guilabel:`Add (+)`, located in the top menu, and then sele msgstr "" #: ../../content/applications/general/email_communication/azure_oauth.rst:36 -msgid "Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the platform, and then input `https:///microsoft_outlook/confirm` in the :guilabel:`URL` field. The Odoo base URL is the canonical domain at which your Odoo instance can be reached in the URL field." +msgid "Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the platform, and then input `https:///microsoft_outlook/confirm` in the :guilabel:`URL` field. The `web.base.url` is subject to change depending on the URL used to log in to the database." msgstr "" #: ../../content/applications/general/email_communication/azure_oauth.rst:41 -msgid "*mydatabase.odoo.com*, where *mydatabase* is the actual prefix of the database's subdomain, assuming it's hosted on Odoo.com" +msgid "The documentation about the :ref:`web.base.url ` explains how to freeze a unique URL. It is also possible to add different redirect URLs on the Microsoft app." msgstr "" #: ../../content/applications/general/email_communication/azure_oauth.rst:44 -msgid "After the URL has been added to the field, :guilabel:`Register` the application so it is created." +msgid "After the URL has been added to the field, :guilabel:`Register` the application, so it is created." msgstr "" #: ../../content/applications/general/email_communication/azure_oauth.rst:47 @@ -1511,7 +1646,7 @@ msgid "Then, create a new email server and check the box for :guilabel:`Outlook` msgstr "" #: ../../content/applications/general/email_communication/azure_oauth.rst:167 -msgid "If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain or email address `." +msgid "If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain or email address `." msgstr "" #: ../../content/applications/general/email_communication/azure_oauth.rst:170 @@ -1551,16 +1686,16 @@ msgid "A generic email address would be used to send emails for all users within msgstr "" #: ../../content/applications/general/email_communication/azure_oauth.rst:206 -#: ../../content/applications/general/email_communication/azure_oauth.rst:247 -msgid "For more information on the from filter visit: :ref:`email_communication/default`." +#: ../../content/applications/general/email_communication/azure_oauth.rst:248 +msgid "Visit the :ref:`From Filtering documentation ` for more information." msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:209 -#: ../../content/applications/general/email_communication/azure_oauth.rst:254 +#: ../../content/applications/general/email_communication/azure_oauth.rst:210 +#: ../../content/applications/general/email_communication/azure_oauth.rst:256 msgid "The :guilabel:`System Parameters` can be accessed by activating :ref:`developer-mode` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu." msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:212 +#: ../../content/applications/general/email_communication/azure_oauth.rst:213 msgid "When using this configuration, every email that is sent from the database will use the address of the configured `notification` mailbox. However it should be noted that the name of the sender will appear but their email address will change:" msgstr "" @@ -1568,1037 +1703,1427 @@ msgstr "" msgid "Name from real sender with static email." msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:221 +#: ../../content/applications/general/email_communication/azure_oauth.rst:222 msgid "Single outgoing mail server configuration:" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:223 +#: ../../content/applications/general/email_communication/azure_oauth.rst:224 msgid "Outgoing mail server **username** (login) = `notifications@example.com`" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:224 +#: ../../content/applications/general/email_communication/azure_oauth.rst:225 msgid "Outgoing mail server :guilabel:`FROM Filtering` = `notifications@example.com`" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:225 -#: ../../content/applications/general/email_communication/azure_oauth.rst:279 +#: ../../content/applications/general/email_communication/azure_oauth.rst:226 +#: ../../content/applications/general/email_communication/azure_oauth.rst:281 msgid "`mail.catchall.domain` in system parameters = `example.com`" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:226 -#: ../../content/applications/general/email_communication/azure_oauth.rst:280 +#: ../../content/applications/general/email_communication/azure_oauth.rst:227 +#: ../../content/applications/general/email_communication/azure_oauth.rst:282 msgid "`mail.default.from` in system parameters = `notifications`" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:229 +#: ../../content/applications/general/email_communication/azure_oauth.rst:230 msgid "User-specific (multiple user) configuration" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:231 +#: ../../content/applications/general/email_communication/azure_oauth.rst:232 msgid "In addition to a generic email server, individual email servers can be set up for users in a database. These email addresses must be set as the :guilabel:`FROM Filtering` on each individual server for this configuration to work." msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:235 +#: ../../content/applications/general/email_communication/azure_oauth.rst:236 msgid "This configuration is the more difficult of the two Microsoft Azure configurations, in that it requires all users configured with email servers to have access rights to settings in order to establish a connection to the email server." msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:240 +#: ../../content/applications/general/email_communication/azure_oauth.rst:241 #: ../../content/applications/general/iot/config/pos.rst:21 #: ../../content/applications/general/iot/config/troubleshooting.rst:604 msgid "Setup" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:242 +#: ../../content/applications/general/email_communication/azure_oauth.rst:243 msgid "Each user should have a separate email server set up. The :guilabel:`FROM Filtering` should be set so that only the user's email is sent from that server. In other words, only a user with an email address that matches the set :guilabel:`FROM Filtering` is able to use this server." msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:249 +#: ../../content/applications/general/email_communication/azure_oauth.rst:251 msgid "A :ref:`fallback server ` must be setup to allow for the sending of :guilabel:`notifications`. The :guilabel:`FROM Filtering` for this server should have the value of the `{mail.default.from}@{mail.catchall.domain}`." msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:258 +#: ../../content/applications/general/email_communication/azure_oauth.rst:260 msgid "The configuration for this transactional email server can work alongside an outgoing mass-mailing email server. The :guilabel:`FROM Filtering` for the mass-mailing email server can remain empty, but it's require to be added in the settings of the *Email Marketing* application." msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:263 -msgid "For more information on setting the mass-mailing email server visit :ref:`email_communication/mass_mails`." +#: ../../content/applications/general/email_communication/azure_oauth.rst:265 +msgid "For more information on setting the mass-mailing email server visit :ref:`email-outbound-custom-domain-smtp-server`." msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:267 +#: ../../content/applications/general/email_communication/azure_oauth.rst:269 msgid "Multiple user outgoing mail server configuration:" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:270 +#: ../../content/applications/general/email_communication/azure_oauth.rst:272 msgid "User #1 mailbox" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:270 +#: ../../content/applications/general/email_communication/azure_oauth.rst:272 msgid "Outgoing mail server #1 **username** (login) = `john@example.com`" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:271 +#: ../../content/applications/general/email_communication/azure_oauth.rst:273 msgid "Outgoing mail server #1 :guilabel:`FROM Filtering` = `john@example.com`" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:273 +#: ../../content/applications/general/email_communication/azure_oauth.rst:275 msgid "User #2 mailbox" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:273 +#: ../../content/applications/general/email_communication/azure_oauth.rst:275 msgid "Outgoing mail server #2 **username** (login) = `jane@example.com`" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:274 +#: ../../content/applications/general/email_communication/azure_oauth.rst:276 msgid "Outgoing mail server #2 :guilabel:`FROM Filtering` = `jane@example.com`" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:276 +#: ../../content/applications/general/email_communication/azure_oauth.rst:278 msgid "Notifications mailbox" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:276 +#: ../../content/applications/general/email_communication/azure_oauth.rst:278 msgid "Outgoing mail server #3 **username** (login) = `notifications@example.com`" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:277 +#: ../../content/applications/general/email_communication/azure_oauth.rst:279 msgid "Outgoing mail server #3 :guilabel:`FROM Filtering` = `notifications@example.com`" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:279 +#: ../../content/applications/general/email_communication/azure_oauth.rst:281 msgid "System Parameters" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:283 +#: ../../content/applications/general/email_communication/azure_oauth.rst:285 msgid "Configure incoming email server" msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:285 +#: ../../content/applications/general/email_communication/azure_oauth.rst:287 msgid "The incoming account should be configured in a similar way to the outgoing email account. Navigate to the :guilabel:`Incoming Mail Servers` in the :guilabel:`Technical Menu` and :guilabel:`Create` a new configuration. Check or Select the button next to :guilabel:`Outlook Oauth Authentication` and enter the :guilabel:`Microsoft Outlook username`. Click on :guilabel:`Connect your Outlook account`. Odoo will state: :guilabel:`Outlook Token Valid` Now :guilabel:`Test and Confirm` the account. The account should be ready to receive email to the Odoo database." msgstr "" -#: ../../content/applications/general/email_communication/azure_oauth.rst:293 -msgid ":doc:`email_servers`" -msgstr "" - #: ../../content/applications/general/email_communication/email_domain.rst:3 msgid "Configure DNS records to send emails in Odoo" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:6 -msgid "SPAM labels overview" +#: ../../content/applications/general/email_communication/email_domain.rst:5 +msgid "This documentation presents three complementary authentication protocols (SPF, DKIM, and DMARC) used to prove the legitimacy of an email sender. Not complying with these protocols will greatly reduce chances of your emails to reach their destination." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:8 -msgid "Sometimes, emails from Odoo are misclassified by the different email providers and end up in spam folders. At the moment, some settings are out of Odoo's control, notably the way the different email providers classify Odoo's emails according to their own restriction policy and/or limitations." +#: ../../content/applications/general/email_communication/email_domain.rst:9 +msgid "**Odoo Online** and **Odoo.sh** databases using the **default Odoo subdomain address** (e.g., `\\@company-name.odoo.com`) are pre-configured to **send authenticated emails** compliant with the SPF, DKIM, and DMARC protocols." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:12 -msgid "It is standard in Odoo that emails are received from ``\"name of the author\" ``. In other words this can be translated to: ``\"name of the author\" <{ICP.mail.from.filter}@{mail.catchall.domain}>``. In this case ICP stands for `ir.config_parameter`, which are the System Parameters. Deliverability is greatly improved with the :ref:`notifications configuration `." +#: ../../content/applications/general/email_communication/email_domain.rst:13 +msgid "If choosing to use a **custom domain** instead, **configuring SPF and DKIM records correctly is essential** to prevent emails from being quarantined as spam or not being delivered to recipients." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:18 -msgid "In order for servers to accept emails from Odoo on a more regular basis, one of the solutions is for customers to create rules within their own mailbox. A filter can be added to the email inbox so that when email is received from Odoo (`notifications@mycompany.odoo.com`) it is moved to the inbox. It is also possible to add the Odoo database domain onto a safe senders list or whitelist on the receiving domain." +#: ../../content/applications/general/email_communication/email_domain.rst:16 +msgid "If using :ref:`the default Odoo email server to send emails from a custom domain `, the SPF and DKIM records must be configured as presented below. If using an outgoing email server, it is required to use the SPF and DKIM records specific to that email service and a custom domain." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:24 -msgid "If an Odoo email server appears on a blacklist, notify Odoo via a `new help ticket `_ and the support team will work to get the servers removed from the blacklist." +#: ../../content/applications/general/email_communication/email_domain.rst:22 +msgid "Email service providers apply different rules to incoming emails. An email may be classified as spam even if it passes the SPF and DKIM checks." msgstr "" #: ../../content/applications/general/email_communication/email_domain.rst:28 -msgid "Should the Odoo database be using a custom domain for sending emails from Odoo there are three records that should be implemented on the custom domain's DNS to ensure deliverability of email. This includes setting records for :abbr:`SPF (Sender Policy Framework)`, :abbr:`DKIM (DomainKeys Identified Mail)` and :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)`. Ultimately though, it is up to the discretion of the final receiving mailbox." +msgid "SPF (Sender Policy Framework)" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:38 -msgid "Be SPF compliant" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:40 +#: ../../content/applications/general/email_communication/email_domain.rst:30 msgid "The Sender Policy Framework (SPF) protocol allows the owner of a domain name to specify which servers are allowed to send emails from that domain. When a server receives an incoming email, it checks whether the IP address of the sending server is on the list of allowed IPs according to the sender's :abbr:`SPF (Sender Policy Framework)` record." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:46 -msgid "The :abbr:`SPF (Sender Policy Framework)` verification is performed on the domain mentioned in the `Return-Path` field of the email. In the case of an email sent by Odoo, this domain corresponds to the value of the `mail.catchall.domain` key in the database system parameters." +#: ../../content/applications/general/email_communication/email_domain.rst:35 +msgid "In Odoo, the **SPF test is performed on the bounce address** defined under the :guilabel:`Alias Domain` field found under the database's :guilabel:`General Settings`. If using a custom domain as :guilabel:`Alias Domain`, it is necessary to configure it to be SPF-compliant." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:50 -msgid "The :abbr:`SPF (Sender Policy Framework)` policy of a domain is set using a TXT record. The way to create or modify a TXT record depends on the provider hosting the :abbr:`DNS (Domain Name System)` zone of the domain name. In order for the verification to work properly, each domain can only have one :abbr:`SPF (Sender Policy Framework)` record." +#: ../../content/applications/general/email_communication/email_domain.rst:39 +msgid "The SPF policy of a domain is set using a TXT record. The way to create or modify this record depends on the provider hosting the :abbr:`DNS (Domain Name System)` zone of the domain name." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:55 -msgid "If the domain name does not yet have a :abbr:`SPF (Sender Policy Framework)` record, create one using the following input: `v=spf1 include:_spf.odoo.com ~all`" +#: ../../content/applications/general/email_communication/email_domain.rst:42 +msgid "If the domain name does not yet have an SPF record, create one using the following input:" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:58 -msgid "If the domain name already has a :abbr:`SPF (Sender Policy Framework)` record, the record must be updated (and do not create a new one)." +#: ../../content/applications/general/email_communication/email_domain.rst:48 +msgid "If the domain name **already has an SPF record, the record must be updated**. Do not create a new one, as a domain must have only one SPF record." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:63 +#: ../../content/applications/general/email_communication/email_domain.rst:52 msgid "If the TXT record is `v=spf1 include:_spf.google.com ~all`, edit it to add `include:_spf.odoo.com`: `v=spf1 include:_spf.odoo.com include:_spf.google.com ~all`" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:66 -msgid "Check if the :abbr:`SPF (Sender Policy Framework)` record is valid with a free tool like `MXToolbox SPF `_." +#: ../../content/applications/general/email_communication/email_domain.rst:55 +msgid "Check the SPF record using a tool like `MXToolbox SPF Record Check `_. The process to create or modify an SPF record depends on the provider hosting the DNS zone of the domain name. The :ref:`most common providers ` and their documentation are listed below." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:72 -msgid "Enable DKIM" +#: ../../content/applications/general/email_communication/email_domain.rst:63 +msgid "DKIM (DomainKeys Identified Mail)" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:74 +#: ../../content/applications/general/email_communication/email_domain.rst:65 msgid "The DomainKeys Identified Mail (DKIM) allows a user to authenticate emails with a digital signature." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:77 -msgid "When sending an email, the Odoo server includes a unique :abbr:`DKIM (DomainKeys Identified Mail)` signature in the headers. The recipient's server decrypts this signature using the :abbr:`DKIM (DomainKeys Identified Mail)` record in the database's domain name. If the signature and the key contained in the record match, this guarantees that the message is authentic and has not been altered during transport." +#: ../../content/applications/general/email_communication/email_domain.rst:67 +msgid "When sending an email, the Odoo email server includes a unique :abbr:`DKIM (DomainKeys Identified Mail)` signature in the headers. The recipient's server decrypts this signature using the DKIM record in the database's domain name. If the signature and the key contained in the record match, it proves the message is authentic and has not been altered during transport." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:72 +msgid "Enabling DKIM is **required** when sending emails **from a custom domain** using the Odoo email server." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:75 +msgid "To enable DKIM, add a :abbr:`CNAME (Canonical Name)` record to the :abbr:`DNS (Domain Name System)` zone of the domain name:" msgstr "" #: ../../content/applications/general/email_communication/email_domain.rst:83 -msgid "To enable :abbr:`DKIM (DomainKeys Identified Mail)`, add a :abbr:`CNAME (Canonical Name)` record to the :abbr:`DNS (Domain Name System)` zone of the domain name:" +msgid "If the domain name is `company-name.com`, make sure to create a subdomain `odoo._domainkey.company-name.com` whose canonical name is `odoo._domainkey.odoo.com.`." msgstr "" #: ../../content/applications/general/email_communication/email_domain.rst:86 -msgid "`odoo._domainkey IN CNAME odoo._domainkey.odoo.com.`" +msgid "The way to create or modify a CNAME record depends on the provider hosting the DNS zone of the domain name. The :ref:`most common providers ` and their documentation are listed below." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:89 -msgid "If the domain name is `mycompany.com`, make sure to create a subdomain `odoo._domainkey.mycompany.com` whose canonical name is `odoo._domainkey.odoo.com.`." +#: ../../content/applications/general/email_communication/email_domain.rst:90 +msgid "Check if the DKIM record is valid using a tool like `MXToolbox DKIM Record Lookup `_. Enter `example.com:odoo` in the DKIM lookup tool, specifying that the selector being tested is `odoo` for the custom domain `example.com`." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:92 -msgid "The way to create or modify a :abbr:`CNAME (Canonical Name)` record depends on the provider hosting the :abbr:`DNS (Domain Name System)` zone of the domain name. The most common providers are :ref:`listed below `." +#: ../../content/applications/general/email_communication/email_domain.rst:97 +msgid "DMARC (Domain-based Message Authentication, Reporting and Conformance)" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:96 -msgid "Check if the :abbr:`DKIM (DomainKeys Identified Mail)` record is valid with a free tool like `DKIM Core `_. If a selector is asked, enter `odoo`." +#: ../../content/applications/general/email_communication/email_domain.rst:99 +msgid "The :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` record is a protocol that unifies :abbr:`SPF (Sender Policy Framework)` and :abbr:`DKIM (DomainKeys Identified Mail)`. The instructions contained in the DMARC record of a domain name tell the destination server what to do with an incoming email that fails the SPF and/or DKIM check." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:102 -msgid "Check the DMARC policy" +#: ../../content/applications/general/email_communication/email_domain.rst:105 +msgid "The aim of this documentation is to help **understand the impact DMARC has on the deliverability of emails**, rather than give precise instructions for creating a DMARC record. Refer to a resource like `DMARC.org `_ to set the DMARC record." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:104 -msgid "The Domain-based Message Authentication, Reporting, & Conformance (DMARC) record is a protocol that unifies :abbr:`SPF (Sender Policy Framework)` and :abbr:`DKIM (DomainKeys Identified Mail)`. The instructions contained in the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` record of a domain name tell the destination server what to do with an incoming email that fails the :abbr:`SPF (Sender Policy Framework)` and/or :abbr:`DKIM (DomainKeys Identified Mail)` check." +#: ../../content/applications/general/email_communication/email_domain.rst:109 +msgid "There are three DMARC policies:" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:112 -msgid "DMARC: TXT record" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:114 -msgid "`v=DMARC1; p=none;`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:116 -msgid "There are three :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` policies:" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:119 +#: ../../content/applications/general/email_communication/email_domain.rst:111 msgid "`p=none`" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:120 -#: ../../content/applications/general/email_communication/email_domain.rst:173 +#: ../../content/applications/general/email_communication/email_domain.rst:112 msgid "`p=quarantine`" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:121 +#: ../../content/applications/general/email_communication/email_domain.rst:113 msgid "`p=reject`" msgstr "" +#: ../../content/applications/general/email_communication/email_domain.rst:115 +msgid "`p=quarantine` and `p=reject` instruct the server that receives an email to quarantine that email or ignore it if the SPF or DKIM check fails." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:119 +msgid "**For the DMARC to pass, the DKIM or SPF check needs to pass** and the domains must be in alignment. If the hosting type is Odoo Online, DKIM configuration on the sending domain is required to pass the DMARC." +msgstr "" + #: ../../content/applications/general/email_communication/email_domain.rst:123 -msgid "`p=quarantine` and `p=reject` instruct the server that receives an email to quarantine that email or ignore it if the :abbr:`SPF (Sender Policy Framework)` and/or :abbr:`DKIM (DomainKeys Identified Mail)` check fails." +msgid "Passing DMARC generally means that the email will be successfully delivered. However, it's important to note that **other factors like spam filters can still reject or quarantine a message**." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:127 -msgid "If the domain name uses :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` and has defined one of these policies, the domain must be :abbr:`SPF (Sender Policy Framework)` compliant or enable :abbr:`DKIM (DomainKeys Identified Mail)`." +#: ../../content/applications/general/email_communication/email_domain.rst:126 +msgid "`p=none` is used for the domain owner to receive reports about entities using their domain. It should not impact the deliverability." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:132 -msgid "Yahoo or AOL are examples of email providers with a :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` policy set to `p=reject`. Odoo strongly advises against using an *@yahoo.com* or *@aol.com* address for the database users. These emails will never reach their recipient." +#: ../../content/applications/general/email_communication/email_domain.rst:130 +msgid ":literal:`_dmarc IN TXT “v=DMARC1; p=none; rua=mailto:postmaster@example.com”` means that aggregate DMARC reports will be sent to `postmaster\\@example.com`." msgstr "" #: ../../content/applications/general/email_communication/email_domain.rst:137 -msgid "`p=none` is used for the domain owner to receive reports about entities using their domain. It should not impact the deliverability if the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` check fails." +msgid "SPF, DKIM and DMARC documentation of common providers" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:141 -msgid ":abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` records are comprised of tags in the form of :abbr:`DNS (Domain Name System)` records. These tags/parameters allow for reporting, such as :abbr:`RUA (Reporting URI of aggregate reports)` and :abbr:`RUF (Reporting URI for forensic reports)`, along with more precise specification like :abbr:`PCT (Percentage of messages subjected to filtering)`, :abbr:`P (Policy for organizational domain)`, :abbr:`SP (Policy for subdomains of the OD)` :abbr:`ADKIM (Alignment mode for DKIM)` & :abbr:`ASPF (Alignment mode for SPF)`. For best practice, the the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` policy should not start out being too restrictive." -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:150 -msgid "The following chart displays available tags:" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:156 -msgid "Tag Name" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:157 -msgid "Purpose" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:158 -msgid "Example" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:159 -msgid "v" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:160 -msgid "Protocol version" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:161 -msgid "`v=DMARC1`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:162 -msgid "pct" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:163 -msgid "Percentage of messages subjected to filtering" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:164 -msgid "`pct=20`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:165 -msgid "ruf" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:166 -msgid "Reporting URI for forensic reports" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:167 -msgid "`ruf=mailto:authfail@example.com`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:168 -msgid "rua" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:169 -msgid "Reporting URI of aggregate reports" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:170 -msgid "`rua=mailto:aggrep@example.com`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:171 -msgid "p" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:172 -msgid "Policy for organizational domain" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:174 -msgid "sp" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:175 -msgid "Policy for subdomains of the OD" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:176 -msgid "`sp=reject`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:177 -msgid "adkim" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:178 -msgid "Alignment mode for DKIM" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:179 -msgid "`adkim=s`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:180 -msgid "aspf" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:181 -msgid "Alignment mode for SPF" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:182 -msgid "`aspf=r`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:184 -msgid "Check the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` record of a domain name with a tool like `MXToolbox DMARC `_." -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:188 -msgid "`DMARC.org is another great resource to learn about DMARC records. `_" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:194 -msgid "SPF, DKIM & DMARC documentation of common providers" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:196 +#: ../../content/applications/general/email_communication/email_domain.rst:139 msgid "`OVH DNS `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:197 -msgid "`OVH SPF `_" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:198 +#: ../../content/applications/general/email_communication/email_domain.rst:140 msgid "`GoDaddy TXT record `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:199 -msgid "`GoDaddy SPF `_" +#: ../../content/applications/general/email_communication/email_domain.rst:141 +msgid "`GoDaddy CNAME record `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:200 -msgid "`GoDaddy DKIM `_" +#: ../../content/applications/general/email_communication/email_domain.rst:142 +msgid "`NameCheap `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:201 -msgid "`NameCheap `_" -msgstr "" - -#: ../../content/applications/general/email_communication/email_domain.rst:203 +#: ../../content/applications/general/email_communication/email_domain.rst:143 msgid "`CloudFlare DNS `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:204 +#: ../../content/applications/general/email_communication/email_domain.rst:144 msgid "`Google Domains `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:205 +#: ../../content/applications/general/email_communication/email_domain.rst:145 msgid "`Azure DNS `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:207 +#: ../../content/applications/general/email_communication/email_domain.rst:147 msgid "To fully test the configuration, use the `Mail-Tester `_ tool, which gives a full overview of the content and configuration in one sent email. Mail-Tester can also be used to configure records for other, lesser-known providers." msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:212 +#: ../../content/applications/general/email_communication/email_domain.rst:152 msgid "`Using Mail-Tester to set SPF Records for specific carriers `_" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:5 -msgid "Send and receive emails in Odoo with an email server" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:8 -msgid "Odoo Online or Odoo.sh users" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:10 -msgid "Since **Odoo sets up its own mail servers for the database**, outgoing and incoming emails already work out-of-the-box. So for **Odoo Online** and **Odoo.sh** customers, nothing needs to be configured!" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:14 -msgid "Unless an external mail server is required to send large batches of mass emails, simply use the standard online Odoo database normally since it has already been pre-configured to send email." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:18 -msgid "The Odoo server is subject to a daily email limit to prevent abuse. The default limit is 200 emails sent per day for databases with an **Enterprise** subscription. This limit can be increased under certain conditions. See the :doc:`FAQ ` or contact support for more information." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:24 -msgid "Scope of this documentation" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:26 -msgid "This document is **mainly dedicated to Odoo on-premise databases** that do not benefit from an out-of-the-box solution to send and receive emails in Odoo, unlike `Odoo Online `_ and `Odoo.sh `_. Incoming and outgoing servers must be configured for on-premise databases." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:31 -msgid "The following sections below contain information on how to integrate an external email server with Odoo." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:35 -msgid "If no one in the company is employed to manage email servers, Odoo Online and Odoo.sh are strongly recommended. In these Odoo hosting types email sending and receiving works instantly and is monitored by professionals. Nevertheless, a company can use their own email server if they want to manage the email server's reputation themselves. For more information see :doc:`Configure DNS records to send emails in Odoo `" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:44 -msgid "Default notifications system" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:46 -msgid "Documents in Odoo (such as a CRM opportunity, a sales order, an invoice, etc.) have a discussion thread, called *chatter*." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:49 -msgid "When a database user posts a message in the chatter, this message is sent by email to the followers of the document as a notification (except to the sender). If a follower replies to the message, the reply updates the chatter, and Odoo relays another reply to the followers as a notification. Messages sent back to the chatter from users or external users will appear in the chatter from their respective email, or as the name listed in their *Contacts* record." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:55 -msgid "These notifications are sent using a default from address. For more information see :ref:`Use a default email address `." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:61 -msgid "Manage outbound messages" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:63 -msgid "As a system administrator, go to :menuselection:`Settings --> General Settings --> Discuss` in Odoo, and enable the :guilabel:`Custom Email Servers` option. Then, click :guilabel:`Save`. Next, click :guilabel:`Outgoing Email Servers` and click :guilabel:`Create` to create a new outgoing mail server record in Odoo. Reference the SMTP data of the external email server. Once all the information has been filled out, click :guilabel:`Test Connection`." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:70 -msgid ":doc:`google_oauth`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:71 -msgid ":doc:`azure_oauth`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:74 -msgid "Ensuring the outgoing domain has :abbr:`SPF (Sender Policy Framework)`, :abbr:`DKIM (DomainKeys Identified Mail)` and :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` set up on the :abbr:`DNS (Domain Name System)` will improve deliverability. For more information see :doc:`email_domain`." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:82 -msgid "Port restriction" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:84 -msgid "Note that port 25 is blocked for security reasons on the Odoo Online and Odoo.sh platforms. Try using ports 465, 587, or 2525 instead." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:90 -msgid "Use a default \"From\" email address" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:92 -msgid "Sometimes, an email's \"From\" (outgoing) address can belong to a different domain, and that can be a problem." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:95 -msgid "For example, if a customer with the email address `mary\\@customer.example.com` responds to a message, Odoo will try to redistribute that same email to the other subscribers in the thread. However, if the domain `customer.example.com` forbids that kind of usage for security, the email that Odoo is trying to redistribute would get rejected by some recipients' email servers." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:100 -msgid "To avoid that problem, Odoo sends all emails using a \"From\" address from the same authorized domain." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:103 -msgid "Access the :guilabel:`System Parameters` by activating :ref:`developer mode ` and going to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:106 -msgid "To force the email address from which emails are sent, a combination of the following keys needs to be set in the system parameters of the database:" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:109 -msgid "`mail.default.from`: accepts the local part or a complete email address as value" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:110 -msgid "`mail.default.from_filter`: accepts a domain name or a full email address as value" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:113 -msgid "The `mail.default.from_filter` works only for `odoo-bin` configurations or the default Odoo email server, otherwise this parameter can be set using the `from_filter` field on `ir.mail_server`." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:116 -msgid "The field can be a domain name or an entire email address, or it can remain empty. If the sender's email address does not match this set filter, then the email will be encapsulated using a combination of the two system parameters: `mail.default.from` and `mail.catchall.domain`." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:121 -msgid "In the following example, the from email address is replaced with the combination of the the two system parameters (`mail.default.from` and `mail.catchall.domain`). This is the default \\ notifications configuration in Odoo: ``“Admin” `` => ``“Admin” ``." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:126 -msgid "In other words if the email address of the author does not match `mail.default.from_filter`, the email address is replaced by `mail.default.from` (if it contains a full email address) or a combination of `mail.default.from` and `mail.catchall.domain`." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:130 -msgid "If the `from_filter` contains a full email address, and if the `mail.default.from` is the same as this address, then all of the email addresses that are different from `mail.default.from` will be encapsulated in `mail.default.from`." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:137 -msgid "Utilizing the \"From\" filter on an outgoing email server" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:139 -msgid "The :guilabel:`FROM Filtering` field allows for the use of a specific outgoing email server depending on the :guilabel:`From` email address or domain that Odoo is sending on behalf of. This setting can be used to improve the deliverability or sending success rate of emails sent from the database. Setting the :guilabel:`FROM Filtering` field can also be used to send from different domains in a multi-company environment. Access this field in Odoo by navigating to :menuselection:`Settings --> Discuss --> Custom Mail Servers --> Outgoing Mail Servers --> New`." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:-1 -msgid "Outgoing email server settings and the FROM filter settings." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:150 -msgid "When an email is sent from Odoo while the :guilabel:`FROM Filtering` field is set, an email server is chosen in the following sequence:" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:153 -msgid "First, Odoo searches for an email server that has the same :guilabel:`FROM Filtering` value as the :guilabel:`From` value (email address) defined in the outgoing email. For example, if the :guilabel:`From` value (email address) is `test\\@example.com`, only the email servers that have the :guilabel:`FROM Filtering` value equal to `test\\@example.com` are returned." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:157 -msgid "However, if no email servers are found that use the :guilabel:`From` value, then Odoo searches for an email server that has the same *domain* as the :guilabel:`From` value (email address) defined in the outgoing email. For example, if the :guilabel:`From` email address is `test\\@example.com`, only the email servers that have the :guilabel:`FROM Filtering` value equal to `example.com` are returned." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:163 -msgid "If no email servers are found after checking for the domain, then Odoo returns all email servers that do not have any :guilabel:`FROM Filtering` value(s) set." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:166 -msgid "Should this query return no results, then Odoo performs a search for an email server using the system parameter: `mail.default.from`. First, the email address listed attempts to match an email server, and then the domain attempts to find a match. If no email server is found, Odoo returns the first outgoing email server (sorted by priority)." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:172 -msgid "If several email servers are found, then Odoo uses the first one according to its priority. For example, if there are two email servers, one with a priority of `10` and the other with a priority of `20`, then the email server with a priority of `10` is used first." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:179 -msgid "Set up different dedicated servers for transactional and mass emails" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:181 -msgid "In Odoo a separate email server can be used for transactional emails and mass mailings. Example: Use Postmark or SendinBlue for transactional emails, and Amazon SES, Mailgun, Sendgrid or :doc:`Mailjet ` for mass mailings." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:186 -msgid "A default outgoing email server is already configured. Do not create an alternative one unless a specific external outgoing email server is needed for technical reasons." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:189 -msgid "To do this, first activate the :ref:`developer mode `, and then go to :menuselection:`Settings --> Technical --> Outgoing` email servers. There, create two outgoing email server settings; one for the transactional emails and one for the mass mailing server. Make sure to give priority to the transactional server over the mass mailing server by providing a lower priority number for the transactional email server." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:195 -msgid "Now, go to :menuselection:`Email Marketing --> Settings` and enable :guilabel:`Dedicated Server`. Choose the appropriate email server. With these settings, Odoo uses the server with the lower priority for transactional emails, and the server here selected for mass mails. Note that in this case, the domain's Sender Policy Framework (SPF) records must be set to include both transactional and mass mail servers." -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:202 -msgid ":doc:`email_domain`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_servers.rst:207 +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:3 msgid "Manage inbound messages" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:209 -msgid "Odoo relies on generic email aliases to fetch incoming messages." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:5 +msgid "An inbound message is an email delivered to an Odoo database. Anyone can send an email to an email alias created in the database or reply to an email that was previously sent from the database based on the *reply-to* header." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:211 -msgid "**Reply messages** of messages sent from Odoo are routed to their original discussion thread (and to the inbox of all its followers) by the alias of the model if there is any or by the catchall alias (**catchall@**). Replies to messages of models that do not have a custom alias will use the catchall alias (`catchall@mycompany.odoo.com`). The catchall address, however, does not have another action attached to it like other aliases might, it is only used to collect replies." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:12 +msgid "Email aliases" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:216 -msgid "**Bounced messages** are used as a Return-Path. One example this is especially useful for is in `Odoo Email Marketing `__. In this case bounces are opt-out based on if the email bounced too many times (5) in the last month and the bounces are separated by one week. This is done to avoid blacklisting someone because of a mail server error. If these circumstances are met then the email is considered invalid and is blacklisted. A log note is added on the contact under :guilabel:`Blacklisted Email Addresses` on the :guilabel:`Email Marketing Configuration Menu`." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:17 +msgid "Model specific aliases" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:224 -msgid "Messages that bounce in the chatter (outside of Email Marketing) will populate a red envelope indicating the failed delivery. This can be helpful to know that a Sales Order or an Invoice did not reach its final destination." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:19 +msgid "Some applications have their specific aliases (sales teams, helpdesk teams, projects, etc.). These aliases are used to:" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:227 -msgid "**Original messages**: several business objects have their own alias to create new records in Odoo from incoming emails:" +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:22 +msgid "Create a record when an email is sent directly to the alias," msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:230 -msgid "Sales channel (to create *Leads* or *Opportunities* in `Odoo CRM `_)" +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:23 +msgid "Receive replies to an email initially sent from a record." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:232 -msgid "Support channel (to create *Tickets* in `Odoo Helpdesk `_)" +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:-1 +msgid "The local-part \"info\" is used for the alias of the sales team." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:233 -msgid "Projects (to create new *Tasks* in `Odoo Project `_)" +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:30 +msgid "In the example displayed above, sending an email to `info@company-name.odoo.com` will create a new opportunity or a new lead automatically assigned to the corresponding sales team. If an email is sent from the chatter of an existing opportunity, the *reply-to* will be `info@company-name.odoo.com`. The reply will be posted in the right chatter, according to the *message-id* header." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:235 -msgid "Job positions (to create *Applicants* in `Odoo Recruitment `_)" +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:39 +msgid "Catchall" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:238 -msgid "Depending on the mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Odoo alias in the mail server." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:41 +msgid "If an application does not have an alias, a generic fallback alias is used: the catchall. An email sent from a chatter has a reply address set to this catchall alias. A reply sent to the catchall is posted to the right chatter thanks to the *message-id* header." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:241 -msgid "Create the corresponding email addresses in the mail server (**catchall@**, **bounce@**, **sales@**, etc.)." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:45 +msgid "By default, the local-part *catchall* will be used. Enable :ref:`developer-mode` and go to :menuselection:`Settings --> Technical --> Emails: Alias Domains` to access the configuration." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:243 -msgid "Set the :guilabel:`Alias Domain` name in :menuselection:`Settings --> General Settings --> Discuss`. Changing the :guilabel:`Alias Domain` will change the catchall's domain for the database." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:48 +msgid "An email to the catchall always needs to be a reply to a previous email sent from the database. If an email is sent directly to the catchall, the sender will receive the following message:" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:246 -msgid "If the database's hosting type is Odoo on-premise, create an :guilabel:`Incoming Mail Server` in Odoo for each alias. To create a new incoming server go to: :menuselection:`Settings --> Discuss --> Custom Mail Servers --> Incoming Mail Servers --> New` Fill out the form according to the email provider's settings. Leave the :guilabel:`Actions to Perform on Incoming Mails` field blank. Once all the information has been filled out, click on :guilabel:`TEST & CONFIRM`." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:-1 +msgid "Bounce email from \"MAILER-DEAMON\" explaining how to contact the database." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:0 -msgid "Incoming mail server configuration on Odoo." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:55 +msgid "The email address `info@company-name.com` displayed in the screenshot above is the email address set on the company. Upon entering the developer mode on a company profile, additional configuration options (such as catchall and bounce) become readable. It can be modified by clicking on the internal link of the Email Domain. It is generally not recommended to modify these options unless specific needs dictate, as it will affect all replies to previously sent emails." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:256 -msgid "If the database's hosting type is Odoo Online or Odoo.sh, redirecting or forwarding incoming messages to Odoo's domain name instead of the external email server is recommended. That way, incoming messages can be received without delay. Redirections for all email addresses should be set to Odoo's domain name in the email server (e.g. `catchall\\@mydomain.ext` to `catchall\\@mycompany.odoo.com`)." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:63 +msgid "An alias can be configured on a sales team in the CRM app. When a customer replies to an email coming from the CRM app, the *reply-to* is `info@company-name.odoo.com`." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:262 -msgid "All the aliases are customizable in Odoo. Object aliases can be edited from their respective configuration view by navigating to :menuselection:`Settings --> Technical Menu --> Email --> Aliases`." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:66 +msgid "When an email is sent from the Contact app, the reply address is `catchall@company-name.odoo.com` because there is no alias on the contact model." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:266 -msgid "To edit catchall and bounce aliases, first activate the :ref:`developer mode `. Then, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (`mail.catchall.alias` & `mail.bounce.alias`). These types of changes should be completed prior to the database going live. If a customer replies after a change is made then the system will not recognize the old alias, and the reply will not be received." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:70 +msgid "It is advised to keep the local-part of the catchall and the bounce unchanged. If this value is modified, previous emails sent from the database will still have the previous local-part values. This could lead to replies not being correctly received in the database." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:272 -msgid "By default, inbound messages are fetched every 5 minutes for on-premise databases." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:77 +msgid "Bounce" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:275 -msgid "This value can be changed in :ref:`developer mode `. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for :guilabel:`Mail: Fetchmail Service`." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:79 +msgid "In the same way the catchall alias is used to build the reply address, the bounce alias is used to build the *return-path* of the email. The *return-path* is used when emails cannot be delivered to the recipient and an error is returned to the sender." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:280 -msgid "System parameters that prevent feedback loops" +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:83 +msgid "By default the name *bounce* will be used. Enable :ref:`developer-mode` and go to :menuselection:`Settings --> Technical --> Emails: Alias Domains` to access the configuration." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:282 -msgid "There are two system parameters that help prevent email loops from occurring in Odoo. These parameters were introduced in Odoo 16 to prevent aliases from creating too many records and to prevent feedback loops on the catchall reply-to email address. They are present in database but not in the *System Parameters*. To override the following defaults they need to be added in." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:87 +msgid "On Odoo Online, when using the default outgoing email server, the return-path address is forced to the value `bounce@company-name.odoo.com` independently of the value set as bounce alias." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:287 -msgid "The two system parameters are as follows:" +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:90 +msgid "When an error occurs, a notification is received and displayed in a red envelope in the chatter. In some cases, the red envelope can just contain a `no error` message, meaning there is an error that could not be handled by Odoo." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:289 -msgid "`mail.gateway.loop.minutes` (120 minutes by default)" +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:94 +msgid "A notification will also be displayed in the Discuss icon on the navigation bar." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:290 -msgid "`mail.gateway.loop.threshold` (20 by default)" +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:-1 +msgid "An email sent to a contact had an issue and the error is reported on the navbar." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:292 -msgid "Add these fields in Odoo by first enabling :ref:`developer mode `, and then navigating to :menuselection:`Settings --> Technical Menu --> Parameters --> System Parameters`. Change the value of these parameters, as needed." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:100 +msgid "If the email address of the recipient is incorrect, by clicking on the red envelope in the chatter an error message containing the reason for the failure will be given." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:296 -msgid "When an email is received in the Odoo database on the catchall email address or on any alias, Odoo looks at the mail received for the given period of time defined in the system parameter `mail.gateway.loop.minutes`. If the received email was sent to an alias then Odoo will reference the `mail.gateway.loop.threshold` system parameter and determine the value as the number of records this alias is allowed to create in the given period of time (value of `mail.gateway.loop.minutes`)." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:0 +msgid "An email sent to a wrong domain generates a bounce displayed as a red envelope." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:302 -msgid "In addition, when email is received to the catchall email address, Odoo will reference the emails received to the database during the set period of time (as stated by the value in the system parameter: `mail.gateway.loop.minutes`). Odoo will then determine whether any of the emails received match that of the email(s) being received during the specified time-frame, and will prevent a feedback loop from occurring if a duplicate email is detected." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:109 +msgid "Receive emails with Odoo's default configuration" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:309 -msgid "Allow alias domain system parameter" +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:111 +msgid "On **Odoo Online** and **Odoo.sh**, the email alias, reply, and bounce addresses are pre-configured. These addresses use the alias domain automatically added to a standard database." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:311 -msgid "Incoming aliases are set in the Odoo database to create records by receiving incoming emails. To view aliases set in the Odoo database, first activate the :ref:`developer mode `. Then, go to :menuselection:`Settings app --> Technical --> Email section --> Aliases`." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:115 +msgid "Assuming the database URL is `https://mydatabase.odoo.com`, the alias domain `mydatabase.odoo.com` is automatically created. Catchall and bounce can be used and their address is respectively `catchall@mydatabase.odoo.com`, and `bounce@mydatabase.odoo.com`." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:315 -msgid "The following system parameter, `mail.catchall.domain.allowed`, set with allowed alias domain values, separated by commas, filters out correctly addressed emails to aliases. Setting the domain(s) for which the alias can create a ticket, lead, opportunity, etc., eliminates false positives where email addresses with only the prefix alias (not the domain) are present." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:119 +msgid "If the CRM app is installed, and a sales team with the alias `info` is created, the `info@mydatabase.odoo.com` address can be used immediately. The same goes for any other alias created in other applications." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:320 -msgid "In some instances, matches have been made in the Odoo database when an email is received with the same alias prefix and a different domain on the incoming email address. This is true in the sender, recipient, and :abbr:`CC (Carbon Copy)` email addresses of an incoming email." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:123 +msgid "The database domain is ready to be used to receive emails without any additional configuration." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:325 -msgid "When Odoo receives emails that have the name `commercial` prefix alias in the sender, recipient, or :abbr:`CC (Carbon Copy)` email address(es) (e.g. commercial@gmail.com, commercial@odoo.net), the database falsely treats the email as the full `commercial` alias (with a different domain), and therefore, creates a ticket/lead/opportunity/etc." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:128 +msgid "Use multiple Odoo subdomains" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:331 -msgid "This alias mismatch issue has been resolved in Odoo 17, however, the `mail.catchall.domain.allowed` system parameter is still used in Odoo 17 for backward compatibility." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:130 +msgid "On **Odoo Online**, the only Odoo subdomain is the one defined at the database creation." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:335 -msgid "To add the `mail.catchall.domain.allowed` system parameter, first, activate the :ref:`developer mode `. Then, go to :menuselection:`Settings app --> Technical --> Parameters section --> System Parameters`. Click :guilabel:`Create`. Then, type in `mail.catchall.domain.allowed` for the :guilabel:`Key` field." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:132 +msgid "On **Odoo.sh**, it is possible to use several Odoo subdomains. In the settings of the branch, additional Odoo subdomains can be added as long as they are not used yet in another branch. These domains must then be added to the alias domains to be used by a company." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:340 -msgid "Next, for the :guilabel:`Value` field, add the domain(s) separated by comma(s) (if plural domains). Manually :guilabel:`Save`, and the system parameter takes immediate effect." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:-1 +msgid "Setting up an Odoo subdomain on a branch." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:-1 -msgid "mail.catchall.domain.allowed system parameter set with key and value highlighted." +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:142 +msgid "Use a custom domain for inbound messages" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:144 +msgid "The :ref:`alias domain ` must be selected in the general settings. If you have multiple companies, each one must be configured." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:-1 +msgid "The alias domain in the general settings." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:150 +msgid "All the aliases will use this custom domain. Replies on models for which an alias is configured are done to `[alias]@my-custom-domain.com`. Replies to other models are sent to the catchall through `catchall@my-custom-domain.com`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:-1 +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:0 +msgid "Technical schema of mailing route when using a custom domain in Odoo." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:158 +msgid "If emails are sent using Odoo's email servers while using a custom domain, follow the :ref:`\"Using a custom domain with Odoo’s email server\" instructions `." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:162 +msgid "Since this custom domain is used, all emails using an alias (replies, bounces and direct sends) are sent to an address of the domain. They are thus delivered to the email server linked to the domain (MX record). To display them in the chatter or to create new records, it is necessary to retrieve these incoming emails in the Odoo database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:171 +msgid "Method" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:172 +msgid "Benefits" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:173 +msgid "Drawbacks" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:174 +msgid ":ref:`Redirections `" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:175 +msgid "Easy to set up, emails are directly sent to the database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:176 +msgid "Each alias of a database needs to be configured." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:177 +msgid ":ref:`Incoming mail servers `" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:178 +msgid "Allows to keep a copy of the email in your mailbox (with IMAP). Allows to create records in the chosen model." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:180 +msgid "Depends on a CRON, meaning emails are not retrieved immediately in the database. Each alias of a database needs to be configured." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:182 +msgid ":ref:`MX record `" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:183 +msgid "Only one record needs to be created to make all aliases work properly." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:184 +msgid "Using a subdomain is required. Requires advanced technical knowledge." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:188 +msgid "For **on-premise databases**, the redirection and the MX record methods also require configuring the :doc:`mail gateway script <../../../../administration/on_premise/email_gateway>`. Going through this script requires **advanced technical and infrastructure knowledge**." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:193 +msgid "Refer to your provider’s documentation for more detailed information on how to handle the methods detailed below." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:199 +msgid "Redirections" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:201 +msgid "If the database is hosted on **Odoo Online** or **Odoo.sh**, using redirections is recommended. They allow messages to be received without delay in the database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:204 +msgid "It is mandatory to redirect the catchall and bounce address to the Odoo subdomain of the database. Every other alias used must be redirected as well." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:208 +msgid "With one sales team, the following redirections are required:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:210 +msgid "`catchall@company-name.com` → `catchall@company-name.odoo.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:211 +msgid "`bounce@company-name.com` → `bounce@company-name.odoo.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:212 +msgid "`info@company-name.com` → `info@company-name.odoo.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:215 +msgid "Some providers ask to validate the redirection by sending a link to the target email address. This procedure is an issue for catchall and bounce since they are not used to create records." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:218 +msgid "Modify the catchall value on the mail alias domain. :ref:`developer-mode` must be enabled to access this menu. For example, it can be changed from `catchall` to `temp-catchall`. This will allow to use `catchall` as the local-part of another alias." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:221 +msgid "Open an app that uses an alias. For example, CRM contains aliases for each sales team. Set `catchall` as the local-part of the alias of a sales team." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:223 +msgid "The validation email will create a record in the CRM app. The email sent will be visible in the chatter, allowing you to validate the redirection." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:225 +msgid "Do not forget to change back the alias of the sales team and the catchall value on the mail alias domain, just as they were before this procedure." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:229 +msgid "An alternative to redirections is **forwarding**. With forwarding, **the address forwarding the email will be identified as the sender**, while with redirections, the original sender will always remain." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:236 +msgid "Incoming mail servers" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:238 +msgid "As mentioned earlier, using redirections is the recommended method to receive emails in Odoo. However, it is also possible to set up incoming mail servers. Using this method means creating an incoming email server for each mailbox on your server, catchall, bounce, and every alias of the database, in order to fetch all incoming emails. Incoming mail servers are created by going to :menuselection:`Settings --> Technical --> Emails: Incoming Mail Servers`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:245 +msgid "We recommend using the IMAP protocol over the POP protocol, as IMAP fetches all unread emails, while POP fetches all the emails' history and then tags them as deleted in your mailbox." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:249 +msgid "It is also possible to connect a mailbox through :doc:`Gmail with Google OAuth ` or :doc:`Outlook with Microsoft Azure OAuth `." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:252 +msgid "Regardless of the protocol chosen, emails are fetched using the *Mail: Fetchmail Service* scheduled action." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:255 +msgid "Additionally, using an incoming mail server in Odoo gives the opportunity to create new records in a specified model. Each incoming mail server can create records in a different model." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:259 +msgid "Emails received on `task@company-name.com` are fetched by the Odoo database. All fetched emails will create a new project task in the database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:268 +msgid "MX record" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:270 +msgid "A third option is to create a MX record in your DNS zone which specifies the mail server managing emails sent to your domain. **Advanced technical knowledge is required.**" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:274 +msgid "This configuration only works with a subdomain on the Odoo Online or Odoo.sh infrastructure (e.g., `@mail.mydomain.com`)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:277 +msgid "Below are presented some specifications depending on the hosting type:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:281 +#: ../../content/applications/general/email_communication/faq.rst:296 +msgid "Odoo Online" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:283 +msgid "The custom subdomain must be added to your :doc:`Odoo Portal <../../websites/website/configuration/domain_names>`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:286 +#: ../../content/applications/general/email_communication/faq.rst:301 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:288 +msgid "The custom subdomain must be added to the :doc:`settings of the project <../../../administration/odoo_sh/getting_started/settings>`:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:0 +msgid "Adding a custom subdomain for mail to Odoo.sh project settings." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:297 +msgid "Infinite email loops" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:299 +msgid "In some cases, infinite mailing loops can be created. Odoo provides some protection against such loops, ensuring the same sender cannot send too many emails **that would create records** to an alias in a specific time span." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:303 +msgid "By default, an email address can send up to 20 emails in 120 minutes. If more emails are sent, they are blocked and the sender receives the following message:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:-1 +msgid "Bounce email received after attempting contact too many times an alias." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:309 +msgid "To change the default behavior, enable :ref:`developer-mode`, then go to :menuselection:`Settings --> Technical --> Parameters: System Parameters` to add two parameters." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:312 +msgid "For the first parameter, enter `mail.gateway.loop.minutes` as the :guilabel:`Key` and choose a number of minutes as the :guilabel:`Value` (`120` is the default behavior)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:314 +msgid "For the second parameter, enter `mail.gateway.loop.threshold` as the :guilabel:`Key` and choose a number of emails as the :guilabel:`Value` (`20` is the default behavior)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_inbound.rst:318 +msgid "These parameters are only used to prevent the creation of new records. They **do not prevent replies** from being added to the chatter." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:3 +msgid "Manage outbound messages" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:8 +msgid "Sending emails with Odoo's default configuration" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:10 +msgid "On **Odoo Online** and **Odoo.sh**, sending and receiving emails works out of the box. No configuration is required." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:13 +msgid "When a database is created, the subdomain `company-name.odoo.com` is used to send and receive emails. The deliverability is optimized for this subdomain as it uses Odoo’s DNS configuration." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:17 +msgid "If the database subdomain is `company-name.odoo.com` and all mailing configurations are the default ones, all emails will be sent from `notifications@company-name.odoo.com`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:-1 +msgid "Odoo’s default outbound messages configuration." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:23 +msgid "Emails are sent with `catchall@company-name.odoo.com` as the *reply-to* address. In addition, delivery errors are sent to `bounce@company-name.odoo.com`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:27 +msgid "The catchall, bounce, and notification addresses do not work like other aliases. They do not have the vocation to create records in a database. Emails sent to an alias are automatically routed and will reply to an existing and linked record or will create a new one in the database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:34 +msgid "Using a custom domain to send emails" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:36 +msgid "The database can be configured to use a custom domain, in which case all default email addresses are built using the custom domain. If the custom domain is `company-name.com`, the sender address will be `notifications@company-name.com`, the *reply-to* address `catchall@company-name.com`, and the *bounce* address `bounce@company-name.com`. The custom domain can be utilized when sending emails either with Odoo’s email servers or an external one." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:42 +msgid "This section assumes ownership of a custom domain. If not, a custom domain must be purchased from a domain registrar such as GoDaddy, Namecheap, or any alternative provider." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:48 +msgid "Using a custom domain with Odoo’s email server" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:50 +msgid "On **Odoo Online** or **Odoo.sh**, some configurations are mandatory in the custom domain's DNS to ensure good deliverability." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:54 +msgid "Most of the configuration will be done on the domain provider’s side, and it might require some configuration on the mail server itself. **Some technical knowledge is required.**" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:57 +msgid "The first step is to configure the :ref:`SPF ` and :ref:`DKIM ` to be compliant with Odoo’s mail server." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:60 +msgid "Next, the custom domain must be set as the alias domain of a company. Select the company, open the :guilabel:`Settings`, and add the custom domain under the :guilabel:`Alias Domain` field." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:63 +msgid "After adding the alias domain, click the :icon:`oi-arrow-right` (:guilabel:`internal link`) icon to assign more companies to the custom domain if needed. Enable the :ref:`developer-mode` mode to modify the default aliases if desired:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:67 +msgid ":guilabel:`Bounce Alias`: the mailbox used to catch delivery errors and populate the :ref:`red envelope ` on the corresponding message." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:69 +msgid ":guilabel:`Catchall Alias`: the default mailbox used to centralize all replies." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:70 +msgid ":guilabel:`Default From Alias`: the default sender address." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:73 +msgid "At the creation of the first alias domain, all companies will use it. If you create a new company, the alias domain automatically set is the one with the lowest priority (ad displayed on the alias domain list in :ref:`developer-mode`)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:77 +msgid "All email aliases (e.g., related to CRM or Helpdesk teams) must have their corresponding mailbox in the custom domain mail server." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:-1 +msgid "Technical schema of external mail server configuration with Odoo." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:83 +msgid "To receive emails in the Odoo database within the corresponding chatter (CRM, invoices, sales orders, etc.), one of these three methods must be used:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:86 +msgid ":ref:`Redirections/forwarding `," +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:87 +msgid ":ref:`Incoming mail servers `," +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:88 +msgid ":ref:`MX record ` (requires advanced technical knowledge)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:90 +msgid "Using a custom domain implies that specific :ref:`local-parts ` might be used by Odoo to send emails." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:96 +msgid "Sending emails with an external SMTP server" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:99 +msgid "If utilizing your own outgoing mail server, it must be paired with your own domain, as updating the DNS of an Odoo subdomain is not feasible." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:102 +msgid "To add an external SMTP server in Odoo, open :guilabel:`Settings`, and enable the :guilabel:`Use Custom Email Servers` option found under the :guilabel:`Discuss` section." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:105 +msgid "Still under the :guilabel:`Discuss` section, click :guilabel:`Outgoing Email Servers`, then `New` to create an outgoing mail server record. Most fields are the common parameters used to set up a connection to an SMTP server; use the values provided by your email provider." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:109 +msgid "Once completed, click :guilabel:`Test Connection`. Note that a successful test connection does not confirm that the email will go out as some restriction might remain on the provider side, thus, it is recommended to consult your provider’s documentation." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:116 +msgid "Local-part values" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:118 +msgid "Below are presented the different local-part values that can be used by Odoo to send emails. It might be required to whitelist them in your mail server:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:121 +msgid "The Alias Domain Bounce Alias (default value = `bounce`)," +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:122 +msgid "The Alias Domain Default From (default value = `notifications`)," +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:123 +msgid "The default admin address `admin@company-name.odoo.com` or, if changed, the new value)," +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:124 +msgid "The default Odoobot address `odoobot@company-name.odoo.com` or, if changed, the new value)," +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:125 +msgid "The specific FROM defined on an email marketing campaign," +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:126 +msgid "The specific FROM that can be defined in an email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:129 +msgid ":doc:`google_oauth`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:130 +msgid ":doc:`azure_oauth`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:135 +msgid "Setting up different servers for transactional and mass emails" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:140 +msgid "Personalized mail servers" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:142 +msgid "Transactional emails and mass mailings can be sent using separate email servers in Odoo. Doing so means day-to-day emails, quotations, or invoices sent to clients will be handled as *transactional emails*. *Mass mailing emails*, including the sending of batches of invoices or quotations, will be managed by the Marketing Automation or Email Marketing application." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:148 +msgid "You can use services like Gmail, Amazon SES, or Brevo for transactional emails, and services like Mailgun, Sendgrid, or Mailjet for mass mailings." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:151 +msgid "First, activate the :ref:`developer-mode` and go to :menuselection:`Settings --> Technical --> Email: Outgoing Mail Servers`. There, add two outgoing email server records, one for the transactional emails server and one for the mass mailings server. Enter a lower :guilabel:`Priority` value for the transactional server (e.g., `1`) over the mass mailings server (e.g., `2`) so transactional emails are given priority." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:-1 +msgid "Example of split between transaction and mass mailing mail servers." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:160 +msgid "Now, go to :menuselection:`Email Marketing --> Configuration --> Settings`, enable :guilabel:`Dedicated Server`, and select the appropriate email server. Odoo uses the server with the lowest priority value for transactional emails, and the server selected here for mass mailings." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:-1 +msgid "Dedicated mail server on Email Marketing app settings." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:171 +msgid "FROM filtering" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:174 +msgid "It’s **highly recommended** to configure the FROM Filtering on the outgoing mail servers as per the instructions of your provider." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:177 +msgid "The :guilabel:`FROM Filtering` field allows for the use of a specific outgoing email server depending on the *From* email address or domain that Odoo is sending on behalf of. The **value must be a domain or a complete address** that matches the sender’s email address and is trusted on the outgoing mail server provider's side." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:182 +msgid "If FROM filtering is not used, emails will go out using the notification address." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:185 +msgid "Some outgoing mail servers require a specific configuration of the FROM filter." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:187 +msgid "When an email is sent from Odoo, the following sequence is used to choose the outgoing email server:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:189 +msgid "First, Odoo searches for a server that has the same FROM filtering value as the From value (i.e., email address) defined in the outgoing email. This configuration is ideal if all users of a company share the same domain but have different local-parts." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:194 +msgid "If the sender's email address is `test@example.com`, only an email server having a FROM filtering value equal to `test@example.com` or `example.com` can be used." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:197 +msgid "If no server is found based on the first criteria, Odoo looks for the first server without a FROM filtering value set. The email will be overridden with the notification address." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:200 +msgid "If no server is found based on the second criteria, Odoo uses the first server, and the email will be overridden with the notification address." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:204 +msgid "To determine which server is first, Odoo uses the priority value (the lower the value is, the higher the priority is). Failing to do so, the first server is determined by the servers' names, using alphabetical order." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:208 +msgid "It is also possible to use Odoo's mail server for transactional emails in addition to mass mailings." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:213 +msgid "Using an external email server and Odoo’s default server" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:215 +msgid "On Odoo Online and Odoo.sh, databases are started with Odoo's SMTP server. If no outgoing mail server is set, the default Odoo's SMTP server will be used." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:-1 +msgid "Adding a mail server using the Odoo's mail server with the CLI authentication." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:222 +msgid "If an outgoing mail server is used simultaneously with Odoo’s default server (CLI), the FROM filter of the outgoing mail server must contain a custom domain, and the FROM filter of the CLI must contain Odoo’s subdomain. If there is no FROM filtering, the email will go out using the notification address." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:-1 +msgid "Splitting of Odoo mail server for transactional emails and Mail server for Mass mailing." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:231 +msgid "On Odoo Online, the command line interface is equivalent to the default Odoo mail server, using the same limit as if there was no outgoing mail server in place." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:235 +msgid "On Odoo Online, the page also shows your daily email usage and your daily limit. On Odoo.sh, you need to check on the monitor page the number of outgoing emails that were sent." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:239 +msgid "On Odoo.sh, to use the command-line interface, an outgoing mail server can be configured on the configuration file." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:243 +msgid "Odoo’s mail server is meant for transactional emails and small-scale marketing campaigns. The :ref:`daily limit ` depends on the database type and the applications used." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:250 +msgid "Using a custom domain with an external email server" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:252 +msgid "Similar to the :ref:`previous chapter `, proper configuration might be needed to ensure that the external email server is allowed to send emails using your custom domain. Refer to your provider’s documentation to properly set up the relevant records (SPF, DKIM, and DMARC). A list of the :ref:`most common providers is available `." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:259 +msgid "DNS configuration is required when you use your own domain. If an external outgoing mail server is used, configuring the records as described in the :doc:`Odoo DNS configuration for our mail servers documentation ` **will not have the desired effect**, as it is independent of Odoo when using a custom email server. Odoo does not allow the configuration of Odoo's subdomain." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:268 +msgid "Port restriction" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:270 +msgid "Port 25 is blocked for security reasons on Odoo Online and Odoo.sh. Try using port 465, 587, or 2525 instead." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:276 +msgid "Alias domain" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:278 +msgid "The catchall domain is company-specific. By default, all companies share Odoo’s subdomain (e.g., `company-name.odoo.com`), but each company may have its own custom email domain." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:281 +msgid "When the :ref:`developer-mode` is activated, the alias domain options are available by going to :menuselection:`Settings --> Technical --> Email: Alias Domains`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:285 +msgid "Any modification of the alias domain must be done very carefully. If one of the aliases (bounce, catchall, default from) is changed, all previous emails that are not properly redirected to the new aliases will be lost." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:289 +msgid "The :guilabel:`Default From Alias` field can be filled with a local-part of the email address (by default `notifications`) or a full email address. Configure it to determine the `FROM` header of your emails. If a full email address is used, all outgoing emails will be overwritten with this address." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:297 +msgid "Notification system" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:299 +msgid "When an email is sent from the chatter, customers can reply directly to it. If a customer replies directly to an email, the answer is logged in the same chatter, thus functioning as a message thread related to the record." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:303 +msgid "Upon receiving the reply, Odoo then uses the subscribed followers (based on the subscribed subtypes) to send them a notification by email, or in the Odoo inbox, depending on the user’s preferences." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:307 +msgid "If a customer with the email address `“Mary” ` makes a direct reply to an email coming from the Odoo database, Odoo's default behavior is to redistribute the email's content to all other followers within the thread." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:311 +msgid "As Mary’s domain does not belong to the alias domain, Odoo overrides the email address and uses the notification email address to notify the followers. This override depends on the configuration done in the database. By default, on Odoo Online and Odoo.sh, the email `FROM` address will be overridden with the value `notifications@company-name.odoo.com` instead of `mary@customer.example.com`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:317 +msgid "The address is constructed using the name of the sender and `{alias domain, default from alias}`@`{alias domain, domain name}`, by default, `notifications@company-name.odoo.com`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:324 +msgid "Using a unique email address for all outgoing emails" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:326 +msgid "To force the email address from which emails are sent, activate the :ref:`developer-mode`, and go to :menuselection:`Settings --> Technical --> Email: Alias Domains`. On the :guilabel:`Default From Alias`, use the the local-part or a complete email address as the value." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers_outbound.rst:331 +msgid "If a **complete address** is used as the :guilabel:`Default From Alias` value, **all** outgoing emails will be overwritten by this address." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:3 -msgid "Email issues" +msgid "Common emailing issues and solutions" msgstr "" #: ../../content/applications/general/email_communication/faq.rst:5 -msgid "This document contains an explanation of the most recurring emailing issues in Odoo." +msgid "This page lists the most common emailing issues and their solutions." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:8 -msgid "Outgoing emails" +#: ../../content/applications/general/email_communication/faq.rst:10 +msgid "Odoo is not an email provider" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:13 -msgid "Email is not sent" +#: ../../content/applications/general/email_communication/faq.rst:12 +msgid "Odoo does not function like a classic email inbox, such as Gmail, Outlook, Yahoo, etc." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:15 -msgid "The first indicator showing that an email has not been sent is the presence of a red :icon:`fa-envelope` :guilabel:`(envelope)` icon, next to the date and time of the message, located in the chatter." +#: ../../content/applications/general/email_communication/faq.rst:14 +msgid "While Odoo uses emails as a way to notify and communicate with users/customers, it is, by design, not a replacement for a dedicated email server. Therefore, it might not behave in the expected way when compared to a traditional email inbox." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:-1 -msgid "Red envelope icon displayed in chatter." +#: ../../content/applications/general/email_communication/faq.rst:18 +msgid "The main differences are the following:" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:23 -msgid "Unsent emails also appear in the Odoo email queue. In :ref:`developer mode `, the email queue can be accessed by going to :menuselection:`Settings app --> Technical menu --> Email --> Emails`. Unsent emails appear in turquoise, while sent emails appear in grey." +#: ../../content/applications/general/email_communication/faq.rst:20 +msgid "By default, once a notification or transactional email (quote, invoice, direct message to a contact) is sent out successfully, the email object is deleted. The email message's content lives in the chatter of the related record. It prevents cluttering the database with multiple copies of the content of the same email (when sent to multiple recipients) if the content is already present in the chatter." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:25 +msgid "There is no concept of (blind) carbon copy ([B]CC). Odoo uses the concept of *followers* added to a chatter to automatically decide when and how :ref:`a contact is notified ` or receives a copy of an email." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:28 +msgid "Incoming emails are handled by checking if the *TO* email address is a valid email address in the Odoo database or, in case of a reply email, if there is a reference in the email header that matches a message sent from the Odoo database. All other emails will be bounced and **not** temporarily parked in a spam or quarantine folder. In other words, any email unrelated to an Odoo database is lost." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:37 +msgid "Outgoing emails" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:42 +msgid "Changing the email address of the admin user account" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:44 +msgid "When an Odoo database is created, the main admin account is assigned a placeholder email address. It is recommended to **replace the admin email address** with a valid email address to prevent outgoing email issues." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:48 +msgid "To do so, on the admin account, click the user icon, click :guilabel:`My Profile` (or :guilabel:`Preferences`), and update the :guilabel:`Email` field found under the :guilabel:`Preferences` tab. Either use any other email address or use your Odoo subdomain (e.g., `company-name.odoo.com`) and `admin` for the local-part (e.g., `admin@company-name.odoo.com`)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:56 +msgid "Delivery failure" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:58 +msgid "When a message is sent, an :icon:`fa-envelope-o` :guilabel:`(envelope)` icon is displayed in the chatter. The icon turns red when delivery has failed for at least one recipient." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:-1 +msgid "Red envelope icon displayed in the chatter." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:64 +msgid "Left-click the envelope to display information about the delivery, and, if possible, the relevant :ref:`error messages `." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:-1 +msgid "Example of a sending failure." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:70 +msgid "Click :guilabel:`See Error Details` to get extra information for the fail reason, **if** Odoo was able to process the original error or bounce email." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:73 +msgid "Click :guilabel:`Send & close` to retry sending the email to all **toggled-on** (:icon:`fa-toggle-on`) recipients under the :guilabel:`Try Again` column. All **toggled-off** (:icon:`fa-toggle-off`) recipients will be ignored." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:77 +msgid "Click :guilabel:`Ignore all` to ignore all currently failing emails and turn the envelope icon from red to white." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:80 +msgid "Unsent emails also appear in the Odoo email queue. To access it, activate the :ref:`developer mode ` and go to :menuselection:`Settings --> Technical --> Email: Emails`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:-1 +msgid "Example of the technical email queue view." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:86 +msgid "Failed emails display the :guilabel:`Delivery Failed` status. Click :guilabel:`Retry` to put a failed email in the email queue again. It will then appear with the :guilabel:`Outgoing` status. The email will be sent again the next time the scheduled action for the email queue runs." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:90 +msgid "Optionally, queued emails can be sent immediately by clicking :guilabel:`Send Now`. Click :guilabel:`Cancel Email` to remove it from the email queue." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:94 +msgid "Sent emails are periodically cleaned from the queue. This is controlled by the *Auto-Vacuum* scheduled action that cleans redundant data on your Odoo database." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:100 msgid "Common error messages" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:33 +#: ../../content/applications/general/email_communication/faq.rst:105 msgid "Daily limit reached" msgstr "" #: ../../content/applications/general/email_communication/faq.rst:-1 -msgid "Warning in Odoo upon email limit reached." +msgid "Email limit reached warning." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:39 -msgid "Each email service provider has its own email sending limits. The limits may be daily, hourly, or sometimes, per minute. This is the same for Odoo, which limits a customer's sending to prevent Odoo's email servers from being blacklisted." +#: ../../content/applications/general/email_communication/faq.rst:110 +msgid "Odoo limits the number of emails that can be sent from an Odoo Online database. Most email service providers (e.g., Google, Yahoo, etc.) will blacklist Odoo's server IP if Odoo's email server is sending too many emails to addresses that do not exist or are no longer valid. It also applies to unsolicited spam emails sent through an Odoo database." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:43 -msgid "Here are the default limits for new databases:" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:45 -msgid "**200 emails per day** for Odoo Online and Odoo.sh databases with an active subscription." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:46 -msgid "**50 emails per day** for one-app free and trial databases." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:49 -msgid "In a one-app free database, if the *Email Marketing* app is installed, the email limit is **20 emails per day**." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:53 -msgid "In the case of migration, the daily limit might be reset to 50 emails per day." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:55 -msgid "If the daily limit is reached:" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:57 -msgid "Contact the Odoo support team, who may increase the daily limit, depending on the following factors:" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:60 -msgid "How many users are in the database?" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:61 -msgid "Which apps are installed?" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:62 -msgid "The bounce rate: the percentage of email addresses that did not receive emails because they were returned by a mail server on its way to the final recipient." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:65 -msgid "Use an external outgoing email server to be independent of Odoo's mail limit (refer to the corresponding :doc:`email documentation `)." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:68 -msgid "Wait until 11 PM (UTC) for the daily limit to reset, and retry sending the email. In :ref:`developer mode `, go to :menuselection:`Settings app --> Technical menu --> Email --> Emails`, then click the :guilabel:`Retry` button next to an unsent email." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:73 -msgid "The daily email limit is comprehensive to the database. By default, any internal message, notification, logged note, etc. counts as an email in the daily limit if it notifies someone via email. This can be mitigated by receiving :ref:`notifications in Odoo `, instead of emails." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:79 -msgid "SMTP error" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:81 -msgid "*Simple Mail Transport Protocol (SMTP)* error messages explain why an email was not transmitted successfully. :abbr:`SMTP (Simple Mail Transport Protocol)` is a protocol to describe the email structure, and transmits data from messages over the Internet. The error messages generated by email services are helpful tools to diagnose and troubleshoot email problems." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:87 -msgid "This is an example of a 554 SMTP permanent delivery error: `554: delivery error: Sorry, your message to ------@yahoo.com cannot be delivered. This mailbox is disabled (554.30). - mta4471.mail.bf1.yahoo.com --- Below this line is a copy of the message.`" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:91 -msgid "The debug menu can be used to investigate SMTP sending issues from a database. To access the menu, :ref:`developer mode ` **must** be activated. Once activated, navigate to the :menuselection:`Debug Menu` in the top-right of the menu bar (the :icon:`fa-bug` :guilabel:`(bug)` icon), and select :menuselection:`Debug Menu --> Manage Messages` from the resulting drop-down menu." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:96 -msgid "The :guilabel:`Manage Messages` menu opens a list of all the messages sent in a particular record. Within each message there is information on sending, including the type, and subtype, of the message." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:100 -msgid "Other information includes to whom the message was sent, and whether Odoo received a bounce-back message from an email server." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:-1 -msgid "Manage messages menu option on the debug menu." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:108 -msgid "A user must be on a view in Odoo that has a chatter in order for the :guilabel:`Manage Messages` menu option to appear." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:112 -msgid "No error populated" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:114 -msgid "Odoo is not always capable of providing information for the reason it failed. The different email providers implement a personalized policy of bounced emails, and it is not always possible for Odoo to interpret it correctly." +#: ../../content/applications/general/email_communication/faq.rst:115 +msgid "The default daily email limit varies between **5 and 200 emails**. The exact limit is depends on several factors (subject to change):" msgstr "" #: ../../content/applications/general/email_communication/faq.rst:118 -msgid "If this is a recurring problem with the same client, or the same domain, do not hesitate to contact `Odoo Support `_ for help in finding a reason." +msgid "Type of database subscription (one app free, trial, paying subscription)" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:119 +msgid "Apps installed (i.e., Email Marketing, Marketing Automation)" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:120 +msgid "If a database migration is ongoing" msgstr "" #: ../../content/applications/general/email_communication/faq.rst:122 -msgid "One of the most common reasons for an email failing to send with no error message is related to :ref:`SPF ` and/or :ref:`DKIM ` configuration. Also, check to make sure the `mail.bounce.alias` is defined in the *system parameters*. Access system parameters in :ref:`developer mode ` by navigating to :menuselection:`Settings app --> Technical menu --> Parameters --> System Parameters`." +msgid "If the daily limit is reached, you can:" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:132 -msgid "Email is sent late" +#: ../../content/applications/general/email_communication/faq.rst:124 +msgid "Contact :ref:`Odoo Support ` to increase your email quota. The following factors will be taken into account:" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:134 -msgid "Email campaigns send at a scheduled time, using a delay pre-programed in the database. Odoo uses a delayed task to send emails that are considered \"not urgent\" (newsletter formats, such as: mass mailing, marketing automation, and events). The system utility **cron** can be used to schedule programs to run automatically at predetermined intervals. Odoo uses that policy to avoid cluttering the mail servers and, instead, prioritizes individual communication. This **cron** is called :guilabel:`Mail: Email Queue Manager`, and can be accessed in :ref:`developer mode ` by going to :menuselection:`Settings app --> Technical menu --> Automation: Scheduled Actions`." +#: ../../content/applications/general/email_communication/faq.rst:127 +msgid "Numbers of users on the database" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:-1 -msgid "Email scheduled to be sent later." +#: ../../content/applications/general/email_communication/faq.rst:128 +msgid "Apps installed" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:129 +msgid "Bounce rate (the percentage of email addresses that did not receive emails because they were returned by an email server on their way to the final recipient)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:131 +msgid "Whether your :ref:`email aliases are correctly set up and use the appropriate custom domains `." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:135 +msgid "When using a custom domain, verify that :ref:`SPF `, :ref:`DKIM `, and :ref:`DMARC ` are correctly configured so that :ref:`Odoo's email servers are allowed to send emails on your custom domain's behalf `." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:140 +msgid ":doc:`Use an external outgoing email server <../email_communication>` to be independent of Odoo's email limit." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:142 +msgid "Wait until the next day, and retry sending the email. To do so, activate the :ref:`developer mode `, go to :menuselection:`Settings --> Technical --> Email: Emails`, and click :guilabel:`Retry` next to the unsent email." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:147 -msgid "What is a **cron**? A cron is an action that Odoo runs in the background to execute particular code to complete a task." +msgid "The daily email limit counts every email leaving your Odoo database, triggered either manually or automatically. By default, any internal message, notification, logged note, etc., counts as an email if it notifies someone via email. This can be mitigated by receiving :ref:`notifications in Odoo ` instead of by email." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:151 -msgid "By default, the *Mass Mailing cron* runs every 60 minutes. This can be changed to no less than 5 minutes. However, running the action every 5 minutes would bog down the Odoo database (stress the system), so this is not recommended. To edit the mass mailing cron, select the scheduled action :guilabel:`Mail: Email Queue Manager`, and proceed to make any necessary adjustments." +#: ../../content/applications/general/email_communication/faq.rst:155 +msgid "SMTP error" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:156 -msgid "Emails that are considered urgent (communication from one person to another, such as sales orders, invoices, purchase orders, etc.) are sent immediately." +#: ../../content/applications/general/email_communication/faq.rst:157 +msgid "`Simple Mail Transport Protocol (SMTP) `_ is a standard used to transmit emails between email servers and/or email clients." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:160 -msgid "Incoming emails" +#: ../../content/applications/general/email_communication/faq.rst:161 +msgid "If you use :ref:`an external STMP server to send emails `, a standard set of `SMTP error codes exists `_. While the code numbers are not specific to Odoo, the exact content of the error message might vary from email server to email server." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:162 -msgid "When there is an issue with incoming emails, there might not be an indication in Odoo. It is the sending email client, who tries to contact a database, that gets a bounce-back message (most of the time it is a :guilabel:`550: mailbox unavailable` error message)." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:167 -msgid "Email is not received" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:169 -msgid "The steps that should be taken depend on the Odoo platform where the database is hosted." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:171 -msgid "**Odoo.sh** users can find their live logs on the folder :file:`~/logs/`." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:173 -msgid "Logs are a stored collection of all the tasks completed in a database. They are a text-only representation, complete with timestamps of every action taken on the Odoo database. This can be helpful to track emails leaving the database. Failure to send can also be seen by logs that indicate that the message tried to send repeatedly. Logs will show every action to the email servers from the database." +#: ../../content/applications/general/email_communication/faq.rst:168 +msgid "A 550 SMTP permanent delivery error from sendgrid.com:" msgstr "" #: ../../content/applications/general/email_communication/faq.rst:179 -msgid "The folder :file:`~/logs/` (accessed by the command line or on the Odoo.sh dashboard) of an Odoo.sh database contains a list of files containing the logs of the database. The log files are created everyday at 5:00 AM (UTC)." +msgid "The error message indicates that you tried sending an email from an unverified email address. Investigating the outgoing email server configuration or the default *FROM* address of your database is a good starting point to troubleshoot the issue, and verify that you whitelisted the email address on the side of sendgrid.com." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:184 -msgid "The two most recent days (today and yesterday) are not compressed, while the older ones are, in order to save space. The naming of the files for today and yesterday are respectively: :file:`odoo.log` and :file:`odoo.log.1`." +msgid "Usually, inputting the error message content in a Google search can yield information on what the root cause might be and how to correct the issue." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:188 -msgid "For the following days, they are named with their dates, and then compressed. Use the command :command:`grep` and :command:`zgrep` (for the compressed ones) to search through the files." +#: ../../content/applications/general/email_communication/faq.rst:187 +msgid "If the issue cannot be resolved and keeps occurring, contact :ref:`Odoo Support `." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:192 -msgid "For more information on logs and how to access them via the Odoo.sh dashboard, see :ref:`this administration documentation `." +#: ../../content/applications/general/email_communication/faq.rst:193 +msgid "No error populated" msgstr "" #: ../../content/applications/general/email_communication/faq.rst:195 -msgid "For more information on accessing logs via the command line visit :ref:`this developer documentation `." +msgid "Odoo is not always capable of providing information on the reason a delivery failed. The different email providers implement their own policy on bounced emails, and it is not always possible for Odoo to interpret it correctly." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:198 -msgid "**Odoo Online** users won't have access to the logs. However `Odoo Support `_ can be contacted if there is a recurring issue with the same client or domain." +#: ../../content/applications/general/email_communication/faq.rst:199 +msgid "If there is a recurring problem with the same customer or the same domain, contact :ref:`Odoo Support `." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:203 -msgid "Get help from Odoo support" +msgid "One of the most common reasons for an email failing to be sent with no error message is related to the :ref:`SPF ` or :ref:`DKIM ` configuration. Also, verify that the implemented email notification setup is adapted to your business needs. See the :doc:`Communication in Odoo by email documentation <../email_communication>` for more information." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:205 -msgid "In order to get helped efficiently, please provide as much information as possible. Here is a list of what can be helpful when reaching out to the Odoo Support team about an issue:" +#: ../../content/applications/general/email_communication/faq.rst:212 +msgid "Execution time" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:208 -msgid "Send a copy of the email headers. The `.EML` file (or **headers**) of the email is the file format containing all the technical information required for an investigation. The documentation from the email provider might explain how to access the EML file/header files. Once the headers of the email are obtained, adding it into the Odoo Support ticket is the most efficient way for the Odoo Support team to investigate." -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:215 -msgid "`Gmail documentation on headers `_" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:216 -msgid "`Outlook documentation on headers `_" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:219 -msgid "Explain the exact flow that is being followed to normally receive those emails in Odoo. Here are examples of questions whose answers can be useful:" +#: ../../content/applications/general/email_communication/faq.rst:214 +msgid "The exact time of an email is sent is handled by a system utility *cron* (scheduled action) that can be used to schedule tasks to run automatically at predetermined intervals. Odoo uses this approach to send emails that are considered \"not urgent\" (i.e., newsletters formats such as mass mailing, marketing automation, and events). This avoids cluttering the mail servers and, instead, prioritizes individual communication." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:222 -msgid "Is this a notification message from a reply being received in Odoo?" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:223 -msgid "Is this a message being sent from the Odoo database?" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:224 -msgid "Is there an incoming email server being used, or is the email somehow being redirected?" -msgstr "" - -#: ../../content/applications/general/email_communication/faq.rst:225 -msgid "Is there an example of an email that has been correctly forwarded?" +msgid "A cron is an action that Odoo runs in the background to execute particular code to complete a task. Odoo also creates cron triggers in certain workflows that can trigger a scheduled action earlier than its scheduled date. Running a scheduled action manually or changing its frequency is generally not recommended, as it might create errors or break specific workflows." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:227 -msgid "Provide answers to the following questions:" +msgid "By default, for the normal email queue, the :guilabel:`Mail: Email Queue Manager` cron runs every 60 minutes. The lowest running interval for a cron is 5 minutes. Odoo recommends an interval of 15 minutes to ensure proper operation. If the interval is too short, not all emails may be processed, which may cause the cron to timeout." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:229 -msgid "Is it a generic issue, or is it specific to a use case? If specific to a use case, which one exactly?" +#: ../../content/applications/general/email_communication/faq.rst:232 +msgid "Emails that are considered urgent (from one person to another, such as sales orders, invoices, purchase orders, etc.) are sent immediately. They do not show up under :menuselection:`Settings --> Technical --> Email: Emails`, unless their delivery fails." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:231 -msgid "Is it working as expected? In case the email is sent using Odoo, the bounce email should reach the Odoo database, and display the :ref:`red envelope `." +#: ../../content/applications/general/email_communication/faq.rst:-1 +msgid "Example of sending information header when a mailing campaign is queued." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:235 -msgid "The bounce system parameter needs to be set in the technical settings in order for the database to correctly receive bounce messages. To access this setting, go to :menuselection:`Settings app --> Technical menu --> Parameters: System Parameters`. Then, select the parameter name :guilabel:`mail.bounce.alias` and set the value to `bounce` if it is not already set." +#: ../../content/applications/general/email_communication/faq.rst:239 +msgid "Email campaigns are sent as soon as possible (after clicking the :guilabel:`Send` button) or at a scheduled time (after clicking the :guilabel:`Schedule` button)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:242 +msgid "For the email marketing queue, the :guilabel:`Mail Marketing: Process queue` cron runs once a day, but will be **automatically triggered early** if a campaign is scheduled outside of this default frequency. If a mailing list contains a large number of recipients, triggering the cron manually multiple times is **not recommended**, as it will not accelerate the processing time and might create errors." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:249 +msgid "To edit crons, enable the :ref:`developer mode ` and go to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:253 +msgid "For more information about crons when using Odoo.sh, check out :doc:`Odoo.sh frequent technical questions <../../../administration/odoo_sh/advanced/frequent_technical_questions>`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:259 +msgid "Email Marketing campaigns stuck in the queue" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:261 +msgid "If multiple Email Marketing campaigns are put in the queue, they are processed in chronological order based on their creation date." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:265 +msgid "If there are three campaigns: Campaign_1 (created 1st of January), Campaign_2 (created 2nd of January), and Campaign_3 (created 3rd of January), they are put in the queue by clicking :guilabel:`Send` on all three of them." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:-1 +msgid "Example of three email marketing campaigns." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:272 +msgid "The cron will try to process Campaign_1, then Campaign_2, and finally Campaign_3. It will not start processing Campaign_2 until it finishes processing Campaign_1." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:275 +msgid "If an email campaign never leaves the queue, there might be an issue with the campaign at the top of the queue. To troubleshoot, we could remove Campaign_1 from the queue by clicking the :guilabel:`Cancel` button, and see if the two other campaigns are sent. Then we could try to fix Campaign_1 or contact :ref:`Odoo Support `." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:283 +msgid "Incoming emails" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:285 +msgid "When there is an issue with incoming emails, there might not be an indication, per se, in Odoo. It is the sending email client, who tries to contact a database, that will get a bounce message (most of the time a :guilabel:`550: mailbox unavailable` error message)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:292 +msgid "Email is not received" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:298 +msgid "Contact :ref:`Odoo Support ` if there is a recurring issue with the same client or domain." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:303 +msgid "You can use database logs to understand and fix issues. Logs are a stored collection of all the tasks completed in a database. They are a text-only representation, complete with timestamps of every action taken on the Odoo database. This can be helpful to track emails leaving the database. Sending failures can also be seen by logs when they indicate that the message tried to send repeatedly. Logs show every action to the email servers from the database." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:310 +msgid "Live logs are located in the :file:`~/logs/` folder (accessed by the command line or on the Odoo.sh dashboard). Log files are created everyday at 5:00 AM (UTC)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:314 +msgid "The two most recent files, for the current day and the previous one, are named :file:`odoo.log` and :file:`odoo.log.1`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:317 +msgid "Log files for older dates are named using their dates and are compressed. Use the commands :command:`grep` and :command:`zgrep` (for the compressed ones) to search through the files." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:321 +msgid "For more information on logs and how to access them via the Odoo.sh dashboard, refer to the :ref:`Odoo.sh logs documentation `." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:324 +msgid "For more information on accessing logs via the command line, refer to the :ref:`developer logging documentation `." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:330 +msgid "Information for Odoo Support" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:332 +msgid "Here is a list of helpful information to include when reaching out to `Odoo Support `_:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:335 +msgid "An export of the full email from the inbox. These are usually in `.eml` or `.msg` file formats containing technical information required for an investigation. The exact process to download the file depends on your third-party email provider." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:340 +msgid "`Gmail Help Center: Trace an email with its full header `_" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:342 +msgid "`Microsoft Support: View internet message headers in Outlook `_" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:344 +msgid "When using a local email software (e.g., Thunderbird, Apple Mail, Outlook, etc.) to synchronize emails, it is usually possible to export the local copies of emails as EML/MSG files. Refer to the documentation of the software used for more information." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:349 +msgid "If possible, the EML/MSG file should be based on the original email that was sent and is failing or is causing issues." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:352 +msgid "For **incoming emails**: if possible contact the original email sender and request an EML/MSG copy of the original email. Sending a copy of the original email (forwarded) only contains partial information related to the troubleshooting." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:356 +msgid "For **outgoing emails**: either provide the EML/MSG of the email or specify what record in the database is affected (e.g., sales order number, contact name, invoice number) and the date/time when the email was sent (e.g., email sent on the 10th January 2024 11:45 AM Central European Time)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:361 +msgid "An explanation of the exact flow that is being followed to normally receive those emails in Odoo. Try to answer the following questions:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:364 +msgid "Is this a notification message from a reply being received in Odoo?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:365 +msgid "Is this a message being sent from the Odoo database?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:366 +msgid "Is there an incoming email server being used, or is the email being redirected/forwarded through a custom email server or provider?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:368 +msgid "Is there an example of an email that has been correctly forwarded?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:369 +msgid "Have you changed any email-related settings recently? Did it stop working after those changes?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:371 +msgid "An answer to the following questions:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:373 +msgid "Is it a generic issue or is it specific to a use case? If specific to a use case, which one?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:374 +msgid "Is it working as expected? In case the email is sent using Odoo, the bounce email should reach the Odoo database and display the :ref:`red envelope `." msgstr "" #: ../../content/applications/general/email_communication/google_oauth.rst:3 @@ -2886,7 +3411,7 @@ msgid "`Mailjet: How can I configure my SMTP parameters? `." +msgid "Odoo :ref:`blocks port 25 ` on Odoo Online and Odoo.sh databases." msgstr "" #: ../../content/applications/general/email_communication/mailjet_api.rst:-1 @@ -3046,32 +3571,32 @@ msgstr "" msgid "Odoo outgoing email server settings." msgstr "" -#: ../../content/applications/general/email_communication/mailjet_api.rst:198 +#: ../../content/applications/general/email_communication/mailjet_api.rst:197 msgid "In order for the notifications feature to work using Mailjet, there are three settings that need to be set in Odoo." msgstr "" -#: ../../content/applications/general/email_communication/mailjet_api.rst:201 -msgid "The :guilabel:`From Filter` needs to be set on the server configuration. It is recommended to set it as a domain and not a full email address. It should match the domain in the two proceeding steps. More information can be referenced :ref:`here `." +#: ../../content/applications/general/email_communication/mailjet_api.rst:200 +msgid "The :guilabel:`From Filter` needs to be set on the server configuration. It is recommended to set it as a domain and not a full email address. It should match the domain in the two proceeding steps. For more information, check out the :ref:`FROM filtering documentation `." msgstr "" -#: ../../content/applications/general/email_communication/mailjet_api.rst:205 +#: ../../content/applications/general/email_communication/mailjet_api.rst:204 msgid "The :guilabel:`mail.default.from` system parameter must have the value `notifications\\@yourdomain.com`." msgstr "" -#: ../../content/applications/general/email_communication/mailjet_api.rst:207 +#: ../../content/applications/general/email_communication/mailjet_api.rst:206 msgid "The :guilabel:`mail.default.from_filter` system parameter must have the value `yourdomain.com`. Replace `yourdomain` with the custom domain for the Odoo database. If there isn't one, then use the :guilabel:`mail.catchall.domain` system parameter." msgstr "" -#: ../../content/applications/general/email_communication/mailjet_api.rst:211 -msgid "For more information see :ref:`Using a default email address `." +#: ../../content/applications/general/email_communication/mailjet_api.rst:210 +msgid "For more information, check out the :ref:`\"Using a unique email address\" documentation `." msgstr "" #: ../../content/applications/general/email_communication/mailjet_api.rst:213 -msgid "The :guilabel:`System Parameters` can be accessed by activating the :ref:`developer mode `." +msgid "The :guilabel:`System Parameters` can be accessed by activating the :ref:`developer-mode`." msgstr "" -#: ../../content/applications/general/email_communication/mailjet_api.rst:216 -msgid "Once the setup is complete, the Odoo database is ready to use the Mailjet email server for mass mailing or transactional emails!" +#: ../../content/applications/general/email_communication/mailjet_api.rst:215 +msgid "Once the setup is complete, the Odoo database is ready to use the Mailjet email server for mass mailing or transactional emails." msgstr "" #: ../../content/applications/general/integrations.rst:3 @@ -5816,7 +6341,7 @@ msgstr "" #: ../../content/applications/general/iot/devices/camera.rst:12 #: ../../content/applications/general/iot/devices/footswitch.rst:14 -#: ../../content/applications/general/iot/devices/printer.rst:14 +#: ../../content/applications/general/iot/devices/printer.rst:21 #: ../../content/applications/general/iot/devices/scale.rst:22 #: ../../content/applications/general/iot/devices/screen.rst:18 msgid "Connection" @@ -5897,7 +6422,6 @@ msgstr "" #: ../../content/applications/general/iot/devices/camera.rst:82 #: ../../content/applications/general/iot/devices/footswitch.rst:52 #: ../../content/applications/general/iot/devices/measurement_tool.rst:92 -#: ../../content/applications/general/iot/devices/printer.rst:98 msgid ":ref:`workcenter_iot`" msgstr "" @@ -6006,7 +6530,7 @@ msgid "Measurement tool input in the Odoo database." msgstr "" #: ../../content/applications/general/iot/devices/measurement_tool.rst:58 -#: ../../content/applications/general/iot/devices/printer.rst:62 +#: ../../content/applications/general/iot/devices/printer.rst:69 msgid "Quality control points can also be accessed by navigating to :menuselection:`IoT App --> Devices`, then select the device. There is a :guilabel:`Quality Control Points` tab, where they can be added with the device." msgstr "" @@ -6015,12 +6539,12 @@ msgid "On a quality check detail form, the :guilabel:`Type` of check can also be msgstr "" #: ../../content/applications/general/iot/devices/measurement_tool.rst:68 -#: ../../content/applications/general/iot/devices/printer.rst:73 +#: ../../content/applications/general/iot/devices/printer.rst:80 msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_control_points`" msgstr "" #: ../../content/applications/general/iot/devices/measurement_tool.rst:69 -#: ../../content/applications/general/iot/devices/printer.rst:74 +#: ../../content/applications/general/iot/devices/printer.rst:81 msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_alerts`" msgstr "" @@ -6052,7 +6576,15 @@ msgstr "" msgid "Printer installation can be done in a few easy steps. The printer can be used to print receipts, labels, orders, or even reports from the different Odoo apps. In addition, printer actions can be assigned as an *action on a trigger* during the manufacturing process, or added onto a quality control point or a quality check." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:16 +#: ../../content/applications/general/iot/devices/printer.rst:14 +msgid "The **only** way to connect a printer directly to an Odoo database is through the use of an |iot| box." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:17 +msgid "Without an |iot| box, printing can still occur, but it is managed through the printer itself, which is not the recommended process." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:23 msgid "The |iot| box supports printers connected through |usb|, network connection, or Bluetooth. `Supported printers `__ are detected automatically, and appear in the :guilabel:`Devices` list of the *IoT* app." msgstr "" @@ -6060,31 +6592,31 @@ msgstr "" msgid "The printer as it would appear in the IoT app devices list." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:25 +#: ../../content/applications/general/iot/devices/printer.rst:32 msgid "Printers can take up to two minutes to appear in the *IoT* app :guilabel:`Devices` list." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:28 +#: ../../content/applications/general/iot/devices/printer.rst:35 msgid "Link printer" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:31 +#: ../../content/applications/general/iot/devices/printer.rst:38 msgid "Link printer to work orders" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:33 +#: ../../content/applications/general/iot/devices/printer.rst:40 msgid "*Work Orders* can be linked to printers, via a quality control point, to print labels for manufactured products." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:36 +#: ../../content/applications/general/iot/devices/printer.rst:43 msgid "In the *Quality app*, a device can be set up on a quality control point. To do that, go to the :menuselection:`Quality app --> Quality Control --> Control Points`, and open the desired control point to which the printer will be linked." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:41 +#: ../../content/applications/general/iot/devices/printer.rst:48 msgid "A *Manufacturing Operation* and *Work Order Operation* need to be attached to a quality control point before the :guilabel:`Type` field allows for the :guilabel:`Print Label` option to be selected." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:45 +#: ../../content/applications/general/iot/devices/printer.rst:52 msgid "From here, edit the control point, by selecting the :guilabel:`Type` field, and selecting :guilabel:`Print Label` from the drop-down menu of options. Doing so reveals a field called :guilabel:`Device`, where the attached *device* can be selected. :guilabel:`Save` the changes, if required." msgstr "" @@ -6092,43 +6624,23 @@ msgstr "" msgid "This is the quality control point setup." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:54 +#: ../../content/applications/general/iot/devices/printer.rst:61 msgid "The printer can now be used with the selected quality control point. When the quality control point is reached during the manufacturing process, the database presents the option to print labels for a specific product." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:67 +#: ../../content/applications/general/iot/devices/printer.rst:74 msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Print Label`. To create :doc:`new quality checks <../../../inventory_and_mrp/quality/quality_management/quality_checks>`, navigate to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:77 -msgid "Link a printer to a work center" -msgstr "" - -#: ../../content/applications/general/iot/devices/printer.rst:79 -msgid "To link a printer to an action, it first needs to be configured on a work center. To do that, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. From here, select the desired work center in which the printer will be used. Next, add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`." -msgstr "" - -#: ../../content/applications/general/iot/devices/printer.rst:85 -msgid "Then, the printer can be linked to either of the following options in the :guilabel:`Actions` drop-down menu: :guilabel:`Print Labels`, :guilabel:`Print Operation`, or :guilabel:`Print Delivery Slip`. A key can also be added to trigger the action." -msgstr "" - -#: ../../content/applications/general/iot/devices/printer.rst:90 -msgid "The first listed trigger on the form will be chosen first. So, the order matters, and these triggers can be dragged into any order." -msgstr "" - -#: ../../content/applications/general/iot/devices/printer.rst:94 -msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the printer." -msgstr "" - -#: ../../content/applications/general/iot/devices/printer.rst:103 +#: ../../content/applications/general/iot/devices/printer.rst:86 msgid "Link printer to reports" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:105 +#: ../../content/applications/general/iot/devices/printer.rst:88 msgid "It is possible to link report types to a specific printer. In the *IoT* app, go to the :guilabel:`Devices` menu, and select the desired printer to be configured." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:108 +#: ../../content/applications/general/iot/devices/printer.rst:91 msgid "From here, go to the :guilabel:`Printer Reports` tab, and click :guilabel:`Add a line`. In the window that appears, check all the types of :guilabel:`Reports` that should be linked to this printer." msgstr "" @@ -6136,27 +6648,27 @@ msgstr "" msgid "The list of reports assigned to a printer in the IoT app." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:117 +#: ../../content/applications/general/iot/devices/printer.rst:100 msgid "Reports can also be configured in the *Technical* menu of the *Settings* app, while in :ref:`debug mode `. To do that, navigate to :menuselection:`Settings App --> Technical --> Actions: Reports`. From here, select the desired report from the list. Then, an :guilabel:`IoT Device` can be set on the report." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:122 +#: ../../content/applications/general/iot/devices/printer.rst:105 msgid "The first time a linked report is selected to print, a :guilabel:`Select Printers` pop-up window appears. Tick the checkbox next to the correct printer for the report, and click :guilabel:`Print`. At that point, the report is linked to the printer." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:127 +#: ../../content/applications/general/iot/devices/printer.rst:110 msgid "Clear device printer cache" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:129 +#: ../../content/applications/general/iot/devices/printer.rst:112 msgid "After a printer is linked to print a report, the setting is saved in a browser's cache. This means a user can have different devices saved in their cache for different reports, based on the device they use to access Odoo. It also means different users can have a report automatically printed from different printers, based on their preferences." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:134 +#: ../../content/applications/general/iot/devices/printer.rst:117 msgid "To unlink a report from a printer, navigate to :menuselection:`IoT app --> Clear Selected Devices`. This generates a list of reports that are linked to a printer on the current device. Click the :guilabel:`Unlink` button next to each report to remove the link." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:139 +#: ../../content/applications/general/iot/devices/printer.rst:122 msgid "This step **only** prevents the report from automatically printing to the listed printer from the current browser. The report is still :ref:`linked ` on the device, under the :guilabel:`Printer Reports` tab." msgstr "" @@ -6164,7 +6676,7 @@ msgstr "" msgid "A list of reports currently linked to a printer in the IoT app." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:148 +#: ../../content/applications/general/iot/devices/printer.rst:131 msgid ":doc:`POS Order Printing <../../../sales/point_of_sale/restaurant/kitchen_printing>`" msgstr "" @@ -6423,73 +6935,106 @@ msgid "Mitchell Admin has multiple companies enabled, but the current company is msgstr "" #: ../../content/applications/general/multi_company.rst:54 -msgid "When he creates a new sales team, the :guilabel:`Company` field automatically defaults to `My Company (Chicago)`." -msgstr "" - -#: ../../content/applications/general/multi_company.rst:58 -msgid "Sharing data" +msgid "When a new sales team is created, the :guilabel:`Company` field automatically defaults to `My Company (Chicago)`." msgstr "" #: ../../content/applications/general/multi_company.rst:60 +msgid "Share data" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:62 msgid "In a |mcd|, certain records are able to be utilized by all of the companies (or several, based on permissions)." msgstr "" -#: ../../content/applications/general/multi_company.rst:64 +#: ../../content/applications/general/multi_company.rst:66 msgid "Products" msgstr "" -#: ../../content/applications/general/multi_company.rst:66 +#: ../../content/applications/general/multi_company.rst:68 msgid "In an |mcd|, new products are created with the :ref:`Company field ` blank, by default. If the *Company* field remains blank, the product is shared across all companies." msgstr "" -#: ../../content/applications/general/multi_company.rst:70 +#: ../../content/applications/general/multi_company.rst:72 msgid "Contacts" msgstr "" -#: ../../content/applications/general/multi_company.rst:72 +#: ../../content/applications/general/multi_company.rst:74 msgid "Similar to products, contact records are shared across companies, by default. To limit access to a single company, click the :ref:`Company field ` on a contact form, and select a company to assign the contact to." msgstr "" -#: ../../content/applications/general/multi_company.rst:79 +#: ../../content/applications/general/multi_company.rst:81 msgid "The :ref:`Inter-Company Transactions ` feature allows for one company in the database to sell or purchase goods and services from another company within the same database. Counterpart documents for orders and invoices can be automatically generated and synchronized, depending on the configuration settings." msgstr "" -#: ../../content/applications/general/multi_company.rst:85 +#: ../../content/applications/general/multi_company.rst:87 msgid "To ensure inter-company transactions are handled appropriately, certain configurations, such as fiscal positions and localizations, need to be accurately assigned. See :ref:`Inter-Company Transactions ` for additional information." msgstr "" -#: ../../content/applications/general/multi_company.rst:90 +#: ../../content/applications/general/multi_company.rst:92 msgid "Use cases" msgstr "" -#: ../../content/applications/general/multi_company.rst:93 +#: ../../content/applications/general/multi_company.rst:95 msgid "Multinational companies" msgstr "" -#: ../../content/applications/general/multi_company.rst:95 +#: ../../content/applications/general/multi_company.rst:97 msgid "A multinational retail chain, which operates in the United States and Canada, needs to manage transactions in both USD and CAD currencies." msgstr "" -#: ../../content/applications/general/multi_company.rst:98 +#: ../../content/applications/general/multi_company.rst:100 msgid "Additionally, because both countries have different tax laws and regulations, it is in the best interest of the customer to utilize the multi-company feature." msgstr "" -#: ../../content/applications/general/multi_company.rst:101 +#: ../../content/applications/general/multi_company.rst:103 msgid "This allows for inter-company transactions they need to manage inventory moves across international borders, while making it simple to sell to customers in both countries in their own currency." msgstr "" -#: ../../content/applications/general/multi_company.rst:105 +#: ../../content/applications/general/multi_company.rst:107 msgid "Separate processes" msgstr "" -#: ../../content/applications/general/multi_company.rst:107 +#: ../../content/applications/general/multi_company.rst:109 msgid "A small furniture company is developing a new line of products that require a separate procurement, inventory, and manufacturing process. The new products are drastically different from the existing catalog. The company is considering utilizing the multi-company feature to treat this new line as a different entity." msgstr "" -#: ../../content/applications/general/multi_company.rst:112 +#: ../../content/applications/general/multi_company.rst:114 msgid "To keep their database from becoming overly complex, the furniture company does not need to add an entirely new company. Instead, they can take advantage of existing features, such as :doc:`analytic accounting <../finance/accounting/reporting/analytic_accounting>`, and multiple warehouses, to manage the new product line, without having to overly complicate transactions." msgstr "" +#: ../../content/applications/general/multi_company.rst:120 +msgid "Limitations" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:122 +msgid "In some instances, a |mcd| may *not* be the best option, due to potential limitations." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:125 +#: ../../content/applications/general/users/access_rights.rst:3 +msgid "Access rights" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:127 +msgid "A user's access rights are configured on a database level. If a user has access to more than one company in a |mcd|, their access rights are the same across every company." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:131 +msgid "Shared records" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:133 +msgid "Individual records are either :ref:`shared ` between all companies, or belong to a single company." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:137 +msgid "PDF Reports" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:139 +msgid "Some customizations, specifically for PDF reports, apply to all companies. It is not always possible to separate reports for individual companies." +msgstr "" + #: ../../content/applications/general/users.rst:5 #: ../../content/applications/general/users/access_rights.rst:32 msgid "Users" @@ -6899,10 +7444,6 @@ msgstr "" msgid "Click :guilabel:`Save` to commit any unsaved changes." msgstr "" -#: ../../content/applications/general/users/access_rights.rst:3 -msgid "Access rights" -msgstr "" - #: ../../content/applications/general/users/access_rights.rst:5 msgid "*Access rights* are permissions that determine the content and applications users can access and edit. In Odoo, these permissions can be set for individual users or for groups of users. Limiting permissions to only those who need them ensures that users do not modify or delete anything they should not have access to." msgstr "" diff --git a/locale/sources/hr.pot b/locale/sources/hr.pot index 9aca3d2d7..da8633d96 100644 --- a/locale/sources/hr.pot +++ b/locale/sources/hr.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 13:30+0000\n" +"POT-Creation-Date: 2024-08-21 11:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -41,7 +41,7 @@ msgstr "" #: ../../content/applications/hr/attendances.rst:59 #: ../../content/applications/hr/attendances/kiosks.rst:22 #: ../../content/applications/hr/frontdesk.rst:15 -#: ../../content/applications/hr/time_off.rst:31 +#: ../../content/applications/hr/time_off.rst:30 msgid "Configuration" msgstr "" @@ -53,7 +53,7 @@ msgstr "" #: ../../content/applications/hr/fleet.rst:13 #: ../../content/applications/hr/lunch.rst:15 #: ../../content/applications/hr/payroll.rst:15 -#: ../../content/applications/hr/recruitment.rst:35 +#: ../../content/applications/hr/recruitment.rst:34 msgid "Settings" msgstr "" @@ -716,7 +716,7 @@ msgstr "" #: ../../content/applications/hr/frontdesk.rst:210 #: ../../content/applications/hr/payroll/reporting.rst:3 #: ../../content/applications/hr/referrals.rst:261 -#: ../../content/applications/hr/time_off.rst:477 +#: ../../content/applications/hr/time_off.rst:494 msgid "Reporting" msgstr "" @@ -983,7 +983,7 @@ msgid "Employees are still able to log overtime hours even if the :guilabel:`Cou msgstr "" #: ../../content/applications/hr/attendances.rst:117 -#: ../../content/applications/hr/time_off.rst:433 +#: ../../content/applications/hr/time_off.rst:450 msgid "Overview" msgstr "" @@ -1746,8 +1746,9 @@ msgid "The departments dashboard view with all the department cards in a Kanban msgstr "" #: ../../content/applications/hr/employees/departments.rst:61 +#: ../../content/applications/hr/fleet/accidents.rst:142 #: ../../content/applications/hr/fleet/service.rst:329 -#: ../../content/applications/hr/recruitment.rst:175 +#: ../../content/applications/hr/recruitment.rst:174 msgid "Kanban view" msgstr "" @@ -1784,7 +1785,7 @@ msgid ":guilabel:`New Applicants`: the number of :ref:`new applicants `. This **only** appears if there are any expense reports waiting for approval." +msgid ":guilabel:`Expense Reports`: the number of employees in the department with :doc:`open expense reports to approve <../../finance/expenses/approve_expenses>`. This **only** appears if there are any expense reports waiting for approval." msgstr "" #: ../../content/applications/hr/employees/departments.rst:81 @@ -1985,7 +1986,7 @@ msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:110 #: ../../content/applications/hr/payroll.rst:874 -#: ../../content/applications/hr/recruitment.rst:419 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:38 msgid "Resumé" msgstr "" @@ -2536,6 +2537,334 @@ msgstr "" msgid ":doc:`fleet/service`" msgstr "" +#: ../../content/applications/hr/fleet.rst:88 +msgid ":doc:`fleet/accidents`" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:3 +msgid "Accidents" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:5 +msgid "When managing a fleet, accidents are inevitable. Tracking accidents is crucial for understanding vehicle maintenance costs and identifying safe drivers." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:8 +msgid "Odoo's *Fleet* app offers multiple ways to track accidents. Below are step-by-step instructions for only **one** method to monitor accidents and repair costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:12 +msgid "Structure" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:14 +msgid "For this example, to track accidents, two :ref:`service types ` are created: `Accident - Driver's Fault` and `Accident - No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:17 +msgid "This tracks various repairs associated with accidents, organized by who was at fault." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:19 +msgid "When an accident occurs, a service record is created. The specific repairs needed for the accident are logged in the *Description* of the service record, and the details about the accident are logged in the *Notes* section." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:23 +msgid "With this organizational structure, it is possible to view all accidents organized by fault, car, driver, or cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:27 +msgid "To manage accidents, the creation of service records is **required**." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:29 +msgid "Refer to the :doc:`service` documentation for detailed instructions on creating service records in Odoo's *Fleet* app." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:33 +msgid "Log accidents and repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:35 +msgid "To log an accident, and initiate the repair process, the first step is to :ref:`create a service record ` detailing the specific repairs needed." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:39 +msgid "Some accidents require multiple repairs with several different vendors. For these scenarios, a separate service record is needed for each vendor performing repairs. To keep records organized, it is recommended to keep the *Notes* field identical, as well as attaching the same important documentation, such as a police report." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:44 +msgid "Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the main :guilabel:`Services` dashboard. Click :guilabel:`New` in the top-left corner, and a blank service form loads." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:47 +#: ../../content/applications/hr/fleet/service.rst:380 +#: ../../content/applications/hr/frontdesk.rst:33 +#: ../../content/applications/hr/lunch/products.rst:12 +#: ../../content/applications/hr/payroll.rst:894 +#: ../../content/applications/hr/payroll/work_entries.rst:56 +#: ../../content/applications/hr/time_off.rst:221 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:49 +msgid ":guilabel:`Description`: enter the description of repairs needed to fully repair the vehicle, such as `Bodywork`, `Windshield Replacement`, or `Replacement Bumper, Tires, and Windows`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:51 +msgid ":guilabel:`Service Type`: for this example, select either `Accident - Driver's Fault` or `Accident - No Fault`, depending on the situation." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:54 +msgid "When entering either of these two :guilabel:`Service Types` for the first time, type in the new service type, then click :guilabel:`Create (new service type)`. A :guilabel:`Create Service Type` pop-up window appears, with the new service type populating the :guilabel:`Name` field. In the :guilabel:`Category` field, select :guilabel:`Service` from the drop-down menu, then click the :guilabel:`Save & Close` button." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:60 +msgid "Once an accident service type has been added to the database, it is available to select from the drop-down menu in the :guilabel:`Service Type` field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:62 +msgid ":guilabel:`Date`: using the calendar popover window, select the date the accident occurred. Navigate to the desired month using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then click the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:65 +msgid ":guilabel:`Cost`: leave this field blank, as the repair cost is not yet known." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:66 +msgid ":guilabel:`Vendor`: select the vendor performing the repairs using the drop-down menu. If the vendor has not already been entered in the system, type in the vendor name, and click either :guilabel:`Create` to add them, or :guilabel:`Create and edit...` to :ref:`add and configure the vendor `." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:70 +msgid ":guilabel:`Vehicle`: select the vehicle that was in the accident from the drop-down menu. When the vehicle is selected, the :guilabel:`Driver` field is populated, and the unit of measure for the :guilabel:`Odometer Value` field appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:73 +msgid ":guilabel:`Driver`: the current driver listed for the selected vehicle populates this field when the :guilabel:`Vehicle` is selected. If a different driver was operating the vehicle when the accident occurred, select the correct driver from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:76 +msgid ":guilabel:`Odometer Value`: enter the odometer reading when the accident occurred. The units of measure are either in kilometers (:guilabel:`km`) or miles (:guilabel:`mi`), depending on how the selected vehicle was configured." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:79 +msgid ":guilabel:`NOTES`: enter the specific details of the accident at the bottom of the service form, such as `Hit a deer` or `Rear-ended at an intersection while stopped`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:82 +msgid "Odoo provides the ability to attach any important paperwork, such as repair estimates and police reports, to the service record. To do so, click the :icon:`fa-paperclip` :guilabel:`(paperclip)` icon, located in the *chatter* of the form, and a file explorer pop-up window appears. Navigate to the desired record, and click :guilabel:`Open` to upload the file." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:88 +msgid "Once a file is added to a service record, a :guilabel:`Files` section appears in the *chatter*. To attach more records, click :icon:`fa-plus-square` :guilabel:`Attach files` to add more documents." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "Enter the information for an accident repair." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:97 +msgid "Service stages" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:99 +msgid "In Odoo's *Fleet* app, there are four default service stages:" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:103 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:18 +msgid "New" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:105 +msgid "The default stage when a service record is created. The service has been requested, but repairs have not begun. The :guilabel:`Cost` field for this stage remains zero." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:108 +msgid "Running" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:110 +msgid "The repair is in-process, but not yet complete. The estimate for repairs is listed in the :guilabel:`Cost` field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:113 +msgid "Completed" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:115 +msgid "All repairs listed on the service form have been completed. The :guilabel:`Cost` field is updated to reflect the final total cost charged for the repairs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:118 +msgid "Cancelled" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:120 +msgid "The service request has been cancelled." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:122 +msgid "During the repair process, change the service status to reflect the vehicle's current state in one of two ways: on the individual :ref:`service record `, or in the :ref:`Kanban service view `." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:129 +msgid "Service record" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:131 +msgid "Open the main *Services* dashboard, by navigating to :menuselection:`Fleet app --> Fleet --> Services`. Next, click on the individual service record to open the detailed service form. Click the desired stage in the top-right corner, above the service form, to change the status." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The stages as seen from the service form." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:144 +msgid "Open the main *Services* dashboard, by navigating to :menuselection:`Fleet app --> Fleet --> Services`. First, click the :icon:`oi-view-kanban` :guilabel:`Kanban` icon in the top-right of the screen, which organizes all repairs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:148 +msgid "Next, remove the default :guilabel:`Service Type` filter in the search bar. Upon doing so, all services appear in a Kanban view, organized by their respective :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:151 +msgid "Drag-and-drop the service record to the desired stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The Kanban view of stages, with a card being dragged and dropped to the Running stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:158 +msgid "Accident reporting" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:160 +msgid "One of the main reasons to track accidents using the method outlined in this document is the ability to view the total accident cost, determine the safest drivers, and calculate the actual total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:164 +msgid "The main :ref:`Services dashboard ` displays all the various accident information, while the :ref:`Reporting dashboard ` displays the total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:171 +msgid "Services dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:173 +msgid "Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the :guilabel:`Services` dashboard. All service records are displayed in a :icon:`oi-view-list` :guilabel:`(List)` view, grouped alphabetically, by :guilabel:`Service Type`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:177 +msgid "The two service types created for accident tracking appear in the list: :guilabel:`Accident - Driver Fault` and :guilabel:`Accident - No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:180 +msgid "Each grouping displays the number of records within each type, and lists the individual records beneath each grouping title." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:184 +msgid "In this example, there are six accidents where the driver was at fault, and four accidents that were not the driver's fault. This dashboard also displays the estimated total :guilabel:`Cost` for all the accidents in each group." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:188 +msgid "An estimated `$19,164.81` dollars are for driver-caused accident repairs, and an estimated `$2,548.21` dollars are for no-fault accidents." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:0 +msgid "Accident services, with the total costs highlighted." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:196 +msgid "The total :guilabel:`Cost` calculates **all** costs on the repair form, including estimated costs, as well as final repair costs. This number may not be accurate, if there are any repairs in the *Running* stage, and the final bill has not yet been calculated." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:203 +msgid "Reporting dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:205 +msgid "Navigate to :menuselection:`Fleet app --> Reporting --> Costs` to view the :menuselection:`Cost Analysis` report. This report displays a :icon:`fa-bar-chart` :guilabel:`(Bar Chart)` of all :guilabel:`Contract` and :guilabel:`Service` costs for the current year, organized by month (:guilabel:`Date : (year)`), by default. The :guilabel:`Sum`, represented by a gray dotted line, is the combined total of both the :guilabel:`Contract` and :guilabel:`Service` costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:211 +msgid "To view the total cost by vehicle, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon at the right of the search bar, revealing a drop-down menu. Click :guilabel:`Vehicle` in the :icon:`oi-group` :guilabel:`Group By` column, and the data is organized by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:215 +msgid "This displays the true cost for each vehicle, including both the contract cost (such as the monthly vehicle lease cost) and all service costs, including all accidents. Hover over a column to reveal a data popover window, which displays the vehicle name and the total cost. This allows for a more complete view of the vehicle cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The Cost Analysis report, displaying total costs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:224 +msgid "To view the individual cost details for both contract costs and repairs, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner of the :guilabel:`Cost Analysis` dashboard. This displays each vehicle on a separate line, and displays the :guilabel:`Contract` cost and :guilabel:`Service` cost, as well as the :guilabel:`Total` cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The Cost Analysis report, displaying the contract and service costs separately, as well as\n" +"the total." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:235 +msgid "The :icon:`oi-view-pivot` :guilabel:`(Pivot)` view organizes the data by vehicle, by default, therefore grouping the data by :guilabel:`Vehicle` is not required. If this filer is already activated, it does not affect the presented data." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:240 +msgid "Manage accident repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:242 +msgid "For companies with multiple employees, who manage a large fleet of vehicles, displaying only service records in the :guilabel:`New` and :guilabel:`Running` stages can be time-saving, if there are a large number of records in the *Services* dashboard." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:246 +msgid "Navigate to :menuselection:`Fleet app --> Fleet --> Services`, where all service requests are organized by :guilabel:`Service Type`. Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon at the right of the search bar, revealing a drop-down menu. Click :guilabel:`Add Custom Filter` in the :icon:`fa-filter` :guilabel:`Filters` column, and a :guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:252 +msgid "Three drop-down fields need to be configured on the pop-up window." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:254 +msgid "In the first field, scroll down, and select :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:256 +msgid "Leave the second field set to :guilabel:`=`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:258 +msgid "Select :guilabel:`Running` from the drop-down menu in the last field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:260 +msgid "Next, click the :icon:`fa-plus` :guilabel:`(plus)` icon to the right of the last field, and an identical rule appears beneath the current rule." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:263 +msgid "Then, change :guilabel:`Running` to :guilabel:`New` in the third field of the second rule, leaving the other fields as-is." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:266 +msgid "Click the :guilabel:`Add` button at the bottom to add the new custom filter." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The filter settings to be added to only display new and running services." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:272 +msgid "This slight modification only presents services in the :guilabel:`New` and :guilabel:`Running` stages. This is a helpful report for a company managing a high number of repairs at any given time." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:275 +msgid "To have this report appear as the default report when opening the :guilabel:`Services` dashboard, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon at the far-right of the search bar. Next, click :guilabel:`Save current search`, beneath the :icon:`fa-star` :guilabel:`Favorites` column, which reveals another drop-down column beneath it. Tick the checkbox beside :guilabel:`Default Filter`, then click :guilabel:`Save`. Then, this customized :guilabel:`Services` dashboard appears, by default, anytime the :guilabel:`Services` dashboard is accessed." +msgstr "" + #: ../../content/applications/hr/fleet/models.rst:3 msgid "Vehicle models" msgstr "" @@ -3798,15 +4127,6 @@ msgstr "" msgid "Depending on what kind of activity, if any, is scheduled, the activity icon may appear differently. For example, a :guilabel:`📞 (phone)` appears if a phone call is scheduled, or an :guilabel:`✉️ (envelope)` appears if an email is scheduled." msgstr "" -#: ../../content/applications/hr/fleet/service.rst:380 -#: ../../content/applications/hr/frontdesk.rst:33 -#: ../../content/applications/hr/lunch/products.rst:12 -#: ../../content/applications/hr/payroll.rst:894 -#: ../../content/applications/hr/payroll/work_entries.rst:56 -#: ../../content/applications/hr/time_off.rst:222 -msgid "Enter the following information on the form:" -msgstr "" - #: ../../content/applications/hr/fleet/service.rst:382 msgid ":guilabel:`Activity Type`: using the drop-down menu, select the activity being scheduled. The default options are :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, :guilabel:`To-Do`, and :guilabel:`Upload Document`." msgstr "" @@ -6129,7 +6449,7 @@ msgid "Salary structure details for Regular Pay, listing all the specific Salary msgstr "" #: ../../content/applications/hr/payroll.rst:556 -#: ../../content/applications/hr/time_off.rst:261 +#: ../../content/applications/hr/time_off.rst:256 msgid "Rules" msgstr "" @@ -6296,7 +6616,7 @@ msgid "A new salary attachment form filled in." msgstr "" #: ../../content/applications/hr/payroll.rst:688 -#: ../../content/applications/hr/recruitment.rst:168 +#: ../../content/applications/hr/recruitment.rst:167 msgid "Salary package configurator" msgstr "" @@ -7063,7 +7383,7 @@ msgid "The salary attachment form with everything filled in for Ronnie Hart's ch msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:343 -#: ../../content/applications/hr/time_off.rst:268 +#: ../../content/applications/hr/time_off.rst:263 msgid "Fill out the following fields on the form:" msgstr "" @@ -8381,111 +8701,111 @@ msgstr "" msgid ":ref:`Configure work entries `" msgstr "" -#: ../../content/applications/hr/recruitment.rst:6 +#: ../../content/applications/hr/recruitment.rst:5 msgid "Recruitment" msgstr "" -#: ../../content/applications/hr/recruitment.rst:8 +#: ../../content/applications/hr/recruitment.rst:7 msgid "Odoo keeps all job applicants organized with a pre-configured series of steps and stages that each applicant goes through. Each stage has a specific step(s) that should be performed. These range from scheduling a phone call, conducting an interview, or sending a job offer, for example. This process is referred to as the 'applicant flow.'" msgstr "" -#: ../../content/applications/hr/recruitment.rst:13 +#: ../../content/applications/hr/recruitment.rst:12 msgid "When an applicant applies for a job position, an *applicant card* is automatically created in Odoo's *Recruitment* app for that specific job position. As the applicant progresses through the recruitment pipeline, the recruitment team moves their card from one stage to the next." msgstr "" -#: ../../content/applications/hr/recruitment.rst:17 +#: ../../content/applications/hr/recruitment.rst:16 msgid ":ref:`Stages can be configured ` so that an email is automatically sent out using a set, pre-configured template as soon as an applicant's card enters a stage. These automated emails are defined on each stage in the applicant flow." msgstr "" -#: ../../content/applications/hr/recruitment.rst:21 +#: ../../content/applications/hr/recruitment.rst:20 msgid "The applicant flow explained in this document is the default flow in Odoo, and goes through the applicant flow when using the *Recruitment* application's default configuration. The applicant flow is able to be modified to suit the specific recruitment flow for any business." msgstr "" -#: ../../content/applications/hr/recruitment.rst:26 +#: ../../content/applications/hr/recruitment.rst:25 msgid "The applicant flow with all its stages are universal and applies to all job positions, unless specified. :ref:`A specific stage can be configured ` to be job-specific, meaning that specific stage is only visible for that specific job position. Otherwise, if a new stage is created, or an existing stage is modified, those changes are visible on all job positions." msgstr "" -#: ../../content/applications/hr/recruitment.rst:37 +#: ../../content/applications/hr/recruitment.rst:36 msgid "Before creating a job position in Odoo, configure the necessary settings for the *Recruitment* app. To view and edit the settings, navigate to :menuselection:`Recruitment app --> Configuration --> Settings`. After any changes are made, click the :guilabel:`Save` button in the top-left corner to save all the changes." msgstr "" -#: ../../content/applications/hr/recruitment.rst:43 +#: ../../content/applications/hr/recruitment.rst:42 msgid "Job posting" msgstr "" -#: ../../content/applications/hr/recruitment.rst:45 +#: ../../content/applications/hr/recruitment.rst:44 msgid "The :guilabel:`Job Posting` section of the *Recruitment* app settings has only one selection to make. If job positions are to be posted to the company's website, enable the :guilabel:`Online Posting` option." msgstr "" -#: ../../content/applications/hr/recruitment.rst:50 +#: ../../content/applications/hr/recruitment.rst:49 msgid "The :guilabel:`Online Posting` is only available if the *Website* application is also installed." msgstr "" -#: ../../content/applications/hr/recruitment.rst:53 +#: ../../content/applications/hr/recruitment.rst:52 msgid "Recruitment process" msgstr "" -#: ../../content/applications/hr/recruitment.rst:55 +#: ../../content/applications/hr/recruitment.rst:54 msgid "The :guilabel:`Recruitment process` section of the settings page specifies what the database can and cannot do during the recruitment process." msgstr "" -#: ../../content/applications/hr/recruitment.rst:59 +#: ../../content/applications/hr/recruitment.rst:58 msgid "Send interview survey" msgstr "" -#: ../../content/applications/hr/recruitment.rst:61 +#: ../../content/applications/hr/recruitment.rst:60 msgid "Odoo is capable of having a survey sent to an applicant to gather more information about them. Surveys can be thought of as exams, or questionnaires, and can be customized in various ways to provide the recruitment team with valuable insights into the applicant" msgstr "" -#: ../../content/applications/hr/recruitment.rst:65 +#: ../../content/applications/hr/recruitment.rst:64 msgid "Enable the :guilabel:`Send Interview Survey` option to send surveys to applicants. Once enabled, an :icon:`fa-arrow-right` :guilabel:`Interview Survey` internal link appears. Click the :icon:`fa-arrow-right` :guilabel:`Interview Survey` link to navigate to a list of all created surveys." msgstr "" -#: ../../content/applications/hr/recruitment.rst:70 +#: ../../content/applications/hr/recruitment.rst:69 msgid "This list includes all surveys that were created in the database, not just surveys used in the *Recruitment* app. If no surveys have been created, the surveys list displays a :guilabel:`No Survey Found` message, and presents options to create a survey from several pre-configured survey templates." msgstr "" -#: ../../content/applications/hr/recruitment.rst:76 +#: ../../content/applications/hr/recruitment.rst:75 msgid "For more detailed information about surveys, refer to the :doc:`survey essentials <../marketing/surveys/create>` documentation." msgstr "" -#: ../../content/applications/hr/recruitment.rst:80 +#: ../../content/applications/hr/recruitment.rst:79 msgid "Enabling the :guilabel:`Send Interview Survey` option will install the *Surveys* application once the settings are saved, if it is not installed already." msgstr "" -#: ../../content/applications/hr/recruitment.rst:84 +#: ../../content/applications/hr/recruitment.rst:83 msgid "Send SMS" msgstr "" -#: ../../content/applications/hr/recruitment.rst:86 +#: ../../content/applications/hr/recruitment.rst:85 msgid "It is possible to send text messages to applicants directly through the *Recruitment* app. To do so, enable the :guilabel:`Send SMS` option. This option requires credits to use, which can be obtained by clicking the :icon:`fa-arrow-right` :guilabel:`Buy credits` internal link that emerges when the feature is enabled." msgstr "" -#: ../../content/applications/hr/recruitment.rst:92 -msgid "For more information, refer to the :doc:`SMS pricing and FAQs <../marketing/sms_marketing/pricing/pricing_and_faq>` documentation." +#: ../../content/applications/hr/recruitment.rst:91 +msgid "For more information, refer to the :doc:`SMS pricing and FAQs <../marketing/sms_marketing/pricing_and_faq>` documentation." msgstr "" -#: ../../content/applications/hr/recruitment.rst:98 +#: ../../content/applications/hr/recruitment.rst:97 msgid "CV display" msgstr "" -#: ../../content/applications/hr/recruitment.rst:100 +#: ../../content/applications/hr/recruitment.rst:99 msgid "When applicants submit an application, one of the default required fields is a resumé, or :abbr:`CV (curriculum vitae)`. All resumés are stored in the *Documents* application, and are accessible on the applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:104 +#: ../../content/applications/hr/recruitment.rst:103 msgid "A resumé has the option to appear on the applicant's form, which can be viewed by clicking on the applicant's card. The resumé appears on the right-side of the screen. If this is not enabled, the resumé is accessed via a link in the chatter, where it needs to be clicked to expand and view it, or downloaded." msgstr "" -#: ../../content/applications/hr/recruitment.rst:109 +#: ../../content/applications/hr/recruitment.rst:108 msgid "Enable the :guilabel:`CV Display` option to show the resumé on the applicant's card by default, and in addition to the document link. When enabled, the resumé appears on the right side of the applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:114 +#: ../../content/applications/hr/recruitment.rst:113 msgid "For the resumé to appear on the right-side, the browser window must be in full-screen mode (where the browser spans the entire screen)." msgstr "" -#: ../../content/applications/hr/recruitment.rst:117 +#: ../../content/applications/hr/recruitment.rst:116 msgid "If the browser window is set to a size smaller than the entire width of the screen (not full-screen), then the resumé does not appear on the right-side. Instead, the resumé appears in the :guilabel:`Files` section of the chatter, below the applicant's card." msgstr "" @@ -8493,55 +8813,55 @@ msgstr "" msgid "The resumé on an applicant's card, appearing on the right side." msgstr "" -#: ../../content/applications/hr/recruitment.rst:128 +#: ../../content/applications/hr/recruitment.rst:127 msgid "CV digitization (OCR)" msgstr "" -#: ../../content/applications/hr/recruitment.rst:130 +#: ../../content/applications/hr/recruitment.rst:129 msgid "When an application is submitted using any of the available methods, such as an online application submission, emailing a resume to the job position alias, or creating an applicant record directly from the database, it is possible to have Odoo extract the applicant's name, phone number, and email address from the resumé and populate the applicant's form. To do so, enable the :guilabel:`CV Digitization (OCR)` option." msgstr "" -#: ../../content/applications/hr/recruitment.rst:136 +#: ../../content/applications/hr/recruitment.rst:135 msgid "When enabled, additional options appear. Click on the corresponding radio button to select one of the following options:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:139 +#: ../../content/applications/hr/recruitment.rst:138 msgid ":guilabel:`Do not digitize`: this option turns off resumé digitization." msgstr "" -#: ../../content/applications/hr/recruitment.rst:140 +#: ../../content/applications/hr/recruitment.rst:139 msgid ":guilabel:`Digitize on demand only`: this option only digitizes resumes when requested. A :guilabel:`Digitize document` buttons appears on applicant cards. When clicked, the resumé is scanned and the applicant's card is updated." msgstr "" -#: ../../content/applications/hr/recruitment.rst:143 +#: ../../content/applications/hr/recruitment.rst:142 msgid ":guilabel:`Digitize automatically`: this option automatically digitizes all resumés when they are submitted." msgstr "" -#: ../../content/applications/hr/recruitment.rst:146 +#: ../../content/applications/hr/recruitment.rst:145 msgid "Beneath these options are two additional links. Click the :icon:`fa-arrow-right` :guilabel:`Buy credits` button to purchase credits for CV digitization. Click the :icon:`fa-arrow-right` :guilabel:`View My Services` to view a list of all current services, and their remaining credit balances." msgstr "" -#: ../../content/applications/hr/recruitment.rst:151 +#: ../../content/applications/hr/recruitment.rst:150 msgid "For more information on document digitization and :abbr:`IAP's (in-app purchases)`, refer to the :doc:`In-app purchase (IAP) <../essentials/in_app_purchase>` documentation." msgstr "" -#: ../../content/applications/hr/recruitment.rst:155 +#: ../../content/applications/hr/recruitment.rst:154 msgid "The :guilabel:`Do not digitize` option for :guilabel:`CV digitization (OCR)` at first may seem like a redundancy. It seems to be the same as disabling the :guilabel:`CV digitization (OCR)` option." msgstr "" -#: ../../content/applications/hr/recruitment.rst:159 +#: ../../content/applications/hr/recruitment.rst:158 msgid "When the :guilabel:`CV digitization (OCR)` option is enabled, a module is installed so that resumés can be scanned. Disabling this option would uninstall the module." msgstr "" -#: ../../content/applications/hr/recruitment.rst:162 +#: ../../content/applications/hr/recruitment.rst:161 msgid "If at some point, there is a desire to temporarily stop digitizing resumés, the :guilabel:`Do not digitize` option is selected. The reason this option is available is so that the module is not uninstalled, allowing for digitization to be enabled in the future by selecting one of the other two options." msgstr "" -#: ../../content/applications/hr/recruitment.rst:170 +#: ../../content/applications/hr/recruitment.rst:169 msgid "When sending an offer to an applicant, an expiration date can be set on the offer. Enter the number of days an offer is valid for in the :guilabel:`days` field. After the set amount of days has passed, if the applicant has not accepted the offer, the offer is no longer available." msgstr "" -#: ../../content/applications/hr/recruitment.rst:177 +#: ../../content/applications/hr/recruitment.rst:176 msgid "To access the Kanban view for a job position, navigate to the main :menuselection:`Recruitment app` dashboard, which is the default view when opening the application. All job positions appear on the main dashboard. Click the :guilabel:`(#) New Applications` smart button on a job position card to navigate to the Kanban view for all the applicants for that particular job position." msgstr "" @@ -8549,35 +8869,35 @@ msgstr "" msgid "Main dashboard view of job position card, showing new applications button." msgstr "" -#: ../../content/applications/hr/recruitment.rst:186 +#: ../../content/applications/hr/recruitment.rst:185 msgid "Inside the job application, the Kanban stages appear, with all the applicants populated in their respective columns, indicating what stage they are currently in. There are six default stages in Odoo:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:190 +#: ../../content/applications/hr/recruitment.rst:189 msgid ":ref:`New `" msgstr "" -#: ../../content/applications/hr/recruitment.rst:191 +#: ../../content/applications/hr/recruitment.rst:190 msgid ":ref:`Initial Qualification `" msgstr "" -#: ../../content/applications/hr/recruitment.rst:192 +#: ../../content/applications/hr/recruitment.rst:191 msgid ":ref:`First Interview `" msgstr "" -#: ../../content/applications/hr/recruitment.rst:193 +#: ../../content/applications/hr/recruitment.rst:192 msgid ":ref:`Second Interview `" msgstr "" -#: ../../content/applications/hr/recruitment.rst:194 +#: ../../content/applications/hr/recruitment.rst:193 msgid ":doc:`Contract Proposal `" msgstr "" -#: ../../content/applications/hr/recruitment.rst:195 +#: ../../content/applications/hr/recruitment.rst:194 msgid ":ref:`Contract Signed `" msgstr "" -#: ../../content/applications/hr/recruitment.rst:197 +#: ../../content/applications/hr/recruitment.rst:196 msgid "The last column, :guilabel:`Contract Signed`, is folded by default. Folded columns appear gray, and the applicants in it are hidden from view. To expand the folded stage and view the applicant cards for that column, click anywhere on the thin gray column that says the stage name and the column expands, revealing the applicants." msgstr "" @@ -8585,23 +8905,23 @@ msgstr "" msgid "Expand a folded column by clicking on it in the Kanban view." msgstr "" -#: ../../content/applications/hr/recruitment.rst:206 +#: ../../content/applications/hr/recruitment.rst:205 msgid "Each stage has a color-coded bar beneath the stage name, providing status information for the applicant's in that specific stage. The status colors are:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:209 +#: ../../content/applications/hr/recruitment.rst:208 msgid ":guilabel:`Green`: the applicant is ready to move to the next stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:210 +#: ../../content/applications/hr/recruitment.rst:209 msgid ":guilabel:`Red`: the applicant is blocked from moving to the next stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:211 +#: ../../content/applications/hr/recruitment.rst:210 msgid ":guilabel:`Gray`: the applicant is still in progress in the current stage and is neither ready nor blocked from the next stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:214 +#: ../../content/applications/hr/recruitment.rst:213 msgid "The status for each card is set manually. To set the status, click on the small circle in the lower-left of the applicant card. A status pop-up window appears. Click on the desired status for the applicant. The status dot on the applicant card as well as the status bar updates." msgstr "" @@ -8609,23 +8929,23 @@ msgstr "" msgid "The applicant card statuses, and status bar." msgstr "" -#: ../../content/applications/hr/recruitment.rst:223 +#: ../../content/applications/hr/recruitment.rst:222 msgid "The names for the three status colors (`In Progress`, `Blocked`, and `Ready for Next Stage`) :ref:`can be modified `, if desired." msgstr "" -#: ../../content/applications/hr/recruitment.rst:229 +#: ../../content/applications/hr/recruitment.rst:228 msgid "Customize stages" msgstr "" -#: ../../content/applications/hr/recruitment.rst:231 +#: ../../content/applications/hr/recruitment.rst:230 msgid "Stages can be modified, added, or deleted to best meet the needs of the particular hiring steps of a business." msgstr "" -#: ../../content/applications/hr/recruitment.rst:235 +#: ../../content/applications/hr/recruitment.rst:234 msgid "New stage" msgstr "" -#: ../../content/applications/hr/recruitment.rst:237 +#: ../../content/applications/hr/recruitment.rst:236 msgid "To create a new stage, click on :icon:`fa-plus` :guilabel:`Stage` and a new column appears. Enter the title for the new stage in the :guilabel:`Stage title` field, then click :guilabel:`Add`. The new column appears, and another new stage is available to create. If no new stages are needed, click anywhere on the screen to exit the new stage creation." msgstr "" @@ -8633,12 +8953,12 @@ msgstr "" msgid "The plus sign to click to add a new column to the Kanban stages." msgstr "" -#: ../../content/applications/hr/recruitment.rst:249 +#: ../../content/applications/hr/recruitment.rst:248 #: ../../content/applications/hr/recruitment/schedule_interviews.rst:223 msgid "Modify stage" msgstr "" -#: ../../content/applications/hr/recruitment.rst:251 +#: ../../content/applications/hr/recruitment.rst:250 msgid "To modify the settings of a stage, hover over the name of the stage, and a :icon:`fa-cog` :guilabel:`(gear)` icon appears in the upper right hand side of the stage. Click on the :icon:`fa-cog` :guilabel:`(gear)` icon and a menu appears. Then click on the :guilabel:`Edit` option. An :guilabel:`Edit: (Stage)` form appears. Make any desired modifications to the form, then click :guilabel:`Save & Close` when done." msgstr "" @@ -8647,95 +8967,95 @@ msgid "The gear icon that appears when a column name is moused over, and the dro "displays when clicked." msgstr "" -#: ../../content/applications/hr/recruitment.rst:265 +#: ../../content/applications/hr/recruitment.rst:264 msgid "Edit stage form" msgstr "" -#: ../../content/applications/hr/recruitment.rst:267 +#: ../../content/applications/hr/recruitment.rst:266 msgid "The :guilabel:`Edit: (Stage)` form is where the stage's settings are configured. The only required field is the :guilabel:`Stage Name`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:270 +#: ../../content/applications/hr/recruitment.rst:269 msgid "The fields to be populated or modified are:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:272 +#: ../../content/applications/hr/recruitment.rst:271 msgid ":guilabel:`Stage Name`: type in a name for the stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:273 +#: ../../content/applications/hr/recruitment.rst:272 msgid ":guilabel:`Email Template`: select an email template to be used from the drop-down menu. If a template is selected, when the applicant card enters the stage, an email is automatically sent to the applicant using the selected template." msgstr "" -#: ../../content/applications/hr/recruitment.rst:276 +#: ../../content/applications/hr/recruitment.rst:275 msgid ":guilabel:`Folded in Kanban`: check the box to have the stage appear folded (hidden) at all times in the default view." msgstr "" -#: ../../content/applications/hr/recruitment.rst:278 +#: ../../content/applications/hr/recruitment.rst:277 msgid ":guilabel:`Hired Stage`: check the box if this stage indicates that the applicant is hired. When an applicant's card enters this stage, the card displays a :guilabel:`Hired` banner in the upper right corner. If this box is checked, this stage is used to determine the hire date of an applicant." msgstr "" -#: ../../content/applications/hr/recruitment.rst:282 +#: ../../content/applications/hr/recruitment.rst:281 msgid ":guilabel:`Job Specific`: if the stage only applies to specific job positions, select the job positions from the drop-down menu. Multiple job positions can be selected." msgstr "" -#: ../../content/applications/hr/recruitment.rst:284 +#: ../../content/applications/hr/recruitment.rst:283 msgid ":guilabel:`Show in Referrals`: check the box if this stage should be seen in the *Referrals* application, and allow the referrer to accrue points when a referral of theirs reaches this stage. If this is active, a :guilabel:`Points` field appears. Enter the amount of referral points the employee receives when an applicant enters this stage. The *Referrals* app must be installed in order to use this option." msgstr "" -#: ../../content/applications/hr/recruitment.rst:289 +#: ../../content/applications/hr/recruitment.rst:288 msgid ":guilabel:`Tooltips` section: there are three pre-configured status labels (colored circles) for each applicant's card, indicating its status. These colors are displayed at the top of each stage to reflect the statuses of the applicants in the stage. The *names* for the label can be modified, but the label itself (the color) cannot. The default names and labels are: :guilabel:`In Progress` (gray), :guilabel:`Blocked` (red), and :guilabel:`Ready for Next Stage` (green)." msgstr "" -#: ../../content/applications/hr/recruitment.rst:294 +#: ../../content/applications/hr/recruitment.rst:293 msgid ":guilabel:`Requirements`: enter any internal notes for this stage explaining any requirements of the stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:298 +#: ../../content/applications/hr/recruitment.rst:297 msgid "Delete stage" msgstr "" -#: ../../content/applications/hr/recruitment.rst:300 +#: ../../content/applications/hr/recruitment.rst:299 msgid "If a stage is no longer needed, the stage can be deleted. To delete a stage, hover over the name of the stage, and a :icon:`fa-cog` :guilabel:`(gear)` icon appears. First, click on the :icon:`fa-cog` :guilabel:`(gear)` icon to reveal a drop-down menu, then click :guilabel:`Delete`. A :guilabel:`Confirmation` pop-up warning appears, asking :guilabel:`Are you sure you want to delete this column?` Click :guilabel:`Delete` to delete the column." msgstr "" -#: ../../content/applications/hr/recruitment.rst:307 +#: ../../content/applications/hr/recruitment.rst:306 msgid "If there are applicants currently in the stage being deleted, an error pops up when attempting to delete the stage. The records currently in the stage to need to be either deleted, archived, or moved to a different stage before the stage can be deleted." msgstr "" -#: ../../content/applications/hr/recruitment.rst:312 +#: ../../content/applications/hr/recruitment.rst:311 msgid "Email templates" msgstr "" -#: ../../content/applications/hr/recruitment.rst:314 +#: ../../content/applications/hr/recruitment.rst:313 msgid "To communicate with the applicant, Odoo has several pre-configured email templates that can be used. The pre-configured email templates and when to use them are as follows:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:317 +#: ../../content/applications/hr/recruitment.rst:316 msgid ":guilabel:`Recruitment: Applicant Acknowledgement`: this template is used to let the applicant know that their application was received. This email is automatically sent out once the applicant is in the :guilabel:`New` stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:320 +#: ../../content/applications/hr/recruitment.rst:319 msgid ":guilabel:`Recruitment: Interest`: this template is used to let the applicant know that their application caught the recruiter's attention, and they have been shortlisted for either a phone call or an interview." msgstr "" -#: ../../content/applications/hr/recruitment.rst:323 +#: ../../content/applications/hr/recruitment.rst:322 msgid ":guilabel:`Recruitment: Schedule Interview`: this template is used to let the applicant know that they have passed the :guilabel:`Initial Qualification` stage and they will be contacted to set up an interview with the recruiter. This email is automatically sent out once the applicant is in the :guilabel:`Initial Qualification` stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:327 +#: ../../content/applications/hr/recruitment.rst:326 msgid ":guilabel:`Recruitment: Not interested anymore`: this template is used when an applicant communicates that they are no longer interested in the position, and thanks them for their time and consideration." msgstr "" -#: ../../content/applications/hr/recruitment.rst:330 +#: ../../content/applications/hr/recruitment.rst:329 msgid ":guilabel:`Recruitment: Refuse`: this template is used when an applicant is no longer being considered for the position." msgstr "" -#: ../../content/applications/hr/recruitment.rst:334 +#: ../../content/applications/hr/recruitment.rst:333 msgid "Email templates can be created, modified, and deleted to suit the needs of a business. For more information on email templates, refer to the :doc:`../general/companies/email_template` document." msgstr "" -#: ../../content/applications/hr/recruitment.rst:337 +#: ../../content/applications/hr/recruitment.rst:336 msgid "To manually send an email, click :guilabel:`Send message` in the chatter. A text box appears, as well as the applicant's email address." msgstr "" @@ -8743,202 +9063,62 @@ msgstr "" msgid "Send an email from the chatter." msgstr "" -#: ../../content/applications/hr/recruitment.rst:344 +#: ../../content/applications/hr/recruitment.rst:343 msgid "Click the :icon:`fa-expand` :guilabel:`(expand)` full composer icon in the bottom right corner of the :guilabel:`Send Message` tab in the chatter. A :guilabel:`Compose Email` pop-up window loads, with the :guilabel:`Recipients` and :guilabel:`Subject` pre-populated. The applicant's email address is entered in the :guilabel:`Recipients` line, and the :guilabel:`Subject` is `(Job Position)`. The email body is empty by default." msgstr "" -#: ../../content/applications/hr/recruitment.rst:350 +#: ../../content/applications/hr/recruitment.rst:349 msgid "To use a pre-configured email template, click the field next to :guilabel:`Load template` in the bottom section of the window. Select the email template to use from the drop-down menu." msgstr "" -#: ../../content/applications/hr/recruitment.rst:353 +#: ../../content/applications/hr/recruitment.rst:352 msgid "Pre-configured email templates may contain dynamic placeholders so unique information can be populated in the email for a more personalized message to the applicant. There are several pre-configured email templates to choose from. Depending on the template selected, the email subject and/or body may change." msgstr "" -#: ../../content/applications/hr/recruitment.rst:359 +#: ../../content/applications/hr/recruitment.rst:358 msgid "Only the email templates that are configured for the model load. There are other email templates pre-configured in Odoo, but if they are not configured for the recruitment application, they do not appear in the list of available templates." msgstr "" -#: ../../content/applications/hr/recruitment.rst:363 +#: ../../content/applications/hr/recruitment.rst:362 msgid "If any attachments are to be added, click the :guilabel:`Attachments` button in the lower left corner. Navigate to the file to be attached, then click :guilabel:`Open` to attach it. To delete an attachment, click the :icon:`fa-close` :guilabel:`(delete)` icon to the right of the attachment." msgstr "" -#: ../../content/applications/hr/recruitment.rst:367 +#: ../../content/applications/hr/recruitment.rst:366 msgid "If any changes need to be made to the email, edit the body of the email. If the edits should be saved to be used in the future, the email can be saved as a new template. Click the :guilabel:`Save Template` button in the bottom. To send the email, click :guilabel:`Send` and the email is sent to the applicant. The email then appears in the chatter." msgstr "" -#: ../../content/applications/hr/recruitment.rst:373 -msgid "Stage flow" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:375 -msgid "In order to move an applicant's card from one stage to another, the applicant's card can either be dragged and dropped in the Kanban view to the desired stage, or the stage can be modified on the applicant's card." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:379 -msgid "To change the stage on the applicant's card, click on the applicant's card in the Kanban view to go to a detailed view of the card. The current stage for the card is highlighted at the top, above the card." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:383 -msgid "Click the desired stage for the card, and the stage changes. A log note indicating the stage change appears in the chatter. Navigate back to the Kanban view by clicking on :guilabel:`Applications` in the breadcrumb menu in the top-left, and the applicant's card now appears in the new stage." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:-1 -msgid "Change the stage of an applicant by clicking on the desired stage at the top of the\n" -"applicant's card." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:395 -msgid "New" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:398 -msgid "The following information is based on Odoo's default recruitment pipeline flow. Be advised that if modifications are made to create a customized recruitment pipeline flow, it will vary from the following information." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:402 -msgid "All applicants appear in the :guilabel:`New` stage, whether submitted online or if the applicant is manually entered by a recruiter." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:405 -msgid "When the applicant's card is created, Odoo automatically populates the :guilabel:`Subject/Application`, the applicant's :guilabel:`Name`, :guilabel:`Email`, :guilabel:`Mobile` number, and :guilabel:`LinkedIn Profile` on the applicant's card. This information is required when applying for a job position, by default." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:411 -msgid "If the website application form is modified, different fields may be populated based on what information is requested on the website." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:414 -msgid "If the applicant entered any information in the :guilabel:`Short Introduction` section of the online application, it will populate in the :guilabel:`Application Summary` tab at the bottom of the applicant's card." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:421 -msgid "If a resumé was attached to the online application, the resumé would appear in the attachments section of the chatter, and is also stored in the *Documents* application. To find the recruitment documents stored in the *Documents* application, navigate to the main :menuselection:`Documents` dashboard, and click the folder labeled :guilabel:`Recruitment` on the left-hand side. All recruitment documents are stored within that folder." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:427 -msgid "If the :ref:`CV Display ` option was enabled in the :ref:`Settings ` menu, the resumé appears on the applicant's card, on the right-hand side." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:431 -msgid "Send interview" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:433 -msgid "At any point in the hiring process, an *interview* can be sent to the applicant to obtain more information. These interviews are custom-made, and can be formatted in a variety of ways." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:436 -msgid "The *Surveys* application is used to send these *interviews*, therefore the *Surveys* application must be installed to send an interview to an applicant." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:439 -msgid "Odoo uses the term *interview*, but these can be thought of as questionnaires, surveys, tests, certifications, etc. Custom interviews can be formatted to suit each individual job positions needs. For more information on creating and editing interview forms, refer to the :doc:`../hr/recruitment/new_job` documentation." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:445 -msgid "A job position for a computer programmer could have an interview in the form of a programming quiz to determine the skill level of the applicant. A job position for a restaurant server could have a questionnaire inquiring about the applicant's availability, if the desired applicant needs to be available on weekend evenings." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:450 -msgid "To send an interview to an applicant, click on an applicant's card to navigate to a detailed view of the applicant's card. At the top-left of the applicant's card, click the :guilabel:`Send Interview` button." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:454 -msgid "If the applicant's card has an email address on file, a :guilabel:`Send an interview` pop-up window appears, with all the information populated." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:458 -msgid "In order to send an email to an applicant, there must be an email address on the applicant's card. If an email address is not entered on the applicant's card, when :guilabel:`Send Interview` is clicked, an :guilabel:`Edit:(Applicant)` pop-up window appears on top of the :guilabel:`Send an interview` pop-up window. Enter the email address in the :guilabel:`email` field, then click :guilabel:`Save & Close`. Once the applicant's information is saved, the :guilabel:`Edit: (Applicant)` closes and the :guilabel:`Send an interview` pop-up window remains." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:465 -msgid "Email templates use dynamic placeholders to personalize the email to the applicant and the job position. Add any additional recipients for the survey if more people should receive the email. If an email is in the database as a contact, add that contact in the :guilabel:`Recipients` field. If an email should be sent to someone who is not in the database as a contact, and they should **not** be added as a contact, add their email in the :guilabel:`Additional emails` field." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:471 -msgid "If any attachments need to be added, click the :guilabel:`Attachments` button and a file explorer window appears. Navigate to the desired file, then click :guilabel:`Open` to attach it to the email. The attachment loads, and is listed above the :guilabel:`Attachments` button." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:475 -msgid "If the emailed interview must be completed by a specific date, select a date for the :guilabel:`Answer deadline` in the lower-right area of the pop-up window. Click on the line next to :guilabel:`Answer deadline`, and a calendar selector appears. Use the :icon:`fa-chevron-left` :guilabel:`(left)` and :icon:`fa-chevron-right` :guilabel:`(right)` arrows on either side of the month to navigate to the desired month, then click on the :guilabel:`day` to select the date." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:481 -msgid "The :guilabel:`Mail Template` field is pre-populated based on the configuration for the interview. A different template can be chosen from the drop-down menu if desired. If a new template is selected, the new email template loads in the email body." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:485 -msgid "To send the email with the interview link to the applicant, click :guilabel:`Send` at the bottom of the email pop-up." -msgstr "" - #: ../../content/applications/hr/recruitment.rst:-1 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:-1 msgid "Send a custom survey, also referred to as an interview form, to an applicant using a\n" "pre-configured template." msgstr "" -#: ../../content/applications/hr/recruitment.rst:496 -msgid "Initial qualification" +#: ../../content/applications/hr/recruitment.rst:377 +msgid ":doc:`recruitment/new_job`" msgstr "" -#: ../../content/applications/hr/recruitment.rst:498 -msgid "If an applicant seems to be a good potential candidate, they are moved to the :guilabel:`Initial Qualification` stage. This could be for a number of reasons, such as they have the relevant experience, education, or certifications the position requires." +#: ../../content/applications/hr/recruitment.rst:378 +msgid ":doc:`recruitment/add-new-applicants`" msgstr "" -#: ../../content/applications/hr/recruitment.rst:502 -msgid "This stage is to quickly sort candidates that have potential, and those that do not meet the requirements. No automatic actions, such as emails, are set for this stage. This stage simply informs the recruitment team to potentially set up a phone call or an interview with the candidate." +#: ../../content/applications/hr/recruitment.rst:379 +msgid ":doc:`recruitment/schedule_interviews`" msgstr "" -#: ../../content/applications/hr/recruitment.rst:509 -msgid "First interview" +#: ../../content/applications/hr/recruitment.rst:380 +msgid ":doc:`recruitment/offer_job_positions`" msgstr "" -#: ../../content/applications/hr/recruitment.rst:511 -msgid "After an applicant has passed the :guilabel:`Initial Qualification` stage, they can be moved to the :guilabel:`First Interview` stage in the job position Kanban view. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`First Interview` stage, or click on the :guilabel:`First Interview` stage button at the top of the individual applicant's card." +#: ../../content/applications/hr/recruitment.rst:381 +msgid ":doc:`recruitment/refuse_applicant`" msgstr "" -#: ../../content/applications/hr/recruitment.rst:-1 -msgid "An applicant's card moves from one stage to another by using the click and drag method." +#: ../../content/applications/hr/recruitment.rst:382 +msgid ":doc:`recruitment/source_analysis`" msgstr "" -#: ../../content/applications/hr/recruitment.rst:521 -msgid "The :guilabel:`First Interview` stage can be modified, so when the applicant's card moves to the :guilabel:`First Interview` stage, an email is automatically sent to the applicant, stating an interview is requested, and :ref:`requests the applicant to schedule their interview `." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:526 -msgid ":ref:`Edit ` the :guilabel:`First Interview` stage, and select the :guilabel:`Recruitment: Schedule Interview` for the :guilabel:`Email Template` field, to automate this action." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:533 -msgid "Second interview" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:535 -msgid "After an applicant has passed the :guilabel:`First Interview` stage, they can be moved to the :guilabel:`Second Interview` stage. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`Second Interview` stage, or click on the :guilabel:`Second Interview` stage button at the top of the individual applicant's card." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:540 -msgid "When the applicant's card moves to the :guilabel:`Second Interview` stage, there are no automatic activities or emails configured. The recruiter can now :doc:`schedule a second interview ` with the applicant, following the same process as the first interview." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:546 -msgid "recruitment/new_job" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:547 -msgid "recruitment/add-new-applicants" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:548 -msgid "recruitment/schedule_interviews" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:549 -msgid "recruitment/offer_job_positions" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:550 -msgid "recruitment/refuse_applicant" +#: ../../content/applications/hr/recruitment.rst:383 +msgid ":doc:`recruitment/recruitment_analysis`" msgstr "" #: ../../content/applications/hr/recruitment/add-new-applicants.rst:3 @@ -9474,26 +9654,355 @@ msgstr "" msgid "Hired banner in the top right corner of applicant card." msgstr "" -#: ../../content/applications/hr/recruitment/offer_job_positions.rst:150 +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:152 msgid "Create employee" msgstr "" -#: ../../content/applications/hr/recruitment/offer_job_positions.rst:152 +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:154 msgid "Once the applicant has been hired, the next step is to create their employee record. Click the :guilabel:`Create Employee` button in the top-left corner of the hired applicant's form." msgstr "" -#: ../../content/applications/hr/recruitment/offer_job_positions.rst:155 +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:157 msgid "An employee form appears, with information from the applicant's card, and the employee contract." msgstr "" -#: ../../content/applications/hr/recruitment/offer_job_positions.rst:157 +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:159 msgid "Fill out the rest of the employee form. For detailed information on the fields, refer to the :doc:`../employees/new_employee` documentation." msgstr "" -#: ../../content/applications/hr/recruitment/offer_job_positions.rst:160 +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:162 msgid "Once completed, the employee record is saved in the *Employees* app." msgstr "" +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:3 +msgid "Recruitment flow" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:5 +msgid "When a prospective employee applies for a job in Odoo, there is a preconfigured process from the :ref:`initial inquiry ` to the :ref:`creating of a new employee ` once hired. The following outlines the default recruitment process for Odoo's *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:11 +msgid "The following is based on Odoo's default recruitment pipeline. Be advised that if :ref:`modifications are made ` to the pipeline, the process differs." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:20 +msgid "At the start of the process, all applicants appear in the :guilabel:`New` stage on the :guilabel:`Applications` page, whether submitted online or if the applicant is :doc:`manually entered by a recruiter `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:24 +msgid "When the applicant's card is created, Odoo automatically populates the :guilabel:`Subject/Application`, the :guilabel:`Applicant's Name`, :guilabel:`Email`, and :guilabel:`Mobile` number, on the applicant's card. This information is required when applying for a job position, by default." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:30 +msgid "If the website application form is modified, different fields may be populated, based on what information is requested on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:33 +msgid "If the applicant entered any information in the *Short Introduction* section of the online application, it populates the :guilabel:`Application Summary` tab at the bottom of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:40 +msgid "If a resumé was attached to the online application, it appears in the :guilabel:`Files` section of the chatter, and is also stored in the *Documents* application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:43 +msgid "To find the recruitment documents, navigate to the main :menuselection:`Documents app` dashboard, and click the :guilabel:`Recruitment` folder on the left-hand side. All recruitment documents are stored within that folder." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:47 +msgid "If the :ref:`CV Display ` option was enabled in the :ref:`Settings ` of the *Recruitment* app, the resumé appears on the applicant's card, on the right-hand side." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:52 +msgid "Depending on the browser zoom level, or size of the browser screen, the resumé may appear below the main applicant card information as a PDF link." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:56 +msgid "Send interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:58 +msgid "At any point in the hiring process, an interview can be sent to the applicant to obtain more information. These interviews are custom-made, and can be formatted in a variety of ways." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:61 +msgid "The *Surveys* application is **required** to send interviews to an applicant, so it **must** be installed." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:64 +msgid "Odoo uses the term *interview*, but these can be thought of as questionnaires, surveys, tests, certifications, etc. Custom interviews can be formatted to suit each individual job position's needs. For more information on creating and editing interviews, refer to the :doc:`../../hr/recruitment/new_job` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:70 +msgid "A job position for a computer programmer could have an interview in the form of a programming quiz to determine the skill level of the applicant. A job position for a restaurant server could have a questionnaire inquiring about the applicant's availability, if the desired applicant needs to be available on weekend evenings." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:75 +msgid "To send an interview to an applicant, first click the applicant's card from the :guilabel:`Applications` page, to view the detailed applicant information. At the top-left of the applicant's card, click the :guilabel:`Send Interview` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:79 +msgid "If the applicant's card has an email address on file, a :guilabel:`Send an interview` pop-up window appears, with the :guilabel:`Recipients`, :guilabel:`Subject`, and email body populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:83 +msgid "To send an email to an applicant, there **must** be an :guilabel:`Email` address on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:86 +msgid "If an email address is not entered on the applicant's card, when the :guilabel:`Send Interview` button is clicked, an :guilabel:`Edit: (Applicant's Name)` pop-up window appears, *on top of* the :guilabel:`Send an interview` pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:90 +msgid "Enter the email address in the :guilabel:`Email` field, then click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:92 +msgid "Once the applicant's information is saved, the :guilabel:`Edit: (Applicant's Name)` pop-up window closes, and the :guilabel:`Send an interview` pop-up window remains." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:95 +msgid "Sometimes, preconfigured email templates in Odoo use dynamic placeholders, which are automatically filled with specific data when the email is sent. For example, if a placeholder for the applicant's name is used, it is replaced with the actual name of the applicant in the email. For more detailed information on email templates, refer to the :doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:101 +msgid "Add the email addresses of any additional recipients for the survey in the :guilabel:`Additional emails` field, if more people should receive the email. If an email address is in the database as a contact, add that contact in the :guilabel:`Recipients` field. If an email should be sent to someone who is not in the database as a contact, and they should **not** be added as a contact, add their email address in the :guilabel:`Additional emails` field." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:107 +msgid "If any attachments need to be added, click the :icon:`fa-paperclip` :guilabel:`Attachments` button, and a file explorer window appears. Navigate to the desired file, and click :guilabel:`Open` to attach it to the email. The attachment loads, and is listed above the :icon:`fa-paperclip` :guilabel:`Attachments` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:112 +msgid "If the emailed interview must be completed by a specific date, enter that date in the :guilabel:`Answer deadline` field, located in the lower-right area of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:115 +msgid "To do so, click the empty field next to :guilabel:`Answer deadline`, and a calendar selector appears. Use the :icon:`fa-chevron-left` :guilabel:`(left)` and :icon:`fa-chevron-right` :guilabel:`(right)` arrows, on either side of the month, to navigate to the desired month. Then, click on the desired day to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:120 +msgid "The :guilabel:`Mail Template` field is pre-populated, based on the configuration for the interview. A different template can be chosen from the drop-down menu, if desired. If a new template is selected, the new email template loads in the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:124 +msgid "To send the email with the interview link to the applicant, click :guilabel:`Send` at the bottom of the email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:135 +msgid "Initial qualification" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:137 +msgid "If an applicant seems to be a good potential candidate, they are moved to the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:140 +msgid "This stage exists to quickly sort candidates that have potential, from those that do not meet the requirements. No automatic actions, such as emails, are set for this stage. This stage simply informs the recruitment team to potentially set up a phone call or an interview with the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:145 +msgid "In order to move an applicant's card from one stage to another, the applicant's card can either be dragged and dropped in the Kanban view of the :guilabel:`Applications` page to the desired stage, or the stage can be modified on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:149 +msgid "To change the stage on the applicant's card, first click the desired applicant's card from the :guilabel:`Applications` page. The current stage for the card is highlighted at the top on a status bar, above the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:153 +msgid "Click the desired stage for the card, and the stage changes. A log note indicating the stage change appears in the chatter, as well." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:0 +msgid "Change the stage of an applicant by clicking on the desired stage at the top of the\n" +"applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:164 +msgid "First interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:166 +msgid "After an applicant has passed the :guilabel:`Initial Qualification` stage, they can be manually moved to the :guilabel:`First Interview` stage on the :guilabel:`Applications` page, while in Kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:170 +msgid "To move the applicant to the next stage, drag-and-drop the applicant's card to the :guilabel:`First Interview` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:173 +msgid "Alternatively, open the desired applicant's card from the :guilabel:`Applications` page, and click the :guilabel:`First Interview` stage on the status bar at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:-1 +msgid "An applicant's card moves from one stage to another by using the click and drag method." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:182 +msgid "The :guilabel:`First Interview` stage can be modified, so when the applicant's card moves to the :guilabel:`First Interview` stage, an email can be automatically sent to the applicant, stating an interview is requested. In this pre-configured email template, a link to the recruiting team's calendar appears, allowing the applicant to schedule their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:187 +msgid ":ref:`Edit ` the :guilabel:`First Interview` stage, and select the :guilabel:`Recruitment: Schedule Interview` option in the :guilabel:`Email Template` field, to automate this action." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:194 +msgid "Second interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:196 +msgid "After an applicant has passed the :guilabel:`First Interview` stage, they can be moved to the :guilabel:`Second Interview` stage. To move the applicant to the next stage, drag-and-drop the applicant's card to the :guilabel:`Second Interview` stage from the Kanban view of the :guilabel:`Applications` page, or click on the :guilabel:`Second Interview` stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:202 +msgid "When the applicant's card moves to the :guilabel:`Second Interview` stage, there are no automatic activities or emails configured for this stage, by default. The recruiter can now :ref:`schedule a second interview ` with the applicant, following the same process as the first interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:210 +msgid "Contract Proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:212 +msgid "After the applicant has completed the various interview processes, the next step is to :doc:`send the job offer `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:215 +msgid "Once the offer has been sent, drag-and-drop the applicant's card to the :guilabel:`Contract Proposal` stage from the Kanban view of the :guilabel:`Applications` page, or click on the :guilabel:`Contract Proposal` stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:220 +msgid "Contract Signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:222 +msgid "Once the contract has been signed, and the applicant has been hired, the applicant's card moves to the :guilabel:`Contract Signed` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:225 +msgid "Drag-and-drop the applicant's card to the :guilabel:`Contract Signed` stage from the Kanban view of the :guilabel:`Applications` page, or click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon at the top of the individual applicant's card, then click :guilabel:`Contract Signed` on the status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:231 +msgid "Refuse applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:233 +msgid "At any point in the recruitment process, a candidate can be :doc:`refused `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:3 +msgid "Recruitment analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:5 +msgid "The *Recruitment Analysis* report allows recruiting departments to see which job positions have the most applicants, which have the most referrals, and how long it takes for applicants to move through the pipeline." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:9 +msgid "Knowing how many applicants each specific job position has, along with statistics about how many are hired and refused, can provide valuable insights. This information can assist the recruiting team to pivot their strategies to acquire the most desirable candidates." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:14 +msgid "Recruitment analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:16 +msgid "Start by navigating to :menuselection:`Recruitment app --> Reporting --> Recruitment Analysis`. This presents a line chart of all applicants for the last year." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:19 +msgid "Three separate color-coded metrics are presented: :guilabel:`In Progress`, :guilabel:`Hired`, and :guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:22 +msgid "Hover the cursor over a month of the chart, and a pop-up window appears, displaying the specific numbers for that month." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:-1 +msgid "The default Recruitment Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:30 +msgid "Pivot table view" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:32 +msgid "For a more detailed view of the information in the :guilabel:`Recruitment Analysis` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner. This displays all the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:36 +msgid "In this view, the job positions are displayed in the rows, and the columns display the total numbers of applicants, including how many of those applicants were hired or refused. The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:40 +msgid "In this example, there are 17 total applicants. Out of that, three have been hired, and four refused. The :guilabel:`Experienced Developer` position has eight total applicants, two of which were hired, and two were refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:-1 +msgid "The detailed pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:49 +msgid "Use case: applicants with referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:51 +msgid "To get a better understanding of how effective the company's :doc:`referral program <../referrals>` is, the :guilabel:`Recruitment Analysis` report can be modified to show how many applicants were referred by current employees." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:55 +msgid "From the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view of the :guilabel:`Recruitment Analysis` report, first click the :guilabel:`Measures` button to reveal a drop-down menu of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:58 +msgid "Click both :guilabel:`Has Referrer` and :guilabel:`Count`, to activate those two measures. Then, click :guilabel:`# Applicant`, :guilabel:`# Hired`, and :guilabel:`# Refused` to deactivate those default measures." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:62 +msgid "Now, the column displays the number of applicants that came from a referral in the :guilabel:`Has Referrer` column, and the total number of applicants in the :guilabel:`Count` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:-1 +msgid "The detailed pivot table view displaying the number of referrals and the total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:69 +msgid "In this example, the :guilabel:`Experienced Developer` job position has the most applicants from referrals. Out of the eight applicants, six have applied through a referral from a current employee. Meanwhile, the :guilabel:`Marketing and Community Manager` job position has the least amount of referrals out of the total applicants, only one out of six." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:75 +msgid "Hired through referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:77 +msgid "It is possible to modify this report even further to see how many referred applicants end up being hired." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:80 +msgid "To view this data, click on a :icon:`fa-plus-square` :guilabel:`[job position]` row, which reveals a drop-down menu. Then, click :guilabel:`State` to show the various states applicants are currently in." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:85 +msgid "Only states that have applicants in them are shown for each job position. If a state does **not** have any applicants, it does not appear in the list." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:88 +msgid "To expand the other rows, and display the various states, click on the :icon:`fa-plus-square` :guilabel:`[job position]` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:-1 +msgid "The detailed pivot table view displaying applicants hired through referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:95 +msgid "In this example, the :guilabel:`Experienced Developer` job position is the most successful in terms of referrals. Both of the hired employees came from internal referrals. Meanwhile, there have been no hired employees for the :guilabel:`Chief Executive Officer` position, and the only hired employee for the :guilabel:`Marketing and Community Manager` was not referred by an employee." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:100 +msgid "In this scenario, it is possible to determine that the current software developers are providing the most referrals, with the highest success rate." +msgstr "" + #: ../../content/applications/hr/recruitment/refuse_applicant.rst:3 msgid "Refuse applicants" msgstr "" @@ -10027,6 +10536,102 @@ msgstr "" msgid "The applicant is also able to cancel or reschedule the interview, if necessary, with the :guilabel:`Cancel/Reschedule` button." msgstr "" +#: ../../content/applications/hr/recruitment/source_analysis.rst:3 +msgid "Source analysis reporting" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:5 +msgid "Reporting is a critical tool used by recruiting departments to gain insights into the entire recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:8 +msgid "Determining where applicants come from can provide information about which sources have the best results. This information is determined by the *Source Analysis* report. With this data, recruitment teams can better pivot their recruiting strategies to gain better applicants, in both quantity and quality." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:14 +msgid "Open report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:16 +msgid "To access the *Source Analysis* report, navigate to :menuselection:`Recruitment app --> Reporting --> Source Analysis`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:19 +msgid "This presents the data for the :icon:`fa-filter` :guilabel:`Last 365 Days Applicant`, in a default :icon:`fa-area-chart` :guilabel:`(Graph)` view, showing the amount of applicants by :guilabel:`Source`, and further separated by stage (:guilabel:`In Progress` and :guilabel:`Hired`)" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:23 +msgid "Hover the cursor over any column to view the specific numbers fort that column." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The default bar chart of the source analysis information." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:29 +msgid "To view more details, view the :guilabel:`Source Analysis` report in a pivot table. To do so, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner. The data is presented in a pivot table, with rows populated by job positions, and columns populated stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:34 +msgid "Source effectiveness report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:36 +msgid "To identify which sources (e.g., job boards, social media, employee referrals, company website) produce the most hires, the pivot table view of the :guilabel:`Source Analysis` report can be configured to display further details." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:40 +msgid "To expand this chart to show what specific sources the applicants came from, click the :icon:`fa-plus-square` :guilabel:`Total` box above the columns, to reveal a drop-down menu, and click :guilabel:`Source`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:44 +msgid "Each column is then grouped by the source, such as: :guilabel:`Search engine`, :guilabel:`Facebook`, :guilabel:`Newsletter`, etc. Each source displays a separate count for :guilabel:`Applicant`, :guilabel:`Hired`, and :guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:48 +msgid "This information, as presented, makes it difficult to view the specific numbers for each source. Click the :icon:`fa-exchange` :guilabel:`(Flip axis)` icon, to swap the information. After that, the rows represent the source, and the columns represent the job positions, further divided by stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The axes flipped in the source analysis report, in pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:56 +msgid "In this view, the total number of applicants, hired employees, and refused applicants, are displayed for each source, as well as for each stage by job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:60 +msgid "Medium" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:62 +msgid "Viewing the medium for the applicants can be beneficial to see which specific medium is more successful." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:65 +msgid "*Mediums* are the specific methods the applicant used to discover and then apply for job positions, such as organic search, paid search, social media ad, email, etc." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:68 +msgid "To further group the results by medium, click into one of the :icon:`fa-plus-square` :guilabel:`[Source]` rows. Click :guilabel:`Medium` in the resulting drop-down menu. The row presents the specific mediums, relevant to that specific source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:72 +msgid "Once :guilabel:`Medium` is selected for one source, clicking into another row automatically reveals the specific metrics for the mediums for that source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The sources rows, expanded to also show the medium for each source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:80 +msgid "The only mediums that appear for a source, are mediums that have been set on an applicant's form. If a medium has **not** been set for any applicants, the medium does not appear in the drop-down rows beneath the source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:84 +msgid "For example, if no applicants applied with the medium *Google Adwords*, that medium does **not** appear beneath the *Search engine* source row." +msgstr "" + #: ../../content/applications/hr/referrals.rst:5 msgid "Referrals" msgstr "" @@ -10761,7 +11366,7 @@ msgid "Time Off" msgstr "" #: ../../content/applications/hr/time_off.rst:7 -msgid "Odoo's *Time Off* application serves as a centralized hub for all time-off-related information. This application manages requests, balances, allocations, approvals, and reports." +msgid "Odoo's **Time Off** application serves as a centralized hub for all time-off-related information. This application manages requests, balances, allocations, approvals, and reports." msgstr "" #: ../../content/applications/hr/time_off.rst:10 @@ -10773,174 +11378,174 @@ msgid "Detailed :ref:`reports ` can be run to see how much t msgstr "" #: ../../content/applications/hr/time_off.rst:20 -msgid "Be advised, only users with specific access rights can see all aspects of the *Time Off* application." +msgid "Be advised, only users with specific access rights can see all aspects of the **Time Off** app." msgstr "" -#: ../../content/applications/hr/time_off.rst:23 -msgid "All users can access the :guilabel:`My Time Off` and :guilabel:`Overview` sections of the *Time Off* application. All other sections require specific access rights." +#: ../../content/applications/hr/time_off.rst:22 +msgid "All users can access the *My Time Off* and *Overview* sections of the **Time Off** app. All other sections require specific access rights." msgstr "" -#: ../../content/applications/hr/time_off.rst:26 -msgid "To better understand how access rights affect the *Time Off* application, refer to the :doc:`employees/new_employee` document, specifically the section about configuring the work information tab." +#: ../../content/applications/hr/time_off.rst:25 +msgid "To better understand how access rights affect the **Time Off** app, refer to the :doc:`employees/new_employee` document, specifically the section about configuring the work information tab." msgstr "" -#: ../../content/applications/hr/time_off.rst:33 +#: ../../content/applications/hr/time_off.rst:32 msgid "In order to allocate time off to employees, and for employees to request and use their time off, the various time off types must be configured first, then allocated to employees (if allocation is required)." msgstr "" -#: ../../content/applications/hr/time_off.rst:40 +#: ../../content/applications/hr/time_off.rst:39 msgid "Time off types" msgstr "" -#: ../../content/applications/hr/time_off.rst:42 +#: ../../content/applications/hr/time_off.rst:41 msgid "To view the currently configured time off types, navigate to :menuselection:`Time Off app --> Configuration --> Time Off Types`. The time off types are presented in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:45 -msgid "The *Time Off* application comes with four pre-configured time off types: :guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, and :guilabel:`Compensatory Days`. These can be modified to suit business needs or used as-is." +#: ../../content/applications/hr/time_off.rst:44 +msgid "The **Time Off** app comes with four preconfigured time off types: :guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, and :guilabel:`Compensatory Days`. These can be modified to suit business needs, or used as-is." msgstr "" -#: ../../content/applications/hr/time_off.rst:50 +#: ../../content/applications/hr/time_off.rst:49 msgid "Create time off type" msgstr "" -#: ../../content/applications/hr/time_off.rst:52 +#: ../../content/applications/hr/time_off.rst:51 msgid "To create a new time off type, navigate to :menuselection:`Time Off app --> Configuration --> Time Off Types`. From here, click the :guilabel:`New` button to reveal a blank time off type form." msgstr "" -#: ../../content/applications/hr/time_off.rst:55 +#: ../../content/applications/hr/time_off.rst:54 msgid "Enter the name for the particular type of time off in the blank line at the top of the form, such as `Sick Time` or `Vacation`. Then, enter the following information on the form." msgstr "" -#: ../../content/applications/hr/time_off.rst:59 +#: ../../content/applications/hr/time_off.rst:58 msgid "The only **required** fields on the time off type form are the name of the :guilabel:`Time Off Type`, the :guilabel:`Take Time Off In`, and the :guilabel:`Kind of Time Off`. In addition, the :guilabel:`Time Off Requests` and :guilabel:`Allocation Requests` sections **must** be configured." msgstr "" -#: ../../content/applications/hr/time_off.rst:65 +#: ../../content/applications/hr/time_off.rst:64 msgid "Time Off Requests section" msgstr "" -#: ../../content/applications/hr/time_off.rst:67 +#: ../../content/applications/hr/time_off.rst:66 msgid ":guilabel:`Approval`: select what specific kind of approval is required for the time off type. The options are:" msgstr "" -#: ../../content/applications/hr/time_off.rst:70 -msgid ":guilabel:`No Validation`: no approvals are required when requesting this type of time off. The time off request is automatically approved." +#: ../../content/applications/hr/time_off.rst:69 +msgid ":guilabel:`No Validation`: No approvals are required when requesting this type of time off. The time off request is automatically approved." msgstr "" -#: ../../content/applications/hr/time_off.rst:72 -msgid ":guilabel:`By Time Off Officer`: only the specified :ref:`Time Off Officer `, set on this form in the :guilabel:`Notified Time Off Officer` field, is required to approve the time off request. This option is selected by default." +#: ../../content/applications/hr/time_off.rst:71 +msgid ":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer `, set on this form in the :guilabel:`Notified Time Off Officer` field, is required to approve the time off request. This option is selected, by default." msgstr "" -#: ../../content/applications/hr/time_off.rst:75 -msgid ":guilabel:`By Employee's Approver`: only the employee's specified approver for time off, which is set on the *Work Information* tab on the :ref:`employee's form `, is required to approve the time off request." +#: ../../content/applications/hr/time_off.rst:74 +msgid ":guilabel:`By Employee's Approver`: Only the employee's specified approver for time off, which is set on the *Work Information* tab on the :ref:`employee's form `, is required to approve the time off request." msgstr "" -#: ../../content/applications/hr/time_off.rst:78 -msgid ":guilabel:`By Employee's Approver and Time Off Officer`: both the employee's :ref:`specified time off approver` and the :ref:`Time Off Officer ` are required to approve the time off request." +#: ../../content/applications/hr/time_off.rst:77 +msgid ":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's :ref:`specified time off approver` and the :ref:`Time Off Officer ` are required to approve the time off request." msgstr "" -#: ../../content/applications/hr/time_off.rst:83 +#: ../../content/applications/hr/time_off.rst:82 msgid "Allocation Requests section" msgstr "" -#: ../../content/applications/hr/time_off.rst:85 -msgid ":guilabel:`Requires allocation`: if the time off must be allocated to employees, select :guilabel:`Yes`. If the time off can be requested without time off being previously allocated, select :guilabel:`No Limit`. If :guilabel:`No Limit` is selected, the following options do not appear on the form." +#: ../../content/applications/hr/time_off.rst:84 +msgid ":guilabel:`Requires allocation`: If the time off must be allocated to employees, select :guilabel:`Yes`. If the time off can be requested without time off being previously allocated, select :guilabel:`No Limit`. If :guilabel:`No Limit` is selected, the following options do not appear on the form." msgstr "" -#: ../../content/applications/hr/time_off.rst:89 -msgid ":guilabel:`Employee Requests`: select :guilabel:`Extra Days Requests Allowed` if the employee is able to request more time off than was allocated." +#: ../../content/applications/hr/time_off.rst:88 +msgid ":guilabel:`Employee Requests`: Select :guilabel:`Extra Days Requests Allowed` if the employee is able to request more time off than was allocated." msgstr "" -#: ../../content/applications/hr/time_off.rst:92 +#: ../../content/applications/hr/time_off.rst:91 msgid "If employees should **not** be able to make requests for more time off than what was allocated, select the :guilabel:`Not Allowed` option." msgstr "" -#: ../../content/applications/hr/time_off.rst:96 +#: ../../content/applications/hr/time_off.rst:95 msgid "Ten days are allocated to the employee for this particular type of time off, and the :guilabel:`Extra Days Requests Allowed` option is enabled. The employee wants to take a vacation for twelve days. They may submit a request for two additional days, since the :guilabel:`Extra Days Requests Allowed` option is enabled." msgstr "" -#: ../../content/applications/hr/time_off.rst:102 +#: ../../content/applications/hr/time_off.rst:101 msgid "It is important to note that requesting additional time off does **not** guarantee that time off is granted." msgstr "" -#: ../../content/applications/hr/time_off.rst:105 -msgid ":guilabel:`Approval`: select the type of approvals required for the allocation of this particular time off type." +#: ../../content/applications/hr/time_off.rst:104 +msgid ":guilabel:`Approval`: Select the type of approvals required for the allocation of this particular time off type." msgstr "" -#: ../../content/applications/hr/time_off.rst:108 +#: ../../content/applications/hr/time_off.rst:107 msgid ":guilabel:`Approved by Time Off Officer` indicates the :ref:`Time Off Officer ` set on this form must approve the allocation." msgstr "" -#: ../../content/applications/hr/time_off.rst:110 +#: ../../content/applications/hr/time_off.rst:109 msgid ":guilabel:`No validation needed` indicates that no approvals are required." msgstr "" -#: ../../content/applications/hr/time_off.rst:113 +#: ../../content/applications/hr/time_off.rst:112 msgid "Configuration section" msgstr "" -#: ../../content/applications/hr/time_off.rst:117 -msgid ":guilabel:`Notified Time Off Officer`: select the person who is notified and responsible for approving requests and allocations for this specific type of time off." +#: ../../content/applications/hr/time_off.rst:116 +msgid ":guilabel:`Notified Time Off Officer`: Select the person who is notified and responsible for approving requests and allocations for this specific type of time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:119 -msgid ":guilabel:`Take Time Off in`: select the format the time off is requested in from the drop-down menu." +#: ../../content/applications/hr/time_off.rst:118 +msgid ":guilabel:`Take Time Off in`: Select the format the time off is requested in from the drop-down menu." msgstr "" -#: ../../content/applications/hr/time_off.rst:122 +#: ../../content/applications/hr/time_off.rst:121 msgid "The options are:" msgstr "" -#: ../../content/applications/hr/time_off.rst:124 +#: ../../content/applications/hr/time_off.rst:123 msgid ":guilabel:`Day`: if time off can only be requested in full day increments (8 hours)." msgstr "" -#: ../../content/applications/hr/time_off.rst:125 +#: ../../content/applications/hr/time_off.rst:124 msgid ":guilabel:`Half Day`: if time off can only be requested in half day increments (4 hours)." msgstr "" -#: ../../content/applications/hr/time_off.rst:126 +#: ../../content/applications/hr/time_off.rst:125 msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." msgstr "" -#: ../../content/applications/hr/time_off.rst:130 -msgid ":guilabel:`Deduct Extra Hours`: enable this option if the time off request should factor in any extra time accrued by the employee" +#: ../../content/applications/hr/time_off.rst:129 +msgid ":guilabel:`Deduct Extra Hours`: Enable this option if the time off request should factor in any extra time accrued by the employee." msgstr "" -#: ../../content/applications/hr/time_off.rst:134 +#: ../../content/applications/hr/time_off.rst:133 msgid "If an employee works two extra hours for the week, and requests five hours of time off, the request would be for three hours, since the two extra worked hours are used first, and deducted from the request." msgstr "" -#: ../../content/applications/hr/time_off.rst:138 -msgid ":guilabel:`Allow To Attach Supporting Document`: enable this option to allow the employee to attach documents to the time off request. This is useful in situations where documentation is required, such as long-term medical leave." +#: ../../content/applications/hr/time_off.rst:137 +msgid ":guilabel:`Allow To Attach Supporting Document`: Enable this option to allow the employee to attach documents to the time off request. This is useful in situations where documentation is required, such as long-term medical leave." msgstr "" -#: ../../content/applications/hr/time_off.rst:141 -msgid ":guilabel:`Kind of Time Off`: select from the drop-down menu the type of time off this is, either :guilabel:`Worked Time` or :guilabel:`Absence`. :guilabel:`Worked Time` indicates that the time off taken counts toward worked time for any type of accrual the employee is working towards, whereas :guilabel:`Absence` does not count toward any type of accrual." +#: ../../content/applications/hr/time_off.rst:140 +msgid ":guilabel:`Kind of Time Off`: From the drop-down menu, select the type of time off, either :guilabel:`Worked Time` or :guilabel:`Absence`. :guilabel:`Worked Time` indicates the time off taken counts toward worked time for any type of accrual the employee is working towards, whereas :guilabel:`Absence` does not count toward any type of accrual." msgstr "" -#: ../../content/applications/hr/time_off.rst:145 -msgid ":guilabel:`Company`: if multiple companies are created in the database, and this time off type only applies to one company, select the company from the drop-down menu. If this field is left blank, the time off type applies to all companies in the database. This field **only** appears in a multi-company database." +#: ../../content/applications/hr/time_off.rst:144 +msgid ":guilabel:`Company`: If multiple companies are created in the database, and this time off type only applies to one company, select the company from the drop-down menu. If this field is left blank, the time off type applies to all companies in the database. This field **only** appears in a multi-company database." msgstr "" -#: ../../content/applications/hr/time_off.rst:151 +#: ../../content/applications/hr/time_off.rst:150 msgid "Negative Cap section" msgstr "" -#: ../../content/applications/hr/time_off.rst:153 +#: ../../content/applications/hr/time_off.rst:152 msgid "Enable the :guilabel:`Allow Negative Cap` option if employees are able to request more time off than they currently have, allowing a negative balance. If enabled, an :guilabel:`Amount in Negative` field appears. In this field, enter the maximum amount of negative time allowed, in days." msgstr "" -#: ../../content/applications/hr/time_off.rst:158 +#: ../../content/applications/hr/time_off.rst:157 msgid "Sara currently has three days of the time off type `Vacation`. She is planning a trip that requires five days of time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:161 +#: ../../content/applications/hr/time_off.rst:160 msgid "The `Vacation` time off type has the :guilabel:`Allow Negative Cap` option enabled, and the :guilabel:`Amount in Negative` is set to five." msgstr "" -#: ../../content/applications/hr/time_off.rst:164 +#: ../../content/applications/hr/time_off.rst:163 msgid "These settings allow Sara to submit a request for five days of the `Vacation` time off type. If approved, her `Vacation` time off balance will be negative two (-2) days." msgstr "" @@ -10949,44 +11554,44 @@ msgid "The top half of the time off type form, with all the information filled o "off." msgstr "" -#: ../../content/applications/hr/time_off.rst:173 +#: ../../content/applications/hr/time_off.rst:172 msgid "Payroll section" msgstr "" -#: ../../content/applications/hr/time_off.rst:175 -msgid "If the time off type should create :doc:`../hr/payroll/work_entries` in the *Payroll* application, select the :guilabel:`Work Entry Type` from the drop-down list." +#: ../../content/applications/hr/time_off.rst:174 +msgid "If the time off type should create :doc:`../hr/payroll/work_entries` in the **Payroll** app, select the :guilabel:`Work Entry Type` from the drop-down list." msgstr "" -#: ../../content/applications/hr/time_off.rst:179 +#: ../../content/applications/hr/time_off.rst:178 msgid "Timesheets section" msgstr "" -#: ../../content/applications/hr/time_off.rst:182 +#: ../../content/applications/hr/time_off.rst:181 msgid "The :guilabel:`Timesheets` section only appears if the user is in developer mode. Refer to the :ref:`developer-mode` document for details on how to access the developer mode." msgstr "" -#: ../../content/applications/hr/time_off.rst:185 -msgid "When an employee takes time off, and is also using timesheets, Odoo creates entries in the *Timesheets* application for the time off. This section defines how they are entered." +#: ../../content/applications/hr/time_off.rst:184 +msgid "When an employee takes time off, and is also using timesheets, Odoo creates entries in the **Timesheets** app for the time off. This section defines how they are entered." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:187 +msgid ":guilabel:`Project`: Select the project the time off type entries appear in." msgstr "" #: ../../content/applications/hr/time_off.rst:188 -msgid ":guilabel:`Project`: select the project that the time off type entries appear in." +msgid ":guilabel:`Task`: Select the task that appears in the timesheet for this time off type. The default options are: :guilabel:`Time Off`, :guilabel:`Meeting`, or :guilabel:`Training`." msgstr "" -#: ../../content/applications/hr/time_off.rst:189 -msgid ":guilabel:`Task`: select the task that appears in the timesheet for this time off type. The default options are: :guilabel:`Time Off`, :guilabel:`Meeting`, or :guilabel:`Training`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:193 +#: ../../content/applications/hr/time_off.rst:192 msgid "Display Option section" msgstr "" -#: ../../content/applications/hr/time_off.rst:195 -msgid ":guilabel:`Color`: select a color to be used in the *Time Off* application dashboard." +#: ../../content/applications/hr/time_off.rst:194 +msgid ":guilabel:`Color`: Select a color to be used in the **Time Off** app dashboard." msgstr "" -#: ../../content/applications/hr/time_off.rst:196 -msgid ":guilabel:`Cover Image`: select an icon to be used in the *Time Off* application dashboard." +#: ../../content/applications/hr/time_off.rst:195 +msgid ":guilabel:`Cover Image`: Select an icon to be used in the **Time Off** app dashboard." msgstr "" #: ../../content/applications/hr/time_off.rst:-1 @@ -10994,328 +11599,344 @@ msgid "The lower half of the time off type form, with all the information filled "off." msgstr "" -#: ../../content/applications/hr/time_off.rst:206 +#: ../../content/applications/hr/time_off.rst:205 msgid "Accrual plans" msgstr "" -#: ../../content/applications/hr/time_off.rst:208 +#: ../../content/applications/hr/time_off.rst:207 msgid "Some time off is earned through an accrual plan, meaning that for every specified amount of time an employee works (hour, day, week, etc), they earn or *accrue* a specified amount of time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:212 +#: ../../content/applications/hr/time_off.rst:211 msgid "If an employee accrues a vacation day for every week they work, they would earn 0.2 vacation days for each hour they work. At the end of a forty hour work week, they would earn one whole vacation day (8 hours)." msgstr "" -#: ../../content/applications/hr/time_off.rst:217 +#: ../../content/applications/hr/time_off.rst:216 msgid "Create accrual plan" msgstr "" -#: ../../content/applications/hr/time_off.rst:219 +#: ../../content/applications/hr/time_off.rst:218 msgid "To create a new accrual plan, navigate to :menuselection:`Time Off app --> Configuration --> Accrual Plans`. Then, click the :guilabel:`New` button, which reveals a blank accrual plan form." msgstr "" +#: ../../content/applications/hr/time_off.rst:223 +msgid ":guilabel:`Name`: Enter the accrual plan name." +msgstr "" + #: ../../content/applications/hr/time_off.rst:224 -msgid ":guilabel:`Name`: enter the accrual plan name." +msgid ":guilabel:`Accrued Gain Time`: Select when the employee begins to accrue time off, either :guilabel:`At the start of the accrual period` or :guilabel:`At the end of the accrual period`." msgstr "" -#: ../../content/applications/hr/time_off.rst:225 -msgid ":guilabel:`Accrued Gain Time`: select when the employee begins to accrue time off, either :guilabel:`At the start of the accrual period` or :guilabel:`At the end of the accrual period`." +#: ../../content/applications/hr/time_off.rst:226 +msgid ":guilabel:`Carry-Over Time`: Select when the employee received previously earned time. The options are:" msgstr "" -#: ../../content/applications/hr/time_off.rst:227 -msgid ":guilabel:`Carry-Over Time`: select when the employee received previously earned time. The options are:" +#: ../../content/applications/hr/time_off.rst:229 +msgid ":guilabel:`At the start of the year`: Select this if the accrual rolls over on January 1 of the upcoming year." msgstr "" -#: ../../content/applications/hr/time_off.rst:230 -msgid ":guilabel:`At the start of the year`: select this if the accrual rolls over on January 1 of the upcoming year." +#: ../../content/applications/hr/time_off.rst:231 +msgid ":guilabel:`At the allocation date`: Select this if the accrual rolls over as soon as time is allocated to the employee." msgstr "" -#: ../../content/applications/hr/time_off.rst:232 -msgid ":guilabel:`At the allocation date`: select this if the accrual rolls over as soon as time is allocated to the employee." +#: ../../content/applications/hr/time_off.rst:233 +msgid ":guilabel:`Other`: Select this option if neither of the other two options are applicable. When selected, a :guilabel:`Carry-Over Date` field appears. Select the date using the two drop-down menus, one for the day and one for the month." msgstr "" -#: ../../content/applications/hr/time_off.rst:234 -msgid ":guilabel:`Other`: select this option if neither of the other two options are applicable. When selected, a :guilabel:`Carry-Over Date` field appears. Select the date using the two drop-down menus, one for the day and one for the month." +#: ../../content/applications/hr/time_off.rst:237 +msgid ":guilabel:`Based on worked time`: Enable this option if time off accrual is determined by the employee's worked hours. Days **not** considered as worked time do **not** contribute to the accrual plan in Odoo." msgstr "" -#: ../../content/applications/hr/time_off.rst:238 -msgid ":guilabel:`Based on worked time`: enable this option if time off accrual is determined by the employee's worked hours. Days **not** considered as worked time do **not** contribute to the accrual plan in Odoo." +#: ../../content/applications/hr/time_off.rst:240 +msgid ":guilabel:`Milestone Transition`: This field is **only** visible after a minimum of two :ref:`rules ` have been configured on the accrual plan. This selection determines when employees move up to a new milestone. If they qualify to change milestones in the middle of a pay period, decide whether the employee changes milestones :guilabel:`Immediately` or :guilabel:`After this accrual's period` (after the current pay period)." msgstr "" -#: ../../content/applications/hr/time_off.rst:241 -msgid ":guilabel:`Milestone Transition`: this selection determines when employees move up to a new milestone. If they qualify to change milestones in the middle of a pay period, select if the employee changes milestones :guilabel:`Immediately` or :guilabel:`After this accrual's period` (after the current pay period)." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:247 -msgid "The :guilabel:`Milestone Transition` field is **only** visible after a minimum of two :ref:`rules ` have been configured on the accrual plan." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:250 -msgid ":guilabel:`Company`: using the drop-down menu, select the company the accrual plan applies to. If left blank, the accrual plan can be used for all companies. This field only appears in a multi-company database." +#: ../../content/applications/hr/time_off.rst:245 +msgid ":guilabel:`Company`: This field **only** appears in a multi-company database. Using the drop-down menu, select the company the accrual plan applies to. If left blank, the accrual plan can be used for all companies." msgstr "" #: ../../content/applications/hr/time_off.rst:-1 msgid "An accrual plan form with all the entries filled out." msgstr "" -#: ../../content/applications/hr/time_off.rst:263 +#: ../../content/applications/hr/time_off.rst:258 msgid "Rules must be created in order for employees to accrue time off from the accrual plan." msgstr "" -#: ../../content/applications/hr/time_off.rst:265 +#: ../../content/applications/hr/time_off.rst:260 msgid "To create a new rule, click the :guilabel:`New Milestone` button in the gray :guilabel:`Rules` section, and a :guilabel:`Create Milestone` modal form appears." msgstr "" -#: ../../content/applications/hr/time_off.rst:270 -msgid ":guilabel:`Employee accrue`: select the parameters for earned time off in this section." +#: ../../content/applications/hr/time_off.rst:265 +msgid ":guilabel:`Employee accrue`: Select the parameters for earned time off in this section." msgstr "" -#: ../../content/applications/hr/time_off.rst:272 +#: ../../content/applications/hr/time_off.rst:267 msgid "First, select either :guilabel:`Days` or :guilabel:`Hours` for the increment of accrued time using the drop-down menu." msgstr "" -#: ../../content/applications/hr/time_off.rst:275 +#: ../../content/applications/hr/time_off.rst:270 msgid "Next, enter the numerical amount of the selected parameter that is accrued. The numerical format is `X.XXXX`, so that partial days or hours can also be configured." msgstr "" -#: ../../content/applications/hr/time_off.rst:278 +#: ../../content/applications/hr/time_off.rst:273 msgid "Last, select how often the time is accrued using the drop-down menu. The default options are :guilabel:`Hourly`, :guilabel:`Daily`, :guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, :guilabel:`Twice a year`, and :guilabel:`Yearly`." msgstr "" -#: ../../content/applications/hr/time_off.rst:282 -msgid "Depending on which option is selected, additional fields may appear. For example, if :guilabel:`Twice a month` is selected, two additional fields appear, to specify the two days of each month that the milestone occurs." +#: ../../content/applications/hr/time_off.rst:277 +msgid "Depending on which option is selected, additional fields may appear. For example, if :guilabel:`Twice a month` is selected, two additional fields appear, to specify the two days of each month the milestone occurs." msgstr "" -#: ../../content/applications/hr/time_off.rst:285 -msgid ":guilabel:`Cap accrued time`: if there is a maximum amount of days the employee can accrue with this plan, enable this option." +#: ../../content/applications/hr/time_off.rst:280 +msgid ":guilabel:`Cap accrued time`: If there is a maximum amount of days the employee can accrue with this plan, enable this option." msgstr "" -#: ../../content/applications/hr/time_off.rst:288 +#: ../../content/applications/hr/time_off.rst:283 msgid "When enabled, two additional fields appear beneath it. Select the type of time period from the drop-down menu, either :guilabel:`Days` or :guilabel:`Hours`." msgstr "" -#: ../../content/applications/hr/time_off.rst:291 +#: ../../content/applications/hr/time_off.rst:286 msgid "Then, enter a numerical value in the field to specify the maximum amount of time that can be accrued." msgstr "" -#: ../../content/applications/hr/time_off.rst:293 -msgid ":guilabel:`Milestone reached`: enter the number and value of the time period that must pass before the employee starts to accumulate time off. The first value is numerical; enter a number in the first field." +#: ../../content/applications/hr/time_off.rst:288 +msgid ":guilabel:`Milestone reached`: Enter the number and value of the time period that must pass before the employee starts to accumulate time off. The first value is numerical; enter a number in the first field." msgstr "" -#: ../../content/applications/hr/time_off.rst:297 +#: ../../content/applications/hr/time_off.rst:292 msgid "Then, select the type of time period using the drop-down menu in the second field. The options are: :guilabel:`Days`, :guilabel:`Months`, or :guilabel:`Years`." msgstr "" -#: ../../content/applications/hr/time_off.rst:299 +#: ../../content/applications/hr/time_off.rst:294 msgid ":guilabel:`Carry over`: select how any unused time off is handled. The options are either:" msgstr "" -#: ../../content/applications/hr/time_off.rst:301 -msgid ":guilabel:`None. Accrued time reset to 0`: any unused time off is gone." +#: ../../content/applications/hr/time_off.rst:296 +msgid ":guilabel:`None. Accrued time reset to 0`: Any unused time off is gone." msgstr "" -#: ../../content/applications/hr/time_off.rst:302 -msgid ":guilabel:`All accrued time carried over`: all unused time off is rolled over to the next calendar year." +#: ../../content/applications/hr/time_off.rst:297 +msgid ":guilabel:`All accrued time carried over`: All unused time off is rolled over to the next calendar year." msgstr "" -#: ../../content/applications/hr/time_off.rst:304 -msgid ":guilabel:`Carry over with a maximum`: unused time off is rolled over to the next calendar year, but there is a cap. An :guilabel:`Up to` field appears if this is selected. Enter the maximum number of :guilabel:`Days` that can roll over to the following year. Any time off beyond this parameter is lost." +#: ../../content/applications/hr/time_off.rst:299 +msgid ":guilabel:`Carry over with a maximum`: Unused time off is rolled over to the next calendar year, but there is a cap. An :guilabel:`Up to` field appears if this is selected. Enter the maximum number of :guilabel:`Days` that can roll over to the following year. Any time off beyond this parameter is lost." msgstr "" -#: ../../content/applications/hr/time_off.rst:309 -msgid "Once the form is completed, click :guilabel:`Save & Close` to save the form and close the modal, or click :guilabel:`Save & New` to save the form and create another milestone. Add as many milestones as desired." +#: ../../content/applications/hr/time_off.rst:305 +msgid "If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time reset to 0`, that rule *overrides* the :guilabel:`Carry-Over Time` set on the accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:308 +msgid "If a company creates an accrual plan, granting employees time off :guilabel:`At the start of the accrual period` (i.e., the beginning of the year), and sets the :guilabel:`Carry-Over Time` on the *accrual plan* to :guilabel:`At the start of the year`, it allows unused vacation time to rollover to the following year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:313 +msgid "Then, the company adds rules to the accrual plan, allocating five days of vacation, annually, on the first of the year (one week of vacation allocated on January 1st)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:316 +msgid "If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrual time reset to 0` on the :guilabel:`Create Milestone` pop-up for, any unused vacation time *does not* carry over, even though on the :guilabel:`Accrual Plan` form, the :guilabel:`Carry-Over Time` is set to :guilabel:`At the start of the year`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:321 +msgid "The carry over set on the *rule* takes precedence over the carry over set on the *accrual plan form*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:324 +msgid "Once the form is completed, click :guilabel:`Save & Close` to save the :guilabel:`Create Milestone` form, and close the modal, or click :guilabel:`Save & New` to save the form and create another milestone. Add as many milestones as desired." msgstr "" #: ../../content/applications/hr/time_off.rst:-1 msgid "A milestone form with all the entries filled out." msgstr "" -#: ../../content/applications/hr/time_off.rst:320 +#: ../../content/applications/hr/time_off.rst:335 msgid "Public holidays" msgstr "" -#: ../../content/applications/hr/time_off.rst:322 +#: ../../content/applications/hr/time_off.rst:337 msgid "To observe public or national holidays, and provide extra days off as holidays to employees, configure the observed *public holidays* in Odoo." msgstr "" -#: ../../content/applications/hr/time_off.rst:325 +#: ../../content/applications/hr/time_off.rst:340 msgid "It is important to configure these days in Odoo, so employees are aware of the days they have off, and do not request time off on days that are already set as a public holiday (non-working days)." msgstr "" -#: ../../content/applications/hr/time_off.rst:328 -msgid "Additionally, all public holidays configured in the *Time Off* app are also reflected in any app that uses working schedules, such as *Calendar*, *Planning*, *Manufacturing*, and more." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:331 -msgid "Due to Odoo's integration with other apps that use working schedules, it is considered best practice to ensure *all* public holidays are configured." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:335 -msgid "Create public holiday" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:337 -msgid "To create a public holiday, navigate to :menuselection:`Time Off app --> Configuration --> Public Holidays`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:340 -msgid "All currently configured public holidays appear in a list view." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:342 -msgid "Click the :guilabel:`New` button, and a new line appears at the bottom of the list." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:344 -#: ../../content/applications/hr/time_off.rst:406 -msgid "Enter the following information on that new line:" +#: ../../content/applications/hr/time_off.rst:343 +msgid "Additionally, all public holidays configured in the **Time Off** app are also reflected in any app that uses working schedules, such as **Calendar**, **Planning**, **Manufacturing**, and more." msgstr "" #: ../../content/applications/hr/time_off.rst:346 -msgid ":guilabel:`Name`: enter the name of the holiday." +msgid "Due to Odoo's integration with other apps that use working schedules, it is considered best practice to ensure *all* public holidays are configured." msgstr "" -#: ../../content/applications/hr/time_off.rst:347 -msgid ":guilabel:`Company`: if in a multi-company database, the current company populates this field by default. It is not possible to edit this field." +#: ../../content/applications/hr/time_off.rst:350 +msgid "Create public holiday" msgstr "" -#: ../../content/applications/hr/time_off.rst:351 -msgid "The :guilabel:`Company` field is hidden by default. To view this field, click the two dots in the top-right corner of the list, to the far-right of the column titles, and activate the :guilabel:`Company` selection from the drop-down menu that appears." +#: ../../content/applications/hr/time_off.rst:352 +msgid "To create a public holiday, navigate to :menuselection:`Time Off app --> Configuration --> Public Holidays`." msgstr "" #: ../../content/applications/hr/time_off.rst:355 -msgid ":guilabel:`Start Date`: using the date and time picker, select the date and time that the holiday starts. By default, this field is configured for the current date. The start time is set according to the start time for the company (according to the :ref:`working schedules `). If the user's computer is set to a different time zone, the start time is adjusted according to the difference in the time zone, compared to the company's time zone." +msgid "All currently configured public holidays appear in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:360 -msgid ":guilabel:`End Date`: using the date and time picker, select the date and time that the holiday ends. By default, this field is configured for the current date, and the time is set to the end time for the company (according to the :ref:`working schedules `). If the user's computer is set to a different time zone, the start time is adjusted according to the difference in the time zone, compared to the company's time zone." +#: ../../content/applications/hr/time_off.rst:357 +msgid "Click the :guilabel:`New` button, and a new line appears at the bottom of the list." msgstr "" -#: ../../content/applications/hr/time_off.rst:367 +#: ../../content/applications/hr/time_off.rst:359 +#: ../../content/applications/hr/time_off.rst:422 +msgid "Enter the following information on that new line:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:361 +msgid ":guilabel:`Name`: Enter the name of the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:362 +msgid ":guilabel:`Company`: If in a multi-company database, the current company populates this field by default. It is **not** possible to edit this field." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:366 +msgid "The :guilabel:`Company` field is hidden, by default. To view this field, click the :icon:`oi-settings-adjust` :guilabel:`(additional options)` icon in the top-right corner of the list, to the far-right of the column titles, and activate the :guilabel:`Company` selection from the drop-down menu that appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:371 +msgid ":guilabel:`Start Date`: Using the date and time picker, select the date and time the holiday starts, then click :icon:`fa-check` :guilabel:`Apply`. By default, this field is configured for the current date. The start time is set according to the start time for the company (according to the :ref:`working schedules `). If the user's computer is set to a different time zone, the start time is adjusted according, compared to the company's time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:376 +msgid ":guilabel:`End Date`: Using the date and time picker, select the date and time the holiday ends, then click :icon:`fa-check` :guilabel:`Apply`. By default, this field is configured for the current date, and the time is set to the end time for the company (according to the :ref:`working schedules `). If the user's computer is set to a different time zone, the start time is adjusted accordingly, compared to the company's time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:383 msgid "A company located in San Francisco operates from 9:00 AM - 6:00 PM, with an eight hour work day and one hour lunch break." msgstr "" -#: ../../content/applications/hr/time_off.rst:370 +#: ../../content/applications/hr/time_off.rst:386 msgid "For a user in New York, with a computer time zone set to Eastern Standard Time, a created public holiday displays a start time of 12:00 PM - 9:00 PM, accounting for the three hour time zone difference." msgstr "" -#: ../../content/applications/hr/time_off.rst:374 +#: ../../content/applications/hr/time_off.rst:390 msgid "Similarly, a user located in Los Angeles, with a computer time zone set to Pacific Standard Time, sees a public holiday time as 9:00 AM - 6:00 PM." msgstr "" -#: ../../content/applications/hr/time_off.rst:377 -msgid ":guilabel:`Working Hours`: if the holiday should only apply to employees who have a specific set of working hours, select the working hours from the drop-down menu. If left blank, the holiday applies to all employees." +#: ../../content/applications/hr/time_off.rst:393 +msgid ":guilabel:`Working Hours`: If the holiday should only apply to employees who have a specific set of working hours, select the working hours from the drop-down menu. If left blank, the holiday applies to all employees." msgstr "" -#: ../../content/applications/hr/time_off.rst:380 -msgid ":guilabel:`Work Entry Type`: if using the *Payroll* application, this field defines how the :ref:`work entries ` for the holiday appear. Select the work entry type from the drop-down menu." +#: ../../content/applications/hr/time_off.rst:396 +msgid ":guilabel:`Work Entry Type`: If using the **Payroll** app, this field defines how the :ref:`work entries ` for the holiday appear. Select the work entry type from the drop-down menu." msgstr "" #: ../../content/applications/hr/time_off.rst:-1 msgid "The list of public holidays in the configuration menu." msgstr "" -#: ../../content/applications/hr/time_off.rst:389 +#: ../../content/applications/hr/time_off.rst:405 msgid "Mandatory days" msgstr "" -#: ../../content/applications/hr/time_off.rst:391 +#: ../../content/applications/hr/time_off.rst:407 msgid "Some companies have special days where specific departments, or the entire staff, is required to be present, and time off is not allowed on those specific days." msgstr "" -#: ../../content/applications/hr/time_off.rst:394 +#: ../../content/applications/hr/time_off.rst:410 msgid "These types of days are called *mandatory days* in Odoo. These can be configured to be company-wide, or department specific. When configured, employees in the specified department or company are unable to submit time off requests for these mandatory days." msgstr "" -#: ../../content/applications/hr/time_off.rst:399 +#: ../../content/applications/hr/time_off.rst:415 msgid "Create mandatory days" msgstr "" -#: ../../content/applications/hr/time_off.rst:401 +#: ../../content/applications/hr/time_off.rst:417 msgid "No mandatory days are configured in Odoo by default. To create a mandatory day, navigate to :menuselection:`Time Off app --> Configuration --> Mandatory Days`." msgstr "" -#: ../../content/applications/hr/time_off.rst:404 +#: ../../content/applications/hr/time_off.rst:420 msgid "Click the :guilabel:`New` button in the top-left corner, and a blank line appears in the list." msgstr "" -#: ../../content/applications/hr/time_off.rst:408 -msgid ":guilabel:`Name`: enter the name of the mandatory day." +#: ../../content/applications/hr/time_off.rst:424 +msgid ":guilabel:`Name`: Enter the name of the mandatory day." msgstr "" -#: ../../content/applications/hr/time_off.rst:409 -msgid ":guilabel:`Company`: if in a multi-company database, this field is visible, and the current company populates this field by default. Using the drop-down menu, select the company the mandatory day is for." +#: ../../content/applications/hr/time_off.rst:425 +msgid ":guilabel:`Company`: If in a multi-company database, this field is visible, and the current company populates this field, by default. Using the drop-down menu, select the company the mandatory day is for." msgstr "" -#: ../../content/applications/hr/time_off.rst:412 -msgid ":guilabel:`Departments`: this column is hidden by default. First, click the :guilabel:`(optional columns)` icon in the top-right corner, next to :guilabel:`Colors`, and then click the checkbox next to :guilabel:`Departments` to reveal that column." +#: ../../content/applications/hr/time_off.rst:428 +msgid ":guilabel:`Departments`: This column is hidden by default. First, click the :icon:`oi-settings-adjust` :guilabel:`(additional options)` icon in the top-right corner, next to :guilabel:`Color`, and then tick the checkbox next to :guilabel:`Departments` to reveal that column." msgstr "" -#: ../../content/applications/hr/time_off.rst:416 +#: ../../content/applications/hr/time_off.rst:433 msgid "Next, select the desired departments from the drop-down menu. Multiple departments can be selected, and there is no limit to the amount of departments that can be added." msgstr "" -#: ../../content/applications/hr/time_off.rst:419 +#: ../../content/applications/hr/time_off.rst:436 msgid "If this field is left blank, the mandatory day applies to the entire company." msgstr "" -#: ../../content/applications/hr/time_off.rst:420 -msgid ":guilabel:`Start Date`: using the calendar picker, select the date the mandatory day starts." +#: ../../content/applications/hr/time_off.rst:437 +msgid ":guilabel:`Start Date`: Using the calendar picker, select the date the mandatory day starts." msgstr "" -#: ../../content/applications/hr/time_off.rst:421 -msgid ":guilabel:`End Date`: using the calendar picker, select the date the mandatory day ends. If creating a single mandatory day, the end date should be the same as the start date." +#: ../../content/applications/hr/time_off.rst:438 +msgid ":guilabel:`End Date`: Using the calendar picker, select the date the mandatory day ends. If creating a single mandatory day, the end date should be the same as the start date." msgstr "" -#: ../../content/applications/hr/time_off.rst:423 -msgid ":guilabel:`Color`: if desired, select a color from the available presented options. If no color is desired, select the `No color` option, represented by a white box with a red line diagonally across it. The selected color appears on the main *Time Off* application dashboard, in both the calendar and in the legend." +#: ../../content/applications/hr/time_off.rst:440 +msgid ":guilabel:`Color`: If desired, select a color from the available presented options. If no color is desired, select the `No color` option, represented by a white box with a red line diagonally across it. The selected color appears on the main **Time Off** app dashboard, in both the calendar and in the legend." msgstr "" #: ../../content/applications/hr/time_off.rst:-1 msgid "The Mandatory Days section with three configured days." msgstr "" -#: ../../content/applications/hr/time_off.rst:435 +#: ../../content/applications/hr/time_off.rst:452 msgid "To view a color-coded schedule of the user's time off, and/or of the team managed by them, navigate to :menuselection:`Time Off app --> Overview`. This presents a calendar with the default filter of `My Team`, in a month view." msgstr "" -#: ../../content/applications/hr/time_off.rst:439 +#: ../../content/applications/hr/time_off.rst:456 msgid "To change the time period displayed, click on the :guilabel:`Month` button to reveal a drop-down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Year` to present the calendar in that corresponding view." msgstr "" -#: ../../content/applications/hr/time_off.rst:443 +#: ../../content/applications/hr/time_off.rst:460 msgid "To navigate forward or backward in time, in the selected increment (:guilabel:`Month`, :guilabel:`Week`, etc.), click the :guilabel:`← (left arrow)` or :guilabel:`→ (right arrow)` to move either forward or backward in that specified amount of time." msgstr "" -#: ../../content/applications/hr/time_off.rst:447 +#: ../../content/applications/hr/time_off.rst:464 msgid "For example, if :guilabel:`Month` is selected, the arrows adjust the view by one month." msgstr "" -#: ../../content/applications/hr/time_off.rst:449 +#: ../../content/applications/hr/time_off.rst:466 msgid "To return to a view containing the current day, click the :guilabel:`Today` button at any time." msgstr "" -#: ../../content/applications/hr/time_off.rst:451 +#: ../../content/applications/hr/time_off.rst:468 msgid "Team members are listed alphabetically on individual lines, and their requested time off, regardless of the status (*validated* or *to approve*), is visible on the calendar." msgstr "" -#: ../../content/applications/hr/time_off.rst:454 +#: ../../content/applications/hr/time_off.rst:471 msgid "Each employee is color-coded. The employee's color is selected at random, and does *not* correspond to the type of time off they requested." msgstr "" -#: ../../content/applications/hr/time_off.rst:457 +#: ../../content/applications/hr/time_off.rst:474 msgid "The status of the time off is represented by the color detail of the request, either appearing solid (*validated*) or striped (*to approve*)." msgstr "" -#: ../../content/applications/hr/time_off.rst:460 +#: ../../content/applications/hr/time_off.rst:477 msgid "The number of days or hours requested is written on the request (if there is enough space)." msgstr "" -#: ../../content/applications/hr/time_off.rst:462 +#: ../../content/applications/hr/time_off.rst:479 msgid "At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph shows how many people are projected to be out on any given day. The number on each individual bar represents the number of employees out for those highlighted days." msgstr "" -#: ../../content/applications/hr/time_off.rst:466 +#: ../../content/applications/hr/time_off.rst:483 msgid "Click on a time off entry to view the details for the specific time off entry. The total number of hours or days are listed, along with the start and end time of the time off. To view the details of the time off request in a modal, click the :guilabel:`View` button." msgstr "" @@ -11323,31 +11944,35 @@ msgstr "" msgid "Overview of the user's team, with time off requests shown." msgstr "" -#: ../../content/applications/hr/time_off.rst:479 +#: ../../content/applications/hr/time_off.rst:496 msgid "The reporting feature allows users to view time off for their team, either by employee or type of time off. This allows users to see which employees are taking time off, how much time off they are taking, and what time off types are being used." msgstr "" -#: ../../content/applications/hr/time_off.rst:483 -msgid "Any report can be added to a spreadsheet through the *Insert in Spreadsheet* button that appears in the top-left of a report. If the *Documents* application is installed, an option to add the report to a spreadsheet appears. If not, the report can be added to a *Dashboard*." +#: ../../content/applications/hr/time_off.rst:500 +msgid "Any report can be added to a spreadsheet, when in either the :icon:`fa-area-chart` :guilabel:`(Graph)` or :icon:`oi-view-pivot` :guilabel:`(Pivot)` view, through the *Insert in Spreadsheet* button that appears in the top-left of the report." msgstr "" -#: ../../content/applications/hr/time_off.rst:488 +#: ../../content/applications/hr/time_off.rst:505 +msgid "If the **Documents** app is installed, an option to add the report to a spreadsheet appears. If not, the report can be added to a *Dashboard*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:509 msgid "By employee" msgstr "" -#: ../../content/applications/hr/time_off.rst:490 +#: ../../content/applications/hr/time_off.rst:511 msgid "To view a report of employee time off requests, navigate to :menuselection:`Time Off app --> Reporting --> by Employee`." msgstr "" -#: ../../content/applications/hr/time_off.rst:493 +#: ../../content/applications/hr/time_off.rst:514 msgid "The default report presents the current year's data in a list view, displaying all the employees in alphabetical order. Each employee's line is collapsed by default. To expand a line, click anywhere on the line." msgstr "" -#: ../../content/applications/hr/time_off.rst:497 +#: ../../content/applications/hr/time_off.rst:518 msgid "The view expands, and has the time off requests organized by time off type. Click anywhere on a time off type line to expand it, and view all the individual time off requests that fall under that type." msgstr "" -#: ../../content/applications/hr/time_off.rst:500 +#: ../../content/applications/hr/time_off.rst:521 msgid "The information shown in the list includes: the :guilabel:`Employee` name, :guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`." msgstr "" @@ -11355,27 +11980,23 @@ msgstr "" msgid "Report of time off, shown by each employee in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:508 -msgid "The report can be displayed in other ways, as well. Click the corresponding button option in the top-right corner of the page to view the data in that specific way. The various options are a :guilabel:`List` (the default view), :guilabel:`Graph`, :guilabel:`Pivot` table, or :guilabel:`Calendar` view." +#: ../../content/applications/hr/time_off.rst:529 +msgid "The report can be displayed in other ways, as well. Click the corresponding button option in the top-right corner of the page to view the data in that specific way. The various options are a :icon:`oi-view-list` :guilabel:`(List)`, or default view, :icon:`fa-area-chart` :guilabel:`(Graph)`, :icon:`oi-view-pivot` :guilabel:`(Pivot)` table, or :icon:`fa-calendar` :guilabel:`(Calendar)` view." msgstr "" -#: ../../content/applications/hr/time_off.rst:-1 -msgid "The various other views highlighted, for the employee time off report." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:517 +#: ../../content/applications/hr/time_off.rst:534 msgid "When a selection has been made, additional options appear for that particular selection. For more detailed information on the reports and their various options, refer to the :doc:`reporting <../essentials/reporting>` documentation." msgstr "" -#: ../../content/applications/hr/time_off.rst:522 +#: ../../content/applications/hr/time_off.rst:539 msgid "By type" msgstr "" -#: ../../content/applications/hr/time_off.rst:524 +#: ../../content/applications/hr/time_off.rst:541 msgid "To view a list of all time off, organized by time off type, navigate to :menuselection:`Time Off app --> Reporting --> by Type`. This shows all time off requests in a default bar chart." msgstr "" -#: ../../content/applications/hr/time_off.rst:527 +#: ../../content/applications/hr/time_off.rst:544 msgid "Hover over a bar to view the :guilabel:`Duration (Days)` of that specific time off type." msgstr "" @@ -11384,35 +12005,35 @@ msgid "The various time off types, and how many days requested, in a bar chart. "highlighted in a red box." msgstr "" -#: ../../content/applications/hr/time_off.rst:534 +#: ../../content/applications/hr/time_off.rst:551 msgid "Click on a bar to go to a detailed list view of all the time off requests for that time off type." msgstr "" -#: ../../content/applications/hr/time_off.rst:536 +#: ../../content/applications/hr/time_off.rst:553 msgid "Each request is listed, with the following information displayed: the :guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the :guilabel:`Description`." msgstr "" -#: ../../content/applications/hr/time_off.rst:540 -msgid "The report can be displayed in other ways, as well. Click the corresponding button option in the top-right corner of the page to view the data in that way. The various options are a :guilabel:`Graph` (the default view), :guilabel:`List`, or :guilabel:`Pivot` table." +#: ../../content/applications/hr/time_off.rst:557 +msgid "The report can be displayed in other ways, as well. Click the corresponding button option in the top-right corner of the page to view the data in that way. The various options are a :icon:`fa-area-chart` :guilabel:`(Graph)` (the default view), :icon:`oi-view-list` :guilabel:`(List)`, or :icon:`oi-view-pivot` :guilabel:`(Pivot)` table." msgstr "" -#: ../../content/applications/hr/time_off.rst:544 +#: ../../content/applications/hr/time_off.rst:562 msgid "When a selection has been made, additional options appear for that particular selection. For more detailed information on the reports, and their various options, refer to the :doc:`reporting <../essentials/reporting>` documentation." msgstr "" -#: ../../content/applications/hr/time_off.rst:549 +#: ../../content/applications/hr/time_off.rst:567 msgid ":doc:`time_off/allocations`" msgstr "" -#: ../../content/applications/hr/time_off.rst:550 +#: ../../content/applications/hr/time_off.rst:568 msgid ":doc:`time_off/request_time_off`" msgstr "" -#: ../../content/applications/hr/time_off.rst:551 +#: ../../content/applications/hr/time_off.rst:569 msgid ":doc:`time_off/my_time`" msgstr "" -#: ../../content/applications/hr/time_off.rst:552 +#: ../../content/applications/hr/time_off.rst:570 msgid ":doc:`time_off/management`" msgstr "" @@ -11425,7 +12046,7 @@ msgid "Once :ref:`time off types ` and :ref:`accrual pl msgstr "" #: ../../content/applications/hr/time_off/allocations.rst:9 -msgid "The *Allocations* section of the *Time Off* app is **only** visible to users who have either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for the *Time Off* application. For more information on access rights, refer to the :doc:`access rights <../../general/users/access_rights/>` documentation." +msgid "The *Allocations* page of the **Time Off** app is **only** visible to users who have either *Time Off Officer* or *Administrator* access rights for the **Time Off** application. For more information on access rights, refer to the :doc:`access rights <../../general/users/access_rights/>` documentation." msgstr "" #: ../../content/applications/hr/time_off/allocations.rst:15 @@ -11449,19 +12070,19 @@ msgid "After entering a name for the allocation on the first blank field of the msgstr "" #: ../../content/applications/hr/time_off/allocations.rst:27 -msgid ":guilabel:`Time Off Type`: using the drop-down menu, select the type of time off that is being allocated to the employees." +msgid ":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time off that is being allocated to the employees." msgstr "" #: ../../content/applications/hr/time_off/allocations.rst:29 -msgid ":guilabel:`Allocation Type`: select either :guilabel:`Regular Allocation` or :guilabel:`Accrual Allocation`. If the allocation is **not** based on an :ref:`accrual plan `, select :guilabel:`Regular Allocation`." +msgid ":guilabel:`Allocation Type`: Select either :guilabel:`Regular Allocation` or :guilabel:`Accrual Allocation`. If the allocation is **not** based on an :ref:`accrual plan `, select :guilabel:`Regular Allocation`." msgstr "" #: ../../content/applications/hr/time_off/allocations.rst:32 -msgid ":guilabel:`Accrual Plan`: if :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears. Using the drop-down menu, select the accrual plan with which the allocation is associated. An accrual plan **must** be selected for an :guilabel:`Accrual Allocation`." +msgid ":guilabel:`Accrual Plan`: If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears. Using the drop-down menu, select the accrual plan with which the allocation is associated. An accrual plan **must** be selected for an :guilabel:`Accrual Allocation`." msgstr "" #: ../../content/applications/hr/time_off/allocations.rst:36 -msgid ":guilabel:`Validity Period/Start Date`: if :guilabel:`Regular Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start Date`." +msgid ":guilabel:`Validity Period/Start Date`: If :guilabel:`Regular Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start Date`." msgstr "" #: ../../content/applications/hr/time_off/allocations.rst:41 @@ -11476,32 +12097,56 @@ msgstr "" msgid "If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this second field is labeled :guilabel:`Run until`." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:51 -msgid ":guilabel:`Allocation`: enter the amount of time that is being allocated to the employees. This field displays the time in either :guilabel:`Hours` or :guilabel:`Days`, depending on how the selected :ref:`Time Off Type ` is configured." +#: ../../content/applications/hr/time_off/allocations.rst:53 +msgid "If the :guilabel:`Start Date` entered is in the middle of a period of time, such as the middle of the month, Odoo applies the allocation to the beginning or end of the period, depending on the *Accrued Gain Time* entered on the :ref:`accrual plan ` (either *At the start of the accrual period*, or *At the end of the accrual period*) instead of the specific date entered." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:54 -msgid ":guilabel:`Mode`: using the drop-down menu, select how the allocation is assigned. This selection determines who receives the time off allocation. The options are :guilabel:`By Employee`, :guilabel:`By Company`, :guilabel:`By Department`, or :guilabel:`By Employee Tag`." +#: ../../content/applications/hr/time_off/allocations.rst:59 +msgid "For example, an allocation is created, and references an accrual plan that grants time *At the start of the accrual period*, monthly, on the first of the month." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:58 -msgid "Depending on what is selected for the :guilabel:`Mode`, the following field is labeled either: :guilabel:`Employees`, :guilabel:`Company`, :guilabel:`Department`, or :guilabel:`Employee Tag`." +#: ../../content/applications/hr/time_off/allocations.rst:62 +msgid "On the allocation form, the :guilabel:`Allocation Type` is set to :guilabel:`Accrual Allocation`, and the :guilabel:`Start Date` entered is `06/16/24`." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:61 +#: ../../content/applications/hr/time_off/allocations.rst:65 +msgid "Odoo's **Time Off** app retroactively applies the allocation to the beginning of the time period entered in the :guilabel:`Start Date`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:68 +msgid "Therefore, this allocation accrues time from `06/01/24`, rather than `06/16/24`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:70 +msgid "Additionally, if on the accrual form, the allocation references an accrual plan that grants time *`At the end of the accrual period*, the allocation accrues time from `7/01/24` rather than `6/18/24`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:74 +msgid ":guilabel:`Allocation`: Enter the amount of time that is being allocated to the employees. This field displays the time in either :guilabel:`Hours` or :guilabel:`Days`, depending on how the selected :ref:`Time Off Type ` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:77 +msgid ":guilabel:`Mode`: Using the drop-down menu, select how the allocation is assigned. This selection determines who receives the time off allocation. The options are :guilabel:`By Employee`, :guilabel:`By Company`, :guilabel:`By Department`, or :guilabel:`By Employee Tag`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:81 +msgid "Depending on what is selected for the :guilabel:`Mode`, the field beneath :guilabel:`Mode` is labeled either: :guilabel:`Employees`, :guilabel:`Company`, :guilabel:`Department`, or :guilabel:`Employee Tag`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:85 msgid "Using the drop-down menu, indicate the specific employees, company, department, or employee tags receiving this time off." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:64 +#: ../../content/applications/hr/time_off/allocations.rst:88 msgid "Multiple selections can be made for either :guilabel:`Employees` or :guilabel:`Employee Tag`." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:66 +#: ../../content/applications/hr/time_off/allocations.rst:90 msgid "Only one selection can be made for the :guilabel:`Company` or :guilabel:`Department`." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:67 -msgid ":guilabel:`Add a reason...`: if any description or note is necessary to explain the time off allocation, enter it in this field at the bottom of the form." +#: ../../content/applications/hr/time_off/allocations.rst:91 +msgid ":guilabel:`Add a reason...`: If any description or note is necessary to explain the time off allocation, enter it in this field at the bottom of the form." msgstr "" #: ../../content/applications/hr/time_off/allocations.rst:-1 @@ -11509,47 +12154,47 @@ msgid "A new allocation form with all the fields filled out for the annual two w "granted to all employees." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:78 +#: ../../content/applications/hr/time_off/allocations.rst:102 msgid "Request allocation" msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:80 +#: ../../content/applications/hr/time_off/allocations.rst:104 msgid "If an employee has used all their time off, or will run out of time off, they can request an allocation for additional time. Allocations can be requested in one of two ways, either from the :ref:`Dashboard ` or the :ref:`My Allocations ` view." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:84 -msgid "To create a new allocation request, click either the :guilabel:`New Allocation Request` button on the main *Time Off* dashboard, or the :guilabel:`New` button in the :guilabel:`My Allocations` list view. Both buttons open a new allocation request form." +#: ../../content/applications/hr/time_off/allocations.rst:108 +msgid "To create a new allocation request, click either the :guilabel:`New Allocation Request` button on the main **Time Off** dashboard, or the :guilabel:`New` button in the :guilabel:`My Allocations` list view. Both buttons open a new allocation request form." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:89 -msgid "Both options open a new allocation request form, but when requested from the :guilabel:`Dashboard`, the form appears in a pop-up window. When requested from the :guilabel:`My Allocations` list view, the screen navigates to a new allocation request page, instead." +#: ../../content/applications/hr/time_off/allocations.rst:113 +msgid "Both options open a new allocation request form, but when requested from the :guilabel:`Dashboard`, the form appears in a pop-up window, and the *Validity Period* field does **not** appear. When requested from the :guilabel:`My Allocations` list view, the screen navigates to a new allocation request page, instead of presenting a pop-up window." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:94 +#: ../../content/applications/hr/time_off/allocations.rst:118 msgid "Enter the following information on the new allocation request form:" msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:96 -msgid ":guilabel:`Time Off Type`: select the type of time off being requested for the allocation from the drop-down menu. After a selection is made, the title updates with the time off type." +#: ../../content/applications/hr/time_off/allocations.rst:120 +msgid ":guilabel:`Time Off Type`: Select the type of time off being requested for the allocation from the drop-down menu. After a selection is made, the title updates with the time off type." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:98 -msgid ":guilabel:`Validity Period`: using the calendar selector, select a start and end date the allocation is valid for. By default, the current date populates the first field, and :guilabel:`No Limit` populates the second field. Adjust both of these dates, if desired." +#: ../../content/applications/hr/time_off/allocations.rst:122 +msgid ":guilabel:`Validity Period`: By default, the current date populates this field, and it is **not** able to be modified. This field **only** appears when requesting an allocatoin from the :guilabel:`My Allocations` view (:menuselection:`Time Off --> My Time --> My Allocations`)." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:101 -msgid ":guilabel:`Allocation`: enter the amount of time being requested in this field. The format is presented in either :guilabel:`Days` or :guilabel:`Hours`, depending on how the :guilabel:`Time Off Type` is configured. Once this field is populated, the name of the allocation request is updated to include the amount of time being requested." +#: ../../content/applications/hr/time_off/allocations.rst:125 +msgid ":guilabel:`Allocation`: Enter the amount of time being requested in this field. The format is presented in either :guilabel:`Days` or :guilabel:`Hours`, depending on how the :guilabel:`Time Off Type` is configured. Once this field is populated, the name of the allocation request is updated to include the amount of time being requested." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:105 -msgid ":guilabel:`Add a reason...`: enter a description for the allocation request. This should include any details that approvers may need to approve the request." +#: ../../content/applications/hr/time_off/allocations.rst:129 +msgid ":guilabel:`Add a reason...`: Enter a description for the allocation request in this field. This should include any details that approvers may need to approve the request." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:108 +#: ../../content/applications/hr/time_off/allocations.rst:132 msgid "If the request was created from the :guilabel:`Dashboard`, click the :guilabel:`Save & Close` button on the :guilabel:`New Allocation` pop-up window to save the information and submit the request." msgstr "" -#: ../../content/applications/hr/time_off/allocations.rst:111 +#: ../../content/applications/hr/time_off/allocations.rst:135 msgid "If the form was completed from the :guilabel:`My Allocations` list view, the information is automatically saved as it is entered. However, the form can be saved manually at any time by clicking the :icon:`fa-cloud-upload` :guilabel:`(cloud upload)` icon." msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index baf9bc73d..9f53c0cb7 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 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 13:30+0000\n" +"POT-Creation-Date: 2024-08-21 11:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -33,7 +33,6 @@ msgid "`Odoo Tutorials: Barcode `_" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations.rst:5 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:5 msgid "Daily operations" msgstr "" @@ -222,353 +221,443 @@ msgid "*Barcode nomenclatures* define how barcodes are recognized and categorize msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:15 -msgid "Odoo *Barcode* supports UPC (Universal Product Code), EAN (European Article Number), and GS1 encoding. The pre-configured nomenclatures in Odoo are *Default Nomenclature* and *Default GS1 Nomenclature*. The default nomenclature uses |UPC| and |EAN| encoding, and supports |UPC|/|EAN| conversion." +msgid "For instance, at a :doc:`Point of Sale <../../../sales/point_of_sale>` station, product weight barcodes in the European Article Number (EAN) format, which begin with `21` and have five digits specifying the weight, are used to weigh products and generate a barcode depicting the weight and price. The `21` and five-digit weight is the barcode pattern used to identify the barcode and can be customized to ensure Odoo correctly interprets all barcodes for the business." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:21 -msgid "|UPC| and |EAN| barcodes **must** be `purchased from GS1 `_ to use these barcodes. GS1 is the **only** official provider of |UPC|/|EAN| and GS1 |GTINs| in the world." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:22 +msgid "Barcodes are also commonly used with Odoo's **Inventory** and **Barcode** apps." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:28 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:32 -msgid "Set up barcode nomenclature" +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:24 +msgid "Odoo **Barcode** supports |EAN|, Universal Product Code (UPC), and :doc:`GS1 ` formats. This document exclusively focuses on :ref:`default rules and patterns in Odoo `, which use |UPC| and |EAN| encoding." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:30 -msgid "To use default nomenclature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Barcode` section, click the checkbox next to :guilabel:`Barcode Scanner` to enable barcodes. Doing so installs the *Barcode* app in the database." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:29 +msgid "To use |UPC| and |EAN| barcodes for uniquely identifying products across the entire supply chain, they **must** be `purchased from GS1 `_." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:34 -msgid "Next, ensure that the :guilabel:`Default Nomenclature` setting is selected in the :guilabel:`Barcode Nomenclature` field. Then, click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:32 +msgid "In Odoo, custom barcode patterns can be defined to recognize barcodes specific to the company. Barcodes do not need to be purchased if used only within the company, such as in the :ref:`example ` where the barcode is written in the |EAN| format." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:52 +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:41 +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:14 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:34 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:14 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:26 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:19 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:13 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:104 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:56 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:8 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:13 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:44 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:56 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:11 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:13 +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:21 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:52 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:24 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:38 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:30 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:23 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:41 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:40 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:21 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:15 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:26 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:17 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:19 +#: ../../content/applications/inventory_and_mrp/purchase/products/temporary_reordering.rst:31 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:19 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:40 +msgid "To use default nomenclature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Barcode` section, tick the :guilabel:`Barcode Scanner` checkbox. Doing so installs the **Barcode** app in the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:44 +msgid "Next, in the :guilabel:`Barcode Nomenclature` field, ensure :guilabel:`Default Nomenclature` is selected. Then, click :guilabel:`Save`." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:-1 msgid "Enabled barcode setting with Default Nomenclature selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:41 -msgid "Once the nomenclature is saved and selected, the :menuselection:`Barcode Nomenclatures` settings can be accessed, via a hidden menu that is **only** discoverable after enabling :ref:`developer mode `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:45 -msgid "Once developer mode is enabled, navigate to :menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures` menu, and select :guilabel:`Default Nomenclature`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:48 -msgid "From this page, the :guilabel:`Barcode Nomenclature` is specified at the top as the `Default Nomenclature`." -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:51 -msgid "Under that, the :guilabel:`UPC/EAN Conversion` field is set to :guilabel:`Always`, by default. This setting determines if a |UPC|/|EAN| barcode should be automatically converted one way or another when trying to match a rule with the other encoding." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:55 -msgid "The other available options for this field are :guilabel:`Never`, :guilabel:`EAN-13 to UPC-A`, and :guilabel:`UPC-A to EAN-13`." +msgid "With the **Barcode** module installed, and the :guilabel:`Default Nomenclature` selected, the barcode actions using |UPC| and |EAN|, detailed in the :ref:`default nomenclature list `, are available for use. And, by default, Odoo automatically handles |UPC|/|EAN| conversion." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:59 -msgid "For |UPC|/|EAN| conversion to work for every barcode scanned, the setting in the :guilabel:`UPC/EAN Conversion` field **must** be set to :guilabel:`Always`." +msgid "Example: product weight barcode" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:62 -msgid "The last field at the top of the page is the :guilabel:`Is GS1 Nomenclature` field. For the :guilabel:`Default Nomenclature`, this field should remain unchecked. This is because the :guilabel:`Default Nomenclature` uses |UPC| and |EAN| encoding, *not* GS1 encoding." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:61 +msgid "To better understand how barcode nomenclature is used to identify products in Odoo, this example where product weight barcodes in |EAN| format are used to allow a :doc:`Point of Sale <../../../sales/point_of_sale>` business to automatically print barcodes, and calculate the price using the weight of the item." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:-1 -msgid "Default Nomenclature page setting fields." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:66 +msgid "To set up barcodes for weighted products, the following rule is used:" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:70 -msgid "Further down the page, there is a list showcasing the :guilabel:`Rule Name`, :guilabel:`Type`, :guilabel:`Encoding`, and :guilabel:`Barcode Pattern` for the *rules* and *barcode patterns* that Odoo supports for the default nomenclature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:74 -msgid "The :ref:`default nomenclature list ` contains all the information that can be condensed with a |UPC|/|EAN| barcode." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:80 -msgid "Use UPC/EAN barcodes in Odoo" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:82 -msgid "For product identification using |UPC|/|EAN| barcodes in Odoo, businesses **must** obtain `barcodes `_ purchased directly from GS1." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:86 -msgid "The |UPC| and |EAN| barcode formats are predominantly used in their own regions. |UPC| is used only in the United States and Canada, while |EAN| is used everywhere else globally." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:89 -msgid "A |UPC| is usually a 12-digit barcode used to identify most products, while |EAN| barcodes use 13-digit barcodes to identify products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:92 -msgid "|UPC| codes can be converted to |EAN| by prefixing them with a zero. In Odoo, by default, |UPC|/|EAN| barcodes are automatically converted one way or another when trying to match a rule with the other encoding." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:96 -msgid "Refer to the :ref:`default nomenclature list ` to see a comprehensive list of all barcode patterns and rules to follow." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:100 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:96 -msgid "Create rules" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:102 -msgid "|UPC| and |EAN| barcodes contain specific information in the barcode. Scanning these codes from the :ref:`default nomenclature list ` automatically fills corresponding data in the Odoo database." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:106 -msgid "Adding new barcode rules to this list ensures that non-standard (:dfn:`user-created`) formats are interpreted accurately." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:109 -msgid "To create new rules, first activate :ref:`developer mode `. Then, navigate to :menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures`. Select the :guilabel:`Default Nomenclature` list item." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:113 -msgid "On the :guilabel:`Default Nomenclature` page, select :guilabel:`Add a line` at the bottom of the table, which opens a :guilabel:`Create Rules` pop-up window to create a new rule." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:-1 -msgid "Create Rules pop-up window on Default Nomenclature page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:120 -msgid "The :guilabel:`Rule Name` field is used internally to identify what the barcode represents." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:122 -msgid "The :guilabel:`Sequence` field represents the priority of the rule; meaning the smaller the value, the higher the rule appears on the table." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:125 -msgid "The barcode :guilabel:`Type` field represents different classifications of information that can be understood by the system (e.g., :guilabel:`Package`, :guilabel:`Lot`, :guilabel:`Location`, :guilabel:`Coupon`, etc.)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:129 -msgid "The :guilabel:`Encoding` field specifies which encoding the barcode uses; this rule **only** applies if the barcode uses this specific encoding. The available :guilabel:`Encoding` options are: :guilabel:`EAN-13`, :guilabel:`EAN-8`, :guilabel:`UPC-A`, and :guilabel:`GS1-28`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:133 -msgid "The :guilabel:`Barcode Pattern` field represents how the sequence of letters or numbers is recognized by the system to contain information about the product. Odoo follows the sequential order of this table, and uses the first rule it matches, based on the sequence." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:138 -msgid "Barcode patterns can also define how numerical values, such as weight or price, are encoded in the barcode." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:141 -msgid "They are indicated by **{NNN}**, where `N` defines where the number's digits are encoded. *Floats* are also supported with the decimals, indicated by `D`, such as **{NNNDD}**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:144 -msgid "In this case, the barcode field on the associated records **must** show these digits as zeros." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:146 -msgid "After filling in the information, click the :guilabel:`Save & New` button to save the rule, and instantly start creating another rule. Or, click :guilabel:`Save & Close` to save the rule, and return to the table of rules." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:151 -msgid "When the :guilabel:`Barcode Pattern` field contains `.*`, it means it can contain **any** number of characters - those characters being **any** number or type of character." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:157 -msgid "Default nomenclature list" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:159 -msgid "The table below contains Odoo's list of :guilabel:`Default Nomenclature` rules. Barcode patterns are written in regular expressions." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:166 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:71 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:186 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 msgid "Rule Name" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:167 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 -msgid "Type" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:168 -msgid "Encoding" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:169 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:72 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:189 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 msgid "Barcode Pattern" msgstr "" +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:73 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "Field in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:74 +msgid "Weighted Barcodes 3 Decimals" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:75 +msgid "(21)....{NNDDD}" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:76 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 +msgid ":guilabel:`Barcode` field on product form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:79 +msgid "To better understand the barcode pattern for weighted products, consider the barcode, `2112345000008`:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:82 +msgid "`21`: code that identifies this a barcode for weighted products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:83 +msgid "`12345`: five digits (denoted by `.....` in the table above) that identify the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:84 +msgid "`00000`: five digits (denoted by `{NNDDD}` in the table) representing the weight of the product. On the product form, the five weight values **must** be `00000`. The first two digits are whole number values, and the last three digits are decimal values. For example, \"13.5 grams\" in the `{NNDDD}` format is `13500`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:88 +msgid "`8`: `check digit `_ for `211234500000`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:90 +msgid "Together, these components make up a 13-character |EAN| - 13 barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:92 +msgid "To configure the product barcode for `Pasta Bolognese`, the |EAN| barcode for weighted products, `2112345000008`, is entered in the :guilabel:`Barcode` field on the product form (accessible by going to :menuselection:`Inventory app --> Products --> Products`, and selecting the desired product). In addition, the :guilabel:`Unit of Measure` is set to :guilabel:`kg`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:-1 +msgid "Barcode field on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:101 +msgid "Next, a customer's bowl of pasta is weighed to be `1.5` kilograms. This generates a new barcode for the pasta, according to the weight: `211234501500`, which has a check digit of `2`. The new barcode is `2112345015002`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:-1 +msgid "Generated barcode that includes a weight of 1.5 kg." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:109 +msgid "Ensure the products scan properly, by navigating to the :menuselection:`Barcode app --> Operations`. Next, click any operation type, such as :guilabel:`Receipts`. Then, click the :guilabel:`New` button to create a draft stock move. Scan the product weight barcode, such as `2112345015002`, and if the intended product appears, the barcode setup is correct." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:-1 +msgid "Show successfully scanned barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:119 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:96 +msgid "Create rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:122 +msgid "Adding new rules is necessary for |UPC| and |EAN| formats that are **not** in Odoo's default list, since barcodes cannot be read successfully if there are unknown fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:125 +msgid "While new rules can be created, Odoo fields do **not** auto-populate with information from these rules. `Custom development `_ is required for this functionality." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:129 +msgid "To create a rule, first enable :ref:`developer mode `. Then, navigate to :menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures`, and select :guilabel:`Default Nomenclature`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:133 +msgid "On this page, configure the following optional fields:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:135 +msgid ":guilabel:`UPC/EAN Conversion`: determines if a |UPC|/|EAN| barcode should be automatically converted when matching a rule with another encoding. Options include :guilabel:`Always` (the default option), :guilabel:`Never`, :guilabel:`EAN-13 to UPC-A`, and :guilabel:`UPC-A to EAN-13`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:138 +msgid ":guilabel:`Is GS1 Nomenclature`: ensure this checkbox is **not** ticked, as the :guilabel:`Default Nomenclature` uses |UPC| and |EAN| encoding, *not* GS1 encoding." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:-1 +msgid "Default Nomenclature page setting fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:145 +msgid "On the :guilabel:`Default Nomenclature` page, click :guilabel:`Add a line` at the bottom of the table, which opens a :guilabel:`Create Rules` pop-up window to create a new rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:148 +msgid "The :guilabel:`Rule Name` field is used internally to identify what the barcode represents." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:150 +msgid "The :guilabel:`Sequence` field represents the priority of the rule; meaning the smaller the value, the higher the rule appears on the table." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:153 +msgid "The barcode :guilabel:`Type` field represents different classifications of information that can be understood by the system (e.g., :guilabel:`Package`, :guilabel:`Lot`, :guilabel:`Location`, :guilabel:`Coupon`, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:157 +msgid "The :guilabel:`Encoding` field specifies which encoding the barcode uses. This rule **only** applies if the barcode uses this specific encoding. The available :guilabel:`Encoding` options are: :guilabel:`EAN-13`, :guilabel:`EAN-8`, :guilabel:`UPC-A`, and :guilabel:`GS1-28`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:161 +msgid "The :guilabel:`Barcode Pattern` field represents how the sequence of letters or numbers is recognized by the system to contain information about the product. Sometimes, when a certain amount of digits are required, the number of `.` is shown. `N` represents whole number digits, and `D` represent decimal digits." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:167 +msgid "`1...` represents any 4-digit number that starts with 1. `NNDD` represents a two digit number with two decimal points. For example, `14.25` is 1425." +msgstr "" + #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:170 -msgid "Price Barcodes 2 Decimals" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:171 -msgid "Priced Product" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:172 -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:180 -msgid "EAN-13" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:173 -msgid "23.....{NNNDD}" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:174 -msgid "Discount Barcodes" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:175 -msgid "Discounted Product" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:176 -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:184 -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:188 -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:192 -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:196 -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:200 -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:204 -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:208 -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:212 -msgid "Any" +msgid "After filling in the information, click the :guilabel:`Save & New` button to save the rule, and instantly start creating another rule. Or, click :guilabel:`Save & Close` to save the rule, and return to the table of rules." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:177 -msgid "22{NN}" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:178 -msgid "Weight Barcodes 3 Decimals" +msgid "Default nomenclature list" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:179 -msgid "Weighted Product" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:181 -msgid "21.....{NNDDD}" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:182 -msgid "Customer Barcodes" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:183 -msgid "Client" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:185 -msgid "042" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:186 -msgid "Coupon & Gift Card Barcodes" +msgid "The table below contains Odoo's list of :guilabel:`Default Nomenclature` rules. Barcode patterns are written in regular expressions." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:187 -msgid "Coupon" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +msgid "Type" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:189 -msgid "043|044" +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:188 +msgid "Encoding" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:190 -msgid "Cashier Barcodes" +msgid "Price Barcodes 2 Decimals" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:191 -msgid "Cashier" +msgid "Priced Product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:192 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:200 +msgid "EAN-13" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:193 -msgid "041" +msgid "23.....{NNNDD}" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:194 -msgid "Location barcodes" +msgid "Discount Barcodes" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:195 +msgid "Discounted Product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:196 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:204 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:208 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:212 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:216 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:220 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:224 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:228 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:232 +msgid "Any" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:197 +msgid "22{NN}" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:198 +msgid "Weight Barcodes 3 Decimals" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:199 +msgid "Weighted Product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:201 +msgid "21.....{NNDDD}" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:202 +msgid "Customer Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:203 +msgid "Client" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:205 +msgid "042" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:206 +msgid "Coupon & Gift Card Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:207 +msgid "Coupon" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:209 +msgid "043|044" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:210 +msgid "Cashier Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:211 +msgid "Cashier" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:213 +msgid "041" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:214 +msgid "Location barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:215 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 msgid "Location" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:197 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:217 msgid "414" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:198 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:218 msgid "Package barcodes" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:199 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:219 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 msgid "Package" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:201 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:221 msgid "PACK" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:202 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:222 msgid "Lot barcodes" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:203 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:223 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 msgid "Lot" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:205 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:225 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:143 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:39 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:40 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:41 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:41 msgid "10" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:226 msgid "Magnetic Credit Card" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:207 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:227 msgid "Credit Card" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:209 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:229 msgid "%.*" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:210 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:230 msgid "Product Barcodes" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:211 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:231 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 msgid "Unit Product" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:213 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:233 msgid ".*" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:216 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:236 +msgid "When the :guilabel:`Barcode Pattern` contains `.*`, it means it can contain any number or type of characters." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:240 msgid ":doc:`gs1_nomenclature`" msgstr "" @@ -600,6 +689,10 @@ msgstr "" msgid ":ref:`Why's my barcode not working? `" msgstr "" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:32 +msgid "Set up barcode nomenclature" +msgstr "" + #: ../../content/applications/inventory_and_mrp/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 "" @@ -761,12 +854,6 @@ msgstr "" msgid "(01)(\\\\d{14})" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 -msgid ":guilabel:`Barcode` field on product form" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 msgid "GTIN of contained trade items" msgstr "" @@ -776,7 +863,7 @@ msgid "(02)(\\\\d{14})" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:3 msgid "Packaging" msgstr "" @@ -1042,8 +1129,8 @@ msgid "(91) ([!\"%-/0-9:-?A-Z_a-z]{0,90})" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:115 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:77 msgid "Package type" msgstr "" @@ -1093,14 +1180,10 @@ msgstr "" msgid "A.I." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 -msgid "Field in Odoo" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:78 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:78 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:22 msgid "Product" msgstr "" @@ -1133,60 +1216,6 @@ msgstr "" msgid ":guilabel:`Lot` on Detailed Operations pop-up" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:52 -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:41 -#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:14 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:53 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:21 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:35 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:38 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:13 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:17 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:13 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:11 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:22 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:36 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:36 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:17 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:19 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:17 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:104 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:49 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:22 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:48 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:21 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:106 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:15 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:11 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:8 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:12 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:20 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:44 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:45 -#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:13 -#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:52 -#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:24 -#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:38 -#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:30 -#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:23 -#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:41 -#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:40 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:21 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:21 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:15 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:26 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:17 -#: ../../content/applications/inventory_and_mrp/purchase/products/temporary_reordering.rst:31 -#: ../../content/applications/inventory_and_mrp/quality/quality_management/failure_locations.rst:19 -msgid "Configuration" -msgstr "" - #: ../../content/applications/inventory_and_mrp/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 "" @@ -2303,942 +2332,1052 @@ msgstr "" msgid "Product management" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment.rst:5 -msgid "Product replenishment" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure.rst:5 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:35 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:51 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:53 +msgid "Configure product" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:3 -msgid "Replenish on order (MTO)" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:189 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:159 +msgid "Packages" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:9 -msgid "*Replenish on order*, also known as *MTO* (make to order), is a replenishment strategy that creates a draft order for a product every time a sales order is created for it. For products that are purchased from a vendor, a request for quotation (RFQ) is created, while a sales order for a product manufactured in-house triggers the creation of a manufacturing order. The creation of a |RFQ| or manufacturing order occurs every time a sales order is created, regardless of the current stock level of the product being ordered." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:7 +msgid "A *package* is a physical container holding one or more products. Packages can also be used to store items in bulk." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:17 -msgid "Unarchive the Replenish on Order (MTO) route" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:10 +msgid "Packages are commonly used for the following purposes:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:19 -msgid "By default, Odoo sets the |MTO| route as *archived*. This is because |MTO| is a somewhat niche workflow that is only used by certain companies. However, it is easy to unarchive the route in just a few simple steps." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:12 +msgid ":ref:`Grouping products to move them in bulk `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:23 -msgid "To do so, begin by navigating to :menuselection:`Inventory --> Configuration --> Routes`. On the :guilabel:`Routes` page, click the :guilabel:`Filters` button and select the :guilabel:`Archived` option. This shows all routes that are currently archived." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:13 +msgid ":ref:`Shipping to customers `: configure package types to align with shipping carriers' size and weight requirements, streamlining the packing process, and ensuring compliance with carrier shipping specifications." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:-1 -msgid "The archived filter on the Routes page." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:16 +msgid "Storing items in bulk." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:31 -msgid "Enable the checkbox next to :guilabel:`Replenish on Order (MTO)`, then click the :guilabel:`Action` button to reveal a drop-down menu. From the drop-down menu, select :guilabel:`Unarchive`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:18 +msgid "*Package use* is a field on the package form in Odoo that is only visible by enabling the *Batch Transfers* and *Packages* features (:menuselection:`Inventory app --> Configuration --> Settings`)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:-1 -msgid "The unarchive action on the Routes page." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:21 +msgid "By default, the *Package Use* field on a packages form is set to *Disposable Box*. Change this field to *Reusable Box* **only** when configuring packages for :ref:`cluster pickings `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:38 -msgid "Finally, remove the :guilabel:`Archived` filter from the :guilabel:`Search...` bar. The :guilabel:`Routes` page will now show all available routes, including :guilabel:`Replenish on Order (MTO)`, which is now selectable on the inventory tab of each product page." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:25 +msgid "*Package type* is an optional feature used for :doc:`calculating shipping cost <../../shipping_receiving/setup_configuration>`, based on real shipping weight. Create package types to include the weight of the package itself (e.g. boxes, pallets, other shipping containers) in shipping cost calculations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:-1 -msgid "The MTO route appears on the Routes page after unarchiving it." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:31 +msgid "While packages are commonly used in the :doc:`three-step delivery route <../../shipping_receiving/daily_operations/delivery_three_steps>`, they can be used in any workflow involving storable products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:47 -msgid "Configure a product to use the MTO route" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:40 +msgid "To use packages, first go to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Operations` heading, activate the :guilabel:`Packages` feature. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:49 -msgid "With the |MTO| route unarchived, products can now be properly configured to use replenish on order. To do so, begin by going to :menuselection:`Inventory --> Products --> Products`, then select an existing product, or click :guilabel:`Create` to configure a new one." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:-1 +msgid "Activate the *Packages* setting in Inventory > Configuration > Settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:53 -msgid "On the product page, select the :guilabel:`Inventory` tab and enable the :guilabel:`Replenish on Order (MTO)` route in the :guilabel:`Routes` section, along with one other route." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:51 +msgid "Pack items" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:57 -msgid "The :guilabel:`Replenish on Order (MTO)` route **does not** work unless another route is selected as well. This is because Odoo needs to know how to replenish the product when an order is placed for it (buy it, manufacture it, etc.)." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:53 +msgid "Products can be added to packages in any transfer by:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:-1 -msgid "Select the MTO route and a second route on the Inventory tab." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:55 +msgid "Clicking each :ref:`Detailed Operations ` icon on the product line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:65 -msgid "If the product is purchased from a vendor to fulfill sales orders, enable the :guilabel:`Can be Purchased` checkbox under the product name. Doing so makes the :guilabel:`Purchase` tab appear alongside the other settings tabs below." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:57 +msgid "Using the :ref:`Put in Pack ` button to place everything in the transfer into a package." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:69 -msgid "Select the :guilabel:`Purchase` tab and specify a :guilabel:`Vendor` and the :guilabel:`Price` they sell the product for." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:63 +msgid "Detailed operations" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:-1 -msgid "Enable \"Can be Purchased\" and specify a vendor." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:65 +msgid "On any warehouse transfer (e.g. receipt, delivery order), add a product to a package by clicking the :guilabel:`⦙≣ (bulleted list)` icon in the :guilabel:`Operations` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:76 -msgid "If the product is manufactured, make sure that it has a bill of materials (BOM) configured for it. To do so, click the :guilabel:`Bill of Materials` smart button at the top of the screen, then click :guilabel:`Create` on the :guilabel:`Bill of Materials` page to configure a new |BOM| for the product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:-1 +msgid "Show \"Detailed Operations\" icon in the product line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:81 -msgid "On the blank |BOM| form, add the components used to manufacture the product on the :guilabel:`Components` tab, along with the operations required for the manufacturing workflow on the :guilabel:`Operations` tab." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:72 +msgid "Doing so opens the :guilabel:`Detailed Operations` pop-up window for the :guilabel:`Product`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:85 -msgid "Finally, click :guilabel:`Save` to save the |BOM|." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:74 +msgid "To put the :guilabel:`Product` in a package, click :guilabel:`Add a line`, and assign the product to a :guilabel:`Destination Package`. Select an existing package, or create a new one by typing the name of the new package, then select :guilabel:`Create...`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:88 -msgid "Fulfill a sales order using the MTO route" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:82 +msgid "Assign a package to \"Destination Package\" field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:90 -msgid "After configuring a product to use the |MTO| route, a replenishment order is created for it every time a sales order including the product is confirmed. The type of order created depends on the second route selected in addition to |MTO|." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:82 +msgid "Twelve units of `Acoustic Bloc Screen` are placed in `PACK0000001`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:94 -msgid "For example, if *Buy* was the second route selected, then a purchase order is created upon confirmation of a sales order." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:84 +msgid "Then, specify the quantity of items to go into the package in the :guilabel:`Done` column. Repeat the above steps to place the :guilabel:`Product` in different packages. Once finished, click :guilabel:`Confirm` to close the window." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:98 -msgid "When the |MTO| route is enabled for a product, a replenishment order is always created upon confirmation of a sales order. This is the case even if there is enough stock of the product on-hand to fulfill the sales order, without buying or manufacturing additional units of it." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:89 +msgid ":doc:`Ship one order in multiple packages <../../shipping_receiving/setup_configuration/multipack>`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:102 -msgid "While the |MTO| route can be used in unison with a variety of other routes, the *Buy* route is used as the example for this workflow. Begin by navigating to the :menuselection:`Sales` app, then click :guilabel:`Create`, which opens a blank quotation form." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:95 +msgid "Put in pack" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:106 -msgid "On the blank quotation form, add a :guilabel:`Customer`, then click :guilabel:`Add a product` under the :guilabel:`Order Lines` tab, and enter a product that has been configured to use the *MTO* and *Buy* routes. Click :guilabel:`Confirm` and the quotation is turned into a sales order." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:97 +msgid "Alternatively, click the :guilabel:`Put in Pack` button on **any** warehouse transfer to create a new package, and place all the items in the transfer in that newly-created package." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:110 -msgid "A :guilabel:`Purchase` smart button now appears in the top-right corner of the sales order. Clicking it opens the |RFQ| associated with the sales order." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:101 +msgid "The :guilabel:`Put in Pack` button appears on receipts, delivery orders, and other transfer forms with the *Packages* feature enabled in :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:113 -msgid "Click :guilabel:`Confirm Order` to confirm the |RFQ|, and turn it into a purchase order. A green :guilabel:`Receive Products` button now appears at the top of the purchase order. Once the products are received, click :guilabel:`Receive Products` to register them into inventory." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:109 +msgid "Image of the \"Put in Pack\" button being clicked." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:117 -msgid "Return to the sales order by clicking the :guilabel:`SO` breadcrumb, or by navigating to :menuselection:`Sales --> Orders --> Orders`, and selecting the sales order." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:109 +msgid "In batch transfer `BATCH/00003`, the :guilabel:`Put in Pack` button was clicked to create a new package, `PACK0000002`, and assign all items to it in the :guilabel:`Destination Package` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:120 -msgid "Finally, click the :guilabel:`Delivery` smart button in the top-right of the order to be taken to the delivery order. Once the products have been shipped to the customer, click :guilabel:`Validate` to confirm the delivery." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:117 +msgid "Create package types by navigating to :menuselection:`Inventory app --> Configuration --> Package Types`, in order to set custom dimensions and weight limits. This feature is mainly used to calculate package weights for shipping costs." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:3 -msgid "Reordering rules" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:122 +msgid ":doc:`Shipping carriers <../../shipping_receiving/setup_configuration/third_party_shipper>`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:9 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:123 +msgid ":doc:`../../shipping_receiving/setup_configuration`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:13 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:125 +msgid "On the :guilabel:`Package Types` list, clicking :guilabel:`New` opens a blank package type form. The fields of the form are as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:19 -msgid "`Odoo Tutorials: Automatic Reordering Rules `_" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:128 +msgid ":guilabel:`Package Type` (required): define the package type's name." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:20 -msgid "`Odoo Tutorials: Manual Reordering Rules `_" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:129 +msgid ":guilabel:`Size`: define the dimensions of the package in millimeters (mm). The fields, from left to right, define the :guilabel:`Length`, :guilabel:`Width`, and :guilabel:`Height`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:23 -msgid "Configure products for reordering rules" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:131 +msgid ":guilabel:`Weight`: weight of an empty package (e.g. an empty box, pallet)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:25 -msgid "In order to use reordering rules for a product, it must first be correctly configured. Begin by navigating to :menuselection:`Inventory app --> Products --> Products`, then select an existing product, or create a new one by clicking :guilabel:`New`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:134 +msgid "Odoo calculates the package's weight by adding the weight of the empty package plus the weight of the item(s), which can be found in the :guilabel:`Weight` field, in the :guilabel:`Inventory` tab, of each product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:29 -msgid "On the product form, under the :guilabel:`General Information` tab, make sure 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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:138 +msgid ":guilabel:`Max Weight`: maximum shipping weight allowed in the package." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 -msgid "Set the Product Type as Storable." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:139 +msgid ":guilabel:`Barcode`: define a barcode to identify the package type from a scan." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:37 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:140 +msgid ":guilabel:`Company`: specify a company to make the package type available **only** at the selected company. Leave the field blank if it is available at all companies." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 -msgid "Select one or more routes on the Inventory tab." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:142 +msgid ":guilabel:`Carrier`: specify the intended shipping carrier for this package type." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:44 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:143 +msgid ":guilabel:`Carrier Code`: define a code that is linked to the package type." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 -msgid "Specify a vendor and price on the Purchase tab." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:-1 +msgid "Package type for FedEx's 25 kilogram box." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:53 -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)`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:152 +msgid "Cluster packages" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:57 -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:`New` to configure a new :abbr:`BoM (Bill of Materials)`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:154 +msgid "To use *cluster packages*, first navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and activate the :guilabel:`Batch Transfers` feature, located in the :guilabel:`Operations` section. Doing so makes the *Package Use* field become visible on a package form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 -msgid "The Bill of Materials smart button on a product form." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:-1 +msgid "Activate the *Batch Transfers* feature in Inventory > Configuration > Settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:66 -msgid "Create new reordering rules" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:163 +msgid "Add new packages by going to :menuselection:`Inventory app --> Products --> Packages`. Then, click :guilabel:`New`, or select an existing package. Doing so opens the package form, which contains the following fields:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:68 -msgid "To create a new reordering rule, navigate to :menuselection:`Inventory app --> Configuration --> Reordering Rules`, then click :guilabel:`New`, and fill out the new line as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:167 +msgid ":guilabel:`Package Reference` (required): name of the package." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:71 -msgid ":guilabel:`Product`: The product that is replenished by the rule." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:168 +msgid ":guilabel:`Package Type`: used for :ref:`configuring shipping boxes to ship to the customer `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:72 -msgid ":guilabel:`Location`: The location where the product is stored." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:172 +msgid ":guilabel:`Package Type` is unnecessary for configuring packages for cluster pickings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:73 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:174 +msgid ":guilabel:`Shipping Weight`: used to input the weight of the package after measuring it on a scale." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:76 -msgid ":guilabel:`Max Quantity`: The maximum quantity that stock is replenished up to." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:176 +msgid ":guilabel:`Company`: specify a company to make the package available **only** at the selected company. Leave the field blank if the package is available at all companies." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:77 -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)." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:178 +msgid ":guilabel:`Location`: current location of the package." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:79 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:179 +msgid ":guilabel:`Pack Date`: the date the package was created." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 -msgid "The form for creating a new reordering rule." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:180 +msgid ":guilabel:`Package Use`: choose :guilabel:`Reusable` for packages used for moving products within the warehouse; :guilabel:`Disposable` for packages used to ship products to customers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:87 -msgid "Reordering rules can also be created from each product form. To do so, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product. Then, click the :guilabel:`Reordering Rules` smart button, and click :guilabel:`New` to fill out the new line, as detailed above." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:-1 +msgid "Display package form to create a cluster pack." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:92 -msgid "For advanced usage of reordering rules, learn about the following reordering rule fields:" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/package.rst:188 +msgid ":doc:`Using cluster packages <../../shipping_receiving/picking_methods/cluster>`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:94 -msgid ":ref:`Trigger `" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:7 +msgid "In Odoo *Inventory*, *packaging* refers to disposable containers holding multiple units of a specific product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:95 -msgid ":ref:`Visibility days `" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:10 +msgid "For example, different packages for cans of soda, such as a 6-pack, a 12-pack, or a case of 36, **must** be configured on the individual product form. This is because packagings are product specific, not generic." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:96 -msgid ":ref:`Route `" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:15 +msgid "Packaging can be used in conjunction with Odoo :ref:`Barcode `. When receiving products from suppliers, scanning the packaging barcode automatically adds the number of units in the packaging to the internal count of the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:99 -msgid "0/0/1 reordering rule" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:22 +msgid "To use packagings, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Then, under the :guilabel:`Products` heading, enable the :guilabel:`Product Packagings` feature, and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:101 -msgid "The *0/0/1* reordering rule is a specialty rule used to replenish a product that is not kept on-hand, each time a sales order (SO) is confirmed for that product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:-1 +msgid "Enable packagings by selecting \"Product Packagings\"." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:105 -msgid "The 0/0/1 reordering rule is similar to the *Replenish on Order (MTO)* route, in that both workflows are used to replenish a product upon confirmation of an |SO|." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:33 +msgid "Create packaging" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:108 -msgid "The main difference between the two methods is that the *Replenish on Order* route automatically reserves the product for the |SO| that caused it to be replenished. This means the product **cannot** be used for a different |SO|." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:35 +msgid "Packagings can be created directly on the product form, or from the :guilabel:`Product Packagings` page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:112 -msgid "The 0/0/1 reordering rule does not have this limitation. A product replenished using the rule is not reserved for any specific |SO|, and can be used as needed." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:39 +msgid "From product form" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:115 -msgid "Another key difference is that replenishment orders created by the *Replenish on Order* route are linked to the original |SO| by a smart button at the top of the order. When using the 0/0/1 reordering rule, a replenishment order is created, but is not linked to the original |SO|." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:41 +msgid "Create packagings on a product form by going to :menuselection:`Inventory app --> Products --> Products`, and select the desired product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:119 -msgid "See the :doc:`Replenish on Order (MTO) ` documentation for a full overview of the MTO route." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:44 +msgid "Under the :guilabel:`Inventory` tab, scroll down to the :guilabel:`Packaging` section, and click :guilabel:`Add a line`. In the table, fill out the following fields:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:121 -msgid "To create a 0/0/1 reordering rule, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:47 +msgid ":guilabel:`Packaging` (required): name of packaging that appears on sales/purchase orders as a packaging option for the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:124 -msgid "At the top of the product's page, click the :icon:`fa-refresh` :guilabel:`Reordering Rules` smart button to open the :guilabel:`Reordering Rules` page for the product. On the resulting page, click :guilabel:`New` to begin configuring a new reordering rule." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:49 +msgid ":guilabel:`Contained quantity` (required): amount of product in the packaging." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:128 -msgid "In the :guilabel:`Location` field of the new reordering rule, select the location in which replenished products should be stored. By default, this location is set to :guilabel:`WH/Stock`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:50 +msgid ":guilabel:`Unit of Measure` (required): measurement unit for quantifying the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:131 -msgid "In the :guilabel:`Route` field, select the route the rule should use to replenish the item. For example, if the product should be purchased from a vendor, select the :guilabel:`Buy` route." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:51 +msgid ":guilabel:`Sales`: check this option for packagings intended for use on sales orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:134 -msgid "In the :guilabel:`Min Quantity` field and :guilabel:`Max Quantity` field, leave the values set to `0.00`. In the :guilabel:`To Order` field, enter a value of `1.00`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:52 +msgid ":guilabel:`Purchase`: check this option for packagings intended for use on purchase orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 -msgid "A 0/0/1 reordering rule." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:55 +msgid "Access additional fields in the :guilabel:`Packaging` table below by clicking the |adjust| icon to the far-right of the column titles in the :guilabel:`Packaging` section, and selecting the desired options from the drop-down menu that appears." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:141 -msgid "With the reordering rule configured using these values, each time an |SO| causes the forecasted quantity of the product to fall below the :guilabel:`Min Quantity` of `0.00`, the selected :guilabel:`Route` is used to replenish the product in one-unit increments, back up to the :guilabel:`Max Quantity` of `0.00`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:59 +msgid ":guilabel:`Barcode`: identifier for tracing packaging in stock moves or pickings, using the :ref:`Barcode app `. Leave blank if not in use." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:147 -msgid "A picture frame is configured with a 0/0/1 reordering rule that uses the *Buy* route. Zero units of the picture frame are kept on-hand at any given time." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:61 +msgid ":guilabel:`Company`: indicates the packaging is only available at the selected company. Leave blank to make the packaging available across all companies." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:150 -msgid "An |SO| is confirmed for one unit of the picture frame, which causes the forecasted quantity to drop to `-1.00`. This triggers the reordering rule, which automatically creates a |PO| for one unit of the picture frame." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:65 +msgid "To create a packaging type for six units of the product, `Grape Soda`, begin by clicking :guilabel:`Add a line`. In the line, name the :guilabel:`Packaging` `6-pack`, and set the :guilabel:`Contained quantity` to `6`. Repeat this process for additional packagings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:154 -msgid "Once the product is received from the vendor, the forecasted quantity of the picture frame returns to `0.00`. There is now one picture frame on-hand, but it is not reserved for the |SO| which triggered its purchase. It can be used to fulfill that |SO|, or reserved for a different order." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:0 +msgid "Create 6-pack case for product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:162 -msgid "Trigger" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:74 +msgid "From product packagings page" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:164 -msgid "When stock falls below the reordering rule's minimum, set the reordering rule's *trigger* to *automatic* to automatically create purchase or manufacturing orders to replenish stock." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:76 +msgid "To view all packagings that have been created, go to :menuselection:`Inventory app --> Configuration --> Product Packagings`. Doing so reveals the :guilabel:`Product Packagings` page with a complete list of all packagings that have been created for all products. Create new packagings by clicking :guilabel:`New`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:167 -msgid "Alternatively, setting the reordering rule's trigger to *manual* displays the product and forecasted stock on the *replenishment dashboard*, where the procurement manager can review the stock levels, lead times, and forecasted dates of arrival." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:82 +msgid "Two soda products, `Grape Soda` and `Diet Coke`, have three types of packagings configured. On the :guilabel:`Product Packagings` page, each product can be sold as a `6-Pack` that contains 6 products, as a `12-Pack` of 12 products, or as a `Case` of 32 products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:172 -msgid ":doc:`strategies`" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:0 +msgid "List of different packagings for products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:175 -msgid "The replenishment dashboard is accessible by going to :menuselection:`Inventory app --> Operations --> Replenishment`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:91 +msgid "Partial reservation" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:178 -msgid "To enable the :guilabel:`Trigger` field, go to :menuselection:`Inventory app --> Configuration --> Reordering Rules`. Then, click the :guilabel:`(slider)` icon, located to the far-right of the column titles, and enable the :guilabel:`Trigger` option from the additional options drop-down menu that appears." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:93 +msgid "After :ref:`completing the packaging setup `, packagings can be reserved in full or partial quantities for outgoing shipments. Partial packaging flexibility expedites order fulfillment by allowing the immediate shipment of available items, while awaiting the rest." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 -msgid "Enable the Trigger field by toggling it in the additional options menu" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:98 +msgid "To configure packaging reservation methods, go to :menuselection:`Inventory app --> Configuration --> Product Categories`. Then, click :guilabel:`New`, or select the desired product category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:187 -msgid "In the :guilabel:`Trigger` column, select :guilabel:`Auto` or :guilabel:`Manual`. Refer to the sections below to learn about the different types of reordering rules." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:101 +msgid "On the product category's form, in the :guilabel:`Logistics` section, :guilabel:`Reserve Packagings` can be set to :guilabel:`Reserve Only Full Packagings` or :guilabel:`Reserve Partial Packagings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:191 -msgid "Auto" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:105 +msgid "To see the :guilabel:`Reserve Packaging` field, the :guilabel:`Product Packaging` feature **must** be enabled. To enable this feature, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll to the :guilabel:`Products` section, tick the :guilabel:`Product Packagings` checkbox, and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:193 -msgid "Automatic reordering rules, configured by setting the reordering rule's :guilabel:`Trigger` field to :guilabel:`Auto`, generates purchase or manufacturing orders when:" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:-1 +msgid "Show Reserve Packagings field on the product categories page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:196 -msgid "the scheduler runs, and the *On Hand* quantity is below the minimum" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:115 +msgid "To better evaluate the options based on business needs, consider the following example:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:197 -msgid "a sales order is confirmed, and lowers the *Forecasted* quantity of the product below the minimum" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:117 +msgid "a product is sold in twelve units per packaging." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:201 -msgid "The scheduler is set to run once a day, by default." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:118 +msgid "an order demands two packagings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:203 -msgid "To manually trigger a reordering rule before the scheduler runs, ensure :ref:`developer mode ` is enabled, and select :menuselection:`Inventory app --> Operations --> Run Scheduler`. Then, click the purple :guilabel:`Run Scheduler` button on the pop-up window that appears." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:119 +msgid "there are only twenty-two units in stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:208 -msgid "Be aware that this also triggers any other scheduled actions." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:121 +msgid "When :guilabel:`Reserve Only Full Packagings` is selected, only twelve units are reserved for the order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:211 -msgid "The product, `Office Lamp`, has an automatic reordering rule set to trigger when the forecasted quantity falls below the :guilabel:`Min Quantity` of `5.00`. Since the current :guilabel:`Forecast` is `55.00`, the reordering rule is **not** triggered." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:124 +msgid "Conversely, when :guilabel:`Reserve Partial Packagings` is selected, twenty-two units are reserved for the order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:0 -msgid "Show automatic reordering rule from the Reordering Rule page." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:128 +msgid "Apply packagings" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:219 -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 app --> Orders --> Requests for Quotation`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:130 +msgid "When creating a sales order in the :menuselection:`Sales` app, specify the packagings that should be used for the product. The chosen packaging is displayed on the :abbr:`SO (Sales Order)` under the :guilabel:`Packaging` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:223 -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 app --> Operations --> Manufacturing Orders`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:135 +msgid "18 cans of the product, `Grape Soda`, is packed using three 6-pack packagings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:227 -msgid "When no route is selected, Odoo selects the :guilabel:`Route` specified in the :guilabel:`Inventory` tab of the product form." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:0 +msgid "Assign packagings on the Sales Order Line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:233 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:215 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:234 -msgid "Manual" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:144 +msgid "Routes for packaging" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:235 -msgid "Manual reordering rules, configured by setting the reordering rule's :guilabel:`Trigger` field to :guilabel:`Manual`, lists a product on the replenishment dashboard when the forecasted quantity falls below a specified minimum. Products on this dashboard are called *needs*, because they are needed to fulfill upcoming sales orders, but the forecasted quantity is not enough." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:146 +msgid "When receiving packagings, by default, they follow the warehouse's :doc:`configured reception route <../../shipping_receiving/daily_operations>`. To **optionally** set up a packaging-specific route, go to :menuselection:`Inventory app --> Configuration --> Routes`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:240 -msgid "The replenishment dashboard, accessible by navigating to :menuselection:`Inventory app --> Operations --> Replenishment`, considers sales order deadlines, forecasted stock levels, and vendor lead times. It displays needs **only** when it is time to reorder items." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:151 +msgid "The *Product Packagings*, *Storage Locations*, and *Multi-Step Routes* features (found by going to :menuselection:`Inventory app --> Configuration --> Settings`) **must** be activated, and saved." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:245 -msgid "If the one-day window for ordering products is too short, skip to the :ref:`visibility days ` section to make the need appear on the replenishment dashboard a specified number of days in advance." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:156 +msgid ":doc:`../../shipping_receiving/daily_operations/use_routes`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:249 -msgid "When a product appears on the replenishment dashboard, clicking the :guilabel:`Order Once` button generates the purchase or manufacturing order with the specified amounts :guilabel:`To Order`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:159 +msgid "Create route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 -msgid "Click the Order Once button on the replenishment dashboard to replenish stock." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:161 +msgid "On the :guilabel:`Routes` page, click :guilabel:`New`, or select a route that is **not** for a warehouse. Next, in the :guilabel:`Applicable on` section, tick the :guilabel:`Packagings` checkbox." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:259 -msgid "Visibility days" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:168 +msgid "Create route for a packaging." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:262 -msgid "Ensure :doc:`lead times <../../shipping_receiving/advanced_operations_shipping/scheduled_dates>` are understood before proceeding with this section." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:168 +msgid "Route with \"Packagings\" selected, with \"Products\" and \"Warehouses\" not selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:265 -msgid "When :ref:`manual reordering rules ` are assigned to a product, *visibility days* make the product appear on the replenishment dashboard (:menuselection:`Inventory app --> Operations --> Replenishment`) a certain number of days in advance." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:171 +msgid "Apply route on packaging" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:271 -msgid "A product has a manual reordering rule set to trigger when the stock level falls below four units. The current on-hand quantity is ten units." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:173 +msgid "Then, to apply the route, go to :menuselection:`Inventory app --> Products --> Products`, and select the product that uses packaging." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:274 -msgid "The current date is February 20th, and the *delivery date* on a sales order (in the :guilabel:`Other Info` tab) is March 3rd — twelve days from the current date." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:176 +msgid "In the product form, switch to the :guilabel:`Inventory` tab. In the :guilabel:`Packaging` section that contains :ref:`configured packagings `, click the |adjust| icon. Tick the :guilabel:`Routes` checkbox to make the column visible in the :guilabel:`Packaging` table." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:277 -msgid "The :ref:`vendor lead time ` is four days, and the :ref:`purchase security lead time ` is one day." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:181 +msgid "In the :guilabel:`Routes` field, select the packaging-specific route. Repeat these steps for all packaging intended to use the route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:281 -msgid "When the :guilabel:`Visibility Days` field of the reordering rule is set to zero, the product appears on the replenishment dashboard five days before the delivery date, which, in this case, is February 27th." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:-1 +msgid "Set route on a packaging." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 -msgid "Graphic representing when the need appears on the replenishment dashboard: Feb 27th." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:69 +msgid "Product type" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:289 -msgid "To see the product on the replenishment dashboard for the current date, February 20, set the :guilabel:`Visibility Days` to `7.00`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:7 +msgid "Define *product types* in Odoo to track products in varying levels of detail." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:292 -msgid "To determine the amount of visibility days needed to see a product on the replenishment dashboard, subtract *today's date* from the *date the need appears* on the replenishment dashboard." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:9 +msgid "Classify products as *storable* to track stock counts, allowing users to trigger :doc:`reordering rules <../../warehouses_storage/replenishment/reordering_rules>` for generating purchase orders. *Consumable* products are assumed to always be in stock, and *service* products are performed and served by the business." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:295 -msgid "Visibility~days = Need~appears~date - Today's~date" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:15 +msgid "`Odoo Tutorials: Product Type `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:300 -msgid "Referring to the example above, today's date is February 20th, and the need for the product appears on February 27th." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:18 +msgid "Set product type" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:303 -msgid "(February 27 - February 20 = 7 days)" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:20 +msgid "To set a product type, go to :menuselection:`Inventory app --> Products --> Products`, and select the desired product from the list." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:305 -msgid "Incorrectly setting the :guilabel:`Visibility Days` fewer than seven days in this case results in the need **not** appearing on the replenishment dashboard." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:23 +msgid "On the product form, in the :guilabel:`Product Type` field, select:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:0 -msgid "Show the replenishment dashboard with the correct and incorrect visibility days set." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:25 +msgid ":guilabel:`Storable Product` for products tracked with stock counts. Only storable products can trigger reordering rules for generating purchase orders;" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:315 -msgid "Route" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:29 +msgid "Choose :guilabel:`Storable Product` if it is necessary to track a product's stock at various locations, inventory valuations, or if the product has lots and/or serial numbers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:317 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:32 +msgid ":guilabel:`Consumable` for products that are always assumed to be in stock, whose quantities are not necessary to track or forecast (e.g. nails, toilet paper, coffee, etc.). Consumables are replaceable and essential, but exact counts are unnecessary; or" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:321 -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 app --> Configuration --> Reordering Rules`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:35 +msgid ":guilabel:`Service` for sellable service products that are performed, and not tracked with stock counts (i.e. maintenance, installation, or repair services)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:325 -msgid "By default, the :guilabel:`Route` column is hidden on the :guilabel:`Reordering Rules` page." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:0 +msgid "Set a product type on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:327 -msgid "Reveal the :guilabel:`Route` column by selecting the :guilabel:`(slider)` icon to the far-right of the column titles, and checking the :guilabel:`Route` option from the drop-down menu that appears." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:43 +msgid "The product types listed above are part of the standard *Inventory* app. For access to the fields below, :ref:`install ` the corresponding apps **in addition** to *Inventory*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:330 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:46 +msgid ":guilabel:`Booking Fees`: charge a fee for booking appointments through the *Appointments* app. Requires the installation of the *Calendar* app and *Pay to Book* (`appointment_account_payment`) module" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:-1 -msgid "Select a preferred route from the drop-down." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:49 +msgid ":guilabel:`Combo`: create discounted products sold in a bundle. Requires the installation of the *PoS* app." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:338 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:51 +msgid ":guilabel:`Event Ticket`: sold to attendees wanting to go to an event. Requires the installation of the *Events* app" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:3 -msgid "Selecting a replenishment strategy" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:53 +msgid ":guilabel:`Event Booth`: sold to partners or sponsors to set up a booth at an event. Requires the installation of the *Events* app" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:10 -msgid "In Odoo, there are two strategies for automatically replenishing inventory: *reordering rules* and the *make to order (MTO)* route. Although these strategies differ slightly, they both have similar consequences: triggering the automatic creation of a |PO| or |MO|. The choice of which strategy to use depends on the business's manufacturing and delivery processes." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:55 +msgid ":guilabel:`Course`: sell access to an educational course. Requires the installation of the *eLearning* app" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:16 -msgid "Terminology" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:59 +msgid "Compare types" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:19 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:56 -msgid "Replenishment report and reordering rules" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:61 +msgid "Below is a summary of how each product type affects common *Inventory* operations, like transfers, reordering rules, and the forecasted report. Click the chart item with an asterisk (*) to navigate to detailed sections." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:21 -msgid "The replenishment report is a list of all products that have a negative forecast quantity." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:70 +msgid "Storable" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:23 -msgid "*Reordering rules* are used to ensure there's always a minimum amount of a product in-stock, in order to manufacture products and/or fulfill sales orders. When the stock level of a product reaches its minimum, Odoo automatically generates a purchase order with the quantity needed to reach the maximum stock level." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:71 +msgid "Consumable" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:28 -msgid "Reordering rules can be created and managed in the replenishment report, or from the product form." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:72 +msgid "Service" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:33 -msgid "Make to order" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:73 +msgid "Physical product" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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**." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:74 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:75 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:83 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:104 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:107 +msgid "Yes" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:80 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:109 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:112 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:113 +msgid "No" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:118 +msgid "On-hand quantity" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:78 +msgid ":ref:`Yes* `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:79 +msgid ":ref:`Yes* `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:58 -msgid "To access the replenishment report, go to :menuselection:`Inventory app --> Operations --> Replenishment.`" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:81 +msgid ":doc:`Inventory valuation <../../warehouses_storage/inventory_valuation/using_inventory_valuation>`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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`" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:86 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:139 +msgid "Create transfer" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:87 +msgid ":ref:`Yes* `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:88 +msgid ":ref:`Yes* `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:89 +msgid ":ref:`No* `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:-1 -msgid "Replenishment report listing all items needing to be purchased to meet current needs." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:90 +msgid ":doc:`Lot/serial number tracking <../product_tracking>`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:163 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:54 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:81 +msgid "Create purchase order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:96 +msgid ":ref:`Yes* `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:98 -msgid "Replenishment report fields" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:98 +msgid "Can be manufactured or subcontracted" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:100 +msgid ":ref:`Yes* `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:104 -msgid ":guilabel:`Product`: the product that requires a replenishment." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:102 +msgid "Can be in a kit" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:105 -msgid ":guilabel:`Location`: the specific location where the product is stored." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:106 +msgid "Placed in package" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:106 -msgid ":guilabel:`Warehouse`: the warehouse where the product is stored." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:108 +msgid ":ref:`Yes* `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:107 -msgid ":guilabel:`On Hand`: the amount of product currently available." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:110 +msgid "Appears on Inventory report" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:108 -msgid ":guilabel:`Forecast`: the amount of product available after all current orders (sales, manufacturing, purchase, etc.) are taken into account." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:111 +msgid ":ref:`Yes `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:110 -msgid ":guilabel:`Preferred Route`: how the product is procured, either :guilabel:`Buy`, :guilabel:`Manufactured`, :guilabel:`Dropship`, etc." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:120 +msgid "A storable product's on-hand and forecasted quantities, based on incoming and outgoing orders, are reflected on the product form, accessed by going to :menuselection:`Inventory app --> Products --> Products`, and selecting the desired product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:112 -msgid ":guilabel:`Vendor`: the company from which the product is acquired." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:128 +msgid "Show \"On Hand\" and \"Forecast\" smart buttons." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:113 -msgid ":guilabel:`Bill of Materials`: the bill of materials for the product (if one is configured)." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:128 +msgid "Current and forecasted quantities are displayed in the **On Hand** and **Forecasted** smart buttons on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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)." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:133 +msgid "On the other hand, consumable products are regarded as always available, and they **cannot** be managed using reordering rules or lot/serial numbers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:141 +msgid "*Transfers* are any warehouse operation, such as receipts, internal or batch transfers, or deliveries." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:144 +msgid "When creating a transfer for storable products in the *Inventory* app, transfers modify the on-hand quantity at each location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:121 -msgid ":guilabel:`Max Quantity`: the amount of product that should be available after replenishing the product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:147 +msgid "For example, transferring five units from the internal location `WH/Stock` to `WH/Packing Zone` decreases the recorded quantity at `WH/Stock` and increases it at `WH/Packing Zone`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:152 +msgid "For consumable products, transfers can be created, but exact quantities at each storage location are not tracked." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:157 +msgid "Service products cannot be included in transfers, but these products can be `linked to projects and tasks for deadline tracking `_." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:128 -msgid ":guilabel:`UoM`: the unit of measure used to acquire the product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:165 +msgid "Both storable and consumable products can be included in a request for quotation in the *Purchase* app." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:129 -msgid ":guilabel:`Company`: the company for which the product is acquired." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:168 +msgid "However, when receiving consumable products, their on-hand quantity does not change upon validating the receipt (e.g. `WH/IN`)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/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. To replenish a product manually, click :guilabel:`Order Once`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:174 +msgid "Manufacture or subcontract" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:135 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:176 +msgid "Storable and consumable products can be manufactured, subcontracted, or included in a bill of materials (BoM)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:138 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:183 +msgid "Show \"Bill of Materials\" and \"Used In\" smart buttons." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:141 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:183 +msgid "When the **Bill of Materials** and **Used In** smart buttons are visible on the product form, this indicates the product can be manufactured or used as a component of a |BOM|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:-1 -msgid "Snooze options to turn off notifications for reordering for a period of time." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:191 +msgid "Both storable and consumable products can be placed in :doc:`packages `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:149 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:193 +msgid "However, for consumable products, the quantity is not tracked, and the product is not listed in the package's :guilabel:`Contents`, accessed by going to :menuselection:`Inventory app --> Products --> Packages`, and selecting the desired package." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:-1 -msgid "Quote request list shows which quotes are directly from the replenishment report." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:201 +msgid "Show Packages page, containing the package contents list." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:158 -msgid "Make to order (MTO) route" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:201 +msgid "A consumable product was placed in the package, but the **Content** section does not list it." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:160 -msgid "Since the |MTO| route is recommended for customized products, the route is hidden by default." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:203 +msgid "If the *Move Entire Package* feature is enabled, moving a package updates the location of the contained storable products. However, the location of consumable products are not updated." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:169 -msgid "To activate the |MTO| route in Odoo:" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:209 +msgid "Inventory report" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:163 -msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:211 +msgid "**Only** storable products appear on the following reports." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:164 -msgid "Activate the :guilabel:`Multi-Step Routes` setting, located under the :guilabel:`Warehouse` section, and click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:213 +msgid "The *stock report* is a comprehensive list of all on-hand, unreserved, incoming, and outgoing storable products. The report is only available to users with :doc:`administrator access <../../../../general/users/access_rights>`, and is found by navigating to :menuselection:`Inventory app --> Reporting --> Stock`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:166 -msgid "Then, go to :menuselection:`Inventory app --> Configuration --> Routes`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:-1 +msgid "Show stock reporting list found in Inventory > Reporting > Stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:167 -msgid "Click on :menuselection:`Filters --> Archived` to show archived routes." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:222 +msgid "The *location report* is a breakdown of each location (internal, external, or virtual) and the on-hand and reserved quantity of each storable product. The report is only available with the *Storage Location* feature activated (:menuselection:`Inventory app --> Configuration --> Settings`), and to users with :doc:`administrator access <../../../../general/users/access_rights>`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:168 -msgid "Select the checkbox next to :guilabel:`Replenish on Order (MTO)`, and click on :menuselection:`Action --> Unarchive`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:227 +msgid "Navigate to the location report by going to :menuselection:`Inventory app --> Reporting --> Locations`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:172 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:-1 +msgid "Show location reporting list found in Inventory > Reporting > Locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:176 -msgid "To set a product's procurement route to |MTO|, go to :menuselection:`Inventory app --> Products --> Products`, and click on the desired product to open its product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:179 -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/product_management/product_replenishment/strategies.rst:182 -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/product_management/product_replenishment/strategies.rst:186 -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/product_management/product_replenishment/strategies.rst:192 -msgid "The |MTO| route cannot be selected alone. |MTO| **only** works if the :guilabel:`Manufacture` or :guilabel:`Buy` route is also selected." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:-1 -msgid "Replenish on Order selected on the product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:3 msgid "Units of measure" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:11 msgid "In some cases, handling products in different units of measure is necessary. For example, a business can buy products from a country that uses the metric system, and then sell those products in a country that uses the imperial system. In that case, the business needs to convert the units." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:15 msgid "Another case for unit conversion is when a business buys products in a big pack from a supplier, and then sells those products in individual units." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:18 msgid "Odoo can be set up to use different *units of measure (UoM)* for one product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:23 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:23 msgid "To use different units of measure in Odoo, first go to :menuselection:`Inventory app --> Configuration --> Settings`, and under the :guilabel:`Products` section, activate the :guilabel:`Units of Measure` setting. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:-1 msgid "Enable Units of Measure in the Inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:32 msgid "Units of measure categories" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:34 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:34 msgid "After enabling the *Units of Measure* setting, view the default units of measure categories in :menuselection:`Inventory app --> Configuration --> UoM Categories`. The category is important for unit conversion; Odoo can convert a product's units from one unit to another **only** if both units belong to the same category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:-1 msgid "Set units of measure categories." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:43 msgid "Each units of measure category has a reference unit. The reference unit is highlighted in blue in the :guilabel:`Uom` column of the :guilabel:`Units of Measure Categories` page. Odoo uses the reference unit as a base for any new units." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:47 msgid "To create a new unit, first select the correct category from the :guilabel:`Units of Measure Categories` page. For example, to sell a product in a box of six units, click the :guilabel:`Unit` category line. Then, on the category page that appears, click :guilabel:`Add a line` in the :guilabel:`Units of Measure` tab. Then, in the :guilabel:`Unit of Measure` field, title the new unit, such as `Box of 6`, then in the :guilabel:`Type` field, select the appropriate size reference, such as :guilabel:`Bigger than the reference Unit of Measure`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:54 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:54 msgid "If applicable, enter a :guilabel:`UNSPSC Category`, which is a globally recognized `code managed by GS1 `_, that **must** be purchased in order to use." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:57 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:57 msgid "In the :guilabel:`Ratio` field, enter how many individual units are in the new |UOM|, such as `6.00000` when using the example of the `6-Pack` (since a box of six is six times *bigger* than the reference unit, `1.00000`)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:-1 msgid "Convert products from one unit to another as long as they belong to the same category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:66 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:66 msgid "Specify a product's units of measure" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:68 msgid "To set units of measure on a product, first go to :menuselection:`Inventory app --> Products --> Products` and select a product to open its product form page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:71 msgid "In the :guilabel:`General Information` tab, edit the :guilabel:`Unit of Measure` field to specify the unit of measure that the product is sold in. The specified unit is also the unit used to keep track of the product's inventory and internal transfers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:75 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:75 msgid "Edit the :guilabel:`Purchase UoM` field to specify the unit of measure that the product is purchased in." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:81 msgid "Unit conversion" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:83 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:83 msgid "Odoo automatically converts unit measurements when products have different :abbr:`UoMs (Units of Measure)` and purchase :abbr:`UoMs (Units of Measure)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:86 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:86 msgid "This occurs in various scenarios, including:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:88 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:88 msgid ":ref:`Vendor orders `: purchase |UOM| on purchase orders (POs) converts to |UOM| on internal warehouse documents" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:90 msgid ":ref:`Automatic replenishment `: generates |POs| when the stock levels of a product (tracked in |UOM|) dips below a certain level. But, the |POs| are created using the purchase |UOM|" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:93 msgid ":ref:`Sell products `: if a different |UOM| is used on the sales order (SO), the quantity is converted to the warehouse's preferred |UOM| on the delivery order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:100 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:100 msgid "Buy products in the purchase UoM" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:102 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:102 msgid "When creating a new request for quotation (RFQ) in the *Purchase* app, Odoo automatically uses the product's specified purchase unit of measure. If needed, manually edit the :guilabel:`UoM` value on the |RFQ|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:106 msgid "After the |RFQ| is confirmed into a |PO|, click the :guilabel:`Receipt` smart button at the top of the |PO|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:109 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:109 msgid "Odoo automatically converts the purchase unit of measure into the product's sales/inventory unit of measure, so the :guilabel:`Demand` column of the delivery receipt shows the converted quantity." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:113 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:113 msgid "When the product's purchase :guilabel:`UoM` is `Box of 6`, and its sales/inventory unit of measure is `Units`, the |PO| shows the quantity in boxes of six, and the receipt (and other internal warehouse documents) shows the quantity in units." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:0 msgid "Image of a purchase order that is using the purchase unit of measure." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:121 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:121 msgid "An order of three quantities is placed using the purchase \"UoM\": `Box of 6`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:0 msgid "Image of receipt displaying the unit of measure." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:127 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:127 msgid "Upon warehouse receipt, the recorded quantities are in the internal \"Unit of Measure\": `Units`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:133 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:133 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:6 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:169 msgid "Replenishment" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:135 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:135 msgid "A request for quotation for a product can also be generated directly from the product form using the :guilabel:`Replenish` button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:138 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:138 msgid "After clicking :guilabel:`Replenish`, a replenish assistant box pops up. The purchase unit of measure can be manually edited in the :guilabel:`Quantity` field, if needed. Then, click :guilabel:`Confirm` to create the |RFQ|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:143 msgid "A |PO| can **only** be automatically generated if at least **one** vendor is listed in the product form's :guilabel:`Purchase` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:-1 msgid "Click Replenish button to manually replenish." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:150 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:150 msgid "Navigate to the created |PO| by clicking the :guilabel:`Forecasted` smart button on the product form. Scroll down to the :guilabel:`Forecasted Inventory` section, and in the :guilabel:`Requests for quotation` line, click the |RFQ| reference number to open the draft |RFQ|. If necessary, the purchase |UOM| can be edited directly on the |PO|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:158 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:158 msgid "Sell in a different UoM" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:160 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:160 msgid "When creating a new quotation in the *Sales* app, Odoo automatically uses the product's specified unit of measure. If needed, the :guilabel:`UoM` can be manually edited on the quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:163 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:163 msgid "After the quotation is sent to the customer, and confirmed into a sales order (SO), click the :guilabel:`Delivery` smart button at the top of the |SO|. Odoo automatically converts the unit of measure into the product's inventory unit of measure, so the :guilabel:`Demand` column of the delivery shows the converted quantity." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:168 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:168 msgid "For example, if the product's |UOM| on the |SO| was changed to `Box of 6`, but its inventory unit of measure is `Units`, the |SO| shows the quantity in boxes of six, and the delivery shows the quantity in units." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:6 msgid "Product tracking" msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:8 +msgid "*Lots* and *serial numbers* are the two ways to identify and track products in Odoo. While there are similarities between the two traceability methods, there are also notable differences that affect receipts, deliveries, and inventory reports." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:12 +msgid "A *lot* usually indicates a specific batch of an item that was received, is currently stored, or was shipped from a warehouse. However, it can also pertain to a batch of products manufactured in-house, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:16 +msgid "A *serial number* is a unique identifier assigned incrementally (or sequentially) to an item or product, used to distinguish it from other items or products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:20 +msgid ":doc:`product_tracking/lots`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:21 +msgid ":doc:`product_tracking/serial_numbers`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:24 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:24 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:22 +msgid "Enable lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:26 +msgid "To track products using lots and serial numbers, the *Lots & Serial Numbers* feature must be enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:29 +msgid "To do that, go to the :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Then, click the :guilabel:`Save` button to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +msgid "Enabled lots and serial numbers feature in inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:38 +msgid "When to use lots" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:40 +msgid "Lots are useful for products that are manufactured or received in large quantities, such as clothes or food. Lots and can be used to trace a product back to a group, which is especially useful when managing product recalls or expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:0 +msgid "Created lot with quantity of products in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:49 +msgid "Manufacturers assign lot numbers to groups of products that have common properties; this can lead to multiple goods sharing the same lot number. This helps identify a number of products in a single group, and allows for end-to-end traceability of these products through each step in their life cycles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:55 +msgid "When to use serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:57 +msgid "The goal of assigning serial numbers to individual products is to make sure every item's history is identifiable when it travels through the supply chain. This can be especially useful for manufacturers that provide after-sales services related to products they sell and deliver." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:0 +msgid "List of serial numbers for product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:66 +msgid "Serial numbers can contain many different types of characters: numbers, letters, typographical symbols, or a mixture of all three types." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:343 +msgid "Traceability" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:72 +msgid "Manufacturers and companies can refer to traceability reports to see the entire life cycle of a product. These reports include vital information, like where it came from (and when), where it was stored, and to whom it was sent." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:76 +msgid "To see the full traceability of a product, or group products by lots and/or serial numbers, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the :guilabel:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:80 +msgid "From here, products with lots or serial numbers assigned to them are listed by default. They can also be expanded to show what lots or serial numbers have been specifically assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:83 +msgid "To group by lots or serial numbers, first remove any default filters from the search bar in the upper-right corner. Then, click :guilabel:`Group By`, and select :guilabel:`Add Custom Group`, which reveals a mini drop-down menu. From this mini drop-down menu, select :guilabel:`Lot/Serial Number`, and click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:88 +msgid "Doing so reveals all existing lots and serial numbers, and each can be expanded to show all product quantities with that assigned number. For unique serial numbers that are *not* reused, there should *only* be one product per serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:-1 +msgid "Reporting page with drop-down lists of lots and serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:97 +msgid "For additional information regarding an individual lot number or serial number, click the line item for the lot or serial number to reveal that specific number's :guilabel:`Lot` or :guilabel:`Serial Number` form. From this form, click the :guilabel:`Location` and :guilabel:`Traceability` smart buttons to see all stock on-hand using that serial number. Any operations made using that lot or serial number can be found here, as well." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:3 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:100 msgid "Assign serial numbers" @@ -3253,7 +3392,6 @@ msgid "`Odoo Tutorials: Serial Numbers Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Then, click the :guilabel:`Save` button to save changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 -msgid "Enabled lots and serial numbers feature in inventory settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:35 -msgid "When to use lots" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:37 -msgid "Lots are useful for products that are manufactured or received in large quantities, such as clothes or food. Lots and can be used to trace a product back to a group, which is especially useful when managing product recalls or expiration dates." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:0 -msgid "Created lot with quantity of products in it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:46 -msgid "Manufacturers assign lot numbers to groups of products that have common properties; this can lead to multiple goods sharing the same lot number. This helps identify a number of products in a single group, and allows for end-to-end traceability of these products through each step in their life cycles." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:52 -msgid "When to use serial numbers" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:54 -msgid "The goal of assigning serial numbers to individual products is to make sure every item's history is identifiable when it travels through the supply chain. This can be especially useful for manufacturers that provide after-sales services related to products they sell and deliver." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:0 -msgid "List of serial numbers for product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:63 -msgid "Serial numbers can contain many different types of characters: numbers, letters, typographical symbols, or a mixture of all three types." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:67 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:343 -msgid "Traceability" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:69 -msgid "Manufacturers and companies can refer to traceability reports to see the entire life cycle of a product. These reports include vital information, like where it came from (and when), where it was stored, and to whom it was sent." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:73 -msgid "To see the full traceability of a product, or group products by lots and/or serial numbers, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the :guilabel:`Lots/Serial Numbers` dashboard." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:77 -msgid "From here, products with lots or serial numbers assigned to them are listed by default. They can also be expanded to show what lots or serial numbers have been specifically assigned to them." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:80 -msgid "To group by lots or serial numbers, first remove any default filters from the search bar in the upper-right corner. Then, click :guilabel:`Group By`, and select :guilabel:`Add Custom Group`, which reveals a mini drop-down menu. From this mini drop-down menu, select :guilabel:`Lot/Serial Number`, and click :guilabel:`Apply`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:85 -msgid "Doing so reveals all existing lots and serial numbers, and each can be expanded to show all product quantities with that assigned number. For unique serial numbers that are *not* reused, there should *only* be one product per serial number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:-1 -msgid "Reporting page with drop-down lists of lots and serial numbers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:94 -msgid "For additional information regarding an individual lot number or serial number, click the line item for the lot or serial number to reveal that specific number's :guilabel:`Lot` or :guilabel:`Serial Number` form. From this form, click the :guilabel:`Location` and :guilabel:`Traceability` smart buttons to see all stock on-hand using that serial number. Any operations made using that lot or serial number can be found here, as well." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:3 msgid "Expiration dates" msgstr "" @@ -3817,7 +3851,8 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:226 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:189 -msgid ":doc:`../../warehouses_storage/removal_strategies`" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:133 +msgid ":doc:`../../shipping_receiving/removal_strategies`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:229 @@ -4263,358 +4298,8 @@ msgid "Show the Traceability Report for a lot, that displays the stock moves." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:380 -msgid ":doc:`differences`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:3 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:189 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:99 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:159 -msgid "Packages" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:7 -msgid "A *package* is a physical container holding one or more products. Packages can also be used to store items in bulk." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:10 -msgid "Packages are commonly used for the following purposes:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:12 -msgid ":ref:`Grouping products to move them in bulk `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:13 -msgid ":ref:`Shipping to customers `: configure package types to align with shipping carriers' size and weight requirements, streamlining the packing process, and ensuring compliance with carrier shipping specifications." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:16 -msgid "Storing items in bulk." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:18 -msgid "*Package use* is a field on the package form in Odoo that is only visible by enabling the *Batch Transfers* and *Packages* features (:menuselection:`Inventory app --> Configuration --> Settings`)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:21 -msgid "By default, the *Package Use* field on a packages form is set to *Disposable Box*. Change this field to *Reusable Box* **only** when configuring packages for :ref:`cluster pickings `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:25 -msgid "*Package type* is an optional feature used for :doc:`calculating shipping cost <../../shipping_receiving/setup_configuration/delivery_method>`, based on real shipping weight. Create package types to include the weight of the package itself (e.g. boxes, pallets, other shipping containers) in shipping cost calculations." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:31 -msgid "While packages are commonly used in the :doc:`three-step delivery route <../../shipping_receiving/daily_operations/delivery_three_steps>`, they can be used in any workflow involving storable products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:40 -msgid "To use packages, first go to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Operations` heading, activate the :guilabel:`Packages` feature. Then, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:-1 -msgid "Activate the *Packages* setting in Inventory > Configuration > Settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:51 -msgid "Pack items" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:53 -msgid "Products can be added to packages in any transfer by:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:55 -msgid "Clicking each :ref:`Detailed Operations ` icon on the product line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:57 -msgid "Using the :ref:`Put in Pack ` button to place everything in the transfer into a package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:63 -msgid "Detailed operations" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:65 -msgid "On any warehouse transfer (e.g. receipt, delivery order), add a product to a package by clicking the :guilabel:`⦙≣ (bulleted list)` icon in the :guilabel:`Operations` tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:-1 -msgid "Show \"Detailed Operations\" icon in the product line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:72 -msgid "Doing so opens the :guilabel:`Detailed Operations` pop-up window for the :guilabel:`Product`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:74 -msgid "To put the :guilabel:`Product` in a package, click :guilabel:`Add a line`, and assign the product to a :guilabel:`Destination Package`. Select an existing package, or create a new one by typing the name of the new package, then select :guilabel:`Create...`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:82 -msgid "Assign a package to \"Destination Package\" field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:82 -msgid "Twelve units of `Acoustic Bloc Screen` are placed in `PACK0000001`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:84 -msgid "Then, specify the quantity of items to go into the package in the :guilabel:`Done` column. Repeat the above steps to place the :guilabel:`Product` in different packages. Once finished, click :guilabel:`Confirm` to close the window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:89 -msgid ":doc:`Ship one order in multiple packages <../../shipping_receiving/advanced_operations_shipping/multipack>`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:95 -msgid "Put in pack" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:97 -msgid "Alternatively, click the :guilabel:`Put in Pack` button on **any** warehouse transfer to create a new package, and place all the items in the transfer in that newly-created package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:101 -msgid "The :guilabel:`Put in Pack` button appears on receipts, delivery orders, and other transfer forms with the *Packages* feature enabled in :menuselection:`Inventory app --> Configuration --> Settings`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:109 -msgid "Image of the \"Put in Pack\" button being clicked." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:109 -msgid "In batch transfer `BATCH/00003`, the :guilabel:`Put in Pack` button was clicked to create a new package, `PACK0000002`, and assign all items to it in the :guilabel:`Destination Package` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:117 -msgid "Create package types by navigating to :menuselection:`Inventory app --> Configuration --> Package Types`, in order to set custom dimensions and weight limits. This feature is mainly used to calculate package weights for shipping costs." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:122 -msgid ":doc:`Shipping carriers <../../shipping_receiving/setup_configuration/third_party_shipper>`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:123 -msgid ":doc:`../../shipping_receiving/setup_configuration/delivery_method`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:125 -msgid "On the :guilabel:`Package Types` list, clicking :guilabel:`New` opens a blank package type form. The fields of the form are as follows:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:128 -msgid ":guilabel:`Package Type` (required): define the package type's name." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:129 -msgid ":guilabel:`Size`: define the dimensions of the package in millimeters (mm). The fields, from left to right, define the :guilabel:`Length`, :guilabel:`Width`, and :guilabel:`Height`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:131 -msgid ":guilabel:`Weight`: weight of an empty package (e.g. an empty box, pallet)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:134 -msgid "Odoo calculates the package's weight by adding the weight of the empty package plus the weight of the item(s), which can be found in the :guilabel:`Weight` field, in the :guilabel:`Inventory` tab, of each product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:138 -msgid ":guilabel:`Max Weight`: maximum shipping weight allowed in the package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:139 -msgid ":guilabel:`Barcode`: define a barcode to identify the package type from a scan." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:140 -msgid ":guilabel:`Company`: specify a company to make the package type available **only** at the selected company. Leave the field blank if it is available at all companies." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:142 -msgid ":guilabel:`Carrier`: specify the intended shipping carrier for this package type." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:143 -msgid ":guilabel:`Carrier Code`: define a code that is linked to the package type." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:-1 -msgid "Package type for FedEx's 25 kilogram box." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:152 -msgid "Cluster packages" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:154 -msgid "To use *cluster packages*, first navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and activate the :guilabel:`Batch Transfers` feature, located in the :guilabel:`Operations` section. Doing so makes the *Package Use* field become visible on a package form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:-1 -msgid "Activate the *Batch Transfers* feature in Inventory > Configuration > Settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:163 -msgid "Add new packages by going to :menuselection:`Inventory app --> Products --> Packages`. Then, click :guilabel:`New`, or select an existing package. Doing so opens the package form, which contains the following fields:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:167 -msgid ":guilabel:`Package Reference` (required): name of the package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:168 -msgid ":guilabel:`Package Type`: used for :ref:`configuring shipping boxes to ship to the customer `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:172 -msgid ":guilabel:`Package Type` is unnecessary for configuring packages for cluster pickings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:174 -msgid ":guilabel:`Shipping Weight`: used to input the weight of the package after measuring it on a scale." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:176 -msgid ":guilabel:`Company`: specify a company to make the package available **only** at the selected company. Leave the field blank if the package is available at all companies." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:178 -msgid ":guilabel:`Location`: current location of the package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:179 -msgid ":guilabel:`Pack Date`: the date the package was created." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:180 -msgid ":guilabel:`Package Use`: choose :guilabel:`Reusable` for packages used for moving products within the warehouse; :guilabel:`Disposable` for packages used to ship products to customers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:-1 -msgid "Display package form to create a cluster pack." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:188 -msgid ":doc:`Using cluster packages <../../warehouses_storage/advanced_operations_warehouse/cluster_picking>`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:5 -msgid "In Odoo *Inventory*, *packaging* refers to disposable containers holding multiple units of a specific product. Each specific packaging **must** be defined on the individual product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:8 -msgid "For example, different packages for cans of soda, such as a 6-pack, a 12-pack, or a case of 36, need to be configured on the individual product form. This is because packagings are product specific — **not** generic." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:15 -msgid "To use packagings, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Then, under the :guilabel:`Products` heading, enable the :guilabel:`Product Packagings` feature, and click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:-1 -msgid "Enable packagings by selecting \"Product Packagings\"." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:24 -msgid "Create packaging" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:26 -msgid "Packagings can be created directly on the product form, or from the :guilabel:`Product Packagings` page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:30 -msgid "From product form" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:32 -msgid "Create packagings on a product form by going to :menuselection:`Inventory app --> Products --> Products`, and select the desired product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:35 -msgid "Under the :guilabel:`Inventory` tab, scroll down to the :guilabel:`Packaging` section, and click :guilabel:`Add a line`. In the table, fill out the following fields:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:38 -msgid ":guilabel:`Packaging` (required): name of packaging that appears on sales/purchase orders as a packaging option for the product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:40 -msgid ":guilabel:`Contained quantity` (required): amount of product in the packaging." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:41 -msgid ":guilabel:`Unit of Measure` (required): measurement unit for quantifying the product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:42 -msgid ":guilabel:`Sales`: check this option for packagings intended for use on sales orders." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:43 -msgid ":guilabel:`Purchase`: check this option for packagings intended for use on purchase orders." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:46 -msgid "Access additional fields in the :guilabel:`Packaging` table below by clicking the :guilabel:`(sliders)` icon to the far-right of the column titles in the :guilabel:`Packaging` section, and selecting the desired options from the drop-down menu that appears." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:0 -msgid "Show the additional options menu's icon: sliders." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:54 -msgid ":guilabel:`Barcode`: identifier for tracing packaging in stock moves or pickings, using the :ref:`Barcode app `. Leave blank if not in use." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:56 -msgid ":guilabel:`Company`: indicates the packaging is only available at the selected company. Leave blank to make the packaging available across all companies." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:60 -msgid "To create a packaging type for six units of the product, `Grape Soda`, begin by clicking :guilabel:`Add a line`. In the line, name the :guilabel:`Packaging` `6-pack`, and set the :guilabel:`Contained quantity` to `6`. Repeat this process for additional packagings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:0 -msgid "Create 6-pack case for product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:69 -msgid "From product packagings page" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:71 -msgid "To view all packagings that have been created, go to :menuselection:`Inventory app --> Configuration --> Product Packagings`. Doing so reveals the :guilabel:`Product Packagings` page with a complete list of all packagings that have been created for all products. Create new packagings by clicking :guilabel:`New`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:77 -msgid "Two soda products, `Grape Soda` and `Diet Coke`, have three types of packagings configured. On the :guilabel:`Product Packagings` page, each product can be sold as a `6-Pack` that contains 6 products, as a `12-Pack` of 12 products, or as a `Case` of 32 products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:0 -msgid "List of different packagings for products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:86 -msgid "Apply packagings" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:88 -msgid "When creating a sales order in the :menuselection:`Sales` app, specify the packagings that should be used for the product. The chosen packaging is displayed on the :abbr:`SO (Sales Order)` under the :guilabel:`Packaging` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:93 -msgid "18 cans of the product, `Grape Soda`, is packed using three 6-pack packagings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:0 -msgid "Assign packagings on the Sales Order Line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:100 -msgid "Packaging can be used in conjunction with Odoo :ref:`Barcode `. When receiving products from suppliers, scanning the packaging barcode automatically adds the number of units in the packaging to the internal count of the product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:293 +msgid ":doc:`../product_tracking`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:3 @@ -4674,7 +4359,7 @@ msgid "Return to the product form (:menuselection:`Inventory app --> Products -- msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 msgid "Enable lots and serial numbers." msgstr "" @@ -5006,1627 +4691,212 @@ msgstr "" msgid "For additional information regarding an individual serial number (or lot number), click the line item for the serial number to reveal that specific serial number's :guilabel:`Serial Number` form. From this form, click the :guilabel:`Location` and :guilabel:`Traceability` smart buttons to see all stock on-hand using that serial number, and any operations made using that serial number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:293 -msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:3 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:69 -msgid "Product type" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:7 -msgid "Define *product types* in Odoo to track products in varying levels of detail." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:9 -msgid "Classify products as *storable* to track stock counts, allowing users to trigger :doc:`reordering rules <../product_replenishment/reordering_rules>` for generating purchase orders. *Consumable* products are assumed to always be in stock, and *service* products are performed and served by the business." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:15 -msgid "`Odoo Tutorials: Product Type `_" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:18 -msgid "Set product type" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:20 -msgid "To set a product type, go to :menuselection:`Inventory app --> Products --> Products`, and select the desired product from the list." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:23 -msgid "On the product form, in the :guilabel:`Product Type` field, select:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:25 -msgid ":guilabel:`Storable Product` for products tracked with stock counts. Only storable products can trigger reordering rules for generating purchase orders;" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:29 -msgid "Choose :guilabel:`Storable Product` if it is necessary to track a product's stock at various locations, inventory valuations, or if the product has lots and/or serial numbers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:32 -msgid ":guilabel:`Consumable` for products that are always assumed to be in stock, whose quantities are not necessary to track or forecast (e.g. nails, toilet paper, coffee, etc.). Consumables are replaceable and essential, but exact counts are unnecessary; or" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:35 -msgid ":guilabel:`Service` for sellable service products that are performed, and not tracked with stock counts (i.e. maintenance, installation, or repair services)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:0 -msgid "Set a product type on the product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:43 -msgid "The product types listed above are part of the standard *Inventory* app. For access to the fields below, :ref:`install ` the corresponding apps **in addition** to *Inventory*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:46 -msgid ":guilabel:`Booking Fees`: charge a fee for booking appointments through the *Appointments* app. Requires the installation of the *Calendar* app and *Pay to Book* (`appointment_account_payment`) module" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:49 -msgid ":guilabel:`Combo`: create discounted products sold in a bundle. Requires the installation of the *PoS* app." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:51 -msgid ":guilabel:`Event Ticket`: sold to attendees wanting to go to an event. Requires the installation of the *Events* app" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:53 -msgid ":guilabel:`Event Booth`: sold to partners or sponsors to set up a booth at an event. Requires the installation of the *Events* app" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:55 -msgid ":guilabel:`Course`: sell access to an educational course. Requires the installation of the *eLearning* app" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:59 -msgid "Compare types" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:61 -msgid "Below is a summary of how each product type affects common *Inventory* operations, like transfers, reordering rules, and the forecasted report. Click the chart item with an asterisk (*) to navigate to detailed sections." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:70 -msgid "Storable" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:71 -msgid "Consumable" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:72 -msgid "Service" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:73 -msgid "Physical product" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:74 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:75 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:83 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:91 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:95 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:103 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:104 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:107 -msgid "Yes" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:76 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:80 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:84 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:85 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:92 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:93 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:97 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:101 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:105 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:109 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:112 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:113 -msgid "No" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:77 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:118 -msgid "On-hand quantity" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:78 -msgid ":ref:`Yes* `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:79 -msgid ":ref:`Yes* `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:81 -msgid ":doc:`Inventory valuation <../../warehouses_storage/inventory_valuation/using_inventory_valuation>`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:86 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:139 -msgid "Create transfer" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:87 -msgid ":ref:`Yes* `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:88 -msgid ":ref:`Yes* `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:89 -msgid ":ref:`No* `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:90 -msgid ":doc:`Lot/serial number tracking `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:94 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:163 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:56 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:79 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:81 -msgid "Create purchase order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:96 -msgid ":ref:`Yes* `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:98 -msgid "Can be manufactured or subcontracted" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:99 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:100 -msgid ":ref:`Yes* `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:102 -msgid "Can be in a kit" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:106 -msgid "Placed in package" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:108 -msgid ":ref:`Yes* `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:110 -msgid "Appears on Inventory report" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:111 -msgid ":ref:`Yes `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:120 -msgid "A storable product's on-hand and forecasted quantities, based on incoming and outgoing orders, are reflected on the product form, accessed by going to :menuselection:`Inventory app --> Products --> Products`, and selecting the desired product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:128 -msgid "Show \"On Hand\" and \"Forecast\" smart buttons." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:128 -msgid "Current and forecasted quantities are displayed in the **On Hand** and **Forecasted** smart buttons on the product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:133 -msgid "On the other hand, consumable products are regarded as always available, and they **cannot** be managed using reordering rules or lot/serial numbers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:141 -msgid "*Transfers* are any warehouse operation, such as receipts, internal or batch transfers, or deliveries." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:144 -msgid "When creating a transfer for storable products in the *Inventory* app, transfers modify the on-hand quantity at each location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:147 -msgid "For example, transferring five units from the internal location `WH/Stock` to `WH/Packing Zone` decreases the recorded quantity at `WH/Stock` and increases it at `WH/Packing Zone`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:152 -msgid "For consumable products, transfers can be created, but exact quantities at each storage location are not tracked." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:157 -msgid "Service products cannot be included in transfers, but these products can be `linked to projects and tasks for deadline tracking `_." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:165 -msgid "Both storable and consumable products can be included in a request for quotation in the *Purchase* app." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:168 -msgid "However, when receiving consumable products, their on-hand quantity does not change upon validating the receipt (e.g. `WH/IN`)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:174 -msgid "Manufacture or subcontract" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:176 -msgid "Storable and consumable products can be manufactured, subcontracted, or included in a bill of materials (BoM)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:183 -msgid "Show \"Bill of Materials\" and \"Used In\" smart buttons." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:183 -msgid "When the **Bill of Materials** and **Used In** smart buttons are visible on the product form, this indicates the product can be manufactured or used as a component of a |BOM|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:191 -msgid "Both storable and consumable products can be placed in :doc:`packages `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:193 -msgid "However, for consumable products, the quantity is not tracked, and the product is not listed in the package's :guilabel:`Contents`, accessed by going to :menuselection:`Inventory app --> Products --> Packages`, and selecting the desired package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:201 -msgid "Show Packages page, containing the package contents list." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:201 -msgid "A consumable product was placed in the package, but the **Content** section does not list it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:203 -msgid "If the *Move Entire Package* feature is enabled, moving a package updates the location of the contained storable products. However, the location of consumable products are not updated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:209 -msgid "Inventory report" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:211 -msgid "**Only** storable products appear on the following reports." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:213 -msgid "The *stock report* is a comprehensive list of all on-hand, unreserved, incoming, and outgoing storable products. The report is only available to users with :doc:`administrator access <../../../../general/users/access_rights>`, and is found by navigating to :menuselection:`Inventory app --> Reporting --> Stock`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:-1 -msgid "Show stock reporting list found in Inventory > Reporting > Stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:222 -msgid "The *location report* is a breakdown of each location (internal, external, or virtual) and the on-hand and reserved quantity of each storable product. The report is only available with the *Storage Location* feature activated (:menuselection:`Inventory app --> Configuration --> Settings`), and to users with :doc:`administrator access <../../../../general/users/access_rights>`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:227 -msgid "Navigate to the location report by going to :menuselection:`Inventory app --> Reporting --> Locations`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:-1 -msgid "Show location reporting list found in Inventory > Reporting > Locations." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving.rst:5 msgid "Shipping and receiving" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping.rst:5 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse.rst:5 -msgid "Advanced operations" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:6 +msgid "Inbound and outbound flows" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:3 -msgid "How to cancel a shipping request to a shipper?" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:8 +msgid "There are several ways to handle how a warehouse receives products (receipts) and ships products (deliveries). Depending on several factors, such as the type of products stocked and sold, warehouse size, and the amount of daily confirmed receipts and delivery orders, the way products are handled when coming in and out of the warehouse can vary a lot. Different settings can be configured for receipts and deliveries; they do not have to be configured to have the same number of steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:6 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:6 -msgid "Overview" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:15 +msgid "`Using Routes (eLearning Tutorial) `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:8 -msgid "Odoo can handle various delivery methods, including third party shippers. Odoo will be linked with the transportation company tracking system." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:16 +msgid "`Push & Pull Rules (eLearning Tutorial) `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:12 -msgid "It will allow you to manage the transport company, the real prices and the destination." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:20 +msgid "Choosing the right inventory flow to handle receipts and deliveries" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:15 -msgid "You can easily cancel the request made to the carrier system." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:22 +msgid "By default, Odoo handles shipping and receiving in three different ways: in one, two, or three steps. The simplest configuration is one step, which is the default. Each additional step required for a warehouse for either the receiving or shipping process will add an additional layer of operations to perform before a product is either received or shipped. These configurations depend entirely on the requirements for the products stored, such as performing quality checks on received products, or using special packaging on shipped products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:18 -msgid "How to cancel a shipping request?" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:30 +msgid "One-step flow" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:20 -msgid "If the delivery order is not **Validated**, then the request hasn't been made. You can choose to cancel the delivery or to change the carrier." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:32 +msgid "The receiving and shipping rules for a one-step configuration are as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:24 -msgid "If you have clicked on **Validate**, the request has been made and you should have received the tracking number and the label. You can still cancel the request. Simply click on the **Cancel** button next to the **Carrier Tracking Ref**:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:34 +msgid "**Receipt**: Receive products directly into stock. No intermediate steps between receipt and stock occur, such as a transfer to a quality control location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:32 -msgid "You will now see that the shipment has been cancelled." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:36 +msgid "**Shipping**: Ship products directly from stock. No intermediate steps between stock and shipping occur, such as a transfer to a packing location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:37 -msgid "You can now change the carrier if you wish." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:38 +msgid "Can only be used if not using :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategies." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:40 -msgid "How to send a shipping request after cancelling one?" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:40 +msgid "Receipts and/or deliveries are handled quickly." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:42 -msgid "After cancelling the shipping request, you can change the carrier you want to use. Confirm it by clicking on the **Send to shipper** button. You will get a new tracking number and a new label." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:41 +msgid "Recommended for small warehouses with low stock levels, and for non-perishable items." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:50 -msgid ":doc:`invoicing`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:42 +msgid "Items are received or shipped directly into/from stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:51 -msgid ":doc:`multipack`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:45 +msgid ":doc:`daily_operations/receipts_delivery_one_step`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:3 -msgid "Dropshipping" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:48 +msgid "Two-step flow" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:7 -msgid "Dropshipping is an order fulfillment strategy that allows sellers to have items shipped directly from suppliers to customers. Normally, a seller purchases a product from a supplier, stores it in their inventory, and ships it to the end customer once an order is placed. With dropshipping, the supplier is responsible for storing and shipping the item. This benefits the seller by reducing inventory costs, including the price of operating warehouses." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:50 +msgid "The receiving and shipping rules for a two-step configuration are as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:14 -msgid "Configure products to be dropshipped" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:52 +msgid "**Input + stock**: Bring products to an input location *before* moving into stock. Products can be organized by different internal storage locations, such as various shelves, freezers, and locked areas, before being stocked in the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:16 -msgid "To use dropshipping as a fulfillment strategy, navigate to the :menuselection:`Purchase` app and select :menuselection:`Configuration --> Settings`. Under the :guilabel:`Logistics` heading, click the :guilabel:`Dropshipping` checkbox, and :guilabel:`Save` to finish." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:55 +msgid "**Pick + ship**: Bring products to an output location before shipping. Packages can be organized by different carriers or shipping docks before being shipped." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:20 -msgid "Next, go to the :menuselection:`Sales` app, click :menuselection:`Products --> Products` and choose an existing product or select :guilabel:`Create` to configure a new one. On the :guilabel:`Product` page, make sure that the :guilabel:`Can be Sold` and :guilabel:`Can be Purchased` checkboxes are enabled." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:57 +msgid "Minimum requirement to use lot numbers or serial numbers to track products with a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)` or :abbr:`FEFO (First Expired, First Out)` removal strategy." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 -msgid "Enable the \"Can be Sold\" and \"Can be Purchased\" checkboxes on the product form." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:60 +msgid "Recommended for larger warehouses with high stock levels, or when stocking large items (such as mattresses, large furniture, heavy machinery, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:29 -msgid "Click on the :guilabel:`Purchase` tab and specify a vendor and the price that they sell the product for. Multiple vendors can be added, but the vendor at the top of the list will be the one automatically selected for purchase orders." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:83 +msgid "Products received will not be available for manufacturing, shipping, etc., until they are transferred into stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 -msgid "The product form with a vendor specified." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:66 +msgid ":doc:`daily_operations/receipts_delivery_two_steps`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:37 -msgid "Finally, select the :guilabel:`Inventory` tab and enable the :guilabel:`Dropship` checkbox in the :guilabel:`Routes` section." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:69 +msgid "Three-step flow" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 -msgid "Enable the Dropship option in the product inventory tab." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:71 +msgid "The receiving and shipping rules for a three-step configuration are as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:45 -msgid "While it is not necessary to enable the :guilabel:`Buy` route in addition to the :guilabel:`Dropship` route, enabling both provides the option of dropshipping the product or purchasing it directly." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:73 +msgid "**Input + quality + stock**: Receive products at the input location, transfer them to a quality control area, and move the ones that pass inspection into stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:50 -msgid "Fulfill orders using dropshipping" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:75 +msgid "**Pick + pack + ship**: Pick products according to their removal strategy, pack them in a dedicated packing area, and bring them to an output location for shipping." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:52 -msgid "When a sales order is created for a dropshipped product, an associated request for quotation (RfQ) is automatically generated to purchase the product from the vendor. Sales orders can be viewed in the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders`. Click the :guilabel:`Purchase` smart button at the top right of a sales order to view the associated :abbr:`RFQ (Request for Quotation)`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:77 +msgid "Can be used when tracking products by lot or serial numbers when using a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 -msgid "A dropship sales order with the Purchase smart button in the top right corner." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:80 +msgid "Recommended for very large warehouses with very high stock levels." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:62 -msgid "Once the :abbr:`RFQ (Request for Quotation)` is confirmed, it becomes a purchase order, and a dropship receipt is created and linked to it. The receipt can be viewed by clicking the :guilabel:`Dropship` smart button in the top-right corner of the purchase order form." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:81 +msgid "Required for any warehouse needing to perform quality control inspections before receiving items into stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 -msgid "A dropship purchase order with the Receipt smart button in the top right corner." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:87 +msgid ":doc:`daily_operations/receipts_three_steps`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:70 -msgid "The dropship receipt displays :guilabel:`Partners/Vendors` in the :guilabel:`Source Location` field, and :guilabel:`Partners/Customers` in the :guilabel:`Destination Location` field. Upon delivery of the product to the customer, click on the :guilabel:`Validate` button at the top-left of the dropship receipt to confirm the delivered quantity." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:88 +msgid ":doc:`daily_operations/delivery_three_steps`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 -msgid "Validate the dropship receipt after delivery." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:3 +msgid "Organize a cross-dock in a warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:79 -msgid "To view all dropship orders, simply navigate to the :menuselection:`Inventory` :guilabel:`Overview` dashboard and click the teal :guilabel:`# TO PROCESS` button on the :guilabel:`Dropship` card." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:5 +msgid "Cross-docking is the process of sending products that are received directly to the customers, without making them enter the stock. The trucks are simply unloaded in a *Cross-Dock* area in order to reorganize products and load another truck." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:-1 -msgid "Click the green button on the Dropship card to view all dropship orders." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:13 +msgid "For more information on how to organize your warehouse, read our blog: `What is cross-docking and is it for me? `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:3 -msgid "Shipping cost invoicing" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:20 +msgid "In the *Inventory* app, open :menuselection:`Configuration --> Settings` and activate the *Multi-Step Routes*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:5 -msgid "Invoicing customers for shipping after delivery ensures accurate charges based on real-time shipping factors like distance, weight, and method." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:27 +msgid "Doing so will also enable the *Storage Locations* feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:8 -msgid "In Odoo, shipping costs can be invoiced in two ways:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:29 +msgid "Now, both *Incoming* and *Outgoing* shipments should be configured to work with 2 steps. To adapt the configuration, go to :menuselection:`Inventory --> Configuration --> Warehouses` and edit your warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:10 -msgid "Agree with the customer on a fixed cost and :ref:`include it in the sale order. `" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:36 +msgid "This modification will lead to the creation of a *Cross-Docking* route that can be found in :menuselection:`Inventory --> Configuration --> Routes`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:13 -msgid ":ref:`Invoice shipping costs to the customer post-delivery `, reflecting the actual expenses incurred by the business." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:43 +msgid "Configure products with Cross-Dock Route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:19 -msgid "To set prices to delivery methods, go to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Shipping` section, enable the :guilabel:`Delivery Methods` feature. Then, click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:45 +msgid "Create the product that uses the *Cross-Dock Route* and then, in the inventory tab, select the routes *Buy* and *Cross-Dock*. Now, in the purchase tab, specify the vendor to who you buy the product and set a price for it." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:-1 -msgid "Enable the \"Delivery Methods\" feature in Settings." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:55 +msgid "Once done, create a sale order for the product and confirm it. Odoo will automatically create two transfers which will be linked to the sale order. The first one is the transfer from the *Input Location* to the *Output Location*, corresponding to the move of the product in the *Cross-Dock* area. The second one is the delivery order from the *Output Location* to your *Customer Location. Both are in state *Waiting Another Operation* because we still need to order the product to our supplier." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:28 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:30 -msgid "Add shipping method" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:68 +msgid "Now, go to the *Purchase* app. There, you will find the purchase order that has been automatically triggered by the system. Validate it and receive the products in the *Input Location*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:30 -msgid "Next, configure the the price of each delivery method by going to :menuselection:`Inventory app --> Configuration --> Shipping Methods` and click the :guilabel:`Create` button. Doing so opens a form to provide details about the shipping provider, including:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:77 +msgid "When the products have been received from the supplier, you can go back to your initial sale order and validate the internal transfer from *Input* to *Output*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:34 -msgid ":guilabel:`Shipping Method` (*required*) the name of the delivery method (e.g. `flat-rate shipping`, `same day delivery`, etc.)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:36 -msgid ":guilabel:`Provider` (*required*): choose the delivery service, like FedEx, if using a third-party carrier Ensure the integration with the shipping carrier is properly installed and select the provider from the drop-down menu." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:41 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:122 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:27 -msgid ":doc:`../setup_configuration/third_party_shipper`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:43 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:61 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:121 -msgid ":guilabel:`Company`: if the shipping method should apply to a specific company, select it from the drop-down menu. Leave the field blank to apply the method to all companies." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:46 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:59 -msgid ":guilabel:`Website`: configure shipping methods for an e-commerce page. Select the applicable website from the drop-down menu, or leave it blank to apply the method to all web pages." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:49 -msgid ":guilabel:`Delivery Product` (*required*): the product listed on the :ref:`sales order line ` as the delivery charge." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:51 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:68 -msgid ":guilabel:`Free if order amount is above`: checking this box enables free shipping if the customer spends above the specified amount." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:57 -msgid "Invoice cost on sales order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:59 -msgid "To invoice shipping costs on the sales order, before the item is delivered, go to the :menuselection:`Sales app` and select the desired sales order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:62 -msgid "On the sales order, click the :guilabel:`Add Shipping` button at the bottom-right corner." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:-1 -msgid "Click \"Add Shipping\" button at the bottom right, near the total." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:68 -msgid "In the :guilabel:`Add a shipping method` pop-up window, choose the intended carrier in the :guilabel:`Shipping Method` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:71 -msgid "Then, click the :guilabel:`Get Rate` button to the calculate shipping price based on real-time shipping data Odoo's shipping carrier integration." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:74 -msgid "The :guilabel:`Cost` is automatically calculated using the weight of the items in the order. Finally, click the :guilabel:`Add` button to close the window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:-1 -msgid "Calculate shipping by selecting a shipping method." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:83 -msgid "On the sales order, the delivery product appears in the :guilabel:`Order Lines` tab, with the :guilabel:`Unit Price` set as the shipping cost calculated in the :guilabel:`Add a shipping method` pop-up window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:-1 -msgid "Show delivery product on the sales order line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:91 -msgid "Finally, after the product is delivered, click the :guilabel:`Create invoice` button, and an invoice is created that includes the shipping cost that was added earlier." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:-1 -msgid "Show \"Create Invoice\" button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:98 -msgid "Then, click the :guilabel:`Create and View Invoice` button, and a draft invoice is generated, with the shipping cost included in the :guilabel:`Invoice Lines` tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:-1 -msgid "Show delivery product in the invoice line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:108 -msgid "Invoice real shipping costs" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:110 -msgid "To modify the invoice to reflect the real cost of shipping, follow the steps :ref:`above ` to create an invoice with a delivery product with a :guilabel:`Unit Price` of zero." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:114 -msgid "Then, on a draft invoice, modify the :guilabel:`Unit Price` to reflect the real shipping cost. Finally, invoice the customer the adjusted shipping cost by clicking :guilabel:`Confirm`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:-1 -msgid "Show delivery product on the invoice line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:123 -msgid ":doc:`../setup_configuration/labels`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:3 -msgid "Change shipping label size" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:8 -msgid "In Odoo, there are a variety of different types of shipping labels that can be selected for delivery orders. Depending on the types of shipping packages used, different label sizes may be more appropriate, and can be configured to fit the package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:15 -msgid "In the :menuselection:`Inventory` module, go to :menuselection:`Configuration --> Delivery --> Shipping Methods.` Click on a delivery method to choose it. For the following example, *FedEx International* will be used." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:-1 -msgid "Different shipping methods." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:23 -msgid "In the :guilabel:`Configuration` tab, under :guilabel:`Label Type`, choose one of the label types available. The availability varies depending on the carrier." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:-1 -msgid "Select a label type." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:30 -msgid "When a sales order with the corresponding shipping company is confirmed and a delivery order is validated, the shipping label will be automatically created as a PDF and appear in the :guilabel:`Chatter`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:35 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:48 -msgid "Create a sales order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:37 -msgid "In the :menuselection:`Sales` application, click :guilabel:`Create` and select an international customer. Click :guilabel:`Add A Product` and select an item. Click :guilabel:`Add Shipping`, select a shipping method, then click :guilabel:`Get Rate`, and finally, click :guilabel:`Add`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:-1 -msgid "Add a shipping method and rate to a sales order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:45 -msgid "Once the quotation is confirmed by clicking :guilabel:`Confirm`, a :guilabel:`Delivery` smart button will appear." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:-1 -msgid "Delivery order smart button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:52 -msgid "Once the delivery order is validated by clicking :guilabel:`Validate` in the delivery order, the shipping documents appear in the :guilabel:`Chatter`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:-1 -msgid "Shipping PDF documents." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:60 -msgid "Example labels" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:62 -msgid "The default :guilabel:`Label Type` is :guilabel:`Paper Letter`. An example of a FedEx letter sized label is:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:-1 -msgid "Full page letter size FedEx shipping label." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:69 -msgid "For comparison, an example of a FedEx bottom-half label is:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:-1 -msgid "Half page letter size FedEx shipping label." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:3 -msgid "Multi-package shipments" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:5 -msgid "In some cases, a delivery order with multiple items may need to be shipped in more than one package. This may be necessary if the items are too large to ship in a single package, or if certain items cannot be packaged together. Shipping a single delivery order in multiple packages provides flexibility for how each item is packaged, without the need to create multiple delivery orders." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:13 -msgid "In order to split a delivery order across multiple packages, the *Packages* setting must be enabled. To do so, navigate to :menuselection:`Inventory --> Configuration --> Settings`, then enable the checkbox next to :guilabel:`Packages`. Click :guilabel:`Save` to confirm the change." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:-1 -msgid "The Packages setting on the Inventory app settings page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:24 -msgid "Ship items in multiple packages" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:26 -msgid "To split items in the same delivery order across multiple packages, begin by navigating to :menuselection:`Inventory --> Delivery Orders`, then select a delivery order that has multiple items, a multiple quantity of the same item, or both." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:30 -msgid "On the :guilabel:`Operations` tab, select the :guilabel:`⁞≣ (menu)` icon in the line of the product that will be shipped in the first package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:-1 -msgid "The menu icon for a product in a delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:37 -msgid "This makes a :guilabel:`Detailed Operations` pop-up window appear. In the table at the bottom of the pop-up window, the :guilabel:`Reserved` column shows the total quantity of the product included in the delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:41 -msgid "If the full quantity will be shipped in the first package, enter the number from the :guilabel:`Done` column in the :guilabel:`Reserved` column. If less than the full quantity will be shipped in the first package, enter a smaller number than the one that appears in the :guilabel:`Reserved` column. Click :guilabel:`Confirm` to confirm the :guilabel:`Done` quantities and close the pop-up." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:-1 -msgid "The Detailed Operations pop-up for a product in a delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:51 -msgid "Repeat the same steps for every item quantity that is included in the first package. Then, click :guilabel:`Put In Pack` to create a package with all of the selected items." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:-1 -msgid "The Put In Pack button on a delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:58 -msgid "For the next package, follow the same steps as detailed above, marking the quantity of each item to be included in the package as :guilabel:`Done` before clicking :guilabel:`Put In Pack` on the delivery order. Continue doing so until the full quantity of all items are added to a package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:62 -msgid "Finally, after all of the packages have been shipped, click :guilabel:`Validate` to confirm that the delivery order has been completed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:66 -msgid "After one or more packages are created, a :guilabel:`Packages` smart button appears in the top-right corner of the delivery order. Click the :guilabel:`Packages` smart button to go to the :guilabel:`Packages` page for the delivery order, where each package can be selected to view all of the items included in it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:0 -msgid "The Packages smart button on a delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:76 -msgid "Create a backorder for items to be shipped later" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:78 -msgid "If some items will be shipped at a later date than others, there is no need to put them in a package until they are ready to be shipped. Instead, create a backorder for the items being shipped later." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:81 -msgid "Begin by shipping the items that will be shipped immediately. If they will be shipped in multiple packages, follow the :ref:`steps above ` to package them as required. If they will be shipped in a single package, simply mark in the :guilabel:`Done` column the quantity of each item being shipped, but **do not** click the :guilabel:`Put In Pack` button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:86 -msgid "After all quantities being shipped immediately are marked as :guilabel:`Done`, click the :guilabel:`Validate` button, and a :guilabel:`Create Backorder?` pop-up window appears. Then, click the :guilabel:`Create Backorder` button. Doing so confirms the items being shipped immediately and creates a new delivery order for the items that will be shipped later." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:-1 -msgid "The Create Backorder? pop-up window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:95 -msgid "The backorder delivery order will be listed in the chatter of the original delivery order in a message that reads :guilabel:`The backorder WH/OUT/XXXXX has been created.`. Click on :guilabel:`WH/OUT/XXXXX` in the message to view the backorder delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:-1 -msgid "The backorder delivery order listed in the chatter of the original delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:103 -msgid "The backorder delivery order can also be accessed by navigating to :menuselection:`Inventory`, clicking the :guilabel:`# Back Orders` button on the :guilabel:`Delivery Orders` card, and selecting the delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:-1 -msgid "The Back Orders button on the Delivery Orders card." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:111 -msgid "Once the remaining items are ready to be shipped, navigate to the backorder delivery order. The items can be shipped in a single package by clicking :guilabel:`Validate` and selecting :guilabel:`Apply` on the :guilabel:`Immediate Transfer?` pop-up window that appears, or shipped in multiple packages by following the steps detailed in the section above." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:116 -msgid "It is also possible to ship out some of the items while creating another backorder for the rest. To do so, simply follow the same steps used to create the first backorder." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:3 -msgid "Printable delivery PDFs" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:5 -msgid "Automatically print delivery-related PDFs documents and labels in Odoo, containing package recipient details, contents, or handling instructions." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:8 -msgid "The following PDFs can be configured to print upon validating an *Inventory* operation (e.g. receipt, picking, delivery orders, quality checks):" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:11 -msgid ":ref:`Delivery slip `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:12 -msgid ":ref:`Return slip `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:13 -msgid ":ref:`Product labels of items in the order `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:14 -msgid ":ref:`Lot and serial number labels `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:15 -msgid ":ref:`Carrier labels `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:16 -msgid ":ref:`Export documents `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:17 -msgid ":ref:`Package content `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:18 -msgid ":ref:`Package label `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:22 -msgid "To automatically print these forms, navigate to :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired operation type." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:25 -msgid "In the :guilabel:`Hardware` tab, tick each of the desired options available in the :guilabel:`Print on Validation` section to download the PDF of those selected documents automatically after validating the :guilabel:`Operation Type`. For details on what each of the checkbox options do, jump to the related section." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:-1 -msgid "Show the *Print on Validation* option in the \"Pick\" *Operation Type*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:37 -msgid "Delivery slip" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:39 -msgid "A *delivery slip* contains recipient and package details, usually placed inside (or attached to) the package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:43 -msgid ":ref:`Picking list `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:44 -msgid ":doc:`Tracking label <../setup_configuration/labels>`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:46 -msgid "After :ref:`enabling the Delivery Slip setting ` in the :guilabel:`Hardware` tab configuration options, clicking :guilabel:`Validate` on the desired operation type downloads a PDF of the delivery slip." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:50 -msgid "The delivery slip shows products, quantities, the delivery order reference number, and the total order weight." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:-1 -msgid "Example delivery slip." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:60 -msgid "Return slip" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:62 -msgid "Print a *return slip* to include in a delivery for customer return packages. It identifies the return, links to the sales order, and includes item details and customer information. It can also include specific return instructions for the customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:66 -msgid "After :ref:`enabling the Return Slip setting ` in the :guilabel:`Hardware` tab configuration options, clicking :guilabel:`Validate` on the desired operation type downloads a PDF of the return slip." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:70 -msgid "The return slip displays the company's return address, along with barcodes for both the order and the return operation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:-1 -msgid "Example return slip." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:80 -msgid "Product labels" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:82 -msgid "Print *product labels* to affix to items in an order, providing essential information, such as product name, barcode, and price." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:85 -msgid "After navigating to the intended operation type (:menuselection:`Inventory app --> Configuration --> Operations Types`), in the :guilabel:`Hardware` tab, tick the :guilabel:`Product Labels` option." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:88 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:141 -msgid "Doing so makes the :guilabel:`Print label as:` drop-down menu visible, where each product label can be printed as:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:91 -msgid ":guilabel:`2 x 7 with price`: PDF displays product name, barcode, and price, fitting two rows and seven columns of product labels per page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 -msgid "Example 2 x 7 with price." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:100 -msgid ":guilabel:`4 x 7 with price`: displays product name, barcode, and price, fitting four rows and seven columns of product labels per page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 -msgid "Example 4 x 7 with price." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:109 -msgid ":guilabel:`4 x 12`: displays product name and barcode. Fits four rows and twelve columns of product labels per page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 -msgid "Example 4 x 12." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:118 -msgid ":guilabel:`4 x 12 with price`: displays product name, barcode, and price. Fits four rows and twelve columns of product labels per page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:120 -msgid ":guilabel:`ZPL Labels`: prints labels in the Zebra Programming Language (ZPL) containing the product name and barcode. Readable for Zebra printers to automatically print labels." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:122 -msgid ":guilabel:`ZPL Labels with price`: prints labels in the :abbr:`ZPL (Zebra Programming Language)` containing the product name, barcode, and price." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:126 -msgid "Product labels can be manually printed from any delivery order, by clicking the :guilabel:`Print Labels` button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:132 -msgid "Lot/SN Labels" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:134 -msgid "Print *lot/SN labels* to affix to items in an order, providing essential information, such as product name, lot or serial number, and the barcode." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:137 -msgid "To automatically print this PDF, navigate to the intended operation type's options page (:menuselection:`Inventory app --> Configuration --> Operations Types`). Then, in the :guilabel:`Hardware` tab, tick the :guilabel:`Lot/SN Labels` option." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:144 -msgid ":guilabel:`4 x 12 - One per lot/SN`: PDF with labels for unique lot/serial numbers in the order, including product name, lot/serial number, and barcode. Fits four rows and twelve columns per page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 -msgid "Order with only one unique set of lot/serial numbers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:154 -msgid "Labels for an order with only one unique set of lot/serial numbers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:156 -msgid ":guilabel:`4 x 12 - One per unit`: PDF with labels matching the quantity of items, displaying the product name, lot/serial number, and barcode. Fits four rows and twelve columns per page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:158 -msgid ":guilabel:`ZPL Labels - One per lot/SN`: prints labels in :abbr:`ZPL (Zebra Programming Language)`, containing the product name, lot/serial number, and barcode." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:160 -msgid ":guilabel:`ZPL Labels - One per unit`: prints labels with the quantity of items in :abbr:`ZPL (Zebra Programming Language)`, containing the product name, lot/serial number, and barcode." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:166 -msgid "Carrier labels" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:168 -msgid "To automatically print a *carrier label* with the recipient address, tracking number, and carrier details for specific third-party shipping carriers, complete the following setup:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:171 -msgid "Tick the :guilabel:`Carrier Labels` checkbox in the :ref:`operation type settings `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:173 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:258 -msgid ":doc:`Connect a printer <../../../../general/iot/devices/printer>` to Odoo's *IoT* app." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:174 -msgid ":ref:`Assign the carrier label to the printer `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:175 -msgid "Configure the shipping method's :ref:`label type `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:180 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:262 -msgid "Assign printer" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:182 -msgid "Refer to the :doc:`Connect a printer <../../../../general/iot/devices/printer>` documentation for details on connecting a printer to Odoo's *IoT* app. Upon completion, assign the carrier label to the printer, by navigating to :menuselection:`IoT app --> Devices`, and selecting the desired printer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:-1 -msgid "Show a list of IoT devices." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:191 -msgid "In the printer configuration form, go to the :guilabel:`Printer Reports` tab to configure the types of documents the printer automatically prints. Click :guilabel:`Add a line` to open the :guilabel:`Add: Reports` pop-up window. In the :guilabel:`Search...` bar, type `Shipping`, and select :guilabel:`Shipping Labels`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:197 -msgid "The :guilabel:`Shipping Documents` report is for :ref:`export documents `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:-1 -msgid "Show carrier label report added to the *Printer Reports*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:204 -msgid "After adding the :guilabel:`Shipping Labels` report in the :guilabel:`Printer Reports` tab, ensure the :guilabel:`Report Type` matches the IoT-connected printer's type." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:207 -msgid "For laser printers, set the :guilabel:`Report Type` to :guilabel:`PDF`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:208 -msgid "For Zebra printers, set the :guilabel:`Report Type` to :guilabel:`Text`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:213 -msgid "Shipping carrier label type" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:215 -msgid "Next, complete the setup for the :doc:`third-party shipping connector <../setup_configuration/third_party_shipper>`. After that, go to :menuselection:`Inventory app --> Configuration --> Shipping Methods`, and select the desired shipping method." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:219 -msgid "On the shipping method configuration form, in the :guilabel:`[carrier name] Configuration` tab, ensure the :guilabel:`Label Format` matches the :ref:`report type assigned earlier `:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:223 -msgid "For laser printers, set the :guilabel:`Label Format` to :guilabel:`PDF`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:224 -msgid "For Zebra printers, set the :guilabel:`Label Format` to :guilabel:`ZPL2`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:-1 -msgid "Show the *Label Type* field on FedEx's shipping method configuration page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:231 -msgid "Example carrier label" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:233 -msgid "After validating the operation, the carrier label is generated in the chatter, and printed using the IoT-connected printer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 -msgid "Show an example carrier label for FedEx." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:242 -msgid "Carrier label for FedEx, containing the recipient address, tracking number, barcode, and other shipping information." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:246 -msgid ":doc:`Print carrier labels <../setup_configuration/labels>`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:251 -msgid "Export document" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:253 -msgid "An *export document*, required by customs to ship packages from one country to another, can be automatically printed in Odoo by following these steps:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:256 -msgid "Tick the :guilabel:`Export Documents` checkbox in the :ref:`operation type settings `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:259 -msgid "Assign the export document to the printer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:264 -msgid "Similar to the :ref:`printer assignment instructions for carrier labels `, after connecting a compatible printer to the Odoo *IoT* app, go to :menuselection:`IoT app --> Devices`, and select the desired printer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:268 -msgid "In the printer configuration form, go to the :guilabel:`Printer Reports` tab, and click :guilabel:`Add a line`. In the :guilabel:`Add: Reports` pop-up window that appears, add the :guilabel:`Shipping Documents` report to assign the export document to the printer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:278 -msgid "Export document for a shipment from the USA to Belgium." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:283 -msgid "Package content" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:285 -msgid "A *package content* PDF includes the package's barcode, packed date, along with a list of contained products and quantities." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:288 -msgid "To print this form automatically, go to :menuselection:`Inventory app --> Configuration --> Operation Types`, and select the desired operation type. Then, go to the :guilabel:`Hardware` tab, and tick the :guilabel:`Package Contents` checkbox." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:293 -msgid "If the option is not available, enable the :doc:`Packages <../../product_management/product_tracking/package>` feature, by going to :menuselection:`Inventory app --> Configuration --> Settings`, ticking the :guilabel:`Packages` checkbox, and clicking :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:298 -msgid "After enabling the feature in the :guilabel:`Hardware` tab, validating the operation prints a PDF of the package contents." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 -msgid "Package contents form showing the package contents, barcode, and pack date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:307 -msgid "Package contents showing the package contents, barcode, and pack date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:312 -msgid "Package label" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:314 -msgid "A *package label* that shows the package's barcode and pack date can be configured to print upon clicking the *Put in Pack* button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:318 -msgid "The :guilabel:`Put in Pack` button is available **only** when the :doc:`Packages <../../product_management/product_tracking/package>` feature is enabled in :menuselection:`Inventory app --> Configuration --> Settings`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:322 -msgid "After it is enabled, the :guilabel:`Put in Pack` button is available on all inventory operations (e.g. receipt, pickings, internal transfers, delivery orders, etc.)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:325 -msgid "To automatically print the package label when the :guilabel:`Put in Pack` button is clicked, go to :menuselection:`Inventory app --> Configuration --> Operation Types`. Select the desired operation type, and tick the :guilabel:`Package Label` checkbox in the :guilabel:`Hardware` tab. Labels can be printed in :guilabel:`PDF` or :guilabel:`ZPL` file formats, as defined in the :guilabel:`Print label as` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 -msgid "PDF of package barcode and package date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:3 -msgid "Scheduled delivery dates" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:10 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:15 -msgid "Lead time types" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:17 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 -msgid "Show graphic of all lead times working together." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:24 -msgid ":ref:`Customer lead time `: 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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:29 -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 ample time to prepare the outgoing shipment earlier, considering the possibility of delays in the fulfillment process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:34 -msgid ":ref:`Purchase lead time `: 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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:39 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:45 -msgid ":ref:`Days to Purchase `: days needed for the vendor to receive a request for quotation (RFQ) and confirm it. It advances the deadline to schedule a |RFQ| by a specified number of days." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:49 -msgid ":ref:`Manufacturing lead time `: 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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:54 -msgid ":ref:`Days to prepare manufacturing order `: number of days needed to replenish components, or manufacture sub-assemblies of the product. Either set one directly on the bill of materials (BoM), or click *Compute* to sum up purchase and manufacturing lead times of components in the |BoM|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:60 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:69 -msgid "Sales lead times" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:71 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:75 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:79 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 -msgid "Set *Delivery Date* in a sales order. Enables delivery lead times feature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:87 -msgid "The following sections demonstrate how to automatically compute expected delivery dates." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:90 -msgid "Customer lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:92 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:98 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 -msgid "Set *Customer Lead Time* on the product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:109 -msgid "Sales security lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:111 -msgid "*Sales security lead time* is set globally for the business in :menuselection:`Inventory app --> Configuration --> Settings`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:114 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:117 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:121 -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/shipping_receiving/advanced_operations_shipping/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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:131 -msgid "Deliver several products" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:133 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:137 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:141 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 -msgid "Show *Shipping Policy* field in the *Other Info* tab of a quotation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:150 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:153 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:160 -msgid "Purchase lead times" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:162 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:165 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:170 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 -msgid "Visualization of PO deadline and receipt date used with vendor lead times." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:178 -msgid ":ref:`PO scheduling with reordering rules `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:181 -msgid "Vendor lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:183 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:186 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:192 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:196 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 -msgid "Add delivery lead times to vendor pricelist on a product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:203 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:209 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 -msgid "Show expected *Receipt Date* of the product from the vendor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 -msgid "Show expected *Scheduled Date* of arrival of the product from the vendor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:225 -msgid "Purchase security lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:227 -msgid "*Purchase security lead time* is set globally for the business in :menuselection:`Inventory app --> Configuration --> Settings`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:230 -msgid "On the :guilabel:`Settings` page, under the :guilabel:`Advanced Scheduling` heading, tick the checkbox for :guilabel:`Security Lead Time for Purchase`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:233 -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. Then, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:237 -msgid "Setting the :guilabel:`Security Lead Time for Purchase` to `2.00` days, pushes the :guilabel:`Scheduled Date` of receipt back by two days. 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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 -msgid "Set security lead time for purchase from the Inventory > Configuration > Settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:249 -msgid "Days to purchase" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:251 -msgid "To set up the *days to purchase* lead time, go to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Advanced Scheduling` section, in the :guilabel:`Days to Purchase` field, specify the number of days required for the vendor to confirm a |RFQ| after receiving it from the company." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 -msgid "Show \"Days to Purchase\" configuration in the Settings page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:263 -msgid "Manufacturing lead times" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:265 -msgid "Lead times can help simplify the procurement process for consumable materials and components used in manufactured products with bills of materials (BoMs)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:268 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 -msgid "Visualization of the determination of planned MO date manufacturing lead times." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:277 -msgid "Manufacturing lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:279 -msgid "Manufacturing lead times for products are configured from a product's bill of materials (BoM) form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:281 -msgid "To add a lead time to a |BoM|, navigate to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and select the desired |BoM| to edit." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:284 -msgid "On the |BoM| form, click the :guilabel:`Miscellaneous` tab. Change the value (in days) in the :guilabel:`Manuf. Lead Time` field to specify the calendar days needed to manufacture the product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 -msgid "Manuf. Lead Time value specified on a product's Bill of Material form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:292 -msgid "If the selected |BoM| is a multi-level |BoM|, the manufacturing lead times of the components are added." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:295 -msgid "If the |BoM| product is subcontracted, the :guilabel:`Manuf. Lead Time` can be used to determine the date at which components should be sent to the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:298 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:301 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:305 -msgid "This ensures the manufacturing process begins on time, in order to meet the delivery date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:307 -msgid "However, it is 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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:312 -msgid ":doc:`Manufacturing planning <../../../manufacturing/workflows/use_mps>`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:313 -msgid ":doc:`Schedule MOs with reordering rules <../../product_management/product_replenishment/reordering_rules>`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:317 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:324 -msgid "Days to prepare manufacturing order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:326 -msgid "Configure the days required to gather components to manufacture a product by going to its |BoM|. To do that, go to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and select the desired |BoM|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:330 -msgid "In the :guilabel:`Miscellaneous` tab of the |BoM|, specify the calendar days needed to obtain components of the product in the :guilabel:`Days to prepare Manufacturing Order` field. Doing so creates |MOs| in advance, and ensures there is enough time to either replenish components, or manufacture semi-finished products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:336 -msgid "Clicking :guilabel:`Compute`, located next to the :guilabel:`Days to prepare Manufacturing Order` field, calculates the longest lead time among all the components listed on the |BoM|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:339 -msgid "*Purchase security lead times* that impact this specific |BoM| are also added to this value." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:343 -msgid "A |BoM| has two components, one has a manufacturing lead time of two days, and the other has a purchase lead time of four days. The :guilabel:`Days to prepare Manufacturing Order` is four days." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:350 -msgid "Manufacturing security lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:352 -msgid "*Manufacturing security lead time* is set globally for the business in :menuselection:`Manufacturing app --> Configuration --> Settings`. Under the :guilabel:`Planning` heading, tick the checkbox for :guilabel:`Security Lead Time`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:356 -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. Then, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:364 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:371 -msgid "Global example" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:373 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:376 -msgid "**Sales security lead time**: 1 day" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:377 -msgid "**Manufacturing security lead time**: 2 days" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:378 -msgid "**Manufacturing lead time**: 3 days" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:379 -msgid "**Purchase security lead time**: 1 day" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:380 -msgid "**Vendor lead time**: 4 days" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:382 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 -msgid "Show timeline of how lead times work together to schedule warehouse operations." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:390 -msgid "**September 1st**: Sales order created, confirmed by salesperson." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:392 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:395 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:398 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:402 -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/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:406 -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." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:86 +msgid "The delivery order is now ready to be processed and can be validated too." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:3 -msgid "Process deliveries in three steps" +msgid "Three-step delivery" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:7 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:5 msgid "Some companies process large amounts of deliveries every day, many of which include multiple products or require special packaging. To make this efficient, a packing step is needed before shipping out products. For this, Odoo has a three step process for delivering goods." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:9 msgid "In the default three-step delivery process, products that are part of a delivery order are picked in the warehouse according to their removal strategy, and brought to a packing zone. After the items have been packed into the different shipments in the packing zone, they are brought to an output location before being shipped. These steps can be modified if they do not fit the needs of the business." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:20 -msgid "Odoo is configured by default to :ref:`receive and deliver goods in one step `, so the settings need to be changed in order to utilize three step deliveries. First, make sure the *Multi-Step Routes* option is enabled in :menuselection:`Inventory --> Configuration --> Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes` will also activate *Storage Locations*." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:18 +msgid "To change delivery settings from :doc:`one step ` to three steps, make sure the *Multi-Step Routes* option is enabled in :menuselection:`Inventory app --> Configuration --> Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes` will also activate *Storage Locations*." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 msgid "Activate multi-step routes and storage locations in inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:27 msgid "Next, the warehouse needs to be configured for three step deliveries. To do this, go to :menuselection:`Inventory app --> Configuration --> Warehouses`, and click on the :guilabel:`warehouse` to edit. Then, select :guilabel:`Pack goods, send goods in output and then deliver (3 steps)` for :guilabel:`Outgoing Shipments`." msgstr "" @@ -6634,19 +4904,24 @@ msgstr "" msgid "Set outgoing shipment option to deliver in three steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:36 msgid "Activating three-step receipts and deliveries creates two new internal locations: a *Packing Zone* (WH/Packing Zone), and *Output* (WH/Output). To rename these locations, go to :menuselection:`Inventory app --> Configuration --> Locations`, click on the :guilabel:`Location` to change, and update the name." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:42 msgid "Deliver in three steps (pick + pack + ship)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:35 +msgid "Create a sales order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:47 msgid "To create a new quote, navigate to :menuselection:`Sales app --> Create`, which reveals a blank quotation form. On the blank quotation form, select a :guilabel:`Customer`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:54 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:51 msgid "A :guilabel:`Delivery` smart button appears in the top right of the quotation form. Clicking it opens the picking order to move the ordered product from `WH/Stock` to `WH/Packing Zone`." msgstr "" @@ -6655,19 +4930,19 @@ msgid "After confirming the sales order, the Delivery smart button appears showi "associated with it." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:63 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:60 msgid "Process a picking" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:62 msgid "The picking order will be created once the sales order is confirmed. To view the picking, navigate to the :menuselection:`Inventory app`, and locate the :guilabel:`Pick` task card on the :guilabel:`Inventory Overview` dashboard." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:66 msgid "Click the :guilabel:`# To Process` button, which reveals the picking order generated from the previously confirmed sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:72 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:69 msgid "Click on the picking to process. If the product is in stock, Odoo will automatically reserve the product. Click :guilabel:`Validate` to mark the picking as done, and complete the transfer to the :guilabel:`Packing Zone`." msgstr "" @@ -6675,19 +4950,19 @@ msgstr "" msgid "Picking order operation showing source location and destination location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:78 msgid "Process a packing" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:83 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:80 msgid "After validating the picking, the packing order is ready to process. Click back to the :guilabel:`Inventory Overview`, and locate the :guilabel:`Pack` task card on the dashboard." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:86 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:83 msgid "Click the :guilabel:`# To Process` button (in this case, :guilabel:`1 To Process`). This reveals the packing order generated from the previously confirmed sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:86 msgid "Click on the packing order associated with the sales order, then click on :guilabel:`Validate` to complete the packing." msgstr "" @@ -6695,27 +4970,27 @@ msgstr "" msgid "Packing order operation showing source location and destination location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:93 msgid "Once the packing order is validated, the product leaves the :guilabel:`WH/Packing Zone` location and moves to the :guilabel:`WH/Output` location. Then, the status of the document will change to :guilabel:`Done`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:98 msgid "Process a delivery" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:100 msgid "Once the packing order has been validated, the delivery order is ready to process. Navigate back to the original sales order to process the delivery by going to :menuselection:`Sales app`, and selecting the sales order created previously." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:105 msgid "Delivery orders can *also* be accessed by going to :menuselection:`Inventory app --> Operations --> Deliveries`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:111 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:108 msgid "The :guilabel:`Delivery` smart button now indicates there are 3 transfers, instead of one. Clicking the :guilabel:`Delivery` smart button shows the three operations for this sales order: the picking, the packing, and the delivery." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:112 msgid "Click the delivery (WH/OUT) transfer to open the delivery order. Then, click :guilabel:`Validate`." msgstr "" @@ -6724,32 +4999,364 @@ msgid "Click Validate on the delivery order to transfer the product from the out "the customer location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:122 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:119 msgid "Once the delivery order is validated, the product leaves the :guilabel:`WH/Output` location and moves to the :guilabel:`Partners/Customers` location. Then, the status of the document will change to :guilabel:`Done`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:3 -msgid "Process receipts and deliveries in one step" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:3 +msgid "Dropshipping" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:7 +msgid "Dropshipping is an order fulfillment strategy that allows sellers to have items shipped directly from suppliers to customers. Normally, a seller purchases a product from a supplier, stores it in their inventory, and ships it to the end customer once an order is placed. With dropshipping, the supplier is responsible for storing and shipping the item. This benefits the seller by reducing inventory costs, including the price of operating warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:14 +msgid "Configure products to be dropshipped" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:16 +msgid "To use dropshipping as a fulfillment strategy, navigate to the :menuselection:`Purchase` app and select :menuselection:`Configuration --> Settings`. Under the :guilabel:`Logistics` heading, click the :guilabel:`Dropshipping` checkbox, and :guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:20 +msgid "Next, go to the :menuselection:`Sales` app, click :menuselection:`Products --> Products` and choose an existing product or select :guilabel:`Create` to configure a new one. On the :guilabel:`Product` page, make sure that the :guilabel:`Can be Sold` and :guilabel:`Can be Purchased` checkboxes are enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:-1 +msgid "Enable the \"Can be Sold\" and \"Can be Purchased\" checkboxes on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:29 +msgid "Click on the :guilabel:`Purchase` tab and specify a vendor and the price that they sell the product for. Multiple vendors can be added, but the vendor at the top of the list will be the one automatically selected for purchase orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:-1 +msgid "The product form with a vendor specified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:37 +msgid "Finally, select the :guilabel:`Inventory` tab and enable the :guilabel:`Dropship` checkbox in the :guilabel:`Routes` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:-1 +msgid "Enable the Dropship option in the product inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:45 +msgid "While it is not necessary to enable the :guilabel:`Buy` route in addition to the :guilabel:`Dropship` route, enabling both provides the option of dropshipping the product or purchasing it directly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:50 +msgid "Fulfill orders using dropshipping" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:52 +msgid "When a sales order is created for a dropshipped product, an associated request for quotation (RfQ) is automatically generated to purchase the product from the vendor. Sales orders can be viewed in the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders`. Click the :guilabel:`Purchase` smart button at the top right of a sales order to view the associated :abbr:`RFQ (Request for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:-1 +msgid "A dropship sales order with the Purchase smart button in the top right corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:62 +msgid "Once the :abbr:`RFQ (Request for Quotation)` is confirmed, it becomes a purchase order, and a dropship receipt is created and linked to it. The receipt can be viewed by clicking the :guilabel:`Dropship` smart button in the top-right corner of the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:-1 +msgid "A dropship purchase order with the Receipt smart button in the top right corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:70 +msgid "The dropship receipt displays :guilabel:`Partners/Vendors` in the :guilabel:`Source Location` field, and :guilabel:`Partners/Customers` in the :guilabel:`Destination Location` field. Upon delivery of the product to the customer, click on the :guilabel:`Validate` button at the top-left of the dropship receipt to confirm the delivered quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:-1 +msgid "Validate the dropship receipt after delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:79 +msgid "To view all dropship orders, simply navigate to the :menuselection:`Inventory` :guilabel:`Overview` dashboard and click the teal :guilabel:`# TO PROCESS` button on the :guilabel:`Dropship` card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:-1 +msgid "Click the green button on the Dropship card to view all dropship orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:3 +msgid "Consignment: buy and sell stock without owning it" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:5 +msgid "Most of the time, products stored in a company's warehouse are either purchased from suppliers, or are manufactured in-house. However, suppliers will sometimes let companies store and sell products in the company's warehouse, without having to buy those items up-front. This is called *consignment*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:10 +msgid "Consignment is a useful method for suppliers to launch new products, and easily deliver to their customers. It's also a great way for the company storing the products (the consignee) to earn something back for their efforts. Consignees can even charge a fee for the convenience of storing products they don't actually own." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:16 +msgid "Enable the consignment setting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:18 +msgid "To receive, store, and sell consignment stock, the feature needs to be enabled in the settings. To do this, go to :menuselection:`Inventory --> Configuration --> Settings`, and under the :guilabel:`Traceability` section, check the box next to :guilabel:`Consignment`, and then click :guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:-1 +msgid "Enabled Consignment setting in Inventory configuration." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:28 +msgid "Receive (and store) consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:30 +msgid "With the feature enabled in Odoo, consignment stock can now be received into a warehouse. From the main :menuselection:`Inventory` dashboard, click into the :guilabel:`Receipts` section. Then, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:35 +msgid "Consignment stock is not actually purchased from the vendor; it is simply received and stored. Because of this, there are no quotations or purchase orders involved in receiving consignment stock. So, *every* receipt of consignment stock will start by creating manual receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:39 +msgid "Choose a vendor to enter in the :guilabel:`Receive From` field, and then choose the same vendor to enter in the :guilabel:`Assign Owner` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:43 +msgid "Since the products received from the vendor will be owned by the same vendor, the :guilabel:`Receive From` and :guilabel:`Assign Owner` fields must match." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:46 +msgid "Once the vendor-related fields are set, enter products into the :guilabel:`Product` lines, and set the quantities to be received into the warehouse under the :guilabel:`Done` column. If the :guilabel:`Units of Measure` feature is enabled, the :abbr:`UoM (Units of Measure)` can be changed, as well. Once all the consignment stock has been received, :guilabel:`Validate` the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:-1 +msgid "Matching vendor fields in consignment Receipt creation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:56 +msgid "Sell and deliver consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:58 +msgid "Once consignment stock has been received into the warehouse, it can be sold the same as any other in-stock product that has the :guilabel:`Can Be Sold` option enabled on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:61 +msgid "To create a sales order, navigate to the :menuselection:`Sales` app, and from the :guilabel:`Quotations` overview, click :guilabel:`Create`. Next, choose a customer to enter into the :guilabel:`Customer` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:66 +msgid "The :guilabel:`Customer` *must* be different from the :guilabel:`Vendor` that supplied the consignment stock received (and stored) in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:69 +msgid "Add the consignment product under the :guilabel:`Product` column in the order lines, set the :guilabel:`Quantity`, and fill out any other pertinent product details on the form. Once the quotation is complete, click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:-1 +msgid "Sales order of consignment stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:77 +msgid "Once the :abbr:`RFQ (Request for Quotation)` has been confirmed, it will become a sales order. From here, the products can be delivered by clicking on the :guilabel:`Delivery` smart button, and selecting :guilabel:`Validate` to validate the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:82 +msgid "Traceability and reporting of consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:84 +msgid "Although consignment stock is owned by the vendor who supplied it, and not by the company storing it in their warehouse, consignment products will *still* appear in certain inventory reports." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:87 +msgid "To find inventory reports, go to :menuselection:`Inventory --> Reporting`, and choose a report to view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:91 +msgid "Since the consignee does not actually own consigment stock, these products are *not* reflected in the :guilabel:`Stock Valuation` report, and have no impact on the consignee's inventory valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:96 +msgid "Product moves report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:98 +msgid "To view all information about on-hand stock moves, navigate to the the :guilabel:`Product Moves` dashboard by going to :menuselection:`Inventory --> Reporting --> Product Moves`. For consignment products, the information in this report is the same as any other product: the history of its product moves can be reviewed; the :guilabel:`Quantity Done` and :guilabel:`Reference` document are available; and its :guilabel:`Locations` are available, as well. The consignment stock will originate from :guilabel:`Partner Location/Vendors`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:106 +msgid "To view a consignment product's moves by ownership, select the :guilabel:`Group By` filter, choose the :guilabel:`Add Custom Group` parameter, and then select :guilabel:`From Owner`, and :guilabel:`Apply` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:-1 +msgid "Consignment stock moves history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:115 +msgid "To see forecasted units of consignment stock, go to :menuselection:`Inventory --> Reporting --> Forecasted Inventory`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:119 +msgid "Stock on hand report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/owned_stock.rst:121 +msgid "View the :guilabel:`Stock On Hand` dashboard by navigating to :menuselection:`Inventory --> Reporting --> Inventory Report`. From this report, the :guilabel:`Locations` of all stock on-hand are displayed, in addition to the quantities per location. For consigment products, the :guilabel:`Owner` column will be populated with the owner of those products, or the original vendor who supplied the products in the first place." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:3 +msgid "Putaway rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:5 +msgid "Putaway is the process of routing products to appropriate storage locations upon shipment arrival." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:7 +msgid "Odoo can accomplish this seamlessly using *putaway rules*, which dictate how products move through specified warehouse locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:10 +msgid "Upon shipment arrival, operations are generated based on putaway rules to efficiently move products to specified locations, and ensure easy retrieval for future delivery orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:13 +msgid "In warehouses that process specific kinds of products, putaway rules can also prevent volatile substances from being stored in close proximity, by directing them to different locations determined by the warehouse manager." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:18 +msgid "`Odoo Tutorials: Putaway Rules `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:23 +msgid "To use putaway rules, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and activate the :guilabel:`Multi-Step Routes` feature under the :guilabel:`Warehouse` section. By doing so, the :guilabel:`Storage Locations` feature is also automatically activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:27 +msgid "Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:-1 +msgid "Activate Multi-Step Routes in Inventory configuration settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:36 +msgid "Define putaway rule" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:38 +msgid "To manage where specific products are routed for storage, navigate to :menuselection:`Inventory app --> Configuration --> Putaway Rules`. Use the :guilabel:`Create` button to configure a new putaway rule on a :guilabel:`Product` or :guilabel:`Product Category` that the rule affects." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:43 +msgid "Putaway rules can be defined either per product/product category, and/or package type (the *Packages* setting must be enabled in :menuselection:`Inventory app --> Configuration --> Settings` for that)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:47 +msgid "In the same line, the :guilabel:`When product arrives in` location is where the putaway rule is triggered to create an operation to move the product to the :guilabel:`Store to` location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:50 +msgid "For this to work, the :guilabel:`Store to` location must be a *sub-location* of the first (e.g., `WH/Stock/Fruits` is a specific, named location inside `WH/Stock` to make the products stored here easier to find)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:55 +msgid "In a warehouse location, **WH/Stock**, there are the following sub-locations:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:57 +msgid "WH/Stock/Fruits" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:58 +msgid "WH/Stock/Vegetables" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:60 +msgid "Ensure all apples are stored in the fruits section by filling the field :guilabel:`Store to` with the location `WH/Stock/Fruits` when the :guilabel:`Product`, `Apple` arrives in `WH/Stock`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:63 +msgid "Repeat this for all products and hit :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:0 +msgid "Create putaway rules for apples and carrots." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:70 +msgid "Putaway rule priority" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:72 +msgid "Odoo selects a putaway rule based on the following priority list (from highest to lowest) until a match is found:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:75 +msgid "Package type and product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:76 +msgid "Package type and product category" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:79 +msgid "Product category" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:82 +msgid "The product `Lemonade can` has the following putaway rules configured:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:84 +msgid "When receiving a `Pallet` (:guilabel:`Package Type`) of `Lemonade cans`, it is redirected to `WH/Stock/Pallets/PAL1`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:86 +msgid "`Lemonade can`'s :guilabel:`Product Category` is `All/drinks`, and when receiving a `Box` of any item in this product category, items are redirected to `WH/Stock/Shelf 1`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:88 +msgid "Any product on a `Pallet` is redirected to `WH/Stock/Pallets`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:89 +msgid "The product `Lemonade can` is redirected to `WH/Stock/Shelf 2`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:90 +msgid "Items in the `All/drinks` product category are redirected to `WH/Stock/Small Refrigerator`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:0 +msgid "Some examples of putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:3 +msgid "One-step receipt and delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:9 msgid "In Odoo *Inventory*, both incoming and outgoing shipments are configured to process in one step, by default. This means purchases will be received directly into stock, and deliveries will be moved directly from stock to customers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:14 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:28 msgid "Incoming and outgoing shipments do **not** need to be configured with the same amount of steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:16 msgid "For example, a warehouse's settings can be configured so products can be received directly in one step, and delivered in three steps (pick + pack + ship)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:24 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:22 msgid "To configure one-step receipts and deliveries for a warehouse, navigate to :menuselection:`Inventory app --> Configuration --> Warehouses`, and select a warehouse to edit." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:25 msgid "Under the :guilabel:`Warehouse Configuration` tab, set :guilabel:`Incoming Shipments` to :guilabel:`Receive goods directly (1 step)`, and set :guilabel:`Outgoing Shipments` to :guilabel:`Deliver goods directly (1 step)`." msgstr "" @@ -6757,33 +5364,33 @@ msgstr "" msgid "Incoming and outgoing shipments set to one-step on warehouse form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:34 msgid "Since one-step receipt and delivery is the default for incoming and outgoing shipments in Odoo, the *Multi-Step Routes* feature is *not* required." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:37 msgid "However, for the :guilabel:`Shipments` settings to appear on a warehouse form, the feature **must** be enabled." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:42 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:41 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:39 msgid "To enable *Multi-Step Routes*, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Warehouse` section, tick the checkbox next to :guilabel:`Multi-Step Routes`, and click :guilabel:`Save`. Doing so also activates the :guilabel:`Storage Locations` feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:48 msgid "Receive goods directly (1 step)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:50 msgid "When products are received in one step, they will move from the vendor location to warehouse stock in the database immediately upon validation of a purchase order (PO)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:58 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:56 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:79 msgid "To create a |PO|, navigate to the :menuselection:`Purchase app`, and click :guilabel:`New`. This opens a blank :guilabel:`Request for Quotation` (RfQ) form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:61 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:59 msgid "Add a vendor in the :guilabel:`Supplier` field. Then, fill out the various fields on the |RfQ|, as necessary." msgstr "" @@ -6791,18 +5398,18 @@ msgstr "" msgid "Filled out new request for quotation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:68 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:66 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:89 msgid "Under the :guilabel:`Products` tab, click :guilabel:`Add a product`, and select a product to add to the |RfQ|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:71 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:92 msgid "Once ready, click :guilabel:`Confirm Order`. This moves the |RfQ| to the :guilabel:`Purchase Order` stage." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:74 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:72 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:95 msgid "Once the |PO| is confirmed, a :guilabel:`Receipt` smart button appears at the top of the form. Clicking the smart button opens the warehouse receipt (WH/IN) form." msgstr "" @@ -6810,14 +5417,14 @@ msgstr "" msgid "Receipt smart button on confirmed purchase order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:82 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:113 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:80 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:111 #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:171 #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:249 msgid "Process receipt" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:82 msgid "From the warehouse receipt form, the products ordered can be received into the warehouse. To receive the products, click :guilabel:`Validate`. Once validated, the receipt moves to the :guilabel:`Done` stage." msgstr "" @@ -6825,31 +5432,31 @@ msgstr "" msgid "Validated warehouse receipt in Done stage." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:92 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:123 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:121 msgid "Click back to the |PO| (via the breadcrumbs, at the top of the form) to view the |PO| form. On the product line, the quantity in the :guilabel:`Received` column now matches the ordered :guilabel:`Quantity`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:97 msgid "Deliver goods directly (1 step)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:99 msgid "When products are delivered in one step, they will move from warehouse stock to the customer location in the database immediately upon validation of a sales order (SO)." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:154 +msgid "Create sales order" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:105 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:156 -msgid "Create sales order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:107 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:158 msgid "To create a |SO|, navigate to the :menuselection:`Sales app`, and click :guilabel:`New`. This opens a blank sales quotation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:110 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:161 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:159 msgid "Add a customer in the :guilabel:`Customer` field. Then, fill out the various fields on the sales quotation form, as necessary." msgstr "" @@ -6857,17 +5464,17 @@ msgstr "" msgid "Filled out new sales quotation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:115 msgid "Under the :guilabel:`Product` tab, click :guilabel:`Add a product`, and select a product to add to the sales order quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:120 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:171 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:118 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:169 msgid "Once ready, click :guilabel:`Confirm`. This moves the quotation to the :guilabel:`Sales Order` stage." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:123 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:174 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:121 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:172 msgid "Once the |SO| is confirmed, a :guilabel:`Delivery` smart button appears at the top of the form. Clicking the smart button opens the warehouse delivery (WH/OUT) form." msgstr "" @@ -6875,17 +5482,17 @@ msgstr "" msgid "Delivery smart button on confirmed sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:131 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:207 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:129 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:205 msgid "Process delivery" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:133 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:131 msgid "From the warehouse delivery form, the products ordered by the customer can be delivered from the warehouse. To deliver the products, change the value in the :guilabel:`Quantity` field to match the ordered quantity in the :guilabel:`Demand` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:137 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:225 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:135 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:223 msgid "Once ready, click :guilabel:`Validate`. Once validated, the delivery order moves to the :guilabel:`Done` stage." msgstr "" @@ -6893,44 +5500,44 @@ msgstr "" msgid "Validated delivery order in Done stage." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:144 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:142 msgid "Click back to the |SO| (via the breadcrumbs, at the top of the form) to view the |SO| form. On the product line, the quantity in the :guilabel:`Delivered` column now matches the ordered :guilabel:`Quantity`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:149 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:229 -msgid ":doc:`shipments_deliveries`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:147 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:227 +msgid ":doc:`../daily_operations`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:3 -msgid "Process receipts and deliveries in two steps" +msgid "Two-step receipt and delivery" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:10 msgid "Depending on a company's needs, receiving and shipping products in and out of the warehouse might require multi-step operations. In Odoo *Inventory*, this can be done using *Multi-Step Routes*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:13 msgid "In the two-step receipt process, products are received in an input area, then transferred to stock. This kind of process for incoming shipments might be beneficial for warehouses with specific storage locations, such as freezers and refrigerators, secured locked areas, or special aisles and shelves." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:19 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:17 msgid "Products can be sorted according to where they are going to be stored, and employees can stock all the products going to a specific location. The products are *not* available for further processing, until they are transferred into stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:23 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:21 msgid "In the two-step delivery process, products are first picked from their respective location in the warehouse, then transferred to an output location before being shipped to the customer." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:26 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:24 msgid "This might be beneficial for companies using a First In, First Out (FIFO), Last In, First Out (LIFO), or First Expired, First Out (FEFO) removal strategy." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:30 msgid "For example, a warehouse's settings can be configured so products can be received in two steps (input + stock), and delivered in three steps (pick + pack + ship)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:36 msgid "In Odoo *Inventory*, both incoming and outgoing shipments are configured to process in one step, by default. To change these settings, the *Multi-Step Routes* feature must be enabled." msgstr "" @@ -6938,11 +5545,11 @@ msgstr "" msgid "Enabled Multi-Step Routes feature in Inventory app settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:48 msgid "Next, configure a warehouse for two-step receipts and deliveries. Navigate to :menuselection:`Inventory app --> Configuration --> Warehouses`, and select a warehouse to edit." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:51 msgid "Under the :guilabel:`Warehouse Configuration` tab, set :guilabel:`Incoming Shipments` to :guilabel:`Receive goods in input and then stock (2 steps)`, and set :guilabel:`Outgoing Shipments` to :guilabel:`Send goods in output and then deliver (2 steps)`." msgstr "" @@ -6950,27 +5557,27 @@ msgstr "" msgid "Incoming and outgoing shipments set to two-step on warehouse form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:60 msgid "Selecting two-step receipts and deliveries automatically creates new *Input* and *Output* warehouse locations in the database, named `WH/Input` and `WH/Output`, respectively." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:63 msgid "To rename or edit these locations, navigate to :menuselection:`Inventory app --> Configuration --> Locations`, and select the desired location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:66 msgid "On the location's form, change the :guilabel:`Location Name`, and make any other necessary changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:72 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:70 msgid "Process receipt in two steps (input + stock)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:74 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:72 msgid "When products are received in two steps, they first move from the vendor location to an input location. Then, they move from the input location to warehouse stock in the database, upon validation of a purchase order (PO), and a subsequent internal transfer." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:82 msgid "Add a vendor in the :guilabel:`Vendor` field. Then, fill out the various fields on the |RfQ|, as necessary." msgstr "" @@ -6982,15 +5589,15 @@ msgstr "" msgid "Delivery smart button for validated purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:103 msgid "For businesses with multiple warehouses that have different step configurations, the :guilabel:`Deliver To` field on the |PO| form **must** be specified as the correct *input location* connected to the two-step warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:109 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:107 msgid "This can be done by selecting the warehouse from the drop-down menu that includes the `Receipts` label at the end of the name." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:113 msgid "From the warehouse receipt form, the products ordered can be received into the warehouse. To receive the products, click :guilabel:`Validate`. Once validated, the receipt moves to the :guilabel:`Done` stage, and the products move to the :guilabel:`WH/Input` location." msgstr "" @@ -6998,27 +5605,27 @@ msgstr "" msgid "Receipt form for products ordered from vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:128 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:126 msgid "Process internal transfer" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:130 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:128 msgid "Once the receipt is validated, an internal transfer is created and ready to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:132 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:130 msgid "To view the internal transfer, navigate to the :menuselection:`Inventory app`, and locate the :guilabel:`Internal Transfers` task card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:135 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:133 msgid "Click the :guilabel:`# To Process` button on the task card to reveal a list of all internal transfers to process, and select the transfer associated with the previously validated receipt." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:138 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:136 msgid "Once ready, click :guilabel:`Validate` to complete the transfer, and move the product from :guilabel:`WH/Input` to :guilabel:`WH/Stock`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:141 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:139 msgid "Once the transfer is validated, the products enter inventory, and are available for customer deliveries or manufacturing orders." msgstr "" @@ -7026,11 +5633,11 @@ msgstr "" msgid "Internal transfer form for products ordered from vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:149 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:147 msgid "Process delivery order in two steps (pick + ship)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:151 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:149 msgid "When products are delivered in two steps, they move from warehouse stock to an output location. Then, they move from the output location to a customer location in the database, upon validation of a picking order, and a subsequent delivery order (DO)." msgstr "" @@ -7038,7 +5645,7 @@ msgstr "" msgid "Filled out new sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:168 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:166 msgid "Under the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`, and select a product to add to the sales order quotation." msgstr "" @@ -7046,23 +5653,23 @@ msgstr "" msgid "Delivery smart button on validated sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:182 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:180 msgid "Process picking" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:184 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:182 msgid "Once the sales order is confirmed, a picking order is generated and ready to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:186 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:184 msgid "To complete the picking, navigate to the :guilabel:`Inventory app`, and locate the :guilabel:`Pick` task card on the :guilabel:`Inventory Overview` dashboard. Alternatively, the picking order can also be accessed via the :guilabel:`Delivery` smart button at the top of the sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:190 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:188 msgid "From the :guilabel:`Inventory Overview` page, click the :guilabel:`# To Process` button on the :guilabel:`Pick` task card. This reveals a list of all pickings to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:193 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:191 msgid "Click on the picking (WH/PICK) operation associated with the sales order to reveal the picking order." msgstr "" @@ -7070,23 +5677,23 @@ msgstr "" msgid "Picking order form for products included in sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:200 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:198 msgid "Manually set the quantity by changing the value in the :guilabel:`Quantity` column, to match the value in the :guilabel:`Demand` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:203 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:201 msgid "Once ready, click :guilabel:`Validate` to complete the picking, and move the product from :guilabel:`WH/Stock` to :guilabel:`WH/Output.`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:209 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:207 msgid "Once the picking is validated, a delivery order is created, and ready to process. Clicking the :guilabel:`Delivery` smart button on the sales order form reveals the newly created delivery order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:212 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:210 msgid "Alternatively, to view the delivery order, navigate back to the :guilabel:`Inventory Overview` page, via the breadcrumbs, and locate the :guilabel:`Delivery Orders` task card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:215 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:213 msgid "Click the :guilabel:`# To Process` button on the task card to reveal a list of all delivery orders to process, and select the order associated with the previously validated picking." msgstr "" @@ -7094,35 +5701,35 @@ msgstr "" msgid "Delivery order form for products ordered by customer." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:222 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:220 msgid "To deliver the products, change the value in the :guilabel:`Quantity` field to match the ordered quantity in the :guilabel:`Demand` field." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:3 -msgid "Process receipts in three steps" +msgid "Three-step receipt" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:7 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:5 msgid "Some companies require a quality control process before receiving goods from suppliers. To accomplish this, Odoo has a three-step process for receiving goods." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:10 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:8 msgid "In the three-step receipt process, products are received in an input area, then transferred to a quality area for inspection. Products that pass the quality inspection are then transferred into stock. The products are not available for further processing until they are transferred out of the quality area and into stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:18 -msgid "Odoo is configured by default to :ref:`receive and deliver goods in one step `, so the settings need to be changed in order to utilize three-step receipts. First, make sure the *Multi-Step Routes* option is enabled in :menuselection:`Inventory --> Configuration --> Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes` will also activate *Storage Locations*." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:16 +msgid "Odoo is configured by default to :doc:`receive and deliver goods in one step `, so the settings need to be changed in order to utilize three-step receipts. First, make sure the *Multi-Step Routes* option is enabled in :menuselection:`Inventory --> Configuration --> Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes` will also activate *Storage Locations*." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 msgid "Activate multi-step routes and storage locations in Inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:28 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:26 msgid "Next, the warehouse needs to be configured for three-step receipts. To do that, go to :menuselection:`Inventory app --> Configuration --> Warehouses`, and select the desired warehouse to be edited. Doing so reveals the detail form for that specific warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:30 msgid "On that :guilabel:`Warehouse` detail form page, select :guilabel:`Receive goods in input, then quality and then stock (3 steps)` for :guilabel:`Incoming Shipments`." msgstr "" @@ -7130,23 +5737,23 @@ msgstr "" msgid "Set incoming shipment option to receive in three steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:37 msgid "Activating three-step receipts and deliveries creates two new internal locations: *Input* (WH/Input), and *Quality Control* (WH/Quality Control). To rename these locations, go to :menuselection:`Inventory app --> Configuration --> Locations`, then click on the desired location to change (or update) the name." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:43 msgid "Receive in three steps (input + quality + stock)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:46 msgid "Create a purchase order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:48 msgid "To create a new :abbr:`RfQ (Request for Quotation)`, navigate to :menuselection:`Purchase app --> New`, which reveals a blank :abbr:`RfQ (Request for Quotation)` form page. On this page, select a :guilabel:`Vendor`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm Order`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:54 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:52 msgid "A :guilabel:`Receipt` smart button will appear in the top right, and the receipt will be associated with the purchase order. Clicking on the :guilabel:`Receipt` smart button will show the receipt order." msgstr "" @@ -7154,23 +5761,23 @@ msgstr "" msgid "After confirming a purchase order, a Receipt smart button will appear." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:63 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:61 msgid "Process a receipt" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:63 msgid "Once the purchase order (PO) is confirmed, a receipt (`WH/IN`) operation is generated and ready to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:66 msgid "The receipt can be confirmed from the original purchase order form, or it can be accessed by navigating to the :menuselection:`Inventory app`, and locating the :guilabel:`Receipts` task card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:69 msgid "Click the :guilabel:`# To Process` button to reveal all incoming receipts to process. Click the receipt associated with the previous purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:74 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:72 msgid "Click :guilabel:`Validate` to validate the receipt, and move the product to the destination location, :guilabel:`WH/Input`." msgstr "" @@ -7178,23 +5785,23 @@ msgstr "" msgid "Receipt operation for product being moved to WH/Input location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:80 msgid "Process a transfer to Quality Control" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:82 msgid "Once the receipt has been validated, an internal transfer operation to move the product to quality control is ready to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:87 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:85 msgid "Click :guilabel:`Inventory Overview` in the breadcrumbs to navigate back to the dashboard, and locate the :guilabel:`Internal Transfers` task card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:88 msgid "Select the :guilabel:`# To Process` button to reveal all internal transfers to process. Then, choose the internal transfer associated with the validated receipt." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:91 msgid "Once ready, click :guilabel:`Validate` to complete the transfer, and move the product from :guilabel:`WH/Input` to :guilabel:`WH/Quality Control`." msgstr "" @@ -7202,19 +5809,19 @@ msgstr "" msgid "Internal transfer for product being moved to quality control zone." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:99 msgid "Process a transfer to stock" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:101 msgid "Once the internal transfer to move the product to quality control has been validated, another internal transfer operation to move the product into warehouse stock is ready to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:104 msgid "Click :guilabel:`YourCompany: Internal Transfers` in the breadcrumbs to reveal the list of all internal transfers to process. Then, select the new internal transfer to move the product from `WH/Quality Control` to `WH/Stock`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:110 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:108 msgid "Once ready, click :guilabel:`Validate` to complete the transfer, and move the product from :guilabel:`WH/Quality Control` to :guilabel:`WH/Stock`." msgstr "" @@ -7222,156 +5829,2249 @@ msgstr "" msgid "Internal transfer for product being moved to warehouse stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:3 -msgid "Incoming shipments and delivery orders" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:3 +msgid "Sell stock from multiple warehouses using virtual locations" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:5 -msgid "In Odoo, there are many different ways to process receipts and deliveries for products moving in and out of a warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:5 +msgid "While keeping stock and selling inventory from one warehouse might work for smaller companies, bigger companies might need to keep stock in, or sell from, multiple warehouses in multiple locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:8 -msgid "A company's preferred method of receiving, or shipping, products depends on several factors, such as the type of products stocked and sold, the size of the warehouse, the amount of receipts and delivery orders processed daily, and so on." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:9 +msgid "Sometimes products included in a single sales order might take stock from two (or more) warehouses; in Odoo, pulling products from multiple warehouses to satisfy sales demands can be done using *virtual locations*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:12 -msgid "Enabling the *Multi-Step Routes* feature in Odoo's *Inventory* app settings allows users to change the manner in which receipts and deliveries are processed in the database." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:14 +msgid "The solution in this document, describing the use of a virtual warehouse to fulfill orders for multiple warehouses, has some limitations. Consider the following before proceeding:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:16 -msgid "`Using Routes (eLearning Tutorial) `_" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:17 +msgid "When the :guilabel:`Warehouse` field is set to a virtual warehouse on a sales order, the virtual warehouse's address is indicated on the picking, packing, and delivery forms, **not** the actual warehouse's address." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:17 -msgid "`Push & Pull Rules (eLearning Tutorial) `_" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:20 +msgid "Each location has a `warehouse_id` (hidden field). This means that the stock in the virtual warehouse will **not** be the sum of the stock of the real warehouses, but rather the sum of the stock in the locations whose warehouse ID is the virtual warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:20 -msgid "The default incoming and outgoing routes in Odoo are set to receive and deliver goods in one step. However, once the *Multi-Step Routes* feature is enabled, the incoming and outgoing routes can be changed to either two steps or three steps." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:25 +msgid "Potential limitation for those using :doc:`two <../../shipping_receiving/daily_operations/receipts_delivery_two_steps>` or :doc:`three-step delivery <../../shipping_receiving/daily_operations/delivery_three_steps>`:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:25 -msgid "To activate the *Multi-Step Routes* feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Warehouse` section, tick the checkbox next to :guilabel:`Multi-Step Routes`, and click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:29 +msgid "The output or packing zone on the various forms is incorrectly listed as the virtual warehouse's address." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:29 -msgid "Doing so *also* enables the :guilabel:`Storage Locations` feature, if not already enabled." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:31 +msgid "There is no workaround for two or three-step deliveries." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:31 -msgid "Adding additional steps to receipts and deliveries moving in and out of the warehouse adds additional operations that must be completed *before* a product is finally received or shipped." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:32 +msgid "Proceed **only** if setting a virtual warehouse's address as the output or packing zone makes sense for the company's workflow." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:34 -msgid "These configurations vary, depending on the needs of the business. They also depend on any requirements for the products stored, including the performance of quality control checks on received products, or the use of special packaging on shipped products." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:36 +msgid "In order to create virtual locations in warehouses, and proceed to the following steps, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` features **must** be enabled." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:39 -msgid "One-step flow" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:39 +msgid "To do so, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Warehouse` section, and enable the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` options. Then, :guilabel:`Save` the changes to finish." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:41 -msgid "The receiving and shipping rules for a one-step configuration are as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:47 +msgid "Create virtual parent location" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:43 -msgid "**Receipt**: receive products directly from vendors into stock. *No* intermediate steps between receipt and input to stock occur." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:49 +msgid "Before creating any virtual stock locations, create a new warehouse that acts as a *virtual* warehouse — the *parent* location of other physical warehouses." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:45 -msgid "**Shipping**: ship products directly from warehouse stock to customer. *No* intermediate steps occur before shipping." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:54 +msgid "Virtual warehouses are great for companies with multiple physical warehouses. This is because a situation might arise when one warehouse runs out of stock of a particular product, but another warehouse still has stock on-hand. In this case, stock from these two (or more) warehouses could be used to fulfill a single sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:47 -msgid "Can *only* be used if **not** using First In, First Out (FIFO), Last In, First Out (LIFO), or First Expired, First Out (FEFO) removal strategies." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:59 +msgid "The \"virtual\" warehouse acts as a single aggregator of all the inventory stored in a company's physical warehouses, and is used (for traceability purposes) to create a hierarchy of locations in Odoo." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:49 -msgid "Items are received or shipped directly into/from stock." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:63 +msgid "To create a new warehouse, go to :menuselection:`Inventory app --> Configuration --> Warehouses`, and click :guilabel:`Create`. From here, the warehouse :guilabel:`Name` and :guilabel:`Short Name` can be changed, and other warehouse details can be changed under the :guilabel:`Warehouse Configuration` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:50 -msgid "Suited for warehouses that require receipts and/or deliveries to be handled quickly." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:68 +msgid "Lastly, click :guilabel:`Save` to finish creating a *regular* warehouse. Continue following the steps below to finish configuring the virtual parent warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:51 -msgid "Recommended for small warehouses with low stock levels, and for non-perishable items." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:-1 +msgid "New warehouse form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:54 -msgid ":doc:`receipts_delivery_one_step`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:76 +msgid ":doc:`Warehouse configurations <../../warehouses_storage/inventory_management/warehouses>`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:57 -msgid "Two-step flow" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:77 +msgid ":ref:`Incoming and outgoing shipments `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:59 -msgid "The receiving and shipping rules for a two-step configuration are as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:78 +msgid ":doc:`../../warehouses_storage/replenishment/resupply_warehouses`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:61 -msgid "**Input + stock**: bring products to an input location *before* moving into stock. Products can be organized by different internal storage locations, such as various shelves, freezers, and locked areas, before being stocked in the warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:83 +msgid "Create child warehouses" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:64 -msgid "**Pick + ship**: bring products to an output location before shipping. Packages can be organized by different carriers, or moved to shipping docks before being shipped." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:85 +msgid "Create at least two *child* warehouses to link to the virtual warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:66 -msgid "Minimum requirement to use lot numbers, or serial numbers, to track products with a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:88 +msgid "In order to take stock from multiple warehouses to fulfill a sales order, there needs to be at least **two** warehouses acting as child locations of the virtual parent location warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:69 -msgid "Products received will not be available for manufacturing, shipping, etc., until they are transferred into warehouse stock." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:91 +msgid "To do that, navigate to :menuselection:`Inventory app --> Configuration --> Warehouses`, click :guilabel:`Create`, and follow the :ref:`preceding instructions ` to configure the physical stock locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:71 -msgid "Recommended for larger warehouses with high stock levels, or when stocking large items (e.g., mattresses, large furniture, heavy machinery, etc.)." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:0 +msgid "**Parent Warehouse**" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:75 -msgid ":doc:`receipts_delivery_two_steps`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:0 +msgid ":guilabel:`Warehouse`: `Virtual Warehouse`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:78 -msgid "Three-step flow" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:0 +msgid ":guilabel:`Location`: `VWH/Stock`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:80 -msgid "The receiving and shipping rules for a three-step configuration are as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:0 +msgid "**Child Warehouses**" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:82 -msgid "**Input + quality + stock**: receive products at the input location, transfer them to a quality control area, and move the ones that pass inspection into stock." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:0 +msgid ":guilabel:`Warehouses`: `Warehouse A` and `Warehouse B`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:84 -msgid "**Pick + pack + ship**: pick products according to their removal strategy, pack them in a dedicated packing area, and bring them to an output location for shipping." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:0 +msgid ":guilabel:`Locations`: `WHA` and `WHB`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:86 -msgid "Can be used when tracking products by lot or serial numbers when using :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:0 +msgid "Graphic of child locations 'WHA' and 'WHB' tied to the parent location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:89 -msgid "Products received will not be available for manufacturing, shipping, etc., until they are transferred into stock." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:110 +msgid "While the virtual stock location will be changed to 'View' later, the :guilabel:`Location Type` **must** be :guilabel:`Internal Location` at this point to :ref:`link the child warehouses ` in the next section." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:91 -msgid "Required for any warehouse needing to perform quality control inspections before receiving items into stock." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:117 +msgid "Link child warehouses to virtual stock" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:93 -msgid "Recommended for very large warehouses with very high stock levels." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:119 +msgid "To set physical warehouses as child locations of the virtual location configured in the :ref:`previous step `, navigate to :menuselection:`Inventory app --> Configuration --> Locations`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:96 -msgid ":doc:`receipts_three_steps`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:123 +msgid "Remove any filters from the search bar. Then, click the physical warehouse :guilabel:`Location` that was previously created to be a child location (e.g. `WHA`), and click :guilabel:`Edit`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:97 -msgid ":doc:`delivery_three_steps`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:126 +msgid "Change the :guilabel:`Parent Location` field from :guilabel:`Physical Locations` to the virtual warehouse's **stock location** (e.g. `VWH/Stock`) from the drop-down menu, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:131 +msgid "To select the virtual warehouse's stock location in the :guilabel:`Parent Location` drop-down menu, the parent warehouse stock location (e.g. `VWH/Stock`) **must** have its :guilabel:`Location Type` set to :guilabel:`Internal Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:-1 +msgid "Set the child warehouse's *Parent Location* to the virtual warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:139 +msgid "Repeat the preceding steps to configure two or more child warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:141 +msgid "Once complete, the virtual, parent warehouse (e.g. `VWH/Stock`) fulfills orders using stock from child warehouses (e.g. `WHA` and `WHB`), if there is insufficient stock in any one location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:145 +msgid "Set virtual stock location as 'view'" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:147 +msgid "Set the virtual stock location's :guilabel:`Location Type` to :guilabel:`View`, as it is a non-existent location used to group various physical warehouses together." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:150 +msgid "To do that, navigate to :menuselection:`Inventory app --> Configuration --> Locations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:152 +msgid "Click the virtual warehouse's stock location (e.g. `VWH/Stock`) that was :ref:`previously created `, from the :guilabel:`Locations` list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:155 +msgid "On the location form, under the :guilabel:`Additional Information` heading, set the :guilabel:`Location Type` to :guilabel:`View`. :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:-1 +msgid "Warehouse location types in location creation screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:163 +msgid "To view the total quantity across **all** linked child warehouses, go to the product form and click the :guilabel:`On Hand` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:0 +msgid "Display stock across all linked warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:171 +msgid "Example: sell products from a virtual warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:173 +msgid "To sell products from multiple warehouses using a virtual parent location, the database must have at least **two** warehouses configured — with at least **one** product, with quantity on-hand in each warehouse, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:178 +msgid "The following product, `Toy soldier`, is available at each location with the quantities:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:180 +msgid "`WHA/Stock` : 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:181 +msgid "`WHB/Stock` : 2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:182 +msgid "Warehouses `WHA` and `WHB` are child warehouses of the virtual warehouse `VWH`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:184 +msgid "Create a quotation for the product by navigating to the :menuselection:`Sales` app and clicking :guilabel:`Create`. On the quote, add a :guilabel:`Customer`, and click :guilabel:`Add a product` to add the two products stored in the two warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:188 +msgid "Then, click the :guilabel:`Other Info` tab on the sales order form. Under the :guilabel:`Delivery` section, change the :guilabel:`Warehouse` field value to the virtual warehouse that was :ref:`previously created `. Next, :guilabel:`Confirm` the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:-1 +msgid "Set virtual warehouse as the *Warehouse* field in sales order's *Other Info* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:196 +msgid "Then, click the :guilabel:`Delivery` smart button. From the warehouse delivery form, confirm that the :guilabel:`Source Location` value matches the :guilabel:`Warehouse` field value from the sales order. Both should list the virtual warehouse location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:200 +msgid "Finally, on the warehouse delivery form, under the :guilabel:`Detailed Operations` tab, confirm that the :guilabel:`Locations` in the :guilabel:`From` column for each product match the child locations that are tied to the virtual parent location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:-1 +msgid "Delivery order with matching source and child locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:209 +msgid "The :guilabel:`Source Location` on the warehouse delivery form, and the :guilabel:`Warehouse` under the :guilabel:`Other Info` tab on the sales order, **must** match for products in the sales order to be pulled from different warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:213 +msgid "If the virtual warehouse is not in the :guilabel:`Source Location` field on the warehouse delivery form, retry product reservation by:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:216 +msgid "Running the scheduler: turn on :ref:`developer mode `, and then go to :menuselection:`Inventory app --> Operations --> Run Scheduler`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:218 +msgid "Clicking :guilabel:`Check Availability` on the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:219 +msgid "If the virtual warehouse is **not** assigned to the :guilabel:`Warehouse` field on the sales order, then cancel it, and create a new sales order with the virtual warehouse set in the :guilabel:`Warehouse` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:222 +msgid "If the :guilabel:`Warehouse` field is missing on the sales order form, then the multiple child warehouses may not have been set up correctly. Review the :ref:`previous section ` to ensure the correct settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:227 +msgid "To use a virtual *parent* location as the default warehouse for sales orders, each salesperson should have the virtual warehouse assigned to them from the drop-down menu next to :guilabel:`Default Warehouse` on their employee form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/stock_warehouses.rst:0 +msgid "Default warehouse location on employee form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:3 +msgid "Storage categories" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:5 +msgid "A *storage category* is used with :doc:`putaway rules `, as an extra location attribute to automatically propose optimal storage locations for products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:8 +msgid "Follow these steps to complete the setup:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:10 +msgid ":ref:`Enable the Storage Category feature `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:11 +msgid ":ref:`Define a storage category ` with specific limitations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:12 +msgid "Assign a :ref:`category to storage locations `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:13 +msgid "Add the storage category as an attribute to a :ref:`putaway rule `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:17 +msgid ":doc:`putaway`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:20 +msgid "Assigning categories to storage locations tells Odoo these locations meet specific requirements, such as temperature or accessibility. Odoo then evaluates these locations, based on defined capacity, and recommends the best one on the warehouse transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:28 +msgid "To enable storage categories, go to :menuselection:`Inventory app --> Configuration --> Settings`. Then, in the :guilabel:`Warehouse` section, ensure the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` features are enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:32 +msgid "Next, activate the :guilabel:`Storage Categories` feature. Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:-1 +msgid "Show the Storage Categories feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:41 +msgid "Define storage category" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:43 +msgid "A storage category with specific limitations **must** be created first, before it is applied to locations, in order to decide the optimal storage location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:46 +msgid "To create a storage category, go to :menuselection:`Inventory app --> Configuration --> Storage Categories`, and click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:49 +msgid "On the storage category form, type a name for the category in the :guilabel:`Storage Category` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:52 +msgid "Options are available to limit capacity by weight, product, and package type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:55 +msgid "Weight limits can be combined with capacity by package or product (e.g. a maximum of one hundred products with a total weight of two hundred kilograms)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:58 +msgid "While it is possible to limit capacity by product and package type at the same location, it may be more practical to store items in different amounts across various locations, as shown in this example of :ref:`capacity by package `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:62 +msgid "The :guilabel:`Allow New Product` field defines when the location is considered available to store a product:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:65 +msgid ":guilabel:`If location is empty`: a product can be added there only if the location is empty." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:66 +msgid ":guilabel:`If products are the same`: a product can be added there only if the same product is already there." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:68 +msgid ":guilabel:`Allow mixed products`: several different products can be stored in this location at the same time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:72 +msgid "When clicked, the :guilabel:`Location` smart button shows which storage locations the category has been assigned to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:76 +msgid "Capacity by weight" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:78 +msgid "On a storage category form (:menuselection:`Inventory app --> Configuration --> Storage Categories`), set a maximum product weight in the :guilabel:`Max Weight` field. This limit applies to each location assigned this storage category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:83 +msgid "Capacity by product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:85 +msgid "In the :guilabel:`Capacity by Product` tab, click :guilabel:`Add a Line` to input items, and enter their capacities in the :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:89 +msgid "Ensure only a maximum of five `Large Cabinets` and two `Corner Desk Right Sit` are stored at a single storage location, by specifying those amounts in the :guilabel:`Capacity by Product` tab of a storage category form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:0 +msgid "Show storage category limiting by product count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:100 +msgid "Capacity by package" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:102 +msgid "For companies using :doc:`packages <../../product_management/configure/package>`, it becomes possible to ensure real-time storage capacity checks, based on package types (e.g., crates, bins, boxes, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:107 +msgid "Enable the :guilabel:`Packages` feature in :menuselection:`Inventory app --> Configuration --> Settings` to show the :guilabel:`Capacity by Package` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:111 +msgid "Create putaway rules for pallet-stored items, by creating the `High Frequency pallets` storage category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:114 +msgid "In the :guilabel:`Capacity by Package` tab, specify the number of packages for the designated :guilabel:`Package Type`, and set a maximum of `2.00` `Pallets` for a specific location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:0 +msgid "Create a storage category on the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:124 +msgid "Assign to location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:126 +msgid "Once the storage category is created, assign it to a location. Navigate to the location by going to :menuselection:`Inventory app --> Configuration --> Locations`, and select the desired location. Then, select the created category in the :guilabel:`Storage Category` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:131 +msgid "Assign the `High Frequency pallets` storage category (which limits pallets stored at any location to two pallets) to the `WH/Stock/pallets/PAL 1` sub-location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:0 +msgid "When a Storage Category is created, it can be linked to a warehouse location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:141 +msgid "Putaway rule" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:143 +msgid "With the :ref:`storage category ` and :ref:`location ` set up, create the :doc:`putaway rule ` by navigating to :menuselection:`Inventory app --> Configuration --> Putaway Rules`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:147 +msgid "Click the :guilabel:`Create` button to create the putaway rule. In the :guilabel:`Having Category` field of the new putaway rule form, select the storage category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:151 +msgid "Continuing the example from above, the `High Frequency Pallets` storage category is assigned to the putaway rule directing pallets of lemonade to locations with the `High Frequency Pallets` storage category :ref:`assigned to them `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:0 +msgid "Storage Categories used in a variety of putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:160 +msgid "Use case: limit capacity by package" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:162 +msgid "To limit the capacity of a storage location by a specific number of packages, :ref:`create a storage category with a Capacity By Package `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:165 +msgid "Continuing the example from above, the `High Frequency Pallets` storage category is assigned to the `PAL1` and `PAL2` locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:168 +msgid "Then, :ref:`putaway rules ` are set, so that any pallets received in the warehouse are directed to be stored in `PAL1` and `PAL2` locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:171 +msgid "Depending on the number of pallets on-hand at each of the storage locations, when one pallet of lemonade cans is received, the following scenarios happen:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:174 +msgid "If `PAL1` and `PAL2` are empty, the pallet is redirected to `WH/Stock/Pallets/PAL1`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:175 +msgid "If `PAL1` is full, the pallet is redirected to `WH/Stock/Pallets/PAL2`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:176 +msgid "If `PAL1` and `PAL2` are full, the pallet is redirected to `WH/Stock/Pallets`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:5 +msgid "Routes and push/pull rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:7 +msgid "In inventory management, the supply chain strategy determines when products should be purchased/manufactured, delivered to distribution centers, and made available to the retail channel." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:11 +msgid "In Odoo, a product's supply chain strategy can be configured using *Routes*, which feature *Pull and Push Rules*. Once everything is properly configured, the Inventory app can automatically generate transfers following the configured push/pull rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:16 +msgid "Inside the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:18 +msgid "In a generic warehouse, there are receiving docks, a quality control area, storage locations, picking and packing areas, and shipping docks. All products go through all these locations. As the products move through the locations, each location triggers the products' specified route and rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of a generic warehouse with stock and quality control area." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:27 +msgid "In this example, vendor trucks unload pallets of ordered products at the receiving docks. Operators then scan the products in the receiving area. Depending on the product's route and rules, some of these products are sent to a quality control area (for example, products that are components used in the manufacturing process), while others are directly stored in their respective locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of a generic push to rule when receiving products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:36 +msgid "Here is an example of a fulfillment route. In the morning, items are picked for all the orders that need to be prepared during the day. These items are picked from storage locations and moved to the picking area, close to where the orders are packed. Then, the orders are packed in their respective boxes, and conveyor belts bring them to the shipping docks, ready to be delivered to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of a generic pull from rule when preparing deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:46 +msgid "Pull rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:48 +msgid "With *Pull Rules*, a demand for some products triggers procurements, while *Push Rules* are triggered by products arriving in a specific location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:51 +msgid "Pull Rules are used to fulfill a sales order. Odoo generates a need at the *Customer Location* for each product in the order. Because pull rules are triggered by a need, Odoo looks for a pull rule defined on the *Customer Location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:55 +msgid "In this case, a \"delivery order\" pull rule that transfers products from the *Shipping Area* to the *Customer Location* is found, and a transfer between the two locations is created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:58 +msgid "Then, Odoo finds another pull rule that tries to fulfill the need for the *Shipping Area*: the \"packing\" rule that transfers products from the *Packing Area* to the *Shipping Area*. Finally, other pull rules are triggered until a transfer between the *Stock* and the *Picking Area* is created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:64 +msgid "All these product transfers are automatically generated by Odoo based on the pull rules, starting from the end (the customer location) and going backward (the stock warehouse). While working, the operator processes these transfers in the opposite order: first the picking, then the packing, and finally the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:70 +msgid "Push rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:72 +msgid "On the other hand, *Push Rules* are much easier to understand. Instead of generating documents based on needs, they are triggered in real time when products arrive in a specific location. Push rules basically say: \"when a product arrives at a specific location, move it to another location.\"" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:76 +msgid "An example of a push rule would be: when a product arrives in the *Receipt Area*, move it to the *Storage Location*. As different push rules can be applied to different products, the user can assign different storage locations for different products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:80 +msgid "Another push rule could be: when products arrive at a location, move them to the *Quality Control Area*. Then, once the quality check is done, move them to their *Storage Location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:84 +msgid "Push rules can only be triggered if there are no pull rules that have already generated the product transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:88 +msgid "Sets of push/pull rules like those are called *Routes*. The grouping on the rule decides if products are grouped in the same transfer or not. For example, during the picking operation, all orders and their products are grouped in one transfer, whereas the packing operation respects the grouping per customer order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:96 +msgid "Use routes and rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:98 +msgid "Since *Routes* are a collection of *Push and Pull Rules*, Odoo helps you manage advanced route configurations such as:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:101 +msgid "Manage product manufacturing chains." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:102 +msgid "Manage default locations per product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:103 +msgid "Define routes within the stock warehouse according to business needs, such as quality control, after-sales services, or supplier returns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:105 +msgid "Help rental management by generating automated return moves for rented products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:107 +msgid "To configure a route for a product, first, open the :guilabel:`Inventory` application and go to :menuselection:`Configuration --> Settings`. Then, in the :guilabel:`Warehouse` section, enable the :guilabel:`Multi-Step Routes` feature and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "Activate the Multi-Step Routes feature in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:116 +msgid "The :guilabel:`Storage Locations` feature is automatically activated with the :guilabel:`Multi-Step Routes` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:119 +msgid "Once this first step is completed, the user can use pre-configured routes that come with Odoo, or they can create custom routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:123 +msgid "Pre-configured routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:125 +msgid "To access Odoo's pre-configured routes, go to :menuselection:`Inventory --> Configuration --> Warehouses`. Then, open a warehouse form. In the :guilabel:`Warehouse Configuration` tab, the user can view the warehouse's pre-configured routes for :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "A pre-configured warehouse in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:134 +msgid "Some more advanced routes, such as pick-pack-ship, are also available. The user can select the route that best fits their business needs. Once the :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` routes are set, head to :menuselection:`Inventory --> Configuration --> Routes` to see the specific routes that Odoo generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of all the preconfigured routes Odoo offers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:143 +msgid "On the :guilabel:`Routes` page, click on a route to open the route form. In the route form, the user can view which places the route is :guilabel:`Applicable On`. The user can also set the route to only apply on a specific :guilabel:`Company`. This is useful for multi-company environments; for example, a user can have a company and warehouse in Country A and a second company and warehouse in Country B." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:150 +msgid ":ref:`Applicable on packagings `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of a route example applicable on product categories and warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:156 +msgid "At the bottom of the route form, the user can view the specific :guilabel:`Rules` for the route. Each :guilabel:`Rule` has an :guilabel:`Action`, a :guilabel:`Source Location`, and a :guilabel:`Destination Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "An example of rules with push & pull actions in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:165 +msgid "Custom Routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:167 +msgid "To create a custom route, go to :menuselection:`Inventory --> Configuration --> Routes`, and click on :guilabel:`Create`. Next, choose the places where this route can be selected. A route can be applicable on a combination of places." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of a pick-pack-ship route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:175 +msgid "Each place has a different behavior, so it is important to tick only the useful ones and adapt each route accordingly. Then, configure the :guilabel:`Rules` of the route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:178 +msgid "If the route is applicable on a product category, the route still needs to be manually set on the product category form by going to :menuselection:`Inventory --> Configuration --> Product Categories`. Then, select the product category and open the form. Next, click :guilabel:`Edit` and under the :guilabel:`Logistics` section, set the :guilabel:`Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:183 +msgid "When applying the route on a product category, all the rules configured in the route are applied to **every** product in the category. This can be helpful if the business uses the dropshipping process for all the products from the same category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of a route applied to the \"all\" product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:191 +msgid "The same behavior applies to the warehouses. If the route can apply to :guilabel:`Warehouses`, all the transfers occurring inside the chosen warehouse that meet the conditions of the route's rules will then follow that route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of the warehouse drop-down menu when selecting applicable on warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:199 +msgid "If the route is applicable on :guilabel:`Sales Order Lines`, it is more or less the opposite. The route must be manually chosen when creating a quotation. This is useful if some products go through different routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:203 +msgid "Remember to toggle the visibility of the :guilabel:`Route` column on the quotation/sales order. Then, the route can be chosen on each line of the quotation/sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of the menu allowing to add new lines to sales orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:210 +msgid "Finally, there are routes that can be applied to products. Those work more or less like the product categories: once selected, the route must be manually set on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:213 +msgid "To set a route on a product, go to :menuselection:`Inventory --> Products --> Products` and select the desired product. Then, go to the :guilabel:`Inventory` tab and under the :guilabel:`Operations` section, select the :guilabel:`Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of a product form, where the route must be selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:222 +msgid "Rules must be set on the route in order for the route to work." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:225 +msgid "Rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:227 +msgid "The rules are defined on the route form. First, go to :menuselection:`Inventory --> Configuration --> Routes` and open the desired route form. Next, click :guilabel:`Edit` and in the :guilabel:`Rules` section, click on :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of the rules menu, where it is possible to add new rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:235 +msgid "The available rules trigger various actions. If Odoo offers *Push* and *Pull* rules, others are also available. Each rule has an :guilabel:`Action`:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:238 +msgid ":guilabel:`Pull From`: this rule is triggered by a need for the product in a specific location. The need can come from a sales order being validated or from a manufacturing order requiring a specific component. When the need appears in the destination location, Odoo generates a picking to fulfill this need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:242 +msgid ":guilabel:`Push To`: this rule is triggered by the arrival of some products in the defined source location. In the case of the user moving products to the source location, Odoo generates a picking to move those products to the destination location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:245 +msgid ":guilabel:`Pull & Push`: this rule allows the generation of pickings in the two situations explained above. This means that when products are required at a specific location, a transfer is created from the previous location to fulfill that need. This creates a need in the previous location and a rule is triggered to fulfill it. Once the second need is fulfilled, the products are pushed to the destination location and all the needs are fulfilled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:250 +msgid ":guilabel:`Buy`: when products are needed at the destination location, a request for quotation is created to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:252 +msgid ":guilabel:`Manufacture`: when products are needed in the source location, a manufacturing order is created to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "Overview of a \"Pull From\" rule that creates a transfer between the stock and the packing\n" +"zone." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:260 +msgid "The :guilabel:`Operation Type` must also be defined on the rule. This defines which kind of picking is created from the rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:263 +msgid "If the rule's :guilabel:`Action` is set to :guilabel:`Pull From` or :guilabel:`Pull & Push`, a :guilabel:`Supply Method` must be set. The :guilabel:`Supply Method` defines what happens at the source location:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:267 +msgid ":guilabel:`Take From Stock`: the products are taken from the available stock of the source location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:269 +msgid ":guilabel:`Trigger Another Rule`: the system tries to find a stock rule to bring the products to the source location. The available stock is ignored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:271 +msgid ":guilabel:`Take From Stock, if Unavailable, Trigger Another Rule`: the products are taken from the available stock of the source location. If there is no stock available, the system tries to find a rule to bring the products to the source location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:276 +msgid "Example flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:278 +msgid "In this example, let's use a custom *Pick - Pack - Ship* route to try a full flow with an advanced custom route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:281 +msgid "First, a quick look at the route's rules and their supply methods. There are three rules, all :guilabel:`Pull From` rules. The :guilabel:`Supply Methods` for each rule are the following:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:284 +msgid ":guilabel:`Take From Stock`: When products are needed in the :guilabel:`WH/Packing Zone`, *picks* (internal transfers from :guilabel:`WH/Stock` to :guilabel:`WH/Packing Zone`) are created from :guilabel:`WH/Stock` to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:287 +msgid ":guilabel:`Trigger Another Rule`: When products are needed in :guilabel:`WH/Output`, *packs* (internal transfers from :guilabel:`WH/Packing Zone` to :guilabel:`WH/Output`) are created from :guilabel:`WH/Packing Zone` to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:290 +msgid ":guilabel:`Trigger Another Rule`: When products are needed in :guilabel:`Partner Locations/Customers`, *delivery orders* are created from :guilabel:`WH/Output` to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "Overview of all the transfers created by the pick - pack - ship route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:298 +msgid "This means that, when a customer orders products that have a *pick - pack - ship* route set on it, a delivery order is created to fulfill the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of the operations created by a pull from transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:306 +msgid "If the source document for multiple tranfers is the same sales order, the status is not the same. The status will be :guilabel:`Waiting Another Operation` if the previous transfer in the list is not done yet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of the transfers' various statuses at the beginning of the process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:314 +msgid "To prepare the delivery order, packed products are needed at the output area, so an internal transfer is requested from the packing zone." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of the detailed operations for a transfer between the packing and output zones." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:321 +msgid "Obviously, the packing zone needs products ready to be packed. So, an internal transfer is requested to the stock and employees can gather the required products from the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of the detailed operations for a transfer between the stock and packing zones." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:328 +msgid "As explained in the introduction of the documentation, the last step in the process (for this route, the delivery order) is the first to be triggered, which then triggers other rules until we reach the first step in the process (here, the internal transfer from the stock to the packing area). Now, everything is ready to be processed so the customer can get the ordered items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:333 +msgid "In this example, the product is delivered to the customer when all the rules have been triggered and the transfers are done." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/use_routes.rst:-1 +msgid "View of the transfers' statuses when the route is completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods.rst:5 +msgid "Picking methods" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:3 +msgid "Batch picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:7 +msgid "*Batch picking* enables a single picker to handle multiple orders at once, reducing the time needed to navigate to the same location in a warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:10 +msgid "When picking in batches, orders are grouped and consolidated into a picking list. After the picking, the batch is taken to an output location, where the products are sorted into their respective delivery packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:15 +msgid ":ref:`Use Barcode app for pickings `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:17 +msgid "Since orders *must* be sorted at the output location after being picked, this picking method suits businesses with a few products that are ordered often. Storing high-demand items in easily accessible locations can increase the number of orders that are fulfilled efficiently." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:24 +msgid "To activate the batch picking option, begin by going to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Operations` section, check the :guilabel:`Batch Transfers` box." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:-1 +msgid "Enable the *Batch Transfers* in Inventory > Configuration > Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:32 +msgid "Since batch picking is a method to optimize the *pick* operation in Odoo, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` options under the :guilabel:`Warehouse` heading must also be checked on this settings page. When finished, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:-1 +msgid "Enable *Storage Locations* and *Multi-Step Routes* Inventory > Configuration > Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:40 +msgid "Lastly, enable the warehouse picking feature, by navigating to the warehouse settings page, which is accessible from :menuselection:`Inventory app --> Configuration --> Warehouses`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:43 +msgid "From here, select the desired warehouse from the list. Then, from the radio options available for :guilabel:`Outgoing Shipments`, select either the :guilabel:`Send goods in output and then deliver (2 steps)` or :guilabel:`Pack goods, send goods in output and then deliver (3 steps)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:128 +msgid ":doc:`Delivery in two steps <../daily_operations/receipts_delivery_two_steps>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:49 +msgid ":doc:`../daily_operations/delivery_three_steps`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:-1 +msgid "Set up 2-step or 3-step outgoing shipments." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:56 +msgid "Create batch transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:58 +msgid "Manually create batch transfers directly from the :menuselection:`Inventory app --> Operations --> Batch Transfers` page. Click the :guilabel:`New` button to begin creating a batch transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:61 +msgid "On the batch transfer form, fill the following fields out accordingly:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:63 +msgid ":guilabel:`Responsible`: employee assigned to the picking. Leave this field blank if *any* worker can fulfill this picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:65 +msgid ":guilabel:`Operation Type`: from the drop-down menu, select the operation type under which the picking is categorized." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:67 +msgid ":guilabel:`Scheduled Date`: specifies the date by which the :guilabel:`Responsible` person should complete the transfer to the output location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:70 +msgid "Next, in the :guilabel:`Transfers` list, click :guilabel:`Add a line` to open the :guilabel:`Add: Transfers` window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:73 +msgid "If the :guilabel:`Operation Type` field was filled, the list will filter transfer records matching the selected :guilabel:`Operation Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:76 +msgid "Click the :guilabel:`New` button to create a new transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:78 +msgid "Once the transfer records are selected, click :guilabel:`Confirm` to confirm the batch picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:81 +msgid "A new batch transfer assigned to the :guilabel:`Responsible`, `Joel Willis`, for the `Pick` :guilabel:`Operation Type`. The :guilabel:`Scheduled Date` is set to `August 11`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:0 +msgid "View of *Batch Transfers* form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:88 +msgid "Clicking the :guilabel:`Add a line` button opens the :guilabel:`Add:Transfers` window, displaying only pickings. This is because the :guilabel:`Operation Type` was set to `Pick` on the batch transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:92 +msgid "Click the checkbox to the left of the transfers, `WH/PICK/00001` and `WH/PICK/00002`, to include them in the new transfer. Then, click the :guilabel:`Select` button to close the :guilabel:`Add:Transfers` window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:0 +msgid "Select multiple transfers from the *Add:Transfers* window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:103 +msgid "Add batch from transfers list" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:105 +msgid "Another method of creating batch transfers is available using the :guilabel:`Add to batch` option in a list. Navigate to the :menuselection:`Inventory app --> Operations` drop-down menu, and select any of the :guilabel:`Transfers` to open a filtered list of transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:-1 +msgid "Show all transfer types in a drop-down menu: Receipts, Deliveries, Internal Transfers,\n" +"Manufacturings, Batch Transfers, Dropships." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:114 +msgid "On the transfers list, select the checkbox to the left of the selected transfers to add in a batch. Next, navigate to the :guilabel:`Actions ⚙️ (gear)` button, and click :guilabel:`Add to batch` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:0 +msgid "Use *Add to batch* button, from the *Action* button's list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:122 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:148 +msgid "Doing so opens an :guilabel:`Add to batch` pop-up window, wherein the employee :guilabel:`Responsible` for the picking can be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:125 +msgid "Choose from the two radio options to add to :guilabel:`an existing batch transfer` or create :guilabel:`a new batch transfer`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:128 +msgid "To begin with a draft, select the :guilabel:`Draft` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:130 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:157 +msgid "Conclude the process by clicking :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:-1 +msgid "Show *Add to batch* window to create a batch transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:137 +msgid "Process batch transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:139 +msgid "Handle batch transfers in the :menuselection:`Inventory app --> Operations --> Batch Transfers` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:142 +msgid "From here, select the intended transfer from the list. Then, on the batch transfer form, input the :guilabel:`Done` quantities for each product, under the :guilabel:`Detailed Operations` tab. Finally, select :guilabel:`Validate` to complete the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:147 +msgid "Be certain the batch transfer is complete when the :guilabel:`Validate` button is highlighted in purple. If the :guilabel:`Check Availability` button is highlighted instead, that means there are items in the batch that are currently *not* available in-stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:154 +msgid "In a batch transfer involving products from pickings, `WH/PICK/00001` and `WH/PICK/00002`, the :guilabel:`Detailed Operations` tab shows that the product, `Cabinet with Doors`, has been picked because the :guilabel:`Done` column matches the value in the :guilabel:`Reserved` column. However, `0.00` quantities have been picked for the other product, `Cable Management Box`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:0 +msgid "Show batch transfer of products from two pickings in the *Detailed Operations* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:163 +msgid "Only in-stock products are visible in the :guilabel:`Detailed Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:165 +msgid "To view the complete product list, switch to the :guilabel:`Operations` tab. On this list, the :guilabel:`Demand` column indicates the required quantity for the order. The :guilabel:`Reserved` column shows the available stock to fulfill the order. Lastly, the :guilabel:`Done` column specifies the products that have been picked, and are ready for the next step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:171 +msgid "The product, `Desk Pad`, from the same batch as the :ref:`example above `, is only visible in the :guilabel:`Operations` tab because there are no :guilabel:`Reserved` quantities in-stock to fulfill the batch picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:175 +msgid "Click the :guilabel:`Check Availability` button to search the stock again for available products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:0 +msgid "Show unavailable reserved quantities in the *Operations* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:182 +msgid "Create backorder" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:184 +msgid "On the batch transfer form, if the :guilabel:`Done` quantity of the product is *less* than the :guilabel:`Reserved` quantity, a pop-up window appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:187 +msgid "This pop-up window provides the option: :guilabel:`Create Backorder?`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:189 +msgid "Clicking the :guilabel:`Create Backorder` button automatically creates a new batch transfer, containing the remaining products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:192 +msgid "Click :guilabel:`No Backorder` to finish the picking *without* creating another batch picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:194 +msgid "Click :guilabel:`Discard` to cancel the validation, and return to the batch transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:-1 +msgid "Show the *Create Backorder* pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:203 +msgid "Process batch transfer: Barcode app" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:205 +msgid "Created batch transfers are also listed in the :menuselection:`Barcode` app, accessible by selecting the :guilabel:`Batch Transfers` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:208 +msgid "By default, confirmed batch pickings appear on the :guilabel:`Batch Transfers` page. On that page, click on the desired batch transfer to open the detailed list of products for the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:-1 +msgid "Show list of to-do batch transfers in *Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:215 +msgid "For the chosen batch transfer, follow the instructions at the top of the page in the black background. Begin by scanning the product's barcode to record a single product for picking. To record multiple quantities, click the :guilabel:`✏️ (pencil)` icon, and enter the required quantities for the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:221 +msgid "Products from the same order are labeled with the same color on the left. Completed pickings are highlighted in green." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:225 +msgid "In a batch transfer for 2 `Cabinet with Doors`, 3 `Acoustic Bloc Screens`, and 4 `Four Person Desks`, the `3/3` and `4/4` :guilabel:`Units` indicate that the last two product pickings are complete." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:229 +msgid "`1/2` units of the `Cabinet with Doors` has already been picked, and after scanning the product barcode for the second cabinet, Odoo prompts the user to `Scan a serial number` to record the unique serial number for :ref:`product tracking `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:0 +msgid "Display products to be picked in barcode view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:237 +msgid "Once all the products have been picked, click on :guilabel:`Validate` to mark the batch transfer as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:3 +msgid "Cluster picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:10 +msgid "Cluster picking is an advanced order fulfillment approach derived from :ref:`batch picking `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:13 +msgid "In this strategy, pickers load a cart with multiple packages, each designated for a specific *sales order* (SO). Then, the picker travels to each storage location, and places the products directly in the package of the associated order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:17 +msgid "This method is most efficient for medium-sized companies, with high order volumes, and relatively few unique products, since the method eliminates the need for sorting products into packages for customers after picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:21 +msgid "However, cluster picking does have some disadvantages. For instance, urgent orders cannot be prioritized, and optimized batches must be manually created beforehand. As a result, the picking process can lead to bottlenecks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:28 +msgid "|SO| 1 calls for one apple and orange" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:29 +msgid "|SO| 2 calls for one apple and banana" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:30 +msgid "|SO| 3 calls for one apple, orange, and banana" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:32 +msgid "Apples are stored in Shelf A, oranges in Shelf B, and bananas in Shelf C." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:34 +msgid "To pick products for three orders at once, the cart is loaded with three empty packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:36 +msgid "Starting at Shelf A, the picker places apples into each package. Next, the picker navigates to Shelf B, and places oranges in the packages designated for |SO| 1 and |SO| 3. Finally, the picker pushes the cart to Shelf C, and loads packages for |SO| 2 and |SO| 3 with a banana, each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:40 +msgid "With the packages for all three |SOS| packed, the picker pushes the cart to the output location, where the packages are sealed and prepared for shipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:0 +msgid "Show example of fulfilling sales orders 2 and 3 at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:50 +msgid "To enable cluster picking, begin by navigating to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Operations` heading, activate the :guilabel:`Packages` and :guilabel:`Batch Transfers` options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:-1 +msgid "Activate *Packages* and *Batch Transfers* features in the settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:58 +msgid "Since batch picking is used to optimize the *pick* operation in Odoo, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` options, under the :guilabel:`Warehouse` heading, must also be checked on this settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:62 +msgid "*Storage locations* allow products to be stored in specific locations they can be picked from, while *multi-step routes* enable the picking operation itself." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:65 +msgid "When finished, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:74 +msgid "Packages setup" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:76 +msgid "After the :guilabel:`Packages` feature is enabled, navigate to :menuselection:`Inventory app --> Products --> Packages`, and click the :guilabel:`New` button to create a new package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:79 +msgid "On the new package form, the :guilabel:`Package Reference` is pre-filled with the next available `PACK` number in the system. :guilabel:`Pack Date` is automatically set to the creation date of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:83 +msgid "Set the :guilabel:`Package Use` field to :guilabel:`Reusable Box`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:86 +msgid ":doc:`Packages <../../product_management/configure/package>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:89 +msgid "A package intended for cluster picking is named `CLUSTER-PACK-3` for easy identification. For this workflow, the products are directly packed using their intended shipping boxes, so :guilabel:`Package Use` is set to :guilabel:`Disposable Box`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:0 +msgid "Create new package form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:98 +msgid "Create cluster batch" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:100 +msgid "To see how cluster picking works in Odoo, navigate to the :menuselection:`Sales` app, and create |SOS| that will be fulfilled together in the same batch. After confirming an |SO|, the :guilabel:`Delivery` smart button becomes visible. Displayed inside the icon is a number representing the amount of steps in the outgoing shipment process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:106 +msgid "Begin by creating three |SOS| for the apples, oranges, and bananas, as shown in the :ref:`example above `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:109 +msgid "After confirming the |SO|, the :guilabel:`Delivery` smart button displays the number `2`, indicating there are two operations to complete: `Pick` and `Delivery`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:0 +msgid "Example sales order for an apple, orange, and banana." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:116 +msgid "With the |SOS| created, orders now must be grouped into batches. To do so, navigate to the *Inventory* dashboard and select the operation type card, :guilabel:`Delivery Orders` or :guilabel:`Pick` (whichever is the first operation in the delivery flow)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:120 +msgid "Doing so displays a filtered list of outgoing operations with the :guilabel:`Ready` status, indicating that all the products in the |SO| are in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:124 +msgid "Cluster pick batches can be created for outgoing shipments in one, two, or three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:127 +msgid ":doc:`Delivery in one step <../daily_operations/receipts_delivery_one_step>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:129 +msgid ":doc:`Delivery in three steps <../daily_operations/delivery_three_steps>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:131 +msgid "Click the checkbox to the left of the corresponding outgoing operation to add them to the batch. With the desired pickings selected, click the :guilabel:`⚙️ Actions (gear)` button, and select the :guilabel:`Add to batch` option from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:136 +msgid "To create a cluster batch, as shown in the :ref:`example above `, in a warehouse configured with two-step outgoing shipments, the following pick operations are selected:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:140 +msgid "`WH/PICK/00007`: linked to |SO| 88 for one apple and orange." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:141 +msgid "`WH/PICK/00008`: linked to |SO| 89 for one apple and banana." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:142 +msgid "`WH/PICK/00009`: linked to |SO| 90 for one apple, orange, and banana." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:151 +msgid "Choose from the two options in the :guilabel:`Add to` field to either: add to :guilabel:`an existing batch transfer`, or create :guilabel:`a new batch transfer`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:154 +msgid "To create draft batch pickings to be confirmed at a later date, select the :guilabel:`Draft` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:164 +msgid "Process batches" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:166 +msgid "To process batches, navigate to :menuselection:`Inventory app --> Operations --> Batch Transfers`. Click on a batch to select it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:169 +msgid "In the :guilabel:`Detailed Operations` tab, products that are to be picked are grouped by location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:171 +msgid "Under the :guilabel:`Source Package` or :guilabel:`Destination Package` field, enter the package used for the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:175 +msgid "Use the :guilabel:`Source Package` field when the picking package is configured as *reusable* on the :ref:`package form `. This means the products are temporarily placed in a container during picking, before getting transferred to their final shipping box." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:179 +msgid "Alternatively, use the :guilabel:`Destination Package` field when the product is directly placed in its *disposable* shipping box during picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:183 +msgid "Process the cluster batch for the three orders of apples, oranges, and bananas :ref:`example ` by assigning each picking to a dedicated package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:186 +msgid "At the storage location for apples, `WH/Stock/Shelf A`, assign the apples in all three pickings to one of the three disposable packages, `CLUSTER-PACK-1`, `CLUSTER-PACK-2`, or `CLUSTER-PACK-3`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:189 +msgid "Record this in Odoo using the :guilabel:`Destination Package` field in the :guilabel:`Detailed Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:0 +msgid "Example of processing cluster pickings in *Inventory*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:197 +msgid "In Barcode" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:199 +msgid "To process cluster pickings directly from the *Barcode* app, select the :guilabel:`Batch Transfers` button from the *Barcode* dashboard. Then, select the desired batch." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:202 +msgid "On the batch transfer screen, the products in the picking are grouped by location, and each line is color-coded to associate products in the same picking together." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:205 +msgid "Then, follow the prompt to :guilabel:`Scan the source location` barcode for the storage location of the first product. Then, scan the barcode for the product and package to process the transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:208 +msgid "Repeat this for all products, and click the :guilabel:`Validate` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:211 +msgid "To find the package barcode, navigate to :menuselection:`Inventory app --> Products --> Packages`, select the desired package, click the :guilabel:`⚙️ (gear)` icon at the top of the package form, and select the :guilabel:`Print` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:215 +msgid "Next, select one of the three print options to generate the package barcode from the :guilabel:`Package Reference` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:0 +msgid "Display where the package barcode can be generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:223 +msgid "Begin processing the cluster picking by going to the first storage location, `Shelf A`, and scanning the :ref:`location barcode `. Doing so highlights all the pickings that need products from this particular location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:227 +msgid "Scan the barcode for the apple, which highlights the picking (labeled in red) for the product `Apple`, for the picking, `WH/PICK/00007`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:230 +msgid "Then, scan the `CLUSTER-PACK-1` package barcode, and place the product in the designated package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:0 +msgid "Example of cluster batch from the *Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.rst:237 +msgid "After creating a batch transfer and assigning a package to a picking, Odoo suggests the specified package by displaying the name *in italics* under the product name, ensuring pickers place products into the correct boxes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:3 +msgid "Process wave transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:5 +msgid "While a batch transfer is a group of several pickings, a **wave transfer** only contains some parts of different pickings. Both methods are used to pick orders in a warehouse, and depending on the situation, one method may be a better fit than the other." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:9 +msgid "To handle orders of a specific product category, or fetch products that are at the same location, wave transfers are the ideal method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:12 +msgid "In Odoo, wave transfers are actually batch transfers with an extra step: transfers are split before being grouped in a batch." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:18 +msgid "Before a wave transfer can be created, the :guilabel:`Batch Transfers` and :guilabel:`Wave Transfers` options must be activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:21 +msgid "First, go to :menuselection:`Inventory --> Configuration --> Settings`. In the :guilabel:`Operations` section, enable :guilabel:`Batch Transfers` and :guilabel:`Wave Transfers`. Then, click :guilabel:`Save` to apply the settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:-1 +msgid "View of Odoo Inventory app settings to enable the wave transfers option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:30 +msgid "Add products to a wave" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:32 +msgid "Now that the settings are activated, start a wave transfer by adding products to a wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:34 +msgid "Wave transfers can only contain product lines from transfers of the same operation type. To view all the transfers and product lines in a specific operation, first go to the :guilabel:`Inventory` dashboard and locate the desired operation type's card. Then, open the options menu (the three dots icon in the corner of the operation type's card) and click :guilabel:`Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:-1 +msgid "How to get an operation type's list of operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:43 +msgid "On the operations page, select the product lines you want to add in a new or existing wave. Then, click :guilabel:`Add to Wave`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:-1 +msgid "Select lines to add to the wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:51 +msgid "Use the :guilabel:`Filters` in the search bar to group lines with the same product, location, carrier, etc..." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:54 +msgid "After that, a pop-up box appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:56 +msgid "To add the selected lines to an existing wave transfer, select the :guilabel:`an existing wave transfer` option and select the existing wave transfer from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:59 +msgid "To create a new wave transfer, select the :guilabel:`a new wave transfer` option. If creating a new wave transfer, an employee can also be set in the optional :guilabel:`Responsible` field. Once the desired options are selected, click :guilabel:`Confirm` to add the product lines to a wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:64 +msgid "View wave transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.rst:66 +msgid "To view all wave transfers and their statuses, go to :menuselection:`Inventory --> Operations --> Wave Transfers`. Wave transfers can also be viewed in the :guilabel:`Barcode` app by going to :menuselection:`Barcode --> Batch Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:6 +msgid "Removal strategies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:8 +msgid "For companies with warehouses, *removal strategies* determine **which** products are taken from the warehouse, and **when**. For example, for perishable products, prioritizing the picking of goods with the nearest expiration date helps minimize food spoilage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:12 +msgid "The following columns in the table below list the removal strategies available in Odoo, and detail how pickings are determined along with the picking order. Leverage these removal strategies to have Odoo automatically select how products are selected for orders:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:21 +msgid ":doc:`FIFO `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:22 +msgid ":doc:`LIFO `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:23 +msgid ":doc:`FEFO `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:24 +msgid ":doc:`Closest Location `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:25 +msgid ":doc:`Least Packages `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:26 +msgid "Based on" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:28 +msgid ":ref:`Incoming date `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:29 +msgid ":ref:`Removal date `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:30 +msgid ":ref:`Location sequence `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:31 +msgid ":ref:`Package quantity `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:32 +msgid "Selection order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:33 +msgid "First in" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:34 +msgid "Last in" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:35 +msgid ":ref:`First to expire `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:36 +msgid ":ref:`Alphanumeric name of location `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:37 +msgid "Quantity closest to fulfilling demand" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:39 +msgid "For comprehensive examples for how to use each removal strategy, refer to each individual documentation page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:47 +msgid "Removal strategies are set on either the product category or storage location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "Change the Force Removal Strategy for either the Product Categories or Locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:53 +msgid "Configure removal strategies on the location by going to :menuselection:`Inventory --> Configuration --> Locations`, and selecting the desired location. On the location form, choose a removal strategy from the :guilabel:`Removal Strategy` field's drop-down menu options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:58 +msgid "To set a removal strategy on a location, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` settings **must** be enabled in :menuselection:`Inventory --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:62 +msgid "These features are **only** necessary when setting the removal strategy on a location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:64 +msgid "Configure removal strategies on product categories by going to :menuselection:`Inventory --> Configuration --> Product Categories` and selecting the intended product category. Next, choose a removal strategy from the :guilabel:`Force Removal Strategy` drop-down menu options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:69 +msgid "When there are different removal strategies applied on both the location and product category for a product, the value set on the :guilabel:`Force Removal Strategy` field set on a :guilabel:`Product Category` form is applied as top priority." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:74 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:94 +msgid "Required features" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:76 +msgid "While some removal strategies are available by default, some additional features **must** be enabled in :menuselection:`Inventory --> Configuration --> Settings` for the removal strategy option to appear in the drop-down menu of the :guilabel:`Force Removal Strategy` or :guilabel:`Removal Strategy` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:81 +msgid "Refer to the table below for a summary of required features. Otherwise, refer to the dedicated sections for the removal strategy for more details on requirements and usage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:89 +msgid "FIFO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:90 +msgid "LIFO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:91 +msgid "FEFO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:92 +msgid "Closest Location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:93 +msgid "Least Packages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:96 +msgid "Lots & Serial Numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:97 +msgid "Lots & Serial Numbers, Expiration Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:98 +msgid "Storage Locations, Multi-Step Routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:104 +msgid "Lots and serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:106 +msgid "Lots and serial numbers differentiate identical products and track information like arrival or expiration dates. To enable this feature, navigate to :menuselection:`Inventory --> Configuration --> Settings`. Under the :guilabel:`Traceability` heading, check the box beside :guilabel:`Lots & Serial Numbers` to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:115 +msgid "Next, ensure the intended product is tracked by lots or serial numbers by navigating to the product form through :menuselection:`Inventory --> Products --> Products`, and selecting the desired product. On the product form, switch to the :guilabel:`Inventory` tab, and under the :guilabel:`Tracking` field, select either the :guilabel:`By Unique Serial Number` or :guilabel:`By Lots` options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:121 +msgid "After enabling the features, assign lot or serial numbers to products using an :doc:`inventory adjustment <../warehouses_storage/inventory_management/count_products>` or during :ref:`product reception `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:126 +msgid "Locations and routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:128 +msgid "**Storage locations** and **multi-step routes** are necessary features for setting **all** types of removal strategies on a location. However, these features are specifically required for the closest location removal strategy since it is only applied at the location level." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:132 +msgid "To activate these features, navigate to :menuselection:`Inventory --> Configuration --> Settings`. Under the :guilabel:`Warehouse` heading, enable the :guilabel:`Storage Location` and :guilabel:`Multi-Step Routes` features." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "Enable the locations and route features." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:97 +msgid "Expiration date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:145 +msgid "Enable the **expiration date** feature to track expiration dates, best before dates, removal dates, and alert dates on a lot or serial number by navigating to :menuselection:`Inventory --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:149 +msgid "Under the :guilabel:`Traceability` heading, ensure the :guilabel:`Lots & Serial Numbers` feature is selected, and then select the check box for :guilabel:`Expiration Dates` to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "Enable expiration dates feature for FEFO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:161 +msgid "The *packages* feature is used to group products together and is required for the least packages removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:164 +msgid "Navigate to :menuselection:`Inventory --> Configuration --> Settings` and select the check box for the :guilabel:`Packages` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "Enable the packages feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:172 +msgid ":doc:`Packages <../product_management/configure/package>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:173 +msgid ":doc:`2-step delivery `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:174 +msgid ":doc:`3-step delivery `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:3 +msgid "Closest location removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:5 +msgid "For the *Closest Location* removal strategy, products are picked based on the alphanumeric order of storage location titles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:8 +msgid "The goal of this strategy is to save the warehouse worker from taking a long journey to a farther shelf when the product is also available at a closer location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:13 +msgid ":doc:`About removal strategies <../removal_strategies>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:16 +msgid "To understand *location sequence* in the closest removal strategy, consider the following example:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:19 +msgid "A product is stored in the following locations: `Shelf A/Pallet`, `Shelf A/Rack 1`, and `Shelf A/Rack 2`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:-1 +msgid "Show a mockup of real storage location in a warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:26 +msgid "The sublocation, `Pallet`, is on the ground level. Products stored here are easier to retrieve, compared to requiring a forklift to reach `Rack 1` and `Rack 2`. The storage locations were strategically named in alphabetic order, based on ease of access." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:31 +msgid "To use this removal strategy, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` settings **must** be enabled in :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:35 +msgid ":ref:`Set up removal strategy `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:40 +msgid "Location names" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:42 +msgid "To configure location names, begin by navigating to :menuselection:`Inventory app --> Configuration --> Locations`. Then, select an existing location, or click :guilabel:`New` to create a new one, and then enter the desired name in the :guilabel:`Location Name` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:46 +msgid "Once the locations are named in alphabetical order, based on their proximity to the output or packing location, set the removal strategy on the :ref:`parent location `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:50 +msgid "To do that, in the :guilabel:`Locations` list, select the parent location of the alphabetically named storage locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:53 +msgid "Doing so opens the form for the parent location. In the :guilabel:`Removal Strategy` field, select :guilabel:`Closest Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:57 +msgid "In a warehouse, the storage location `WH/Stock/Shelf 1` is located closest to the packing area, where products retrieved from shelves are packed for shipment. The popular product, `iPhone charger` is stored in three locations, `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and `WH/Stock/Shelf 3`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:62 +msgid "To use closest location, set the removal strategy on the parent location, 'WH/Stock'." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:79 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:37 +msgid "Workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:67 +msgid "To see how the closest location removal strategy works, consider the following example, featuring the popular product, `iPhone charger`, which is stored in `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and `WH/Stock/Shelf 3`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:71 +msgid "Fifteen, five, and thirty units are in stock at each respective location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:74 +msgid "To check the on-hand stock at each storage location, navigate to the product form, and click the :guilabel:`On Hand` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:0 +msgid "Show on-hand stock at all locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:81 +msgid "Create a :ref:`delivery order ` for eighteen units of the `iPhone charger` by navigating to the :menuselection:`Sales app` and creating a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:84 +msgid "After adding the products, clicking :guilabel:`Confirm` creates a delivery order that reserves items stored at the closest location, using the removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:87 +msgid "For more details about *where* the units were picked, select the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right. Doing so opens the :guilabel:`Open: Stock move` pop-up window that displays how the reserved items were picked, according to the removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:91 +msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked. All fifteen of the units stored at the closest location, `WH/Stock/Shelf 1`, are picked first. The remaining three units are then selected from the second closest location, `WH/Stock/Shelf 2`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.rst:-1 +msgid "Display *Pick From* quantities for the order for iPhone chargers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:3 +msgid "FEFO removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:5 +msgid "The *First Expired, First Out* (FEFO) removal strategy targets products for removal based on their assigned removal dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:14 +msgid "Removal date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:16 +msgid "Products **must** be removed from inventory before their *removal date*, which is set as a certain number of days before the product's *expiration date*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:19 +msgid "The user sets this number of days by navigating to the product form's :guilabel:`Inventory` tab. Under the :guilabel:`Traceability` section, ensure the :guilabel:`Tracking` field is set to either :guilabel:`By Lots` or :guilabel:`By Unique Serial Number`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:23 +msgid "Next, select the :guilabel:`Expiration Date` option, which makes the :guilabel:`Removal Date` field (and other date fields) appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:27 +msgid "The :guilabel:`Lots and Serial Numbers` and :guilabel:`Expiration Dates` features **must** be enabled in :menuselection:`Inventory app --> Configuration --> Settings` to track expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:31 +msgid "The expiration date of a product is determined by adding the date the product was received to the number of days specified in the :guilabel:`Expiration Date` field of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:34 +msgid "The removal date takes this expiration date, and subtracts the number of days specified in the :guilabel:`Removal Date` field of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:38 +msgid ":doc:`Expiration dates <../../product_management/product_tracking/expiration_dates>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:41 +msgid "In the :guilabel:`Inventory` tab of the product, `Egg`, the following :guilabel:`Dates` are set by the user:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:44 +msgid ":guilabel:`Expiration Date`: `30` days after receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:45 +msgid ":guilabel:`Removal Date`: `15` days before expiration date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:-1 +msgid "Display expiration and removal dates set on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:51 +msgid "A shipment of Eggs arrive at the warehouse on January 1st. So, the expiration date of the Eggs is **January 31st** (Jan 1st + 30). By extension, the removal date is **January 16th** (Jan 31 - 15)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:57 +msgid "To view the expiration dates of items in stock, navigate to the product form, and click the :guilabel:`On Hand` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:60 +msgid "Next, click the additional options icon, located on the far-right, and select the columns: :guilabel:`Expiration Date` and :guilabel:`Removal Date`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:-1 +msgid "Show expiration dates from the inventory adjustments model accessed from the *On Hand*\n" +"smart button from the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:71 +msgid "Using the :abbr:`FEFO (First Expired, First Out)` removal strategy ensures that products with the nearest removal date are picked first." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:74 +msgid "To understand how this removal strategy works, consider the following example below about the product, `Carton of eggs`, which is a box containing twelve eggs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:77 +msgid "The product is tracked :guilabel:`By Lots`, and the product category's :guilabel:`Force Removal Strategy` is set to :guilabel:`First Expired, First Out (FEFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:24 +msgid ":ref:`Set up force removal strategy `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:60 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:25 +msgid ":ref:`Enable lots tracking `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:83 +msgid "`Odoo Tutorials: Perishable Products `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:35 +msgid "LOT1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:36 +msgid "LOT2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:37 +msgid "LOT3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:72 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:38 +msgid "On-hand stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:73 +msgid "5" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:75 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:145 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:186 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:257 +msgid "2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:96 +msgid "1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:98 +msgid "April 4" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:99 +msgid "April 10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:100 +msgid "April 15" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:101 +msgid ":ref:`Removal date `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:102 +msgid "February 26" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:103 +msgid "March 4" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:104 +msgid "March 9" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:106 +msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and create a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:109 +msgid "Clicking :guilabel:`Confirm` creates a delivery order for today, December 29th, and the lot numbers with the soonest expiration dates are reserved, using the :abbr:`FEFO (First Expired, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:113 +msgid "To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right of the Carton of egg's product line, in the :guilabel:`Operations` tab of the delivery order. Doing so opens the :guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:117 +msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:120 +msgid "Since the order demanded six Cartons of eggs, using the :abbr:`FEFO (First Expired, First Out)` removal strategy, all five Cartons from `LOT1`, with the removal date of February 26th, are picked. The remaining Carton is selected from `LOT2`, which has a removal date of March 4th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.rst:-1 +msgid "The stock moves window that shows the lots to be removed using FEFO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:3 +msgid "FIFO removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:5 +msgid "The *First In, First Out* (FIFO) removal strategy selects products with the earliest arrival dates. This method is useful for companies selling products that have short demand cycles, like clothes, for example. By using :abbr:`FIFO (First In, First Out)`, companies can prevent prolonged stock retention of specific styles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:14 +msgid "Various quantities of the product, `T-shirt`, tracked by lot numbers, arrive on August 1st and August 25th. For an order made on September 1st, the :abbr:`FIFO (First In, First Out)` removal strategy prioritizes lots that have been in stock the longest. So, products received on August 1st are selected first for picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:0 +msgid "Illustration of FIFO selecting the oldest products in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:24 +msgid ":ref:`Lot/serial number setup details `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:29 +msgid "Arrival date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:31 +msgid "To see the product lot or serial number that arrived in inventory first, navigate to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:34 +msgid "Then, select the :guilabel:`▶️ (right-pointing arrow)` icon on the left of a product line, in order to reveal a list of the product's lots or serial numbers that are in stock. The :guilabel:`Created On` field shows the lot/serial number creation date, which is, essentially, the arrival date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:39 +msgid "Serial number `00000000500` of the product, `Cabinet with Doors`, arrived on December 29th, as displayed in the :guilabel:`Created On` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:0 +msgid "Display arrival date of a lot for an item." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:49 +msgid "To understand how :abbr:`FIFO (First In, First Out)` rotates products out, consider the following example, focusing on three lots of white shirts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:52 +msgid "The shirts are from the *All/Clothes* category, where :abbr:`FIFO (First In, First Out)` is set as the :guilabel:`Force Removal Strategy`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:55 +msgid "The white shirts are tracked :guilabel:`By Lots` in the :guilabel:`Inventory` tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:62 +msgid "The following table represents the on-hand stock and lot number details of white shirts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:74 +msgid "3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:42 +msgid ":ref:`Created on `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:77 +msgid "March 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:78 +msgid "April 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:79 +msgid "May 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:81 +msgid "To see the removal strategy in action, create a :ref:`delivery order ` for six white shirts by navigating to the :menuselection:`Sales app` and creating a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:84 +msgid "After clicking :guilabel:`Confirm` on the sales order, a delivery order with the oldest lot numbers for shirts are reserved, using the :abbr:`FIFO (First In, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:87 +msgid "To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right of the white shirt's product line in the :guilabel:`Operations` tab of the delivery order. Doing so opens the :guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:91 +msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked from. Since the order demanded six shirts, all five shirts from `LOT1`, and one shirt from `LOT2`, are selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fifo.rst:-1 +msgid "Two lots being reserved for a sales order with the FIFO strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:3 +msgid "Least packages removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:5 +msgid "The *Least Packages* removal strategy fulfills an order by opening the fewest number of packages, which is ideal for maintaining organized stock without needing to open multiple boxes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:10 +msgid "`Odoo Tutorials: Least Packages `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:12 +msgid "To understand how the removal strategy works, consider the following example, featuring a warehouse that stores packages of flour in bulk packages of `100 kg`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:15 +msgid "To minimize moisture, and/or prevent pests from entering open packages, the least packages removal strategy is used to pick from a single, opened package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:21 +msgid "A package of `100 kg` of flour is depleted to `54 kg` after fulfilling some orders. There are other packages of `100 kg` in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:24 +msgid "When an order for `14 kg` of flour is placed, the package of `54 kg` is selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:25 +msgid "When an order for *more* than `54 kg` of flour is placed, an unopened `100 kg` package is used to fulfill the order. While this temporarily results in two open packages, these open packages are prioritized in the next picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:32 +msgid "Using the least package removal strategy, the fewest number of packages is used to fulfill an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:35 +msgid "The :ref:`Packages feature ` **must** be enabled to use this strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:38 +msgid "Consider the following example, featuring the product, `Flour`. The product's :guilabel:`Units of Measure` field, located on the product form, is set to `kg`. The product is stored in packages of `100 kg`, with one remaining package containing `54 kg`. The product category's :guilabel:`Force Removal Strategy` is set to :guilabel:`Least Packages`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:44 +msgid ":ref:`Set removal strategy on product category `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:47 +msgid "To check the product's on-hand stock, navigate to the product form, and click the :guilabel:`On Hand` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:0 +msgid "Show on-hand stock in each package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:54 +msgid "Create a :ref:`delivery order ` for eighty kilograms of flour by going to the :menuselection:`Sales app` and creating a new quotation. After clicking :guilabel:`Confirm`, the delivery order is created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:58 +msgid "On the delivery order, the :guilabel:`Quantity` field displays the amount automatically picked, according to the removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:61 +msgid "For more details about *where* the units were picked, select the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right. Doing so opens the :guilabel:`Open: Stock move` pop-up window, displaying how the reserved items were picked, according to the removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:65 +msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked. Since the order demanded eighty kilograms, which exceeds the quantity in the opened package of `54 kg`, an unopened package of `100 kg` is selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/least_packages.rst:-1 +msgid "Show which package was picked in the *Pick From* field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:3 +msgid "LIFO removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:5 +msgid "The *Last In, First Out* (LIFO) removal strategy picks the **newest** products on-hand, based on the date they entered a warehouse's stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:8 +msgid "Every time an order is placed for products using the :abbr:`LIFO (Last In, First Out)` strategy, 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/shipping_receiving/removal_strategies/lifo.rst:16 +msgid "In many countries, the :abbr:`LIFO (Last In, First Out)` removal strategy is banned, since it can potentially result in old, expired, or obsolete products being delivered to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:19 +msgid "Consider the following example, with the product, `Cinder Block`, which is tracked :guilabel:`By Lots` in the :guilabel:`Inventory` tab of the product form. The :guilabel:`Force Removal Strategy` for the cinder block's product category is set to :guilabel:`Last In, First Out (LIFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:26 +msgid ":ref:`Check arrival date `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:28 +msgid "The following table represents the cinder blocks in stock, and their various lot number details." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:43 +msgid "June 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:44 +msgid "June 3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:45 +msgid "June 6" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:47 +msgid "To see the removal strategy in action, create a :ref:`delivery order ` for seven cinder blocks by navigating to the :menuselection:`Sales app` and creating a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:51 +msgid ":guilabel:`Confirm` the sales order to create a delivery order. Doing so reserves the newest lot numbers are using the :abbr:`LIFO (Last In, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:54 +msgid "To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right of the cinder block's product line in the :guilabel:`Operations` tab of the delivery order. Doing so opens the :guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:58 +msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked from. Since the order demanded seven cinder blocks, the newest cinder blocks from `LOT3` are selected, using the :abbr:`LIFO (Last In, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/lifo.rst:-1 +msgid "The detailed operations shows which lots are being selected for the picking." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:6 @@ -7522,16 +8222,6 @@ msgstr "" msgid "In the :guilabel:`General` tab on the operation type form, locate the :guilabel:`Reservation Method` field, and select :guilabel:`At Confirmation`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:30 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:79 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:37 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:65 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:69 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:47 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:30 -msgid "Workflow" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:32 msgid "To see the *at confirmation* reservation method in action, create a new |SO| by navigating to :menuselection:`Sales app --> New`." msgstr "" @@ -7863,8 +8553,272 @@ msgstr "" msgid "List of orders in waiting status and check availability button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:5 -msgid "Setup and configuration" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:6 +msgid "Delivery methods" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:8 +msgid "When activated in Odoo, the *Delivery Methods* setting adds the option of calculating the cost of shipping on sales orders and e-commerce shopping carts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:11 +msgid "When integrated with a :ref:`third-party carrier `, shipping prices are calculated based on the carrier's pricing and packaging information." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:15 +msgid ":ref:`Third-party shipping carrier setup `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:16 +msgid "`Odoo Tutorials: Delivery Prices `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:22 +msgid "To calculate shipping on sales orders and e-commerce, the *Delivery Costs* module must be installed. To do so, navigate to the :menuselection:`Apps` application from the main Odoo dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:25 +msgid "Then, remove the :guilabel:`Apps` filter, and type in `Delivery Costs` in the :guilabel:`Search...` bar. After finding the :guilabel:`Delivery Costs` module, click :guilabel:`Activate` to install it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:-1 +msgid "Install the Delivery Costs module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:33 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:28 +msgid "Add shipping method" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:35 +msgid "To configure delivery methods, go to :menuselection:`Inventory app --> Configuration --> Shipping Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:39 +msgid "If the :guilabel:`Shipping Methods` option is not available from the :guilabel:`Configuration` drop-down menu, verify whether the feature is enabled by following these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:42 +msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:43 +msgid "Scroll to the :guilabel:`Shipping` section and enable the :guilabel:`Delivery Methods` feature by checking the corresponding checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:0 +msgid "Enable the *Delivery Methods* feature by checking the box in Configuration > Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:50 +msgid "On the :guilabel:`Shipping Methods` page, add a method by clicking :guilabel:`New`. Doing so opens a form to provide details about the shipping provider, including:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:53 +msgid ":guilabel:`Shipping Method` (*Required field*): the name of the delivery method (e.g. `flat-rate shipping`, `same day delivery`, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:55 +msgid ":guilabel:`Provider` (*Required field*): choose the delivery service, like Fedex, if using a :ref:`third-party carrier `. Ensure the integration with the shipping carrier is properly installed and select the provider from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:59 +msgid "For more details on configuring custom shipping methods, such as :ref:`fixed price `, :ref:`based on rules `, or :ref:`pickup in store ` options, refer to their respective sections below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:46 +msgid ":guilabel:`Website`: configure shipping methods for an e-commerce page. Select the applicable website from the drop-down menu, or leave it blank to apply the method to all web pages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:128 +msgid ":guilabel:`Company`: if the shipping method should apply to a specific company, select it from the drop-down menu. Leave the field blank to apply the method to all companies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:69 +msgid ":guilabel:`Delivery Product` (*Required field*): the product listed on the :ref:`sales order line ` as the delivery charge." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:51 +msgid ":guilabel:`Free if order amount is above`: checking this box enables free shipping if the customer spends above the specified amount." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:74 +msgid "For examples on how to configure specific shipping methods, refer to the sections below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:79 +msgid "Fixed price" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:81 +msgid "To configure a shipping price that is the same for all orders, go to :menuselection:`Inventory app --> Configuration --> Shipping Methods`. Then, click :guilabel:`New`, and on the shipping method form, set the :guilabel:`Provider` to the :guilabel:`Fixed Price` option. Selecting this option makes the :guilabel:`Fixed Price` field become available, which is where the fixed rate shipping amount is defined." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:87 +msgid "To enable free shipping if the amount of the order exceeds a specified amount, check the box :guilabel:`Free if order amount is above` and fill in the amount." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:91 +msgid "To set up `$20` flat-rate shipping that becomes free if the customer spends over `$100`, fill in the following fields:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:94 +msgid ":guilabel:`Shipping Method`: `Flat-rate shipping`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:95 +msgid ":guilabel:`Provider`: :guilabel:`Fixed Price`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:96 +msgid ":guilabel:`Fixed Price`: `$20.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:97 +msgid ":guilabel:`Free if order amount is above`: `$100.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:98 +msgid ":guilabel:`Delivery Product`: `[SHIP] Flat`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:0 +msgid "Example of filling out a shipping method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:107 +msgid "Based on rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:109 +msgid "To calculate the price of shipping based on pricing rules, set the :guilabel:`Provider` field to the :guilabel:`Based on Rules` option. Optionally, adjust :guilabel:`Margin on Rate` and :guilabel:`Additional margin` to include additional shipping costs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:114 +msgid "Create pricing rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:116 +msgid "Navigate to the :guilabel:`Pricing` tab and click :guilabel:`Add a line`. Doing so opens the :guilabel:`Create Pricing Rules` window, where the :guilabel:`Condition` related to the product weight, volume, price, or quantity is compared to a defined amount to calculate the :guilabel:`Delivery Cost`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:121 +msgid "Once finished, click either :guilabel:`Save & New` to add another rule, or :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:124 +msgid "To charge customers $20 in shipping for orders with five or fewer products, set the :guilabel:`Condition` to `Quantity <= 5.00`, and the :guilabel:`Delivery Cost` to `$20`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:0 +msgid "Display window to add a pricing rule. Set a condition and delivery cost." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:131 +msgid "To restrict shipping to specific destinations on the eCommerce website, in the shipping method form, navigate to the :guilabel:`Destination Availability` tab and define the :guilabel:`Countries`, :guilabel:`States`, and :guilabel:`Zip Prefixes`. Leave these fields empty if all locations apply." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:136 +msgid "Calculate delivery cost" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:138 +msgid "Shipping cost is the :guilabel:`Delivery cost` specified in the rule that satisfies the :guilabel:`Condition`, plus any extra charges from the :guilabel:`Margin on rate` and :guilabel:`Additional margin`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:142 +msgid "Total = Rule's~Delivery~Cost + (Margin~on~rate \\times Rule's~Delivery~Cost) + Additional~margin\n" +"\n" +"" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:146 +msgid "With the two following rules set up:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:148 +msgid "If the order contains five or fewer products, shipping is $20" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:149 +msgid "If the order contains more than five products, shipping is $50." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:151 +msgid ":guilabel:`Margin on Rate` is `10%` and :guilabel:`Additional margin` is `$9.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:-1 +msgid "Show example of \"Based on rules\" shipping method with margins configured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:157 +msgid "When the first rule is applied, the delivery cost is $31 (20 + (0.1 * 20) + 9). When the second rule is applied, the delivery cost is $64 (50 + (0.1 * 50) + 9)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:163 +msgid "Pickup in store" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:165 +msgid "To configure in-store pickup, select :guilabel:`Pickup in store` in the :guilabel:`Provider` field and specify the pickup location in :guilabel:`Warehouse`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:168 +msgid "To invoice the customer for the shipping cost to the pickup location, choose the :guilabel:`Get Rate and Create Shipment` option in the :guilabel:`Integration Level` field. Then, pick either the :guilabel:`Estimated cost` or :guilabel:`Real cost` radio options in the :guilabel:`Invoicing Policy` field to decide whether the added shipping charge on the sales order is the precise cost from the shipping carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:175 +msgid ":doc:`Invoice cost of shipping `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:180 +msgid "Add shipping" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:182 +msgid "Shipping methods can be added to sales orders in the form of delivery products, which appear as individual line items. First, navigate to the desired sales order by going to :menuselection:`Sales app --> Orders --> Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:186 +msgid "On the sales order, click the :guilabel:`Add shipping` button, which opens the :guilabel:`Add a shipping method` pop-up window. Then, choose a :guilabel:`Shipping Method` from the list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:189 +msgid "The :guilabel:`Total Order Weight` is pre-filled based on product weights (that are defined in the :guilabel:`Inventory` tab for each product form). Edit the field to specify the exact weight, and then click :guilabel:`Add` to add the shipping method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:194 +msgid "The amount defined in :guilabel:`Total Order Weight` overwrites the total product weights defined on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:197 +msgid "The shipping cost is added to the *sales order line* as the :guilabel:`Delivery Product` detailed on the shipping method form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:201 +msgid "`Furniture Delivery`, a delivery product with a fixed rate of `$200`, is added to sales order `S00088`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:0 +msgid "Show delivery order on the sales order line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:209 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:260 +msgid "Delivery order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:211 +msgid "The shipping method added to the sales order is linked to the shipping carrier details on the delivery order. To add or change the delivery method on the delivery itself, go to the :guilabel:`Additional Info` tab and modify the :guilabel:`Carrier` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:-1 +msgid "Shipping carrier information on the delivery form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:3 @@ -7897,7 +8851,7 @@ msgid ":doc:`third_party_shipper`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:18 -msgid ":doc:`delivery_method`" +msgid ":doc:`../setup_configuration`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:19 @@ -8022,251 +8976,63 @@ msgstr "" msgid "Show Bpost shipping method." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:3 -msgid "Delivery methods" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel.rst:3 +msgid "How to cancel a shipping request to a shipper?" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:5 -msgid "When activated in Odoo, the *Delivery Methods* setting adds the option of calculating the cost of shipping on sales orders and e-commerce shopping carts." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:6 +msgid "Overview" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:8 -msgid "When integrated with a :ref:`third-party carrier `, shipping prices are calculated based on the carrier's pricing and packaging information." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel.rst:8 +msgid "Odoo can handle various delivery methods, including third party shippers. Odoo will be linked with the transportation company tracking system." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:12 -msgid ":ref:`Third-party shipping carrier setup `" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel.rst:12 +msgid "It will allow you to manage the transport company, the real prices and the destination." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:13 -msgid "`Odoo Tutorials: Delivery Prices `_" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel.rst:15 +msgid "You can easily cancel the request made to the carrier system." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:19 -msgid "To calculate shipping on sales orders and e-commerce, the *Delivery Costs* module must be installed. To do so, navigate to the :menuselection:`Apps` application from the main Odoo dashboard." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel.rst:18 +msgid "How to cancel a shipping request?" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:22 -msgid "Then, remove the :guilabel:`Apps` filter, and type in `Delivery Costs` in the :guilabel:`Search...` bar. After finding the :guilabel:`Delivery Costs` module, click :guilabel:`Activate` to install it." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel.rst:20 +msgid "If the delivery order is not **Validated**, then the request hasn't been made. You can choose to cancel the delivery or to change the carrier." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:-1 -msgid "Install the *Delivery Costs* module." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel.rst:24 +msgid "If you have clicked on **Validate**, the request has been made and you should have received the tracking number and the label. You can still cancel the request. Simply click on the **Cancel** button next to the **Carrier Tracking Ref**:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:32 -msgid "To configure delivery methods, go to :menuselection:`Inventory app --> Configuration --> Shipping Methods`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel.rst:32 +msgid "You will now see that the shipment has been cancelled." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:36 -msgid "If the :guilabel:`Shipping Methods` option is not available from the :guilabel:`Configuration` drop-down menu, verify whether the feature is enabled by following these steps:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel.rst:37 +msgid "You can now change the carrier if you wish." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:39 -msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel.rst:40 +msgid "How to send a shipping request after cancelling one?" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:40 -msgid "Scroll to the :guilabel:`Shipping` section and enable the :guilabel:`Delivery Methods` feature by checking the corresponding checkbox." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel.rst:42 +msgid "After cancelling the shipping request, you can change the carrier you want to use. Confirm it by clicking on the **Send to shipper** button. You will get a new tracking number and a new label." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 -msgid "Enable the *Delivery Methods* feature by checking the box in Configuration > Settings." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:163 +msgid ":doc:`invoicing`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:47 -msgid "On the :guilabel:`Shipping Methods` page, add a method by clicking :guilabel:`New`. Doing so opens a form to provide details about the shipping provider, including:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:50 -msgid ":guilabel:`Shipping Method` (*Required field*): the name of the delivery method (e.g. `flat-rate shipping`, `same day delivery`, etc.)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:52 -msgid ":guilabel:`Provider` (*Required field*): choose the delivery service, like Fedex, if using a :ref:`third-party carrier `. Ensure the integration with the shipping carrier is properly installed and select the provider from the drop-down menu." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:56 -msgid "For more details on configuring custom shipping methods, such as :ref:`fixed price `, :ref:`based on rules `, or :ref:`pickup in store ` options, refer to their respective sections below." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:66 -msgid ":guilabel:`Delivery Product` (*Required field*): the product listed on the :ref:`sales order line ` as the delivery charge." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:71 -msgid "For examples on how to configure specific shipping methods, refer to the sections below." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:76 -msgid "Fixed price" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:78 -msgid "To configure a shipping price that is the same for all orders, go to :menuselection:`Inventory app --> Configuration --> Shipping Methods`. Then, click :guilabel:`New`, and on the shipping method form, set the :guilabel:`Provider` to the :guilabel:`Fixed Price` option. Selecting this option makes the :guilabel:`Fixed Price` field become available, which is where the fixed rate shipping amount is defined." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:84 -msgid "To enable free shipping if the amount of the order exceeds a specified amount, check the box :guilabel:`Free if order amount is above` and fill in the amount." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:88 -msgid "To set up `$20` flat-rate shipping that becomes free if the customer spends over `$100`, fill in the following fields:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:91 -msgid ":guilabel:`Shipping Method`: `Flat-rate shipping`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:92 -msgid ":guilabel:`Provider`: :guilabel:`Fixed Price`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:93 -msgid ":guilabel:`Fixed Price`: `$20.00`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:94 -msgid ":guilabel:`Free if order amount is above`: `$100.00`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:95 -msgid ":guilabel:`Delivery Product`: `[SHIP] Flat`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 -msgid "Example of filling out a shipping method." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:104 -msgid "Based on rules" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:106 -msgid "To calculate the price of shipping based on pricing rules, set the :guilabel:`Provider` field to the :guilabel:`Based on Rules` option. Optionally, adjust :guilabel:`Margin on Rate` and :guilabel:`Additional margin` to include additional shipping costs." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:111 -msgid "Create pricing rules" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:113 -msgid "Navigate to the :guilabel:`Pricing` tab and click :guilabel:`Add a line`. Doing so opens the :guilabel:`Create Pricing Rules` window, where the :guilabel:`Condition` related to the product weight, volume, price, or quantity is compared to a defined amount to calculate the :guilabel:`Delivery Cost`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:118 -msgid "Once finished, click either :guilabel:`Save & New` to add another rule, or :guilabel:`Save & Close`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:121 -msgid "To charge customers $20 in shipping for orders with five or fewer products, set the :guilabel:`Condition` to `Quantity <= 5.00`, and the :guilabel:`Delivery Cost` to `$20`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 -msgid "Display window to add a pricing rule. Set a condition and delivery cost." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:128 -msgid "To restrict shipping to specific destinations on the eCommerce website, in the shipping method form, navigate to the :guilabel:`Destination Availability` tab and define the :guilabel:`Countries`, :guilabel:`States`, and :guilabel:`Zip Prefixes`. Leave these fields empty if all locations apply." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:133 -msgid "Calculate delivery cost" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:135 -msgid "Shipping cost is the :guilabel:`Delivery cost` specified in the rule that satisfies the :guilabel:`Condition`, plus any extra charges from the :guilabel:`Margin on rate` and :guilabel:`Additional margin`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:139 -msgid "Total = Rule's~Delivery~Cost + (Margin~on~rate \\times Rule's~Delivery~Cost) + Additional~margin\n" -"\n" -"" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:143 -msgid "With the two following rules set up:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:145 -msgid "If the order contains five or fewer products, shipping is $20" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:146 -msgid "If the order contains more than five products, shipping is $50." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:148 -msgid ":guilabel:`Margin on Rate` is `10%` and :guilabel:`Additional margin` is `$9.00`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:-1 -msgid "Show example of \"Based on rules\" shipping method with margins configured." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:154 -msgid "When the first rule is applied, the delivery cost is $31 (20 + (0.1 * 20) + 9). When the second rule is applied, the delivery cost is $64 (50 + (0.1 * 50) + 9)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:160 -msgid "Pickup in store" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:162 -msgid "To configure in-store pickup, select :guilabel:`Pickup in store` in the :guilabel:`Provider` field and specify the pickup location in :guilabel:`Warehouse`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:165 -msgid "To invoice the customer for the shipping cost to the pickup location, choose the :guilabel:`Get Rate and Create Shipment` option in the :guilabel:`Integration Level` field. Then, pick either the :guilabel:`Estimated cost` or :guilabel:`Real cost` radio options in the :guilabel:`Invoicing Policy` field to decide whether the added shipping charge on the sales order is the precise cost from the shipping carrier." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:172 -msgid ":doc:`Invoice cost of shipping <../advanced_operations_shipping/invoicing>`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:177 -msgid "Add shipping" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:179 -msgid "Shipping methods can be added to sales orders in the form of delivery products, which appear as individual line items. First, navigate to the desired sales order by going to :menuselection:`Sales app --> Orders --> Orders`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:183 -msgid "On the sales order, click the :guilabel:`Add shipping` button, which opens the :guilabel:`Add a shipping method` pop-up window. Then, choose a :guilabel:`Shipping Method` from the list." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:186 -msgid "The :guilabel:`Total Order Weight` is pre-filled based on product weights (that are defined in the :guilabel:`Inventory` tab for each product form). Edit the field to specify the exact weight, and then click :guilabel:`Add` to add the shipping method." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:191 -msgid "The amount defined in :guilabel:`Total Order Weight` overwrites the total product weights defined on the product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:194 -msgid "The shipping cost is added to the *sales order line* as the :guilabel:`Delivery Product` detailed on the shipping method form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:198 -msgid "`Furniture Delivery`, a delivery product with a fixed rate of `$200`, is added to sales order `S00088`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 -msgid "Show delivery order on the sales order line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:206 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:255 -msgid "Delivery order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:208 -msgid "The shipping method added to the sales order is linked to the shipping carrier details on the delivery order. To add or change the delivery method on the delivery itself, go to the :guilabel:`Additional Info` tab and modify the :guilabel:`Carrier` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:-1 -msgid "Shipping carrier information on the delivery form." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:164 +msgid ":doc:`multipack`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:3 @@ -8305,6 +9071,424 @@ msgstr "" msgid "You need to write to xmlrequests@dhl.com along with your full Account details like account number, region, address, etc. to get API Access." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:3 +msgid "FedEx integration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:5 +msgid "Integrating a FedEx account with Odoo's **Inventory** app makes it possible to :doc:`calculate shipping rates <../setup_configuration>`, and :doc:`generate shipping labels ` within Odoo. This is accomplished by enabling the FedEx *shipping connector*, then configuring at least one *shipping method*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:11 +msgid "This documentation contains configuration details specific to FedEx integration. See the documentation on :doc:`third-party shippers ` for general shipper integration instructions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:16 +msgid "Enable shipping connector" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:18 +msgid "To enable the shipping connector for FedEx, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Scroll down to the :guilabel:`Shipping Connectors` section, and tick the checkbox next to :guilabel:`FedEx Connector`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:22 +msgid "Finally, click :guilabel:`Save` to save the changes. After doing so, a :icon:`oi-arrow-right` :guilabel:`FedEx Shipping Methods` button appears below :guilabel:`FedEx Connector`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:-1 +msgid "The FedEx Shipping Methods button below the FedEx Connector." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:30 +msgid "Configure shipping method" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:32 +msgid "Once the FedEx shipping connector is enabled, it is necessary to configure at least one shipping method. After doing so, the shipping method can be included in sales orders (SOs), and used to compute shipping costs, and print shipping labels." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:36 +msgid "To enable a shipping method, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and click the :guilabel:`FedEx Shipping Methods` button below the :guilabel:`FedEx Connector` checkbox. Doing so opens a page that shows all existing FedEx shipping methods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:41 +msgid "To see all shipping methods for every shipper with a connector enabled, navigate to :menuselection:`Inventory app --> Configuration --> Shipping Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:44 +msgid "Select a shipping method to open its form. Alternatively, click :guilabel:`New` to open a blank form, and configure a new shipping method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:-1 +msgid "The form for a FedEx shipping method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:52 +msgid "Enabling the FedEx shipping connector automatically creates two default shipping methods: :guilabel:`FedEx US` and :guilabel:`FedEx International`. Each of these methods are pre-configured with test credentials, allowing them to be used for testing purposes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:56 +msgid "Before the shipping method can be used to create actual shipments, the test credentials must be replaced with credentials from a valid FedEx account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:60 +msgid "General information" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:62 +msgid "At the very top of a shipping method form are fields used to configure the way the method operates in Odoo. In the :guilabel:`Provider` field, select :guilabel:`FedEx` from the drop-down menu, if it is not already selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:66 +msgid "The rest of the fields in this section are general to all shipping providers. For details on how to fill them out, see the documentation on :doc:`third-party shippers `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:70 +msgid "Fedex Configuration tab" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:72 +msgid "The options in the :guilabel:`Fedex Configuration` tab of a FedEx shipping method form are used to connect the method to a FedEx account, and configure the shipping details associated with the method (drop-off type, package type, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:76 +msgid "A FedEx business account is required to obtain the information needed to fill out the fields in this tab. To create a new account, navigate to FedEx's `Open Account `_ page, click on :guilabel:`Create Account`, and follow the instructions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:82 +msgid "Developer Key and Meter Number fields" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:84 +msgid "A *developer key* is used to integrate a FedEx account with an external service, like the Odoo **Inventory** app. A *meter number* is a unique ID number used by FedEx to identify negotiated shipping rates for each account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:88 +msgid "To get a developer key and meter number, begin by navigating to FedEx's `Developer Resource Center `_. Then, click on the :guilabel:`FedEx Web Services` drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:92 +msgid "Click :guilabel:`Get Test Key` to start the process of getting a developer key and meter number which can be used to configure a shipping method for testing purposes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:95 +msgid "Click :guilabel:`Get Production Key` to start the process of getting a developer key and meter number, which can be used to configure a shipping method that generates real shipments with FedEx." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:98 +msgid "After clicking either option, follow the instructions until the :guilabel:`Confirmation` screen is reached. This screen displays the developer key and meter number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:101 +msgid "Once the developer key and meter number are determined, enter them in the :guilabel:`Developer Key` and :guilabel:`Meter Number` fields on the :guilabel:`Fedex Configuration` tab of the shipping method form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:106 +msgid "Password and Account Number fields" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:108 +msgid "A *password* is used, along with a username, to log into a FedEx account. An *account number* is the unique number assigned to each FedEx account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:111 +msgid "To find a FedEx account number, log in to a FedEx account at https://www.fedex.com. Click on the account holder's name in the top-right corner of the screen, and select :menuselection:`My Profile` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:115 +msgid "On the profile page, click :guilabel:`Account Management` on the left side of the screen. The account number is displayed on this screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:118 +msgid "Once the password and account number are determined, enter them in the :guilabel:`Password` and :guilabel:`Account Number` fields on the :guilabel:`Fedex Configuration` tab of the shipping method form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:123 +msgid "Shipping details" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:125 +msgid "The main section of the :guilabel:`Fedex Configuration` tab includes a number of additional fields used provide information about the shipping method:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:128 +msgid ":guilabel:`Fedex Service Type`: The FedEx service used to ship a package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:129 +msgid ":guilabel:`Fedex Drop-Off Type`: The method for getting a package into FedEx's possession." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:130 +msgid ":guilabel:`Fedex Package Type`: The type of package used for the shipping method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:131 +msgid ":guilabel:`Package Weight Unit`: The unit of measure used to weigh packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:132 +msgid ":guilabel:`Package Length Unit`: The unit of measure used to determine the dimensions of packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:133 +msgid ":guilabel:`Label Type`: The type of shipping label used for packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:134 +msgid ":guilabel:`Label Format`: The file format used by Odoo to generate shipping labels." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:135 +msgid ":guilabel:`Commercial Invoice Type`: The dimensions and type of the paper used to print invoices." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:138 +msgid "The options that should be selected on the :guilabel:`Fedex Configuration` tab of a shipping method depend on the negotiated shipping services of the associated FedEx account. To confirm the available services for a FedEx account, visit the *Account Management* page after logging in to the FedEx website, or speak with a customer service representative." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:144 +msgid "Options section" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:146 +msgid "The :guilabel:`Options` section of the :guilabel:`Fedex Configuration` tab provides a few additional options to further configure the shipping method:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:149 +msgid ":guilabel:`Saturday Delivery`: Tick the checkbox to allow packages shipped with the delivery method to be delivered on Saturdays." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:151 +msgid ":guilabel:`Generate Return Label`: Tick the checkbox to automatically generate a return label upon validation of a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:153 +msgid ":guilabel:`Duties paid by`: Use the drop-down menu to select whether duty charges should be paid by the :guilabel:`Sender` or :guilabel:`Recipient`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:157 +msgid "Activate shipping method" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:159 +msgid "By default, shipping methods in Odoo are created within a *test environment*. This means they can only be used for testing purposes, and are unable to generate actual shipping orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:162 +msgid "To activate a shipping method in a *production environment*, click the :icon:`fa-stop` :guilabel:`Test Environment` smart button at the top of the shipping method form. After doing so, the smart buttons changes to read :icon:`fa-play` :guilabel:`Production Environment`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:166 +msgid "With the production environment enabled, validating a delivery order using the shipping method generates an actual shipping label with FedEx." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:169 +msgid "Click the :icon:`fa-play` :guilabel:`Production Environment` smart button to return the shipping method to a test environment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/fedex.rst:173 +msgid "**Do not** enable the production environment for a shipping method before it is ready to be used for actual shipping orders. Doing so may lead to the creation of unwanted charges with FedEx." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:3 +msgid "Shipping cost invoicing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:5 +msgid "Invoicing customers for shipping after delivery ensures accurate charges based on real-time shipping factors like distance, weight, and method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:8 +msgid "In Odoo, shipping costs can be invoiced in two ways:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:10 +msgid "Agree with the customer on a fixed cost and :ref:`include it in the sale order. `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:13 +msgid ":ref:`Invoice shipping costs to the customer post-delivery `, reflecting the actual expenses incurred by the business." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:19 +msgid "To set prices to delivery methods, go to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Shipping` section, enable the :guilabel:`Delivery Methods` feature. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:-1 +msgid "Enable the \"Delivery Methods\" feature in Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:30 +msgid "Next, configure the the price of each delivery method by going to :menuselection:`Inventory app --> Configuration --> Shipping Methods` and click the :guilabel:`Create` button. Doing so opens a form to provide details about the shipping provider, including:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:34 +msgid ":guilabel:`Shipping Method` (*required*) the name of the delivery method (e.g. `flat-rate shipping`, `same day delivery`, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:36 +msgid ":guilabel:`Provider` (*required*): choose the delivery service, like FedEx, if using a third-party carrier Ensure the integration with the shipping carrier is properly installed and select the provider from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:41 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:122 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:27 +msgid ":doc:`../setup_configuration/third_party_shipper`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:49 +msgid ":guilabel:`Delivery Product` (*required*): the product listed on the :ref:`sales order line ` as the delivery charge." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:57 +msgid "Invoice cost on sales order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:59 +msgid "To invoice shipping costs on the sales order, before the item is delivered, go to the :menuselection:`Sales app` and select the desired sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:62 +msgid "On the sales order, click the :guilabel:`Add Shipping` button at the bottom-right corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:-1 +msgid "Click \"Add Shipping\" button at the bottom right, near the total." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:68 +msgid "In the :guilabel:`Add a shipping method` pop-up window, choose the intended carrier in the :guilabel:`Shipping Method` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:71 +msgid "Then, click the :guilabel:`Get Rate` button to the calculate shipping price based on real-time shipping data Odoo's shipping carrier integration." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:74 +msgid "The :guilabel:`Cost` is automatically calculated using the weight of the items in the order. Finally, click the :guilabel:`Add` button to close the window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:-1 +msgid "Calculate shipping by selecting a shipping method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:83 +msgid "On the sales order, the delivery product appears in the :guilabel:`Order Lines` tab, with the :guilabel:`Unit Price` set as the shipping cost calculated in the :guilabel:`Add a shipping method` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:-1 +msgid "Show delivery product on the sales order line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:91 +msgid "Finally, after the product is delivered, click the :guilabel:`Create invoice` button, and an invoice is created that includes the shipping cost that was added earlier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:-1 +msgid "Show \"Create Invoice\" button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:98 +msgid "Then, click the :guilabel:`Create and View Invoice` button, and a draft invoice is generated, with the shipping cost included in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:-1 +msgid "Show delivery product in the invoice line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:108 +msgid "Invoice real shipping costs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:110 +msgid "To modify the invoice to reflect the real cost of shipping, follow the steps :ref:`above ` to create an invoice with a delivery product with a :guilabel:`Unit Price` of zero." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:114 +msgid "Then, on a draft invoice, modify the :guilabel:`Unit Price` to reflect the real shipping cost. Finally, invoice the customer the adjusted shipping cost by clicking :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:-1 +msgid "Show delivery product on the invoice line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:123 +msgid ":doc:`../setup_configuration/labels`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:3 +msgid "Change shipping label size" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:8 +msgid "In Odoo, there are a variety of different types of shipping labels that can be selected for delivery orders. Depending on the types of shipping packages used, different label sizes may be more appropriate, and can be configured to fit the package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:15 +msgid "In the :menuselection:`Inventory` module, go to :menuselection:`Configuration --> Delivery --> Shipping Methods.` Click on a delivery method to choose it. For the following example, *FedEx International* will be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:-1 +msgid "Different shipping methods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:23 +msgid "In the :guilabel:`Configuration` tab, under :guilabel:`Label Type`, choose one of the label types available. The availability varies depending on the carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:-1 +msgid "Select a label type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:30 +msgid "When a sales order with the corresponding shipping company is confirmed and a delivery order is validated, the shipping label will be automatically created as a PDF and appear in the :guilabel:`Chatter`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:37 +msgid "In the :menuselection:`Sales` application, click :guilabel:`Create` and select an international customer. Click :guilabel:`Add A Product` and select an item. Click :guilabel:`Add Shipping`, select a shipping method, then click :guilabel:`Get Rate`, and finally, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:-1 +msgid "Add a shipping method and rate to a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:45 +msgid "Once the quotation is confirmed by clicking :guilabel:`Confirm`, a :guilabel:`Delivery` smart button will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:-1 +msgid "Delivery order smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:52 +msgid "Once the delivery order is validated by clicking :guilabel:`Validate` in the delivery order, the shipping documents appear in the :guilabel:`Chatter`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:-1 +msgid "Shipping PDF documents." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:60 +msgid "Example labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:62 +msgid "The default :guilabel:`Label Type` is :guilabel:`Paper Letter`. An example of a FedEx letter sized label is:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:-1 +msgid "Full page letter size FedEx shipping label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:69 +msgid "For comparison, an example of a FedEx bottom-half label is:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/label_type.rst:-1 +msgid "Half page letter size FedEx shipping label." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:3 msgid "Print shipping labels" msgstr "" @@ -8446,16 +9630,504 @@ msgstr "" msgid "Sample label generated from Odoo's shipping connector with FedEx." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:163 -msgid ":doc:`../advanced_operations_shipping/invoicing`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:3 +msgid "Multi-package shipments" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels.rst:164 -msgid ":doc:`../advanced_operations_shipping/multipack`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:5 +msgid "In some cases, a delivery order with multiple items may need to be shipped in more than one package. This may be necessary if the items are too large to ship in a single package, or if certain items cannot be packaged together. Shipping a single delivery order in multiple packages provides flexibility for how each item is packaged, without the need to create multiple delivery orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:13 +msgid "In order to split a delivery order across multiple packages, the *Packages* setting must be enabled. To do so, navigate to :menuselection:`Inventory --> Configuration --> Settings`, then enable the checkbox next to :guilabel:`Packages`. Click :guilabel:`Save` to confirm the change." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:-1 +msgid "The Packages setting on the Inventory app settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:24 +msgid "Ship items in multiple packages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:26 +msgid "To split items in the same delivery order across multiple packages, begin by navigating to :menuselection:`Inventory --> Delivery Orders`, then select a delivery order that has multiple items, a multiple quantity of the same item, or both." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:30 +msgid "On the :guilabel:`Operations` tab, select the :guilabel:`⁞≣ (menu)` icon in the line of the product that will be shipped in the first package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:-1 +msgid "The menu icon for a product in a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:37 +msgid "This makes a :guilabel:`Detailed Operations` pop-up window appear. In the table at the bottom of the pop-up window, the :guilabel:`Reserved` column shows the total quantity of the product included in the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:41 +msgid "If the full quantity will be shipped in the first package, enter the number from the :guilabel:`Done` column in the :guilabel:`Reserved` column. If less than the full quantity will be shipped in the first package, enter a smaller number than the one that appears in the :guilabel:`Reserved` column. Click :guilabel:`Confirm` to confirm the :guilabel:`Done` quantities and close the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:-1 +msgid "The Detailed Operations pop-up for a product in a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:51 +msgid "Repeat the same steps for every item quantity that is included in the first package. Then, click :guilabel:`Put In Pack` to create a package with all of the selected items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:-1 +msgid "The Put In Pack button on a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:58 +msgid "For the next package, follow the same steps as detailed above, marking the quantity of each item to be included in the package as :guilabel:`Done` before clicking :guilabel:`Put In Pack` on the delivery order. Continue doing so until the full quantity of all items are added to a package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:62 +msgid "Finally, after all of the packages have been shipped, click :guilabel:`Validate` to confirm that the delivery order has been completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:66 +msgid "After one or more packages are created, a :guilabel:`Packages` smart button appears in the top-right corner of the delivery order. Click the :guilabel:`Packages` smart button to go to the :guilabel:`Packages` page for the delivery order, where each package can be selected to view all of the items included in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:0 +msgid "The Packages smart button on a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:76 +msgid "Create a backorder for items to be shipped later" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:78 +msgid "If some items will be shipped at a later date than others, there is no need to put them in a package until they are ready to be shipped. Instead, create a backorder for the items being shipped later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:81 +msgid "Begin by shipping the items that will be shipped immediately. If they will be shipped in multiple packages, follow the :ref:`steps above ` to package them as required. If they will be shipped in a single package, simply mark in the :guilabel:`Done` column the quantity of each item being shipped, but **do not** click the :guilabel:`Put In Pack` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:86 +msgid "After all quantities being shipped immediately are marked as :guilabel:`Done`, click the :guilabel:`Validate` button, and a :guilabel:`Create Backorder?` pop-up window appears. Then, click the :guilabel:`Create Backorder` button. Doing so confirms the items being shipped immediately and creates a new delivery order for the items that will be shipped later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:-1 +msgid "The Create Backorder? pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:95 +msgid "The backorder delivery order will be listed in the chatter of the original delivery order in a message that reads :guilabel:`The backorder WH/OUT/XXXXX has been created.`. Click on :guilabel:`WH/OUT/XXXXX` in the message to view the backorder delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:-1 +msgid "The backorder delivery order listed in the chatter of the original delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:103 +msgid "The backorder delivery order can also be accessed by navigating to :menuselection:`Inventory`, clicking the :guilabel:`# Back Orders` button on the :guilabel:`Delivery Orders` card, and selecting the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:-1 +msgid "The Back Orders button on the Delivery Orders card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:111 +msgid "Once the remaining items are ready to be shipped, navigate to the backorder delivery order. The items can be shipped in a single package by clicking :guilabel:`Validate` and selecting :guilabel:`Apply` on the :guilabel:`Immediate Transfer?` pop-up window that appears, or shipped in multiple packages by following the steps detailed in the section above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:116 +msgid "It is also possible to ship out some of the items while creating another backorder for the rest. To do so, simply follow the same steps used to create the first backorder." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:3 +msgid "Printable delivery PDFs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:5 +msgid "Automatically print delivery-related PDFs documents and labels in Odoo, containing package recipient details, contents, or handling instructions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:8 +msgid "The following PDFs can be configured to print upon validating an *Inventory* operation (e.g. receipt, picking, delivery orders, quality checks):" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:11 +msgid ":ref:`Delivery slip `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:12 +msgid ":ref:`Return slip `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:13 +msgid ":ref:`Product labels of items in the order `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:14 +msgid ":ref:`Lot and serial number labels `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:15 +msgid ":ref:`Carrier labels `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:16 +msgid ":ref:`Export documents `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:17 +msgid ":ref:`Package content `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:18 +msgid ":ref:`Package label `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:22 +msgid "To automatically print these forms, navigate to :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired operation type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:25 +msgid "In the :guilabel:`Hardware` tab, tick each of the desired options available in the :guilabel:`Print on Validation` section to download the PDF of those selected documents automatically after validating the :guilabel:`Operation Type`. For details on what each of the checkbox options do, jump to the related section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:-1 +msgid "Show the *Print on Validation* option in the \"Pick\" *Operation Type*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:37 +msgid "Delivery slip" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:39 +msgid "A *delivery slip* contains recipient and package details, usually placed inside (or attached to) the package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:43 +msgid ":ref:`Picking list `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:44 +msgid ":doc:`Tracking label <../setup_configuration/labels>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:46 +msgid "After :ref:`enabling the Delivery Slip setting ` in the :guilabel:`Hardware` tab configuration options, clicking :guilabel:`Validate` on the desired operation type downloads a PDF of the delivery slip." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:50 +msgid "The delivery slip shows products, quantities, the delivery order reference number, and the total order weight." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:-1 +msgid "Example delivery slip." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:60 +msgid "Return slip" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:62 +msgid "Print a *return slip* to include in a delivery for customer return packages. It identifies the return, links to the sales order, and includes item details and customer information. It can also include specific return instructions for the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:66 +msgid "After :ref:`enabling the Return Slip setting ` in the :guilabel:`Hardware` tab configuration options, clicking :guilabel:`Validate` on the desired operation type downloads a PDF of the return slip." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:70 +msgid "The return slip displays the company's return address, along with barcodes for both the order and the return operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:-1 +msgid "Example return slip." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:80 +msgid "Product labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:82 +msgid "Print *product labels* to affix to items in an order, providing essential information, such as product name, barcode, and price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:85 +msgid "After navigating to the intended operation type (:menuselection:`Inventory app --> Configuration --> Operations Types`), in the :guilabel:`Hardware` tab, tick the :guilabel:`Product Labels` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:88 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:141 +msgid "Doing so makes the :guilabel:`Print label as:` drop-down menu visible, where each product label can be printed as:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:91 +msgid ":guilabel:`2 x 7 with price`: PDF displays product name, barcode, and price, fitting two rows and seven columns of product labels per page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:0 +msgid "Example 2 x 7 with price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:100 +msgid ":guilabel:`4 x 7 with price`: displays product name, barcode, and price, fitting four rows and seven columns of product labels per page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:0 +msgid "Example 4 x 7 with price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:109 +msgid ":guilabel:`4 x 12`: displays product name and barcode. Fits four rows and twelve columns of product labels per page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:0 +msgid "Example 4 x 12." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:118 +msgid ":guilabel:`4 x 12 with price`: displays product name, barcode, and price. Fits four rows and twelve columns of product labels per page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:120 +msgid ":guilabel:`ZPL Labels`: prints labels in the Zebra Programming Language (ZPL) containing the product name and barcode. Readable for Zebra printers to automatically print labels." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:122 +msgid ":guilabel:`ZPL Labels with price`: prints labels in the :abbr:`ZPL (Zebra Programming Language)` containing the product name, barcode, and price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:126 +msgid "Product labels can be manually printed from any delivery order, by clicking the :guilabel:`Print Labels` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:132 +msgid "Lot/SN Labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:134 +msgid "Print *lot/SN labels* to affix to items in an order, providing essential information, such as product name, lot or serial number, and the barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:137 +msgid "To automatically print this PDF, navigate to the intended operation type's options page (:menuselection:`Inventory app --> Configuration --> Operations Types`). Then, in the :guilabel:`Hardware` tab, tick the :guilabel:`Lot/SN Labels` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:144 +msgid ":guilabel:`4 x 12 - One per lot/SN`: PDF with labels for unique lot/serial numbers in the order, including product name, lot/serial number, and barcode. Fits four rows and twelve columns per page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:0 +msgid "Order with only one unique set of lot/serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:154 +msgid "Labels for an order with only one unique set of lot/serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:156 +msgid ":guilabel:`4 x 12 - One per unit`: PDF with labels matching the quantity of items, displaying the product name, lot/serial number, and barcode. Fits four rows and twelve columns per page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:158 +msgid ":guilabel:`ZPL Labels - One per lot/SN`: prints labels in :abbr:`ZPL (Zebra Programming Language)`, containing the product name, lot/serial number, and barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:160 +msgid ":guilabel:`ZPL Labels - One per unit`: prints labels with the quantity of items in :abbr:`ZPL (Zebra Programming Language)`, containing the product name, lot/serial number, and barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:166 +msgid "Carrier labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:168 +msgid "To automatically print a *carrier label* with the recipient address, tracking number, and carrier details for specific third-party shipping carriers, complete the following setup:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:171 +msgid "Tick the :guilabel:`Carrier Labels` checkbox in the :ref:`operation type settings `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:173 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:258 +msgid ":doc:`Connect a printer <../../../../general/iot/devices/printer>` to Odoo's *IoT* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:174 +msgid ":ref:`Assign the carrier label to the printer `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:175 +msgid "Configure the shipping method's :ref:`label type `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:180 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:262 +msgid "Assign printer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:182 +msgid "Refer to the :doc:`Connect a printer <../../../../general/iot/devices/printer>` documentation for details on connecting a printer to Odoo's *IoT* app. Upon completion, assign the carrier label to the printer, by navigating to :menuselection:`IoT app --> Devices`, and selecting the desired printer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:-1 +msgid "Show a list of IoT devices." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:191 +msgid "In the printer configuration form, go to the :guilabel:`Printer Reports` tab to configure the types of documents the printer automatically prints. Click :guilabel:`Add a line` to open the :guilabel:`Add: Reports` pop-up window. In the :guilabel:`Search...` bar, type `Shipping`, and select :guilabel:`Shipping Labels`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:197 +msgid "The :guilabel:`Shipping Documents` report is for :ref:`export documents `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:-1 +msgid "Show carrier label report added to the *Printer Reports*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:204 +msgid "After adding the :guilabel:`Shipping Labels` report in the :guilabel:`Printer Reports` tab, ensure the :guilabel:`Report Type` matches the IoT-connected printer's type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:207 +msgid "For laser printers, set the :guilabel:`Report Type` to :guilabel:`PDF`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:208 +msgid "For Zebra printers, set the :guilabel:`Report Type` to :guilabel:`Text`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:213 +msgid "Shipping carrier label type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:215 +msgid "Next, complete the setup for the :doc:`third-party shipping connector <../setup_configuration/third_party_shipper>`. After that, go to :menuselection:`Inventory app --> Configuration --> Shipping Methods`, and select the desired shipping method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:219 +msgid "On the shipping method configuration form, in the :guilabel:`[carrier name] Configuration` tab, ensure the :guilabel:`Label Format` matches the :ref:`report type assigned earlier `:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:223 +msgid "For laser printers, set the :guilabel:`Label Format` to :guilabel:`PDF`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:224 +msgid "For Zebra printers, set the :guilabel:`Label Format` to :guilabel:`ZPL2`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:-1 +msgid "Show the *Label Type* field on FedEx's shipping method configuration page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:231 +msgid "Example carrier label" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:233 +msgid "After validating the operation, the carrier label is generated in the chatter, and printed using the IoT-connected printer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:0 +msgid "Show an example carrier label for FedEx." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:242 +msgid "Carrier label for FedEx, containing the recipient address, tracking number, barcode, and other shipping information." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:246 +msgid ":doc:`Print carrier labels <../setup_configuration/labels>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:251 +msgid "Export document" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:253 +msgid "An *export document*, required by customs to ship packages from one country to another, can be automatically printed in Odoo by following these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:256 +msgid "Tick the :guilabel:`Export Documents` checkbox in the :ref:`operation type settings `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:259 +msgid "Assign the export document to the printer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:264 +msgid "Similar to the :ref:`printer assignment instructions for carrier labels `, after connecting a compatible printer to the Odoo *IoT* app, go to :menuselection:`IoT app --> Devices`, and select the desired printer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:268 +msgid "In the printer configuration form, go to the :guilabel:`Printer Reports` tab, and click :guilabel:`Add a line`. In the :guilabel:`Add: Reports` pop-up window that appears, add the :guilabel:`Shipping Documents` report to assign the export document to the printer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:278 +msgid "Export document for a shipment from the USA to Belgium." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:283 +msgid "Package content" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:285 +msgid "A *package content* PDF includes the package's barcode, packed date, along with a list of contained products and quantities." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:288 +msgid "To print this form automatically, go to :menuselection:`Inventory app --> Configuration --> Operation Types`, and select the desired operation type. Then, go to the :guilabel:`Hardware` tab, and tick the :guilabel:`Package Contents` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:293 +msgid "If the option is not available, enable the :doc:`Packages <../../product_management/configure/package>` feature, by going to :menuselection:`Inventory app --> Configuration --> Settings`, ticking the :guilabel:`Packages` checkbox, and clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:298 +msgid "After enabling the feature in the :guilabel:`Hardware` tab, validating the operation prints a PDF of the package contents." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:0 +msgid "Package contents form showing the package contents, barcode, and pack date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:307 +msgid "Package contents showing the package contents, barcode, and pack date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:312 +msgid "Package label" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:314 +msgid "A *package label* that shows the package's barcode and pack date can be configured to print upon clicking the *Put in Pack* button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:318 +msgid "The :guilabel:`Put in Pack` button is available **only** when the :doc:`Packages <../../product_management/configure/package>` feature is enabled in :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:322 +msgid "After it is enabled, the :guilabel:`Put in Pack` button is available on all inventory operations (e.g. receipt, pickings, internal transfers, delivery orders, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:325 +msgid "To automatically print the package label when the :guilabel:`Put in Pack` button is clicked, go to :menuselection:`Inventory app --> Configuration --> Operation Types`. Select the desired operation type, and tick the :guilabel:`Package Label` checkbox in the :guilabel:`Hardware` tab. Labels can be printed in :guilabel:`PDF` or :guilabel:`ZPL` file formats, as defined in the :guilabel:`Print label as` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/print_on_validation.rst:0 +msgid "PDF of package barcode and package date." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:3 -msgid "Sendcloud configuration" +msgid "Sendcloud integration" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:5 @@ -8487,7 +10159,7 @@ msgid "Odoo integration of Sendcloud works on free Sendcloud plans *only* if a b msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:37 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:174 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:180 msgid "Warehouse configuration" msgstr "" @@ -8773,15 +10445,19 @@ msgstr "" msgid "Optionally, create shipping rules to automatically generate shipping labels tailored to different product needs. For example, a shipping rule can be created for customers shipping expensive jewelry items to purchase insurance." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:227 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:228 +msgid "Shipping rules do **not** affect :ref:`shipping rate calculations `, and are only used to improve the process of :doc:`generating shipping labels `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:232 msgid "To use shipping rules, navigate to :menuselection:`Inventory app --> Configuration --> Delivery: Shipping Methods`, and select the intended `Sendcloud` shipping method." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:230 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:235 msgid "Under the :guilabel:`Sendcloud Configuration` tab, in the :guilabel:`OPTIONS` section, choose the kind of shipments the shipping rules apply to, via the :guilabel:`Use Sendcloud shipping rules` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:234 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:239 msgid "From here, choose either: :guilabel:`Shipping` to customers, :guilabel:`Returns` from customers, or :guilabel:`Both`." msgstr "" @@ -8789,39 +10465,39 @@ msgstr "" msgid "Use Shipping Rules field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:241 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:246 msgid "Then, in the Sendcloud website, navigate to :menuselection:`Settings --> Shipping rules`. Create a new shipping rule by clicking :guilabel:`Create New`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:244 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:249 msgid "In the :guilabel:`Actions` section, set a :guilabel:`Condition` to determine when the rule applies. Then, configure what to do when packages meet the condition." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:248 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:253 msgid "`Create shipping rules on Sendcloud `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:252 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:257 msgid "FAQ" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:255 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:260 msgid "Shipment is too heavy" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:257 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:262 msgid "If the shipment is too heavy for the Sendcloud service that is configured, then the weight is split to simulate multiple packages. Products will need to be put in different :guilabel:`Packages` to :guilabel:`Validate` the transfer and generate labels." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:261 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:266 msgid ":guilabel:`Rules` can also be set up in Sendcloud to use other shipping methods when the weight is too heavy. However, note that these rules will not apply to the shipping price calculation on the calculation on the sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:266 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:271 msgid "Personal carrier contract" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:268 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:273 msgid "Use custom prices from a direct carrier contract, via CSV upload, by first logging into Sendcloud, navigating to :menuselection:`Settings --> Carriers --> My contracts`, and then selecting the intended contract." msgstr "" @@ -8829,11 +10505,11 @@ msgstr "" msgid "Navigate to the contracts section in Sendcloud." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:276 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:281 msgid "Under the :guilabel:`Contract prices` section, click :guilabel:`Download CSV` and fill out the contract prices in the :guilabel:`price` column of the CSV file template." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:280 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:285 msgid "Ensure the CSV file includes the correct prices to avoid any inaccuracies." msgstr "" @@ -8841,35 +10517,35 @@ msgstr "" msgid "Show sample contract CSV from Sendcloud, highlighting the price column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:286 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:291 msgid ":guilabel:`Upload` the completed CSV file to Sendcloud, then click :guilabel:`Save these prices`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:289 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:294 msgid "`Sendcloud: How to upload contract prices with carriers `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:293 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:298 msgid "Measuring volumetric weight" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:295 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:300 msgid "Many carriers have several measures for weight. There is the actual weight of the products in the parcel, and there is the *volumetric weight* (:dfn:`Volumetric weight is the volume that a package occupies when in transit. In other words it is the physical size of a package`)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:300 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:305 msgid "Check to see if selected carrier(s) already have defined formulas to compute the volumetric weight." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:304 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:309 msgid "`Sendcloud: How to calculate & automate parcel volumetric weight `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:308 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:313 msgid "Unable to calculate shipping rate" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:310 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:315 msgid "First, verify that the product being shipped has a weight that is supported by the selected shipping method. If this is set, then verify that the destination country (from the customer address) is supported by the carrier. The country of origin (warehouse address) should also be supported by the carrier." msgstr "" @@ -8882,7 +10558,7 @@ msgid "Starshipit is a shipping service operator that facilitates the integratio msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:11 -msgid ":doc:`Automatically calculate shipping `" +msgid ":doc:`Automatically calculate shipping <../setup_configuration>`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:12 @@ -9019,7 +10695,7 @@ msgid ":guilabel:`Delivery Product`: assign or create the delivery product that msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:127 -msgid "The fields discussed in this section are specific to configuring Starshipit. For more information about the other fields, refer to :doc:`delivery_method`." +msgid "The fields discussed in this section are specific to configuring Starshipit. For more information about the other fields, refer to :doc:`../setup_configuration`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:130 @@ -9187,7 +10863,7 @@ msgid "Third-party shipping carriers" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:10 -msgid "Users can link third-party shipping carriers to Odoo databases, in order to verify carriers' delivery to specific addresses, :doc:`automatically calculate shipping costs `, and :doc:`generate shipping labels `." +msgid "Users can link third-party shipping carriers to Odoo databases, in order to verify carriers' delivery to specific addresses, :doc:`automatically calculate shipping costs <../setup_configuration>`, and :doc:`generate shipping labels `." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:14 @@ -9241,7 +10917,7 @@ msgid ":doc:`Sendcloud `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:40 -msgid "EU" +msgid ":ref:`EU* `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:41 @@ -9268,151 +10944,155 @@ msgstr "" msgid "India" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:52 +msgid "\\* Sendcloud currently supports shipping **from** Austria, Belgium, France, Germany, Italy, the Netherlands, Spain, and the United Kingdom, and **to** any European country." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:58 msgid "To ensure proper setup of a third-party shipping carrier with Odoo, follow these steps:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:60 msgid ":ref:`Install the shipping connector `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:54 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:61 msgid ":ref:`Set up delivery method `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:55 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:62 msgid ":ref:`Activate production environment `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:56 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:63 msgid ":ref:`Configure warehouse `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:57 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:64 msgid ":ref:`Specify weight of products `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:69 msgid "Install shipping connector" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:71 msgid "To install shipping connectors, go to :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:66 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:73 msgid "Under the :guilabel:`Shipping Connectors` section, tick the third-party shipping carrier's checkbox to install it. Multiple third-party shipping connectors can be selected at once. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:71 -msgid ":doc:`Delivery methods ` can also be integrated with operations in the *Sales*, *eCommerce*, and *Website* apps. To install, refer to the :ref:`install apps and modules ` documentation." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:78 +msgid ":doc:`Delivery methods <../setup_configuration>` can also be integrated with operations in the *Sales*, *eCommerce*, and *Website* apps. To install, refer to the :ref:`install apps and modules ` documentation." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:-1 msgid "Options of available shipping connectors in Odoo." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:89 msgid "Delivery method" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:91 msgid "To configure the API credentials, and activate the shipping carrier, begin by going to :menuselection:`Inventory app --> Configuration --> Shipping Methods`, and select the desired delivery method." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:96 msgid "The list often includes **two** delivery methods from the same :guilabel:`Provider`: one for international shipping and one for domestic shipping." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:92 -msgid "Additional delivery methods can be created for specific purposes, such as :doc:`packaging <../../product_management/product_tracking/packaging>`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:96 -msgid ":doc:`Configure delivery methods `" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:99 -msgid "Ensure the delivery method is published when it should be available on the *Website* app. To publish a delivery method on the website, click the desired delivery method, then click the :guilabel:`Unpublished` smart button. Doing so changes that smart button to read: :guilabel:`Published`." +msgid "Additional delivery methods can be created for specific purposes, such as :doc:`packaging <../../product_management/configure/packaging>`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:104 -msgid "The :guilabel:`Shipping Method` page contains details about the provider, including:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:103 +msgid ":doc:`Configure delivery methods <../setup_configuration>`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:106 -msgid ":guilabel:`Shipping Method` (*Required field*): the name of the delivery method (e.g. `FedEx US`, `FedEx EU`, etc.)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:108 -msgid ":guilabel:`Website`: configure shipping methods for an *eCommerce* page that is connected to a specific website in the database. Select the applicable website from the drop-down menu, or leave it blank to apply the method to all web pages." +msgid "Ensure the delivery method is published when it should be available on the *Website* app. To publish a delivery method on the website, click the desired delivery method, then click the :guilabel:`Unpublished` smart button. Doing so changes that smart button to read: :guilabel:`Published`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:111 -msgid ":guilabel:`Provider` (*Required field*): choose the third-party delivery service, like FedEx. Upon choosing a provider, the :guilabel:`Integration Level`, :guilabel:`Invoicing Policy` and :guilabel:`Insurance Percentage` fields become available." +msgid "The :guilabel:`Shipping Method` page contains details about the provider, including:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:114 -msgid ":guilabel:`Integration Level`: choose :guilabel:`Get Rate` to simply get an :ref:`estimated shipment cost ` on an |SO| or invoice." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:113 +msgid ":guilabel:`Shipping Method` (*Required field*): the name of the delivery method (e.g. `FedEx US`, `FedEx EU`, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:115 +msgid ":guilabel:`Website`: configure shipping methods for an *eCommerce* page that is connected to a specific website in the database. Select the applicable website from the drop-down menu, or leave it blank to apply the method to all web pages." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:118 -msgid "Select :guilabel:`Get Rate and Create Shipment` to also :doc:`generate shipping labels `." +msgid ":guilabel:`Provider` (*Required field*): choose the third-party delivery service, like FedEx. Upon choosing a provider, the :guilabel:`Integration Level`, :guilabel:`Invoicing Policy` and :guilabel:`Insurance Percentage` fields become available." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:123 -msgid ":guilabel:`Delivery Product` (*Required field*): the delivery charge name that is added to the |SO| or invoice." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:121 +msgid ":guilabel:`Integration Level`: choose :guilabel:`Get Rate` to simply get an :ref:`estimated shipment cost ` on an |SO| or invoice." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:125 -msgid ":guilabel:`Invoicing Policy`: select and calculate an :guilabel:`Estimated cost` of shipping directly from the shipping carrier. If the :guilabel:`Real cost` of shipping is wanted instead, refer to this :doc:`doc about invoicing real shipping costs <../advanced_operations_shipping/invoicing>`." +msgid "Select :guilabel:`Get Rate and Create Shipment` to also :doc:`generate shipping labels `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:129 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:130 +msgid ":guilabel:`Delivery Product` (*Required field*): the delivery charge name that is added to the |SO| or invoice." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:132 +msgid ":guilabel:`Invoicing Policy`: select and calculate an :guilabel:`Estimated cost` of shipping directly from the shipping carrier. If the :guilabel:`Real cost` of shipping is wanted instead, refer to :doc:`Invoice real shipping costs ` document." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:135 msgid ":guilabel:`Margin on Rate`: specify an additional percentage amount added to the base shipping rate to cover extra costs, such as handling fees, packaging materials, exchange rates, etc." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:131 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:137 msgid ":guilabel:`Free if order amount is above`: enables free shipping for orders surpassing a specified amount entered in the corresponding :guilabel:`Amount` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:133 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:139 msgid ":guilabel:`Insurance Percentage`: specify a percentage amount of the shipping costs reimbursed to the senders if the package is lost or stolen in transit." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:140 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:146 msgid "Screenshot of a FedEx shipping method." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:140 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:146 msgid "**Shipping Method** configuration page for `FedEx US`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:142 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:148 msgid "In the :guilabel:`Configuration` tab, fill out the API credential fields (e.g. API key, password, account number, etc.). Depending on the third-party shipping carrier chosen in the :guilabel:`Provider` field, the :guilabel:`Configuration` tab will contain different required fields. For more details about configuring specific carriers' credentials, refer to the following documents:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:149 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:155 msgid ":doc:`DHL credentials `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:150 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:156 msgid ":doc:`Sendcloud credentials `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:151 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:157 msgid ":doc:`UPS credentials `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:156 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:162 msgid "Production environment" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:158 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:164 msgid "With the delivery method details configured, click the :guilabel:`Test Environment` smart button to set it to :guilabel:`Production Environment`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:162 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:168 msgid "Setting the delivery method to :guilabel:`Production` creates **real** shipping labels, and users are at risk of being charged through their carrier account (e.g. UPS, FedEx, etc.) **before** users charge customers for shipping. Verify all configurations are correct before launching the delivery method to :guilabel:`Production`." msgstr "" @@ -9420,11 +11100,11 @@ msgstr "" msgid "Show the \"Test Environment\" smart button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:176 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:182 msgid "Ensure the warehouse's :guilabel:`Address` (including ZIP code) and :guilabel:`Phone` number are entered accurately. To do that, go to :menuselection:`Inventory app --> Configuration --> Warehouses`, and select the desired warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:180 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:186 msgid "On the warehouse configuration page, open the warehouse contact page by clicking the :guilabel:`Company` field." msgstr "" @@ -9432,7 +11112,7 @@ msgstr "" msgid "Highlight the \"Company\" field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:187 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:193 msgid "Verify that the :guilabel:`Address` and :guilabel:`Phone` number are correct, as they are required for the shipping connector to work properly." msgstr "" @@ -9440,15 +11120,15 @@ msgstr "" msgid "Show company address and phone number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:197 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:203 msgid "Product weight" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:199 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:205 msgid "For the carrier integration to work properly, specify the weight of products by going to :menuselection:`Inventory app --> Products --> Products`, and selecting the desired product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:202 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:208 msgid "Then, switch to the :guilabel:`Inventory` tab, and define the :guilabel:`Weight` of the product in the :guilabel:`Logistics` section." msgstr "" @@ -9456,23 +11136,23 @@ msgstr "" msgid "Display the \"Weight\" field in the Inventory tab of the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:210 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:216 msgid "Apply third-party shipping carrier" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:212 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:218 msgid "Shipping carriers can be applied on a :abbr:`SO (Sales Order)`, invoice, or delivery order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:214 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:220 msgid "After configuring the third-party carrier's :ref:`delivery method ` in Odoo, create or navigate to a quotation by going to :menuselection:`Sales app --> Orders --> Quotations`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:221 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:227 msgid "Sales order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:223 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:229 msgid "To assign a third-party shipping carrier, and get an estimated cost of shipping, begin by going to :menuselection:`Sales app --> Orders --> Quotations`. Create or select an existing quotation, and add the cost of shipping through a third-party carrier to a quotation, by clicking the :guilabel:`Add Shipping` button in the bottom-right corner of the :guilabel:`Order Lines` tab." msgstr "" @@ -9480,35 +11160,35 @@ msgstr "" msgid "Show the \"Add shipping\" button at the bottom of a quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:232 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:238 msgid "In the resulting :guilabel:`Add a shipping method` pop-up window, select the intended carrier from the :guilabel:`Shipping Method` drop-down menu. The :guilabel:`Cost` field is automatically filled based on:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:236 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:242 msgid "the amount specified in the :guilabel:`Total Order Weight` field (if it is not provided, the sum of :ref:`product weights ` in the order is used)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:238 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:244 msgid "the distance between the warehouse's :ref:`source address ` and the customer's address." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:243 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:249 msgid "After selecting a third-party provider in the :guilabel:`Shipping Method` field, click :guilabel:`Get Rate` in the :guilabel:`Add a shipping method` pop-up window to get the estimated cost through the shipping connector. Then, click the :guilabel:`Add` button to add the delivery charge to the |SO| or invoice." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:249 -msgid ":doc:`Charge customers for shipping after product delivery <../advanced_operations_shipping/invoicing>`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:255 +msgid ":doc:`Charge customers for shipping after product delivery `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:257 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:262 msgid "For users making shipments without installing the *Sales* app, assign the shipping carrier to the delivery order, by first going to the :menuselection:`Inventory` app. Then, from the :guilabel:`Inventory Overview` dashboard, select the :guilabel:`Delivery Orders` operation type, and choose the desired delivery order that is not already marked as :guilabel:`Done` or :guilabel:`Cancelled`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:263 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:268 msgid "In the :guilabel:`Additional info` tab, set the :guilabel:`Carrier` field to the desired third-party shipping carrier. When the delivery method is set to :ref:`production mode `, a :guilabel:`Tracking Reference` is provided." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:269 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:274 msgid ":doc:`Generate shipping labels `" msgstr "" @@ -9516,39 +11196,39 @@ msgstr "" msgid "Show the delivery order's \"Additional info\" tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:278 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:283 msgid "Troubleshooting" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:280 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:285 msgid "Since shipping connectors can sometimes be complex to set up, here are some checks to try when things are not working as expected:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:283 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:288 msgid "Ensure the :ref:`warehouse information ` (e.g., address and phone number) in Odoo is correct **and** matches the records saved in the shipping provider's website." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:286 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:291 msgid "Verify that the :ref:`package type ` and parameters are valid for the shipping carrier. To check, ensure the shipment can be directly created on the shipping carrier's website." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:289 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:294 msgid "When encountering a price mismatch between Odoo's estimated cost and the provider's charge, first ensure the delivery method is set to :ref:`production environment `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:293 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:298 msgid "Then, create the shipment in both the carrier's website and Odoo, and verify the prices are the same across Odoo, the shipping provider, and in the *debug logs*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:297 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:302 msgid "When checking for a price mismatch in the debug logs, if the request says the package weighs six kilograms, but the response from FedEx says the package weights seven kilograms, it concludes that the issue is on FedEx's side." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:302 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:307 msgid "Debug log" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:304 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:309 msgid "Track shipping data inconsistencies by activating debug logging. To do that, go to the delivery method's configuration page (:menuselection:`Inventory app --> Configuration --> Shipping Method`), and select the desired shipping method. Click the :guilabel:`No Debugging` smart button to activate :guilabel:`Debug Requests`." msgstr "" @@ -9556,11 +11236,11 @@ msgstr "" msgid "Show the \"No Debug\" smart button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:313 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:318 msgid "With :guilabel:`Debug Requests` activated, each time the shipping connector is used to estimate the cost of shipping, records are saved in the :guilabel:`Logging` report. To access the report, turn on :ref:`developer mode `, and go to :menuselection:`Settings app --> Technical --> Database Structure section --> Logging`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:319 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:324 msgid "Logs are created for a shipping method each time the :ref:`Get Rate ` button is clicked on :abbr:`SOs (Sales Orders)` and invoices, **and** when a customer adds the shipping carrier to their order through the *Website* app." msgstr "" @@ -9568,7 +11248,7 @@ msgstr "" msgid "Show how to find the \"Logging\" option from the \"Technical\" menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:328 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:333 msgid "Click the *HTTP request* line item to open a detailed page, and verify the correct information is sent from Odoo to the shipping carrier. In the *HTTP response*, verify that the same information is received." msgstr "" @@ -9805,7 +11485,7 @@ msgid ":guilabel:`UPS Service Type`: Select from the drop-down menu the type of msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:183 -msgid ":guilabel:`UPS Package Type`: (*required*) Select from the drop-down menu the :doc:`package type <../../product_management/product_tracking/package>` that is supported for the shipping service." +msgid ":guilabel:`UPS Package Type`: (*required*) Select from the drop-down menu the :doc:`package type <../../product_management/configure/package>` that is supported for the shipping service." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:185 @@ -10058,1302 +11738,6 @@ msgstr "" msgid "Warehouses and storage" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:3 -msgid "Batch picking" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:7 -msgid "*Batch picking* enables a single picker to handle multiple orders at once, reducing the time needed to navigate to the same location in a warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:10 -msgid "When picking in batches, orders are grouped and consolidated into a picking list. After the picking, the batch is taken to an output location, where the products are sorted into their respective delivery packages." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:15 -msgid ":ref:`Use Barcode app for pickings `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:17 -msgid "Since orders *must* be sorted at the output location after being picked, this picking method suits businesses with a few products that are ordered often. Storing high-demand items in easily accessible locations can increase the number of orders that are fulfilled efficiently." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:24 -msgid "To activate the batch picking option, begin by going to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Operations` section, check the :guilabel:`Batch Transfers` box." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 -msgid "Enable the *Batch Transfers* in Inventory > Configuration > Settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:32 -msgid "Since batch picking is a method to optimize the *pick* operation in Odoo, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` options under the :guilabel:`Warehouse` heading must also be checked on this settings page. When finished, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:-1 -msgid "Enable *Storage Locations* and *Multi-Step Routes* Inventory > Configuration > Settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:40 -msgid "Lastly, enable the warehouse picking feature, by navigating to the warehouse settings page, which is accessible from :menuselection:`Inventory app --> Configuration --> Warehouses`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:43 -msgid "From here, select the desired warehouse from the list. Then, from the radio options available for :guilabel:`Outgoing Shipments`, select either the :guilabel:`Send goods in output and then deliver (2 steps)` or :guilabel:`Pack goods, send goods in output and then deliver (3 steps)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:48 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:128 -msgid ":ref:`Delivery in two steps `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:49 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:129 -msgid ":ref:`Delivery in three steps `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 -msgid "Set up 2-step or 3-step outgoing shipments." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:56 -msgid "Create batch transfers" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:58 -msgid "Manually create batch transfers directly from the :menuselection:`Inventory app --> Operations --> Batch Transfers` page. Click the :guilabel:`New` button to begin creating a batch transfer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:61 -msgid "On the batch transfer form, fill the following fields out accordingly:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:63 -msgid ":guilabel:`Responsible`: employee assigned to the picking. Leave this field blank if *any* worker can fulfill this picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:65 -msgid ":guilabel:`Operation Type`: from the drop-down menu, select the operation type under which the picking is categorized." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:67 -msgid ":guilabel:`Scheduled Date`: specifies the date by which the :guilabel:`Responsible` person should complete the transfer to the output location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:70 -msgid "Next, in the :guilabel:`Transfers` list, click :guilabel:`Add a line` to open the :guilabel:`Add: Transfers` window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:73 -msgid "If the :guilabel:`Operation Type` field was filled, the list will filter transfer records matching the selected :guilabel:`Operation Type`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:76 -msgid "Click the :guilabel:`New` button to create a new transfer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:78 -msgid "Once the transfer records are selected, click :guilabel:`Confirm` to confirm the batch picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:81 -msgid "A new batch transfer assigned to the :guilabel:`Responsible`, `Joel Willis`, for the `Pick` :guilabel:`Operation Type`. The :guilabel:`Scheduled Date` is set to `August 11`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 -msgid "View of *Batch Transfers* form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:88 -msgid "Clicking the :guilabel:`Add a line` button opens the :guilabel:`Add:Transfers` window, displaying only pickings. This is because the :guilabel:`Operation Type` was set to `Pick` on the batch transfer form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:92 -msgid "Click the checkbox to the left of the transfers, `WH/PICK/00001` and `WH/PICK/00002`, to include them in the new transfer. Then, click the :guilabel:`Select` button to close the :guilabel:`Add:Transfers` window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 -msgid "Select multiple transfers from the *Add:Transfers* window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:103 -msgid "Add batch from transfers list" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:105 -msgid "Another method of creating batch transfers is available using the :guilabel:`Add to batch` option in a list. Navigate to the :menuselection:`Inventory app --> Operations` drop-down menu, and select any of the :guilabel:`Transfers` to open a filtered list of transfers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 -msgid "Show all transfer types in a drop-down menu: Receipts, Deliveries, Internal Transfers,\n" -"Manufacturings, Batch Transfers, Dropships." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:114 -msgid "On the transfers list, select the checkbox to the left of the selected transfers to add in a batch. Next, navigate to the :guilabel:`Actions ⚙️ (gear)` button, and click :guilabel:`Add to batch` from the resulting drop-down menu." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 -msgid "Use *Add to batch* button, from the *Action* button's list." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:122 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:148 -msgid "Doing so opens an :guilabel:`Add to batch` pop-up window, wherein the employee :guilabel:`Responsible` for the picking can be assigned." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:125 -msgid "Choose from the two radio options to add to :guilabel:`an existing batch transfer` or create :guilabel:`a new batch transfer`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:128 -msgid "To begin with a draft, select the :guilabel:`Draft` checkbox." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:130 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:157 -msgid "Conclude the process by clicking :guilabel:`Confirm`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:-1 -msgid "Show *Add to batch* window to create a batch transfer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:137 -msgid "Process batch transfer" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:139 -msgid "Handle batch transfers in the :menuselection:`Inventory app --> Operations --> Batch Transfers` page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:142 -msgid "From here, select the intended transfer from the list. Then, on the batch transfer form, input the :guilabel:`Done` quantities for each product, under the :guilabel:`Detailed Operations` tab. Finally, select :guilabel:`Validate` to complete the picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:147 -msgid "Be certain the batch transfer is complete when the :guilabel:`Validate` button is highlighted in purple. If the :guilabel:`Check Availability` button is highlighted instead, that means there are items in the batch that are currently *not* available in-stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:154 -msgid "In a batch transfer involving products from pickings, `WH/PICK/00001` and `WH/PICK/00002`, the :guilabel:`Detailed Operations` tab shows that the product, `Cabinet with Doors`, has been picked because the :guilabel:`Done` column matches the value in the :guilabel:`Reserved` column. However, `0.00` quantities have been picked for the other product, `Cable Management Box`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 -msgid "Show batch transfer of products from two pickings in the *Detailed Operations* tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:163 -msgid "Only in-stock products are visible in the :guilabel:`Detailed Operations` tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:165 -msgid "To view the complete product list, switch to the :guilabel:`Operations` tab. On this list, the :guilabel:`Demand` column indicates the required quantity for the order. The :guilabel:`Reserved` column shows the available stock to fulfill the order. Lastly, the :guilabel:`Done` column specifies the products that have been picked, and are ready for the next step." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:171 -msgid "The product, `Desk Pad`, from the same batch as the :ref:`example above `, is only visible in the :guilabel:`Operations` tab because there are no :guilabel:`Reserved` quantities in-stock to fulfill the batch picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:175 -msgid "Click the :guilabel:`Check Availability` button to search the stock again for available products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 -msgid "Show unavailable reserved quantities in the *Operations* tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:182 -msgid "Create backorder" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:184 -msgid "On the batch transfer form, if the :guilabel:`Done` quantity of the product is *less* than the :guilabel:`Reserved` quantity, a pop-up window appears." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:187 -msgid "This pop-up window provides the option: :guilabel:`Create Backorder?`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:189 -msgid "Clicking the :guilabel:`Create Backorder` button automatically creates a new batch transfer, containing the remaining products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:192 -msgid "Click :guilabel:`No Backorder` to finish the picking *without* creating another batch picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:194 -msgid "Click :guilabel:`Discard` to cancel the validation, and return to the batch transfer form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 -msgid "Show the *Create Backorder* pop-up." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:203 -msgid "Process batch transfer: Barcode app" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:205 -msgid "Created batch transfers are also listed in the :menuselection:`Barcode` app, accessible by selecting the :guilabel:`Batch Transfers` button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:208 -msgid "By default, confirmed batch pickings appear on the :guilabel:`Batch Transfers` page. On that page, click on the desired batch transfer to open the detailed list of products for the picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:-1 -msgid "Show list of to-do batch transfers in *Barcode* app." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:215 -msgid "For the chosen batch transfer, follow the instructions at the top of the page in the black background. Begin by scanning the product's barcode to record a single product for picking. To record multiple quantities, click the :guilabel:`✏️ (pencil)` icon, and enter the required quantities for the picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:221 -msgid "Products from the same order are labeled with the same color on the left. Completed pickings are highlighted in green." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:225 -msgid "In a batch transfer for 2 `Cabinet with Doors`, 3 `Acoustic Bloc Screens`, and 4 `Four Person Desks`, the `3/3` and `4/4` :guilabel:`Units` indicate that the last two product pickings are complete." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:229 -msgid "`1/2` units of the `Cabinet with Doors` has already been picked, and after scanning the product barcode for the second cabinet, Odoo prompts the user to `Scan a serial number` to record the unique serial number for :ref:`product tracking `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 -msgid "Display products to be picked in barcode view." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:237 -msgid "Once all the products have been picked, click on :guilabel:`Validate` to mark the batch transfer as :guilabel:`Done`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:3 -msgid "Cluster picking" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:10 -msgid "Cluster picking is an advanced order fulfillment approach derived from :ref:`batch picking `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:13 -msgid "In this strategy, pickers load a cart with multiple packages, each designated for a specific *sales order* (SO). Then, the picker travels to each storage location, and places the products directly in the package of the associated order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:17 -msgid "This method is most efficient for medium-sized companies, with high order volumes, and relatively few unique products, since the method eliminates the need for sorting products into packages for customers after picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:21 -msgid "However, cluster picking does have some disadvantages. For instance, urgent orders cannot be prioritized, and optimized batches must be manually created beforehand. As a result, the picking process can lead to bottlenecks." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:28 -msgid "|SO| 1 calls for one apple and orange" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:29 -msgid "|SO| 2 calls for one apple and banana" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:30 -msgid "|SO| 3 calls for one apple, orange, and banana" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:32 -msgid "Apples are stored in Shelf A, oranges in Shelf B, and bananas in Shelf C." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:34 -msgid "To pick products for three orders at once, the cart is loaded with three empty packages." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:36 -msgid "Starting at Shelf A, the picker places apples into each package. Next, the picker navigates to Shelf B, and places oranges in the packages designated for |SO| 1 and |SO| 3. Finally, the picker pushes the cart to Shelf C, and loads packages for |SO| 2 and |SO| 3 with a banana, each." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:40 -msgid "With the packages for all three |SOS| packed, the picker pushes the cart to the output location, where the packages are sealed and prepared for shipment." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 -msgid "Show example of fulfilling sales orders 2 and 3 at once." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:50 -msgid "To enable cluster picking, begin by navigating to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Operations` heading, activate the :guilabel:`Packages` and :guilabel:`Batch Transfers` options." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:-1 -msgid "Activate *Packages* and *Batch Transfers* features in the settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:58 -msgid "Since batch picking is used to optimize the *pick* operation in Odoo, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` options, under the :guilabel:`Warehouse` heading, must also be checked on this settings page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:62 -msgid "*Storage locations* allow products to be stored in specific locations they can be picked from, while *multi-step routes* enable the picking operation itself." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:65 -msgid "When finished, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:74 -msgid "Packages setup" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:76 -msgid "After the :guilabel:`Packages` feature is enabled, navigate to :menuselection:`Inventory app --> Products --> Packages`, and click the :guilabel:`New` button to create a new package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:79 -msgid "On the new package form, the :guilabel:`Package Reference` is pre-filled with the next available `PACK` number in the system. :guilabel:`Pack Date` is automatically set to the creation date of the form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:83 -msgid "Set the :guilabel:`Package Use` field to :guilabel:`Reusable Box`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:86 -msgid ":doc:`Packages <../../product_management/product_tracking/package>`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:89 -msgid "A package intended for cluster picking is named `CLUSTER-PACK-3` for easy identification. For this workflow, the products are directly packed using their intended shipping boxes, so :guilabel:`Package Use` is set to :guilabel:`Disposable Box`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 -msgid "Create new package form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:98 -msgid "Create cluster batch" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:100 -msgid "To see how cluster picking works in Odoo, navigate to the :menuselection:`Sales` app, and create |SOS| that will be fulfilled together in the same batch. After confirming an |SO|, the :guilabel:`Delivery` smart button becomes visible. Displayed inside the icon is a number representing the amount of steps in the outgoing shipment process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:106 -msgid "Begin by creating three |SOS| for the apples, oranges, and bananas, as shown in the :ref:`example above `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:109 -msgid "After confirming the |SO|, the :guilabel:`Delivery` smart button displays the number `2`, indicating there are two operations to complete: `Pick` and `Delivery`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 -msgid "Example sales order for an apple, orange, and banana." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:116 -msgid "With the |SOS| created, orders now must be grouped into batches. To do so, navigate to the *Inventory* dashboard and select the operation type card, :guilabel:`Delivery Orders` or :guilabel:`Pick` (whichever is the first operation in the delivery flow)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:120 -msgid "Doing so displays a filtered list of outgoing operations with the :guilabel:`Ready` status, indicating that all the products in the |SO| are in stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:124 -msgid "Cluster pick batches can be created for outgoing shipments in one, two, or three steps." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:127 -msgid ":ref:`Delivery in one step `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:131 -msgid "Click the checkbox to the left of the corresponding outgoing operation to add them to the batch. With the desired pickings selected, click the :guilabel:`⚙️ Actions (gear)` button, and select the :guilabel:`Add to batch` option from the resulting drop-down menu." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:136 -msgid "To create a cluster batch, as shown in the :ref:`example above `, in a warehouse configured with two-step outgoing shipments, the following pick operations are selected:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:140 -msgid "`WH/PICK/00007`: linked to |SO| 88 for one apple and orange." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:141 -msgid "`WH/PICK/00008`: linked to |SO| 89 for one apple and banana." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:142 -msgid "`WH/PICK/00009`: linked to |SO| 90 for one apple, orange, and banana." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:151 -msgid "Choose from the two options in the :guilabel:`Add to` field to either: add to :guilabel:`an existing batch transfer`, or create :guilabel:`a new batch transfer`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:154 -msgid "To create draft batch pickings to be confirmed at a later date, select the :guilabel:`Draft` checkbox." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:164 -msgid "Process batches" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:166 -msgid "To process batches, navigate to :menuselection:`Inventory app --> Operations --> Batch Transfers`. Click on a batch to select it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:169 -msgid "In the :guilabel:`Detailed Operations` tab, products that are to be picked are grouped by location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:171 -msgid "Under the :guilabel:`Source Package` or :guilabel:`Destination Package` field, enter the package used for the picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:175 -msgid "Use the :guilabel:`Source Package` field when the picking package is configured as *reusable* on the :ref:`package form `. This means the products are temporarily placed in a container during picking, before getting transferred to their final shipping box." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:179 -msgid "Alternatively, use the :guilabel:`Destination Package` field when the product is directly placed in its *disposable* shipping box during picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:183 -msgid "Process the cluster batch for the three orders of apples, oranges, and bananas :ref:`example ` by assigning each picking to a dedicated package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:186 -msgid "At the storage location for apples, `WH/Stock/Shelf A`, assign the apples in all three pickings to one of the three disposable packages, `CLUSTER-PACK-1`, `CLUSTER-PACK-2`, or `CLUSTER-PACK-3`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:189 -msgid "Record this in Odoo using the :guilabel:`Destination Package` field in the :guilabel:`Detailed Operations` tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 -msgid "Example of processing cluster pickings in *Inventory*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:197 -msgid "In Barcode" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:199 -msgid "To process cluster pickings directly from the *Barcode* app, select the :guilabel:`Batch Transfers` button from the *Barcode* dashboard. Then, select the desired batch." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:202 -msgid "On the batch transfer screen, the products in the picking are grouped by location, and each line is color-coded to associate products in the same picking together." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:205 -msgid "Then, follow the prompt to :guilabel:`Scan the source location` barcode for the storage location of the first product. Then, scan the barcode for the product and package to process the transfer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:208 -msgid "Repeat this for all products, and click the :guilabel:`Validate` button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:211 -msgid "To find the package barcode, navigate to :menuselection:`Inventory app --> Products --> Packages`, select the desired package, click the :guilabel:`⚙️ (gear)` icon at the top of the package form, and select the :guilabel:`Print` option." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:215 -msgid "Next, select one of the three print options to generate the package barcode from the :guilabel:`Package Reference` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 -msgid "Display where the package barcode can be generated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:223 -msgid "Begin processing the cluster picking by going to the first storage location, `Shelf A`, and scanning the :ref:`location barcode `. Doing so highlights all the pickings that need products from this particular location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:227 -msgid "Scan the barcode for the apple, which highlights the picking (labeled in red) for the product `Apple`, for the picking, `WH/PICK/00007`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:230 -msgid "Then, scan the `CLUSTER-PACK-1` package barcode, and place the product in the designated package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 -msgid "Example of cluster batch from the *Barcode* app." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:237 -msgid "After creating a batch transfer and assigning a package to a picking, Odoo suggests the specified package by displaying the name *in italics* under the product name, ensuring pickers place products into the correct boxes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:3 -msgid "Organize a cross-dock in a warehouse" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:5 -msgid "Cross-docking is the process of sending products that are received directly to the customers, without making them enter the stock. The trucks are simply unloaded in a *Cross-Dock* area in order to reorganize products and load another truck." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:13 -msgid "For more information on how to organize your warehouse, read our blog: `What is cross-docking and is it for me? `_" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:20 -msgid "In the *Inventory* app, open :menuselection:`Configuration --> Settings` and activate the *Multi-Step Routes*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:27 -msgid "Doing so will also enable the *Storage Locations* feature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:29 -msgid "Now, both *Incoming* and *Outgoing* shipments should be configured to work with 2 steps. To adapt the configuration, go to :menuselection:`Inventory --> Configuration --> Warehouses` and edit your warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:36 -msgid "This modification will lead to the creation of a *Cross-Docking* route that can be found in :menuselection:`Inventory --> Configuration --> Routes`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:43 -msgid "Configure products with Cross-Dock Route" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:45 -msgid "Create the product that uses the *Cross-Dock Route* and then, in the inventory tab, select the routes *Buy* and *Cross-Dock*. Now, in the purchase tab, specify the vendor to who you buy the product and set a price for it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:55 -msgid "Once done, create a sale order for the product and confirm it. Odoo will automatically create two transfers which will be linked to the sale order. The first one is the transfer from the *Input Location* to the *Output Location*, corresponding to the move of the product in the *Cross-Dock* area. The second one is the delivery order from the *Output Location* to your *Customer Location. Both are in state *Waiting Another Operation* because we still need to order the product to our supplier." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:68 -msgid "Now, go to the *Purchase* app. There, you will find the purchase order that has been automatically triggered by the system. Validate it and receive the products in the *Input Location*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:77 -msgid "When the products have been received from the supplier, you can go back to your initial sale order and validate the internal transfer from *Input* to *Output*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:86 -msgid "The delivery order is now ready to be processed and can be validated too." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:3 -msgid "Consignment: buy and sell stock without owning it" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:5 -msgid "Most of the time, products stored in a company's warehouse are either purchased from suppliers, or are manufactured in-house. However, suppliers will sometimes let companies store and sell products in the company's warehouse, without having to buy those items up-front. This is called *consignment*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:10 -msgid "Consignment is a useful method for suppliers to launch new products, and easily deliver to their customers. It's also a great way for the company storing the products (the consignee) to earn something back for their efforts. Consignees can even charge a fee for the convenience of storing products they don't actually own." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:16 -msgid "Enable the consignment setting" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:18 -msgid "To receive, store, and sell consignment stock, the feature needs to be enabled in the settings. To do this, go to :menuselection:`Inventory --> Configuration --> Settings`, and under the :guilabel:`Traceability` section, check the box next to :guilabel:`Consignment`, and then click :guilabel:`Save` to finish." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:-1 -msgid "Enabled Consignment setting in Inventory configuration." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:28 -msgid "Receive (and store) consignment stock" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:30 -msgid "With the feature enabled in Odoo, consignment stock can now be received into a warehouse. From the main :menuselection:`Inventory` dashboard, click into the :guilabel:`Receipts` section. Then, click :guilabel:`Create`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:35 -msgid "Consignment stock is not actually purchased from the vendor; it is simply received and stored. Because of this, there are no quotations or purchase orders involved in receiving consignment stock. So, *every* receipt of consignment stock will start by creating manual receipts." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:39 -msgid "Choose a vendor to enter in the :guilabel:`Receive From` field, and then choose the same vendor to enter in the :guilabel:`Assign Owner` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:43 -msgid "Since the products received from the vendor will be owned by the same vendor, the :guilabel:`Receive From` and :guilabel:`Assign Owner` fields must match." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:46 -msgid "Once the vendor-related fields are set, enter products into the :guilabel:`Product` lines, and set the quantities to be received into the warehouse under the :guilabel:`Done` column. If the :guilabel:`Units of Measure` feature is enabled, the :abbr:`UoM (Units of Measure)` can be changed, as well. Once all the consignment stock has been received, :guilabel:`Validate` the receipt." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:-1 -msgid "Matching vendor fields in consignment Receipt creation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:56 -msgid "Sell and deliver consignment stock" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:58 -msgid "Once consignment stock has been received into the warehouse, it can be sold the same as any other in-stock product that has the :guilabel:`Can Be Sold` option enabled on the product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:61 -msgid "To create a sales order, navigate to the :menuselection:`Sales` app, and from the :guilabel:`Quotations` overview, click :guilabel:`Create`. Next, choose a customer to enter into the :guilabel:`Customer` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:66 -msgid "The :guilabel:`Customer` *must* be different from the :guilabel:`Vendor` that supplied the consignment stock received (and stored) in the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:69 -msgid "Add the consignment product under the :guilabel:`Product` column in the order lines, set the :guilabel:`Quantity`, and fill out any other pertinent product details on the form. Once the quotation is complete, click :guilabel:`Confirm`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:-1 -msgid "Sales order of consignment stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:77 -msgid "Once the :abbr:`RFQ (Request for Quotation)` has been confirmed, it will become a sales order. From here, the products can be delivered by clicking on the :guilabel:`Delivery` smart button, and selecting :guilabel:`Validate` to validate the delivery." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:82 -msgid "Traceability and reporting of consignment stock" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:84 -msgid "Although consignment stock is owned by the vendor who supplied it, and not by the company storing it in their warehouse, consignment products will *still* appear in certain inventory reports." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:87 -msgid "To find inventory reports, go to :menuselection:`Inventory --> Reporting`, and choose a report to view." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:91 -msgid "Since the consignee does not actually own consigment stock, these products are *not* reflected in the :guilabel:`Stock Valuation` report, and have no impact on the consignee's inventory valuation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:96 -msgid "Product moves report" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:98 -msgid "To view all information about on-hand stock moves, navigate to the the :guilabel:`Product Moves` dashboard by going to :menuselection:`Inventory --> Reporting --> Product Moves`. For consignment products, the information in this report is the same as any other product: the history of its product moves can be reviewed; the :guilabel:`Quantity Done` and :guilabel:`Reference` document are available; and its :guilabel:`Locations` are available, as well. The consignment stock will originate from :guilabel:`Partner Location/Vendors`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:106 -msgid "To view a consignment product's moves by ownership, select the :guilabel:`Group By` filter, choose the :guilabel:`Add Custom Group` parameter, and then select :guilabel:`From Owner`, and :guilabel:`Apply` to finish." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:-1 -msgid "Consignment stock moves history." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:115 -msgid "To see forecasted units of consignment stock, go to :menuselection:`Inventory --> Reporting --> Forecasted Inventory`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:119 -msgid "Stock on hand report" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:121 -msgid "View the :guilabel:`Stock On Hand` dashboard by navigating to :menuselection:`Inventory --> Reporting --> Inventory Report`. From this report, the :guilabel:`Locations` of all stock on-hand are displayed, in addition to the quantities per location. For consigment products, the :guilabel:`Owner` column will be populated with the owner of those products, or the original vendor who supplied the products in the first place." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:3 -msgid "Putaway rules" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:5 -msgid "Putaway is the process of routing products to appropriate storage locations upon shipment arrival." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:7 -msgid "Odoo can accomplish this seamlessly using *putaway rules*, which dictate how products move through specified warehouse locations." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:10 -msgid "Upon shipment arrival, operations are generated based on putaway rules to efficiently move products to specified locations, and ensure easy retrieval for future delivery orders." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:13 -msgid "In warehouses that process specific kinds of products, putaway rules can also prevent volatile substances from being stored in close proximity, by directing them to different locations determined by the warehouse manager." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:18 -msgid "`Odoo Tutorials: Putaway Rules `_" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:23 -msgid "To use putaway rules, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and activate the :guilabel:`Multi-Step Routes` feature under the :guilabel:`Warehouse` section. By doing so, the :guilabel:`Storage Locations` feature is also automatically activated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:27 -msgid "Finally, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:-1 -msgid "Activate Multi-Step Routes in Inventory configuration settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:36 -msgid "Define putaway rule" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:38 -msgid "To manage where specific products are routed for storage, navigate to :menuselection:`Inventory app --> Configuration --> Putaway Rules`. Use the :guilabel:`Create` button to configure a new putaway rule on a :guilabel:`Product` or :guilabel:`Product Category` that the rule affects." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:43 -msgid "Putaway rules can be defined either per product/product category, and/or package type (the *Packages* setting must be enabled in :menuselection:`Inventory app --> Configuration --> Settings` for that)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:47 -msgid "In the same line, the :guilabel:`When product arrives in` location is where the putaway rule is triggered to create an operation to move the product to the :guilabel:`Store to` location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:50 -msgid "For this to work, the :guilabel:`Store to` location must be a *sub-location* of the first (e.g., `WH/Stock/Fruits` is a specific, named location inside `WH/Stock` to make the products stored here easier to find)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:55 -msgid "In a warehouse location, **WH/Stock**, there are the following sub-locations:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:57 -msgid "WH/Stock/Fruits" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:58 -msgid "WH/Stock/Vegetables" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:60 -msgid "Ensure all apples are stored in the fruits section by filling the field :guilabel:`Store to` with the location `WH/Stock/Fruits` when the :guilabel:`Product`, `Apple` arrives in `WH/Stock`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:63 -msgid "Repeat this for all products and hit :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:0 -msgid "Create putaway rules for apples and carrots." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:70 -msgid "Putaway rule priority" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:72 -msgid "Odoo selects a putaway rule based on the following priority list (from highest to lowest) until a match is found:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:75 -msgid "Package type and product" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:76 -msgid "Package type and product category" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:79 -msgid "Product category" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:82 -msgid "The product `Lemonade can` has the following putaway rules configured:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:84 -msgid "When receiving a `Pallet` (:guilabel:`Package Type`) of `Lemonade cans`, it is redirected to `WH/Stock/Pallets/PAL1`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:86 -msgid "`Lemonade can`'s :guilabel:`Product Category` is `All/drinks`, and when receiving a `Box` of any item in this product category, items are redirected to `WH/Stock/Shelf 1`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:88 -msgid "Any product on a `Pallet` is redirected to `WH/Stock/Pallets`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:89 -msgid "The product `Lemonade can` is redirected to `WH/Stock/Shelf 2`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:90 -msgid "Items in the `All/drinks` product category are redirected to `WH/Stock/Small Refrigerator`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:0 -msgid "Some examples of putaway rules." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:99 -msgid "Storage categories" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:101 -msgid "A *storage category* is an extra location attribute. Storage categories allow the user to define the quantity of products that can be stored in the location, and how the location will be selected with putaway rules." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:108 -msgid "To enable storage categories, go to :menuselection:`Inventory app --> Configuration --> Settings`, and activate the :guilabel:`Storage Categories` feature in the :guilabel:`Warehouse` section. Then, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:113 -msgid "The :guilabel:`Storage Locations` feature **must** be enabled to enable :guilabel:`Storage Categories`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:117 -msgid "Define storage category" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:119 -msgid "To create a storage category, go to :menuselection:`Inventory app --> Configuration --> Storage Categories` and click :guilabel:`Create`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:122 -msgid "On the storage category form, type a name for the :guilabel:`Storage Category` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:124 -msgid "Options are available to limit the capacity by weight, by product, or by package type. The :guilabel:`Allow New Product` field defines when the location is considered available to store a product:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:128 -msgid ":guilabel:`If location is empty`: a product can be added there only if the location is empty." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:129 -msgid ":guilabel:`If products are the same`: a product can be added there only if the same product is already there." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:131 -msgid ":guilabel:`Allow mixed products`: several different products can be stored in this location at the same time." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:135 -msgid "Create putaway rules for pallet-stored items and ensure real-time storage capacity checks by creating the `High Frequency pallets` storage category." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:138 -msgid "Name the :guilabel:`Storage Category`, and select :guilabel:`If all products are same` in the :guilabel:`Allow New Product` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:141 -msgid "Then, define package capacity in the :guilabel:`Capacity by Package` tab, specifying the number of packages for the designated :guilabel:`Package Type` and setting a maximum of `2.00` `Pallets` for a specific location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:0 -msgid "Create a storage category on the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:149 -msgid "Once the storage category settings are saved, the storage category can be linked to a location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:151 -msgid "To do that, navigate to the location by going to :menuselection:`Inventory app --> Configuration --> Locations`, and select the location. Click :guilabel:`Edit` and select the created category in the :guilabel:`Storage Category` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:156 -msgid "Assign the `High Frequency pallets` storage category to the `WH/Stock/pallets/PAL 1` sub-location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:0 -msgid "When a Storage Category is created, it can be linked to a warehouse location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:164 -msgid "Storage categories in putaway rules" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:166 -msgid "To continue the example from above, apply the `High Frequency Pallets` on the `PAL1` and `PAL2` locations and :ref:`rework the putaway rules ` as follows:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:169 -msgid "Assume one pallet of lemonade cans is received:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:171 -msgid "If PAL1 and PAL2 are empty, the pallet will be redirected to WH/Stock/Pallets/PAL1." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:172 -msgid "If PAL1 is full, the pallet will be redirected to WH/Stock/Pallets/PAL2." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:173 -msgid "If PAL1 and 2 are full, the pallet will be redirected to WH/Stock/Pallets." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:-1 -msgid "Storage Categories used in a variety of putaway rules." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:3 -msgid "Sell stock from multiple warehouses using virtual locations" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:5 -msgid "While keeping stock and selling inventory from one warehouse might work for smaller companies, bigger companies might need to keep stock in, or sell from, multiple warehouses in multiple locations." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:9 -msgid "Sometimes products included in a single sales order might take stock from two (or more) warehouses; in Odoo, pulling products from multiple warehouses to satisfy sales demands can be done using *virtual locations*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:14 -msgid "The solution in this document, describing the use of a virtual warehouse to fulfill orders for multiple warehouses, has some limitations. Consider the following before proceeding:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:17 -msgid "When the :guilabel:`Warehouse` field is set to a virtual warehouse on a sales order, the virtual warehouse's address is indicated on the picking, packing, and delivery forms, **not** the actual warehouse's address." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:20 -msgid "Each location has a `warehouse_id` (hidden field). This means that the stock in the virtual warehouse will **not** be the sum of the stock of the real warehouses, but rather the sum of the stock in the locations whose warehouse ID is the virtual warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:25 -msgid "Potential limitation for those using :doc:`two <../../shipping_receiving/daily_operations/receipts_delivery_two_steps>` or :doc:`three-step delivery <../../shipping_receiving/daily_operations/delivery_three_steps>`:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:29 -msgid "The output or packing zone on the various forms is incorrectly listed as the virtual warehouse's address." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:31 -msgid "There is no workaround for two or three-step deliveries." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:32 -msgid "Proceed **only** if setting a virtual warehouse's address as the output or packing zone makes sense for the company's workflow." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:36 -msgid "In order to create virtual locations in warehouses, and proceed to the following steps, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` features **must** be enabled." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:39 -msgid "To do so, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Warehouse` section, and enable the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` options. Then, :guilabel:`Save` the changes to finish." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:47 -msgid "Create virtual parent location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:49 -msgid "Before creating any virtual stock locations, create a new warehouse that acts as a *virtual* warehouse — the *parent* location of other physical warehouses." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:54 -msgid "Virtual warehouses are great for companies with multiple physical warehouses. This is because a situation might arise when one warehouse runs out of stock of a particular product, but another warehouse still has stock on-hand. In this case, stock from these two (or more) warehouses could be used to fulfill a single sales order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:59 -msgid "The \"virtual\" warehouse acts as a single aggregator of all the inventory stored in a company's physical warehouses, and is used (for traceability purposes) to create a hierarchy of locations in Odoo." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:63 -msgid "To create a new warehouse, go to :menuselection:`Inventory app --> Configuration --> Warehouses`, and click :guilabel:`Create`. From here, the warehouse :guilabel:`Name` and :guilabel:`Short Name` can be changed, and other warehouse details can be changed under the :guilabel:`Warehouse Configuration` tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:68 -msgid "Lastly, click :guilabel:`Save` to finish creating a *regular* warehouse. Continue following the steps below to finish configuring the virtual parent warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:-1 -msgid "New warehouse form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:76 -msgid ":doc:`Warehouse configurations <../inventory_management/warehouses>`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:77 -msgid ":ref:`Incoming and outgoing shipments `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:78 -msgid ":doc:`Resupply from another warehouse <../inventory_management/resupply_warehouses>`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:83 -msgid "Create child warehouses" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:85 -msgid "Create at least two *child* warehouses to link to the virtual warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:88 -msgid "In order to take stock from multiple warehouses to fulfill a sales order, there needs to be at least **two** warehouses acting as child locations of the virtual parent location warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:91 -msgid "To do that, navigate to :menuselection:`Inventory app --> Configuration --> Warehouses`, click :guilabel:`Create`, and follow the :ref:`preceding instructions ` to configure the physical stock locations." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 -msgid "**Parent Warehouse**" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 -msgid ":guilabel:`Warehouse`: `Virtual Warehouse`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 -msgid ":guilabel:`Location`: `VWH/Stock`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 -msgid "**Child Warehouses**" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 -msgid ":guilabel:`Warehouses`: `Warehouse A` and `Warehouse B`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 -msgid ":guilabel:`Locations`: `WHA` and `WHB`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 -msgid "Graphic of child locations 'WHA' and 'WHB' tied to the parent location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:110 -msgid "While the virtual stock location will be changed to 'View' later, the :guilabel:`Location Type` **must** be :guilabel:`Internal Location` at this point to :ref:`link the child warehouses ` in the next section." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:117 -msgid "Link child warehouses to virtual stock" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:119 -msgid "To set physical warehouses as child locations of the virtual location configured in the :ref:`previous step `, navigate to :menuselection:`Inventory app --> Configuration --> Locations`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:123 -msgid "Remove any filters from the search bar. Then, click the physical warehouse :guilabel:`Location` that was previously created to be a child location (e.g. `WHA`), and click :guilabel:`Edit`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:126 -msgid "Change the :guilabel:`Parent Location` field from :guilabel:`Physical Locations` to the virtual warehouse's **stock location** (e.g. `VWH/Stock`) from the drop-down menu, and click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:131 -msgid "To select the virtual warehouse's stock location in the :guilabel:`Parent Location` drop-down menu, the parent warehouse stock location (e.g. `VWH/Stock`) **must** have its :guilabel:`Location Type` set to :guilabel:`Internal Location`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:-1 -msgid "Set the child warehouse's *Parent Location* to the virtual warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:139 -msgid "Repeat the preceding steps to configure two or more child warehouses." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:141 -msgid "Once complete, the virtual, parent warehouse (e.g. `VWH/Stock`) fulfills orders using stock from child warehouses (e.g. `WHA` and `WHB`), if there is insufficient stock in any one location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:145 -msgid "Set virtual stock location as 'view'" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:147 -msgid "Set the virtual stock location's :guilabel:`Location Type` to :guilabel:`View`, as it is a non-existent location used to group various physical warehouses together." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:150 -msgid "To do that, navigate to :menuselection:`Inventory app --> Configuration --> Locations`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:152 -msgid "Click the virtual warehouse's stock location (e.g. `VWH/Stock`) that was :ref:`previously created `, from the :guilabel:`Locations` list." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:155 -msgid "On the location form, under the :guilabel:`Additional Information` heading, set the :guilabel:`Location Type` to :guilabel:`View`. :guilabel:`Save` the changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:-1 -msgid "Warehouse location types in location creation screen." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:163 -msgid "To view the total quantity across **all** linked child warehouses, go to the product form and click the :guilabel:`On Hand` smart button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 -msgid "Display stock across all linked warehouses." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:171 -msgid "Example: sell products from a virtual warehouse" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:173 -msgid "To sell products from multiple warehouses using a virtual parent location, the database must have at least **two** warehouses configured — with at least **one** product, with quantity on-hand in each warehouse, respectively." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:178 -msgid "The following product, `Toy soldier`, is available at each location with the quantities:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:180 -msgid "`WHA/Stock` : 1" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:181 -msgid "`WHB/Stock` : 2" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:182 -msgid "Warehouses `WHA` and `WHB` are child warehouses of the virtual warehouse `VWH`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:184 -msgid "Create a quotation for the product by navigating to the :menuselection:`Sales` app and clicking :guilabel:`Create`. On the quote, add a :guilabel:`Customer`, and click :guilabel:`Add a product` to add the two products stored in the two warehouses." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:188 -msgid "Then, click the :guilabel:`Other Info` tab on the sales order form. Under the :guilabel:`Delivery` section, change the :guilabel:`Warehouse` field value to the virtual warehouse that was :ref:`previously created `. Next, :guilabel:`Confirm` the sales order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:-1 -msgid "Set virtual warehouse as the *Warehouse* field in sales order's *Other Info* tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:196 -msgid "Then, click the :guilabel:`Delivery` smart button. From the warehouse delivery form, confirm that the :guilabel:`Source Location` value matches the :guilabel:`Warehouse` field value from the sales order. Both should list the virtual warehouse location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:200 -msgid "Finally, on the warehouse delivery form, under the :guilabel:`Detailed Operations` tab, confirm that the :guilabel:`Locations` in the :guilabel:`From` column for each product match the child locations that are tied to the virtual parent location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:-1 -msgid "Delivery order with matching source and child locations." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:209 -msgid "The :guilabel:`Source Location` on the warehouse delivery form, and the :guilabel:`Warehouse` under the :guilabel:`Other Info` tab on the sales order, **must** match for products in the sales order to be pulled from different warehouses." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:213 -msgid "If the virtual warehouse is not in the :guilabel:`Source Location` field on the warehouse delivery form, retry product reservation by:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:216 -msgid "Running the scheduler: turn on :ref:`developer mode `, and then go to :menuselection:`Inventory app --> Operations --> Run Scheduler`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:218 -msgid "Clicking :guilabel:`Check Availability` on the delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:219 -msgid "If the virtual warehouse is **not** assigned to the :guilabel:`Warehouse` field on the sales order, then cancel it, and create a new sales order with the virtual warehouse set in the :guilabel:`Warehouse` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:222 -msgid "If the :guilabel:`Warehouse` field is missing on the sales order form, then the multiple child warehouses may not have been set up correctly. Review the :ref:`previous section ` to ensure the correct settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:227 -msgid "To use a virtual *parent* location as the default warehouse for sales orders, each salesperson should have the virtual warehouse assigned to them from the drop-down menu next to :guilabel:`Default Warehouse` on their employee form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 -msgid "Default warehouse location on employee form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:3 -msgid "Process wave transfers" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:5 -msgid "While a batch transfer is a group of several pickings, a **wave transfer** only contains some parts of different pickings. Both methods are used to pick orders in a warehouse, and depending on the situation, one method may be a better fit than the other." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:9 -msgid "To handle orders of a specific product category, or fetch products that are at the same location, wave transfers are the ideal method." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:12 -msgid "In Odoo, wave transfers are actually batch transfers with an extra step: transfers are split before being grouped in a batch." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:18 -msgid "Before a wave transfer can be created, the :guilabel:`Batch Transfers` and :guilabel:`Wave Transfers` options must be activated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:21 -msgid "First, go to :menuselection:`Inventory --> Configuration --> Settings`. In the :guilabel:`Operations` section, enable :guilabel:`Batch Transfers` and :guilabel:`Wave Transfers`. Then, click :guilabel:`Save` to apply the settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:-1 -msgid "View of Odoo Inventory app settings to enable the wave transfers option." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:30 -msgid "Add products to a wave" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:32 -msgid "Now that the settings are activated, start a wave transfer by adding products to a wave." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:34 -msgid "Wave transfers can only contain product lines from transfers of the same operation type. To view all the transfers and product lines in a specific operation, first go to the :guilabel:`Inventory` dashboard and locate the desired operation type's card. Then, open the options menu (the three dots icon in the corner of the operation type's card) and click :guilabel:`Operations`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:-1 -msgid "How to get an operation type's list of operations." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:43 -msgid "On the operations page, select the product lines you want to add in a new or existing wave. Then, click :guilabel:`Add to Wave`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:-1 -msgid "Select lines to add to the wave." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:51 -msgid "Use the :guilabel:`Filters` in the search bar to group lines with the same product, location, carrier, etc..." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:54 -msgid "After that, a pop-up box appears." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:56 -msgid "To add the selected lines to an existing wave transfer, select the :guilabel:`an existing wave transfer` option and select the existing wave transfer from the drop-down menu." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:59 -msgid "To create a new wave transfer, select the :guilabel:`a new wave transfer` option. If creating a new wave transfer, an employee can also be set in the optional :guilabel:`Responsible` field. Once the desired options are selected, click :guilabel:`Confirm` to add the product lines to a wave." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:64 -msgid "View wave transfers" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:66 -msgid "To view all wave transfers and their statuses, go to :menuselection:`Inventory --> Operations --> Wave Transfers`. Wave transfers can also be viewed in the :guilabel:`Barcode` app by going to :menuselection:`Barcode --> Batch Transfers`." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:6 msgid "Inventory management" msgstr "" @@ -11380,7 +11764,7 @@ msgid ":doc:`Warehouses ` represent a physical msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:26 -msgid "Configure :doc:`routes ` in a warehouse to control how products move to customers, from vendors, within the warehouse, or :doc:`between warehouses `." +msgid "Configure :doc:`routes <../shipping_receiving/daily_operations/use_routes>` in a warehouse to control how products move to customers, from vendors, within the warehouse, or :doc:`between warehouses `." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:31 @@ -11914,70 +12298,6 @@ msgstr "" msgid ":doc:`use_locations`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:3 -msgid "Resupply from another warehouse" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:5 -msgid "A common use case for multiple warehouses is to have one central warehouse that resupplies multiple shops, and in this case, each shop is considered a local warehouse. When a shop wants to replenish a product, the product is ordered to the central warehouse. Odoo allows the user to easily set which warehouse(s) can resupply another warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:13 -msgid "To resupply from another warehouse, first go to :menuselection:`Inventory --> Configuration --> Settings --> Warehouse` and activate :guilabel:`Multi-Step Routes`. Then, click :guilabel:`Save` to apply the setting." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:-1 -msgid "Enable Multi-Step Routes in Inventory settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:21 -msgid "View all the configured warehouses by going to :menuselection:`Inventory --> Configuration --> Warehouses`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:24 -msgid "Create a new warehouse by clicking :guilabel:`Create`. Then, give the warehouse a name and a :guilabel:`Short Name`. Finally, click :guilabel:`Save` to finish creating the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:27 -msgid "After that, go back to the :guilabel:`Warehouses` page and open the warehouse that will be resupplied by the second warehouse. Then, click :guilabel:`Edit`. In the :guilabel:`Warehouse Configuration` tab, locate the :guilabel:`Resupply From` field, and check the box next to the second warehouse's name. If the warehouse can be resupplied by more than one warehouse, make sure to check those warehouses' boxes too. Finally, click :guilabel:`Save` to apply the setting. Now, Odoo knows which warehouses can resupply this warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:-1 -msgid "Supply one warehouse with another in the Warehouse Configuration tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:39 -msgid "Set route on a product" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:41 -msgid "After configuring which warehouse(s) to resupply from, a new route is now available on all product forms. The new route appears as :guilabel:`Supply Product from [Warehouse Name]` under the :guilabel:`Inventory` tab on a product form. Use the :guilabel:`Supply Product from [Warehouse Name]` route with a reordering rule or the make to order (MTO) route to replenish stock by moving the product from one warehouse to another." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:-1 -msgid "Route setting which enables a product to resupplied from a second warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:51 -msgid "When a product's reordering rule is triggered and the product has the :guilabel:`Supply Product from [Warehouse Name]` route set, Odoo automatically creates two pickings. One picking is a *delivery order* from the second warehouse, which contains all the necessary products, and the second picking is a *receipt* with the same products for the main warehouse. The product move from the second warehouse to the main warehouse is fully tracked in Odoo." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:57 -msgid "On the picking/transfer records created by Odoo, the :guilabel:`Source Document` is the product's reordering rule. The location between the delivery order and the receipt is a transit location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:-1 -msgid "A reordering rule automatically creates two receipts for stock between warehouses." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:-1 -msgid "A warehouse order for resupplying one warehouse's stock with another." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:-1 -msgid "A receipt for stock received to one warehouse from another." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:3 msgid "Scrap inventory" msgstr "" @@ -12111,18 +12431,18 @@ msgid "To create specific storage locations, enable the *Storage Locations* feat msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:15 -msgid "Typically, the :guilabel:`Storage Locations` feature is used with :doc:`Multi-Step Routes `, which controls how products move between locations." +msgid "Typically, the :guilabel:`Storage Locations` feature is used with :doc:`Multi-Step Routes <../../shipping_receiving/daily_operations/use_routes>`, which controls how products move between locations." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:-1 msgid "Show Storage Locations feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:23 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:24 msgid "Create new location" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:25 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:26 msgid "After enabling *Storage Locations*, go to :menuselection:`Inventory app --> Configuration --> Locations`." msgstr "" @@ -12130,81 +12450,81 @@ msgstr "" msgid "List of internal locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:33 msgid "On this page, click :guilabel:`New`. The new location form can then be configured as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:34 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:35 msgid ":guilabel:`Location Name`: recognizable name of the location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:36 msgid ":guilabel:`Parent Location`: the location within which the new location exists. After the location is created, it is listed on the :guilabel:`Locations` page using a *location hierarchy*, to describe how a specific location fits within larger areas of the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:41 msgid "In `WH/Stock/Zone A/Refrigerator 1`, \"Refrigerator 1\" is the location name, \"Zone A\" is the parent location, and everything before it is the path showing where this spot is within the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:46 msgid "Additional Information section" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:48 msgid "In addition to the required fields above, configure the following location fields to ensure the location serves its intended purpose in the database:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:51 msgid ":guilabel:`Location Type`: from the drop-down menu, choose :guilabel:`Vendor Location`, :guilabel:`View`, :guilabel:`Internal Location`, :guilabel:`Customer Location`, :guilabel:`Inventory Loss`, :guilabel:`Production`, or :guilabel:`Transit Location` to categorize the location. For details on each location type, refer to the :ref:`Location Types section `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:55 -msgid ":guilabel:`Storage Category`: only available with the :ref:`Storage Categories ` feature enabled in :menuselection:`Inventory app --> Configuration --> Settings`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:58 -msgid ":guilabel:`Company`: the company the location belongs to." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:56 +msgid ":guilabel:`Storage Category`: only available with the :doc:`Storage Categories <../../shipping_receiving/daily_operations/storage_category>` feature enabled in :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:59 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:77 +msgid ":guilabel:`Company`: the company the location belongs to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:60 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:79 msgid ":guilabel:`Is a Scrap Location?`: tick this checkbox to allow for scrapped/damaged goods to be stored in this location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:61 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:79 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:81 msgid ":guilabel:`Is a Return Location?`: tick this checkbox to allow products to be returned to this location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:63 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:64 msgid ":guilabel:`Barcode`: used with the *Barcode* app, enter the barcode to :ref:`identify actions ` at this location when scanned." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:65 -msgid ":guilabel:`Replenish Location`: used for :doc:`configuring routes `, tick this checkbox to set the location as a destination for receiving products from *Buy*, *Manufacture*, or other procurement routes, ensuring products are correctly supplied to the warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:66 +msgid ":guilabel:`Replenish Location`: used for :doc:`configuring routes <../../shipping_receiving/daily_operations/use_routes>`, tick this checkbox to set the location as a destination for receiving products from *Buy*, *Manufacture*, or other procurement routes, ensuring products are correctly supplied to the warehouse." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:-1 msgid "Additional Information section of new location creation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:73 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:75 msgid "Configure the remaining fields in the :guilabel:`Additional Information` section as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:75 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:77 msgid ":guilabel:`Company`: the company whose warehouse the location is inside of. Leave this field blank if this location is shared between companies." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:83 msgid ":guilabel:`Barcode`: the barcode assigned to the location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:84 msgid ":guilabel:`Replenish Location`: tick this checkbox to get all quantities to replenish at this location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:87 msgid "In the :guilabel:`Cyclic Counting` section, change the value in the :guilabel:`Inventory Frequency (Days)` field from the default `0`, if necessary." msgstr "" @@ -12212,31 +12532,31 @@ msgstr "" msgid "Cyclic Counting section of new location creation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:94 msgid "When different than `0`, the inventory count dates for products stored at this location are automatically set at the defined frequency." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:95 -msgid "In the :guilabel:`Logistics` section, in the :guilabel:`Removal Strategy` field, click the drop-down menu and select the :doc:`removal strategy <../removal_strategies>` for how items should be removed from this location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:102 -msgid "Cyclic Counting section" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:97 +msgid "In the :guilabel:`Logistics` section, in the :guilabel:`Removal Strategy` field, click the drop-down menu and select the :doc:`removal strategy <../../shipping_receiving/removal_strategies>` for how items should be removed from this location." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:104 +msgid "Cyclic Counting section" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:106 msgid "To schedule regular inventory counts at this location, set the :guilabel:`Inventory Frequency (Days)` field to the desired interval. By default, it is set to `0` (no scheduled counts)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:107 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:109 msgid "For example, setting this field to `30`, schedules a count every thirty days. For more specifics on setting up and using this feature, refer to the :doc:`Cycle Counts documentation `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:110 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:112 msgid "The :guilabel:`Last Effective Inventory` field displays the date the last inventory count at this location occurred. When scheduled inventory counts are enabled, the :guilabel:`Next Expected Inventory` field displays the date of the next inventory count." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:117 msgid "With inventory counts scheduled to occur every `30` days, and the :guilabel:`Last Effective Inventory` count occurring on July 16, the :guilabel:`Next Expected Inventory` is August 15." msgstr "" @@ -12244,31 +12564,27 @@ msgstr "" msgid "Show Cyclic Count section of the locations form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:123 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:125 msgid "Logistics section" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:125 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:127 msgid "In the :guilabel:`Logistics` section of the locations form, optionally select a :guilabel:`Removal Strategy` to determine the order and priority of how products are picked from inventory. The options are: :guilabel:`First In First Out (FIFO)`, :guilabel:`Last In First Out (LIFO)`, :guilabel:`Closest Location`, and :guilabel:`First Expiry First Out (FEFO)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:131 -msgid ":doc:`../removal_strategies`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:134 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:136 msgid "Current stock at location" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:136 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:138 msgid "To view the current stock at a single location, go to :menuselection:`Inventory app --> Configuration --> Locations`, and select the desired location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:139 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:141 msgid "Next, click the :guilabel:`Current Stock` smart button to get a list of all products at the location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:145 msgid "A list of current stock at `Shelf 1` consists of `266` cabinets and `39` desks." msgstr "" @@ -12276,605 +12592,83 @@ msgstr "" msgid "Show stock at Shelf 1." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:5 -msgid "Routes and push/pull rules" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:7 -msgid "In inventory management, the supply chain strategy determines when products should be purchased/manufactured, delivered to distribution centers, and made available to the retail channel." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:11 -msgid "In Odoo, a product's supply chain strategy can be configured using *Routes*, which feature *Pull and Push Rules*. Once everything is properly configured, the Inventory app can automatically generate transfers following the configured push/pull rules." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:16 -msgid "Inside the warehouse" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:18 -msgid "In a generic warehouse, there are receiving docks, a quality control area, storage locations, picking and packing areas, and shipping docks. All products go through all these locations. As the products move through the locations, each location triggers the products' specified route and rules." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of a generic warehouse with stock and quality control area." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:27 -msgid "In this example, vendor trucks unload pallets of ordered products at the receiving docks. Operators then scan the products in the receiving area. Depending on the product's route and rules, some of these products are sent to a quality control area (for example, products that are components used in the manufacturing process), while others are directly stored in their respective locations." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of a generic push to rule when receiving products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:36 -msgid "Here is an example of a fulfillment route. In the morning, items are picked for all the orders that need to be prepared during the day. These items are picked from storage locations and moved to the picking area, close to where the orders are packed. Then, the orders are packed in their respective boxes, and conveyor belts bring them to the shipping docks, ready to be delivered to customers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of a generic pull from rule when preparing deliveries." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:46 -msgid "Pull rules" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:48 -msgid "With *Pull Rules*, a demand for some products triggers procurements, while *Push Rules* are triggered by products arriving in a specific location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:51 -msgid "Pull Rules are used to fulfill a sales order. Odoo generates a need at the *Customer Location* for each product in the order. Because pull rules are triggered by a need, Odoo looks for a pull rule defined on the *Customer Location*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:55 -msgid "In this case, a \"delivery order\" pull rule that transfers products from the *Shipping Area* to the *Customer Location* is found, and a transfer between the two locations is created." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:58 -msgid "Then, Odoo finds another pull rule that tries to fulfill the need for the *Shipping Area*: the \"packing\" rule that transfers products from the *Packing Area* to the *Shipping Area*. Finally, other pull rules are triggered until a transfer between the *Stock* and the *Picking Area* is created." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:64 -msgid "All these product transfers are automatically generated by Odoo based on the pull rules, starting from the end (the customer location) and going backward (the stock warehouse). While working, the operator processes these transfers in the opposite order: first the picking, then the packing, and finally the delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:70 -msgid "Push rules" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:72 -msgid "On the other hand, *Push Rules* are much easier to understand. Instead of generating documents based on needs, they are triggered in real time when products arrive in a specific location. Push rules basically say: \"when a product arrives at a specific location, move it to another location.\"" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:76 -msgid "An example of a push rule would be: when a product arrives in the *Receipt Area*, move it to the *Storage Location*. As different push rules can be applied to different products, the user can assign different storage locations for different products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:80 -msgid "Another push rule could be: when products arrive at a location, move them to the *Quality Control Area*. Then, once the quality check is done, move them to their *Storage Location*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:84 -msgid "Push rules can only be triggered if there are no pull rules that have already generated the product transfers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:88 -msgid "Sets of push/pull rules like those are called *Routes*. The grouping on the rule decides if products are grouped in the same transfer or not. For example, during the picking operation, all orders and their products are grouped in one transfer, whereas the packing operation respects the grouping per customer order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:96 -msgid "Use routes and rules" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:98 -msgid "Since *Routes* are a collection of *Push and Pull Rules*, Odoo helps you manage advanced route configurations such as:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:101 -msgid "Manage product manufacturing chains." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:102 -msgid "Manage default locations per product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:103 -msgid "Define routes within the stock warehouse according to business needs, such as quality control, after-sales services, or supplier returns." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:105 -msgid "Help rental management by generating automated return moves for rented products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:107 -msgid "To configure a route for a product, first, open the :guilabel:`Inventory` application and go to :menuselection:`Configuration --> Settings`. Then, in the :guilabel:`Warehouse` section, enable the :guilabel:`Multi-Step Routes` feature and click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "Activate the Multi-Step Routes feature in Odoo Inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:116 -msgid "The :guilabel:`Storage Locations` feature is automatically activated with the :guilabel:`Multi-Step Routes` feature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:119 -msgid "Once this first step is completed, the user can use pre-configured routes that come with Odoo, or they can create custom routes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:123 -msgid "Pre-configured routes" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:125 -msgid "To access Odoo's pre-configured routes, go to :menuselection:`Inventory --> Configuration --> Warehouses`. Then, open a warehouse form. In the :guilabel:`Warehouse Configuration` tab, the user can view the warehouse's pre-configured routes for :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "A pre-configured warehouse in Odoo Inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:134 -msgid "Some more advanced routes, such as pick-pack-ship, are also available. The user can select the route that best fits their business needs. Once the :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` routes are set, head to :menuselection:`Inventory --> Configuration --> Routes` to see the specific routes that Odoo generated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of all the preconfigured routes Odoo offers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:143 -msgid "On the :guilabel:`Routes` page, click on a route to open the route form. In the route form, the user can view which places the route is :guilabel:`Applicable On`. The user can also set the route to only apply on a specific :guilabel:`Company`. This is useful for multi-company environments; for example, a user can have a company and warehouse in Country A and a second company and warehouse in Country B." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of a route example applicable on product categories and warehouses." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:153 -msgid "At the bottom of the route form, the user can view the specific :guilabel:`Rules` for the route. Each :guilabel:`Rule` has an :guilabel:`Action`, a :guilabel:`Source Location`, and a :guilabel:`Destination Location`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "An example of rules with push & pull actions in Odoo Inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:162 -msgid "Custom Routes" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:164 -msgid "To create a custom route, go to :menuselection:`Inventory --> Configuration --> Routes`, and click on :guilabel:`Create`. Next, choose the places where this route can be selected. A route can be applicable on a combination of places." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of a pick-pack-ship route." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:172 -msgid "Each place has a different behavior, so it is important to tick only the useful ones and adapt each route accordingly. Then, configure the :guilabel:`Rules` of the route." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:175 -msgid "If the route is applicable on a product category, the route still needs to be manually set on the product category form by going to :menuselection:`Inventory --> Configuration --> Product Categories`. Then, select the product category and open the form. Next, click :guilabel:`Edit` and under the :guilabel:`Logistics` section, set the :guilabel:`Routes`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:180 -msgid "When applying the route on a product category, all the rules configured in the route are applied to **every** product in the category. This can be helpful if the business uses the dropshipping process for all the products from the same category." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of a route applied to the \"all\" product category." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:188 -msgid "The same behavior applies to the warehouses. If the route can apply to :guilabel:`Warehouses`, all the transfers occurring inside the chosen warehouse that meet the conditions of the route's rules will then follow that route." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of the warehouse drop-down menu when selecting applicable on warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:196 -msgid "If the route is applicable on :guilabel:`Sales Order Lines`, it is more or less the opposite. The route must be manually chosen when creating a quotation. This is useful if some products go through different routes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:200 -msgid "Remember to toggle the visibility of the :guilabel:`Route` column on the quotation/sales order. Then, the route can be chosen on each line of the quotation/sales order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of the menu allowing to add new lines to sales orders." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:207 -msgid "Finally, there are routes that can be applied to products. Those work more or less like the product categories: once selected, the route must be manually set on the product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:210 -msgid "To set a route on a product, go to :menuselection:`Inventory --> Products --> Products` and select the desired product. Then, go to the :guilabel:`Inventory` tab and under the :guilabel:`Operations` section, select the :guilabel:`Routes`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of a product form, where the route must be selected." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:219 -msgid "Rules must be set on the route in order for the route to work." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:222 -msgid "Rules" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:224 -msgid "The rules are defined on the route form. First, go to :menuselection:`Inventory --> Configuration --> Routes` and open the desired route form. Next, click :guilabel:`Edit` and in the :guilabel:`Rules` section, click on :guilabel:`Add a line`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of the rules menu, where it is possible to add new rules." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:232 -msgid "The available rules trigger various actions. If Odoo offers *Push* and *Pull* rules, others are also available. Each rule has an :guilabel:`Action`:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:235 -msgid ":guilabel:`Pull From`: this rule is triggered by a need for the product in a specific location. The need can come from a sales order being validated or from a manufacturing order requiring a specific component. When the need appears in the destination location, Odoo generates a picking to fulfill this need." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:239 -msgid ":guilabel:`Push To`: this rule is triggered by the arrival of some products in the defined source location. In the case of the user moving products to the source location, Odoo generates a picking to move those products to the destination location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:242 -msgid ":guilabel:`Pull & Push`: this rule allows the generation of pickings in the two situations explained above. This means that when products are required at a specific location, a transfer is created from the previous location to fulfill that need. This creates a need in the previous location and a rule is triggered to fulfill it. Once the second need is fulfilled, the products are pushed to the destination location and all the needs are fulfilled." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:247 -msgid ":guilabel:`Buy`: when products are needed at the destination location, a request for quotation is created to fulfill the need." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:249 -msgid ":guilabel:`Manufacture`: when products are needed in the source location, a manufacturing order is created to fulfill the need." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "Overview of a \"Pull From\" rule that creates a transfer between the stock and the packing\n" -"zone." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:257 -msgid "The :guilabel:`Operation Type` must also be defined on the rule. This defines which kind of picking is created from the rule." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:260 -msgid "If the rule's :guilabel:`Action` is set to :guilabel:`Pull From` or :guilabel:`Pull & Push`, a :guilabel:`Supply Method` must be set. The :guilabel:`Supply Method` defines what happens at the source location:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:264 -msgid ":guilabel:`Take From Stock`: the products are taken from the available stock of the source location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:266 -msgid ":guilabel:`Trigger Another Rule`: the system tries to find a stock rule to bring the products to the source location. The available stock is ignored." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:268 -msgid ":guilabel:`Take From Stock, if Unavailable, Trigger Another Rule`: the products are taken from the available stock of the source location. If there is no stock available, the system tries to find a rule to bring the products to the source location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:273 -msgid "Example flow" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:275 -msgid "In this example, let's use a custom *Pick - Pack - Ship* route to try a full flow with an advanced custom route." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:278 -msgid "First, a quick look at the route's rules and their supply methods. There are three rules, all :guilabel:`Pull From` rules. The :guilabel:`Supply Methods` for each rule are the following:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:281 -msgid ":guilabel:`Take From Stock`: When products are needed in the :guilabel:`WH/Packing Zone`, *picks* (internal transfers from :guilabel:`WH/Stock` to :guilabel:`WH/Packing Zone`) are created from :guilabel:`WH/Stock` to fulfill the need." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:284 -msgid ":guilabel:`Trigger Another Rule`: When products are needed in :guilabel:`WH/Output`, *packs* (internal transfers from :guilabel:`WH/Packing Zone` to :guilabel:`WH/Output`) are created from :guilabel:`WH/Packing Zone` to fulfill the need." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:287 -msgid ":guilabel:`Trigger Another Rule`: When products are needed in :guilabel:`Partner Locations/Customers`, *delivery orders* are created from :guilabel:`WH/Output` to fulfill the need." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "Overview of all the transfers created by the pick - pack - ship route." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:295 -msgid "This means that, when a customer orders products that have a *pick - pack - ship* route set on it, a delivery order is created to fulfill the order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of the operations created by a pull from transfer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:303 -msgid "If the source document for multiple tranfers is the same sales order, the status is not the same. The status will be :guilabel:`Waiting Another Operation` if the previous transfer in the list is not done yet." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of the transfers' various statuses at the beginning of the process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:311 -msgid "To prepare the delivery order, packed products are needed at the output area, so an internal transfer is requested from the packing zone." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of the detailed operations for a transfer between the packing and output zones." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:318 -msgid "Obviously, the packing zone needs products ready to be packed. So, an internal transfer is requested to the stock and employees can gather the required products from the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of the detailed operations for a transfer between the stock and packing zones." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:325 -msgid "As explained in the introduction of the documentation, the last step in the process (for this route, the delivery order) is the first to be triggered, which then triggers other rules until we reach the first step in the process (here, the internal transfer from the stock to the packing area). Now, everything is ready to be processed so the customer can get the ordered items." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:330 -msgid "In this example, the product is delivered to the customer when all the rules have been triggered and the transfers are done." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "View of the transfers' statuses when the route is completed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:3 -msgid "Transfer products between warehouses using replenishment" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:5 -msgid "For companies that use multiple warehouses, it is often necessary to transfer items between them. This is referred to as an *inter-warehouse transfer*. Odoo *Inventory* handles the administrative process of inter-warehouse transfers to ensure that inventory counts remain accurate during and after the transfer. This document will detail the method for conducting an inter-warehouse transfer using replenishment." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:12 -msgid "Configure warehouses for inter-warehouse replenishment" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:14 -msgid "First, ensure the :guilabel:`Multi-Step Routes` setting is enabled by navigating to :menuselection:`Inventory --> Configuration --> Settings`, and then check the box under the :guilabel:`Warehouse` tab. This will provide additional configuration options when creating a second warehouse that are needed for inter-warehouse replenishment." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:19 -msgid "By default, Odoo comes with a main warehouse already configured. If an additional warehouse has not already been created, do so now from the :guilabel:`Inventory` module by selecting :menuselection:`Configuration --> Warehouses --> Create`. Otherwise, select the warehouse that products will be transferred to from the :guilabel:`Warehouses` page and then click :guilabel:`Edit` to change its settings. Configure the warehouse as follows:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:25 -msgid ":guilabel:`Warehouse`: choose a name that is not already being used for another warehouse (e.g. `Alternative Warehouse`)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:27 -msgid ":guilabel:`Short Name`: choose a short name by which the warehouse will be identified (e.g. `ALT_WH`)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:30 -msgid "Click :guilabel:`Save` and the new warehouse will be created. In addition, a new :guilabel:`Resupply From` field will appear on the warehouse's form. Click :guilabel:`Edit` and then check the box next to the warehouse that will be used to resupply the warehouse that is currently being configured." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:-1 -msgid "A warehouse settings form configured to allow resupplying between warehouses." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:39 -msgid "For the purposes of this demonstration, the warehouse that products are transferred from (outgoing) will be titled \"San Francisco\", and the warehouse that products are transferred to (incoming) will be titled \"San Francisco 2\"." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:44 -msgid "Configure products for inter-warehouse replenishment" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:46 -msgid "Products must also be configured properly in order for them to be transferred between warehouses. Navigate to :menuselection:`Inventory --> Products --> Products` and select an existing product or :guilabel:`Create` a new one, if necessary." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:50 -msgid "Then, on the product form, go to the :guilabel:`Inventory` tab and enable the checkbox for :guilabel:`X: Supply Product from Y`, with *X* being the warehouse receiving the transferred products and *Y* being the warehouse that products are transferred from." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:-1 -msgid "Enable the checkbox to resupply one warehouse from another." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:59 -msgid "Replenish one warehouse from another" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:61 -msgid "Starting in the :menuselection:`Inventory` module, select :menuselection:`Products --> Products` and then choose the product that will be replenished. Click the :guilabel:`Replenish` button on the top left of the product page and fill out the pop-up form as follows:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:65 -msgid ":guilabel:`Quantity`: the number of units that will be sent to the warehouse being replenished" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:66 -msgid ":guilabel:`Scheduled Date`: the date that the replenishment is scheduled to take place" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:67 -msgid ":guilabel:`Warehouse`: the warehouse that will be replenished" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:68 -msgid ":guilabel:`Preferred Routes`: select `X: Supply Product from Y`, with *X* being the warehouse to be replenished and *Y* being the warehouse that the product will be transferred from" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:-1 -msgid "The form for replenishing a product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:75 -msgid "Click :guilabel:`Confirm` and a delivery order will be created for the outgoing warehouse along with a receipt for the warehouse that will receive the product. Depending on the configuration settings for the outgoing and incoming warehouses, processing delivery orders and receipts will require between one and three steps. This document will detail how to process one-step deliveries and receipts." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:82 -msgid "Process the delivery order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:84 -msgid "The first stage of a replenishment order is processing the delivery from the warehouse that the product is being transferred from. On the :menuselection:`Inventory` dashboard, select the :guilabel:`X to Process` button on the :guilabel:`Delivery Orders` card for the outgoing warehouse, then the delivery order created for the replenishment. On the delivery order page, click the :guilabel:`Check Availability` button in the top left to reserve the quantity of the product to be transferred. Once the delivery has been dispatched, click the :guilabel:`Validate` button to register the quantities shipped." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:-1 -msgid "The delivery orders card for the outgoing warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:97 -msgid "Process the receipt" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:99 -msgid "Once the goods arrive at the incoming warehouse, the receipt created for that warehouse must be processed as well. Return to the :menuselection:`Inventory` dashboard and select the :guilabel:`X to Process` button on the :guilabel:`Receipts` card for the incoming warehouse, then the receipt created for the replenishment. On the receipt page, click the :guilabel:`Validate` button in the top left of the page to register the quantities received." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:109 -msgid "After processing the receipt, the products transferred will now appear in the inventory of the incoming warehouse. The stock numbers for both warehouses can be viewed by returning to the product page and selecting the :guilabel:`X Units On Hand` button at the top of the screen." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:114 -msgid "Automate inter-warehouse replenishment" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:116 -msgid "Using reordering rules, it is possible to automate the process of replenishing one warehouse from another." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:119 -msgid "To get started, navigate to :menuselection:`Inventory --> Products --> Products`, and then choose the product that will be replenished. From the product page, select the :guilabel:`Reordering Rules` smart button at the top of the form, and then on the next page, click :guilabel:`Create` to configure the form as follows:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:124 -msgid ":guilabel:`Location`: the location that the reordering rule will replenish when triggered, in this case, the incoming warehouse" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:126 -msgid ":guilabel:`Min Quantity`: when the quantity on hand at the incoming warehouse falls below this number, the reordering rule will be triggered" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:128 -msgid ":guilabel:`Max Quantity`: when the reordering rule is triggered, the product will be replenished at the incoming warehouse up to this quantity" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:130 -msgid ":guilabel:`Multiple Quantity`: specify if the product should be replenished in batches of a certain quantity; for example, a product could be replenished in batches of 20" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:132 -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 "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:-1 -msgid "A fully configured reordering rule." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:139 -msgid "Finish by clicking :guilabel:`Save` and the reordering rule will be created. Now, when the scheduler runs automatically each day, a transfer will be created for each reordering rule that has been triggered." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:144 -msgid "To manually trigger reordering rules, start from the :menuselection:`Inventory` module and select :menuselection:`Operation --> Run Scheduler`, then click the green :guilabel:`Run Scheduler` button in the pop-up that appears." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:148 -msgid "After the scheduler runs, a delivery order and receipt will be created for the outgoing and incoming warehouses, respectively. Both the delivery order and receipt should be processed using the same method as detailed above." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:5 msgid "In the Odoo *Inventory* app, a *warehouse* is a physical space with an address for storing items, such as a storage facility, distribution center, or physical store." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:8 -msgid "Each database has a pre-configured warehouse with the company's address. Users can set up multiple warehouses, and :doc:`create stock moves ` between them." +msgid "Each database has a pre-configured warehouse with the company's address. Users can set up multiple warehouses, and :doc:`create stock moves <../../shipping_receiving/daily_operations/use_routes>` between them." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:14 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:15 msgid "To create or manage warehouses, go to :menuselection:`Inventory app --> Configuration --> Warehouses`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:18 msgid "Then, select an existing warehouse, or create a new one by clicking :guilabel:`New`. Doing so opens the warehouse form, which contains the following fields:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:21 msgid ":guilabel:`Warehouse` (*required field*): the full name of the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:22 msgid ":guilabel:`Short Name` (*required field*): the abbreviated code for the warehouse (maximum five characters). The short name for the default warehouse in Odoo is `WH`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:25 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:26 msgid "The :guilabel:`Short Name` appears on warehouse documents, so it is recommended to use an memorable one, like \"WH[first letters of location]\" (e.g. `WHA`, `WHB`, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:28 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:29 msgid ":guilabel:`Address` (*required field*): the address of the warehouse. To change the warehouse address when creating two or more warehouses, hover over the field, and click the :icon:`fa-arrow-right` :guilabel:`(right arrow)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:31 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:32 msgid ":guilabel:`Company` (*required field*): the company that owns the warehouse; this can be set as the company that owns the Odoo database, or the company of a customer or vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:33 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:34 msgid ":guilabel:`Intrastat region`: :doc:`region name <../../../../finance/accounting/reporting/intrastat>` required for companies in the European Union." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:39 msgid "The options below are available **only** when the *Multi-Step Routes* feature is enabled in :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:41 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:42 msgid ":guilabel:`Incoming Shipments`: select the option to receive products from the warehouse in :doc:`one <../../shipping_receiving/daily_operations/receipts_delivery_one_step>`, :doc:`two <../../shipping_receiving/daily_operations/receipts_delivery_two_steps>`, or :doc:`three <../../shipping_receiving/daily_operations/receipts_three_steps>` steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:47 msgid ":guilabel:`Outgoing Shipments`: select the option to deliver products from the warehouse in :doc:`one <../../shipping_receiving/daily_operations/receipts_delivery_one_step>`, :doc:`two <../../shipping_receiving/daily_operations/receipts_delivery_two_steps>`, or :doc:`three <../../shipping_receiving/daily_operations/delivery_three_steps>` steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:52 msgid ":guilabel:`Dropship Subcontractors`: available with the *Subcontracting* feature enabled in :menuselection:`Manufacturing app --> Configuration --> Settings`. Tick this checkbox to purchase components from vendors, and dropship them to subcontractors." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:54 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:55 msgid ":guilabel:`Resupply Subcontractors`: available with the *Subcontracting* feature, tick this checkbox to supply subcontractors with raw materials stored in *this* specific warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:56 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:57 msgid ":guilabel:`Manufacture to Resupply`: tick this checkbox to allow for items to be manufactured in this warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:58 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:59 msgid ":guilabel:`Manufacture`: choose whether to manufacture products in :doc:`one <../../../manufacturing/basic_setup/one_step_manufacturing>`, :doc:`two <../../../manufacturing/basic_setup/two_step_manufacturing>`, or :doc:`three steps <../../../manufacturing/basic_setup/three_step_manufacturing>`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:63 msgid ":guilabel:`Buy to Resupply`: tick this checkbox to allow for purchased products to be delivered to the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:65 msgid ":guilabel:`Resupply From`: available with multiple warehouses in the database, select warehouses to pull stock *from* to fulfill orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:69 msgid ":doc:`Use inventory adjustments to add stock to new warehouses `" msgstr "" @@ -13199,51 +12993,322 @@ msgstr "" msgid "Go to :menuselection:`Inventory app --> Configuration --> Product Categories` and select the desired product category. In the :guilabel:`Inventory Valuation` section, select the appropriate :guilabel:`Costing Method`:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:110 -msgid ":guilabel:`Standard Price`: 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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:113 +msgid "Standard Price" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:114 -msgid ":guilabel:`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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:115 +msgid "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 is the cost defined on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:119 -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." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:123 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:164 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:235 +msgid "Operation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:124 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:165 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:236 +msgid "Unit Cost" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:125 -msgid ":guilabel:`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 is highly sensitive to input data and human error." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:166 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:237 +msgid "Qty On Hand" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:126 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:167 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:238 +msgid "Incoming Value" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:127 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:168 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:239 +msgid "Inventory Value" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:129 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:134 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:139 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:144 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:149 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:175 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:246 +msgid "$10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:130 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:171 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:242 +msgid "0" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:132 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:170 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:173 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:241 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:244 +msgid "$0" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:133 -msgid "Changing the costing method greatly impacts inventory valuation. It is highly recommended to consult an accountant first before making any adjustments here." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:174 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:245 +msgid "Receive 8 products for $10/unit" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:135 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:176 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:247 +msgid "8" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:136 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:177 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:248 +msgid "8 * $10" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:137 -msgid ":doc:`using_inventory_valuation`" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:178 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:249 +msgid "$80" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:139 -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 generates a corresponding record in the *Inventory Valuation* report." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:138 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:179 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:250 +msgid "Receive 4 products for $16/unit" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:140 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:181 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:252 +msgid "12" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:141 +msgid "4 * $10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:142 +msgid "$120" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:184 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:255 +msgid "Deliver 10 products" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:146 -msgid "It is possible to use different valuation settings for different product categories." +msgid "-10 * $10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:147 +msgid "$20" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:148 +msgid "Receive 2 products for $9/unit" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:150 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:191 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:263 +msgid "4" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:151 +msgid "2 * $10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:152 +msgid "$40" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:154 +msgid "Average Cost (AVCO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:156 +msgid "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/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:180 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:185 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:251 +msgid "$12" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:182 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:253 +msgid "4 * $16" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:183 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:254 +msgid "$144" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:187 +msgid "-10 * $12" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:188 +msgid "$24" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:189 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:261 +msgid "Receive 2 products for $6/unit" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:190 +msgid "$9" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:192 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:264 +msgid "2 * $6" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:193 +msgid "$36" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:195 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:267 +msgid "How are unit cost and inventory value calculated at each step?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:197 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:269 +msgid "When receiving four products for $16 each:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:199 +msgid "Inventory value is calculated by adding the previous inventory value with the incoming value: :math:`$80 + (4 * $16) = $144`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:201 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:273 +msgid "Unit cost is calculated by dividing the inventory value by the quantity on-hand: :math:`$144 / 12 = $12`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:204 +msgid "When delivering ten products, the average unit cost is used to calculate the inventory value, regardless of the purchase price of the product. Therefore, inventory value is :math:`$144 + (-10 * $12) = $24`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:208 +msgid "Receive two products for $6 each:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:210 +msgid "Inventory value: :math:`$24 + (2 * $6) = $36`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:211 +msgid "Unit cost: :math:`$36 / 4 = $9`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:214 +msgid "When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, changing the numerical value in the *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 *Cost* amount is then automatically updated, based on the average purchase price of both the inventory on-hand and the costs accumulated from validated purchase orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:221 +msgid "First In First Out (FIFO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:223 +msgid "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." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:228 +msgid "This method is arguably the most accurate inventory valuation method for a variety of reasons, but it is highly sensitive to input data and human error." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:256 +msgid "$16" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:0 +msgid "-8 * $10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:0 +msgid "-2 * $16" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:260 +msgid "$32" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:262 +msgid "$11" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:265 +msgid "$44" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:271 +msgid "Inventory value is calculated by adding the previous inventory value to the incoming value: :math:`$80 + (4 * $16) = $144`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:276 +msgid "When delivering ten products, eight units were purchased for $10, and two units were purchased for $16." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:279 +msgid "First, the incoming value is calculated by multiplying the on-hand quantity by the purchased price: :math:`(-8 * $10) + (-2 * $16) = -112`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:281 +msgid "The inventory value is calculated by subtracting the incoming value from the previous inventory value: :math:`$144 - $112 = $32`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:283 +msgid "Unit cost is calculated by dividing the inventory value by the remaining quantity: :math:`$32 / 2 = $16`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:286 +msgid "When receiving two products for $6, inventory value is :math:`$32 + $12 = $44`. Unit cost is :math:`$44 / 4 = $11`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:290 +msgid "Changing the costing method greatly impacts inventory valuation. It is highly recommended to consult an accountant first before making any adjustments here." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:294 +msgid ":doc:`using_inventory_valuation`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:296 +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 generates a corresponding record in the *Inventory Valuation* report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:303 +msgid "It is possible to use different valuation settings for different product categories." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:308 msgid "Types of accounting" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:153 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:310 msgid "With automated inventory valuation set up, the generated journal entries depend on the chosen accounting mode: *Continental* or *Anglo-Saxon*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:157 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:314 msgid "Verify the accounting mode by activating the :ref:`developer-mode`, and navigating to :menuselection:`Accounting app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:160 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:317 msgid "Then, in the :guilabel:`Search...` bar, look for `Anglo-Saxon Accounting`, to see if the feature is enabled. If it is **not** enabled, *Continental* accounting mode is in use." msgstr "" @@ -13251,49 +13316,49 @@ msgstr "" msgid "Show the Anglo-Saxon accounting mode feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:167 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:324 msgid "In *Anglo-Saxon* accounting, the costs of goods sold (COGS) are reported when products are sold or delivered. This means the cost of a good is only recorded as an expense when a customer is invoiced for a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:171 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:328 msgid "So, for **manual** valuation method, set the *Expense Account* to *Stock Valuation* for the current asset type; for **automatic** valuation method, set the *Expense Account* to an *Expenses* or a *Cost of Revenue* type (e.g. *Cost of Production*, *Cost of Goods Sold*, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:175 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:332 msgid "In *Continental* accounting, the cost of a good is reported as soon as a product is received into stock. Because of this, the *Expense Account* can be set to **either** *Expenses* or a *Cost of Revenue* type, however, it is more commonly set to an *Expenses* account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:179 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:336 msgid "Refer to the :ref:`Expense ` and :ref:`Stock input/output ` sections for details on configuring each account type." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:186 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:343 msgid "Expense account" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:188 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:345 msgid "To configure the *expense account*, which is used in both manual and automatic inventory valuation, go to the :guilabel:`Account Properties` section of the intended product category (:menuselection:`Inventory app --> Configuration --> Product Categories`). Then, choose an existing account from the :guilabel:`Expense Account` drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:193 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:350 msgid "To ensure the chosen account is the correct :guilabel:`Type,` click the |right arrow| icon to the right of the account. Then, set the account type based on the information below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:198 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:266 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:355 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:423 msgid "Anglo-Saxon" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:202 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:229 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:359 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:386 msgid "Automated" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:204 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:361 msgid "In Anglo-Saxon accounting for automated inventory valuation, set the :guilabel:`Expense Account` to the `Expenses` account. Then, click the |right arrow| icon to the right of the account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:208 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:365 msgid "In the pop-up window, choose :guilabel:`Expenses` or :guilabel:`Cost of Revenue` from the :guilabel:`Type` drop-down menu." msgstr "" @@ -13301,7 +13366,13 @@ msgstr "" msgid "Show **Expense Account** field, and external link icon." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:217 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:372 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:391 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:233 +msgid "Manual" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:374 msgid "To configure the :guilabel:`Expense Account`, choose :guilabel:`Stock Valuation` from the field's drop-down menu. Verify the account's type by clicking the |right arrow| icon, and then ensure the :guilabel:`Type` is :guilabel:`Current Assets`." msgstr "" @@ -13309,49 +13380,49 @@ msgstr "" msgid "Show the **Expense Account** field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:225 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:284 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:382 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:441 msgid "Continental" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:231 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:236 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:388 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:393 msgid "Set the :guilabel:`Expense Account` to the :guilabel:`Expenses` or :guilabel:`Cost of Revenue` account type." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:242 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:399 msgid "Stock input/output (automated only)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:244 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:401 msgid "To configure the :guilabel:`Stock Input Account` and :guilabel:`Stock Output Account`, go to :menuselection:`Inventory app --> Configuration --> Product Categories` and select the desired product category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:248 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:405 msgid "In the :guilabel:`Inventory Valuation` field, select :guilabel:`Automated`. Doing so makes the :guilabel:`Account Stock Properties` section appear. These accounts are defined as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:251 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:408 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/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:253 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:410 msgid ":guilabel:`Stock Journal`: accounting journal where entries are automatically posted when a product's inventory valuation changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:255 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:412 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/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:259 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:416 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/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:268 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:425 msgid "In Anglo-Saxon accounting, the :guilabel:`Stock Input Account` and :guilabel:`Stock Output Account` are set to *different* :guilabel:`Current Assets` accounts. This way, delivering products and invoicing the customer balance the *Stock Output* account, while receiving products and billing vendors balance the *Stock Input* account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:273 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:430 msgid "To modify the account type, go to the click the |right arrow| icon to the right of the stock input/output account. In the pop-up window, choose :guilabel:`Current Assets` from the :guilabel:`Type` drop-down menu." msgstr "" @@ -13359,15 +13430,15 @@ msgstr "" msgid "Display account setup page, highlighting the **Type** field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:281 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:438 msgid "The *Stock Input* account is set to `Stock Interim (Received)`, a *Current Asset* account type." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:286 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:443 msgid "In Continental accounting, the :guilabel:`Stock Input Account` and :guilabel:`Stock Output Account` are set to **the same** :guilabel:`Current Assets` account. That way, one account can be balanced when items are bought and sold." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:291 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:448 msgid "The stock input and output accounts are both set to `Stock Interim (Received)`, a :guilabel:`Current Assets` account type. They can also be set to the `Stock Interim (Delivered)`, as long as the input and output accounts are assigned to the **same** account." msgstr "" @@ -13375,23 +13446,23 @@ msgstr "" msgid "Show the Stock Input and Output accounts." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:301 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:458 msgid "Inventory valuation reporting" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:303 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:460 msgid "To start, go to :menuselection:`Accounting app --> Reporting --> Balance Sheet`. Click the :guilabel:`Current Assets` line item to unfold the drop-down menu, and look for the nested :guilabel:`Stock Valuation`, :guilabel:`Stock Interim (Received)`, and :guilabel:`Stock Interim (Delivered)` lines." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:309 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:466 msgid "At the top of the dashboard, click the :guilabel:`As of [date]` button to display accounting records up to a specified date." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:313 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:470 msgid ":ref:`Stock accounts and what they do `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:314 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:471 msgid ":doc:`../../../../finance/accounting/get_started/cheat_sheet`" msgstr "" @@ -13399,11 +13470,11 @@ msgstr "" msgid "See the full inventory valuation breakdown in Odoo Accounting app." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:320 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:477 msgid "Access more specific information by clicking the :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` icon to the right of the desired journal. Select :guilabel:`General Ledger` to see a list of all of the journal entries, where each line item's :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` icon can be clicked to reveal the :guilabel:`View Journal Entry` option to open the individualized journal entry." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:326 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:483 msgid "Additionally, annotations to the :guilabel:`Balance Sheet` can be added by choosing :guilabel:`Annotate`, filling in the text box, and clicking :guilabel:`Save`." msgstr "" @@ -13464,7 +13535,7 @@ msgid ":ref:`Developer mode ` **must** be turned on to see the : msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:60 -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." +msgid "The :doc:`consignment <../../shipping_receiving/daily_operations/owned_stock>` 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/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:-1 @@ -13575,767 +13646,1398 @@ msgstr "" msgid "`Odoo Tutorial: Inventory Valuation `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:6 -msgid "Removal strategies" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:13 +msgid "In Odoo, there are two strategies for automatically replenishing inventory: *reordering rules* and the *make to order (MTO)* route. Although these strategies differ slightly, they both have similar consequences: triggering the automatic creation of a |PO| or |MO|. The choice of which strategy to use depends on the business's manufacturing and delivery processes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:8 -msgid "For companies with warehouses, *removal strategies* determine **which** products are taken from the warehouse, and **when**. For example, for perishable products, prioritizing the picking of goods with the nearest expiration date helps minimize food spoilage." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:19 +msgid "Terminology" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:12 -msgid "The following columns in the table below list the removal strategies available in Odoo, and detail how pickings are determined along with the picking order. Leverage these removal strategies to have Odoo automatically select how products are selected for orders:" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:59 +msgid "Replenishment report and reordering rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:21 -msgid ":doc:`FIFO `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:24 +msgid "The replenishment report is a list of all products that have a negative forecast quantity." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:22 -msgid ":doc:`LIFO `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:26 +msgid "*Reordering rules* are used to ensure there's always a minimum amount of a product in-stock, in order to manufacture products and/or fulfill sales orders. When the stock level of a product reaches its minimum, Odoo automatically generates a purchase order with the quantity needed to reach the maximum stock level." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:23 -msgid ":doc:`FEFO `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:31 +msgid "Reordering rules can be created and managed in the replenishment report, or from the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:24 -msgid ":doc:`Closest Location `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:36 +msgid "Make to order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:25 -msgid ":doc:`Least Packages `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:38 +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/warehouses_storage/removal_strategies.rst:26 -msgid "Based on" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:41 +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/warehouses_storage/removal_strategies.rst:27 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:28 -msgid ":ref:`Incoming date `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:44 +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/warehouses_storage/removal_strategies.rst:29 -msgid ":ref:`Removal date `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:48 +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/warehouses_storage/removal_strategies.rst:30 -msgid ":ref:`Location sequence `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:51 +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/warehouses_storage/removal_strategies.rst:31 -msgid ":ref:`Package quantity `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:61 +msgid "To access the replenishment report, go to :menuselection:`Inventory app --> Operations --> Replenishment.`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:32 -msgid "Selection order" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:64 +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/warehouses_storage/removal_strategies.rst:33 -msgid "First in" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:69 +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/warehouses_storage/removal_strategies.rst:34 -msgid "Last in" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:75 +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/warehouses_storage/removal_strategies.rst:35 -msgid ":ref:`First to expire `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:81 +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 "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:36 -msgid ":ref:`Alphanumeric name of location `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:-1 +msgid "Replenishment report listing all items needing to be purchased to meet current needs." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:37 -msgid "Quantity closest to fulfilling demand" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:90 +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/warehouses_storage/removal_strategies.rst:39 -msgid "For comprehensive examples for how to use each removal strategy, refer to each individual documentation page." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:96 +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/warehouses_storage/removal_strategies.rst:47 -msgid "Removal strategies are set on either the product category or storage location." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:101 +msgid "Replenishment report fields" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:-1 -msgid "Change the Force Removal Strategy for either the Product Categories or Locations." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:103 +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/warehouses_storage/removal_strategies.rst:53 -msgid "Configure removal strategies on the location by going to :menuselection:`Inventory --> Configuration --> Locations`, and selecting the desired location. On the location form, choose a removal strategy from the :guilabel:`Removal Strategy` field's drop-down menu options." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:107 +msgid ":guilabel:`Product`: the product that requires a replenishment." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:58 -msgid "To set a removal strategy on a location, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` settings **must** be enabled in :menuselection:`Inventory --> Configuration --> Settings`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:108 +msgid ":guilabel:`Location`: the specific location where the product is stored." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:62 -msgid "These features are **only** necessary when setting the removal strategy on a location." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:109 +msgid ":guilabel:`Warehouse`: the warehouse where the product is stored." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:64 -msgid "Configure removal strategies on product categories by going to :menuselection:`Inventory --> Configuration --> Product Categories` and selecting the intended product category. Next, choose a removal strategy from the :guilabel:`Force Removal Strategy` drop-down menu options." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:110 +msgid ":guilabel:`On Hand`: the amount of product currently available." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:69 -msgid "When there are different removal strategies applied on both the location and product category for a product, the value set on the :guilabel:`Force Removal Strategy` field set on a :guilabel:`Product Category` form is applied as top priority." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:111 +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/warehouses_storage/removal_strategies.rst:74 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:94 -msgid "Required features" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:113 +msgid ":guilabel:`Preferred Route`: how the product is procured, either :guilabel:`Buy`, :guilabel:`Manufactured`, :guilabel:`Dropship`, etc." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:76 -msgid "While some removal strategies are available by default, some additional features **must** be enabled in :menuselection:`Inventory --> Configuration --> Settings` for the removal strategy option to appear in the drop-down menu of the :guilabel:`Force Removal Strategy` or :guilabel:`Removal Strategy` field." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:115 +msgid ":guilabel:`Vendor`: the company from which the product is acquired." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:81 -msgid "Refer to the table below for a summary of required features. Otherwise, refer to the dedicated sections for the removal strategy for more details on requirements and usage." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:116 +msgid ":guilabel:`Bill of Materials`: the bill of materials for the product (if one is configured)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:89 -msgid "FIFO" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:117 +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/warehouses_storage/removal_strategies.rst:90 -msgid "LIFO" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:120 +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/warehouses_storage/removal_strategies.rst:91 -msgid "FEFO" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:122 +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/warehouses_storage/removal_strategies.rst:92 -msgid "Closest Location" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:124 +msgid ":guilabel:`Max Quantity`: the amount of product that should be available after replenishing the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:93 -msgid "Least Packages" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:126 +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/warehouses_storage/removal_strategies.rst:95 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:96 -msgid "Lots & Serial Numbers" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:129 +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/warehouses_storage/removal_strategies.rst:97 -msgid "Lots & Serial Numbers, Expiration Date" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:131 +msgid ":guilabel:`UoM`: the unit of measure used to acquire the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:98 -msgid "Storage Locations, Multi-Step Routes" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:132 +msgid ":guilabel:`Company`: the company for which the product is acquired." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:104 -msgid "Lots and serial numbers" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:134 +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. To replenish a product manually, click :guilabel:`Order Once`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:106 -msgid "Lots and serial numbers differentiate identical products and track information like arrival or expiration dates. To enable this feature, navigate to :menuselection:`Inventory --> Configuration --> Settings`. Under the :guilabel:`Traceability` heading, check the box beside :guilabel:`Lots & Serial Numbers` to enable the feature." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:138 +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/warehouses_storage/removal_strategies.rst:115 -msgid "Next, ensure the intended product is tracked by lots or serial numbers by navigating to the product form through :menuselection:`Inventory --> Products --> Products`, and selecting the desired product. On the product form, switch to the :guilabel:`Inventory` tab, and under the :guilabel:`Tracking` field, select either the :guilabel:`By Unique Serial Number` or :guilabel:`By Lots` options." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:141 +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/warehouses_storage/removal_strategies.rst:121 -msgid "After enabling the features, assign lot or serial numbers to products using an :doc:`inventory adjustment ` or during :ref:`product reception `." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:144 +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 "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:126 -msgid "Locations and routes" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:-1 +msgid "Snooze options to turn off notifications for reordering for a period of time." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:128 -msgid "**Storage locations** and **multi-step routes** are necessary features for setting **all** types of removal strategies on a location. However, these features are specifically required for the closest location removal strategy since it is only applied at the location level." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:152 +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 "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:132 -msgid "To activate these features, navigate to :menuselection:`Inventory --> Configuration --> Settings`. Under the :guilabel:`Warehouse` heading, enable the :guilabel:`Storage Location` and :guilabel:`Multi-Step Routes` features." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:-1 +msgid "Quote request list shows which quotes are directly from the replenishment report." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:-1 -msgid "Enable the locations and route features." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:161 +msgid "Make to order (MTO) route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:143 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:97 -msgid "Expiration date" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:163 +msgid "Since the |MTO| route is recommended for customized products, the route is hidden by default." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:145 -msgid "Enable the **expiration date** feature to track expiration dates, best before dates, removal dates, and alert dates on a lot or serial number by navigating to :menuselection:`Inventory --> Configuration --> Settings`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:172 +msgid "To activate the |MTO| route in Odoo:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:149 -msgid "Under the :guilabel:`Traceability` heading, ensure the :guilabel:`Lots & Serial Numbers` feature is selected, and then select the check box for :guilabel:`Expiration Dates` to enable the feature." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:166 +msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:-1 -msgid "Enable expiration dates feature for FEFO." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:167 +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/warehouses_storage/removal_strategies.rst:161 -msgid "The *packages* feature is used to group products together and is required for the least packages removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:169 +msgid "Then, go to :menuselection:`Inventory app --> Configuration --> Routes`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:164 -msgid "Navigate to :menuselection:`Inventory --> Configuration --> Settings` and select the check box for the :guilabel:`Packages` feature." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:170 +msgid "Click on :menuselection:`Filters --> Archived` to show archived routes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:-1 -msgid "Enable the packages feature." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:171 +msgid "Select the checkbox next to :guilabel:`Replenish on Order (MTO)`, and click on :menuselection:`Action --> Unarchive`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:172 -msgid ":doc:`Packages <../product_management/product_tracking/package>`" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:175 +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/warehouses_storage/removal_strategies.rst:173 -msgid ":doc:`2-step delivery <../shipping_receiving/daily_operations/receipts_delivery_two_steps>`" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:179 +msgid "To set a product's procurement route to |MTO|, go to :menuselection:`Inventory app --> Products --> Products`, and click on the desired product to open its product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:174 -msgid ":doc:`3-step delivery <../shipping_receiving/daily_operations/delivery_three_steps>`" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:182 +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/warehouses_storage/removal_strategies/closest_location.rst:3 -msgid "Closest location removal" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:185 +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/warehouses_storage/removal_strategies/closest_location.rst:5 -msgid "For the *Closest Location* removal strategy, products are picked based on the alphanumeric order of storage location titles." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:189 +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/warehouses_storage/removal_strategies/closest_location.rst:8 -msgid "The goal of this strategy is to save the warehouse worker from taking a long journey to a farther shelf when the product is also available at a closer location." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.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 "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:12 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:9 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:11 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:9 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:13 -msgid ":doc:`About removal strategies <../removal_strategies>`" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:-1 +msgid "Replenish on Order selected on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:16 -msgid "To understand *location sequence* in the closest removal strategy, consider the following example:" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:3 +msgid "Lead times" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:19 -msgid "A product is stored in the following locations: `Shelf A/Pallet`, `Shelf A/Rack 1`, and `Shelf A/Rack 2`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:10 +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/warehouses_storage/removal_strategies/closest_location.rst:-1 -msgid "Show a mockup of real storage location in a warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:15 +msgid "Lead time types" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:26 -msgid "The sublocation, `Pallet`, is on the ground level. Products stored here are easier to retrieve, compared to requiring a forklift to reach `Rack 1` and `Rack 2`. The storage locations were strategically named in alphabetic order, based on ease of access." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:17 +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/warehouses_storage/removal_strategies/closest_location.rst:31 -msgid "To use this removal strategy, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` settings **must** be enabled in :menuselection:`Inventory app --> Configuration --> Settings`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:-1 +msgid "Show graphic of all lead times working together." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:35 -msgid ":ref:`Set up removal strategy `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:24 +msgid ":ref:`Customer lead time `: 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/warehouses_storage/removal_strategies/closest_location.rst:40 -msgid "Location names" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:29 +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 ample time to prepare the outgoing shipment earlier, considering the possibility of delays in the fulfillment process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:42 -msgid "To configure location names, begin by navigating to :menuselection:`Inventory app --> Configuration --> Locations`. Then, select an existing location, or click :guilabel:`New` to create a new one, and then enter the desired name in the :guilabel:`Location Name` field." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:34 +msgid ":ref:`Purchase lead time `: 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/warehouses_storage/removal_strategies/closest_location.rst:46 -msgid "Once the locations are named in alphabetical order, based on their proximity to the output or packing location, set the removal strategy on the :ref:`parent location `." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:39 +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/warehouses_storage/removal_strategies/closest_location.rst:50 -msgid "To do that, in the :guilabel:`Locations` list, select the parent location of the alphabetically named storage locations." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:45 +msgid ":ref:`Days to Purchase `: days needed for the vendor to receive a request for quotation (RFQ) and confirm it. It advances the deadline to schedule a |RFQ| by a specified number of days." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:53 -msgid "Doing so opens the form for the parent location. In the :guilabel:`Removal Strategy` field, select :guilabel:`Closest Location`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:49 +msgid ":ref:`Manufacturing lead time `: 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/warehouses_storage/removal_strategies/closest_location.rst:57 -msgid "In a warehouse, the storage location `WH/Stock/Shelf 1` is located closest to the packing area, where products retrieved from shelves are packed for shipment. The popular product, `iPhone charger` is stored in three locations, `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and `WH/Stock/Shelf 3`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:54 +msgid ":ref:`Days to prepare manufacturing order `: number of days needed to replenish components, or manufacture sub-assemblies of the product. Either set one directly on the bill of materials (BoM), or click *Compute* to sum up purchase and manufacturing lead times of components in the |BoM|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:62 -msgid "To use closest location, set the removal strategy on the parent location, 'WH/Stock'." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:60 +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/warehouses_storage/removal_strategies/closest_location.rst:67 -msgid "To see how the closest location removal strategy works, consider the following example, featuring the popular product, `iPhone charger`, which is stored in `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and `WH/Stock/Shelf 3`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:69 +msgid "Sales lead times" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:71 -msgid "Fifteen, five, and thirty units are in stock at each respective location." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:71 +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/warehouses_storage/removal_strategies/closest_location.rst:74 -msgid "To check the on-hand stock at each storage location, navigate to the product form, and click the :guilabel:`On Hand` smart button." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:75 +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/warehouses_storage/removal_strategies/closest_location.rst:0 -msgid "Show on-hand stock at all locations." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:79 +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/warehouses_storage/removal_strategies/closest_location.rst:81 -msgid "Create a :ref:`delivery order ` for eighteen units of the `iPhone charger` by navigating to the :menuselection:`Sales app` and creating a new quotation." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:0 +msgid "Set *Delivery Date* in a sales order. Enables delivery lead times feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:84 -msgid "After adding the products, clicking :guilabel:`Confirm` creates a delivery order that reserves items stored at the closest location, using the removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:87 +msgid "The following sections demonstrate how to automatically compute expected delivery dates." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:87 -msgid "For more details about *where* the units were picked, select the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right. Doing so opens the :guilabel:`Open: Stock move` pop-up window that displays how the reserved items were picked, according to the removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:90 +msgid "Customer lead time" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:91 -msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked. All fifteen of the units stored at the closest location, `WH/Stock/Shelf 1`, are picked first. The remaining three units are then selected from the second closest location, `WH/Stock/Shelf 2`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:92 +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/warehouses_storage/removal_strategies/closest_location.rst:-1 -msgid "Display *Pick From* quantities for the order for iPhone chargers." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:98 +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/warehouses_storage/removal_strategies/fefo.rst:3 -msgid "FEFO removal" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:0 +msgid "Set *Customer Lead Time* on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:5 -msgid "The *First Expired, First Out* (FEFO) removal strategy targets products for removal based on their assigned removal dates." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:109 +msgid "Sales security lead time" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:14 -msgid "Removal date" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:111 +msgid "*Sales security lead time* is set globally for the business in :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:16 -msgid "Products **must** be removed from inventory before their *removal date*, which is set as a certain number of days before the product's *expiration date*." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:114 +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/warehouses_storage/removal_strategies/fefo.rst:19 -msgid "The user sets this number of days by navigating to the product form's :guilabel:`Inventory` tab. Under the :guilabel:`Traceability` section, ensure the :guilabel:`Tracking` field is set to either :guilabel:`By Lots` or :guilabel:`By Unique Serial Number`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:117 +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/warehouses_storage/removal_strategies/fefo.rst:23 -msgid "Next, select the :guilabel:`Expiration Date` option, which makes the :guilabel:`Removal Date` field (and other date fields) appear." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:121 +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/warehouses_storage/removal_strategies/fefo.rst:27 -msgid "The :guilabel:`Lots and Serial Numbers` and :guilabel:`Expiration Dates` features **must** be enabled in :menuselection:`Inventory app --> Configuration --> Settings` to track expiration dates." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:0 +msgid "View of the security lead time for sales configuration from the sales settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:31 -msgid "The expiration date of a product is determined by adding the date the product was received to the number of days specified in the :guilabel:`Expiration Date` field of the product form." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:131 +msgid "Deliver several products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:34 -msgid "The removal date takes this expiration date, and subtracts the number of days specified in the :guilabel:`Removal Date` field of the product form." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:133 +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/warehouses_storage/removal_strategies/fefo.rst:38 -msgid ":doc:`Expiration dates <../../product_management/product_tracking/expiration_dates>`" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:137 +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/warehouses_storage/removal_strategies/fefo.rst:41 -msgid "In the :guilabel:`Inventory` tab of the product, `Egg`, the following :guilabel:`Dates` are set by the user:" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:141 +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/warehouses_storage/removal_strategies/fefo.rst:44 -msgid ":guilabel:`Expiration Date`: `30` days after receipt" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:-1 +msgid "Show *Shipping Policy* field in the *Other Info* tab of a quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:45 -msgid ":guilabel:`Removal Date`: `15` days before expiration date" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:150 +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/warehouses_storage/removal_strategies/fefo.rst:-1 -msgid "Display expiration and removal dates set on the product form." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:153 +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/warehouses_storage/removal_strategies/fefo.rst:51 -msgid "A shipment of Eggs arrive at the warehouse on January 1st. So, the expiration date of the Eggs is **January 31st** (Jan 1st + 30). By extension, the removal date is **January 16th** (Jan 31 - 15)." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:160 +msgid "Purchase lead times" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:57 -msgid "To view the expiration dates of items in stock, navigate to the product form, and click the :guilabel:`On Hand` smart button." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:162 +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/warehouses_storage/removal_strategies/fefo.rst:60 -msgid "Next, click the additional options icon, located on the far-right, and select the columns: :guilabel:`Expiration Date` and :guilabel:`Removal Date`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:165 +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/warehouses_storage/removal_strategies/fefo.rst:-1 -msgid "Show expiration dates from the inventory adjustments model accessed from the *On Hand*\n" -"smart button from the product form." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:170 +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/warehouses_storage/removal_strategies/fefo.rst:71 -msgid "Using the :abbr:`FEFO (First Expired, First Out)` removal strategy ensures that products with the nearest removal date are picked first." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:-1 +msgid "Visualization of PO deadline and receipt date used with vendor lead times." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:74 -msgid "To understand how this removal strategy works, consider the following example below about the product, `Carton of eggs`, which is a box containing twelve eggs." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:178 +msgid ":ref:`PO scheduling with reordering rules `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:77 -msgid "The product is tracked :guilabel:`By Lots`, and the product category's :guilabel:`Force Removal Strategy` is set to :guilabel:`First Expired, First Out (FEFO)`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:181 +msgid "Vendor lead time" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:81 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:59 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:24 -msgid ":ref:`Set up force removal strategy `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:183 +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/warehouses_storage/removal_strategies/fefo.rst:82 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:60 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:25 -msgid ":ref:`Enable lots tracking `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:186 +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/warehouses_storage/removal_strategies/fefo.rst:83 -msgid "`Odoo Tutorials: Perishable Products `_" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:192 +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/warehouses_storage/removal_strategies/fefo.rst:90 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:69 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:35 -msgid "LOT1" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:196 +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/warehouses_storage/removal_strategies/fefo.rst:91 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:70 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:36 -msgid "LOT2" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:0 +msgid "Add delivery lead times to vendor pricelist on a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:92 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:71 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:37 -msgid "LOT3" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:203 +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/warehouses_storage/removal_strategies/fefo.rst:93 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:72 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:38 -msgid "On-hand stock" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:209 +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/warehouses_storage/removal_strategies/fefo.rst:94 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:73 -msgid "5" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:0 +msgid "Show expected *Receipt Date* of the product from the vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:95 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:75 -msgid "2" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:0 +msgid "Show expected *Scheduled Date* of arrival of the product from the vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:96 -msgid "1" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:225 +msgid "Purchase security lead time" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:98 -msgid "April 4" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:227 +msgid "*Purchase security lead time* is set globally for the business in :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:99 -msgid "April 10" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:230 +msgid "On the :guilabel:`Settings` page, under the :guilabel:`Advanced Scheduling` heading, tick the checkbox for :guilabel:`Security Lead Time for Purchase`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:100 -msgid "April 15" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:233 +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. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:101 -msgid ":ref:`Removal date `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:237 +msgid "Setting the :guilabel:`Security Lead Time for Purchase` to `2.00` days, pushes the :guilabel:`Scheduled Date` of receipt back by two days. 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/warehouses_storage/removal_strategies/fefo.rst:102 -msgid "February 26" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:0 +msgid "Set security lead time for purchase from the Inventory > Configuration > Settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:103 -msgid "March 4" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:249 +msgid "Days to purchase" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:104 -msgid "March 9" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:251 +msgid "To set up the *days to purchase* lead time, go to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Advanced Scheduling` section, in the :guilabel:`Days to Purchase` field, specify the number of days required for the vendor to confirm a |RFQ| after receiving it from the company." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:106 -msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and create a new quotation." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:-1 +msgid "Show \"Days to Purchase\" configuration in the Settings page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:109 -msgid "Clicking :guilabel:`Confirm` creates a delivery order for today, December 29th, and the lot numbers with the soonest expiration dates are reserved, using the :abbr:`FEFO (First Expired, First Out)` removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:263 +msgid "Manufacturing lead times" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:113 -msgid "To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right of the Carton of egg's product line, in the :guilabel:`Operations` tab of the delivery order. Doing so opens the :guilabel:`Open: Stock move` pop-up window." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:265 +msgid "Lead times can help simplify the procurement process for consumable materials and components used in manufactured products with bills of materials (BoMs)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:117 -msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked from." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:268 +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/warehouses_storage/removal_strategies/fefo.rst:120 -msgid "Since the order demanded six Cartons of eggs, using the :abbr:`FEFO (First Expired, First Out)` removal strategy, all five Cartons from `LOT1`, with the removal date of February 26th, are picked. The remaining Carton is selected from `LOT2`, which has a removal date of March 4th." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:-1 +msgid "Visualization of the determination of planned MO date manufacturing lead times." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:-1 -msgid "The stock moves window that shows the lots to be removed using FEFO." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:277 +msgid "Manufacturing lead time" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:3 -msgid "FIFO removal" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:279 +msgid "Manufacturing lead times for products are configured from a product's bill of materials (BoM) form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:5 -msgid "The *First In, First Out* (FIFO) removal strategy selects products with the earliest arrival dates. This method is useful for companies selling products that have short demand cycles, like clothes, for example. By using :abbr:`FIFO (First In, First Out)`, companies can prevent prolonged stock retention of specific styles." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:281 +msgid "To add a lead time to a |BoM|, navigate to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and select the desired |BoM| to edit." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:14 -msgid "Various quantities of the product, `T-shirt`, tracked by lot numbers, arrive on August 1st and August 25th. For an order made on September 1st, the :abbr:`FIFO (First In, First Out)` removal strategy prioritizes lots that have been in stock the longest. So, products received on August 1st are selected first for picking." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:284 +msgid "On the |BoM| form, click the :guilabel:`Miscellaneous` tab. Change the value (in days) in the :guilabel:`Manuf. Lead Time` field to specify the calendar days needed to manufacture the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:0 -msgid "Illustration of FIFO selecting the oldest products in stock." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:-1 +msgid "Manuf. Lead Time value specified on a product's Bill of Material form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:24 -msgid ":ref:`Lot/serial number setup details `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:292 +msgid "If the selected |BoM| is a multi-level |BoM|, the manufacturing lead times of the components are added." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:29 -msgid "Arrival date" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:295 +msgid "If the |BoM| product is subcontracted, the :guilabel:`Manuf. Lead Time` can be used to determine the date at which components should be sent to the subcontractor." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:31 -msgid "To see the product lot or serial number that arrived in inventory first, navigate to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:298 +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/warehouses_storage/removal_strategies/fifo.rst:34 -msgid "Then, select the :guilabel:`▶️ (right-pointing arrow)` icon on the left of a product line, in order to reveal a list of the product's lots or serial numbers that are in stock. The :guilabel:`Created On` field shows the lot/serial number creation date, which is, essentially, the arrival date." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:301 +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/warehouses_storage/removal_strategies/fifo.rst:39 -msgid "Serial number `00000000500` of the product, `Cabinet with Doors`, arrived on December 29th, as displayed in the :guilabel:`Created On` field." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:305 +msgid "This ensures the manufacturing process begins on time, in order to meet the delivery date." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:0 -msgid "Display arrival date of a lot for an item." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:307 +msgid "However, it is 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/warehouses_storage/removal_strategies/fifo.rst:49 -msgid "To understand how :abbr:`FIFO (First In, First Out)` rotates products out, consider the following example, focusing on three lots of white shirts." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:312 +msgid ":doc:`Manufacturing planning <../../../manufacturing/workflows/use_mps>`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:52 -msgid "The shirts are from the *All/Clothes* category, where :abbr:`FIFO (First In, First Out)` is set as the :guilabel:`Force Removal Strategy`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:313 +msgid ":doc:`Schedule MOs with reordering rules `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:55 -msgid "The white shirts are tracked :guilabel:`By Lots` in the :guilabel:`Inventory` tab of the product form." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:316 +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/warehouses_storage/removal_strategies/fifo.rst:62 -msgid "The following table represents the on-hand stock and lot number details of white shirts." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:323 +msgid "Days to prepare manufacturing order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:74 -msgid "3" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:325 +msgid "Configure the days required to gather components to manufacture a product by going to its |BoM|. To do that, go to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and select the desired |BoM|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:76 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:42 -msgid ":ref:`Created on `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:329 +msgid "In the :guilabel:`Miscellaneous` tab of the |BoM|, specify the calendar days needed to obtain components of the product in the :guilabel:`Days to prepare Manufacturing Order` field. Doing so creates |MOs| in advance, and ensures there is enough time to either replenish components, or manufacture semi-finished products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:77 -msgid "March 1" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:335 +msgid "Clicking :guilabel:`Compute`, located next to the :guilabel:`Days to prepare Manufacturing Order` field, calculates the longest lead time among all the components listed on the |BoM|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:78 -msgid "April 1" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:338 +msgid "*Purchase security lead times* that impact this specific |BoM| are also added to this value." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:79 -msgid "May 1" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:342 +msgid "A |BoM| has two components, one has a manufacturing lead time of two days, and the other has a purchase lead time of four days. The :guilabel:`Days to prepare Manufacturing Order` is four days." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:81 -msgid "To see the removal strategy in action, create a :ref:`delivery order ` for six white shirts by navigating to the :menuselection:`Sales app` and creating a new quotation." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:349 +msgid "Manufacturing security lead time" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:84 -msgid "After clicking :guilabel:`Confirm` on the sales order, a delivery order with the oldest lot numbers for shirts are reserved, using the :abbr:`FIFO (First In, First Out)` removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:351 +msgid "*Manufacturing security lead time* is set globally for the business in :menuselection:`Manufacturing app --> Configuration --> Settings`. Under the :guilabel:`Planning` heading, tick the checkbox for :guilabel:`Security Lead Time`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:87 -msgid "To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right of the white shirt's product line in the :guilabel:`Operations` tab of the delivery order. Doing so opens the :guilabel:`Open: Stock move` pop-up window." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:355 +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. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:91 -msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked from. Since the order demanded six shirts, all five shirts from `LOT1`, and one shirt from `LOT2`, are selected." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:-1 +msgid "View of the security lead time for manufacturing from the manufacturing app settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:-1 -msgid "Two lots being reserved for a sales order with the FIFO strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:363 +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/warehouses_storage/removal_strategies/least_packages.rst:3 -msgid "Least packages removal" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:370 +msgid "Global example" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:5 -msgid "The *Least Packages* removal strategy fulfills an order by opening the fewest number of packages, which is ideal for maintaining organized stock without needing to open multiple boxes." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:372 +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/warehouses_storage/removal_strategies/least_packages.rst:10 -msgid "`Odoo Tutorials: Least Packages `_" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:375 +msgid "**Sales security lead time**: 1 day" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:12 -msgid "To understand how the removal strategy works, consider the following example, featuring a warehouse that stores packages of flour in bulk packages of `100 kg`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:376 +msgid "**Manufacturing security lead time**: 2 days" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:15 -msgid "To minimize moisture, and/or prevent pests from entering open packages, the least packages removal strategy is used to pick from a single, opened package." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:377 +msgid "**Manufacturing lead time**: 3 days" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:21 -msgid "A package of `100 kg` of flour is depleted to `54 kg` after fulfilling some orders. There are other packages of `100 kg` in stock." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:378 +msgid "**Purchase security lead time**: 1 day" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:24 -msgid "When an order for `14 kg` of flour is placed, the package of `54 kg` is selected." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:379 +msgid "**Vendor lead time**: 4 days" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:25 -msgid "When an order for *more* than `54 kg` of flour is placed, an unopened `100 kg` package is used to fulfill the order. While this temporarily results in two open packages, these open packages are prioritized in the next picking." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:381 +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/warehouses_storage/removal_strategies/least_packages.rst:32 -msgid "Using the least package removal strategy, the fewest number of packages is used to fulfill an order." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:-1 +msgid "Show timeline of how lead times work together to schedule warehouse operations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:35 -msgid "The :ref:`Packages feature ` **must** be enabled to use this strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:389 +msgid "**September 1st**: Sales order created, confirmed by salesperson." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:38 -msgid "Consider the following example, featuring the product, `Flour`. The product's :guilabel:`Units of Measure` field, located on the product form, is set to `kg`. The product is stored in packages of `100 kg`, with one remaining package containing `54 kg`. The product category's :guilabel:`Force Removal Strategy` is set to :guilabel:`Least Packages`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:391 +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/warehouses_storage/removal_strategies/least_packages.rst:44 -msgid ":ref:`Set removal strategy on product category `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:394 +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/warehouses_storage/removal_strategies/least_packages.rst:47 -msgid "To check the product's on-hand stock, navigate to the product form, and click the :guilabel:`On Hand` smart button." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:397 +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/warehouses_storage/removal_strategies/least_packages.rst:0 -msgid "Show on-hand stock in each package." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:401 +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/warehouses_storage/removal_strategies/least_packages.rst:54 -msgid "Create a :ref:`delivery order ` for eighty kilograms of flour by going to the :menuselection:`Sales app` and creating a new quotation. After clicking :guilabel:`Confirm`, the delivery order is created." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:405 +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/warehouses_storage/removal_strategies/least_packages.rst:58 -msgid "On the delivery order, the :guilabel:`Quantity` field displays the amount automatically picked, according to the removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:3 +msgid "Replenish on order (MTO)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:61 -msgid "For more details about *where* the units were picked, select the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right. Doing so opens the :guilabel:`Open: Stock move` pop-up window, displaying how the reserved items were picked, according to the removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:9 +msgid "*Replenish on order*, also known as *MTO* (make to order), is a replenishment strategy that creates a draft order for a product every time a sales order is created for it. For products that are purchased from a vendor, a request for quotation (RFQ) is created, while a sales order for a product manufactured in-house triggers the creation of a manufacturing order. The creation of a |RFQ| or manufacturing order occurs every time a sales order is created, regardless of the current stock level of the product being ordered." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:65 -msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked. Since the order demanded eighty kilograms, which exceeds the quantity in the opened package of `54 kg`, an unopened package of `100 kg` is selected." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:17 +msgid "Unarchive the Replenish on Order (MTO) route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:-1 -msgid "Show which package was picked in the *Pick From* field." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:19 +msgid "By default, Odoo sets the |MTO| route as *archived*. This is because |MTO| is a somewhat niche workflow that is only used by certain companies. However, it is easy to unarchive the route in just a few simple steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:3 -msgid "LIFO removal" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:23 +msgid "To do so, begin by navigating to :menuselection:`Inventory --> Configuration --> Routes`. On the :guilabel:`Routes` page, click the :guilabel:`Filters` button and select the :guilabel:`Archived` option. This shows all routes that are currently archived." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:5 -msgid "The *Last In, First Out* (LIFO) removal strategy picks the **newest** products on-hand, based on the date they entered a warehouse's stock." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:-1 +msgid "The archived filter on the Routes page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:8 -msgid "Every time an order is placed for products using the :abbr:`LIFO (Last In, First Out)` strategy, 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)." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:31 +msgid "Enable the checkbox next to :guilabel:`Replenish on Order (MTO)`, then click the :guilabel:`Action` button to reveal a drop-down menu. From the drop-down menu, select :guilabel:`Unarchive`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:16 -msgid "In many countries, the :abbr:`LIFO (Last In, First Out)` removal strategy is banned, since it can potentially result in old, expired, or obsolete products being delivered to customers." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:-1 +msgid "The unarchive action on the Routes page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:19 -msgid "Consider the following example, with the product, `Cinder Block`, which is tracked :guilabel:`By Lots` in the :guilabel:`Inventory` tab of the product form. The :guilabel:`Force Removal Strategy` for the cinder block's product category is set to :guilabel:`Last In, First Out (LIFO)`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:38 +msgid "Finally, remove the :guilabel:`Archived` filter from the :guilabel:`Search...` bar. The :guilabel:`Routes` page will now show all available routes, including :guilabel:`Replenish on Order (MTO)`, which is now selectable on the inventory tab of each product page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:26 -msgid ":ref:`Check arrival date `" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:-1 +msgid "The MTO route appears on the Routes page after unarchiving it." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:28 -msgid "The following table represents the cinder blocks in stock, and their various lot number details." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:47 +msgid "Configure a product to use the MTO route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:43 -msgid "June 1" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:49 +msgid "With the |MTO| route unarchived, products can now be properly configured to use replenish on order. To do so, begin by going to :menuselection:`Inventory --> Products --> Products`, then select an existing product, or click :guilabel:`Create` to configure a new one." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:44 -msgid "June 3" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:53 +msgid "On the product page, select the :guilabel:`Inventory` tab and enable the :guilabel:`Replenish on Order (MTO)` route in the :guilabel:`Routes` section, along with one other route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:45 -msgid "June 6" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:57 +msgid "The :guilabel:`Replenish on Order (MTO)` route **does not** work unless another route is selected as well. This is because Odoo needs to know how to replenish the product when an order is placed for it (buy it, manufacture it, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:47 -msgid "To see the removal strategy in action, create a :ref:`delivery order ` for seven cinder blocks by navigating to the :menuselection:`Sales app` and creating a new quotation." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:-1 +msgid "Select the MTO route and a second route on the Inventory tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:51 -msgid ":guilabel:`Confirm` the sales order to create a delivery order. Doing so reserves the newest lot numbers are using the :abbr:`LIFO (Last In, First Out)` removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:65 +msgid "If the product is purchased from a vendor to fulfill sales orders, enable the :guilabel:`Can be Purchased` checkbox under the product name. Doing so makes the :guilabel:`Purchase` tab appear alongside the other settings tabs below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:54 -msgid "To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` icon, located on the far-right of the cinder block's product line in the :guilabel:`Operations` tab of the delivery order. Doing so opens the :guilabel:`Open: Stock move` pop-up window." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:69 +msgid "Select the :guilabel:`Purchase` tab and specify a :guilabel:`Vendor` and the :guilabel:`Price` they sell the product for." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:58 -msgid "In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where the quantities to fulfill the :guilabel:`Demand` are picked from. Since the order demanded seven cinder blocks, the newest cinder blocks from `LOT3` are selected, using the :abbr:`LIFO (Last In, First Out)` removal strategy." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:-1 +msgid "Enable \"Can be Purchased\" and specify a vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:-1 -msgid "The detailed operations shows which lots are being selected for the picking." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:76 +msgid "If the product is manufactured, make sure that it has a bill of materials (BOM) configured for it. To do so, click the :guilabel:`Bill of Materials` smart button at the top of the screen, then click :guilabel:`Create` on the :guilabel:`Bill of Materials` page to configure a new |BOM| for the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:81 +msgid "On the blank |BOM| form, add the components used to manufacture the product on the :guilabel:`Components` tab, along with the operations required for the manufacturing workflow on the :guilabel:`Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:85 +msgid "Finally, click :guilabel:`Save` to save the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:88 +msgid "Fulfill a sales order using the MTO route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:90 +msgid "After configuring a product to use the |MTO| route, a replenishment order is created for it every time a sales order including the product is confirmed. The type of order created depends on the second route selected in addition to |MTO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:94 +msgid "For example, if *Buy* was the second route selected, then a purchase order is created upon confirmation of a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:98 +msgid "When the |MTO| route is enabled for a product, a replenishment order is always created upon confirmation of a sales order. This is the case even if there is enough stock of the product on-hand to fulfill the sales order, without buying or manufacturing additional units of it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:102 +msgid "While the |MTO| route can be used in unison with a variety of other routes, the *Buy* route is used as the example for this workflow. Begin by navigating to the :menuselection:`Sales` app, then click :guilabel:`Create`, which opens a blank quotation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:106 +msgid "On the blank quotation form, add a :guilabel:`Customer`, then click :guilabel:`Add a product` under the :guilabel:`Order Lines` tab, and enter a product that has been configured to use the *MTO* and *Buy* routes. Click :guilabel:`Confirm` and the quotation is turned into a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:110 +msgid "A :guilabel:`Purchase` smart button now appears in the top-right corner of the sales order. Clicking it opens the |RFQ| associated with the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:113 +msgid "Click :guilabel:`Confirm Order` to confirm the |RFQ|, and turn it into a purchase order. A green :guilabel:`Receive Products` button now appears at the top of the purchase order. Once the products are received, click :guilabel:`Receive Products` to register them into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:117 +msgid "Return to the sales order by clicking the :guilabel:`SO` breadcrumb, or by navigating to :menuselection:`Sales --> Orders --> Orders`, and selecting the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:120 +msgid "Finally, click the :guilabel:`Delivery` smart button in the top-right of the order to be taken to the delivery order. Once the products have been shipped to the customer, click :guilabel:`Validate` to confirm the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:3 +msgid "Reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:9 +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/warehouses_storage/replenishment/reordering_rules.rst:13 +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/warehouses_storage/replenishment/reordering_rules.rst:19 +msgid "`Odoo Tutorials: Automatic Reordering Rules `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:20 +msgid "`Odoo Tutorials: Manual Reordering Rules `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:23 +msgid "Configure products for reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:25 +msgid "In order to use reordering rules for a product, it must first be correctly configured. Begin by navigating to :menuselection:`Inventory app --> Products --> Products`, then select an existing product, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:29 +msgid "On the product form, under the :guilabel:`General Information` tab, make sure 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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:-1 +msgid "Set the Product Type as Storable." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:37 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:-1 +msgid "Select one or more routes on the Inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:44 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:-1 +msgid "Specify a vendor and price on the Purchase tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:53 +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/warehouses_storage/replenishment/reordering_rules.rst:57 +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:`New` to configure a new :abbr:`BoM (Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:-1 +msgid "The Bill of Materials smart button on a product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:66 +msgid "Create new reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:68 +msgid "To create a new reordering rule, navigate to :menuselection:`Inventory app --> Configuration --> Reordering Rules`, then click :guilabel:`New`, and fill out the new line as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:71 +msgid ":guilabel:`Product`: The product that is replenished by the rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:72 +msgid ":guilabel:`Location`: The location where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:73 +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/warehouses_storage/replenishment/reordering_rules.rst:76 +msgid ":guilabel:`Max Quantity`: The maximum quantity that stock is replenished up to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:77 +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/warehouses_storage/replenishment/reordering_rules.rst:79 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:-1 +msgid "The form for creating a new reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:87 +msgid "Reordering rules can also be created from each product form. To do so, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product. Then, click the :guilabel:`Reordering Rules` smart button, and click :guilabel:`New` to fill out the new line, as detailed above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:92 +msgid "For advanced usage of reordering rules, learn about the following reordering rule fields:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:94 +msgid ":ref:`Trigger `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:95 +msgid ":ref:`Visibility days `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:96 +msgid ":ref:`Route `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:99 +msgid "0/0/1 reordering rule" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:101 +msgid "The *0/0/1* reordering rule is a specialty rule used to replenish a product that is not kept on-hand, each time a sales order (SO) is confirmed for that product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:105 +msgid "The 0/0/1 reordering rule is similar to the *Replenish on Order (MTO)* route, in that both workflows are used to replenish a product upon confirmation of an |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:108 +msgid "The main difference between the two methods is that the *Replenish on Order* route automatically reserves the product for the |SO| that caused it to be replenished. This means the product **cannot** be used for a different |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:112 +msgid "The 0/0/1 reordering rule does not have this limitation. A product replenished using the rule is not reserved for any specific |SO|, and can be used as needed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:115 +msgid "Another key difference is that replenishment orders created by the *Replenish on Order* route are linked to the original |SO| by a smart button at the top of the order. When using the 0/0/1 reordering rule, a replenishment order is created, but is not linked to the original |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:119 +msgid "See the :doc:`Replenish on Order (MTO) ` documentation for a full overview of the MTO route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:121 +msgid "To create a 0/0/1 reordering rule, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:124 +msgid "At the top of the product's page, click the :icon:`fa-refresh` :guilabel:`Reordering Rules` smart button to open the :guilabel:`Reordering Rules` page for the product. On the resulting page, click :guilabel:`New` to begin configuring a new reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:128 +msgid "In the :guilabel:`Location` field of the new reordering rule, select the location in which replenished products should be stored. By default, this location is set to :guilabel:`WH/Stock`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:131 +msgid "In the :guilabel:`Route` field, select the route the rule should use to replenish the item. For example, if the product should be purchased from a vendor, select the :guilabel:`Buy` route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:134 +msgid "In the :guilabel:`Min Quantity` field and :guilabel:`Max Quantity` field, leave the values set to `0.00`. In the :guilabel:`To Order` field, enter a value of `1.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:-1 +msgid "A 0/0/1 reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:141 +msgid "With the reordering rule configured using these values, each time an |SO| causes the forecasted quantity of the product to fall below the :guilabel:`Min Quantity` of `0.00`, the selected :guilabel:`Route` is used to replenish the product in one-unit increments, back up to the :guilabel:`Max Quantity` of `0.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:147 +msgid "A picture frame is configured with a 0/0/1 reordering rule that uses the *Buy* route. Zero units of the picture frame are kept on-hand at any given time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:150 +msgid "An |SO| is confirmed for one unit of the picture frame, which causes the forecasted quantity to drop to `-1.00`. This triggers the reordering rule, which automatically creates a |PO| for one unit of the picture frame." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:154 +msgid "Once the product is received from the vendor, the forecasted quantity of the picture frame returns to `0.00`. There is now one picture frame on-hand, but it is not reserved for the |SO| which triggered its purchase. It can be used to fulfill that |SO|, or reserved for a different order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:162 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:164 +msgid "When stock falls below the reordering rule's minimum, set the reordering rule's *trigger* to *automatic* to automatically create purchase or manufacturing orders to replenish stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:167 +msgid "Alternatively, setting the reordering rule's trigger to *manual* displays the product and forecasted stock on the *replenishment dashboard*, where the procurement manager can review the stock levels, lead times, and forecasted dates of arrival." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:172 +msgid ":doc:`../replenishment`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:175 +msgid "The replenishment dashboard is accessible by going to :menuselection:`Inventory app --> Operations --> Replenishment`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:178 +msgid "To enable the :guilabel:`Trigger` field, go to :menuselection:`Inventory app --> Configuration --> Reordering Rules`. Then, click the :guilabel:`(slider)` icon, located to the far-right of the column titles, and enable the :guilabel:`Trigger` option from the additional options drop-down menu that appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:-1 +msgid "Enable the Trigger field by toggling it in the additional options menu" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:187 +msgid "In the :guilabel:`Trigger` column, select :guilabel:`Auto` or :guilabel:`Manual`. Refer to the sections below to learn about the different types of reordering rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:191 +msgid "Auto" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:193 +msgid "Automatic reordering rules, configured by setting the reordering rule's :guilabel:`Trigger` field to :guilabel:`Auto`, generates purchase or manufacturing orders when:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:196 +msgid "the scheduler runs, and the *On Hand* quantity is below the minimum" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:197 +msgid "a sales order is confirmed, and lowers the *Forecasted* quantity of the product below the minimum" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:201 +msgid "The scheduler is set to run once a day, by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:203 +msgid "To manually trigger a reordering rule before the scheduler runs, ensure :ref:`developer mode ` is enabled, and select :menuselection:`Inventory app --> Operations --> Run Scheduler`. Then, click the purple :guilabel:`Run Scheduler` button on the pop-up window that appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:208 +msgid "Be aware that this also triggers any other scheduled actions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:211 +msgid "The product, `Office Lamp`, has an automatic reordering rule set to trigger when the forecasted quantity falls below the :guilabel:`Min Quantity` of `5.00`. Since the current :guilabel:`Forecast` is `55.00`, the reordering rule is **not** triggered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:0 +msgid "Show automatic reordering rule from the Reordering Rule page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:219 +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 app --> Orders --> Requests for Quotation`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:223 +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 app --> Operations --> Manufacturing Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:227 +msgid "When no route is selected, Odoo selects the :guilabel:`Route` specified in the :guilabel:`Inventory` tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:235 +msgid "Manual reordering rules, configured by setting the reordering rule's :guilabel:`Trigger` field to :guilabel:`Manual`, lists a product on the replenishment dashboard when the forecasted quantity falls below a specified minimum. Products on this dashboard are called *needs*, because they are needed to fulfill upcoming sales orders, but the forecasted quantity is not enough." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:240 +msgid "The replenishment dashboard, accessible by navigating to :menuselection:`Inventory app --> Operations --> Replenishment`, considers sales order deadlines, forecasted stock levels, and vendor lead times. It displays needs **only** when it is time to reorder items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:245 +msgid "If the one-day window for ordering products is too short, skip to the :ref:`visibility days ` section to make the need appear on the replenishment dashboard a specified number of days in advance." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:249 +msgid "When a product appears on the replenishment dashboard, clicking the :guilabel:`Order Once` button generates the purchase or manufacturing order with the specified amounts :guilabel:`To Order`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:-1 +msgid "Click the Order Once button on the replenishment dashboard to replenish stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:259 +msgid "Visibility days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:262 +msgid "Ensure :doc:`lead times ` are understood before proceeding with this section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:264 +msgid "When :ref:`manual reordering rules ` are assigned to a product, *visibility days* make the product appear on the replenishment dashboard (:menuselection:`Inventory app --> Operations --> Replenishment`) a certain number of days in advance." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:270 +msgid "A product has a manual reordering rule set to trigger when the stock level falls below four units. The current on-hand quantity is ten units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:273 +msgid "The current date is February 20th, and the *delivery date* on a sales order (in the :guilabel:`Other Info` tab) is March 3rd — twelve days from the current date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:276 +msgid "The :ref:`vendor lead time ` is four days, and the :ref:`purchase security lead time ` is one day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:280 +msgid "When the :guilabel:`Visibility Days` field of the reordering rule is set to zero, the product appears on the replenishment dashboard five days before the delivery date, which, in this case, is February 27th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:-1 +msgid "Graphic representing when the need appears on the replenishment dashboard: Feb 27th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:288 +msgid "To see the product on the replenishment dashboard for the current date, February 20, set the :guilabel:`Visibility Days` to `7.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:291 +msgid "To determine the amount of visibility days needed to see a product on the replenishment dashboard, subtract *today's date* from the *date the need appears* on the replenishment dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:294 +msgid "Visibility~days = Need~appears~date - Today's~date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:299 +msgid "Referring to the example above, today's date is February 20th, and the need for the product appears on February 27th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:302 +msgid "(February 27 - February 20 = 7 days)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:304 +msgid "Incorrectly setting the :guilabel:`Visibility Days` fewer than seven days in this case results in the need **not** appearing on the replenishment dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:0 +msgid "Show the replenishment dashboard with the correct and incorrect visibility days set." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:314 +msgid "Route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:316 +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/warehouses_storage/replenishment/reordering_rules.rst:320 +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 app --> Configuration --> Reordering Rules`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:324 +msgid "By default, the :guilabel:`Route` column is hidden on the :guilabel:`Reordering Rules` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:326 +msgid "Reveal the :guilabel:`Route` column by selecting the :guilabel:`(slider)` icon to the far-right of the column titles, and checking the :guilabel:`Route` option from the drop-down menu that appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:329 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:-1 +msgid "Select a preferred route from the drop-down." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:337 +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/warehouses_storage/replenishment/resupply_warehouses.rst:3 +msgid "Resupply from another warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:5 +msgid "A common use case for multiple warehouses is to have one central warehouse that resupplies multiple shops, and in this case, each shop is considered a local warehouse. When a shop wants to replenish a product, the product is ordered to the central warehouse. Odoo allows the user to easily set which warehouse(s) can resupply another warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:13 +msgid "To resupply from another warehouse, first go to :menuselection:`Inventory --> Configuration --> Settings --> Warehouse` and activate :guilabel:`Multi-Step Routes`. Then, click :guilabel:`Save` to apply the setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:-1 +msgid "Enable Multi-Step Routes in Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:21 +msgid "View all the configured warehouses by going to :menuselection:`Inventory --> Configuration --> Warehouses`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:24 +msgid "Create a new warehouse by clicking :guilabel:`Create`. Then, give the warehouse a name and a :guilabel:`Short Name`. Finally, click :guilabel:`Save` to finish creating the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:27 +msgid "After that, go back to the :guilabel:`Warehouses` page and open the warehouse that will be resupplied by the second warehouse. Then, click :guilabel:`Edit`. In the :guilabel:`Warehouse Configuration` tab, locate the :guilabel:`Resupply From` field, and check the box next to the second warehouse's name. If the warehouse can be resupplied by more than one warehouse, make sure to check those warehouses' boxes too. Finally, click :guilabel:`Save` to apply the setting. Now, Odoo knows which warehouses can resupply this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:-1 +msgid "Supply one warehouse with another in the Warehouse Configuration tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:39 +msgid "Set route on a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:41 +msgid "After configuring which warehouse(s) to resupply from, a new route is now available on all product forms. The new route appears as :guilabel:`Supply Product from [Warehouse Name]` under the :guilabel:`Inventory` tab on a product form. Use the :guilabel:`Supply Product from [Warehouse Name]` route with a reordering rule or the make to order (MTO) route to replenish stock by moving the product from one warehouse to another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:-1 +msgid "Route setting which enables a product to resupplied from a second warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:51 +msgid "When a product's reordering rule is triggered and the product has the :guilabel:`Supply Product from [Warehouse Name]` route set, Odoo automatically creates two pickings. One picking is a *delivery order* from the second warehouse, which contains all the necessary products, and the second picking is a *receipt* with the same products for the main warehouse. The product move from the second warehouse to the main warehouse is fully tracked in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:57 +msgid "On the picking/transfer records created by Odoo, the :guilabel:`Source Document` is the product's reordering rule. The location between the delivery order and the receipt is a transit location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:-1 +msgid "A reordering rule automatically creates two receipts for stock between warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:-1 +msgid "A warehouse order for resupplying one warehouse's stock with another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:-1 +msgid "A receipt for stock received to one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:3 +msgid "Transfer products between warehouses using replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:5 +msgid "For companies that use multiple warehouses, it is often necessary to transfer items between them. This is referred to as an *inter-warehouse transfer*. Odoo *Inventory* handles the administrative process of inter-warehouse transfers to ensure that inventory counts remain accurate during and after the transfer. This document will detail the method for conducting an inter-warehouse transfer using replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:12 +msgid "Configure warehouses for inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:14 +msgid "First, ensure the :guilabel:`Multi-Step Routes` setting is enabled by navigating to :menuselection:`Inventory --> Configuration --> Settings`, and then check the box under the :guilabel:`Warehouse` tab. This will provide additional configuration options when creating a second warehouse that are needed for inter-warehouse replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:19 +msgid "By default, Odoo comes with a main warehouse already configured. If an additional warehouse has not already been created, do so now from the :guilabel:`Inventory` module by selecting :menuselection:`Configuration --> Warehouses --> Create`. Otherwise, select the warehouse that products will be transferred to from the :guilabel:`Warehouses` page and then click :guilabel:`Edit` to change its settings. Configure the warehouse as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:25 +msgid ":guilabel:`Warehouse`: choose a name that is not already being used for another warehouse (e.g. `Alternative Warehouse`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:27 +msgid ":guilabel:`Short Name`: choose a short name by which the warehouse will be identified (e.g. `ALT_WH`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:30 +msgid "Click :guilabel:`Save` and the new warehouse will be created. In addition, a new :guilabel:`Resupply From` field will appear on the warehouse's form. Click :guilabel:`Edit` and then check the box next to the warehouse that will be used to resupply the warehouse that is currently being configured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:-1 +msgid "A warehouse settings form configured to allow resupplying between warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:39 +msgid "For the purposes of this demonstration, the warehouse that products are transferred from (outgoing) will be titled \"San Francisco\", and the warehouse that products are transferred to (incoming) will be titled \"San Francisco 2\"." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:44 +msgid "Configure products for inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:46 +msgid "Products must also be configured properly in order for them to be transferred between warehouses. Navigate to :menuselection:`Inventory --> Products --> Products` and select an existing product or :guilabel:`Create` a new one, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:50 +msgid "Then, on the product form, go to the :guilabel:`Inventory` tab and enable the checkbox for :guilabel:`X: Supply Product from Y`, with *X* being the warehouse receiving the transferred products and *Y* being the warehouse that products are transferred from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:-1 +msgid "Enable the checkbox to resupply one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:59 +msgid "Replenish one warehouse from another" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:61 +msgid "Starting in the :menuselection:`Inventory` module, select :menuselection:`Products --> Products` and then choose the product that will be replenished. Click the :guilabel:`Replenish` button on the top left of the product page and fill out the pop-up form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:65 +msgid ":guilabel:`Quantity`: the number of units that will be sent to the warehouse being replenished" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:66 +msgid ":guilabel:`Scheduled Date`: the date that the replenishment is scheduled to take place" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:67 +msgid ":guilabel:`Warehouse`: the warehouse that will be replenished" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:68 +msgid ":guilabel:`Preferred Routes`: select `X: Supply Product from Y`, with *X* being the warehouse to be replenished and *Y* being the warehouse that the product will be transferred from" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:-1 +msgid "The form for replenishing a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:75 +msgid "Click :guilabel:`Confirm` and a delivery order will be created for the outgoing warehouse along with a receipt for the warehouse that will receive the product. Depending on the configuration settings for the outgoing and incoming warehouses, processing delivery orders and receipts will require between one and three steps. This document will detail how to process one-step deliveries and receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:82 +msgid "Process the delivery order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:84 +msgid "The first stage of a replenishment order is processing the delivery from the warehouse that the product is being transferred from. On the :menuselection:`Inventory` dashboard, select the :guilabel:`X to Process` button on the :guilabel:`Delivery Orders` card for the outgoing warehouse, then the delivery order created for the replenishment. On the delivery order page, click the :guilabel:`Check Availability` button in the top left to reserve the quantity of the product to be transferred. Once the delivery has been dispatched, click the :guilabel:`Validate` button to register the quantities shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:-1 +msgid "The delivery orders card for the outgoing warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:97 +msgid "Process the receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:99 +msgid "Once the goods arrive at the incoming warehouse, the receipt created for that warehouse must be processed as well. Return to the :menuselection:`Inventory` dashboard and select the :guilabel:`X to Process` button on the :guilabel:`Receipts` card for the incoming warehouse, then the receipt created for the replenishment. On the receipt page, click the :guilabel:`Validate` button in the top left of the page to register the quantities received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:109 +msgid "After processing the receipt, the products transferred will now appear in the inventory of the incoming warehouse. The stock numbers for both warehouses can be viewed by returning to the product page and selecting the :guilabel:`X Units On Hand` button at the top of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:114 +msgid "Automate inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:116 +msgid "Using reordering rules, it is possible to automate the process of replenishing one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:119 +msgid "To get started, navigate to :menuselection:`Inventory --> Products --> Products`, and then choose the product that will be replenished. From the product page, select the :guilabel:`Reordering Rules` smart button at the top of the form, and then on the next page, click :guilabel:`Create` to configure the form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:124 +msgid ":guilabel:`Location`: the location that the reordering rule will replenish when triggered, in this case, the incoming warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:126 +msgid ":guilabel:`Min Quantity`: when the quantity on hand at the incoming warehouse falls below this number, the reordering rule will be triggered" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:128 +msgid ":guilabel:`Max Quantity`: when the reordering rule is triggered, the product will be replenished at the incoming warehouse up to this quantity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:130 +msgid ":guilabel:`Multiple Quantity`: specify if the product should be replenished in batches of a certain quantity; for example, a product could be replenished in batches of 20" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:132 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:-1 +msgid "A fully configured reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:139 +msgid "Finish by clicking :guilabel:`Save` and the reordering rule will be created. Now, when the scheduler runs automatically each day, a transfer will be created for each reordering rule that has been triggered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:144 +msgid "To manually trigger reordering rules, start from the :menuselection:`Inventory` module and select :menuselection:`Operation --> Run Scheduler`, then click the green :guilabel:`Run Scheduler` button in the pop-up that appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/warehouse_replenishment_transfer.rst:148 +msgid "After the scheduler runs, a delivery order and receipt will be created for the outgoing and incoming warehouses, respectively. Both the delivery order and receipt should be processed using the same method as detailed above." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting.rst:5 +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting.rst:3 msgid "Reporting" msgstr "" @@ -14393,7 +15095,7 @@ msgid "Inventory adjustments do **not** create |SVLs|; only items purchased from msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:54 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:70 msgid "Generate reports" msgstr "" @@ -14515,53 +15217,53 @@ msgid "Display *Moves History* page of to-do deliveries that reserved the produc msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:58 -msgid ":icon:`fa-refresh` :guilabel:`Replenishment`: access the :doc:`reordering rules <../../product_management/product_replenishment/reordering_rules>` page to replenish products at the specific location." +msgid ":icon:`fa-refresh` :guilabel:`Replenishment`: access the :doc:`reordering rules <../replenishment/reordering_rules>` page to replenish products at the specific location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:61 msgid "In the upper-left corner of the page, click the the :guilabel:`New` button to make an :doc:`inventory adjustment <../inventory_management/count_products>` to record quantities of a certain product at a specific :guilabel:`Location`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:66 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:65 msgid "To view products, quantities, and their locations for a specified date, click the :guilabel:`Inventory At Date` button (also located in the upper-left corner of the page). Select a date and time in the :guilabel:`Inventory at Date` field, then click :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:73 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:72 msgid "After learning how to :ref:`navigate the locations dashboard `, it can be used to create and share different reports." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:76 msgid "A few common reports that can be created using the :guilabel:`Locations` dashboard are detailed below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:80 msgid "Dead stock report" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:83 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:82 msgid "To get list of expired items, also referred to as *dead stock*, follow these steps:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:85 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:114 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:113 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:142 msgid "Go to :menuselection:`Inventory app --> Reporting --> Locations`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:86 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:144 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:143 msgid "Then, click the |down| icon to the right of the :guilabel:`Search...` bar to reveal a drop-down list of :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorite` options." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:88 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:87 msgid "Enable the :guilabel:`Internal Locations` and :guilabel:`Expiration Alerts` option under the :guilabel:`Filters` section." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:90 msgid "The report now displays a list of expired products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:93 msgid "This report can also be generated from the :ref:`Lot and Serials Numbers ` page, accessed by going to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." msgstr "" @@ -14569,23 +15271,23 @@ msgstr "" msgid "Show a list of products whose expiration dates have exceeded today." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:104 msgid "Stranded inventory report" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:107 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:106 msgid "Businesses using multi-step flows in the *Inventory* or *Manufacturing* apps, may have *stranded* items, which are products not in their proper storage locations, due to human error. Use this report to periodically check transfer locations (e.g. *WH/Input*, *WH/Pre-Processing*) to ensure items are moved to their intended storage locations, and accurately recorded in the database." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:112 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:111 msgid "To get a list of items that might be sitting idly in storage, follow these steps:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:114 msgid "In the :guilabel:`Search...` bar, begin typing the name of the location where products are intended to be moved to, such as `WH/Input`, or `WH/Packing`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:116 msgid "Select the :guilabel:`Search Location for:` [location name] option from the resulting drop-down menu that appears beneath the :guilabel:`Search...` bar." msgstr "" @@ -14593,15 +15295,15 @@ msgstr "" msgid "Show search result for the location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:124 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:123 msgid "The report now displays a list of products at the transit location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:127 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:126 msgid "Searching `Input` in :guilabel:`Location` shows a list of products at a *WH/Input* location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:129 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:128 msgid "The list shows `500` quantities of `Chicken`, which is alarming if not refrigerated soon after reception. The stranded inventory report helps identify items that have been idling in non-storage locations." msgstr "" @@ -14609,19 +15311,19 @@ msgstr "" msgid "Show items stored at a specific location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:138 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:137 msgid "Inventory discrepancy report" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:140 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:139 msgid "To generate a report of items that have been moved since the last :doc:`inventory audit <../inventory_management/cycle_counts>`, follow these steps:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:146 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:145 msgid "Enable the :guilabel:`Internal Locations` and :guilabel:`Conflicts` option from the :guilabel:`Filters` section." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:148 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:147 msgid "The report now displays items whose quantities have changed since the last cycle count." msgstr "" @@ -14629,7 +15331,7 @@ msgstr "" msgid "Show items from the *Conflicts* filter in the report." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:154 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:153 msgid "Click the :icon:`fa-history` :guilabel:`History` button to view inventory transfers, including receipts and deliveries, that have occurred since the inventory adjustment." msgstr "" @@ -14791,7 +15493,7 @@ msgid ":guilabel:`Category`: group records by product category. To configure the msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:84 -msgid ":guilabel:`Batch Transfer`: group records by :doc:`batch <../advanced_operations_warehouse/batch_transfers>`." +msgid ":guilabel:`Batch Transfer`: group records by :doc:`batch <../../shipping_receiving/picking_methods/batch>`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:87 @@ -14890,7 +15592,7 @@ msgid ":guilabel:`History`: access the stock move history of the product, displa msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:55 -msgid ":guilabel:`Replenishment`: access the :doc:`reordering rules <../../product_management/product_replenishment/reordering_rules>` page for the product to create or manage methods of procuring the product." +msgid ":guilabel:`Replenishment`: access the :doc:`reordering rules <../replenishment/reordering_rules>` page for the product to create or manage methods of procuring the product." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:58 @@ -14950,7 +15652,7 @@ msgid ":guilabel:`Can be Expensed`: show items that can be expensed. Only availa msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:110 -msgid ":doc:`../../product_management/product_tracking/type`" +msgid ":doc:`../../product_management/configure/type`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:114 @@ -14958,7 +15660,7 @@ msgid "The :guilabel:`Group By` section allows users to add pre-made and custom msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:117 -msgid ":guilabel:`Product Type`: group items by :doc:`product type <../../product_management/product_tracking/type>`." +msgid ":guilabel:`Product Type`: group items by :doc:`product type <../../product_management/configure/type>`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:119 @@ -16998,7 +17700,7 @@ msgid ":doc:`Analytic distribution <../../../finance/accounting/reporting/analyt msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:228 -msgid ":doc:`Lead times <../../inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates>`" +msgid ":doc:`Lead times <../../inventory/warehouses_storage/replenishment/lead_times>`" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:-1 @@ -17666,6 +18368,501 @@ msgstr "" msgid "The Done button for a work order on a manufacturing order." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:3 +msgid "Allocation reports" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:11 +msgid "When fulfilling sales orders (SOs), or sourcing components for manufacturing orders (MOs), it is sometimes necessary to prioritize one |SO| or |MO| over another. In situations where there is insufficient stock on-hand to fulfill every |SO| or |MO|, ensuring that products and components are reserved for priority orders is essential." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:16 +msgid "In Odoo *Manufacturing*, allocation reports are used on |MOs| to assign products to specific sales orders |SOs|, or components to specific |MOs|. This ensures the products or components are available for those orders, and are not used by mistake." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:23 +msgid "To use allocation reports, the *Allocation Report for Manufacturing Orders* feature **must** be enabled. To do so, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the checkbox next to :guilabel:`Allocation Report for Manufacturing Orders`. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:28 +msgid "For products that are sold, it is also necessary to configure them so they can be included in |SOs|. To do so, begin by navigating to :menuselection:`Inventory --> Products --> Products`, and select a product. Under the :guilabel:`Product Name` field on the product form, make sure that the :guilabel:`Can Be Sold` checkbox is ticked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:34 +msgid "Allocate products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:36 +msgid "To allocate products or components from an |MO| to an |SO|, or to a different |MO|, begin by navigating to :menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`. Click :guilabel:`New` to create a new |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:40 +msgid "On the |MO| form, select a product in the :guilabel:`Product` field, and specify the quantity to be produced in the :guilabel:`Quantity` field. Finally, click :guilabel:`Confirm` to confirm the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:43 +msgid "The rest of the allocation workflow depends on the current on-hand quantity of the product being manufactured, and whether or not there are any |SOs| or |MOs| which require the product, but have not already been allocated units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:47 +msgid "If there **are** existing |SOs| and |MOs| that require the product, **and** there are too few units of the product on-hand to fulfill those orders, then an :icon:`fa-list` :guilabel:`Allocation` smart button appears at the top of the page as soon as the |MO| is confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:51 +msgid "If there **are** existing |SOs| and |MOs| that require the product, **and** there are enough units of the product on-hand to fulfill those orders, then the :icon:`fa-list` :guilabel:`Allocation` smart button only appears at the top of the page once the |MO| has been marked as done, by clicking :guilabel:`Produce All`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:-1 +msgid "The Allocation smart button at the top of an MO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:61 +msgid "If there **are not** any existing |SOs| and |MOs| that require the product, the :icon:`fa-list` :guilabel:`Allocation` smart button does not appear, even when the |MO| has been marked as done." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:64 +msgid "Click the :icon:`fa-list` :guilabel:`Allocation` smart button to open the :guilabel:`MRP Reception Report` for the |MO|. This report lists open delivery orders or |MOs|, depending on the type of product produced in the original |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:69 +msgid "Allocate to delivery order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:71 +msgid "If the |MO| contains a finished product, the report lists any open delivery orders for which quantities of the product have yet to be reserved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:75 +msgid "An |MO| is created to produce three units of a *rocking chair*. Clicking the :guilabel:`Allocation` smart button on the |MO| opens an allocation report that lists open delivery orders that require one or more rocking chairs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:79 +msgid "Click the :guilabel:`Assign All` button to the right of a specific order to assign products for each quantity required to fulfill that order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:83 +msgid "If an order requires one quantity of four units of the product, and one quantity of one unit of the product, clicking :guilabel:`Assign All` assigns five units of the product to fulfill both quantities." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:87 +msgid "Alternatively, click :guilabel:`Assign` next to a specific quantity to only assign products to that quantity, and not any others in the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:91 +msgid "If an order requires one quantity of four units of the product, and one quantity of one unit of the product, clicking :guilabel:`Assign` next to the quantity of one unit assigns a product to that quantity, but leaves the quantity of four units without any products assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:-1 +msgid "The MRP Reception Report for an MO containing finished products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:100 +msgid "Allocate to MO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:102 +msgid "If the |MO| contains a component, the report lists any open |MOs| for which quantities of the component have yet to be reserved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:106 +msgid "An |MO| is created to produce three units of *wood*, which is used as a component for the *rocking chair* product. Clicking the :guilabel:`Allocation` smart button on the |MO| opens an allocation report that lists open rocking chair |MOs| that require one or more pieces of wood." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:110 +msgid "Click the :guilabel:`Assign All` or :guilabel:`Assign` button to the right of a specific |MO| to assign components to that |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:-1 +msgid "The MRP Reception Report for an MO containing components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:118 +msgid "Unassign products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:120 +msgid "After assigning products to a quantity within a delivery order, or components to an |MO|, the :guilabel:`Assign` button turns into an :guilabel:`Unassign` button. Click :guilabel:`Unassign` to unreserve the assigned products from that quantity, making them available for other quantities." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:125 +msgid "Print labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:127 +msgid "After clicking :guilabel:`Assign All` or :guilabel:`Assign`, the :guilabel:`Print Labels` or :guilabel:`Print Label` button to the right of either button becomes selectable. Selecting either button generates and downloads a PDF document with one label for each product that was assigned. These labels are used to designate each product as being reserved for that specific order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/allocation.rst:-1 +msgid "The assignment labels generated by clicking Print Labels or Print Label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:3 +msgid "Overall equipment effectiveness" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:9 +msgid "In Odoo's *Manufacturing* app, *overall equipment effectiveness* (OEE) represents the amount of time a work center is fully productive. |OEE| is displayed as a percentage of the total time a work center is active." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:13 +msgid "Fully productive time is considered to be time when the work center is operational **and** processing work orders that have not exceeded their *expected duration*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:16 +msgid "|OEE| helps manufacturing teams understand the efficiency of work centers, and the causes of manufacturing downtime." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:20 +msgid "Since |OEE| tracks work center productivity, using it requires enabling the work centers feature in the settings of the Manufacturing app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:23 +msgid "To do so, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the checkbox next to :guilabel:`Work Orders`, under the :guilabel:`Operations` heading. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:28 +msgid "Efficiency standards" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:30 +msgid "For |OEE| to accurately reflect the percentage of fully productive time for a work center, the work center **must** be properly configured with the correct productivity metrics. These include the work center's *time efficiency*, *capacity*, and *OEE target*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:35 +msgid "Time efficiency" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:37 +msgid "Time efficiency represents the efficiency of a work center when processing work orders, and is represented as a percentage. A time efficiency value of 100% signifies that the work center processes work orders at the speed of the expected duration, as listed on a product's |BoM|. A value less than or greater than 100% signifies that the work center processes work orders slower or faster than an operation's expected duration, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:43 +msgid "To set the time efficiency for a work center, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`, and select a work center. On the :guilabel:`General Information` tab, enter a numerical value in the :guilabel:`Time Efficiency` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:48 +msgid "Manufacturing a *chair* product requires two operations: *cut* and *assemble*. The product's |BoM| lists an expected duration of 30 minutes for each operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:51 +msgid "The cut operation is carried out at the *cut station* work center, which has a time efficiency value of 50%. This means it takes twice as long to complete the operation, for a total time of one hour." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:55 +msgid "The assemble operation is carried out at the *assembly line* work center, which has a time efficiency value of 200%. This means it takes half as long to complete the operation, for a total time of 15 minutes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:60 +msgid "Capacity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:62 +msgid "Capacity represents how many units of a product can be produced in parallel at a work center. The duration of work orders for multiple units increases or decreases, based on how many units the work center can handle." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:66 +msgid "To set the capacity for a work center, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`, and select a work center. On the :guilabel:`General Information` tab, enter a numerical value in the :guilabel:`Capacity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:71 +msgid "A *drill station* work center has a capacity of one unit. An |MO| is confirmed for 10 units of a *chair*, a product manufactured using the drill station." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:74 +msgid "Since there are ten times as many units to produce than the work center can handle at once, the operation time is ten times the duration listed on the product's |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:78 +msgid "|OEE| target" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:80 +msgid "The |OEE| target is the goal for how much of a work center's operating time should be fully productive time. It is displayed as a percentage, and should only be set as high as `100%`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:83 +msgid "To set the |OEE| target for a work center, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings --> Work Centers`, and select a work center. On the :guilabel:`General Information` tab, enter a numerical value of `100.00` or less in the :guilabel:`OEE Target` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:88 +msgid "Calculating |OEE|" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:90 +msgid "|OEE| is represented as a percentage value between zero and 100. The value signifies the amount of time that a work center was fully productive. The remainder signifies the amount of time that the work center was operating at less than full efficiency. This can occur for a number of reasons, including *reduced speed*, *material availability*, and *equipment failure*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:96 +msgid "Fully productive time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:98 +msgid "For a work center to be considered fully productive, it must be able to receive work orders, have the components necessary to process work orders, and be operating within the expected duration of the work order it is processing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:103 +msgid "An *assembly line* work center is not blocked, and receives a work order to assemble a *bicycle*. The required components are available, so production begins as soon as they are picked and delivered to the work center. The work order has an expected duration of 30 minutes, and is completed in 27 minutes. All of this time is considered fully productive time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:109 +msgid "Reduced speed" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:111 +msgid "When a work center is operating at reduced speed, it means that it is processing a work order that has exceeded its expected duration. While the work center may be operational, this is not considered fully productive time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:116 +msgid "A *cutting station* work center receives a work order to cut boards for a *table*. The expected duration of the work order is 15 minutes. The work order ends up taking 18 minutes to complete. The work center is considered to have been operating at reduced speed during the three minutes that exceeded the expected duration." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:122 +msgid "Material availability" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:124 +msgid "Material availability refers to situations where a work center is able to accept a work order, but the required components are not available. This can occur because the components are not in stock, or are reserved for a different order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:129 +msgid "Manufacturing of a *bench* requires 20 units of *wood*. A manufacturing order (MO) is confirmed for 10 units of the bench, but there is not enough wood in stock to begin manufacturing. The time it takes to acquire the wood is recorded as material availability downtime." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:134 +msgid "Equipment failure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:136 +msgid "Equipment failure signifies any period of time when a work center is unusable due to maintenance issues with its equipment. This can be due to equipment breaking down, or when a work center is shut down for scheduled maintenance. In these cases, a work center can be blocked using a :doc:`maintenance request <../../maintenance/maintenance_requests>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:142 +msgid "The drill at a *drill station* work center breaks down, causing the work center to be unusable. A maintenance request is created to fix the drill, and the work center is blocked from receiving work orders. It takes two hours to fix the drill, and make the work center available again. This two-hour period is recorded as equipment failure downtime." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:148 +msgid "|OEE| reporting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:150 +msgid "To view |OEE| reporting metrics for every work center, navigate to :menuselection:`Manufacturing app --> Reporting --> Overall Equipment Effectiveness`. This page shows the metrics for each work center with |OEE| data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:154 +msgid "Alternatively, to see |OEE| reporting metrics for a single work center, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`, and select a work center. At the top of the work center's form, click the :icon:`fa-pie-chart` :guilabel:`OEE` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:158 +msgid "By default, the main |OEE| reporting page shows data in a bar chart, while the page for a specific work center shows it in a pie chart. To select a different chart type on either page, click the :icon:`fa-bar-chart` :guilabel:`(bar chart)`, :icon:`fa-line-chart` :guilabel:`(line chart)`, or :icon:`fa-pie-chart` :guilabel:`(pie chart)` button above the displayed chart." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:163 +msgid "It is also possible to see |OEE| data in a pivot view, or a list displaying each time entry, by clicking the :icon:`oi-view-pivot` :guilabel:`(pivot view)` or :icon:`oi-view-list` :guilabel:`(list view)` buttons at the top-right corner of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/oee.rst:-1 +msgid "The dashboard of the OEE report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:3 +msgid "Production analysis" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:8 +msgid "The *Production Analysis* report provides statistics about products manufactured using Odoo's *Manufacturing* app. The report is useful when trying to understand production costs, manufacturing durations, and other important statistics about manufactured products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:12 +msgid "To open the Production Analysis report, navigate to :menuselection:`Manufacturing app --> Reporting --> Production Analysis`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:16 +msgid "The :guilabel:`Production Analysis` report is one of many reports available across the Odoo app suite. This documentation only covers the measures specific to the :guilabel:`Production Analysis` report, along with a few use case examples." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:20 +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:21 +msgid "For a full overview of the basic features available in most Odoo reports, see the documentation on :doc:`reporting essentials <../../../essentials/reporting>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:24 +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:25 +msgid "Measures" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:26 +msgid "*Measures* are the datasets that can be selected in the :guilabel:`Production Analysis` report. Each dataset represents a specific statistic about |MOs| in the database. Choose a measure by clicking the :guilabel:`Measures` :icon:`fa-caret-down` button, and selecting one of the options from the drop-down menu:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:31 +msgid "The options displayed in the :guilabel:`Measures` :icon:`fa-caret-down` drop-down menu, and the order they appear in, differ depending on the filters, groupings, and comparisons enabled in the :guilabel:`Search...` bar. By default, the available measures appear as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:35 +msgid ":guilabel:`Average Employee Cost/Unit`: the average cost paid to employees to produce one unit of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:37 +msgid ":guilabel:`By-Products Total Cost`: the total value of all by-products created by manufacturing the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:39 +msgid ":guilabel:`Component Cost/Unit`: the average cost of the components required to produce one unit of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:41 +msgid ":guilabel:`Cost/Unit`: the average cost of producing one unit of the product, including component, employee, operation, and subcontracting costs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:43 +msgid ":guilabel:`Duration of Operations/Unit`: the average total duration of operations required to produce one unit of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:45 +msgid ":guilabel:`Quantity Demanded`: the total number of units of the product included in |MOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:46 +msgid ":guilabel:`Quantity Produced`: the total number of units of the product that have actually been produced." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:48 +msgid ":guilabel:`Total Component Cost`: the total amount spent on the product's components, across every |MO| for the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:50 +msgid ":guilabel:`Total Cost`: the total amount spent manufacturing every unit of the product produced so far." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:52 +msgid ":guilabel:`Total Duration of Operations`: the cumulative duration of every operation completed while manufacturing the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:54 +msgid ":guilabel:`Total Employee Cost`: the cumulative amount paid to employees to manufacture the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:56 +msgid ":guilabel:`Total Operation Cost`: the cumulative amount spent on operations required to produce the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:58 +msgid ":guilabel:`Total Operation Cost/Unit`: the average cost of the operations required to produce one unit of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:60 +msgid ":guilabel:`Total Subcontracting Cost`: the cumulative amount paid to subcontractors to produce the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:62 +msgid ":guilabel:`Total Subcontracting Cost/Unit`: the average cost of engaging a subcontractor to produce one unit of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:64 +msgid ":guilabel:`Yield Percentage (%)`: the total quantity of the product produced versus the total quantity demanded, represented as a percentage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:66 +msgid ":guilabel:`Count`: the total count of |MOs| created for the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:69 +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:51 +msgid "Only one measure can be selected at a time when one of the :icon:`fa-area-chart` :guilabel:`(graph view)` options is enabled. However, multiple measures, and varying group-by criteria (on the x and y axes), can be selected when using the :icon:`oi-view-pivot` :guilabel:`(pivot table)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:75 +msgid "Use case: compare products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:77 +msgid "One of the best uses for the :guilabel:`Production Analysis` report is comparing statistics about two or more products. This is accomplished by entering the products into the :guilabel:`Search...` bar, then selecting the necessary measure, filter, and grouping, to see the desired data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:82 +msgid "Toy manufacturer *Tommy's Toys* is trying to reduce their manufacturing operation costs. To accomplish this, they have decided to identify redundant products and cease manufacturing the ones with higher operational costs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:86 +msgid "Two of the toys that have been singled out for analysis are the *pogo stick* and *moon shoes*. Tommy's Toys believes these two toys are so similar that they can stop manufacturing one, without significantly impacting their product offering." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:90 +msgid "To compare operation costs for the toys, business analyst Mike opens the :menuselection:`Manufacturing` app, and navigates to the :guilabel:`Production Analysis` page. In the :guilabel:`Search...` bar, he enters the names of both products. Then, he opens the :guilabel:`Search...` bar drop-down menu, and clicks :guilabel:`Product` in the :guilabel:`Group By` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:96 +msgid "Below the :guilabel:`Search...` bar, Mike clicks on the :guilabel:`Measures` :icon:`fa-caret-down` drop-down menu, and selects the :guilabel:`Total Operation Cost/Unit` option. Finally, he selects the :icon:`fa-bar-chart` :guilabel:`(bar chart)` graph type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:100 +msgid "With these options selected, the :guilabel:`Production Analysis` report shows a bar chart for the current year, with one bar for each product, signifying the average operation cost for one unit of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:104 +msgid "With this data, Mike is able to see that the average operation cost for the moon shoes is almost twice the cost of the pogo stick. Using this insight, Tommy's Toys decides to cease production of moon shoes, thus lowering their average cost of manufacturing operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:0 +msgid "The bar chart comparing the operation costs of the pogo stick and moon shoes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:113 +msgid "Use case: compare time periods" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:115 +msgid "The :guilabel:`Production Analysis` report can also be used to compare data for two different time periods. This is accomplished using the options in the :guilabel:`Comparison` section of the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:120 +msgid "Furniture company *Fanny's Furnishings* wants to compare their production costs for the first and second quarters of 2024, to see which products they spent the most money producing in each quarter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:124 +msgid "To compare the two time periods, shop floor supervisor Adam opens the :menuselection:`Manufacturing` app, and navigates to the :guilabel:`Production Analysis` page. He begins by selecting the :icon:`fa-pie-chart` :guilabel:`(pie chart)` graph type option at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:130 +msgid "The :guilabel:`Comparison` feature is meant to be used with the :icon:`fa-pie-chart` :guilabel:`(pie chart)` graph type, or the :icon:`oi-view-pivot` :guilabel:`(pivot)` view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:133 +msgid "A :guilabel:`Comparison` option can still be selected with the other view types enabled, but doing so does not change the way data is displayed on the report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:136 +msgid "Next, Adam selects the :guilabel:`Total Cost` option from the :guilabel:`Measures` :icon:`fa-caret-down` drop-down menu. This option displays the total amount spent producing each product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:140 +msgid "In the :guilabel:`Search...` bar drop-down menu, he leaves the :guilabel:`2024` filter enabled in the :guilabel:`End Date` section, and enables the :guilabel:`Q2` filter as well. With both of these time periods selected, the pie chart shows data for the second quarter of 2024." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:144 +msgid "Finally, Adam selects the :guilabel:`End Date: Previous Period` option in the :guilabel:`Comparison` section of the :guilabel:`Search...` bar. Doing so causes the pie chart to be split into an inner circle, and an outer ring." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:148 +msgid "The outer ring shows data for the selected time period, quarter two of 2024. The inner circle shows data for the previous time period, quarter one of 2024." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:152 +msgid "If :guilabel:`End Date: Previous Year` is selected instead of :guilabel:`End Date: Previous Period`, the inner circle shows data for the selected time period, one *year* previous." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:155 +msgid "In the case of this example, it would show data for quarter two of 2023." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:157 +msgid "Using this report, Adam can see that the products with the highest total cost for quarter two are the *bicycle* and *tricycle*. On the other hand, in quarter one, the *roller skates* had the highest total cost." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/reporting/production_analysis.rst:0 +msgid "The pie chart view of the Production Analysis report, with a comparison filter enabled." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor.rst:5 msgid "Shop Floor" msgstr "" @@ -18583,12 +19780,6 @@ msgstr "" msgid "Once the :guilabel:`Subcontracting` setting is enabled, it is also necessary to properly configure the subcontracted product, and the product's |BoM|." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:35 -#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:51 -#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:53 -msgid "Configure product" -msgstr "" - #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:37 msgid "To configure a product for basic subcontracting, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product, or create a new one by clicking :guilabel:`New`." msgstr "" @@ -19252,134 +20443,6 @@ msgstr "" msgid "Workflows" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:3 -msgid "Allocation reports" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:11 -msgid "When fulfilling sales orders (SOs), or sourcing components for manufacturing orders (MOs), it is sometimes necessary to prioritize one |SO| or |MO| over another. In situations where there is insufficient stock on-hand to fulfill every |SO| or |MO|, ensuring that products and components are reserved for priority orders is essential." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:16 -msgid "In Odoo *Manufacturing*, allocation reports are used on |MOs| to assign products to specific sales orders |SOs|, or components to specific |MOs|. This ensures the products or components are available for those orders, and are not used by mistake." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:23 -msgid "To use allocation reports, the *Allocation Report for Manufacturing Orders* feature **must** be enabled. To do so, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the checkbox next to :guilabel:`Allocation Report for Manufacturing Orders`. Then, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:28 -msgid "For products that are sold, it is also necessary to configure them so they can be included in |SOs|. To do so, begin by navigating to :menuselection:`Inventory --> Products --> Products`, and select a product. Under the :guilabel:`Product Name` field on the product form, make sure that the :guilabel:`Can Be Sold` checkbox is ticked." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:34 -msgid "Allocate products" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:36 -msgid "To allocate products or components from an |MO| to an |SO|, or to a different |MO|, begin by navigating to :menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`. Click :guilabel:`New` to create a new |MO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:40 -msgid "On the |MO| form, select a product in the :guilabel:`Product` field, and specify the quantity to be produced in the :guilabel:`Quantity` field. Finally, click :guilabel:`Confirm` to confirm the |MO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:43 -msgid "The rest of the allocation workflow depends on the current on-hand quantity of the product being manufactured, and whether or not there are any |SOs| or |MOs| which require the product, but have not already been allocated units." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:47 -msgid "If there **are** existing |SOs| and |MOs| that require the product, **and** there are too few units of the product on-hand to fulfill those orders, then an :icon:`fa-list` :guilabel:`Allocation` smart button appears at the top of the page as soon as the |MO| is confirmed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:51 -msgid "If there **are** existing |SOs| and |MOs| that require the product, **and** there are enough units of the product on-hand to fulfill those orders, then the :icon:`fa-list` :guilabel:`Allocation` smart button only appears at the top of the page once the |MO| has been marked as done, by clicking :guilabel:`Produce All`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:-1 -msgid "The Allocation smart button at the top of an MO." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:61 -msgid "If there **are not** any existing |SOs| and |MOs| that require the product, the :icon:`fa-list` :guilabel:`Allocation` smart button does not appear, even when the |MO| has been marked as done." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:64 -msgid "Click the :icon:`fa-list` :guilabel:`Allocation` smart button to open the :guilabel:`MRP Reception Report` for the |MO|. This report lists open delivery orders or |MOs|, depending on the type of product produced in the original |MO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:69 -msgid "Allocate to delivery order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:71 -msgid "If the |MO| contains a finished product, the report lists any open delivery orders for which quantities of the product have yet to be reserved." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:75 -msgid "An |MO| is created to produce three units of a *rocking chair*. Clicking the :guilabel:`Allocation` smart button on the |MO| opens an allocation report that lists open delivery orders that require one or more rocking chairs." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:79 -msgid "Click the :guilabel:`Assign All` button to the right of a specific order to assign products for each quantity required to fulfill that order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:83 -msgid "If an order requires one quantity of four units of the product, and one quantity of one unit of the product, clicking :guilabel:`Assign All` assigns five units of the product to fulfill both quantities." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:87 -msgid "Alternatively, click :guilabel:`Assign` next to a specific quantity to only assign products to that quantity, and not any others in the order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:91 -msgid "If an order requires one quantity of four units of the product, and one quantity of one unit of the product, clicking :guilabel:`Assign` next to the quantity of one unit assigns a product to that quantity, but leaves the quantity of four units without any products assigned." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:-1 -msgid "The MRP Reception Report for an MO containing finished products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:100 -msgid "Allocate to MO" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:102 -msgid "If the |MO| contains a component, the report lists any open |MOs| for which quantities of the component have yet to be reserved." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:106 -msgid "An |MO| is created to produce three units of *wood*, which is used as a component for the *rocking chair* product. Clicking the :guilabel:`Allocation` smart button on the |MO| opens an allocation report that lists open rocking chair |MOs| that require one or more pieces of wood." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:110 -msgid "Click the :guilabel:`Assign All` or :guilabel:`Assign` button to the right of a specific |MO| to assign components to that |MO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:-1 -msgid "The MRP Reception Report for an MO containing components." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:118 -msgid "Unassign products" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:120 -msgid "After assigning products to a quantity within a delivery order, or components to an |MO|, the :guilabel:`Assign` button turns into an :guilabel:`Unassign` button. Click :guilabel:`Unassign` to unreserve the assigned products from that quantity, making them available for other quantities." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:125 -msgid "Print labels" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:127 -msgid "After clicking :guilabel:`Assign All` or :guilabel:`Assign`, the :guilabel:`Print Labels` or :guilabel:`Print Label` button to the right of either button becomes selectable. Selecting either button generates and downloads a PDF document with one label for each product that was assigned. These labels are used to designate each product as being reserved for that specific order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:-1 -msgid "The assignment labels generated by clicking Print Labels or Print Label." -msgstr "" - #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:3 msgid "By-Products" msgstr "" @@ -19592,7 +20655,7 @@ msgid "The |PLM| app is a great way to make changes to product |BoMs|. However, msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:150 -msgid "In such a case, the *Field Service* app can be used to schedule :doc:`onsite interventions <../../../services/field_service/onsite_interventions>`. These interventions allow service technicians (or other employees) to be sent to a customer's location to address an issue with a product." +msgid "In such a case, the *Field Service* app can be used to schedule :doc:`onsite interventions <../../../services/field_service/creating_tasks>`. These interventions allow service technicians (or other employees) to be sent to a customer's location to address an issue with a product." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:158 @@ -19825,174 +20888,6 @@ msgstr "" msgid "After the final work order for the backorder |MO| has been completed, the |MO| can be closed by clicking the :guilabel:`Close Production` button at the bottom of the work order's card." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:3 -msgid "Overall equipment effectiveness" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:9 -msgid "In Odoo's *Manufacturing* app, *overall equipment effectiveness* (OEE) represents the amount of time a work center is fully productive. |OEE| is displayed as a percentage of the total time a work center is active." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:13 -msgid "Fully productive time is considered to be time when the work center is operational **and** processing work orders that have not exceeded their *expected duration*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:16 -msgid "|OEE| helps manufacturing teams understand the efficiency of work centers, and the causes of manufacturing downtime." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:20 -msgid "Since |OEE| tracks work center productivity, using it requires enabling the work centers feature in the settings of the Manufacturing app." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:23 -msgid "To do so, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the checkbox next to :guilabel:`Work Orders`, under the :guilabel:`Operations` heading. Then, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:28 -msgid "Efficiency standards" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:30 -msgid "For |OEE| to accurately reflect the percentage of fully productive time for a work center, the work center **must** be properly configured with the correct productivity metrics. These include the work center's *time efficiency*, *capacity*, and *OEE target*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:35 -msgid "Time efficiency" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:37 -msgid "Time efficiency represents the efficiency of a work center when processing work orders, and is represented as a percentage. A time efficiency value of 100% signifies that the work center processes work orders at the speed of the expected duration, as listed on a product's |BoM|. A value less than or greater than 100% signifies that the work center processes work orders slower or faster than an operation's expected duration, respectively." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:43 -msgid "To set the time efficiency for a work center, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`, and select a work center. On the :guilabel:`General Information` tab, enter a numerical value in the :guilabel:`Time Efficiency` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:48 -msgid "Manufacturing a *chair* product requires two operations: *cut* and *assemble*. The product's |BoM| lists an expected duration of 30 minutes for each operation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:51 -msgid "The cut operation is carried out at the *cut station* work center, which has a time efficiency value of 50%. This means it takes twice as long to complete the operation, for a total time of one hour." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:55 -msgid "The assemble operation is carried out at the *assembly line* work center, which has a time efficiency value of 200%. This means it takes half as long to complete the operation, for a total time of 15 minutes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:60 -msgid "Capacity" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:62 -msgid "Capacity represents how many units of a product can be produced in parallel at a work center. The duration of work orders for multiple units increases or decreases, based on how many units the work center can handle." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:66 -msgid "To set the capacity for a work center, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`, and select a work center. On the :guilabel:`General Information` tab, enter a numerical value in the :guilabel:`Capacity` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:71 -msgid "A *drill station* work center has a capacity of one unit. An |MO| is confirmed for 10 units of a *chair*, a product manufactured using the drill station." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:74 -msgid "Since there are ten times as many units to produce than the work center can handle at once, the operation time is ten times the duration listed on the product's |BoM|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:78 -msgid "|OEE| target" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:80 -msgid "The |OEE| target is the goal for how much of a work center's operating time should be fully productive time. It is displayed as a percentage, and should only be set as high as `100%`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:83 -msgid "To set the |OEE| target for a work center, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings --> Work Centers`, and select a work center. On the :guilabel:`General Information` tab, enter a numerical value of `100.00` or less in the :guilabel:`OEE Target` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:88 -msgid "Calculating |OEE|" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:90 -msgid "|OEE| is represented as a percentage value between zero and 100. The value signifies the amount of time that a work center was fully productive. The remainder signifies the amount of time that the work center was operating at less than full efficiency. This can occur for a number of reasons, including *reduced speed*, *material availability*, and *equipment failure*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:96 -msgid "Fully productive time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:98 -msgid "For a work center to be considered fully productive, it must be able to receive work orders, have the components necessary to process work orders, and be operating within the expected duration of the work order it is processing." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:103 -msgid "An *assembly line* work center is not blocked, and receives a work order to assemble a *bicycle*. The required components are available, so production begins as soon as they are picked and delivered to the work center. The work order has an expected duration of 30 minutes, and is completed in 27 minutes. All of this time is considered fully productive time." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:109 -msgid "Reduced speed" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:111 -msgid "When a work center is operating at reduced speed, it means that it is processing a work order that has exceeded its expected duration. While the work center may be operational, this is not considered fully productive time." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:116 -msgid "A *cutting station* work center receives a work order to cut boards for a *table*. The expected duration of the work order is 15 minutes. The work order ends up taking 18 minutes to complete. The work center is considered to have been operating at reduced speed during the three minutes that exceeded the expected duration." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:122 -msgid "Material availability" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:124 -msgid "Material availability refers to situations where a work center is able to accept a work order, but the required components are not available. This can occur because the components are not in stock, or are reserved for a different order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:129 -msgid "Manufacturing of a *bench* requires 20 units of *wood*. A manufacturing order (MO) is confirmed for 10 units of the bench, but there is not enough wood in stock to begin manufacturing. The time it takes to acquire the wood is recorded as material availability downtime." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:134 -msgid "Equipment failure" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:136 -msgid "Equipment failure signifies any period of time when a work center is unusable due to maintenance issues with its equipment. This can be due to equipment breaking down, or when a work center is shut down for scheduled maintenance. In these cases, a work center can be blocked using a :doc:`maintenance request <../../maintenance/maintenance_requests>`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:142 -msgid "The drill at a *drill station* work center breaks down, causing the work center to be unusable. A maintenance request is created to fix the drill, and the work center is blocked from receiving work orders. It takes two hours to fix the drill, and make the work center available again. This two-hour period is recorded as equipment failure downtime." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:148 -msgid "|OEE| reporting" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:150 -msgid "To view |OEE| reporting metrics for every work center, navigate to :menuselection:`Manufacturing app --> Reporting --> Overall Equipment Effectiveness`. This page shows the metrics for each work center with |OEE| data." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:154 -msgid "Alternatively, to see |OEE| reporting metrics for a single work center, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`, and select a work center. At the top of the work center's form, click the :icon:`fa-pie-chart` :guilabel:`OEE` smart button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:158 -msgid "By default, the main |OEE| reporting page shows data in a bar chart, while the page for a specific work center shows it in a pie chart. To select a different chart type on either page, click the :icon:`fa-bar-chart` :guilabel:`(bar chart)`, :icon:`fa-line-chart` :guilabel:`(line chart)`, or :icon:`fa-pie-chart` :guilabel:`(pie chart)` button above the displayed chart." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:163 -msgid "It is also possible to see |OEE| data in a pivot view, or a list displaying each time entry, by clicking the :icon:`oi-view-pivot` :guilabel:`(pivot view)` or :icon:`oi-view-list` :guilabel:`(list view)` buttons at the top-right corner of the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:-1 -msgid "The dashboard of the OEE report." -msgstr "" - #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:3 msgid "Scrap during manufacturing" msgstr "" @@ -21650,127 +22545,167 @@ msgid "Advanced" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:3 -msgid "Analyze the performance of your purchases" +msgid "Purchase Analysis report" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:5 -msgid "If your company regularly purchases products, you have several reasons to track and analyze your performance. The insights gathered can help you to better forecast and plan your future orders. For example, you can assess if your business is dependent on particular vendors, and the data can help you negotiate discounts on prices." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:11 -msgid "Generate customized reports" +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:8 +msgid "The *Purchase Analysis* report provides statistics about products purchased using Odoo's **Purchase** app. This data is useful for gaining a deeper understanding of key metrics related to purchase orders (POs), including the quantity of products ordered and received, the amount of time it takes to receive purchased products, and more." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:13 -msgid "Go to *Reporting* to access the purchase analysis. Simply by accessing the reporting dashboard, you can get a quick overview of your actual performance. By default, the reporting dashboard displays a line chart presenting the untaxed amount of your purchase orders per day, and below it, key metrics and a pivot table." +msgid "To open the Purchase Analysis report, navigate to :menuselection:`Purchase app --> Reporting --> Purchase`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:-1 -msgid "Reporting dashboard in Odoo Purchase" +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:17 +msgid "The :guilabel:`Purchase Analysis` report is one of many reports available across the Odoo app suite. This documentation only covers the measures specific to the :guilabel:`Purchase Analysis` report, along with a few use case examples." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:22 -msgid "While the data initially presented is useful, there are several tools and features you can use to get even more insights on your purchases." +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:27 +msgid "*Measures* refer to the various datasets that can be displayed on the :guilabel:`Purchase Analysis` report, with each dataset representing a key statistic about |POs| or products. To choose a measure, click the :guilabel:`Measures` :icon:`fa-caret-down` button, and select one of the options from the drop-down menu:" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:26 -msgid "Use filters to select the data you need" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:28 -msgid "Odoo offers several default filters you can use and combine by clicking on *Filters*. When you select one or several filters, Odoo looks for all the orders that match at least one of the filters you have chosen and populates the chart, key metrics, and pivot table with the data. The pre-configured filters are:" +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:32 +msgid ":guilabel:`# of Lines`: The number of |PO| order lines, across all |POs|." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:33 -msgid "All *Requests for Quotation*" +msgid ":guilabel:`Average Cost`: The average cost of |POs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:34 +msgid ":guilabel:`Days to Confirm`: The number of days it takes to confirm a |PO|." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:35 -msgid "All *Purchase Orders*, except canceled ones" +msgid ":guilabel:`Days to Receive`: The number of days it takes to receive the products in a |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:36 +msgid ":guilabel:`Gross Weight`: The total weight of purchased products." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:37 -msgid "*Confirmation Date Last Year* includes all orders that were confirmed the previous year, canceled purchase orders included" +msgid ":guilabel:`Qty Billed`: The quantity of a product (or products) for which the vendor has already been billed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:39 +msgid ":guilabel:`Qty Ordered`: The quantity of a product (or products) ordered." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:40 -msgid "*Order Date* includes all orders - request for quotations and purchases orders (canceled ones included) - depending on their date of creation" +msgid ":guilabel:`Qty Received`: The quantity of an ordered product (or products) received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:41 +msgid ":guilabel:`Qty to be Billed`: The quantity of an ordered product (or products) for which the vendor has yet to be billed." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:43 -msgid "*Confirmation Date* includes all confirmed orders, canceled ones included, depending on their date of confirmation" +msgid ":guilabel:`Total`: The total amount spent, including tax." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:47 -msgid "When you have to select a period, you can use multiple years, and, with at least one year selected, multiple quarters and the three most recent months." +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:44 +msgid ":guilabel:`Untaxed Total`: The total amount spent, excluding tax. This measure is selected by default." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:51 -msgid "If you use the *Order Date* or *Confirmation Date* filters, the *Comparison* feature appears next to *Filters*. It enables you to compare the period you filtered with the previous one." +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:46 +msgid ":guilabel:`Volume`: The total volume of ordered products, for products which are measured by volume." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:-1 -msgid "Reporting filters in Odoo Purchase" +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:48 +msgid ":guilabel:`Count`: The total count of |POs|." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:59 -msgid "Add custom filters" +msgid "Use case: determine days to receive products from each vendor" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:61 -msgid "Thanks to the 31 filtering options to choose from, the possibilities of your customizing your dataset are almost limitless. Go to :menuselection:`Filters --> Add Custom Filter`, specify the condition the filtering option should meet (e.g. *is equal to*, *contains*, etc.), and click on *Apply*. If you want to select orders matching several conditions simultaneously (*and* operator), repeat the process to add another custom filter. If you want to use the *or* operator, don't click on *Apply*, and click on *Add a condition* instead. Once you have added all the desired filtering options, click on *Apply*." +msgid "One possible use case for the :guilabel:`Purchase Analysis` report is determining how long each vendor takes to deliver purchased items. This allows companies to make better informed decisions about which vendors they want to purchase from." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:-1 -msgid "Custom reporting filter in Odoo Purchase" +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:66 +msgid "A local bike shop, *Bike Haus*, sells high-quality unicycles, bicycles, tricycles, and all the accessories needed to ride and maintain them. They purchase their inventory from a few different vendors, and then sell those products on to customers through their storefront." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:70 +msgid "Recently, Bike Haus has decided to have their purchasing manager, David, look into how long it has taken each of their vendors to deliver the items they've purchased during the current year, 2024." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:74 -msgid "To avoid having to recreate custom filters every time, save them by clicking on :menuselection:`Favorites --> Save current search --> Save`. The customized search filter can then be accessed by clicking on *Favorites* or can even be set as the default filter when you open the reporting dashboard." +msgid "David starts by navigating to :menuselection:`Purchase app --> Reporting --> Purchase`, and selecting the :icon:`fa-bar-chart` (bar chart) graph type at the top of the report." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:80 -msgid "Measure exactly what you need" +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:77 +msgid "Next, he clicks the :icon:`fa-caret-down` :guilabel:`(toggle)` button on the right of the search bar to open its drop-down menu. In the :guilabel:`Confirmation Date` filter section, he makes sure that **only** the :guilabel:`2024` filter is enabled. Then, he selects the :guilabel:`Vendor` option in the :guilabel:`Group By` section, before clicking away from the drop-down menu to close it." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:82 -msgid "Before selecting what you want to measure, you need to decide whether you prefer using the graph view or the pivot view. By default, the dashboard presents both views. However, the measures you select won't be applied to both views. You can access each view separately by clicking on the icons at the top right of the dashboard." +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:83 +msgid "Finally, David clicks on the :guilabel:`Measures` :icon:`fa-caret-down` drop-down menu, and selects the :guilabel:`Days to Receive` option." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:-1 -msgid "Switch reporting view in Odoo Purchase" +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:86 +msgid "With all of these options enabled, the :guilabel:`Purchase Analysis` report shows a bar chart, with one bar for each vendor, representing the average number of days it takes to receive products purchased from the vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:92 -msgid "Visualize your data" +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:90 +msgid "Using this data, David can see that it takes Bike Friends over 4.5 days, on average, to deliver purchased products. This is more than four times the amount of time it takes any other vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:94 -msgid "You can transform the main graph in just a click by selecting one of the three charts: bar, line or pie. Fourteen different measures are available, but you can only use one at a time. However, you can group the measure using one or several of the 19 *Groups*." +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:93 +msgid "Based on these findings, David makes the decision to reduce the quantity of products purchased from Bike Friends." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:-1 -msgid "Reporting graph view in Odoo Purchase" +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:0 +msgid "The Purchase report, showing the average days to receive products from vendors." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:102 -msgid "For bar and line charts, the selected measure is your y-axis, and the first group you select is used to create the x-axis. Adding more group adds additional lines (line chart) or transforms your bar chart into a stacked bar chart. For pie charts, the more groups you select, the more slices are displayed." +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:101 +msgid "Use case: compare vendor POs for two time periods" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:103 +msgid "Another use for the :guilabel:`Purchase Analysis` report is to compare key statistics about |POs| for two different time periods, for a specific vendor. By doing so, it is easy to understand how purchases from the vendor have increased or decreased." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:108 -msgid "Explore your data" +msgid "Following the :ref:`previous example `, it has been one month since Bike Haus decided to reduce the quantity of products purchased from Bike Friends, one of their retailers. Bike Haus' purchasing manager, David, wants to understand the impact this decision has had on the amount of money they have spent on Bike Friends products." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:110 -msgid "The pivot table view enables you to explore your data in great detail. Unlike the graph view, the pivot table enables you to add several measures at the same time. By clicking on *Measures* or on the **+** sign in the *Total* column, you can add as many as you want, each assigned to a new column. By clicking on the **+** sign in the *Total* row, you can add *Groups*. If you click on a group's **+** sign, you can add a sub-group, and so on." +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:113 +msgid "David starts by navigating to :menuselection:`Purchase app --> Reporting --> Purchase`. Then, he selects the :icon:`oi-view-pivot` :guilabel:`(pivot table)` option at the top of the screen." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:-1 -msgid "Pivot table view in Odoo Purchase" +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:116 +msgid "In the search bar, he types `Bike Friends`, and clicks :guilabel:`Enter`, so the report only shows data for purchases from Bike Friends." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:121 -msgid "You can insert your pivot table's data directly in the Spreadsheet app or export it as an Excel file." +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:119 +msgid "Then, David clicks the :icon:`fa-caret-down` :guilabel:`(toggle)` button on the right of the search bar to open its drop-down menu. In the :guilabel:`Confirmation Date` field, he leaves the :guilabel:`June` and :guilabel:`2024` filters enabled. He also selects :guilabel:`Confirmation Date: Previous Period` in the :guilabel:`Comparison` section, before clicking away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:125 +msgid "Next, David clicks on the :guilabel:`Measures` :icon:`fa-caret-down` drop-down menu. He leaves the :guilabel:`Total` and :guilabel:`Untaxed Total` datasets enabled, and disables the :guilabel:`Order` and :guilabel:`Count` datasets." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:129 +msgid "Finally, David clicks the :icon:`fa-minus-square-o` :guilabel:`Total` button above the rows on the pivot table, and selects the :guilabel:`Product` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:132 +msgid "With all of these options configured, the :guilabel:`Purchase Analysis` report shows a pivot table comparing purchase data for the current month, June, with the previous month, May." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:135 +msgid "The pivot table is broken down into two main columns: one for the untaxed total spent, and one for the taxed total spent. These columns are further broken down into three smaller columns: the amount spent in May, the amount spent in June, and the variation between the two months, represented as a percentage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:140 +msgid "On the left side of the pivot table, one row is shown for each product purchased from Bike Friends during June. Using this report, David is able to see that Bike Haus has spent much less money on products purchased from Bike Friends, compared to the previous month." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:0 +msgid "The Purchase report, comparing the amount spent at a vendor." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:3 @@ -22711,6 +23646,7 @@ msgid "Draft bill created" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:158 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:186 msgid ":doc:`manage`" msgstr "" @@ -22984,6 +23920,214 @@ msgstr "" msgid ":doc:`control_bills`" msgstr "" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:3 +msgid "Requests for quotation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:12 +msgid "Odoo's requests for quotation (RFQs) feature in the **Purchase** app standardizes ordering products from multiple vendors with varying prices and delivery times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:15 +msgid "|RFQs| are documents companies send to vendors requesting product pricing. In Odoo, once the vendor approves the |RFQ|, the purchase order (PO) is confirmed to align on lead times and pricing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:24 +msgid "To auto-populate product information and prices on an |RFQ|, configure products by going to :menuselection:`Purchase app --> Products --> Products`. Select an existing product, or create a new one by selecting :guilabel:`New`. Doing so opens the product form, where various sales and purchasing data can be configured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:29 +msgid "To configure purchasable products, tick the :guilabel:`Can be purchased` checkbox, under the product name. Then, go to the :guilabel:`Inventory` tab, and enable the :guilabel:`Buy` route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:-1 +msgid "Required configuration for purchasable products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:37 +msgid "Vendor pricelist" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:39 +msgid "In the :guilabel:`Purchase` tab of the product form, input the vendor and their price, to have this information auto-populate on an |RFQ| each time the product is listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:42 +msgid "Default columns include :guilabel:`Quantity`, :guilabel:`Price`, and :guilabel:`Delivery Lead Time`, but other columns like, :guilabel:`Product Variant` or :guilabel:`Discounts`, can also be enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:45 +msgid "To enable or disable columns, click the :icon:`oi-settings-adjust` :guilabel:`(additional options)` icon on the right side of the header row to reveal a drop-down menu of additional columns that can be added (or removed) from the :guilabel:`Purchase` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:50 +msgid "Alternatively, prices and delivery lead times for existing products can be added in bulk by going to :menuselection:`Purchase app --> Configuration --> Vendor Pricelists`. Click :guilabel:`New` in the top-left corner. In the :guilabel:`Vendor` section of the pricelist form that appears, add the product information as it pertains to the vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:56 +msgid "Order products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:58 +msgid "With products and prices configured, follow these steps to create and send |RFQs| to make purchases for the company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:62 +msgid "|RFQ| dashboard" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:64 +msgid "To get started, navigate to :menuselection:`Purchase app --> Orders --> Requests for Quotation`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:66 +msgid "The :guilabel:`Requests for Quotation` dashboard displays an overview of the company's |RFQs|, |POs|, and their status. The top of the screen breaks down all |RFQs| in the company, as well as individual ones (where the user is the buyer) with a summary of their status." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:70 +msgid "The top-right corner also provides a quick report of the company's recent purchases by total value, lead times, and number of |RFQs| sent." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:73 +msgid "Additionally, the dashboard includes buttons for:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:75 +msgid ":guilabel:`To Send`: orders in the |RFQ| stage that have not been sent to the vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:76 +msgid ":guilabel:`Waiting`: |RFQs| that have been sent by email, and are waiting on vendor confirmation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:77 +msgid ":guilabel:`Late`: |RFQs| or |POs| where the :guilabel:`Order Deadline` has passed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:-1 +msgid "RFQ dashboard with orders and order statuses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:83 +msgid "In addition to various view options, the :guilabel:`Requests for Quotation` dashboard provides :guilabel:`Filters` and :guilabel:`Group By` options, accessible via the search bar drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:87 +msgid ":doc:`../../../essentials/search`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:90 +msgid "Create new |RFQ|" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:92 +msgid "To create a new |RFQ|, click the :guilabel:`New` button on the top-left corner of the :guilabel:`Requests for Quotation` dashboard to reveal a new |PO| form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:95 +msgid "Start by assigning a :guilabel:`Vendor`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:97 +msgid "The :guilabel:`Vendor Reference` field points to the sales and delivery order numbers sent by the vendor. This comes in handy once products are received, and the |PO| needs to be matched to the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:101 +msgid "The :guilabel:`Blanket Order` field refers to long-term purchase agreements on recurring orders with set pricing. To view and configure blanket orders, head to :menuselection:`Purchase app --> Orders --> Purchase agreements`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:105 +msgid "The :guilabel:`Currency` can be changed, if purchasing products from a vendor in another country." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:107 +msgid "Next, configure an :guilabel:`Order Deadline`, which is the date by which the vendor must confirm their agreement to supply the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:111 +msgid "After the :guilabel:`Order Deadline` is exceeded, the |RFQ| is marked as late, but the products can still be ordered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:114 +msgid ":guilabel:`Expected Arrival` is automatically calculated based on the :guilabel:`Order Deadline` and vendor lead time. Tick the checkbox for :guilabel:`Ask confirmation` to ask for signage at delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:118 +msgid "With the :doc:`Storage Locations feature <../../inventory/warehouses_storage/inventory_management/use_locations>` activated, the :guilabel:`Deliver to` field appears, with options for the order shipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:122 +msgid "Select the receiving warehouse address here, or select :guilabel:`Dropship` to indicate that this order is to be shipped directly to the end customer. When :guilabel:`Dropship` is selected, the :guilabel:`Dropship address` field is enabled. Contact names auto-populate here from the **Contacts** app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:128 +msgid "Products tab" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:130 +msgid "In the :guilabel:`Products` tab, add the products to be ordered. Click :guilabel:`Add a product`, and type in the product name, or select the item from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:133 +msgid "To create a new product and add it, type the new product name in the :guilabel:`Product` column, select :guilabel:`Create [product name]` from the resulting drop-down menu, and manually add the unit price. Or, select :guilabel:`Create and edit...` to be taken to the product form for that new item." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:138 +msgid ":guilabel:`Catalog` can also be selected to navigate to a product menu from the chosen vendor. From here, products can be added to the cart." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:142 +msgid "To make adjustments to products and prices, access the product form by clicking the :icon:`oi-arrow-right` :guilabel:`(right arrow)` icon that becomes available upon hovering over the :guilabel:`Product` name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:147 +msgid "Send |RFQ|" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:149 +msgid "Clicking :guilabel:`Send by Email` reveals a :guilabel:`Compose Email` pop-up window, with a :guilabel:`Purchase: Request for Quotation` template loaded, ready to send to the vendor's email address (configured in the **Contacts** app)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:153 +msgid "After crafting the desired message, click :guilabel:`Send`. Once sent, the |RFQ| moves to the :guilabel:`RFQ Sent` stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:156 +msgid "Clicking :guilabel:`Print RFQ` downloads a PDF of the |RFQ|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:159 +msgid "Confirm order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:161 +msgid "Clicking :guilabel:`Confirm Order` directly transforms the |RFQ| into an active |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:164 +msgid "Odoo tracks communications on each order through the chatter of the |PO| form. This shows the emails sent between the user and the contact, as well as any internal notes and activities. Messages, notes, and activities can also be logged on the chatter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:168 +msgid "Once an |RFQ| is confirmed, it creates a |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:170 +msgid "On the new |PO|, the :guilabel:`Order Deadline` field changes to :guilabel:`Confirmation Date`, which displays the date and time the user confirmed the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:173 +msgid "Depending on the user's chosen configuration in the **Purchase** app settings, a *vendor bill* is created once products have been ordered or received. For more information, refer to the documentation on :doc:`managing vendor bills `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:178 +msgid "After an order is placed, clicking :guilabel:`Receive Products` records the reception of new products into the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst:182 +msgid "With the **Inventory** app installed, confirming a |PO| automatically creates a receipt document, with the product information and expected arrival dates automatically populated." +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/products.rst:5 msgid "Products" msgstr "" @@ -23129,7 +24273,7 @@ msgid "This rule is deleted upon confirmation of the purchase order (PO) generat msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/products/temporary_reordering.rst:27 -msgid ":doc:`../../inventory/product_management/product_replenishment/reordering_rules`" +msgid ":doc:`../../inventory/warehouses_storage/replenishment/reordering_rules`" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/products/temporary_reordering.rst:33 diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index 093c16300..8164c8f58 100644 --- a/locale/sources/marketing.pot +++ b/locale/sources/marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 13:30+0000\n" +"POT-Creation-Date: 2024-08-21 11:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -74,7 +74,7 @@ msgstr "" #: ../../content/applications/marketing/email_marketing.rst:64 #: ../../content/applications/marketing/email_marketing.rst:736 -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:420 +#: ../../content/applications/marketing/social_marketing/social_posts.rst:52 #: ../../content/applications/marketing/surveys.rst:145 msgid "List view" msgstr "" @@ -129,7 +129,7 @@ msgstr "" #: ../../content/applications/marketing/email_marketing.rst:91 #: ../../content/applications/marketing/email_marketing.rst:709 -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:391 +#: ../../content/applications/marketing/social_marketing/social_posts.rst:23 msgid "Kanban view" msgstr "" @@ -182,7 +182,7 @@ msgid "View of the three-dot drop-down menu on the Odoo Email Marketing dashboar msgstr "" #: ../../content/applications/marketing/email_marketing.rst:127 -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:404 +#: ../../content/applications/marketing/social_marketing/social_posts.rst:36 msgid "Calendar view" msgstr "" @@ -355,7 +355,7 @@ msgid "When all desired options are configured, click :guilabel:`Save` to save t msgstr "" #: ../../content/applications/marketing/email_marketing.rst:274 -#: ../../content/applications/marketing/events.rst:89 +#: ../../content/applications/marketing/events.rst:99 msgid "Settings" msgstr "" @@ -1123,7 +1123,7 @@ msgid "Using a mailing list that contains outdated contact information, or malfo msgstr "" #: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:105 -msgid "Mailings sent using a *From* email address that differs from the sender's domain are likely to bounce with certain email providers due to failing :ref:`DMARC authentication `." +msgid "Mailings sent using a *From* email address that differs from the sender's domain are likely to bounce with certain email providers due to failing :ref:`DMARC authentication `." msgstr "" #: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:108 @@ -1594,7 +1594,7 @@ msgid ":doc:`../marketing_automation`" msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:3 -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:15 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:15 msgid "Mailing lists" msgstr "" @@ -1643,7 +1643,7 @@ msgid "Clicking :guilabel:`Send Mailing` reveals a separate page with a blank em msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:40 -msgid "Clicking :guilabel:`Send SMS` reveals a separate page with a blank SMS template form, which can be filled out by following steps explained in the :doc:`SMS essentials doc <../sms_marketing/essentials/sms_essentials>`." +msgid "Clicking :guilabel:`Send SMS` reveals a separate page with a blank SMS template form, which can be filled out by following steps explained in the :doc:`SMS Marketing doc <../sms_marketing>`." msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:44 @@ -1924,7 +1924,7 @@ msgid "Once they've chosen the appropriate opt-out reason from the options prese msgstr "" #: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:61 -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:102 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:102 msgid "Blacklist" msgstr "" @@ -2009,22 +2009,22 @@ msgid "Events" msgstr "" #: ../../content/applications/marketing/events.rst:7 -msgid "Explore the various aspects of the Odoo *Events* detailed dashboard, and useful settings, that can be utilized to generate and gather valuable data about events (and their attendees), which can then be used to improve decision-making and event-planning." +msgid "Explore the various aspects of the Odoo **Events** detailed dashboard, and useful settings, that can be utilized to generate and gather valuable data about events (and their attendees), which can then be used to improve decision-making and event-planning." msgstr "" #: ../../content/applications/marketing/events.rst:12 msgid "`Odoo Tutorials: Events `_" msgstr "" -#: ../../content/applications/marketing/events.rst:47 +#: ../../content/applications/marketing/events.rst:57 msgid "Events dashboard" msgstr "" -#: ../../content/applications/marketing/events.rst:49 -msgid "When the *Events* application is opened, Odoo reveals the main :guilabel:`Events` dashboard, which can be viewed in a number of different ways. Those different view options are accessible from the :guilabel:`Events` dashboard in the upper-right corner, via a series of view-related icon buttons." +#: ../../content/applications/marketing/events.rst:59 +msgid "When the **Events** application is opened, Odoo reveals the main :guilabel:`Events` dashboard, which can be viewed in a number of different ways. Those different view options are accessible from the :guilabel:`Events` dashboard in the upper-right corner, via a series of view-related icon buttons." msgstr "" -#: ../../content/applications/marketing/events.rst:53 +#: ../../content/applications/marketing/events.rst:63 msgid "By default, the :guilabel:`Events` dashboard is displayed in the :icon:`oi-view-kanban` :guilabel:`Kanban` view, which is populated with a variety of pipeline stages." msgstr "" @@ -2032,19 +2032,19 @@ msgstr "" msgid "Overview of events setting with the kanban view in Odoo Events." msgstr "" -#: ../../content/applications/marketing/events.rst:60 +#: ../../content/applications/marketing/events.rst:70 msgid "This view showcases all the events in the database in their respective stages. By default, the stages are: :guilabel:`New`, :guilabel:`Booked`, :guilabel:`Announced`, :guilabel:`Ended`, and :guilabel:`Cancelled`." msgstr "" -#: ../../content/applications/marketing/events.rst:65 +#: ../../content/applications/marketing/events.rst:75 msgid "The :guilabel:`Ended` and :guilabel:`Cancelled` stages are folded, by default, and located to the right of the other stages." msgstr "" -#: ../../content/applications/marketing/events.rst:68 +#: ../../content/applications/marketing/events.rst:78 msgid "On each event card, find the scheduled date of the event, the name of the event, the location, the number of expected :guilabel:`Attendees`, any scheduled activities related to the event, the status of the event, and the person responsible for the event." msgstr "" -#: ../../content/applications/marketing/events.rst:72 +#: ../../content/applications/marketing/events.rst:82 msgid "To quickly add a new event to a pipeline, click the :icon:`fa-plus` :guilabel:`(plus)` icon at the top of the stage to which the event should be added to reveal a blank Kanban card to fill out." msgstr "" @@ -2052,71 +2052,71 @@ msgstr "" msgid "Typical blank kanban card to fill out in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events.rst:79 +#: ../../content/applications/marketing/events.rst:89 msgid "In this blank Kanban card, enter the name of :guilabel:`Event`, along with the start and end :guilabel:`Date` and time." msgstr "" -#: ../../content/applications/marketing/events.rst:82 +#: ../../content/applications/marketing/events.rst:92 msgid "Then, either click :guilabel:`Add` to add it to the stage and edit it later, or click :guilabel:`Edit` to add the event to stage and edit its configurations on a separate page." msgstr "" -#: ../../content/applications/marketing/events.rst:85 +#: ../../content/applications/marketing/events.rst:95 msgid "Each event card can be dragged-and-dropped into any stage on the Kanban pipeline, providing easy organizational access." msgstr "" -#: ../../content/applications/marketing/events.rst:91 -msgid "To access the event settings and feature options in Odoo *Events*, navigate to :menuselection:`Events app --> Configuration --> Settings`. From here, tick the checkboxes beside the desired settings and/or features, and click :guilabel:`Save` to activate them." +#: ../../content/applications/marketing/events.rst:101 +msgid "To access the event settings and feature options in Odoo **Events**, navigate to :menuselection:`Events app --> Configuration --> Settings`. From here, tick the checkboxes beside the desired settings and/or features, and click :guilabel:`Save` to activate them." msgstr "" -#: ../../content/applications/marketing/events.rst:96 +#: ../../content/applications/marketing/events.rst:106 msgid "Events section" msgstr "" -#: ../../content/applications/marketing/events.rst:98 -msgid "In the :guilabel:`Events` section of the :guilabel:`Settings` page, there are selectable features that can be enabled to add various elements to events created with the Odoo *Events* application." +#: ../../content/applications/marketing/events.rst:108 +msgid "In the :guilabel:`Events` section of the :guilabel:`Settings` page, there are selectable features that can be enabled to add various elements to events created with the Odoo **Events** application." msgstr "" #: ../../content/applications/marketing/events.rst:-1 msgid "The Events section on the Odoo Events settings page in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events.rst:105 +#: ../../content/applications/marketing/events.rst:115 msgid "The :guilabel:`Schedule & Tracks` feature allows users to manage and publish a schedule with tracks for events. *Tracks* is a catch-all term that refers to talks, lectures, demonstrations, presentations, and other similar elements that users may choose to include as part of an event." msgstr "" -#: ../../content/applications/marketing/events.rst:109 +#: ../../content/applications/marketing/events.rst:119 msgid "When the :guilabel:`Schedule & Tracks` feature is enabled, two additional fields appear beneath it: :guilabel:`Live Broadcast` and :guilabel:`Event Gamification`." msgstr "" -#: ../../content/applications/marketing/events.rst:112 +#: ../../content/applications/marketing/events.rst:122 msgid "The :guilabel:`Live Broadcast` feature lets users air tracks online, via a *YouTube* integration." msgstr "" -#: ../../content/applications/marketing/events.rst:114 +#: ../../content/applications/marketing/events.rst:124 msgid "The :guilabel:`Event Gamification` feature lets users share a quiz after any event track, in order for attendees to gauge how much they learned from the track they just saw/heard. Companies can also benefit from this feature, in that the subsequent responses and results of the quizzes can help determine where a company's strengths and weaknesses are, when it comes to their presentations." msgstr "" -#: ../../content/applications/marketing/events.rst:119 +#: ../../content/applications/marketing/events.rst:129 msgid "Next, is the :guilabel:`Online Exhibitors` feature. This feature allows users to display sponsors and exhibitors on event pages, which can serve as a valuable incentive to encourage partners and businesses to participate in the event." msgstr "" -#: ../../content/applications/marketing/events.rst:123 +#: ../../content/applications/marketing/events.rst:133 msgid "The :guilabel:`Jitsi Server Domain` field represents an external conferencing service that is integrated with Odoo. It is what is used to create and host virtual conferences, community rooms, and other similar elements for events." msgstr "" -#: ../../content/applications/marketing/events.rst:127 +#: ../../content/applications/marketing/events.rst:137 msgid "The :guilabel:`Community Chat Rooms` feature allows users to create virtual conference rooms for event attendees, providing them with a centralized place to meet and discuss anything related to the event." msgstr "" -#: ../../content/applications/marketing/events.rst:131 +#: ../../content/applications/marketing/events.rst:141 msgid "Lastly, there is the :guilabel:`Booth Management` feature. This feature provides users with the ability to create and manage event booths and booth reservations. When enabled, users can create different booth tiers, with individual price points, and sell them to interested parties." msgstr "" -#: ../../content/applications/marketing/events.rst:136 +#: ../../content/applications/marketing/events.rst:146 msgid "Registration section" msgstr "" -#: ../../content/applications/marketing/events.rst:138 +#: ../../content/applications/marketing/events.rst:148 msgid "The :guilabel:`Registration` section of the :guilabel:`Settings` page provides selectable settings that are directly related to event registration." msgstr "" @@ -2124,19 +2124,19 @@ msgstr "" msgid "The Registration section in the Odoo Events settings page in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events.rst:145 +#: ../../content/applications/marketing/events.rst:155 msgid "The :guilabel:`Tickets` setting allows users to sell event tickets, via standard sales orders." msgstr "" -#: ../../content/applications/marketing/events.rst:147 +#: ../../content/applications/marketing/events.rst:157 msgid "The :guilabel:`Online Ticketing` setting creates a selectable *Event Ticket* product type on product forms, which provides users with the ability to sell event tickets online, via their website/eCommerce store." msgstr "" -#: ../../content/applications/marketing/events.rst:152 +#: ../../content/applications/marketing/events.rst:162 msgid "Attendance section" msgstr "" -#: ../../content/applications/marketing/events.rst:154 +#: ../../content/applications/marketing/events.rst:164 msgid "In the :guilabel:`Attendance` section of the :guilabel:`Settings` page, there is a selectable setting that is directly related to how attendees can attend/enter the event." msgstr "" @@ -2144,69 +2144,124 @@ msgstr "" msgid "The Attendance section in the Odoo Events Settings page in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events.rst:161 +#: ../../content/applications/marketing/events.rst:171 msgid "The :guilabel:`Use Event Barcode` setting, when activated, enables barcode (and QR code) scanning for attendees to enter the event. This provides attendees with quick access, and helps Odoo users easily track, manage, and analyze all event attendees." msgstr "" -#: ../../content/applications/marketing/events.rst:165 +#: ../../content/applications/marketing/events.rst:175 msgid "The :guilabel:`Barcode Nomenclature` field, beneath the :guilabel:`Use Event Barcode` setting, is set to :guilabel:`Default Nomenclature`, by default, but can be changed at any time." msgstr "" -#: ../../content/applications/marketing/events.rst:169 +#: ../../content/applications/marketing/events.rst:179 #: ../../content/applications/marketing/events/create_events.rst:3 msgid "Create events" msgstr "" -#: ../../content/applications/marketing/events.rst:171 -msgid "With Odoo *Events*, events can be manually created from scratch or built off of pre-made templates. Once launched, the *Events* application then integrates with the *Website* app for the front-end promotion and registration of the event for attendees, the *Sales* app for the purchasing ability of paid tickets, and the *CRM* application through customizable lead generation rules." +#: ../../content/applications/marketing/events.rst:181 +msgid "With Odoo **Events**, events can be manually created from scratch or built off of pre-made templates." msgstr "" -#: ../../content/applications/marketing/events.rst:177 +#: ../../content/applications/marketing/events.rst:184 +msgid "Once launched, the **Events** application then integrates with the **Website** app for the front-end promotion and registration of the event for attendees, the **Sales** app for the purchasing ability of paid tickets, and the **CRM** application through customizable lead generation rules." +msgstr "" + +#: ../../content/applications/marketing/events.rst:189 msgid ":doc:`events/create_events`" msgstr "" -#: ../../content/applications/marketing/events.rst:180 +#: ../../content/applications/marketing/events.rst:192 #: ../../content/applications/marketing/events/sell_tickets.rst:3 msgid "Sell event tickets" msgstr "" -#: ../../content/applications/marketing/events.rst:182 +#: ../../content/applications/marketing/events.rst:194 msgid "Create custom ticket tiers (with various price points) for potential event attendees to choose from, directly on the event template form, under the *Tickets* tab." msgstr "" -#: ../../content/applications/marketing/events.rst:185 +#: ../../content/applications/marketing/events.rst:197 msgid "Odoo simplifies the ticket-purchasing process by providing plenty of payment method options, as well." msgstr "" -#: ../../content/applications/marketing/events.rst:189 +#: ../../content/applications/marketing/events.rst:201 msgid ":doc:`events/sell_tickets`" msgstr "" -#: ../../content/applications/marketing/events.rst:192 +#: ../../content/applications/marketing/events.rst:204 msgid "Track and manage talks" msgstr "" -#: ../../content/applications/marketing/events.rst:194 +#: ../../content/applications/marketing/events.rst:206 msgid "Discover how to access various event tracks (talks, presentations, etc.), view entire agendas, and learn how attendees can propose talks for the event." msgstr "" -#: ../../content/applications/marketing/events.rst:198 +#: ../../content/applications/marketing/events.rst:210 msgid ":doc:`events/track_manage_talks`" msgstr "" -#: ../../content/applications/marketing/events.rst:201 +#: ../../content/applications/marketing/events.rst:213 #: ../../content/applications/marketing/events/event_templates.rst:3 msgid "Event templates" msgstr "" -#: ../../content/applications/marketing/events.rst:203 -msgid "Discover the process to customize and configure event templates, which can be used to expedite the event-creation process." +#: ../../content/applications/marketing/events.rst:215 +msgid "Learn the process to customize and configure event templates, which can be used to expedite the event-creation process." msgstr "" -#: ../../content/applications/marketing/events.rst:207 +#: ../../content/applications/marketing/events.rst:219 msgid ":doc:`events/event_templates`" msgstr "" +#: ../../content/applications/marketing/events.rst:222 +#: ../../content/applications/marketing/events/event_booths.rst:3 +msgid "Event booths" +msgstr "" + +#: ../../content/applications/marketing/events.rst:224 +msgid "Explore the various ways to create, manage, and sell event booths with the Odoo **Events** application." +msgstr "" + +#: ../../content/applications/marketing/events.rst:228 +msgid ":doc:`events/event_booths`" +msgstr "" + +#: ../../content/applications/marketing/events.rst:231 +#: ../../content/applications/marketing/events/event_tracks.rst:3 +msgid "Event tracks" +msgstr "" + +#: ../../content/applications/marketing/events.rst:233 +msgid "Find out how to create, manage, and schedule different experiences (aka *Tracks*) for events with Odoo." +msgstr "" + +#: ../../content/applications/marketing/events.rst:237 +msgid ":doc:`events/event_tracks`" +msgstr "" + +#: ../../content/applications/marketing/events.rst:240 +msgid "Registration desk" +msgstr "" + +#: ../../content/applications/marketing/events.rst:242 +msgid "Grant access to event attendees quickly and easily with the Odoo **Events** *Registration Desk* feature." +msgstr "" + +#: ../../content/applications/marketing/events.rst:246 +msgid ":doc:`events/registration_desk`" +msgstr "" + +#: ../../content/applications/marketing/events.rst:249 +#: ../../content/applications/marketing/events/revenues_report.rst:3 +msgid "Revenues report" +msgstr "" + +#: ../../content/applications/marketing/events.rst:251 +msgid "Gain invaluable insight into event-related revenues with customizable reports and metrics." +msgstr "" + +#: ../../content/applications/marketing/events.rst:254 +msgid ":doc:`events/revenues_report`" +msgstr "" + #: ../../content/applications/marketing/events/create_events.rst:5 msgid "With the *Events* application, event organizers can create and configure in-person or online-only events in Odoo. Each new event contains a number of customizable options that are geared around specific event logistics, as needed per event, such as ticket sales and registration desk, booths, tracks, sponsors, rooms, and more." msgstr "" @@ -2324,82 +2379,82 @@ msgid "Then, from the resulting file explorer window, select the desired image t msgstr "" #: ../../content/applications/marketing/events/create_events.rst:104 -msgid "This :guilabel:`Twitter Wall` field **only** appears on the event form if the *Social Marketing* app is installed, and an X account has been added as a stream on the application. To learn more, check out the :doc:`Social marketing essentials <../social_marketing/essentials/social_essentials>` documentation." +msgid "This :guilabel:`Twitter Wall` field **only** appears on the event form if the *Social Marketing* app is installed, and an X account has been added as a stream on the application. To learn more, check out the :doc:`Social Marketing <../social_marketing>` documentation." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:109 +#: ../../content/applications/marketing/events/create_events.rst:108 msgid ":guilabel:`Template`: choose a pre-configured event template from the resulting drop-down menu." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:111 +#: ../../content/applications/marketing/events/create_events.rst:110 msgid "Or, create a new one directly from this field, by typing in the name of the new template, and selecting either:" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:114 +#: ../../content/applications/marketing/events/create_events.rst:113 msgid ":guilabel:`Create` (which creates the template, and can be edited later) or" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:115 +#: ../../content/applications/marketing/events/create_events.rst:114 msgid ":guilabel:`Create and edit...` (which creates the template, and reveals a separate template page to configure the template in greater detail)." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:118 +#: ../../content/applications/marketing/events/create_events.rst:117 msgid ":guilabel:`Tags`: add any corresponding tags to briefly describe the event (e.g. `Online`, `Conference`, etc.). Multiple tags can be added per event." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:122 +#: ../../content/applications/marketing/events/create_events.rst:121 msgid "Tags can be displayed on events that are listed on the website by enabling the *Show on Website* checkbox from :menuselection:`Events app --> Configuration --> Event Tag Categories`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:125 +#: ../../content/applications/marketing/events/create_events.rst:124 msgid ":guilabel:`Organizer`: designate the organizer of the event (a company, contact, or employee)." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:126 +#: ../../content/applications/marketing/events/create_events.rst:125 msgid ":guilabel:`Responsible`: designate a user in the database to be responsible for this event." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:127 +#: ../../content/applications/marketing/events/create_events.rst:126 msgid ":guilabel:`Company`: designate which company in the database to which this event is related. This field **only** appears if working in a multi-company environment. This field is auto-populated, but modifiable, and is **required**." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:130 +#: ../../content/applications/marketing/events/create_events.rst:129 msgid ":guilabel:`Website`: choose to restrict the publishing of this event to a specific website created in Odoo. If this field is left blank, the event can be published on *all* websites in the database. To learn more, refer to the :doc:`Multiple websites <../../websites/website/configuration/multi_website>` documentation." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:134 +#: ../../content/applications/marketing/events/create_events.rst:133 msgid ":guilabel:`Venue`: enter event venue details. This field pulls pertinent information from the *Contacts* application. Alternatively, :guilabel:`Venue` information can be manually added in this field, as well. At the very least, there **must** be a venue name, address, city, zip code/region, and country entered." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:138 +#: ../../content/applications/marketing/events/create_events.rst:137 msgid ":guilabel:`Exhibition Map`: if desired, click the :guilabel:`Upload your file` button to upload an image of the event venue map." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:140 +#: ../../content/applications/marketing/events/create_events.rst:139 msgid ":guilabel:`Limit Registrations`: if this checkbox is ticked, a limit to the amount of registrations is added to the event, and that desired limit amount **must** be entered in the blank field before :guilabel:`Attendees`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:143 +#: ../../content/applications/marketing/events/create_events.rst:142 msgid ":guilabel:`Badge Dimension`: select a desired paper format dimension for event badges. The options are: :guilabel:`A4 foldable`, :guilabel:`A6`, or :guilabel:`4 per sheet`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:145 +#: ../../content/applications/marketing/events/create_events.rst:144 msgid ":guilabel:`Badge Background`: if desired, click the :guilabel:`Upload your file` button to upload a custom background image for event badges." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:148 +#: ../../content/applications/marketing/events/create_events.rst:147 msgid "When the above fields in the event form have been adequately filled in, move on to the four tabs at the bottom of the event form for further customization." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:151 +#: ../../content/applications/marketing/events/create_events.rst:150 msgid "Those tabs are: :ref:`Tickets `, :ref:`Communication `, :ref:`Questions `, and :ref:`Notes `." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:158 +#: ../../content/applications/marketing/events/create_events.rst:157 msgid "Tickets tab" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:160 +#: ../../content/applications/marketing/events/create_events.rst:159 msgid "Create custom tickets (and ticket tiers) for events in the :guilabel:`Tickets` tab of an event form." msgstr "" @@ -2407,67 +2462,67 @@ msgstr "" msgid "A typical tickets tab on an event form in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:166 +#: ../../content/applications/marketing/events/create_events.rst:165 msgid "To create a ticket, click :guilabel:`Add a line` in the :guilabel:`Tickets` tab. Then, enter a name for the ticket (e.g. `Basic Ticket` or `VIP`) in the :guilabel:`Name` field." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:169 +#: ../../content/applications/marketing/events/create_events.rst:168 msgid "In the :guilabel:`Product` field, either select the pre-configured :guilabel:`Event Registration` product, or create a new one by typing in the name of the new event registration product, and then select either :guilabel:`Create` or :guilabel:`Create and edit...` from the resulting drop-down menu." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:175 +#: ../../content/applications/marketing/events/create_events.rst:174 msgid "Upon installing Odoo *Events*, a new product type, *Event Ticket*, becomes available on product forms (:menuselection:`Sales --> Products --> Products`). In order for an event registration product to be selectable in the *Tickets* tab, the event registration :guilabel:`Product Type` **must** be set to :guilabel:`Event Ticket`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:181 +#: ../../content/applications/marketing/events/create_events.rst:180 msgid "Existing event registration products can be modified directly from this field, as well, by clicking the :icon:`oi-arrow-right` :guilabel:`(right arrow)` icon, located beside the event registration product. Doing so reveals that product's form. If the *Inventory* application is installed, additional choices are available to customize for the product." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:186 +#: ../../content/applications/marketing/events/create_events.rst:185 msgid "Next, set the registration cost of the ticket in the :guilabel:`Price` field." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:189 +#: ../../content/applications/marketing/events/create_events.rst:188 msgid "The *Sales Price* defined on the event registration product's product form sets the default cost of a ticket. Modifying the :guilabel:`Price` of a ticket in the :guilabel:`Tickets` tab, sets a new registration cost of the ticket for that event." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:193 +#: ../../content/applications/marketing/events/create_events.rst:192 msgid "Next, determine a :guilabel:`Sales Start` and :guilabel:`Sales End` date in their respective fields. To do that, click into the blank field to reveal a calendar popover. From there, select the desired date and time, then click :icon:`fa-check` :guilabel:`Apply`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:197 +#: ../../content/applications/marketing/events/create_events.rst:196 msgid "Then, if desired, designate a :guilabel:`Maximum` amount of that specific ticket that can be sold." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:199 +#: ../../content/applications/marketing/events/create_events.rst:198 msgid "The :guilabel:`Taken` column populates with the number of tickets that are sold." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:201 +#: ../../content/applications/marketing/events/create_events.rst:200 msgid "Optionally, in the :guilabel:`Color` column, add a custom color to differentiate ticket badges. The selected color displays on ticket badges when printed." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:204 +#: ../../content/applications/marketing/events/create_events.rst:203 msgid "To delete any tickets from the :guilabel:`Tickets` tab, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the corresponding line for the ticket that should be deleted." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:208 +#: ../../content/applications/marketing/events/create_events.rst:207 msgid "To add an optional :guilabel:`Description` column to the :guilabel:`Tickets` tab, click the :icon:`oi-settings-adjust` :guilabel:`(additional options)` drop-down menu, located to the far-right of the column titles." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:212 +#: ../../content/applications/marketing/events/create_events.rst:211 msgid "Then, tick the checkbox beside :guilabel:`Description` from the resulting drop-down menu." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:214 +#: ../../content/applications/marketing/events/create_events.rst:213 msgid "When added, the option to add brief descriptions for each event ticket appears, which can be used to inform attendees of any perks or amenities that may coincide with specific ticket purchases." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:220 +#: ../../content/applications/marketing/events/create_events.rst:219 msgid "Communication tab" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:222 +#: ../../content/applications/marketing/events/create_events.rst:221 msgid "In the :guilabel:`Communication` tab of an event form, create various marketing communications that can be scheduled to be sent at specific intervals leading up to, and following, the event." msgstr "" @@ -2475,93 +2530,93 @@ msgstr "" msgid "Typical communication tab on an event form in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:230 +#: ../../content/applications/marketing/events/create_events.rst:229 msgid "By default, Odoo provides three separate pre-configured communications on every new event form. One is an email sent after each registration to confirm the purchase with the attendee. The other two are email event reminders that are scheduled to be sent at different time intervals leading up to the event to remind the recipient of the upcoming event." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:235 +#: ../../content/applications/marketing/events/create_events.rst:234 msgid "To add a communication in the :guilabel:`Communication` tab, click :guilabel:`Add a line`. Then, select the desired type of communication in the :guilabel:`Send` field. The options are: :guilabel:`Mail`, :guilabel:`SMS`, :guilabel:`Social Post`, or :guilabel:`WhatsApp`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:239 +#: ../../content/applications/marketing/events/create_events.rst:238 msgid "There is no limit to the number of communications that can be added in the :guilabel:`Communication` tab of an event form." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:242 +#: ../../content/applications/marketing/events/create_events.rst:241 msgid "To delete a communication from the :guilabel:`Communication` tab, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the corresponding communication line. Doing so removes the communication from the event entirely." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:247 +#: ../../content/applications/marketing/events/create_events.rst:246 msgid "The :guilabel:`Social Post` option **only** appears if the *Social Marketing* application is installed. The :guilabel:`WhatsApp` option **only** appears if the *WhatsApp Integration* module is installed." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:251 +#: ../../content/applications/marketing/events/create_events.rst:250 msgid ":doc:`WhatsApp <../../productivity/whatsapp>` templates **cannot** be edited during active configuration. A separate approval from *Meta* is required." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:255 +#: ../../content/applications/marketing/events/create_events.rst:254 msgid "Mail" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:257 +#: ../../content/applications/marketing/events/create_events.rst:256 msgid "Select an existing email template from the :guilabel:`Template` drop-down menu." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:259 +#: ../../content/applications/marketing/events/create_events.rst:258 msgid "Next, define the :guilabel:`Interval`, :guilabel:`Unit`, and :guilabel:`Trigger` from their respective drop-down fields, letting Odoo know when the communication should be sent." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:262 +#: ../../content/applications/marketing/events/create_events.rst:261 msgid "The :guilabel:`Unit` options are: :guilabel:`Immediately`, :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, and :guilabel:`Months`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:265 +#: ../../content/applications/marketing/events/create_events.rst:264 msgid "Then, select an option from the :guilabel:`Trigger` drop-down menu. The options are: :guilabel:`After each registration`, :guilabel:`Before the event`, and :guilabel:`After the event`." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:268 +#: ../../content/applications/marketing/events/create_events.rst:267 msgid "The :guilabel:`Sent` column populates with the number of sent communications. And, beside the number are different icons that appear, depending on the status of that particular communication." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:271 +#: ../../content/applications/marketing/events/create_events.rst:270 msgid "The status of *Running* is represented by a :icon:`fa-cogs` :guilabel:`(three gears)` icon. The status of *Sent* is represented by a :icon:`fa-check` :guilabel:`(checkmark)` icon. And, the status of *Scheduled* is represented by an :icon:`fa-hourglass-half` :guilabel:`(hourglass)` icon." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:276 +#: ../../content/applications/marketing/events/create_events.rst:275 msgid "To send a confirmation email an hour after an attendee registers for an event, configure the following communication:" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:279 +#: ../../content/applications/marketing/events/create_events.rst:278 msgid ":guilabel:`Interval`: `1`" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:280 +#: ../../content/applications/marketing/events/create_events.rst:279 msgid ":guilabel:`Unit`: :guilabel:`Hours`" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:281 +#: ../../content/applications/marketing/events/create_events.rst:280 msgid ":guilabel:`Trigger`: :guilabel:`After each registration`" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:284 +#: ../../content/applications/marketing/events/create_events.rst:283 msgid "Existing email templates can be modified directly from the :guilabel:`Template` drop-down menu, if necessary, by clicking the :icon:`oi-arrow-right` :guilabel:`(right arrow)` icon next to the template name. Doing so reveals a separate page where users can edit the :guilabel:`Content`, :guilabel:`Email Configuration`, and :guilabel:`Settings` of that particular email template." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:289 +#: ../../content/applications/marketing/events/create_events.rst:288 msgid "To view and manage all email templates, activate :ref:`developer-mode` and navigate to :menuselection:`Settings --> Technical --> Email: Email Templates`. Modify with caution as email templates effect all communications where the template is used." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:296 +#: ../../content/applications/marketing/events/create_events.rst:295 #: ../../content/applications/marketing/surveys/create.rst:50 #: ../../content/applications/marketing/surveys/questions.rst:20 msgid "Questions tab" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:298 +#: ../../content/applications/marketing/events/create_events.rst:297 msgid "In the :guilabel:`Questions` tab of an event form, users can create brief questionnaires for registrants to interact with, and respond to, after they register for the event." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:301 +#: ../../content/applications/marketing/events/create_events.rst:300 msgid "These questions can be focused on gathering basic information about the attendee, learning about their preferences, expectations, and other things of that nature. This information can also be used to create more detailed reporting metrics, in addition to being utilized to create specific lead generation rules." msgstr "" @@ -2569,15 +2624,15 @@ msgstr "" msgid "Typical questions tab on an event form in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:311 +#: ../../content/applications/marketing/events/create_events.rst:310 msgid "By default, Odoo provides three questions in the :guilabel:`Questions` tab for every event form. The default questions require the registrant(s) to provide their :guilabel:`Name` and :guilabel:`Email`, and make it optional to include their :guilabel:`Phone` number, as well." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:315 +#: ../../content/applications/marketing/events/create_events.rst:314 msgid "The information gathered from the :guilabel:`Questions` tab can be found on the :guilabel:`Attendees` dashboard, accessible via the :icon:`fa-users` :guilabel:`Attendees` smart button. Odoo populates individual records that contain basic information about the registrant(s), as well as their preferences." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:320 +#: ../../content/applications/marketing/events/create_events.rst:319 msgid "To add a question in the :guilabel:`Questions` tab, click :guilabel:`Add a line`. Doing so reveals a :guilabel:`Create Question` pop-up window. From here, users can create and configure their question." msgstr "" @@ -2585,91 +2640,91 @@ msgstr "" msgid "The Create Question pop-up window that appears in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:327 +#: ../../content/applications/marketing/events/create_events.rst:326 msgid "First, enter the question in the field at the top of the form. Then, decide if the question should require a :guilabel:`Mandatory Answer` and/or if Odoo should :guilabel:`Ask once per order`, by ticking their respective boxes, if desired." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:331 +#: ../../content/applications/marketing/events/create_events.rst:330 msgid "If the :guilabel:`Ask once per order` checkbox is ticked, the question will only be asked once, and its value is propogated to every attendee in the order (if multiple tickets are purchased at once). If the checkbox is *not* ticked for this setting, Odoo will present the question for every attendee that is connected to that registration." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:336 +#: ../../content/applications/marketing/events/create_events.rst:335 msgid "Next, select a :guilabel:`Question Type` option:" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:338 +#: ../../content/applications/marketing/events/create_events.rst:337 msgid ":guilabel:`Selection`: provide answer options to the question for registrants to choose from. Selectable answer options can be managed in the :guilabel:`Answers` column at the bottom of the pop-up window." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:341 +#: ../../content/applications/marketing/events/create_events.rst:340 msgid ":guilabel:`Text Input`: lets the users enter a custom response to the question in a text field." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:342 +#: ../../content/applications/marketing/events/create_events.rst:341 msgid ":guilabel:`Name`: provides registrants with a field for them to enter their name." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:343 +#: ../../content/applications/marketing/events/create_events.rst:342 msgid ":guilabel:`Email`: provides registrants with a field for them to enter their email address." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:344 +#: ../../content/applications/marketing/events/create_events.rst:343 msgid ":guilabel:`Phone`: provides registrants with a field for them to enter their phone number." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:345 +#: ../../content/applications/marketing/events/create_events.rst:344 msgid ":guilabel:`Company`: provides registrants with a field for them to enter a company they are associated with." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:348 +#: ../../content/applications/marketing/events/create_events.rst:347 msgid "Once all the desired configurations have been entered, either click :guilabel:`Save & Close` to save the question, and return to the :guilabel:`Questions` tab on the event form, or click :guilabel:`Save & New` to save the question and immediately create a new question on a new :guilabel:`Create Question` pop-up window." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:353 +#: ../../content/applications/marketing/events/create_events.rst:352 msgid "As questions are added to the :guilabel:`Questions` tab, the informative columns showcase the configurations of each question." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:356 +#: ../../content/applications/marketing/events/create_events.rst:355 msgid "The informative columns are the following:" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:358 +#: ../../content/applications/marketing/events/create_events.rst:357 msgid ":guilabel:`Title`" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:359 +#: ../../content/applications/marketing/events/create_events.rst:358 msgid ":guilabel:`Mandatory`" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:360 +#: ../../content/applications/marketing/events/create_events.rst:359 msgid ":guilabel:`Once per Order`" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:361 +#: ../../content/applications/marketing/events/create_events.rst:360 msgid ":guilabel:`Type`" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:362 +#: ../../content/applications/marketing/events/create_events.rst:361 msgid ":guilabel:`Answers` (if applicable)" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:364 +#: ../../content/applications/marketing/events/create_events.rst:363 msgid "For :guilabel:`Selection` and :guilabel:`Text Input` types, a :icon:`fa-bar-chart` :guilabel:`Stats` button appears on the right side of the question line. When clicked, Odoo reveals a separate page, showcasing the response metrics to that specific question." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:368 +#: ../../content/applications/marketing/events/create_events.rst:367 msgid "To delete any question from the :guilabel:`Questions` tab, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the corresponding question line." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:371 +#: ../../content/applications/marketing/events/create_events.rst:370 msgid "There is no limit to the number of questions that can be added in the :guilabel:`Questions` tab of an event form." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:377 +#: ../../content/applications/marketing/events/create_events.rst:376 msgid "Notes tab" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:379 +#: ../../content/applications/marketing/events/create_events.rst:378 msgid "In the :guilabel:`Notes` tab of an event form, users can leave detailed internal notes and/or event-related instructions/information for attendees." msgstr "" @@ -2677,63 +2732,59 @@ msgstr "" msgid "Typical notes tab on an event form in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:386 +#: ../../content/applications/marketing/events/create_events.rst:385 msgid "In the :guilabel:`Note` field of the :guilabel:`Notes` tab, users can leave internal notes for other event employees, like \"to-do\" lists, contact information, instructions, and so on." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:389 +#: ../../content/applications/marketing/events/create_events.rst:388 msgid "In the :guilabel:`Ticket Instructions` field of the :guilabel:`Notes` tab, users can leave specific instructions for people attending the event that appear on the attendees ticket." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:393 +#: ../../content/applications/marketing/events/create_events.rst:392 msgid "Publish events" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:395 +#: ../../content/applications/marketing/events/create_events.rst:394 msgid "Once all configurations and modifications are complete on the event form, it is time to publish the event on the website. Doing so makes the event visible to website visitors, and makes it possible for people to register for the event." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:399 +#: ../../content/applications/marketing/events/create_events.rst:398 msgid "To publish an event after all the customizations are complete, click the :icon:`fa-globe` :guilabel:`Go to Website` smart button at the top of the event form. Doing so reveals the event's web page, which can be customized like any other web page on the site, via the :guilabel:`Edit` button." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:404 +#: ../../content/applications/marketing/events/create_events.rst:403 msgid "To learn more about website design functionality and options, consult the :doc:`Building block <../../websites/website/web_design/building_blocks>` documentation." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:407 +#: ../../content/applications/marketing/events/create_events.rst:406 msgid "Once the event website is ready to be shared, click the red :guilabel:`Unpublished` toggle switch in the header menu, changing it to a green :guilabel:`Published` switch. At this point, the event web page is published, and viewable/accessible by all website visitors." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:412 +#: ../../content/applications/marketing/events/create_events.rst:411 msgid "Send event invites" msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:414 +#: ../../content/applications/marketing/events/create_events.rst:413 msgid "To send event invites to potential attendees, navigate to the desired event form, via :menuselection:`Events app --> Events`, and click into the desired event. Following this, click the :guilabel:`Invite` button in the upper-left corner of the event form." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:418 +#: ../../content/applications/marketing/events/create_events.rst:417 msgid "Doing so reveals a blank email form to fill out, as desired. To learn more about how to create and customize emails like this, refer to the :ref:`Create an email ` documentation." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:422 +#: ../../content/applications/marketing/events/create_events.rst:421 msgid "Proceed to create and customize an email message to send as an invite to potential attendees. Remember to include a link to the registration page on the event website, allowing interested recipients to quickly register." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:427 -msgid "Sending emails from Odoo is subject to a daily limit, which, by default, is 200. To learn more about daily limits, visit the :ref:`email_communication/daily_limit_mail` documentation." +#: ../../content/applications/marketing/events/create_events.rst:426 +msgid "Sending emails from Odoo is subject to a daily limit, which, by default, is 200. To learn more about daily limits, visit the :ref:`email-issues-outgoing-delivery-failure-messages-limit` documentation." msgstr "" -#: ../../content/applications/marketing/events/create_events.rst:431 +#: ../../content/applications/marketing/events/create_events.rst:430 #: ../../content/applications/marketing/events/event_tracks.rst:310 msgid ":doc:`track_manage_talks`" msgstr "" -#: ../../content/applications/marketing/events/event_booths.rst:3 -msgid "Event booths" -msgstr "" - #: ../../content/applications/marketing/events/event_booths.rst:5 msgid "The Odoo *Events* application provides users with the ability to create event booths, sell their availability, and manage their reservations." msgstr "" @@ -2758,7 +2809,7 @@ msgid "The Booth Management setting in the Odoo Events application." msgstr "" #: ../../content/applications/marketing/events/event_booths.rst:22 -msgid "When the :guilabel:`Booth Management` setting is activated, a new :doc:`Product Type <../../inventory_and_mrp/inventory/product_management/product_tracking/type>` becomes available on all product forms: *Event Booth*." +msgid "When the :guilabel:`Booth Management` setting is activated, a new :doc:`Product Type <../../inventory_and_mrp/inventory/product_management/configure/type>` becomes available on all product forms: *Event Booth*." msgstr "" #: ../../content/applications/marketing/events/event_booths.rst:26 @@ -3296,10 +3347,6 @@ msgstr "" msgid "Any of these pre-configured settings related to the selected event template chosen in the :guilabel:`Template` field on an event form can be modified, as desired." msgstr "" -#: ../../content/applications/marketing/events/event_tracks.rst:3 -msgid "Event tracks" -msgstr "" - #: ../../content/applications/marketing/events/event_tracks.rst:5 msgid "Odoo *Events* provides the ability to create, schedule, and manage talks, lectures, demonstrations, presentations, etc., which known as *Tracks* in Odoo." msgstr "" @@ -3639,6 +3686,375 @@ msgstr "" msgid "The track-related event submenu options on an event website built with Odoo Events." msgstr "" +#: ../../content/applications/marketing/events/registration_desk.rst:3 +msgid "Registration Desk" +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:5 +msgid "Use the *Registration Desk* feature in Odoo **Events** to grant access to registered event attendees as they arrive, and store attendee-related data in the reporting metrics." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:9 +msgid "Registration Desk page" +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:11 +msgid "On a mobile device (on the Odoo app or in a browser), open the :menuselection:`Events app`, and click the :guilabel:`Registration Desk` to view the :guilabel:`Registration Desk` page." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:-1 +msgid "The Registration Desk page in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:18 +msgid "At the bottom of the :guilabel:`Registration Desk` box, there are options to either :guilabel:`Scan a badge` or :guilabel:`Select Attendee`." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:22 +msgid "Scan a badge" +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:24 +msgid "Scan the codes present on event attendee badges, by navigating to :menuselection:`Events app --> Registration Desk`, and selecting the :guilabel:`Scan a badge` option." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:28 +msgid "Odoo **must** be granted access to the camera being used for the :guilabel:`Scan a badge` option to work." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:31 +msgid "Once Odoo has access to the camera, a :guilabel:`Barcode Scanner` pop-up window appears, showing the camera's point-of-view. There is also a specified view finder box present, whose size can be manually modified, accordingly, using the :icon:`fa-crop` :guilabel:`(crop)` icon." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:-1 +msgid "The Barcode Scanner window of the Registration Desk in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:39 +msgid "When the badge code is in the middle of the view finder box, the code is scanned, the :guilabel:`Barcode Scanner` pop-up window disappears, and the attendee is granted access to the event. Once the code is scanned, their attendance is logged in the Odoo **Events** app." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:43 +msgid "If the barcode being scanned is invalid, an error pop-up message appears in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:46 +msgid "Select attendee" +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:48 +msgid "Manually grant access to event attendees, by navigating to :menuselection:`Events app --> Registration Desk`, and selecting the :guilabel:`Select Attendee` option." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:51 +msgid "Odoo reveals an :guilabel:`Attendees` page, with all the attendees for every event in the database, in a default :icon:`oi-view-kanban` :guilabel:`Kanban` view." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:-1 +msgid "The Attendees page, via the Registration Desk, located in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:58 +msgid "On the :guilabel:`Attendees` page, each attendee card displays that person's name, which event they are registered to attend, their associated company (if applicable), what ticket tier they purchased (if applicable), along with two buttons: a :icon:`fa-check` :guilabel:`(checkmark)` and :icon:`fa-undo` :guilabel:`(counter-clockwise arrow)`." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:63 +msgid "To grant access to a person, marking them as attended, click the :icon:`fa-check` :guilabel:`(checkmark)` button on that attendee's card." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:66 +msgid "Click the :icon:`fa-undo` :guilabel:`(counter-clockwise arrow)` button on an attendee's card to undo the previous action." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:70 +msgid "It is recommended to use an event-specific filter on the :guilabel:`Attendees` page, via the search bar drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:73 +msgid "To do that, click the :icon:`fa-sort-desc` :guilabel:`(down arrow)` beside the seach bar to reveal a drop-down menu with :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` options." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:77 +msgid "For example, click the :guilabel:`Event` option, in the :guilabel:`Group By` column. Then, click away to remove the drop-down menu. Odoo reveals the :guilabel:`Attendees` page with event-specific columns, allowing users to locate specific event attendees." +msgstr "" + +#: ../../content/applications/marketing/events/registration_desk.rst:82 +#: ../../content/applications/marketing/events/revenues_report.rst:72 +msgid ":doc:`../../essentials/search`" +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:5 +msgid "The Odoo **Events** application creates custom reports, based on event-related data and analytics. These reports can either be focused on *Attendees* or *Revenues*." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:8 +msgid "The following documentation focuses on the reporting options related to event *Revenues*." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:11 +msgid "Revenues reporting page" +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:13 +msgid "To access the *Attendees* reporting page, navigate to :menuselection:`Events app --> Reporting --> Revenues`." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:-1 +msgid "The default view of the Revenues reporting page in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:20 +msgid "By default, the :guilabel:`Revenues` reporting page appears as a graph (a :icon:`fa-line-chart` :guilabel:`(Line Chart)` with :icon:`fa-database` :guilabel:`(Stacked)` data). The default filters, :guilabel:`Non-free tickets` and :guilabel:`Event Start Date: (current year)`, are present in the search bar." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:26 +msgid "To learn more about the various graph views (and graph view options), refer to the :ref:`Graph views ` documentation." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:29 +msgid "The :guilabel:`Revenues` reporting page can also be viewed as a :ref:`pivot table `, by clicking the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:34 +msgid "Measures" +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:36 +msgid "Choosing specific :ref:`Measures ` is a quick way to customize reporting pages." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:39 +msgid "Regardless of the chosen view, the measures on the :guilabel:`Revenues` reporting page are as follows: :guilabel:`Revenues`, :guilabel:`Untaxed Revenues`, and :guilabel:`Count`." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:43 +msgid "In the default graph view of the :guilabel:`Revenues` reporting page, only the :guilabel:`Revenues` option is set in the :guilabel:`Measures` drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:46 +msgid "In graph view, only one of the :guilabel:`Measures` can be selected at a time." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:48 +msgid "When the pivot option is selected, all :guilabel:`Measures` options are selected, by default." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:50 +msgid ":guilabel:`Revenues`: shows the revenues generated from events." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:51 +msgid ":guilabel:`Untaxed Revenues`: shows the untaxed revenues generated from events." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:52 +msgid ":guilabel:`Count`: shows the total amount of registrants who attended events." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:55 +msgid "Filters and grouping options" +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:57 +msgid "To reveal a drop-down menu of filter and grouping options to create custom reports, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` to the right of the search bar." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:60 +msgid "Doing so opens a drop-down mega menu of options organized into columns: :ref:`Filters `, :ref:`Group By `, and :ref:`Favorites `." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:65 +msgid "If a time-related option has been selected from the :guilabel:`Filters` column (e.g. the default :guilabel:`Event Start Date: (year)` filter), a :guilabel:`Comparison` column appears, with comparison options for the corresponding time-related filter option selected." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:69 +msgid "Only **one** selection can be made from the :guilabel:`Comparison` column at a time." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:75 +msgid "Filter options" +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:77 +msgid "In the :guilabel:`Filters` column of the drop-down mega menu, there are various event-related options that can be utilized to create custom reports, based on a number of specific criteria." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:80 +msgid "Multiple options in the :guilabel:`Filters` column can be selected at once." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:82 +msgid "The :guilabel:`Filters` column has the following options:" +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:84 +msgid ":guilabel:`Non-free tickets`: event tickets/registrations that were **not** free." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:85 +msgid ":guilabel:`Free`: event tickets/registrations that *were* free." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:86 +msgid ":guilabel:`Pending payment`: event tickets/registrations that were purchased, but still have payment pending." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:88 +msgid ":guilabel:`Sold`: event tickets/registrations that have been successfully sold (and paid for)." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:89 +msgid ":guilabel:`Registration Date`: Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon to reveal a list of month, quarter, and year options. Select any number of these options to view a specific periods of time and see how many registrations happened during that time." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:92 +msgid ":guilabel:`Upcoming/Running`: include revenue-related information for events that are either currently running or are going to happen in the future." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:94 +msgid ":guilabel:`Past Events`: include revenue-related information for events that have already taken place." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:96 +msgid ":guilabel:`Event Start Date`: Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon to reveal a list of month, quarter, and year options. Select any number of these options to designate event start dates to use as filters for revenue-related event data." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:99 +msgid ":guilabel:`Event End Date`: Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon to reveal a list of month, quarter, and year options. Select any number of these options to designate event end dates to use as filters for revenue-related event data." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:102 +msgid ":guilabel:`Published Events`: Select this option to show revenue-related data for published events." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:104 +msgid ":guilabel:`Add Custom Filter`: Create a custom filter to analyze event-related revenue data. To learn more, refer to the documentation on :ref:`custom filters `." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:108 +msgid "Group By options" +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:110 +msgid "In the :guilabel:`Group By` column of the drop-down mega menu, there are various event-related options to create custom groupings of data." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:113 +msgid "Multiple :guilabel:`Group By` options can be selected at once." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:115 +msgid "The :guilabel:`Group By` column has the following options:" +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:117 +msgid ":guilabel:`Event Type`: Group data based on the type of event." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:118 +msgid ":guilabel:`Event`: Organize data into individual groups, separated by events." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:119 +msgid ":guilabel:`Product`: Group data based on the event registration product." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:120 +msgid ":guilabel:`Ticket`: Group data based on the type of event ticket purchased by attendees." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:121 +msgid ":guilabel:`Registration Status`: Group data based on the status of registrations." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:122 +msgid ":guilabel:`Sale Order Status`: Group data based on the status of event-related sales orders." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:123 +msgid ":guilabel:`Customer`: Group data based on customer records." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:124 +msgid ":guilabel:`Add Custom Group`: Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon to reveal a drop-down of grouping options. To select one, click on the desired option, and Odoo adds it to the :guilabel:`Group By` column. Multiple selections can be made." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:129 +msgid "Sample report: event ticket analysis (graph)" +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:131 +msgid "The following is an example of how various filters and grouping options can create a useful analytic graph report related to event revenues. In this case, the configurations present data about sold or free tickets to published events, with the metrics separated by ticket type and event." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:-1 +msgid "The event ticket analysis sample report with unique filters and groupings in place." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:139 +msgid "To create such a report, navigate to :menuselection:`Events app --> Reporting --> Revenues`. Stay in the default graph view, but remove the default filters from the search bar." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:142 +msgid "Then, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` to the right of the search bar, to reveal the drop-down mega menu of filter and grouping options." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:145 +msgid "From here, select :guilabel:`Free` and :guilabel:`Sold` from the :guilabel:`Filters` column." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:147 +msgid "Then, since it is desired to **only** view data related to already published events, select the :guilabel:`Published Events` option in the :guilabel:`Filters` column, as well." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:150 +msgid "Next, in the :guilabel:`Group By` column, select the :guilabel:`Event` and :guilabel:`Ticket` options, **in that sequential order**. Doing so first groups the data by event, *then* by ticket type, which provides a more useful array of data to analyze." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:155 +msgid "The order in which the options are selected in the :guilabel:`Group By` column directly affects how the data is presented on the report." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:158 +msgid "From there, additional configurations can be added for more detailed data, if desired." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:160 +msgid "If no additional filters or groupings are added, Odoo presents a graphical representation of data related to all *free* or *sold* tickets for *published events*, grouped by *event*, and organized by *ticket* type." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:165 +msgid "Sample report: event type analysis (pivot table)" +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:167 +msgid "The following is an example of how various filters and grouping options can create a useful analytic pivot table report related to event revenues. In this case, the configurations present data about how much revenue different event types have generated, in order to gauge which events are the most profitable." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:-1 +msgid "The event type analysis sample report with unique filters and groupings in place." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:176 +msgid "First, navigate to :menuselection:`Events app --> Reporting --> Revenues`, and switch to the pivot table view, by clicking the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:180 +msgid "Keep the default filters (:guilabel:`Non-free tickets` and :guilabel:`Event Start Date: (year)`) in the search bar." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:183 +msgid "Next, open the :guilabel:`Measures` drop-down menu, and deselect the option for :guilabel:`Count`, because this report is only going to focus on revenues." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:186 +msgid "Then, click :icon:`fa-plus-square` :guilabel:`Total` above the column titles, and select :guilabel:`Event Type` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/events/revenues_report.rst:189 +msgid "With these configurations in place, all the revenues generated from the events (and their corresponding registrations) are displayed, organized by the event type (presented as expandable columns)." +msgstr "" + #: ../../content/applications/marketing/events/sell_tickets.rst:5 msgid "Odoo *Events* provides users with the ability to create custom event tickets (and ticket tiers), with various price points." msgstr "" @@ -3961,8 +4377,8 @@ msgid "Get started by creating a :ref:`new campaign from scratch `_" msgstr "" @@ -4004,7 +4420,7 @@ msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:81 #: ../../content/applications/marketing/marketing_automation/campaign_templates.rst:5 -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:82 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:82 msgid "Campaign templates" msgstr "" @@ -5042,7 +5458,7 @@ msgid "Once the SMS template is configured, click :guilabel:`Save & Close` to sa msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:169 -msgid ":doc:`Creating and configuring SMS templates <../sms_marketing/essentials/sms_essentials>`" +msgid ":doc:`Creating and configuring SMS templates <../sms_marketing>`" msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:174 @@ -5066,7 +5482,7 @@ msgid "Next, select the unit of time for the interval number in the *interval ty msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:192 -msgid "If the interval number is set to `0` and the interval type is set to :guilabel:`Hours`, the activity will be executed immediately after the trigger type occurs (at the next scheduled run of the :ref:`Mail: Email Queue Manager cron `)." +msgid "If the interval number is set to `0` and the interval type is set to :guilabel:`Hours`, the activity will be executed immediately after the trigger type occurs (at the next scheduled run of the :ref:`Mail: Email Queue Manager cron `)." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:199 @@ -5268,1606 +5684,1581 @@ msgstr "" msgid "Once a trigger type is selected, the :guilabel:`Create Activities` pop-up window opens to configure the child activity. The process is the same as :ref:`creating a new activity `, with the exception that the :guilabel:`Trigger` field is pre-filled with the selected trigger type, and the :guilabel:`Activity` field has the parent activity selected." msgstr "" -#: ../../content/applications/marketing/sms_marketing.rst:8 +#: ../../content/applications/marketing/sms_marketing.rst:5 msgid "SMS Marketing" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials.rst:5 -#: ../../content/applications/marketing/social_marketing/essentials.rst:5 -msgid "Essentials" +#: ../../content/applications/marketing/sms_marketing.rst:7 +msgid "Utilizing :abbr:`SMS (Short Message Service)` outreach in communication strategies can help companies expand their market reach, especially in some countries, where emails might not be very common, or even used at all." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:3 +#: ../../content/applications/marketing/sms_marketing.rst:11 +msgid "Odoo's *SMS Marketing* application can also help boost conversion rates around valuable actions, such as event registrations, free trials, purchases, etc., since text and mobile-based marketing channels typically yield higher :abbr:`CTOR (click-to-open rate)` and :abbr:`CTR (click-through rate)` outcomes." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing.rst:49 +msgid "SMS marketing dashboard" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing.rst:51 +msgid "When the application is opened, Odoo displays the main :guilabel:`SMS Marketing` dashboard, which showcases the various SMS mailings that have been created, along with pertinent information and data related to that specific message." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing.rst:55 +msgid "The :icon:`oi-view-kanban` :guilabel:`Kanban` view is the default Odoo uses when the application is opened, which provides an organized display of the SMS mailings that have been created, and what their current status is at the moment." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing.rst:60 +msgid "An :abbr:`SMS (Short Message Service)` mailing can have one of the following statuses: :guilabel:`Draft`, :guilabel:`In Queue`, :guilabel:`Sending`, or :guilabel:`Sent`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing.rst:63 +msgid "In the upper right corner of the main :guilabel:`SMS Marketing` dashboard, there are a few different view options to choose from. Each one provides a unique take on the same SMS information." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing.rst:66 +msgid "The :icon:`oi-view-list` :guilabel:`List` view provides the same useful data related to SMS mailings, but in a more traditional list layout." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing.rst:69 +msgid "The :icon:`fa-calendar` :guilabel:`Calendar` view shows when SMS mailings are scheduled or have been sent. Clicking a future date opens a blank SMS template to be scheduled for that date." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing.rst:72 +msgid "Lastly, the :icon:`fa-area-chart` :guilabel:`Graph` view visualizes that same SMS-related data in series of graphs and charts. Odoo also provides various ways to sort and group the data for more detailed analysis." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:3 +msgid "Create SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:5 +msgid "To start, click :guilabel:`Create` on the main :guilabel:`SMS Marketing` dashboard, and Odoo reveals a blank SMS template form, which can be configured in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:-1 +msgid "Creating an SMS marketing template." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:12 +msgid "First, give the mailing a :guilabel:`Subject`, which describes what the mailing is about." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:14 +msgid "Next, in the :guilabel:`Recipients` field, choose to whom this :abbr:`SMS (Short Message Service)` will be sent. By default, Odoo has :guilabel:`Mailing List` selected. If this is the desired :guilabel:`Recipients` field option, specify which mailing list Odoo should send this :abbr:`SMS (Short Message Service)` to in the :guilabel:`Select Mailing List` field." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:20 +msgid "To create (or edit) a mailing list, go to :menuselection:`Mailing Lists --> Mailing List`. There, Odoo displays all previously created mailing lists, along with various types of data related to that specific list (e.g. number of contacts, mailings, recipients, etc.)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:24 +msgid "To learn more about mailing lists and contacts, check out :doc:`mailing_lists_blacklists`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:-1 +msgid "View of the mailing list page in the SMS marketing application." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:30 +msgid "To reveal all the possible options in the :guilabel:`Recipients` field, click the field to see all the choices Odoo makes available." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:33 +msgid "When another field (other than :guilabel:`Mailing List`) is selected, the option to specify that chosen field even further becomes available — either with a default recipient filter equation that appears automatically (which can be customized to fit any business need), or, if no default recipient filter equation is present, an :guilabel:`Add Filter` button will appear." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:38 +msgid "Clicking the :guilabel:`Add Filter` button, reveals fully customizable domain rule fields, which can be configured similar to an equation. You can create multiple recipient rules, if necessary." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:41 +msgid "Then, Odoo will only send the :abbr:`SMS (Short Message Service)` to recipients who fit into whatever criteria is configured in those fields. Multiple rules can be added." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:45 +msgid "If :guilabel:`Contact` is chosen, all of the *Contacts* records in the Odoo database (vendors, customers, etc.) will receive the :abbr:`SMS (Short Message Service)`, by default — unless more specific recipient rules are entered." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:49 +msgid "For instance, the message below will only be sent to contacts in the database that are located in the United States (e.g. `Country` > `Country Name` equals `United States`), and they haven't blacklisted themselves from any mailings (e.g. `Blacklist` > `is` > `not set`)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:0 +msgid "Contact recipients on SMS marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:58 +msgid "Writing SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:60 +msgid "Enter the content of the :abbr:`SMS (Short Message Service)` in the text field, found in the :guilabel:`SMS Content` tab. Links and emojis can also be included. Beneath the text field, Odoo displays how many characters are used in the message, along with how many :abbr:`SMS (Short Message Service)` mailings it will take to deliver the complete message." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:66 +msgid "To check the price of sending an :abbr:`SMS (Short Message Service)` for a country, click on the :guilabel:`Information` icon." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:-1 +msgid "SMS price check icon." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:74 +msgid "Credits must be purchased from Odoo in order to take advantage of the *SMS Marketing* app; :abbr:`SMS (Short Message Service)` messages will not be sent without credits." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:78 +msgid "`Odoo SMS - FAQ `_" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:81 +msgid "Track links used in SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:83 +msgid "When links are used in :abbr:`SMS (Short Message Service)` messages, Odoo automatically generates link trackers to gather analytical data and metrics related to those specific links, which can be found by going to :menuselection:`Configuration --> Link Tracker`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:-1 +msgid "SMS Link Tracker page." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:92 +msgid "Adjust SMS settings" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:94 +msgid "Under the :guilabel:`Settings` tab of the SMS template, there is an option to :guilabel:`Include opt-out link`. If activated, the recipient is able to unsubscribe from the mailing list, thus avoiding all future mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:98 +msgid "An employee can be designated as the :guilabel:`Responsible` in the :guilabel:`Tracking` section of the :guilabel:`Settings` tab, as well." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:-1 +msgid "SMS Settings tab." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:106 +msgid "Send SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:108 +msgid "Once a mailing is created, choose when Odoo should deliver the message from the following options:" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:110 +msgid ":guilabel:`Send`: sends the message immediately. Consider using this option if the recipient list is highly refined, or in cases that involve fast approaching deadlines, such as a \"flash sale.\"" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:112 +msgid ":guilabel:`Schedule`: choose a day (and time) for Odoo to send the mailing. This is typically the best option for mailings related to a specific event. Such a method can also be used to promote a limited-time offer, or to help plan a company's content strategy in advance." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/create_sms.rst:115 +msgid ":guilabel:`Test`: allows for an :abbr:`SMS (Short Message Service)` to be sent to one or multiple numbers for test purposes. Remember to use a comma between phone numbers if multiple numbers are used as recipients." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:3 msgid "Mailing lists and blacklists" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:5 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:5 msgid "Creating or importing mailing lists in Odoo is very useful when curating content to specific groups of people that already share similar demographics or interests. Mailing lists are also a great way to get started if a company is migrating from another system, and already has a established audience." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:10 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:10 msgid "Moreover, providing an audience with the option to 'unsubscribe' from mailings, helps businesses maintain good customer relations, by giving recipients the power to control what they are (and aren't) sent." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:17 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:17 msgid "In the :guilabel:`SMS Marketing` app, there's an option on the header menu called :guilabel:`Mailing Lists`. When clicked, a sub-menu is revealed with options for :guilabel:`Mailing Lists` and :guilabel:`Mailing List Contacts`." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:21 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:21 msgid "Click :menuselection:`Mailing Lists --> Mailing Lists` to see an overview of all mailing lists in the database." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:-1 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:-1 msgid "View of the main SMS mailing list page on the Odoo SMS Marketing application." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:28 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:28 msgid "To edit any existing list, select the desired list from the :guilabel:`Mailing Lists` page, and proceed to modify it in a number of ways." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:31 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:31 msgid "To create a new mailing list, click :guilabel:`Create` in the upper left corner of the :guilabel:`Mailing Lists` page. Doing so, will reveal a blank mailing list template form." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:-1 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:-1 msgid "View of the mailing list pop-up window in Odoo SMS Marketing." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:38 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:38 msgid "First, choose a name for the :guilabel:`Mailing List`, and activate the option :guilabel:`Is Public`, to make the mailing list accessible to recipients on the :guilabel:`Subscription Management page`. Doing so allows users to update their subscription preferences at any time." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:43 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:43 msgid "Checking the :guilabel:`Is Public` box is not required, but is recommended to maintain good customer relations." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:46 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:46 msgid "When those fields are filled in, click :guilabel:`Create` to finalize the form. Then on the main :guilabel:`Mailing Lists` dashboard, the new mailing list that was just created will be accessible." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:49 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:49 msgid "To edit or customize the mailing list further, select the mailing list from the main :guilabel:`Mailing Lists` page to reveal the mailing list detail form." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:52 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:52 msgid "Along the top of the mailing list detail form, there are various analytical smart buttons displaying statistics for different metrics related to the mailing list (e.g. :guilabel:`Recipients`, :guilabel:`Mailings`, etc.)." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:56 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:56 msgid "To review or edit any of those elements, click the desired smart button to reveal a separate page with in-depth data associated with the mailing list." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:59 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:59 msgid "To make changes to the mailing list itself, click the :guilabel:`Edit` button in the upper-left corner of the mailing list detail form." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:-1 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:-1 msgid "View of the mailing list template form in Odoo SMS Marketing." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:67 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:67 msgid "Don't forget to hit the :guilabel:`Save` button once changes have been made." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:70 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:70 msgid "Mailing lists contacts" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:72 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:72 msgid "Access contacts information from one or more mailing lists navigate to :menuselection:`Mailing Lists --> Mailing List Contacts` to reveal a dashboard with with all the contacts associated with one or more of the configured mailing lists in the database." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:-1 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:-1 msgid "View of the mailing lists contact page in the Odoo SMS Marketing application." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:81 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:81 msgid "By default, Odoo reveals the :guilabel:`Mailing List Contacts` page with the :guilabel:`Exclude Blacklisted Phone` filter in the search bar. Therefore only showing contact information for recipients who still want to receive communications and mailings." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:86 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:86 msgid "Communication history in the Chatter" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:88 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:88 msgid "An accessible record of every sent mailing(s) is kept on each recipient's *chatter* section, located beneath a recipient's contact form (in the *Contacts* application)." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:91 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:91 msgid "Database users can reference the chatter to easily keep track of communications, and see a history of interactions with contacts and prospects." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:94 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:94 msgid "For example, sales representatives can use the chatter to quickly find out which :abbr:`SMS (Short Message Service)` mailing promotions a certain customer has received (or not received)." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:-1 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:-1 msgid "View of what the chatter looks like in the Odoo Contacts app." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:104 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:104 msgid "Odoo *SMS Marketing* has a :guilabel:`Blacklist` feature that provides recipients with the power to add their phone number to a list of people who no longer want to receieve communications or mailings." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:108 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:108 msgid "This is also known as the unsubscribe process: customers will automatically be added onto a *blacklist*, if they click :guilabel:`Unsubscribe`, via their :guilabel:`Subscription Management` page. Customers can also be added manually to the blacklist, if necessary." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:112 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:112 msgid "To see a complete collection of blacklisted numbers, navigate to the :menuselection:`SMS Marketing app --> Configuration --> Blacklisted Phone Numbers` to reveal a dashboard containing every blacklisted phone number in the database." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:-1 -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:-1 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:-1 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:-1 msgid "SMS Blacklist menu in the application." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:120 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:120 msgid "To manually add a number to a blacklist, click the :guilabel:`Create` button in the upper-left corner of the dashboard and enter the phone number on the next page's form. There's also a checkbox to indicate whether that particular phone numnber is :guilabel:`Active` (or not)." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:128 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:128 msgid "Once the form is completed, click :guilabel:`Save` to add it to the :guilabel:`Blacklisted Phone Numbers` list. To remove any number from the blacklist, select the desired number on the dashboard, and then, on the phone number's form, click :guilabel:`Unblacklist`." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:133 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:133 msgid "Importing blacklists" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:135 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:135 msgid "During a software/platform migration, it is possible to import an already existing blacklist of contacts. This would include customers, who have already asked to be blacklisted` on :abbr:`SMS (Short Message Service)` mailings." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:139 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:139 msgid "To do that, navigate to :menuselection:`SMS Marketing app --> Configuration --> Blacklisted Phone Numbers`, and then select the :guilabel:`Favorites` drop-down menu (beneath the search bar), and click :guilabel:`Import records`." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:-1 +#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:-1 msgid "View of how to import a blacklist in Odoo SMS Marketing." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:3 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:3 msgid "SMS campaign settings" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:5 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:5 msgid "Utilizing :abbr:`SMS (Short Message Service)` campaigns with Odoo *SMS Marketing* isn't just an effective advertisement strategy, it's also a great way to remind people about upcoming events, issued invoices, and so much more." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:9 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:9 msgid "But, before :abbr:`SMS (Short Message Service)` campaigns can be created (and sent), a few specific settings and features must be enabled first." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:13 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:13 msgid "SMS campaign setting" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:15 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:15 msgid "To enable :abbr:`SMS (Short Message Service)` campaigns in Odoo, make sure the *Mailing Campaigns* feature is activated by going to :menuselection:`Email Marketing --> Configuration --> Settings`, and then enable :guilabel:`Mailing Campaigns` and :guilabel:`Save` the changes." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:-1 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:-1 msgid "View of the mailing campaigns setting in Odoo." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:24 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:24 msgid "Activating the *Mailing Campaigns* feature in the *General Settings* also enables the *A/B Test* feature." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:27 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:27 msgid "Once the setting is enabled, navigate back to the :menuselection:`SMS Marketing` app, and notice the :guilabel:`Campaigns` header menu is now available for use. Similarly, the :guilabel:`A/B Test` tab is now also available on every :abbr:`SMS (Short Message Service)` template form." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:32 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:32 msgid "A/B tests" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:34 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:34 msgid ":guilabel:`A/B Tests` allows any :abbr:`SMS (Short Message Service)` mailings to be tested against other versions within the same campaign, in order to compare which version is the most successful in producing engagement and/or conversion outcomes." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:38 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:38 msgid "On an :abbr:`SMS (Short Message Service)` template form, under the :guilabel:`A/B Tests` tab, initially, there's only a single checkbox labeled: :guilabel:`Allow A/B Testing.`" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:41 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:41 msgid "When clicked, a series of other options appear." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:-1 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:-1 msgid "The A/B Test tab is located on an Odoo SMS Marketing app campaign form." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:47 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:47 msgid "In the first field, enter a desired percentage of recipients to conduct the A/B Test on." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:49 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:49 msgid "Beneath the percentage field is the :guilabel:`Winner Selection` field. This is what Odoo will use to determine the successful result of an A/B Test. In other words, this tells Odoo how to pick a winning A/B test." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:53 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:53 msgid "The following sections are available: :guilabel:`Manual`, :guilabel:`Highest Click Rate`, :guilabel:`Leads`, :guilabel:`Quotations`, or :guilabel:`Revenues`." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:56 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:56 msgid "Finally, the :guilabel:`Send Final On` field is listed. This represents the date-time that Odoo uses as a deadline to determine the winning mailing variation. Then, Odoo sends that winning mailing variation to the remaining recipients, who weren't involved in the test, at that prior date and time." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:62 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:62 msgid "Quickly create different versions of the mailing to add to the A/B Test by clicking the :guilabel:`Create an Alternate Version` button." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:66 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:66 msgid "Remember, the winning mailing variation is based on the criteria selected in the :guilabel:`Winner Selection` field." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:70 -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:15 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:70 +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:15 msgid "Campaigns page" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:72 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:72 msgid "To create, edit, or analyze any campaign, click :menuselection:`Campaigns` in the header menu of the :guilabel:`SMS Marketing` app. On the :guilabel:`Campaigns` page, each campaign displays various information related to the mailings associated with that campaign (e.g. number of emails, social posts, SMSs, and push notifications)." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:-1 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:-1 msgid "Dasbhoard view of different Campaigns in the Odoo SMS Marketing app, separated by stage." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:84 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:84 msgid "Click :guilabel:`Create` to create a new campaign, and Odoo reveals a blank campaign template form to fill out. Alternatively, select any previously-made campaign in order to duplicate, review, or edit its campaign template form." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:-1 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:-1 msgid "View of an SMS campaign template in Odoo SMS marketing." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:92 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:92 msgid "With each campaign, the options to :guilabel:`Send New Mailing`, :guilabel:`Send SMS`, :guilabel:`Send Social Post`, and :guilabel:`Push Notifications` are available above the template form." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:96 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:96 msgid "Whenever one of those communication options is added to the campaign, Odoo will create a new corresponding tab on the template form, where those types of messages can be reviewed or edited, along with various data sets related to each specific mailing." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:100 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:100 msgid "At the top of the template, there are various analytical smart buttons. When clicked, Odoo reveals in-depth metrics related to that specific topic (e.g. :guilabel:`Engagement`, :guilabel:`Opportunities`, etc.) on a separate page." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:104 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:104 msgid "Beneath the smart buttons, are fields for :guilabel:`Campaign Name` and :guilabel:`Responsible`. Odoo also allows for various :guilabel:`Tags` to be added, as well (if necessary)." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:108 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:108 msgid "Sending SMSs through the Contacts app" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:110 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:110 msgid "Sending :abbr:`SMS (Short Message Service)` mailings directly through a contact's form is available by default." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:113 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:113 msgid "In order to send an :abbr:`SMS (Short Message Service)` in this fashion, navigate to the :menuselection:`Contacts` app, select the desired contact in the database, and click on the :guilabel:`SMS` icon on the contact form (next to the :guilabel:`Phone Number` field)." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:-1 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:-1 msgid "The SMS icon is located on an individual's contact form in Odoo Contacts." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:121 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:121 msgid "To send a message to multiple contacts at once, navigate to the main :menuselection:`Contacts` app main dashboard, choose the :guilabel:`List View`, and select all the desired contacts to whom the message should be sent. Then, under :guilabel:`Action`, select :guilabel:`Send SMS`." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:-1 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:-1 msgid "Select a number of contacts, click action, and select send multiple SMSs." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:130 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:130 msgid "Set up SMS templates for future use" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:132 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:132 msgid "In order to set up :guilabel:`SMS Templates` for future use, activate :ref:`developer mode `, by navigating to the main Odoo dashboard that is full of apps, and select the :menuselection:`Settings app`. Then, scroll down to the :guilabel:`Developer Tools` section, and click :guilabel:`Activate the Developer Mode`." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:137 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:137 msgid "Once *developer mode* is activated, the main Odoo dashboard appears once more, with a now-visible bug icon, which is located at the top-right corner of the dashboard; this bug icon indicates that developer mode is currently active." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:141 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:141 msgid "Next return to the :menuselection:`Settings app` and, in the now-visible header menus at the top, choose :menuselection:`Technical --> SMS Templates` to begin setting up :abbr:`SMS (Short Message Service)` templates for future marketing campaigns." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:-1 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:-1 msgid "Select the SMS Template option in the Technical dropdown on the Settings app." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:149 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:149 msgid "Inside of the :guilabel:`SMS Templates` dashboard, Odoo reveals an entire page of :abbr:`SMS (Short Message Service)` templates. The default :guilabel:`List` view showcases each template's name, and to which recipients it applies." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:153 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:153 msgid "On this page, :abbr:`SMS (Short Message Service)` templates can be edited or created from scratch." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:-1 +#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:-1 msgid "The SMS Templates page in Odoo is available after enabling developer mode in the General\n" "Settings" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:3 -msgid "SMS essentials" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:5 -msgid "Utilizing :abbr:`SMS (Short Message Service)` outreach in communication strategies can help companies expand their market reach, especially in some countries, where emails might not be very common, or even used at all." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:9 -msgid "Odoo's *SMS Marketing* application can also help boost conversion rates around valuable actions, such as event registrations, free trials, purchases, etc., since text and mobile-based marketing channels typically yield higher :abbr:`CTOR (click-to-open rate)` and :abbr:`CTR (click-through rate)` outcomes." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:15 -msgid "SMS marketing dashboard" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:17 -msgid "When the application is opened, Odoo displays the main :guilabel:`SMS Marketing` dashboard, which showcases the various SMS mailings that have been created, along with pertinent information and data related to that specific message." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:21 -msgid "The :guilabel:`Kanban` view is the default Odoo uses when the application is opened, which provides an organized display of the SMS mailings that have been created, and what their current status is at the moment." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:26 -msgid "An :abbr:`SMS (Short Message Service)` mailing can have one of the following statuses: :guilabel:`Draft`, :guilabel:`In Queue`, :guilabel:`Sending`, or :guilabel:`Sent`." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:29 -msgid "In the upper right corner of the main :guilabel:`SMS Marketing` dashboard, there are a few different view options to choose from. Each one provides a unique take on the same SMS information." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:32 -msgid "The :guilabel:`List` view provides the same useful data related to SMS mailings, but in a more traditional list layout." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:35 -msgid "The :guilabel:`Calendar` view provides a simple calendar, making it easy to see when SMS mailings are going to be sent (or have been sent). If a future date is clicked, Odoo reveals a blank SMS template that, when completed, will be scheduled to be sent on that specific future date." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:39 -msgid "Lastly, the :guilabel:`Graph` view visualizes that same SMS-related data in series of graphs and charts. Odoo also provides various ways to sort and group the data for more detailed analysis." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:43 -msgid "Create SMS messages" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:45 -msgid "To start, click :guilabel:`Create` on the main :guilabel:`SMS Marketing` dashboard, and Odoo reveals a blank SMS template form, which can be configured in a number of different ways." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:-1 -msgid "Creating an SMS marketing template." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:52 -msgid "First, give the mailing a :guilabel:`Subject`, which describes what the mailing is about." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:54 -msgid "Next, in the :guilabel:`Recipients` field, choose to whom this :abbr:`SMS (Short Message Service)` will be sent. By default, Odoo has :guilabel:`Mailing List` selected. If this is the desired :guilabel:`Recipients` field option, specify which mailing list Odoo should send this :abbr:`SMS (Short Message Service)` to in the :guilabel:`Select Mailing List` field." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:60 -msgid "To create (or edit) a mailing list, go to :menuselection:`Mailing Lists --> Mailing List`. There, Odoo displays all previously created mailing lists, along with various types of data related to that specific list (e.g. number of contacts, mailings, recipients, etc.)." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:64 -msgid "To learn more about mailing lists and contacts, check out :doc:`mailing_lists_blacklists`." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:-1 -msgid "View of the mailing list page in the SMS marketing application." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:70 -msgid "To reveal all the possible options in the :guilabel:`Recipients` field, click the field to see all the choices Odoo makes available." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:73 -msgid "When another field (other than :guilabel:`Mailing List`) is selected, the option to specify that chosen field even further becomes available — either with a default recipient filter equation that appears automatically (which can be customized to fit any business need), or, if no default recipient filter equation is present, an :guilabel:`Add Filter` button will appear." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:78 -msgid "Clicking the :guilabel:`Add Filter` button, reveals fully customizable domain rule fields, which can be configured similar to an equation. You can create multiple recipient rules, if necessary." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:81 -msgid "Then, Odoo will only send the :abbr:`SMS (Short Message Service)` to recipients who fit into whatever criteria is configured in those fields. Multiple rules can be added." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:85 -msgid "If :guilabel:`Contact` is chosen, all of the *Contacts* records in the Odoo database (vendors, customers, etc.) will receive the :abbr:`SMS (Short Message Service)`, by default — unless more specific recipient rules are entered." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:89 -msgid "For instance, the message below will only be sent to contacts in the database that are located in the United States (e.g. `Country` > `Country Name` equals `United States`), and they haven't blacklisted themselves from any mailings (e.g. `Blacklist` > `is` > `not set`)." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:0 -msgid "Contact recipients on SMS marketing." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:98 -msgid "Writing SMS messages" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:100 -msgid "Enter the content of the :abbr:`SMS (Short Message Service)` in the text field, found in the :guilabel:`SMS Content` tab. Links and emojis can also be included. Beneath the text field, Odoo displays how many characters are used in the message, along with how many :abbr:`SMS (Short Message Service)` mailings it will take to deliver the complete message." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:106 -msgid "To check the price of sending an :abbr:`SMS (Short Message Service)` for a country, click on the :guilabel:`Information` icon." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:-1 -msgid "SMS price check icon." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:114 -msgid "Credits must be purchased from Odoo in order to take advantage of the *SMS Marketing* app; :abbr:`SMS (Short Message Service)` messages will not be sent without credits." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:118 -msgid "`Odoo SMS - FAQ `_" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:121 -msgid "Track links used in SMS messages" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:123 -msgid "When links are used in :abbr:`SMS (Short Message Service)` messages, Odoo automatically generates link trackers to gather analytical data and metrics related to those specific links, which can be found by going to :menuselection:`Configuration --> Link Tracker`." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:-1 -msgid "SMS Link Tracker page." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:132 -msgid "Adjust SMS settings" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:134 -msgid "Under the :guilabel:`Settings` tab of the SMS template, there is an option to :guilabel:`Include opt-out link`. If activated, the recipient is able to unsubscribe from the mailing list, thus avoiding all future mailings." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:138 -msgid "An employee can be designated as the :guilabel:`Responsible` in the :guilabel:`Tracking` section of the :guilabel:`Settings` tab, as well." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:-1 -msgid "SMS Settings tab." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:146 -msgid "Send SMS messages" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:148 -msgid "Once a mailing is created, choose when Odoo should deliver the message from the following options:" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:150 -msgid ":guilabel:`Send`: sends the message immediately. Consider using this option if the recipient list is highly refined, or in cases that involve fast approaching deadlines, such as a \"flash sale.\"" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:152 -msgid ":guilabel:`Schedule`: choose a day (and time) for Odoo to send the mailing. This is typically the best option for mailings related to a specific event. Such a method can also be used to promote a limited-time offer, or to help plan a company's content strategy in advance." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:155 -msgid ":guilabel:`Test`: allows for an :abbr:`SMS (Short Message Service)` to be sent to one or multiple numbers for test purposes. Remember to use a comma between phone numbers if multiple numbers are used as recipients." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:160 -msgid "Visualize reports" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:162 -msgid "On the :guilabel:`Reporting` page (accessible via the :menuselection:`Reporting` option in the header menu), there are options to apply different combinations of :guilabel:`Filters` and :guilabel:`Measures` to view metrics in a number of different layouts (e.g. :guilabel:`Graph`, :guilabel:`List`, and :guilabel:`Cohort` views.)" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:167 -msgid "Each :guilabel:`Reporting` metric view option allows for more extensive performance analysis of :abbr:`SMS (Short Message Service)` mailings." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:170 -msgid "For example, while in the default :guilabel:`Graph` view, :abbr:`SMS (Short Message Service)` data is visualized as different graphs and charts, which can be sorted and grouped in various ways (e.g. :guilabel:`Measures` drop down menu)." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:-1 -msgid "Reporting page in SMS Marketing." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:179 -msgid "SMS messages can be sent using automation rules in Odoo. Odoo *Studio* is required to use automation rules." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:182 -msgid "To install Odoo *Studio*, go to the :menuselection:`Apps application`. Then, using the :guilabel:`Search...` bar, search for `studio`." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:185 -msgid "If it is not already installed, click :guilabel:`Install`." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:187 -msgid "Adding the *Studio* application upgrades the subscription status to *Custom*, which increases the cost. Consult `support `_, or reach out to the database's customer success manager, with any questions on making the change." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:191 -msgid "To use automation rules, navigate in :ref:`developer mode `, to :menuselection:`Settings app --> Technical menu --> Automation section --> Automation Rules`. Then, click :guilabel:`New` to create a new rule." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:195 -msgid "Enter a name for the automation rule, and select a :guilabel:`Model` to implement this rule on." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:197 -msgid "Based on the selection for the :guilabel:`Trigger`, additional fields will populate below. Set the :guilabel:`Trigger` to one of the following options:" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:200 -msgid ":guilabel:`Values Updated`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:202 -msgid ":guilabel:`User is set`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:203 -msgid ":guilabel:`State is set to`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:204 -msgid ":guilabel:`On archived`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:205 -msgid ":guilabel:`On unarchived`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:207 -msgid ":guilabel:`Timing Conditions`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:209 -msgid ":guilabel:`Based on date field`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:210 -msgid ":guilabel:`After creation`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:211 -msgid ":guilabel:`After last update`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:213 -msgid ":guilabel:`Custom`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:215 -msgid ":guilabel:`On save`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:216 -msgid ":guilabel:`On deletion`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:217 -msgid ":guilabel:`On UI change`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:219 -msgid ":guilabel:`External`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:221 -msgid ":guilabel:`On webhook`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:223 -msgid "Other options may appear based on the :guilabel:`Model` selected. For example if the :guilabel:`Calendar Event` model is selected, then the following options appear in addition to those above:" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:227 -msgid ":guilabel:`Email Events`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:229 -msgid ":guilabel:`On incoming message`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:230 -msgid ":guilabel:`On outgoing message`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:232 -msgid "Under the :guilabel:`Before Update Domain` field, set a condition to be met before updating the record. Click :guilabel:`Edit Domain` to set record parameters." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:235 -msgid "Under the :guilabel:`Actions To Do` tab, select :guilabel:`Add an action`. Next, in the resulting :guilabel:`Create Actions` pop-up window, select :guilabel:`Send SMS`, and set the :guilabel:`Allowed Groups`. :guilabel:`Allowed Groups` are the access rights groups that are allowed to execute this rule. Leave the field empty to allow all groups. See this documentation: :ref:`access-rights/groups`." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:241 -msgid "Next, set the :guilabel:`SMS Template` and choose whether the SMS message should be logged as a note, by making a selection in the drop-down menu: :guilabel:`Send SMS as`. Click :guilabel:`Save and Close` to save the changes to this new action." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:-1 -msgid "Automation rule template with rule to do, SMS template and log as note highlighted." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:249 -msgid "Add any necessary notes under the :guilabel:`Notes` tab. Finally, navigate away from the completed automation rule, or manually save (by clicking the :guilabel:`☁️ (cloud)` icon), to implement the change." -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:254 -msgid ":doc:`sms_campaign_settings`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:255 -msgid ":doc:`mailing_lists_blacklists`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:256 -msgid ":doc:`../../../essentials/in_app_purchase`" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/pricing.rst:5 -msgid "Pricing and FAQ" -msgstr "" - -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:5 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:5 msgid "SMS Pricing and FAQ" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:8 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:8 msgid "What do I need to send SMSs?" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:10 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:10 msgid "SMS Text Messaging is an In-App Purchase (IAP) service that *requires prepaid credits* to work." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:13 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:13 msgid "How many types of SMSs are there?" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:15 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:15 msgid "There are 2 types: GSM7 and UNICODE." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:17 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:17 msgid "**GSM7** is the standard format, with a limit of 160 characters per message, that includes the following characters:" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:-1 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:-1 msgid "GSM7 characters available in Odoo SMS Marketing." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:24 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:24 msgid "**UNICODE** is the format applied if a special character, that *is not* in the GSM7 list, is used. Limit per SMS: 70 characters." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:28 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:28 msgid "For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above these limits, the content is divided into a multi-part message* and the limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. Then, in real-time, the system displays the number of SMS mailings the message represents." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:34 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:34 msgid "How much does it cost to send an SMS?" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:36 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:36 msgid "The price of an SMS depends on the destination and the length (number of characters) of the message. To see the **price per country, please consult**: `Odoo SMS - FAQ `_." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:40 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:40 msgid "The number of SMSs a message represents will always be available in the database." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:-1 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:-1 msgid "Number of GSM7 characters that fit in an SMS message in Odoo SMS Marketing." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:47 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:47 msgid "How to buy credits" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:49 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:49 msgid "Go to :menuselection:`Settings --> Buy Credits`." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:-1 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:-1 msgid "Buying credits for SMS Marketing in Odoo settings." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:55 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:55 msgid "Or go to :menuselection:`Settings --> View my Services`." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:-1 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:-1 msgid "Using Odoo IAP to recharge credits for SMS Marketing in Odoo settings." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:62 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:62 msgid "If Odoo Online (Saas) is being used, along with the Enterprise version, free trial credits are available to test the feature." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:66 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:66 msgid "More common questions" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "**Is there an expiration time for my credits?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "No, credits do not expire." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "**Can I send an SMS to a phone number (which is not a mobile phone) because I see the icon in front of the field “phone”?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "Only if that phone number supports SMS (e.g. SIP phones)." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "**Do I receive an invoice to buy my credits?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "Yes." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "**Can the recipient answer me?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "No, it is not possible to reply to the SMS." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "**What happens if I send multiple SMSs at once, but I don't have enough credits to send them all?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "Multiple SMS communications at once at are counted as a single transaction, so no SMSs will be sent until there are enough credits to send them all." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "**Do I have a history of the sent SMSs?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "A history of sent SMSs, along with all pertinent information related to its sent contacts (and the message itself), can be found in the :guilabel:`Sent` column of the main :guilabel:`SMS Marketing` dashboard (while in :guilabel:`Kanban` view)." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:91 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:91 msgid "For more detailed information, select a desired SMS from the main dashboard (in :guilabel:`Kanban` view), and click on either link in the blue banner above the SMS detail form to learn more." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "**Can I send as many SMSs I want at once?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "Yes, if you have enough credits." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "**If an SMS is sent to a number that doesn't exist in the list of recipients, will credits be lost?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "No, not if the phone number is incorrectly formatted (e.g. too many digits). However, if the SMS is sent to the wrong person (or to a fake number), the credit for that SMS will be lost." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "**What happens if I send my SMS to a paying number (e.g.: a contest to win a ticket for a festival)?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "The SMS will not be delivered to that kind of number, so no charges will be made." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "**Can I identify the numbers that do not exist when I send several SMSs?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "Only the ones that have an invalid format." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "**How does the GDPR regulation affect this service?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "Please find our `Privacy Policy here `__." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "**Can I use my own SMS provider?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0 msgid "Yes, but it is not possible out-of-the-box. Odoo experts can help customize a database to allow for the use of a personal SMS provider. Please check our success packs `here `_." msgstr "" -#: ../../content/applications/marketing/social_marketing.rst:8 +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:3 +msgid "SMS analysis" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:5 +msgid "On the :guilabel:`Reporting` page (accessible via the :menuselection:`Reporting` option in the header menu), there are options to apply different combinations of :guilabel:`Filters` and :guilabel:`Measures` to view metrics in a number of different layouts (e.g. :guilabel:`Graph`, :guilabel:`List`, and :guilabel:`Cohort` views.)" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:10 +msgid "Each :guilabel:`Reporting` metric view option allows for more extensive performance analysis of :abbr:`SMS (Short Message Service)` mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:13 +msgid "For example, while in the default :guilabel:`Graph` view, :abbr:`SMS (Short Message Service)` data is visualized as different graphs and charts, which can be sorted and grouped in various ways (e.g. :guilabel:`Measures` drop down menu)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:-1 +msgid "Reporting page in SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:22 +msgid "SMS messages can be sent using automation rules in Odoo. Odoo *Studio* is required to use automation rules." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:25 +msgid "To install Odoo *Studio*, go to the :menuselection:`Apps application`. Then, using the :guilabel:`Search...` bar, search for `studio`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:28 +msgid "If it is not already installed, click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:30 +msgid "Adding the *Studio* application upgrades the subscription status to *Custom*, which increases the cost. Consult `support `_, or reach out to the database's customer success manager, with any questions on making the change." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:34 +msgid "To use automation rules, navigate in :ref:`developer mode `, to :menuselection:`Settings app --> Technical menu --> Automation section --> Automation Rules`. Then, click :guilabel:`New` to create a new rule." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:38 +msgid "Enter a name for the automation rule, and select a :guilabel:`Model` to implement this rule on." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:40 +msgid "Based on the selection for the :guilabel:`Trigger`, additional fields will populate below. Set the :guilabel:`Trigger` to one of the following options:" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:43 +msgid ":guilabel:`Values Updated`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:45 +msgid ":guilabel:`User is set`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:46 +msgid ":guilabel:`State is set to`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:47 +msgid ":guilabel:`On archived`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:48 +msgid ":guilabel:`On unarchived`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:50 +msgid ":guilabel:`Timing Conditions`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:52 +msgid ":guilabel:`Based on date field`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:53 +msgid ":guilabel:`After creation`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:54 +msgid ":guilabel:`After last update`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:56 +msgid ":guilabel:`Custom`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:58 +msgid ":guilabel:`On save`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:59 +msgid ":guilabel:`On deletion`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:60 +msgid ":guilabel:`On UI change`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:62 +msgid ":guilabel:`External`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:64 +msgid ":guilabel:`On webhook`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:66 +msgid "Other options may appear based on the :guilabel:`Model` selected. For example if the :guilabel:`Calendar Event` model is selected, then the following options appear in addition to those above:" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:70 +msgid ":guilabel:`Email Events`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:72 +msgid ":guilabel:`On incoming message`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:73 +msgid ":guilabel:`On outgoing message`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:75 +msgid "Under the :guilabel:`Before Update Domain` field, set a condition to be met before updating the record. Click :guilabel:`Edit Domain` to set record parameters." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:78 +msgid "Under the :guilabel:`Actions To Do` tab, select :guilabel:`Add an action`. Next, in the resulting :guilabel:`Create Actions` pop-up window, select :guilabel:`Send SMS`, and set the :guilabel:`Allowed Groups`. :guilabel:`Allowed Groups` are the access rights groups that are allowed to execute this rule. Leave the field empty to allow all groups. See this documentation: :ref:`access-rights/groups`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:84 +msgid "Next, set the :guilabel:`SMS Template` and choose whether the SMS message should be logged as a note, by making a selection in the drop-down menu: :guilabel:`Send SMS as`. Click :guilabel:`Save and Close` to save the changes to this new action." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:-1 +msgid "Automation rule template with rule to do, SMS template and log as note highlighted." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:92 +msgid "Add any necessary notes under the :guilabel:`Notes` tab. Finally, navigate away from the completed automation rule, or manually save (by clicking the :guilabel:`☁️ (cloud)` icon), to implement the change." +msgstr "" + +#: ../../content/applications/marketing/social_marketing.rst:5 msgid "Social Marketing" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:3 -msgid "Social marketing campaigns" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:5 -msgid "Social marketing campaigns help companies connect directly with the marketplace. These campaigns are helpful when introducing a new product to customers, explaining the value of a product or service, or when advertising an upcoming event or product release." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:9 -msgid "The most effective social marketing campaigns typically involve multiple channels to maximize content distribution, and Odoo's *Social Marketing* application acts as a singular control center to monitor, plan, post, track, and analyze all of the various content and content channels within a single dashboard." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:17 -msgid "To access a complete overview of all social marketing campaigns, open the :menuselection:`Social Marketing` application, and click :menuselection:`Campaigns` from the header menu. Doing so reveals a separate page with every campaign in a default kanban view." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:-1 -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:-1 -msgid "View of the campaigns page in the Odoo Social Marketing application." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:25 -msgid "Each *stage* in the kanban view can be edited, by clicking the :guilabel:`gear icon` to the left of the :guilabel:`+ (plus sign)` - located to the right of the stage title." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:29 -msgid "The **gear icon** *only* appears when the cursor hovers to the left of the **+ (plus sign)**. When the gear icon is clicked, a drop-down menu reveals the options: :guilabel:`Fold`, :guilabel:`Edit Stage`, and :guilabel:`Delete`." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:37 -msgid "Clicking :guilabel:`Fold` minimizes that specific stage's column. The stage column can be restored by clicking the folded version of it on the main :guilabel:`Campaigns` dashboard in the default kanban view." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:41 -msgid "Selecting :guilabel:`Edit Stage` reveals a pop-up window, in which the name and the sequence of the stage can be modified. If changes are made, be sure to click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:44 -msgid "Clicking :guilabel:`Delete` removes the stage entirely." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:47 -msgid "To add a new stage to the pipeline, side-scroll to the right on the :guilabel:`Campaigns` dashboard, click :guilabel:`Add a Column`, enter in the desired information, and click :guilabel:`Add`." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:52 -msgid "The same social marketing campaign information on the :guilabel:`Campaigns` dashboard can also be viewed as a list, by selecting the :guilabel:`List` option, located under the search bar, in the upper-right corner." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:57 -msgid "Create social marketing campaigns" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:59 -msgid "First, open the :menuselection:`Social Marketing` application, and select :guilabel:`Campaigns` from the header menu." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:62 -msgid "On the :guilabel:`Campaigns` dashboard, a new campaign can be created by clicking the quick add :guilabel:`+ (plus sign)` located in the top-right corner of each stage in the pipeline, visible in the kanban view. Campaigns can also be created by clicking :guilabel:`Create` in the upper-left corner of the :guilabel:`Campaigns` dashboard." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:67 -msgid "Both options reveal a new campaign detail window directly on the :guilabel:`Campaigns` dashboard when clicked." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:-1 -msgid "View of the quick add option for campaigns in Odoo Social Marketing." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:74 -msgid "Here, the :guilabel:`Campaign Name`, :guilabel:`Responsible`, and :guilabel:`Tags` can be entered. When all modifications are complete, click :guilabel:`Add` to add the campaign to the database." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:78 -msgid "Edit social marketing campaigns" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:80 -msgid "In order to edit a campaign in greater detail, and create/send various forms of communications related to it, the template page for that campaign must be accessed and modified, accordingly. There are multiple ways to access a template page for a campaign." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:84 -msgid "After entering the pertinent information in the :guilabel:`Quick Add` campaign drop-down, click :guilabel:`Edit`." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:86 -msgid "Simply select the desired campaign from the :guilabel:`Campaigns` dashboard in list or kanban view." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:88 -msgid "On the :guilabel:`Campaigns` dashboard in the kanban view, select the :guilabel:`⋮ (three dots)` drop-down menu on the desired campaign, and select :guilabel:`Edit`." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:91 -msgid "Any of the above routes will reveal the *Campaign Template* page for that specific campaign." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:94 -msgid "Social marketing campaign templates" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:96 -msgid "On a *Campaign Template* page, numerous elements can be customized/modified, and various forms of communications can be created, modified, and sent or scheduled. Below is a sample of a completed campaign template." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:-1 -msgid "View of a sample campaign template page in Odoo Social Marketing." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:105 -msgid "In order for the :guilabel:`Send New Mailing` option to appear on campaign templates, make sure the *Mailing Campaigns* feature is enabled in the *Email Marketing* app. To do that, navigate to :menuselection:`Email Marketing --> Configuration --> Settings`, activate :guilabel:`Mailing Campaigns`, and click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:111 -msgid "In order for the :guilabel:`Send SMS` option to appear, the Odoo *SMS Marketing* application must be installed on the database." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:115 -msgid "Add content and communications to campaigns" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:117 -msgid "If the proper settings and applications are installed (as instructed above), there are four forms of communication/content options that can be added to campaigns. Each of these options are displayed as buttons in the upper-left corner of the campaign template page." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:121 -msgid ":guilabel:`Send New Mailing`: reveals a blank email template on a separate page, in which the message can be fully customized in a variety of ways." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:123 -msgid ":guilabel:`Send SMS`: reveals a blank SMS template on a separate page, in which a SMS communication can be created and configured." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:125 -msgid ":guilabel:`Send Social Post`: reveals a blank social post template on a separate page, in which a post can be created, and applied to social media accounts that are already connected to the database." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:128 -msgid ":guilabel:`Push Notification`: reveals a similar blank social post template on a separate page, however, the :guilabel:`Push Notification` options are already pre-selected in the :guilabel:`Post on` field." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:132 -msgid "Whichever form of communication is created, once it's completed, Odoo returns to the :guilabel:`Campaign Template` page, showcasing that new content in its corresponding tab (e.g. :guilabel:`Mailings`, :guilabel:`SMS`, :guilabel:`Social Media`, and/or :guilabel:`Push Notifications`)." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:137 -msgid "As content and communications are added to a campaign, tabs for those specific mediums appear, along with a variety of analytical smart buttons (e.g. :guilabel:`Revenues`, :guilabel:`Quotations`, :guilabel:`Leads`, etc.)." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:141 -msgid "These smart buttons, located at the top of the template, display different metrics related to the campaign, and its various communications and content. Clicking any smart button reveals a separate page dedicated to that particular element of the campaign, allowing for quicker, more organized analysis." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:147 -msgid "The Odoo *Social Marketing* app is integrated with other Odoo applications, such as *Sales*, *Invoicing*, *CRM*, and *Website*." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:151 -msgid ":doc:`/applications/marketing/social_marketing/essentials/social_essentials`" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:3 -msgid "Social marketing essentials" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:5 +#: ../../content/applications/marketing/social_marketing.rst:7 msgid "Odoo's *Social Marketing* application helps content marketers create and schedule posts, manage various social media accounts, analyze content effectiveness, and engage directly with social media followers in one, centralized location." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:10 +#: ../../content/applications/marketing/social_marketing.rst:28 msgid "Social media accounts" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:12 +#: ../../content/applications/marketing/social_marketing.rst:30 msgid "In order to create social posts and analyze content with Odoo *Social Marketing*, social media accounts **must** be added as a *stream* on the application's main dashboard." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:16 +#: ../../content/applications/marketing/social_marketing.rst:34 msgid "Be aware that personal profiles **cannot** be added as a stream. The main use of Odoo *Social Marketing* is to manage and analyze business accounts on social media platforms." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:20 +#: ../../content/applications/marketing/social_marketing.rst:38 msgid "Odoo *Social Marketing* has some limitations in regards to social media accounts. For example, Odoo **cannot** handle a large quantity of various pages (e.g. ~40 pages) under the same company. The same limitations are present in a multi-company environment because of how the API is constructed." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:26 +#: ../../content/applications/marketing/social_marketing.rst:44 msgid "In multi-company environments, if every company doesn't activate a page at once, it will result in a permission error." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:29 +#: ../../content/applications/marketing/social_marketing.rst:47 msgid "For example, if Company 1 is the only company selected from the main Odoo dashboard, and activates *Facebook Page 1* and *Facebook Page 2*, then those pages will be accesible on the *Social Marketing* dashboard." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:33 +#: ../../content/applications/marketing/social_marketing.rst:51 msgid "However, if on that same database, the user adds Company 2 from the company drop-down menu in the header, and attempts to add those same streams, it results in a permission error." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +#: ../../content/applications/marketing/social_marketing.rst:0 msgid "View of the permission error that appears when incorrectly attempting to add stream." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:41 +#: ../../content/applications/marketing/social_marketing.rst:59 msgid "Social media streams" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:43 +#: ../../content/applications/marketing/social_marketing.rst:61 msgid "To add a social media business account as a stream, navigate to :menuselection:`Social Marketing app` and select the :guilabel:`Add A Stream` button located in the upper-left corner. Doing so reveals an :guilabel:`Add a Stream` pop-up window." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +#: ../../content/applications/marketing/social_marketing.rst:-1 msgid "View of the pop-up window that appears when Add a Stream is selected in Odoo." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:51 +#: ../../content/applications/marketing/social_marketing.rst:69 msgid "In the :guilabel:`Add a Stream` pop-up window, choose to :guilabel:`Link a new account` for a business from any of the following popular social media platforms: :guilabel:`Facebook`, :guilabel:`Instagram`, :guilabel:`LinkedIn`, :guilabel:`Twitter`, and :guilabel:`YouTube`." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:55 +#: ../../content/applications/marketing/social_marketing.rst:73 msgid "After clicking the desired social media outlet from the :guilabel:`Add a Stream` pop-up window, Odoo navigates directly to that specific social media outlet's authorization page, where permission must be granted, in order for Odoo to add that particular social media account as a stream to the *Social Marketing* application." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +#: ../../content/applications/marketing/social_marketing.rst:-1 msgid "Sample of a populated social marketing dashboard with social media streams and content." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:64 +#: ../../content/applications/marketing/social_marketing.rst:82 msgid "Once permission is granted, Odoo navigates back to the :guilabel:`Feed` on the main :guilabel:`Social Marketing` dashboard, and a new column, with that account's posts, is added. Accounts/streams can be added at any time." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:69 +#: ../../content/applications/marketing/social_marketing.rst:87 msgid "A :guilabel:`Facebook` page can be added as long as the :guilabel:`Facebook` account that grants permission is the administrator for the page. It should also be noted that different pages can be added for different streams." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:74 +#: ../../content/applications/marketing/social_marketing.rst:92 msgid ":guilabel:`Instagram` accounts are added through a :guilabel:`Facebook` login because it uses the same API. This means, an :guilabel:`Instagram` account needs to be linked to a :guilabel:`Facebook` account in order for it to show up as a stream in Odoo." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:79 -msgid "Posts" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:81 -msgid "Clicking on a post from a social media stream reveals a pop-up window, showcasing the content of that specific post, along with all the engagement data related to it (e.g. likes, comments, etc.)." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "Sample of a social media post's pop-up window in Odoo Social Marketing application." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:88 -msgid "If desired, the user can leave a new comment of the post from the post's pop-up window, by typing one in the :guilabel:`Write a comment...` field, and clicking :guilabel:`Enter` to post that comment." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:93 -msgid "Create leads from comments" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:95 -msgid "Odoo *Social Marketing* also provides the ability to create leads directly from social media comments." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:98 -msgid "To create a lead from a comment left on a social media post, click on the desired post from the dashboard to reveal that post's specific pop-up window. Then, scroll to the desired comment, and click the :guilabel:`three vertical dots` icon to the right of that comment." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:102 -msgid "Doing so reveals a drop-down menu with the option: :guilabel:`Create Lead`." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "The drop-down menu beside a comment revealing the option to create a lead." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:108 -msgid "Upon clicking :guilabel:`Create Lead` from the comment's drop-down menu, a :guilabel:`Conver Post to Lead` pop-up window appears." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "The convert post to lead pop-up window that appears in Odoo Social Marketing." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:115 -msgid "In this pop-up window, select to either: :guilabel:`Create a new customer`, :guilabel:`Link to an existing customer`, or :guilabel:`Do not link to a customer`." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:119 -msgid "If :guilabel:`Link to an existing customer` is selected, a new :guilabel:`Customer` field appears beneath those options, wherein a customer can be chosen to be linked to this lead." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:122 -msgid "Once the desired selection has been made, click the :guilabel:`Convert` button at the bottom of the :guilabel:`Convert Post to Lead` pop-up window. Doing so reveals a fresh lead detail form, where the necessary information can be entered and processed." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "New lead detail form generated from a social media comment in Odoo Social Marketing." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:131 -msgid "Insights" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:133 -msgid "When a social media account stream is added to the *Social Marketing* dashboard, each stream also displays and links that specific social media platform's KPIs (if the platform has them)." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:136 -msgid "To get redirected to the statistics and metrics related to any social media account's KPIs, click on the :guilabel:`Insights` link, located at the top of each stream." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "Visual of how the Insights link appears on the dashboard of the Social Marketing app." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:144 -msgid "In a multi-company environment, if not *all* pages are selected, de-authentication happens." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:146 -msgid "For example, if the companies have 3 *Facebook* pages, but only grant access to 1, and try to grant access to another at a later date, they will be de-authenticated, and access to the initial page's insights/analytics will be lost." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:150 -msgid "So, be sure to add *all* pages for *all* companies in a multi-company environment to avoid this issue. If a page gets de-autenticated, simply remove the stream, and re-establish it." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:154 -msgid "Create and post social media content" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:156 -msgid "Odoo *Social Marketing* offers the ability to create and post content for social media accounts directly through the application." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:159 -msgid "To create content for social media accounts, navigated to the :menuselection:`Social Marketing app`, and click :guilabel:`New Post` located in the upper-right corner of the *Social Marketing* dashboard." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "New Post button on the main dashboard of the Odoo Social Marketing application." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:167 -msgid "Or, navigate to :menuselection:`Social Marketing app --> Posts` and click the :guilabel:`New` button." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "New button on the Social Posts page in the Odoo Social Marketing application." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:174 -msgid "Either route reveals a blank social media post detail form that can be customized and configured in a number of different ways." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "Blank social media post detail page in Odoo Social Marketing." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:182 -msgid "Post detail form" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:184 -msgid "The social media post detail form in Odoo *Social Marketing* has many different configurable options available." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:188 -msgid "Company" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:190 -msgid "If working in a multi-company environment, the first field in the :guilabel:`Your Post` section of the social media post detail form is :guilabel:`Company`. In this field, select the company that should be connected to this specific social media post." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:195 -msgid "Post on" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:197 -msgid "If working in a single-company environment, the first field in the :guilabel:`Your Post` section of the social media post detail form is :guilabel:`Post on`. In this field, determine which social media outlets (streams) this post is intended to be posted on, and/or which website's visitors this post should be sent to, via push notification, by checking the box beside the desired option(s)." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:202 -msgid "Odoo automatically provides every available social media account that's been linked to the database as an option in this section. If a social media account hasn't been added as a stream to the *Social Marketing* application, it will **not** appear as an option on the post template." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:206 -msgid "Multiple social media outlets (streams) and websites can be selected in the :guilabel:`Post on` field. At least **one** option in the :guilabel:`Post on` field *must* be selected." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:210 -msgid "In order for the :guilabel:`Push Notification` option to appear on the social media post detail form in Odoo *Social Marketing*, make sure the *Enable Web Push Notifications* feature is enabled in the *Website* app." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:214 -msgid "To do that, navigate to :menuselection:`Website app --> Configuration --> Settings`, activate :guilabel:`Enable Web Push Notifications`, fill out the corresponding fields, and click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:219 -msgid "Message" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:221 -msgid "Next, there's the :guilabel:`Message` field. This is where the main content of the post is created." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:223 -msgid "In the :guilabel:`Message` field, type in the desired message for the social post. After typing, click away from the :guilabel:`Message` field to reveal visual samples of how the post will look on all the previously selected social media accounts (and/or websites, as push notifications)." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "Sample social media post with visual samples of how it will appear on social media outlets." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:232 -msgid "Emojis can also be added directly to the text in the :guilabel:`Message` field. Just click the :guilabel:`🙂 (smiley face)` icon, located on the line of the :guilabel:`Message` field to the far right. Clicking this icon reveals a drop-down menu containing numerous emojis to choose from." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:237 -msgid "If :guilabel:`Twitter` is chosen in the :guilabel:`Post on` field, a character counter appears beneath the :guilabel:`Message` field." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:241 -msgid "Attach Images" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:243 -msgid "If images are to be used in the post, click the :guilabel:`Attach Images` button, in the :guilabel:`Attach Images` field, located beneath the :guilabel:`Message` field. When clicked, Odoo reveals a pop-up window. In this pop-up window, select the desired image from the hard drive, and upload it." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:248 -msgid "After successfully uploading and attaching the desired image, Odoo reveals a new preview of the social media post, complete with the newly-added image, on the right side of the detail form." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "Visualized samples of post with newly-attached images in Odoo Social Marketing." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:256 -msgid "Campaign" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:258 -msgid "Next, there is the :guilabel:`Campaign` field. This non-required field provides the options to attach this post to a specific marketing campaign." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:261 -msgid "To add this post to a pre-existing campaign, click the empty :guilabel:`Campaign` field to reveal a drop-down menu, containing all the existing campaigns in the database. Select the desired campaign from this drop-down menu to add this post to that campaign." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:265 -msgid "To create a new campaign directly from the social media post detail form, start typing the name of the new campaign in the blank :guilabel:`Campaign` field, and select either :guilabel:`Create` or :guilabel:`Create and edit...`." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "Drop-down menu options of Create or Create and edit in the Campaign field." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:273 -msgid "Clicking :guilabel:`Create` creates the campaign, which can be edited/customized later." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:275 -msgid "Clicking :guilabel:`Create and edit...` creates the campaign, and reveals a :guilabel:`Create Campaign` pop-up form, wherein the :guilabel:`Campaign Identifier`, :guilabel:`Responsible`, and :guilabel:`Tags` can be instantly configured." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "Create campaign pop-up window that appears on a social media post detail form." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:283 -msgid "When all the desired settings have been entered, click :guilabel:`Save & Close` to save the campaign and return to the social media post detail form." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:287 -msgid "When" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:289 -msgid "Then, in the :guilabel:`When` field, choose either :guilabel:`Send Now` to have Odoo publish the post immediately, or :guilabel:`Schedule later` to have Odoo publish the post at a later date and time." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:293 -msgid "If :guilabel:`Schedule later` is selected, a new :guilabel:`Scheduled Date` field appears. Clicking the empty field reveals a pop-up calendar, in which a future date and time can be designated." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "Schedule date pop-up window that appears on social media post detail form in Odoo." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:300 -msgid "After selecting a desired date and time, click :guilabel:`Apply`. Then, Odoo will promptly publish the post at that specific date and time on the pre-detemined social media account(s)." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:304 -msgid "If scheduling a post, the :guilabel:`Post` button at the top of the social media post detail form changes to :guilabel:`Schedule`. Be sure to click :guilabel:`Schedule` after completing the social media post detail form." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:308 -msgid "Doing so, locks in that specific date/time for Odoo to send the post, and it changes the status of the post to :guilabel:`Scheduled`." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:312 -msgid "Push Notification Options" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:314 -msgid "If one (or multiple) :guilabel:`[Push Notification]` options are chosen in the :guilabel:`Post on` field, a specific :guilabel:`Push Notification Options` section appears at the bottom of the social media post detail form." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "Push notification options section on a social media post detail form." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:322 -msgid "It should be noted that *none* of these fields are required." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:324 -msgid "The first field in this section is :guilabel:`Notification Title`. In this field, there is the option to add a custom title to the push notification that will be sent." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:327 -msgid "To designate a specific page on the website that should trigger this push notification, enter that page's URL in the :guilabel:`Target URL` field. Then, once a visitor reaches that specific page, Odoo will display the push notification." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:331 -msgid "Below that field is the option to add a custom :guilabel:`Icon Image` to the push notification. This is an icon that appears beside the push notification." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:334 -msgid "To upload a new image, click the :guilabel:`✏️ (pencil) icon` when hovering over the :guilabel:`Icon Image` camera icon. Doing so reveals a pop-up window, in which the desired icon image can be located on the hard drive, and subsequently uploaded." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:338 -msgid "Once that's complete, Odoo automatically updates the visual preview of how the icon appears on the push notification." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:342 -msgid "Next, if the post is scheduled to be posted later, there is the option to ensure the post is sent in the visitor's timezone, by enabling the :guilabel:`Local Time` option. If enabled, Odoo will send it at the appropriate, pre-determined time, taking the visitor's location into consideration." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 -msgid "The Local Time option in the Push Notification Options section of features." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:351 -msgid "Then, there is the :guilabel:`Match all records` field. This field provides the ability to target a specific group of recipients in the database, based on certain criteria, and can be applied to match :guilabel:`all` or :guilabel:`any` of the rules." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:355 -msgid "To utilize this field, click the :guilabel:`+ Add condition` button, which reveals an equation-like rule field." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:358 -msgid "In this equation-like rule field, specifiy the specific criteria Odoo should take into account when sending this post to a particular target audience." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "Push notification conditions set up to match a specific amount of records in the database." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:365 -msgid "To add an additional rule, click the :guilabel:`➕ (plus sign) icon` to the far-right of the rule." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:367 -msgid "To add a branch (series of additional rules based on the previous rule, to further specify a target audience), click the unique :guilabel:`branch icon`, located to the right of the :guilabel:`➕ (plus sign) icon`." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:371 -msgid "Lastly, click the :guilabel:`🗑️ (trash can) icon` to delete any rule." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:373 -msgid "The size of the specified target audience of recipients is represented by the number of :guilabel:`Records` displayed beneath the rules." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:377 -msgid "Posts page" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:379 -msgid "To see a complete overview of posts, go to Odoo :menuselection:`Social Marketing app --> Posts`. Here, on the :guilabel:`Social Posts` page, every post that has been created and posted with Odoo can be seen and accessed." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:383 -msgid "There are four different view options for the :guilabel:`Social Posts` page data: *kanban*, *calendar*, *list*, and *pivot*." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:386 -msgid "The view options are located in the upper right corner of the :guilabel:`Posts` page, beneath the search bar." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:393 -msgid "By default, Odoo displays the posts in a kanban view. The information on this page can be sorted even further, via the left sidebar, where all connected social accounts and posts can be quickly seen, accessed, and analyzed." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:397 -msgid "The kanban view is represented by an :guilabel:`inverted bar graph icon` in the upper-right corner." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 -msgid "Kanban view of the posts page in the Odoo Social Marketing application." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:406 -msgid "The calendar view option displays a visual representation of posts in a calendar format of when posts were published, or are scheduled to be published. This option provides a clear overview of any planned day, week, or month, and Odoo displays all drafted, scheduled, and published posts." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:411 -msgid "Clicking on a date reveals a blank social media post detail form, in which a social media post can be created, and Odoo will post it on that specific date/time." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:414 -msgid "The calendar view is represented by a :guilabel:`calendar icon` in the upper-right corner." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 -msgid "Example of the calendar view in Odoo Social Marketing." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:422 -msgid "The list view option is similar to the kanban option, but instead of individual blocks, all post information is displayed in a clear, list layout. Each line of the list displays the :guilabel:`Social Accounts`, :guilabel:`Message`, and :guilabel:`Status` of every post." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:426 -msgid "There is also a helpful left sidebar that organizes all posts by :guilabel:`Status` and lists all connected :guilabel:`Social Accounts`, as well." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:429 -msgid "The list view is represented by four vertical lines in the upper-right corner." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 -msgid "View of the list option on the posts page in Odoo Social Marketing." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:435 -msgid "Pivot view" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:437 -msgid "The pivot view option provides a fully customizable grid table, where different measures of data can be added and analyzed." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 -msgid "View of the pivot option on the posts page in Odoo Social Marketing." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:444 -msgid "The pivot view option provides numerous analytical options, allowing for in-depth, detailed analysis of various posts and metrics." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:447 -msgid "Click on any :guilabel:`➕ (plus sign) icon` next to a line in the pivot table to reveal more metric options to add to the grid." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:450 -msgid "While in the pivot view, the option to :guilabel:`Insert in Spreadsheet` is available, located to the right of the :guilabel:`Measures` drop-down menu, in the upper-left corner of the :guilabel:`Social Posts` page." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:454 -msgid "Next to the :guilabel:`Insert in Spreadsheet` are three options, specific to the pivot view." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:456 -msgid "From left to right, those options are:" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:458 -msgid ":guilabel:`Flip Axis`, which switches the *X* and *Y* axis in the grid table." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:459 -msgid ":guilabel:`Expand All`, which expands each line in the grid, revealing more detailed information related to it." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:461 -msgid ":guilabel:`Download`, which, when clicked, instantly downloads the pivot table as a spreadsheet." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:465 -msgid "Visitors" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:467 -msgid "To see a complete overview of all the people who have visited the website(s) connected to the database, navigate to :menuselection:`Social Marketing app --> Visitors`." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "View of the Visitors page in the Odoo Social Marketing application." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:474 -msgid "Here, Odoo provides a detailed layout of all the visitors' pertinent information in a default kanban view. If visitors already have contact information in the database, the option to send them an :guilabel:`Email` and/or an :guilabel:`SMS` is available." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:478 -msgid "This same visitor data can also be viewed as a list or a graph. Those view options are located in the upper-right corner of the :guilabel:`Visitors` page." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:482 +#: ../../content/applications/marketing/social_marketing.rst:97 msgid "Social media page" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:484 +#: ../../content/applications/marketing/social_marketing.rst:99 msgid "Another way to quickly link social media accounts to Odoo *Social Marketing* can be done on the :guilabel:`Social Media` page. To access the :guilabel:`Social Media` page, navigate to :menuselection:`Social Marketing app --> Configuration --> Social Media`." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:488 +#: ../../content/applications/marketing/social_marketing.rst:103 msgid "On the :guilabel:`Social Media` page there is a collection of all social media options, each complete with a :guilabel:`Link account` button: :guilabel:`Facebook`, :guilabel:`Instagram`, :guilabel:`LinkedIn`, :guilabel:`Twitter`, :guilabel:`YouTube`, and :guilabel:`Push Notifications`." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +#: ../../content/applications/marketing/social_marketing.rst:-1 msgid "View of the social media page in the Odoo Social Marketing application." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:497 +#: ../../content/applications/marketing/social_marketing.rst:112 msgid "Social accounts page" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:499 +#: ../../content/applications/marketing/social_marketing.rst:114 msgid "To see a list of all social accounts and websites linked to the database, go to :menuselection:`Social Marketing app --> Configuration --> Social Accounts`. This :guilabel:`Social Accounts` display the :guilabel:`Name`, the :guilabel:`Handle/Short Name`, the :guilabel:`Social Media` platform, who it was :guilabel:`Created by`, and the :guilabel:`Company` to which it is associated." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +#: ../../content/applications/marketing/social_marketing.rst:-1 +#: ../../content/applications/marketing/social_marketing.rst:-1 msgid "View of the social accounts page in the Odoo Social Marketing application." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:509 +#: ../../content/applications/marketing/social_marketing.rst:124 msgid "To edit/modify any of the social accounts on this page, simply select the desired account from the list on this page, and proceed to make any adjustments necessary." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:513 +#: ../../content/applications/marketing/social_marketing.rst:128 msgid "Social streams page" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:515 +#: ../../content/applications/marketing/social_marketing.rst:130 msgid "To view a separate page with all the social media streams that have been added to the main *Social Marketing* dashboard, navigate to :menuselection:`Social Marketing app --> Configuration --> Social Streams`." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:523 +#: ../../content/applications/marketing/social_marketing.rst:138 msgid "Here, the social stream information is organized in a list with the :guilabel:`Social Media`, the :guilabel:`Title` of the stream, the :guilabel:`Type` of the stream (e.g. :guilabel:`Posts`, :guilabel:`Keyword`, etc.), who it was :guilabel:`Created by`, and the :guilabel:`Company` to which it is associated." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:528 +#: ../../content/applications/marketing/social_marketing.rst:143 msgid "To modify any stream's information, simply click the desired stream from the list, and proceed to make any necessary adjustments." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:532 -msgid ":doc:`/applications/marketing/social_marketing/essentials/social_campaigns`" +#: ../../content/applications/marketing/social_marketing.rst:147 +msgid "Visitors" +msgstr "" + +#: ../../content/applications/marketing/social_marketing.rst:149 +msgid "To see a complete overview of all the people who have visited the website(s) connected to the database, navigate to :menuselection:`Social Marketing app --> Visitors`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing.rst:-1 +msgid "View of the Visitors page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing.rst:156 +msgid "Here, Odoo provides a detailed layout of all the visitors' pertinent information in a default kanban view. If visitors already have contact information in the database, the option to send them an :guilabel:`Email` and/or an :guilabel:`SMS` is available." +msgstr "" + +#: ../../content/applications/marketing/social_marketing.rst:160 +msgid "This same visitor data can also be viewed as a list or a graph. Those view options are located in the upper-right corner of the :guilabel:`Visitors` page." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:3 +msgid "Social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:5 +msgid "Social marketing campaigns help companies connect directly with the marketplace. These campaigns are helpful when introducing a new product to customers, explaining the value of a product or service, or when advertising an upcoming event or product release." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:9 +msgid "The most effective social marketing campaigns typically involve multiple channels to maximize content distribution, and Odoo's *Social Marketing* application acts as a singular control center to monitor, plan, post, track, and analyze all of the various content and content channels within a single dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:17 +msgid "To access a complete overview of all social marketing campaigns, open the :menuselection:`Social Marketing` application, and click :menuselection:`Campaigns` from the header menu. Doing so reveals a separate page with every campaign in a default kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:-1 +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:-1 +msgid "View of the campaigns page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:25 +msgid "Each *stage* in the kanban view can be edited, by clicking the :guilabel:`gear icon` to the left of the :guilabel:`+ (plus sign)` - located to the right of the stage title." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:29 +msgid "The **gear icon** *only* appears when the cursor hovers to the left of the **+ (plus sign)**. When the gear icon is clicked, a drop-down menu reveals the options: :guilabel:`Fold`, :guilabel:`Edit Stage`, and :guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:37 +msgid "Clicking :guilabel:`Fold` minimizes that specific stage's column. The stage column can be restored by clicking the folded version of it on the main :guilabel:`Campaigns` dashboard in the default kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:41 +msgid "Selecting :guilabel:`Edit Stage` reveals a pop-up window, in which the name and the sequence of the stage can be modified. If changes are made, be sure to click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:44 +msgid "Clicking :guilabel:`Delete` removes the stage entirely." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:47 +msgid "To add a new stage to the pipeline, side-scroll to the right on the :guilabel:`Campaigns` dashboard, click :guilabel:`Add a Column`, enter in the desired information, and click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:52 +msgid "The same social marketing campaign information on the :guilabel:`Campaigns` dashboard can also be viewed as a list, by selecting the :guilabel:`List` option, located under the search bar, in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:57 +msgid "Create social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:59 +msgid "First, open the :menuselection:`Social Marketing` application, and select :guilabel:`Campaigns` from the header menu." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:62 +msgid "On the :guilabel:`Campaigns` dashboard, a new campaign can be created by clicking the quick add :guilabel:`+ (plus sign)` located in the top-right corner of each stage in the pipeline, visible in the kanban view. Campaigns can also be created by clicking :guilabel:`Create` in the upper-left corner of the :guilabel:`Campaigns` dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:67 +msgid "Both options reveal a new campaign detail window directly on the :guilabel:`Campaigns` dashboard when clicked." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:-1 +msgid "View of the quick add option for campaigns in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:74 +msgid "Here, the :guilabel:`Campaign Name`, :guilabel:`Responsible`, and :guilabel:`Tags` can be entered. When all modifications are complete, click :guilabel:`Add` to add the campaign to the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:78 +msgid "Edit social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:80 +msgid "In order to edit a campaign in greater detail, and create/send various forms of communications related to it, the template page for that campaign must be accessed and modified, accordingly. There are multiple ways to access a template page for a campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:84 +msgid "After entering the pertinent information in the :guilabel:`Quick Add` campaign drop-down, click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:86 +msgid "Simply select the desired campaign from the :guilabel:`Campaigns` dashboard in list or kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:88 +msgid "On the :guilabel:`Campaigns` dashboard in the kanban view, select the :guilabel:`⋮ (three dots)` drop-down menu on the desired campaign, and select :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:91 +msgid "Any of the above routes will reveal the *Campaign Template* page for that specific campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:94 +msgid "Social marketing campaign templates" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:96 +msgid "On a *Campaign Template* page, numerous elements can be customized/modified, and various forms of communications can be created, modified, and sent or scheduled. Below is a sample of a completed campaign template." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:-1 +msgid "View of a sample campaign template page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:105 +msgid "In order for the :guilabel:`Send New Mailing` option to appear on campaign templates, make sure the *Mailing Campaigns* feature is enabled in the *Email Marketing* app. To do that, navigate to :menuselection:`Email Marketing --> Configuration --> Settings`, activate :guilabel:`Mailing Campaigns`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:111 +msgid "In order for the :guilabel:`Send SMS` option to appear, the Odoo *SMS Marketing* application must be installed on the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:115 +msgid "Add content and communications to campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:117 +msgid "If the proper settings and applications are installed (as instructed above), there are four forms of communication/content options that can be added to campaigns. Each of these options are displayed as buttons in the upper-left corner of the campaign template page." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:121 +msgid ":guilabel:`Send New Mailing`: reveals a blank email template on a separate page, in which the message can be fully customized in a variety of ways." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:123 +msgid ":guilabel:`Send SMS`: reveals a blank SMS template on a separate page, in which a SMS communication can be created and configured." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:125 +msgid ":guilabel:`Send Social Post`: reveals a blank social post template on a separate page, in which a post can be created, and applied to social media accounts that are already connected to the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:128 +msgid ":guilabel:`Push Notification`: reveals a similar blank social post template on a separate page, however, the :guilabel:`Push Notification` options are already pre-selected in the :guilabel:`Post on` field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:132 +msgid "Whichever form of communication is created, once it's completed, Odoo returns to the :guilabel:`Campaign Template` page, showcasing that new content in its corresponding tab (e.g. :guilabel:`Mailings`, :guilabel:`SMS`, :guilabel:`Social Media`, and/or :guilabel:`Push Notifications`)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:137 +msgid "As content and communications are added to a campaign, tabs for those specific mediums appear, along with a variety of analytical smart buttons (e.g. :guilabel:`Revenues`, :guilabel:`Quotations`, :guilabel:`Leads`, etc.)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:141 +msgid "These smart buttons, located at the top of the template, display different metrics related to the campaign, and its various communications and content. Clicking any smart button reveals a separate page dedicated to that particular element of the campaign, allowing for quicker, more organized analysis." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:147 +msgid "The Odoo *Social Marketing* app is integrated with other Odoo applications, such as *Sales*, *Invoicing*, *CRM*, and *Website*." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:3 +msgid "Social posts" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:5 +msgid "The Odoo *Social Marketing* application provides various ways to create posts for any type of social media outlet." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:9 +msgid "Posts page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:11 +msgid "To see a complete overview of posts, go to Odoo :menuselection:`Social Marketing app --> Posts`. Here, on the :guilabel:`Social Posts` page, every post that has been created and posted with Odoo can be seen and accessed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:15 +msgid "There are four different view options for the :guilabel:`Social Posts` page data: *kanban*, *calendar*, *list*, and *pivot*." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:18 +msgid "The view options are located in the upper right corner of the :guilabel:`Posts` page, beneath the search bar." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:25 +msgid "By default, Odoo displays the posts in a kanban view. The information on this page can be sorted even further, via the left sidebar, where all connected social accounts and posts can be quickly seen, accessed, and analyzed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:29 +msgid "The kanban view is represented by an :guilabel:`inverted bar graph icon` in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:0 +msgid "Kanban view of the posts page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:38 +msgid "The calendar view option displays a visual representation of posts in a calendar format of when posts were published, or are scheduled to be published. This option provides a clear overview of any planned day, week, or month, and Odoo displays all drafted, scheduled, and published posts." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:43 +msgid "Clicking on a date reveals a blank social media post detail form, in which a social media post can be created, and Odoo will post it on that specific date/time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:46 +msgid "The calendar view is represented by a :guilabel:`calendar icon` in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:0 +msgid "Example of the calendar view in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:54 +msgid "The list view option is similar to the kanban option, but instead of individual blocks, all post information is displayed in a clear, list layout. Each line of the list displays the :guilabel:`Social Accounts`, :guilabel:`Message`, and :guilabel:`Status` of every post." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:58 +msgid "There is also a helpful left sidebar that organizes all posts by :guilabel:`Status` and lists all connected :guilabel:`Social Accounts`, as well." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:61 +msgid "The list view is represented by four vertical lines in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:0 +msgid "View of the list option on the posts page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:67 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:69 +msgid "The pivot view option provides a fully customizable grid table, where different measures of data can be added and analyzed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:0 +msgid "View of the pivot option on the posts page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:76 +msgid "The pivot view option provides numerous analytical options, allowing for in-depth, detailed analysis of various posts and metrics." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:79 +msgid "Click on any :guilabel:`➕ (plus sign) icon` next to a line in the pivot table to reveal more metric options to add to the grid." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:82 +msgid "While in the pivot view, the option to :guilabel:`Insert in Spreadsheet` is available, located to the right of the :guilabel:`Measures` drop-down menu, in the upper-left corner of the :guilabel:`Social Posts` page." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:86 +msgid "Next to the :guilabel:`Insert in Spreadsheet` are three options, specific to the pivot view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:88 +msgid "From left to right, those options are:" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:90 +msgid ":guilabel:`Flip Axis`, which switches the *X* and *Y* axis in the grid table." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:91 +msgid ":guilabel:`Expand All`, which expands each line in the grid, revealing more detailed information related to it." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:93 +msgid ":guilabel:`Download`, which, when clicked, instantly downloads the pivot table as a spreadsheet." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:97 +msgid "Posts" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:99 +msgid "Clicking on a post from a social media stream reveals a pop-up window, showcasing the content of that specific post, along with all the engagement data related to it (e.g. likes, comments, etc.)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "Sample of a social media post's pop-up window in Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:106 +msgid "If desired, the user can leave a new comment of the post from the post's pop-up window, by typing one in the :guilabel:`Write a comment...` field, and clicking :guilabel:`Enter` to post that comment." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:111 +msgid "Create leads from comments" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:113 +msgid "Odoo *Social Marketing* also provides the ability to create leads directly from social media comments." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:116 +msgid "To create a lead from a comment left on a social media post, click on the desired post from the dashboard to reveal that post's specific pop-up window. Then, scroll to the desired comment, and click the :guilabel:`three vertical dots` icon to the right of that comment." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:120 +msgid "Doing so reveals a drop-down menu with the option: :guilabel:`Create Lead`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "The drop-down menu beside a comment revealing the option to create a lead." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:126 +msgid "Upon clicking :guilabel:`Create Lead` from the comment's drop-down menu, a :guilabel:`Conver Post to Lead` pop-up window appears." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "The convert post to lead pop-up window that appears in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:133 +msgid "In this pop-up window, select to either: :guilabel:`Create a new customer`, :guilabel:`Link to an existing customer`, or :guilabel:`Do not link to a customer`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:137 +msgid "If :guilabel:`Link to an existing customer` is selected, a new :guilabel:`Customer` field appears beneath those options, wherein a customer can be chosen to be linked to this lead." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:140 +msgid "Once the desired selection has been made, click the :guilabel:`Convert` button at the bottom of the :guilabel:`Convert Post to Lead` pop-up window. Doing so reveals a fresh lead detail form, where the necessary information can be entered and processed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "New lead detail form generated from a social media comment in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:149 +msgid "Insights" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:151 +msgid "When a social media account stream is added to the *Social Marketing* dashboard, each stream also displays and links that specific social media platform's KPIs (if the platform has them)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:154 +msgid "To get redirected to the statistics and metrics related to any social media account's KPIs, click on the :guilabel:`Insights` link, located at the top of each stream." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "Visual of how the Insights link appears on the dashboard of the Social Marketing app." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:162 +msgid "In a multi-company environment, if not *all* pages are selected, de-authentication happens." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:164 +msgid "For example, if the companies have 3 *Facebook* pages, but only grant access to 1, and try to grant access to another at a later date, they will be de-authenticated, and access to the initial page's insights/analytics will be lost." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:168 +msgid "So, be sure to add *all* pages for *all* companies in a multi-company environment to avoid this issue. If a page gets de-autenticated, simply remove the stream, and re-establish it." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:172 +msgid "Create and post social media content" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:174 +msgid "Odoo *Social Marketing* offers the ability to create and post content for social media accounts directly through the application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:177 +msgid "To create content for social media accounts, navigated to the :menuselection:`Social Marketing app`, and click :guilabel:`New Post` located in the upper-right corner of the *Social Marketing* dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "New Post button on the main dashboard of the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:185 +msgid "Or, navigate to :menuselection:`Social Marketing app --> Posts` and click the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "New button on the Social Posts page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:192 +msgid "Either route reveals a blank social media post detail form that can be customized and configured in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "Blank social media post detail page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:200 +msgid "Post detail form" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:202 +msgid "The social media post detail form in Odoo *Social Marketing* has many different configurable options available." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:206 +msgid "Company" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:208 +msgid "If working in a multi-company environment, the first field in the :guilabel:`Your Post` section of the social media post detail form is :guilabel:`Company`. In this field, select the company that should be connected to this specific social media post." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:213 +msgid "Post on" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:215 +msgid "If working in a single-company environment, the first field in the :guilabel:`Your Post` section of the social media post detail form is :guilabel:`Post on`. In this field, determine which social media outlets (streams) this post is intended to be posted on, and/or which website's visitors this post should be sent to, via push notification, by checking the box beside the desired option(s)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:220 +msgid "Odoo automatically provides every available social media account that's been linked to the database as an option in this section. If a social media account hasn't been added as a stream to the *Social Marketing* application, it will **not** appear as an option on the post template." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:224 +msgid "Multiple social media outlets (streams) and websites can be selected in the :guilabel:`Post on` field. At least **one** option in the :guilabel:`Post on` field *must* be selected." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:228 +msgid "In order for the :guilabel:`Push Notification` option to appear on the social media post detail form in Odoo *Social Marketing*, make sure the *Enable Web Push Notifications* feature is enabled in the *Website* app." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:232 +msgid "To do that, navigate to :menuselection:`Website app --> Configuration --> Settings`, activate :guilabel:`Enable Web Push Notifications`, fill out the corresponding fields, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:237 +msgid "Message" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:239 +msgid "Next, there's the :guilabel:`Message` field. This is where the main content of the post is created." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:241 +msgid "In the :guilabel:`Message` field, type in the desired message for the social post. After typing, click away from the :guilabel:`Message` field to reveal visual samples of how the post will look on all the previously selected social media accounts (and/or websites, as push notifications)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "Sample social media post with visual samples of how it will appear on social media outlets." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:250 +msgid "Emojis can also be added directly to the text in the :guilabel:`Message` field. Just click the :guilabel:`🙂 (smiley face)` icon, located on the line of the :guilabel:`Message` field to the far right. Clicking this icon reveals a drop-down menu containing numerous emojis to choose from." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:255 +msgid "If :guilabel:`Twitter` is chosen in the :guilabel:`Post on` field, a character counter appears beneath the :guilabel:`Message` field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:259 +msgid "Attach Images" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:261 +msgid "If images are to be used in the post, click the :guilabel:`Attach Images` button, in the :guilabel:`Attach Images` field, located beneath the :guilabel:`Message` field. When clicked, Odoo reveals a pop-up window. In this pop-up window, select the desired image from the hard drive, and upload it." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:266 +msgid "After successfully uploading and attaching the desired image, Odoo reveals a new preview of the social media post, complete with the newly-added image, on the right side of the detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "Visualized samples of post with newly-attached images in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:274 +msgid "Campaign" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:276 +msgid "Next, there is the :guilabel:`Campaign` field. This non-required field provides the options to attach this post to a specific marketing campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:279 +msgid "To add this post to a pre-existing campaign, click the empty :guilabel:`Campaign` field to reveal a drop-down menu, containing all the existing campaigns in the database. Select the desired campaign from this drop-down menu to add this post to that campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:283 +msgid "To create a new campaign directly from the social media post detail form, start typing the name of the new campaign in the blank :guilabel:`Campaign` field, and select either :guilabel:`Create` or :guilabel:`Create and edit...`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "Drop-down menu options of Create or Create and edit in the Campaign field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:291 +msgid "Clicking :guilabel:`Create` creates the campaign, which can be edited/customized later." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:293 +msgid "Clicking :guilabel:`Create and edit...` creates the campaign, and reveals a :guilabel:`Create Campaign` pop-up form, wherein the :guilabel:`Campaign Identifier`, :guilabel:`Responsible`, and :guilabel:`Tags` can be instantly configured." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "Create campaign pop-up window that appears on a social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:301 +msgid "When all the desired settings have been entered, click :guilabel:`Save & Close` to save the campaign and return to the social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:305 +msgid "When" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:307 +msgid "Then, in the :guilabel:`When` field, choose either :guilabel:`Send Now` to have Odoo publish the post immediately, or :guilabel:`Schedule later` to have Odoo publish the post at a later date and time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:311 +msgid "If :guilabel:`Schedule later` is selected, a new :guilabel:`Scheduled Date` field appears. Clicking the empty field reveals a pop-up calendar, in which a future date and time can be designated." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "Schedule date pop-up window that appears on social media post detail form in Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:318 +msgid "After selecting a desired date and time, click :guilabel:`Apply`. Then, Odoo will promptly publish the post at that specific date and time on the pre-detemined social media account(s)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:322 +msgid "If scheduling a post, the :guilabel:`Post` button at the top of the social media post detail form changes to :guilabel:`Schedule`. Be sure to click :guilabel:`Schedule` after completing the social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:326 +msgid "Doing so, locks in that specific date/time for Odoo to send the post, and it changes the status of the post to :guilabel:`Scheduled`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:330 +msgid "Push Notification Options" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:332 +msgid "If one (or multiple) :guilabel:`[Push Notification]` options are chosen in the :guilabel:`Post on` field, a specific :guilabel:`Push Notification Options` section appears at the bottom of the social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "Push notification options section on a social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:340 +msgid "It should be noted that *none* of these fields are required." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:342 +msgid "The first field in this section is :guilabel:`Notification Title`. In this field, there is the option to add a custom title to the push notification that will be sent." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:345 +msgid "To designate a specific page on the website that should trigger this push notification, enter that page's URL in the :guilabel:`Target URL` field. Then, once a visitor reaches that specific page, Odoo will display the push notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:349 +msgid "Below that field is the option to add a custom :guilabel:`Icon Image` to the push notification. This is an icon that appears beside the push notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:352 +msgid "To upload a new image, click the :guilabel:`✏️ (pencil) icon` when hovering over the :guilabel:`Icon Image` camera icon. Doing so reveals a pop-up window, in which the desired icon image can be located on the hard drive, and subsequently uploaded." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:356 +msgid "Once that's complete, Odoo automatically updates the visual preview of how the icon appears on the push notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:360 +msgid "Next, if the post is scheduled to be posted later, there is the option to ensure the post is sent in the visitor's timezone, by enabling the :guilabel:`Local Time` option. If enabled, Odoo will send it at the appropriate, pre-determined time, taking the visitor's location into consideration." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:0 +msgid "The Local Time option in the Push Notification Options section of features." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:369 +msgid "Then, there is the :guilabel:`Match all records` field. This field provides the ability to target a specific group of recipients in the database, based on certain criteria, and can be applied to match :guilabel:`all` or :guilabel:`any` of the rules." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:373 +msgid "To utilize this field, click the :guilabel:`+ Add condition` button, which reveals an equation-like rule field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:376 +msgid "In this equation-like rule field, specifiy the specific criteria Odoo should take into account when sending this post to a particular target audience." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:-1 +msgid "Push notification conditions set up to match a specific amount of records in the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:383 +msgid "To add an additional rule, click the :guilabel:`➕ (plus sign) icon` to the far-right of the rule." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:385 +msgid "To add a branch (series of additional rules based on the previous rule, to further specify a target audience), click the unique :guilabel:`branch icon`, located to the right of the :guilabel:`➕ (plus sign) icon`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:389 +msgid "Lastly, click the :guilabel:`🗑️ (trash can) icon` to delete any rule." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:391 +msgid "The size of the specified target audience of recipients is represented by the number of :guilabel:`Records` displayed beneath the rules." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/social_posts.rst:395 +msgid ":doc:`social_campaigns`" msgstr "" #: ../../content/applications/marketing/surveys.rst:5 @@ -8356,6 +8747,10 @@ msgstr "" msgid "When the :guilabel:`Question Time Limit` option is enabled, designate how much time (in :guilabel:`seconds`) participants have to answer the question during a *Live Session* survey." msgstr "" +#: ../../content/applications/marketing/surveys/questions.rst:336 +msgid "Survey text colors are directly linked to the colors used for the :doc:`website theme <../../websites/website/web_design/themes>`." +msgstr "" + #: ../../content/applications/marketing/surveys/scoring.rst:3 msgid "Scoring surveys" msgstr "" diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index daa9ceea1..42f08ae24 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 13:30+0000\n" +"POT-Creation-Date: 2024-08-21 11:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -868,6 +868,7 @@ msgid "The :guilabel:`Deduplication Rules` page (:menuselection:`Data Cleaning a msgstr "" #: ../../content/applications/productivity/data_cleaning.rst:133 +#: ../../content/applications/productivity/data_cleaning.rst:255 msgid "These rules can be configured for each model in the database, and with varying levels of specificity." msgstr "" @@ -972,22 +973,190 @@ msgid "Recycle records" msgstr "" #: ../../content/applications/productivity/data_cleaning.rst:214 -msgid "On the :guilabel:`Field Recycle Records` dashboard (:menuselection:`Data Cleaning app --> Recycle Records`), Odoo detects records that can be archived or deleted, by matching conditions within the records set by the recycle record's rules." +msgid "Use the *Recycle Records* feature to rid the database of old and outdated records." msgstr "" -#: ../../content/applications/productivity/data_cleaning.rst:221 -msgid "Field cleaning" +#: ../../content/applications/productivity/data_cleaning.rst:216 +msgid "On the :guilabel:`Field Recycle Records` dashboard (:menuselection:`Data Cleaning app --> Recycle Records`), Odoo detects records that can be archived or deleted, by matching conditions within the records set by the :ref:`recycle record's rules `." msgstr "" -#: ../../content/applications/productivity/data_cleaning.rst:223 -msgid "On the :guilabel:`Field Cleaning Records* dashboard (:menuselection:`Data Cleaning app --> Field Cleaning`), Odoo suggests formatting changes to data in fields of a record, to follow a convention set by the field cleaning rules." +#: ../../content/applications/productivity/data_cleaning.rst:-1 +msgid "Field Recycle Records dashboard in the Data Cleaning application." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:224 +msgid "The :guilabel:`RECYCLE RULES` sidebar lists each of the active recycle record rules, and displays the total number of records detected beside each rule." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:227 +msgid "By default, the :guilabel:`All` option is selected. Records are displayed in the list view, with the following columns:" msgstr "" #: ../../content/applications/productivity/data_cleaning.rst:230 +msgid ":guilabel:`Record ID`: the ID of the original record." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:231 +msgid ":guilabel:`Record Name`: the name or title of the original record." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:233 +msgid "Select a specific rule in the :guilabel:`RECYCLE RULES` sidebar to filter the duplicate records." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:235 +msgid "To recycle records, click the :icon:`fa-check` :guilabel:`Validate` button on the row of the record." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:237 +msgid "Upon doing so, the record is recycled, depending on how the rule is configured, to be either archived or deleted from the database." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:241 +msgid "Discard groupings by clicking the :icon:`fa-times` :guilabel:`Discard` button. Upon doing so, the record is hidden from the list, and is not detected by the recycle rule again in the future." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:244 +msgid "View discarded records by selecting the :guilabel:`Discarded` filter from the :ref:`search bar ` drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:250 +msgid "Recycle record rules" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:252 +msgid "The :guilabel:`Recycle Records Rules` page (:menuselection:`Data Cleaning app --> Configuration --> Rules: Recycle Records`) is where the conditions for records to be recycled can be set." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:259 +msgid "The recycle rules run once a day, by default, as part of a scheduled action chron (*Data Recycle: Clean Records*). However, each rule can be :ref:`run manually ` anytime." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:263 +msgid "By default, no recycle record rules exist. Click the :guilabel:`New` button to create a new rule." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:265 +msgid "On the recycle record rule form, first choose a :guilabel:`Model` for this rule to target. Selecting a model updates the rule title to the chosen model." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:268 +msgid "Optionally, configure a :guilabel:`Filter` to specify the records eligible for this rule. The number of eligible records is shown in the :icon:`oi-arrow-right` :guilabel:`# record(s)` link." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:271 +msgid "Next, configure the field and time range for how the rule detects the records to recycle:" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:273 +msgid ":guilabel:`Time Field`: select a field from the model to base the time (:dfn:`Delta`)." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:274 +msgid ":guilabel:`Delta`: type the length of time, which must be a whole number (e.g. `7`)." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:275 +msgid ":guilabel:`Delta Unit`: select the unit of time (:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or :guilabel:`Years`)." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:278 +msgid "Then, select a :guilabel:`Recycle Mode`:" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:280 +msgid ":guilabel:`Manual`: requires each detected record to be manually recycled, and enables the :guilabel:`Notify Users` field." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:282 +msgid ":guilabel:`Automatic`: automatically merges recycled groupings, without notifying users." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:284 +msgid "Lastly, select a :guilabel:`Recycle Action` to either :guilabel:`Archive` or :guilabel:`Delete` records. If :guilabel:`Delete` is selected, choose whether or not to :guilabel:`Include Archived` records in the rule." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:288 +msgid "With the rule's configuration complete, either close the rule form, or :ref:`run the rule manually ` to instantly capture records to recycle." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:292 +msgid "A recycle rule can be configured to delete archived leads and opportunities that were last updated a year ago, and with a specific lost reason, by using the following configuration:" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:295 +msgid ":guilabel:`Model`: :guilabel:`Lead/Opportunity`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:296 +msgid ":guilabel:`Filter`:" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:298 +msgid "`Active` `is` `not set`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:299 +msgid "`Lost Reason` `is in` `Too expensive`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:301 +msgid ":guilabel:`Time Field`: :guilabel:`Last Updated on (Lead/Opportunity)`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:302 +msgid ":guilabel:`Delta`: `1`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:303 +msgid ":guilabel:`Delta Unit`: :guilabel:`Years`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:304 +msgid ":guilabel:`Recycle Mode`: :guilabel:`Automatic`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:305 +msgid ":guilabel:`Recycle Action`: :guilabel:`Delete`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:306 +msgid ":guilabel:`Include Archived`: :icon:`fa-check-square`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:0 +msgid "Recycle records rule form for a lead/opportunity." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:315 +msgid "Manually run a recycle rule" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:317 +msgid "To manually run a specific recycle rule at any time, navigate to :menuselection:`Data Cleaning app --> Configuration --> Rules: Recycle Records`, and select the rule to run." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:320 +msgid "Then, on the rule form, click the :guilabel:`Run Now` button on the top-left. Upon doing so, the :icon:`fa-bars` :guilabel:`Records` smart button displays the number of records captured." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:323 +msgid "Click the :icon:`fa-bars` :guilabel:`Records` smart button to manage these records." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:328 +msgid "Field cleaning" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:330 +msgid "On the :guilabel:`Field Cleaning Records` dashboard (:menuselection:`Data Cleaning app --> Field Cleaning`), Odoo suggests formatting changes to data in fields of a record, to follow a convention set by the field cleaning rules." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:337 msgid "Merge action manager" msgstr "" -#: ../../content/applications/productivity/data_cleaning.rst:232 +#: ../../content/applications/productivity/data_cleaning.rst:339 msgid "The :guilabel:`Merge Action Manager` (:menuselection:`Data Cleaning app --> Configuration --> Merge Action Manager`) enables or disables the *Merge* action available in the *Actions* menu for models in the database." msgstr "" @@ -1872,7 +2041,7 @@ msgid "Three tabs are available: :ref:`Tags `, :ref:`Access Righ msgstr "" #: ../../content/applications/productivity/documents.rst:58 -#: ../../content/applications/productivity/sign.rst:250 +#: ../../content/applications/productivity/sign.rst:290 msgid "Tags" msgstr "" @@ -2101,7 +2270,7 @@ msgid "Upload by email" msgstr "" #: ../../content/applications/productivity/documents.rst:252 -msgid "Select the :guilabel:`Download and Upload` option to enable users to upload their files to your workspace using an :guilabel:`Email Alias`. To create the email alias, enter its name in the :guilabel:`Email Alias` field. The :doc:`domain name <../general/email_communication/email_servers>` should be set by default, but you can modify it by clicking it." +msgid "Select the :guilabel:`Download and Upload` option to enable users to upload their files to your workspace using an :guilabel:`Email Alias`. To create the email alias, enter its name in the :guilabel:`Email Alias` field. The :doc:`domain name <../general/email_communication>` should be set by default, but you can modify it by clicking it." msgstr "" #: ../../content/applications/productivity/documents.rst:257 @@ -3202,58 +3371,218 @@ msgid "Other countries" msgstr "" #: ../../content/applications/productivity/sign.rst:88 -msgid ":doc:`Australia `" +msgid ":doc:`Algeria `" msgstr "" #: ../../content/applications/productivity/sign.rst:89 -msgid ":doc:`Brazil `" +msgid ":doc:`Angola `" msgstr "" #: ../../content/applications/productivity/sign.rst:90 -msgid ":doc:`Canada `" +msgid ":doc:`Argentina `" msgstr "" #: ../../content/applications/productivity/sign.rst:91 -msgid ":doc:`China `" +msgid ":doc:`Australia `" msgstr "" #: ../../content/applications/productivity/sign.rst:92 -msgid ":doc:`India `" +msgid ":doc:`Azerbaijan `" msgstr "" #: ../../content/applications/productivity/sign.rst:93 -msgid ":doc:`Japan `" +msgid ":doc:`Bangladesh `" msgstr "" #: ../../content/applications/productivity/sign.rst:94 -msgid ":doc:`Mexico `" +msgid ":doc:`Brazil `" msgstr "" #: ../../content/applications/productivity/sign.rst:95 -msgid ":doc:`Russia `" +msgid ":doc:`Canada `" msgstr "" #: ../../content/applications/productivity/sign.rst:96 -msgid ":doc:`South Korea `" +msgid ":doc:`Chile `" msgstr "" #: ../../content/applications/productivity/sign.rst:97 -msgid ":doc:`United Kingdom `" +msgid ":doc:`China `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:98 +msgid ":doc:`Colombia `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:99 +msgid ":doc:`Dominican Republic `" msgstr "" #: ../../content/applications/productivity/sign.rst:100 -msgid "Send a document to sign" +msgid ":doc:`Ecuador `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:101 +msgid ":doc:`Egypt `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:102 +msgid ":doc:`Ethiopia `" msgstr "" #: ../../content/applications/productivity/sign.rst:103 -msgid "One-time signature" +msgid ":doc:`Guatemala `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:104 +msgid ":doc:`Hong Kong `" msgstr "" #: ../../content/applications/productivity/sign.rst:105 -msgid "You can click :guilabel:`Upload a PDF to sign` from your dashboard for a one-time signature. Select your document, open it, and drag and drop the required :ref:`fields ` in your document. You can modify the :ref:`role ` assigned to a field by clicking on it and selecting the one you want." +msgid ":doc:`India `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:106 +msgid ":doc:`Indonesia `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:107 +msgid ":doc:`Iran `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:108 +msgid ":doc:`Iraq `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:109 +msgid ":doc:`Israel `" msgstr "" #: ../../content/applications/productivity/sign.rst:110 +msgid ":doc:`Japan `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:111 +msgid ":doc:`Kazakhstan `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:112 +msgid ":doc:`Kenya `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:113 +msgid ":doc:`Kuwait `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:114 +msgid ":doc:`Malaysia `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:115 +msgid ":doc:`Mexico `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:116 +msgid ":doc:`Morocco `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:117 +msgid ":doc:`New Zealand `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:118 +msgid ":doc:`Nigeria `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:119 +msgid ":doc:`Norway `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:120 +msgid ":doc:`Oman `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:121 +msgid ":doc:`Pakistan `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:122 +msgid ":doc:`Peru `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:123 +msgid ":doc:`Philippines `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:124 +msgid ":doc:`Qatar `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:125 +msgid ":doc:`Russia `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:126 +msgid ":doc:`Saudi Arabia `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:127 +msgid ":doc:`Singapore `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:128 +msgid ":doc:`South Africa `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:129 +msgid ":doc:`South Korea `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:130 +msgid ":doc:`Switzerland `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:131 +msgid ":doc:`Thailand `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:132 +msgid ":doc:`Turkey `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:133 +msgid ":doc:`Ukraine `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:134 +msgid ":doc:`United Arab Emirates `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:135 +msgid ":doc:`United Kingdom `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:136 +msgid ":doc:`Uzbekistan `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:137 +msgid ":doc:`Vietnam `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:140 +msgid "Send a document to sign" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:143 +msgid "One-time signature" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:145 +msgid "You can click :guilabel:`Upload a PDF to sign` from your dashboard for a one-time signature. Select your document, open it, and drag and drop the required :ref:`fields ` in your document. You can modify the :ref:`role ` assigned to a field by clicking on it and selecting the one you want." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:150 msgid "When ready, click :guilabel:`Send`, and fill in the required fields. Once sent, your document remains available. Go to :menuselection:`Documents --> All Documents` to see your document and the status of the signatures." msgstr "" @@ -3261,84 +3590,84 @@ msgstr "" msgid "Signature status" msgstr "" -#: ../../content/applications/productivity/sign.rst:118 +#: ../../content/applications/productivity/sign.rst:158 msgid "Validity dates and reminders" msgstr "" -#: ../../content/applications/productivity/sign.rst:120 +#: ../../content/applications/productivity/sign.rst:160 msgid "You can set **validity dates** on limited-duration agreement documents or send **automatic email reminders** to obtain signatures on time. From your dashboard, click :guilabel:`Send` on your document. On the new page, go to the :guilabel:`Options` section and fill in the :guilabel:`Valid Until` and :guilabel:`Reminder` fields." msgstr "" -#: ../../content/applications/productivity/sign.rst:126 +#: ../../content/applications/productivity/sign.rst:166 #: ../../content/applications/productivity/spreadsheet/templates.rst:3 msgid "Templates" msgstr "" -#: ../../content/applications/productivity/sign.rst:128 +#: ../../content/applications/productivity/sign.rst:168 msgid "You can create document templates when you have to send the same document several times. From your dashboard, click :guilabel:`Upload a PDF template`. Select the document and add the required :ref:`fields `. You can modify the :ref:`role ` of a field by clicking on it and selecting the one you want." msgstr "" -#: ../../content/applications/productivity/sign.rst:133 +#: ../../content/applications/productivity/sign.rst:173 msgid "Click :guilabel:`Template Properties` to add :guilabel:`Tags` to your template, define a :guilabel:`Signed Document Workspace`, add :guilabel:`Signed Document Tags`, set a :guilabel:`Redirect Link` that will be available in the signature confirmation message received after the signature, or define :guilabel:`Authorized Users` if you want to restrict the use of your template to specific authorized users or groups." msgstr "" -#: ../../content/applications/productivity/sign.rst:139 +#: ../../content/applications/productivity/sign.rst:179 msgid "Your templates are visible by default on your dashboard. You can click :guilabel:`Send` to quickly send a document template to a signer or :guilabel:`Sign Now` if you are ready to sign your document immediately." msgstr "" -#: ../../content/applications/productivity/sign.rst:144 +#: ../../content/applications/productivity/sign.rst:184 msgid "You can **create a template from a document that was previously sent**. To do so, go to :menuselection:`Documents --> All Documents`. On the document you want to retrieve, click on the the vertical ellipsis (:guilabel:`⋮`), then :guilabel:`Template`. Click on the vertical ellipsis (:guilabel:`⋮`) again, then :guilabel:`Restore`. Your document now appears on your dashboard next to your other templates." msgstr "" -#: ../../content/applications/productivity/sign.rst:153 +#: ../../content/applications/productivity/sign.rst:193 msgid "Roles" msgstr "" -#: ../../content/applications/productivity/sign.rst:155 +#: ../../content/applications/productivity/sign.rst:195 msgid "Each field in a Sign document is related to a role corresponding to a specific person. When a document is being signed, the person assigned to the role must fill in their assigned fields and sign it." msgstr "" -#: ../../content/applications/productivity/sign.rst:159 +#: ../../content/applications/productivity/sign.rst:199 msgid "Roles are available by going to :menuselection:`Sign --> Configuration --> Roles`." msgstr "" -#: ../../content/applications/productivity/sign.rst:161 +#: ../../content/applications/productivity/sign.rst:201 msgid "It is possible to update existing roles or to create new roles by clicking on :guilabel:`New`. Choose a :guilabel:`Role Name`, add an :guilabel:`Extra Authentication Step` to confirm the identity of the signing person, and if the document can be reassigned to another contact, select :guilabel:`Change Authorized` for the role. A :guilabel:`Color` can also be chosen for the role. This color can help understand which roles are responsible for which field when configuring a template." msgstr "" -#: ../../content/applications/productivity/sign.rst:169 +#: ../../content/applications/productivity/sign.rst:209 msgid "Secured identification" msgstr "" -#: ../../content/applications/productivity/sign.rst:171 +#: ../../content/applications/productivity/sign.rst:211 msgid "As the owner of a document, you may request an :guilabel:`Extra Authentication Step` through :ref:`SMS verification ` or via :ref:`Itsme® ` (available in Belgium and the Netherlands). Both authentication options require :ref:`credits `. If you do not have any credits left, the authentication steps will be skipped." msgstr "" -#: ../../content/applications/productivity/sign.rst:177 +#: ../../content/applications/productivity/sign.rst:217 msgid ":doc:`In-App Purchase (IAP) <../essentials/in_app_purchase>`" msgstr "" -#: ../../content/applications/productivity/sign.rst:178 -msgid ":doc:`SMS pricing and FAQ <../marketing/sms_marketing/pricing/pricing_and_faq>`" +#: ../../content/applications/productivity/sign.rst:218 +msgid ":doc:`SMS pricing and FAQ <../marketing/sms_marketing/pricing_and_faq>`" msgstr "" -#: ../../content/applications/productivity/sign.rst:183 +#: ../../content/applications/productivity/sign.rst:223 msgid "SMS verification" msgstr "" -#: ../../content/applications/productivity/sign.rst:185 +#: ../../content/applications/productivity/sign.rst:225 msgid "Go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Unique Code Via SMS`." msgstr "" -#: ../../content/applications/productivity/sign.rst:189 +#: ../../content/applications/productivity/sign.rst:229 msgid "Before being able to send SMS Text Messages, you need to register your phone number. To do so, go to :menuselection:`Sign --> Configuration --> Settings` and click :guilabel:`Buy credits` under :guilabel:`Authenticate by SMS`." msgstr "" -#: ../../content/applications/productivity/sign.rst:193 +#: ../../content/applications/productivity/sign.rst:233 msgid "Go to the document to sign, add the field for which the SMS verification is required, for example, the :guilabel:`Signature` field, and click :guilabel:`Send`. On the new page, select the :guilabel:`customer` and click :guilabel:`Send`." msgstr "" -#: ../../content/applications/productivity/sign.rst:197 +#: ../../content/applications/productivity/sign.rst:237 msgid "The person signing the document fills in the :guilabel:`Signature` field, then :guilabel:`Sign`, and clicks :guilabel:`Validate & Send Completed Document`. A :guilabel:`Final Validation` page pops up where to add their phone number. One-time codes are sent by SMS." msgstr "" @@ -3346,27 +3675,27 @@ msgstr "" msgid "Add a hash to your document" msgstr "" -#: ../../content/applications/productivity/sign.rst:205 +#: ../../content/applications/productivity/sign.rst:245 msgid "This feature is enabled by default." msgstr "" -#: ../../content/applications/productivity/sign.rst:206 +#: ../../content/applications/productivity/sign.rst:246 msgid "As soon as the :guilabel:`Extra Authentication Step` applies to a role, this validation step is requested for any field assigned to this role." msgstr "" -#: ../../content/applications/productivity/sign.rst:212 +#: ../../content/applications/productivity/sign.rst:252 msgid "Itsme®" msgstr "" -#: ../../content/applications/productivity/sign.rst:214 +#: ../../content/applications/productivity/sign.rst:254 msgid "Itsme® authentication can be used to allow signatories to provide their identity using itsme®. This feature is only available in **Belgium** and the **Netherlands**." msgstr "" -#: ../../content/applications/productivity/sign.rst:217 +#: ../../content/applications/productivity/sign.rst:257 msgid "The feature can be enabled in :guilabel:`Sign Settings` and applies automatically to the :guilabel:`Customer (identified with itsme®)` role. To enable it for other roles, go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Via itsme®`." msgstr "" -#: ../../content/applications/productivity/sign.rst:222 +#: ../../content/applications/productivity/sign.rst:262 msgid "Go to the document that needs to be signed and add the :guilabel:`Signature` field. Switch to any role configured to use the feature, and click :guilabel:`Validate` and :guilabel:`Send`." msgstr "" @@ -3374,19 +3703,19 @@ msgstr "" msgid "select customer identified with itsme®" msgstr "" -#: ../../content/applications/productivity/sign.rst:228 +#: ../../content/applications/productivity/sign.rst:268 msgid "Upon signing the document, the signer completes the :guilabel:`Signature` field and proceeds by clicking on :guilabel:`Validate & Send Completed Document`, triggering a :guilabel:`Final verification` page where authentication via itsme® is required." msgstr "" -#: ../../content/applications/productivity/sign.rst:233 +#: ../../content/applications/productivity/sign.rst:273 msgid "Signatory hash" msgstr "" -#: ../../content/applications/productivity/sign.rst:235 +#: ../../content/applications/productivity/sign.rst:275 msgid "Each time someone signs a document, a **hash** - a unique digital signature of the operation - is generated to ensure traceability, integrity, and inalterability. This process guarantees that any changes made after a signature is affixed can be easily detected, maintaining the document's authenticity and security throughout its lifecycle." msgstr "" -#: ../../content/applications/productivity/sign.rst:240 +#: ../../content/applications/productivity/sign.rst:280 msgid "A visual security frame displaying the beginning of the hash is added to the signatures. Internal users can hide or show it by turning the :guilabel:`Frame` option on or off when signing the document." msgstr "" @@ -3394,103 +3723,103 @@ msgstr "" msgid "Adding the visual security frame to a signature." msgstr "" -#: ../../content/applications/productivity/sign.rst:252 +#: ../../content/applications/productivity/sign.rst:292 msgid "Tags can be used to categorize and organize documents, allowing users to quickly search for and filter documents based on specific criteria." msgstr "" -#: ../../content/applications/productivity/sign.rst:255 +#: ../../content/applications/productivity/sign.rst:295 msgid "You can manage tags by going to :menuselection:`Configuration --> Tags`. To create a tag, click :guilabel:`New`. On the new line, add the :guilabel:`Tag Name` and select a :guilabel:`Color Index` for your tag." msgstr "" -#: ../../content/applications/productivity/sign.rst:259 +#: ../../content/applications/productivity/sign.rst:299 msgid "To apply a tag to a document, use the dropdown list available in your document." msgstr "" -#: ../../content/applications/productivity/sign.rst:262 +#: ../../content/applications/productivity/sign.rst:302 msgid "You can modify the tags of a signed document by going to :menuselection:`Documents --> All Documents`, clicking the vertical ellipsis (:guilabel:`⋮`) on your document, then :guilabel:`Details`, and modifying your :guilabel:`Tags`." msgstr "" -#: ../../content/applications/productivity/sign.rst:267 +#: ../../content/applications/productivity/sign.rst:307 msgid "Sign order" msgstr "" -#: ../../content/applications/productivity/sign.rst:269 +#: ../../content/applications/productivity/sign.rst:309 msgid "When a document needs to be signed by different parties, the signing order lets you control the order in which your recipients receive it for signature." msgstr "" -#: ../../content/applications/productivity/sign.rst:272 -msgid "After uploading a PDF with at least two signature fields with two different roles and clicking :guilabel:`Send`, toggle the :guilabel:`Specify Signing Order` button and search for the signer's name or email information to add them. You can decide on the signing order by typing **1** or **2** in the first column." +#: ../../content/applications/productivity/sign.rst:312 +msgid "After uploading a PDF with at least two signature fields with two different roles and clicking :guilabel:`Send`, toggle the :guilabel:`Specify Signing Order` switch and search for the signer's name or email information to add them. You can decide on the signing order by typing **1** or **2** in the first column." msgstr "" -#: ../../content/applications/productivity/sign.rst:277 +#: ../../content/applications/productivity/sign.rst:-1 +msgid "Toggle the switch to specify the signing order." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:320 msgid "Each recipient receives the signature request notification only once the previous recipient has completed their action." msgstr "" -#: ../../content/applications/productivity/sign.rst:281 -msgid "`Odoo Quick Tips: Sign order [video] `_" -msgstr "" - -#: ../../content/applications/productivity/sign.rst:286 +#: ../../content/applications/productivity/sign.rst:326 msgid "Field types" msgstr "" -#: ../../content/applications/productivity/sign.rst:288 +#: ../../content/applications/productivity/sign.rst:328 msgid "Fields are used in a document to indicate what information must be completed by the signers. You can add fields to your document simply by dragging and dropping them for the left column into your document." msgstr "" -#: ../../content/applications/productivity/sign.rst:292 +#: ../../content/applications/productivity/sign.rst:332 msgid "Various field types can be used to sign documents (placeholder, autocompletion, etc.). By configuring your own field types, also known as signature item types, the signing process can be even faster for your customers, partners, and employees." msgstr "" -#: ../../content/applications/productivity/sign.rst:296 +#: ../../content/applications/productivity/sign.rst:336 msgid "To create and edit field types, go to :menuselection:`Sign --> Configuration --> Settings --> Edit field types`." msgstr "" -#: ../../content/applications/productivity/sign.rst:299 +#: ../../content/applications/productivity/sign.rst:339 msgid "You can select an existing field by clicking on it, or you can :guilabel:`Create` a new one. First, edit the :guilabel:`Field Name`. Then, select a :guilabel:`Field Type`:" msgstr "" -#: ../../content/applications/productivity/sign.rst:302 +#: ../../content/applications/productivity/sign.rst:342 msgid ":guilabel:`Signature`: users are asked to enter their signature either by drawing it, generating an automatic one based on their name, or uploading a local file (usually an image). Each subsequent :guilabel:`Signature` field type then reuses the data entered in the first field." msgstr "" -#: ../../content/applications/productivity/sign.rst:305 +#: ../../content/applications/productivity/sign.rst:345 msgid ":guilabel:`Initial`: users are asked to enter their initials, in a similar way to the :guilabel:`Signature` field." msgstr "" -#: ../../content/applications/productivity/sign.rst:307 +#: ../../content/applications/productivity/sign.rst:347 msgid ":guilabel:`Text`: users enter text on a single line." msgstr "" -#: ../../content/applications/productivity/sign.rst:308 +#: ../../content/applications/productivity/sign.rst:348 msgid ":guilabel:`Multiline Text`: users enter text on multiple lines." msgstr "" -#: ../../content/applications/productivity/sign.rst:309 +#: ../../content/applications/productivity/sign.rst:349 msgid ":guilabel:`Checkbox`: users can tick a box (e.g., to mark their approval or consent)." msgstr "" -#: ../../content/applications/productivity/sign.rst:310 +#: ../../content/applications/productivity/sign.rst:350 msgid ":guilabel:`Selection`: users choose a single option from a variety of options." msgstr "" -#: ../../content/applications/productivity/sign.rst:312 +#: ../../content/applications/productivity/sign.rst:352 msgid "The :guilabel:`Auto-fill Partner Field` setting is used to automatically fill in a field during the signature process. It uses the value of one of the fields on the contact (`res.partner`) model of the person signing the document. To do so, enter the contact model field's technical name." msgstr "" -#: ../../content/applications/productivity/sign.rst:317 +#: ../../content/applications/productivity/sign.rst:357 msgid "To know the technical name of a field, enable developer mode and hover your mouse on the question mark next to the field." msgstr "" -#: ../../content/applications/productivity/sign.rst:321 +#: ../../content/applications/productivity/sign.rst:361 msgid "Auto-completed values are suggestions and can be modified as required by the person signing the document." msgstr "" -#: ../../content/applications/productivity/sign.rst:324 +#: ../../content/applications/productivity/sign.rst:364 msgid "The size of the fields can also be changed by editing the :guilabel:`Default Width` and :guilabel:`Default Height`. Both sizes are defined as a percentage of the full page expressed as a decimal, with 1 equalling the full page's width or height. By default, the width of new fields you create is set to 15% (0.150) of a full page's width, while their height is set to 1.5% (0.015) of a full page's height." msgstr "" -#: ../../content/applications/productivity/sign.rst:330 +#: ../../content/applications/productivity/sign.rst:370 msgid "Next, write a :guilabel:`Tip`. Tips are displayed inside arrows on the left-hand side of the user's screen during the signing process to help them understand what the step entails (e.g., \"Sign here\" or “Fill in your birthdate”). You can also use a :guilabel:`Placeholder` text to be displayed inside the field before it is completed." msgstr "" @@ -3498,6 +3827,1112 @@ msgstr "" msgid "Tip and placeholder example in Odoo Sign" msgstr "" +#: ../../content/applications/productivity/sign/algeria.rst:5 +msgid "Odoo Sign legality in Algeria" +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Algeria." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:11 +msgid "Legal framework for electronic signatures in Algeria" +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:13 +msgid "In Algeria, electronic signatures are regulated under the `Civil Code `_ and the Law 15 04 of Electronic Signature. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:18 +#: ../../content/applications/productivity/sign/angola.rst:17 +#: ../../content/applications/productivity/sign/argentina.rst:19 +#: ../../content/applications/productivity/sign/australia.rst:19 +#: ../../content/applications/productivity/sign/azerbaijan.rst:18 +#: ../../content/applications/productivity/sign/bangladesh.rst:18 +#: ../../content/applications/productivity/sign/brazil.rst:18 +#: ../../content/applications/productivity/sign/canada.rst:18 +#: ../../content/applications/productivity/sign/chile.rst:21 +#: ../../content/applications/productivity/sign/china.rst:17 +#: ../../content/applications/productivity/sign/colombia.rst:17 +#: ../../content/applications/productivity/sign/dominican_republic.rst:18 +#: ../../content/applications/productivity/sign/ecuador.rst:18 +#: ../../content/applications/productivity/sign/egypt.rst:17 +#: ../../content/applications/productivity/sign/ethiopia.rst:17 +#: ../../content/applications/productivity/sign/guatemala.rst:17 +#: ../../content/applications/productivity/sign/hong_kong.rst:17 +#: ../../content/applications/productivity/sign/india.rst:20 +#: ../../content/applications/productivity/sign/indonesia.rst:21 +#: ../../content/applications/productivity/sign/iran.rst:18 +#: ../../content/applications/productivity/sign/iraq.rst:18 +#: ../../content/applications/productivity/sign/israel.rst:17 +#: ../../content/applications/productivity/sign/japan.rst:18 +#: ../../content/applications/productivity/sign/kazakhstan.rst:19 +#: ../../content/applications/productivity/sign/kenya.rst:17 +#: ../../content/applications/productivity/sign/kuwait.rst:18 +#: ../../content/applications/productivity/sign/malaysia.rst:18 +#: ../../content/applications/productivity/sign/mexico.rst:19 +#: ../../content/applications/productivity/sign/morocco.rst:18 +#: ../../content/applications/productivity/sign/new_zealand.rst:18 +#: ../../content/applications/productivity/sign/nigeria.rst:18 +#: ../../content/applications/productivity/sign/norway.rst:19 +#: ../../content/applications/productivity/sign/oman.rst:17 +#: ../../content/applications/productivity/sign/pakistan.rst:17 +#: ../../content/applications/productivity/sign/peru.rst:19 +#: ../../content/applications/productivity/sign/philippines.rst:18 +#: ../../content/applications/productivity/sign/qatar.rst:18 +#: ../../content/applications/productivity/sign/russia.rst:20 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:17 +#: ../../content/applications/productivity/sign/singapore.rst:17 +#: ../../content/applications/productivity/sign/south_africa.rst:18 +#: ../../content/applications/productivity/sign/south_korea.rst:18 +#: ../../content/applications/productivity/sign/switzerland.rst:18 +#: ../../content/applications/productivity/sign/thailand.rst:17 +#: ../../content/applications/productivity/sign/turkey.rst:19 +#: ../../content/applications/productivity/sign/ukraine.rst:17 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:20 +#: ../../content/applications/productivity/sign/united_kingdom.rst:22 +#: ../../content/applications/productivity/sign/uzbekistan.rst:18 +#: ../../content/applications/productivity/sign/vietnam.rst:19 +msgid "**Legal recognition**: electronic signatures are legally equivalent to handwritten signatures if they meet certain criteria." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:20 +#: ../../content/applications/productivity/sign/angola.rst:19 +#: ../../content/applications/productivity/sign/argentina.rst:21 +#: ../../content/applications/productivity/sign/australia.rst:21 +#: ../../content/applications/productivity/sign/azerbaijan.rst:20 +#: ../../content/applications/productivity/sign/bangladesh.rst:20 +#: ../../content/applications/productivity/sign/brazil.rst:20 +#: ../../content/applications/productivity/sign/canada.rst:20 +#: ../../content/applications/productivity/sign/chile.rst:23 +#: ../../content/applications/productivity/sign/china.rst:19 +#: ../../content/applications/productivity/sign/colombia.rst:19 +#: ../../content/applications/productivity/sign/dominican_republic.rst:20 +#: ../../content/applications/productivity/sign/ecuador.rst:20 +#: ../../content/applications/productivity/sign/egypt.rst:19 +#: ../../content/applications/productivity/sign/ethiopia.rst:19 +#: ../../content/applications/productivity/sign/guatemala.rst:19 +#: ../../content/applications/productivity/sign/hong_kong.rst:19 +#: ../../content/applications/productivity/sign/india.rst:22 +#: ../../content/applications/productivity/sign/indonesia.rst:23 +#: ../../content/applications/productivity/sign/iran.rst:20 +#: ../../content/applications/productivity/sign/iraq.rst:20 +#: ../../content/applications/productivity/sign/israel.rst:19 +#: ../../content/applications/productivity/sign/japan.rst:20 +#: ../../content/applications/productivity/sign/kazakhstan.rst:21 +#: ../../content/applications/productivity/sign/kenya.rst:19 +#: ../../content/applications/productivity/sign/kuwait.rst:20 +#: ../../content/applications/productivity/sign/malaysia.rst:20 +#: ../../content/applications/productivity/sign/mexico.rst:21 +#: ../../content/applications/productivity/sign/morocco.rst:20 +#: ../../content/applications/productivity/sign/new_zealand.rst:20 +#: ../../content/applications/productivity/sign/nigeria.rst:20 +#: ../../content/applications/productivity/sign/norway.rst:21 +#: ../../content/applications/productivity/sign/oman.rst:19 +#: ../../content/applications/productivity/sign/pakistan.rst:19 +#: ../../content/applications/productivity/sign/peru.rst:21 +#: ../../content/applications/productivity/sign/philippines.rst:20 +#: ../../content/applications/productivity/sign/qatar.rst:20 +#: ../../content/applications/productivity/sign/russia.rst:22 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:19 +#: ../../content/applications/productivity/sign/singapore.rst:19 +#: ../../content/applications/productivity/sign/south_africa.rst:20 +#: ../../content/applications/productivity/sign/south_korea.rst:20 +#: ../../content/applications/productivity/sign/switzerland.rst:20 +#: ../../content/applications/productivity/sign/thailand.rst:19 +#: ../../content/applications/productivity/sign/turkey.rst:21 +#: ../../content/applications/productivity/sign/ukraine.rst:19 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:22 +#: ../../content/applications/productivity/sign/united_kingdom.rst:24 +#: ../../content/applications/productivity/sign/uzbekistan.rst:20 +#: ../../content/applications/productivity/sign/vietnam.rst:21 +msgid "**Reliability and security**: electronic signatures must be created with a secure method that can reliably identify the signatory and ensure the integrity of the signed document." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:22 +#: ../../content/applications/productivity/sign/ecuador.rst:22 +#: ../../content/applications/productivity/sign/kazakhstan.rst:23 +#: ../../content/applications/productivity/sign/ukraine.rst:21 +msgid "**Qualified electronic signature**: digital signature generated using a digital certificate supplied by a qualified provider." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:26 +msgid "How Odoo Sign complies with Algerian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:28 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Algeria by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:31 +#: ../../content/applications/productivity/sign/angola.rst:33 +#: ../../content/applications/productivity/sign/argentina.rst:32 +#: ../../content/applications/productivity/sign/australia.rst:30 +#: ../../content/applications/productivity/sign/azerbaijan.rst:31 +#: ../../content/applications/productivity/sign/bangladesh.rst:31 +#: ../../content/applications/productivity/sign/brazil.rst:35 +#: ../../content/applications/productivity/sign/canada.rst:33 +#: ../../content/applications/productivity/sign/chile.rst:34 +#: ../../content/applications/productivity/sign/china.rst:30 +#: ../../content/applications/productivity/sign/colombia.rst:33 +#: ../../content/applications/productivity/sign/dominican_republic.rst:31 +#: ../../content/applications/productivity/sign/ecuador.rst:31 +#: ../../content/applications/productivity/sign/egypt.rst:30 +#: ../../content/applications/productivity/sign/ethiopia.rst:30 +#: ../../content/applications/productivity/sign/guatemala.rst:30 +#: ../../content/applications/productivity/sign/hong_kong.rst:30 +#: ../../content/applications/productivity/sign/india.rst:34 +#: ../../content/applications/productivity/sign/indonesia.rst:36 +#: ../../content/applications/productivity/sign/iran.rst:29 +#: ../../content/applications/productivity/sign/iraq.rst:34 +#: ../../content/applications/productivity/sign/israel.rst:30 +#: ../../content/applications/productivity/sign/japan.rst:31 +#: ../../content/applications/productivity/sign/kazakhstan.rst:32 +#: ../../content/applications/productivity/sign/kenya.rst:30 +#: ../../content/applications/productivity/sign/kuwait.rst:29 +#: ../../content/applications/productivity/sign/malaysia.rst:32 +#: ../../content/applications/productivity/sign/mexico.rst:33 +#: ../../content/applications/productivity/sign/morocco.rst:31 +#: ../../content/applications/productivity/sign/new_zealand.rst:31 +#: ../../content/applications/productivity/sign/nigeria.rst:29 +#: ../../content/applications/productivity/sign/norway.rst:32 +#: ../../content/applications/productivity/sign/oman.rst:30 +#: ../../content/applications/productivity/sign/pakistan.rst:31 +#: ../../content/applications/productivity/sign/peru.rst:33 +#: ../../content/applications/productivity/sign/philippines.rst:33 +#: ../../content/applications/productivity/sign/qatar.rst:31 +#: ../../content/applications/productivity/sign/russia.rst:35 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:30 +#: ../../content/applications/productivity/sign/singapore.rst:28 +#: ../../content/applications/productivity/sign/south_africa.rst:31 +#: ../../content/applications/productivity/sign/south_korea.rst:33 +#: ../../content/applications/productivity/sign/switzerland.rst:31 +#: ../../content/applications/productivity/sign/thailand.rst:28 +#: ../../content/applications/productivity/sign/turkey.rst:32 +#: ../../content/applications/productivity/sign/ukraine.rst:30 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:33 +#: ../../content/applications/productivity/sign/united_kingdom.rst:37 +#: ../../content/applications/productivity/sign/uzbekistan.rst:31 +#: ../../content/applications/productivity/sign/vietnam.rst:33 +msgid "**Secure signature creation**: Odoo Sign utilizes advanced cryptographic techniques to ensure the authenticity and integrity of electronic signatures." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:33 +#: ../../content/applications/productivity/sign/angola.rst:35 +#: ../../content/applications/productivity/sign/argentina.rst:34 +#: ../../content/applications/productivity/sign/australia.rst:32 +#: ../../content/applications/productivity/sign/azerbaijan.rst:33 +#: ../../content/applications/productivity/sign/bangladesh.rst:33 +#: ../../content/applications/productivity/sign/brazil.rst:37 +#: ../../content/applications/productivity/sign/canada.rst:35 +#: ../../content/applications/productivity/sign/chile.rst:36 +#: ../../content/applications/productivity/sign/china.rst:32 +#: ../../content/applications/productivity/sign/colombia.rst:35 +#: ../../content/applications/productivity/sign/dominican_republic.rst:33 +#: ../../content/applications/productivity/sign/ecuador.rst:33 +#: ../../content/applications/productivity/sign/egypt.rst:32 +#: ../../content/applications/productivity/sign/ethiopia.rst:32 +#: ../../content/applications/productivity/sign/guatemala.rst:32 +#: ../../content/applications/productivity/sign/hong_kong.rst:32 +#: ../../content/applications/productivity/sign/india.rst:36 +#: ../../content/applications/productivity/sign/indonesia.rst:38 +#: ../../content/applications/productivity/sign/iran.rst:31 +#: ../../content/applications/productivity/sign/iraq.rst:36 +#: ../../content/applications/productivity/sign/israel.rst:32 +#: ../../content/applications/productivity/sign/japan.rst:33 +#: ../../content/applications/productivity/sign/kazakhstan.rst:34 +#: ../../content/applications/productivity/sign/kenya.rst:32 +#: ../../content/applications/productivity/sign/kuwait.rst:31 +#: ../../content/applications/productivity/sign/malaysia.rst:34 +#: ../../content/applications/productivity/sign/mexico.rst:35 +#: ../../content/applications/productivity/sign/morocco.rst:33 +#: ../../content/applications/productivity/sign/new_zealand.rst:33 +#: ../../content/applications/productivity/sign/nigeria.rst:31 +#: ../../content/applications/productivity/sign/norway.rst:34 +#: ../../content/applications/productivity/sign/oman.rst:32 +#: ../../content/applications/productivity/sign/pakistan.rst:33 +#: ../../content/applications/productivity/sign/peru.rst:35 +#: ../../content/applications/productivity/sign/philippines.rst:35 +#: ../../content/applications/productivity/sign/qatar.rst:33 +#: ../../content/applications/productivity/sign/russia.rst:37 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:32 +#: ../../content/applications/productivity/sign/singapore.rst:30 +#: ../../content/applications/productivity/sign/south_africa.rst:33 +#: ../../content/applications/productivity/sign/south_korea.rst:35 +#: ../../content/applications/productivity/sign/switzerland.rst:33 +#: ../../content/applications/productivity/sign/thailand.rst:30 +#: ../../content/applications/productivity/sign/turkey.rst:34 +#: ../../content/applications/productivity/sign/ukraine.rst:32 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:35 +#: ../../content/applications/productivity/sign/united_kingdom.rst:39 +#: ../../content/applications/productivity/sign/uzbekistan.rst:33 +#: ../../content/applications/productivity/sign/vietnam.rst:35 +msgid "**Third-party signature authenticator**: Odoo Online serves as an independent validation mechanism that adds an extra layer of security to the procurement process." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:35 +#: ../../content/applications/productivity/sign/angola.rst:37 +#: ../../content/applications/productivity/sign/argentina.rst:36 +#: ../../content/applications/productivity/sign/australia.rst:34 +#: ../../content/applications/productivity/sign/azerbaijan.rst:35 +#: ../../content/applications/productivity/sign/bangladesh.rst:35 +#: ../../content/applications/productivity/sign/brazil.rst:39 +#: ../../content/applications/productivity/sign/canada.rst:37 +#: ../../content/applications/productivity/sign/chile.rst:38 +#: ../../content/applications/productivity/sign/china.rst:34 +#: ../../content/applications/productivity/sign/colombia.rst:37 +#: ../../content/applications/productivity/sign/dominican_republic.rst:35 +#: ../../content/applications/productivity/sign/ecuador.rst:35 +#: ../../content/applications/productivity/sign/egypt.rst:34 +#: ../../content/applications/productivity/sign/ethiopia.rst:34 +#: ../../content/applications/productivity/sign/guatemala.rst:34 +#: ../../content/applications/productivity/sign/hong_kong.rst:34 +#: ../../content/applications/productivity/sign/india.rst:38 +#: ../../content/applications/productivity/sign/indonesia.rst:40 +#: ../../content/applications/productivity/sign/iran.rst:33 +#: ../../content/applications/productivity/sign/iraq.rst:38 +#: ../../content/applications/productivity/sign/israel.rst:34 +#: ../../content/applications/productivity/sign/japan.rst:35 +#: ../../content/applications/productivity/sign/kazakhstan.rst:36 +#: ../../content/applications/productivity/sign/kenya.rst:34 +#: ../../content/applications/productivity/sign/kuwait.rst:33 +#: ../../content/applications/productivity/sign/malaysia.rst:36 +#: ../../content/applications/productivity/sign/mexico.rst:37 +#: ../../content/applications/productivity/sign/morocco.rst:35 +#: ../../content/applications/productivity/sign/new_zealand.rst:35 +#: ../../content/applications/productivity/sign/nigeria.rst:33 +#: ../../content/applications/productivity/sign/norway.rst:36 +#: ../../content/applications/productivity/sign/oman.rst:34 +#: ../../content/applications/productivity/sign/pakistan.rst:35 +#: ../../content/applications/productivity/sign/peru.rst:37 +#: ../../content/applications/productivity/sign/philippines.rst:37 +#: ../../content/applications/productivity/sign/qatar.rst:35 +#: ../../content/applications/productivity/sign/russia.rst:39 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:34 +#: ../../content/applications/productivity/sign/singapore.rst:32 +#: ../../content/applications/productivity/sign/south_africa.rst:35 +#: ../../content/applications/productivity/sign/south_korea.rst:37 +#: ../../content/applications/productivity/sign/switzerland.rst:35 +#: ../../content/applications/productivity/sign/thailand.rst:32 +#: ../../content/applications/productivity/sign/turkey.rst:36 +#: ../../content/applications/productivity/sign/ukraine.rst:34 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:37 +#: ../../content/applications/productivity/sign/united_kingdom.rst:41 +#: ../../content/applications/productivity/sign/uzbekistan.rst:35 +#: ../../content/applications/productivity/sign/vietnam.rst:37 +msgid "**Audit trails**: detailed audit logs are maintained to provide evidence of the signing process, including timestamps, IP addresses, and identity verification." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:37 +#: ../../content/applications/productivity/sign/angola.rst:39 +#: ../../content/applications/productivity/sign/argentina.rst:38 +#: ../../content/applications/productivity/sign/australia.rst:36 +#: ../../content/applications/productivity/sign/azerbaijan.rst:37 +#: ../../content/applications/productivity/sign/bangladesh.rst:37 +#: ../../content/applications/productivity/sign/brazil.rst:41 +#: ../../content/applications/productivity/sign/canada.rst:39 +#: ../../content/applications/productivity/sign/chile.rst:40 +#: ../../content/applications/productivity/sign/china.rst:36 +#: ../../content/applications/productivity/sign/colombia.rst:39 +#: ../../content/applications/productivity/sign/dominican_republic.rst:37 +#: ../../content/applications/productivity/sign/ecuador.rst:37 +#: ../../content/applications/productivity/sign/egypt.rst:36 +#: ../../content/applications/productivity/sign/ethiopia.rst:36 +#: ../../content/applications/productivity/sign/guatemala.rst:36 +#: ../../content/applications/productivity/sign/hong_kong.rst:36 +#: ../../content/applications/productivity/sign/india.rst:40 +#: ../../content/applications/productivity/sign/indonesia.rst:42 +#: ../../content/applications/productivity/sign/iran.rst:35 +#: ../../content/applications/productivity/sign/iraq.rst:40 +#: ../../content/applications/productivity/sign/israel.rst:36 +#: ../../content/applications/productivity/sign/japan.rst:37 +#: ../../content/applications/productivity/sign/kazakhstan.rst:38 +#: ../../content/applications/productivity/sign/kenya.rst:36 +#: ../../content/applications/productivity/sign/kuwait.rst:35 +#: ../../content/applications/productivity/sign/malaysia.rst:38 +#: ../../content/applications/productivity/sign/mexico.rst:39 +#: ../../content/applications/productivity/sign/morocco.rst:37 +#: ../../content/applications/productivity/sign/new_zealand.rst:37 +#: ../../content/applications/productivity/sign/nigeria.rst:35 +#: ../../content/applications/productivity/sign/norway.rst:38 +#: ../../content/applications/productivity/sign/oman.rst:36 +#: ../../content/applications/productivity/sign/pakistan.rst:37 +#: ../../content/applications/productivity/sign/peru.rst:39 +#: ../../content/applications/productivity/sign/philippines.rst:39 +#: ../../content/applications/productivity/sign/qatar.rst:37 +#: ../../content/applications/productivity/sign/russia.rst:41 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:36 +#: ../../content/applications/productivity/sign/singapore.rst:34 +#: ../../content/applications/productivity/sign/south_africa.rst:37 +#: ../../content/applications/productivity/sign/south_korea.rst:39 +#: ../../content/applications/productivity/sign/switzerland.rst:37 +#: ../../content/applications/productivity/sign/thailand.rst:34 +#: ../../content/applications/productivity/sign/turkey.rst:38 +#: ../../content/applications/productivity/sign/ukraine.rst:36 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:39 +#: ../../content/applications/productivity/sign/united_kingdom.rst:43 +#: ../../content/applications/productivity/sign/uzbekistan.rst:37 +#: ../../content/applications/productivity/sign/vietnam.rst:39 +msgid "**Cryptographic traceability and immutability**: Odoo Sign ensures that any operation is logged securely. An audit log provides full transparency to all parties while preserving private data." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:39 +#: ../../content/applications/productivity/sign/angola.rst:41 +#: ../../content/applications/productivity/sign/argentina.rst:40 +#: ../../content/applications/productivity/sign/australia.rst:38 +#: ../../content/applications/productivity/sign/azerbaijan.rst:39 +#: ../../content/applications/productivity/sign/bangladesh.rst:39 +#: ../../content/applications/productivity/sign/brazil.rst:43 +#: ../../content/applications/productivity/sign/canada.rst:41 +#: ../../content/applications/productivity/sign/chile.rst:42 +#: ../../content/applications/productivity/sign/china.rst:38 +#: ../../content/applications/productivity/sign/colombia.rst:41 +#: ../../content/applications/productivity/sign/dominican_republic.rst:39 +#: ../../content/applications/productivity/sign/ecuador.rst:39 +#: ../../content/applications/productivity/sign/egypt.rst:38 +#: ../../content/applications/productivity/sign/ethiopia.rst:38 +#: ../../content/applications/productivity/sign/guatemala.rst:38 +#: ../../content/applications/productivity/sign/hong_kong.rst:38 +#: ../../content/applications/productivity/sign/india.rst:42 +#: ../../content/applications/productivity/sign/indonesia.rst:44 +#: ../../content/applications/productivity/sign/iran.rst:37 +#: ../../content/applications/productivity/sign/iraq.rst:42 +#: ../../content/applications/productivity/sign/israel.rst:38 +#: ../../content/applications/productivity/sign/japan.rst:39 +#: ../../content/applications/productivity/sign/kazakhstan.rst:40 +#: ../../content/applications/productivity/sign/kenya.rst:38 +#: ../../content/applications/productivity/sign/kuwait.rst:37 +#: ../../content/applications/productivity/sign/malaysia.rst:40 +#: ../../content/applications/productivity/sign/mexico.rst:41 +#: ../../content/applications/productivity/sign/morocco.rst:39 +#: ../../content/applications/productivity/sign/new_zealand.rst:39 +#: ../../content/applications/productivity/sign/nigeria.rst:37 +#: ../../content/applications/productivity/sign/norway.rst:40 +#: ../../content/applications/productivity/sign/oman.rst:38 +#: ../../content/applications/productivity/sign/pakistan.rst:39 +#: ../../content/applications/productivity/sign/peru.rst:41 +#: ../../content/applications/productivity/sign/philippines.rst:41 +#: ../../content/applications/productivity/sign/qatar.rst:39 +#: ../../content/applications/productivity/sign/russia.rst:43 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:38 +#: ../../content/applications/productivity/sign/singapore.rst:36 +#: ../../content/applications/productivity/sign/south_africa.rst:39 +#: ../../content/applications/productivity/sign/south_korea.rst:41 +#: ../../content/applications/productivity/sign/switzerland.rst:39 +#: ../../content/applications/productivity/sign/thailand.rst:36 +#: ../../content/applications/productivity/sign/turkey.rst:40 +#: ../../content/applications/productivity/sign/ukraine.rst:38 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:41 +#: ../../content/applications/productivity/sign/united_kingdom.rst:45 +#: ../../content/applications/productivity/sign/uzbekistan.rst:39 +#: ../../content/applications/productivity/sign/vietnam.rst:41 +msgid "**Multiple authentication means**: authentication by SMS, email, geoIP or handwritten electronic signature." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:43 +#: ../../content/applications/productivity/sign/angola.rst:45 +#: ../../content/applications/productivity/sign/argentina.rst:44 +#: ../../content/applications/productivity/sign/australia.rst:42 +#: ../../content/applications/productivity/sign/azerbaijan.rst:43 +#: ../../content/applications/productivity/sign/bangladesh.rst:43 +#: ../../content/applications/productivity/sign/brazil.rst:47 +#: ../../content/applications/productivity/sign/canada.rst:45 +#: ../../content/applications/productivity/sign/chile.rst:46 +#: ../../content/applications/productivity/sign/china.rst:42 +#: ../../content/applications/productivity/sign/colombia.rst:45 +#: ../../content/applications/productivity/sign/dominican_republic.rst:43 +#: ../../content/applications/productivity/sign/ecuador.rst:43 +#: ../../content/applications/productivity/sign/egypt.rst:42 +#: ../../content/applications/productivity/sign/ethiopia.rst:42 +#: ../../content/applications/productivity/sign/guatemala.rst:42 +#: ../../content/applications/productivity/sign/hong_kong.rst:42 +#: ../../content/applications/productivity/sign/india.rst:46 +#: ../../content/applications/productivity/sign/indonesia.rst:48 +#: ../../content/applications/productivity/sign/iran.rst:41 +#: ../../content/applications/productivity/sign/iraq.rst:46 +#: ../../content/applications/productivity/sign/israel.rst:42 +#: ../../content/applications/productivity/sign/japan.rst:43 +#: ../../content/applications/productivity/sign/kazakhstan.rst:44 +#: ../../content/applications/productivity/sign/kenya.rst:42 +#: ../../content/applications/productivity/sign/kuwait.rst:41 +#: ../../content/applications/productivity/sign/malaysia.rst:44 +#: ../../content/applications/productivity/sign/mexico.rst:45 +#: ../../content/applications/productivity/sign/morocco.rst:43 +#: ../../content/applications/productivity/sign/new_zealand.rst:43 +#: ../../content/applications/productivity/sign/nigeria.rst:41 +#: ../../content/applications/productivity/sign/norway.rst:44 +#: ../../content/applications/productivity/sign/oman.rst:42 +#: ../../content/applications/productivity/sign/pakistan.rst:43 +#: ../../content/applications/productivity/sign/peru.rst:45 +#: ../../content/applications/productivity/sign/philippines.rst:45 +#: ../../content/applications/productivity/sign/qatar.rst:43 +#: ../../content/applications/productivity/sign/russia.rst:47 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:42 +#: ../../content/applications/productivity/sign/singapore.rst:40 +#: ../../content/applications/productivity/sign/south_africa.rst:43 +#: ../../content/applications/productivity/sign/south_korea.rst:45 +#: ../../content/applications/productivity/sign/switzerland.rst:43 +#: ../../content/applications/productivity/sign/thailand.rst:40 +#: ../../content/applications/productivity/sign/turkey.rst:44 +#: ../../content/applications/productivity/sign/ukraine.rst:42 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:45 +#: ../../content/applications/productivity/sign/united_kingdom.rst:49 +#: ../../content/applications/productivity/sign/uzbekistan.rst:43 +#: ../../content/applications/productivity/sign/vietnam.rst:45 +msgid "Types of documents you can sign with Odoo Sign" +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:45 +#: ../../content/applications/productivity/sign/angola.rst:47 +#: ../../content/applications/productivity/sign/argentina.rst:46 +#: ../../content/applications/productivity/sign/australia.rst:44 +#: ../../content/applications/productivity/sign/azerbaijan.rst:45 +#: ../../content/applications/productivity/sign/bangladesh.rst:45 +#: ../../content/applications/productivity/sign/brazil.rst:49 +#: ../../content/applications/productivity/sign/canada.rst:47 +#: ../../content/applications/productivity/sign/chile.rst:48 +#: ../../content/applications/productivity/sign/china.rst:44 +#: ../../content/applications/productivity/sign/colombia.rst:47 +#: ../../content/applications/productivity/sign/dominican_republic.rst:45 +#: ../../content/applications/productivity/sign/ecuador.rst:45 +#: ../../content/applications/productivity/sign/egypt.rst:44 +#: ../../content/applications/productivity/sign/ethiopia.rst:44 +#: ../../content/applications/productivity/sign/guatemala.rst:44 +#: ../../content/applications/productivity/sign/hong_kong.rst:44 +#: ../../content/applications/productivity/sign/india.rst:48 +#: ../../content/applications/productivity/sign/indonesia.rst:50 +#: ../../content/applications/productivity/sign/iran.rst:43 +#: ../../content/applications/productivity/sign/iraq.rst:48 +#: ../../content/applications/productivity/sign/israel.rst:44 +#: ../../content/applications/productivity/sign/japan.rst:45 +#: ../../content/applications/productivity/sign/kazakhstan.rst:46 +#: ../../content/applications/productivity/sign/kenya.rst:44 +#: ../../content/applications/productivity/sign/kuwait.rst:43 +#: ../../content/applications/productivity/sign/malaysia.rst:46 +#: ../../content/applications/productivity/sign/mexico.rst:47 +#: ../../content/applications/productivity/sign/morocco.rst:45 +#: ../../content/applications/productivity/sign/new_zealand.rst:45 +#: ../../content/applications/productivity/sign/nigeria.rst:43 +#: ../../content/applications/productivity/sign/norway.rst:46 +#: ../../content/applications/productivity/sign/oman.rst:44 +#: ../../content/applications/productivity/sign/pakistan.rst:45 +#: ../../content/applications/productivity/sign/peru.rst:47 +#: ../../content/applications/productivity/sign/philippines.rst:47 +#: ../../content/applications/productivity/sign/qatar.rst:45 +#: ../../content/applications/productivity/sign/russia.rst:49 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:44 +#: ../../content/applications/productivity/sign/singapore.rst:42 +#: ../../content/applications/productivity/sign/south_africa.rst:45 +#: ../../content/applications/productivity/sign/south_korea.rst:47 +#: ../../content/applications/productivity/sign/switzerland.rst:45 +#: ../../content/applications/productivity/sign/thailand.rst:42 +#: ../../content/applications/productivity/sign/turkey.rst:46 +#: ../../content/applications/productivity/sign/ukraine.rst:44 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:47 +#: ../../content/applications/productivity/sign/united_kingdom.rst:51 +#: ../../content/applications/productivity/sign/uzbekistan.rst:45 +#: ../../content/applications/productivity/sign/vietnam.rst:47 +msgid "Odoo Sign is versatile and can be used for a wide range of documents, including but not limited to:" +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:47 +#: ../../content/applications/productivity/sign/angola.rst:49 +#: ../../content/applications/productivity/sign/argentina.rst:48 +#: ../../content/applications/productivity/sign/australia.rst:46 +#: ../../content/applications/productivity/sign/azerbaijan.rst:47 +#: ../../content/applications/productivity/sign/bangladesh.rst:47 +#: ../../content/applications/productivity/sign/brazil.rst:51 +#: ../../content/applications/productivity/sign/canada.rst:49 +#: ../../content/applications/productivity/sign/chile.rst:50 +#: ../../content/applications/productivity/sign/china.rst:46 +#: ../../content/applications/productivity/sign/colombia.rst:49 +#: ../../content/applications/productivity/sign/dominican_republic.rst:47 +#: ../../content/applications/productivity/sign/ecuador.rst:47 +#: ../../content/applications/productivity/sign/egypt.rst:46 +#: ../../content/applications/productivity/sign/ethiopia.rst:46 +#: ../../content/applications/productivity/sign/guatemala.rst:46 +#: ../../content/applications/productivity/sign/hong_kong.rst:46 +#: ../../content/applications/productivity/sign/india.rst:50 +#: ../../content/applications/productivity/sign/indonesia.rst:52 +#: ../../content/applications/productivity/sign/iran.rst:45 +#: ../../content/applications/productivity/sign/iraq.rst:50 +#: ../../content/applications/productivity/sign/israel.rst:46 +#: ../../content/applications/productivity/sign/japan.rst:47 +#: ../../content/applications/productivity/sign/kazakhstan.rst:48 +#: ../../content/applications/productivity/sign/kenya.rst:46 +#: ../../content/applications/productivity/sign/kuwait.rst:45 +#: ../../content/applications/productivity/sign/malaysia.rst:48 +#: ../../content/applications/productivity/sign/mexico.rst:49 +#: ../../content/applications/productivity/sign/morocco.rst:47 +#: ../../content/applications/productivity/sign/new_zealand.rst:47 +#: ../../content/applications/productivity/sign/nigeria.rst:45 +#: ../../content/applications/productivity/sign/norway.rst:48 +#: ../../content/applications/productivity/sign/oman.rst:46 +#: ../../content/applications/productivity/sign/pakistan.rst:47 +#: ../../content/applications/productivity/sign/peru.rst:49 +#: ../../content/applications/productivity/sign/philippines.rst:49 +#: ../../content/applications/productivity/sign/qatar.rst:47 +#: ../../content/applications/productivity/sign/russia.rst:51 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:46 +#: ../../content/applications/productivity/sign/singapore.rst:44 +#: ../../content/applications/productivity/sign/south_africa.rst:47 +#: ../../content/applications/productivity/sign/south_korea.rst:49 +#: ../../content/applications/productivity/sign/switzerland.rst:47 +#: ../../content/applications/productivity/sign/thailand.rst:44 +#: ../../content/applications/productivity/sign/turkey.rst:48 +#: ../../content/applications/productivity/sign/ukraine.rst:46 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:49 +#: ../../content/applications/productivity/sign/united_kingdom.rst:53 +#: ../../content/applications/productivity/sign/uzbekistan.rst:47 +#: ../../content/applications/productivity/sign/vietnam.rst:49 +msgid "**Contracts and agreements**: business contracts, employment agreements, and service contracts." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:48 +#: ../../content/applications/productivity/sign/angola.rst:50 +#: ../../content/applications/productivity/sign/argentina.rst:49 +#: ../../content/applications/productivity/sign/australia.rst:47 +#: ../../content/applications/productivity/sign/azerbaijan.rst:48 +#: ../../content/applications/productivity/sign/bangladesh.rst:48 +#: ../../content/applications/productivity/sign/brazil.rst:52 +#: ../../content/applications/productivity/sign/canada.rst:50 +#: ../../content/applications/productivity/sign/chile.rst:51 +#: ../../content/applications/productivity/sign/china.rst:47 +#: ../../content/applications/productivity/sign/colombia.rst:50 +#: ../../content/applications/productivity/sign/dominican_republic.rst:48 +#: ../../content/applications/productivity/sign/ecuador.rst:48 +#: ../../content/applications/productivity/sign/egypt.rst:47 +#: ../../content/applications/productivity/sign/ethiopia.rst:47 +#: ../../content/applications/productivity/sign/guatemala.rst:47 +#: ../../content/applications/productivity/sign/hong_kong.rst:47 +#: ../../content/applications/productivity/sign/india.rst:51 +#: ../../content/applications/productivity/sign/indonesia.rst:53 +#: ../../content/applications/productivity/sign/iran.rst:46 +#: ../../content/applications/productivity/sign/iraq.rst:51 +#: ../../content/applications/productivity/sign/israel.rst:47 +#: ../../content/applications/productivity/sign/japan.rst:48 +#: ../../content/applications/productivity/sign/kazakhstan.rst:49 +#: ../../content/applications/productivity/sign/kenya.rst:47 +#: ../../content/applications/productivity/sign/kuwait.rst:46 +#: ../../content/applications/productivity/sign/malaysia.rst:49 +#: ../../content/applications/productivity/sign/mexico.rst:50 +#: ../../content/applications/productivity/sign/morocco.rst:48 +#: ../../content/applications/productivity/sign/new_zealand.rst:48 +#: ../../content/applications/productivity/sign/nigeria.rst:46 +#: ../../content/applications/productivity/sign/norway.rst:49 +#: ../../content/applications/productivity/sign/oman.rst:47 +#: ../../content/applications/productivity/sign/pakistan.rst:48 +#: ../../content/applications/productivity/sign/peru.rst:50 +#: ../../content/applications/productivity/sign/philippines.rst:50 +#: ../../content/applications/productivity/sign/qatar.rst:48 +#: ../../content/applications/productivity/sign/russia.rst:52 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:47 +#: ../../content/applications/productivity/sign/singapore.rst:45 +#: ../../content/applications/productivity/sign/south_africa.rst:48 +#: ../../content/applications/productivity/sign/south_korea.rst:50 +#: ../../content/applications/productivity/sign/switzerland.rst:48 +#: ../../content/applications/productivity/sign/thailand.rst:45 +#: ../../content/applications/productivity/sign/turkey.rst:49 +#: ../../content/applications/productivity/sign/ukraine.rst:47 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:50 +#: ../../content/applications/productivity/sign/united_kingdom.rst:54 +#: ../../content/applications/productivity/sign/uzbekistan.rst:48 +#: ../../content/applications/productivity/sign/vietnam.rst:50 +msgid "**Financial documents**: loan agreements, investment documents, and financial reports." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:49 +#: ../../content/applications/productivity/sign/angola.rst:51 +#: ../../content/applications/productivity/sign/argentina.rst:50 +#: ../../content/applications/productivity/sign/australia.rst:48 +#: ../../content/applications/productivity/sign/azerbaijan.rst:49 +#: ../../content/applications/productivity/sign/bangladesh.rst:49 +#: ../../content/applications/productivity/sign/brazil.rst:53 +#: ../../content/applications/productivity/sign/canada.rst:51 +#: ../../content/applications/productivity/sign/chile.rst:52 +#: ../../content/applications/productivity/sign/china.rst:48 +#: ../../content/applications/productivity/sign/colombia.rst:51 +#: ../../content/applications/productivity/sign/dominican_republic.rst:49 +#: ../../content/applications/productivity/sign/ecuador.rst:49 +#: ../../content/applications/productivity/sign/egypt.rst:48 +#: ../../content/applications/productivity/sign/ethiopia.rst:48 +#: ../../content/applications/productivity/sign/guatemala.rst:48 +#: ../../content/applications/productivity/sign/hong_kong.rst:48 +#: ../../content/applications/productivity/sign/india.rst:52 +#: ../../content/applications/productivity/sign/indonesia.rst:54 +#: ../../content/applications/productivity/sign/iran.rst:47 +#: ../../content/applications/productivity/sign/iraq.rst:52 +#: ../../content/applications/productivity/sign/israel.rst:48 +#: ../../content/applications/productivity/sign/japan.rst:49 +#: ../../content/applications/productivity/sign/kazakhstan.rst:50 +#: ../../content/applications/productivity/sign/kenya.rst:48 +#: ../../content/applications/productivity/sign/kuwait.rst:47 +#: ../../content/applications/productivity/sign/malaysia.rst:50 +#: ../../content/applications/productivity/sign/mexico.rst:51 +#: ../../content/applications/productivity/sign/morocco.rst:49 +#: ../../content/applications/productivity/sign/new_zealand.rst:49 +#: ../../content/applications/productivity/sign/nigeria.rst:47 +#: ../../content/applications/productivity/sign/norway.rst:50 +#: ../../content/applications/productivity/sign/oman.rst:48 +#: ../../content/applications/productivity/sign/pakistan.rst:49 +#: ../../content/applications/productivity/sign/peru.rst:51 +#: ../../content/applications/productivity/sign/philippines.rst:51 +#: ../../content/applications/productivity/sign/qatar.rst:49 +#: ../../content/applications/productivity/sign/russia.rst:53 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:48 +#: ../../content/applications/productivity/sign/singapore.rst:46 +#: ../../content/applications/productivity/sign/south_africa.rst:49 +#: ../../content/applications/productivity/sign/south_korea.rst:51 +#: ../../content/applications/productivity/sign/switzerland.rst:49 +#: ../../content/applications/productivity/sign/thailand.rst:46 +#: ../../content/applications/productivity/sign/turkey.rst:50 +#: ../../content/applications/productivity/sign/ukraine.rst:48 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:51 +#: ../../content/applications/productivity/sign/united_kingdom.rst:55 +#: ../../content/applications/productivity/sign/uzbekistan.rst:49 +#: ../../content/applications/productivity/sign/vietnam.rst:51 +msgid "**HR documents**: employee onboarding forms, non-disclosure agreements (NDAs), and performance reviews." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:51 +#: ../../content/applications/productivity/sign/angola.rst:53 +#: ../../content/applications/productivity/sign/argentina.rst:52 +#: ../../content/applications/productivity/sign/australia.rst:50 +#: ../../content/applications/productivity/sign/azerbaijan.rst:51 +#: ../../content/applications/productivity/sign/bangladesh.rst:51 +#: ../../content/applications/productivity/sign/brazil.rst:55 +#: ../../content/applications/productivity/sign/canada.rst:53 +#: ../../content/applications/productivity/sign/chile.rst:54 +#: ../../content/applications/productivity/sign/china.rst:50 +#: ../../content/applications/productivity/sign/colombia.rst:53 +#: ../../content/applications/productivity/sign/dominican_republic.rst:51 +#: ../../content/applications/productivity/sign/ecuador.rst:51 +#: ../../content/applications/productivity/sign/egypt.rst:50 +#: ../../content/applications/productivity/sign/ethiopia.rst:50 +#: ../../content/applications/productivity/sign/guatemala.rst:50 +#: ../../content/applications/productivity/sign/hong_kong.rst:50 +#: ../../content/applications/productivity/sign/india.rst:54 +#: ../../content/applications/productivity/sign/indonesia.rst:56 +#: ../../content/applications/productivity/sign/iran.rst:49 +#: ../../content/applications/productivity/sign/iraq.rst:54 +#: ../../content/applications/productivity/sign/israel.rst:50 +#: ../../content/applications/productivity/sign/japan.rst:51 +#: ../../content/applications/productivity/sign/kazakhstan.rst:52 +#: ../../content/applications/productivity/sign/kenya.rst:50 +#: ../../content/applications/productivity/sign/kuwait.rst:49 +#: ../../content/applications/productivity/sign/malaysia.rst:52 +#: ../../content/applications/productivity/sign/mexico.rst:53 +#: ../../content/applications/productivity/sign/morocco.rst:51 +#: ../../content/applications/productivity/sign/new_zealand.rst:51 +#: ../../content/applications/productivity/sign/nigeria.rst:49 +#: ../../content/applications/productivity/sign/norway.rst:52 +#: ../../content/applications/productivity/sign/oman.rst:50 +#: ../../content/applications/productivity/sign/pakistan.rst:51 +#: ../../content/applications/productivity/sign/peru.rst:53 +#: ../../content/applications/productivity/sign/philippines.rst:53 +#: ../../content/applications/productivity/sign/qatar.rst:51 +#: ../../content/applications/productivity/sign/russia.rst:55 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:50 +#: ../../content/applications/productivity/sign/singapore.rst:48 +#: ../../content/applications/productivity/sign/south_africa.rst:51 +#: ../../content/applications/productivity/sign/south_korea.rst:53 +#: ../../content/applications/productivity/sign/switzerland.rst:51 +#: ../../content/applications/productivity/sign/thailand.rst:48 +#: ../../content/applications/productivity/sign/turkey.rst:52 +#: ../../content/applications/productivity/sign/ukraine.rst:50 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:53 +#: ../../content/applications/productivity/sign/united_kingdom.rst:57 +#: ../../content/applications/productivity/sign/uzbekistan.rst:51 +#: ../../content/applications/productivity/sign/vietnam.rst:53 +msgid "**Commercial transactions**: purchase orders, sales agreements, and supplier contracts." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:54 +#: ../../content/applications/productivity/sign/angola.rst:56 +#: ../../content/applications/productivity/sign/argentina.rst:55 +#: ../../content/applications/productivity/sign/australia.rst:53 +#: ../../content/applications/productivity/sign/azerbaijan.rst:54 +#: ../../content/applications/productivity/sign/bangladesh.rst:54 +#: ../../content/applications/productivity/sign/brazil.rst:58 +#: ../../content/applications/productivity/sign/canada.rst:56 +#: ../../content/applications/productivity/sign/chile.rst:57 +#: ../../content/applications/productivity/sign/china.rst:53 +#: ../../content/applications/productivity/sign/colombia.rst:56 +#: ../../content/applications/productivity/sign/dominican_republic.rst:54 +#: ../../content/applications/productivity/sign/ecuador.rst:54 +#: ../../content/applications/productivity/sign/egypt.rst:53 +#: ../../content/applications/productivity/sign/ethiopia.rst:53 +#: ../../content/applications/productivity/sign/guatemala.rst:53 +#: ../../content/applications/productivity/sign/hong_kong.rst:53 +#: ../../content/applications/productivity/sign/india.rst:57 +#: ../../content/applications/productivity/sign/indonesia.rst:59 +#: ../../content/applications/productivity/sign/iran.rst:52 +#: ../../content/applications/productivity/sign/iraq.rst:57 +#: ../../content/applications/productivity/sign/israel.rst:53 +#: ../../content/applications/productivity/sign/japan.rst:54 +#: ../../content/applications/productivity/sign/kazakhstan.rst:55 +#: ../../content/applications/productivity/sign/kenya.rst:53 +#: ../../content/applications/productivity/sign/kuwait.rst:52 +#: ../../content/applications/productivity/sign/malaysia.rst:55 +#: ../../content/applications/productivity/sign/mexico.rst:56 +#: ../../content/applications/productivity/sign/morocco.rst:54 +#: ../../content/applications/productivity/sign/new_zealand.rst:54 +#: ../../content/applications/productivity/sign/nigeria.rst:52 +#: ../../content/applications/productivity/sign/norway.rst:55 +#: ../../content/applications/productivity/sign/oman.rst:53 +#: ../../content/applications/productivity/sign/pakistan.rst:54 +#: ../../content/applications/productivity/sign/peru.rst:56 +#: ../../content/applications/productivity/sign/philippines.rst:56 +#: ../../content/applications/productivity/sign/qatar.rst:54 +#: ../../content/applications/productivity/sign/russia.rst:58 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:53 +#: ../../content/applications/productivity/sign/singapore.rst:51 +#: ../../content/applications/productivity/sign/south_africa.rst:54 +#: ../../content/applications/productivity/sign/south_korea.rst:56 +#: ../../content/applications/productivity/sign/switzerland.rst:54 +#: ../../content/applications/productivity/sign/thailand.rst:51 +#: ../../content/applications/productivity/sign/turkey.rst:55 +#: ../../content/applications/productivity/sign/ukraine.rst:53 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:56 +#: ../../content/applications/productivity/sign/united_kingdom.rst:60 +#: ../../content/applications/productivity/sign/uzbekistan.rst:54 +#: ../../content/applications/productivity/sign/vietnam.rst:56 +msgid "Potential exceptions" +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:56 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Algeria:" +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:59 +#: ../../content/applications/productivity/sign/angola.rst:61 +#: ../../content/applications/productivity/sign/argentina.rst:60 +#: ../../content/applications/productivity/sign/australia.rst:58 +#: ../../content/applications/productivity/sign/azerbaijan.rst:59 +#: ../../content/applications/productivity/sign/bangladesh.rst:59 +#: ../../content/applications/productivity/sign/brazil.rst:63 +#: ../../content/applications/productivity/sign/canada.rst:61 +#: ../../content/applications/productivity/sign/chile.rst:62 +#: ../../content/applications/productivity/sign/china.rst:58 +#: ../../content/applications/productivity/sign/colombia.rst:61 +#: ../../content/applications/productivity/sign/dominican_republic.rst:59 +#: ../../content/applications/productivity/sign/ecuador.rst:59 +#: ../../content/applications/productivity/sign/egypt.rst:58 +#: ../../content/applications/productivity/sign/ethiopia.rst:58 +#: ../../content/applications/productivity/sign/guatemala.rst:58 +#: ../../content/applications/productivity/sign/hong_kong.rst:58 +#: ../../content/applications/productivity/sign/india.rst:62 +#: ../../content/applications/productivity/sign/indonesia.rst:64 +#: ../../content/applications/productivity/sign/iran.rst:57 +#: ../../content/applications/productivity/sign/iraq.rst:62 +#: ../../content/applications/productivity/sign/israel.rst:58 +#: ../../content/applications/productivity/sign/japan.rst:59 +#: ../../content/applications/productivity/sign/kazakhstan.rst:60 +#: ../../content/applications/productivity/sign/kenya.rst:58 +#: ../../content/applications/productivity/sign/kuwait.rst:57 +#: ../../content/applications/productivity/sign/malaysia.rst:60 +#: ../../content/applications/productivity/sign/mexico.rst:61 +#: ../../content/applications/productivity/sign/morocco.rst:59 +#: ../../content/applications/productivity/sign/new_zealand.rst:59 +#: ../../content/applications/productivity/sign/nigeria.rst:57 +#: ../../content/applications/productivity/sign/norway.rst:60 +#: ../../content/applications/productivity/sign/oman.rst:58 +#: ../../content/applications/productivity/sign/pakistan.rst:59 +#: ../../content/applications/productivity/sign/peru.rst:61 +#: ../../content/applications/productivity/sign/philippines.rst:61 +#: ../../content/applications/productivity/sign/qatar.rst:59 +#: ../../content/applications/productivity/sign/russia.rst:63 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:58 +#: ../../content/applications/productivity/sign/singapore.rst:56 +#: ../../content/applications/productivity/sign/south_africa.rst:59 +#: ../../content/applications/productivity/sign/south_korea.rst:61 +#: ../../content/applications/productivity/sign/switzerland.rst:59 +#: ../../content/applications/productivity/sign/thailand.rst:56 +#: ../../content/applications/productivity/sign/turkey.rst:60 +#: ../../content/applications/productivity/sign/ukraine.rst:58 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:61 +#: ../../content/applications/productivity/sign/united_kingdom.rst:65 +#: ../../content/applications/productivity/sign/uzbekistan.rst:59 +#: ../../content/applications/productivity/sign/vietnam.rst:61 +msgid "**Wills and trusts**: documents related to inheritance, wills, and trusts often require handwritten signatures." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:61 +#: ../../content/applications/productivity/sign/angola.rst:63 +#: ../../content/applications/productivity/sign/argentina.rst:62 +#: ../../content/applications/productivity/sign/australia.rst:60 +#: ../../content/applications/productivity/sign/azerbaijan.rst:61 +#: ../../content/applications/productivity/sign/bangladesh.rst:61 +#: ../../content/applications/productivity/sign/brazil.rst:65 +#: ../../content/applications/productivity/sign/canada.rst:63 +#: ../../content/applications/productivity/sign/chile.rst:64 +#: ../../content/applications/productivity/sign/china.rst:60 +#: ../../content/applications/productivity/sign/colombia.rst:63 +#: ../../content/applications/productivity/sign/dominican_republic.rst:61 +#: ../../content/applications/productivity/sign/ecuador.rst:61 +#: ../../content/applications/productivity/sign/egypt.rst:60 +#: ../../content/applications/productivity/sign/ethiopia.rst:60 +#: ../../content/applications/productivity/sign/guatemala.rst:60 +#: ../../content/applications/productivity/sign/hong_kong.rst:60 +#: ../../content/applications/productivity/sign/india.rst:64 +#: ../../content/applications/productivity/sign/indonesia.rst:66 +#: ../../content/applications/productivity/sign/iran.rst:59 +#: ../../content/applications/productivity/sign/iraq.rst:64 +#: ../../content/applications/productivity/sign/israel.rst:60 +#: ../../content/applications/productivity/sign/japan.rst:61 +#: ../../content/applications/productivity/sign/kazakhstan.rst:62 +#: ../../content/applications/productivity/sign/kenya.rst:60 +#: ../../content/applications/productivity/sign/kuwait.rst:59 +#: ../../content/applications/productivity/sign/malaysia.rst:62 +#: ../../content/applications/productivity/sign/mexico.rst:63 +#: ../../content/applications/productivity/sign/morocco.rst:61 +#: ../../content/applications/productivity/sign/new_zealand.rst:61 +#: ../../content/applications/productivity/sign/nigeria.rst:59 +#: ../../content/applications/productivity/sign/norway.rst:62 +#: ../../content/applications/productivity/sign/oman.rst:60 +#: ../../content/applications/productivity/sign/pakistan.rst:61 +#: ../../content/applications/productivity/sign/peru.rst:63 +#: ../../content/applications/productivity/sign/philippines.rst:63 +#: ../../content/applications/productivity/sign/qatar.rst:61 +#: ../../content/applications/productivity/sign/russia.rst:65 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:60 +#: ../../content/applications/productivity/sign/singapore.rst:58 +#: ../../content/applications/productivity/sign/south_africa.rst:61 +#: ../../content/applications/productivity/sign/south_korea.rst:63 +#: ../../content/applications/productivity/sign/switzerland.rst:61 +#: ../../content/applications/productivity/sign/thailand.rst:58 +#: ../../content/applications/productivity/sign/turkey.rst:62 +#: ../../content/applications/productivity/sign/ukraine.rst:60 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:63 +#: ../../content/applications/productivity/sign/united_kingdom.rst:67 +#: ../../content/applications/productivity/sign/uzbekistan.rst:61 +#: ../../content/applications/productivity/sign/vietnam.rst:63 +msgid "**Real estate transactions**: some property transactions may still require notarized handwritten signatures." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:63 +#: ../../content/applications/productivity/sign/angola.rst:65 +#: ../../content/applications/productivity/sign/argentina.rst:64 +#: ../../content/applications/productivity/sign/australia.rst:62 +#: ../../content/applications/productivity/sign/azerbaijan.rst:63 +#: ../../content/applications/productivity/sign/bangladesh.rst:63 +#: ../../content/applications/productivity/sign/brazil.rst:67 +#: ../../content/applications/productivity/sign/canada.rst:65 +#: ../../content/applications/productivity/sign/chile.rst:66 +#: ../../content/applications/productivity/sign/china.rst:62 +#: ../../content/applications/productivity/sign/colombia.rst:65 +#: ../../content/applications/productivity/sign/dominican_republic.rst:63 +#: ../../content/applications/productivity/sign/ecuador.rst:63 +#: ../../content/applications/productivity/sign/egypt.rst:62 +#: ../../content/applications/productivity/sign/ethiopia.rst:62 +#: ../../content/applications/productivity/sign/guatemala.rst:62 +#: ../../content/applications/productivity/sign/hong_kong.rst:62 +#: ../../content/applications/productivity/sign/india.rst:66 +#: ../../content/applications/productivity/sign/indonesia.rst:68 +#: ../../content/applications/productivity/sign/iran.rst:61 +#: ../../content/applications/productivity/sign/iraq.rst:66 +#: ../../content/applications/productivity/sign/israel.rst:62 +#: ../../content/applications/productivity/sign/japan.rst:63 +#: ../../content/applications/productivity/sign/kazakhstan.rst:64 +#: ../../content/applications/productivity/sign/kenya.rst:62 +#: ../../content/applications/productivity/sign/kuwait.rst:61 +#: ../../content/applications/productivity/sign/malaysia.rst:64 +#: ../../content/applications/productivity/sign/mexico.rst:65 +#: ../../content/applications/productivity/sign/morocco.rst:63 +#: ../../content/applications/productivity/sign/new_zealand.rst:63 +#: ../../content/applications/productivity/sign/nigeria.rst:61 +#: ../../content/applications/productivity/sign/norway.rst:64 +#: ../../content/applications/productivity/sign/oman.rst:62 +#: ../../content/applications/productivity/sign/pakistan.rst:63 +#: ../../content/applications/productivity/sign/peru.rst:65 +#: ../../content/applications/productivity/sign/philippines.rst:65 +#: ../../content/applications/productivity/sign/qatar.rst:63 +#: ../../content/applications/productivity/sign/russia.rst:67 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:62 +#: ../../content/applications/productivity/sign/singapore.rst:60 +#: ../../content/applications/productivity/sign/south_africa.rst:63 +#: ../../content/applications/productivity/sign/south_korea.rst:65 +#: ../../content/applications/productivity/sign/switzerland.rst:63 +#: ../../content/applications/productivity/sign/thailand.rst:60 +#: ../../content/applications/productivity/sign/turkey.rst:64 +#: ../../content/applications/productivity/sign/ukraine.rst:62 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:65 +#: ../../content/applications/productivity/sign/united_kingdom.rst:69 +#: ../../content/applications/productivity/sign/uzbekistan.rst:63 +#: ../../content/applications/productivity/sign/vietnam.rst:65 +msgid "**Government forms**: specific government forms and applications may mandate physical signatures." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:65 +#: ../../content/applications/productivity/sign/angola.rst:67 +#: ../../content/applications/productivity/sign/argentina.rst:66 +#: ../../content/applications/productivity/sign/australia.rst:64 +#: ../../content/applications/productivity/sign/azerbaijan.rst:65 +#: ../../content/applications/productivity/sign/bangladesh.rst:65 +#: ../../content/applications/productivity/sign/brazil.rst:69 +#: ../../content/applications/productivity/sign/canada.rst:67 +#: ../../content/applications/productivity/sign/chile.rst:68 +#: ../../content/applications/productivity/sign/china.rst:64 +#: ../../content/applications/productivity/sign/colombia.rst:67 +#: ../../content/applications/productivity/sign/dominican_republic.rst:65 +#: ../../content/applications/productivity/sign/ecuador.rst:65 +#: ../../content/applications/productivity/sign/egypt.rst:64 +#: ../../content/applications/productivity/sign/ethiopia.rst:64 +#: ../../content/applications/productivity/sign/guatemala.rst:64 +#: ../../content/applications/productivity/sign/hong_kong.rst:64 +#: ../../content/applications/productivity/sign/india.rst:68 +#: ../../content/applications/productivity/sign/indonesia.rst:70 +#: ../../content/applications/productivity/sign/iran.rst:63 +#: ../../content/applications/productivity/sign/iraq.rst:68 +#: ../../content/applications/productivity/sign/israel.rst:64 +#: ../../content/applications/productivity/sign/japan.rst:65 +#: ../../content/applications/productivity/sign/kazakhstan.rst:66 +#: ../../content/applications/productivity/sign/kenya.rst:64 +#: ../../content/applications/productivity/sign/kuwait.rst:63 +#: ../../content/applications/productivity/sign/malaysia.rst:66 +#: ../../content/applications/productivity/sign/mexico.rst:67 +#: ../../content/applications/productivity/sign/morocco.rst:65 +#: ../../content/applications/productivity/sign/new_zealand.rst:65 +#: ../../content/applications/productivity/sign/nigeria.rst:63 +#: ../../content/applications/productivity/sign/norway.rst:66 +#: ../../content/applications/productivity/sign/oman.rst:64 +#: ../../content/applications/productivity/sign/pakistan.rst:65 +#: ../../content/applications/productivity/sign/peru.rst:67 +#: ../../content/applications/productivity/sign/philippines.rst:67 +#: ../../content/applications/productivity/sign/qatar.rst:65 +#: ../../content/applications/productivity/sign/russia.rst:69 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:64 +#: ../../content/applications/productivity/sign/singapore.rst:62 +#: ../../content/applications/productivity/sign/south_africa.rst:65 +#: ../../content/applications/productivity/sign/south_korea.rst:67 +#: ../../content/applications/productivity/sign/switzerland.rst:65 +#: ../../content/applications/productivity/sign/thailand.rst:62 +#: ../../content/applications/productivity/sign/turkey.rst:66 +#: ../../content/applications/productivity/sign/ukraine.rst:64 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:67 +#: ../../content/applications/productivity/sign/united_kingdom.rst:71 +#: ../../content/applications/productivity/sign/uzbekistan.rst:65 +#: ../../content/applications/productivity/sign/vietnam.rst:67 +msgid "Disclaimer" +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:67 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Algeria, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/algeria.rst:73 +#: ../../content/applications/productivity/sign/angola.rst:75 +#: ../../content/applications/productivity/sign/argentina.rst:74 +#: ../../content/applications/productivity/sign/azerbaijan.rst:73 +#: ../../content/applications/productivity/sign/bangladesh.rst:73 +#: ../../content/applications/productivity/sign/chile.rst:76 +#: ../../content/applications/productivity/sign/colombia.rst:75 +#: ../../content/applications/productivity/sign/dominican_republic.rst:73 +#: ../../content/applications/productivity/sign/ecuador.rst:73 +#: ../../content/applications/productivity/sign/ethiopia.rst:72 +#: ../../content/applications/productivity/sign/guatemala.rst:72 +#: ../../content/applications/productivity/sign/hong_kong.rst:72 +#: ../../content/applications/productivity/sign/iran.rst:71 +#: ../../content/applications/productivity/sign/iraq.rst:76 +#: ../../content/applications/productivity/sign/israel.rst:72 +#: ../../content/applications/productivity/sign/kazakhstan.rst:74 +#: ../../content/applications/productivity/sign/kenya.rst:72 +#: ../../content/applications/productivity/sign/kuwait.rst:71 +#: ../../content/applications/productivity/sign/malaysia.rst:74 +#: ../../content/applications/productivity/sign/morocco.rst:73 +#: ../../content/applications/productivity/sign/new_zealand.rst:73 +#: ../../content/applications/productivity/sign/nigeria.rst:71 +#: ../../content/applications/productivity/sign/norway.rst:74 +#: ../../content/applications/productivity/sign/oman.rst:72 +#: ../../content/applications/productivity/sign/pakistan.rst:73 +#: ../../content/applications/productivity/sign/peru.rst:75 +#: ../../content/applications/productivity/sign/philippines.rst:75 +#: ../../content/applications/productivity/sign/qatar.rst:73 +#: ../../content/applications/productivity/sign/saudi_arabia.rst:72 +#: ../../content/applications/productivity/sign/singapore.rst:70 +#: ../../content/applications/productivity/sign/south_africa.rst:73 +#: ../../content/applications/productivity/sign/switzerland.rst:73 +#: ../../content/applications/productivity/sign/thailand.rst:70 +#: ../../content/applications/productivity/sign/turkey.rst:74 +#: ../../content/applications/productivity/sign/ukraine.rst:72 +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:75 +#: ../../content/applications/productivity/sign/uzbekistan.rst:73 +#: ../../content/applications/productivity/sign/vietnam.rst:75 +msgid "*Last updated: June 21, 2024*" +msgstr "" + +#: ../../content/applications/productivity/sign/angola.rst:5 +msgid "Odoo Sign legality in Angola" +msgstr "" + +#: ../../content/applications/productivity/sign/angola.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Angola." +msgstr "" + +#: ../../content/applications/productivity/sign/angola.rst:11 +msgid "Legal framework for electronic signatures in Angola" +msgstr "" + +#: ../../content/applications/productivity/sign/angola.rst:13 +msgid "In Angola, electronic signatures are regulated under the Presidential Decree 312/2018 and Executive Order 74/2019. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/angola.rst:21 +msgid "**Certified electronic signature**: digital signature generated using a digital certificate supplied by a qualified provider. In some cases, only the certified electronic signature has legal and juridical validity in Angola. In those cases, simple electronic signatures like the Odoo Signature only work as a proof of the agreement to celebrate the corresponding transaction, which will be submitted to the authority's criteria." +msgstr "" + +#: ../../content/applications/productivity/sign/angola.rst:28 +msgid "How Odoo Sign complies with Angolan regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/angola.rst:30 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Angola by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/angola.rst:58 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Angola:" +msgstr "" + +#: ../../content/applications/productivity/sign/angola.rst:69 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Angola, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/argentina.rst:5 +msgid "Odoo Sign legality in Argentina" +msgstr "" + +#: ../../content/applications/productivity/sign/argentina.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Argentina." +msgstr "" + +#: ../../content/applications/productivity/sign/argentina.rst:11 +msgid "Legal framework for electronic signatures in Argentina" +msgstr "" + +#: ../../content/applications/productivity/sign/argentina.rst:13 +msgid "In Argentina, electronic signatures are regulated under the `Digital Signature Law `_, and the `Civil and Commercial Code `_. The law governs transactions performed through electronic means and the use of electronic signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/argentina.rst:23 +msgid "**Qualified digital signatures**: the law recognizes electronic signatures supported by digital certificates issued by accredited Certification Service Providers." +msgstr "" + +#: ../../content/applications/productivity/sign/argentina.rst:27 +msgid "How Odoo Sign complies with Argentinian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/argentina.rst:29 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Argentina by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/argentina.rst:57 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Argentina:" +msgstr "" + +#: ../../content/applications/productivity/sign/argentina.rst:68 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Argentina, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + #: ../../content/applications/productivity/sign/australia.rst:5 msgid "Odoo Sign legality in Australia" msgstr "" @@ -3514,32 +4949,6 @@ msgstr "" msgid "In Australia, electronic signatures are regulated under the `Electronic Transactions Act (ETA) `_, the `Electronic Transactions Regulations (ETR) `_ and local regulations in each state. The law governs transactions performed through electronic means and the use of electronic signatures. The key points of the law include:" msgstr "" -#: ../../content/applications/productivity/sign/australia.rst:19 -#: ../../content/applications/productivity/sign/brazil.rst:18 -#: ../../content/applications/productivity/sign/canada.rst:18 -#: ../../content/applications/productivity/sign/china.rst:17 -#: ../../content/applications/productivity/sign/india.rst:20 -#: ../../content/applications/productivity/sign/japan.rst:18 -#: ../../content/applications/productivity/sign/mexico.rst:19 -#: ../../content/applications/productivity/sign/russia.rst:20 -#: ../../content/applications/productivity/sign/south_korea.rst:18 -#: ../../content/applications/productivity/sign/united_kingdom.rst:22 -msgid "**Legal recognition**: electronic signatures are legally equivalent to handwritten signatures if they meet certain criteria." -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:21 -#: ../../content/applications/productivity/sign/brazil.rst:20 -#: ../../content/applications/productivity/sign/canada.rst:20 -#: ../../content/applications/productivity/sign/china.rst:19 -#: ../../content/applications/productivity/sign/india.rst:22 -#: ../../content/applications/productivity/sign/japan.rst:20 -#: ../../content/applications/productivity/sign/mexico.rst:21 -#: ../../content/applications/productivity/sign/russia.rst:22 -#: ../../content/applications/productivity/sign/south_korea.rst:20 -#: ../../content/applications/productivity/sign/united_kingdom.rst:24 -msgid "**Reliability and security**: electronic signatures must be created with a secure method that can reliably identify the signatory and ensure the integrity of the signed document." -msgstr "" - #: ../../content/applications/productivity/sign/australia.rst:25 msgid "How Odoo Sign complies with Australian regulations" msgstr "" @@ -3548,218 +4957,10 @@ msgstr "" msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Australia by incorporating the following features:" msgstr "" -#: ../../content/applications/productivity/sign/australia.rst:30 -#: ../../content/applications/productivity/sign/brazil.rst:35 -#: ../../content/applications/productivity/sign/canada.rst:33 -#: ../../content/applications/productivity/sign/china.rst:29 -#: ../../content/applications/productivity/sign/india.rst:34 -#: ../../content/applications/productivity/sign/japan.rst:31 -#: ../../content/applications/productivity/sign/mexico.rst:33 -#: ../../content/applications/productivity/sign/russia.rst:35 -#: ../../content/applications/productivity/sign/south_korea.rst:33 -#: ../../content/applications/productivity/sign/united_kingdom.rst:37 -msgid "**Secure signature creation**: Odoo Sign utilizes advanced cryptographic techniques to ensure the authenticity and integrity of electronic signatures." -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:32 -#: ../../content/applications/productivity/sign/brazil.rst:37 -#: ../../content/applications/productivity/sign/canada.rst:35 -#: ../../content/applications/productivity/sign/china.rst:31 -#: ../../content/applications/productivity/sign/india.rst:36 -#: ../../content/applications/productivity/sign/japan.rst:33 -#: ../../content/applications/productivity/sign/mexico.rst:35 -#: ../../content/applications/productivity/sign/russia.rst:37 -#: ../../content/applications/productivity/sign/south_korea.rst:35 -#: ../../content/applications/productivity/sign/united_kingdom.rst:39 -msgid "**Third-party signature authenticator**: Odoo Online serves as an independent validation mechanism that adds an extra layer of security to the procurement process." -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:34 -#: ../../content/applications/productivity/sign/brazil.rst:39 -#: ../../content/applications/productivity/sign/canada.rst:37 -#: ../../content/applications/productivity/sign/china.rst:33 -#: ../../content/applications/productivity/sign/india.rst:38 -#: ../../content/applications/productivity/sign/japan.rst:35 -#: ../../content/applications/productivity/sign/mexico.rst:37 -#: ../../content/applications/productivity/sign/russia.rst:39 -#: ../../content/applications/productivity/sign/south_korea.rst:37 -#: ../../content/applications/productivity/sign/united_kingdom.rst:41 -msgid "**Audit trails**: detailed audit logs are maintained to provide evidence of the signing process, including timestamps, IP addresses, and identity verification." -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:36 -#: ../../content/applications/productivity/sign/brazil.rst:41 -#: ../../content/applications/productivity/sign/canada.rst:39 -#: ../../content/applications/productivity/sign/china.rst:35 -#: ../../content/applications/productivity/sign/india.rst:40 -#: ../../content/applications/productivity/sign/japan.rst:37 -#: ../../content/applications/productivity/sign/mexico.rst:39 -#: ../../content/applications/productivity/sign/russia.rst:41 -#: ../../content/applications/productivity/sign/south_korea.rst:39 -#: ../../content/applications/productivity/sign/united_kingdom.rst:43 -msgid "**Cryptographic traceability and immutability**: Odoo Sign ensures that any operation is logged securely. An audit log provides full transparency to all parties while preserving private data." -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:38 -#: ../../content/applications/productivity/sign/brazil.rst:43 -#: ../../content/applications/productivity/sign/canada.rst:41 -#: ../../content/applications/productivity/sign/china.rst:37 -#: ../../content/applications/productivity/sign/india.rst:42 -#: ../../content/applications/productivity/sign/japan.rst:39 -#: ../../content/applications/productivity/sign/mexico.rst:41 -#: ../../content/applications/productivity/sign/russia.rst:43 -#: ../../content/applications/productivity/sign/south_korea.rst:41 -#: ../../content/applications/productivity/sign/united_kingdom.rst:45 -msgid "**Multiple authentication means**: authentication by SMS, email, geoIP or handwritten electronic signature." -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:42 -#: ../../content/applications/productivity/sign/brazil.rst:47 -#: ../../content/applications/productivity/sign/canada.rst:45 -#: ../../content/applications/productivity/sign/china.rst:40 -#: ../../content/applications/productivity/sign/india.rst:46 -#: ../../content/applications/productivity/sign/japan.rst:43 -#: ../../content/applications/productivity/sign/mexico.rst:45 -#: ../../content/applications/productivity/sign/russia.rst:47 -#: ../../content/applications/productivity/sign/south_korea.rst:45 -#: ../../content/applications/productivity/sign/united_kingdom.rst:49 -msgid "Types of documents you can sign with Odoo Sign" -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:44 -#: ../../content/applications/productivity/sign/brazil.rst:49 -#: ../../content/applications/productivity/sign/canada.rst:47 -#: ../../content/applications/productivity/sign/china.rst:42 -#: ../../content/applications/productivity/sign/india.rst:48 -#: ../../content/applications/productivity/sign/japan.rst:45 -#: ../../content/applications/productivity/sign/mexico.rst:47 -#: ../../content/applications/productivity/sign/russia.rst:49 -#: ../../content/applications/productivity/sign/south_korea.rst:47 -#: ../../content/applications/productivity/sign/united_kingdom.rst:51 -msgid "Odoo Sign is versatile and can be used for a wide range of documents, including but not limited to:" -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:46 -#: ../../content/applications/productivity/sign/brazil.rst:51 -#: ../../content/applications/productivity/sign/canada.rst:49 -#: ../../content/applications/productivity/sign/china.rst:44 -#: ../../content/applications/productivity/sign/india.rst:50 -#: ../../content/applications/productivity/sign/japan.rst:47 -#: ../../content/applications/productivity/sign/mexico.rst:49 -#: ../../content/applications/productivity/sign/russia.rst:51 -#: ../../content/applications/productivity/sign/south_korea.rst:49 -#: ../../content/applications/productivity/sign/united_kingdom.rst:53 -msgid "**Contracts and agreements**: business contracts, employment agreements, and service contracts." -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:47 -#: ../../content/applications/productivity/sign/brazil.rst:52 -#: ../../content/applications/productivity/sign/canada.rst:50 -#: ../../content/applications/productivity/sign/china.rst:45 -#: ../../content/applications/productivity/sign/india.rst:51 -#: ../../content/applications/productivity/sign/japan.rst:48 -#: ../../content/applications/productivity/sign/mexico.rst:50 -#: ../../content/applications/productivity/sign/russia.rst:52 -#: ../../content/applications/productivity/sign/south_korea.rst:50 -#: ../../content/applications/productivity/sign/united_kingdom.rst:54 -msgid "**Financial documents**: loan agreements, investment documents, and financial reports." -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:48 -#: ../../content/applications/productivity/sign/brazil.rst:53 -#: ../../content/applications/productivity/sign/canada.rst:51 -#: ../../content/applications/productivity/sign/china.rst:46 -#: ../../content/applications/productivity/sign/india.rst:52 -#: ../../content/applications/productivity/sign/japan.rst:49 -#: ../../content/applications/productivity/sign/mexico.rst:51 -#: ../../content/applications/productivity/sign/russia.rst:53 -#: ../../content/applications/productivity/sign/south_korea.rst:51 -#: ../../content/applications/productivity/sign/united_kingdom.rst:55 -msgid "**HR documents**: employee onboarding forms, non-disclosure agreements (NDAs), and performance reviews." -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:50 -#: ../../content/applications/productivity/sign/brazil.rst:55 -#: ../../content/applications/productivity/sign/canada.rst:53 -#: ../../content/applications/productivity/sign/china.rst:47 -#: ../../content/applications/productivity/sign/india.rst:54 -#: ../../content/applications/productivity/sign/japan.rst:51 -#: ../../content/applications/productivity/sign/mexico.rst:53 -#: ../../content/applications/productivity/sign/russia.rst:55 -#: ../../content/applications/productivity/sign/south_korea.rst:53 -#: ../../content/applications/productivity/sign/united_kingdom.rst:57 -msgid "**Commercial transactions**: purchase orders, sales agreements, and supplier contracts." -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:53 -#: ../../content/applications/productivity/sign/brazil.rst:58 -#: ../../content/applications/productivity/sign/canada.rst:56 -#: ../../content/applications/productivity/sign/china.rst:50 -#: ../../content/applications/productivity/sign/india.rst:57 -#: ../../content/applications/productivity/sign/japan.rst:54 -#: ../../content/applications/productivity/sign/mexico.rst:56 -#: ../../content/applications/productivity/sign/russia.rst:58 -#: ../../content/applications/productivity/sign/south_korea.rst:56 -#: ../../content/applications/productivity/sign/united_kingdom.rst:60 -msgid "Potential exceptions" -msgstr "" - #: ../../content/applications/productivity/sign/australia.rst:55 msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Australia:" msgstr "" -#: ../../content/applications/productivity/sign/australia.rst:58 -#: ../../content/applications/productivity/sign/brazil.rst:63 -#: ../../content/applications/productivity/sign/canada.rst:61 -#: ../../content/applications/productivity/sign/china.rst:55 -#: ../../content/applications/productivity/sign/india.rst:62 -#: ../../content/applications/productivity/sign/japan.rst:59 -#: ../../content/applications/productivity/sign/mexico.rst:61 -#: ../../content/applications/productivity/sign/russia.rst:63 -#: ../../content/applications/productivity/sign/south_korea.rst:61 -#: ../../content/applications/productivity/sign/united_kingdom.rst:65 -msgid "**Wills and trusts**: documents related to inheritance, wills, and trusts often require handwritten signatures." -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:60 -#: ../../content/applications/productivity/sign/brazil.rst:65 -#: ../../content/applications/productivity/sign/canada.rst:63 -#: ../../content/applications/productivity/sign/china.rst:56 -#: ../../content/applications/productivity/sign/india.rst:64 -#: ../../content/applications/productivity/sign/japan.rst:61 -#: ../../content/applications/productivity/sign/mexico.rst:63 -#: ../../content/applications/productivity/sign/russia.rst:65 -#: ../../content/applications/productivity/sign/south_korea.rst:63 -#: ../../content/applications/productivity/sign/united_kingdom.rst:67 -msgid "**Real estate transactions**: some property transactions may still require notarized handwritten signatures." -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:62 -#: ../../content/applications/productivity/sign/brazil.rst:67 -#: ../../content/applications/productivity/sign/canada.rst:65 -#: ../../content/applications/productivity/sign/china.rst:57 -#: ../../content/applications/productivity/sign/india.rst:66 -#: ../../content/applications/productivity/sign/japan.rst:63 -#: ../../content/applications/productivity/sign/mexico.rst:65 -#: ../../content/applications/productivity/sign/russia.rst:67 -#: ../../content/applications/productivity/sign/south_korea.rst:65 -#: ../../content/applications/productivity/sign/united_kingdom.rst:69 -msgid "**Government forms**: specific government forms and applications may mandate physical signatures." -msgstr "" - -#: ../../content/applications/productivity/sign/australia.rst:64 -#: ../../content/applications/productivity/sign/brazil.rst:69 -#: ../../content/applications/productivity/sign/canada.rst:67 -#: ../../content/applications/productivity/sign/china.rst:59 -#: ../../content/applications/productivity/sign/india.rst:68 -#: ../../content/applications/productivity/sign/japan.rst:65 -#: ../../content/applications/productivity/sign/mexico.rst:67 -#: ../../content/applications/productivity/sign/russia.rst:69 -#: ../../content/applications/productivity/sign/south_korea.rst:67 -#: ../../content/applications/productivity/sign/united_kingdom.rst:71 -msgid "Disclaimer" -msgstr "" - #: ../../content/applications/productivity/sign/australia.rst:66 msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Australia, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." msgstr "" @@ -3767,8 +4968,10 @@ msgstr "" #: ../../content/applications/productivity/sign/australia.rst:72 #: ../../content/applications/productivity/sign/brazil.rst:77 #: ../../content/applications/productivity/sign/canada.rst:75 -#: ../../content/applications/productivity/sign/china.rst:66 +#: ../../content/applications/productivity/sign/china.rst:72 +#: ../../content/applications/productivity/sign/egypt.rst:72 #: ../../content/applications/productivity/sign/india.rst:76 +#: ../../content/applications/productivity/sign/indonesia.rst:78 #: ../../content/applications/productivity/sign/japan.rst:73 #: ../../content/applications/productivity/sign/mexico.rst:75 #: ../../content/applications/productivity/sign/russia.rst:77 @@ -3777,6 +4980,78 @@ msgstr "" msgid "*Last updated: June 19, 2024*" msgstr "" +#: ../../content/applications/productivity/sign/azerbaijan.rst:5 +msgid "Odoo Sign legality in Azerbaijan" +msgstr "" + +#: ../../content/applications/productivity/sign/azerbaijan.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Azerbaijan." +msgstr "" + +#: ../../content/applications/productivity/sign/azerbaijan.rst:11 +msgid "Legal framework for electronic signatures in Azerbaijan" +msgstr "" + +#: ../../content/applications/productivity/sign/azerbaijan.rst:13 +msgid "In Azerbaijan, electronic signatures are regulated under the `Law on Electronic Digital Signature `_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/azerbaijan.rst:22 +msgid "**Digital signature certificate**: digital signature generated using a digital certificate supplied by a qualified provider." +msgstr "" + +#: ../../content/applications/productivity/sign/azerbaijan.rst:26 +msgid "How Odoo Sign complies with Azerbaijani regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/azerbaijan.rst:28 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Azerbaijan by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/azerbaijan.rst:56 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Azerbaijan:" +msgstr "" + +#: ../../content/applications/productivity/sign/azerbaijan.rst:67 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Azerbaijan, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/bangladesh.rst:5 +msgid "Odoo Sign legality in Bangladesh" +msgstr "" + +#: ../../content/applications/productivity/sign/bangladesh.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Bangladesh." +msgstr "" + +#: ../../content/applications/productivity/sign/bangladesh.rst:11 +msgid "Legal framework for electronic signatures in Bangladesh" +msgstr "" + +#: ../../content/applications/productivity/sign/bangladesh.rst:13 +msgid "In Bangladesh, electronic signatures are regulated under the `Information and Communication Technology Act `_. The law recognizes the use of electronic documents and electronic signatures for the execution of contracts and other transactions. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/bangladesh.rst:22 +msgid "**Special cases**: some cases require a traditional signature. These requirements can vary on a case-by-case basis, particularly when dealing with public sector entities." +msgstr "" + +#: ../../content/applications/productivity/sign/bangladesh.rst:26 +msgid "How Odoo Sign complies with Bangladeshi regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/bangladesh.rst:28 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Bangladesh by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/bangladesh.rst:56 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Bangladesh:" +msgstr "" + +#: ../../content/applications/productivity/sign/bangladesh.rst:67 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Bangladesh, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + #: ../../content/applications/productivity/sign/brazil.rst:5 msgid "Odoo Sign legality in Brazil" msgstr "" @@ -3849,6 +5124,43 @@ msgstr "" msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Canada, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." msgstr "" +#: ../../content/applications/productivity/sign/chile.rst:5 +msgid "Odoo Sign legality in Chile" +msgstr "" + +#: ../../content/applications/productivity/sign/chile.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Chile." +msgstr "" + +#: ../../content/applications/productivity/sign/chile.rst:11 +msgid "Legal framework for electronic signatures in Chile" +msgstr "" + +#: ../../content/applications/productivity/sign/chile.rst:13 +msgid "In Chile, electronic signatures are regulated under the `Law 19.799 on electronic documents, electronic signature and certification services of such signature `_, `Decree 181/2002 `_ and `Law No. 21,180, on Digital Transformation of the State `_. The law establishes the legal basis for acknowledging electronic records, contracts, and signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/chile.rst:25 +#: ../../content/applications/productivity/sign/hong_kong.rst:21 +msgid "**Certified electronic signatures**: special electronic signature that incorporates certificates issued by a recognized certification authority." +msgstr "" + +#: ../../content/applications/productivity/sign/chile.rst:29 +msgid "How Odoo Sign complies with Chilean regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/chile.rst:31 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Chile by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/chile.rst:59 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Chile:" +msgstr "" + +#: ../../content/applications/productivity/sign/chile.rst:70 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Chile, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + #: ../../content/applications/productivity/sign/china.rst:5 msgid "Odoo Sign legality in China" msgstr "" @@ -3877,14 +5189,261 @@ msgstr "" msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of China by incorporating the following features:" msgstr "" -#: ../../content/applications/productivity/sign/china.rst:52 +#: ../../content/applications/productivity/sign/china.rst:55 msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in China:" msgstr "" -#: ../../content/applications/productivity/sign/china.rst:61 +#: ../../content/applications/productivity/sign/china.rst:66 msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of China, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." msgstr "" +#: ../../content/applications/productivity/sign/colombia.rst:5 +msgid "Odoo Sign legality in Colombia" +msgstr "" + +#: ../../content/applications/productivity/sign/colombia.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Colombia." +msgstr "" + +#: ../../content/applications/productivity/sign/colombia.rst:11 +msgid "Legal framework for electronic signatures in Colombia" +msgstr "" + +#: ../../content/applications/productivity/sign/colombia.rst:13 +msgid "In Colombia, electronic signatures are regulated under the `Law 529 of 1999 `_. The law establishes the legal basis for acknowledging electronic records, contracts, and signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/colombia.rst:21 +msgid "**Certified electronic signatures**: special electronic signature that incorporates certificates issued by a recognized certification authority. In some cases, only the certified electronic signature has legal and juridical validity in Colombia. In those cases, simple electronic signatures like the Odoo Signature only work as a proof of the agreement to celebrate the corresponding transaction, which will be submitted to the authority's criteria." +msgstr "" + +#: ../../content/applications/productivity/sign/colombia.rst:28 +msgid "How Odoo Sign complies with Colombian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/colombia.rst:30 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Colombia by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/colombia.rst:58 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Colombia:" +msgstr "" + +#: ../../content/applications/productivity/sign/colombia.rst:69 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Colombia, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/dominican_republic.rst:5 +msgid "Odoo Sign legality in the Dominican Republic" +msgstr "" + +#: ../../content/applications/productivity/sign/dominican_republic.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in the Dominican Republic." +msgstr "" + +#: ../../content/applications/productivity/sign/dominican_republic.rst:11 +msgid "Legal framework for electronic signatures in the Dominican Republic" +msgstr "" + +#: ../../content/applications/productivity/sign/dominican_republic.rst:13 +msgid "In the Dominican Republic, electronic signatures are regulated under the `Law 126-02 on Electronic Commerce, Documents and Digital Signatures `_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/dominican_republic.rst:22 +#: ../../content/applications/productivity/sign/kenya.rst:21 +#: ../../content/applications/productivity/sign/morocco.rst:22 +#: ../../content/applications/productivity/sign/oman.rst:21 +msgid "**Certified electronic signature**: digital signature generated using a digital certificate supplied by a qualified provider." +msgstr "" + +#: ../../content/applications/productivity/sign/dominican_republic.rst:26 +msgid "How Odoo Sign complies with Dominican regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/dominican_republic.rst:28 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of the Dominican Republic by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/dominican_republic.rst:56 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in the Dominican Republic:" +msgstr "" + +#: ../../content/applications/productivity/sign/dominican_republic.rst:67 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of the Dominican Republic, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/ecuador.rst:5 +msgid "Odoo Sign legality in Ecuador" +msgstr "" + +#: ../../content/applications/productivity/sign/ecuador.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Ecuador." +msgstr "" + +#: ../../content/applications/productivity/sign/ecuador.rst:11 +msgid "Legal framework for electronic signatures in Ecuador" +msgstr "" + +#: ../../content/applications/productivity/sign/ecuador.rst:13 +msgid "In Ecuador, electronic signatures are regulated under the `Law on Electronic Commerce, Electronic Signatures and Data Messages `_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/ecuador.rst:26 +msgid "How Odoo Sign complies with Ecuadoran regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/ecuador.rst:28 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Ecuador by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/ecuador.rst:56 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Ecuador:" +msgstr "" + +#: ../../content/applications/productivity/sign/ecuador.rst:67 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Ecuador, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/egypt.rst:5 +msgid "Odoo Sign legality in Egypt" +msgstr "" + +#: ../../content/applications/productivity/sign/egypt.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Egypt." +msgstr "" + +#: ../../content/applications/productivity/sign/egypt.rst:11 +msgid "Legal framework for electronic signatures in Egypt" +msgstr "" + +#: ../../content/applications/productivity/sign/egypt.rst:13 +msgid "In Egypt, electronic signatures are regulated under the `E-Signature Law `_. The law governs transactions performed through electronic means and the use of digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/egypt.rst:21 +msgid "**Qualified electronic signatures**: law recognizes special digital signatures certified by a qualified authority. In some cases, this type of signature is mandatory." +msgstr "" + +#: ../../content/applications/productivity/sign/egypt.rst:25 +msgid "How Odoo Sign complies with Egyptian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/egypt.rst:27 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Egypt by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/egypt.rst:55 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Egypt:" +msgstr "" + +#: ../../content/applications/productivity/sign/egypt.rst:66 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Egypt, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/ethiopia.rst:5 +msgid "Odoo Sign legality in Ethiopia" +msgstr "" + +#: ../../content/applications/productivity/sign/ethiopia.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Ethiopia." +msgstr "" + +#: ../../content/applications/productivity/sign/ethiopia.rst:11 +msgid "Legal framework for electronic signatures in Ethiopia" +msgstr "" + +#: ../../content/applications/productivity/sign/ethiopia.rst:13 +msgid "In Ethiopia, electronic signatures are regulated under the `Electronic Signature Proclamation No. 1072/2018 `_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/ethiopia.rst:21 +msgid "**Certificate electronic signature**: digital signature generated using a digital certificate supplied by a qualified provider." +msgstr "" + +#: ../../content/applications/productivity/sign/ethiopia.rst:25 +msgid "How Odoo Sign complies with Ethiopian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/ethiopia.rst:27 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Ethiopia by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/ethiopia.rst:55 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Ethiopia:" +msgstr "" + +#: ../../content/applications/productivity/sign/ethiopia.rst:66 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Ethiopia, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/guatemala.rst:5 +msgid "Odoo Sign legality in Guatemala" +msgstr "" + +#: ../../content/applications/productivity/sign/guatemala.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Guatemala." +msgstr "" + +#: ../../content/applications/productivity/sign/guatemala.rst:11 +msgid "Legal framework for electronic signatures in Guatemala" +msgstr "" + +#: ../../content/applications/productivity/sign/guatemala.rst:13 +msgid "In Guatemala, electronic signatures are regulated under the `Electronic Communications and Signatures Law `_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/guatemala.rst:21 +msgid "**Certification service providers**: digital signature generated using a digital certificate supplied by a qualified provider." +msgstr "" + +#: ../../content/applications/productivity/sign/guatemala.rst:25 +msgid "How Odoo Sign complies with Guatemalan regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/guatemala.rst:27 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Guatemala by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/guatemala.rst:55 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Guatemala:" +msgstr "" + +#: ../../content/applications/productivity/sign/guatemala.rst:66 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Guatemala, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/hong_kong.rst:5 +msgid "Odoo Sign legality in Hong Kong" +msgstr "" + +#: ../../content/applications/productivity/sign/hong_kong.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Hong Kong." +msgstr "" + +#: ../../content/applications/productivity/sign/hong_kong.rst:11 +msgid "Legal framework for electronic signatures in Hong Kong" +msgstr "" + +#: ../../content/applications/productivity/sign/hong_kong.rst:13 +msgid "In Hong Kong, electronic signatures are regulated under the `Electronic Transactions Ordinance `_. The law establishes the legal basis for acknowledging electronic records, contracts, and signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/hong_kong.rst:25 +msgid "How Odoo Sign complies with Hong Kong regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/hong_kong.rst:27 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Hong Kong by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/hong_kong.rst:55 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Hong Kong:" +msgstr "" + +#: ../../content/applications/productivity/sign/hong_kong.rst:66 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Hong Kong, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + #: ../../content/applications/productivity/sign/india.rst:5 msgid "Odoo Sign legality in India" msgstr "" @@ -3921,6 +5480,146 @@ msgstr "" msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of India, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." msgstr "" +#: ../../content/applications/productivity/sign/indonesia.rst:5 +msgid "Odoo Sign legality in Indonesia" +msgstr "" + +#: ../../content/applications/productivity/sign/indonesia.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Indonesia." +msgstr "" + +#: ../../content/applications/productivity/sign/indonesia.rst:11 +msgid "Legal framework for electronic signatures in Indonesia" +msgstr "" + +#: ../../content/applications/productivity/sign/indonesia.rst:13 +msgid "In Indonesia, electronic signatures are regulated under the `Law of the Republic of Indonesia No. 11 of 2008 on Electronic Information and Transactions `_, Government Regulation No. 71 of 2019 on Organization of Electronic system and Transactions, as well as the Minister of Communications and Informatics (MoCI) Regulation No. 11 of 2018 on Administration of Electronic Certification (\"MoCI Regulation 11 of 2018\"). The law governs transactions performed through electronic means and the use of electronic signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/indonesia.rst:25 +msgid "**Certified e-signatures**: the law recognizes digital signature certificates that serve as proof of identity of an individual for a certain purpose that can be used in special cases to provide additional security. These certificates are issued by Certification Authorities and are required by law for the signature of specific acts." +msgstr "" + +#: ../../content/applications/productivity/sign/indonesia.rst:31 +msgid "How Odoo Sign complies with Indonesian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/indonesia.rst:33 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Indonesia by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/indonesia.rst:61 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Indonesia:" +msgstr "" + +#: ../../content/applications/productivity/sign/indonesia.rst:72 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Indonesia, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/iran.rst:5 +msgid "Odoo Sign legality in Iran" +msgstr "" + +#: ../../content/applications/productivity/sign/iran.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Iran." +msgstr "" + +#: ../../content/applications/productivity/sign/iran.rst:11 +msgid "Legal framework for electronic signatures in Iran" +msgstr "" + +#: ../../content/applications/productivity/sign/iran.rst:13 +msgid "In Iran, electronic signatures are regulated under the `Iran Civil Code `_ and the `Electronic Commerce Act `_. The law governs the use of electronic records and signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/iran.rst:24 +msgid "How Odoo Sign complies with Iranian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/iran.rst:26 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Iran by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/iran.rst:54 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Iran:" +msgstr "" + +#: ../../content/applications/productivity/sign/iran.rst:65 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Iran, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/iraq.rst:5 +msgid "Odoo Sign legality in Iraq" +msgstr "" + +#: ../../content/applications/productivity/sign/iraq.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Iraq." +msgstr "" + +#: ../../content/applications/productivity/sign/iraq.rst:11 +msgid "Legal framework for electronic signatures in Iraq" +msgstr "" + +#: ../../content/applications/productivity/sign/iraq.rst:13 +msgid "In Iraq, electronic signatures are regulated under the `Electronic Signature and Electronic transactions Law No. 78 Of 2012 `_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/iraq.rst:22 +msgid "**Certified electronic signatures**: Special electronic signature that incorporates certificates issued by a recognized certification authority. In some cases, only the certified electronic signature has legal and juridical validity in Iraq. In those cases, simple electronic signatures like the Odoo Signature only work as a proof of the agreement of wills to celebrate the corresponding transaction, which will be submitted to the authority's criteria." +msgstr "" + +#: ../../content/applications/productivity/sign/iraq.rst:29 +msgid "How Odoo Sign complies with Iraqi regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/iraq.rst:31 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Iraq by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/iraq.rst:59 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Iraq:" +msgstr "" + +#: ../../content/applications/productivity/sign/iraq.rst:70 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Iraq, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/israel.rst:5 +msgid "Odoo Sign legality in Israel" +msgstr "" + +#: ../../content/applications/productivity/sign/israel.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Israel." +msgstr "" + +#: ../../content/applications/productivity/sign/israel.rst:11 +msgid "Legal framework for electronic signatures in Israel" +msgstr "" + +#: ../../content/applications/productivity/sign/israel.rst:13 +msgid "In Israel, electronic signatures are regulated under the Electronic Signature Law, and various electronic signature regulations. The law governs transactions performed through electronic means and the use of electronic signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/israel.rst:21 +msgid "**Certified electronic signature**: the law recognizes electronic signatures supported by digital certificates issued by Certified Providers." +msgstr "" + +#: ../../content/applications/productivity/sign/israel.rst:25 +msgid "How Odoo Sign complies with Israeli regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/israel.rst:27 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Israel by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/israel.rst:55 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Israel:" +msgstr "" + +#: ../../content/applications/productivity/sign/israel.rst:66 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Israel, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + #: ../../content/applications/productivity/sign/japan.rst:5 msgid "Odoo Sign legality in Japan" msgstr "" @@ -3957,6 +5656,138 @@ msgstr "" msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Japan, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." msgstr "" +#: ../../content/applications/productivity/sign/kazakhstan.rst:5 +msgid "Odoo Sign legality in Kazakhstan" +msgstr "" + +#: ../../content/applications/productivity/sign/kazakhstan.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Kazakhstan." +msgstr "" + +#: ../../content/applications/productivity/sign/kazakhstan.rst:11 +msgid "Legal framework for electronic signatures in Kazakhstan" +msgstr "" + +#: ../../content/applications/productivity/sign/kazakhstan.rst:13 +msgid "In Kazakhstan, electronic signatures are regulated under the `Civil Code `_ and the `Law On Electronic Document and Electronic Digital Signature `_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/kazakhstan.rst:27 +msgid "How Odoo Sign complies with Kazakhstani regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/kazakhstan.rst:29 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Kazakhstan by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/kazakhstan.rst:57 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Kazakhstan:" +msgstr "" + +#: ../../content/applications/productivity/sign/kazakhstan.rst:68 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Kazakhstan, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/kenya.rst:5 +msgid "Odoo Sign legality in Kenya" +msgstr "" + +#: ../../content/applications/productivity/sign/kenya.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Kenya." +msgstr "" + +#: ../../content/applications/productivity/sign/kenya.rst:11 +msgid "Legal framework for electronic signatures in Kenya" +msgstr "" + +#: ../../content/applications/productivity/sign/kenya.rst:13 +msgid "In Kenya, electronic signatures are regulated under the `Information and Communications Act `_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/kenya.rst:25 +msgid "How Odoo Sign complies with Kenyan regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/kenya.rst:27 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Kenya by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/kenya.rst:55 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Kenya:" +msgstr "" + +#: ../../content/applications/productivity/sign/kenya.rst:66 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Kenya, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/kuwait.rst:5 +msgid "Odoo Sign legality in Kuwait" +msgstr "" + +#: ../../content/applications/productivity/sign/kuwait.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Kuwait." +msgstr "" + +#: ../../content/applications/productivity/sign/kuwait.rst:11 +msgid "Legal framework for electronic signatures in Kuwait" +msgstr "" + +#: ../../content/applications/productivity/sign/kuwait.rst:13 +msgid "In Kuwait, electronic signatures are regulated under the `Law No.20 of 2014 concerning Electronic Transactions and its Implementing Regulations `_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/kuwait.rst:24 +msgid "How Odoo Sign complies with Kuwaiti regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/kuwait.rst:26 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Kuwait by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/kuwait.rst:54 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Kuwait:" +msgstr "" + +#: ../../content/applications/productivity/sign/kuwait.rst:65 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Kuwait, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/malaysia.rst:5 +msgid "Odoo Sign legality in Malaysia" +msgstr "" + +#: ../../content/applications/productivity/sign/malaysia.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Malaysia." +msgstr "" + +#: ../../content/applications/productivity/sign/malaysia.rst:11 +msgid "Legal framework for electronic signatures in Malaysia" +msgstr "" + +#: ../../content/applications/productivity/sign/malaysia.rst:13 +msgid "In Malaysia, electronic signatures are regulated under the `Digital Signature Act 1997 `_ and the `Electronic Commerce Act 2006 `_. The law governs transactions performed through electronic means and the use of digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/malaysia.rst:22 +msgid "**Certified digital signatures**: the law governs the use of digital certificates to provide major security and integrity to digital signatures. In some cases, electronic signatures must be certified by an electronic signature certification authority." +msgstr "" + +#: ../../content/applications/productivity/sign/malaysia.rst:27 +msgid "How Odoo Sign complies with Malaysian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/malaysia.rst:29 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Malaysia by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/malaysia.rst:57 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Malaysia:" +msgstr "" + +#: ../../content/applications/productivity/sign/malaysia.rst:68 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Malaysia, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + #: ../../content/applications/productivity/sign/mexico.rst:5 msgid "Odoo Sign legality in Mexico" msgstr "" @@ -3993,6 +5824,318 @@ msgstr "" msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Mexico, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." msgstr "" +#: ../../content/applications/productivity/sign/morocco.rst:5 +msgid "Odoo Sign legality in Morocco" +msgstr "" + +#: ../../content/applications/productivity/sign/morocco.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Morocco." +msgstr "" + +#: ../../content/applications/productivity/sign/morocco.rst:11 +msgid "Legal framework for electronic signatures in Morocco" +msgstr "" + +#: ../../content/applications/productivity/sign/morocco.rst:13 +msgid "In Morocco, electronic signatures are regulated under the `Law No. 53-05 on Digital Signature `_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/morocco.rst:26 +msgid "How Odoo Sign complies with Moroccan regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/morocco.rst:28 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Morocco by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/morocco.rst:56 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Morocco:" +msgstr "" + +#: ../../content/applications/productivity/sign/morocco.rst:67 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Morocco, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/new_zealand.rst:5 +msgid "Odoo Sign legality in New Zealand" +msgstr "" + +#: ../../content/applications/productivity/sign/new_zealand.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in New Zealand." +msgstr "" + +#: ../../content/applications/productivity/sign/new_zealand.rst:11 +msgid "Legal framework for electronic signatures in New Zealand" +msgstr "" + +#: ../../content/applications/productivity/sign/new_zealand.rst:13 +msgid "In New Zealand, electronic signatures are regulated under the `Contract and Commercial Law Act `_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/new_zealand.rst:22 +msgid "**Special cases**: in New Zealand, there are certain use cases that require a traditional signature and expressly exclude the use of electronic signatures." +msgstr "" + +#: ../../content/applications/productivity/sign/new_zealand.rst:26 +msgid "How Odoo Sign complies with New Zealand regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/new_zealand.rst:28 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of New Zealand by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/new_zealand.rst:56 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in New Zealand:" +msgstr "" + +#: ../../content/applications/productivity/sign/new_zealand.rst:67 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of New Zealand, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/nigeria.rst:5 +msgid "Odoo Sign legality in Nigeria" +msgstr "" + +#: ../../content/applications/productivity/sign/nigeria.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Nigeria." +msgstr "" + +#: ../../content/applications/productivity/sign/nigeria.rst:11 +msgid "Legal framework for electronic signatures in Nigeria" +msgstr "" + +#: ../../content/applications/productivity/sign/nigeria.rst:13 +msgid "In Nigeria, electronic signatures are regulated under the `Nigerian Evidence Act `_. The law governs transactions performed through electronic means and the use of digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/nigeria.rst:24 +msgid "How Odoo Sign complies with Nigerian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/nigeria.rst:26 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Nigeria by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/nigeria.rst:54 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Nigeria:" +msgstr "" + +#: ../../content/applications/productivity/sign/nigeria.rst:65 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Nigeria, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/norway.rst:5 +msgid "Odoo Sign legality in Norway" +msgstr "" + +#: ../../content/applications/productivity/sign/norway.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Norway." +msgstr "" + +#: ../../content/applications/productivity/sign/norway.rst:11 +msgid "Legal framework for electronic signatures in Norway" +msgstr "" + +#: ../../content/applications/productivity/sign/norway.rst:13 +msgid "In Norway, electronic signatures are regulated under the Act on electronic trust services that incorporates Electronic Identification and Trust Services for Electronic Transactions in the Internal Market (eIDAS) and Regulation No. 910/2014 of the European Parliament and of the Council. The law governs transactions performed through electronic means and the use of electronic signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/norway.rst:23 +msgid "**Qualified trust service providers**: the law recognizes electronic signatures supported by digital certificates issued by Qualified Trust Service Providers." +msgstr "" + +#: ../../content/applications/productivity/sign/norway.rst:27 +msgid "How Odoo Sign complies with Norwegian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/norway.rst:29 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Norway by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/norway.rst:57 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Norway:" +msgstr "" + +#: ../../content/applications/productivity/sign/norway.rst:68 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Norway, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/oman.rst:5 +msgid "Odoo Sign legality in Oman" +msgstr "" + +#: ../../content/applications/productivity/sign/oman.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Oman." +msgstr "" + +#: ../../content/applications/productivity/sign/oman.rst:11 +msgid "Legal framework for electronic signatures in Oman" +msgstr "" + +#: ../../content/applications/productivity/sign/oman.rst:13 +msgid "In Oman, electronic signatures are regulated under the Electronic Transactions Law. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/oman.rst:25 +msgid "How Odoo Sign complies with Omani regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/oman.rst:27 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Oman by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/oman.rst:55 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Oman:" +msgstr "" + +#: ../../content/applications/productivity/sign/oman.rst:66 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Oman, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/pakistan.rst:5 +msgid "Odoo Sign legality in Pakistan" +msgstr "" + +#: ../../content/applications/productivity/sign/pakistan.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Pakistan." +msgstr "" + +#: ../../content/applications/productivity/sign/pakistan.rst:11 +msgid "Legal framework for electronic signatures in Pakistan" +msgstr "" + +#: ../../content/applications/productivity/sign/pakistan.rst:13 +msgid "In Pakistan, electronic signatures are regulated under the `Electronic Transactions Ordinance `_. The law governs the use of electronic records and signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/pakistan.rst:21 +msgid "**Certified electronic signatures**: special electronic signature that incorporates certificates issued by an accredited certification service provider authorized by the Certification Council as being capable of establishing authenticity and integrity of an electronic document." +msgstr "" + +#: ../../content/applications/productivity/sign/pakistan.rst:26 +msgid "How Odoo Sign complies with Pakistani regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/pakistan.rst:28 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Pakistan by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/pakistan.rst:56 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Pakistan:" +msgstr "" + +#: ../../content/applications/productivity/sign/pakistan.rst:67 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Pakistan, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/peru.rst:5 +msgid "Odoo Sign legality in Peru" +msgstr "" + +#: ../../content/applications/productivity/sign/peru.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Peru." +msgstr "" + +#: ../../content/applications/productivity/sign/peru.rst:11 +msgid "Legal framework for electronic signatures in Peru" +msgstr "" + +#: ../../content/applications/productivity/sign/peru.rst:13 +msgid "In Peru, electronic signatures are regulated under the `Peruvian Civil Code, Law 27269 – Law of Digital Signatures and Certificates `_, `Supreme Decree N° 052-2008-PCM – Regulation of the Law of Digital Signatures and Certificates `_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/peru.rst:23 +msgid "**Digital signatures generated with the official electronic signature infrastructure**: digital signature generated using a digital certificate supplied by a provider accredited as such by the National Institute for the Defense of Competition and the Protection of Intellectual Property." +msgstr "" + +#: ../../content/applications/productivity/sign/peru.rst:28 +msgid "How Odoo Sign complies with Peruvian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/peru.rst:30 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Peru by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/peru.rst:58 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Peru:" +msgstr "" + +#: ../../content/applications/productivity/sign/peru.rst:69 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Peru, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/philippines.rst:5 +msgid "Odoo Sign legality in the Philippines" +msgstr "" + +#: ../../content/applications/productivity/sign/philippines.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in the Philippines." +msgstr "" + +#: ../../content/applications/productivity/sign/philippines.rst:11 +msgid "Legal framework for electronic signatures in the Philippines" +msgstr "" + +#: ../../content/applications/productivity/sign/philippines.rst:13 +msgid "In the Philippines, electronic signatures are regulated under the `Republic Act No. 8792 `_ and the `Electronic Commerce Act `_. The law governs the use of electronic records and signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/philippines.rst:22 +msgid "**Philippine national public key infrastructure system**: the Philippine government operates an official PKI system known as the Philippine National Public Key Infrastructure. This system requires subscribers to adhere to specific obligations regarding the custody and proper use of digital certificates." +msgstr "" + +#: ../../content/applications/productivity/sign/philippines.rst:28 +msgid "How Odoo Sign complies with Philippine regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/philippines.rst:30 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of the Philippines by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/philippines.rst:58 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in the Philippines:" +msgstr "" + +#: ../../content/applications/productivity/sign/philippines.rst:69 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of the Philippines, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/qatar.rst:5 +msgid "Odoo Sign legality in Qatar" +msgstr "" + +#: ../../content/applications/productivity/sign/qatar.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Qatar." +msgstr "" + +#: ../../content/applications/productivity/sign/qatar.rst:11 +msgid "Legal framework for electronic signatures in Qatar" +msgstr "" + +#: ../../content/applications/productivity/sign/qatar.rst:13 +msgid "In Qatar, electronic signatures are regulated under the `Electronic Transactions and Commerce Law No. 16 of 2010 `_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/qatar.rst:22 +msgid "**Certification authorities**: digital signature generated using a digital certificate supplied by a certified provider." +msgstr "" + +#: ../../content/applications/productivity/sign/qatar.rst:26 +msgid "How Odoo Sign complies with Qatari regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/qatar.rst:28 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Qatar by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/qatar.rst:56 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Qatar:" +msgstr "" + +#: ../../content/applications/productivity/sign/qatar.rst:67 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Qatar, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + #: ../../content/applications/productivity/sign/russia.rst:5 msgid "Odoo Sign legality in Russia" msgstr "" @@ -4029,6 +6172,110 @@ msgstr "" msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Russia, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." msgstr "" +#: ../../content/applications/productivity/sign/saudi_arabia.rst:5 +msgid "Odoo Sign legality in Saudi Arabia" +msgstr "" + +#: ../../content/applications/productivity/sign/saudi_arabia.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Saudi Arabia." +msgstr "" + +#: ../../content/applications/productivity/sign/saudi_arabia.rst:11 +msgid "Legal framework for electronic signatures in Saudi Arabia" +msgstr "" + +#: ../../content/applications/productivity/sign/saudi_arabia.rst:13 +msgid "In Saudi Arabia, electronic signatures are regulated under the `Electronic Transactions Law `_ and the Regulation No. 1/1429. The law governs transactions performed through electronic means and the use of electronic signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/saudi_arabia.rst:21 +msgid "**Certificate-based digital signatures**: the law recognizes electronic signatures supported by digital certificates issued by accredited Certification Service Provider." +msgstr "" + +#: ../../content/applications/productivity/sign/saudi_arabia.rst:25 +msgid "How Odoo Sign complies with Saudi regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/saudi_arabia.rst:27 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Saudi Arabia by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/saudi_arabia.rst:55 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Saudi Arabia:" +msgstr "" + +#: ../../content/applications/productivity/sign/saudi_arabia.rst:66 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Saudi Arabia, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/singapore.rst:5 +msgid "Odoo Sign legality in Singapore" +msgstr "" + +#: ../../content/applications/productivity/sign/singapore.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Singapore." +msgstr "" + +#: ../../content/applications/productivity/sign/singapore.rst:11 +msgid "Legal framework for electronic signatures in Singapore" +msgstr "" + +#: ../../content/applications/productivity/sign/singapore.rst:13 +msgid "In Singapore, electronic signatures are regulated under the `Electronic Transactions Act `_. The law recognizes the use of electronic documents and electronic signatures for the execution of contracts and other transactions. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/singapore.rst:23 +msgid "How Odoo Sign complies with Singapore regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/singapore.rst:25 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Singapore by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/singapore.rst:53 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Singapore:" +msgstr "" + +#: ../../content/applications/productivity/sign/singapore.rst:64 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Singapore, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/south_africa.rst:5 +msgid "Odoo Sign legality in South Africa" +msgstr "" + +#: ../../content/applications/productivity/sign/south_africa.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in South Africa." +msgstr "" + +#: ../../content/applications/productivity/sign/south_africa.rst:11 +msgid "Legal framework for electronic signatures in South Africa" +msgstr "" + +#: ../../content/applications/productivity/sign/south_africa.rst:13 +msgid "In South Africa, electronic signatures are regulated under the `Electronic Communications and Transactions Act `_. The law governs transactions performed through electronic means and the use of digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/south_africa.rst:22 +msgid "**Advance electronic signatures**: in some cases, electronic signatures must be certified by an electronic signature certification authority." +msgstr "" + +#: ../../content/applications/productivity/sign/south_africa.rst:26 +msgid "How Odoo Sign complies with South African regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/south_africa.rst:28 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of South Africa by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/south_africa.rst:56 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in South Africa:" +msgstr "" + +#: ../../content/applications/productivity/sign/south_africa.rst:67 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of South Africa, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + #: ../../content/applications/productivity/sign/south_korea.rst:5 msgid "Odoo Sign legality in South Korea" msgstr "" @@ -4065,6 +6312,178 @@ msgstr "" msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of South Korea, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." msgstr "" +#: ../../content/applications/productivity/sign/switzerland.rst:5 +msgid "Odoo Sign legality in Switzerland" +msgstr "" + +#: ../../content/applications/productivity/sign/switzerland.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Switzerland." +msgstr "" + +#: ../../content/applications/productivity/sign/switzerland.rst:11 +msgid "Legal framework for electronic signatures in Switzerland" +msgstr "" + +#: ../../content/applications/productivity/sign/switzerland.rst:13 +msgid "In Switzerland, electronic signatures are regulated under the `Federal Act on Electronic Signatures `_ and the Swiss Code of Obligations. The law governs transactions performed through electronic means and the use of electronic signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/switzerland.rst:22 +msgid "**Qualified electronic signatures**: the law recognizes electronic signatures supported by digital certificates issued by accredited Certification Service Providers mandatory in some cases." +msgstr "" + +#: ../../content/applications/productivity/sign/switzerland.rst:26 +msgid "How Odoo Sign complies with Swiss regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/switzerland.rst:28 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Switzerland by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/switzerland.rst:56 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Switzerland:" +msgstr "" + +#: ../../content/applications/productivity/sign/switzerland.rst:67 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Switzerland, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/thailand.rst:5 +msgid "Odoo Sign legality in Thailand" +msgstr "" + +#: ../../content/applications/productivity/sign/thailand.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Thailand." +msgstr "" + +#: ../../content/applications/productivity/sign/thailand.rst:11 +msgid "Legal framework for electronic signatures in Thailand" +msgstr "" + +#: ../../content/applications/productivity/sign/thailand.rst:13 +msgid "In Thailand, electronic signatures are regulated under the `Electronic Transaction Act B.E. 2544 `_. The law governs transactions performed through electronic means and the use of digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/thailand.rst:23 +msgid "How Odoo Sign complies with Thai regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/thailand.rst:25 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Thailand by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/thailand.rst:53 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Thailand:" +msgstr "" + +#: ../../content/applications/productivity/sign/thailand.rst:64 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Thailand, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/turkey.rst:5 +msgid "Odoo Sign legality in Turkey" +msgstr "" + +#: ../../content/applications/productivity/sign/turkey.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Turkey." +msgstr "" + +#: ../../content/applications/productivity/sign/turkey.rst:11 +msgid "Legal framework for electronic signatures in Turkey" +msgstr "" + +#: ../../content/applications/productivity/sign/turkey.rst:13 +msgid "In Turkey, electronic signatures are regulated under the `Electronic Signature Law No.5070 `_, `Code of Obligations No. 6098 `_, among other secondary regulations. The law governs transactions performed through electronic means and the use of electronic signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/turkey.rst:23 +msgid "**Electronic certificate service provider**: the law recognizes electronic signatures supported by digital certificates issued by accredited Certification Service Provider." +msgstr "" + +#: ../../content/applications/productivity/sign/turkey.rst:27 +msgid "How Odoo Sign complies with Turkish regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/turkey.rst:29 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Turkey by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/turkey.rst:57 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Turkey:" +msgstr "" + +#: ../../content/applications/productivity/sign/turkey.rst:68 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Turkey, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/ukraine.rst:5 +msgid "Odoo Sign legality in Ukraine" +msgstr "" + +#: ../../content/applications/productivity/sign/ukraine.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Ukraine." +msgstr "" + +#: ../../content/applications/productivity/sign/ukraine.rst:11 +msgid "Legal framework for electronic signatures in Ukraine" +msgstr "" + +#: ../../content/applications/productivity/sign/ukraine.rst:13 +msgid "In Ukraine, electronic signatures are regulated under the Law of Ukraine No. 852-IV \"On Electronic Digital Signature. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/ukraine.rst:25 +msgid "How Odoo Sign complies with Ukrainian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/ukraine.rst:27 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Ukraine by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/ukraine.rst:55 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Ukraine:" +msgstr "" + +#: ../../content/applications/productivity/sign/ukraine.rst:66 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Ukraine, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:5 +msgid "Odoo Sign legality in the United Arab Emirates" +msgstr "" + +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in the United Arab Emirates." +msgstr "" + +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:11 +msgid "Legal framework for electronic signatures in the United Arab Emirates" +msgstr "" + +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:13 +msgid "In the United Arab Emirates, electronic signatures are regulated under the `Federal Decree by Law No. 46 of 2021 on Electronic Transactions and Trust Services `_, `ADGM Electronic Transactions Regulations 202 `_, `DIFC Law No. 2 of 2017 `_. The law governs transactions performed through electronic means and the use of digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:24 +msgid "**Qualified electronic signature**: the law recognizes electronic signatures supported by digital certificates issued by a qualified trust service provider." +msgstr "" + +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:28 +msgid "How Odoo Sign complies with Emirati regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:30 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of the United Arab Emirates by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:58 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in the United Arab Emirates:" +msgstr "" + +#: ../../content/applications/productivity/sign/united_arab_emirates.rst:69 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of the United Arab Emirates, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + #: ../../content/applications/productivity/sign/united_kingdom.rst:5 msgid "Odoo Sign legality in the United Kingdom" msgstr "" @@ -4101,39 +6520,115 @@ msgstr "" msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of the United Kingdom, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." msgstr "" +#: ../../content/applications/productivity/sign/uzbekistan.rst:5 +msgid "Odoo Sign legality in Uzbekistan" +msgstr "" + +#: ../../content/applications/productivity/sign/uzbekistan.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Uzbekistan." +msgstr "" + +#: ../../content/applications/productivity/sign/uzbekistan.rst:11 +msgid "Legal framework for electronic signatures in Uzbekistan" +msgstr "" + +#: ../../content/applications/productivity/sign/uzbekistan.rst:13 +msgid "In Uzbekistan, electronic signatures are regulated under the `Law On Electronic Digital Signature `_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/uzbekistan.rst:22 +msgid "**Electronic digital signature keys**: digital signature generated using a digital certificate supplied by a qualified provider." +msgstr "" + +#: ../../content/applications/productivity/sign/uzbekistan.rst:26 +msgid "How Odoo Sign complies with Uzbekistani regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/uzbekistan.rst:28 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Uzbekistan by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/uzbekistan.rst:56 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Uzbekistan:" +msgstr "" + +#: ../../content/applications/productivity/sign/uzbekistan.rst:67 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Uzbekistan, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/vietnam.rst:5 +msgid "Odoo Sign legality in Vietnam" +msgstr "" + +#: ../../content/applications/productivity/sign/vietnam.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Vietnam." +msgstr "" + +#: ../../content/applications/productivity/sign/vietnam.rst:11 +msgid "Legal framework for electronic signatures in Vietnam" +msgstr "" + +#: ../../content/applications/productivity/sign/vietnam.rst:13 +msgid "In Vietnam, electronic signatures are regulated under the `Civil Code No. 91/2015/QH132015 `_, the `Law on E-Transactions No. 51/2005/QH11 `_. The law governs transactions performed through electronic means and the use of digital signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/vietnam.rst:23 +msgid "**Certified electronic signatures**: the law regulates the use of digital certificates that guarantee security and integrity of the signature. In some cases, electronic signatures must be certified by an electronic signature certification service provide" +msgstr "" + +#: ../../content/applications/productivity/sign/vietnam.rst:28 +msgid "How Odoo Sign complies with Vietnamese regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/vietnam.rst:30 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Vietnam by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/vietnam.rst:58 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Vietnam:" +msgstr "" + +#: ../../content/applications/productivity/sign/vietnam.rst:69 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Vietnam, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + #: ../../content/applications/productivity/spreadsheet.rst:6 msgid "Spreadsheet" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:15 +#: ../../content/applications/productivity/spreadsheet.rst:16 msgid "Spreadsheet lets you organize, analyze, and visualize your data in tabular form. Among others, you can:" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:18 +#: ../../content/applications/productivity/spreadsheet.rst:19 msgid ":doc:`Insert and link your Odoo data (pivots, graphs, lists, and menus) `." msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:19 -msgid ":doc:`Use formulas and functions `." -msgstr "" - #: ../../content/applications/productivity/spreadsheet.rst:20 -msgid ":doc:`Use default templates or create new ones `." +msgid ":doc:`Use global filters `." msgstr "" #: ../../content/applications/productivity/spreadsheet.rst:21 -msgid "Format data." +msgid ":doc:`Use formulas and functions `." msgstr "" #: ../../content/applications/productivity/spreadsheet.rst:22 +msgid ":doc:`Use default templates or create new ones `." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet.rst:23 +msgid "Format data." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet.rst:24 msgid "Sort and filter data." msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:27 +#: ../../content/applications/productivity/spreadsheet.rst:29 msgid "Glossary" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:29 +#: ../../content/applications/productivity/spreadsheet.rst:31 msgid "Some of Spreadsheet's main :abbr:`UI (user interface)` elements are highlighted and defined below." msgstr "" @@ -4141,35 +6636,35 @@ msgstr "" msgid "Spreadsheet main UI elements" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:35 +#: ../../content/applications/productivity/spreadsheet.rst:37 msgid "Menu bar" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:36 +#: ../../content/applications/productivity/spreadsheet.rst:38 msgid "Top bar" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:37 +#: ../../content/applications/productivity/spreadsheet.rst:39 msgid "Formula bar" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:38 +#: ../../content/applications/productivity/spreadsheet.rst:40 msgid "Filters button" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:39 +#: ../../content/applications/productivity/spreadsheet.rst:41 msgid "Row header" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:40 +#: ../../content/applications/productivity/spreadsheet.rst:42 msgid "Column header" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:41 +#: ../../content/applications/productivity/spreadsheet.rst:43 msgid "Cell menu" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:42 +#: ../../content/applications/productivity/spreadsheet.rst:44 msgid "Bottom bar" msgstr "" @@ -4552,6 +7047,7 @@ msgid "`Excel DVARP article `_" msgstr "" +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:3 +msgid "Global filters" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:11 +msgid "Create dynamic views of :doc:`inserted data `, by mapping data source fields to *global filters* in the Odoo **Spreadsheets** app." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:15 +msgid "The global filters are represented by the |global-filter| icon, and enable data that was inserted via a pivot table, list, or chart to be filtered. Global filters differ from the *sort and filter* feature for cell ranges represented by the :icon:`fa-filter` :guilabel:`(filter)` icon." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:-1 +msgid "The global filters menu sidebar on a spreadsheet." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:24 +msgid "Add filters" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:26 +msgid "Navigate to the :menuselection:`Documents app` and click on the desired spreadsheet, then open the |global-filter| filter menu." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:29 +msgid "Create a new filter by selecting one of the buttons under the :guilabel:`Add a new filter...` section:" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:32 +msgid ":ref:`Date `: filter dates by matching data source date fields to a time range (e.g., *Month / Quarter*, *Relative Period*, or *From / To*)." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:34 +msgid ":ref:`Relation `: filter records by matching data source fields to fields in a related model (e.g., *Lead/Opportunity*, *Sales Order*, or *Event Registration*)." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:37 +msgid ":ref:`Text `: filter text by matching data source text fields to a string of text (e.g., *Restrict values to a range* and/or provide a *Default value*)." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:41 +msgid "Only filters that are able to be applied to the fields in the data source are shown." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:48 +msgid "The *Date* global filter enables the filtering of data sources by a specific time range, to automatically filter on the current period, or to offset the time range relative to the period." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:51 +msgid "With the |global-filter| menu open, select the :guilabel:`Date` button to create a new date filter. The :guilabel:`Filter properties` menu displays the following fields for configuration below." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:54 +msgid "First, enter a name for the new date filter in the :guilabel:`Label` field." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:56 +msgid "Then, select one of the three period options in the :guilabel:`Time range` field:" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:58 +msgid ":guilabel:`Month / Quarter`: enables a drop-down menu of specific months and quarters of a year (i.e., *Q1*, *Q2*, *January*, etc.)." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:60 +msgid ":guilabel:`Relative Period`: enables a drop-down menu of specific moving time frames (i.e., *Year to Date*, *Last 7 Days*, *Last 30 Days*, etc.)." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:62 +msgid ":guilabel:`From / To`: enables *Date from...* and *Date to...* date selection fields to define a specific time range (e.g., `06/05/2024` to `06/27/2024`)." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:65 +msgid "Optionally, set a :guilabel:`Default value` for the :guilabel:`Time range`." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:68 +msgid "The :guilabel:`Default value` field only appears for :guilabel:`Month / Quarter` or :guilabel:`Relative Period` ranges." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:71 +msgid "If the :guilabel:`Month / Quarter` range is selected, tick the :guilabel:`Automatically filter on the current period` checkbox to define the default period of either :guilabel:`Month`, :guilabel:`Quarter`, or :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:75 +msgid "Next, configure the :guilabel:`Field matching` for each data source. To do so, expand the section by clicking on the :guilabel:`Field matching` heading, to reveal a list of the data sources in the spreadsheet where each data source has two fields for matching:" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:79 +msgid ":guilabel:`Date field`: select a date field from the data source model to apply the time range to." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:80 +msgid ":guilabel:`Period offset`: (optionally) select an offset that shifts the time range by a relative period." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:83 +msgid "The options available are: :guilabel:`Previous`, :guilabel:`Before Previous`, :guilabel:`Next`, :guilabel:`After Next`." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:86 +msgid "Lastly, once all the information is entered on the form, click the :guilabel:`Save` button. If any of the data source fields do not match the data type of *date* (or *datetime*), an error is shown stating :guilabel:`Some required fields are not valid`." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:91 +msgid "Consider a :guilabel:`Period offset` of :guilabel:`Next` when using the :guilabel:`Month / Quarter` range to apply the filter to the *next* period relative to the set time range." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:94 +msgid "With this configuration, selecting `January` `2024` as the date, filters data as `February` `2024`; where the selected month is offset to the next month." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:0 +msgid "A date filter with a period offset of \"Next\" configured." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:104 +msgid "Relation" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:106 +msgid "The *Relation* global filter enables the filtering of records in data sources by selecting a field from a related model." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:109 +msgid "With the |global-filter| menu open, select the :guilabel:`Relation` button to create a new relation filter. The :guilabel:`Filter properties` menu displays the following fields for configuration." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:112 +msgid "First, enter a name for the new relation filter in the :guilabel:`Label` field." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:114 +msgid "Then, select or search for a model from the :guilabel:`Related model` field." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:116 +msgid "Once a model is selected, the :guilabel:`Default value` and :guilabel:`Field matching` fields appear." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:119 +msgid "Optionally, set a :guilabel:`Default value` for the :guilabel:`Related model`. The available options are records of the model." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:122 +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:160 +msgid "Next, configure the :guilabel:`Field matching` for each data source. To do so, expand the section by clicking on the :guilabel:`Field matching` heading, to reveal a list of the data sources in the spreadsheet where each data source has a field for matching." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:126 +msgid "Select a field from the data source model from which to apply the relation filter." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:128 +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:166 +msgid "Lastly, once all the information is entered on the form, click the :guilabel:`Save` button. If any of the data source fields do not match the data type of the related model, an error is shown stating :guilabel:`Some required fields are not valid`." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:133 +msgid "Consider a *Relation* filter with the :guilabel:`Related model` set as :guilabel:`Contact`. The :guilabel:`Field matching` *CRM* lead (`crm.lead`) pivot data sources are set to :guilabel:`Customer`." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:137 +msgid "With this configuration, selecting a customer record filters the pivot table to only leads that are related to the selected customer record." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:0 +msgid "A relation filter with the Contact model configured." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:149 +msgid "The *Text* global filter enables the filtering of text by matching data source text fields to a string of text or to a range of predefined values." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:152 +msgid "With the |global-filter| menu open, select the :guilabel:`Text` button to create a new text filter. The :guilabel:`Filter properties` menu displays the following fields for configuration." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:155 +msgid "First, enter a name for the new text filter in the :guilabel:`Label` field." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:157 +msgid "Then, choose whether or not to :guilabel:`Restrict values to a range` by ticking the checkbox. Doing so, reveals a field to input a range within the spreadsheet. Either type in or select the range." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:164 +msgid "Select a field from the data source model from which to apply the text filter." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:171 +msgid "Consider a text filter with the range `A2:A6` added to the :guilabel:`Restrict values to a range` field. The spreadsheet has five different product names listed as values in the cells of column `A`, rows `2` though `6`." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:175 +msgid "With the above configuration, a pivot table of products can be filtered by product name by selecting one of the 5 predefined values available in the text filter." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:178 +msgid "Furthermore, if the values in the range `A2:A6` are added dynamically– the text filter becomes dynamic as well." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:0 +msgid "A dynamic text filter with a restricted range." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:186 +msgid "Manage filters" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:188 +msgid "Open the |global-filter| filter menu by navigating to the :menuselection:`Documents app` and clicking on the desired spreadsheet." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:191 +msgid "Existing global filters appear under the :guilabel:`Filters` section. Filters can be used individually, or at the same time." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:195 +msgid "The order of existing filters can be changed by hovering over a filter and using the |drag-handle| icon to change the position." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:198 +msgid "To reset a filter with set values back to default, click on the :icon:`fa-times` (clear) icon next to the value in the filter." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/global_filters.rst:201 +msgid "To edit an existing filter, select the :icon:`fa-cog` :guilabel:`(gear)` icon to open the filter's :guilabel:`Filter properties` menu. From here, edits can be made or the filter can be deleted by clicking the :guilabel:`Remove` button." +msgstr "" + #: ../../content/applications/productivity/spreadsheet/insert.rst:3 msgid "Link Odoo data" msgstr "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index e2740152c..f4ff9629e 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 13:30+0000\n" +"POT-Creation-Date: 2024-08-21 11:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -57,6 +57,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:13 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:20 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:15 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:20 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:14 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:19 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:17 @@ -82,6 +83,7 @@ msgstr "" #: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:24 #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:14 #: ../../content/applications/sales/subscriptions/closing.rst:9 +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:17 msgid "Configuration" msgstr "" @@ -195,15 +197,15 @@ msgstr "" msgid "First, ensure the *Leads* feature is enabled in the database by navigating to :menuselection:`CRM app --> Configuration --> Settings`. Tick the :guilabel:`Leads` checkbox, then click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:17 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:19 msgid "Configure email aliases" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:19 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:21 msgid "Each sales team has the option to create and utilize their own unique email alias. When messages are sent to this address, a lead (or opportunity), is created with the information from the message." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:23 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:25 msgid "To create or update a sales teams' email alias, navigate to :menuselection:`CRM app --> Configuration --> Sales Teams`. Click on a team from the list to open the team's details page." msgstr "" @@ -211,35 +213,35 @@ msgstr "" msgid "The sales team details page, focused on the email alias section." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:30 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:32 msgid "In the :guilabel:`Email Alias` field, enter a name for the email alias, or edit the existing name. In the :guilabel:`Accept Emails From` field, use the drop-down menu to choose who is allowed to send messages to this email alias:" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:34 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:36 msgid ":guilabel:`Everyone`: messages are accepted from any email address." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:35 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:37 msgid ":guilabel:`Authenticated Partners`: only accepts messages from email addresses associated with a a partner (contact or customer) record." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:37 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:39 msgid ":guilabel:`Followers only`: only accepts messages from those who are following a record related to the team, such as a lead or opportunity. Messages are also accepted from team members." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:39 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:41 msgid ":guilabel:`Authenticated Employees`: only accepts messages from email addresses that are connected to a record in the *Employees* app." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:43 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:45 msgid "Leads created from email" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:45 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:47 msgid "Leads created from email alias messages can be viewed by navigating to :menuselection:`CRM app --> Leads`. Click a lead from the list to open it, and view the details." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:48 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:50 msgid "The email received by the alias is added to the *chatter* thread for the lead. The subject line of the message is added to the title field, and the :guilabel:`Email` field is updated with the contact's email address." msgstr "" @@ -247,51 +249,51 @@ msgstr "" msgid "The chatter thread of a newly created lead in the CRM app." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:57 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:59 msgid "If the *leads* feature is **not** enabled on the database, messages to the email alias are added to the database as opportunities." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:61 -msgid ":doc:`../../../general/email_communication/email_servers`" -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:64 -msgid "Manually create leads" +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:63 +msgid ":doc:`../../../general/email_communication`" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:66 +msgid "Manually create leads" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:68 msgid "Leads can be added directly to the *CRM* app by manually creating a new record. Navigate to :menuselection:`CRM app --> Leads` to view a list of existing leads." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:70 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:72 msgid "Leads can also be added via the :doc:`Generate Leads ` button." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:72 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:74 msgid "At the top-left of the list, click :guilabel:`New` to open a blank :guilabel:`Leads` form." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:74 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:76 msgid "In the first field of the new form, enter a title for the new lead. Next, enter a :guilabel:`Contact Name`, and a :guilabel:`Company Name`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:78 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:80 msgid "If a lead is :doc:`converted to an opportunity `, the :guilabel:`Company Name` field is used to either link this opportunity to an existing customer, or to create a new customer." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:82 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:84 msgid "Manually create opportunities" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:84 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:86 msgid "To manually create an opportunity, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`. At the top-left of the page, click :guilabel:`New` to create a new opportunity Kanban card. In the :guilabel:`Organization/Contact` field, enter the name of the company the opportunity is for." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:88 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:90 msgid "Choose a name, and enter it in the :guilabel:`Opportunity` field. *This is a required field.* When manually creating an opportunity, it is helpful to add a name that relates to the details of the opportunity." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:93 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:95 msgid "In the example below, the opportunity is named `5 VP Chairs`. This identifies the product the customer is interested in, as well as the potential number of products." msgstr "" @@ -299,43 +301,43 @@ msgstr "" msgid "An example of an opportunity in the CRM pipeline." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:100 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:102 msgid "Enter the contact information for the opportunity in the :guilabel:`Email` and :guilabel:`Phone` fields." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:103 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:105 msgid "In the :guilabel:`Expected Revenue` field, enter an estimated value for the opportunity." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:106 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:108 msgid "The information in the :guilabel:`Expected Revenue` and priority fields can be used to track performance for individual salespeople, and on a team basis. See :doc:`../performance/expected_revenue_report` and :doc:`../track_leads/lead_scoring` for more information." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:111 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:113 msgid "Then, use the |st-o| :guilabel:`(star)` icons to assign a priority." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:113 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:115 msgid "|st-o| |st-o| |st-o|: low priority" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:114 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:116 msgid "|st| |st-o| |st-o|: medium priority" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:115 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:117 msgid "|st| |st| |st-o|: high priority" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:116 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:118 msgid "|st| |st| |st|: very high priority" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:119 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:121 msgid "Assigning a priority changes the order of leads in Kanban view, with higher priority leads displayed first." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:122 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:124 msgid "Once all the necessary information has been entered, click :guilabel:`Add`." msgstr "" @@ -682,114 +684,118 @@ msgid "Qualified lead form with New Quotation button emphasized." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:29 +msgid "The **Sales** application **must** be installed for the :guilabel:`New Quotation` button to appear." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:33 msgid "The :guilabel:`Customer` field is **not** required on the opportunity form." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:31 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:35 msgid "However, customer information must be added or linked before a quotation can be sent. If the :guilabel:`Customer` field is left blank on the opportunity, clicking the :guilabel:`New Quotation` button opens a pop-up window with the following options:" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:35 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:39 msgid ":guilabel:`Create a new customer`: creates a new customer record, using any available information provided on the opportunity form." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:37 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:41 msgid ":guilabel:`Link to an existing customer`: opens a drop-down field with existing customer names. Select a name to link this new quotation to an existing customer record." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:39 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:43 msgid ":guilabel:`Do not link to a customer`: the quotation will **not** be linked to a customer, and no changes are made to the customer information." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:42 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:46 msgid "Once this button is clicked, a new quotation form appears. Confirm the information in the top half of the form, and update any missing or incorrect fields:" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:45 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:49 msgid ":guilabel:`Customer`: the company or contact for whom this quotation was created." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:46 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:50 msgid ":guilabel:`Referrer`: if this customer was referred by another customer or contact, select it from the drop-down menu in this field." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:48 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:52 msgid ":guilabel:`Invoice Address`: physical address where the invoice should be sent." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:49 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:53 msgid ":guilabel:`Delivery Address`: physical address where any products should be delivered." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:50 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:54 msgid ":guilabel:`Quotation Template`: if applicable, select a pre-configured :doc:`quotation template ` from this field." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:52 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:56 msgid ":guilabel:`Expiration`: date when this quotation is no longer valid." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:53 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:57 msgid ":guilabel:`Quotation Date`: creation date of draft/sent orders, confirmation date of confirmed orders. Note that this field is only visible if :doc:`Developer mode (debug mode) ` is active." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:56 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:60 msgid ":guilabel:`Recurring Plan`: if this quotation is for a recurring product or subscription, select the recurring plan configuration to be used." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:58 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:62 msgid ":guilabel:`Pricelist`: select a pricelist to be applied to this order." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:59 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:63 msgid ":guilabel:`Payment Terms`: select any applicable payment terms for this quotation." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:66 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:70 msgid "The :guilabel:`Expiration` field automatically populates based on the creation date of the quotation, and the default validity time frame." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:69 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:73 msgid "To update the default validity time frame, navigate to :menuselection:`Sales app --> Configuration --> Settings --> Quotations & Orders` and update the :guilabel:`Default Quotation Validity` field. To disable automatic expiration, enter `0` in this field." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:73 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:77 msgid "When the desired changes are complete, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:75 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:79 msgid "When using a quotation template, the expiration date is based off of the :guilabel:`Quotation Validity` field on the template. To alter the validity date computation on a template, go to :menuselection:`Sales app --> Configuration --> Sales Orders --> Quotation Templates`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:79 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:83 msgid "Then, click on a template to open it, and update the number in the :guilabel:`Quotation Validity` field." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:83 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:87 msgid "Order lines" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:85 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:89 msgid "After updating the customer, payment, and deadline information on the new quotation, the :guilabel:`Order Lines` tab can be updated with the appropriate product information." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:88 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:92 msgid "To do that, click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:90 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:94 msgid "Next, type the name of an item into the :guilabel:`Product` field to search through the product catalog. Then, select a product from the drop-down menu, or create a new one by selecting :guilabel:`Create` or :guilabel:`Create and Edit`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:94 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:98 msgid "After selecting a product, update the :guilabel:`Quantity`, if necessary. Confirm the information in the remaining fields." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:97 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:101 msgid "To remove a line from the quotation, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:99 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:103 msgid "To organize products into sections click :guilabel:`Add a section` and type a name for the section. Then, click the :icon:`oi-draggable` :guilabel:`(drag)` icon to the left of the name and drag to move the section to the appropriate location. Move each product using the same method to finish organizing the quotation order lines." msgstr "" @@ -797,15 +803,15 @@ msgstr "" msgid "Categories are used to create separate sections on the order lines of a quote." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:109 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:113 msgid "Product catalog" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:111 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:115 msgid "To quickly add numerous products to the quotation, click the :guilabel:`Catalog` button to open the product catalog." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:114 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:118 msgid "All products in the database are listed as cards and can be sorted in the left panel by :guilabel:`Product Category` and :guilabel:`Attributes`." msgstr "" @@ -813,7 +819,7 @@ msgstr "" msgid "The product catalog displays all products as cards." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:121 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:125 msgid "To add a product, click the :icon:`fa-shopping-cart` :guilabel:`Add` button on the product card. Set the quantity of the item using the :icon:`fa-plus` :guilabel:`(add)` or :icon:`fa-minus` :guilabel:`(subtract)` buttons, or type the quantity in the number field between the two buttons. To remove an item, click the :icon:`fa-trash` :guilabel:`Remove` button on the product card." msgstr "" @@ -821,113 +827,113 @@ msgstr "" msgid "The purple add and subtract buttons are used to set the quantity of an item." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:130 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:134 msgid "Once all product quantities are set, click the :guilabel:`Back to Quotation` button to return to the quotation. The items selected in the product catalog now appear in the :guilabel:`Order Lines` tab." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:134 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:138 msgid "Preview and send quotation" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:136 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:140 msgid "To see a preview of the quotation as the customer will see it, click the :guilabel:`Preview` button. Doing so opens a preview in the :guilabel:`Customer Portal`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:139 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:143 msgid "After reviewing the customer preview, click :guilabel:`Return to edit mode` to return to the quotation form in the backend." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:142 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:146 msgid "When the quotation is ready to deliver to the customer, click the :guilabel:`Send by Email` button." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:144 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:148 msgid "Doing so opens a pop-up window with a pre-configured email message. Information from the quotation, including the contact information, total cost, and quotation title are be imported from the quotation." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:148 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:152 msgid "A PDF of the quotation is added as an attachment to the email." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:151 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:155 msgid "A pre-loaded template is used to create the email message. To alter the template, click the internal link to the right of the :guilabel:`Load template` field, located at the bottom of the email pop-up window." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:155 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:159 msgid "To select a new template, select an option from the :guilabel:`Load template` drop-down menu." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:157 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:161 msgid "Proceed to make any necessary changes to the email, then click :guilabel:`Send`. A copy of the message is added to the *Chatter* of the of the record." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:160 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:164 msgid "After a quotation is sent, the originating opportunity's :guilabel:`Quotations` smart button updates with a new count. This quotation, and all other quotations can be accessed through this smart button at the top of the opportunity in the *CRM* app." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:164 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:168 msgid "Any quotations attached to the opportunity that are confirmed, and have therefore been converted to sales orders, will be deducted from the number listed on the :guilabel:`Quotations` smart button. Instead, the value of the sales order will appear in the :guilabel:`Orders` smart button located in the same control panel." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:170 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:174 msgid "Mark an opportunity won or lost" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:172 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:176 msgid "In order to keep the pipeline up to date and accurate, opportunities need to be identified as *won* or *lost* once a customer has responded to a quotation." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:175 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:179 msgid "To mark an opportunity as *won* or *lost*, return to the opportunity using the breadcrumbs at the top-left of the quotation form. Or navigate to :menuselection:`CRM app --> Sales --> My Pipeline` and click on the correct opportunity to open it." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:179 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:183 msgid "At the top-left of the form, click on either the :guilabel:`Won` or :guilabel:`Lost` button." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:181 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:185 msgid "If the opportunity is marked *won*, a green :guilabel:`Won` banner is added to the record, and it is moved to the :guilabel:`Won` stage." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:184 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:188 msgid "Marking an opportunity as *lost*, via the :guilabel:`Lost` button opens a :guilabel:`Mark Lost` pop-up window, where a :guilabel:`Lost Reason` can be entered." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:187 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:191 msgid "From the :guilabel:`Lost Reason` drop-down field, 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/acquire_leads/send_quotes.rst:192 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:196 msgid "It's best practice to try and use pre-configured :guilabel:`Lost Reason` values as much as possible or to limit the creation of new values only to sales team leads. Using consistent values for this parameter will make pipeline analysis easier and more accurate when filtering for the :guilabel:`Lost Reason` parameter." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:197 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:201 msgid "To set up new values for this field, navigate to :menuselection:`CRM --> Configuration --> Lost Reasons`, and click both :guilabel:`New`and :guilabel:`Save` for each new entry added to the list." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:201 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:205 msgid "Additional notes and comments can be added in the :guilabel:`Closing Note` field." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:203 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:207 #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:34 #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:192 msgid "When all the desired information has been entered in the :guilabel:`Mark Lost` pop-up window, click :guilabel:`Mark as Lost`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:206 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:210 msgid "Upon clicking :guilabel:`Mark as Lost`, the pop-up window disappears, and Odoo returns to the opportunity form, where a new red :guilabel:`Lost` banner is now present in the upper-right corner of the opportunity." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:210 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:214 msgid "Once an opportunity is marked as *lost*, it is no longer considered active, and it is removed from the pipeline." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:213 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:217 msgid "In order to view a *lost* opportunity from the pipeline, click the :guilabel:`down arrow icon` to the right of the search bar, and select either :guilabel:`Lost` or :guilabel:`Archived` from the drop-down menu that appears." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:218 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:222 msgid "While opportunities that have been marked as *lost* are considered *Archived*, be advised that, in order for an opportunity to be included as *lost* in reporting, it **must** be specifically marked as *lost*, not *Archived*." msgstr "" @@ -3510,6 +3516,230 @@ msgstr "" msgid "Assign and track leads" msgstr "" +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:3 +msgid "Lead distribution report" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:5 +msgid "A *lead distribution report* can be used to see if active leads are being assigned equitably across sales members. It can also be used to view the distribution of good or :doc:`quality leads `, and see how frequently each salesperson is receiving (and keeping) leads." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:9 +msgid "Lead distribution reports can be run each week to help keep salespeople on track, while providing them with ample good leads. These reports can also be used to see whether sales members are staying productive, if good leads are being lost too often by one salesperson, and what percentage of good leads are being retained overall." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:15 +msgid "Create lead distribution reports" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:17 +msgid "To create a lead distribution report, first navigate to :menuselection:`CRM app --> Reporting --> Pipeline`, which reveals the :guilabel:`Pipeline Analysis` dashboard." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:20 +msgid "Remove all the default filters in the search bar at the top of the page. Doing so displays data related to *all* leads." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:23 +msgid ":ref:`Custom filters ` can now be added by clicking the :icon:`fa-caret-down` :guilabel:`(down caret)` icon, to the right of the search bar, to reveal a drop-down menu of search and filter options." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:27 +msgid "Three columns are displayed: :ref:`Filters `, :ref:`Group By `, and :ref:`Favorites `. To begin, navigate to the bottom of the :guilabel:`Filters` column, and click :guilabel:`Add Custom Filter`. This opens an :guilabel:`Add Custom Filter` pop-up window, where the essential filters can be added one at a time." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:35 +msgid "Essential filters" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:37 +msgid "The following filter conditions are used to create a basic lead distribution report. Together they gather all leads created within a certain timespan that have an associated contact method and have been assigned to a sales team." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:42 +msgid "Lead creation date" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:44 +msgid "Click the first field, under :guilabel:`Match any of the following rules:`, that has the value :guilabel:`Country` in it. In the popover that appears, type `Created on` in the search bar, or scroll to search through the list to locate and select it." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:48 +msgid "Then, in the second field of that row, select :guilabel:`>=` from the drop-down menu. This operator **only** includes values greater than (or equal to) the value in the third, rightmost field." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:51 +msgid "The third field on the :guilabel:`Add Custom Filter` pop-up window should contain the earliest date leads are selected from." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:54 +msgid "For example, setting `01/01/2024 00:00:00` only includes leads created from, and including, the first day of 2024." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:-1 +msgid "Add a Created On rule for the start of the year onward." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:64 +msgid "Sales team" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:66 +msgid "Click :guilabel:`New rule` to add another row to the form, and choose :guilabel:`Sales Team` for this rule's parameter. Then, click the second field of the new rule, and select :guilabel:`contains` from the drop-down menu. Selecting this operator filters for any records that contain the words in the third, rightmost field." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:72 +msgid "For certain pre-determined, limited choices like a sales team, the :guilabel:`is in` operator helps make for an easier and more accurate selection, via a drop-down menu in the third field, instead of risking a typo or incorrect value in the text box field that accompanies the :guilabel:`contains` operator." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:77 +msgid "In this third field, enter the name of the desired sales team(s) that are to be included in the report. It is important for all :guilabel:`contains` argument values to be specific enough and spelled correctly as they exist in Odoo, otherwise this risks returning multiple (or zero) values." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:-1 +msgid "Use Sales Team to filter the location the lead is associated with." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:86 +msgid "By adding more than one rule to the form, a new option emerges at the top of the pop-up window above all the filters, to specify whether :guilabel:`any` :icon:`fa-caret-down` or :guilabel:`all` :icon:`fa-caret-down` of the conditions should match. This distinction is important to set correctly, as it impacts the driving logic of how the filters return data." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:91 +msgid "Click the default :guilabel:`any` :icon:`fa-caret-down` menu item and be sure the :guilabel:`all` :icon:`fa-caret-down` option is chosen instead. This setting will **only** show records that match *all* the rules contained inside the form." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:98 +msgid "Contact method" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:101 +msgid "The instruction below is not necessary, however, it's highly recommended to add a set contact value to the report's search criteria. A lot of spam, duplicate, or low quality leads can easily be screened out of the report simply by adding either a set :guilabel:`Phone` or :guilabel:`Email` rule." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:106 +msgid "Add another :guilabel:`New rule` to the form and set the first field to the first field to :guilabel:`Phone`. Then, select :guilabel:`is set` from the drop-down menu in the second field. Selecting this operator **only** filters for records that have a phone number associated with the lead." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:111 +msgid "Alternatively (or in addition to the above rule), click :guilabel:`New rule` and set the first field to :guilabel:`Email`. Then, select :guilabel:`is set` from the drop-down menu in the second field." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:114 +msgid "These rules add only leads with an associated contact method to the report." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:119 +msgid "Active status" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:121 +msgid "Click the :icon:`fa-sitemap` :guilabel:`(Add branch)` icon to the right of the `Phone is set` line, to add a new rule that branches from the rules above." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:124 +msgid "Two horizontal sets of fields appear below a line showing :guilabel:`any` :icon:`fa-caret-down` :guilabel:`of:` option. This setting filters for records that match **any** of the rules contained inside. This uses the same logic as an OR (`|`) logical operator." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:128 +msgid "Set the first field to :guilabel:`Active`. Then, select :guilabel:`is set` in the next field." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:130 +msgid "Next, click the :icon:`fa-plus` :guilabel:`(Add New Rule)` button next to :guilabel:`Active is set` to create a new line of fields beneath it." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:133 +msgid "Set the first field to :guilabel:`Active`. Then, select :guilabel:`is not set` in the next field." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:-1 +msgid "Use Active to include active status in the report." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:139 +msgid "This rule adds the activity status of the lead to the report." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:142 +msgid "Active status is an important filter to include when creating a lead distribution report because it includes **all** leads regardless of won/lost or active/inactive status in the report. This provides a comprehensive view of all the leads assigned to each sales member." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:147 +msgid "Group by" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:149 +msgid "Once all filters are set, click the :guilabel:`Add` button to add these filters to the search bar. To have the report grouped appropriately, click the :icon:`fa-caret-down` :guilabel:`(down caret)` icon, to the right of the search bar, and click :guilabel:`Salesperson` in the :guilabel:`Group By` section. All results are now grouped by the salesperson assigned to each lead." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:154 +msgid "Once the rules for the filter are set, click the purple :guilabel:`Confirm` button at the bottom of the pop-up menu to save the custom filter and close the pop-up menu." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:157 +msgid "The :guilabel:`Pipeline Analysis` dashboard is now displayed again with each filter rule in the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:160 +msgid "Click the :icon:`fa-area-chart` :guilabel:`(Graph)` icon, to the right of the search bar, to view the report as a bar chart. Alternatively, click the :icon:`oi-view-list` :guilabel:`(List)` icon to view leads in a grouped list." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:165 +msgid "To save the filter so it can easily be re-applied, click the :guilabel:`Save current search` button in the :guilabel:`Favorites` section of the search bar drop-down menu." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:168 +msgid "Next, type a name for the filter in the text box below. Check the :guilabel:`Shared` checkbox to have the filter shared with any user with access to the pipeline. Finally, click the purple :guilabel:`Save` button below to save the filter." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:172 +msgid "The filter will now appear with the name it was given under the :guilabel:`Favorites` section of the drop-down menu and can be re-applied by clicking on it." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:176 +msgid "Filter for quality leads" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:178 +msgid "The following additional conditions are provided as an example of a *good*, but *not comprehensive*, set of rules for finding quality leads. These filters should be applied on top of the :ref:`crm/track_leads/essential-filters` in the order specified to achieve a heavily-detailed filter." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:183 +msgid "**Referred-by:** Filter for referrals, such as by appointment or sales member." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:184 +msgid "**Source:** Filter for specific source UTMs, such as Facebook or LinkedIn." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:185 +msgid "**Notes:** Filter for internal notes." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:186 +msgid "**Tags:** Filter for categorical tags." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:187 +msgid "**Email:** Filter for specific email domains, such as gmail.com or yahoo.com." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:188 +msgid "**Salesperson:** Filter for leads associated with certain sales members." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:190 +msgid "These conditions can be added, removed, or modified to best fit the desired information in the report." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:194 +msgid ":ref:`quality_leads_report/add-quality-rules`" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_distribution_report.rst:195 +msgid ":doc:`../../../essentials/search`" +msgstr "" + #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:3 msgid "Assign leads with predictive lead scoring" msgstr "" @@ -5651,26 +5881,30 @@ msgid ":doc:`Ingenico configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:25 -msgid ":doc:`SIX configuration `" +msgid ":doc:`Mercado Pago configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:26 -msgid ":doc:`Stripe configuration `" +msgid ":doc:`SIX configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:27 -msgid ":doc:`Vantiv configuration `" +msgid ":doc:`Stripe configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:28 -msgid ":doc:`Viva Wallet configuration `" +msgid ":doc:`Vantiv configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:29 +msgid ":doc:`Viva Wallet configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:30 msgid ":doc:`Worldline configuration `" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:31 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:32 msgid "Once the terminal is configured, you can :doc:`create the corresponding payment method and add it to the POS <../payment_methods>`." msgstr "" @@ -5819,6 +6053,7 @@ msgid "Ingenico" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:5 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:5 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:5 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:5 msgid "Connecting a payment terminal allows you to offer a fluid payment flow to your customers and ease the work of your cashiers." @@ -5901,6 +6136,158 @@ msgstr "" msgid "Once your payment is processed, on the payment record, you’ll find the type of card that has been used and the transaction ID." msgstr "" +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:3 +msgid "Mercado Pago" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:9 +msgid "Only **Point Smart** payment terminals in **Argentina**, **Brazil**, and **Mexico** are supported. They can be purchased on `Mercado Pago's website `_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:14 +msgid "`Mercado Pago online payments `_" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:22 +msgid "Create a `Mercado Pago account `_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:23 +msgid "Associate your Point Smart terminal with a :guilabel:`store` and a :guilabel:`cash drawer` by following `Mercado Pago's documentation `_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:27 +msgid "All purchased terminals are automatically displayed on your Mercado dashboard." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:29 +msgid "Set your Point Smart terminal to the :guilabel:`Point of Sale` operation mode." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:32 +msgid "Odoo does not support the :guilabel:`Standalone` operation mode." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:34 +msgid ":ref:`Create a Point Smart application `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:35 +msgid ":ref:`Generate your credentials `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:36 +msgid ":ref:`Create and configure the related payment method `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:41 +msgid "Point Smart application" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:43 +msgid "Create a new application from Mercado Pago's `developer panel `_ by following `Mercado Pago's applications documentation `_, making sure you select :guilabel:`In person Payments`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:51 +msgid "Credentials" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:53 +msgid "Once the Point Smart application is created, three credentials are required:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:55 +msgid "An access token that Odoo uses to call Mercado Pago." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:56 +msgid "A webhook secret key that Odoo uses to authenticate notifications sent by Mercado Pago." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:57 +msgid "The **terminal serial number** at the back of your Point Smart terminal." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:59 +msgid "Retrieve the access token and webhook secret key by following `Mercado Pago's credentials documentation `_. Then, copy and paste them into Odoo when creating the payment method." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:64 +msgid "For the webhooks configuration, add the URL of your Odoo database (e.g., `https://mycompany.odoo.com`) followed by `/pos_mercado_pago/notification` (e.g., `https://mycompany.odoo.com/pos_mercado_pago/notification`)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:0 +msgid "Webhooks configuration on Mercado Pago." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:74 +msgid "Payment method" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:76 +msgid ":doc:`Activate the POS Mercado Pago module <../../../../general/apps_modules>` to enable the payment terminal." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:78 +msgid ":doc:`Create the related payment method <../../payment_methods>` by going to :menuselection:`Point of Sale --> Configuration --> Payment Methods`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:80 +msgid "Set the journal type as :guilabel:`Bank`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:81 +msgid "Select :guilabel:`Mercado Pago` in the :guilabel:`Use a Payment Terminal` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:82 +msgid "Fill in the mandatory fields with the :ref:`previously generated credentials `:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:85 +msgid "Fill in the :guilabel:`Production user token` field using the access token." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:86 +msgid "Fill in the :guilabel:`Production secret key` field using the webhook secret key." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:87 +msgid "Fill in the :guilabel:`Terminal S/N` field using the terminal serial number. You can find it at the back of your terminal." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:89 +msgid "Click the :guilabel:`Force PDV` button to activate the Point of Sale mode." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:-1 +msgid "Form to create a new payment method." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:94 +msgid "Select the payment method by going to the :ref:`POS' settings ` and adding it to the payment method under the :guilabel:`Payment Methods` field of the :guilabel:`Payment` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:101 +msgid "Paying with a payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:103 +msgid "When processing a payment, select your Mercado Pago payment method, check the amount, and click :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment Successful`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:108 +msgid "In case of connection issues between Odoo and the payment terminal, force the payment by clicking :guilabel:`Force Done`, which allows you to validate the order. This option is only available after receiving an error message informing you that the connection failed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:111 +msgid "To cancel the payment request, click :guilabel:`Cancel`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:114 +msgid "Any action made on the terminal should trigger a notification on the POS interface. Ensure the :ref:`webhook secret key ` is correctly configured if you are not notified." +msgstr "" + #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:3 msgid "SIX" msgstr "" @@ -6526,7 +6913,7 @@ msgid "And then scan the discount tag. The discount will be applied and you can msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:3 -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:321 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:333 msgid "Discounts" msgstr "" @@ -6964,7 +7351,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:3 #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:38 -#: ../../content/applications/sales/subscriptions/products.rst:105 +#: ../../content/applications/sales/subscriptions/products.rst:116 msgid "Pricelists" msgstr "" @@ -6997,7 +7384,8 @@ msgid "Go to :menuselection:`Point of Sale --> Products --> Pricelists` and clic msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:42 -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:243 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:98 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:255 msgid "Multiple prices per product" msgstr "" @@ -7030,7 +7418,8 @@ msgid "Setup form of a multiple prices pricelist" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:63 -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:359 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:126 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:414 msgid "Advanced price rules" msgstr "" @@ -7954,7 +8343,7 @@ msgid "Define the :guilabel:`Shipping Policy`; select :guilabel:`As soon as poss msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:28 -msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method`" +msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration`" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:29 @@ -11761,114 +12150,134 @@ msgid "Discount and loyalty program template cards." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:35 -msgid "Templates only appear when no programs have been created, and they disappear once the first program is created." +msgid "Templates **only** appear when no programs have been created, and they disappear once the first program is created." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:38 msgid "Creating or editing a program opens the program form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:40 -msgid "The program form contains the following options:" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:42 -msgid ":guilabel:`Program Name`: Enter the name of the program. The program name is *not* visible to the customer." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:44 -msgid ":guilabel:`Program Type`: Select the desired :ref:`program type `." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:46 -msgid ":guilabel:`Currency`: Select the currency used for the program." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:47 -msgid ":guilabel:`Points Unit`: Enter the name of the points used for the :guilabel:`Loyalty Cards` program (e.g. `Loyalty Points`). The points unit name *is* visible to the customer. This field is only available when the :guilabel:`Program Type` is set to :guilabel:`Loyalty Cards`." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:50 -msgid ":guilabel:`Validity`: Select the date until which the program is valid. Leave this field blank for no end date, meaning the program is always valid and does not expire." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:52 -msgid ":guilabel:`Limit Usage`: Check this box and enter a number to limit the number of times the program can be used during the :guilabel:`Validity` period." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:54 -msgid ":guilabel:`Company`: In the case of multiple companies, choose the company for which the program is available." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:56 -msgid ":guilabel:`Available On`: Select the app(s) on which the program is available." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:57 -msgid ":guilabel:`Website`: Select the website(s) on which the program is available. Leave this field blank to make it available on all websites." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:59 -msgid ":guilabel:`Point of Sale`: Select the point(s) of sale at which the program is available. Leave this field blank to make it available at all :abbr:`PoS (Point of Sale)`." -msgstr "" - #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:-1 msgid "Program options on the loyalty program form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:67 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:44 +msgid "The program form contains the following fields:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:46 +msgid ":guilabel:`Program Name`: Enter the name of the program in this field. The program name is **not** visible to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:48 +msgid ":guilabel:`Program Type`: Select the desired :ref:`program type ` from the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:50 +msgid ":guilabel:`Currency`: Select the currency used for the program." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:51 +msgid ":guilabel:`Pricelist`: If desired, select a pricelist from the drop-down menu to have this loyalty program applied to a specific pricelist (and customers attached to the pricelist). More than one pricelist can be selected in this field. When a single loyalty program is linked to several pricelists, it makes it viable for different customer segments to have different pricelists, but the *same* loyalty programs. If this field is left blank, the program applies to everyone, regardless of pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:57 +msgid ":guilabel:`Points Unit`: Enter the name of the points used for the :guilabel:`Loyalty Cards` program (e.g. `Loyalty Points`). The points unit name *is* visible to the customer. This field is **only** available when the :guilabel:`Program Type` is set to :guilabel:`Loyalty Cards`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:60 +msgid ":guilabel:`Start Date`: Select the date on which the program becomes valid. Leave this field blank if the program should always be valid and not expire." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:62 +msgid ":guilabel:`End Date`: Select the date on which the program stops being valid. Leave this field blank if the program should always be valid and not expire." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:64 +msgid ":guilabel:`Limit Usage`: If desired, tick this checkbox, and enter a number of :guilabel:`usages` to limit the number of times the program can be used during the validity period." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:66 +msgid ":guilabel:`Company`: If working in a multi-company database, choose the one company for which the program is available. If left blank, the program is available to all companies in the database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:68 +msgid ":guilabel:`Available On`: Select the apps on which the program is available." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:69 +msgid ":guilabel:`Website`: Select a website on which the program is available. Leave this field blank to make it available on all websites." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:71 +msgid ":guilabel:`Point of Sale`: Select the point(s) of sale at which the program is available. Leave this field blank to make it available at all :abbr:`PoS (Point of Sale)`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:75 msgid "The options available on the program form vary depending on the :ref:`Program Type ` selected." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:70 -msgid "All of the existing cards, codes, coupons, etc. that have been generated for the program are accessible through the smart button located in the upper-right corner of the form." +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:78 +msgid "All of the existing cards, codes, coupons, etc. that have been generated for the program are accessible through the smart button located at the top of the form." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:-1 msgid "Program items smart button on the loyalty program form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:80 -msgid "Program types" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:82 -msgid "The different :guilabel:`Program Types` available on the program form are:" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:84 -msgid ":guilabel:`Coupons`: Generate and share single-use coupon codes that grant immediate access to rewards." -msgstr "" - #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:86 -msgid ":guilabel:`Next Order Coupons`: Generate and share single-use coupon codes that grant access to rewards on the customer's next order." +msgid "In Odoo 17 (and later), when a loyalty card or coupon is associated with a contact in the database, a :guilabel:`Loyalty Cards` smart button conditionally appears on the contact form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:88 -msgid ":guilabel:`Loyalty Cards`: When making purchases, the customer accumulates points to exchange for rewards on current and/or future orders." +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:-1 +msgid "The Loyalty Card smart button as it appears on a contact form in Odoo 17." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:90 -msgid ":guilabel:`Promotions`: Set conditional rules for ordering products, which, when fulfilled, grant access to rewards for the customer." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:92 -msgid ":guilabel:`Discount Code`: Set codes which, when entered upon checkout, grant discounts to the customer." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:94 -msgid ":guilabel:`Buy X Get Y`: For every X item bought, the customer is granted 1 credit. After accumulating a specified amount of credits, the customer can trade them in to receive Y item." +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:93 +msgid "This smart button **only** appears if a loyalty card or coupon is associated with the contact." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:98 -msgid "Conditional rules" +msgid "Program types" msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:100 +msgid "The different :guilabel:`Program Types` available on the program form are:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:102 +msgid ":guilabel:`Coupons`: Generate and share single-use coupon codes that grant immediate access to rewards." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:104 +msgid ":guilabel:`Loyalty Cards`: When making purchases, the customer accumulates points to exchange for rewards on current and/or future orders." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:106 +msgid ":guilabel:`Promotions`: Set conditional rules for ordering products, which, when fulfilled, grant access to rewards for the customer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:108 +msgid ":guilabel:`Discount Code`: Set codes which, when entered upon checkout, grant discounts to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:110 +msgid ":guilabel:`Buy X Get Y`: for every (X) item bought, the customer is granted 1 credit. After accumulating a specified amount of credits, the customer can trade them in to receive (Y) item." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:112 +msgid ":guilabel:`Next Order Coupons`: Generate and share single-use coupon codes that grant access to rewards on the customer's next order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:116 +msgid "Conditional rules" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:118 msgid "Next, configure the :guilabel:`Conditional rules` that determine when the program applies to a customer's order." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:103 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:121 msgid "In the :guilabel:`Rules & Rewards` tab, click :guilabel:`Add` next to :guilabel:`Conditional rules` to add *conditions* to the program. This reveals a :guilabel:`Create Conditional rules` pop-up window." msgstr "" @@ -11876,39 +12285,39 @@ msgstr "" msgid "Rules & Rewards tab of the loyalty program form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:112 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:130 msgid "The options for :guilabel:`Conditional rules` vary depending on the selected :ref:`Program Type `." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:115 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:133 msgid "The following options are available for configuring conditional rules:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:117 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:135 msgid ":guilabel:`Discount Code`: Enter a custom code to be used for the :guilabel:`Discount Code` program, or use the default one generated by Odoo. This field is only available when the :guilabel:`Program Type` is set to :guilabel:`Discount Code`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:120 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:138 msgid ":guilabel:`Minimum Quantity`: Enter the minimum number of products that must be purchased in order to access the reward. Set the minimum quantity to at least `1` to ensure that the customer must make a purchase in order to access the reward." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:123 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:141 msgid ":guilabel:`Minimum Purchase`: Enter the minimum amount (in currency), with :guilabel:`tax Included` or :guilabel:`tax Excluded`, that must be spent in order to access the reward. If both a minimum quantity *and* minimum purchase amount are entered, then the customer's order must meet both conditions." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:127 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:145 msgid ":guilabel:`Products`: Select the specific product(s) for which the program applies. Leave this field blank to apply it to all products." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:129 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:147 msgid ":guilabel:`Categories`: Select the category of products for which the program applies. Choose :guilabel:`All` to apply it to all product categories." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:131 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:149 msgid ":guilabel:`Product Tag:` Select a tag to apply the program to products with that specific tag." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:132 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:150 msgid ":guilabel:`Grant`: Enter the number of points the customer earns :guilabel:`per order`, :guilabel:`per currency spent`, or :guilabel:`per unit paid` (for the :guilabel:`Loyalty Cards` and :guilabel:`Buy X Get Y` programs)." msgstr "" @@ -11916,68 +12325,68 @@ msgstr "" msgid "Conditional rules configuration window for a discount or loyalty program." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:140 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:158 msgid "Click :guilabel:`Save & Close` to save the rule and close the pop-up window, or click :guilabel:`Save & New` to save the rule and immediately create a new one." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:144 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:162 msgid "Rewards" msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:146 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:164 msgid "In the :guilabel:`Rules & Rewards` tab of the program form, click :guilabel:`Add` next to :guilabel:`Rewards` to add *rewards* to the program. This reveals a :guilabel:`Create Rewards` pop-up window." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:151 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:169 msgid "The options for :guilabel:`Rewards` vary depending on the selected :ref:`Program Type `." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:154 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:172 msgid "The following options are available for configuring rewards:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:156 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:174 msgid ":guilabel:`Reward Type`: Select the reward type among :guilabel:`Free Product`, :guilabel:`Discount`, and :guilabel:`Free Shipping`. The other options for reward configuration depend on the :guilabel:`Reward Type` selected." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:160 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:178 msgid ":guilabel:`Free Product`:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:162 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:180 msgid ":guilabel:`Quantity Rewarded`: Select the number of free products rewarded to the customer." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:163 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:181 msgid ":guilabel:`Product`: Select the product given for free as a reward. Only one product can be selected." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:165 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:183 msgid ":guilabel:`Product Tag`: Select a tag to further specify the free product eligible for the reward." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:168 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:186 msgid ":guilabel:`Discount`:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:170 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:188 msgid ":guilabel:`Discount`: Enter the discounted amount in either :guilabel:`percentage`, :guilabel:`currency per point`, or :guilabel:`currency per order`. Then, select whether the discount applies to the entire :guilabel:`Order`, only the :guilabel:`Cheapest Product` on the order, or only :guilabel:`Specific Products`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:174 -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:179 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:192 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:197 msgid ":guilabel:`Max Discount`: Enter the maximum amount (in currency) that this reward may grant as a discount. Leave this field at `0` for no limit." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:177 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:195 msgid ":guilabel:`Free Shipping`:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:182 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:200 msgid ":guilabel:`In exchange of`: Enter the number of points required to exchange for the reward (for the :guilabel:`Loyalty Cards` and :guilabel:`Buy X Get Y` programs)." msgstr "" -#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:184 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:202 msgid ":guilabel:`Description on order`: Enter the description of the reward, which is displayed to the customer upon checkout." msgstr "" @@ -12304,7 +12713,7 @@ msgid "After activating and saving the :guilabel:`Pricelists` feature, the :guil msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:45 -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:375 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:430 msgid "Either option reveals the :guilabel:`Pricelists` page, in which pricelists can be created and/or modified at any time." msgstr "" @@ -12324,7 +12733,15 @@ msgstr "" msgid "The :guilabel:`Public Pricelist` is the default pricelist used with Odoo *Sales* and *eCommerce*. This pricelist is applied by default, if there are no matching criteria." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:64 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:65 +msgid "In Odoo 17 (and above), it is no longer required to have a pricelist entered in the :guilabel:`Pricelist` field on a quotation form in order to confirm it (i.e. turn it into a sales order)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:69 +msgid "It should also be noted that, in Odoo 17 (and above), a chatter section can be found on pricelist forms, which enhances the ability to communicate about them." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:72 msgid "From the :guilabel:`Pricelists` page, either select the desired pricelist to edit, or click :guilabel:`New` to create a new pricelist, which reveals a blank pricelist form that can be configured in a number of different ways." msgstr "" @@ -12332,111 +12749,123 @@ msgstr "" msgid "How the pricelist detail form looks in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:72 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:80 msgid "When creating a new pricelist, start by adding a name for the pricelist at the top of the form, in the blank field. Next, select which :guilabel:`Currency` should be used." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:75 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:83 msgid "Then, if working in a multi-company environment, select which company this pricelist should apply to in the :guilabel:`Company` field. If this field is left blank, the pricelist is automatically applied to all companies in the database." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:80 -msgid "Price rules tab" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:82 -msgid "The :guilabel:`Price Rules` tab functionality on a pricelist form varies depending on the :guilabel:`Pricelists` setting chosen: either :guilabel:`Multiple prices per product` or :guilabel:`Advanced price rules (discounts, formulas)`." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:86 -msgid "However, the :guilabel:`Time-based rules` tab and :guilabel:`Configuration` tab are always the same, regardless of the chosen :guilabel:`Pricelists` setting." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:88 +msgid "Price Rules tab" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:90 -msgid "Price rules tab (multiple prices per product)" +msgid "The :guilabel:`Price Rules` tab functionality on a pricelist form varies depending on the :guilabel:`Pricelists` setting chosen: either :guilabel:`Multiple prices per product` or :guilabel:`Advanced price rules (discounts, formulas)`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:92 -msgid "With the :guilabel:`Multiple prices per product` setting activated, the :guilabel:`Price Rules` tab on pricelist forms provides the option to add specific products, with a specific price, to a pricelist." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:96 -msgid "To add a specific product and price to a pricelist form, click the :guilabel:`Price Rules` tab, then click :guilabel:`Add a line` in the :guilabel:`Products` column. Then, select the desired product for which a specific price should be applied." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:94 +msgid "However, the :guilabel:`Time-based rules` tab and :guilabel:`Configuration` tab are always the same, regardless of the chosen :guilabel:`Pricelists` setting." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:100 -msgid "Next, if necessary, select a product variant under the :guilabel:`Variants` column (e.g. a specific product size, color, etc.). If no variants are selected, then this price will apply to all variants of the product." +msgid "With the :guilabel:`Multiple prices per product` setting activated, the :guilabel:`Price Rules` tab on pricelist forms provides the option to add specific products, with a specific price, to a pricelist." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:104 +msgid "To add a specific product and price to a pricelist form, click the :guilabel:`Price Rules` tab, then click :guilabel:`Add a line` in the :guilabel:`Products` column. Then, select the desired product for which a specific price should be applied." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:108 +msgid "Next, if necessary, select a product variant under the :guilabel:`Variants` column (e.g. a specific product size, color, etc.). If no variants are selected, then this price will apply to all variants of the product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:112 msgid "If a minimum amount of the product must be purchased in order to apply the specific price, enter the amount under the :guilabel:`Min. Quantity` column." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:107 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:115 msgid "To configure the price of the product for this specific pricelist, enter the desired amount under the :guilabel:`Price` column. Then, there is the option to add a :guilabel:`Start Date` and :guilabel:`End Date` to the configured product price, if desired." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:111 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:119 msgid "To add another product line, click :guilabel:`Add a line` again, and repeat the process. There is no limit to how many products can be added in the :guilabel:`Price Rules` tab of a pricelist form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:114 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:122 msgid "For more information, check out the following section: :ref:`Multiple prices per product `." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:118 -msgid "Price rules tab (advanced price rules)" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:120 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:128 msgid "With the :guilabel:`Advanced price rules (discounts, formulas)` setting activated, the :guilabel:`Price Rules` tab on pricelist forms provides the option to configure detailed price rules based on formulas." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:124 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:132 msgid "Check out the :ref:`Advanced price rules (discounts, formulas) ` section for detailed steps on how to add advanced price rules to a pricelist." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:128 -msgid "Time-based rules tab" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:130 -msgid "Time-based rules are used specifically with :doc:`subscription products `. Be sure to check out the Odoo *Subscriptions* :doc:`documentation `." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:134 -msgid "Under the :guilabel:`Time-based rules` tab, the same functionality of the :guilabel:`Price Rules` tab is present, with the only difference being that a repeating time period can be applied in the :guilabel:`Period` column." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:136 +msgid "Recurring Prices tab" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:138 -msgid "After a :guilabel:`Product` and potential :guilabel:`Variant` are selected in the :guilabel:`Time-based rules` tab, select the blank field in the :guilabel:`Period` column to reveal a drop-down menu of pre-designated recurrence periods (e.g. `Monthly`, `Quarterly`, `Weekly`, etc.)." +msgid "Recurring prices are specifically used with :doc:`subscription products <../../../subscriptions/products>`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:142 -msgid "New recurrence periods can also be directly created from this column, by typing in the new name for the :guilabel:`Period` and then selecting :guilabel:`Create` to create the time period, which can be edited later. Or, select :guilabel:`Create and edit...` to reveal a pop-up form, in which the new recurrence period can be directly configured." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:141 +msgid "Under the :guilabel:`Recurring Prices` tab, the same functionality of the :guilabel:`Price Rules` tab is present. The only difference being that a recurring time period can be applied in the :guilabel:`Recurring Plan` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:145 +msgid "Once :guilabel:`Products` and/or :guilabel:`Product Variants` are selected, click :guilabel:`Add a price rule`, and select the blank field in the :guilabel:`Recurring Plan` column to reveal a drop-down menu of pre-designated recurrence periods (e.g. `Monthly`, `Quarterly`, `Weekly`, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:149 +msgid "New recurrence periods can also be created from this column. To do so, type in the name for the new :guilabel:`Recurring Plan`, then select :guilabel:`Create` from the resulting drop-down menu to create the time period, which can be edited later." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:153 +msgid "Or, select :guilabel:`Create and edit...` to reveal a :guilabel:`Create Recurring Plan` pop-up form. From this pop-up form, the new recurrence period can be configured, with specific :guilabel:`Details`, :guilabel:`Self-Service`, and :guilabel:`Pricing` options. When the configurations are complete, click the :guilabel:`Save & Close` button." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 msgid "Custom time period pop-up form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:151 -msgid "From this :guilabel:`Create Period` pop-up form, add a :guilabel:`Name`, :guilabel:`Duration`, then a :guilabel:`Unit` (e.g. `Days`, `Weeks`, etc.). When finished, click :guilabel:`Save and Close`." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:162 +msgid "Lastly, add the desired price for this recurring price rule in the :guilabel:`Recurring Price` column." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:154 -msgid "Lastly, add the desired price for this time-based rule in the :guilabel:`Price` column." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:166 +msgid ":doc:`../../../subscriptions`" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:157 -msgid ":doc:`/applications/sales/subscriptions`" +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:169 +msgid "Rental rules tab" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:160 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:171 +msgid "Under the :guilabel:`Rental rules` tab, specific price rules can be configured for various rental products, using the same methodology as the :guilabel:`Price Rules` and :guilabel:`Recurring Prices` tabs." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:175 +msgid "To add a rental rule, click :guilabel:`Add a line`, and select a desired product in the :guilabel:`Products` column. Then, select any specific :guilabel:`Variants`, if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:178 +msgid "Next, designate a :guilabel:`Period` of time for the rental rule (e.g. `Daily`, `Hourly`, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:180 +msgid "Lastly, configure a :guilabel:`Price` for the rental rule in the respective column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:183 msgid "Configuration tab" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:162 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:185 msgid "Under the :guilabel:`Configuration` tab, there are a few options that can further customize the pricelist." msgstr "" @@ -12444,71 +12873,43 @@ msgstr "" msgid "Configuration tab on pricelist detail form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:169 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:192 msgid "From here, under the :guilabel:`Availability` section, in the :guilabel:`Country Groups` field, certain country groups can be added to the pricelist. There is no limit to how many country groups can be added in this field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:174 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:197 msgid "If no country is set for a customer, Odoo takes the first pricelist without any country group." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:176 -msgid "Under the :guilabel:`Website` section, there are a few options that can be configured. In the :guilabel:`Website` field, this pricelist can be applied to a specific website, if working in a multi-website environment. If left blank, the pricelist will be applied to all websites in the database." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:181 -msgid "Click the :guilabel:`Selectable` checkbox to have this pricelist as a selectable option for customers to choose as they shop. If the :guilabel:`Selectable` box is left unchecked, customers **cannot** select this pricelist for themselves as they shop." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:185 -msgid "Lastly, there is the option to add an :guilabel:`E-commerce Promotional Code`. To add a code, type in the desired promo code that, when entered during the checkout process, applies the pricelist to the customer, even if the customer does not fall into the previously-specified criteria." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:190 -msgid "Show discount percentage to customers" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:192 -msgid "With Odoo *Sales*, the option to show the public price *and* the computed discount percentage on the product catalog is available." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:195 -msgid "To do that, navigate to :menuselection:`Sales app --> Configuration --> Settings`, and in the :guilabel:`Pricing` section, click the checkbox next to the :guilabel:`Discounts` feature, and then click :guilabel:`Save` to save all changes." -msgstr "" - #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:199 -msgid "After activating the :guilabel:`Discounts` feature, navigate to the pricelists page, either by clicking the :guilabel:`Pricelists` link from the :guilabel:`Settings` page, or by going to :menuselection:`Sales app --> Products --> Pricelists`." +msgid "Under the :guilabel:`Website` section, there are a few options that can be configured. In the :guilabel:`Website` field, this pricelist can be applied to a specific website, if working in a multi-website environment. If left blank, the pricelist is applied to all websites in the database." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:203 -msgid "On the :guilabel:`Pricelists` page, select the desired pricelist to edit. On the pricelist form, click into the :guilabel:`Configuration` tab. In the :guilabel:`Configuration` tab, at the bottom, a :guilabel:`Discounts` section is now available." +msgid "Tick the :guilabel:`Selectable` checkbox to have this pricelist as a selectable option for customers to choose as they shop. If the :guilabel:`Selectable` box is left unticked, customers **cannot** select this pricelist for themselves." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 -msgid "What the discount options are on the configuration tab of a pricelist in Odoo Sales." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:207 +msgid "Lastly, there is the option to add an :guilabel:`E-commerce Promotional Code`. To add a code, type in the desired promo code that, when entered during the checkout process, applies the pricelist to the customer, even if the customer does not fall into the previously-specified criteria." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:211 -msgid "The options available in this section are:" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:213 -msgid ":guilabel:`Discount included in the price`: shows the customer only the final price with the discount already included." +msgid "Then, in the :guilabel:`Discounts` section, there is a :guilabel:`Discount Policy` field with two options to choose from: :guilabel:`Discount included in the price` or :guilabel:`Show public price & discount to the customer`." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:215 -msgid ":guilabel:`Show public price & discount to the customer`: shows the customer the public price *and* the discount they're earning." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:219 -msgid "Customer pricelist application" +msgid "If :guilabel:`Discount included in the price` is selected, the price shown to the customer already accounts for the discount being applied. However, if :guilabel:`Show public price & discount to the customer` is selected, the customer sees the actual public price *and* how much they are saving with this pricelist discount." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:221 +msgid "Customer pricelist application" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:223 msgid "While the default pricelist applied to any customer is the :guilabel:`Public Pricelist`, Odoo provides the opportunity to directly apply a different pricelist to customers on their contact form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:224 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:226 msgid "To do that, open the desired customer's contact form, either by navigating to :menuselection:`Sales app --> Orders --> Customers` and selecting the customer from the main :guilabel:`Customers` page, or by clicking on the customer's name on a sales order." msgstr "" @@ -12516,7 +12917,7 @@ msgstr "" msgid "Sample customer detail form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:232 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:234 msgid "On the desired customer's contact form, under the :guilabel:`Sales & Purchase` tab, in the :guilabel:`Sales` section, designate what pricelist should be applied to this specific customer from the drop-down menu in the :guilabel:`Pricelist` field." msgstr "" @@ -12524,15 +12925,23 @@ msgstr "" msgid "The pricelist field in a customer detail form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:245 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:243 +msgid "When a customer is added to the database, the default pricelist is automatically applied to them. There is **no way** to have a blank *Pricelist* field on a contact form. Even if that field is left blank, the default pricelist appears when that contact form is opened again." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:247 +msgid "However, when that contact is added to a quotation, and the *Pricelist* field is auto-populated (based on the information from their contact form), that predetermined pricelist can be removed from the *Pricelist* field, and the quotation can still be confirmed, and subsequently, turned into a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:257 msgid "To apply several prices per individual product, select the :guilabel:`Multiple prices per product` option, after enabling the :guilabel:`Pricelists` feature on the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:249 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:261 msgid "Next, apply pricelists to specific products using the product form. Navigate to the :menuselection:`Sales app --> Products --> Products` and select the product for which multiple prices should be applied. Selecting a product from the :guilabel:`Products` page reveals that specific product's product form on a separate page." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:254 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:266 msgid "On the product form, click the :guilabel:`Extra Prices` smart button, located at the top of the form." msgstr "" @@ -12540,7 +12949,7 @@ msgstr "" msgid "How the extra prices smart button appears in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:261 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:273 msgid "Doing so reveals a separate page displaying the :guilabel:`Price Rules` that are specific to that particular product. Here, price rules can be edited or created at any time." msgstr "" @@ -12548,59 +12957,59 @@ msgstr "" msgid "How the extra price rules per product page appears in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:268 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:280 msgid "To create a new price rule for a product from this specific :guilabel:`Price Rules` page, click :guilabel:`New` to add a new, customizable row that has the desired product already populated in the :guilabel:`Applied On` column." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:272 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:284 msgid "Next, select which :guilabel:`Pricelist` this specific product price rule should apply to, via the drop-down menu in the :guilabel:`Pricelist` column." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:276 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:288 msgid "The :guilabel:`Public Pricelist` is the default pricelist used with Odoo *Sales* and *eCommerce*." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:279 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:291 msgid "To create a new pricelist from this page, type in the desired name of the new pricelist in the :guilabel:`Pricelist` column, then select :guilabel:`Create` from the drop-down menu. All pricelists can be modified at any time, by navigating to :menuselection:`Sales app --> Products --> Pricelists`. Pricelists can also be created on that specific :guilabel:`Pricelists` page, as well." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:285 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:297 msgid "After the desired pricelist is added to the row, designate a :guilabel:`Min. Quantity` for the price rule." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:289 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:301 msgid "If the :guilabel:`Min. Quantity` column is set to `2`, the new price in the :guilabel:`Price` column will be applied to orders of 2 or more products. So, in theory, if a single product costs $100, customers can be encouraged to buy more, if the :guilabel:`Price` is set at $85 per product for a :guilabel:`Min. Quantity` of `2` products." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:294 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:306 msgid "Next, enter the desired amount in the :guilabel:`Price` column. Then, if needed, enter a :guilabel:`Start Date` and :guilabel:`End Date` for the product's price rule." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:297 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:309 msgid "And lastly, if working in a multi-company environment, select which company this price rule should be applied to in the :guilabel:`Company` field. Leaving this field blank means the price rule applies for all companies in the database." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:301 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:313 msgid "Click away from the row to activate Odoo's auto-save capability, meaning that newly-created price rule is now ready to be used." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:304 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:316 msgid "Proceed to add as many unique price rules per product as desired. There is no limit to how many price rules can be added per product." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:307 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:319 msgid "With the price rule(s) in place for a specific product, customers who fall into those corresponding pricelists automatically see those new prices applied. The number of price rules applied to a particular product are also displayed in the :guilabel:`Extra Prices` smart button, located on every product form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:313 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:325 msgid "When a price rule/pricelist is added to a product via the :guilabel:`Extra Prices` smart button, it is also reflected on the pricelist itself. Similarly, when a price rule for a specific product is added to a pricelist, it is also reflected on the product form via the :guilabel:`Extra Prices` smart button." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:323 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:335 msgid "The *Discounts* feature allows the ability to set a discount or increase the price on *individual items* in a sales order. This is calculated as a percentage of that product's sales price." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:326 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:338 msgid "To access discounts, navigate to the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click the :guilabel:`Discounts` checkbox, then click :guilabel:`Save`." msgstr "" @@ -12608,15 +13017,15 @@ msgstr "" msgid "Click the checkbox labeled Discounts to activate Discounts." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:334 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:346 msgid "After the setting has been activated, navigate to the desired quotation by going to :menuselection:`Sales app --> Orders --> Quotations` at the top of the page. Once there, click on the desired quote from the list." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:338 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:350 msgid "In the order lines section of the quotation form, a new column heading will appear labeled :guilabel:`Disc.%`. This column is used to set discounts on individual line items. Enter the desired discount for each product line and the new price will automatically be calculated in the quote :guilabel:`Total` at the bottom of the page." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:344 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:356 msgid "A discount can also be added directly to a sales order in the same way. Navigate to :menuselection:`Sales app --> Orders --> Orders`, click on the desired sales order, and add the discount to :guilabel:`Disc.%` as described above." msgstr "" @@ -12624,27 +13033,71 @@ msgstr "" msgid "The Dis.% heading will now appear in Order Lines." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:353 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:365 msgid "Positive values for :guilabel:`Disc.%` will apply a *discount*, while negative values can be used to *increase* the price." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:361 -msgid "The :guilabel:`Advanced price rules (discounts, formulas)` pricelist feature provides the option to set price change rules based on discounts and formulas. These changes can be relative to the product list/catalog price, the product's cost, or another pricelist." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:369 +msgid "Discount button" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:365 -msgid "To use advanced pricing rules, with discounts and formulas, select the :guilabel:`Advanced price rules (discounts, formulas)` option, after enabling the :guilabel:`Pricelists` feature on the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click :guilabel:`Save`." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:371 +msgid "In Odoo 17, with the :ref:`Discounts setting ` enabled, a :guilabel:`Discount` button appears at the bottom of sales orders." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:370 -msgid "After activating and saving that :guilabel:`Pricelists` feature, the :guilabel:`Settings` page reloads and, from here, either select the :guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app --> Products --> Pricelists`." +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:-1 +msgid "The discount button located at the bottom of a sales order form in the Odoo Sales app." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:378 -msgid "From the :guilabel:`Pricelists` page, select a desired pricelist to modify, or create a new pricelist by clicking the :guilabel:`New` button." +msgid "When the :guilabel:`Discount` button on a sales order is clicked, a :guilabel:`Discount` pop-up window appears." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:381 +msgid "On this pop-up window, configure the :guilabel:`Discount` percentage, and select one of the following discount options: :guilabel:`On All Order Lines`, :guilabel:`Global Discount`, or :guilabel:`Fixed Amount`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:385 +msgid ":guilabel:`On All Order Lines`: When selected, Odoo provides the ability to add the specified discount percentage (configured in the :guilabel:`Discount` field of the pop-up window) on all existing order lines of the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:388 +msgid ":guilabel:`Global Discount`: When selected, Odoo adds a discount product to the order, which has the cumulative value equivalent to the specified discount percentage (configured in the :guilabel:`Discount` field of the pop-up window). Any product added (or removed) *after* the discount is added does **not** affect the discount value on the order line." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:394 +msgid "In this example, since the total of the order is $600, and there is a 30% global discount, that specific line is added to the sales order with a -180 value (which is 30% of $600)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:0 +msgid "The sales order with the applied global discount option in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:401 +msgid ":guilabel:`Fixed Amount`: When selected, the percentage designation in the :guilabel:`Discount` field turns to a monetary value (e.g. dollars), wherein a specific amount must be entered. This configured value is added as a discount line on the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:406 +msgid "It is more beneficial to add a :guilabel:`Fixed Amount` discount after **all** desired products have been added to a sales order. If there are changes made to the sales order *after* the discount is added, make sure to change the value on the :guilabel:`Discount` line, or remove the line and add the discount again." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:416 +msgid "The :guilabel:`Advanced price rules (discounts, formulas)` pricelist feature provides the option to set price change rules based on discounts and formulas. These changes can be relative to the product list/catalog price, the product's cost, or another pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:420 +msgid "To use advanced pricing rules, with discounts and formulas, select the :guilabel:`Advanced price rules (discounts, formulas)` option, after enabling the :guilabel:`Pricelists` feature on the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:425 +msgid "After activating and saving that :guilabel:`Pricelists` feature, the :guilabel:`Settings` page reloads and, from here, either select the :guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app --> Products --> Pricelists`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:433 +msgid "From the :guilabel:`Pricelists` page, select a desired pricelist to modify, or create a new pricelist by clicking the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:436 msgid "On the pricelist form, under the :guilabel:`Price Rules` tab, click :guilabel:`Add a line` to add an advanced price rule. Doing so reveals a :guilabel:`Create Pricelist Rules` pop-up form, in which the advanced rule is configured." msgstr "" @@ -12652,35 +13105,35 @@ msgstr "" msgid "How the Create Pricelist Rules pop-up form looks in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:390 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:445 msgid "Price computation" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:392 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:447 msgid "On this form, first choose one of the three :guilabel:`Computation` options:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:394 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:449 msgid ":guilabel:`Fixed Price`: the price computation is based on a fixed price." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:395 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:450 msgid ":guilabel:`Discount`: the price computation is based on a discount." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:396 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:451 msgid ":guilabel:`Formula`: the price computation is based on a formula." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:399 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:454 msgid "Each :guilabel:`Computation` option reveals its own computation-specific fields on the form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:401 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:456 msgid "If :guilabel:`Fixed Price` is selected, enter the desired price in the :guilabel:`Fixed Price` field below. If :guilabel:`Discount` is selected, enter the desired discount percentage in the :guilabel:`Discount` field that appears." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:405 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:460 msgid "If :guilabel:`Formula` is selected, a number of configurable options appear." msgstr "" @@ -12688,15 +13141,15 @@ msgstr "" msgid "The various formula computation options present in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:411 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:466 msgid "To configure the :guilabel:`Formula` computation option, start by selecting an option from the :guilabel:`Based on` field: :guilabel:`Sales Price`, :guilabel:`Cost`, or :guilabel:`Other Pricelist`. This determines what the advanced price rule formula will be based on." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:415 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:470 msgid "Next, in the :guilabel:`Discount` field, determine how much of a discount should be applied. It should be noted that a mark-up can be applied by setting a negative discount in this field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:419 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:474 msgid "To formulate a 100% markup (or 2 times the cost of the product), with a $5 minimum margin, set the :guilabel:`Based on` field to :guilabel:`Cost`, the :guilabel:`Discount` to `-100`, and the :guilabel:`Margins` to `5`. This is often seen in retail situations." msgstr "" @@ -12704,27 +13157,27 @@ msgstr "" msgid "How it looks to formulate a markup cost with 5 dollar minimum margin in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:427 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:482 msgid "Then, in the :guilabel:`Extra Fee` field, specify a fixed amount to add (or subtract) to the amount calculated with the discount. After that, enter a desired figure in the :guilabel:`Rounding Method` field. The rounding method sets the price so that it is a multiple of the value in the field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:432 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:487 msgid "Rounding is applied *after* the discount and *before* the surcharge." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:435 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:490 msgid "To have prices that end in 9.99, set the :guilabel:`Rounding Method` to `10` and the :guilabel:`Extra Fee` to `-0.01`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:438 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:493 msgid "Lastly, specify the minimum amount of margin over the base price in the :guilabel:`Margins` field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:440 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:495 msgid "Once all formula-related configurations are complete, Odoo provides an example of the formula in a blue block to the right of the configurations." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:444 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:499 msgid "To apply 20% discounts, with prices rounded up to 9.99, set the :guilabel:`Based on` field to :guilabel:`Sales Price`, the :guilabel:`Discount` field to `20`, the :guilabel:`Extra Fee` field to `-0.01`, and the :guilabel:`Rounding Method` field to `10`." msgstr "" @@ -12732,55 +13185,55 @@ msgstr "" msgid "Example of a 20% discount with prices rounded to 9.99 in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:453 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:508 msgid "Conditions" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:455 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:510 msgid "At the bottom of the :guilabel:`Create Pricelist Rules` pop-up form is the :guilabel:`Conditions` section." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:458 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:513 msgid "Here, start by selecting one of the options in the :guilabel:`Apply On` field:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:460 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:515 msgid ":guilabel:`All Products`: the advanced pricelist rule will be applied to all products." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:461 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:516 msgid ":guilabel:`Product Category`: the advanced pricelist rule will be applied to a specific category of products." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:463 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:518 msgid ":guilabel:`Product`: the advanced pricelist rule will be applied to a specific product." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:464 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:519 msgid ":guilabel:`Product Variant`: the advanced pricelist rule will be applied to a specific product variant." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:467 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:522 msgid "If any of those options, apart from :guilabel:`All Products`, are selected, a new option-specific field appears, in which the specific :guilabel:`Product Category`, :guilabel:`Product`, or :guilabel:`Product Variant` must be chosen." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:471 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:526 msgid "Then, select a minimum quantity to be applied to the advanced pricelist rule in the :guilabel:`Min. Quantity` field. Lastly, select a range of dates for the pricelist item validation in the :guilabel:`Validity` field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:475 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:530 msgid "Once all configurations are complete, either click :guilabel:`Save & Close` to save the advanced pricelist rule, or click :guilabel:`Save & New` to immediately create another advanced pricelist rule on a fresh form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:480 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:535 msgid "If a price rule is set for a particular product, and another one for its product category, Odoo takes the rule of the product itself." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:484 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:539 msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:485 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:540 msgid ":doc:`/applications/websites/ecommerce/products/price_management`" msgstr "" @@ -13791,6 +14244,459 @@ msgstr "" msgid "Send Quotations" msgstr "" +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:3 +msgid "Create quotations" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:5 +msgid "In Odoo **Sales**, quotations can be created and sent to customers. Once a quotation has been confirmed, it officially turns into a *sales order*, which can then be invoiced and paid for." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:11 +msgid "Quotation settings" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:13 +msgid "To access these setting options, navigate to :menuselection:`Sales app --> Configuration --> Settings`, and scroll to the :guilabel:`Quotations & Orders` section." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:-1 +msgid "The Quotations and Orders section on the Odoo Sales app Settings page." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:20 +msgid ":guilabel:`Quotation Templates`: Enable this option to create quotation templates featuring standard product offers, which are then selectable on quotation forms. When this checkbox is ticked, an additional field, :guilabel:`Default Template`, appears, along with a link to the :guilabel:`Quotation Templates` page." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:24 +msgid ":guilabel:`Online Signature`: Request an online signature to confirm orders." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:25 +msgid ":guilabel:`Online Payment`: Request an online prepayment from customers to confirm orders. Request a full or partial payment (via down payment). When this checkbox is ticked, an additional field, :guilabel:`Prepayment amount (%)`, appears. There is also a link to the :guilabel:`Payment Providers` page." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:29 +msgid ":guilabel:`Default Quotation Validity`: Determine a set amount (in :guilabel:`days`) that quotations can remain valid for." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:31 +msgid ":guilabel:`Default Recurrence`: Select a default period from the drop-down menu to use as a recurrence period for a new quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:33 +msgid ":guilabel:`Sale Warnings`: Get warning messages about orders that include specific products or customers." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:35 +msgid ":guilabel:`PDF Quote builder`: Customize the look of quotations with header pages, product descriptions, footer pages, and more." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:37 +msgid ":guilabel:`Lock Confirmed Sales`: Ensure no further edits can be made to confirmed orders." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:38 +msgid ":guilabel:`Pro-Forma Invoice`: Send pro-forma invoices to customers." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:40 +msgid "To activate any of these settings, tick the checkbox beside the desired option(s). Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:44 +msgid "Quotations dashboard" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:46 +msgid "The *Quotations* dashboard is the page that appears when the :menuselection:`Sales app` is opened." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:48 +msgid "By default, the :guilabel:`Quotations` dashboard displays all quotations in the database related to the current user, as indicated by the default :guilabel:`My Quotations` filter present in the search bar." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:-1 +msgid "The Quotations dashboard present in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:57 +msgid "To view *all* quotations in the database, remove the :guilabel:`My Quotations` filter from the search bar." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:60 +msgid "Quotations on this page appear in a default list view, but can also be viewed in a :icon:`oi-view-kanban` :guilabel:`Kanban` view, :icon:`fa-calendar` :guilabel:`Calendar`, :icon:`oi-view-pivot` :guilabel:`Pivot` table, :icon:`fa-area-chart` :guilabel:`Graph`, or :icon:`fa-clock-o` :guilabel:`Activity` view." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:65 +msgid "To view and/or modify any listed quotation from the :guilabel:`Quotations` dashboard, click on the desired quotation line from the list, and Odoo reveals the specific form for that selected quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:70 +msgid "Create quotation" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:72 +msgid "To create a quotation, open the :menuselection:`Sales app`, and click the :guilabel:`New` button, located in the upper-left corner of the main :guilabel:`Quotations` dashboard." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:76 +msgid "The :guilabel:`New` button is **only** present if the :guilabel:`Quotations` dashboard is in list or Kanban view." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:79 +msgid "Clicking the :guilabel:`New` button reveals a blank quotation form, with various fields and tabs to configure." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:-1 +msgid "A typical quotation form in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:86 +msgid "Begin by entering the customer's name in the :guilabel:`Customer` field at the top of the form. This is a **required** field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:89 +msgid "If the customer's information is already in the database, the :guilabel:`Invoice Address` and :guilabel:`Delivery Address` fields auto-populate with the saved information for those respective fields, based on the data from that customer's contact record (found in the **Contacts** application)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:94 +msgid "If the customer was referred by another customer or contact, enter their name in the :guilabel:`Referrer` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:97 +msgid "If a :guilabel:`Referrer` is selected, a new field, :guilabel:`Commission Plan` appears, in which a commission can be selected from the drop-down menu. This commission is rewarded to the contact selected in the :guilabel:`Referrer` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:101 +msgid "Next, if they have not already been auto-populated with the customer's information, enter the appropriate addresses in the :guilabel:`Invoice Address` and :guilabel:`Delivery Address` fields. Both of these fields are **required**." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:105 +msgid "Then, if desired, choose a :guilabel:`Quotation Template` from the drop-down field to apply to this quotation. It should be noted that some additional fields may appear, depending on the template selected." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:109 +msgid "The default date that appears in the :guilabel:`Expiration` field is based on the number configured in the :ref:`Default Quotation Validity setting ` (in :menuselection:`Sales app --> Configuration --> Settings`)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:114 +msgid "When using a quotation template, the date in the :guilabel:`Expiration` field is based off the :guilabel:`Quotation Validity` figure on the template form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:117 +msgid "If the quotation is for a recurring product or subscription, select the desired :guilabel:`Recurring Plan` from that specific drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:120 +msgid "If desired, select a specific :guilabel:`Pricelist` to be applied to this quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:122 +msgid "Lastly, select any specific :guilabel:`Payment Terms` to be used for this quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:125 +msgid "Order Lines tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:127 +msgid "The first tab on the quotation form is the :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:129 +msgid "In this tab, select products, and quantities of those products, to add them to the quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:131 +msgid "There are two ways to add products to the quotation from this tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:133 +msgid "Click :guilabel:`Add a product`, select the desired item from the :guilabel:`Product` drop-down field, and proceed to adjust the quantity of that selected product, if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:136 +msgid "Or, click :guilabel:`Catalog` to reveal a separate page, showcasing every item (and every potential product variant) in an organized catalog display, with items organizable by :guilabel:`Product Category` and :guilabel:`Attributes`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:-1 +msgid "A product catalog accessible via a quotation in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:144 +msgid "From here, simply locate the desired items, click the :icon:`fa-shopping-cart` :guilabel:`Add` button on the product card, and adjust the quantity, if needed. When complete, click the :guilabel:`Back to Quotation` button in the upper-left corner to return to the quotation, where the newly-selected catalog items can be found in the :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:149 +msgid "If multiple items should be presented in a more organized way on the quotation, click :guilabel:`Add a section`, enter a name for the section, and drag-and-drop that section heading in the desired location amongst the items in the :guilabel:`Order Lines` tab. The section heading appears in bold." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:153 +msgid "If needed, click :guilabel:`Add a note` beneath a certain product line to add a custom note about that specific product. The note appears in italics. Then, if needed, proceed to drag-and-drop the note beneath the desired product line." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:157 +msgid "Beneath the product lines, there are buttons that can be clicked to apply any of the following: :guilabel:`Coupon Code`, :guilabel:`Promotions`, :guilabel:`Discount`, and/or :guilabel:`Add shipping`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:162 +msgid ":doc:`../products_prices/ewallets_giftcards`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:163 +msgid ":doc:`../products_prices/loyalty_discount`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:164 +msgid ":doc:`../products_prices/prices/pricing`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:167 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:160 +msgid "Optional Products tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:169 +msgid "Open the :guilabel:`Optional Products` tab to select related products that can be presented to the customer, which may result in an increased sale." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:172 +msgid "For example, if the customer wants to buy a car, an optional product that could be offered is a *Trailer Hitch*." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:176 +msgid ":doc:`optional_products`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:179 +msgid "Other Info tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:181 +msgid "In the :guilabel:`Other Info` tab, there are various quotation-related configurations separated into four different sections: :guilabel:`Sales`, :guilabel:`Delivery`, :guilabel:`Invoicing`, and :guilabel:`Tracking`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:186 +msgid "Some fields **only** appear if specific settings and options have been configured." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:189 +msgid "Sales section" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:191 +msgid "In the :guilabel:`Sales` section of the :guilabel:`Other Info` tab, there are sales specific fields that can be configured." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:-1 +msgid "The Sales section of the Other Info tab of a quotation form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:198 +msgid ":guilabel:`Salesperson`: Assign a salesperson from the drop-down menu to be associated with this quotation. The user who originally created the quotation is selected in this field, by default." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:200 +msgid ":guilabel:`Sales Team`: Assign a specific sales team to this quotation. If the selected :guilabel:`Salesperson` is a member of a sales team, that team is auto-populated in the field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:202 +msgid ":guilabel:`Company`: Select a company from the drop-down menu this quotation should be associated with. This field only appears when working in a multi-company environment." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:204 +msgid ":guilabel:`Online signature`: Tick this checkbox to request an online signature from the customer to confirm the order. This field only appears if the *Online Signature* setting has been enabled." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:206 +msgid ":guilabel:`Online payment`: Tick this checkbox, and enter a desired percentage in the adjacent field, to request an online payment from the customer (for that designated percentage of the total amount) to confirm the order. This field only appears if the *Online Payment* setting has been enabled." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:210 +msgid ":guilabel:`Customer Reference`: Enter a custom reference ID for this customer. The entered reference ID can contain letters, numbers, or a mix of both." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:212 +msgid ":guilabel:`Tags`: Add specific tags to the quotation for added organization and enhanced searchability in the Odoo **Sales** application. Multiple tags can be added, if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:216 +msgid "Delivery section" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:218 +msgid "In the :guilabel:`Delivery` section of the :guilabel:`Other Info` tab, there are delivery-specific fields that can be configured." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:-1 +msgid "The Delivery section of the Other Info tab of a quotation form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:225 +msgid ":guilabel:`Shipping Weight`: Displays the weight of the items being shipped. This field is not modifiable. Product weight is configured on individual product forms." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:227 +msgid ":guilabel:`Incoterm`: Select an Incoterm (International Commerical Term) to use as predefined commerical terms for international transactions." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:229 +msgid ":guilabel:`Incoterm Location`: If an Incoterm is being used, enter the international location in this field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:231 +msgid ":guilabel:`Shipping Policy`: Select a desired shipping policy from the drop-down menu. If all products are delivered at once, the delivery order is scheduled, based on the greatest product lead time. Otherwise, it is based on the shortest lead time. The available options are: :guilabel:`As soon as possible` or :guilabel:`When all products are ready`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:235 +msgid ":guilabel:`Delivery Date`: Click into the empty field to reveal a calendar popover, from which a customer delivery date can be selected. If no custom date is required, refer to the :guilabel:`Expected` date listed to the right of that field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:240 +msgid "Invoicing section" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:242 +msgid "In the :guilabel:`Invoicing` section of the :guilabel:`Other Info` tab, there are invoicing specific fields that can be configured." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:-1 +msgid "The Invoicing section of the Other Info tab of a quotation form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:249 +msgid ":guilabel:`Fiscal Position`: Select a fiscal position to be used to adapt taxes and accounts for particular customers or sales orders/invoices. The default value comes from the customer. If a selection is made in this field, an :icon:`fa-refresh` :guilabel:`Update Taxes` clickable link and icon appear. When clicked, the taxes for this partiuclar customer and quotation are updated. A confirmation window appears, as well." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:254 +msgid ":guilabel:`Analytic Account`: Select an analytic account to apply to this customer/quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:257 +msgid "Tracking section" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:259 +msgid "In the :guilabel:`Tracking` section of the :guilabel:`Other Info` tab, there are tracking specific fields that can be configured." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:-1 +msgid "The Tracking section of the Other Info tab of a quotation form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:266 +msgid ":guilabel:`Source Document`: Enter the reference of the document that generated the quotation/sales order, if applicable." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:268 +msgid ":guilabel:`Opportunity`: Select the specific opportunity (from the **CRM** app) related to this quotation, if applicable." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:270 +msgid ":guilabel:`Campaign`: Select the marketing campaign related to this quotation, if applicable." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:271 +msgid ":guilabel:`Medium`: Select the method by which this quotation originated (e.g. *Email*), if applicable." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:273 +msgid ":guilabel:`Source`: Select the source of the link used to generate this quotation (e.g. *Facebook*), if applicable." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:277 +msgid ":doc:`../../../websites/website/reporting/link_tracker`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:280 +msgid "Notes tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:282 +msgid "In the :guilabel:`Notes` tab of the quotation form, enter any specific internal notes about the quotation and/or customer, if desired." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:286 +msgid "Sending and confirming quotations" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:288 +msgid "Once all the necessary fields and tabs have been configured, it is time to send the quotation to the customer for confirmation. Upon confirmation, the quotation turns into an official sales order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:291 +msgid "At the top of the form, there is a series of buttons:" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:293 +msgid ":guilabel:`Send by Email`: When clicked, a pop-up window appears with the customer's name and email address in the :guilabel:`Recipients` field, the quotation (and reference ID) in the :guilabel:`Subject` field, and a brief default message in the body of the email, which can be modified, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:298 +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:306 +msgid "Below that, a PDF copy of the quotation is attached. When ready, click :guilabel:`Send` to send the quotation, via email, to the customer, so they can review and confirm it." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:300 +msgid ":guilabel:`Send PRO-FORMA Invoice`: This button **only** appears if the *Pro-Forma Invoice* setting has been enabled. When clicked, a pop-up window appears with the customer's name and email address in the :guilabel:`Recipients` field, the *Proforma* invoice (and reference ID) in the :guilabel:`Subject` field, and a brief default message in the body of the email, which can be modified, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:308 +msgid ":guilabel:`Confirm`: When clicked, the quotation is confirmed, and the status changes to :guilabel:`Sales Order`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:310 +msgid ":guilabel:`Preview`: When clicked, Odoo reveals a preview of the quotation the customer sees when they log into their customer portal. Click the :icon:`fa-arrow-right` :guilabel:`Back to edit mode` link at the top of the preview page, in the blue banner, to return to the quotation form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:313 +msgid ":guilabel:`Cancel`: When clicked, the quotation is canceled." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:316 +msgid "If the *Lock Confirmed Sales* setting is enabled, the sales order becomes :guilabel:`Locked`, and is indicated as such on the sales order form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:319 +msgid "At this point, the quotation has been confirmed, turned into a sales order, and is now ready to be invoiced and paid for." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:322 +msgid "For more information about invoicing, refer to the :doc:`Invoice based on delivered or ordered quantities <../invoicing/invoicing_policy>`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:326 +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:89 +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:77 +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:99 +msgid ":doc:`quote_template`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:327 +msgid ":doc:`deadline`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:328 +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:90 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:282 +msgid ":doc:`get_signature_to_validate`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:329 +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:78 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:283 +msgid ":doc:`get_paid_to_validate`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:330 +msgid ":doc:`pdf_quote_builder`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/create_quotations.rst:331 +msgid ":doc:`../invoicing/proforma`" +msgstr "" + #: ../../content/applications/sales/sales/send_quotations/deadline.rst:3 msgid "Quotation deadlines" msgstr "" @@ -13872,19 +14778,19 @@ msgstr "" msgid "Activate the Customer Addresses setting." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:21 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:23 msgid "Contact form configuration" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:23 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:25 msgid "To add multiple addresses to a contact, go to :menuselection:`Sales app --> Orders --> Customers`, and clear any default filters from the search bar. Then, click on the desired customer to open their contact form." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:28 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:30 msgid "Contact forms can be accessed in the *Contacts* application, as well." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:30 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:32 msgid "From the contact form, click :guilabel:`Edit`, and then select :guilabel:`Add`, which is located under the :guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create Contact` pop-up form, in which additional addresses can be configured." msgstr "" @@ -13892,35 +14798,35 @@ msgstr "" msgid "Add a contact/address to the contact form." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:38 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:40 msgid "On the :guilabel:`Create Contact` pop-up form, start by clicking the default :guilabel:`Other Address` field to reveal a drop-down menu of address-related options." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:41 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:43 msgid "Select any of the following options:" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:43 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:45 msgid ":guilabel:`Contact`: adds another contact to the existing contact form." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:44 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:46 msgid ":guilabel:`Invoice Address`: adds a specific invoice address to the existing contact form." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:45 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:47 msgid ":guilabel:`Delivery Address`: adds a specific delivery address to the existing contact form." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:46 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:48 msgid ":guilabel:`Other Address`: adds an alternate address to the existing contact form." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:47 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:49 msgid ":guilabel:`Private Address`: adds a private address to the existing contact form." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:49 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:51 msgid "Once an option is selected, proceed to enter the corresponding contact information that should be used for the specified address type." msgstr "" @@ -13928,15 +14834,15 @@ msgstr "" msgid "Create a new contact/address on a contact form." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:56 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:58 msgid "Then, click :guilabel:`Save & Close` to save the address and close the :guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save the address and immediately input another one." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:60 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:62 msgid "Address added to quotations" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:62 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:64 msgid "When a customer is added to a quotation, the :guilabel:`Invoice Address` and :guilabel:`Delivery Address` fields autopopulate with the corresponding addresses specified on the customer's contact form." msgstr "" @@ -13944,15 +14850,15 @@ msgstr "" msgid "Invoice and Delivery Addresses autopopulate on a quotation." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:70 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:72 msgid "The :guilabel:`Invoice Address` and :guilabel:`Delivery Address` can also be edited directly from the quotation by clicking the :guilabel:`Edit` button, and then clicking the :guilabel:`➡️ (right arrow)` internal link buttons next to each address line." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:74 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:76 msgid "These addresses can be updated at any time to ensure accurate invoicing and delivery." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:77 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:79 msgid "If any changes are made on a form in Odoo, include *Contacts* forms, remember to click :guilabel:`Save` to save the changes to the database." msgstr "" @@ -14001,6 +14907,7 @@ msgid "The online payment setting on quotation template forms in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:43 +#: ../../content/applications/sales/subscriptions/payment_providers.rst:5 msgid "Payment providers" msgstr "" @@ -14053,17 +14960,6 @@ msgstr "" msgid "Sample of notification that appears in the chatter when an online payment is made." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:89 -#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:77 -#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:99 -msgid ":doc:`quote_template`" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:90 -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:249 -msgid ":doc:`get_signature_to_validate`" -msgstr "" - #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:3 msgid "Online signatures for order confirmations" msgstr "" @@ -14148,11 +15044,6 @@ msgstr "" msgid "Then, when the quotation is paid and confirmed, a delivery order is automatically created (if the Odoo *Inventory* app is installed)." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:78 -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:250 -msgid ":doc:`get_paid_to_validate`" -msgstr "" - #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:3 msgid "Optional products" msgstr "" @@ -14857,10 +15748,6 @@ msgstr "" msgid "To delete any line item from the :guilabel:`Lines` tab (product, section, and/or note), click the :guilabel:`🗑️ (trash can)` icon on the far-right side of the line." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:160 -msgid "Optional Products tab" -msgstr "" - #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:162 msgid "The use of *optional products* is a marketing strategy that involves the cross-selling of products along with a core product. The aim is to offer useful and related products to customers, which may result in an increased sale." msgstr "" @@ -14949,6 +15836,42 @@ msgstr "" msgid "There is also a blue banner at the top of the quotation template design with a link to quickly return :guilabel:`Back to edit mode`. When clicked, Odoo returns to the quotation form in the back-end of the *Sales* application." msgstr "" +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:249 +msgid "Mass cancel quotations/sales orders" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:251 +msgid "Cancel multiple quotations (or sales orders) by navigating to the :menuselection:`Sales app --> Orders --> Quotations` dashboard, landing, by default, in the list view. Then, on the left side of the table, tick the preferred checkboxes for removal." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:256 +msgid "Select all records in the table by selecting the checkbox column header at the top-left of the table; the total number of selected items are displayed at the top of the page." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:259 +msgid "Then, with the desired quotations (or sales orders) selected from the list view on the :guilabel:`Quotations` page, click the :icon:`fa-cog` :guilabel:`Actions` button to reveal a drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:263 +msgid "From this drop-down menu, select :guilabel:`Cancel quotations`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 +msgid "The Cancel quotations option on the Actions drop-down menu in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:270 +msgid "This action can be performed for quotations in *any* stage, even if it is confirmed as a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:273 +msgid "Upon selecting the :guilabel:`Cancel quotations` option, a :guilabel:`Cancel quotations` confirmation pop-up window appears. To complete the cancellation, click the :guilabel:`Cancel quotations` button." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:278 +msgid "An error pop-up message appears when attempting to cancel an order for an ongoing subscription that has an invoice." +msgstr "" + #: ../../content/applications/sales/subscriptions.rst:5 msgid "Subscriptions" msgstr "" @@ -15234,7 +16157,7 @@ msgid "When the :guilabel:`Trigger Now` button is clicked, Odoo will trigger the msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:132 -msgid "Sending a SMS text message in Odoo requires In-App Purchase (IAP) credit or tokens. For more information on :abbr:`IAP (In-App Purchase)`, visit :doc:`../../essentials/in_app_purchase`. For more information on sending SMS messages, visit :doc:`../../marketing/sms_marketing/essentials/sms_essentials`." +msgid "Sending a SMS text message in Odoo requires In-App Purchase (IAP) credit or tokens. For more information on :abbr:`IAP (In-App Purchase)`, visit :doc:`../../essentials/in_app_purchase`. For more information on sending SMS messages, visit :doc:`../../marketing/sms_marketing`." msgstr "" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:137 @@ -15497,6 +16420,150 @@ msgstr "" msgid "Recurrence periods configured as product variants on the eCommerce product page." msgstr "" +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:3 +msgid "Wire transfer" +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:5 +msgid "The *wire transfer* payment method allows for payment instructions to be shared with a customer after purchasing a product. With a subscription, these payment instructions are shared every time the payment is renewed." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:10 +msgid "The wire transfer payment method requires minimal setup, but in most cases, it is inefficient compared to other online payment providers. It is recommended to use another payment provider with subscriptions, due to wire transfers requiring manual confirmation for each payment." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:19 +msgid "To use the wire transfer payment method, first ensure the *Wire Transfer* payment method is enabled." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:21 +msgid "To do so, begin by navigating to the *Payment Providers* page in either the **Accounting**, **Website**, or **Sales** apps." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:24 +msgid "For example, navigate to :menuselection:`Accounting app --> Configuration --> Online Payments: Payment Providers`, then click the :guilabel:`Wire Transfer` card." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:28 +msgid "If the **Accounting** app is not installed, the *Payment Providers* page can also be reached by navigating to :menuselection:`Website app --> Configuration --> eCommerce: Payment Providers`, or :menuselection:`Sales app --> Configuration --> Online Payments: Payment Providers`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:32 +msgid "Next, set the :guilabel:`State` to :guilabel:`Enabled` to enable wire transfers. Use the drop-down menus next to the :guilabel:`Company` and :guilabel:`Website` fields to set where wire transfers can be used." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:36 +msgid "The options in the :guilabel:`Configuration` tab can be used to customize the wire transfer. Optionally tick the checkbox next to :guilabel:`Enable QR Codes` to enable the use of QR codes when paying by wire transfer, if desired." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:40 +msgid "Use the drop-down menu next to the :guilabel:`Communication` field to select the communication type used on sales orders. Choose :guilabel:`Based on Document Reference` to use the sales order (or invoice number), or :guilabel:`Based on Customer ID` to use the customer identifier. With either method selected, communication is given to the customer, once they choose the wire transfer payment method." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:46 +msgid "The configuration options listed under the :guilabel:`Availability` section are used to set payment restrictions, and are optional. Use the :guilabel:`Maximum Amount` field to set a maximum payment value, the :guilabel:`Currencies` field to restrict any currencies from being used for payment, and the :guilabel:`Countries` field to restrict payment from any particular countries, if desired." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:51 +msgid "In the :guilabel:`Messages` tab, use the :guilabel:`Pending Message` field to add a message containing wire transfer information. This message is displayed to the customer after confirming their order, as well as if the order is marked as pending after the payment is processed." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:55 +msgid "If :doc:`a bank account <../../../finance/accounting/bank>` has already been defined, the account number is automatically added to the default message generated by Odoo. A bank account can also be added afterwards, and the message updates with the appropriate bank information by clicking :icon:`fa-refresh` :guilabel:`Reload pending message`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:60 +msgid "Once all necessary configuration settings are complete, the :icon:`fa-eye-slash` :guilabel:`Unpublished` smart button located at the top of the page automatically changes to :icon:`fa-globe` :guilabel:`Published` to show the wire transfer payment option is now visible to customers. Only keep the payment method published if payments are ready to be received." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:66 +msgid "It is possible to keep the payment method enabled, but **not** visible to customers, until payments are ready to be received. To do that, set the smart button to :icon:`fa-eye-slash` :guilabel:`Unpublished` after setting the :guilabel:`State` to :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:-1 +msgid "The wire transfer card enabled and published." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:75 +msgid "Test mode" +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:77 +msgid "The wire transfer payment method can be tested before it is accessed by customers by selecting the :guilabel:`Test Mode` option in the :guilabel:`State` field on the form. Upon selecting :guilabel:`Test Mode`, an orange :guilabel:`Test mode` banner appears in the upper-right corner of the form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:82 +msgid "Next, enter the credentials for a bank account with accessible transactions in the :guilabel:`Messages` tab. To re-enable normal function after testing, change the :guilabel:`State` setting to :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:87 +msgid "By default, the payment provider remains :guilabel:`Unpublished` in :guilabel:`Test Mode`, so it is not visible to visitors." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:91 +msgid "It is recommended to use the :guilabel:`Test Mode` setting on a duplicate (or test) database to avoid potential issues with invoice numbering." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:97 +msgid "Pay by wire transfer" +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:99 +msgid "With wire transfers :ref:`enabled and published `, customers see wire transfers as an available payment method at checkout when purchasing a product." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:102 +msgid "When this method is selected by a customer, they are shown the *Pending Message* set in the :ref:`wire transfer configuration page `, after confirming their purchase. Once the purchase is confirmed, a sales order is created." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:-1 +msgid "The wire transfer pending message shown to customers." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:111 +msgid "Online orders remain in the *Quotation sent* (i.e. unpaid order) stage until both the payment is received, *and* the order is confirmed manually, using the :guilabel:`Confirm` button on the sales order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:115 +msgid "To begin processing the payment, navigate to :menuselection:`Sales app --> Orders --> Orders`, and click the corresponding sales order. Ensure the sales order is correct, then click :guilabel:`Confirm` to confirm the sales order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:119 +msgid "Next, click the new :guilabel:`Create Invoice` button, then choose :guilabel:`Regular invoice`, and click :guilabel:`Create Draft Invoice`. A draft of the invoice appears. Click :guilabel:`Confirm` to validate the invoice." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:123 +msgid "To send this invoice to the customer, click the :guilabel:`Send & Print` button. A :guilabel:`Send` pop-up window appears, with an email template configured, and a PDF invoice attached." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:126 +msgid "Ensure the information is correct, then click :guilabel:`Send & Print`. The pop-up window disappears, and the :guilabel:`Send & Print` button turns gray to show the invoice has been sent." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:130 +msgid "The default template for sending an invoice can be modified by navigating to :menuselection:`Settings app --> Companies --> Email Templates --> Review All Templates --> Invoice: Sending`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:134 +msgid "Next, click the :guilabel:`Register payment` button on the invoice page. A pop-up window titled, :guilabel:`Register Payment`, appears with options for selecting the type of payment. In the :guilabel:`Journal` field, select :guilabel:`Bank` from the drop-down menu. Next, set the :guilabel:`Payment Method` to :guilabel:`Manual`. Ensure the :guilabel:`Amount` and :guilabel:`Payment Date` are correct, then click the :guilabel:`Create Payment` button." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:-1 +msgid "The register payment pop-up window." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:144 +msgid "The customer invoice is revealed with a green :guilabel:`In Payment` banner in the upper-right corner. At this point, the flow is now complete." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:-1 +msgid "The green in payment banner displayed on the invoice." +msgstr "" + +#: ../../content/applications/sales/subscriptions/payment_providers/wire_transfer.rst:152 +msgid "If payment has been received before sending the invoice, such as in cash, the payment can still be registered in Odoo by clicking the :guilabel:`Register Payment` button, and creating the payment *before* clicking :guilabel:`Send & Print`. Now, when an invoice is sent using the :guilabel:`Send & Print` button, a new line is automatically added to the invoice message, stating the invoice is already paid." +msgstr "" + #: ../../content/applications/sales/subscriptions/plans.rst:3 msgid "Subscription plans" msgstr "" @@ -15733,15 +16800,27 @@ msgstr "" msgid "The :guilabel:`Product Type` field is set to :guilabel:`Service` by default, as well. However, subscription products *can* be set to other types, if needed." msgstr "" +#: ../../content/applications/sales/subscriptions/products.rst:71 +msgid "When creating a physical subscription product in the Odoo **Sales** application, the :guilabel:`Invoicing Policy` must be set to :guilabel:`Ordered quantities`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:74 +msgid "Setting it to :guilabel:`Delivered quantities` causes issues with invoice creation, and disrupts the subscription process." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:77 +msgid "Similarly, when creating a physical subscription product in the Odoo **Subscriptions** application, the :guilabel:`Invoicing Policy` must **not** be set to :guilabel:`Based on Delivered Quantity (Manual)` for the same reasons." +msgstr "" + #: ../../content/applications/sales/subscriptions/products.rst:-1 msgid "A basic subscription product form in Odoo Subscriptions application." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:75 +#: ../../content/applications/sales/subscriptions/products.rst:86 msgid "Time-based pricing" msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:77 +#: ../../content/applications/sales/subscriptions/products.rst:88 msgid "Once the desired fields in the :guilabel:`General Information` tab have been entered, click the :guilabel:`Time-based pricing` tab on the product form." msgstr "" @@ -15749,15 +16828,15 @@ msgstr "" msgid "The time-based pricing tab on a subscription product form in Odoo Subscriptions." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:84 +#: ../../content/applications/sales/subscriptions/products.rst:95 msgid "From here, click :guilabel:`Add a price` to begin defining recurring prices." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:86 +#: ../../content/applications/sales/subscriptions/products.rst:97 msgid "In the :guilabel:`Period` column, select a desired recurrence period. In the :guilabel:`Pricelist` column, select a pricelist, if needed. Then, in the :guilabel:`Price` column, enter the price for that recurrence period." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:91 +#: ../../content/applications/sales/subscriptions/products.rst:102 msgid ":guilabel:`Daily` and :guilabel:`Hourly` periods **cannot** be used on recurring products." msgstr "" @@ -15765,23 +16844,23 @@ msgstr "" msgid "The validation error pop-up window that appears in Odoo Subscriptions." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:98 +#: ../../content/applications/sales/subscriptions/products.rst:109 msgid "There is *no limit* to how many lines can be added to the :guilabel:`Time-based pricing` table." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:101 +#: ../../content/applications/sales/subscriptions/products.rst:112 msgid "An existing product can be made into a subscription product, simply by marking it as :guilabel:`Recurring`, and configuring :guilabel:`Time-based pricing` on the product form." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:107 +#: ../../content/applications/sales/subscriptions/products.rst:118 msgid ":doc:`Pricelists <../sales/products_prices/prices/pricing>` can be used with subscription products to give special pricing to customers included in pricelists." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:110 +#: ../../content/applications/sales/subscriptions/products.rst:121 msgid "This can be configured either in the :guilabel:`Time-based pricing` tab of the product form, or on the pricelist form in the *Sales* application." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:113 +#: ../../content/applications/sales/subscriptions/products.rst:124 msgid "To create recurring price rules for specific pricelists in the :guilabel:`Time-based pricing` tab of the product form, select a pricelist in the :guilabel:`Pricelist` column." msgstr "" @@ -15789,23 +16868,23 @@ msgstr "" msgid "Pricelists in the \"Time-based pricing\" tab of the product form." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:120 +#: ../../content/applications/sales/subscriptions/products.rst:131 msgid "When pricelists are added to the :guilabel:`Time-based pricing` tab, the pricelist form in the *Sales* app is automatically updated." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:123 +#: ../../content/applications/sales/subscriptions/products.rst:134 msgid "Time-based pricing rules can also be configured directly on the pricelist form." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:125 +#: ../../content/applications/sales/subscriptions/products.rst:136 msgid "To do this, go to :menuselection:`Sales app --> Products --> Pricelists`, and select a pricelist (or click :guilabel:`New` to create a new pricelist)." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:129 +#: ../../content/applications/sales/subscriptions/products.rst:140 msgid "Pricelists are also accessible through the Odoo *Subscriptions* app by following the same menu steps." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:132 +#: ../../content/applications/sales/subscriptions/products.rst:143 msgid "Then, on the pricelist form, under the :guilabel:`Time-based rules` tab, click :guilabel:`Add a line`." msgstr "" @@ -15813,15 +16892,15 @@ msgstr "" msgid "The time-based rules tab on a pricelist form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:139 +#: ../../content/applications/sales/subscriptions/products.rst:150 msgid "Then, select a subscription product in the :guilabel:`Products` column, and select a recurrence period in the :guilabel:`Period` column. Lastly, enter a :guilabel:`Price` for that particular product and period. Add as many lines as needed." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:143 +#: ../../content/applications/sales/subscriptions/products.rst:154 msgid "When :guilabel:`Time-based rules` are added to the pricelist form, the :guilabel:`Time-based pricing` tab of the product form is automatically updated." msgstr "" -#: ../../content/applications/sales/subscriptions/products.rst:147 +#: ../../content/applications/sales/subscriptions/products.rst:158 msgid ":doc:`ecommerce`" msgstr "" diff --git a/locale/sources/services.pot b/locale/sources/services.pot index 461e5dfda..c5bb00e8c 100644 --- a/locale/sources/services.pot +++ b/locale/sources/services.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 13:30+0000\n" +"POT-Creation-Date: 2024-08-21 11:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -28,149 +28,49 @@ msgstr "" msgid "`Odoo Tutorials: Field Service `_" msgstr "" -#: ../../content/applications/services/field_service/default_warehouse.rst:3 -msgid "User default warehouse" +#: ../../content/applications/services/field_service/creating_tasks.rst:3 +msgid "Creating field service tasks" msgstr "" -#: ../../content/applications/services/field_service/default_warehouse.rst:5 -msgid "Setting up a **default warehouse** can be useful for field technicians who keep a supply in their van or those who always resupply from the same warehouse. It also allows field workers to switch between warehouses from their profiles." +#: ../../content/applications/services/field_service/creating_tasks.rst:5 +msgid "Tasks in Odoo Field Service can be created manually or automatically, including from sales orders or helpdesk tickets." msgstr "" -#: ../../content/applications/services/field_service/default_warehouse.rst:9 -msgid "Products in sales orders created during field interventions are always pulled from the default warehouse, keeping the inventory accurate." +#: ../../content/applications/services/field_service/creating_tasks.rst:9 +#: ../../content/applications/services/project/tasks/task_creation.rst:9 +msgid "Manual task creation" msgstr "" -#: ../../content/applications/services/field_service/default_warehouse.rst:13 -msgid ":doc:`../../inventory_and_mrp/inventory`" +#: ../../content/applications/services/field_service/creating_tasks.rst:11 +msgid "To create a new field service task:" msgstr "" -#: ../../content/applications/services/field_service/default_warehouse.rst:16 -#: ../../content/applications/services/field_service/worksheets.rst:15 -#: ../../content/applications/services/helpdesk/overview/help_center.rst:14 -#: ../../content/applications/services/planning.rst:29 -#: ../../content/applications/services/project/project_management.rst:19 -#: ../../content/applications/services/project/tasks/recurring_tasks.rst:13 -msgid "Configuration" +#: ../../content/applications/services/field_service/creating_tasks.rst:13 +msgid "Open the Field service app and go to :menuselection:`Field Service --> All Tasks --> All Tasks`." msgstr "" -#: ../../content/applications/services/field_service/default_warehouse.rst:18 -msgid "To set up a user default warehouse, the :doc:`storage locations <../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations>` feature needs to be activated in the **Inventory** app. It is also necessary to have more than one warehouse in your database." +#: ../../content/applications/services/field_service/creating_tasks.rst:14 +msgid "Click :guilabel:`New`." msgstr "" -#: ../../content/applications/services/field_service/default_warehouse.rst:23 -msgid "You can either set it up :ref:`for your profile `, or :ref:`for all users `." +#: ../../content/applications/services/field_service/creating_tasks.rst:15 +msgid "Fill in the task title, :guilabel:`Customer` and any other :ref:`optional field `, then save manually." msgstr "" -#: ../../content/applications/services/field_service/default_warehouse.rst:27 -msgid ":doc:`../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations`" +#: ../../content/applications/services/field_service/creating_tasks.rst:19 +msgid "Task creation from a sales order" msgstr "" -#: ../../content/applications/services/field_service/default_warehouse.rst:32 -msgid "For your profile" +#: ../../content/applications/services/field_service/creating_tasks.rst:21 +msgid "This feature allows for field service tasks to be automatically created from a sales order. When you create a quotation with the :ref:`service product ` and confirm it, a task is automatically created in your Field Service project. Click the :guilabel:`Tasks` smart button to access it from the sales order." msgstr "" -#: ../../content/applications/services/field_service/default_warehouse.rst:34 -msgid "To set up a default warehouse for yourself, click your **profile icon** in the upper right corner of the screen, then, go to :menuselection:`My Profile --> Preferences --> Default Warehouse`. Select the default warehouse from the drop-down menu." +#: ../../content/applications/services/field_service/creating_tasks.rst:27 +msgid "Task creation from a helpdesk ticket" msgstr "" -#: ../../content/applications/services/field_service/default_warehouse.rst:41 -msgid "For all users" -msgstr "" - -#: ../../content/applications/services/field_service/default_warehouse.rst:43 -msgid "To set up a default warehouse for a specific user, go to :menuselection:`Settings --> Users --> Manage users`, select a user, then go to the :guilabel:`Preferences` tab. Scroll down to :guilabel:`Inventory`, and select the default warehouse from the drop-down menu." -msgstr "" - -#: ../../content/applications/services/field_service/default_warehouse.rst:-1 -msgid "Selection of a default warehouse on a user profile." -msgstr "" - -#: ../../content/applications/services/field_service/default_warehouse.rst:51 -msgid "Use in field service tasks" -msgstr "" - -#: ../../content/applications/services/field_service/default_warehouse.rst:53 -msgid "Once a default warehouse has been configured for a user, the materials used for a sales order related to a Field Service task are pulled from that specific warehouse. Open the related sales order, go to the :guilabel:`Other Info` tab, then scroll down to :guilabel:`Delivery`. The default warehouse is applied correctly." -msgstr "" - -#: ../../content/applications/services/field_service/default_warehouse.rst:58 -msgid "Once the Field Service task is marked as done, the stock of the default warehouse is automatically updated." -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:3 -msgid "Onsite interventions planning" -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:6 -msgid "From a sales order" -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:8 -msgid "Allowing your sales team to open onsite interventions creates a seamless experience for your customers. They can receive a quotation they first have to approve before the work even starts." -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:11 -msgid "Go to :menuselection:`Field Service --> Configuration --> Products` and create or edit a product." -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:13 -msgid "Under the :guilabel:`General Information` tab, select :guilabel:`Service` as :guilabel:`Product Type`." -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:15 -msgid "Under the :guilabel:`Sales` tab, select :guilabel:`Timesheets on tasks` as :guilabel:`Service Invoicing Policy`." -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:17 -msgid "Select :guilabel:`Create a task in an existing project` as :guilabel:`Service Tracking`." -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:18 -msgid "Select your :guilabel:`Project`." -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:19 -msgid "If you use them, select your :guilabel:`Worksheet Template`, and save." -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:-1 -msgid "Product configuration to create tasks from sales orders in Odoo Field Service" -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:25 -msgid "From the :doc:`Sales <../../sales/sales>` app, create a quotation with the product and confirm it. A task is automatically set up under your Field Service project. It is directly accessible from the sales order." -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:-1 -msgid "Field Service task on a sales order in Odoo Sales" -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:34 -msgid "From helpdesk tickets" -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:36 -msgid "The integration with the :doc:`Helpdesk <../helpdesk>` app lets your helpdesk team manage intervention requests directly. Planning field service tasks from tickets speeds up your processes." -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:40 -msgid "Configure the helpdesk team" -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:42 -msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select a team and enable :guilabel:`Onsite Interventions`." -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:-1 -msgid "Onsite interventions settings in Odoo Helpdesk" -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:49 -msgid "The helpdesk tickets of the team now display the :guilabel:`Plan Intervention` button. Click on it to create a new task under your field service project." -msgstr "" - -#: ../../content/applications/services/field_service/onsite_interventions.rst:-1 -msgid "Plan intervention from helpdesk tickets in Odoo Helpdesk" +#: ../../content/applications/services/field_service/creating_tasks.rst:29 +msgid "If you have the Helpdesk app installed, you can :ref:`create field service tasks from a helpdesk ticket `." msgstr "" #: ../../content/applications/services/field_service/planning_itinerary.rst:3 @@ -221,6 +121,123 @@ msgstr "" msgid "Click your task in the left column or the map pin to display the task's details. From there, you can :guilabel:`Open` the task or click :guilabel:`Navigate to` to get an itinerary from your current location to this specific task's location." msgstr "" +#: ../../content/applications/services/field_service/product_management.rst:3 +msgid "Product management" +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:5 +msgid "When field service workers perform tasks on-site, they commonly use products to complete their work. Odoo Field Service allows them to record these products using the **product catalog** and **default warehouse** features. Doing so keeps your inventory up-to-date in real-time and automatically adds the products to the invoice." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:11 +msgid "Product catalog" +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:13 +msgid "To activate the product catalog for Field Service, go to :menuselection:`Field Service --> Configuration --> Settings` and enable the :guilabel:`Time and Material Invoicing` feature." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:16 +msgid "To add products to a task, proceed as follows:" +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:18 +msgid "Go to Field Service and open a task." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:19 +msgid "Click the :guilabel:`Products` smart button." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:20 +msgid "Click :guilabel:`Add` on a product card to add it to your task." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:21 +msgid "If needed, adjust the number of products using the :guilabel:`-` and :guilabel:`+` buttons." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:23 +msgid "Going back to your task, the smart button now displays the amount of products you added and the price. You can return to the product catalog at any time to edit the product selection." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:27 +msgid "To create and edit products from Field Service, go to :menuselection:`Field Service --> Configuration --> Products`." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:29 +msgid "To find your products more easily, use the search bar and filter your products by :guilabel:`Product Category` and :guilabel:`Attributes`." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:33 +msgid "User default warehouse" +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:35 +msgid "Setting up a **default warehouse** can be useful for field technicians who keep a supply on the go in their van or those who always resupply from the same warehouse. It also allows field workers to switch between warehouses from their profiles." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:39 +msgid "Products in sales orders created during field interventions are always pulled from the default warehouse, keeping the inventory accurate." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:43 +msgid ":doc:`../../inventory_and_mrp/inventory`" +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:46 +#: ../../content/applications/services/field_service/worksheets.rst:15 +#: ../../content/applications/services/helpdesk/overview/help_center.rst:14 +#: ../../content/applications/services/planning.rst:29 +#: ../../content/applications/services/project/project_management.rst:19 +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:13 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:48 +msgid "To set up a user default warehouse, the :doc:`storage locations <../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations>` feature needs to be activated in the **Inventory** app. It is also necessary to have more than one warehouse in your database." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:53 +msgid "You can either set it up :ref:`for your profile `, or :ref:`for all users `." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:57 +msgid ":doc:`../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations`" +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:62 +msgid "For your profile" +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:64 +msgid "To set up a default warehouse for yourself, click your **profile icon** in the upper right corner of the screen, then, go to :menuselection:`My Profile --> Preferences --> Default Warehouse`. Select the default warehouse from the drop-down menu." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:71 +msgid "For all users" +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:73 +msgid "To set up a default warehouse for a specific user, go to :menuselection:`Settings --> Users --> Manage users`, select a user, then go to the :guilabel:`Preferences` tab. Scroll down to :guilabel:`Inventory`, and select the default warehouse from the drop-down menu." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:-1 +msgid "Selection of a default warehouse on a user profile." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:81 +msgid "Use in field service tasks" +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:83 +msgid "Once a default warehouse has been configured for a user, the materials used for a sales order related to a Field Service task are pulled from that specific warehouse. Open the related sales order, go to the :guilabel:`Other Info` tab, then scroll down to :guilabel:`Delivery`. The default warehouse is applied correctly." +msgstr "" + +#: ../../content/applications/services/field_service/product_management.rst:88 +msgid "Once the Field Service task is marked as done, the stock of the default warehouse is automatically updated." +msgstr "" + #: ../../content/applications/services/field_service/worksheets.rst:3 msgid "Worksheets" msgstr "" @@ -1421,7 +1438,7 @@ msgid "When the necessary information has been entered, click :guilabel:`Create msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:256 -msgid ":doc:`../../../inventory_and_mrp/inventory/product_management/product_replenishment/uom`" +msgid ":doc:`../../../inventory_and_mrp/inventory/product_management/configure/uom`" msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:257 @@ -2379,7 +2396,7 @@ msgid ":doc:`/applications/services/helpdesk/advanced/close_tickets`" msgstr "" #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:351 -msgid ":doc:`/applications/general/email_communication/email_servers`" +msgid ":doc:`../../../general/email_communication`" msgstr "" #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:352 @@ -3543,6 +3560,94 @@ msgstr "" msgid "**To stop** the recurrence, open the last task in recurrence and press the :guilabel:`Recurrent` button next to the :guilabel:`Planned date`." msgstr "" +#: ../../content/applications/services/project/tasks/sub-tasks.rst:3 +msgid "Sub-tasks" +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:5 +msgid "When handling project tasks, you can often benefit from splitting the workload into smaller **sub-tasks**, making it easier to track progress and manage the work." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:8 +msgid "Odoo’s sub-task feature is particularly useful in some of the following cases:" +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:10 +msgid "The task workload is too big to handle in one record." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:11 +msgid "There’s a clear sequence of steps to follow." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:12 +msgid "Some parts of the workload fall under the scope of different projects and/or assignees." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:14 +msgid "The original task to which sub-tasks are linked is referred to as the **parent task**. The sub-tasks of the parent task are known as **child tasks**." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:18 +msgid "Creating sub-tasks" +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:20 +msgid "To create a sub-task:" +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:22 +msgid "Open the Project app, then go into your desired project." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:23 +msgid "Click the task where you want to add the sub-task, then click the :guilabel:`Sub-tasks` tab." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:24 +msgid "Click :guilabel:`Add a line`, then fill in the :guilabel:`Title`." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:25 +msgid "Click the :icon:`fa-cloud-upload` (:guilabel:`save`) icon to save the task manually." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:28 +msgid "You can edit several fields of a sub-task directly from the parent task’s sub-task tab without opening the individual sub-task. By default, those are: :guilabel:`Title`, :guilabel:`Priority`, :guilabel:`Status`, and :guilabel:`Assignees`. Use the :icon:`fa-sliders` (:guilabel:`sliders`) icon to add or remove fields." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:33 +msgid "Once the new sub-task is created, the following changes occur in the parent task:" +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:35 +msgid "A **smart button** displays the total number of sub-tasks, as well as the number of closed (**done** or **canceled**) sub-tasks. Click the smart button to access the list of the sub-tasks." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:37 +msgid "The :guilabel:`Allocated time` displays the amount of time allocated to the parent task, as well as time allocated to the sub-tasks. This can be used to ensure that the time allocated to sub-tasks does not exceed time allocated to the parent task." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:40 +msgid "The :guilabel:`Timesheets` tab includes a breakdown of time spent on the parent task as well as sub-tasks." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:43 +msgid "Click :guilabel:`View` to open the sub-task you created. The sub-task form is identical to the :ref:`task form `." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:48 +msgid "A **smart button** allows to navigate back to the :guilabel:`Parent task`." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:49 +msgid "The :guilabel:`Sub-tasks` tab allows for further creation of sub-tasks." +msgstr "" + +#: ../../content/applications/services/project/tasks/sub-tasks.rst:50 +msgid "Selecting a :guilabel:`Project` will trigger this sub-task to be displayed in the Kanban view of the selected project." +msgstr "" + #: ../../content/applications/services/project/tasks/task_creation.rst:3 msgid "Task creation" msgstr "" @@ -3551,10 +3656,6 @@ msgstr "" msgid "Tasks in Odoo Project can be created manually or automatically, including from emails or website forms." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:9 -msgid "Manual task creation" -msgstr "" - #: ../../content/applications/services/project/tasks/task_creation.rst:11 msgid "Open the Project app and choose the desired project. Create a new task by doing one of the following:" msgstr "" @@ -3571,83 +3672,83 @@ msgstr "" msgid "Fill in the :guilabel:`Task Title` and add one or more :guilabel:`Assignees`, then click :guilabel:`Add`." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:23 +#: ../../content/applications/services/project/tasks/task_creation.rst:25 msgid "Task configuration" msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:25 +#: ../../content/applications/services/project/tasks/task_creation.rst:27 msgid "Click the task to open it. The task form includes the following fields that you can fill in:" msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:27 +#: ../../content/applications/services/project/tasks/task_creation.rst:29 msgid ":guilabel:`Task Title`: title of the task." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:28 +#: ../../content/applications/services/project/tasks/task_creation.rst:30 msgid ":icon:`fa-star-o` (:guilabel:`Star`): click the :icon:`fa-star-o` (:guilabel:`star`) icon to mark the task as high priority. The icon will turn yellow. Click it again to remove the high priority." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:30 +#: ../../content/applications/services/project/tasks/task_creation.rst:32 msgid ":guilabel:`Project`: the project that this task belongs to." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:31 +#: ../../content/applications/services/project/tasks/task_creation.rst:33 msgid ":guilabel:`Assignees`: the person(s) in charge of handling the work on this task." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:32 +#: ../../content/applications/services/project/tasks/task_creation.rst:34 msgid ":guilabel:`Tags`: custom labels allowing to categorize and filter your tasks." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:33 +#: ../../content/applications/services/project/tasks/task_creation.rst:35 msgid ":guilabel:`Customer`: the person or company that will be billed for this task. This field only appears in tasks that belong to billable projects." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:35 +#: ../../content/applications/services/project/tasks/task_creation.rst:37 msgid ":guilabel:`Sales Order Item`: this can be either the sales order that was used to create this task, or a sales order that was linked to this task manually. This field only appears in tasks linked to billable projects." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:38 +#: ../../content/applications/services/project/tasks/task_creation.rst:40 msgid ":guilabel:`Allocated Time`: the amount of time that the work on this task is expected to last, tracked by timesheets." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:40 +#: ../../content/applications/services/project/tasks/task_creation.rst:42 msgid ":guilabel:`Deadline`: the expected end date of the task. Once this field is filled in, you can also add a start date to designate the entire time frame of the tasks' duration." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:45 +#: ../../content/applications/services/project/tasks/task_creation.rst:47 msgid "You can also create new tasks by switching to the list or Gantt view and clicking :guilabel:`New`." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:47 +#: ../../content/applications/services/project/tasks/task_creation.rst:49 msgid "The following fields can also be edited directly from the Kanban view without opening the individual task: :icon:`fa-star-o` (**priority**), :guilabel:`Allocated hours`, :guilabel:`Assignees`, and **task status**. You can also **color code** or :guilabel:`Set a Cover image` to your task by clicking the :icon:`fa-ellipsis-v` (**vertical ellipsis**)." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:51 +#: ../../content/applications/services/project/tasks/task_creation.rst:53 msgid "You can use the following keyboard shortcuts in the task title to configure new tasks (modify the values in the examples below according to your needs):" msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:54 +#: ../../content/applications/services/project/tasks/task_creation.rst:56 msgid "**30h**: to allocate 30 hours to the task." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:55 +#: ../../content/applications/services/project/tasks/task_creation.rst:57 msgid "**#tags**: to add tags to the task." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:56 +#: ../../content/applications/services/project/tasks/task_creation.rst:58 msgid "**@user**: to assign the task to a user." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:57 +#: ../../content/applications/services/project/tasks/task_creation.rst:59 msgid "**!**: to star the task as high priority." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:59 +#: ../../content/applications/services/project/tasks/task_creation.rst:61 msgid "Along with using the correct format, follow this order: the task's name, followed by the allocated time, the tags, the assignee, and then the priority." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:62 +#: ../../content/applications/services/project/tasks/task_creation.rst:64 msgid "For example, if you want to create a task named \"Prepare workshop\", allocate 5h hours to it, add the \"School\" tag, assign it to Audrey and set its priority to :guilabel:`High`, enter the following task title: Prepare workshop 5h #school @Audrey !" msgstr "" @@ -3655,31 +3756,31 @@ msgstr "" msgid "Using keyboard shortcuts to create a task in Project." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:70 +#: ../../content/applications/services/project/tasks/task_creation.rst:74 msgid "Creating tasks from an email alias" msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:72 +#: ../../content/applications/services/project/tasks/task_creation.rst:76 msgid "This feature allows for project tasks to be automatically created once an email is delivered to a designated email address." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:75 +#: ../../content/applications/services/project/tasks/task_creation.rst:79 msgid "To configure it, open the Project app, then click the :icon:`fa-ellipsis-v` (:guilabel:`vertical ellipsis`) icon next to the desired project's name. Select :guilabel:`Settings`, then open the :guilabel:`Settings` tab." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:79 +#: ../../content/applications/services/project/tasks/task_creation.rst:83 msgid "Fill in the :guilabel:`Create tasks by sending an email to` field as follows:" msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:81 +#: ../../content/applications/services/project/tasks/task_creation.rst:85 msgid "**Section of the alias before the @ symbol**: type the name of the email alias, e.g. `contact`, `help`, `jobs`." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:83 -msgid "**Domain**: in most cases, this is filled in by default with your :doc:`domain <../../../general/email_communication/email_servers>`." +#: ../../content/applications/services/project/tasks/task_creation.rst:87 +msgid "**Domain**: in most cases, this is filled in by default with your :doc:`domain <../../../general/email_communication>`." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:85 +#: ../../content/applications/services/project/tasks/task_creation.rst:89 msgid "**Accept Emails From**: refine the senders whose emails will create tasks in the project." msgstr "" @@ -3687,67 +3788,67 @@ msgstr "" msgid "View of the email alias chosen on the dashboard view in Odoo Project" msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:90 +#: ../../content/applications/services/project/tasks/task_creation.rst:94 msgid "Once configured, the email alias can be seen under the name of your project on the Kanban dashboard." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:92 +#: ../../content/applications/services/project/tasks/task_creation.rst:96 msgid "When an email is sent to the alias, the email is automatically converted into a project task. The following rules apply:" msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:95 +#: ../../content/applications/services/project/tasks/task_creation.rst:99 msgid "The email sender is displayed in the :guilabel:`Customer` field." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:96 +#: ../../content/applications/services/project/tasks/task_creation.rst:100 msgid "The email subject is displayed in the :guilabel:`Task Title` field." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:97 +#: ../../content/applications/services/project/tasks/task_creation.rst:101 msgid "The email body is displayed in the :guilabel:`Description` field." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:98 +#: ../../content/applications/services/project/tasks/task_creation.rst:102 msgid "The whole content of the email is additionally displayed in the **chatter**." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:99 +#: ../../content/applications/services/project/tasks/task_creation.rst:103 msgid "All the recipients of the email (To/Cc/Bcc) that are Odoo users are automatically added as **followers** of the task." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:103 +#: ../../content/applications/services/project/tasks/task_creation.rst:107 msgid "Creating tasks from a website form" msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:105 +#: ../../content/applications/services/project/tasks/task_creation.rst:109 msgid "If you have the Website app installed in your database, you can configure any form on your website to trigger the creation of tasks in a project." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:108 +#: ../../content/applications/services/project/tasks/task_creation.rst:112 msgid "Go to the website page where you wish to add the the form and :ref:`add the Form building block `." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:110 +#: ../../content/applications/services/project/tasks/task_creation.rst:114 msgid "In the website editor, edit the following fields:" msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:112 +#: ../../content/applications/services/project/tasks/task_creation.rst:116 msgid ":guilabel:`Action`: select :guilabel:`Create a Task`." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:113 +#: ../../content/applications/services/project/tasks/task_creation.rst:117 msgid ":guilabel:`Project`: choose the project that you want the new tasks to be created in." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:115 +#: ../../content/applications/services/project/tasks/task_creation.rst:119 msgid ":ref:`Customize the form `." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:117 +#: ../../content/applications/services/project/tasks/task_creation.rst:121 msgid "When the form is submitted, it automatically creates a project task. The task's content is defined by the form's corresponding fields." msgstr "" -#: ../../content/applications/services/project/tasks/task_creation.rst:121 +#: ../../content/applications/services/project/tasks/task_creation.rst:125 msgid ":doc:`Dynamic website content <../../../websites/website/web_design/building_blocks/dynamic_content>`" msgstr "" diff --git a/locale/sources/studio.pot b/locale/sources/studio.pot index 1af208143..acda38a08 100644 --- a/locale/sources/studio.pot +++ b/locale/sources/studio.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 13:30+0000\n" +"POT-Creation-Date: 2024-08-21 11:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1794,62 +1794,80 @@ msgid "Views" msgstr "" #: ../../content/applications/studio/views.rst:5 -msgid "Views are the interface that allows displaying the data contained in a model. One model can have several views, which are simply different ways to show the same data. In Studio, views are organized into four categories: :ref:`general `, :ref:`multiple records `, :ref:`timeline `, and :ref:`reporting `." +msgid "Views are the interface that allows displaying the data contained in a :doc:`model `. One model can have several views, which are simply different ways to show the same data. In Studio, views are organized into four categories: :ref:`general `, :ref:`multiple records `, :ref:`timeline `, and :ref:`reporting `." msgstr "" #: ../../content/applications/studio/views.rst:12 -msgid "To change the default view of a model, go to :menuselection:`Studio --> Views --> Dropdown menu (⋮) --> Set as Default`." +msgid "To change the default view of a model, :ref:`access Studio `, go to :guilabel:`Views`, click the :icon:`fa-ellipsis-v` (:guilabel:`ellipsis`) icon next to the desired view, and click :guilabel:`Set as Default`." msgstr "" -#: ../../content/applications/studio/views.rst:16 -msgid "You can modify views by using the built-in XML editor. To do so, activate :ref:`Developer mode `, go to the view you want to edit, select the :guilabel:`View` tab and then click on :guilabel:` XML`." +#: ../../content/applications/studio/views.rst:15 +msgid "You can modify views using the built-in XML editor: Activate the :ref:`Developer mode `, go to the view you want to edit, select the :guilabel:`View` tab, and click :guilabel:` XML`." msgstr "" -#: ../../content/applications/studio/views.rst:21 -msgid "If you are editing a view using the XML editor, avoid making changes directly to standard views and inherited views, as those would be reset and would not be kept in case of an update or module upgrade. Always make sure you select the right Studio inherited views. Indeed, when you modify a view in Studio by drag-and-dropping a new field, a specific Studio inherited view and its XPath, the latter which defines which part of the view is modified, are automatically generated." +#: ../../content/applications/studio/views.rst:20 +msgid "If you are editing a view using the XML editor, avoid making changes directly to standard and inherited views, as these would be reset and lost during updates or module upgrades. Always make sure you select the right Studio inherited views: When you modify a view in Studio by dragging and dropping a new field, for example, a specific Studio inherited view and its corresponding XPath, which defines the modified part of the view, are automatically generated." msgstr "" -#: ../../content/applications/studio/views.rst:31 +#: ../../content/applications/studio/views.rst:30 msgid "General views" msgstr "" -#: ../../content/applications/studio/views.rst:34 -#: ../../content/applications/studio/views.rst:97 -#: ../../content/applications/studio/views.rst:195 -#: ../../content/applications/studio/views.rst:311 +#: ../../content/applications/studio/views.rst:33 +#: ../../content/applications/studio/views.rst:104 +#: ../../content/applications/studio/views.rst:205 +#: ../../content/applications/studio/views.rst:320 msgid "The settings described below are found under the view's :guilabel:`View` tab unless specified otherwise." msgstr "" -#: ../../content/applications/studio/views.rst:40 +#: ../../content/applications/studio/views.rst:39 msgid "Form" msgstr "" -#: ../../content/applications/studio/views.rst:42 -msgid "The :guilabel:`Form` view is used when creating and editing records, such as contacts, sales orders, products, etc." +#: ../../content/applications/studio/views.rst:41 +msgid "The :guilabel:`Form` :icon:`fa-address-card` view is used when creating and editing records, such as contacts, sales orders, products, etc." msgstr "" -#: ../../content/applications/studio/views.rst:45 -msgid "To structure a form, drag-and-drop the :guilabel:`Tabs and Columns` element found under the :guilabel:`+ Add` tab." +#: ../../content/applications/studio/views.rst:44 +msgid "To structure a form, drag and drop the :guilabel:`Tabs and Columns` element found under the :guilabel:`+ Add` tab." msgstr "" -#: ../../content/applications/studio/views.rst:47 -#: ../../content/applications/studio/views.rst:132 +#: ../../content/applications/studio/views.rst:46 +#: ../../content/applications/studio/views.rst:137 msgid "To prevent users from creating, editing, or deleting records, untick :guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." msgstr "" +#: ../../content/applications/studio/views.rst:48 +msgid "To add a button, click :guilabel:`Add a button` at the top of the form, enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:51 +#: ../../content/applications/studio/views.rst:153 +msgid ":guilabel:`Run a Server Action`: select the :ref:`server action ` to be executed from the dropdown list;" +msgstr "" + +#: ../../content/applications/studio/views.rst:53 +#: ../../content/applications/studio/views.rst:155 +msgid ":guilabel:`Call a method`: specify an existing Python method already defined in Odoo." +msgstr "" + +#: ../../content/applications/studio/views.rst:55 +msgid "To add a smart button, click the :icon:`fa-plus-square` (:guilabel:`plus`) icon in the top-right corner of the form. Enter a :guilabel:`Label`, choose an :guilabel:`Icon`, and select a :ref:`related field `." +msgstr "" + #: ../../content/applications/studio/views.rst:0 msgid "Sales order model's Form view" msgstr "" -#: ../../content/applications/studio/views.rst:59 +#: ../../content/applications/studio/views.rst:67 msgid "Activity" msgstr "" -#: ../../content/applications/studio/views.rst:61 -msgid "The :guilabel:`Activity` view is used to schedule and have an overview of activities (emails, calls, etc.) linked to records." +#: ../../content/applications/studio/views.rst:69 +msgid "The :guilabel:`Activity` :icon:`fa-clock-o` view is used to schedule and have an overview of activities (emails, calls, etc.) linked to records." msgstr "" -#: ../../content/applications/studio/views.rst:65 +#: ../../content/applications/studio/views.rst:73 msgid "This view can only be modified within Studio by editing the XML code." msgstr "" @@ -1857,84 +1875,89 @@ msgstr "" msgid "Lead/Opportunity model's Activity view" msgstr "" -#: ../../content/applications/studio/views.rst:76 +#: ../../content/applications/studio/views.rst:83 msgid "Search" msgstr "" -#: ../../content/applications/studio/views.rst:78 -msgid "The :guilabel:`Search` view is added on top of other views to filter, group, and search records." +#: ../../content/applications/studio/views.rst:85 +msgid "The :guilabel:`Search` :icon:`oi-search` view is added on top of other views to filter, group, and search records." msgstr "" -#: ../../content/applications/studio/views.rst:80 +#: ../../content/applications/studio/views.rst:88 msgid "To add custom :guilabel:`Filters` and structure them using :guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop them under :guilabel:`Filters`." msgstr "" -#: ../../content/applications/studio/views.rst:82 -msgid "To add an existing field under the search dropdown menu, go to the :guilabel:`+ Add` tab and drag-and-drop it under :guilabel:`Autocompletion Fields`." +#: ../../content/applications/studio/views.rst:90 +msgid "To add an existing field under the search dropdown menu, go to the :guilabel:`+ Add` tab and drag and drop it under :guilabel:`Autocompletion Fields`." msgstr "" #: ../../content/applications/studio/views.rst:0 msgid "Project model's Search view on the Kanban view" msgstr "" -#: ../../content/applications/studio/views.rst:94 +#: ../../content/applications/studio/views.rst:101 msgid "Multiple records views" msgstr "" -#: ../../content/applications/studio/views.rst:103 +#: ../../content/applications/studio/views.rst:110 msgid "Kanban" msgstr "" -#: ../../content/applications/studio/views.rst:105 -msgid "The :guilabel:`Kanban` view is often used to support business flows by moving records across stages or as an alternative way to display records inside *cards*." +#: ../../content/applications/studio/views.rst:112 +msgid "The :guilabel:`Kanban` :icon:`oi-view-kanban` view is often used to support business flows by moving records across stages or as an alternative way to display records inside *cards*." msgstr "" -#: ../../content/applications/studio/views.rst:109 +#: ../../content/applications/studio/views.rst:116 msgid "If the :guilabel:`Kanban` view exists, it is used by default to display data on mobile devices instead of the :ref:`List view `." msgstr "" -#: ../../content/applications/studio/views.rst:112 +#: ../../content/applications/studio/views.rst:119 msgid "To prevent users from creating new records, untick :guilabel:`Can Create`." msgstr "" -#: ../../content/applications/studio/views.rst:113 +#: ../../content/applications/studio/views.rst:120 msgid "To create records directly within the view, in a minimalistic form, enable :guilabel:`Quick Create`." msgstr "" -#: ../../content/applications/studio/views.rst:115 -msgid "To change the way records are grouped by default, select a new group under :guilabel:`Default Group by`." +#: ../../content/applications/studio/views.rst:122 +#: ../../content/applications/studio/views.rst:149 +msgid "To set a default grouping for records, select a field under :guilabel:`Default Group By`." msgstr "" #: ../../content/applications/studio/views.rst:0 msgid "Project model's Kanban view" msgstr "" -#: ../../content/applications/studio/views.rst:127 +#: ../../content/applications/studio/views.rst:132 msgid "List" msgstr "" -#: ../../content/applications/studio/views.rst:129 -msgid "The :guilabel:`List` view is used to overview many records at once, look for records, and edit simple records." -msgstr "" - #: ../../content/applications/studio/views.rst:134 -msgid "To create and edit records directly within the view, select either :guilabel:`New record on top` or :guilabel:`New record at the bottom` under :guilabel:`Editable`." +msgid "The :guilabel:`List` :icon:`oi-view-list` view is used to overview many records at once, look for records, and edit simple records." msgstr "" -#: ../../content/applications/studio/views.rst:138 +#: ../../content/applications/studio/views.rst:139 +msgid "To create and edit records directly within the view, select either :guilabel:`Add record at the bottom`, :guilabel:`Add record on top` or :guilabel:`Open form view` under :guilabel:`When Creating Record`." +msgstr "" + +#: ../../content/applications/studio/views.rst:144 msgid "This prevents users from opening records in :ref:`Form view ` from the :guilabel:`List` view." msgstr "" -#: ../../content/applications/studio/views.rst:141 +#: ../../content/applications/studio/views.rst:147 msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." msgstr "" -#: ../../content/applications/studio/views.rst:142 +#: ../../content/applications/studio/views.rst:148 msgid "To change the way records are sorted by default, select a field under :guilabel:`Sort By`." msgstr "" -#: ../../content/applications/studio/views.rst:145 -msgid "To add a drag handle icon to reorder records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." +#: ../../content/applications/studio/views.rst:150 +msgid "To add a button, click :guilabel:`Add a button` at the top of the list, enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:158 +msgid "To add a :icon:`oi-draggable` (:guilabel:`drag handle`) icon to reorder records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." msgstr "" #: ../../content/applications/studio/views.rst:0 @@ -1945,31 +1968,31 @@ msgstr "" msgid "Sales order model's List view" msgstr "" -#: ../../content/applications/studio/views.rst:161 +#: ../../content/applications/studio/views.rst:172 msgid "Map" msgstr "" -#: ../../content/applications/studio/views.rst:163 -msgid "The :guilabel:`Map` view is used to display records on a map. For example, it is used in the Field Service app to plan an itinerary between different tasks." +#: ../../content/applications/studio/views.rst:174 +msgid "The :guilabel:`Map` :icon:`fa-map-marker` view is used to display records on a map. For example, it is used in the Field Service app to plan an itinerary between different tasks." msgstr "" -#: ../../content/applications/studio/views.rst:167 +#: ../../content/applications/studio/views.rst:178 msgid "A :ref:`Many2One field ` linked to the *Contact* model is required to activate the view, as the contact address is used to position records on the map." msgstr "" -#: ../../content/applications/studio/views.rst:170 +#: ../../content/applications/studio/views.rst:181 msgid "To select which kind of contact should be used on the map, select it under :guilabel:`Contact Field`." msgstr "" -#: ../../content/applications/studio/views.rst:172 -msgid "To hide the name or the address of the record, tick :guilabel:`Hide name` or :guilabel:`Hide Address`." +#: ../../content/applications/studio/views.rst:183 +msgid "To hide the name or the address of the record, tick :guilabel:`Hide Name` or :guilabel:`Hide Address`." msgstr "" -#: ../../content/applications/studio/views.rst:174 +#: ../../content/applications/studio/views.rst:185 msgid "To add information from other fields, select them under :guilabel:`Additional Fields`." msgstr "" -#: ../../content/applications/studio/views.rst:175 +#: ../../content/applications/studio/views.rst:186 msgid "To have a route suggested between the different records, tick :guilabel:`Enable Routing` and select which field should be used to sort records for the routing." msgstr "" @@ -1977,75 +2000,75 @@ msgstr "" msgid "Task model's Map view" msgstr "" -#: ../../content/applications/studio/views.rst:187 +#: ../../content/applications/studio/views.rst:197 msgid "Timeline views" msgstr "" -#: ../../content/applications/studio/views.rst:190 +#: ../../content/applications/studio/views.rst:200 msgid "When you first activate one of the timeline views, you need to select which :ref:`Date ` or :ref:`Date & Time ` fields on your model should be used to define when the records start and stop in order to display them on the view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop Date Field` after activating the view." msgstr "" -#: ../../content/applications/studio/views.rst:201 +#: ../../content/applications/studio/views.rst:211 msgid "Calendar" msgstr "" -#: ../../content/applications/studio/views.rst:203 -msgid "The :guilabel:`Calendar` view is used to overview and manage records inside a calendar." +#: ../../content/applications/studio/views.rst:213 +msgid "The :guilabel:`Calendar` :icon:`fa-calendar` view is used to overview and manage records inside a calendar." msgstr "" -#: ../../content/applications/studio/views.rst:205 +#: ../../content/applications/studio/views.rst:216 msgid "To create records directly within the view instead of opening the :ref:`Form view `, enable :guilabel:`Quick Create`." msgstr "" -#: ../../content/applications/studio/views.rst:209 +#: ../../content/applications/studio/views.rst:220 msgid "This only works on specific models that can be *quick-created* using only a *name*. However, most models do not support quick creation and open the :guilabel:`Form` view to fill in the required fields." msgstr "" -#: ../../content/applications/studio/views.rst:213 +#: ../../content/applications/studio/views.rst:224 msgid "To color records on the calendar, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color." msgstr "" -#: ../../content/applications/studio/views.rst:217 +#: ../../content/applications/studio/views.rst:228 msgid "As the number of colors is limited, the same color can end up being assigned to different values." msgstr "" -#: ../../content/applications/studio/views.rst:220 +#: ../../content/applications/studio/views.rst:231 msgid "To display events lasting the whole day at the top of the calendar, select a :ref:`Checkbox field ` that specifies if the event lasts the whole day." msgstr "" -#: ../../content/applications/studio/views.rst:223 +#: ../../content/applications/studio/views.rst:234 msgid "To choose the default time scale used to display events, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Display Mode`." msgstr "" -#: ../../content/applications/studio/views.rst:227 -msgid "You can also use :guilabel:`Delay Field` to display the duration of the event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on the model which specifies the duration of the event. However, if you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken into account." +#: ../../content/applications/studio/views.rst:238 +msgid "You can also use a :guilabel:`Delay Field` to display the duration of the event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on the model which specifies the duration of the event. However, if you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken into account." msgstr "" #: ../../content/applications/studio/views.rst:0 msgid "Calendar Event model's Calendar view" msgstr "" -#: ../../content/applications/studio/views.rst:242 +#: ../../content/applications/studio/views.rst:252 msgid "Cohort" msgstr "" -#: ../../content/applications/studio/views.rst:244 -msgid "The :guilabel:`Cohort` view is used to examine the life cycle of records over a time period. For example, it is used in the Subscriptions app to view the subscriptions' retention rate." +#: ../../content/applications/studio/views.rst:254 +msgid "The :guilabel:`Cohort` :icon:`oi-view-cohort` view is used to examine the life cycle of records over a time period. For example, it is used in the Subscriptions app to view the subscriptions' retention rate." msgstr "" -#: ../../content/applications/studio/views.rst:247 +#: ../../content/applications/studio/views.rst:258 msgid "To display a measure (i.e., the aggregated value of a given field) by default on the view, select a :guilabel:`Measure Field`." msgstr "" -#: ../../content/applications/studio/views.rst:249 +#: ../../content/applications/studio/views.rst:260 msgid "To choose which time interval is used by default to group results, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Interval`." msgstr "" -#: ../../content/applications/studio/views.rst:251 +#: ../../content/applications/studio/views.rst:262 msgid "To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` :dfn:`the percentage of records staying over a period of time, it starts at 100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of records moving out over a period of time - it starts at 0% and increases with time`." msgstr "" -#: ../../content/applications/studio/views.rst:255 +#: ../../content/applications/studio/views.rst:266 msgid "To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` (from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is used." msgstr "" @@ -2053,51 +2076,51 @@ msgstr "" msgid "Subscription model's Cohort view" msgstr "" -#: ../../content/applications/studio/views.rst:268 +#: ../../content/applications/studio/views.rst:278 msgid "Gantt" msgstr "" -#: ../../content/applications/studio/views.rst:270 -msgid "The :guilabel:`Gantt` view is used to forecast and examine the overall progress of records. Records are represented by a bar under a time scale." -msgstr "" - -#: ../../content/applications/studio/views.rst:273 -msgid "To prevent users from creating or editing records, untick :guilabel:`Can Create` or :guilabel:`Can Edit`." -msgstr "" - -#: ../../content/applications/studio/views.rst:275 -msgid "To fill cells in gray whenever a record should not be created there (e.g., on weekends for employees), tick :guilabel:`Display Unavailability`." -msgstr "" - -#: ../../content/applications/studio/views.rst:279 -msgid "The underlying model must support this feature, and support for it cannot be added using Studio. It is supported for the Project, Time Off, Planning, and Manufacturing apps." -msgstr "" - -#: ../../content/applications/studio/views.rst:282 -msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +#: ../../content/applications/studio/views.rst:280 +msgid "The :guilabel:`Gantt` :icon:`fa-tasks` view is used to forecast and examine the overall progress of records. Records are represented by a bar under a time scale." msgstr "" #: ../../content/applications/studio/views.rst:283 -msgid "To collapse multiple records in a single row, tick :guilabel:`Collapse First Level`." +msgid "To prevent users from creating or editing records, untick :guilabel:`Can Create` or :guilabel:`Can Edit`." msgstr "" -#: ../../content/applications/studio/views.rst:284 -msgid "To choose which way records are grouped by default on rows (e.g., per employee or project), select a field under :guilabel:`Default Group by`." +#: ../../content/applications/studio/views.rst:285 +msgid "To fill cells in gray whenever a record should not be created there (e.g., on weekends for employees), tick :guilabel:`Display Unavailability`." msgstr "" -#: ../../content/applications/studio/views.rst:286 -msgid "To define a default time scale to view records, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Scale`." -msgstr "" - -#: ../../content/applications/studio/views.rst:288 -msgid "To color records on the view, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color." +#: ../../content/applications/studio/views.rst:289 +msgid "The underlying model must support this feature, and support for it cannot be added using Studio. It is supported for the Project, Time Off, Planning, and Manufacturing apps." msgstr "" #: ../../content/applications/studio/views.rst:292 -msgid "As the number of colors is limited, the same color can be assigned to different values." +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/studio/views.rst:293 +msgid "To collapse multiple records in a single row, tick :guilabel:`Collapse First Level`." msgstr "" #: ../../content/applications/studio/views.rst:294 +msgid "To choose which way records are grouped by default on rows (e.g., per employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/studio/views.rst:296 +msgid "To define a default time scale to view records, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/studio/views.rst:298 +msgid "To color records on the view, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:302 +msgid "As the number of colors is limited, the same color can be assigned to different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:304 msgid "To specify with which degree of precision each time scale should be divided by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or :guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or :guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month Precision`." msgstr "" @@ -2105,31 +2128,31 @@ msgstr "" msgid "Planning Shift model's Gantt view" msgstr "" -#: ../../content/applications/studio/views.rst:308 +#: ../../content/applications/studio/views.rst:317 msgid "Reporting views" msgstr "" -#: ../../content/applications/studio/views.rst:317 +#: ../../content/applications/studio/views.rst:326 msgid "Pivot" msgstr "" -#: ../../content/applications/studio/views.rst:319 -msgid "The :guilabel:`Pivot` view is used to explore and analyze the data contained in records in an interactive manner. It is especially useful to aggregate numeric data, create categories, and drill down the data by expanding and collapsing different levels of data." +#: ../../content/applications/studio/views.rst:328 +msgid "The :guilabel:`Pivot` :icon:`oi-view-pivot` view is used to explore and analyze the data contained in records in an interactive manner. It is especially useful to aggregate numeric data, create categories, and drill down the data by expanding and collapsing different levels of data." msgstr "" -#: ../../content/applications/studio/views.rst:323 +#: ../../content/applications/studio/views.rst:332 msgid "To access all records whose data is aggregated under a cell, tick :guilabel:`Access records from cell`." msgstr "" -#: ../../content/applications/studio/views.rst:325 +#: ../../content/applications/studio/views.rst:334 msgid "To divide the data into different categories, select field(s) under :guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or :guilabel:`Row grouping - Second level`." msgstr "" -#: ../../content/applications/studio/views.rst:327 +#: ../../content/applications/studio/views.rst:336 msgid "To add different types of data to be measured using the view, select a field under :guilabel:`Measures`." msgstr "" -#: ../../content/applications/studio/views.rst:329 +#: ../../content/applications/studio/views.rst:338 msgid "To display a count of records that made up the aggregated data in a cell, tick :guilabel:`Display count`." msgstr "" @@ -2137,50 +2160,38 @@ msgstr "" msgid "Purchase Report model's Pivot view" msgstr "" -#: ../../content/applications/studio/views.rst:341 +#: ../../content/applications/studio/views.rst:349 msgid "Graph" msgstr "" -#: ../../content/applications/studio/views.rst:343 -msgid "The :guilabel:`Graph` view is used to showcase data from records in a bar, line, or pie chart." -msgstr "" - -#: ../../content/applications/studio/views.rst:345 -msgid "To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` under :guilabel:`Type`." -msgstr "" - -#: ../../content/applications/studio/views.rst:347 -msgid "To choose a default data dimension (category), select a field under :guilabel:`First dimension` and, if needed, another under :guilabel:`Second dimension`." -msgstr "" - -#: ../../content/applications/studio/views.rst:349 -msgid "To select a default type of data to be measured using the view, select a field under :guilabel:`Measure`." -msgstr "" - #: ../../content/applications/studio/views.rst:351 -msgid "*For Bar and Line charts only*: To sort the different data categories by their value, select :guilabel:`Ascending` (from lowest to highest value) or :guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgid "The :guilabel:`Graph` :icon:`fa-area-chart` view is used to showcase data from records in a bar, line, or pie chart." msgstr "" #: ../../content/applications/studio/views.rst:354 -msgid "*For Bar and Pie charts only*: To access all records whose data is aggregated under a data category on the chart, tick :guilabel:`Access records from graph`." +msgid "To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` under :guilabel:`Type`." msgstr "" #: ../../content/applications/studio/views.rst:356 +msgid "To choose a default data dimension (category), select a field under :guilabel:`First dimension` and, if needed, another under :guilabel:`Second dimension`." +msgstr "" + +#: ../../content/applications/studio/views.rst:358 +msgid "To select a default type of data to be measured using the view, select a field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/studio/views.rst:360 +msgid "*For Bar and Line charts only*: To sort the different data categories by their value, select :guilabel:`Ascending` (from lowest to highest value) or :guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/studio/views.rst:363 +msgid "*For Bar and Pie charts only*: To access all records whose data is aggregated under a data category on the chart, tick :guilabel:`Access records from graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:365 msgid "*For Bar charts only*: When using two data dimensions (categories), display the two columns on top of each other by default by ticking :guilabel:`Stacked graph`." msgstr "" #: ../../content/applications/studio/views.rst:0 msgid "Sales Analysis Report model's Bar chart on Graph view" msgstr "" - -#: ../../content/applications/studio/views.rst:368 -msgid "Dashboard" -msgstr "" - -#: ../../content/applications/studio/views.rst:370 -msgid "The :guilabel:`Dashboard` view is used to display multiple reporting views and key performance indicators. Which elements are displayed on the view depends on the configuration of the other reporting views." -msgstr "" - -#: ../../content/applications/studio/views.rst:0 -msgid "Sales Analysis Report model's Dashboard view" -msgstr "" diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index f2eb566f1..66f16047e 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 13:30+0000\n" +"POT-Creation-Date: 2024-08-21 11:43+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -229,7 +229,7 @@ msgid "Run a modern open-source online store with Odoo eCommerce. Learn how to s msgstr "" #: ../../content/applications/websites/ecommerce.rst:14 -#: ../../content/applications/websites/website.rst:14 +#: ../../content/applications/websites/website.rst:47 msgid "Odoo offers a :ref:`free custom domain name ` to all Odoo Online databases for one year. Visitors can then access your website with an address such as `www.example.com` rather than the default `example.odoo.com`." msgstr "" @@ -238,12 +238,12 @@ msgid ":doc:`Website Documentation `" msgstr "" #: ../../content/applications/websites/ecommerce.rst:20 -#: ../../content/applications/websites/website.rst:19 +#: ../../content/applications/websites/website.rst:52 msgid "`Odoo Tutorials: Website `_" msgstr "" #: ../../content/applications/websites/ecommerce.rst:21 -#: ../../content/applications/websites/website.rst:20 +#: ../../content/applications/websites/website.rst:53 msgid "`Odoo Tutorials: eCommerce `_" msgstr "" @@ -605,72 +605,74 @@ msgid "Own shipping methods" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:17 -msgid "You can create your own custom shipping methods and define rules to compute shipping costs. To do so, go to :menuselection:`Website --> Configuration --> Shipping Methods`, and either select an **existing** shipping method, or :guilabel:`Create` one. When creating a shipping method, you can choose between :doc:`Fixed Price `, :doc:`Based on Rules `, and :guilabel:`Pickup in store`." +msgid "You can create your own custom shipping methods and define rules to compute shipping costs. To do so, go to :menuselection:`Website --> Configuration --> Shipping Methods`, and either select an **existing** shipping method, or :guilabel:`Create` one. When creating a shipping method, you can choose between :ref:`Fixed Price `, :ref:`Based on Rules `, and :guilabel:`Pickup in store`." msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:26 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:24 msgid "Pickup in store" msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:28 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:26 msgid ":guilabel:`Pickup in store` must first be **enabled** in the settings (:menuselection:`Website --> Configuration --> Settings --> Shipping section)` by checking :guilabel:`On Site Payments & Picking`. Once enabled, you can select and :guilabel:`Customize Pickup Sites`. :guilabel:`Picking sites` can be made **website-specific**, but are by default available for *all* websites." msgstr "" +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:32 +msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:33 +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:83 +msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing`" +msgstr "" + #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:34 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method`" +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:85 +msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack`" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:35 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing`" +msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel`" msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:36 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack`" -msgstr "" - -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:37 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel`" -msgstr "" - -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:42 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:40 msgid "Shipping providers" msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:44 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:42 msgid "Another solution is to use one of the integrations with an existing shipping provider. The advantage of using an integration is that delivery costs are automatically computed based on each order as well as generating shipping labels." msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:51 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:49 msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:52 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:50 msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials`" msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:53 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:51 msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials`" msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:54 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:52 #: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:84 msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels`" msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:57 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:55 #: ../../content/applications/websites/ecommerce/products.rst:205 msgid "Website availability" msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:59 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:57 msgid "Shipping methods can be made available on **specific** websites *only*, if desired. To do so, go to :menuselection:`Website --> Configuration --> Settings --> Shipping Methods`, and select the desired **shipping method**. In the :guilabel:`Website` field, set the website you want the shipping method to be restrained to. Leave the field **empty** for the method to be available on *all* websites." msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:65 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:63 msgid "Delivery method at checkout" msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:67 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:65 msgid "Customers can choose the shipping method at the end of the checkout process, at the :guilabel:`Confirm Order` step." msgstr "" @@ -951,14 +953,6 @@ msgstr "" msgid "If customers are allowed to pay when picking up their order in stores or by wire transfer, the quotation is **not** be confirmed and the stock is **not** be reserved. Orders must be confirmed manually to reserve products in stock." msgstr "" -#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:83 -msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing`" -msgstr "" - -#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:85 -msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack`" -msgstr "" - #: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:88 msgid "Returns and refunds" msgstr "" @@ -1769,7 +1763,7 @@ msgid "Price per unit" msgstr "" #: ../../content/applications/websites/ecommerce/products/price_management.rst:55 -msgid "It is possible to display a :doc:`price per unit ` on the product page. To do that, go to :menuselection:`Website --> Configuration --> Settings` and enable :guilabel:`Product Reference Price` under the :guilabel:`Shop - Products` section. When enabled, ensure an amount is set in the :guilabel:`Base Unit Count` field of the **product template**, and in the :guilabel:`Sales Price`." +msgid "It is possible to display a :doc:`price per unit <../../../inventory_and_mrp/inventory/product_management/configure/uom>` on the product page. To do that, go to :menuselection:`Website --> Configuration --> Settings` and enable :guilabel:`Product Reference Price` under the :guilabel:`Shop - Products` section. When enabled, ensure an amount is set in the :guilabel:`Base Unit Count` field of the **product template**, and in the :guilabel:`Sales Price`." msgstr "" #: ../../content/applications/websites/ecommerce/products/price_management.rst:-1 @@ -1789,7 +1783,7 @@ msgid "Pay attention that having the price per unit may be **mandatory** in some msgstr "" #: ../../content/applications/websites/ecommerce/products/price_management.rst:77 -msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom`" +msgid ":doc:`../../../inventory_and_mrp/inventory/product_management/configure/uom`" msgstr "" #: ../../content/applications/websites/ecommerce/products/price_management.rst:82 @@ -3006,7 +3000,7 @@ msgid "Live Chat" msgstr "" #: ../../content/applications/websites/livechat.rst:7 -msgid "Odoo *Live Chat* allows users to communicate with website visitors in real-time. With *Live Chat*, leads can be qualified for their sales potential, support questions can be answered quickly, and issues can be directed to the appropriate team for further investigation or follow up. *Live Chat* also provides the opportunity for instant feedback from customers." +msgid "Odoo **Live Chat** allows users to communicate with website visitors in real-time. With **Live Chat**, leads can be qualified for their sales potential, support questions can be answered quickly, and issues can be directed to the appropriate team for further investigation or follow up. **Live Chat** also provides the opportunity for instant feedback from customers." msgstr "" #: ../../content/applications/websites/livechat.rst:13 @@ -3014,11 +3008,11 @@ msgid "Enable Live Chat" msgstr "" #: ../../content/applications/websites/livechat.rst:15 -msgid "The *Live Chat* application can be installed multiple ways:" +msgid "The **Live Chat** application can be installed multiple ways:" msgstr "" #: ../../content/applications/websites/livechat.rst:17 -msgid "Go to :menuselection:`Apps application --> Live Chat` and click :guilabel:`Install`." +msgid "Go to :menuselection:`Apps application`, search `Live Chat`, and click :guilabel:`Install`." msgstr "" #: ../../content/applications/websites/livechat.rst:18 @@ -3034,7 +3028,7 @@ msgid "View of the settings page and the live chat feature for Odoo Live Chat." msgstr "" #: ../../content/applications/websites/livechat.rst:30 -msgid "After the *Live Chat* application is installed, a live chat *Channel* is created by default." +msgid "After the **Live Chat** application is installed, a live chat *Channel* is created, by default." msgstr "" #: ../../content/applications/websites/livechat.rst:33 @@ -3078,15 +3072,15 @@ msgid "Current operators can be edited, or removed, by clicking on their respect msgstr "" #: ../../content/applications/websites/livechat.rst:76 -msgid "Click :guilabel:`Add` to reveal an :guilabel:`Add: Operators` modal." +msgid "Click :guilabel:`Add` to reveal an :guilabel:`Add: Operators` pop-up window." msgstr "" #: ../../content/applications/websites/livechat.rst:78 -msgid "In the modal, scroll to find the desired users, or enter their name in the :guilabel:`Search...` bar. Then, click the checkbox next to the users to be added, and click :guilabel:`Select`." +msgid "In the pop-up window, scroll to find the desired users, or enter their name in the search bar. Then, tick the checkbox next to the users to be added, and click :guilabel:`Select`." msgstr "" #: ../../content/applications/websites/livechat.rst:81 -msgid "New operators can be created and added to the list directly from this modal, as well, by clicking :guilabel:`New`, and filling out the :guilabel:`Create Operators` form. When the form is complete, click :guilabel:`Save & Close`, or :guilabel:`Save & New` for multiple record creations." +msgid "New operators can be created and added to the list directly from this pop-up window, as well, by clicking :guilabel:`New`, and filling out the :guilabel:`Create Operators` form. When the form is complete, click :guilabel:`Save & Close`, or :guilabel:`Save & New` for multiple record creations." msgstr "" #: ../../content/applications/websites/livechat.rst:86 @@ -3102,7 +3096,7 @@ msgid "Livechat button" msgstr "" #: ../../content/applications/websites/livechat.rst:104 -msgid "The *Livechat Button* is the icon that appears in the bottom corner of the website." +msgid "The *Livechat Button* is the icon that appears in the bottom-right corner of the website." msgstr "" #: ../../content/applications/websites/livechat.rst:-1 @@ -3122,7 +3116,7 @@ msgid "Color selection, for the button or header, can be made manually using a s msgstr "" #: ../../content/applications/websites/livechat.rst:126 -msgid "Livechat window" +msgid "Livechat Window" msgstr "" #: ../../content/applications/websites/livechat.rst:128 @@ -3150,106 +3144,114 @@ msgid "Channel Rules tab" msgstr "" #: ../../content/applications/websites/livechat.rst:153 -msgid "The :guilabel:`Channel Rules` tab on the live chat channel detail form determines when the live chat window opens on the website, by configuring when a :guilabel:`URL Regex` action is triggered, such as a page visit." +msgid "To configure which website user actions open the live chat window, go to the :guilabel:`Channel Rules` tab on the live chat channel detail form." msgstr "" -#: ../../content/applications/websites/livechat.rst:157 -msgid "To create a new channel rule, click :guilabel:`Add a line`. This opens the :guilabel:`Create Rules` modal." +#: ../../content/applications/websites/livechat.rst:156 +msgid "To create a new channel rule, click :guilabel:`Add a line`. This opens the :guilabel:`Create Rules` pop-up window." msgstr "" #: ../../content/applications/websites/livechat.rst:-1 msgid "View of a channel's rules form for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:165 +#: ../../content/applications/websites/livechat.rst:164 msgid "Create new rules" msgstr "" -#: ../../content/applications/websites/livechat.rst:167 -msgid "Fill out the fields on the :guilabel:`Create Rules` modal, as instructed below. Then, click :guilabel:`Save & Close`." +#: ../../content/applications/websites/livechat.rst:166 +msgid "Fill out the fields on the :guilabel:`Create Rules` pop-up window as instructed below, then click :guilabel:`Save & Close`." msgstr "" -#: ../../content/applications/websites/livechat.rst:172 +#: ../../content/applications/websites/livechat.rst:171 msgid "Live Chat Button" msgstr "" -#: ../../content/applications/websites/livechat.rst:174 -msgid "The *Live Chat Button* is the icon that appears in the bottom corner of the website. Select from one of the following display options:" +#: ../../content/applications/websites/livechat.rst:173 +msgid "The *Livechat Button* is the icon that appears in the bottom-right corner of the website. Select from one of the following display options:" msgstr "" -#: ../../content/applications/websites/livechat.rst:177 +#: ../../content/applications/websites/livechat.rst:176 msgid ":guilabel:`Show`: displays the chat button on the page." msgstr "" -#: ../../content/applications/websites/livechat.rst:178 +#: ../../content/applications/websites/livechat.rst:177 msgid ":guilabel:`Show with notification`: displays the chat button, as well as a floating text bubble next to the button." msgstr "" -#: ../../content/applications/websites/livechat.rst:180 -msgid ":guilabel:`Open automatically`: displays the button and automatically opens the chat window after a specified amount of time (designated in the :guilabel:`Open automatically timer` field, which is revealed when selecting this option)." +#: ../../content/applications/websites/livechat.rst:179 +msgid ":guilabel:`Open automatically`: displays the button, and automatically opens the chat window after a specified amount of time (designated in the :guilabel:`Open automatically timer` field, that appears when this option is selected)." msgstr "" -#: ../../content/applications/websites/livechat.rst:183 +#: ../../content/applications/websites/livechat.rst:182 msgid ":guilabel:`Hide`: hides the chat button on the page." msgstr "" -#: ../../content/applications/websites/livechat.rst:185 +#: ../../content/applications/websites/livechat.rst:184 msgid "Chatbot" msgstr "" -#: ../../content/applications/websites/livechat.rst:187 +#: ../../content/applications/websites/livechat.rst:186 msgid "To include a :doc:`Chatbot ` on this channel, select it from the drop-down menu. If the chatbot should only be active when no operators are active, check the box labeled :guilabel:`Enabled only if no operator`." msgstr "" -#: ../../content/applications/websites/livechat.rst:191 +#: ../../content/applications/websites/livechat.rst:190 msgid "The :guilabel:`Enabled only if no operator` field is **only** visible if a chatbot is selected in the :guilabel:`Chatbot` field." msgstr "" -#: ../../content/applications/websites/livechat.rst:194 +#: ../../content/applications/websites/livechat.rst:193 msgid "URL Regex" msgstr "" -#: ../../content/applications/websites/livechat.rst:196 +#: ../../content/applications/websites/livechat.rst:195 msgid "The *URL Regex* specifies the web pages where this rule should be applied. In the :guilabel:`URL Regex` field, input the relative URL of the page where the chat button should appear." msgstr "" -#: ../../content/applications/websites/livechat.rst:200 -msgid "Open automatically timer" +#: ../../content/applications/websites/livechat.rst:199 +msgid "For example, to apply the rule to the URL, `https://mydatabse.odoo.com/shop`, enter `/shop` to the :guilabel:`URL Regex` field." msgstr "" #: ../../content/applications/websites/livechat.rst:202 +msgid "To apply the rule to *all* pages on the database, enter `/` in the :guilabel:`URL Regex` field." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:205 +msgid "Open automatically timer" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:207 msgid "This field designates the amount of time (in seconds) a page should be open before the chat window opens. This field **only** appears if the :guilabel:`Live Chat Button` for this rule is set to :guilabel:`Open automatically`." msgstr "" -#: ../../content/applications/websites/livechat.rst:206 +#: ../../content/applications/websites/livechat.rst:211 msgid "Country" msgstr "" -#: ../../content/applications/websites/livechat.rst:208 -msgid "If this channel should only be available to site visitors in specific countries, add them to the :guilabel:`Country` field. If this field is left blank, the channel is available to all site visitors, regardless of location." +#: ../../content/applications/websites/livechat.rst:213 +msgid "If this channel should **only** be available to site visitors in specific countries, add them to the :guilabel:`Country` field. If this field is left blank, the channel is available to all site visitors, regardless of location." msgstr "" -#: ../../content/applications/websites/livechat.rst:213 +#: ../../content/applications/websites/livechat.rst:218 msgid "In order to track the geographical location of visitors, *GeoIP* **must** be installed on the database. While this feature is installed by default on *Odoo Online* databases, *On-Premise* databases require additional :doc:`setup steps `." msgstr "" -#: ../../content/applications/websites/livechat.rst:220 +#: ../../content/applications/websites/livechat.rst:225 msgid "Widget tab" msgstr "" -#: ../../content/applications/websites/livechat.rst:222 +#: ../../content/applications/websites/livechat.rst:227 msgid "The :guilabel:`Widget` tab on the live chat channel detail form provides the code for a website widget. This code can be added to a website to provide access to a live chat window." msgstr "" -#: ../../content/applications/websites/livechat.rst:226 +#: ../../content/applications/websites/livechat.rst:231 msgid "The live chat widget can be added to websites created through Odoo by navigating to :menuselection:`Website app --> Configuration --> Settings`. Then, scroll to the :menuselection:`Email & Marketing` section. In the :guilabel:`Channel` field, select the channel to add to the site. Click :guilabel:`Save` to apply." msgstr "" -#: ../../content/applications/websites/livechat.rst:231 +#: ../../content/applications/websites/livechat.rst:236 msgid "To add the widget to a website created on a third-party platform, click the first :guilabel:`COPY` button on the :guilabel:`Widget` tab, and paste the code into the `` tag on the site." msgstr "" -#: ../../content/applications/websites/livechat.rst:234 +#: ../../content/applications/websites/livechat.rst:239 msgid "Likewise, to send a live chat session to a customer, click the second :guilabel:`COPY` button on the :guilabel:`Widget` tab. This link can be sent directly to a customer. When they click the link, they are redirected to a new chat window." msgstr "" @@ -3257,23 +3259,23 @@ msgstr "" msgid "View of the widget tab for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:243 +#: ../../content/applications/websites/livechat.rst:248 msgid ":doc:`../productivity/discuss`" msgstr "" -#: ../../content/applications/websites/livechat.rst:244 +#: ../../content/applications/websites/livechat.rst:249 msgid ":doc:`livechat/responses`" msgstr "" -#: ../../content/applications/websites/livechat.rst:245 +#: ../../content/applications/websites/livechat.rst:250 msgid ":doc:`livechat/ratings`" msgstr "" -#: ../../content/applications/websites/livechat.rst:246 +#: ../../content/applications/websites/livechat.rst:251 msgid ":doc:`livechat/chatbots`" msgstr "" -#: ../../content/applications/websites/livechat.rst:247 +#: ../../content/applications/websites/livechat.rst:252 msgid ":doc:`livechat/participate`" msgstr "" @@ -4133,7 +4135,7 @@ msgid "Commands and canned responses" msgstr "" #: ../../content/applications/websites/livechat/responses.rst:5 -msgid "In the Odoo *Live Chat* application, *commands* allow the user to perform specific actions both inside the chat window, and through other Odoo applications. The *Live Chat* app also includes *canned responses*. These are customized, preconfigured substitutions that allow users to replace shortcut entries in place of longer, well-thought out responses to some of the most common questions and comments." +msgid "In the Odoo **Live Chat** application, *commands* allow the user to perform specific actions both inside the chat window, and through other Odoo applications. The **Live Chat** app also includes *canned responses*. These are customized, preconfigured substitutions that allow users to replace shortcut entries in place of longer, well-thought out responses to some of the most common questions and comments." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:11 @@ -4173,50 +4175,42 @@ msgid "Type `@username` to mention a user in the conversation. A notification wi msgstr "" #: ../../content/applications/websites/livechat/responses.rst:45 -msgid "Type `#channel` to mention a *Discuss* channel." -msgstr "" - -#: ../../content/applications/websites/livechat/responses.rst:46 msgid "Type `/command` to execute a command." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:47 +#: ../../content/applications/websites/livechat/responses.rst:46 msgid "Type `:shortcut` to insert a :ref:`canned response `." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:-1 -msgid "View of the message generated from using the /help command in Odoo Live Chat." -msgstr "" - -#: ../../content/applications/websites/livechat/responses.rst:54 +#: ../../content/applications/websites/livechat/responses.rst:49 msgid ":doc:`/applications/productivity/discuss`" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:55 +#: ../../content/applications/websites/livechat/responses.rst:50 msgid ":doc:`/applications/productivity/discuss/team_communication`" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:58 +#: ../../content/applications/websites/livechat/responses.rst:53 msgid "Ticket & search tickets" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:60 +#: ../../content/applications/websites/livechat/responses.rst:55 msgid "The `/ticket` and `/search_tickets` commands allow operators to create helpdesk tickets directly from a conversation, and search through existing tickets by keyword or ticket number." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:64 -msgid "The `/ticket` and `/search_tickets` commands can **only** be used if the *Helpdesk* app has been installed, and *Live Chat* has been activated on a *Helpdesk* team. To activate *Live Chat*, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`, and select a team. Scroll to the :guilabel:`Channels` section, and check the box labeled, :guilabel:`Live Chat`." +#: ../../content/applications/websites/livechat/responses.rst:59 +msgid "The `/ticket` and `/search_tickets` commands can **only** be used if the **Helpdesk** app has been installed, and *Live Chat* has been activated on a *Helpdesk* team. To activate *Live Chat*, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`, and select a team. Scroll to the :guilabel:`Channels` section, and check the box labeled, :guilabel:`Live Chat`." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:72 +#: ../../content/applications/websites/livechat/responses.rst:67 msgid "Create a ticket from a live chat" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:74 +#: ../../content/applications/websites/livechat/responses.rst:69 msgid "If an operator types `/ticket` in the chat window, the conversation is used to create a *Helpdesk* ticket." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:77 +#: ../../content/applications/websites/livechat/responses.rst:72 msgid "After entering the `/ticket` command, type a title for the ticket into the chat window, then press `Enter`." msgstr "" @@ -4225,135 +4219,127 @@ msgstr "" msgid "View of the results from a helpdesk search in a Live Chat conversation." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:84 +#: ../../content/applications/websites/livechat/responses.rst:79 msgid "The newly created ticket will be added to the *Helpdesk* team that has live chat enabled. If more than one team has live chat enabled, the ticket will automatically be assigned based on the team's priority." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:88 +#: ../../content/applications/websites/livechat/responses.rst:83 msgid "The transcript from the conversation will be added to the new ticket, under the :guilabel:`Description` tab." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:91 -msgid "To access the new ticket, click on the link in the chat window, or go to the :menuselection:`Helpdesk app`, and click the :guilabel:`Tickets` button on the Kanban card for the appropriate team." +#: ../../content/applications/websites/livechat/responses.rst:86 +msgid "To access the new ticket, click on the link in the chat window, or go to the :menuselection:`Helpdesk app` and click the :guilabel:`Tickets` button on the Kanban card for the appropriate team." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:96 +#: ../../content/applications/websites/livechat/responses.rst:91 msgid "Search for a ticket from a live chat" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:98 +#: ../../content/applications/websites/livechat/responses.rst:93 msgid "If an operator types `/search_tickets` in the chat window, they can search through *Helpdesk* tickets, either by ticket number or keyword." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:101 +#: ../../content/applications/websites/livechat/responses.rst:96 msgid "After entering the `/search_tickets` command, type a keyword or ticket number, then press :kbd:`Enter`. If one or more related tickets are found, a list of links is generated in the conversation window." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:110 +#: ../../content/applications/websites/livechat/responses.rst:105 msgid "Results from the search command will only be seen by the operator, not the customer." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:113 +#: ../../content/applications/websites/livechat/responses.rst:108 msgid "History" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:115 -msgid "Typing `/history` in the chat window generates a list of the most recent pages the visitor has viewed on the website (up to fifteen pages)." +#: ../../content/applications/websites/livechat/responses.rst:110 +msgid "If an operator types `/history` in the chat window, it generates a list of the most recent pages the visitor has viewed on the website (up to 15)." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:-1 msgid "View of the results from a /history command in a Live Chat conversation." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:123 +#: ../../content/applications/websites/livechat/responses.rst:118 msgid "Lead" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:125 -msgid "By typing `/lead` in the chat window, an operator can create a *lead* in the *CRM* application." +#: ../../content/applications/websites/livechat/responses.rst:120 +msgid "By typing `/lead` in the chat window, an operator can create a *lead* in the **CRM** application." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:-1 msgid "View of the results from a /lead command in a Live Chat conversation." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:132 -msgid "The `/lead` command can only be used if the *CRM* app has been installed." +#: ../../content/applications/websites/livechat/responses.rst:127 +msgid "The `/lead` command can only be used if the **CRM** app has been installed." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:134 +#: ../../content/applications/websites/livechat/responses.rst:129 msgid "After typing `/lead`, create a title for this new lead, then press `Enter`. A link with the lead title appears. Click the link, or navigate to the :menuselection:`CRM` app to view the :guilabel:`Pipeline`." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:139 +#: ../../content/applications/websites/livechat/responses.rst:134 msgid "The link to the new lead can only be seen and accessed by the operator, not the customer." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:141 +#: ../../content/applications/websites/livechat/responses.rst:136 msgid "The transcript of that specific live chat conversation (where the lead was created) is added to the :guilabel:`Internal Notes` tab of the lead form." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:144 +#: ../../content/applications/websites/livechat/responses.rst:139 msgid "On the :guilabel:`Extra Information` tab of the lead form, the :guilabel:`Source` will be listed as :guilabel:`Livechat`." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:148 +#: ../../content/applications/websites/livechat/responses.rst:143 msgid "Leave" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:150 +#: ../../content/applications/websites/livechat/responses.rst:145 msgid "If an operator types `/leave` in the chat window, they can automatically exit the conversation. This command does not cause the customer to be removed from the conversation, nor does it automatically end the conversation." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:155 +#: ../../content/applications/websites/livechat/responses.rst:150 msgid ":doc:`/applications/sales/crm/acquire_leads`" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:156 +#: ../../content/applications/websites/livechat/responses.rst:151 msgid ":doc:`../../services/helpdesk`" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:161 +#: ../../content/applications/websites/livechat/responses.rst:156 msgid "Canned responses" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:163 -msgid "*Canned responses* are customizable inputs, where a typed shortcut populates a longer response. A user enters a keyword *shortcut*, which is then automatically replaced by the expanded *substitution* response. The shortcut is the keyword or key phrase that is to be replaced. The substitution is the longer message that replaces the shortcut." +#: ../../content/applications/websites/livechat/responses.rst:158 +msgid "*Canned responses* are customizable inputs where a *shortcut* stands in for a longer response. An operator will enter the shortcut, and it is automatically replaced by the expanded *substitution* response in the conversation." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:171 +#: ../../content/applications/websites/livechat/responses.rst:163 msgid "Create canned responses" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:173 +#: ../../content/applications/websites/livechat/responses.rst:165 msgid "To create a new canned response, go to :menuselection:`Live Chat app --> Configuration --> Canned Responses --> New`." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:176 +#: ../../content/applications/websites/livechat/responses.rst:168 msgid "Type a shortcut command in the :guilabel:`Shortcut` field. Next, click the :guilabel:`Substitution` field, and type the message that should replace the shortcut." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:180 -msgid "Try to connect the shortcut to the topic of the substitution. Not only does this make it easier to use the responses, it prevents the list of responses from becoming disorganized and overwhelming." +#: ../../content/applications/websites/livechat/responses.rst:172 +msgid "Try to connect the shortcut to the topic of the substitution. The easier it is for the operators to remember, the easier it is to use the canned responses in conversations." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:184 -msgid "In the :guilabel:`Description` field, add any information that provides context for this response, such as guidelines for when it should or should not be used." -msgstr "" - -#: ../../content/applications/websites/livechat/responses.rst:187 -msgid "The :guilabel:`Last Used` field keeps track of the date and time each response was most recently used. This field **cannot** be edited." -msgstr "" - -#: ../../content/applications/websites/livechat/responses.rst:191 +#: ../../content/applications/websites/livechat/responses.rst:176 msgid "Use canned responses in a live chat conversation" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:193 +#: ../../content/applications/websites/livechat/responses.rst:178 msgid "To use a canned response during a live chat conversation, type a colon (`:`) into the chat window, followed by the shortcut." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:197 +#: ../../content/applications/websites/livechat/responses.rst:182 msgid "An operator is chatting with a visitor. As soon as they type `:` they would see a list of available responses. They can manually select one from the list, or continue to type. If they want to use the canned response `'I am sorry to hear that.'`, they would type `:sorry`." msgstr "" @@ -4361,7 +4347,7 @@ msgstr "" msgid "View of a chat window and the use of a canned response in Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:206 +#: ../../content/applications/websites/livechat/responses.rst:191 msgid "Typing `:` into a chat window on its own will generate a list of available canned responses. Responses can be manually selected from the list, in addition to the use of shortcuts." msgstr "" @@ -4369,12 +4355,16 @@ msgstr "" msgid "View of a chat window and the list of available canned responses." msgstr "" -#: ../../content/applications/websites/website.rst:8 +#: ../../content/applications/websites/website.rst:7 msgid "Website" msgstr "" -#: ../../content/applications/websites/website.rst:10 -msgid "Discover the best **Open-Source Website Builder** and learn how to build beautiful websites that convert visitors into leads or revenues." +#: ../../content/applications/websites/website.rst:9 +msgid "**Odoo Website** offers a user-friendly platform for creating and managing your website. It includes various tools and features to help you design, publish, and maintain web pages without needing advanced technical skills. You can easily customize layouts, add multimedia content, and integrate with other Odoo apps to expand your website's functionality." +msgstr "" + +#: ../../content/applications/websites/website.rst:54 +msgid ":doc:`../general/integrations/unsplash`" msgstr "" #: ../../content/applications/websites/website/configuration/address_autocomplete.rst:3 @@ -4992,30 +4982,110 @@ msgid "Google Search Console is a free web service provided by Google that allow msgstr "" #: ../../content/applications/websites/website/configuration/google_search_console.rst:10 -msgid "To enable GSC, go to `Google Search Console `_, enter your domain or URL prefix, follow the instructions, and copy the code from Google." +msgid "To enable Google Search Console for your website, go to `Google Search Console `_. Then, select the property type :ref:`GSC-Domain` or :ref:`GSC-URL prefix`." msgstr "" #: ../../content/applications/websites/website/configuration/google_search_console.rst:-1 msgid "Google Search Console domain or URL prefix" msgstr "" -#: ../../content/applications/websites/website/configuration/google_search_console.rst:-1 -msgid "Verify domain or URL prefix" +#: ../../content/applications/websites/website/configuration/google_search_console.rst:20 +msgid "Domain property" msgstr "" -#: ../../content/applications/websites/website/configuration/google_search_console.rst:19 -msgid "Then, access your Odoo database, go to :menuselection:`Website --> Configuration --> Settings`, and enable :guilabel:`Google Search Console` in the :guilabel:`SEO` section. Paste the code in the dedicated field." +#: ../../content/applications/websites/website/configuration/google_search_console.rst:22 +msgid "A domain property in Search Console tracks all versions of your website, including subdomains and protocols (http/https). This comprehensive view allows you to analyze your overall website's search performance and make informed decisions to optimize its visibility. Enter the domain, e.g., `example.com` and click :guilabel:`Continue`." msgstr "" -#: ../../content/applications/websites/website/configuration/google_search_console.rst:-1 -msgid "Website Settings pasting GSC code" +#: ../../content/applications/websites/website/configuration/google_search_console.rst:28 +msgid "The domain property type can only be verified via `DNS record `_." msgstr "" -#: ../../content/applications/websites/website/configuration/google_search_console.rst:27 -msgid "To prevent Google from indexing both your custom domain name `www.example.com` and your original Odoo database URL `www.example.odoo.com`, :ref:`map your domain name with your Odoo website `." +#: ../../content/applications/websites/website/configuration/google_search_console.rst:30 +msgid "Google suggests creating at least one domain property to represent your site, as it is the most complete view of your website information." msgstr "" -#: ../../content/applications/websites/website/configuration/google_search_console.rst:32 +#: ../../content/applications/websites/website/configuration/google_search_console.rst:36 +msgid "URL prefix property" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:38 +msgid "This type of verification is usually simpler as you have multiple verification methods, such as using your existing Google Analytics or Tag Manager account. It also makes sense to view a section of your website separately. For example, if you work with a consultant on a specific part of your website, you might want to verify this part separately to limit access to your data. Enter the URL, e.g., `https://www.example.odoo.com` and click :guilabel:`Continue`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:46 +msgid "Site ownership verification" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:48 +msgid "Before using Google Search Console for your website, you must verify your site ownership. This verification process is a security measure that protects both you and Google. It ensures that only authorized users have access to sensitive data and that you have control over how your website is treated in Google Search." +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:53 +msgid "Five methods are available to do this:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:57 +msgid ":ref:`GSC-HTML-file-upload`" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:58 +msgid "`DNS record `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:59 +msgid "`HTML tag `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:60 +msgid "`Google Analytics tracking code `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:61 +msgid "`Google Tag Manager container snippet `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:64 +msgid "The best method for you depends on your comfort level and technical expertise. For beginners, using a file upload or HTML tag might be easiest. Those options are convenient if you already use Google Analytics or Tag Manager. You need to access your domain registrar's settings for domain verification." +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:72 +msgid "HTML file upload" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:74 +msgid "This method involves uploading an HTML file provided by Google containing the verification code you have to put in your Odoo's Website Settings. Google verifies ownership by checking for this code." +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:77 +msgid "Once you added your website URL under the URL prefix option and clicked :guilabel:`continue`, expand the HTML file section where you find a download :icon:`fa-download` button." +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:0 +msgid "HTML file download" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:83 +msgid "Download your HTML verification file and copy the verification code (e.g., `google123abc.html`)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:0 +msgid "Open and copy html file" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:88 +msgid "In your Odoo database, go to :menuselection:`Website --> Configuration --> Settings`, and enable :guilabel:`Google Search Console` in the :guilabel:`SEO` section. Paste the verification code (e.g., `google123abc.html`) in the dedicated field." +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:0 +msgid "Paste html code in Odoo" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:95 +msgid "In Google Search Console, click :guilabel:`Verify`. If you perform the steps above correctly, verification should be done immediately." +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:99 msgid ":doc:`domain_names`" msgstr "" @@ -6480,34 +6550,38 @@ msgid ":abbr:`GTM (Google Tag Manager)` is a tag management system that allows y msgstr "" #: ../../content/applications/websites/website/reporting/analytics.rst:140 -msgid "Google Tag Manager may not be compliant with local data protection regulations." +msgid "Some GTM tags use data layers (e.g., advanced eCommerce tracking data layers) to retrieve variables and send them to Google Analytics. Data layers are currently not managed in Odoo." msgstr "" #: ../../content/applications/websites/website/reporting/analytics.rst:142 -msgid "To use GTM, proceed as follows:" +msgid "Google Tag Manager may not be compliant with local data protection regulations." msgstr "" #: ../../content/applications/websites/website/reporting/analytics.rst:144 -msgid "Create or sign in to a Google account by going to https://tagmanager.google.com/." +msgid "To use GTM, proceed as follows:" msgstr "" #: ../../content/applications/websites/website/reporting/analytics.rst:146 -msgid "In the :guilabel:`Accounts` tab, click :guilabel:`Create account`." +msgid "Create or sign in to a Google account by going to https://tagmanager.google.com/." msgstr "" #: ../../content/applications/websites/website/reporting/analytics.rst:148 -msgid "Enter an :guilabel:`Account Name` and select the account's :guilabel:`Country`." +msgid "In the :guilabel:`Accounts` tab, click :guilabel:`Create account`." msgstr "" #: ../../content/applications/websites/website/reporting/analytics.rst:150 +msgid "Enter an :guilabel:`Account Name` and select the account's :guilabel:`Country`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:152 msgid "Enter your website's URL in the :guilabel:`Container name` field and select the :guilabel:`Target platform`." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:153 +#: ../../content/applications/websites/website/reporting/analytics.rst:155 msgid "Click :guilabel:`Create` and agree to the Terms of Service." msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:155 +#: ../../content/applications/websites/website/reporting/analytics.rst:157 msgid "Copy the `` and `` codes from the popup window. Then, go to your website, click :guilabel:`Edit`, go to the :guilabel:`Themes` tab, scroll down to the :guilabel:`Website Settings` section, then click :guilabel:`` and :guilabel:`` to paste the codes." msgstr "" @@ -6515,7 +6589,7 @@ msgstr "" msgid "Install Google Tag Manager" msgstr "" -#: ../../content/applications/websites/website/reporting/analytics.rst:164 +#: ../../content/applications/websites/website/reporting/analytics.rst:166 msgid "The data is collected in the marketing tools used to monitor the website (e.g., Google Analytics, Plausible, Facebook Pixel), not in Odoo." msgstr ""