diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 7f671cb07..9fea1dc97 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 10:38+0000\n" +"POT-Creation-Date: 2024-08-21 07:41+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" @@ -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 "" @@ -4908,197 +4929,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/finance.pot b/locale/sources/finance.pot index dd35c8ea2..17d117028 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 10:38+0000\n" +"POT-Creation-Date: 2024-08-21 07:41+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -119,7 +119,7 @@ msgid "The following financial :doc:`reports ` are availab msgstr "" #: ../../content/applications/finance/accounting.rst:127 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:996 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:995 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:418 msgid "Financial reports" msgstr "" @@ -158,12 +158,12 @@ msgid "Audit" msgstr "" #: ../../content/applications/finance/accounting.rst:139 -#: ../../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:141 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1038 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1037 msgid "Trial balance" msgstr "" @@ -340,56 +340,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 @@ -413,7 +413,7 @@ msgstr "" #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:9 #: ../../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 @@ -431,7 +431,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:8 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:415 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:25 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:762 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:761 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:21 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:34 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:603 @@ -440,9 +440,9 @@ msgstr "" #: ../../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 @@ -463,7 +463,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 "" @@ -471,45 +471,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 "" @@ -517,67 +517,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 "" @@ -585,11 +585,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 "" @@ -1910,6 +1910,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:167 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:71 @@ -3691,7 +3692,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 @@ -3715,7 +3716,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 @@ -3723,7 +3724,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 @@ -3731,28 +3732,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 @@ -3760,86 +3761,78 @@ 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 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 "" @@ -3847,83 +3840,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 "" @@ -4653,7 +4646,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:359 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:247 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:243 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1011 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1010 #: ../../content/applications/finance/fiscal_localizations/romania.rst:65 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:38 #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:41 @@ -6633,58 +6626,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 "" @@ -7663,7 +7656,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 @@ -10620,7 +10613,7 @@ msgstr "" #: ../../content/applications/finance/accounting/vendor_bills.rst:5 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:588 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:698 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:697 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:612 #: ../../content/applications/finance/fiscal_localizations/italy.rst:279 msgid "Vendor bills" @@ -11345,7 +11338,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 @@ -14563,8 +14556,8 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:255 #: ../../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 "" @@ -14604,7 +14597,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:225 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:267 #: ../../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:41 msgid "Contacts" msgstr "" @@ -15151,7 +15144,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 "" @@ -15399,7 +15392,7 @@ msgid ":guilabel:`Documents type 33` electronic invoice must have at least one i msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:421 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:922 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:921 msgid "Validation and DTE status" msgstr "" @@ -15507,34 +15500,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:517 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:516 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:522 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:521 msgid "Commercial validation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:524 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:523 msgid "Once the invoice has been sent to the customer:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:526 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:525 msgid ":guilabel:`DTE Partner Status` changes to :guilabel:`Sent`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:527 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:526 msgid "The customer must send a reception confirmation email." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:528 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:527 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:530 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:529 msgid "The field :guilabel:`DTE Acceptance Status` is updated automatically." msgstr "" @@ -15542,11 +15535,11 @@ msgstr "" msgid "Message with the commercial acceptance from the customer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:537 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:536 msgid "Processed for claimed invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:539 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:538 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 "" @@ -15554,13 +15547,13 @@ msgstr "" msgid "Invoice Commercial status updated to claimed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:549 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:548 #: ../../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:551 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:550 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 "" @@ -15620,33 +15613,33 @@ 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:583 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:582 msgid "The company's :abbr:`RUT (Rol Único Tributario)` number is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:584 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:583 msgid "The certificate owner :abbr:`RUT (Rol Único Tributario)` number is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:585 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:584 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:587 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:586 msgid "The resolution date is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:588 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:587 msgid "The resolution number is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:593 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:592 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:348 msgid "Credit notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:595 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:594 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 "" @@ -15654,16 +15647,16 @@ msgstr "" msgid "Creation of CAF for Credit notes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:607 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:663 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:606 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:662 msgid "Use cases" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:610 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:609 msgid "Cancel referenced document" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:612 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:611 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 "" @@ -15671,11 +15664,11 @@ msgstr "" msgid "Credit note canceling the referenced document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:622 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:621 msgid "Correct referenced document" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:624 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:623 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 "" @@ -15683,7 +15676,7 @@ msgstr "" msgid "Credit note correcting referenced document text." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:633 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:632 msgid "Odoo creates a credit note with the corrected text in an invoice and :guilabel:`Price` `0.00`." msgstr "" @@ -15691,15 +15684,15 @@ msgstr "" msgid "Credit note with the corrected value on the invoice lines." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:640 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:639 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:644 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:643 msgid "Corrects referenced document amount" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:646 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:645 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 "" @@ -15707,20 +15700,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:655 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:654 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:368 msgid "Debit notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:657 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:656 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:666 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:665 msgid "Add debt on invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:668 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:667 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 "" @@ -15728,7 +15721,7 @@ msgstr "" msgid "Debit note correcting referenced document amount." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:676 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:675 msgid "In this case Odoo automatically includes the :guilabel:`Source Invoice` in the :guilabel:`Cross Reference` tab." msgstr "" @@ -15736,15 +15729,15 @@ msgstr "" msgid "Automatic reference to invoice in a debit note." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:684 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:683 msgid "You can only add debit notes to an invoice already accepted by the SII." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:687 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:686 msgid "Cancel credit notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:689 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:688 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 "" @@ -15752,47 +15745,47 @@ msgstr "" msgid "Debit note to cancel the referenced document (credit note)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:700 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:699 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:703 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:702 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:705 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:704 msgid "Automatically send the reception acknowledgement to your vendor." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:706 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:705 msgid "Accept or claim the document and send this status to your vendor." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:709 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:708 msgid "Reception" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:711 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:710 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:714 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:713 msgid "The vendor bill maps all the information included in the XML." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:715 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:714 msgid "An email is sent to the vendor with the reception acknowledgement." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:716 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:715 msgid "The :guilabel:`DTE Status` is set as :guilabel:`Acuse de Recibido Enviado`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:719 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:718 msgid "Acceptation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:721 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:720 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 "" @@ -15800,11 +15793,11 @@ msgstr "" msgid "Button for accepting vendor bills." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:730 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:729 msgid "Claim" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:732 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:731 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 "" @@ -15813,122 +15806,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:742 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:741 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:747 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:746 msgid "Electronic purchase invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:749 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:748 msgid "The *electronic purchase invoice* is a feature included in the `l10n_cl_edi` module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:751 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:750 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:757 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:756 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:764 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:763 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:768 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:767 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:772 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:771 msgid ":guilabel:`Type`: select :guilabel:`Purchase` from the drop-down menu for vendor bill journals." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:773 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:772 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:777 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:776 msgid "Generate an electronic purchase invoice" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:779 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:778 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:782 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:781 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:785 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:784 msgid "After the vendor bill is posted:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:787 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:786 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:789 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:863 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:933 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:788 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:862 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:932 msgid "The :guilabel:`DTE SII Status` is set as :guilabel:`Pending to be sent`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:791 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:790 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:796 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:745 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:795 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:744 msgid "Delivery guide" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:798 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:797 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:803 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:802 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:807 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:806 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:811 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:810 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:817 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:816 msgid "Verify the following important information in the :guilabel:`Price for the Delivery Guide` configuration:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:820 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:819 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:822 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:821 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:824 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:823 msgid ":guilabel:`No show price`: no price is shown in the delivery guide." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:826 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:825 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:830 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:829 msgid "Delivery guide from a sales process" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:833 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:832 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:835 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:834 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 "" @@ -15936,11 +15929,11 @@ msgstr "" msgid "Create Delivery Guide button on a sales process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:843 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:842 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:846 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:845 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 "" @@ -15948,15 +15941,15 @@ msgstr "" msgid "First Delivery Guide number warning message." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:853 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:852 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:859 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:858 msgid "After the delivery guide is created:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:861 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:860 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax Document) is automatically created and added to the :guilabel:`chatter`." msgstr "" @@ -15964,11 +15957,11 @@ msgstr "" msgid "Chatter notes of Delivery Guide creation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:869 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:868 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:873 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:872 msgid "Once the delivery guide is sent, it may then be printed by clicking on the :guilabel:`Print Delivery Guide` button." msgstr "" @@ -15976,27 +15969,27 @@ msgstr "" msgid "Printing Delivery Guide PDF." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:880 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:879 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:886 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:885 msgid "Electronic receipt" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:888 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:887 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:893 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:892 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:897 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:896 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:903 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:902 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 "" @@ -16004,7 +15997,7 @@ msgstr "" msgid "Electronic Receipt module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:912 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:911 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 "" @@ -16012,15 +16005,15 @@ msgstr "" msgid "Document type 39 for Electronic Receipts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:924 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:923 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:929 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:928 msgid "After the receipt is posted:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:931 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:930 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax Document) is created automatically and added to the :guilabel:`chatter`." msgstr "" @@ -16028,35 +16021,35 @@ msgstr "" msgid "Electronic Receipts STE creation status." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:939 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:938 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:943 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:942 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:947 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:946 msgid "Electronic export of goods" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:949 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:948 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:954 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:953 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:957 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:956 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:963 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:962 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:968 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:967 msgid "Contact configurations" msgstr "" @@ -16064,11 +16057,11 @@ msgstr "" msgid "Taxpayer Type needed for the Electronic Exports of Goods module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:975 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:974 msgid "Chilean customs" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:977 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:976 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 "" @@ -16076,11 +16069,11 @@ msgstr "" msgid "Chilean customs fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:985 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:984 msgid "PDF report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:987 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:986 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 "" @@ -16088,15 +16081,15 @@ msgstr "" msgid "PDF report section for the Electronic Exports of Goods PDF Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:999 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:998 msgid "Balance tributario de 8 columnas" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1001 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1000 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:1005 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1004 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 "" @@ -16108,19 +16101,19 @@ msgstr "" msgid "Chilean Fiscal Balance (8 Columns)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1018 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1017 msgid "Propuesta F29" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1020 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1019 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:1025 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1024 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:1028 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1027 msgid "You can find this report in :menuselection:`Accounting --> Reporting --> Tax Reports` and selecting the :guilabel:`Report` option :guilabel:`Propuesta F29 (CL)`." msgstr "" @@ -16128,7 +16121,7 @@ msgstr "" msgid "Location of the Propuesta F29 (CL) Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1035 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1034 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 "" @@ -16136,7 +16129,7 @@ msgstr "" msgid "Default PPM and Proportional Factor for the Propuesta F29 Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1043 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1042 msgid "Or manually in the reports by clicking on the :guilabel:`✏️ (pencil)` icon." msgstr "" @@ -17860,7 +17853,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 @@ -21370,26 +21363,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 "" @@ -21397,11 +21390,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 "" @@ -21409,43 +21402,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 "" @@ -21453,63 +21446,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 "" @@ -21521,55 +21514,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 "" @@ -21577,19 +21570,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 "" @@ -21597,91 +21590,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 "" @@ -21689,23 +21682,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 "" @@ -21713,27 +21706,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 "" @@ -21741,23 +21734,23 @@ 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:725 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:724 msgid "Invoicing flow" 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 "" @@ -21765,63 +21758,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 "" @@ -21829,23 +21822,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 "" @@ -21853,19 +21846,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 "" @@ -21873,27 +21866,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 "" @@ -21901,15 +21894,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 "" @@ -21917,7 +21910,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 "" @@ -21925,59 +21918,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 "" @@ -21989,27 +21982,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 "" @@ -22017,11 +22010,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 "" @@ -22029,83 +22022,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 "" @@ -22113,23 +22106,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 "" @@ -22141,59 +22134,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 "" @@ -22205,7 +22198,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 "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index a2d41a07f..bf8c099db 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 10:38+0000\n" +"POT-Creation-Date: 2024-08-21 07:41+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1236,15 +1236,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 diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 15eaffa9a..94aa6d5fd 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 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 10:38+0000\n" +"POT-Creation-Date: 2024-08-21 07:41+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 "" @@ -214,109 +213,429 @@ msgid "To apply the inventory adjustment, click the green :guilabel:`✅ Apply` msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:3 -#: ../../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" +msgid "Default barcode nomenclature" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:5 -msgid "There are different situations in which barcode nomenclatures can be useful. A well-known use case is the one of a point of sale which sells products in bulk, in which the customers will scale their products themselves and get the printed barcode to stick on the product. This barcode will contain the weight of the product and help compute the price accordingly." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:10 +msgid "Define *barcode nomenclatures* to ensure Odoo correctly recognizes and categorizes barcodes. When scanned, a barcode matches the **first** rule with a matching pattern, based on regular expressions. A barcode is successfully read if its prefix and/or length matches the defined rule." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:13 -msgid "Create a Barcode Nomenclature" +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:14 +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:15 -msgid "Odoo supports Barcode Nomenclatures, which determine the mapping and interpretation of the encoded information. You can configure your barcode nomenclature being in :ref:`developer mode `. To do so, go to :menuselection:`Inventory --> Configuration --> Barcode Nomenclature`." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:21 +msgid "Barcodes are also commonly used with Odoo's **Inventory** and **Barcode** apps." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:20 -msgid "You can create a barcode nomenclature from there, and then add a line to create your first rule." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:23 +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:26 -msgid "The first step is to specify the **rule name**, for example Weight Barcode with 3 Decimals. You then have to specify the type for barcode nomenclature, in our case it will be Weighted Product." +#: ../../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:33 -msgid "The Barcode Pattern is a regular expression that defines the structure of the barcode. In this example 21 defines the products on which the rule will be applied, those are the numbers by which the product barcode should start. The 5 “dots” are the following numbers of the product barcode and are there simply to identify the product in question. The “N” define a number and the “D” define the decimals." +#: ../../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:39 +#: ../../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:18 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/uom.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:22 +#: ../../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_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/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:12 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack.rst:11 +#: ../../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/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:11 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:65 +#: ../../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/management/subcontracting.rst:23 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:11 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:15 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:13 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:10 +msgid "Configuration" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:40 -msgid "The encoding allows to specify the barcode encoding on which the rule should be applied." +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 "You can define different rules and order their priority thanks to the sequence. The first rule which matches the scanned barcode will be applied." +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:49 -msgid "Configure your Product" +#: ../../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:51 -msgid "The barcode of the product should start by “21”;" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:52 -msgid "The 5 “dots” are the other numbers of your product barcode, allowing to identify the product;" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:53 -msgid "The barcode should contain 0’s where you did defined D’s or N’s. In our case we need to set 5 zeros because we configured “21…..{NNDDD}”;" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:54 -msgid "In EAN-13, the last number is a check number, use an EAN13 generator to know which digit it should be in your case." +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 "In case you weight 1,5 Kg of pasta, the balance will print you the following barcode 2112345015002. If you scan this barcode in your POS or when receiving products in your barcode application, Odoo will automatically create a new line for the Pasta product for a quantity of 1.5 Kg. For the point of sale, a price depending on the quantity will also be computed." +msgid "Example: product weight barcode" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:70 -msgid "Rule Types" +#: ../../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: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: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:72 -msgid "**Priced Product**: allows you to identify the product and specify its price, used in POS." +#: ../../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 -msgid "**Discounted Product**: allows you to create one barcode per applied discount. You can then scan your product in the POS and then scan the discount barcode, discount will be applied on the normal price of the product." +#: ../../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 Product**: allows you to identify the product and specify its weight, used in both POS (in which the price is computed based on the weight) and in inventory." +msgid "Weighted Barcodes 3 Decimals" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:75 -msgid "**Client**: allows you to identify the customer, for example used with loyalty program." +msgid "(21)....{NNDDD}" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:76 -msgid "**Cashier**: allows you to identify the cashier when entering the POS." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:77 -msgid "**Location**: allows you to identify the location on a transfer when multi-location is activated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:78 -msgid "**Package**: allows you to identify packages on a transfer when packages are activated." +#: ../../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 "**Credit Card**: doesn’t need manual modification, exists for data from the Mercury module." +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:80 -msgid "**Unit Product**: allows you to identify a product for both POS and transfers." +#: ../../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 "When the barcode pattern contains .*, it means that it can contain any number of characters, those characters being any number." +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 "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 "Default nomenclature list" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:179 +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 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +msgid "Type" +msgstr "" + +#: ../../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 "Price Barcodes 2 Decimals" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:191 +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 "23.....{NNNDD}" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:194 +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:217 +msgid "414" +msgstr "" + +#: ../../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: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:221 +msgid "PACK" +msgstr "" + +#: ../../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: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:225 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:143 +msgid "10" +msgstr "" + +#: ../../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:227 +msgid "Credit Card" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:229 +msgid "%.*" +msgstr "" + +#: ../../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: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:233 +msgid ".*" +msgstr "" + +#: ../../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 "" #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:3 @@ -403,10 +722,6 @@ msgstr "" msgid ":ref:`Non-unit quantities workflow `" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:96 -msgid "Create rules" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:98 msgid "GS1 rules are a specific format of information contained in the barcode, beginning with an |AI| and containing a defined length of characters. Scanning GS1 barcodes from the :ref:`default GS1 list ` auto-fills corresponding data in the Odoo database." msgstr "" @@ -475,22 +790,6 @@ msgstr "" msgid "The table below contains Odoo's default list of GS1 rules. Barcode patterns are written in regular expressions. Only the first three rules require a `check digit `_ as the final character." msgstr "" -#: ../../content/applications/inventory_and_mrp/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/gs1_nomenclature.rst:173 -msgid "Type" -msgstr "" - -#: ../../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/gs1_nomenclature.rst:173 msgid "GS1 Content Type" msgstr "" @@ -503,10 +802,6 @@ msgstr "" msgid "Serial Shipping Container Code" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 -msgid "Package" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 msgid "(00)(\\\\d{18})" msgstr "" @@ -530,23 +825,12 @@ msgstr "" msgid "Global Trade Item Number (GTIN)" msgstr "" -#: ../../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/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 "(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 "" @@ -556,7 +840,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 "" @@ -590,11 +874,6 @@ msgstr "" msgid "I.D. of a physical location" msgstr "" -#: ../../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/gs1_nomenclature.rst:189 msgid "(414)(\\\\d{13})" msgstr "" @@ -604,12 +883,6 @@ msgstr "" msgid "Batch or lot number" msgstr "" -#: ../../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/gs1_nomenclature.rst:191 msgid "(10) ([!\"%-/0-9:-?A-Z_a-z]{0,20})" msgstr "" @@ -833,8 +1106,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 "" @@ -884,14 +1157,9 @@ 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 msgid "Product" msgstr "" @@ -916,11 +1184,6 @@ msgstr "" msgid "Lot Number" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:143 -msgid "10" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 msgid "(10)([!\"%-/0-9:-?A-Z_a-z]{0,20})" msgstr "" @@ -929,41 +1192,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:39 -#: ../../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/lots.rst:22 -#: ../../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:18 -#: ../../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_three_steps.rst:16 -#: ../../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:12 -#: ../../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/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:11 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:65 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:23 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:11 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:15 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:13 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:10 -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 "" @@ -1741,972 +1969,685 @@ 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 +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 +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:7 -msgid "Reordering rules are used to keep forecasted stock levels above a certain threshold without exceeding a specified upper limit. This is accomplished by specifying a minimum quantity that stock should not fall below and a maximum quantity that stock should not exceed." +#: ../../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:11 -msgid "Reordering rules can be configured for each product based on the route used to replenish it. If a product uses the *Buy* route, then a Request for Quotation (RFQ) is created when the reordering rule is triggered. If a product uses the *Manufacture* route, then a Manufacturing Order (MO) is created instead. This is the case regardless of the selected replenishment route." +#: ../../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:17 -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:18 -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:21 -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:23 -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:27 -msgid "On the product form, under the :guilabel:`General Information` tab, make sure that the :guilabel:`Product Type` is set to :guilabel:`Storable Product`. This is necessary because Odoo only tracks stock quantities for storable products, and this number is used to trigger reordering rules." +#: ../../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:35 -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:42 -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:51 -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:55 -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:64 -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:66 -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:69 -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:70 -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:71 -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:74 -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:75 -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:77 -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:85 -msgid "Reordering rules can also be created from each product form. To do so, navigate to :menuselection:`Inventory app --> Products --> Products`, then select a product. Click on :menuselection:`Reordering Rules smart button --> New`, then 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:90 -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:92 -msgid ":ref:`Trigger `" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:5 +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:93 -msgid ":ref:`Visibility days `" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/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, **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:94 -msgid ":ref:`Preferred route `" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:13 +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:97 -msgid "The fields above are not available by default, and must be enabled by selecting the :guilabel:`(slider)` icon in the far-right corner, and selecting the desired column from the drop-down menu." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:20 +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:104 -msgid "Trigger" +#: ../../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:106 -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:31 +msgid "Create packaging" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:109 -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:33 +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:114 -msgid ":doc:`strategies`" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:37 +msgid "From product form" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:117 -msgid "The :guilabel:`Replenishment` dashboard is accessible by going to :menuselection:`Inventory app --> Operations --> Replenishment`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:39 +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:120 -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:42 +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:-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:45 +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:129 -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:47 +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:133 -msgid "Auto" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:48 +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:135 -msgid "Automatic reordering rules, enabled by setting the reordering rule's :guilabel:`Trigger` field to :guilabel:`Auto`, generate purchase or manufacturing orders when:" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:49 +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:138 -msgid "the scheduler runs, and the *On Hand* quantity is below the minimum" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:50 +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:139 -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:53 +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_replenishment/reordering_rules.rst:142 -msgid "The scheduler is set to run once a day, by default." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:0 +msgid "Show the additional options menu's icon: sliders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:144 -msgid "To manually trigger a reordering rule before the scheduler runs, ensure :ref:`developer mode ` is enabled, and then select :menuselection:`Inventory app --> Operations --> Run Scheduler`. Then, select the green :guilabel:`Run Scheduler` button on the pop-up window that appears." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:61 +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:149 -msgid "Be aware that this also triggers *any other* scheduled actions." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:63 +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:152 -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:67 +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:0 -msgid "Show automatic reordering rule from the Reordering Rule page." +#: ../../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:160 -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:76 +msgid "From product packagings page" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:164 -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:78 +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:168 -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:84 +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:174 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:163 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:182 -msgid "Manual" +#: ../../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:176 -msgid "Manual reordering rules, configured by setting the reordering rule's :guilabel:`Trigger` field to :guilabel:`Manual`, list 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, for which the forecasted quantity is not enough." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:93 +msgid "Partial reservation" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:181 -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:95 +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:186 -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:100 +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:-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:103 +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:197 -msgid "Visibility days" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:107 +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:200 -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:-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:203 -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:117 +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:209 -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:119 +msgid "a product is sold in twelve units per packaging." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:212 -msgid "The current date is February twentieth, and the *delivery date* on a sales order (in the :guilabel:`Other Info` tab) is March third — twelve days from the current date." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:120 +msgid "an order demands two packagings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:215 -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:121 +msgid "there are only twenty-two units in stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:218 -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 twenty-seventh." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:123 +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:-1 -msgid "Graphic representing when the need appears on the replenishment dashboard: Feb 27." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:126 +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:226 -msgid "To see the product on the replenishment dashboard for the current date, February twentieth, set the :guilabel:`Visibility Days` to `7.00`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:130 +msgid "Apply packagings" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:229 -msgid "To determine the number 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/packaging.rst:132 +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:232 -msgid "Visibility~days = Need~appears~date - Today's~date" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/packaging.rst:137 +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:237 -msgid "Referring to the example above, today's date is February twentieth, and the need for the product appears on February twenty-seventh." +#: ../../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:240 -msgid "(February 27 - February 20 = 7 days)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:242 -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/product_management/product_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/product_management/product_replenishment/reordering_rules.rst:252 -msgid "Preferred route" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:254 -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/product_management/product_replenishment/reordering_rules.rst:258 -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` or :menuselection:`Inventory app --> Operations --> Replenishment`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:263 -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/product_management/product_replenishment/reordering_rules.rst:-1 -msgid "Select a preferred route from the drop-down." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:271 -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/product_management/product_replenishment/strategies.rst:3 -msgid "Selecting a replenishment strategy" -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." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:16 -msgid "Terminology" -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" -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." -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." -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." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:33 -msgid "Make to order" -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**." -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." -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." -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." -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." -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.`" -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`" -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." -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." -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." -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." -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." -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." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:98 -msgid "Replenishment report fields" -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." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:104 -msgid ":guilabel:`Product`: the product that requires a replenishment." -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." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:106 -msgid ":guilabel:`Warehouse`: the warehouse where the product is stored." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:107 -msgid ":guilabel:`On Hand`: the amount of product currently available." -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." -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." -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." -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)." -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)." -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." -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." -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." -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." -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." -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." -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." -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`." -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." -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." -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." -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." -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." -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." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:158 -msgid "Make to order (MTO) route" -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." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:169 -msgid "To activate the |MTO| route in Odoo:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:163 -msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." -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`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:166 -msgid "Then, go to :menuselection:`Inventory app --> Configuration --> Routes`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:167 -msgid "Click on :menuselection:`Filters --> Archived` to show archived routes." -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`." -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." -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 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/differences.rst:3 -msgid "Difference between lots and serial numbers" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:5 +#: ../../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/differences.rst:9 +#: ../../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/differences.rst:13 +#: ../../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/differences.rst:17 -msgid ":doc:`lots`" +#: ../../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/differences.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:19 -msgid ":doc:`serial_numbers`" +#: ../../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/differences.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:24 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:28 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:20 msgid "Enable lots & serial numbers" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:23 +#: ../../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/differences.rst:26 +#: ../../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/differences.rst:-1 +#: ../../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/differences.rst:35 +#: ../../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/differences.rst:37 +#: ../../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/differences.rst:0 +#: ../../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/differences.rst:46 +#: ../../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/differences.rst:52 +#: ../../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/differences.rst:54 +#: ../../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/differences.rst:0 +#: ../../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/differences.rst:63 +#: ../../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/differences.rst:67 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:70 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:321 #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:114 msgid "Traceability" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:69 +#: ../../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/differences.rst:73 +#: ../../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/differences.rst:77 +#: ../../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/differences.rst:80 +#: ../../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/differences.rst:85 +#: ../../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/differences.rst:-1 +#: ../../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/differences.rst:94 +#: ../../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 "" @@ -2956,7 +2897,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:190 -msgid ":doc:`../../warehouses_storage/advanced_operations_warehouse/removal`" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:105 +msgid ":doc:`../../shipping_receiving/removal_strategies`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:229 @@ -3027,6 +2969,10 @@ msgstr "" msgid "Lots are useful for managing large quantities of manufactured or received products, aiding in tracing items back to their group, particularly for product recalls or :doc:`expiration dates `." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:19 +msgid ":doc:`serial_numbers`" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:24 msgid "To track products by lots, enable the *Lots & Serial Numbers* feature. Then, configure each product to be tracked by serial numbers on the product form." msgstr "" @@ -3369,403 +3315,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:356 -msgid ":doc:`differences`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:3 -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." -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, **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_tracking/packaging.rst:13 -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_tracking/packaging.rst:20 -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:31 -msgid "Create packaging" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:33 -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:37 -msgid "From product form" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:39 -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:42 -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:45 -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:47 -msgid ":guilabel:`Contained quantity` (required): amount of product in the packaging." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:48 -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:49 -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:50 -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:53 -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:61 -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:63 -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:67 -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:76 -msgid "From product packagings page" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:78 -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:84 -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:93 -msgid "Partial reservation" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:95 -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_tracking/packaging.rst:100 -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_tracking/packaging.rst:103 -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_tracking/packaging.rst:107 -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_tracking/packaging.rst:-1 -msgid "Show Reserve Packagings field on the product categories page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:117 -msgid "To better evaluate the options based on business needs, consider the following example:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:119 -msgid "a product is sold in twelve units per packaging." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:120 -msgid "an order demands two packagings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:121 -msgid "there are only twenty-two units in stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:123 -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_tracking/packaging.rst:126 -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_tracking/packaging.rst:130 -msgid "Apply packagings" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:132 -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:137 -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." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:319 +msgid ":doc:`../product_tracking`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:3 @@ -4093,871 +3644,205 @@ 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:319 -msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences`" -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: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:15 +msgid "`Using Routes (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:16 +msgid "`Push & Pull Rules (eLearning Tutorial) `_" 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: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:18 -msgid "How to cancel a shipping request?" +#: ../../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: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:30 +msgid "One-step flow" 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: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:32 -msgid "You will now see that the shipment has been cancelled." +#: ../../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:37 -msgid "You can now change the carrier if you wish." +#: ../../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:40 -msgid "How to send a shipping request after cancelling one?" +#: ../../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: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:40 +msgid "Receipts and/or deliveries are handled quickly." 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: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:51 -msgid ":doc:`multipack`" +#: ../../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/dropshipping.rst:3 -msgid "Use dropshipping to ship directly from suppliers to customers" +#: ../../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:5 -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:48 +msgid "Two-step flow" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:12 -msgid "Configure products to be dropshipped" +#: ../../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 "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: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:18 -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: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:-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: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:27 -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: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:-1 -msgid "The product form with a vendor specified." +#: ../../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:35 -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:66 +msgid ":doc:`daily_operations/receipts_delivery_two_steps`" 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:69 +msgid "Three-step flow" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:43 -msgid "Fulfill orders using dropshipping" +#: ../../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 "When a customer completes an online purchase for a dropshipped product, a sales order will be automatically created with an associated request for quotation (:abbr:`RFQ (Request for Quotation)`) for the supplier. 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: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:52 -msgid "Dropship sales orders can also be created manually through the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders --> Create` and adding a product configured for 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:-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: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:60 -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:`Receipt` smart button in the top right corner of the purchase order form." +#: ../../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:-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: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:68 -msgid "The dropship receipt will list the supplier in the :guilabel:`Receive From` section and the customer in the :guilabel:`Destination Location` section. 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:87 +msgid ":doc:`daily_operations/receipts_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.rst:88 +msgid ":doc:`daily_operations/delivery_three_steps`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:77 -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:3 +msgid "Organize a cross-dock in a warehouse" 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: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/invoicing.rst:3 -msgid "Shipping cost invoicing" +#: ../../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: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: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: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: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: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: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: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: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: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:43 +msgid "Configure products with Cross-Dock Route" 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: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: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: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: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: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:34 -msgid ":guilabel:`Shipping Method` (*required*) the name of the delivery method (e.g. `flat-rate shipping`, `same day delivery`, etc.)." +#: ../../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: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:23 -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 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:91 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:141 -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/scheduled_dates.rst:3 -msgid "Scheduled delivery dates" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:5 -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:10 -msgid "Lead time types" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:12 -msgid "Different lead times for different operations can impact various stages of the order fulfillment process. Here's a summary of the types of lead times in Odoo:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/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:19 -msgid ":ref:`Customer lead time `: The default time frame for fulfilling customer orders. The customer lead time is the number of days from the date the sales order (SO) is confirmed to the date the products are shipped from the warehouse. This is also known as *delivery lead time*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:24 -msgid ":ref:`Sales security lead time `: moves the *scheduled delivery date* forward by a specified number of days. This serves as a buffer to allow the team ample time to prepare the outgoing shipment earlier, considering the possibility of delays in the fulfillment process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:29 -msgid ":ref:`Purchase lead time `: the number of days from the confirmation of a purchase order (PO) to the receipt of products. It provides insight on the time it takes for products to arrive at the warehouse, facilitating effective scheduling and planning of supplier deliveries." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:34 -msgid ":ref:`Purchase security lead time `: advances the order deadline on a :abbr:`PO (Purchase Order)` by a specified number of days. This proactive approach of placing orders earlier mitigates the risk of vendor or shipping delays. Thus, for products that are set to replenish to order, the need appears on the *Replenishment report* earlier, according to the specified number of days." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:40 -msgid ":ref:`Manufacturing lead time `: the number of days needed to complete a manufacturing order (MO) from the date of confirmation. This lead time includes weekends (non-working hours in Odoo), and is used to forecast an approximate production date for a finished good." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:45 -msgid ":ref:`Manufacturing security lead time `: moves the scheduled date of the :abbr:`MO (Manufacturing Order)` forward by a specified number of days. When used in conjunction with :ref:`replenish to order `, the security lead time makes the need appear earlier on the replenishment report." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:53 -msgid "Sales lead times" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:55 -msgid "Customer lead times and sales security lead times can be configured to automatically compute an *expected delivery date* on a :abbr:`SO (Sales Order)`. The expected delivery date ensures a realistic *delivery dates* setting for shipments from the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:59 -msgid "Odoo issues a warning message if the set delivery date is earlier than the expected date, as it may not be feasible to fulfill the order by that time, which would impact other warehouse operations." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:63 -msgid "A :abbr:`SO (Sales Order)` containing a `Coconut-scented candle` is confirmed on July 11th. The product has a customer lead time of 14 days, and the business uses a sales security lead time of 1 day. Based on the lead time inputs, Odoo suggests a delivery date in 15 days, on July 26th." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/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:71 -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:74 -msgid "Customer lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:76 -msgid "Set the customer lead time on each product form, by navigating to the products page. To do so, go to :menuselection:`Sales app --> Products --> Products`. From there, select the desired product, and switch to the :guilabel:`Inventory` tab. Then, under the :guilabel:`Customer Lead Time` field, fill in the number of calendar days required to fulfill the delivery order from start to finish." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:82 -msgid "Set a 14-day customer lead time for the `Coconut-scented candle` by navigating to its product form. Then, in the :guilabel:`Inventory` tab, type `14.00` days into the :guilabel:`Customer Lead Time` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/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:93 -msgid "Sales security lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:95 -msgid "*Sales security lead time* is set globally for the business in :menuselection:`Inventory app --> Configuration --> Settings`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:98 -msgid "On the configuration page, under the :guilabel:`Advanced Scheduling` heading, locate the box for :guilabel:`Security Lead Time for Sales`, and click the checkbox to enable the feature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:101 -msgid "Next, enter the desired number of calendar days. This security lead time is a buffer notifying the team to prepare for outgoing shipments earlier than the scheduled date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:105 -msgid "Setting the :guilabel:`Security Lead Time for Sales` to `1.00` day, pushes the :guilabel:`Scheduled Date` of a delivery order (DO) forward by one day. In that case, if a product is initially scheduled for delivery on April 6th, but with a one-day security lead time, the new scheduled date for the delivery order would be April 5th." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/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:115 -msgid "Deliver several products" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:117 -msgid "For orders that include multiple products with different lead times, the lead times can be configured directly from the quotation itself. On a quotation, click the :guilabel:`Other Info` tab, and set the :guilabel:`Shipping Policy` to:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:121 -msgid ":guilabel:`As soon as possible` to deliver products as soon as they are ready. The :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is determined by adding today's date to the shortest lead time among the products in the order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:125 -msgid ":guilabel:`When all products are ready` to wait to fulfill the entire order at once. The :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is determined by adding today's date to the longest lead time among the products in the order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/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:134 -msgid "In a quotation containing 2 products, `Yoga mat` and `Resistance band,` the products have a lead time of 8 days and 5 days, respectively. Today's date is April 2nd." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:137 -msgid "When the :guilabel:`Shipping Policy` is set to :guilabel:`As soon as possible`, the scheduled delivery date is 5 days from today: April 7th. On the other hand, selecting :guilabel:`When all products are ready` configures the scheduled date to be 8 days from today: April 10th." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:144 -msgid "Purchase lead times" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:146 -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:149 -msgid "Odoo calculates the supplier shipment *receipt date*, and :abbr:`PO (Purchase Order)` deadline, based on the required date the product is needed in the warehouse. By working backwards from the receipt date, vendor lead times and purchase security lead times are taken into account, in order to determine the :abbr:`PO (Purchase Order)` deadline." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:154 -msgid "This deadline is the date by which the order should be confirmed, in order to ensure timely arrival by the expected receipt date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/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:162 -msgid ":ref:`PO scheduling with reordering rules `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:165 -msgid "Vendor lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:167 -msgid "To set a vendor lead time for orders arriving in the warehouse from a vendor location, begin by navigating to a product form through :menuselection:`Purchase app --> Products --> Products`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:170 -msgid "Next, select the desired product, and switch to the :guilabel:`Purchase` tab. In the editable vendor pricelist, click the :guilabel:`Add a line` button to add vendor details, such as the :guilabel:`Vendor` name, :guilabel:`Price` offered for the product, and lastly, the :guilabel:`Delivery Lead Time`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:176 -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:180 -msgid "On the vendor pricelist of the product form, the :guilabel:`Delivery Lead Time` for the selected vendor is set to `10 days.`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/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:187 -msgid "By setting the vendor lead time, the expected arrival date of the item is automatically determined as the date of the :abbr:`PO (Purchase Order)` confirmation, plus the vendor lead time. This ensures that warehouse employees are notified, if the products do **not** arrive within the expected timeframe." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:193 -msgid "On a :abbr:`PO (Purchase Order)` confirmed on July 11th, for a product configured with a 10-day vendor lead time, Odoo automatically sets the :guilabel:`Receipt Date` to July 21st. The receipt date also appears as the :guilabel:`Scheduled Date` on the warehouse receipt form, accessible from the :guilabel:`Receipt` smart button, located on the :guilabel:`PO (Purchase Order)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/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:209 -msgid "Purchase security lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:211 -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:214 -msgid "On the configuration page, under the :guilabel:`Advanced Scheduling` heading, locate the box for :guilabel:`Security Lead Time for Purchase`, and click the checkbox to enable the feature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:217 -msgid "Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is set to account for potential delays in supplier deliveries." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:221 -msgid "Setting the :guilabel:`Security Lead Time for Purchase` to `2.00` days, pushes the :guilabel:`Scheduled Date` of receipt back by one day. In that case, if a product is initially scheduled to arrive on April 6th, with a two-day security lead time, the new scheduled date for the receipt would be April 8th." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/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:233 -msgid "Manufacturing lead times" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:235 -msgid "Lead times can help simplify the procurement process for consumable materials and components used in manufactured products with bills of materials." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:238 -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:247 -msgid "Manufacturing lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:249 -msgid "Configure the manufacturing lead time directly on the product form, by navigating to :menuselection:`Manufacturing app --> Products --> Products`, and select the desired product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:252 -msgid "In the :guilabel:`Inventory` tab of the product, specify the calendar days needed to the manufacture the product in the :guilabel:`Manufacturing Lead Time` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:256 -msgid "Specify a 14-day :guilabel:`Manufacturing Lead Time` for a product directly in the :guilabel:`Inventory` tab of the product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 -msgid "View of the manufacturing lead time configuration from the product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:263 -msgid "Establish a :abbr:`MO (Manufacturing Order)` deadline, based on the *expected delivery date*, indicated in the :guilabel:`Scheduled Date` field of the :abbr:`DO (Delivery Order)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:266 -msgid "The :abbr:`MO (Manufacturing Order)` deadline, which is the :guilabel:`Scheduled Date` field on the :abbr:`MO (Manufacturing Order)`, is calculated as the *expected delivery date* subtracted by the manufacturing lead time." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:270 -msgid "This ensures the manufacturing process begins on time, in order to meet the delivery date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:272 -msgid "However, it's important to note that lead times are based on calendar days. Lead times do **not** consider weekends, holidays, or *work center capacity* (:dfn:`the number of operations that can be performed at the work center simultaneously`)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:277 -msgid ":ref:`Manufacturing planning `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:278 -msgid ":ref:`Configure automatic MO scheduling with reordering rules `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:282 -msgid "A product's scheduled shipment date on the :abbr:`DO (Delivery Order)` is August 15th. The product requires 14 days to manufacture. So, the latest date to start the :abbr:`MO (Manufacturing Order)` to meet the commitment date is August 1st." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:289 -msgid "Manufacturing security lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:291 -msgid "*Manufacturing security lead time* is set globally for the business in :menuselection:`Manufacturing app --> Configuration --> Settings`. Under the :guilabel:`Planning` heading, locate the box for :guilabel:`Security Lead Time`, and click the checkbox to enable the feature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:295 -msgid "Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is set to account for potential delays in the manufacturing process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/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:303 -msgid "A product has a scheduled shipment date on the :abbr:`DO (Delivery Order)` set for August 15th. The manufacturing lead time is 7 days, and manufacturing security lead time is 3 days. So, the :guilabel:`Scheduled Date` on the :abbr:`MO (Manufacturing Order)` reflects the latest date to begin the manufacturing order. In this example, the planned date on the :abbr:`MO (Manufacturing Order)` is August 5th." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:310 -msgid "Global example" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:312 -msgid "See the following example to understand how all the lead times work together to ensure timely order fulfillment:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:315 -msgid "**Sales security lead time**: 1 day" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:316 -msgid "**Manufacturing security lead time**: 2 days" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:317 -msgid "**Manufacturing lead time**: 3 days" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:318 -msgid "**Purchase security lead time**: 1 day" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:319 -msgid "**Vendor lead time**: 4 days" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:321 -msgid "The customer places an order for a manufactured product on September 1st, and the scheduled delivery date from the warehouse is on September 20th. Odoo uses lead times and automated reordering rules to schedule the necessary operations, based on the outgoing shipment delivery date, September 20th:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/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:329 -msgid "**September 1st**: Sales order created, confirmed by salesperson." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:331 -msgid "**September 9th**: Deadline to order components to ensure they arrive in time when manufacturing begins (4-day supplier lead time)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:334 -msgid "**September 13th**: Scheduled date of receipt for components. Initially, it was set to 9/14, but the 1-day purchase security lead time pushed the date earlier by 1 day." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:337 -msgid "**September 14th**: Deadline to begin manufacturing. Calculated by subtracting the manufacturing lead time of 3 days, and the manufacturing security lead time of 2 days, from the expected delivery date of September 19th." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:341 -msgid "**September 19th**: :guilabel:`Scheduled Date` on the delivery order form indicates the updated expected delivery date, which was originally set as September 20th. But the sales security lead time pushed the date forward by a day." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:345 -msgid "Odoo's replenishment planning maps a business' order fulfillment process, setting pre-determined deadlines and raw material order dates, including buffer days for potential delays. This ensures products are delivered on time." +#: ../../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 @@ -4965,7 +3850,7 @@ msgstr "" 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 "" @@ -4973,19 +3858,26 @@ 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/daily_operations/receipts_delivery_one_step.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:139 +#: ../../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 shows the picking order, packing order, and the delivery order associated with the sales order." msgstr "" @@ -4994,12 +3886,12 @@ 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 -msgid "The picking, packing, and delivery orders will be created once the sales order is confirmed. To view these transfers, go to :menuselection:`Inventory --> Operations --> Transfers`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:62 +msgid "The picking, packing, and delivery orders will be created once the sales order is confirmed. To view these transfers, go to :menuselection:`Inventory --> Operations --> Transfers`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 @@ -5007,11 +3899,11 @@ msgid "Ready status for the pick operation while the packing and delivery operat "another operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:73 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:70 msgid "The status of the picking will be :guilabel:`Ready`, since the product must be picked from stock before it can be packed. The status of the packing order and delivery order will both be :guilabel:`Waiting Another Operation`, since the packing and delivery cannot happen until the picking is completed. The status of the delivery order will only change to :guilabel:`Ready` when the packing has been marked :guilabel:`Done`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:79 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:76 msgid "The receipt can also be found in the *Inventory* application. In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Pick` kanban card." msgstr "" @@ -5019,7 +3911,7 @@ msgstr "" msgid "The pick order can be seen in the Inventory Kanban view." 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 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`. Then the packing order will be ready. Since the documents are linked, the products which have been previously picked are automatically reserved on the packing order." msgstr "" @@ -5028,11 +3920,11 @@ msgstr "" msgid "Validate the picking by clicking Validate." 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 "Process a packing" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:95 msgid "The packing order will be ready to be processed once the picking is completed, and can be found in the :menuselection:`Inventory` application :guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart button in the :guilabel:`Pack` kanban card." msgstr "" @@ -5040,7 +3932,7 @@ msgstr "" msgid "The packing order can be seen in the Inventory kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:103 msgid "Click on the packing order associated with the sales order, then click on :guilabel:`Validate` to complete the packing." msgstr "" @@ -5049,15 +3941,15 @@ msgid "Click Validate on the packing order to transfer the product from the pack "output location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:114 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:111 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:119 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:116 msgid "Process a delivery" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:121 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:118 msgid "The delivery order will be ready to be processed once the packing is completed, and can be found in the :menuselection:`Inventory` application :guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart button in the :guilabel:`Delivery Orders` kanban card." msgstr "" @@ -5065,7 +3957,7 @@ msgstr "" msgid "The delivery order can be seen in the Delivery Orders Kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:129 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:126 msgid "Click on the delivery order associated with the sales order, then click on :guilabel:`Validate` to complete the move." msgstr "" @@ -5075,35 +3967,367 @@ 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:137 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:134 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 "Use dropshipping to ship directly from suppliers to customers" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:7 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:5 +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:12 +msgid "Configure products to be dropshipped" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:14 +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:18 +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:27 +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:35 +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:43 +msgid "Fulfill orders using dropshipping" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:45 +msgid "When a customer completes an online purchase for a dropshipped product, a sales order will be automatically created with an associated request for quotation (:abbr:`RFQ (Request for Quotation)`) for the supplier. 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:52 +msgid "Dropship sales orders can also be created manually through the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders --> Create` and adding a product configured for dropshipping." +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:60 +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:`Receipt` 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:68 +msgid "The dropship receipt will list the supplier in the :guilabel:`Receive From` section and the customer in the :guilabel:`Destination Location` section. 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:77 +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:5 msgid "By default, incoming shipments are configured to be received directly into stock, and outgoing shipments are configured to be delivered directly from stock to the customer; the default setting for warehouses in Odoo is one step receipts and deliveries." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:10 msgid "Incoming and outgoing shipments do not need to be configured with the same steps. For example, products can be received in one step, but shipped in three steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:13 msgid "In the following example, one step will be used for both receipts and deliveries." msgstr "" -#: ../../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_one_step.rst:18 msgid "Configure the warehouse" msgstr "" -#: ../../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_one_step.rst:20 msgid "If another receiving or shipping configuration is set on the warehouse, they can easily be set back to the one step setting." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:25 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:23 msgid "Begin by navigating to :menuselection:`Inventory --> Configuration --> Warehouses`, and click on the desired warehouse to edit. Next, on the :guilabel:`Warehouse Configuration` tab, under the :guilabel:`Shipments` section, select :guilabel:`Receive goods directly (1 step)` for :guilabel:`Incoming Shipments` and/or :guilabel:`Deliver goods directly (1 step)` for :guilabel:`Outgoing Shipments`." msgstr "" @@ -5111,23 +4335,23 @@ msgstr "" msgid "Set incoming and outgoing shipment options to receive and deliver in one step." 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 "Receive goods directly (1 step)" msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:37 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:67 +#: ../../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_delivery_one_step.rst:39 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:69 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:48 -msgid "Create a purchase order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:41 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:71 msgid "On the main :menuselection:`Purchase` application dashboard, start by making a new quote by clicking :guilabel:`New`. Then, select (or create) a :guilabel:`Vendor` from the drop-down field, add a storable :guilabel:`Product` to the order lines, and click :guilabel:`Confirm Order` to finalize the quote as a new purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:46 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:44 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:96 msgid "A :guilabel:`Receipt` smart button will appear in the top-right corner of the :abbr:`PO (purchase order)` form — click it to reveal the associated receipt for the purchase order." msgstr "" @@ -5135,8 +4359,8 @@ msgstr "" msgid "Receipt smart button appears on the confirmed purchase order." msgstr "" -#: ../../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:91 +#: ../../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_two_steps.rst:89 msgid "Purchase order receipts can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# to Process` smart button in the :guilabel:`Receipts` kanban card." msgstr "" @@ -5144,13 +4368,13 @@ msgstr "" msgid "Receipt kanban card's 1 to Process smart button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:63 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:100 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:97 +#: ../../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_two_steps.rst:98 +#: ../../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/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:63 msgid "When viewing the receipt (associated with the purchase order above), click :guilabel:`Validate` to then complete the receipt." msgstr "" @@ -5158,7 +4382,7 @@ msgstr "" msgid "Validate the purchase order via the Validate smart button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:73 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:71 msgid "If :guilabel:`Storage Locations` are activated, clicking the :guilabel:`≣ (bullet list)` details icon next to the :guilabel:`🗑️ (trash)` delete icon enables the :guilabel:`Detailed Operations` screen to pop-up. This allows the location(s) to be specified for the received product(s)." msgstr "" @@ -5167,19 +4391,19 @@ msgid "Select the Storage Location for the products being received in the Detail "pop-up." 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_one_step.rst:80 msgid "Once the receipt is validated, the product leaves the :guilabel:`Supplier Location` and enters the :guilabel:`WH/Stock Location`. Once it arrives here, it will be available for manufacturing, sales, etc. Then, the status of the document will change to :guilabel:`Done`, thus completing the reception process in one step." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:88 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:86 msgid "Deliver goods directly (1 step)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:91 msgid "Start my navigating to the main :menuselection:`Sales` app dashboard, and make a new quote by clicking :guilabel:`New`. Then select (or create) a :guilabel:`Customer` from the drop-down field, add a storable :guilabel:`Product` that is in stock to the order lines, and click :guilabel:`Confirm` to finalize the quotation as a sales order." 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 "A :guilabel:`Delivery` smart button will appear in the top-right corner of the :abbr:`SO (Sales Order)` form — click it to reveal the associated delivery order for the sales order." msgstr "" @@ -5187,7 +4411,7 @@ msgstr "" msgid "The Delivery smart button appears after the sales order is confirmed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:109 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:107 msgid "Delivery orders can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# to Process` smart button in the :guilabel:`Delivery Orders` kanban card." msgstr "" @@ -5195,12 +4419,12 @@ msgstr "" msgid "Delivery Orders kanban card's 1 to Process smart button." msgstr "" -#: ../../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:194 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:116 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:192 msgid "Process the delivery" 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_one_step.rst:118 msgid "When viewing the delivery order (associated with the sales order above), click :guilabel:`Validate` to then complete the delivery." msgstr "" @@ -5208,51 +4432,51 @@ msgstr "" msgid "Validate the delivery order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:127 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:125 msgid "Once the picking order is validated, the product leaves the :guilabel:`WH/Stock location` and moves to the :guilabel:`Partners/Customers location`. Then, the status of the document will change to :guilabel:`Done`, thus completing delivery in one step." 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:7 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:5 msgid "Depending on a company's business processes, multiple steps may be needed before receiving or shipping products. In the two-step receipt process, products are received in an input area, then transferred to stock. Two-step receipts work best when various storage locations are being used, such as locked or secured areas, freezers and refrigerators, or various shelves." 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 "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:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:14 msgid "In the two-step delivery process, products that are part of a delivery order are picked from the warehouse according to their removal strategy, and brought to an output location before being shipped." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:18 msgid "One situation where this would be useful is when using either a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy, where the products that are being picked need to be selected based on their receipt date or expiration date." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:25 -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 two-step receipts and deliveries. Incoming and outgoing shipments do not need to be set to have the same steps. For example, products can be received in two steps, but shipped in one step. In the following example, two steps will be used for both receipts and deliveries." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:23 +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 two-step receipts and deliveries. Incoming and outgoing shipments do not need to be set to have the same steps. For example, products can be received in two steps, but shipped in one step. In the following example, two steps will be used for both receipts and deliveries." 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 "Configure multi-step routes" msgstr "" -#: ../../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_delivery_two_steps.rst:32 msgid "First, make sure the :guilabel:`Multi-Step Routes` option is enabled in :menuselection:`Inventory --> Configuration --> Settings`, under the :guilabel:`Warehouse` heading. After enabling the setting, :guilabel:`Save` the changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:37 msgid "Activating the :guilabel:`Multi-Step Routes` setting will also activate the :guilabel:`Storage Locations` feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:44 msgid "Next, the warehouse needs to be configured for two-step receipts and deliveries. Go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click on the warehouse to change the warehouse 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 "Then, select :guilabel:`Receive goods in input and then stock (2 steps)` for :guilabel:`Incoming Shipments`, and :guilabel:`Send goods in output and then deliver (2 steps)` for :guilabel:`Outgoing Shipments`." msgstr "" @@ -5260,19 +4484,19 @@ msgstr "" msgid "Set incoming and outgoing shipment options to receive and deliver in two steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:57 msgid "Activating two-step receipts and deliveries will create new *input* and *output* locations, which by default, are labeled :guilabel:`WH/Input` and :guilabel:`WH/Output`, respectively, on the :guilabel:`Locations` dashboard. To rename these locations, go to :menuselection:`Configuration --> Locations`, and select the :guilabel:`Location` to change. On the location form, update the :guilabel:`Location Name`, and make any other changes (if necessary)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:66 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:64 msgid "Process a receipt in two steps (input + stock)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:75 msgid "For businesses with multiple warehouses that have different step configurations, the :guilabel:`Deliver To` field on the :abbr:`PO (Purchase Order)` form may need to be specified as the correct *input location* connected to the two-step warehouse, which can be done by selecting the warehouse from the drop-down selection 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:83 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:81 msgid "After confirming the :abbr:`PO (Purchase Order)`, a :guilabel:`Receipt` smart button will appear in the top of the :abbr:`PO (Purchase Order)` form — click it to reveal the associated receipt." msgstr "" @@ -5285,11 +4509,11 @@ msgstr "" msgid "One receipt ready to process in the Inventory Overview kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:102 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:100 msgid "The receipt and internal transfer will be created once the purchase order is confirmed. The status of the receipt will be :guilabel:`Ready`, since the receipt must be processed first. The status of the internal transfer will be :guilabel:`Waiting Another Operation`, since the transfer cannot happen until the receipt is completed. The status of the internal transfer will only change to :guilabel:`Ready` once the receipt has been marked as :guilabel:`Done`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:106 msgid "Click on the :guilabel:`Receipt` associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to the :guilabel:`Input Location`." msgstr "" @@ -5298,11 +4522,11 @@ msgid "Validate the receipt by clicking Validate, then the product will be trans "WH/Input location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:115 msgid "Process the internal transfer" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:119 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:117 msgid "Once the product is in the :guilabel:`Input Location`, the internal transfer is ready to move the product into stock. Navigate to the :menuselection:`Inventory` app, and on the :guilabel:`Inventory Overview` dashboard, click the :guilabel:`# To Process` smart button in the :guilabel:`Internal Transfers` kanban card." msgstr "" @@ -5311,7 +4535,7 @@ msgstr "" msgid "One Internal Transfer ready to process in the Inventory Overview kanban view." 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 "Click on the :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to stock. Once the transfer is validated, the product enters the stock and is available for customer deliveries or manufacturing orders." msgstr "" @@ -5319,15 +4543,15 @@ msgstr "" msgid "Validate the internal transfer to move the item to stock." 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 "Process a delivery order in two steps (pick + ship)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:141 msgid "In the :menuselection:`Sales` application, create a new quote by clicking :guilabel:`New`. Select (or create) a :guilabel:`Customer`, add a storable :guilabel:`Product` to the order lines, and then click :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:147 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:145 msgid "After confirming the :abbr:`SO (Sales Order)`, a :guilabel:`Delivery` smart button will appear in the top, above the :abbr:`SO (Sales Order)` form. Click the :guilabel:`Delivery` smart button to reveal the associated receipt." msgstr "" @@ -5336,7 +4560,7 @@ 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/receipts_delivery_two_steps.rst:157 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:155 msgid "Sales order receipts can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# To Process` smart button in the :guilabel:`Pick` kanban card." msgstr "" @@ -5344,15 +4568,15 @@ msgstr "" msgid "The pick order can be seen in the Inventory kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:166 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:164 msgid "Process the picking" 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 "The picking and delivery order will be created once the sales order is confirmed. When the :guilabel:`Delivery` smart button appears, click it to reveal the :guilabel:`Transfers` dashboard, which lists both the picking and the delivery orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:172 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:170 msgid "The status of the picking will be :guilabel:`Ready`, since the product must be picked from stock before it can be shipped. The status of the delivery order will be :guilabel:`Waiting Another Operation`, since the delivery cannot happen until the picking is completed. The status of the delivery order will only change to :guilabel:`Ready` once the picking has been marked as :guilabel:`Done`." msgstr "" @@ -5361,15 +4585,15 @@ msgid "Ready status for the pick operation while the delivery operation is Waiti "Operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:183 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:181 msgid "Click on the picking delivery order to begin processing it. If the product is in stock, Odoo will automatically reserve the product. Click :guilabel:`Validate` to mark the picking as :guilabel:`Done`, then the delivery order will be ready for processing. Since the documents are linked, the products which have been previously picked are automatically reserved on the delivery order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:196 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:194 msgid "The delivery order will be ready to be processed once the picking is completed, and can be found in the :menuselection:`Inventory` application, on the :guilabel:`Inventory Overview` dashboard. Click the :guilabel:`# To Process` smart button in the :guilabel:`Delivery Orders` kanban card to begin." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:201 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:199 msgid "The delivery order associated with the :abbr:`SO (Sales Order)` can also be quickly accessed by clicking on the :guilabel:`Delivery` smart button again, and choosing the delivery order on the :guilabel:`Transfers` page (which should now be marked as :guilabel:`Ready`)." msgstr "" @@ -5377,39 +4601,39 @@ msgstr "" msgid "The delivery order can be seen in the Inventory Kanban view." 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 "Click on the delivery order associated with the :abbr:`SO (Sales Order)`, then click on :guilabel:`Validate` to complete the move." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:217 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:215 msgid "Once the delivery order is validated, the product leaves the :guilabel:`WH/Output` location on the :guilabel:`Transfers` dashboard 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_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 "" @@ -5417,27 +4641,27 @@ 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: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 "" -#: ../../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 "One receipt and two internal transfers (one transfer to quality, and a subsequent transfer to stock) will be created once the purchase order is confirmed. To view these transfers, go to :menuselection:`Inventory --> Operations --> Transfers`." msgstr "" @@ -5446,15 +4670,15 @@ msgid "The status of the three receipt transfers will show which operation is re "are waiting another operation." 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 "The status of the receipt transferring the product to the input location will be :guilabel:`Ready`, since the receipt must be processed before any other operation can occur. The status of the two internal transfers will be :guilabel:`Waiting Another Operation`, since the transfers cannot be processed until the linked step before each transfer is completed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:79 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:77 msgid "The status of the first internal transfer to *quality* will only change to :guilabel:`Ready` when the receipt has been marked :guilabel:`Done`. The status for the second internal transfer to *stock* will be marked :guilabel:`Ready` only after the transfer to quality has been marked :guilabel:`Done`." 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 "The receipt can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Receipts` kanban card." msgstr "" @@ -5462,7 +4686,7 @@ msgstr "" msgid "One Receipt ready to process in the Inventory Overview kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:90 msgid "Click on the receipt associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to the :guilabel:`Input Location`." msgstr "" @@ -5471,15 +4695,15 @@ msgid "Validate the receipt by clicking Validate, and the product will be transf "WH/Quality location." 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 Quality Control" 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 product is in the :guilabel:`Input Location`, the internal transfer is ready to move the product to :guilabel:`Quality Control`. In the :menuselection:`Inventory` :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:112 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:110 msgid "Click on the :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the transfer and move the product to the :guilabel:`Quality Control` location. Once the transfer is validated, the product is ready for the quality inspection, but is not available for manufacturing or delivery orders." msgstr "" @@ -5487,149 +4711,2130 @@ msgstr "" msgid "Validate the internal transfer to move the item to the Quality Control location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:122 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:120 msgid "Process a transfer to stock" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:124 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:122 msgid "Once the product is in the :guilabel:`Quality Control` location, the final internal transfer is ready to move the product to :guilabel:`Stock`. In the :guilabel:`Inventory` overview dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` Kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:128 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:126 msgid "Click on the final :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the transfer and move the product to stock. Once the transfer is validated, the product enters the stock and is available for customer deliveries or manufacturing orders." 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 "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." +#: ../../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:12 -msgid "`Using Routes (eLearning Tutorial) `_" +#: ../../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:13 -msgid "`Push & Pull Rules (eLearning Tutorial) `_" +#: ../../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:17 -msgid "Choosing the right inventory flow to handle receipts and deliveries" +#: ../../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:19 -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." +#: ../../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:27 -msgid "One-step flow" +#: ../../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:29 -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: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:31 -msgid "**Receipt**: Receive products directly into stock. No intermediate steps between receipt and stock occur, such as a transfer to a quality control location." +#: ../../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:33 -msgid "**Shipping**: Ship products directly from stock. No intermediate steps between stock and shipping occur, such as a transfer to a packing location." +#: ../../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:35 -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." +#: ../../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:37 -msgid "Receipts and/or deliveries are handled quickly." +#: ../../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:38 -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:47 +msgid "Create virtual parent location" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:39 -msgid "Items are received or shipped directly into/from stock." +#: ../../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:42 -msgid ":doc:`receipts_delivery_one_step`" +#: ../../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:45 -msgid "Two-step flow" +#: ../../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:47 -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: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:49 -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: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:52 -msgid "**Pick + ship**: Bring products to an output location before shipping. Packages can be organized by different carriers or shipping docks before being shipped." +#: ../../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 "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: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 "Recommended for larger warehouses with high stock levels, or when stocking large items (such as mattresses, large furniture, heavy machinery, etc.)." +#: ../../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 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:80 -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:78 +msgid ":doc:`../../warehouses_storage/replenishment/resupply_warehouses`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:63 -msgid ":ref:`Process receipts and deliveries in two steps `" +#: ../../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:66 -msgid "Three-step flow" +#: ../../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:68 -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: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:70 -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: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:72 -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 "**Parent Warehouse**" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:74 -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." +#: ../../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:77 -msgid "Recommended for very large warehouses with very high stock levels." +#: ../../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:78 -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:0 +msgid "**Child Warehouses**" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:84 -msgid ":ref:`Process receipts in three steps `" +#: ../../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:85 -msgid ":ref:`Process deliveries in three steps `" +#: ../../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/setup_configuration.rst:5 -msgid "Setup and configuration" +#: ../../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/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/stock_warehouses.rst:117 +msgid "Link child warehouses to virtual stock" +msgstr "" + +#: ../../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/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/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:-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: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/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:162 +msgid "Custom Routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/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/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: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/shipping_receiving/daily_operations/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/shipping_receiving/daily_operations/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/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: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/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: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/shipping_receiving/daily_operations/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/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: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/shipping_receiving/daily_operations/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/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:219 +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:222 +msgid "Rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/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/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: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/shipping_receiving/daily_operations/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/shipping_receiving/daily_operations/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/shipping_receiving/daily_operations/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/shipping_receiving/daily_operations/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/shipping_receiving/daily_operations/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/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: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/shipping_receiving/daily_operations/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/shipping_receiving/daily_operations/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/shipping_receiving/daily_operations/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/shipping_receiving/daily_operations/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/shipping_receiving/daily_operations/use_routes.rst:273 +msgid "Example flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/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/shipping_receiving/daily_operations/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/shipping_receiving/daily_operations/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/shipping_receiving/daily_operations/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/shipping_receiving/daily_operations/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/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: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/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: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/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: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/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: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/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: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/shipping_receiving/daily_operations/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/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:3 +msgid "Removal strategies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:5 +msgid "For companies with warehouses, **removal strategies** determine which products are taken from the warehouse, and when. Removal strategies are typically defined for specific picking operations. This helps companies to select the best products, optimize the distance workers need to travel when picking items for orders, and account for quality control, such as moving products with expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:11 +msgid "Usually, *Removal Strategies* are defined in picking operations to select the best products to optimize the distance for the worker, for quality control purposes, or to first move the products with the closest expiration date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:15 +msgid "When a product needs to be moved, Odoo finds available products that can be assigned to the transfer. The way Odoo assigns these products depends on the :guilabel:`Removal Strategy` defined in either the :guilabel:`Product Category` or the :guilabel:`Location` dashboards." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:19 +msgid "To change the :guilabel:`Removal Strategy`, go to :menuselection:`Inventory app --> Configuration --> Locations` or :menuselection:`Product Categories`. Click on a :guilabel:`Location` or :guilabel:`Product Category`, and then click :guilabel:`Edit`. Change the product category :guilabel:`Force Removal Strategy` or the location :guilabel:`Removal Strategy` by clicking on the drop-down menu and selecting the desired removal strategy. After selecting the new removal strategy, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/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:31 +msgid "What happens inside the warehouse?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:33 +msgid "Most warehouses share the same important areas: receiving docks and sorting areas, storage locations, picking and packing areas, and shipping/loading docks. While all products entering or leaving the warehouse might go through each of these locations at some point, removal strategies can have an effect on which products are taken, from where, and when." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:38 +msgid "In this example below, vendor trucks unload pallets of goods at the receiving docks. Then, operators scan the products in the receiving area, with the reception date and expiration date. After that, products are stored in their respective storage locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:43 +msgid "Not all products have expiration dates, but in this example, expiration dates apply." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "Products entering stock via the receiving area." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:49 +msgid "In Odoo, receive products by navigating to the :menuselection:`Inventory` application, and in the kanban view, click on either the :guilabel:`Receipts` heading or :guilabel:`# TO PROCESS` button. On the :guilabel:`Receipts` dashboard, find and click on the individual receipt which will open the warehouse intake form. Click :guilabel:`Edit`, and then enter the received quantity in the :guilabel:`Done` column. To finish, :guilabel:`Validate` to receive the products and register them in the Odoo database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:57 +msgid "Receiving products can also be done within the Odoo *Barcode* application. If using the *Barcode* app, scan the product(s), update the quantity, and finally, click :guilabel:`Validate`. After products are received in Odoo, the products can then be moved to their respective storage locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:62 +msgid "Continuing with the same example, below, imagine several sales orders are made for the products received earlier, that use expiration dates. In this example, the products weren't received on the same day, and they don't have the same expiration date. In this situation, logically, sending products with the closest expiration date is preferred, instead of products received first or last. Using the chosen removal strategy configured for those products (in this example, :ref:`FEFO `), Odoo generates a transfer for the products with the soonest expiration date to the picking area, then the packing area, and finally, to the shipping docks for delivery to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "Products being packed at the packing area for delivery, taking the expiration dates into\n" +"account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:77 +msgid "To pick for delivery, the product's lot/serial number can be found on the transfer form. To learn more about picking and shipping, refer to either the :doc:`Two-step delivery <../shipping_receiving/daily_operations/receipts_delivery_two_steps>` or :doc:`Three-step delivery <../shipping_receiving/daily_operations/delivery_three_steps>` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:83 +msgid "How each removal strategy works" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:85 +msgid "Removal strategies determine which products are taken from the warehouse when orders are confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:88 +msgid "First In, First Out (FIFO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:90 +msgid "When using a :guilabel:`First In, First Out (FIFO)` strategy, demand for a product triggers a removal rule, which requests a transfer for the lot/serial number that entered the stock first (and therefore, has been in stock for the longest time)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:94 +msgid "For example, imagine there are three lots of nails in the warehouse, and have the corresponding lot numbers: `00001`, `00002`, `00003`. Each lot has five boxes of nails in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:97 +msgid "Lot `00001` entered the stock on May 23, lot `00002` on May 25, and lot `00003` on June 1. A customer orders six boxes on June 11." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:100 +msgid "Using the :abbr:`FIFO (First In, First Out)` removal strategy, a transfer request will pick the five boxes from lot `00001` first, and then from the boxes in lot `00002`, since lot `00001` entered the stock first. The box from lot `00002` is taken next because it has the oldest receipt date after lot `00001`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "The detailed operations for the transfer shows the nail lots to be removed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:110 +msgid "Last In, First Out (LIFO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:112 +msgid "Similar to the :abbr:`FIFO (First In, First Out)` method, the :guilabel:`Last In, First Out (LIFO)` removal strategy moves products based on the date they entered a warehouse's stock. Instead of removing the oldest stock on-hand, however, it targets the **newest** stock on-hand for removal." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:116 +msgid "Every time an order for products with the :abbr:`LIFO (Last In, First Out)` method is placed, a transfer is created for the lot/serial number that has most recently entered the stock (the **last** lot/serial number that entered the warehouse's inventory)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:121 +msgid "In many countries, the :abbr:`LIFO (Last In, First Out)` removal strategy in banned, since it can potentially result in old, expired, or obsolete products being delivered to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:124 +msgid "For example, imagine there are three lots of boxes of screws in the warehouse, and have the corresponding lot numbers: `10001`, `10002`, and `10003`, each with 10 boxes of screws per lot." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:127 +msgid "Lot `10001` entered the stock on June 1, lot `10002` on June 3, and lot `10003` on June 6. A customer orders seven boxes on June 8." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:130 +msgid "Using the :abbr:`LIFO (Last In, First Out)` removal strategy, a transfer is requested for seven boxes of screws from lot `10003` because that lot is the last one to have entered the stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "The detailed operations shows which lots are being selected for the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:138 +msgid "First Expired, First Out (FEFO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:140 +msgid "While the :abbr:`FIFO (First In, First Out)` and :abbr:`LIFO (Last In, First Out)` methods target products for removal based on date of entry into the warehouse, the :guilabel:`First Expired, First Out (FEFO)` method targets products for removal based on their assigned expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:144 +msgid "Using the :abbr:`FEFO (First Expired, First Out)` removal strategy, every sales order that includes products with this removal strategy assigned ensures that transfers are requested for products with the expiration date soonest to the order date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:148 +msgid "As an example, imagine there are three lots of six-egg boxes. Those three lots have the following lot numbers: `20001`, `20002`, and `20003`, each with five boxes in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:151 +msgid "Lot `20001` entered the stock on July 1 and expires on July 15, lot `20002` entered on July 2 and expires on July 14, and lot `20003` entered on July 3 and expires on July 21. A customer orders six boxes on July 5." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:155 +msgid "Using the :abbr:`FEFO (First Expired, First Out)` method, a transfer is requested for the five boxes from lot `20002` and one from lot `20001`. All the boxes in lot `20002` are transferred because they have the earliest expiration date. The transfer also requests one box from lot `20001` because it has the next closest expiration date after lot `20002`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "The detailed operations for the transfer shows the lots to be removed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:165 +msgid "Using removal strategies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:167 +msgid "To differentiate some units of products from others, the units need to be tracked, either by :guilabel:`Lot` or by :guilabel:`Serial Number`. To do so, go to :menuselection:`Inventory --> Configuration --> Settings`. Then, activate the :guilabel:`Storage Locations`, :guilabel:`Multi-Step Routes`, and :guilabel:`Lots & Serial Numbers` settings. Click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid ":alt: Traceability settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid ":alt: Warehouse settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:181 +msgid "To use the :abbr:`FEFO (First Expired, First Out)` removal strategy, the :guilabel:`Expiration Dates` setting needs to be activated as well. To enable this, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the checkbox next to :guilabel:`Expiration Dates`. Remember to click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:187 +msgid "Now, specific removal strategies can be defined on product categories. To do this, go to :menuselection:`Inventory app --> Configuration --> Product Categories`, and choose a product category to define the removal strategy on. In the :guilabel:`Force Removal Strategy` field, choose a removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:192 +msgid "The *First Expired, First Out* (FEFO) strategy is a bit different from the other two removal strategies. For :abbr:`FEFO (First Expired, First Out)`, the expiration date is important, not the date the product entered the stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:196 +msgid "For example, imagine there are three lots of six-egg boxes (in this specific case, don't forget to use :doc:`units of measure <../product_management/configure/uom>`). Those three lots have the following numbers: :guilabel:`20001`, :guilabel:`20002`, and :guilabel:`20003`, each with five boxes in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:201 +msgid ":guilabel:`20001` entered the stock on the 1st of July and expires on the 15th of July, :guilabel:`20002` entered on the 2nd and expires on the 14th of July, and :guilabel:`20003` entered on the 4th and expires on the 21st of July. A customer orders six boxes on the 5th of July. With the :abbr:`FEFO (First Expired, First Out)` strategy selected, a transfer is requested for the five boxes of :guilabel:`20002` and one from :guilabel:`20001`. The transfer for all the boxes in lot :guilabel:`20002` is because they have the closest expiration date. The transfer also requests one box from :guilabel:`20001` because has the next closest expiration date after lot :guilabel:`20002`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:210 +msgid "Basically, for every sales order of a product with the :abbr:`FEFO (First Expired, First Out)` strategy, a transfer is requested for the product that has the nearest expiration date from the order date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:215 +msgid "Closest Location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:217 +msgid "The *Closest Location* strategy is completely different from the other removal strategies. It is not related to the date of entry in the warehouse, but rather the location of the product. It is commonly used for products that do not deteriorate with time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:221 +msgid "The aim is to avoid making the warehouse worker take a long journey to the bottom of the stock when the product is also located at a near location. This method is only available if the :guilabel:`Storage Locations` setting is on. The closest location is actually the one that comes first in the alphabetic order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:227 +msgid "Use removal strategies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:229 +msgid "To differentiate some units from others, the units need to be tracked, either by *lot* or by *serial number*. To do so, go to :menuselection:`Inventory --> Configuration --> Settings`. Then, activate the :guilabel:`Storage Location`, :guilabel:`Multi-Step Routes`, and :guilabel:`Lots & Serial Numbers` settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "Removal strategy on a product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:238 +msgid "To view all products with lots/serial numbers assigned to them, navigate to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. This reveals a page with drop-down menus of all products assigned lots or serial numbers, filtered by *product* by default. To change the category these products are filtered by, click :guilabel:`Product` (in the search bar, in the top right of the page) to remove the default filter, and select a new filter if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "Click on Products, then Lots/Serial Numbers to display all the products with lots or serial\n" +"numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:249 +msgid "To view the serial numbers being selected for a sales order, go to the :guilabel:`Sales app` and select the sales order in question. In the sales order, click the :guilabel:`Delivery` smart button in the top right. In the :guilabel:`Operations` tab, click the :guilabel:`⦙≣ (Detailed Operations)` icon in the far right for the product in question. The :guilabel:`Detailed Operations` window appears, and displays the lot or serial numbers selected for that specific product for the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:257 +msgid "FIFO (First In, First Out)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:259 +msgid "The :abbr:`FIFO (First In, First Out)` removal strategy implies that products which enter a warehouse's stock first are removed first. Companies should use this method if they are selling products with short demand cycles, such as clothes, to ensure they are not stuck with outdated styles in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:264 +msgid "In this example, there are three lots of white shirts. The shirts are from the *All/Clothes* category, where *FIFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "View of the lots of white shirts in the inventory valuation report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:272 +msgid "Lot `000001` contains five shirts, lot `000002` contains three shirts, and lot `000003` contains two shirts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:275 +msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`White Shirt`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (for this example, `6.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:282 +msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the oldest lot numbers will be reserved thanks to the :abbr:`FIFO (First In, First Out)` strategy. All five shirts from lot `000001` and one shirt from lot `000002` will be selected to be sent to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.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.rst:292 +msgid "LIFO (Last In, First Out)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:294 +msgid "The :abbr:`LIFO (Last In, First Out)` removal strategy works in the **opposite** manner from the :abbr:`FIFO (First In, First Out)` strategy. With this method, the products that are received **last** are moved out first. This method is mostly used for products without a shelf life, and no time-sensitive factors, such as expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:299 +msgid "In this example, there are three lots of cinder blocks. The blocks are from the *All/Building Materials* category, where *FIFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "View of the lots of cinder blocks in the inventory valuation report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:307 +msgid "Lot `000020` contains three cinder blocks, lot `000030` contains five cinder blocks, and lot `0000400` contains four cinder blocks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:310 +msgid "To see how the :abbr:`LIFO (Last In, First Out)` strategy works, first navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`, and select a product category (for this example, the :guilabel:`All/Building Materials` category) to edit. This reveals a product category form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:315 +msgid "Once on the product category form, under the :guilabel:`Logistics` section, change the :guilabel:`Force Removal Strategy` to :guilabel:`Last In First Out (LIFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "Last in first out (LIFO) strategy set up as forced removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:322 +msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`Cinder Block`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (for this example, `5.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:329 +msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the newest lot numbers will be reserved thanks to the :abbr:`LIFO (Last In, First Out)` strategy. All four cinder blocks from lot `0000400` and one cinder block from lot `000030` will be selected to be sent to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "Two lots being reserved for sale with the LIFO strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:341 +msgid "FEFO (First Expired, First Out)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:343 +msgid "The :abbr:`FEFO (First Expired, First Out)` removal strategy differs from the :abbr:`FIFO (First In, First Out)` and :abbr:`LIFO (Last In, First Out)` strategies, because it targets products for removal based on **expiration dates** instead of their warehouse receipt dates. With this method, the products that are going to expire first are moved out first. This method is used for perishable products, such as medicine, food, and beauty products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:349 +msgid "Lots are picked based on their **removal date** from earliest to latest. Removal dates indicate how many days *before* the expiration date the product needs to be removed from stock. The removal date is set on the product form. Lots without a removal date defined are picked after lots with removal dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:355 +msgid "If products are not removed from stock when they should be, lots that are past the expiration date may still be picked for delivery orders!" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:359 +msgid ":doc:`../product_management/product_tracking/expiration_dates`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:361 +msgid "First, go to :menuselection:`Inventory app --> Configuration --> Settings` and ensure :guilabel:`Expiration Dates` is enabled. Once the :guilabel:`Expiration Dates` setting is enabled, it's possible to define different expiration dates for individual serialized products, as well as for lot numbers containing many products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:366 +msgid "In this example, there are three lots of hand cream. The creams are from the *All/Health & Beauty* category, where *FEFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:370 +msgid "Lot `0000001` contains twenty tubes of hand cream, expiring on Sept 30, lot `0000002` contains ten tubes of hand cream, expiring on November 30, and lot `0000003` contains ten tubes of hand cream, expiring on October 31." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "View the hand cream lot numbers and expiration dates in the inventory report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:378 +msgid "Expiration dates can be entered when validating the received products, or set on products by going to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Click :guilabel:`Create`, enter the serial number, and select the product from the drop-down menu. Next, select the expiration date in the :guilabel:`Dates` tab. Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "View of the removal date for 0000001." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:387 +msgid "To see how the :abbr:`FEFO (First Expired, First Out)` strategy works, first navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`, and select a product category (in this example, the :guilabel:`All/Health & Beauty` category) to edit. This reveals a product category form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:392 +msgid "Once on the product category form, under the :guilabel:`Logistics` section, change the :guilabel:`Force Removal Strategy` to :abbr:`FEFO (First Expired, First Out)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "FEFO forced removal strategy set on the product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:399 +msgid "Next, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`Hand Cream`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (in this example, `25.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:406 +msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the lot numbers expiring first will be reserved thanks to the :abbr:`FEFO (First Expired, First Out)` strategy. All twenty tubes of hand cream from lot `0000001` and five from lot `0000003` will be selected to be sent to the customer, detailed in the :guilabel:`Detailed Operations` tab in the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:-1 +msgid "Hand cream lot numbers selected for the sales order." +msgstr "" + +#: ../../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 @@ -5661,7 +6866,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 @@ -5786,251 +6991,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:122 +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:123 +msgid ":doc:`multipack`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:3 @@ -6069,6 +7086,204 @@ 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/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:23 +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 "" @@ -6178,16 +7393,120 @@ 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:122 -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:123 -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/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 @@ -6219,7 +7538,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 "" @@ -6499,15 +7818,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 "" @@ -6515,39 +7838,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 "" @@ -6555,11 +7878,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 "" @@ -6567,35 +7890,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 "" @@ -6604,7 +7927,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 @@ -6658,7 +7981,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 @@ -6685,151 +8008,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 "" @@ -6837,11 +8164,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 "" @@ -6849,7 +8176,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 "" @@ -6857,15 +8184,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 "" @@ -6873,23 +8200,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 "" @@ -6897,35 +8224,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 "" @@ -6933,39 +8260,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 "" @@ -6973,11 +8300,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 "" @@ -6985,7 +8312,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 "" @@ -7105,1680 +8432,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/removal.rst:3 -msgid "Removal strategies (FIFO, LIFO, FEFO)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:5 -msgid "For companies with warehouses, **removal strategies** determine which products are taken from the warehouse, and when. Removal strategies are typically defined for specific picking operations. This helps companies to select the best products, optimize the distance workers need to travel when picking items for orders, and account for quality control, such as moving products with expiration dates." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:11 -msgid "Usually, *Removal Strategies* are defined in picking operations to select the best products to optimize the distance for the worker, for quality control purposes, or to first move the products with the closest expiration date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:15 -msgid "When a product needs to be moved, Odoo finds available products that can be assigned to the transfer. The way Odoo assigns these products depends on the :guilabel:`Removal Strategy` defined in either the :guilabel:`Product Category` or the :guilabel:`Location` dashboards." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:19 -msgid "To change the :guilabel:`Removal Strategy`, go to :menuselection:`Inventory app --> Configuration --> Locations` or :menuselection:`Product Categories`. Click on a :guilabel:`Location` or :guilabel:`Product Category`, and then click :guilabel:`Edit`. Change the product category :guilabel:`Force Removal Strategy` or the location :guilabel:`Removal Strategy` by clicking on the drop-down menu and selecting the desired removal strategy. After selecting the new removal strategy, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Change the Force Removal Strategy for either the Product Categories or Locations." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:31 -msgid "What happens inside the warehouse?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:33 -msgid "Most warehouses share the same important areas: receiving docks and sorting areas, storage locations, picking and packing areas, and shipping/loading docks. While all products entering or leaving the warehouse might go through each of these locations at some point, removal strategies can have an effect on which products are taken, from where, and when." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:38 -msgid "In this example below, vendor trucks unload pallets of goods at the receiving docks. Then, operators scan the products in the receiving area, with the reception date and expiration date. After that, products are stored in their respective storage locations." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:43 -msgid "Not all products have expiration dates, but in this example, expiration dates apply." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Products entering stock via the receiving area." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:49 -msgid "In Odoo, receive products by navigating to the :menuselection:`Inventory` application, and in the kanban view, click on either the :guilabel:`Receipts` heading or :guilabel:`# TO PROCESS` button. On the :guilabel:`Receipts` dashboard, find and click on the individual receipt which will open the warehouse intake form. Click :guilabel:`Edit`, and then enter the received quantity in the :guilabel:`Done` column. To finish, :guilabel:`Validate` to receive the products and register them in the Odoo database." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:57 -msgid "Receiving products can also be done within the Odoo *Barcode* application. If using the *Barcode* app, scan the product(s), update the quantity, and finally, click :guilabel:`Validate`. After products are received in Odoo, the products can then be moved to their respective storage locations." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:62 -msgid "Continuing with the same example, below, imagine several sales orders are made for the products received earlier, that use expiration dates. In this example, the products weren't received on the same day, and they don't have the same expiration date. In this situation, logically, sending products with the closest expiration date is preferred, instead of products received first or last. Using the chosen removal strategy configured for those products (in this example, :ref:`FEFO `), Odoo generates a transfer for the products with the soonest expiration date to the picking area, then the packing area, and finally, to the shipping docks for delivery to the customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Products being packed at the packing area for delivery, taking the expiration dates into\n" -"account." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:77 -msgid "To pick for delivery, the product's lot/serial number can be found on the transfer form. To learn more about picking and shipping, refer to either the :ref:`Two-step delivery ` or :ref:`Three-step delivery ` documentation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:83 -msgid "How each removal strategy works" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:85 -msgid "Removal strategies determine which products are taken from the warehouse when orders are confirmed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:88 -msgid "First In, First Out (FIFO)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:90 -msgid "When using a :guilabel:`First In, First Out (FIFO)` strategy, demand for a product triggers a removal rule, which requests a transfer for the lot/serial number that entered the stock first (and therefore, has been in stock for the longest time)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:94 -msgid "For example, imagine there are three lots of nails in the warehouse, and have the corresponding lot numbers: `00001`, `00002`, `00003`. Each lot has five boxes of nails in it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:97 -msgid "Lot `00001` entered the stock on May 23, lot `00002` on May 25, and lot `00003` on June 1. A customer orders six boxes on June 11." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:100 -msgid "Using the :abbr:`FIFO (First In, First Out)` removal strategy, a transfer request will pick the five boxes from lot `00001` first, and then from the boxes in lot `00002`, since lot `00001` entered the stock first. The box from lot `00002` is taken next because it has the oldest receipt date after lot `00001`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "The detailed operations for the transfer shows the nail lots to be removed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:110 -msgid "Last In, First Out (LIFO)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:112 -msgid "Similar to the :abbr:`FIFO (First In, First Out)` method, the :guilabel:`Last In, First Out (LIFO)` removal strategy moves products based on the date they entered a warehouse's stock. Instead of removing the oldest stock on-hand, however, it targets the **newest** stock on-hand for removal." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:116 -msgid "Every time an order for products with the :abbr:`LIFO (Last In, First Out)` method is placed, a transfer is created for the lot/serial number that has most recently entered the stock (the **last** lot/serial number that entered the warehouse's inventory)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:121 -msgid "In many countries, the :abbr:`LIFO (Last In, First Out)` removal strategy in banned, since it can potentially result in old, expired, or obsolete products being delivered to customers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:124 -msgid "For example, imagine there are three lots of boxes of screws in the warehouse, and have the corresponding lot numbers: `10001`, `10002`, and `10003`, each with 10 boxes of screws per lot." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:127 -msgid "Lot `10001` entered the stock on June 1, lot `10002` on June 3, and lot `10003` on June 6. A customer orders seven boxes on June 8." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:130 -msgid "Using the :abbr:`LIFO (Last In, First Out)` removal strategy, a transfer is requested for seven boxes of screws from lot `10003` because that lot is the last one to have entered the stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "The detailed operations shows which lots are being selected for the picking." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:138 -msgid "First Expired, First Out (FEFO)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:140 -msgid "While the :abbr:`FIFO (First In, First Out)` and :abbr:`LIFO (Last In, First Out)` methods target products for removal based on date of entry into the warehouse, the :guilabel:`First Expired, First Out (FEFO)` method targets products for removal based on their assigned expiration dates." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:144 -msgid "Using the :abbr:`FEFO (First Expired, First Out)` removal strategy, every sales order that includes products with this removal strategy assigned ensures that transfers are requested for products with the expiration date soonest to the order date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:148 -msgid "As an example, imagine there are three lots of six-egg boxes. Those three lots have the following lot numbers: `20001`, `20002`, and `20003`, each with five boxes in it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:151 -msgid "Lot `20001` entered the stock on July 1 and expires on July 15, lot `20002` entered on July 2 and expires on July 14, and lot `20003` entered on July 3 and expires on July 21. A customer orders six boxes on July 5." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:155 -msgid "Using the :abbr:`FEFO (First Expired, First Out)` method, a transfer is requested for the five boxes from lot `20002` and one from lot `20001`. All the boxes in lot `20002` are transferred because they have the earliest expiration date. The transfer also requests one box from lot `20001` because it has the next closest expiration date after lot `20002`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "The detailed operations for the transfer shows the lots to be removed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:165 -msgid "Using removal strategies" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:167 -msgid "To differentiate some units of products from others, the units need to be tracked, either by :guilabel:`Lot` or by :guilabel:`Serial Number`. To do so, go to :menuselection:`Inventory --> Configuration --> Settings`. Then, activate the :guilabel:`Storage Locations`, :guilabel:`Multi-Step Routes`, and :guilabel:`Lots & Serial Numbers` settings. Click :guilabel:`Save` to save changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid ":alt: Traceability settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid ":alt: Warehouse settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:181 -msgid "To use the :abbr:`FEFO (First Expired, First Out)` removal strategy, the :guilabel:`Expiration Dates` setting needs to be activated as well. To enable this, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the checkbox next to :guilabel:`Expiration Dates`. Remember to click :guilabel:`Save` to save all changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:187 -msgid "Now, specific removal strategies can be defined on product categories. To do this, go to :menuselection:`Inventory app --> Configuration --> Product Categories`, and choose a product category to define the removal strategy on. In the :guilabel:`Force Removal Strategy` field, choose a removal strategy." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:192 -msgid "The *First Expired, First Out* (FEFO) strategy is a bit different from the other two removal strategies. For :abbr:`FEFO (First Expired, First Out)`, the expiration date is important, not the date the product entered the stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:196 -msgid "For example, imagine there are three lots of six-egg boxes (in this specific case, don't forget to use :doc:`units of measure `). Those three lots have the following numbers: :guilabel:`20001`, :guilabel:`20002`, and :guilabel:`20003`, each with five boxes in it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:202 -msgid ":guilabel:`20001` entered the stock on the 1st of July and expires on the 15th of July, :guilabel:`20002` entered on the 2nd and expires on the 14th of July, and :guilabel:`20003` entered on the 4th and expires on the 21st of July. A customer orders six boxes on the 5th of July. With the :abbr:`FEFO (First Expired, First Out)` strategy selected, a transfer is requested for the five boxes of :guilabel:`20002` and one from :guilabel:`20001`. The transfer for all the boxes in lot :guilabel:`20002` is because they have the closest expiration date. The transfer also requests one box from :guilabel:`20001` because has the next closest expiration date after lot :guilabel:`20002`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:211 -msgid "Basically, for every sales order of a product with the :abbr:`FEFO (First Expired, First Out)` strategy, a transfer is requested for the product that has the nearest expiration date from the order date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:216 -msgid "Closest Location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:218 -msgid "The *Closest Location* strategy is completely different from the other removal strategies. It is not related to the date of entry in the warehouse, but rather the location of the product. It is commonly used for products that do not deteriorate with time." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:222 -msgid "The aim is to avoid making the warehouse worker take a long journey to the bottom of the stock when the product is also located at a near location. This method is only available if the :guilabel:`Storage Locations` setting is on. The closest location is actually the one that comes first in the alphabetic order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:228 -msgid "Use removal strategies" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:230 -msgid "To differentiate some units from others, the units need to be tracked, either by *lot* or by *serial number*. To do so, go to :menuselection:`Inventory --> Configuration --> Settings`. Then, activate the :guilabel:`Storage Location`, :guilabel:`Multi-Step Routes`, and :guilabel:`Lots & Serial Numbers` settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Removal strategy on a product category." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:239 -msgid "To view all products with lots/serial numbers assigned to them, navigate to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. This reveals a page with drop-down menus of all products assigned lots or serial numbers, filtered by *product* by default. To change the category these products are filtered by, click :guilabel:`Product` (in the search bar, in the top right of the page) to remove the default filter, and select a new filter if desired." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Click on Products, then Lots/Serial Numbers to display all the products with lots or serial\n" -"numbers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:250 -msgid "To view the serial numbers being selected for a sales order, go to the :guilabel:`Sales app` and select the sales order in question. In the sales order, click the :guilabel:`Delivery` smart button in the top right. In the :guilabel:`Operations` tab, click the :guilabel:`⦙≣ (Detailed Operations)` icon in the far right for the product in question. The :guilabel:`Detailed Operations` window appears, and displays the lot or serial numbers selected for that specific product for the delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:258 -msgid "FIFO (First In, First Out)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:260 -msgid "The :abbr:`FIFO (First In, First Out)` removal strategy implies that products which enter a warehouse's stock first are removed first. Companies should use this method if they are selling products with short demand cycles, such as clothes, to ensure they are not stuck with outdated styles in stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:265 -msgid "In this example, there are three lots of white shirts. The shirts are from the *All/Clothes* category, where *FIFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "View of the lots of white shirts in the inventory valuation report." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:273 -msgid "Lot `000001` contains five shirts, lot `000002` contains three shirts, and lot `000003` contains two shirts." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:276 -msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`White Shirt`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (for this example, `6.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:283 -msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the oldest lot numbers will be reserved thanks to the :abbr:`FIFO (First In, First Out)` strategy. All five shirts from lot `000001` and one shirt from lot `000002` will be selected to be sent to the customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Two lots being reserved for a sales order with the FIFO strategy." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:293 -msgid "LIFO (Last In, First Out)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:295 -msgid "The :abbr:`LIFO (Last In, First Out)` removal strategy works in the **opposite** manner from the :abbr:`FIFO (First In, First Out)` strategy. With this method, the products that are received **last** are moved out first. This method is mostly used for products without a shelf life, and no time-sensitive factors, such as expiration dates." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:300 -msgid "In this example, there are three lots of cinder blocks. The blocks are from the *All/Building Materials* category, where *FIFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "View of the lots of cinder blocks in the inventory valuation report." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:308 -msgid "Lot `000020` contains three cinder blocks, lot `000030` contains five cinder blocks, and lot `0000400` contains four cinder blocks." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:311 -msgid "To see how the :abbr:`LIFO (Last In, First Out)` strategy works, first navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`, and select a product category (for this example, the :guilabel:`All/Building Materials` category) to edit. This reveals a product category form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:316 -msgid "Once on the product category form, under the :guilabel:`Logistics` section, change the :guilabel:`Force Removal Strategy` to :guilabel:`Last In First Out (LIFO)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Last in first out (LIFO) strategy set up as forced removal strategy." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:323 -msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`Cinder Block`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (for this example, `5.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:330 -msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the newest lot numbers will be reserved thanks to the :abbr:`LIFO (Last In, First Out)` strategy. All four cinder blocks from lot `0000400` and one cinder block from lot `000030` will be selected to be sent to the customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Two lots being reserved for sale with the LIFO strategy." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:342 -msgid "FEFO (First Expired, First Out)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:344 -msgid "The :abbr:`FEFO (First Expired, First Out)` removal strategy differs from the :abbr:`FIFO (First In, First Out)` and :abbr:`LIFO (Last In, First Out)` strategies, because it targets products for removal based on **expiration dates** instead of their warehouse receipt dates. With this method, the products that are going to expire first are moved out first. This method is used for perishable products, such as medicine, food, and beauty products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:350 -msgid "Lots are picked based on their **removal date** from earliest to latest. Removal dates indicate how many days *before* the expiration date the product needs to be removed from stock. The removal date is set on the product form. Lots without a removal date defined are picked after lots with removal dates." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:356 -msgid "If products are not removed from stock when they should be, lots that are past the expiration date may still be picked for delivery orders!" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:360 -msgid "For more information about expiration dates, reference the :doc:`Expiration dates <../../product_management/product_tracking/expiration_dates>` document." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:363 -msgid "First, go to :menuselection:`Inventory app --> Configuration --> Settings` and ensure :guilabel:`Expiration Dates` is enabled. Once the :guilabel:`Expiration Dates` setting is enabled, it's possible to define different expiration dates for individual serialized products, as well as for lot numbers containing many products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:368 -msgid "In this example, there are three lots of hand cream. The creams are from the *All/Health & Beauty* category, where *FEFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:372 -msgid "Lot `0000001` contains twenty tubes of hand cream, expiring on Sept 30, lot `0000002` contains ten tubes of hand cream, expiring on November 30, and lot `0000003` contains ten tubes of hand cream, expiring on October 31." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "View the hand cream lot numbers and expiration dates in the inventory report." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:380 -msgid "Expiration dates can be entered when validating the received products, or set on products by going to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Click :guilabel:`Create`, enter the serial number, and select the product from the drop-down menu. Next, select the expiration date in the :guilabel:`Dates` tab. Finally, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "View of the removal date for 0000001." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:389 -msgid "To see how the :abbr:`FEFO (First Expired, First Out)` strategy works, first navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`, and select a product category (in this example, the :guilabel:`All/Health & Beauty` category) to edit. This reveals a product category form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:394 -msgid "Once on the product category form, under the :guilabel:`Logistics` section, change the :guilabel:`Force Removal Strategy` to :abbr:`FEFO (First Expired, First Out)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "FEFO forced removal strategy set on the product category." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:401 -msgid "Next, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`Hand Cream`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (in this example, `25.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:408 -msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the lot numbers expiring first will be reserved thanks to the :abbr:`FEFO (First Expired, First Out)` strategy. All twenty tubes of hand cream from lot `0000001` and five from lot `0000003` will be selected to be sent to the customer, detailed in the :guilabel:`Detailed Operations` tab in the sales order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:-1 -msgid "Hand cream lot numbers selected for the sales order." -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 "" @@ -8805,7 +8458,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 @@ -9327,70 +8980,6 @@ msgstr "" msgid ":doc:`count_products`" 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 "" @@ -9499,18 +9088,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 "" @@ -9518,79 +9107,79 @@ 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 +msgid ":guilabel:`Company`: the company the location belongs to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:60 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:62 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 "The form for creating a new location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:74 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:76 msgid "Cyclic Counting section" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:78 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:79 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:81 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:82 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:84 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:87 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:89 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 "" @@ -9598,31 +9187,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:95 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:97 msgid "Logistics section" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:99 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:103 -msgid ":doc:`../advanced_operations_warehouse/removal`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:108 msgid "Current stock at location" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:110 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:111 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:113 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:115 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:117 msgid "A list of current stock at `Shelf 1` consists of `266` cabinets and `39` desks." msgstr "" @@ -9630,601 +9215,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: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/management/one_step_manufacturing>`, :doc:`two <../../../manufacturing/management/two_step_manufacturing>`, or :doc:`three steps <../../../manufacturing/management/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 "" @@ -10233,7 +9300,7 @@ msgid "Example warehouse form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation.rst:5 -#: ../../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:280 msgid "Inventory valuation" msgstr "" @@ -10389,69 +9456,346 @@ msgstr "" msgid "From the product category's configuration page, choose the desired :guilabel:`Costing Method`:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:85 -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:88 +msgid "Standard Price" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:89 -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:90 +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:94 -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:98 +#: ../../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:210 +msgid "Operation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:99 +#: ../../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:211 +msgid "Unit Cost" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:100 -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:141 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:212 +msgid "Qty On Hand" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:142 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:213 +msgid "Incoming Value" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:102 +#: ../../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:214 +msgid "Inventory Value" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:104 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:109 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:114 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:119 +#: ../../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:150 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:221 +msgid "$10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:146 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:217 +msgid "0" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:107 +#: ../../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:148 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:216 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:219 +msgid "$0" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:108 -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:149 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:220 +msgid "Receive 8 products for $10/unit" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:110 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:151 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:222 +msgid "8" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:111 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:152 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:223 +msgid "8 * $10" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:112 -msgid ":doc:`using_inventory_valuation`" +#: ../../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:224 +msgid "$80" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:114 -msgid "When the :guilabel:`Costing Method` is changed, products already in stock that were using the :guilabel:`Standard` costing method **do not** change value; rather, the existing units keep their value, and any product moves from then on affect the average cost, and the cost of the product will change. If the value in the :guilabel:`Cost` field on a product form is changed manually, Odoo will generate a corresponding record in the *Inventory Valuation* report." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:113 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:154 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:225 +msgid "Receive 4 products for $16/unit" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:156 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:227 +msgid "12" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:116 +msgid "4 * $10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:117 +msgid "$120" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:118 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:159 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:230 +msgid "Deliver 10 products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:161 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:232 +msgid "2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:121 +msgid "-10 * $10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:122 +msgid "$20" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:123 +msgid "Receive 2 products for $9/unit" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:125 -msgid "Inventory valuation in Odoo can be set to be updated manually or automatically. While *Expense* accounts apply to both, the *Stock Input* and *Stock Output* accounts are only used for automated valuation." +#: ../../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:238 +msgid "4" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:126 +msgid "2 * $10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:127 +msgid "$40" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:129 +msgid "Average Cost (AVCO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:131 +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:155 +#: ../../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:226 +msgid "$12" +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:228 +msgid "4 * $16" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:158 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:229 +msgid "$144" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:162 +msgid "-10 * $12" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:163 +msgid "$24" +msgstr "" + +#: ../../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:236 +msgid "Receive 2 products for $6/unit" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:165 +msgid "$9" +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:239 +msgid "2 * $6" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:168 +msgid "$36" +msgstr "" + +#: ../../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:242 +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:172 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:244 +msgid "When receiving four products for $16 each:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:174 +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:176 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:248 +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:179 +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:183 +msgid "Receive two products for $6 each:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:185 +msgid "Inventory value: :math:`$24 + (2 * $6) = $36`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:186 +msgid "Unit cost: :math:`$36 / 4 = $9`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:189 +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:196 +msgid "First In First Out (FIFO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:198 +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:203 +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:231 +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:235 +msgid "$32" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:237 +msgid "$11" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:240 +msgid "$44" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:246 +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:251 +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:254 +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:256 +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:258 +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:261 +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:265 +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:269 +msgid ":doc:`using_inventory_valuation`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:271 +msgid "When the :guilabel:`Costing Method` is changed, products already in stock that were using the :guilabel:`Standard` costing method **do not** change value; rather, the existing units keep their value, and any product moves from then on affect the average cost, and the cost of the product will change. If the value in the :guilabel:`Cost` field on a product form is changed manually, Odoo will generate a corresponding record in the *Inventory Valuation* report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:282 +msgid "Inventory valuation in Odoo can be set to be updated manually or automatically. While *Expense* accounts apply to both, the *Stock Input* and *Stock Output* accounts are only used for automated valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:286 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:135 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:292 msgid "Expense account" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:137 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:294 msgid "To configure the *expense account*, 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:141 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:298 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:146 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:214 +#: ../../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:371 msgid "Anglo-Saxon" 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:177 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:307 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:334 msgid "Automated" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:152 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:309 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:156 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:313 msgid "In the pop-up window, choose :guilabel:`Expenses` or :guilabel:`Cost of Revenue` from the :guilabel:`Type` drop-down menu." msgstr "" @@ -10459,7 +9803,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:165 +#: ../../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:339 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:174 +msgid "Manual" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:322 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 "" @@ -10467,49 +9817,49 @@ msgstr "" msgid "Show the **Expense Account** field." msgstr "" -#: ../../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:232 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:330 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:389 msgid "Continental" 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:184 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:336 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:341 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:190 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:347 msgid "Stock input/output (automated only)" 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:349 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:196 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:353 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:199 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:356 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:201 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:358 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:203 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:360 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:207 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:364 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:216 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:373 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:221 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:378 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 "" @@ -10517,15 +9867,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:229 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:386 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:234 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:391 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:239 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:396 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 "" @@ -10533,23 +9883,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:249 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:406 msgid "Inventory valuation reporting" 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 "To start, go to :menuselection:`Accounting --> Reporting --> Balance Sheet`. At the top of the dashboard, change the :guilabel:`As of` field value to :guilabel:`Today`, and adjust the filtering :guilabel:`Options` to :guilabel:`Unfold All` in order to see all of the latest data displayed, all at once." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:257 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:414 msgid ":doc:`../../../../finance/accounting/get_started/cheat_sheet`" 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 "Under the parent :guilabel:`Current Assets` line item, look for the nested :guilabel:`Stock Valuation Account` line item, where the total valuation of all of the inventory on hand is displayed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:263 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:420 msgid "Access more specific information with the :guilabel:`Stock Valuation Account` drop-down menu, by selecting either the :guilabel:`General Ledger` to see an itemized view of all of the journal entries, or by selecting :guilabel:`Journal Items` to review all of the individualized journal entries that were submitted to the account. As well, annotations to the :guilabel:`Balance Sheet` can be added by choosing :guilabel:`Annotate`, filling in the text box, and clicking :guilabel:`Save`." msgstr "" @@ -10614,7 +9964,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 @@ -10725,6 +10075,1264 @@ msgstr "" msgid "`Odoo Tutorial: Inventory Valuation `_" msgstr "" +#: ../../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/replenishment.rst:19 +msgid "Terminology" +msgstr "" + +#: ../../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/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/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/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/replenishment.rst:36 +msgid "Make to order" +msgstr "" + +#: ../../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/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/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/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/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/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/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/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/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/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/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/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/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/replenishment.rst:101 +msgid "Replenishment report fields" +msgstr "" + +#: ../../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/replenishment.rst:107 +msgid ":guilabel:`Product`: the product that requires a replenishment." +msgstr "" + +#: ../../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/replenishment.rst:109 +msgid ":guilabel:`Warehouse`: the warehouse where the product is stored." +msgstr "" + +#: ../../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/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/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/replenishment.rst:115 +msgid ":guilabel:`Vendor`: the company from which the product is acquired." +msgstr "" + +#: ../../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/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/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/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/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/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/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/replenishment.rst:131 +msgid ":guilabel:`UoM`: the unit of measure used to acquire the product." +msgstr "" + +#: ../../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/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/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/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/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/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/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/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/replenishment.rst:161 +msgid "Make to order (MTO) route" +msgstr "" + +#: ../../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/replenishment.rst:172 +msgid "To activate the |MTO| route in Odoo:" +msgstr "" + +#: ../../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/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/replenishment.rst:169 +msgid "Then, go to :menuselection:`Inventory app --> Configuration --> Routes`." +msgstr "" + +#: ../../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/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/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/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/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/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/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/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/replenishment.rst:-1 +msgid "Replenish on Order selected on the product form." +msgstr "" + +#: ../../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/replenishment/lead_times.rst:5 +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/replenishment/lead_times.rst:10 +msgid "Lead time types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:12 +msgid "Different lead times for different operations can impact various stages of the order fulfillment process. Here's a summary of the types of lead times in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/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/replenishment/lead_times.rst:19 +msgid ":ref:`Customer lead time `: The default time frame for fulfilling customer orders. The customer lead time is the number of days from the date the sales order (SO) is confirmed to the date the products are shipped from the warehouse. This is also known as *delivery lead time*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:24 +msgid ":ref:`Sales security lead time `: moves the *scheduled delivery date* forward by a specified number of days. This serves as a buffer to allow the team ample time to prepare the outgoing shipment earlier, considering the possibility of delays in the fulfillment process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:29 +msgid ":ref:`Purchase lead time `: the number of days from the confirmation of a purchase order (PO) to the receipt of products. It provides insight on the time it takes for products to arrive at the warehouse, facilitating effective scheduling and planning of supplier deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:34 +msgid ":ref:`Purchase security lead time `: advances the order deadline on a :abbr:`PO (Purchase Order)` by a specified number of days. This proactive approach of placing orders earlier mitigates the risk of vendor or shipping delays. Thus, for products that are set to replenish to order, the need appears on the *Replenishment report* earlier, according to the specified number of days." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:40 +msgid ":ref:`Manufacturing lead time `: the number of days needed to complete a manufacturing order (MO) from the date of confirmation. This lead time includes weekends (non-working hours in Odoo), and is used to forecast an approximate production date for a finished good." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:45 +msgid ":ref:`Manufacturing security lead time `: moves the scheduled date of the :abbr:`MO (Manufacturing Order)` forward by a specified number of days. When used in conjunction with :ref:`replenish to order `, the security lead time makes the need appear earlier on the replenishment report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:53 +msgid "Sales lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:55 +msgid "Customer lead times and sales security lead times can be configured to automatically compute an *expected delivery date* on a :abbr:`SO (Sales Order)`. The expected delivery date ensures a realistic *delivery dates* setting for shipments from the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:59 +msgid "Odoo issues a warning message if the set delivery date is earlier than the expected date, as it may not be feasible to fulfill the order by that time, which would impact other warehouse operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:63 +msgid "A :abbr:`SO (Sales Order)` containing a `Coconut-scented candle` is confirmed on July 11th. The product has a customer lead time of 14 days, and the business uses a sales security lead time of 1 day. Based on the lead time inputs, Odoo suggests a delivery date in 15 days, on July 26th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/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/replenishment/lead_times.rst:71 +msgid "The following sections demonstrate how to automatically compute expected delivery dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:74 +msgid "Customer lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:76 +msgid "Set the customer lead time on each product form, by navigating to the products page. To do so, go to :menuselection:`Sales app --> Products --> Products`. From there, select the desired product, and switch to the :guilabel:`Inventory` tab. Then, under the :guilabel:`Customer Lead Time` field, fill in the number of calendar days required to fulfill the delivery order from start to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:82 +msgid "Set a 14-day customer lead time for the `Coconut-scented candle` by navigating to its product form. Then, in the :guilabel:`Inventory` tab, type `14.00` days into the :guilabel:`Customer Lead Time` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/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/replenishment/lead_times.rst:93 +msgid "Sales security lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:95 +msgid "*Sales security lead time* is set globally for the business in :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:98 +msgid "On the configuration page, under the :guilabel:`Advanced Scheduling` heading, locate the box for :guilabel:`Security Lead Time for Sales`, and click the checkbox to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:101 +msgid "Next, enter the desired number of calendar days. This security lead time is a buffer notifying the team to prepare for outgoing shipments earlier than the scheduled date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:105 +msgid "Setting the :guilabel:`Security Lead Time for Sales` to `1.00` day, pushes the :guilabel:`Scheduled Date` of a delivery order (DO) forward by one day. In that case, if a product is initially scheduled for delivery on April 6th, but with a one-day security lead time, the new scheduled date for the delivery order would be April 5th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/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/replenishment/lead_times.rst:115 +msgid "Deliver several products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:117 +msgid "For orders that include multiple products with different lead times, the lead times can be configured directly from the quotation itself. On a quotation, click the :guilabel:`Other Info` tab, and set the :guilabel:`Shipping Policy` to:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:121 +msgid ":guilabel:`As soon as possible` to deliver products as soon as they are ready. The :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is determined by adding today's date to the shortest lead time among the products in the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:125 +msgid ":guilabel:`When all products are ready` to wait to fulfill the entire order at once. The :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is determined by adding today's date to the longest lead time among the products in the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/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/replenishment/lead_times.rst:134 +msgid "In a quotation containing 2 products, `Yoga mat` and `Resistance band,` the products have a lead time of 8 days and 5 days, respectively. Today's date is April 2nd." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:137 +msgid "When the :guilabel:`Shipping Policy` is set to :guilabel:`As soon as possible`, the scheduled delivery date is 5 days from today: April 7th. On the other hand, selecting :guilabel:`When all products are ready` configures the scheduled date to be 8 days from today: April 10th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:144 +msgid "Purchase lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:146 +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/replenishment/lead_times.rst:149 +msgid "Odoo calculates the supplier shipment *receipt date*, and :abbr:`PO (Purchase Order)` deadline, based on the required date the product is needed in the warehouse. By working backwards from the receipt date, vendor lead times and purchase security lead times are taken into account, in order to determine the :abbr:`PO (Purchase Order)` deadline." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:154 +msgid "This deadline is the date by which the order should be confirmed, in order to ensure timely arrival by the expected receipt date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/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/replenishment/lead_times.rst:162 +msgid ":ref:`PO scheduling with reordering rules `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:165 +msgid "Vendor lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:167 +msgid "To set a vendor lead time for orders arriving in the warehouse from a vendor location, begin by navigating to a product form through :menuselection:`Purchase app --> Products --> Products`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:170 +msgid "Next, select the desired product, and switch to the :guilabel:`Purchase` tab. In the editable vendor pricelist, click the :guilabel:`Add a line` button to add vendor details, such as the :guilabel:`Vendor` name, :guilabel:`Price` offered for the product, and lastly, the :guilabel:`Delivery Lead Time`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:176 +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/replenishment/lead_times.rst:180 +msgid "On the vendor pricelist of the product form, the :guilabel:`Delivery Lead Time` for the selected vendor is set to `10 days.`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/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/replenishment/lead_times.rst:187 +msgid "By setting the vendor lead time, the expected arrival date of the item is automatically determined as the date of the :abbr:`PO (Purchase Order)` confirmation, plus the vendor lead time. This ensures that warehouse employees are notified, if the products do **not** arrive within the expected timeframe." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:193 +msgid "On a :abbr:`PO (Purchase Order)` confirmed on July 11th, for a product configured with a 10-day vendor lead time, Odoo automatically sets the :guilabel:`Receipt Date` to July 21st. The receipt date also appears as the :guilabel:`Scheduled Date` on the warehouse receipt form, accessible from the :guilabel:`Receipt` smart button, located on the :guilabel:`PO (Purchase Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/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/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/replenishment/lead_times.rst:209 +msgid "Purchase security lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:211 +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/replenishment/lead_times.rst:214 +msgid "On the configuration page, under the :guilabel:`Advanced Scheduling` heading, locate the box for :guilabel:`Security Lead Time for Purchase`, and click the checkbox to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:217 +msgid "Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is set to account for potential delays in supplier deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:221 +msgid "Setting the :guilabel:`Security Lead Time for Purchase` to `2.00` days, pushes the :guilabel:`Scheduled Date` of receipt back by one day. In that case, if a product is initially scheduled to arrive on April 6th, with a two-day security lead time, the new scheduled date for the receipt would be April 8th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/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/replenishment/lead_times.rst:233 +msgid "Manufacturing lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:235 +msgid "Lead times can help simplify the procurement process for consumable materials and components used in manufactured products with bills of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:238 +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/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/replenishment/lead_times.rst:247 +msgid "Manufacturing lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:249 +msgid "Configure the manufacturing lead time directly on the product form, by navigating to :menuselection:`Manufacturing app --> Products --> Products`, and select the desired product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:252 +msgid "In the :guilabel:`Inventory` tab of the product, specify the calendar days needed to the manufacture the product in the :guilabel:`Manufacturing Lead Time` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:256 +msgid "Specify a 14-day :guilabel:`Manufacturing Lead Time` for a product directly in the :guilabel:`Inventory` tab of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:0 +msgid "View of the manufacturing lead time configuration from the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:263 +msgid "Establish a :abbr:`MO (Manufacturing Order)` deadline, based on the *expected delivery date*, indicated in the :guilabel:`Scheduled Date` field of the :abbr:`DO (Delivery Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:266 +msgid "The :abbr:`MO (Manufacturing Order)` deadline, which is the :guilabel:`Scheduled Date` field on the :abbr:`MO (Manufacturing Order)`, is calculated as the *expected delivery date* subtracted by the manufacturing lead time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:270 +msgid "This ensures the manufacturing process begins on time, in order to meet the delivery date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:272 +msgid "However, it's important to note that lead times are based on calendar days. Lead times do **not** consider weekends, holidays, or *work center capacity* (:dfn:`the number of operations that can be performed at the work center simultaneously`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:277 +msgid ":ref:`Manufacturing planning `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:278 +msgid ":ref:`Configure automatic MO scheduling with reordering rules `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:282 +msgid "A product's scheduled shipment date on the :abbr:`DO (Delivery Order)` is August 15th. The product requires 14 days to manufacture. So, the latest date to start the :abbr:`MO (Manufacturing Order)` to meet the commitment date is August 1st." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:289 +msgid "Manufacturing security lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:291 +msgid "*Manufacturing security lead time* is set globally for the business in :menuselection:`Manufacturing app --> Configuration --> Settings`. Under the :guilabel:`Planning` heading, locate the box for :guilabel:`Security Lead Time`, and click the checkbox to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:295 +msgid "Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is set to account for potential delays in the manufacturing process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/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/replenishment/lead_times.rst:303 +msgid "A product has a scheduled shipment date on the :abbr:`DO (Delivery Order)` set for August 15th. The manufacturing lead time is 7 days, and manufacturing security lead time is 3 days. So, the :guilabel:`Scheduled Date` on the :abbr:`MO (Manufacturing Order)` reflects the latest date to begin the manufacturing order. In this example, the planned date on the :abbr:`MO (Manufacturing Order)` is August 5th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:310 +msgid "Global example" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:312 +msgid "See the following example to understand how all the lead times work together to ensure timely order fulfillment:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:315 +msgid "**Sales security lead time**: 1 day" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:316 +msgid "**Manufacturing security lead time**: 2 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:317 +msgid "**Manufacturing lead time**: 3 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:318 +msgid "**Purchase security lead time**: 1 day" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:319 +msgid "**Vendor lead time**: 4 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:321 +msgid "The customer places an order for a manufactured product on September 1st, and the scheduled delivery date from the warehouse is on September 20th. Odoo uses lead times and automated reordering rules to schedule the necessary operations, based on the outgoing shipment delivery date, September 20th:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/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/replenishment/lead_times.rst:329 +msgid "**September 1st**: Sales order created, confirmed by salesperson." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:331 +msgid "**September 9th**: Deadline to order components to ensure they arrive in time when manufacturing begins (4-day supplier lead time)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:334 +msgid "**September 13th**: Scheduled date of receipt for components. Initially, it was set to 9/14, but the 1-day purchase security lead time pushed the date earlier by 1 day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:337 +msgid "**September 14th**: Deadline to begin manufacturing. Calculated by subtracting the manufacturing lead time of 3 days, and the manufacturing security lead time of 2 days, from the expected delivery date of September 19th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:341 +msgid "**September 19th**: :guilabel:`Scheduled Date` on the delivery order form indicates the updated expected delivery date, which was originally set as September 20th. But the sales security lead time pushed the date forward by a day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.rst:345 +msgid "Odoo's replenishment planning maps a business' order fulfillment process, setting pre-determined deadlines and raw material order dates, including buffer days for potential delays. This ensures products are delivered on time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.rst:3 +msgid "Replenish on order (MTO)" +msgstr "" + +#: ../../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/replenishment/mto.rst:17 +msgid "Unarchive the Replenish on Order (MTO) route" +msgstr "" + +#: ../../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/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/replenishment/mto.rst:-1 +msgid "The archived filter on the Routes page." +msgstr "" + +#: ../../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/replenishment/mto.rst:-1 +msgid "The unarchive action on the Routes page." +msgstr "" + +#: ../../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/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/replenishment/mto.rst:47 +msgid "Configure a product to use the MTO route" +msgstr "" + +#: ../../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/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/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/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/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/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/replenishment/mto.rst:-1 +msgid "Enable \"Can be Purchased\" and specify a vendor." +msgstr "" + +#: ../../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:7 +msgid "Reordering rules are used to keep forecasted stock levels above a certain threshold without exceeding a specified upper limit. This is accomplished by specifying a minimum quantity that stock should not fall below and a maximum quantity that stock should not exceed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:11 +msgid "Reordering rules can be configured for each product based on the route used to replenish it. If a product uses the *Buy* route, then a Request for Quotation (RFQ) is created when the reordering rule is triggered. If a product uses the *Manufacture* route, then a Manufacturing Order (MO) is created instead. This is the case regardless of the selected replenishment route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:17 +msgid "`Odoo Tutorials: Automatic Reordering Rules `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:18 +msgid "`Odoo Tutorials: Manual Reordering Rules `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:21 +msgid "Configure products for reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:23 +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:27 +msgid "On the product form, under the :guilabel:`General Information` tab, make sure that the :guilabel:`Product Type` is set to :guilabel:`Storable Product`. This is necessary because Odoo only tracks stock quantities for storable products, and this number is used to trigger reordering rules." +msgstr "" + +#: ../../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:35 +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:42 +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:51 +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:55 +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:64 +msgid "Create new reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:66 +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:69 +msgid ":guilabel:`Product`: The product that is replenished by the rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:70 +msgid ":guilabel:`Location`: The location where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:71 +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:74 +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:75 +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:77 +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:85 +msgid "Reordering rules can also be created from each product form. To do so, navigate to :menuselection:`Inventory app --> Products --> Products`, then select a product. Click on :menuselection:`Reordering Rules smart button --> New`, then fill out the new line, as detailed above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:90 +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:92 +msgid ":ref:`Trigger `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:93 +msgid ":ref:`Visibility days `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:94 +msgid ":ref:`Preferred route `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:97 +msgid "The fields above are not available by default, and must be enabled by selecting the :guilabel:`(slider)` icon in the far-right corner, and selecting the desired column from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:104 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:106 +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:109 +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:114 +msgid ":doc:`../replenishment`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:117 +msgid "The :guilabel:`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:120 +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:129 +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:133 +msgid "Auto" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:135 +msgid "Automatic reordering rules, enabled by setting the reordering rule's :guilabel:`Trigger` field to :guilabel:`Auto`, generate purchase or manufacturing orders when:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:138 +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:139 +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:142 +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:144 +msgid "To manually trigger a reordering rule before the scheduler runs, ensure :ref:`developer mode ` is enabled, and then select :menuselection:`Inventory app --> Operations --> Run Scheduler`. Then, select the green :guilabel:`Run Scheduler` button on the pop-up window that appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:149 +msgid "Be aware that this also triggers *any other* scheduled actions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:152 +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:160 +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:164 +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:168 +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:176 +msgid "Manual reordering rules, configured by setting the reordering rule's :guilabel:`Trigger` field to :guilabel:`Manual`, list 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, for which the forecasted quantity is not enough." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:181 +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:186 +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:-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:197 +msgid "Visibility days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:200 +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:202 +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:208 +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:211 +msgid "The current date is February twentieth, and the *delivery date* on a sales order (in the :guilabel:`Other Info` tab) is March third — twelve days from the current date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:214 +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:217 +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 twenty-seventh." +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 27." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:225 +msgid "To see the product on the replenishment dashboard for the current date, February twentieth, set the :guilabel:`Visibility Days` to `7.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:228 +msgid "To determine the number 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:231 +msgid "Visibility~days = Need~appears~date - Today's~date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:236 +msgid "Referring to the example above, today's date is February twentieth, and the need for the product appears on February twenty-seventh." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:239 +msgid "(February 27 - February 20 = 7 days)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:241 +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:251 +msgid "Preferred route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:253 +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:257 +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` or :menuselection:`Inventory app --> Operations --> Replenishment`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:262 +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:270 +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: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/maintenance.rst:8 msgid "Maintenance" msgstr "" diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index 17384e1e6..d53f5252b 100644 --- a/locale/sources/marketing.pot +++ b/locale/sources/marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-04-29 10:38+0000\n" +"POT-Creation-Date: 2024-08-21 07:41+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -33,7 +33,7 @@ msgid "Odoo *Email Marketing* provides professional-grade email design tools, te msgstr "" #: ../../content/applications/marketing/email_marketing.rst:17 -#: ../../content/applications/marketing/email_marketing.rst:219 +#: ../../content/applications/marketing/email_marketing.rst:220 #: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:74 msgid ":doc:`/applications/marketing/email_marketing/mailing_lists`" msgstr "" @@ -43,15 +43,19 @@ msgstr "" msgid ":doc:`/applications/marketing/email_marketing/unsubscriptions`" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:21 +#: ../../content/applications/marketing/email_marketing.rst:19 +msgid ":doc:`/applications/marketing/email_marketing/analyze_metrics`" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:22 msgid "Email marketing dashboard" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:23 +#: ../../content/applications/marketing/email_marketing.rst:24 msgid "To get started, click on the :menuselection:`Email Marketing` app icon, located on the main Odoo dashboard, which leads to the main :guilabel:`Email Marketing` dashboard (in the default kanban view)." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:27 +#: ../../content/applications/marketing/email_marketing.rst:28 msgid "To see all the mailings in the database, remove the default :guilabel:`My Mailings` filter from the search bar." msgstr "" @@ -59,51 +63,51 @@ msgstr "" msgid "View of the main dashboard of the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:35 +#: ../../content/applications/marketing/email_marketing.rst:36 msgid "In the search bar, by default, the filter: :guilabel:`My Mailings` is present. That means the only information being seen (at that time) on the :guilabel:`Email Marketing` dashboard are emails that the current user has created, sent, or is responsible for." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:39 +#: ../../content/applications/marketing/email_marketing.rst:40 msgid "This filter can be removed by clicking the :guilabel:`X` next to :guilabel:`My Mailings` in the search bar. Doing so, reveals all the information for every email in the database." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:43 +#: ../../content/applications/marketing/email_marketing.rst:44 msgid "Default kanban view and stages" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:45 +#: ../../content/applications/marketing/email_marketing.rst:46 msgid "The four kanban columns each represent the various stages of emails that have been built or sent within the *Email Marketing* application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:48 +#: ../../content/applications/marketing/email_marketing.rst:49 msgid "The stages are: :guilabel:`Draft`, :guilabel:`In Queue`, :guilabel:`Sending`, :guilabel:`Sent`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:50 +#: ../../content/applications/marketing/email_marketing.rst:51 msgid ":guilabel:`Draft`: means the email is still being written/created." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:51 +#: ../../content/applications/marketing/email_marketing.rst:52 msgid ":guilabel:`In Queue`: means the email is scheduled, and sent at a later date." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:52 +#: ../../content/applications/marketing/email_marketing.rst:53 msgid ":guilabel:`Sending`: means the email is currently being sent to its recipients." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:53 +#: ../../content/applications/marketing/email_marketing.rst:54 msgid ":guilabel:`Sent`: means the email has already been sent to its recipients." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:55 +#: ../../content/applications/marketing/email_marketing.rst:56 msgid "In each stage, there are drag-and-drop cards representing the email campaigns that have been created, and the stage they are in represents the current status of that mailing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:58 +#: ../../content/applications/marketing/email_marketing.rst:59 msgid "Each mailing block on the :guilabel:`Email Marketing` dashboard provides key information related to that specific email." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:61 +#: ../../content/applications/marketing/email_marketing.rst:62 msgid "When the cursor hovers over the upper-right corner of an email campaign card, three vertical dots (:guilabel:`⋮`) appear. When clicked, a mini drop-down menu reveals the option to color-code the email :guilabel:`Delete` the email altogether, or :guilabel:`Archive` the message for potential future use." msgstr "" @@ -111,16 +115,16 @@ msgstr "" msgid "View of the three-dot drop-down menu on the Odoo Email Marketing dashboard." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:70 +#: ../../content/applications/marketing/email_marketing.rst:71 msgid "In the upper-right corner of the main :guilabel:`Email Marketing` dashboard, there are other view options to choose from: :guilabel:`List` and :guilabel:`Graph`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:74 +#: ../../content/applications/marketing/email_marketing.rst:75 #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:420 msgid "List view" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:76 +#: ../../content/applications/marketing/email_marketing.rst:77 msgid "The :guilabel:`List` view (represented by the :guilabel:`☰ (three vertical lines)` icon) provides the same key information, but in a classic list format." msgstr "" @@ -128,11 +132,11 @@ msgstr "" msgid "How the List view appears in the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:84 +#: ../../content/applications/marketing/email_marketing.rst:85 msgid "Graph view" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:86 +#: ../../content/applications/marketing/email_marketing.rst:87 msgid "The :guilabel:`Graph` view (represented by the :guilabel:`📊 (bar graph)` icon) provides the same key information, but in a variety of customizable graph (and chart) layouts." msgstr "" @@ -140,31 +144,31 @@ msgstr "" msgid "How the Graph view appears in the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:93 +#: ../../content/applications/marketing/email_marketing.rst:94 msgid "In the upper-left corner, there is a :guilabel:`Measures` menu, providing even more filter options to further customize the graph views." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:96 +#: ../../content/applications/marketing/email_marketing.rst:97 msgid "Those :guilabel:`Measures` options are: :guilabel:`A/B Testing percentage`, :guilabel:`Color Index`, and :guilabel:`Count` (which is selected, by default)." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:100 +#: ../../content/applications/marketing/email_marketing.rst:101 msgid "Filters, Group By, and Favorites search options" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:102 +#: ../../content/applications/marketing/email_marketing.rst:103 msgid "Regardless of the view chosen for the :guilabel:`Email Marketing` dashboard, the :guilabel:`Filters`, :guilabel:`Group by`, and :guilabel:`Favorites` options are always available." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:105 +#: ../../content/applications/marketing/email_marketing.rst:106 msgid "These options provide various ways to specify and organize the information seen on the :guilabel:`Email Marketing` dashboard." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:110 +#: ../../content/applications/marketing/email_marketing.rst:111 msgid "Filters" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:112 +#: ../../content/applications/marketing/email_marketing.rst:113 msgid "This drop-down menu provides different ways to filter email campaigns on the dashboard. The options are: :guilabel:`My Mailings`, :guilabel:`Sent Date`, :guilabel:`Archived`, and :guilabel:`Add Custom Filter`. If :guilabel:`Add Custom Filter` is selected, Odoo reveals an additional drop-down menu, with three customizable fields to fill in, in order to retrieve results that fit more specific criteria." msgstr "" @@ -172,19 +176,19 @@ msgstr "" msgid "View of filters drop-down menu options on the Odoo Email Marketing dashboard." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:121 +#: ../../content/applications/marketing/email_marketing.rst:122 msgid "Group By" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:123 +#: ../../content/applications/marketing/email_marketing.rst:124 msgid "This drop-down menu provides additional ways to organize the data on the dashboard by grouping them in specific ways. Using this drop-down menu, the data can be grouped by the messages' :guilabel:`Status`, or who it was :guilabel:`Sent By`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:127 +#: ../../content/applications/marketing/email_marketing.rst:128 msgid "There is also the option to group the data by :guilabel:`Sent Period`, which has its own sub-menu of options to choose from. The :guilabel:`Sent Period` options are :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:131 +#: ../../content/applications/marketing/email_marketing.rst:132 msgid "If none of the above :guilabel:`Group By` options deliver the desired results, click :guilabel:`Add Custom Group` at the bottom of the drop-down menu. Doing so reveals a new field, wherein custom criteria can be selected and applied, thus delivering any grouping of data that may be desired." msgstr "" @@ -192,11 +196,11 @@ msgstr "" msgid "View of the Group By drop-down menu on the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:139 +#: ../../content/applications/marketing/email_marketing.rst:140 msgid "Favorites" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:141 +#: ../../content/applications/marketing/email_marketing.rst:142 msgid "This drop-down menu provides different ways to incorporate past search filters and other record-related options to customize the dashboard. The options are: :guilabel:`Save current search`, :guilabel:`Import records`, :guilabel:`Add to my dashboard`, and :guilabel:`Add to Google Spreadsheet`." msgstr "" @@ -204,11 +208,11 @@ msgstr "" msgid "View of the Favorites drop-down menu on the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:150 +#: ../../content/applications/marketing/email_marketing.rst:151 msgid "Settings" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:152 +#: ../../content/applications/marketing/email_marketing.rst:153 msgid "To view (and modify) the *Email Marketing* settings, navigate to :menuselection:`Email Marketing application --> Configuration --> Settings`." msgstr "" @@ -216,31 +220,31 @@ msgstr "" msgid "View of the Settings page in the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:159 +#: ../../content/applications/marketing/email_marketing.rst:160 msgid "On this :guilabel:`Settings` page, there are three features available. The features are: :guilabel:`Mailing Campaigns`, :guilabel:`Blacklist Option when Unsubscribing`, and :guilabel:`Dedicated Server`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:163 +#: ../../content/applications/marketing/email_marketing.rst:164 msgid ":guilabel:`Mailing Campaigns`: enables the option to manage mass mailing campaigns." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:164 +#: ../../content/applications/marketing/email_marketing.rst:165 msgid ":guilabel:`Blacklist Option when Unsubscribing`: allows recipients to blacklist themselves from future mailings during the unsubscribing process." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:166 +#: ../../content/applications/marketing/email_marketing.rst:167 msgid ":guilabel:`Dedicated Server`: provides the option to utilize a separate, dedicated server for mailings. When enabled, Odoo reveals a new field (and link), in which the specific server configurations must be entered, in order for it to connect properly to Odoo." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:171 +#: ../../content/applications/marketing/email_marketing.rst:172 msgid "Create an email" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:173 +#: ../../content/applications/marketing/email_marketing.rst:174 msgid "To create an email, open the :menuselection:`Email Marketing` application, and click the :guilabel:`Create` button in the upper-left corner." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:176 +#: ../../content/applications/marketing/email_marketing.rst:177 msgid "Clicking :guilabel:`Create` reveals a blank email detail form." msgstr "" @@ -248,31 +252,31 @@ msgstr "" msgid "View of a blank email detail form in Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:182 +#: ../../content/applications/marketing/email_marketing.rst:183 msgid "First, enter a :guilabel:`Subject` to the email. The :guilabel:`Subject` is visible in the recipients' inbox, allowing them to get quickly see what the message is about." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:186 +#: ../../content/applications/marketing/email_marketing.rst:187 msgid "The :guilabel:`Subject` field is mandatory. An email can not be sent without a :guilabel:`Subject`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:190 +#: ../../content/applications/marketing/email_marketing.rst:191 msgid "The :guilabel:`☺ (smiley face)` icon at the end of the :guilabel:`Subject` field (and :guilabel:`Preview Text` field) represents emojis. Click that :guilabel:`☺ (smiley face)` icon to reveal a menu of emojis that can be used in either field." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:194 +#: ../../content/applications/marketing/email_marketing.rst:195 msgid "Next, there is the option to enter some :guilabel:`Preview Text`. This text is a catchy preview sentence that encourages recipients to open the message. In most inboxes, this is displayed next to the subject." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:199 +#: ../../content/applications/marketing/email_marketing.rst:200 msgid "Keep the :guilabel:`Preview Text` empty to show the first characters of the email content, instead." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:203 +#: ../../content/applications/marketing/email_marketing.rst:204 msgid "Recipients" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:205 +#: ../../content/applications/marketing/email_marketing.rst:206 msgid "After that, it's time to choose the recipients of this email, which can be completed in the :guilabel:`Recipients` field." msgstr "" @@ -280,67 +284,67 @@ msgstr "" msgid "View of recipients drop-down menu in the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:212 +#: ../../content/applications/marketing/email_marketing.rst:213 msgid "The default option is :guilabel:`Mailing List`. If :guilabel:`Mailing List` option is selected, a specific :guilabel:`Mailing List` needs to be chosen from the adjacent :guilabel:`Select mailing lists` field drop-down menu." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:216 +#: ../../content/applications/marketing/email_marketing.rst:217 msgid "Then, Odoo will only send this email to contacts on that specific mailing list." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:221 +#: ../../content/applications/marketing/email_marketing.rst:222 msgid "When the :guilabel:`Recipients` field is clicked, a drop-down menu of other options is revealed. Each option provides different ways Odoo can create a target audience for the email." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:224 +#: ../../content/applications/marketing/email_marketing.rst:225 msgid "Those options (excluding the default :guilabel:`Mailing List`) provide the option to create a more specified recipient filter, in an equation-like format." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:227 +#: ../../content/applications/marketing/email_marketing.rst:228 msgid "The :guilabel:`Recipients` field options are as follows:" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:229 +#: ../../content/applications/marketing/email_marketing.rst:230 msgid ":guilabel:`Applicant`: filter focuses on specific job applicants in the database." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:230 +#: ../../content/applications/marketing/email_marketing.rst:231 msgid ":guilabel:`Contact`: filter focuses on specific contacts in the database." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:231 +#: ../../content/applications/marketing/email_marketing.rst:232 msgid ":guilabel:`Event Registration`: filter focuses on people in the database who purchased event registrations." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:233 +#: ../../content/applications/marketing/email_marketing.rst:234 msgid ":guilabel:`Event Track`: filter focuses on people in the database who hosted a specific talk (track) at an event." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:235 +#: ../../content/applications/marketing/email_marketing.rst:236 msgid ":guilabel:`Lead/Opportunity`: filter focuses on leads or opportunities in the database." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:236 +#: ../../content/applications/marketing/email_marketing.rst:237 msgid ":guilabel:`Mailing Contact`: filter focuses on specific mailing contacts in the database." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:237 +#: ../../content/applications/marketing/email_marketing.rst:238 msgid ":guilabel:`Sales Order`: filter focuses on a specific sales orders in the database." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:239 +#: ../../content/applications/marketing/email_marketing.rst:240 msgid "If the specified recipient fields don't automatically reveal themselves, simply click the :guilabel:`Add Filter` button beneath the :guilabel:`Recipients` field, and Odoo reveals the necessary equation fields to further drill down the target recipients for this mailing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:244 +#: ../../content/applications/marketing/email_marketing.rst:245 msgid "Add a recipient filter" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:246 +#: ../../content/applications/marketing/email_marketing.rst:247 msgid "To add a more specified recipient filter, select any recipient option (other than :guilabel:`Mailing List`), and clicking :guilabel:`Add Filter`, if needed, to reveal three fields, formatted like an equation." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:250 +#: ../../content/applications/marketing/email_marketing.rst:251 msgid "To reveal the sub-menu options, click each field, and make the desired selections, until the preferred configuration has been achieved. The number of :guilabel:`Records` that match the rule(s) are indicated to the right of the :guilabel:`Recipients` field, in green." msgstr "" @@ -348,28 +352,28 @@ msgstr "" msgid "View of how recipient filters can be customized in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:259 +#: ../../content/applications/marketing/email_marketing.rst:260 #: ../../content/applications/marketing/events/event_essentials.rst:191 msgid "Some sub-menu options in the first rule field allow for a second choice to provide even more specificity." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:262 +#: ../../content/applications/marketing/email_marketing.rst:263 msgid "To the right of each rule, are :guilabel:`× (Delete node)`, :guilabel:`＋ (Add node)`, and :guilabel:`⋯ (Add branch)` icons." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:265 +#: ../../content/applications/marketing/email_marketing.rst:266 msgid "The :guilabel:`× (Delete node)` icon deletes a specific node (line) of the rule. The :guilabel:`＋ (Add node)` icon adds a node (line) to the rule. And, the :guilabel:`⋯ (Add branch)` icon adds a branch to the node. A branch means two additional, indented sub-nodes are added to the rule, providing even more specificity to the line above it." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:271 +#: ../../content/applications/marketing/email_marketing.rst:272 msgid "Mail body tab" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:273 +#: ../../content/applications/marketing/email_marketing.rst:274 msgid "At the bottom of the email form are two tabs: :guilabel:`Mail Body` and :guilabel:`Settings`. Let's focus on :guilabel:`Mail Body` tab first." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:276 +#: ../../content/applications/marketing/email_marketing.rst:277 msgid "In the :guilabel:`Mail Body` tab, there are a number of pre-configured message templates to choose from. Select the desired template, and modify every element of its design details with Odoo's drag-and-drop building blocks, located on the right sidebar. Each building block provides unique features and professional design elements." msgstr "" @@ -377,23 +381,23 @@ msgstr "" msgid "View of the building blocks used to create mailings in Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:286 +#: ../../content/applications/marketing/email_marketing.rst:287 msgid "To build an email from scratch, select the :guilabel:`Plain Text` template, and Odoo provides a blank email canvas, which can be customized in a number of ways - either by using the front-end rich text editor that accepts slash (:guilabel:`/`) commands, or with the XML code editor when :ref:`Developer Mode (debug mode) ` is engaged, and the :guilabel:`` icon is clicked." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:293 +#: ../../content/applications/marketing/email_marketing.rst:294 msgid "Settings tab" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:295 +#: ../../content/applications/marketing/email_marketing.rst:296 msgid "To the right of the :guilabel:`Mail Body` tab is the :guilabel:`Settings` tab." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:298 +#: ../../content/applications/marketing/email_marketing.rst:299 msgid "The options available in the :guilabel:`Settings` tab will be different, depending on if the :guilabel:`Mailing Campaigns` feature is activated in the :guilabel:`Settings` page of the :menuselection:`Email Marketing` application (:menuselection:`Email Marketing --> Configuration --> Settings`)." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:303 +#: ../../content/applications/marketing/email_marketing.rst:304 msgid "Without the :guilabel:`Mailing Campaigns` feature activated, the :guilabel:`Settings` tab on the email detail form looks like this:" msgstr "" @@ -401,23 +405,23 @@ msgstr "" msgid "View of settings tab in Odoo Email Marketing app, without settings activated." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:310 +#: ../../content/applications/marketing/email_marketing.rst:311 msgid ":guilabel:`Responsible`: choose an employee (in the database) to be responsible for this particular email." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:312 +#: ../../content/applications/marketing/email_marketing.rst:313 msgid ":guilabel:`Send From`: designate an email alias that'll display as the sender of this particular email." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:314 +#: ../../content/applications/marketing/email_marketing.rst:315 msgid ":guilabel:`Reply To`: designate an email alias to whom all the replies to this particular email will be sent." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:316 +#: ../../content/applications/marketing/email_marketing.rst:317 msgid ":guilabel:`Attachments`: if any specific documents are required (or helpful) for this event invite, they can be sent along with this email, by clicking :guilabel:`ATTACH A FILE`, and adding the appropriate document(s)." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:320 +#: ../../content/applications/marketing/email_marketing.rst:321 msgid "When the :guilabel:`Mailing Campaigns` feature *is* activated, additional :guilabel:`Marketing` options appear in the :guilabel:`Settings` tab, which look like this:" msgstr "" @@ -425,15 +429,15 @@ msgstr "" msgid "View of settings tab in Odoo Email Marketing when settings are activated." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:327 +#: ../../content/applications/marketing/email_marketing.rst:328 msgid "The additional features are: :guilabel:`Mailing Campaign`, :guilabel:`Allow A/B Testing`, and :guilabel:`A/B Testing percentage`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:331 +#: ../../content/applications/marketing/email_marketing.rst:332 msgid "Mailing campaigns" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:333 +#: ../../content/applications/marketing/email_marketing.rst:334 msgid "The :guilabel:`Mailing Campaign` field provides the option to add this particular email to a previously-made email campaign in the database. Click the empty field to reveal a drop-down menu containing all previously-made mailing campaigns in the database." msgstr "" @@ -441,19 +445,19 @@ msgstr "" msgid "View of a mailing campaign drop-down menu in Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:341 +#: ../../content/applications/marketing/email_marketing.rst:342 msgid "If the desired campaign isn't available in the initial drop-down menu, select :guilabel:`Search More` to reveal a complete list of all mailing campaigns in the database. Or, type the name of the desired mailing campaign in the :guilabel:`Mailing Campaign` field, until Odoo reveals the desired campaign in the drop-down menu. Then, select the desired campaign." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:347 +#: ../../content/applications/marketing/email_marketing.rst:348 msgid "Create new mailing campaign (from Settings tab)" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:349 +#: ../../content/applications/marketing/email_marketing.rst:350 msgid "To create a new campaign from this :guilabel:`Mailing Campaign` field, start typing the name of this new campaign, and select :guilabel:`Create [Campaign Name]` or :guilabel:`Create and Edit...`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:352 +#: ../../content/applications/marketing/email_marketing.rst:353 msgid "Click :guilabel:`Create` to add this new mailing campaign to the database, and modify its settings in the future. And click :guilabel:`Create and Edit...` to add this new mailing campaign to the database, and Odoo reveals a pop-up window." msgstr "" @@ -461,31 +465,31 @@ msgstr "" msgid "View of the email mailing campaign pop-up window in Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:360 +#: ../../content/applications/marketing/email_marketing.rst:361 msgid "Here, the new mailing campaign can be further customized. Adjust the :guilabel:`Campaign Name`, assign a :guilabel:`Responsible`, and add :guilabel:`Tags`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:363 +#: ../../content/applications/marketing/email_marketing.rst:364 msgid "The top row of the :guilabel:`Create: Mailing Campaign` pop-up window is filled with analytical smart buttons. Each of which displays various metrics related to the campaign. When clicked, Odoo reveals a separate, more detailed page with even more in-depth statistics." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:367 +#: ../../content/applications/marketing/email_marketing.rst:368 msgid "The option to instantly a new communication from this pop-up window is available in the upper-left corner. The adjustable status bar is located in the upper-right." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:370 +#: ../../content/applications/marketing/email_marketing.rst:371 msgid "When all modifications are ready to be finalized, click :guilabel:`Save`. To delete the entire campaign, click :guilabel:`Discard`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:374 +#: ../../content/applications/marketing/email_marketing.rst:375 msgid "Create new mailing campaign (from Campaigns page)" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:376 +#: ../../content/applications/marketing/email_marketing.rst:377 msgid "When the :guilabel:`Mailing Campaigns` feature is activated, a new :guilabel:`Campaigns` option appears in the header of the *Email Marketing* application. Campaigns can also be created on this :guilabel:`Campaigns` page in the *Email Marketing* app." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:380 +#: ../../content/applications/marketing/email_marketing.rst:381 msgid "To do that, navigate to :menuselection:`Email Marketing app --> Campaigns --> Create`. When that's clicked, a pop-up window appears, in which the :guilabel:`Campaign Name`, :guilabel:`Responsible`, and :guilabel:`Tags` can be added directly on the :guilabel:`Campaigns` dashboard." msgstr "" @@ -493,62 +497,202 @@ msgstr "" msgid "View of the campaign pop-up window in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:388 +#: ../../content/applications/marketing/email_marketing.rst:389 msgid "Click :guilabel:`Add` to add the campaign to the database, and freely edit it later on. Or, click :guilabel:`Edit` and Odoo reveals the campaign template form on a separate page, providing the opportunity to further edit the campaign, send communications related to the campaign, and analyze various metrics related to the campaign, via the smart buttons at the top of the form." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:394 +#: ../../content/applications/marketing/email_marketing.rst:395 msgid "A/B testing" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:396 +#: ../../content/applications/marketing/email_marketing.rst:397 msgid "Back in the :guilabel:`Settings` tab of the mailing, if the :guilabel:`Allow A/B Testing` box is checked, recipients are only be mailed to once. This allows different mailings to be sent to randomly selected recipients. This tests the overall effectiveness of the mailing, and eliminates the need for duplicate messages." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:401 +#: ../../content/applications/marketing/email_marketing.rst:402 msgid "The :guilabel:`A/B Testing percentage` field represents the percentage of contacts in the database that this message will be mailed to, as a part of the :guilabel:`A/B Testing`. Enter a number between `1-100`. The recipients are randomly chosen." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:406 +#: ../../content/applications/marketing/email_marketing.rst:407 msgid "Send, schedule, or test" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:408 +#: ../../content/applications/marketing/email_marketing.rst:409 msgid "After finalizing the mailing, Odoo provides the following options in the upper-left corner of the email template page. Those options are: :guilabel:`Send`, :guilabel:`Schedule`, and :guilabel:`Test`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:412 +#: ../../content/applications/marketing/email_marketing.rst:413 msgid "While in :guilabel:`Edit` mode, there are also buttons to :guilabel:`Save` or :guilabel:`Discard` the mailing, as well." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:415 +#: ../../content/applications/marketing/email_marketing.rst:416 msgid ":guilabel:`Send` - Click to have Odoo send the email to the desired recipients. When Odoo has sent the mailing, the status changes to *Sent*." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:417 +#: ../../content/applications/marketing/email_marketing.rst:418 msgid ":guilabel:`Schedule` - Click to reveal a pop-up window, in which a future date-time is chosen. Odoo sends the mailing to the desired recipients at that specified date-time. When a date-time is chosen, the status of the mailing changes to *In Queue*." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:420 +#: ../../content/applications/marketing/email_marketing.rst:421 msgid ":guilabel:`Test` - Click to reveal a pop-up window, in which Odoo allows a sample email to be sent for testing purposes. Enter the desired recipient's email address in the :guilabel:`Recipients` field, and click :guilabel:`Send Sample Mail`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:423 +#: ../../content/applications/marketing/email_marketing.rst:424 msgid ":guilabel:`Save` - Click to save the mailing as a draft, which can be edited (and sent) at a later date. When clicked, the status of the mailing stays as :guilabel:`Draft`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:425 +#: ../../content/applications/marketing/email_marketing.rst:426 msgid ":guilabel:`Discard` - Click to discard any changes that have been made since the last save." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:428 +#: ../../content/applications/marketing/email_marketing.rst:429 msgid "When :guilabel:`Save` or :guilabel:`Discard` is selected (while in :guilabel:`Edit` mode), those options are replaced with an :guilabel:`Edit` button and a :guilabel:`Create` button. Click :guilabel:`Edit` to re-enter :guilabel:`Edit` mode. Click :guilabel:`Create` to start creating a new mailing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:434 +#: ../../content/applications/marketing/email_marketing.rst:435 msgid "By default, there's a daily limit applied for **all emails** sent throughout *all* applications. So, if there are remaining emails to be sent after a limit has been reached, those mailings *will not* be sent automatically the next day. The sending needs to be forced, by opening the email and clicking :guilabel:`Retry`." msgstr "" +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:3 +msgid "Analyze metrics" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:7 +msgid "To properly understand the success or failure of an email marketing campaign, it is necessary to monitor several key metrics. The insights gained from these metrics can then be used to optimize future campaigns. Odoo's **Email Marketing** application tracks several :ref:`key metrics `, which can be interpreted to improve future campaigns." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:13 +msgid "View metrics" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:15 +msgid "After a mass mail has been sent, the results for that particular mailing are displayed in multiple locations." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:18 +msgid "To access the metrics for an individual mailing, navigate to :menuselection:`Email Marketing app --> Mailings`. Locate the specific mailing in the list view, and use the column headings to view the results for that mailing. Click on one of the mailings in the list to open the record. At the top of the record, detailed metrics are displayed as smart buttons." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:-1 +msgid "The smart buttons on a mass mailing, displaying the results of the message." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:27 +msgid "Below is a non-comprehensive selection of percentage-based metrics that are key for analyzing the success of an email marketing campaign." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:31 +msgid "Click on any smart button to see the recipient records for that respective metric." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:36 +msgid "Opened rate" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:38 +msgid "The :guilabel:`Opened` rate measures the percentage of emails opened by recipients against the total number of sent emails." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:41 +msgid "A high open rate may indicate the subject line was timely, compelling, and successfully prompted the recipients to view the message." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:44 +msgid "A low open rate may indicate the subject line failed to capture the recipients' interest. It could also indicate the email ended up in a spam or junk folder, due to having a poor sender reputation, or failing to :doc:`configure the proper DNS records <../../general/email_communication/email_domain>`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:50 +msgid "Replied rate" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:52 +msgid "The :guilabel:`Replied` rate measures the percentage of recipients who responded to the email directly against the total number of sent emails." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:55 +msgid "A high replied rate may indicate the email resonated with recipients, prompting them to take action or provide feedback." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:58 +msgid "A low replied rate may suggest that the message lacked relevance or did not contain a clear call-to-action." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:62 +msgid "Clicked rate" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:64 +msgid "The :guilabel:`Clicked` rate, represents the *Click Through Rate (CTR)*, which measures the percentage of recipients who clicked on a link within the email against the total number of sent emails." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:68 +msgid "A high |CTR| may indicate the email content was relevant and appropriately targeted. Recipients were motivated to click the links provided, and likely found the content engaging." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:71 +msgid "A low |CTR| may indicate issues with either the targeting, or the content itself. If there were any calls to action, recipients may have been unmotivated, or the message itself may have been directed toward the wrong audience." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:76 +msgid "Received rate" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:78 +msgid "The *Received* rate measures the percentage of emails successfully delivered against the total number of sent emails." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:81 +msgid "A high received rate can indicate the mailing list used is up-to-date and the sender authentication is trusted by email providers." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:84 +msgid "A low received rate may indicate issues with either the mailing list used for the mailing, or with the sender authentication. View the :ref:`email-marketing/deliverability-issues` section for more information." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:89 +msgid "Bounced rate" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:91 +msgid "The *Bounced* rate measures the percentage of emails unsuccessfully delivered, against the total number of sent emails." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:94 +msgid "A high bounce rate could indicate issues with either the mailing list used for the mailing, or with the sender authentication." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:97 +msgid "A low bounce rate may indicate the mailing list used is up-to-date and the sender authentication is trusted by email providers. View the :ref:`email-marketing/deliverability-issues` section for more information." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:104 +msgid "Deliverability issues" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:106 +msgid "The following defines possible reasons for a high bounce rate or low received rate:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:108 +msgid "Using a mailing list that contains outdated contact information, or malformed email addresses, is likely to result in a high bounce rate and/or a low received rate." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:110 +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 :doc:`DMARC authentication <../../general/email_communication/email_domain>`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:113 +msgid "Failing to :doc:`configure the proper DNS records <../../general/email_communication/email_domain>` can also result in a high bounce rate." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:117 +msgid ":doc:`Mailing campaigns <../email_marketing>`" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:118 +msgid ":doc:`Manage unsubscriptions `" +msgstr "" + #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:3 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:15 msgid "Mailing lists" diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index f995218e3..58541825e 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 10:38+0000\n" +"POT-Creation-Date: 2024-08-21 07:41+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1037,7 +1037,7 @@ msgid "Create sub-workspaces from the left menu" msgstr "" #: ../../content/applications/productivity/documents.rst:58 -#: ../../content/applications/productivity/sign.rst:241 +#: ../../content/applications/productivity/sign.rst:281 msgid "Tags" msgstr "" @@ -2143,58 +2143,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 "" @@ -2202,76 +2362,76 @@ msgstr "" msgid "Signature status" msgstr "" -#: ../../content/applications/productivity/sign.rst:118 +#: ../../content/applications/productivity/sign.rst:158 #: ../../content/applications/productivity/spreadsheet/templates.rst:3 msgid "Templates" msgstr "" -#: ../../content/applications/productivity/sign.rst:120 +#: ../../content/applications/productivity/sign.rst:160 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:125 +#: ../../content/applications/productivity/sign.rst:165 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:131 +#: ../../content/applications/productivity/sign.rst:171 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:136 +#: ../../content/applications/productivity/sign.rst:176 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 ⋮, then :guilabel:`Template`. Click on ⋮ again, then :guilabel:`Restore`. Your document now appears on your dashboard next to your other templates." msgstr "" -#: ../../content/applications/productivity/sign.rst:144 +#: ../../content/applications/productivity/sign.rst:184 msgid "Roles" msgstr "" -#: ../../content/applications/productivity/sign.rst:146 +#: ../../content/applications/productivity/sign.rst:186 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:150 +#: ../../content/applications/productivity/sign.rst:190 msgid "Roles are available by going to :menuselection:`Sign --> Configuration --> Roles`." msgstr "" -#: ../../content/applications/productivity/sign.rst:152 +#: ../../content/applications/productivity/sign.rst:192 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:160 +#: ../../content/applications/productivity/sign.rst:200 msgid "Secured identification" msgstr "" -#: ../../content/applications/productivity/sign.rst:162 +#: ../../content/applications/productivity/sign.rst:202 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:168 +#: ../../content/applications/productivity/sign.rst:208 msgid ":doc:`In-App Purchase (IAP) <../essentials/in_app_purchase>`" msgstr "" -#: ../../content/applications/productivity/sign.rst:169 +#: ../../content/applications/productivity/sign.rst:209 msgid ":doc:`SMS pricing and FAQ <../marketing/sms_marketing/pricing/pricing_and_faq>`" msgstr "" -#: ../../content/applications/productivity/sign.rst:174 +#: ../../content/applications/productivity/sign.rst:214 msgid "SMS verification" msgstr "" -#: ../../content/applications/productivity/sign.rst:176 +#: ../../content/applications/productivity/sign.rst:216 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:180 +#: ../../content/applications/productivity/sign.rst:220 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:184 +#: ../../content/applications/productivity/sign.rst:224 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:188 +#: ../../content/applications/productivity/sign.rst:228 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 "" @@ -2279,27 +2439,27 @@ msgstr "" msgid "Add a hash to your document" msgstr "" -#: ../../content/applications/productivity/sign.rst:196 +#: ../../content/applications/productivity/sign.rst:236 msgid "This feature is enabled by default." msgstr "" -#: ../../content/applications/productivity/sign.rst:197 +#: ../../content/applications/productivity/sign.rst:237 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:203 +#: ../../content/applications/productivity/sign.rst:243 msgid "Itsme®" msgstr "" -#: ../../content/applications/productivity/sign.rst:205 +#: ../../content/applications/productivity/sign.rst:245 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:208 +#: ../../content/applications/productivity/sign.rst:248 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:213 +#: ../../content/applications/productivity/sign.rst:253 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 "" @@ -2307,19 +2467,19 @@ msgstr "" msgid "select customer identified with itsme®" msgstr "" -#: ../../content/applications/productivity/sign.rst:219 +#: ../../content/applications/productivity/sign.rst:259 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:224 +#: ../../content/applications/productivity/sign.rst:264 msgid "Signatory hash" msgstr "" -#: ../../content/applications/productivity/sign.rst:226 +#: ../../content/applications/productivity/sign.rst:266 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:231 +#: ../../content/applications/productivity/sign.rst:271 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 "" @@ -2327,103 +2487,103 @@ msgstr "" msgid "Adding the visual security frame to a signature." msgstr "" -#: ../../content/applications/productivity/sign.rst:243 +#: ../../content/applications/productivity/sign.rst:283 msgid "Tags can be used to categorize and organize documents, allowing users to search for and filter documents based on specific criteria quickly." msgstr "" -#: ../../content/applications/productivity/sign.rst:246 +#: ../../content/applications/productivity/sign.rst:286 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:250 +#: ../../content/applications/productivity/sign.rst:290 msgid "To apply a tag to a document, use the dropdown list available in your document." msgstr "" -#: ../../content/applications/productivity/sign.rst:253 +#: ../../content/applications/productivity/sign.rst:293 msgid "Sign order" msgstr "" -#: ../../content/applications/productivity/sign.rst:255 +#: ../../content/applications/productivity/sign.rst:295 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:258 +#: ../../content/applications/productivity/sign.rst:298 msgid "By going to :menuselection:`Configuration --> Settings`, you can :guilabel:`Enable Signing Order`. Each recipient receives the signature request notification only once the previous recipient has completed their action." msgstr "" -#: ../../content/applications/productivity/sign.rst:262 +#: ../../content/applications/productivity/sign.rst:302 msgid "Add at least two :guilabel:`Signature` fields with different roles to your document. Click :guilabel:`Send`, go to the :guilabel:`Options` tab, and tick the :guilabel:`Specify signing order` box." msgstr "" -#: ../../content/applications/productivity/sign.rst:266 +#: ../../content/applications/productivity/sign.rst:306 msgid "Add the signer's :guilabel:`Name or email` information. You can decide on the :guilabel:`Sign Order` by typing :guilabel:`1` or :guilabel:`2` in the :guilabel:`Sign Order` column." msgstr "" -#: ../../content/applications/productivity/sign.rst:270 +#: ../../content/applications/productivity/sign.rst:310 msgid "`Odoo Quick Tips: Sign order [video] `_" msgstr "" -#: ../../content/applications/productivity/sign.rst:275 +#: ../../content/applications/productivity/sign.rst:315 msgid "Field types" msgstr "" -#: ../../content/applications/productivity/sign.rst:277 +#: ../../content/applications/productivity/sign.rst:317 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:281 +#: ../../content/applications/productivity/sign.rst:321 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:285 +#: ../../content/applications/productivity/sign.rst:325 msgid "To create and edit field types, go to :menuselection:`Sign --> Configuration --> Settings --> Edit field types`." msgstr "" -#: ../../content/applications/productivity/sign.rst:288 +#: ../../content/applications/productivity/sign.rst:328 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:291 +#: ../../content/applications/productivity/sign.rst:331 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:294 +#: ../../content/applications/productivity/sign.rst:334 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:296 +#: ../../content/applications/productivity/sign.rst:336 msgid ":guilabel:`Text`: users enter text on a single line." msgstr "" -#: ../../content/applications/productivity/sign.rst:297 +#: ../../content/applications/productivity/sign.rst:337 msgid ":guilabel:`Multiline Text`: users enter text on multiple lines." msgstr "" -#: ../../content/applications/productivity/sign.rst:298 +#: ../../content/applications/productivity/sign.rst:338 msgid ":guilabel:`Checkbox`: users can tick a box (e.g., to mark their approval or consent)." msgstr "" -#: ../../content/applications/productivity/sign.rst:299 +#: ../../content/applications/productivity/sign.rst:339 msgid ":guilabel:`Selection`: users choose a single option from a variety of options." msgstr "" -#: ../../content/applications/productivity/sign.rst:301 +#: ../../content/applications/productivity/sign.rst:341 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:306 +#: ../../content/applications/productivity/sign.rst:346 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:310 +#: ../../content/applications/productivity/sign.rst:350 msgid "Auto-completed values are suggestions and can be modified as required by the person signing the document." msgstr "" -#: ../../content/applications/productivity/sign.rst:313 +#: ../../content/applications/productivity/sign.rst:353 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:319 +#: ../../content/applications/productivity/sign.rst:359 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 "" @@ -2431,6 +2591,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 "" @@ -2447,32 +3713,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 "" @@ -2481,218 +3721,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 "" @@ -2700,8 +3732,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 @@ -2710,6 +3744,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 "" @@ -2782,6 +3888,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 "" @@ -2810,14 +3953,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 "" @@ -2854,6 +4244,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 "" @@ -2890,6 +4420,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 "" @@ -2926,6 +4588,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 "" @@ -2962,6 +4936,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 "" @@ -2998,6 +5076,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 "" @@ -3034,6 +5284,78 @@ 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 "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index bb3320e53..e80626367 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 10:38+0000\n" +"POT-Creation-Date: 2024-08-21 07:41+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -49,7 +49,7 @@ msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:10 #: ../../content/applications/sales/crm/optimize/gamification.rst:11 #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:27 -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:44 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:60 #: ../../content/applications/sales/point_of_sale/configuration.rst:6 #: ../../content/applications/sales/point_of_sale/employee_login.rst:13 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:13 @@ -175,6 +175,7 @@ msgid "To compare the details of the similar leads/opportunities, click the :gui msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:95 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:44 msgid "When merging, Odoo gives priority to whichever lead/opportunity was created in the system first, merging the information into the first created lead/opportunity. However, if a lead and an opportunity are being merged, the resulting record is referred to as an opportunity, regardless of which record was created first." msgstr "" @@ -195,6 +196,7 @@ msgid "Below those fields, the leads/opportunities to merge are listed, along wi msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:116 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:11 msgid "When merging opportunities, no information is lost. Data from the other opportunity is logged in the chatter, and the information fields, for reference." msgstr "" @@ -1228,6 +1230,123 @@ msgstr "" msgid ":doc:`../performance/win_loss`" msgstr "" +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:3 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:41 +msgid "Merge similar leads and opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:5 +msgid "Odoo automatically detects similar *leads* and *opportunities* within the **CRM** app. These identified duplicate records can be merged, without losing any information in the process. Doing so keep the pipeline organized, and prevents customers from being contacted by more than one salesperson." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:15 +msgid "Identify similar leads and opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:17 +msgid "Similar leads and opportunities are identified by comparing the email address and phone number of the associated contact. If a similar lead/opportunity is found, a *Similar Leads* smart button appears at the top of the lead (or opportunity) record." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:-1 +msgid "An opportunity record with emphasis on the Similar Leads smart button." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:26 +msgid "Compare similar leads and opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:28 +msgid "To compare the details of similar leads/opportunities, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`, or :menuselection:`CRM app --> Leads`. Open a lead or opportunity, and click the :guilabel:`Similar Leads` smart button. Doing so opens an :guilabel:`Opportunities` page, in Kanban view, that only displays similar leads/opportunities. Click on a card to view the details for the lead/opportunity, and confirm if they should be merged." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:35 +msgid "*Leads* will not appear in the header menu unless the leads feature has been activated. This can be done by navigating to :guilabel:`CRM app --> Configuration --> Settings` and ticking the checkbox next to :guilabel:`Leads`, then clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:49 +msgid "After confirming the leads/opportunities should be merged, return to the :guilabel:`Opportunities` page, in Kanban view, using the breadcrumb link, or by clicking the :guilabel:`Similar Leads` smart button on the opportunity form. Click the :icon:`oi-view-list` :guilabel:`(list)` icon to change to list view." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:54 +msgid "Tick the checkbox on the left of the page for the leads/opportunities to be merged. Then, click the :icon:`fa-cog` :guilabel:`Action` icon at the top of the page, to reveal a drop-down menu. From that drop-down menu, select the :guilabel:`Merge` option to merge the selected opportunities or leads." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:59 +msgid "When :guilabel:`Merge` is selected from the :icon:`fa-cog` :guilabel:`Action` drop-down menu, a :guilabel:`Merge` pop-up modal appears. In that pop-up modal, under the :guilabel:`Assign opportunities to` section, optionally select a :guilabel:`Salesperson` and :guilabel:`Sales Team` from the appropriate drop-down menus." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:64 +msgid "Below those fields, the leads/opportunities to merge are listed, along with their related information. To add more, click :guilabel:`Add a line`, tick the checkbox next to the desired leads/opportunities from the resulting :guilabel:`Add: Leads/Opportunities' pop-up modal, then click the :guilabel:`Select` button. The additional selections now appear in the list. To merge those selected leads/opportunities, click :guilabel:`Merge`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:70 +msgid "The pop-up window disappears, and the detail card for the merged opportunity/lead appears." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:-1 +msgid "List of similar leads and opportunities selected for merge in the CRM app." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:77 +msgid "Merging is an irreversible action. Do **not** merge leads/opportunities unless absolutely certain they should be combined." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:81 +msgid "When leads/opportunities should not be merged" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:83 +msgid "There may be instances where a similar lead or opportunity is identified, but should *not* be merged. These circumstances vary, based on the processes of the sales team and organization. Some potential scenarios are listed below." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:88 +msgid "Lost leads" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:90 +msgid "If a lead/opportunity has been marked as :doc:`lost `, it can still be merged with an active lead or opportunity. The resulting lead/opportunity is marked active, and added to the pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:95 +msgid "Different contact within an organization" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:97 +msgid "Leads/opportunities from the same organization, but with different points of contact, may not have the same needs. In this case, it is beneficial to *not* merge these records, though assigning the same salesperson, or sales team, can prevent duplicated work and miscommunication." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:102 +msgid "Duplicates with more than one salesperson" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:104 +msgid "If more than one lead/opportunity exists in the database, there may be multiple salespeople assigned to them, who are actively working on them independently. While these leads/opportunities may need to be managed separately, it is recommended that any affected salespeople be tagged in an internal note for visibility." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:110 +msgid "Contact information is similar, but not identical" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:112 +msgid "Similar leads and opportunities are identified by comparing the email addresses and phone numbers of the associated contacts. However, if the email address is similar, but not identical, they may need to remain independent." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:117 +msgid "Three different leads were added to the pipeline, and assigned to different salespeople. They were identified as *Similar Leads*, due to the email addresses of the contacts." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:120 +msgid "Two of the leads appear to come from the same individual, `Robin`, and have identical email addresses. These leads should be merged." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:123 +msgid "The third lead has the same email domain, but the address is different, as is the contact name. While this lead is most likely from the same organization, it is from a different contact, and should **not** be merged." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:0 +msgid "List of similar leads with emphasis on the contact information in the CRM app." +msgstr "" + #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:3 msgid "Multiple sales teams" msgstr "" @@ -1309,7 +1428,7 @@ msgid "Assign leads with predictive lead scoring" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:5 -msgid "The Odoo *CRM* app can automatically assign leads/opportunities to sales teams and salespeople. A standard practice is to assign leads based on the probability of winning each lead. Companies can prioritize the leads that are more likely to result in successful deals by quickly assigning them to the appropriate salespeople." +msgid "The Odoo **CRM** app can automatically assign leads/opportunities to sales teams and salespeople. A standard practice is to assign leads based on the probability of winning each lead. Companies can prioritize the leads that are more likely to result in successful deals by quickly assigning them to the appropriate salespeople." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:10 @@ -1321,7 +1440,7 @@ msgid "Predictive lead scoring" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:16 -msgid "Predictive lead scoring is a machine-learning model that uses historical data from Odoo *CRM* to score open leads/opportunities." +msgid "Predictive lead scoring is a machine-learning model that uses historical data from Odoo **CRM** to score open leads/opportunities." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:19 @@ -1345,26 +1464,54 @@ msgid "\\begin{equation}\n" msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:33 -msgid "The probability of success of each opportunity is displayed on the opportunity form, and it updates automatically as the opportunity progresses through the CRM pipeline." +msgid "Breaking down the equation:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:35 +msgid ":math:`P(A|B)` = probability of a successful lead in this *case*" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:36 +msgid ":math:`P(A)` = overall probability of a lead being successful, regardless of the conditions" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:37 +msgid ":math:`P(B|A)` = probability of this being the *case*, given a lead is successful" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:38 +msgid ":math:`P(B)` = probability of this being the *case*" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:40 +msgid "The term *case* refers to the variables that can affect a lead being successful in Odoo. This can include variables, such as the assigned salesperson, the source of the lead, the language of the lead, and other historical and demographic data." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:44 +msgid "The variables considered in this calculation can be :ref:`configured ` to tailor the calculation to each business's needs." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:47 +msgid "The probability of success for each opportunity is displayed on the opportunity form, and updates automatically, as the opportunity progresses through the CRM pipeline." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:-1 msgid "The probability of success displayed on the opportunity form." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:40 -msgid "When an opportunity moves to the next stage, its probability of success automatically increases according to the predictive lead scoring algorithm." +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:54 +msgid "When an opportunity moves to the next stage, its probability of success automatically increases, according to the predictive lead scoring algorithm." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:46 -msgid "Predictive lead scoring is always active in Odoo *CRM*. However, the variables used to calculate the probability of success can be customized in the settings." +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:62 +msgid "Predictive lead scoring is always active in Odoo **CRM**. However, the variables used to calculate the probability of success can be customized in the settings." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:49 -msgid "To customize the variables used by predictive lead scoring, go to :menuselection:`CRM --> Configuration --> Settings`. Under :guilabel:`Predictive Lead Scoring`, click on the :guilabel:`Update Probabilities` button." +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:65 +msgid "To customize the variables used by predictive lead scoring, go to :menuselection:`CRM app --> Configuration --> Settings`. Under :guilabel:`Predictive Lead Scoring`, click the :guilabel:`Update Probabilities` button." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:53 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:69 msgid "Then, click on the drop-down menu to choose which variables the predictive lead scoring feature will take into account." msgstr "" @@ -1372,91 +1519,91 @@ msgstr "" msgid "The Update Probabilities window in the Predictive Lead Scoring settings." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:60 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:76 msgid "Any number of the following variables can be activated:" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:62 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:78 msgid ":guilabel:`State`: the geographical state from which the opportunity originates" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:63 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:79 msgid ":guilabel:`Country`: the geographical country from which the opportunity originates" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:64 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:80 msgid ":guilabel:`Phone Quality`: whether or not a phone number is listed for the opportunity" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:65 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:81 msgid ":guilabel:`Email Quality`: whether or not an email address is listed for the opportunity" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:66 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:82 msgid ":guilabel:`Source`: the source of an opportunity (e.g. search engine, social media)" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:67 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:83 msgid ":guilabel:`Language`: the spoken language specified on the opportunity" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:68 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:84 msgid ":guilabel:`Tags`: the tags placed on the opportunity" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:71 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:87 msgid "The variables `Stage` and `Team` are always in effect. `Stage` refers to the CRM pipeline stage that an opportunity is in. `Team` refers to the sales team that is assigned to an opportunity. Predictive lead scoring *always* takes into account these two variables, regardless of which optional variables are selected." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:76 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:92 msgid "Next, click on the date field next to the option :guilabel:`Consider leads created as of the:` to select the date from which predictive lead scoring will begin its calculations." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:79 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:95 msgid "Lastly, click :guilabel:`Confirm` to save changes." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:82 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:98 msgid "Change the probability manually" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:84 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:100 msgid "An opportunity's probability of success can be changed manually on the opportunity form. Click on the probability number to edit it." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:88 -msgid "Manually changing the probability removes the automatic probability updates for that opportunity. The probability will no longer update automatically as the opportunity moves through each stage of the pipeline." +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:104 +msgid "Manually changing the probability removes the automatic probability updates for that opportunity. The probability no longer updates automatically, as the opportunity moves through each stage of the pipeline." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:92 -msgid "To reactivate automatic probability, click on the gear icon next to the probability percentage." +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:108 +msgid "To reactivate automatic probability, click on the :icon:`fa-cog` :guilabel:`(gear) icon next to the :guilabel:`Probability` percentage." msgstr "" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:-1 msgid "The gear icon used to reactivate automatic probability on an opportunity form." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:99 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:116 msgid "Assign leads based on probability" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:101 -msgid "Odoo *CRM* can assign leads/opportunities to sales teams and salespeople based on specified rules. Create assignment rules based on the leads' probability of success to prioritize those that are more likely to result in deals." +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:118 +msgid "Odoo **CRM** can assign leads/opportunities to sales teams and salespeople, based on specified rules. Create assignment rules, based on the leads' probability of success, to prioritize those that are more likely to result in deals." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:106 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:123 msgid "Configure rule-based assignment" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:108 -msgid "To activate *rule-based assignment*, navigate to :menuselection:`CRM --> Configuration --> Settings`, and activate :guilabel:`Rule-Based Assignment`." +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:125 +msgid "To activate *Rule-Based Assignment*, navigate to :menuselection:`CRM app --> Configuration --> Settings`, and tick the :guilabel:`Rule-Based Assignment` checkbox. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:111 -msgid "The rule-based assignment feature can be set to run :guilabel:`Manually`, meaning an Odoo user must manually trigger the assignment, or :guilabel:`Repeatedly`, meaning Odoo will automatically trigger the assignment according to the chosen time period." +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:128 +msgid "The :guilabel:`Rule-Based Assignment`` feature can be set to run :guilabel:`Manually`, meaning an Odoo user **must** manually trigger the assignment, or :guilabel:`Repeatedly`, meaning Odoo will automatically trigger the assignment according to the chosen time period." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:115 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:132 msgid "To set up automatic lead assignment, select :guilabel:`Repeatedly` for the :guilabel:`Running` section. Then, customize how often Odoo will trigger the automatic assignment in the :guilabel:`Repeat every` section." msgstr "" @@ -1464,39 +1611,39 @@ msgstr "" msgid "The Rule-Based Assignment setting in CRM settings." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:123 -msgid "If rule-based assignment is set to run :guilabel:`Repeatedly`, the assignment can still be triggered manually using the circular arrow icon in the :guilabel:`Rule-Based Assignment` settings (or using the :guilabel:`Assign Leads` button on the sales team configuration page)." +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:140 +msgid "If :guilabel:`Rule-Based Assignment` is set to run :guilabel:`Repeatedly`, the assignment can still be triggered manually using the circular arrow icon in the :guilabel:`Rule-Based Assignment` settings (or using the :guilabel:`Assign Leads` button on the sales team configuration page)." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:128 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:145 msgid "Configure assignment rules" msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:130 -msgid "Next, configure the *assignment rules* for each sales team and/or salesperson. These rules determine which leads Odoo assigns to which people. To get started, navigate to :menuselection:`CRM --> Configuration --> Sales Teams`, and select a sales team." +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:147 +msgid "Next, configure the *assignment rules* for each sales team and/or salesperson. These rules determine which leads Odoo assigns to which people. To get started, navigate to :menuselection:`CRM app --> Configuration --> Sales Teams`, and select a sales team." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:134 -msgid "On the sales team configuration form, under :guilabel:`Assignment Rules`, click on :guilabel:`Edit Domain` to configure the rules that Odoo uses to determine lead assignment for this sales team. The rules can include anything that may be relevant for this company or team, and any number of rules can be added." +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:151 +msgid "On the sales team configuration form, under :guilabel:`Assignment Rules`, click :guilabel:`Edit Domain` to configure the rules that Odoo uses to determine lead assignment for this sales team. The rules can include anything that may be relevant for this company or team, and any number of rules can be added." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:139 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:156 msgid "Click :guilabel:`Add Filter` to start creating assignment rules. Click on the :guilabel:`+` sign on the right of the assignment rule to add another line. Click on the :guilabel:`x` symbol to remove the line." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:143 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:160 msgid "To create an assignment rule based on an opportunity's probability of success, click on the far left drop-down menu of an assignment rule line, and select :guilabel:`Probability`." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:146 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:163 msgid "From the middle drop-down menu, select the desired equation symbol—most likely the symbol for *greater than*, *less than*, *greater than or equal to*, or *less than or equal to*." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:149 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:166 msgid "In the far right space, enter the desired number value of the probability. Finally, click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:153 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:170 msgid "To configure an assignment rule such that a sales team receives leads that have a probability of success of 20% or greater, create a :guilabel:`Domain` line that reads: `Probability >= 20`." msgstr "" @@ -1504,18 +1651,178 @@ msgstr "" msgid "Sales team domain set to probability greater than or equal to twenty percent." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:160 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:177 msgid "Separate assignment rules can also be configured for individual team members. From the sales team configuration page, click on a team member in the :guilabel:`Members` tab, then edit the :guilabel:`Domain` section. Click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:164 -msgid "If automatic lead assignment is configured in the settings, both the sales team and individual team members have the option to :guilabel:`Skip auto assignment`. Check this box to omit a particular sales team or salesperson from being assigned leads automatically by Odoo's rule-based assignment feature. If :guilabel:`Skip auto assignment` is activated, the sales team or salesperson can still be assigned leads manually." +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:181 +msgid "If automatic lead assignment is configured in the settings, both the sales team and individual team members have the option to :guilabel:`Skip auto assignment`. Check this box to omit a particular sales team or salesperson from being assigned leads automatically by Odoo's Rule-Based Assignment feature. If :guilabel:`Skip auto assignment` is activated, the sales team or salesperson can still be assigned leads manually." msgstr "" -#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:170 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:187 msgid "To manually assign leads to this sales team, click on the :guilabel:`Assign Leads` button at the top of the sales team configuration page. This will assign any leads that are currently unassigned and match this team's specified domain." msgstr "" +#: ../../content/applications/sales/members.rst:3 +msgid "Members" +msgstr "" + +#: ../../content/applications/sales/members.rst:5 +msgid "The **Members** application is where all operations related to memberships can be configured and managed. The **Members** app integrates with the **Sales** and **Accounting** applications to sell and invoice memberships directly to customers." +msgstr "" + +#: ../../content/applications/sales/members.rst:10 +msgid "Membership products" +msgstr "" + +#: ../../content/applications/sales/members.rst:12 +msgid "To create a new membership product, navigate to :menuselection:`Members app --> Configuration --> Membership Products`, and click :guilabel:`New` to open a blank product form." +msgstr "" + +#: ../../content/applications/sales/members.rst:15 +msgid "On the new product form, enter a name for the product in the field under :guilabel:`Product Name`. Use the two blank fields to the right of :guilabel:`Membership Duration` to set a date from which the membership becomes active. Finally, use the :guilabel:`Membership Fee` field to set the price at which the product is sold to customers." +msgstr "" + +#: ../../content/applications/sales/members.rst:20 +msgid "The following optional fields can also be configured for each product:" +msgstr "" + +#: ../../content/applications/sales/members.rst:22 +msgid ":guilabel:`Internal Reference`: Set an internal reference number for the product." +msgstr "" + +#: ../../content/applications/sales/members.rst:23 +msgid ":guilabel:`Product Category`: Set a category for the product." +msgstr "" + +#: ../../content/applications/sales/members.rst:24 +msgid ":guilabel:`Company`: Set the company inventory for the product to appear in." +msgstr "" + +#: ../../content/applications/sales/members.rst:25 +msgid ":guilabel:`Active`: Hide a product without removing it from inventory." +msgstr "" + +#: ../../content/applications/sales/members.rst:26 +msgid ":guilabel:`Visible on current website`: Make the product visible to customers on the current website." +msgstr "" + +#: ../../content/applications/sales/members.rst:28 +msgid ":guilabel:`Description`: Set an internal product description." +msgstr "" + +#: ../../content/applications/sales/members.rst:29 +msgid ":guilabel:`Sales Description`: Set a product description that is visible on quotations." +msgstr "" + +#: ../../content/applications/sales/members.rst:30 +msgid ":guilabel:`Income Account`: Use a different value than the default from the product category." +msgstr "" + +#: ../../content/applications/sales/members.rst:31 +msgid ":guilabel:`Taxes`: Set the default tax used when selling this product." +msgstr "" + +#: ../../content/applications/sales/members.rst:34 +msgid "Membership products require a start and end date, as they are used to determine :ref:`membership status `. Membership products can be sold *before* their active start date." +msgstr "" + +#: ../../content/applications/sales/members.rst:-1 +msgid "A new membership product in the members app." +msgstr "" + +#: ../../content/applications/sales/members.rst:42 +msgid "Membership products can be added to a sales order, and invoiced as regular products or subscriptions." +msgstr "" + +#: ../../content/applications/sales/members.rst:46 +msgid "Activate a membership" +msgstr "" + +#: ../../content/applications/sales/members.rst:48 +msgid "To activate a membership from the **Contacts** application, navigate to the :menuselection:`Contacts app`, and click on a contact to open that specific contact form." +msgstr "" + +#: ../../content/applications/sales/members.rst:51 +msgid "From the contact form, open the :guilabel:`Membership` tab, and click :guilabel:`Buy Membership`." +msgstr "" + +#: ../../content/applications/sales/members.rst:55 +msgid "To successfully buy a membership, both the :guilabel:`Account Receivable` and :guilabel:`Account Payable` lines **must** be configured for that contact. These can be found in the contact form's :guilabel:`Accounting` tab, under the :guilabel:`Accounting entries` section." +msgstr "" + +#: ../../content/applications/sales/members.rst:59 +msgid "On the :guilabel:`Join Membership` pop-up window that appears, select a :guilabel:`Membership` from the drop-down menu. Then, configure a :guilabel:`Member Price`." +msgstr "" + +#: ../../content/applications/sales/members.rst:62 +msgid "Click :guilabel:`Invoice Membership` when both fields are filled in. Doing so reveals a :guilabel:`Membership Invoices` page, wherein invoices can be confirmed and completed." +msgstr "" + +#: ../../content/applications/sales/members.rst:65 +msgid "Alternatively, to offer a free membership, tick the :guilabel:`Free Member` checkbox, in the :guilabel:`Membership` tab of a contact form." +msgstr "" + +#: ../../content/applications/sales/members.rst:71 +msgid "Membership status" +msgstr "" + +#: ../../content/applications/sales/members.rst:73 +msgid "The :guilabel:`Current Membership Status` is listed on the :guilabel:`Membership` tab of each contact record:" +msgstr "" + +#: ../../content/applications/sales/members.rst:76 +msgid ":guilabel:`Non Member`: a partner who has **not** applied for membership." +msgstr "" + +#: ../../content/applications/sales/members.rst:77 +msgid ":guilabel:`Cancelled Member`: a member who has cancelled their membership." +msgstr "" + +#: ../../content/applications/sales/members.rst:78 +msgid ":guilabel:`Old Member`: a member whose membership end date has passed." +msgstr "" + +#: ../../content/applications/sales/members.rst:79 +msgid ":guilabel:`Waiting Member`: a member who has applied for membership, but whose invoice has not yet been created." +msgstr "" + +#: ../../content/applications/sales/members.rst:81 +msgid ":guilabel:`Invoiced Member`: a member whose invoice has been created, but has not been paid." +msgstr "" + +#: ../../content/applications/sales/members.rst:82 +msgid ":guilabel:`Paid Member`: a member who has paid the membership fee." +msgstr "" + +#: ../../content/applications/sales/members.rst:85 +msgid "Publish members directory" +msgstr "" + +#: ../../content/applications/sales/members.rst:87 +msgid "To publish a list of active members on the website, the **Online Members Directory** module must first be :ref:`installed `. After installing the module, add the `/members` page to the website's menu by :doc:`editing the website menu <../websites/website/pages/menus>`." +msgstr "" + +#: ../../content/applications/sales/members.rst:-1 +msgid "The Online Members directory module in Odoo." +msgstr "" + +#: ../../content/applications/sales/members.rst:96 +msgid "Publish individual members" +msgstr "" + +#: ../../content/applications/sales/members.rst:98 +msgid "Navigate to :menuselection:`CRM app --> Sales --> Customers`, and click the Kanban card for a member. From the customer form that appears, click the :guilabel:`Go to Website` smart button at the top of the page to open the member's webpage." +msgstr "" + +#: ../../content/applications/sales/members.rst:102 +msgid "Click the :icon:`fa-pencil` :guilabel:`Edit` button to reveal a sidebar of editing tools. After making any necessary changes to the page, click :guilabel:`Save`. At the top of the page, slide the :guilabel:`Unpublished` toggle to the active, :guilabel:`Published` position." +msgstr "" + +#: ../../content/applications/sales/members.rst:106 +msgid "Repeat these steps for all desired members." +msgstr "" + #: ../../content/applications/sales/point_of_sale.rst:6 msgid "Point of Sale" msgstr "" @@ -4300,7 +4607,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 diff --git a/locale/sources/services.pot b/locale/sources/services.pot index 2621239d9..58027338f 100644 --- a/locale/sources/services.pot +++ b/locale/sources/services.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 10:38+0000\n" +"POT-Creation-Date: 2024-08-21 07:41+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -875,7 +875,7 @@ msgid "When the necessary information has been entered, click :guilabel:`Create msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:248 -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/services/helpdesk/overview.rst:5 diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index 2c954598f..7e0fde20a 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-23 10:38+0000\n" +"POT-Creation-Date: 2024-08-21 07:41+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -607,72 +607,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/managing_products/products.rst:203 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 "" @@ -953,14 +955,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 "" @@ -1457,7 +1451,7 @@ msgid "Price per unit" msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:56 -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/managing_products/price_management.rst:-1 @@ -1477,7 +1471,7 @@ msgid "Pay attention that having the price per unit may be **mandatory** in some msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:78 -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/managing_products/price_management.rst:83 @@ -2012,6 +2006,7 @@ msgid "Add a description to your course." msgstr "" #: ../../content/applications/websites/elearning.rst:67 +#: ../../content/applications/websites/livechat.rst:92 msgid "Options tab" msgstr "" @@ -3002,7 +2997,7 @@ msgid "Live Chat" msgstr "" #: ../../content/applications/websites/livechat.rst:8 -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:14 @@ -3010,254 +3005,274 @@ msgid "Enable Live Chat" msgstr "" #: ../../content/applications/websites/livechat.rst:16 -msgid "In order to enable *Live Chat*, the *Live Chat* application needs to be installed. This can be done in one of two ways." +msgid "The **Live Chat** application is installed in multiple ways:" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:18 +msgid "Go to :menuselection:`Apps application`, search `Live Chat`, and click :guilabel:`Install`." msgstr "" #: ../../content/applications/websites/livechat.rst:19 -msgid "Go to :menuselection:`Apps --> Live Chat` and click :guilabel:`Install`." +msgid "Go to the :menuselection:`Helpdesk app --> Configuration --> Teams` list view, select a team, and on the team's settings page, tick the :guilabel:`Live Chat` checkbox, under the :guilabel:`Channels` section." msgstr "" -#: ../../content/applications/websites/livechat.rst:20 -msgid "In the :menuselection:`Website` application, go to :menuselection:`Configuration --> Settings`, scroll to the :guilabel:`Email & Marketing` section, check the box next to :guilabel:`Livechat`, and click :guilabel:`Save`." +#: ../../content/applications/websites/livechat.rst:22 +msgid "In the :menuselection:`Website` app, go to :menuselection:`Configuration --> Settings`, scroll to the :guilabel:`How to configure the Twitter API access` section, tick the :guilabel:`Livechat` checkbox, and click :guilabel:`Save`." msgstr "" #: ../../content/applications/websites/livechat.rst:-1 msgid "View of the settings page and the live chat feature for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:28 -msgid "After the :guilabel:`Live Chat` application is installed, a live chat :guilabel:`Channel` will be created by default and automatically selected in the drop-down." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:32 -msgid "Create a new live chat channel" +#: ../../content/applications/websites/livechat.rst:31 +msgid "After the **Live Chat** application is installed, a live chat *Channel* is created by default." msgstr "" #: ../../content/applications/websites/livechat.rst:34 -msgid "To create a new live chat *Channel*, go to :menuselection:`Main Odoo Dashboard --> Live Chat app --> New`. This will open a blank channel detail form. Enter the name of the new channel in the :guilabel:`Channel Name` field." +msgid "Create a new live chat channel" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:36 +msgid "To create a new live chat *Channel*, go to :menuselection:`Live Chat app --> New`. This opens a blank channel detail form. Enter the name of the new channel in the :guilabel:`Channel Name` field." msgstr "" #: ../../content/applications/websites/livechat.rst:-1 msgid "View of a live chat channel form for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:42 -msgid "To configure the remaining tabs on the channel detail form (:guilabel:`Operators`, :guilabel:`Options`, :guilabel:`Channel Rules`, and :guilabel:`Widgets`), follow the steps below." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:46 -msgid "Operators" +#: ../../content/applications/websites/livechat.rst:43 +msgid "To configure the remaining tabs on the channel detail form (:ref:`Operators `, :ref:`Options `, :ref:`Channel Rules `, and :ref:`Widget `), follow the steps below." msgstr "" #: ../../content/applications/websites/livechat.rst:48 -msgid "*Operators* are the users who will respond to live chat requests from customers. When a user is added as an operator in a live chat channel, they will be able to receive chats from website visitors wherever they are in the database. Chat windows will open in the bottom right corner of the screen." +msgid "The channel detail form for any channel can be accessed by navigating back to the :guilabel:`Website Live Chat Channels` dashboard, via the breadcrumbs. Click the Kanban card for the appropriate live chat channel to open the channel detail form." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:55 +msgid "Operators tab" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:57 +msgid "*Operators* are the users who act as agents and respond to live chat requests from customers. When a user is added as an operator in a live chat channel, they can receive chats from website visitors wherever they are in the database. Chat windows open in the bottom-right corner of the screen." msgstr "" #: ../../content/applications/websites/livechat.rst:-1 msgid "View of a live chat pop up window in an Odoo database." msgstr "" -#: ../../content/applications/websites/livechat.rst:57 -msgid "The user who originally created the live chat channel will be added as an operator by default." +#: ../../content/applications/websites/livechat.rst:65 +msgid "On the channel detail form, click the :guilabel:`Operators` tab. The user who originally created the live chat channel has been added as an operator by default." msgstr "" -#: ../../content/applications/websites/livechat.rst:59 -msgid "To add additional users, navigate back to the :guilabel:`Website Live Chat Channels` dashboard via the breadcrumbs and click on the appropriate :guilabel:`Live Chat Channel`. Then, on the channel detail form, under the :guilabel:`Operators` tab, click :guilabel:`ADD` to reveal an :guilabel:`Add: Operators` pop-up window." +#: ../../content/applications/websites/livechat.rst:69 +msgid "Current operators can be edited, or removed, by clicking on their respective boxes in the :guilabel:`Operators` tab, which reveals a separate :guilabel:`Open: Operators` pop-up window. In that pop-up window, adjust any information, as needed. Then, click :guilabel:`Save`, or click :guilabel:`Remove` to remove that operator from the channel." msgstr "" -#: ../../content/applications/websites/livechat.rst:64 -msgid "In the pop-up window, search for the desired user(s). Then, click the checkbox next to the user(s) to be added, and click :guilabel:`SELECT`." +#: ../../content/applications/websites/livechat.rst:74 +msgid "Click :guilabel:`Add` to reveal an :guilabel:`Add: Operators` pop-up window." msgstr "" -#: ../../content/applications/websites/livechat.rst:67 -msgid "New operators can be created and added to the list directly from this pop-up, as well, by clicking :guilabel:`New`, and filling out the :guilabel:`Create Operators` pop-up form. When the form is complete, click :guilabel:`SAVE & CLOSE` (or :guilabel:`SAVE & NEW` for multiple record creations)." +#: ../../content/applications/websites/livechat.rst:76 +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:72 -msgid "Current operators can be edited (or removed) by clicking on their respective boxes in the :guilabel:`Operators` tab, which reveals a separate :guilabel:`Open: Operators` pop-up. In that pop-up, adjust any information as needed, and click :guilabel:`Save`, or click :guilabel:`Remove` to remove that operator from the channel." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:78 -msgid "Options" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:80 -msgid "The :guilabel:`Options` tab on the live chat channel details form contains the visual and text settings for the live chat window." +#: ../../content/applications/websites/livechat.rst:79 +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:84 -msgid "Livechat button" +msgid "Creating a new user can impact the status of an Odoo subscription, as the total number of users in a database counts towards the billing rate. Proceed with caution before creating a new user. If a user already exists, adding them as an operator does **not** alter the subscription or billing rate for a database." msgstr "" -#: ../../content/applications/websites/livechat.rst:86 -msgid "The *Livechat Button* is the icon that appears in the bottom corner of the website." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:-1 -msgid "View of an Odoo website emphasizing the livechat button." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:92 -msgid "Change the text in the :guilabel:`Text of the Button` field to update the greeting displayed in the text bubble when the live chat button appears on the website." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:95 -msgid "Change the :guilabel:`Livechat Button Color` by clicking a color bubble to open the color selection window. Click the :guilabel:`🔄 (refresh)` icon to the right of the color bubbles to reset the colors to the default selection." +#: ../../content/applications/websites/livechat.rst:94 +msgid "The :guilabel:`Options` tab on the live chat channel detail form contains the visual and text settings for the live chat window." msgstr "" #: ../../content/applications/websites/livechat.rst:100 -msgid "Color selection, for the button or header, can be made manually using a slider or through RGB, HSL, or HEX color code entries from the pop-up color selection window that appears when either of the color bubbles are clicked. Different options will be available, depending on your operating system." +msgid "Livechat Button section" msgstr "" -#: ../../content/applications/websites/livechat.rst:106 -msgid "Livechat window" +#: ../../content/applications/websites/livechat.rst:102 +msgid "The *Livechat Button* is the icon that appears in the bottom-right corner of the website." msgstr "" #: ../../content/applications/websites/livechat.rst:108 +msgid "View of an Odoo website emphasizing the livechat button." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:108 +msgid "The Live Chat button in the bottom-right corner of an Odoo website." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:110 +msgid "Change the text in the :guilabel:`Text of the Button` field to update the greeting displayed in the text bubble when the live chat button appears on the website." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:113 +msgid "The :guilabel:`Livechat Button Color` alters the color of the live chat button as it appears on the website. To change the color, click on a color bubble to open the color selection window, then click and drag the circle along the color gradient. Click out of the selection window once complete. Click the :icon:`fa-refresh` :guilabel:`(refresh)` icon to the right of the color bubbles to reset the colors to the default selection." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:120 +msgid "Color selection, for the button or header, can be made manually using a slider or through RGB, HSL, or HEX color code entries from the pop-up color selection window that appears when either of the color bubbles are clicked. Different options are available, depending on the operating system." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:126 +msgid "Livechat Window section" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:128 msgid "The *Livechat Window* is the space where the live chat conversation with website visitors takes place." msgstr "" -#: ../../content/applications/websites/livechat.rst:111 -msgid "Edit the :guilabel:`Welcome Message` to change the message a visitor sees when they open a new chat session. This message will appear as though it is sent by a live chat operator, and acts as both a greeting and an invitation to continue the conversation." +#: ../../content/applications/websites/livechat.rst:131 +msgid "Edit the :guilabel:`Welcome Message` to change the message a visitor sees when they open a new chat session. This message appears as though it is sent by a live chat operator, and acts as both a greeting and an invitation to continue the conversation." msgstr "" -#: ../../content/applications/websites/livechat.rst:115 -msgid "Edit the :guilabel:`Chat Input Placeholder` to alter the text that appears in the box where visitors will type their replies." +#: ../../content/applications/websites/livechat.rst:135 +msgid "Edit the :guilabel:`Chat Input Placeholder` to alter the text that appears in the box where visitors type their replies. This message prompts the visitor to initiate the chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:118 -msgid "The *Channel Header* is the colored bar at the top of the chat window. The :guilabel:`Channel Header Color` can be changed following the same steps as the *Livechat Button Color* above." +#: ../../content/applications/websites/livechat.rst:138 +msgid "The *Channel Header* is the colored bar at the top of the chat window. The :guilabel:`Channel Header Color` can be changed following the same steps as the :ref:`Livechat button `." msgstr "" -#: ../../content/applications/websites/livechat.rst:124 +#: ../../content/applications/websites/livechat.rst:145 msgid "The Livechat Window with a purple header. The chat input placeholder reads \"Ask Something...\"" msgstr "" -#: ../../content/applications/websites/livechat.rst:127 -msgid "Channel rules" +#: ../../content/applications/websites/livechat.rst:150 +msgid "Channel Rules tab" msgstr "" -#: ../../content/applications/websites/livechat.rst:129 -msgid "The :guilabel:`Channel Rules` tab on the live chat channel details form determines when the *Live Chat Window* opens on the website, by configuring when a :guilabel:`URL Regex` action is triggered (e.g., a page visit)." +#: ../../content/applications/websites/livechat.rst:152 +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:133 -msgid "To create a new channel rule, click :guilabel:`Add a line`. This opens the :guilabel:`Open: Rules` pop-up." +#: ../../content/applications/websites/livechat.rst:155 +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:141 +#: ../../content/applications/websites/livechat.rst:163 msgid "Create new rules" msgstr "" -#: ../../content/applications/websites/livechat.rst:143 -msgid "Fill out the fields on the :guilabel:`Open: Rules` pop-up as instructed below, then click :guilabel:`Save`." +#: ../../content/applications/websites/livechat.rst:165 +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:148 +#: ../../content/applications/websites/livechat.rst:170 msgid "Live Chat Button" msgstr "" -#: ../../content/applications/websites/livechat.rst:150 -msgid "The *Livechat Button* is the icon that appears in the bottom corner of the website. Select from one of the following display options:" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:153 -msgid ":guilabel:`Show` displays the chat button on the page(s)." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:154 -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:156 -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)." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:159 -msgid ":guilabel:`Hide` hides the chat button on the page(s)." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:161 -msgid "Chatbot" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:163 -msgid "If a *Chatbot* will be included on this channel, select it from the dropdown. If the chatbot will only be active when no operators are active, check the box labeled :guilabel:`Enabled only if no operator`." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:167 -msgid "URL Regex" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:169 -msgid "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:172 -msgid "Open automatically timer" +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:174 -msgid "This field designates the amount of time (in seconds) a page will be open before the chat window will open. If the :guilabel:`Livechat Button` for this rule is not set to :guilabel:`Open automatically`, this field will be ignored." +#: ../../content/applications/websites/livechat.rst:175 +msgid ":guilabel:`Show`: displays the chat button on the page." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:176 +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:178 -msgid "Country" +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:180 -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 will be available to all site visitors, regardless of location." +#: ../../content/applications/websites/livechat.rst:181 +msgid ":guilabel:`Hide`: hides the chat button on the page." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:183 +msgid "Chatbot" msgstr "" #: ../../content/applications/websites/livechat.rst:185 -msgid "In order to track the geographical location of visitors, :guilabel:`GeoIP` must be installed on the database. While this feature is installed by default on *Odoo Online*, *On-Premise* databases will require additional :doc:`setup steps `." +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, tick the checkbox labeled, :guilabel:`Enabled only if no operator`." msgstr "" -#: ../../content/applications/websites/livechat.rst:190 -msgid "Widget" +#: ../../content/applications/websites/livechat.rst:189 +msgid "URL Regex" msgstr "" -#: ../../content/applications/websites/livechat.rst:192 -msgid "The :guilabel:`Widget` tab on the live chat channel details form provides the shortcode for an embeddable website widget. This code can be added to a website to provide access to a live chat window." +#: ../../content/applications/websites/livechat.rst:191 +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:196 -msgid "The live chat widget can be added to websites created through Odoo by navigating to the :menuselection:`Website --> Configuration --> Settings`. Then scroll to the :guilabel:`Livechat` section, and select the channel to add to the site. Click :guilabel:`Save` to apply." +#: ../../content/applications/websites/livechat.rst:195 +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:200 -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." +#: ../../content/applications/websites/livechat.rst:198 +msgid "To apply the rule to *all* pages on the database, enter `/` in the :guilabel:`URL Regex` field." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:201 +msgid "Open automatically timer" msgstr "" #: ../../content/applications/websites/livechat.rst:203 -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, and once they click the link, it will open a new chat." +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:207 +msgid "Country" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:209 +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:214 +msgid "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:221 +msgid "Widget tab" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:223 +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:227 +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:`How to configure the Twitter API access` 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:232 +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:235 +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 "" #: ../../content/applications/websites/livechat.rst:-1 msgid "View of the widget tab for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:212 +#: ../../content/applications/websites/livechat.rst:244 msgid "Participate in a conversation" msgstr "" -#: ../../content/applications/websites/livechat.rst:214 +#: ../../content/applications/websites/livechat.rst:246 msgid "As explained above, *operators* are the users who will respond to live chat requests from customers. The information below outlines the necessary steps for operators participating in live chat conversations on an Odoo database." msgstr "" -#: ../../content/applications/websites/livechat.rst:219 +#: ../../content/applications/websites/livechat.rst:251 msgid "Set an online chat name" msgstr "" -#: ../../content/applications/websites/livechat.rst:221 +#: ../../content/applications/websites/livechat.rst:253 msgid "Before participating in a live chat, operators should update their *Online Chat Name*. This is the name that will be displayed to site visitors in the live chat conversation." msgstr "" -#: ../../content/applications/websites/livechat.rst:224 +#: ../../content/applications/websites/livechat.rst:256 msgid "To update the :guilabel:`Online Chat Name`, click on the user name in the upper-right corner of any page in the database. Select :guilabel:`My Profile` to open the Profile page. On the right side of the :guilabel:`Preferences` tab, locate the :guilabel:`Online Chat Name` field and enter the preferred name." msgstr "" @@ -3265,11 +3280,11 @@ msgstr "" msgid "View of the My Profile option in Odoo." msgstr "" -#: ../../content/applications/websites/livechat.rst:233 +#: ../../content/applications/websites/livechat.rst:265 msgid "If a users :guilabel:`Online Chat Name` is not set, the name displayed will default to the :guilabel:`User Name`." msgstr "" -#: ../../content/applications/websites/livechat.rst:237 +#: ../../content/applications/websites/livechat.rst:269 msgid "A user has their full name as their :guilabel:`User Name`, but they do not want to include their last name in a live chat conversation. They would then set their :guilabel:`Online Chat Name` to include only their first name." msgstr "" @@ -3277,43 +3292,43 @@ msgstr "" msgid "View of user profile in Odoo, emphasizing the Online Chat name field." msgstr "" -#: ../../content/applications/websites/livechat.rst:246 +#: ../../content/applications/websites/livechat.rst:278 msgid "Join or leave a channel" msgstr "" -#: ../../content/applications/websites/livechat.rst:248 -msgid "To join a live chat channel, go to the :menuselection:`Live Chat` app and click the :guilabel:`JOIN` button on the kanban card for the appropriate channel." +#: ../../content/applications/websites/livechat.rst:280 +msgid "To join a live chat channel, go to the :menuselection:`Live Chat` app, and click the :guilabel:`JOIN` button on the Kanban card for the appropriate channel." msgstr "" -#: ../../content/applications/websites/livechat.rst:251 -msgid "Any channel where the user is currently active will show a :guilabel:`LEAVE` button. Click this button to disconnect from the channel." +#: ../../content/applications/websites/livechat.rst:283 +msgid "Any channel where the user is currently active shows a :guilabel:`LEAVE` button. Click this button to disconnect from the channel." msgstr "" #: ../../content/applications/websites/livechat.rst:-1 msgid "View of a channel form and the option to join a channel for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:259 +#: ../../content/applications/websites/livechat.rst:291 msgid "*Operators* that do not show any activity in Odoo for more than thirty minutes will be considered disconnected, and subsequently removed from the channel." msgstr "" -#: ../../content/applications/websites/livechat.rst:263 +#: ../../content/applications/websites/livechat.rst:295 msgid "Manage live chat requests" msgstr "" -#: ../../content/applications/websites/livechat.rst:265 +#: ../../content/applications/websites/livechat.rst:297 msgid "When an operator is active in a channel, chat windows will open in the bottom right corner of the screen, no matter where they are in the database. They can participate in conversations without leaving their current location." msgstr "" -#: ../../content/applications/websites/livechat.rst:270 -msgid "Conversations can also be accessed by clicking the :guilabel:`Conversations` icon in the menu bar." +#: ../../content/applications/websites/livechat.rst:302 +msgid "Conversations can also be accessed by clicking the :icon:`fa-comments` :guilabel:`(messages)` icon in the menu bar." msgstr "" #: ../../content/applications/websites/livechat.rst:0 msgid "View of the menu bar in Odoo emphasizing the conversations icon." msgstr "" -#: ../../content/applications/websites/livechat.rst:277 +#: ../../content/applications/websites/livechat.rst:309 msgid "Live chat conversations can also be viewed by navigating to :menuselection:`Dashboard --> Discuss`. New conversations will appear in bold under the :guilabel:`LIVECHAT` heading along the left panel." msgstr "" @@ -3321,15 +3336,15 @@ msgstr "" msgid "View of the discuss application with a message sent through live chat in Odoo." msgstr "" -#: ../../content/applications/websites/livechat.rst:284 +#: ../../content/applications/websites/livechat.rst:316 msgid "Click on a conversation in the left panel to select it. This will open the conversation. From this view, an operator can participate in the chat the same as they would in the normal chat window." msgstr "" -#: ../../content/applications/websites/livechat.rst:288 +#: ../../content/applications/websites/livechat.rst:320 msgid ":doc:`Get Started with Discuss `" msgstr "" -#: ../../content/applications/websites/livechat.rst:289 +#: ../../content/applications/websites/livechat.rst:321 msgid ":doc:`/applications/websites/livechat/responses`" msgstr "" @@ -3783,7 +3798,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, pre-configured 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 @@ -3795,7 +3810,7 @@ msgid "Execute a command" msgstr "" #: ../../content/applications/websites/livechat/responses.rst:17 -msgid "Live chat *commands* are keywords that trigger pre-configured actions. When a live chat *operator* is participating in a conversation with a customer or website visitor, they can execute a command by typing `/`, followed by the command." +msgid "Live chat *commands* are keywords that trigger preconfigured actions. When a live chat *operator* is participating in a conversation with a customer or website visitor, they can execute a command by typing `/`, followed by the command." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:21 @@ -3819,54 +3834,46 @@ msgid "Type `@username` to mention a user in the conversation. A notification wi msgstr "" #: ../../content/applications/websites/livechat/responses.rst:39 -msgid "Type `#channel` to mention a *Discuss* channel." -msgstr "" - -#: ../../content/applications/websites/livechat/responses.rst:40 msgid "Type `/command` to execute a command." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:41 +#: ../../content/applications/websites/livechat/responses.rst:40 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:48 +#: ../../content/applications/websites/livechat/responses.rst:43 msgid ":doc:`/applications/productivity/discuss`" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:49 +#: ../../content/applications/websites/livechat/responses.rst:44 msgid ":doc:`/applications/productivity/discuss/team_communication`" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:52 +#: ../../content/applications/websites/livechat/responses.rst:47 msgid "Helpdesk & Helpdesk search" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:54 +#: ../../content/applications/websites/livechat/responses.rst:49 msgid "The `/helpdesk` and `/helpdesk_search` commands allow operators to both create helpdesk tickets directly from a conversation, and search through existing tickets by keyword or ticket number." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:58 -msgid "The `/helpdesk` and `/helpdesk_search` commands can only be used if the *Helpdesk* app has been installed, and *Live Chat* has been activated on a *Helpdesk* team. To activate :guilabel:`Live Chat`, go to :menuselection:`Helpdesk application --> Configuration --> 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:53 +msgid "The `/helpdesk` and `/helpdesk_search` commands can only be used if the **Helpdesk** app has been installed, and *Live Chat* has been activated on a *Helpdesk* team. To activate :guilabel:`Live Chat`, go to :menuselection:`Helpdesk application --> Configuration --> 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:64 +#: ../../content/applications/websites/livechat/responses.rst:59 msgid "Create a ticket from a live chat" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:66 +#: ../../content/applications/websites/livechat/responses.rst:61 msgid "If an operator types `/helpdesk` in the chat window, the conversation is used to create a *Helpdesk* ticket." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:70 +#: ../../content/applications/websites/livechat/responses.rst:65 msgid "In version 16.3, the command to create a new ticket is `/ticket`. This only applies to databases running version 16.3." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:73 +#: ../../content/applications/websites/livechat/responses.rst:68 msgid "After entering the `/helpdesk` command, type a title for the ticket into the chat window, then press `Enter`." msgstr "" @@ -3875,135 +3882,135 @@ msgstr "" msgid "View of the results from a helpdesk search in a Live Chat conversation." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:80 +#: ../../content/applications/websites/livechat/responses.rst:75 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:84 +#: ../../content/applications/websites/livechat/responses.rst:79 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:87 -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:82 +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:92 +#: ../../content/applications/websites/livechat/responses.rst:87 msgid "Search for a ticket from a live chat" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:94 +#: ../../content/applications/websites/livechat/responses.rst:89 msgid "If an operator types `/helpdesk_search` in the chat window, they can search through *Helpdesk* tickets by ticket number or keyword." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:98 +#: ../../content/applications/websites/livechat/responses.rst:93 msgid "In version 16.3, the command to search through *Helpdesk* tickets is `/search_tickets`. This only applies to databases running version 16.3." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:101 +#: ../../content/applications/websites/livechat/responses.rst:96 msgid "After entering the `/helpdesk_search` command, type a keyword or ticket number, then press `Enter`. If one or more related tickets are found, a list of links will be 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 "If an operator types `/history` in the chat window, it will generate a list of the most recent pages the visitor has viewed on the website (up to 15)." +#: ../../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:`/applications/services/helpdesk/overview/getting_started`" 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 *shortcut* stands in for a longer response. An operator will enter the shortcut, and it will automatically be replaced by the expanded *substitution* response in the conversation." +#: ../../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:168 +#: ../../content/applications/websites/livechat/responses.rst:163 msgid "Create canned responses" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:170 +#: ../../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:173 +#: ../../content/applications/websites/livechat/responses.rst:168 msgid "From here, type the shortcut command into the :guilabel:`Shortcut` field." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:175 +#: ../../content/applications/websites/livechat/responses.rst:170 msgid "Then, click into the :guilabel:`Substitution` field, and enter the custom message that will be sent to visitors in place of the shortcut. Click :guilabel:`Save`." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:179 -msgid "Try to connect the shortcut to the topic of the substitution. The easier it is for the operators to remember, the easier it will be to use the canned responses in conversations." +#: ../../content/applications/websites/livechat/responses.rst:174 +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:183 +#: ../../content/applications/websites/livechat/responses.rst:178 msgid "Use canned responses in a live chat conversation" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:185 +#: ../../content/applications/websites/livechat/responses.rst:180 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:189 +#: ../../content/applications/websites/livechat/responses.rst:184 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 "" @@ -4011,7 +4018,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:198 +#: ../../content/applications/websites/livechat/responses.rst:193 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 "" @@ -4642,30 +4649,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 "" @@ -6051,34 +6138,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 "" @@ -6086,7 +6177,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 ""