diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index d6e20eceb..a11d82c07 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: 2023-06-15 11:45+0000\n" +"POT-Creation-Date: 2023-07-03 09:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -192,7 +192,7 @@ msgstr "" #: ../../content/administration/install/deploy.rst:58 #: ../../content/administration/install/deploy.rst:153 #: ../../content/administration/install/deploy.rst:276 -msgid "in ``/etc/odoo.conf`` set:" +msgid "in :ref:`the configuration file ` set:" msgstr "" #: ../../content/administration/install/deploy.rst:53 @@ -409,7 +409,7 @@ msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo" msgstr "" #: ../../content/administration/install/deploy.rst:241 -msgid "in ``/etc/odoo.conf``:" +msgid "in :ref:`the configuration file `:" msgstr "" #: ../../content/administration/install/deploy.rst:257 @@ -2158,7 +2158,7 @@ msgid ":doc:`/applications/general/email_communication/email_servers`" msgstr "" #: ../../content/administration/maintain/enterprise.rst:6 -msgid "Upgrade Community to Enterprise" +msgid "Switch from Community to Enterprise" msgstr "" #: ../../content/administration/maintain/enterprise.rst:8 @@ -6670,44 +6670,68 @@ msgstr "" msgid "If you are using the Website or Studio app, we recommend you always do a test upgrade before upgrading your production instance." msgstr "" -#: ../../content/administration/upgrade/odoo_online.rst:6 -msgid "Requesting a test upgrade" +#: ../../content/administration/upgrade/odoo_online.rst:5 +msgid "Odoo databases can be manually upgraded directly from the main Odoo website. To upgrade an Odoo database, navigate to the `database manager `_ page and sign in." msgstr "" #: ../../content/administration/upgrade/odoo_online.rst:8 -msgid "Go to your `database manager `_" +msgid "The database manager page displays all of the Odoo databases associated with the user's account. Any databases that are not already on the most recent version of Odoo display an **arrow in a circle** icon next to the database name, indicating that the database can be upgraded." msgstr "" -#: ../../content/administration/upgrade/odoo_online.rst:9 -msgid "Click on your profile icon and select *My Databases*." +#: ../../content/administration/upgrade/odoo_online.rst:-1 +msgid "The database manager page with an upgrade button next to the name of a database." msgstr "" -#: ../../content/administration/upgrade/odoo_online.rst:0 -msgid "Selecting My Databases under my profile" -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:14 -msgid "Click on the up arrow button next to your main database name to proceed to the test upgrade." -msgstr "" - -#: ../../content/administration/upgrade/odoo_online.rst:0 -msgid "Selecting the action settings icon" +#: ../../content/administration/upgrade/odoo_online.rst:17 +msgid "Test database" msgstr "" #: ../../content/administration/upgrade/odoo_online.rst:19 -msgid "In the pop-up message that appears, select the target version and then :guilabel:`Test` as purpose." +msgid "Click on the **arrow in a circle** icon to start the upgrade process. On the :guilabel:`Upgrade your database` pop-up, select the version of Odoo that the platform will be upgraded to. In the :guilabel:`Email to notify` field, enter an email address that will receive email notifications about the database upgrade." msgstr "" -#: ../../content/administration/upgrade/odoo_online.rst:23 -msgid "The :guilabel:`Production` purpose doesn't appear if you didn't test your upgraded database at least once." +#: ../../content/administration/upgrade/odoo_online.rst:24 +msgid "There is also a :guilabel:`Purpose` section on the pop-up that is used to specify the reason for the upgrade. However, at this stage of the process, the only selectable option is :guilabel:`Test`, as Odoo requires users to create a test copy of the upgraded database before converting the actual database." msgstr "" -#: ../../content/administration/upgrade/odoo_online.rst:26 -msgid "This triggers the automated upgrade process. A confirmation email is then sent to you with the the link to the upgraded database or to provide information if the upgrade failed." +#: ../../content/administration/upgrade/odoo_online.rst:-1 +msgid "The \"Upgrade your database\" pop-up." msgstr "" -#: ../../content/administration/upgrade/odoo_online.rst:30 -msgid "You can also see and access your test database from your *My Databases* page." +#: ../../content/administration/upgrade/odoo_online.rst:33 +msgid "After filling out the form, click the :guilabel:`Upgrade` button. The pop-up disappears and the database being upgraded shows a red :guilabel:`Upgrade in progress` tag next to its name. An email confirming that the upgrade is in progress is also sent to the email address specified on the pop-up." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:-1 +msgid "The \"Upgrade in progress\" tag next to the database name." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:42 +msgid "Once the upgrade is complete, a new test database appears on the `database manager `_ page. To access the test database, click the drop-down arrow (:guilabel:`⯆`) to the left of the main database's name. Doing so makes the test version appear below it. Finally, click the green :guilabel:`Connect` button on the right side of the test version's row to go to the database." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:-1 +msgid "A test database on the database manager page." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:52 +msgid "Except for being on the newer version of Odoo, the test database is an exact copy of the one being upgraded. It is important to do extensive testing in this database to ensure that the upgrade has not altered or corrupted any data, and that all workflows still proceed as expected." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:57 +msgid "Production database" +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:59 +msgid "After confirming the integrity of the new version, return to the `database manager `_ page. Once again, click on the **arrow in a circle** icon next to the database being upgraded. The :guilabel:`Upgrade your database` pop-up appears as before, except that there is now a :guilabel:`Production` option under the :guilabel:`Purpose` section." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:64 +msgid "Select the :guilabel:`Production` option and then click :guilabel:`Upgrade` to begin the upgrade process. As before, a notification email is sent to the email address provided and a red :guilabel:`Upgrade in progress` tag appears next to the name of the database." +msgstr "" + +#: ../../content/administration/upgrade/odoo_online.rst:68 +msgid "After the upgrade is finished, the :guilabel:`Upgrade in progress` tag disappears and the database is upgraded to the version specified." msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:10 diff --git a/locale/sources/contributing.pot b/locale/sources/contributing.pot index 419d32d09..05d896e89 100644 --- a/locale/sources/contributing.pot +++ b/locale/sources/contributing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-05-30 12:32+0000\n" +"POT-Creation-Date: 2023-07-03 09:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index ee177f136..e9d77ad54 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: 2023-06-15 11:45+0000\n" +"POT-Creation-Date: 2023-07-03 09:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -396,16 +396,16 @@ msgstr "" #: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:69 #: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:23 #: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:14 +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:13 #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:61 #: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:21 #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:46 #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:12 +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:15 #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:15 #: ../../content/applications/finance/accounting/get_started/vat_units.rst:22 #: ../../content/applications/finance/accounting/payments/batch.rst:11 #: ../../content/applications/finance/accounting/payments/batch_sdd.rst:20 -#: ../../content/applications/finance/accounting/payments/checks.rst:39 -#: ../../content/applications/finance/accounting/payments/checks.rst:102 #: ../../content/applications/finance/accounting/payments/follow_up.rst:14 #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:9 #: ../../content/applications/finance/accounting/payments/online.rst:21 @@ -425,7 +425,8 @@ msgstr "" #: ../../content/applications/finance/documents.rst:17 #: ../../content/applications/finance/fiscal_localizations.rst:21 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:14 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:104 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:8 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:413 #: ../../content/applications/finance/fiscal_localizations/chile.rst:29 #: ../../content/applications/finance/fiscal_localizations/chile.rst:290 #: ../../content/applications/finance/fiscal_localizations/chile.rst:332 @@ -1878,6 +1879,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:111 #: ../../content/applications/finance/accounting/taxes.rst:5 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:164 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:71 #: ../../content/applications/finance/fiscal_localizations/chile.rst:198 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:123 #: ../../content/applications/finance/fiscal_localizations/peru.rst:69 @@ -1929,8 +1931,8 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:130 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:236 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 -#: ../../content/applications/finance/accounting/payments/checks.rst:84 -#: ../../content/applications/finance/accounting/payments/checks.rst:133 +#: ../../content/applications/finance/accounting/payments/checks.rst:108 +#: ../../content/applications/finance/accounting/payments/checks.rst:127 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:67 msgid "Bank" msgstr "" @@ -2390,6 +2392,46 @@ msgstr "" msgid "And here is the credit note’s journal entry generated to reverse the original invoice above:" msgstr "" +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:3 +msgid "Delivery and invoice addresses" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:5 +msgid "Companies often have multiple locations, and it is common that a customer invoice should be sent to one address and the delivery should be sent to another. Odoo's **Customer Addresses** feature is designed to handle this scenario by making it easy to specify which address to use for each case." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:10 +msgid ":doc:`overview`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:15 +msgid "To specify a sales order's invoice and delivery addresses, first go to :menuselection:`Accounting --> Configuration --> Settings`. In the :guilabel:`Customer Invoices` section, enable :guilabel:`Customer Addresses` and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:19 +msgid "On quotations and sales orders, there are now fields for :guilabel:`Invoice Address` and :guilabel:`Delivery Address`. If the customer has an invoice or delivery address listed on their contact record, the corresponding field will use that address by default, but any contact's address can be used instead." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:25 +msgid "Invoice and deliver to different addresses" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:27 +msgid "Delivery orders and their delivery slip reports use the address set as the :guilabel:`Delivery Address` on the sales order. By default, invoice reports show both the shipping address and the invoice address to assure the customer that the delivery is going to the correct location." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:31 +msgid "Emails also go to different addresses. The quotation and sales order are sent to the main contact's email, as usual, but the invoice is sent to the email of the address set as the :guilabel:`Invoice Address` on the sales order." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:36 +msgid "Reports, such as the delivery slip and invoice report, can be :doc:`customized using Studio `." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:38 +msgid "If :doc:`Send by Post ` is checked when you click :guilabel:`Send & Print`, the invoice will be mailed to the invoice address." +msgstr "" + #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:3 msgid "Deferred revenues" msgstr "" @@ -3392,9 +3434,9 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:222 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:232 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:248 -#: ../../content/applications/finance/accounting/payments/checks.rst:67 -#: ../../content/applications/finance/accounting/payments/checks.rst:80 -#: ../../content/applications/finance/accounting/payments/checks.rst:129 +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 msgid "Account" msgstr "" @@ -3403,9 +3445,9 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:222 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:232 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:248 -#: ../../content/applications/finance/accounting/payments/checks.rst:67 -#: ../../content/applications/finance/accounting/payments/checks.rst:80 -#: ../../content/applications/finance/accounting/payments/checks.rst:129 +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 #: ../../content/applications/finance/fiscal_localizations/france.rst:88 msgid "Debit" msgstr "" @@ -3415,9 +3457,9 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:222 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:232 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:248 -#: ../../content/applications/finance/accounting/payments/checks.rst:67 -#: ../../content/applications/finance/accounting/payments/checks.rst:80 -#: ../../content/applications/finance/accounting/payments/checks.rst:129 +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 #: ../../content/applications/finance/fiscal_localizations/france.rst:90 msgid "Credit" msgstr "" @@ -3426,8 +3468,8 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:115 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 -#: ../../content/applications/finance/accounting/payments/checks.rst:69 -#: ../../content/applications/finance/accounting/payments/checks.rst:131 +#: ../../content/applications/finance/accounting/payments/checks.rst:95 +#: ../../content/applications/finance/accounting/payments/checks.rst:125 msgid "Account Receivable" msgstr "" @@ -3530,6 +3572,46 @@ msgstr "" msgid "Click `here `_ to know about our *Privacy Policy*." msgstr "" +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:3 +msgid "Default terms and conditions (T&C)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:5 +msgid "Specifying terms and conditions is essential to establish important contractual points, such as return and refunds, warranty, and after-sale services." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:8 +msgid "You can add default terms and conditions at the bottom of all customer invoices, sales orders, and quotations, either as text or a link to a web page." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:12 +msgid "`Odoo Tutorial: Terms & Conditions `_" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:17 +msgid "Go to :menuselection:`Accounting --> Configuration --> Settings`. Under the :guilabel:`Customer Invoices`, enable :guilabel:`Default Terms & Conditions`. By default, the :guilabel:`Add a Note` option is selected, and the terms and conditions are displayed at the bottom of the document. Enter the terms and conditions in the text box below." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:-1 +msgid "Example of terms and conditions as a note" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:26 +msgid "You can also add a PDF version of your terms and conditions as an attachment when sending the document via email. Edit the email templates if you want to include them by default." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:29 +msgid "Alternatively, to display the terms and conditions on a web page, select the :guilabel:`Add a link to a Web Page` option and click :guilabel:`Save`. Click :guilabel:`Update Terms`, edit the content, and click :guilabel:`Save`. The link to that page is then added as a note in your document." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:34 +msgid "You can edit the layout and content of the page using the :doc:`Website ` app. If the Website app is activated, the :guilabel:`Edit in Website Builder` option then replaces :guilabel:`Update Terms`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:-1 +msgid "Example of terms and conditions as a web page" +msgstr "" + #: ../../content/applications/finance/accounting/get_started.rst:5 msgid "Get started" msgstr "" @@ -4115,6 +4197,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:3 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:79 #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:87 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:56 #: ../../content/applications/finance/fiscal_localizations/chile.rst:145 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:237 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:38 @@ -4447,6 +4530,14 @@ msgstr "" msgid ":doc:`../../fiscal_localizations`" msgstr "" +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:190 +msgid "`Odoo Tutorials: Chart of accounts `_" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:191 +msgid "`Odoo Tutorials: Update your chart of accounts `_" +msgstr "" + #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:7 msgid "Accounting cheat sheet" msgstr "" @@ -4580,6 +4671,7 @@ msgid "Balance = Debit - Credit" msgstr "" #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:133 +#: ../../content/applications/finance/accounting/payments/checks.rst:84 msgid "Journal entries" msgstr "" @@ -4867,6 +4959,7 @@ msgid "Select the currency and journal to use." msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:130 +#: ../../content/applications/finance/accounting/payments/checks.rst:58 msgid "Payment registration" msgstr "" @@ -5343,143 +5436,149 @@ msgid "Checks" msgstr "" #: ../../content/applications/finance/accounting/payments/checks.rst:5 -msgid "There are two ways to handle payments received by checks. Odoo support both approaches so that you can use the one that better fits your habits." +msgid "There are two ways to handle payments received by checks in Odoo, either by using :ref:`outstanding accounts ` or by :ref:`bypassing the reconciliation process `." msgstr "" #: ../../content/applications/finance/accounting/payments/checks.rst:9 -msgid "**Undeposited Funds:** once you receive the check, you record a payment by check on the invoice. (using a Check journal and posted on the Undeposited Fund account) Then, once the check arrives in your bank account, move money from Undeposited Funds to your bank account." +msgid "**Using outstanding accounts is recommended**, as your bank account balance stays accurate by taking into account checks yet to be cashed." msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:16 -msgid "**One journal entry only:** once your receive the check, you record a payment on your bank, paid by check, without going through the **Undeposited Funds**. Once you process your bank statement, you do the matching with your bank feed and the check payment, without creating a dedicated journal entry." +#: ../../content/applications/finance/accounting/payments/checks.rst:13 +msgid "Both methods produce the same data in your accounting at the end of the process. But if you have checks that have not been cashed in, the **Outstanding Account** method reports these checks in the **Outstanding Receipts** account. However, funds appear in your bank account whether or not they are reconciled, as the bank value is reflected at the moment of the bank statement." msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:23 -msgid "We recommend the first approach as it is more accurate (your bank account balance is accurate, taking into accounts checks that have not been cashed yet). Both approaches require the same effort." +#: ../../content/applications/finance/accounting/payments/checks.rst:20 +msgid ":ref:`Outstanding accounts `" msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:27 -msgid "Even if the first method is cleaner, Odoo support the second approach because some accountants are used to it (quickbooks and peachtree users)." +#: ../../content/applications/finance/accounting/payments/checks.rst:21 +msgid ":ref:`Bank reconciliation `" msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:32 -msgid "You may have a look at the *Deposit Ticket feature* if you deposit several checks to your bank accounts in batch." +#: ../../content/applications/finance/accounting/payments/checks.rst:26 +msgid "Method 1: Outstanding account" msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:36 -msgid "Option 1: Undeposited Funds" +#: ../../content/applications/finance/accounting/payments/checks.rst:28 +msgid "When you receive a check, you :doc:`record a payment <../bank/reconciliation>` by check on the invoice. Then, when your bank account is credited with the check's amount, you reconcile the payment and statement to move the amount from the **Outstanding Receipt** account to the **Bank** account." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:33 +msgid "You can create a new payment method named *Checks* if you would like to identify such payments quickly. To do so, go to :menuselection:`Accounting --> Configuration --> Journals --> Bank`, click the :guilabel:`Incoming Payments` tab, and :guilabel:`Add a line`. As :guilabel:`Payment Method`, select :guilabel:`Manual`, enter `Checks` as name, and :guilabel:`Save`." msgstr "" #: ../../content/applications/finance/accounting/payments/checks.rst:41 -msgid "Create a journal **Checks**" +msgid "Method 2: Reconciliation bypass" msgstr "" #: ../../content/applications/finance/accounting/payments/checks.rst:43 -msgid "Set **Undeposited Checks** as a default credit/debit account" +msgid "When you receive a check, you :doc:`record a payment <../bank/reconciliation>` on the related invoice. The amount is then moved from the **Account Receivable** to the **Bank** account, bypassing the reconciliation and creating only **one journal entry**." msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:45 -msgid "Set the bank account related to this journal as **Allow Reconciliation**" +#: ../../content/applications/finance/accounting/payments/checks.rst:47 +msgid "To do so, you *must* follow the following setup. Go to :menuselection:`Accounting --> Configuration --> Journals --> Bank`. Click the :guilabel:`Incoming Payments` tab and then :guilabel:`Add a line`, select :guilabel:`Manual` as :guilabel:`Payment Method`, and enter `Checks` as :guilabel:`Name`. Click the toggle menu button, tick :guilabel:`Outstanding Receipts accounts`, and in the :guilabel:`Outstanding Receipts accounts` column, and set the :guilabel:`Bank` account for the **Checks** payment method." msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:48 -#: ../../content/applications/finance/accounting/payments/checks.rst:108 -msgid "From check payments to bank statements" +#: ../../content/applications/finance/accounting/payments/checks.rst:-1 +msgid "Bypass the Outstanding Receipts account using the Bank account." msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:50 -msgid "The first way to handle checks is to create a check journal. Thus, checks become a payment method in itself and you will record two transactions." +#: ../../content/applications/finance/accounting/payments/checks.rst:61 +msgid "By default, there are two ways to register payments made by check:" msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:54 -#: ../../content/applications/finance/accounting/payments/checks.rst:110 -msgid "Once you receive a customer check, go to the related invoice and click on **Register Payment**. Fill in the information about the payment:" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/checks.rst:57 -msgid "Payment method: Check Journal (that you configured with the debit and credit default accounts as **Undeposited Funds**)" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/checks.rst:60 -msgid "Memo: write the Check number" +#: ../../content/applications/finance/accounting/payments/checks.rst:63 +msgid "**Manual**: for single checks;" msgstr "" #: ../../content/applications/finance/accounting/payments/checks.rst:64 -msgid "This operation will produce the following journal entry:" +msgid "**Batch**: for multiple checks at once." msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:67 -#: ../../content/applications/finance/accounting/payments/checks.rst:80 -#: ../../content/applications/finance/accounting/payments/checks.rst:129 -msgid "Statement Match" +#: ../../content/applications/finance/accounting/payments/checks.rst:66 +msgid "This documentation focuses on **single-check** payments. For **batch deposits**, see :doc:`the batch payments documentation `." msgstr "" #: ../../content/applications/finance/accounting/payments/checks.rst:69 -#: ../../content/applications/finance/accounting/payments/checks.rst:71 -#: ../../content/applications/finance/accounting/payments/checks.rst:82 -#: ../../content/applications/finance/accounting/payments/checks.rst:84 -#: ../../content/applications/finance/accounting/payments/checks.rst:131 -#: ../../content/applications/finance/accounting/payments/checks.rst:133 -msgid "100.00" +msgid "Once you receive a customer check, go to the related invoice (:menuselection:`Accounting --> Customer --> Invoices)`, and click :guilabel:`Register Payment`. Fill in the payment information:" msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:71 -#: ../../content/applications/finance/accounting/payments/checks.rst:82 -msgid "Undeposited Funds" +#: ../../content/applications/finance/accounting/payments/checks.rst:72 +msgid ":guilabel:`Journal: Bank`;" msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:74 -#: ../../content/applications/finance/accounting/payments/checks.rst:119 -msgid "The invoice is marked as paid as soon as you record the check." +#: ../../content/applications/finance/accounting/payments/checks.rst:73 +msgid ":guilabel:`Payment method`: :guilabel:`Manual` (or **Checks** if you have created a specific payment method);" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:75 +msgid ":guilabel:`Memo`: enter the check number;" msgstr "" #: ../../content/applications/finance/accounting/payments/checks.rst:76 -msgid "Then, once you get the bank statements, you will match this statement with the check that is in Undeposited Funds." +msgid "Click :guilabel:`Create Payment`." msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:82 -#: ../../content/applications/finance/accounting/payments/checks.rst:131 -msgid "X" +#: ../../content/applications/finance/accounting/payments/checks.rst:-1 +msgid "Check payment info" msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:88 -msgid "If you use this approach to manage received checks, you get the list of checks that have not been cashed in the **Undeposit Funds** account (accessible, for example, from the general ledger)." +#: ../../content/applications/finance/accounting/payments/checks.rst:81 +msgid "The generated journal entries are different depending on the payment registration method chosen." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:87 +msgid "Outstanding account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:89 +msgid "The invoice is marked as :guilabel:`In Payment` as soon as you record the payment. This operation produces the following **journal entry**:" msgstr "" #: ../../content/applications/finance/accounting/payments/checks.rst:93 -msgid "Both methods will produce the same data in your accounting at the end of the process. But, if you have checks that have not been cashed, this one is cleaner because those checks have not been reported yet on your bank account." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/checks.rst:99 -msgid "Option 2: One journal entry only" -msgstr "" - #: ../../content/applications/finance/accounting/payments/checks.rst:104 -msgid "These is nothing to configure if you plan to manage your checks using this method." +#: ../../content/applications/finance/accounting/payments/checks.rst:123 +msgid "Statement Match" msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:113 -msgid "**Payment method:** the bank that will be used for the deposit" +#: ../../content/applications/finance/accounting/payments/checks.rst:95 +#: ../../content/applications/finance/accounting/payments/checks.rst:97 +#: ../../content/applications/finance/accounting/payments/checks.rst:106 +#: ../../content/applications/finance/accounting/payments/checks.rst:108 +#: ../../content/applications/finance/accounting/payments/checks.rst:125 +#: ../../content/applications/finance/accounting/payments/checks.rst:127 +msgid "100.00" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:97 +#: ../../content/applications/finance/accounting/payments/checks.rst:106 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:76 +msgid "Outstanding Receipts" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:100 +msgid "Then, once you receive the bank statements, match this statement with the check of the **Outstanding Receipts** account. This produces the following **journal entry**:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:106 +#: ../../content/applications/finance/accounting/payments/checks.rst:125 +msgid "X" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:111 +msgid "If you use this approach to manage received checks, you get the list of checks that have not been cashed in the **Outstanding Receipt** account (accessible, for example, from the general ledger)." msgstr "" #: ../../content/applications/finance/accounting/payments/checks.rst:115 -msgid "Memo: write the check number" +msgid "Reconciliation bypass" msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:121 -msgid "Once you will receive the bank statements, you will do the matching with the statement and this actual payment. (technically: point this payment and relate it to the statement line)" +#: ../../content/applications/finance/accounting/payments/checks.rst:117 +msgid "The invoice is marked as :guilabel:`Paid` as soon as you record the check." msgstr "" -#: ../../content/applications/finance/accounting/payments/checks.rst:125 -msgid "With this approach, you will get the following journal entry in your books:" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/checks.rst:137 -msgid "You may also record the payment directly without going on the customer invoice, using the menu :menuselection:`Sales --> Payments`. This method may be more convenient if you have a lot of checks to record in a batch but you will have to reconcile entries afterwards (matching payments with invoices)" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/checks.rst:143 -msgid "If you use this approach to manage received checks, you can use the report **Bank Reconciliation Report** to verify which checks have been received or paid by the bank. (this report is available from the **More** option from the Accounting dashboard on the related bank account)." +#: ../../content/applications/finance/accounting/payments/checks.rst:119 +msgid "With this approach, you bypass the use of **outstanding accounts**, effectively getting only one journal entry in your books and bypassing the reconciliation:" msgstr "" #: ../../content/applications/finance/accounting/payments/follow_up.rst:3 @@ -8557,6 +8656,7 @@ msgstr "" #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:52 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:679 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:124 msgid "Reports" msgstr "" @@ -9924,7 +10024,7 @@ msgid "Expenses" msgstr "" #: ../../content/applications/finance/expenses.rst:7 -msgid "Odoo **Expenses** streamlines the management of expenses. After an employee submits their expenses in Odoo, the expenses are reviewed by management and accounting teams. Once approved, payments can then be processed and disbursed back to the employee for reimbursement(s)." +msgid "Odoo **Expenses** streamlines the management of expenses. After an employee submits their expenses in Odoo, the expenses are reviewed by management and accounting teams. Once approved, payments can then be processed and disbursed back to the employee for reimbursement(s)." msgstr "" #: ../../content/applications/finance/expenses.rst:12 @@ -9932,11 +10032,11 @@ msgid "`Odoo Expenses: product page `_" msgstr "" #: ../../content/applications/finance/expenses.rst:15 -msgid "Set expense types" +msgid "Set expense categories" msgstr "" #: ../../content/applications/finance/expenses.rst:17 -msgid "The first step to track expenses is to configure the different *expense types* for the company (managed as *products* in Odoo). Each \"product\" can be as specific or generalized as needed. Go to :menuselection:`Expenses app --> Configuration --> Expense Products` to view the current expensable products in a default kanban view." +msgid "The first step to track expenses is to configure the different types of expenses for the company (managed as *expense categories* in Odoo). Each category can be as specific or generalized as needed. Go to :menuselection:`Expenses app --> Configuration --> Expense Categories` to view the current expensable categories in a default list view." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 @@ -9944,163 +10044,192 @@ msgid "Set expense costs on products." msgstr "" #: ../../content/applications/finance/expenses.rst:26 -msgid "To create a new expense product, click :guilabel:`Create`. A product form will appear. Only two fields are required, the :guilabel:`Product Name` and the :guilabel:`Unit of Measure`. Enter the :guilabel:`Product Name` in the field, and select the :guilabel:`Unit of Measure` from the drop-down menu (most products will be set to :guilabel:`Units`)." +msgid "To create a new expense category, click :guilabel:`New`. A product form will appear, with the description field labeled :guilabel:`Product Name`." msgstr "" -#: ../../content/applications/finance/expenses.rst:32 -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 checked off in the `Product Catalog` section. Click on the :guilabel:`Units of Measure` internal link to view, create, and edit the units of measure. Refer to :doc:`this document ` to learn more about units of measure and how to configure them." +#: ../../content/applications/finance/expenses.rst:30 +msgid "Expense categories are managed like products in Odoo. The expense category form follows the standard product form in Odoo, and the information entered is similar. Expense products will be referred to as expense categories throughout this document since the main menu refers to these as :guilabel:`Expense Categories`." msgstr "" -#: ../../content/applications/finance/expenses.rst:43 +#: ../../content/applications/finance/expenses.rst:35 +msgid "Only two fields are required, the :guilabel:`Product Name` and the :guilabel:`Unit of Measure`. Enter the :guilabel:`Product Name` in the field, and select the :guilabel:`Unit of Measure` from the drop-down menu (most products will be set to :guilabel:`Units`)." +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 view, create, and edit the units of measure. Refer to :doc:`this document ` to learn more about units of measure and how to configure them." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:51 msgid "The :guilabel:`Cost` field on the product form is populated with a value of `0.00` by default. When a specific expense should always be reimbursed for a particular price, enter that amount in the :guilabel:`Cost` field. Otherwise, leave the :guilabel:`Cost` set to `0.00`, and employees will report the actual cost when submitting an expense report." msgstr "" -#: ../../content/applications/finance/expenses.rst:49 +#: ../../content/applications/finance/expenses.rst:57 +msgid "The :guilabel:`Cost` field is always visible on the expense category form, but the :guilabel:`Sales Price` field is *only* visible if the :guilabel:`Sales Price` is selected under the :guilabel:`Re-Invoice Expenses` section. Otherwise, the :guilabel:`Sales Price` field is hidden." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:63 msgid "Here are some examples for when to set a specific :guilabel:`Cost` on a product vs. leaving the :guilabel:`Cost` at `0.00`:" msgstr "" -#: ../../content/applications/finance/expenses.rst:52 +#: ../../content/applications/finance/expenses.rst:66 msgid "**Meals**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an expense for a meal, they enter the actual amount of the bill and will be reimbursed for that amount. An expense for a meal costing $95.23 would equal a reimbursement for $95.23." msgstr "" -#: ../../content/applications/finance/expenses.rst:55 -msgid "**Mileage**: Set the :guilabel:`Cost` to `0.30`. When an employee logs an expense for \"mileage\", they enter the number of miles driven, and are reimbursed 0.30 per mile they entered. An expense for 100 miles would equal a reimbursement for $30.00." +#: ../../content/applications/finance/expenses.rst:69 +msgid "**Mileage**: Set the :guilabel:`Cost` to `0.30`. When an employee logs an expense for \"mileage\", they enter the number of miles driven in the :guilabel:`Quantity` field, and are reimbursed 0.30 per mile they entered. An expense for 100 miles would equal a reimbursement for $30.00." msgstr "" -#: ../../content/applications/finance/expenses.rst:58 +#: ../../content/applications/finance/expenses.rst:73 msgid "**Monthly Parking**: Set the :guilabel:`Cost` to `75.00`. When an employee logs an expense for \"monthly parking\", the reimbursement would be for $75.00." msgstr "" -#: ../../content/applications/finance/expenses.rst:60 +#: ../../content/applications/finance/expenses.rst:75 msgid "**Expenses**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an expense that is not a meal, mileage, or monthly parking, they use the generic :guilabel:`Expenses` product. An expense for a laptop costing $350.00 would be logged as an :guilabel:`Expenses` product, and the reimbursement would be for $350.00." msgstr "" -#: ../../content/applications/finance/expenses.rst:65 +#: ../../content/applications/finance/expenses.rst:80 msgid "Select an :guilabel:`Expense Account` if using the Odoo *Accounting* app. It is recommended to check with the accounting department to determine the correct account to reference in this field as it will affect reports." msgstr "" -#: ../../content/applications/finance/expenses.rst:69 -msgid "Set a tax on each product in the :guilabel:`Vendor Taxes` and :guilabel:`Customer Taxes` fields if applicable. It is considered good practice to use a tax that is configured with :ref:`Tax Included in Price `. Taxes will be automatically configured if this is set." +#: ../../content/applications/finance/expenses.rst:84 +msgid "Set a tax on each product in the :guilabel:`Vendor Taxes` and :guilabel:`Customer Taxes` fields, if applicable. It is considered good practice to use a tax that is configured with :ref:`Tax Included in Price `. Taxes will be automatically configured if this is set." msgstr "" -#: ../../content/applications/finance/expenses.rst:76 +#: ../../content/applications/finance/expenses.rst:91 msgid "Record expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:79 +#: ../../content/applications/finance/expenses.rst:94 msgid "Manually create a new expense" msgstr "" -#: ../../content/applications/finance/expenses.rst:81 -msgid "To record a new expense, begin in the main :menuselection:`Expenses` app dashboard, which presents the default :guilabel:`My Expenses to Report` view. This view can also be accessed from :menuselection:`Expenses app --> My Expenses --> My Expenses to Report`." +#: ../../content/applications/finance/expenses.rst:96 +msgid "To record a new expense, begin in the main :menuselection:`Expenses` app dashboard, which presents the default :guilabel:`My Expenses` view. This view can also be accessed from :menuselection:`Expenses app --> My Expenses --> My Expenses`." msgstr "" -#: ../../content/applications/finance/expenses.rst:85 -msgid "First, click :guilabel:`Create`, and then fill out the various fields on the form." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:87 -msgid ":guilabel:`Description`: Enter a short description for the expense in the :guilabel:`Description` field. This should be short and informative, such as `lunch with client` or `hotel for conference`." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:90 -msgid ":guilabel:`Product`: Select the product from the drop-down menu that most closely corresponds to the expense. For example, an airplane ticket would be appropriate for an expense :guilabel:`Product` named :guilabel:`Air Travel`." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:93 -msgid ":guilabel:`Unit Price`: Enter the total amount paid for the expense in one of two ways:" -msgstr "" - -#: ../../content/applications/finance/expenses.rst:95 -msgid "If the expense is for one single item/expense, enter the cost in the :guilabel:`Unit Price` field, and leave the :guilabel:`Quantity` `1.00`." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:97 -msgid "If the expense is for multiples of the same item/expense, enter the price *per unit* in the :guilabel:`Unit Price` field, and enter the *quantity of units* in the :guilabel:`Quantity` field." +#: ../../content/applications/finance/expenses.rst:100 +msgid "First, click :guilabel:`New`, and then fill out the various fields on the form." msgstr "" #: ../../content/applications/finance/expenses.rst:102 -msgid "In the case of a hotel stay, for example, the :guilabel:`Unit Price` would be set as the cost *per night*, and set the :guilabel:`Quantity` to the *number of nights* stayed." +msgid ":guilabel:`Description`: Enter a short description for the expense in the :guilabel:`Description` field. This should be short and informative, such as `lunch with client` or `hotel for conference`." msgstr "" #: ../../content/applications/finance/expenses.rst:105 -msgid ":guilabel:`Taxes`: If taxes were paid on the expense, select the tax percentage using the drop-down menu. Tax options are pre-configured based on the localization setting selected when the database was created. Adding any new taxes should only be done when necessary." +msgid ":guilabel:`Category`: Select the expense category from the drop-down menu that most closely corresponds to the expense. For example, an airplane ticket would be appropriate for an expense :guilabel:`Category` named :guilabel:`Air Travel`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:108 +msgid ":guilabel:`Total`: Enter the total amount paid for the expense in one of two ways:" msgstr "" #: ../../content/applications/finance/expenses.rst:110 -msgid "When a tax is selected, the :guilabel:`Total` value will update in real time to show the added taxes." +msgid "If the expense is for one single item/expense, and the category selected was for a single item, enter the cost in the :guilabel:`Total` field (the :guilabel:`Quantity` field is hidden)." msgstr "" -#: ../../content/applications/finance/expenses.rst:113 -msgid ":guilabel:`Paid By`: Click the radio button to indicate who paid for the expense and should be reimbursed. If the employee paid for the expense (and should be reimbursed) select :guilabel:`Employee (to reimburse)`. If the company paid directly instead (e.g. if the company credit card was used to pay for the expense) select :guilabel:`Company`." +#: ../../content/applications/finance/expenses.rst:112 +msgid "If the expense is for multiples of the same item/expense with a fixed price, the :guilabel:`Unit Price` is displayed. Enter the quantity in the :guilabel:`Quantity` field, and the total cost is automatically updated with the correct total (the :guilabel:`Unit Price` x the :guilabel:`Quantity` = the total). Be advised, the word \"total\" does not appear, the total cost simply appears below the :guilabel:`Quantity`." msgstr "" -#: ../../content/applications/finance/expenses.rst:117 -msgid ":guilabel:`Expense Date`: Using the calendar module, enter the date the expense was incurred. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows to navigate to the correct month, then click on the specific day to enter the selection." +#: ../../content/applications/finance/expenses.rst:119 +msgid "For example, in the case of mileage driven, the :guilabel:`Unit Price` is populated as the cost *per mile*. Set the :guilabel:`Quantity` to the *number of miles* driven, and the total is calculated." msgstr "" -#: ../../content/applications/finance/expenses.rst:120 -msgid ":guilabel:`Bill Reference`: If there is any reference text that should be included for the expense, enter it in this field." +#: ../../content/applications/finance/expenses.rst:123 +msgid ":guilabel:`Included Taxes`: If taxes were configured on the expense category, the tax percentage and amount appear automatically after entering either the :guilabel:`Total` or the :guilabel:`Quantity`." msgstr "" -#: ../../content/applications/finance/expenses.rst:122 -msgid ":guilabel:`Account`: Select the expense account that this expense should be logged on from the drop-down menu." +#: ../../content/applications/finance/expenses.rst:128 +msgid "When a tax is configured on an expense category, the :guilabel:`Included Taxes` value will update in real time as the :guilabel:`Total` or :guilabel:`Quantity` is updated." msgstr "" -#: ../../content/applications/finance/expenses.rst:124 +#: ../../content/applications/finance/expenses.rst:131 msgid ":guilabel:`Employee`: Using the drop-down menu, select the employee this expense is for." msgstr "" -#: ../../content/applications/finance/expenses.rst:125 -msgid ":guilabel:`Customer to Reinvoice`: If the expense is something that should be paid for by a customer, select the customer that will be invoiced for this expense from the drop-down menu. For example, if a customer wishes to have an on-site meeting, and agrees to pay for the expenses associated with it (such as travel, hotel, meals, etc.), then all expenses tied to that meeting would indicate that customer as the :guilabel:`Customer to Reinvoice`." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:130 -msgid ":guilabel:`Analytic Account`: Select the account the expense should be written against from the drop-down menu." -msgstr "" - #: ../../content/applications/finance/expenses.rst:132 -msgid ":guilabel:`Company`: If multiple companies are set-up, select the company this expense should be filed for from the drop-down menu. If there is only one company, this field will be automatically populated." +msgid ":guilabel:`Paid By`: Click the radio button to indicate who paid for the expense and should be reimbursed. If the employee paid for the expense (and should be reimbursed) select :guilabel:`Employee (to reimburse)`. If the company paid directly instead (e.g. if the company credit card was used to pay for the expense) select :guilabel:`Company`. Depending on the expense category selected, this field may not appear." msgstr "" -#: ../../content/applications/finance/expenses.rst:135 +#: ../../content/applications/finance/expenses.rst:137 +msgid ":guilabel:`Bill Reference`: If there is any reference text that should be included for the expense, enter it in this field." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:139 +msgid ":guilabel:`Expense Date`: Using the calendar module, enter the date the expense was incurred. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows to navigate to the correct month, then click on the specific day to enter the selection." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:142 +msgid ":guilabel:`Account`: Select the expense account that this expense should be logged on from the drop-down menu." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:144 +msgid ":guilabel:`Customer to Reinvoice`: If the expense is something that should be paid for by a customer, select the :abbr:`SO (Sales Order)` and customer that will be invoiced for this expense from the drop-down menu. All sales orders in the drop-down menu list both the :abbr:`SO (Sales Order)` as well as the company the sales order is written for, but after the expense is saved, the customer name disappears and only the :abbr:`SO (Sales Order)` is visible on the expense." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:151 +msgid "A customer wishes to have an on-site meeting for a custom garden (design and installation) and agrees to pay for the expenses associated with it (such as travel, hotel, meals, etc.). All expenses tied to that meeting would indicate the sales order for the custom garden (which also references the customer) as the :guilabel:`Customer to Reinvoice`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:156 +msgid ":guilabel:`Analytic Distribution`: Select the account(s) the expense should be written against from the drop-down menu for either :guilabel:`Projects`, :guilabel:`Departments`, or both. Multiple accounts can be listed for each category if needed. Adjust the percentage for each analytic account by typing in the percentage value next to the account." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:160 +msgid ":guilabel:`Company`: If multiple companies are set up, select the company this expense should be filed for from the drop-down menu. The current company will automatically populate this field." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:162 msgid ":guilabel:`Notes...`: If any notes are needed in order to clarify the expense, enter them in the notes field." msgstr "" -#: ../../content/applications/finance/expenses.rst:138 -msgid "Once all the fields have been filled out, click :guilabel:`Save`." -msgstr "" - #: ../../content/applications/finance/expenses.rst:-1 msgid "A filled in expense form for a client lunch." msgstr "" -#: ../../content/applications/finance/expenses.rst:145 +#: ../../content/applications/finance/expenses.rst:170 msgid "Attach a receipt" msgstr "" -#: ../../content/applications/finance/expenses.rst:147 -msgid "After the expense is saved, the next step is to attach a receipt. A new :guilabel:`Attach Receipt` button appears after the entry is saved, beneath the former :guilabel:`Save` button (which turns into an :guilabel:`Edit` button)." +#: ../../content/applications/finance/expenses.rst:172 +msgid "After the expense is created, the next step is to attach a receipt. Click the :guilabel:`Attach Receipt` button, and a file explorer appears. Navigate to the receipt to be attached, and click :guilabel:`Open`. The new receipt is recorded in the chatter, and the number of receipts will appear next to the :guilabel:`📎 (paperclip)` icon beneath the expense form. More than one receipt can be attached to an individual expense, as needed. The number of receipts attached to the expense will be noted on the paperclip icon." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 -msgid "Attach a receipt after saving the record." +msgid "Attach a receipt and it appears in the chatter." msgstr "" -#: ../../content/applications/finance/expenses.rst:155 -msgid "Click the new :guilabel:`Attach Receipt` button, and a file explorer appears. Navigate to the receipt to be attached, and click :guilabel:`Open`. A new :guilabel:`Receipts` smart button appears at the top, and the new receipt is recorded in the chatter. More than one receipt can be attached to an individual expense, as needed. The number of receipts attached to the expense will be noted on the smart button." +#: ../../content/applications/finance/expenses.rst:184 +msgid "Create new expenses from a scanned receipt" msgstr "" -#: ../../content/applications/finance/expenses.rst:166 +#: ../../content/applications/finance/expenses.rst:186 +msgid "Rather than manually inputting all of the information for an expense, expenses can be created by scanning a PDF receipt." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:189 +msgid "First, in the main :guilabel:`Expenses` app dashboard view (this view can also be accessed from :menuselection:`Expenses app --> My Expenses --> My Expenses`), click :guilabel:`Scan`, and a file explorer pops up. Navigate to the receipt to be uploaded, click on it to select it, and then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Create an expense by scanning a receipt. Click Scan at the top of the Expenses dashboard\n" +"view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:199 +msgid "The receipt is scanned, and a new entry is created with today's date as the :guilabel:`Expense Date`, and any other fields it can populate based on the scanned data, such as the total. Click on the new entry to open the individual expense form, and make any changes needed. The scanned receipt appears in the chatter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:205 msgid "Automatically create new expenses from an email" msgstr "" -#: ../../content/applications/finance/expenses.rst:168 +#: ../../content/applications/finance/expenses.rst:207 msgid "Instead of individually creating each expense in the *Expenses* app, expenses can be automatically created by sending an email to an email alias." msgstr "" -#: ../../content/applications/finance/expenses.rst:171 -msgid "To do so, first, an email alias needs to be configured. Go to :menuselection:`Expenses app --> Configuration --> Settings`. Ensure :guilabel:`Incoming Emails` is checked off." +#: ../../content/applications/finance/expenses.rst:210 +msgid "To do so, first, an email alias needs to be configured. Go to :menuselection:`Expenses app --> Configuration --> Settings`. Ensure :guilabel:`Incoming Emails` is enabled." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 @@ -10108,196 +10237,244 @@ msgstr "" msgid "Create the domain alias by clicking the link." msgstr "" -#: ../../content/applications/finance/expenses.rst:179 +#: ../../content/applications/finance/expenses.rst:218 msgid "If the domain alias needs to be set up, :guilabel:`Setup your domain alias` will appear beneath the incoming emails check box instead of the email address field. Refer to this documentation for setup instructions and more information: :doc:`/administration/maintain/domain_names`. Once the domain alias is configured, the email address field will be visible beneath the incoming emails section." msgstr "" -#: ../../content/applications/finance/expenses.rst:185 -msgid "Next, enter the email address to be used in the email field, then click :guilabel:`Save`. Now that the email address has been entered, emails can be sent to that alias to create new expenses without having to be in the Odoo database." +#: ../../content/applications/finance/expenses.rst:224 +msgid "Next, enter the email address to be used in the email field, and then click :guilabel:`Save`. Now that the email address has been entered, emails can be sent to that alias to create new expenses without having to be in the Odoo database." msgstr "" -#: ../../content/applications/finance/expenses.rst:189 +#: ../../content/applications/finance/expenses.rst:228 msgid "To submit an expense via email, create a new email and enter the product's *internal reference* code (if available) and the amount of the expense in the email subject. Next, attach the receipt to the email. Odoo creates the expense by taking the information in the email subject and combining it with the receipt." msgstr "" -#: ../../content/applications/finance/expenses.rst:194 -msgid "To check an expense product's internal reference, go to :menuselection:`Expenses app --> Configuration --> Expense Products`. If an internal reference is listed on the product, it is visible in this view as :guilabel:`(Ref###)`." +#: ../../content/applications/finance/expenses.rst:233 +msgid "To check an expense categories internal reference, go to :menuselection:`Expenses app --> Configuration --> Expense Categories`. If an internal reference is listed on the expense category, it is listed in the :guilabel:`Internal Reference` column." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Internal reference numbers are listed in the main Expense Categories view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:241 +msgid "To add an internal reference on an expense category, click on the category to open the form. Enter the internal reference in the field. Beneath the :guilabel:`Internal Reference` field, this sentence appears: :guilabel:`Use this reference as a subject prefix when submitting by email.`" msgstr "" #: ../../content/applications/finance/expenses.rst:-1 msgid "Internal reference numbers are listed in the main Expense Products view." msgstr "" -#: ../../content/applications/finance/expenses.rst:202 -msgid "To add an internal reference on an expense product, click on the product, then click :guilabel:`Edit`. In edit mode, enter the :guilabel:`Internal Reference` in the field. Beneath the :guilabel:`Internal Reference` field, this sentence appears: :guilabel:`Use this reference as a subject prefix when submitting by email.`." +#: ../../content/applications/finance/expenses.rst:250 +msgid "For security purposes, only authenticated employee emails are accepted by Odoo when creating an expense from an email. To confirm an authenticated employee email address, go to the employee card in the :menuselection:`Employees` app, and refer to the :guilabel:`Work Email`" msgstr "" -#: ../../content/applications/finance/expenses.rst:212 -msgid "For security purposes, only authenticated employee emails are accepted by Odoo when creating an expense from an email. To confirm an authenticated employee email address, go to the employee card in the :guilabel:`Employees` app, and refer to the :guilabel:`Work Email` in the main field." +#: ../../content/applications/finance/expenses.rst:259 +msgid "If submitting an expense via email for a $25.00 meal during a work trip, the email subject would be `FOOD $25.00`." msgstr "" -#: ../../content/applications/finance/expenses.rst:221 -msgid "If submitting an expense via email for a $25.00 meal during a work trip, the email subject would be `Ref005 Meal $25.00`." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:224 +#: ../../content/applications/finance/expenses.rst:262 msgid "Explanation:" msgstr "" -#: ../../content/applications/finance/expenses.rst:226 -msgid "The :guilabel:`Internal Reference` for the expense product `Meals` is `Ref005`" +#: ../../content/applications/finance/expenses.rst:264 +msgid "The :guilabel:`Internal Reference` for the expense category `Meals` is `FOOD`" msgstr "" -#: ../../content/applications/finance/expenses.rst:227 +#: ../../content/applications/finance/expenses.rst:265 msgid "The :guilabel:`Cost` for the expense is `$25.00`" msgstr "" -#: ../../content/applications/finance/expenses.rst:230 +#: ../../content/applications/finance/expenses.rst:270 msgid "Create an expense report" msgstr "" -#: ../../content/applications/finance/expenses.rst:232 -msgid "When expenses are ready to submit (such as at the end of a business trip, or once a month), an *expense report* needs to be created. Go to the main :menuselection:`Expenses` app dashboard, which displays a default :guilabel:`My Expenses` view, or go to :menuselection:`Expenses app --> My Expenses --> My Expenses to Report`." +#: ../../content/applications/finance/expenses.rst:272 +msgid "When expenses are ready to submit (such as at the end of a business trip, or once a month), an *expense report* needs to be created. Go to the main :menuselection:`Expenses` app dashboard, which displays a default :guilabel:`My Expenses` view, or go to :menuselection:`Expenses app --> My Expenses --> My Expenses`." msgstr "" -#: ../../content/applications/finance/expenses.rst:237 -msgid "First, each individual expense for the report must be selected by clicking the check box next to each entry, or quickly select all the expenses in the list by clicking the check box next to :guilabel:`Expense Date`." +#: ../../content/applications/finance/expenses.rst:277 +msgid "Expenses are color coded by status. Any expense with a status of :guilabel:`To Report` (expenses that still need to be added to an expense report) the text appears in blue. All other statuses (:guilabel:`To Submit`, :guilabel:`Submitted`, and :guilabel:`Approved`) the text appears in black." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:281 +msgid "First, select each individual expense for the report by clicking the check box next to each entry, or quickly select all the expenses in the list by clicking the check box next to :guilabel:`Expense Date`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:285 +msgid "Another way to quickly add all expenses that are not on an expense report is to click :guilabel:`Create Report` without selecting any expenses, and Odoo will select all expenses with a status of :guilabel:`To Submit` that are not already on a report." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 msgid "Select the expenses to submit, then create the report." msgstr "" -#: ../../content/applications/finance/expenses.rst:245 -msgid "Once the expenses have been selected, click the :guilabel:`Create Report` button. The new report appears with all the expenses listed, and the number of documents is visible in the :guilabel:`Documents` smart button." +#: ../../content/applications/finance/expenses.rst:294 +msgid "Any expense can be selected from the :guilabel:`My Expenses` list, regardless of status. The :guilabel:`Create Report` button is visible as long as there is a minimum of 1 expense with a status of :guilabel:`To Report` selected. When the :guilabel:`Create Report` button is clicked, only expenses with a status of :guilabel:`To Submit` that are *not* currently on another expense report will appear in the newly created expense report." msgstr "" -#: ../../content/applications/finance/expenses.rst:249 -msgid "It is recommended to add a short summary for each report to help keep expenses organized. Click the :guilabel:`Edit` button, and the :guilabel:`Expense Report Summary` field appears. Enter a short description for the expense report (such as `Client Trip NYC`, or `Repairs for Company Car`). Next, select a :guilabel:`Manager` from the drop-down menu to assign a manager to review the report." +#: ../../content/applications/finance/expenses.rst:300 +msgid "Once the expenses have been selected, click the :guilabel:`Create Report` button. The new report appears with all the expenses listed in the :guilabel:`Expense` tab. If there is a receipt attached to an individual expense, a :guilabel:`📎 (paperclip)` icon appears next to the :guilabel:`Customer to Reinvoice` and :guilabel:`Analytic Distribution` columns." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:305 +msgid "When the report is created, the date range for the expenses appears in the :guilabel:`Expense Report Summary` field by default. It is recommended to edit this field with a short summary for each report to help keep expenses organized. Enter a short description for the expense report (such as `Client Trip NYC`, or `Repairs for Company Car`) in the :guilabel:`Expense Report Summary` field. Next, select a :guilabel:`Manager` from the drop-down menu to assign a manager to review the report. If needed, the :guilabel:`Journal` can be changed. Use the drop-down menu to select a different :guilabel:`Journal`." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 msgid "Enter a short description and select a manager for the report." msgstr "" -#: ../../content/applications/finance/expenses.rst:258 -msgid "If some expenses are not on the report that should be, they can still be added. Click :guilabel:`Add a line` at the bottom of the :guilabel:`Expense` tab. Click the check box next to each expense to add, then click :guilabel:`Select`. The items now appear on the report that was just created." +#: ../../content/applications/finance/expenses.rst:317 +msgid "If some expenses are not on the report that should be, they can still be added. Click :guilabel:`Add a line` at the bottom of the :guilabel:`Expense` tab. A pop up appears with all the available expenses that can be added to the report (with a status of :guilabel:`To Submit`). Click the check box next to each expense to add, then click :guilabel:`Select`. The items now appear on the report that was just created. If a new expense needs to be added that does *not* appear on the list, click :guilabel:`New` to create a new expense and add it to the report." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 msgid "Add more expenses to the report before submitting." msgstr "" -#: ../../content/applications/finance/expenses.rst:267 -msgid ":guilabel:`Add a line` only appears when the document is in edit mode. It does not appear otherwise." +#: ../../content/applications/finance/expenses.rst:329 +msgid "Expense reports can be created in one of three places:" msgstr "" -#: ../../content/applications/finance/expenses.rst:270 -msgid "When all edits have been completed, click :guilabel:`Save`." +#: ../../content/applications/finance/expenses.rst:331 +msgid "Go to the main :menuselection:`Expenses` app dashboard (also accessed by going to :menuselection:`Expenses app --> My Expenses --> My Expenses`)" msgstr "" -#: ../../content/applications/finance/expenses.rst:273 +#: ../../content/applications/finance/expenses.rst:333 +msgid "Go to :menuselection:`Expenses app --> My Expenses --> My Reports`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:334 +msgid "Go to :menuselection:`Expenses app --> Expense Reports`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:336 +msgid "In any of these views, click :guilabel:`New` to create a new expense report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:341 msgid "Submit an expense report" msgstr "" -#: ../../content/applications/finance/expenses.rst:275 +#: ../../content/applications/finance/expenses.rst:343 msgid "When an expense report is completed, the next step is to submit the report to a manager for approval. Reports must be individually submitted, and cannot be submitted in batches. Open the specific report from the list of expense reports (if the report is not already open). To view all expense reports, go to :menuselection:`Expenses app --> My Expenses --> My Reports`." msgstr "" -#: ../../content/applications/finance/expenses.rst:280 -msgid "If the list is large, grouping the results by status may be helpful since only reports that are in a :guilabel:`Draft` mode need to be submitted, reports with an :guilabel:`Approved` or :guilabel:`Submitted` status do not." +#: ../../content/applications/finance/expenses.rst:348 +msgid "If the list is large, grouping the results by status may be helpful since only reports that have a :guilabel:`To Submit` status need to be submitted, reports with an :guilabel:`Approved` or :guilabel:`Submitted` status do not." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:352 +msgid "The :guilabel:`To Submit` expenses are easily identifiable not just from the :guilabel:`To Submit` status, but the text appears in blue, while the other expenses text appears in black." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 msgid "Submit the report to the manager." msgstr "" -#: ../../content/applications/finance/expenses.rst:289 -msgid "The status of each report is shown in the :guilabel:`Status` column on the far right. If the :guilabel:`Status` column is not visible, click the :guilabel:`⋮ (additional options)` icon at the end of the row, and check the box next to :guilabel:`Status`." +#: ../../content/applications/finance/expenses.rst:360 +msgid "The status of each report is shown in the :guilabel:`Status` column on the right. If the :guilabel:`Status` column is not visible, click the :guilabel:`Additional Options (two dots)` icon at the end of the row, and enable :guilabel:`Status`." msgstr "" -#: ../../content/applications/finance/expenses.rst:293 +#: ../../content/applications/finance/expenses.rst:364 msgid "Click on a report to open it, then click :guilabel:`Submit To Manager`. After submitting a report, the next step is to wait for the manager to approve it." msgstr "" -#: ../../content/applications/finance/expenses.rst:297 +#: ../../content/applications/finance/expenses.rst:368 msgid "The :ref:`expenses/approve`, :ref:`expenses/post`, and :ref:`expenses/reimburse` sections are **only** for users with the *necessary rights*." msgstr "" -#: ../../content/applications/finance/expenses.rst:303 +#: ../../content/applications/finance/expenses.rst:374 msgid "Approve expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:305 -msgid "In Odoo, not just anyone can approve expense reports— only users with the necessary rights (or permissions) can. This means that a user must have at least *Team Approver* rights for the *Expenses* app. Employees with the necessary rights can review expense reports, and approve or reject them, as well as provide feedback thanks to the integrated communication tool." +#: ../../content/applications/finance/expenses.rst:376 +msgid "In Odoo, not just anyone can approve expense reports— only users with the necessary rights (or permissions) can. This means that a user must have at least *Team Approver* rights for the *Expenses* app. Employees with the necessary rights can review expense reports, approve or reject them, and provide feedback thanks to the integrated communication tool." msgstr "" -#: ../../content/applications/finance/expenses.rst:310 +#: ../../content/applications/finance/expenses.rst:381 msgid "To see who has rights to approve, go to the main :menuselection:`Settings` app and click on :guilabel:`Manage Users`." msgstr "" -#: ../../content/applications/finance/expenses.rst:314 -msgid "If the *Settings* app is not available, then certain rights are not set on the account. In the :guilabel:`Access Rights` tab of a user's card in the :menuselection:`Settings` app, the :guilabel:`Administration` section is set to one of three options:" +#: ../../content/applications/finance/expenses.rst:385 +msgid "If the *Settings* app is not available, then certain rights are not set on the account. Check the :guilabel:`Access Rights` tab of a user's card in the :menuselection:`Settings` app. the :guilabel:`Administration` section (bottom right of the :guilabel:`Access Rights` tab) is set to one of three options:" msgstr "" -#: ../../content/applications/finance/expenses.rst:318 +#: ../../content/applications/finance/expenses.rst:390 msgid ":guilabel:`None (blank)`: The user cannot access the *Settings* app at all." msgstr "" -#: ../../content/applications/finance/expenses.rst:319 +#: ../../content/applications/finance/expenses.rst:391 msgid ":guilabel:`Access Rights`: The user can only view the :guilabel:`User's & Companies` section of the *Settings* app." msgstr "" -#: ../../content/applications/finance/expenses.rst:321 +#: ../../content/applications/finance/expenses.rst:393 msgid ":guilabel:`Settings`: The user has access to the entire *Settings* app with no restrictions." msgstr "" -#: ../../content/applications/finance/expenses.rst:323 +#: ../../content/applications/finance/expenses.rst:395 msgid "Please refer to :doc:`this document ` to learn more about managing users and their access rights." msgstr "" -#: ../../content/applications/finance/expenses.rst:326 +#: ../../content/applications/finance/expenses.rst:398 msgid "Click on an individual to view their card, which displays the :guilabel:`Access Rights` tab in the default view. Scroll down to the :guilabel:`Human Resources` section. Under :guilabel:`Expenses`, there are four options:" msgstr "" -#: ../../content/applications/finance/expenses.rst:330 +#: ../../content/applications/finance/expenses.rst:402 msgid ":guilabel:`None (blank)`: A blank field means the user has no rights to view or approve expense reports, and can only view their own." msgstr "" -#: ../../content/applications/finance/expenses.rst:332 +#: ../../content/applications/finance/expenses.rst:404 msgid ":guilabel:`Team Approver`: The user can only view and approve expense reports for their own specific team." msgstr "" -#: ../../content/applications/finance/expenses.rst:334 +#: ../../content/applications/finance/expenses.rst:406 msgid ":guilabel:`All Approver`: The user can view and approve any expense report." msgstr "" -#: ../../content/applications/finance/expenses.rst:335 -msgid ":guilabel:`Administrator`: The user can view and approve any expense report as well as access the reporting and configuration menus in the *Expenses* app." +#: ../../content/applications/finance/expenses.rst:407 +msgid ":guilabel:`Administrator`: The user can view and approve any expense report, as well as access the reporting and configuration menus in the *Expenses* app." msgstr "" -#: ../../content/applications/finance/expenses.rst:338 -msgid "Users who are able to approve expense reports (typically managers) can easily view all expense reports to validate. Go to :menuselection:`Expenses app --> Expense Reports --> Reports to Approve`. This view lists all the expense reports that have been submitted but not approved, as noted by the :guilabel:`Submitted` tag in the status column." +#: ../../content/applications/finance/expenses.rst:410 +msgid "Users who are able to approve expense reports (typically managers) can easily view all expense reports they have access rights to. Go to :menuselection:`Expenses app --> Expense Reports`, and a list appears with all expense reports that have a status of either :guilabel:`To Submit`, :guilabel:`Submitted`, :guilabel:`Approved`, :guilabel:`Posted`, or :guilabel:`Done`. Expense reports with a status of :guilabel:`Refused` are hidden in the default view." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 msgid "Reports to validate are found on the Reports to Approve page." msgstr "" -#: ../../content/applications/finance/expenses.rst:347 -msgid "Reports can be approved in two ways (individually or several at once) and refused only one way. To approve multiple expense reports at once, remain in the list view. First, select the reports to approve by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all reports in the list. Next, click on the :guilabel:`⚙️ Action (gear)` icon, then click :guilabel:`Approve Report`." +#: ../../content/applications/finance/expenses.rst:420 +msgid "When viewing expense reports, there is a panel of filters that can be enabled or disabled on the left side. The three categories that filters can be applied on are :guilabel:`Status`, :guilabel:`Employee`, and :guilabel:`Company`. To view only expense reports with a particular status, enable the specific status filter to display the expense reports with only that status. Disable the specific status filter to hide the reports with that status. To view expense reports for a particular employee and/or company, enable the specific employee name filter and/or company filter in the :guilabel:`Employee` and :guilabel:`Company` sections." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:428 +msgid "Reports can be approved in two ways (individually or several at once) and refused only one way. To approve multiple expense reports at once, remain in the list view. First, select the reports to approve by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all the reports in the list." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:434 +msgid "Only reports with a status of :guilabel:`Submitted` can be approved. It is recommended to only display the submitted reports by adjusting the status filter on the left side by only having the :guilabel:`Submitted` filter enabled." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:438 +msgid "If a report is selected that is unable to be approved, the :guilabel:`Approve Report` button **will not appear**, indicating there is a problem with the selected report(s)." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:441 +msgid "Next, click the :guilabel:`Approve Report` button." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 msgid "Approve multiple reports by clicking the checkboxes next to each report." msgstr "" -#: ../../content/applications/finance/expenses.rst:357 -msgid "To approve an individual report, click on a report to go to a detailed view of that report. In this view, several options are presented: :guilabel:`Approve`, :guilabel:`Refuse`, or :guilabel:`Reset to draft`. Click :guilabel:`Approve` to approve the report." +#: ../../content/applications/finance/expenses.rst:447 +msgid "To approve an individual report, click on a report to go to a detailed view of that report. In this view, several options are presented: :guilabel:`Approve`, :guilabel:`Report in Next Payslip`, :guilabel:`Refuse`, or :guilabel:`Reset to draft`. Click :guilabel:`Approve` to approve the report." msgstr "" -#: ../../content/applications/finance/expenses.rst:361 -msgid "If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief explanation for the refusal in the :guilabel:`Reason to refuse Expense` field, then click :guilabel:`Refuse`." +#: ../../content/applications/finance/expenses.rst:451 +msgid "If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief explanation for the refusal in the :guilabel:`Reason to Refuse Expense` field, and then click :guilabel:`Refuse`." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 @@ -10305,182 +10482,192 @@ msgstr "" msgid "Send messages in the chatter." msgstr "" -#: ../../content/applications/finance/expenses.rst:368 -msgid "Team managers can easily view all the expense reports for their team members. While in the :guilabel:`Reports to Approve` view, click on :guilabel:`Filters`, then click :guilabel:`My Team`. This presents all the reports for the manager's team." +#: ../../content/applications/finance/expenses.rst:458 +msgid "Team managers can easily view all the expense reports for their team members. While in the :guilabel:`Expense Reports` view, click the drop-down arrow in the right-side of the search box, and click on :guilabel:`My Team` in the :guilabel:`Filters` section. This presents all the reports for the manager's team." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 msgid "Select the My Team filter." msgstr "" -#: ../../content/applications/finance/expenses.rst:377 -msgid "If more information is needed, such as a receipt is missing, communication is easy from the chatter. In an individual report, simply type in a message, tagging the proper person (if needed), and post it to the chatter by clicking :guilabel:`Send`. The message is posted in the chatter, and the person tagged will be notified via email of the message, as well as anyone following." +#: ../../content/applications/finance/expenses.rst:468 +msgid "If more information is needed, such as a missing receipt, communication is easy from the chatter. In an individual report, simply click :guilabel:`Send message` to open the message text box. Type in a message, tagging the proper person (if needed), and post it to the chatter by clicking :guilabel:`Send`. The message is posted in the chatter, and the person tagged will be notified via email of the message, as well as any followers." msgstr "" -#: ../../content/applications/finance/expenses.rst:390 +#: ../../content/applications/finance/expenses.rst:474 +msgid "The only people that can be tagged in a message are *followers*. To see who is a follower, click on the :guilabel:`👤 (person)` icon to display the followers of the expense." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:484 msgid "Post expenses in accounting" msgstr "" -#: ../../content/applications/finance/expenses.rst:392 -msgid "Once an expense report is approved, the next step is to post the report to the accounting journal. To view all expense reports to post, go to :menuselection:`Expenses --> Expense Reports --> Reports To Post`." +#: ../../content/applications/finance/expenses.rst:486 +msgid "Once an expense report is approved, the next step is to post the report to the accounting journal. To view all expense reports, go to :menuselection:`Expenses app --> Expense Reports`. To view only the expense reports that have been approved and need to be posted, adjust the filters on the left side so that only the :guilabel:`Approved` status is enabled." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 msgid "View reports to post by clicking on expense reports, then reports to post." msgstr "" -#: ../../content/applications/finance/expenses.rst:400 -msgid "Just like approvals, expense reports can be posted in two ways (individually or several at once). To post multiple expense reports at once, remain in the list view. First, select the reports to post by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all reports in the list. Next, click on the :guilabel:`⚙️ Action (gear)` icon, then click :guilabel:`Post Entries`." +#: ../../content/applications/finance/expenses.rst:495 +msgid "Just like approvals, expense reports can be posted in two ways (individually or several at once). To post multiple expense reports at once, remain in the list view. First, select the reports to post by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all the reports in the list. Next, click :guilabel:`Post Entries`." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 -msgid "Post multiple reports from the Post Entries view." +msgid "Post multiple reports at a time from the Expense Reports view, with the Approved filter." msgstr "" -#: ../../content/applications/finance/expenses.rst:410 -msgid "To post an individual report, click on a report to go to the detailed view of that report. In this view, several options are presented: :guilabel:`Post Journal Entries`, :guilabel:`Report In Next Payslip`, or :guilabel:`Refuse`. Click :guilabel:`Post Journal Entries` to post the report." +#: ../../content/applications/finance/expenses.rst:504 +msgid "To post an individual report, click on a report to go to the detailed view of that report. In this view, several options are presented: :guilabel:`Post Journal Entries`, :guilabel:`Report In Next Payslip`, :guilabel:`Refuse`, or :guilabel:`Reset to Draft`. Click :guilabel:`Post Journal Entries` to post the report." msgstr "" -#: ../../content/applications/finance/expenses.rst:414 -msgid "If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief explanation for the refusal in the :guilabel:`Reason to refuse Expense` field, then click :guilabel:`Refuse`. Refused reports can be viewed by going to :menuselection:`Expenses app --> Expense Reports --> All Reports`. This list shows all reports, including the refused ones." +#: ../../content/applications/finance/expenses.rst:509 +msgid "If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief explanation for the refusal in the :guilabel:`Reason to Refuse Expense` field, and then click :guilabel:`Refuse`. Refused reports can be viewed by going to :menuselection:`Expenses app --> Expense Reports`, then adjusting the filters on the left so that only :guilabel:`Refused` is selected. This will only show the refused expense reports." msgstr "" -#: ../../content/applications/finance/expenses.rst:420 +#: ../../content/applications/finance/expenses.rst:516 msgid "To post expense reports to an accounting journal, the user must have following access rights:" msgstr "" -#: ../../content/applications/finance/expenses.rst:422 +#: ../../content/applications/finance/expenses.rst:518 msgid "Accounting: Accountant or Adviser" msgstr "" -#: ../../content/applications/finance/expenses.rst:423 +#: ../../content/applications/finance/expenses.rst:519 msgid "Expenses: Manager" msgstr "" -#: ../../content/applications/finance/expenses.rst:428 +#: ../../content/applications/finance/expenses.rst:524 msgid "Reimburse employees" msgstr "" -#: ../../content/applications/finance/expenses.rst:430 -msgid "After an expense report is posted to an accounting journal, the next step is to reimburse the employee. To view all expense reports to pay, go to :menuselection:`Expenses --> Expense Reports --> Reports To Pay`." +#: ../../content/applications/finance/expenses.rst:526 +msgid "After an expense report is posted to an accounting journal, the next step is to reimburse the employee. To view all the expense reports to pay, go to :menuselection:`Expenses app --> Expense Reports --> Reports To Pay`." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 msgid "View reports to pay by clicking on expense reports, then reports to pay." msgstr "" -#: ../../content/applications/finance/expenses.rst:438 -msgid "Just like approvals and posting, expense reports can be paid in two ways (individually or several at once). To pay multiple expense reports at once, remain in the list view. First, select the reports to pay by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all reports in the list. Next, click on the :guilabel:`⚙️ Action (gear)` icon, then click :guilabel:`Register Payment`." +#: ../../content/applications/finance/expenses.rst:534 +msgid "Just like approvals and posting, expense reports can be paid in two ways (individually or several at once). To pay multiple expense reports at once, remain in the list view. First, select the reports to pay by clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select all the reports in the list. Next, click :guilabel:`Register Payment`." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 -msgid "Post multiple reports by clicking the checkboxes, clicking the gear, then post the entries." +msgid "Post multiple reports by selecting them, clicking the gear, and then post the entries." msgstr "" -#: ../../content/applications/finance/expenses.rst:448 +#: ../../content/applications/finance/expenses.rst:543 msgid "To pay an individual report, click on a report to go to a detailed view of that report. Click :guilabel:`Register Payment` to pay the employee." msgstr "" -#: ../../content/applications/finance/expenses.rst:452 +#: ../../content/applications/finance/expenses.rst:546 +msgid "A :guilabel:`Register Payment` pop-up appears, and the :guilabel:`Journal`, :guilabel:`Payment Method`, and :guilabel:`Payment Date` can be modified, if needed. When the selections are correct, click :guilabel:`Create Payment` to send the payment to the employee." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:550 +msgid "To pay an individual report, click on a report in the list view to go to a detailed view of that report. Click :guilabel:`Register Payment` to pay the employee. A :guilabel:`Register Payment` pop-up appears, but when paying an individual expense report instead of several at once, more options appear in the pop-up. In addition to the :guilabel:`Journal`, :guilabel:`Payment Method`, and :guilabel:`Payment Date` fields, a :guilabel:`Recipient Bank Account`, :guilabel:`Amount`, and :guilabel:`Memo` field appear. Select the employee's bank account from the drop-down menu to directly deposit the payment to their account. When all other selections are correct, click :guilabel:`Create Payment` to send the payment to the employee." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "Different options appear when registering an individual expense report versus multiple\n" +"expense reports at once." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:565 msgid "Re-invoice expenses to customers" msgstr "" -#: ../../content/applications/finance/expenses.rst:454 -msgid "If expenses are tracked on customer projects, expenses can be automatically charged back to the customer. This is done by creating an expense report, then creating a sales order with the expensed items on it. Then, managers approve the expense report, and the accounting department posts the journal entries. Finally, the customer is invoiced." +#: ../../content/applications/finance/expenses.rst:567 +msgid "If expenses are tracked on customer projects, expenses can be automatically charged back to the customer. This is done by creating an expense, referencing the :abbr:`SO (Sales Order)` the expense should be added to, and then creating the expense report. Next, managers approve the expense report, and the accounting department posts the journal entries. Finally, once the expense report is posted to a journal, the expense(s) appears on the :abbr:`SO (Sales Order)` that was referenced. The sales order can then be invoiced, thus invoicing the customer for the expense." msgstr "" -#: ../../content/applications/finance/expenses.rst:460 +#: ../../content/applications/finance/expenses.rst:575 #: ../../content/applications/finance/fiscal_localizations/india.rst:55 #: ../../content/applications/finance/fiscal_localizations/india.rst:195 msgid "Setup" msgstr "" -#: ../../content/applications/finance/expenses.rst:462 -msgid "First, specify the invoicing policy for each expense product. Go to :menuselection:`Expenses app --> Configuration --> Expense Products`. Click on the expense product to edit, then click :guilabel:`Edit`. Under the :guilabel:`Invoicing` section, select the :guilabel:`Invoicing Policy` and :guilabel:`Re-Invoicing Policy` by clicking the radio button next to the desired selection." +#: ../../content/applications/finance/expenses.rst:577 +msgid "First, specify the invoicing policy for each expense category. Go to :menuselection:`Expenses app --> Configuration --> Expense Categories`. Click on the expense category to open the expense category form. Under the :guilabel:`Invoicing` section, click the radio button next to the desired selection for :guilabel:`Re-Invoicing Expenses`. Options are :guilabel:`None`, :guilabel:`At cost`, and :guilabel:`Sales price`." msgstr "" -#: ../../content/applications/finance/expenses.rst:467 -msgid ":guilabel:`Invoicing Policy`:" +#: ../../content/applications/finance/expenses.rst:583 +msgid ":guilabel:`Re-Invoicing Expenses`:" msgstr "" -#: ../../content/applications/finance/expenses.rst:469 -msgid ":guilabel:`Ordered quantities`: Expense product will only invoice expenses based on the ordered quantity." +#: ../../content/applications/finance/expenses.rst:585 +msgid ":guilabel:`None`: Expense category will not be re-invoiced." msgstr "" -#: ../../content/applications/finance/expenses.rst:471 -msgid ":guilabel:`Delivered quantities`: Expense product will only invoice expenses based on the delivered quantity." +#: ../../content/applications/finance/expenses.rst:586 +msgid ":guilabel:`At cost`: Expense category will invoice expenses at their real cost." msgstr "" -#: ../../content/applications/finance/expenses.rst:474 -msgid ":guilabel:`Re-Invoicing Policy`:" +#: ../../content/applications/finance/expenses.rst:587 +msgid ":guilabel:`At sales price`: Expense category will invoice the price set on the sale order." msgstr "" -#: ../../content/applications/finance/expenses.rst:476 -msgid ":guilabel:`No`: Expense product will not be re-invoiced." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:477 -msgid ":guilabel:`At cost`: Expense product will invoice expenses at their real cost." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:478 -msgid ":guilabel:`At sales price`: Expense product will invoice the price set on the sale order." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:481 +#: ../../content/applications/finance/expenses.rst:590 msgid "Create an expense" msgstr "" -#: ../../content/applications/finance/expenses.rst:483 -msgid "First, when :ref:`creating a new expense `, the correct information needs to be entered in order to re-invoice a customer. Select the :guilabel:`Customer to Reinvoice` from the drop-down menu. Next, select the :guilabel:`Analytic Account` the expense will be posted to." +#: ../../content/applications/finance/expenses.rst:592 +msgid "First, when :ref:`creating a new expense `, the correct information needs to be entered in order to re-invoice a customer. Select the *sales order* the expense will appear on in the :guilabel:`Customer to Reinvoice` section, from the drop-down menu. Next, select the :guilabel:`Analytic Account` the expense will be posted to. After the expense(s) are created, the expense report needs to be :ref:`created ` and :ref:`submitted ` as usual." msgstr "" #: ../../content/applications/finance/expenses.rst:-1 msgid "Ensure the customer to be invoiced is called out on the expense." msgstr "" -#: ../../content/applications/finance/expenses.rst:492 -msgid "Create a quote and sales order" +#: ../../content/applications/finance/expenses.rst:604 +msgid "Selecting a :guilabel:`Customer to Reinvoice` when creating an expense is critical, since this is what causes the expenses to be automatically invoiced after an expense report is approved." msgstr "" -#: ../../content/applications/finance/expenses.rst:494 -msgid "In the :menuselection:`Sales` app, create a quote for the customer being invoiced, listing the expense products. First, click :guilabel:`Create` to create a new quotation. Next, select the :guilabel:`Customer` being invoiced for the expenses from the drop-down menu." +#: ../../content/applications/finance/expenses.rst:607 +msgid "The :guilabel:`Customer to Reinvoice` field can be modified *until an expense report is* **approved**, then the field is no longer able to be modified." msgstr "" -#: ../../content/applications/finance/expenses.rst:498 -msgid "In the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`. In the :guilabel:`Product` field, select the first item being invoiced from the drop-down menu, or type in the product name. Then, update the :guilabel:`Quantity`, the :guilabel:`Delivered` quantity, and the :guilabel:`Unit Price` if needed. Repeat this for all products being invoiced. When all the products have been added to the quote, click :guilabel:`Confirm` and the quotation becomes a sales order." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:-1 -msgid "Create and confirm the sales order with the expenses listed as products." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:508 -msgid "Once the quote turns into a sales order, a :guilabel:`Delivered` column appears. The delivered quantity must be updated for each item. Click on the `0.000` field for each product, and enter the delivered quantity. When all delivered quantities have been entered, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/finance/expenses.rst:513 +#: ../../content/applications/finance/expenses.rst:611 msgid "Validate and post expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:515 -msgid "Only employees with permissions (typically managers or supervisors) can :ref:`approve expenses `. Before approving an expense report, ensure the :guilabel:`Analytic Account` is set on every expense line of a report. If an :guilabel:`Analytic Account` is missing, click :guilabel:`Edit` and select the correct account from the drop-down menu, then click :guilabel:`Approve` or :guilabel:`Refuse`." +#: ../../content/applications/finance/expenses.rst:613 +msgid "Only employees with permissions (typically managers or supervisors) can :ref:`approve expenses `. Before approving an expense report, ensure the :guilabel:`Analytic Distribution` is set on every expense line of a report. If an :guilabel:`Analytic Distribution` is missing, assign the correct account(s) from the drop-down menu, and then click :guilabel:`Approve` or :guilabel:`Refuse`." msgstr "" -#: ../../content/applications/finance/expenses.rst:521 -msgid "The accounting department is typically responsible for :ref:`posting journal entries `. Once an expense report is approved, it can then be posted." +#: ../../content/applications/finance/expenses.rst:619 +msgid "The accounting department is typically responsible for :ref:`posting journal entries `. Once an expense report is approved, it can then be posted. The :abbr:`SO (Sales Order)` is **only** updated *after the journal entries are posted*. One the journal entries are posted, the expenses now appear on the referenced :abbr:`SO (Sales Order)`." msgstr "" -#: ../../content/applications/finance/expenses.rst:525 +#: ../../content/applications/finance/expenses.rst:625 msgid "Invoice expenses" msgstr "" -#: ../../content/applications/finance/expenses.rst:527 -msgid "Once the quote has turned into a sales order, and the expense report has been approved, it is time to invoice the customer. Go to :menuselection:`Sales app --> To Invoice --> Orders to Invoice` to view the sales orders ready to be invoiced." +#: ../../content/applications/finance/expenses.rst:627 +msgid "Once the :abbr:`SO (Sales Order)` has been updated, it is time to invoice the customer. After the expense report has been approved and the journal entries have been posted, click the :guilabel:`Sales Orders` smart button to open the :abbr:`SO (Sales Order)`. The expenses to be re-invoiced are now on the :abbr:`SO (Sales Order)`." msgstr "" -#: ../../content/applications/finance/expenses.rst:531 -msgid "Next, find the sales order related to the expense report, click into it, and then click :guilabel:`Create Invoice` and a :guilabel:`Create invoices` pop-up window appears. Select if the invoice is a :guilabel:`Regular invoice`, :guilabel:`Down payment (percentage)`, or :guilabel:`Down payment (fixed amount)` by clicking the radio button next to the selection. For either down payment options, enter the amount (fixed or percentage) in the :guilabel:`Down Payment Amount` field. Finally, click either :guilabel:`create and view invoice` or :guilabel:`create invoice`." +#: ../../content/applications/finance/expenses.rst:-1 +msgid "After the expense report is posted to the journal entry, the sales order can be called up\n" +"by clicking on the sales order number." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:638 +msgid "More than one :abbr:`SO (Sales Order)` can be referenced on an expense report. If more than one :abbr:`SO (Sales Order)` is referenced, the :guilabel:`Sales Orders` smart button will list the number of :abbr:`SO (Sales Order)`'s. If multiple :abbr:`SO (Sales Order)`'s are listed, the :guilabel:`Sales Orders` smart button opens a list view of all the :abbr:`SO (Sales Order)`'s on the expense report. Click on a :abbr:`SO (Sales Order)` to open the individual :abbr:`SO (Sales Order)`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:645 +msgid "The expenses are listed in the :abbr:`SO (Sales Order)` :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:-1 +msgid "See the expenses listed on the sales order after clicking into it." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:651 +msgid "Next, click :guilabel:`Create Invoice`, and select if the invoice is for a :guilabel:`Regular invoice`, a :guilabel:`Down payment (percentage)`, or a :guilabel:`Down payment (fixed amount)` by clicking the radio button next to it. Then, click :guilabel:`Create Invoice`. The customer has now been invoiced for the expenses." msgstr "" #: ../../content/applications/finance/fiscal_localizations.rst:5 @@ -10865,6 +11052,7 @@ msgid ":ref:`Install ` the following modules to get all the fea msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:26 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:16 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:42 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:16 #: ../../content/applications/finance/fiscal_localizations/france.rst:182 @@ -10879,6 +11067,7 @@ msgid "Name" msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:27 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:17 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:43 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:17 #: ../../content/applications/finance/fiscal_localizations/india.rst:17 @@ -10892,6 +11081,7 @@ msgid "Technical name" msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:28 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:18 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:44 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:18 #: ../../content/applications/finance/fiscal_localizations/france.rst:59 @@ -11958,177 +12148,597 @@ msgstr "" msgid "Belgium" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:8 -msgid "Fiscal certification: POS restaurant" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/belgium.rst:10 -msgid "In Belgium, the owner of a cooking business such as a restaurant or food truck is required by law to use a government-certified **Cash Register System** for their receipts. This applies if their yearly earnings (excluding VAT, drinks, and take-away food) exceed 25,000 euros." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:14 -msgid "This government-certified system entails the use of a :ref:`certified POS system `, along with a device called a :ref:`Fiscal Data Module ` (or **black box**) and a :ref:`VAT Signing Card `." +msgid ":ref:`Install ` the following modules to get all the features of the Belgian localization, following the :abbr:`IFRS(International Financial Reporting Standards)` rules." msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:19 -msgid "Do not forget to register as *foodservice industry manager* on the `Federal Public Service Finance registration form `_." +msgid ":guilabel:`Belgium - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:20 +msgid "`l10n_be`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:21 +msgid "Default :ref:`fiscal localization package `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:22 +msgid ":guilabel:`Belgium - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:23 +msgid "`l10n_be_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:24 +msgid "Access to specific accounting reports for Belgium." msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:25 -msgid "Certified POS system" +msgid ":guilabel:`Belgium - Accounting Reports (post wizard)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:26 +msgid "`l10n_be_reports_post_wizard`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:27 -msgid "The Odoo POS system is certified for the major versions of databases hosted on **Odoo Online** and **Odoo.sh**. Please refer to the following table to ensure that your POS system is certified." +msgid "Enables the VAT wizard when posting a tax return journal entry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:28 +msgid ":guilabel:`Belgium - Import Bank CODA Statements`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:29 +msgid "`l10n_be_coda`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:30 +msgid "Import CODA bank statements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:31 +msgid ":guilabel:`Belgium - Import SODA files`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:32 +msgid "`l10n_be_soda`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:33 +msgid "Import SODA files." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:34 +msgid ":guilabel:`Belgium - Disallowed Expenses Data`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:35 +msgid "`l10n_be_disallowed_expenses`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:36 +msgid "Access to the use of disallowed expenses features." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:37 +msgid ":guilabel:`Belgium - Payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:38 +msgid "`l10n_be_hr_payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:39 +msgid "Access to the basic payroll features for Belgium." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:40 +msgid ":guilabel:`Belgium - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:41 +msgid "`l10n_be_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:42 +msgid "Integration of accounting data with payroll." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:43 +msgid ":guilabel:`Belgium - Payroll - Dimona`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:44 +msgid "`l10n_be_hr_payroll_dimona`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:45 +msgid "Access to Dimona features for payroll." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:46 +msgid ":guilabel:`Belgium - Payroll - Fleet`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:47 +msgid "`l10n_be_hr_payroll_fleet`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:48 +msgid "Fleet features for payroll." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:49 +msgid ":guilabel:`Salary Configurator (Belgium)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:50 +msgid "`l10n_be_hr_contract_salary`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:51 +msgid "Access to the salary configurator feature." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:58 +msgid "You can reach the :guilabel:`Chart of accounts` by going to :menuselection:`Accounting --> Configuration --> Accounting: Chart of Accounts`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:61 +msgid "The Belgian chart of accounts includes pre-configured accounts as described in the :abbr:`PCMN(Plan Comptable Minimum Normalisé)`. To add a new account, click :guilabel:`New`. A new line appears. Fill it in, click :guilabel:`Save`, and then :guilabel:`Setup` to configure it further." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:66 +msgid ":doc:`../accounting/get_started/chart_of_accounts`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:73 +msgid "Default Belgian taxes are created automatically when the :guilabel:`Belgium - Accounting` and the :guilabel:`Belgium - Accounting Reports` modules are installed. Each tax impacts the Belgian :guilabel:`Tax Report`, available by going to :menuselection:`Accounting --> Reporting --> Statements Reports: Tax Report`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:78 +msgid "In Belgium, the standard VAT rate is **21%**, but there are lower rates for some categories of goods and services. An intermediate rate of **12%** is applied on social housing and food served in restaurants, while a reduced rate of **6%** applies to most basic goods, such as food, water supply, books, and medicine. A **0%** rate applies to some exceptional goods and services, such as some daily and weekly publications, as well as recycled goods." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:87 +msgid "Non-deductible taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:89 +msgid "In Belgium, some taxes are not fully deductible, such as taxes on the maintenance of cars. This means a part of these taxes is considered as an expense." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:92 +msgid "In Odoo, you can configure non-deductible taxes by creating tax rules for these taxes and linking them to the corresponding accounts. This way, the system automatically calculates the taxes and allocates them to the appropriate accounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:96 +msgid "To configure a new non-deductible tax, go to :menuselection:`Accounting --> Configuration --> Accounting: Taxes`, and click :guilabel:`New`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:99 +msgid ":guilabel:`Add a line` and select :guilabel:`Base` in the :guilabel:`Based On` column;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:100 +msgid ":guilabel:`Add a line`, then select :guilabel:`on tax` in the :guilabel:`Based on` column and enter the **non-deductible** percentage in the :guilabel:`%` column;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:102 +msgid "On the :guilabel:`of tax` line, select the :guilabel:`Tax Grid(s)` related to your tax;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:103 +msgid ":guilabel:`Add a line` with the **deductible** percentage in the :guilabel:`%` column;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:104 +msgid "Set :guilabel:`of tax` in :guilabel:`Based On`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:105 +msgid "Select :guilabel:`411000 VAT recoverable` as account, and select the related tax grid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:107 +msgid "Once you have created a non-deductible tax, you can apply it to your transactions by selecting the appropriate tax during the encoding of bills and credit notes. The system automatically calculates the tax amount and allocates it to the corresponding accounts based on the tax rules configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:112 +msgid "With the Belgian localization, the **21% car** tax is created by default (50% non-deductible)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Example of not-fully deductible tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:118 +msgid ":doc:`Taxes <../accounting/taxes>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:119 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:50 +msgid ":doc:`../accounting/reporting/tax_returns`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:126 +msgid "Here is the list of Belgian-specific reports available:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:128 +msgid "Balance sheet;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:129 +msgid "Profit & loss;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:130 +msgid "Tax report;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:131 +msgid "Partner VAT Listing;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:132 +msgid "EC Sales List;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:133 +msgid "Intrastat." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:135 +msgid "You can access Belgian-specific versions of reports by clicking on the **book** icon when on a report and selecting its Belgian version: **(BE)**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 +msgid "Belgian version of reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:142 +msgid ":doc:`../accounting/reporting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:147 +msgid "Disallowed expenses report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:149 +msgid "**Disallowed expenses** are expenses that can be deducted from your accounting result but not from your fiscal result." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:152 +msgid "The **disallowed expenses report** is available by going to :menuselection:`Accounting --> Reporting --> Management: Disallowed Expenses`. It allows financial results in real-time, and periodic changes. This report is generated based on the **disallowed expenses categories** that you can reach by going to :menuselection:`Accounting --> Configuration --> Management: Disallowed Expenses Categories`. Some categories already exist by default but do not have any rates. Click on :guilabel:`Set Rates` to update a specific category." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:160 +msgid "You can add multiple rates for various dates. In that case, the rate used to calculate the expense depends on the date at which it is calculated, and the rate set for that date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:162 +msgid "If you have the **Fleet** app installed, tick the :guilabel:`Car Category` box when applicable. This makes the vehicle mandatory while booking a vendor bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:165 +msgid "To link a disallowed expenses category with a specific account, go to :menuselection:`Accounting --> Configuration --> Acounting: Chart of Accounts`. Find the account you want, and click on :guilabel:`Setup`. Add the :guilabel:`Disallowed Expense category` in the :guilabel:`Disallowed Expenses` field. From now, when an expense is created with this account, the disallowed expense is calculated based on the rate mentioned in the :guilabel:`Disallowed Expense category`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:171 +msgid "Let's take an example reflecting **restaurant** and **car expenses**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:176 +msgid "Restaurant expenses" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:178 +msgid "In Belgium, 31% of **restaurant** expenses are non-deductible. Create a new **disallowed expenses category** and set both :guilabel:`Related Account(s)` and :guilabel:`Current Rate`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 +msgid "Disallowed expenses categories" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:187 +msgid "Car expenses: vehicle split" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:189 +msgid "In Belgium, the deductible percentage varies from car to car and, therefore, should be indicated for each vehicle. To do so, open :menuselection:`Fleet` and select a vehicle. In the :guilabel:`Tax info` tab, go to the :guilabel:`Disallowed Expenses Rate` section and click on :guilabel:`Add a line`. Add a :guilabel:`Start Date` and a :guilabel:`%`. The amounts go in the same account for all car expenses." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:195 +msgid "When you create a bill for car expenses, you can link each expense to a specific car by filling the :guilabel:`Vehicle` column, so the right percentage is applied." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:201 +msgid "The :guilabel:`vehicle split` option available in the disallowed expenses report allows you to see the rate and disallowed amount for each car." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:210 +msgid "Fee form 281.50 and form 325" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:215 +msgid "Fee form 281.50" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:217 +msgid "Annually, a **281.50 fee form** must be reported to the fiscal authorities. To do so, the tag `281.50` must be added on the **contact form** of the entities concerned by the **281.50** fee. To add the tag, open :menuselection:`Contacts`, select the person or company you want to create a **281.50 fee form** for, and add the `281.50` tag in the :guilabel:`Tags` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 +msgid "add the tag 281.50 on a contact form" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:226 +msgid "Make sure the **street, zip code, country**, and **VAT number** are also informed on the **Contact form**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:229 +msgid "Then, depending on the nature of the expense, add the corresponding `281.50` tag on the impact accounts. To do so, go to :menuselection:`Accounting --> Configuration --> Accounting: Chart of Accounts`, and click on :guilabel:`Setup` to add the corresponding `281.50` tag on the impacted accounts, i.e., :guilabel:`281.50 - Commissions`, depending on the nature of the expense." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:237 +msgid "Form 325" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:239 +msgid "You can create a **325 form** by going to :menuselection:`Accounting --> Reporting --> Belgium: Create 325 form`. A new page pops up: select the right options and click :guilabel:`Generate 325 form`. To open an already generated **325 form**, go to :menuselection:`Accounting --> Reporting --> Belgium: Open 325 forms`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 +msgid "Add the tag 281-50 on a contact form" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:250 +msgid "CODA and SODA statements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:255 +msgid "CODA" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:257 +msgid "**CODA** is an electronic XML format used to import Belgian bank statements. You can download CODA files from your bank and import them directly into Odoo by clicking :guilabel:`Import Statement` from your :guilabel:`Bank` journal on your dashboard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 +msgid "Import CODA files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:265 +msgid "The :guilabel:`Belgium - Import Bank CODA Statements` module is installed by default when the :guilabel:`Belgium - Accounting` and the :guilabel:`Belgium - Accounting Reports` modules are installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:270 +msgid ":ref:`Import bank statements files `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:275 +msgid "SODA" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:277 +msgid "**SODA** is an electronic XML format used to import accounting entries related to salaries. SODA files can be imported into the journal you use to record salaries by going to your Accounting **dashboard** and clicking :guilabel:`Upload` in the related journal card form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:281 +msgid "Once your **SODA** files are imported, the entries are created automatically in your 'salary' journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 +msgid "Import SODA files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:290 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:256 +msgid "Electronic invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:292 +msgid "Odoo supports the **E-FFF** and **Peppol BIS Billing 3.0 (UBL)** electronic invoicing formats. To enable them, go to :menuselection:`Accounting --> Configuration --> Journals --> Customer Invoices --> Advanced Settings --> Electronic Invoicing`, and tick :guilabel:`E-FFF (BE)` and :guilabel:`Peppol BIS Billing 3.0`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:298 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:179 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:102 +msgid ":doc:`../accounting/customer_invoices/electronic_invoicing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:303 +msgid "Cash discount" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:305 +msgid "In Belgium, if an early payment discount is offered on an invoice, the tax is calculated based on the discounted total amount, whether the customer benefits from the discount or not." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:308 +msgid "To apply the right tax amount and report it correctly in your VAT return, set the tax reduction as :guilabel:`Always (upon invoice)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:312 +msgid ":doc:`../accounting/customer_invoices/cash_discounts`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:317 +msgid "Fiscal certification: POS restaurant" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:319 +msgid "In Belgium, the owner of a cooking business such as a restaurant or food truck is required by law to use a government-certified **Cash Register System** for their receipts. This applies if their yearly earnings (excluding VAT, drinks, and take-away food) exceed 25,000 euros." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:323 +msgid "This government-certified system entails the use of a :ref:`certified POS system `, along with a device called a :ref:`Fiscal Data Module ` (or **black box**) and a :ref:`VAT Signing Card `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:328 +msgid "Do not forget to register as *foodservice industry manager* on the `Federal Public Service Finance registration form `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:334 +msgid "Certified POS system" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:336 +msgid "The Odoo POS system is certified for the major versions of databases hosted on **Odoo Online** and **Odoo.sh**. Please refer to the following table to ensure that your POS system is certified." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:344 #: ../../content/applications/finance/payment_providers/stripe.rst:19 msgid "Odoo Online" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:36 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:345 msgid "Odoo.sh" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:37 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:346 msgid "On-Premise" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:38 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:347 msgid "Odoo 16.0" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:39 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:40 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:348 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:349 msgid "Review in progress" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:41 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:43 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:44 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:45 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:49 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:53 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:350 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:352 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:353 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:354 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:358 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:362 msgid "Not certified" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:42 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:351 msgid "Odoo 15.2" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:46 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:355 msgid "Odoo 15.0" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:47 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:48 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:51 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:52 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:356 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:357 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:360 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:361 msgid "Certified" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:50 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:359 msgid "Odoo 14.0" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:56 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:365 msgid ":doc:`/administration/maintain/supported_versions`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:58 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:367 msgid "A `certified POS system `_ must adhere to rigorous government regulations, which means it operates differently from a non-certified POS." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:62 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:371 msgid "On a certified POS, you cannot:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:64 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:373 msgid "Set up and use the **global discounts** feature (the `pos_discount` module is blacklisted and cannot be activated)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:66 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:375 msgid "Set up and use the **loyalty programs** feature (the `pos_loyalty` module is blacklisted and cannot be activated)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:68 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:377 msgid "Reprint receipts (the `pos_reprint` module is blacklisted and cannot be activated)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:69 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:378 msgid "Modify prices in order lines." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:70 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:379 msgid "Modify or delete order lines in POS orders." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:71 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:380 msgid "Sell products without a valid VAT number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:72 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:381 msgid "Use a POS that is not connected to an IoT box." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:74 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:383 msgid "The :doc:`cash rounding <../../sales/point_of_sale/pricing/cash_rounding>` feature must be activated and set to a :guilabel:`Rounding Precision` of `0,05` and a :guilabel:`Rounding Method` set as :guilabel:`Half-Up`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:77 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:386 msgid "Taxes must be set as included in the price. To set it up, go to :menuselection:`Point of Sale --> Configuration --> Settings`, and from the :guilabel:`Accounting` section, open the :guilabel:`Default Sales Tax` form by clicking the arrow next to the default sales tax field. There, click :guilabel:`Advanced Options` and enable :guilabel:`Included in Price`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:81 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:390 msgid "At the start of a POS session, users must click :guilabel:`Work in` to clock in. Doing so allows the registration of POS orders. If users are not clocked in, they cannot make POS orders. Likewise, they must click :guilabel:`Work Out` to clock out at the end of the session." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:86 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:395 msgid "If you configure a POS to work with a black box, you cannot use it again without it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:91 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:400 msgid "The Fiscal Data Module" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:93 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:402 msgid "The :abbr:`FDM (Fiscal Data Module)`, or `black box `_, is a government-certified device that works together with the Point of Sale application and saves your POS orders information. Concretely, a **hash** (:dfn:`unique code`) is generated for each POS order and added to its receipt. This allows the government to verify that all revenue is declared." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:99 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:408 msgid "Ensure your black box is approved by the Belgian government. You can check the compliance of your black box by visiting the `Federal Public Service Finance `_ website." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:106 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:415 msgid "Before setting up your database to work with an FDM, ensure you have the following hardware:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:108 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:417 msgid "a registered :ref:`black box ` (go to `www.boîtenoire.be `_ to order yours);" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:110 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:419 msgid "an RS-232 serial null modem cable per FDM;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:111 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:420 msgid "an RS-232 serial-to-USB adapter per FDM;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:112 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:421 msgid "an :ref:`IoT Box ` (one IoT box per black box); and" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:113 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:422 msgid "a receipt printer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:118 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:427 msgid "Black box module" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:120 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:429 msgid "As a pre-requisite, :ref:`activate ` the `Belgian Registered Cash Register` module (technical name: `pos_blackbox_be`)." msgstr "" @@ -12136,7 +12746,7 @@ msgstr "" msgid "black box modules for belgian fiscal certification" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:127 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:435 msgid "Once the module is activated, add your VAT number to your company information. To set it up, go to :menuselection:`Settings --> Companies --> Update Info`, and fill in the :guilabel:`VAT` field. Then, enter a national registration number for every staff member who operates the POS system. To do so, go to the :guilabel:`Employees` app and open an employee form. There, go to :menuselection:`HR settings tab --> Attendance/Point of Sale`, and fill in the :guilabel:`INSZ or BIS number` field." msgstr "" @@ -12144,35 +12754,35 @@ msgstr "" msgid "ISNZ or BIS number field on employee form" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:138 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:445 msgid "To input your information, click on your avatar, go to :menuselection:`My Profile --> Preference tab`, and enter your INSZ or BIS number in the designated field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:142 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:449 msgid "You must configure the black box directly in the production database. Utilizing it in a testing environment may result in incorrect data being stored within the black box." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:148 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:455 msgid "IoT Box" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:150 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:457 msgid "In order to use a Fiscal Data Module, you need a registered IoT Box. To register your IoT box, you must contact us through our `support contact form `_ and provide the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:154 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:461 msgid "your VAT number;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:155 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:462 msgid "your company's name, address, and legal structure; and" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:156 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:463 msgid "the Mac address of your IoT Box." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:158 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:465 msgid "Once your IoT box is certified, :doc:`connect <../../productivity/iot/config/connect>` it to your database. To verify that the IoT Box recognizes the FDM, go to the IoT homepage and scroll down the :guilabel:`IOT Device` section, which should display the FDM." msgstr "" @@ -12180,19 +12790,19 @@ msgstr "" msgid "Hardware status page on a registered IoT Box" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:166 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:472 msgid "Then, add the IoT to your POS. To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, select your POS, scroll down to the :guilabel:`Connected Device` section, and enable :guilabel:`IoT Box`. Lastly, add the FMD in the :guilabel:`Fiscal Data Module` field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:171 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:477 msgid "To be able to use an FDM, you must at least connect one :guilabel:`Receipt Printer`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:176 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:482 msgid "VAT signing card" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:178 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:484 msgid "When you open a POS session and make your initial transaction, you are prompted to enter the PIN provided with your :abbr:`VSC (VAT signing card)`. The card is delivered by the :abbr:`FPS (Service Public Federal Finances)` upon `registration `_." msgstr "" @@ -14189,7 +14799,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:18 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:1504 -#: ../../content/applications/finance/spreadsheet.rst:25 +#: ../../content/applications/finance/spreadsheet.rst:26 msgid "Glossary" msgstr "" @@ -14444,11 +15054,6 @@ msgstr "" msgid "In the :guilabel:`Advanced Settings` tab, check the :guilabel:`Electronic Invoicing` checkbox to enable it for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:179 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:102 -msgid ":doc:`../accounting/customer_invoices/electronic_invoicing`" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:182 msgid "Withholding" msgstr "" @@ -18295,10 +18900,6 @@ msgstr "" msgid "To download it, go to :menuselection:`Accounting --> Report --> Audit Reports --> Tax Report`, and click on :guilabel:`Export eCDF declaration`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:50 -msgid ":doc:`../accounting/reporting/tax_returns`" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:51 msgid "`Platform for electronic gathering of financial data (eCDF) `_" msgstr "" @@ -18647,10 +19248,6 @@ msgstr "" msgid "You must also configure the company with a real address within Mexico (including all fields) and add ``EKU9003173C9`` as the **VAT** number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:256 -msgid "Electronic invoicing" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/mexico.rst:258 msgid "The invoicing process in Odoo is based on `Annex 20 `_ version 3.3 of electronic invoicing of the SAT." msgstr "" @@ -21329,10 +21926,6 @@ msgstr "" msgid "101002" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:76 -msgid "Outstanding Receipts" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:78 msgid "101003" msgstr "" @@ -22034,7 +22627,7 @@ msgstr "" #: ../../content/applications/finance/payment_providers.rst:343 #: ../../content/applications/finance/payment_providers/authorize.rst:40 -#: ../../content/applications/finance/payment_providers/stripe.rst:119 +#: ../../content/applications/finance/payment_providers/stripe.rst:122 msgid "Configuration tab" msgstr "" @@ -22212,7 +22805,7 @@ msgstr "" #: ../../content/applications/finance/payment_providers/paypal.rst:157 #: ../../content/applications/finance/payment_providers/razorpay.rst:46 #: ../../content/applications/finance/payment_providers/sips.rst:32 -#: ../../content/applications/finance/payment_providers/stripe.rst:142 +#: ../../content/applications/finance/payment_providers/stripe.rst:145 msgid ":doc:`../payment_providers`" msgstr "" @@ -22374,7 +22967,7 @@ msgstr "" #: ../../content/applications/finance/payment_providers/adyen.rst:137 #: ../../content/applications/finance/payment_providers/authorize.rst:43 -#: ../../content/applications/finance/payment_providers/stripe.rst:124 +#: ../../content/applications/finance/payment_providers/stripe.rst:127 msgid "Place a hold on a card" msgstr "" @@ -23238,7 +23831,7 @@ msgstr "" #: ../../content/applications/finance/payment_providers/stripe.rst:21 #: ../../content/applications/finance/payment_providers/stripe.rst:37 -msgid "Go to the **eCommerce** or the **Sales** app and click on the *Activate Stripe* or the *Set payments* button on the onboarding banner." +msgid "Go to the **eCommerce** or the **Sales** app and click the :guilabel:`Activate Stripe` or the :guilabel:`Set payments` button on the onboarding banner." msgstr "" #: ../../content/applications/finance/payment_providers/stripe.rst:23 @@ -23268,7 +23861,7 @@ msgid "Odoo.sh or On-premise" msgstr "" #: ../../content/applications/finance/payment_providers/stripe.rst:41 -msgid "At the end of the process, you are redirected to the payment provider **Stripe** on Odoo." +msgid "At the end of the process, you are redirected to the payment provider **Stripe** in Odoo." msgstr "" #: ../../content/applications/finance/payment_providers/stripe.rst:42 @@ -23288,198 +23881,198 @@ msgid "You are all set and can continue to :ref:`stripe/local-payment-methods`." msgstr "" #: ../../content/applications/finance/payment_providers/stripe.rst:48 -msgid "To connect your Stripe account after the onboarding is already completed, go to :menuselection:`Accounting --> Configuration --> Payment Providers --> Stripe` and click on the *Connect Stripe* button." +msgid "To connect your Stripe account after the onboarding has already been completed, go to :menuselection:`Accounting --> Configuration --> Payment Providers --> Stripe` and click the :guilabel:`Connect Stripe` button." msgstr "" #: ../../content/applications/finance/payment_providers/stripe.rst:53 -msgid "If you are testing Stripe (in **test mode**), change the **State** to *Test Mode*. We recommend doing this on a test Odoo database rather than on your main database." +msgid "If you are testing Stripe (in **test mode**), change the :guilabel:`State` to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database rather than on your main database." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:59 +#: ../../content/applications/finance/payment_providers/stripe.rst:60 msgid "Fill in your credentials" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:61 +#: ../../content/applications/finance/payment_providers/stripe.rst:62 msgid "In case your **API Credentials** are required to connect with your Stripe account, these are the credentials that must be completed:" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:64 +#: ../../content/applications/finance/payment_providers/stripe.rst:65 msgid ":ref:`Publishable Key `: The key solely used to identify the account with Stripe." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:65 +#: ../../content/applications/finance/payment_providers/stripe.rst:66 msgid ":ref:`Secret Key `: The key to sign the merchant account with Stripe." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:66 +#: ../../content/applications/finance/payment_providers/stripe.rst:67 msgid ":ref:`Webhook Signing Secret `: When you enable your webhook on your Stripe account, this signing secret must be set to authenticate the messages sent from Stripe to Odoo." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:69 +#: ../../content/applications/finance/payment_providers/stripe.rst:70 msgid "To retrieve the publishable and secret keys, follow this `link to your API keys `_, or log into your Stripe dashboard and go to :menuselection:`Developers --> API Keys --> Standard Keys`." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:76 +#: ../../content/applications/finance/payment_providers/stripe.rst:77 msgid "Generate a webhook" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:78 +#: ../../content/applications/finance/payment_providers/stripe.rst:79 msgid "In case your **Webhook Signing Secret** is required to connect with your Stripe account, you can create a webhook either automatically or manually." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:82 +#: ../../content/applications/finance/payment_providers/stripe.rst:83 msgid "Manage the webhook automatically" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:84 -msgid "Make sure your :ref:`Publishable and Secret keys ` are filled in, then click on the :guilabel:`Generate your Webhook` button." +#: ../../content/applications/finance/payment_providers/stripe.rst:85 +msgid "Make sure your :ref:`Publishable and Secret keys ` are filled in, then click the :guilabel:`Generate your Webhook` button." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:88 -msgid "To update the webhook, click once again on the :guilabel:`Generate your Webhook` button." +#: ../../content/applications/finance/payment_providers/stripe.rst:89 +msgid "To update the webhook, click once again the :guilabel:`Generate your Webhook` button." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:90 +#: ../../content/applications/finance/payment_providers/stripe.rst:91 msgid "Manage the webhook manually" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:92 -msgid "Visit the `webhooks page on Stripe `_, or log into your Stripe dashboard and go to :menuselection:`Developers --> Webhooks`. Then, click on :guilabel:`Add endpoint` in your :guilabel:`Hosted endpoints` and insert the following data into the pop-up form:" +#: ../../content/applications/finance/payment_providers/stripe.rst:93 +msgid "Visit the `webhooks page on Stripe `_, or log into your Stripe dashboard and go to :menuselection:`Developers --> Webhooks`. Then, click :guilabel:`Add endpoint` and insert the following data in the :guilabel:`Listen to Stripe events` form:" msgstr "" #: ../../content/applications/finance/payment_providers/stripe.rst:0 -msgid "In the :guilabel:`Endpoint URL`, enter your Odoo database's URL followed by" -msgstr "" - -#: ../../content/applications/finance/payment_providers/stripe.rst:0 -msgid "`/payment/stripe/webhook`." +msgid "In the :guilabel:`Endpoint URL` field, enter your Odoo database's URL followed by `/payment/stripe/webhook`." msgstr "" #: ../../content/applications/finance/payment_providers/stripe.rst:0 msgid "For example: `https://yourcompany.odoo.com/payment/stripe/webhook`" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:100 -msgid "At the bottom of the form, you can select events to listen to. Click on :guilabel:`Select events`. Then:" +#: ../../content/applications/finance/payment_providers/stripe.rst:101 +msgid "At the bottom of the form, click :guilabel:`+ Select events`, then:" msgstr "" #: ../../content/applications/finance/payment_providers/stripe.rst:103 -msgid "In the :guilabel:`Payment Intent` section, select :guilabel:`payment_intent.amount_capturable_updated` and :guilabel:`payment_intent.succeeded`." +msgid "In the :guilabel:`Charge` section, select :guilabel:`charge.refunded` and :guilabel:`charge.refund.updated`." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:106 -msgid "In the :guilabel:`Setup Intent` section, select :guilabel:`setup_intent.succeeded`." +#: ../../content/applications/finance/payment_providers/stripe.rst:105 +msgid "In the :guilabel:`Payment Intent` section, select :guilabel:`payment_intent.amount_capturable_updated`, :guilabel:`payment_intent.payment_failed` and :guilabel:`payment_intent.succeeded`." msgstr "" #: ../../content/applications/finance/payment_providers/stripe.rst:109 +msgid "In the :guilabel:`Setup Intent` section, select :guilabel:`setup_intent.succeeded`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:112 msgid "It is possible to select other events, but they are currently not processed by Odoo." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:111 -msgid "When you click on :guilabel:`Add endpoint`, your Webhook is configured. Click on :guilabel:`reveal` to display your signing secret." +#: ../../content/applications/finance/payment_providers/stripe.rst:114 +msgid "Once you have selected the events, click :guilabel:`Add events`, then :guilabel:`Add endpoint` to generate your webhook. Click :guilabel:`Reveal` to display your signing secret." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:115 -msgid "To update an existing webhook, click on it. Then, click on the three dots at the right side of the **Webhook URL** and on :guilabel:`Update details`." +#: ../../content/applications/finance/payment_providers/stripe.rst:118 +msgid "To update an existing webhook, click on it. Then, click the three dots at the right side of the **Webhook URL** and select :guilabel:`Update details`." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:126 +#: ../../content/applications/finance/payment_providers/stripe.rst:129 msgid "Stripe allows you to **capture an amount manually** instead of having an immediate capture. This feature earmarks an amount on the customer's account for a determined period of time that depends on the payment method used." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:130 -msgid "To set it up, enable the :guilabel:`Capture Amount Manually` option on Odoo, as explained in the :ref:`payment providers documentation `." +#: ../../content/applications/finance/payment_providers/stripe.rst:133 +msgid "To set it up, enable the :guilabel:`Capture Amount Manually` option in Odoo, as explained in the :ref:`payment providers documentation `." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:134 +#: ../../content/applications/finance/payment_providers/stripe.rst:137 msgid "When the manual capture feature is activated, your customers are not able to proceed with any payment if unsupported payment methods are selected." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:138 +#: ../../content/applications/finance/payment_providers/stripe.rst:141 msgid "Odoo doesn't support the partial capture yet. Be aware that a partial capture from Stripe's interface is still managed as a full capture by Odoo." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:147 +#: ../../content/applications/finance/payment_providers/stripe.rst:150 msgid "Enable local payment methods" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:149 +#: ../../content/applications/finance/payment_providers/stripe.rst:152 msgid "Local payment methods are payment methods that are only available for certain merchants and customers countries and currencies." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:152 +#: ../../content/applications/finance/payment_providers/stripe.rst:155 msgid "Odoo supports the following local payment methods:" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:154 +#: ../../content/applications/finance/payment_providers/stripe.rst:157 msgid "Bancontact" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:155 +#: ../../content/applications/finance/payment_providers/stripe.rst:158 msgid "EPS" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:156 +#: ../../content/applications/finance/payment_providers/stripe.rst:159 msgid "giropay" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:157 +#: ../../content/applications/finance/payment_providers/stripe.rst:160 msgid "iDEAL" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:158 +#: ../../content/applications/finance/payment_providers/stripe.rst:161 msgid "Przelewy24 (P24)" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:160 -msgid "To enable some of these local payment methods with Stripe, list them as supported payment icons. To do so, go to :menuselection:`Payment Providers --> Stripe --> Configuration` and add the desired payment methods in the **Supported Payment Icons** field. If the desired payment method is already listed, you don't have anything to do." +#: ../../content/applications/finance/payment_providers/stripe.rst:163 +msgid "To enable some of these local payment methods with Stripe go to :menuselection:`Payment Providers --> Stripe --> Configuration` and add the desired payment methods in the :guilabel:`Supported Payment Methods` field. If the desired payment method is already listed, you don't have anything to do." msgstr "" #: ../../content/applications/finance/payment_providers/stripe.rst:-1 msgid "Select and add icons of the payment methods you want to enable" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:170 +#: ../../content/applications/finance/payment_providers/stripe.rst:173 msgid "If a payment icon record does not exist in the database and its related local payment method is listed above, it is considered enabled with Stripe." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:172 -msgid "If a local payment method is not listed above, it is not supported and cannot be enabled." -msgstr "" - -#: ../../content/applications/finance/payment_providers/stripe.rst:177 -msgid "Enable express checkout" +#: ../../content/applications/finance/payment_providers/stripe.rst:175 +msgid "If a local payment method is not listed, it is not supported and cannot be enabled." msgstr "" #: ../../content/applications/finance/payment_providers/stripe.rst:180 +msgid "Enable express checkout" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:183 msgid ":ref:`payment_providers/features/express_checkout`" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:182 +#: ../../content/applications/finance/payment_providers/stripe.rst:185 msgid "After ticking the :guilabel:`Allow Express Checkout` checkbox, **Google Pay** is enabled out of the box, but **Apple Pay** requires extra steps: You must register your web domain with Apple. This can be done either automatically from Odoo, or manually from Stripe." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:187 +#: ../../content/applications/finance/payment_providers/stripe.rst:190 msgid "Register automatically from Odoo" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:189 +#: ../../content/applications/finance/payment_providers/stripe.rst:192 msgid "Navigate to your payment provider and make sure that it is :guilabel:`enabled`." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:190 -msgid "Go to the :guilabel:`Configuration` tab and click on the :guilabel:`Enable Apple Pay` button. A notification shows that the web domain was successfully registered with Apple." +#: ../../content/applications/finance/payment_providers/stripe.rst:193 +msgid "Go to the :guilabel:`Configuration` tab and click the :guilabel:`Enable Apple Pay` button. A notification shows that the web domain was successfully registered with Apple." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:193 +#: ../../content/applications/finance/payment_providers/stripe.rst:196 msgid "Register manually from Stripe" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:195 -msgid "Visit the `Apple pay web domains page on Stripe `_, or log into your Stripe dashboard and go to :menuselection:`Settings --> Payments methods --> Apple Pay --> Configure --> Web domains`. Then, click on :guilabel:`Add new domain` and insert the web domain of your Odoo database into the pop-up form. Odoo already hosts the verification file of Stripe. Click on :guilabel:`Add` to register your web domain with Apple." +#: ../../content/applications/finance/payment_providers/stripe.rst:198 +msgid "Visit the `Apple pay web domains page on Stripe `_, or log into your Stripe dashboard and go to :menuselection:`Settings --> Payments methods --> Apple Pay --> Configure --> Web domains`. Then, click :guilabel:`Add new domain` and insert the web domain of your Odoo database into the pop-up form. Odoo already hosts the verification file of Stripe. Click :guilabel:`Add` to register your web domain with Apple." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:203 +#: ../../content/applications/finance/payment_providers/stripe.rst:206 msgid "This operation must be repeated whenever your web domain changes." msgstr "" @@ -23843,31 +24436,31 @@ msgstr "" msgid "Spreadsheet" msgstr "" -#: ../../content/applications/finance/spreadsheet.rst:13 +#: ../../content/applications/finance/spreadsheet.rst:14 msgid "Spreadsheet lets you organize, analyze, and visualize your data in tabular form. Among others, you can:" msgstr "" -#: ../../content/applications/finance/spreadsheet.rst:16 +#: ../../content/applications/finance/spreadsheet.rst:17 msgid ":doc:`Insert and link your Odoo data (pivots, graphs, lists, and menus) `." msgstr "" -#: ../../content/applications/finance/spreadsheet.rst:17 -msgid "Use default templates or create your own." -msgstr "" - #: ../../content/applications/finance/spreadsheet.rst:18 -msgid "Format your data." +msgid ":doc:`Use default templates or create new ones `." msgstr "" #: ../../content/applications/finance/spreadsheet.rst:19 -msgid "Use formulas and functions." +msgid "Format data." msgstr "" #: ../../content/applications/finance/spreadsheet.rst:20 -msgid "Sort and filter your data." +msgid "Use formulas and functions." msgstr "" -#: ../../content/applications/finance/spreadsheet.rst:27 +#: ../../content/applications/finance/spreadsheet.rst:21 +msgid "Sort and filter data." +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:28 msgid "Some of Spreadsheet's main :abbr:`UI (user interface)` elements are highlighted and defined below." msgstr "" @@ -23875,40 +24468,40 @@ msgstr "" msgid "Spreadsheet main UI elements" msgstr "" -#: ../../content/applications/finance/spreadsheet.rst:33 +#: ../../content/applications/finance/spreadsheet.rst:34 msgid "Menu bar" msgstr "" -#: ../../content/applications/finance/spreadsheet.rst:34 +#: ../../content/applications/finance/spreadsheet.rst:35 msgid "Top bar" msgstr "" -#: ../../content/applications/finance/spreadsheet.rst:35 +#: ../../content/applications/finance/spreadsheet.rst:36 msgid "Formula bar" msgstr "" -#: ../../content/applications/finance/spreadsheet.rst:36 +#: ../../content/applications/finance/spreadsheet.rst:37 msgid "Filters button" msgstr "" -#: ../../content/applications/finance/spreadsheet.rst:37 +#: ../../content/applications/finance/spreadsheet.rst:38 msgid "Row header" msgstr "" -#: ../../content/applications/finance/spreadsheet.rst:38 +#: ../../content/applications/finance/spreadsheet.rst:39 msgid "Column header" msgstr "" -#: ../../content/applications/finance/spreadsheet.rst:39 +#: ../../content/applications/finance/spreadsheet.rst:40 msgid "Cell menu" msgstr "" -#: ../../content/applications/finance/spreadsheet.rst:40 +#: ../../content/applications/finance/spreadsheet.rst:41 msgid "Bottom bar" msgstr "" #: ../../content/applications/finance/spreadsheet/insert.rst:3 -msgid "Linking Odoo data" +msgid "Link Odoo data" msgstr "" #: ../../content/applications/finance/spreadsheet/insert.rst:5 @@ -23986,3 +24579,171 @@ msgstr "" #: ../../content/applications/finance/spreadsheet/insert.rst:57 msgid "To change which records are :ref:`used by the pivot `, right-click on a pivot cell, select :guilabel:`See pivot properties`, and click :guilabel:`Edit domain`." msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:3 +msgid "Templates" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:5 +msgid "Spreadsheet templates allow you to quickly create spreadsheets without starting from scratch." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:7 +msgid "Several pre-built templates are available when creating a new spreadsheet from the **Documents** app, such as:" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:10 +msgid ":ref:`budget reports `," +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:11 +msgid ":ref:`pipeline revenue reports `, or" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:12 +msgid ":ref:`sales commission report `." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:-1 +msgid "View of all the default templates" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:17 +msgid "You can also :ref:`save any spreadsheet as a template ` and :ref:`manage and edit existing templates `." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:21 +msgid "Default templates" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:26 +msgid "Accounting: budget reports" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:28 +msgid "Budget reports compare a company's actual spending with its budget over a defined period. Two templates are available: one uses quarterly intervals (:guilabel:`Budget Report (Quarterly)`), while the other uses monthly intervals (:guilabel:`Budget Report (Monthly)`)." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:-1 +msgid "Extract of a budget report" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:35 +msgid "The cells under the :guilabel:`Actuals` column are automatically filled in with the amount of money made and spent over the corresponding period (month or quarter). The data is taken from posted journal items under :ref:`income and expense accounts `." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:40 +msgid "Journal items under the :guilabel:`Other Income` account type are not considered when collecting data." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:43 +msgid "To analyze your budget's performance, fill the cells under the :guilabel:`Budget` column with how much money you expect to make (:guilabel:`Income` rows) and spend (:guilabel:`Expenses` rows) over the related period and per account. Then, the performance (:guilabel:`Perf.`) column compares :guilabel:`Actuals` data to their corresponding budget, expressed as a percentage." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:48 +msgid "Lastly, the :guilabel:`Net Profit` row represents the total :guilabel:`Income` minus the total :guilabel:`Expenses` for the :guilabel:`Actuals` and :guilabel:`Budget` columns." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:54 +msgid "CRM: pipeline revenue reports" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:56 +msgid "Two pipeline revenue reports are available. The :guilabel:`Pipeline Revenue Report (Monthly)` is dedicated to one-time revenue (:abbr:`NRR (non-recurring revenue)`), while the :guilabel:`MRR/NRR Pipeline Revenue Report (Monthly)` covers recurring and non-recurring revenue (:abbr:`MRR (monthly recurring revenue)`)." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:62 +msgid "Enable :guilabel:`Recurring Revenues` by going to :menuselection:`CRM --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:-1 +msgid "Extract of a pipeline revenue report" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:68 +msgid "The cells under the :guilabel:`Actuals` column are automatically filled in with the amount of monthly revenue from **won** opportunities." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:71 +msgid "To compute the revenue performance, fill in the monthly revenue targets." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:73 +msgid "For the :guilabel:`Revenue by Team` sheet, fill in the cells under the :guilabel:`Target` columns for each sales team." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:75 +msgid "For the :guilabel:`Revenue by Salesperson` sheet, open the :guilabel:`Targets` sheet and fill in the cells next to each salesperson. Use the :guilabel:`Monthly Factor` table below to adapt the main targets depending on the month of the year." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:79 +msgid "Then, the performance (:guilabel:`Perf.`) column compares :guilabel:`Actuals` data to their related budget, expressed as a percentage." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:82 +msgid "Lastly, the :guilabel:`Forecasted` column gathers the monthly revenue of leads multiplied by their :guilabel:`Probability` percentage." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:86 +msgid "For actuals and forecasts:" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:88 +msgid "The :guilabel:`Expected Closing` date found on leads is used to assign them to a month." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:89 +msgid "The recurring monthly revenue is used even if the recurring plan's number of months is set to a different value than 1 month. For example, a yearly plan's revenue is divided by 12 months." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:95 +msgid "Sales: sales commission" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:97 +msgid "This report presents the monthly commission earned or due to each salesperson." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:-1 +msgid "Extract of a sales commission report" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:102 +msgid "The :guilabel:`Rate` column is pre-filled with the percentage rate from the :guilabel:`Rates` tab, which can be customized for each product category according to the company's policy. Adjusting the rate for a specific product category automatically updates the commission amount for that category." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:106 +msgid "The :guilabel:`Invoiced` column shows the total amount of untaxed invoices grouped by salesperson and month." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:109 +msgid "Lastly, the :guilabel:`Comm.` column is computed by multiplying the invoiced amount with the rate percentage." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:115 +msgid "Save a spreadsheet as a template" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:117 +msgid "Any spreadsheet can be saved as a template. From the menu bar, click :menuselection:`File --> Save as template`. Modify the default :guilabel:`Template Name` if necessary and click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:122 +msgid "Templates are available to all users on the database." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:127 +msgid "Manage and edit templates" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:129 +msgid "Manage templates by going to :menuselection:`Documents --> Configuration --> Spreadsheet Templates`. Remove the :guilabel:`My Templates` :ref:`filter ` to view all templates in the database." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:133 +msgid "To edit an existing template, click `✎ Edit` next to the desired template. Modifications are automatically saved." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:137 +msgid "Use the download button under the :guilabel:`Data` column to export a template in JSON format. The file can be imported into another database." +msgstr "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index d2f3c1e44..2ddd2268c 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: 2023-05-30 12:32+0000\n" +"POT-Creation-Date: 2023-07-03 09:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -2571,7 +2571,7 @@ msgid "Grouping records on the Sales Analysis report" msgstr "" #: ../../content/applications/general/search.rst:95 -msgid "You can also **custom groups** by using a wide selection of fields present on the model. To do so, click :menuselection:`Group By --> Add Custom Group`, select a field, and click :guilabel:`Apply`." +msgid "You can **customize groups** by using a wide selection of fields present on the model. To do so, click :menuselection:`Group By --> Add Custom Group`, select a field, and click :guilabel:`Apply`." msgstr "" #: ../../content/applications/general/search.rst:99 diff --git a/locale/sources/hr.pot b/locale/sources/hr.pot index af8d747c1..f818438cf 100644 --- a/locale/sources/hr.pot +++ b/locale/sources/hr.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 16.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-05-15 06:38+0000\n" +"POT-Creation-Date: 2023-07-03 09:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -100,3 +100,300 @@ msgstr "" #: ../../content/applications/hr/attendances/hardware.rst:51 msgid "We recommend using the `Honeywell product line `_. If the barcode scanner is connected directly to a computer, it must be configured to use the computer's keyboard layout." msgstr "" + +#: ../../content/applications/hr/employees.rst:7 +msgid "Employees" +msgstr "" + +#: ../../content/applications/hr/employees.rst:9 +msgid "Odoo *Employees* organizes a company's employee records, contracts, and departments." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:3 +msgid "Add a new employee" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:5 +msgid "When a new employee is hired, the first step is to create a new employee form. Starting in the :menuselection:`Employees` app default view, click the :guilabel:`Create` button to access a new employee form. Fill out the required information (underlined in bold) and any additional details, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Create a new employee card." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:15 +msgid "The current company phone number and name is populated in the :guilabel:`Work Phone` and :guilabel:`Company` fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:19 +msgid "General information" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:22 +msgid "Required fields" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:24 +msgid ":guilabel:`Name`: Enter the employee's name." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:25 +msgid ":guilabel:`Company`: Select the company from the drop-down menu that the new employee is hired by, or create a new company by typing the name in the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:27 +msgid ":guilabel:`Working Hours`: In the :guilabel:`Work Information` tab, select the desired :guilabel:`Working Hours` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Working Hours are located in the Work Information tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:35 +msgid ":guilabel:`Working Hours` are related to a company's working times, and an employee cannot have working hours that are outside of a company's working times." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:38 +msgid "Each individual working time is company-specific, so for multi-company databases, each company needs to have its own working hours set." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:41 +msgid "If an employee's working hours are not configured as a working time for the company, new working times can be added, or existing working times can be modified. To add or modify a working time, go to the :menuselection:`Payroll app --> Configuration --> Working Times`, and add a new working time or edit an existing one." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:46 +msgid "After the new working time is created, set the working hours for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:49 +msgid "Optional fields" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:51 +msgid ":guilabel:`Photo`: In the top right image box of the employee card, click on the :guilabel:`✏️ (pencil)` edit icon to select a photo to upload." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:53 +msgid ":guilabel:`Job Position`: Enter the employee's job position title." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:54 +msgid "Tags: Click on a tag in the drop-down menu to add any tags applicable to the employee. Any tag can be created in this field by typing it in. Once created, the new tag is available for all employee cards. There is no limit to the amount of tags that can be added." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:57 +msgid "Work Contact Information: Enter the employees :guilabel:`Work Mobile`, :guilabel:`Work Phone`, :guilabel:`Work Email`, and/or :guilabel:`Company` name." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:59 +msgid ":guilabel:`Department`: Select the employee's department from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:60 +msgid ":guilabel:`Manager`: Select the employee's manager from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:61 +msgid ":guilabel:`Coach`: Select the employee's coach from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:64 +msgid "After a :guilabel:`Manager` is selected, if the :guilabel:`Coach` field is blank, the selected manager automatically populates the :guilabel:`Coach` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:68 +msgid "To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, :guilabel:`Coach`, or :guilabel:`Company`, click the :guilabel:`External Link` button next to the respective selection. The :guilabel:`External Link` button opens the selected form, allowing for modifications. Click :guilabel:`Save` after any edits are made." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:74 +msgid "Additional information tabs" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:77 +msgid "Resumé tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:80 +msgid "Resumé" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:82 +msgid "Next, the employee's work history is entered in the :guilabel:`Resumé` tab. Each previous experience must be entered individually. Click :guilabel:`Create a New Entry`, and the :guilabel:`Create Resumé lines` form appears. Enter the following information, then click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and create another line." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Add information for the previous work experience in this form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:92 +msgid ":guilabel:`Name`: Type in the name of the previous work experience." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:93 +msgid ":guilabel:`Type`: From the drop-down menu, select either :guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Internal Certification`, :guilabel:`Internal Training`, or type in a new entry." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:96 +msgid ":guilabel:`Display Type`: Select either :guilabel:`Classic`, :guilabel:`Certification`, or :guilabel:`Course` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:98 +msgid ":guilabel:`Date Start` and :guilabel:`Date End`: Enter the start and end dates for the work experience. To select a date, use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons to scroll to the desired month, then click on the day to select it." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:101 +msgid ":guilabel:`Description`: Enter any relevant details in the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:104 +msgid "Skills" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:106 +msgid "An employee's skills can be entered in the :guilabel:`Resumé` tab in the same manner a resumé line is created. Click the :guilabel:`Create a New Entry` button under :guilabel:`Skills` and a :guilabel:`Create Skills` form appears. Fill in the information, then click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and immediately create a new entry." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Create a new skill for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:116 +msgid ":guilabel:`Skill Type`: Select from the drop-down menu either :guilabel:`Languages`, :guilabel:`Dev`, :guilabel:`Music`, :guilabel:`Marketing`, or type in a new skill type. After entering the new skill type, an option to :guilabel:`Create` the skill or :guilabel:`Create and Edit` the skill appears. Click :guilabel:`Create and Edit`, and a pop-up for the specific skill type appears. This can also be accessed with the :guilabel:`External Link` button next to the new skill. This form allows for the creation of specific skills and levels. Click :guilabel:`Add a line` and enter the information for the new skill, then repeat for all other added skills. Repeat this process for the :guilabel:`Levels` section. Click :guilabel:`Add a line` to add each level and progress." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Add a new skill and levels." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:131 +msgid "To add a math skill set, enter `Math` in the :guilabel:`Name` field. In the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, and `Trigonometry`. And, in the :guilabel:`Levels` field enter `beginner`, `intermediate`, and `expert`. Then, either click :guilabel:`Save & Close` or :guilabel:`Save & New`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:136 +msgid ":guilabel:`Skill`: The corresponding skills associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. For example, selecting :guilabel:`Language` as the :guilabel:`Skill Type` presents a variety of languages to select from under the :guilabel:`Skills` field. Select the appropriate pre-configured skill, or type in a new one." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:140 +msgid ":guilabel:`Skill Level`: Pre-defined skill levels associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. Select a level or create a new skill level by typing it in." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:142 +msgid ":guilabel:`Progress`: Progress is automatically selected based on the selected :guilabel:`Skill Level`. Skill levels and progress can be modified in the :guilabel:`Skill Type` pop-up form, which is accessed via the :guilabel:`External Link` button next to :guilabel:`Skill Type` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:146 +msgid "To delete any line from the :guilabel:`Resumé` tab, click the :guilabel:`🗑️ (trash can)` delete icon to delete the entry. Add a new line by clicking the :guilabel:`ADD` button next to the corresponding section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:151 +msgid "Work information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:153 +msgid ":guilabel:`Location`: Select the :guilabel:`Work Address` from the drop-down menu. The :guilabel:`External Link` button opens up the selected company form in a window, and allows for editing. The :guilabel:`Work Location` is where any specific location details should be noted, such as a floor, or building." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:157 +msgid ":guilabel:`Approvers`: Using the drop-down menus, select the employees responsible for approving :guilabel:`Time Off`, :guilabel:`Expenses`, and :guilabel:`Timesheets` for the employee. The :guilabel:`External Link` button opens a form with the approver's :guilabel:`Name`, :guilabel:`Email Address`, :guilabel:`Company`, :guilabel:`Phone`, and :guilabel:`Mobile` fields. These can be modified, if needed. Click :guilabel:`Save` after making any edits." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:162 +msgid ":guilabel:`Schedule`: Select the :guilabel:`Working Hours` (required) and :guilabel:`Timezone` for the employee. The :guilabel:`External Link` button opens up a detailed view of the specific daily working hours. Working hours can be created, modified, or deleted here. Global time off (such as holidays) can be entered in the :guilabel:`Global Time Off` tab. Click :guilabel:`Add a line` to add a new global time off." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:167 +msgid ":guilabel:`Planning`: Click on a planning role from the drop-down menu for both the :guilabel:`Default Planning Role` and the :guilabel:`Planning Roles` fields to add a role. There is no limit to the amount of :guilabel:`Planning Roles` that can be selected for an employee, but there can only be one :guilabel:`Default Planning Role`. The default is the *typical* role that the employee performs, where the :guilabel:`Planning Roles` are *all* the specific roles the employee is able to perform." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Add the work information to the Work Information tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:179 +msgid "Private information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:181 +msgid "No information in the :guilabel:`Private Information` tab is required, however, some information in this section may be critical for the company's payroll department. In order to properly process payslips and ensure all deductions are accounted for, the employee's personal information should be entered." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:186 +msgid "Here, the employee's :guilabel:`Private Contact`, :guilabel:`Marital Status`, :guilabel:`Emergency Contact`, :guilabel:`Education`, :guilabel:`Citizenship`, :guilabel:`Dependant`, and :guilabel:`Work Permit` information is entered. Fields are entered either using a drop-down menu, clicking a check box, or typing in the information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:191 +msgid ":guilabel:`Private Contact`: Enter the :guilabel:`Address` for the employee. The selection can be made with the drop-down menu. If the information is not available, type in the name for the new address. To edit the new address, click the :guilabel:`External Link` button to open the address form. On the address form, enter the necessary details, then click :guilabel:`Save`. Some other information in the :guilabel:`Private Contact` section may auto-populate, if the address is already listed in the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:197 +msgid ":guilabel:`Marital Status`: Select either :guilabel:`Single`, :guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, or :guilabel:`Divorced` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:200 +msgid ":guilabel:`Emergency Contact`: Type in the name and phone number of the employee's emergency contact." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:202 +msgid ":guilabel:`Education`: Select the highest level of education completed by the employee from the :guilabel:`Certificate Level` drop-down menu. Options include :guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, :guilabel:`Doctor`, or :guilabel:`Other`. Type in the :guilabel:`Field of Study`, and the name of the :guilabel:`School` in the respective fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:206 +msgid ":guilabel:`Citizenship`: This section houses all the information relevant to the citizenship of the employee. Some selections use a drop-down menu, as does the :guilabel:`Nationality (Country)`, :guilabel:`Gender`, and :guilabel:`Country of Birth` sections. The :guilabel:`Date of Birth` uses a calendar module to select the date. First, click on the name of the month, then the year, to access the year ranges. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons, navigate to the correct year range, and click on the year. Next, click on the month. Last, click on the day to select the date. Type in the information for the :guilabel:`Identification No`, :guilabel:`Passport No`, and :guilabel:`Place of Birth` fields. If the employee is :guilabel:`Disabled` or a :guilabel:`Nonresident`, click the check box next to the respective fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:216 +msgid ":guilabel:`Dependant`: If the employee has any dependants, that information is entered here. Type in the number of children the employee has, and check the boxes next to :guilabel:`Disabled Children` and/or :guilabel:`Other Dependent People` if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:219 +msgid ":guilabel:`Work Permit`: If the employee has a work permit, enter the information in this section. Type in the :guilabel:`Visa No` and/or :guilabel:`Work Permit No` in the corresponding fields. Using the calendar module, select the :guilabel:`Visa Expire Date` to enter the expiration date." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Add the private information to the Private Information tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:228 +msgid "HR settings tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:230 +msgid "This tab provides various fields for different information, depending on the country the company is located. Different fields are configured for different locations, however some sections appear regardless." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:234 +msgid ":guilabel:`Status`: If applicable, select a :guilabel:`Related User`, :guilabel:`Job Position`, and :guilabel:`Language` with the drop-down menus. Type in the :guilabel:`Registration Number of the Employee`, and the :guilabel:`NIF Country Code` if available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:237 +msgid ":guilabel:`Fleet`: If the employee has access to a company car, enter the :guilabel:`Mobility Card` information here." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:239 +msgid ":guilabel:`Timesheets`: Enter the employee's cost per hour in a $XX.XX format. This is factored in when the employee is working at a work center. This value affects the employee's pay, and may also affect manufacturing costs for a product, if the value of the manufactured product is not a fixed amount." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:243 +msgid ":guilabel:`Attendance`: This section may only appear for Belgian companies. Enter the :guilabel:`INSZ or BIS` number if applicable. :guilabel:`Badge ID` and a :guilabel:`PIN Code` can be entered here, if the employee needs/has one. Click :guilabel:`Generate` next to the :guilabel:`Badge ID` to create a badge ID." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Enter any information prompted in the HR Settings tab for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:253 +msgid "Personal documents tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:255 +msgid "The :guilabel:`Personal Documents` tab is only displayed for certain countries. If this tab is not visible, it is not applicable to the company's location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:258 +msgid "Add a file for the employee's :guilabel:`ID Card Copy`, :guilabel:`Driving License`, :guilabel:`Mobile Subscription Invoice`, :guilabel:`SIM Card Copy`, and :guilabel:`Internet Subscription Invoice` by clicking the :guilabel:`Upload Your File` button next to the corresponding field. File types that can be accepted are :file:`.jpg`, :file:`.png`, and :file:`.pdf`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Upload personal documents for the employee in the Personal Documents tab, either a jpg,\n" +"png, or pdf." +msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 1de84bbf2..cf0bb3bf3 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: 2023-06-15 11:45+0000\n" +"POT-Creation-Date: 2023-07-03 09:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -342,9 +342,8 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst:12 #: ../../content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst:14 -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:13 #: ../../content/applications/inventory_and_mrp/inventory/management/misc/wave_transfers.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:51 #: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:14 #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:9 #: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/delivery_three_steps.rst:18 @@ -637,65 +636,306 @@ msgid ":doc:`lots`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:3 -msgid "Expiration Dates" +msgid "Expiration dates" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:5 -msgid "In many companies, products have expiration dates and they should be managed based on those dates. In the food industry, for example, tracking and managing product stock based on expiration dates is mandatory to avoid selling expired products to customers." +msgid "In Odoo, *expiration dates* can be used to manage and track the lifecycles of perishable products, from purchase to sale. Using expiration dates reduces product loss due to unexpected expiry, and helps to avoid sending expired products to customers." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:9 -msgid "With Odoo, you can track and manage your products based on their expiration dates, even if they are already tracked by lots or serial numbers." +msgid "In Odoo, only products that are tracked using *lots* and *serial numbers* can be assigned expiration information. Once a lot or serial number has been assigned, an expiration date can be set. This is especially helpful for companies (such as food manufacturers) that consistently, or exclusively, buy and sell perishable products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:17 +msgid ":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:16 -msgid "Application configuration" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:19 +msgid ":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:18 -msgid "To use expiration date tracking, open the *Inventory* application and go to :menuselection:`Configuration --> Settings` and activate the *Lots & Serial Numbers* and *Expiration Dates* features." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:19 +msgid "Enable expiration dates" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:26 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:68 -#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:90 -msgid "Product configuration" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:21 +msgid "To enable the use of *expiration dates*, go to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Traceability` section. Then, click the checkbox to enable the :guilabel:`Lots & Serial Numbers` feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:28 -msgid "Now, you can define different dates in the *inventory tab* of the product form:" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:25 +msgid "Once that feature is activated, a new option will appear to enable :guilabel:`Expiration Dates`. Click that checkbox to enable the feature, and be sure to :guilabel:`Save` changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:30 -msgid "Product Use Time: the number of days before the goods start deteriorating, without being dangerous. This is used to calculate the Best before date on each lot/serial number received." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 +msgid "Enabled lots and serial numbers and expiration dates settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:32 -msgid "Product Life Time: the number of days before the goods may become dangerous and must not be consumed. This is used to calculate the Expiration date on each lot/serial number received." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:33 +msgid "Once the :guilabel:`Lots & Serial Numbers` feature is activated, additional features appear to :guilabel:`Display Lots & Serial Numbers on Delivery Slips`; to :guilabel:`Display Lots & Serial Numbers on Invoices`; and to :guilabel:`Display Expiration Dates on Delivery Slips`. Activating these features helps with end-to-end traceability, making it easier to manage product recalls, identify \"bad\" batches of products, and more." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:34 -msgid "Product Removal Time: shows the number of days before the goods should be removed from the stock. This is used to calculate the Removal date on each lot/serial number received." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:40 +msgid "Configure expiration dates on products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:36 -msgid "Product Alert Time: refers to the number of days before an alert should be raised on the lot/serial number. This is used to calculate the Alert date on each lot/serial number received. Once the Alert date is reached, an Activity is assigned on the relevant lot/serial number to the Responsible user defined on the Product." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:42 +msgid "Once the :guilabel:`Lots & Serial Numbers` and :guilabel:`Expiration Dates` features have been enabled in the settings of the *Inventory* app, expiration information can be configured on individual products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:45 -msgid "Expiration Date on Lots/Serial Numbers" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:46 +msgid "To do so, go to :menuselection:`Inventory app --> Products --> Products`, and select a product to edit. Selecting a product reveals the product form for that particular item. Once on the product form, click :guilabel:`Edit` in the upper-left corner to make changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:47 -msgid "When receiving a product into inventory, the dates will automatically be updated on the corresponding lot/serial number. These updates will be based on the receipt date of the product and the days set on the product form." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:51 +msgid "To be tracked using lots or serial numbers, or to configure expiration information, products *must* have their :guilabel:`Product Type` set as :guilabel:`Storable Product` under the :guilabel:`General Information` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:58 -msgid "Expiration Alerts" +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:55 +msgid "Then, click the :guilabel:`Inventory` tab, and scroll down to the :guilabel:`Traceability` section. From here, make sure that either :guilabel:`By Unique Serial Number` or :guilabel:`By Lots` is checked." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:60 -msgid "You can access expiration alerts from the *inventory* app. To do so, go to :menuselection:`Master Data --> Lots/Serial Numbers`. There, you can use the pre-existing filter to show all the lots/serial numbers that have exceeded their respective alert dates." +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:59 +msgid "Once it is, a new :guilabel:`Expiration Date` checkbox appears that must also be clicked. When both are enabled, a new :guilabel:`Dates` field appears to the right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:63 +msgid "If a product has stock on-hand prior to activating tracking by lots or serial numbers, an inventory adjustment might need to be performed in order to assign lot numbers to the existing stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:68 +msgid "For processing large quantities of products on receipts or deliveries, it is recommended to track using lots, so multiple products can be traced back to the same lot, if any issues arise." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 +msgid "Expiration dates configuration on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:75 +msgid "Under the :guilabel:`Dates` field, there are four categories of expiration information to configure for the product:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:78 +msgid ":guilabel:`Expiration Time`: the number of days after receiving products (either from a vendor or in stock after production) in which goods may become dangerous and should not be used or consumed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:80 +msgid ":guilabel:`Best Before Time`: the number of days before the expiration date in which the goods start deteriorating, **without** necessarily being dangerous yet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:82 +msgid ":guilabel:`Removal Time`: the number of days before the expiration date in which the goods should be removed from stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:84 +msgid ":guilabel:`Alert Time`: the number of days before the expiration date in which an alert should be raised on goods in a particular lot or containing a particular serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:88 +msgid "The values entered into these fields automatically compute the expiration date for goods entered into stock, whether purchased from a vendor or manufactured in-house." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:91 +msgid "Once all the expiration information has been configured, click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:94 +msgid "If the :guilabel:`Dates` field is not populated with any values for expiration information, dates (and lots) can be manually assigned upon receipts and deliveries in and out of the warehouse. Even when assigned, they can still be overwritten and changed manually if needed, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:99 +msgid "Set expiration dates on receipts with lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:101 +msgid "Generating expiration dates for **incoming** goods can be done directly from the purchase order. To create a purchase order, go to the :menuselection:`Purchase` app and click :guilabel:`Create` to create a new request for quotation (RFQ)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:105 +msgid "Then, fill out the information by adding a :guilabel:`Vendor`, and add products to the :guilabel:`Product` lines by clicking :guilabel:`Add a product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:108 +msgid "Choose the desired quantity to order by changing the number in the :guilabel:`Quantity` column, and click :guilabel:`Confirm Order`. This converts the :abbr:`RFQ (request for quotation)` into a purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:112 +msgid "Click the :guilabel:`Receipt` smart button at the top of the purchase order to be taken to the warehouse receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:116 +msgid "Clicking :guilabel:`Validate` before assigning a serial number to the ordered product quantities causes a :guilabel:`User Error` popup to appear. The popup requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` cannot be validated without an assigned lot or serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:0 +msgid "User error popup when validating an order with no lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:125 +msgid "From here, click the :guilabel:`Additional Options` menu (hamburger) icon located on the far-right of the product line. When clicked, a :guilabel:`Detailed Operations` pop-up will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:128 +msgid "In this pop-up, click :guilabel:`Add a line`, and assign a lot or serial number under the :guilabel:`Lot/Serial Number Name` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:131 +msgid "An expiration date automatically populates, based on the configuration on the product form (if previously configured)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:135 +msgid "If the :guilabel:`Dates` field on the product form has not been configured, this date can be manually entered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:138 +msgid "After the expiration date has been established, mark the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up. Finally, click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 +msgid "Detailed operations popup showing expiration dates for ordered products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:145 +msgid "A :guilabel:`Traceability` smart button will appear upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document; the :guilabel:`Product` being traced; the :guilabel:`Lot/Serial #`; and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:151 +msgid "Set expiration dates on manufactured products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:153 +msgid "Expiration dates can also be generated for products manufactured in-house. To assign expiration dates to manufactured products, a manufacturing order (MO) needs to be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:156 +msgid "To create a :abbr:`MO (manufacturing order)`, go to :menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`, and click :guilabel:`Create`. Choose a product to manufacture from the :guilabel:`Product` field drop-down menu, then select the :guilabel:`Quantity` to produce." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 +msgid "Manufacturing order for product with expiration date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:165 +msgid "To manufacture a product, there must be materials to consume in the lines in the :guilabel:`Product` column. This can be achieved either by creating a :guilabel:`Bill of Material` for the :guilabel:`Product`, or manually adding materials to consume by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:170 +msgid "Once ready, click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:172 +msgid "Next to :guilabel:`Lot/Serial Number`, either select an existing lot number from the drop-down menu, or click the green :guilabel:`+` sign to automatically assign a new lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:175 +msgid "Then, select a number of units for the :guilabel:`Quantity` field, and click :guilabel:`Mark as Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:178 +msgid "Click on the :guilabel:`External Link` icon in the assigned :guilabel:`Lot/Serial Number` field. A pop-up appears, revealing a detail form for that specific number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:181 +msgid "On that pop-up, under the :guilabel:`Dates` tab, all expiration information that was previously configured for the product is displayed. That same information is also available on the detail form for that specific product, or by going to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 +msgid "Dates tab with expiration information for specific lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:191 +msgid "Sell products with expiration dates" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:193 +msgid "Selling perishable products with expiration dates is done the same as any other type of product. The first step in selling perishable products is to create a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:196 +msgid "To do that, go to :menuselection:`Sales app --> Create` to create a new quotation, and fill out the information on the sales order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:199 +msgid "Add a :guilabel:`Customer`, click :guilabel:`Add a product` to add the desired products to the :guilabel:`Product` lines, and set a :guilabel:`Quantity` for the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:202 +msgid "Then, click the :guilabel:`Other Info` tab. Under the :guilabel:`Delivery` section, change the :guilabel:`Delivery Date` to a date after the expected date, and click the :guilabel:`green checkmark` icon to confirm the date. Finally, click :guilabel:`Confirm` to confirm the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:206 +msgid "Next, click the :guilabel:`Delivery` smart button at the top of the sales order to see the warehouse receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:209 +msgid "On the warehouse receipt form, click :guilabel:`Validate`, and then :guilabel:`Apply` in the accompanying pop-up window, to automatically process all :guilabel:`Done` quantities, and deliver the products to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:213 +msgid "If the products are delivered before the :guilabel:`Alert Date` set on the product form, then no alerts will be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:217 +msgid "To sell perishable products with expiration dates, the :guilabel:`Removal Strategy` for the :guilabel:`Location` the products are stored in must be set to :abbr:`FEFO (First Expiry, First Out)`. If there is not enough stock of perishable products in one lot, Odoo will automatically take the remaining quantity required from a second lot with the next-soonest expiration date. Removal strategies can also be set on :guilabel:`Product Categories`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:224 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:209 +msgid ":doc:`/applications/inventory_and_mrp/inventory/routes/strategies/removal`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:227 +msgid "View expiration dates for lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:229 +msgid "To view (and/or group) all products with expiration dates by lot number, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:232 +msgid "Once there, remove any default search filters from the :guilabel:`Search...` bar. Then, click :guilabel:`Group By`, choose :guilabel:`Add Custom Group`, and select the :guilabel:`Expiration Date` parameter from the drop-down menu. Finally, click :guilabel:`Apply` to apply the filter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:236 +msgid "Doing so breaks down all perishable products, their expiration dates, and the assigned lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 +msgid "Group by expiration dates on lots and serial numbers page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:243 +msgid "Expiration alerts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:245 +msgid "To see expiration alerts, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:247 +msgid "Then, click into a :guilabel:`Lot/Serial Number` with perishable products. Doing so reveals the serial number detail form. On the serial number detail form, click the :guilabel:`Dates` tab to see all expiration information related to the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:251 +msgid "To edit the form, click :guilabel:`Edit` in the upper-left corner of the form, then change the :guilabel:`Expiration Date` to today's date (or earlier), and click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:255 +msgid "After saving, the lot number form displays a red :guilabel:`Expiration Alert` at the top of the form to indicate that the products in this lot are either expired or expiring soon. From here, click back to the :guilabel:`Lots/Serial Numbers` page (via the breadcrumbs)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:259 +msgid "To see the new expiration alert, or any expiration alerts for products that are expired (or will expire soon), remove all of the search filters from the :guilabel:`Search...` bar on the :guilabel:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:263 +msgid "Then, click :guilabel:`Filters`, and choose :guilabel:`Expiration Alerts`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates.rst:-1 +msgid "Expiration alert for product past the expiration date." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:3 @@ -714,10 +954,6 @@ msgstr "" msgid "Lots are useful for products that are manufactured or received in large quantities (such as clothes or food), and can be used to trace a product back to a group. This is especially useful when managing product recalls or expiration dates." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:19 -msgid ":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers`" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:22 #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:20 msgid "Enable lots & serial numbers" @@ -920,10 +1156,6 @@ msgstr "" msgid "The lot automatically chosen for delivery orders varies, depending on the selected removal strategy (:abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expiry, First Out)`). It will also depend on the quantity ordered, and if there is enough quantity in one lot to fulfill the order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:209 -msgid ":doc:`/applications/inventory_and_mrp/inventory/routes/strategies/removal`" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:211 msgid "Then, click :guilabel:`Add a line`, select an additional (different) :guilabel:`Lot/Serial Number`, apply the rest of the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up. Lastly, click the :guilabel:`Validate` button to deliver the products." msgstr "" @@ -1021,10 +1253,6 @@ msgstr "" msgid "The goal of assigning serial numbers to individual products is to make sure that 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 to products that they sell and deliver." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:17 -msgid ":doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots`" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst:22 msgid "To track products using serial numbers, the :guilabel:`Lots & Serial Numbers` feature must be enabled. To enable this, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Remember to click the :guilabel:`Save` button to save changes." msgstr "" @@ -1936,141 +2164,253 @@ msgid "Products" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:3 -msgid "Select a replenishment strategy" +msgid "Selecting a replenishment strategy" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:5 -msgid "In Odoo, there are two strategies for 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 purchase or manufacturing order. The choice of which strategy to use depends on the business's manufacturing and delivery processes." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/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/management/products/strategies.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:16 #: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:6 msgid "Terminology" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:14 -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:19 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:54 msgid "Replenishment report and reordering rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/management/products/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/management/products/strategies.rst:18 -msgid "Reordering rules are used to ensure that 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/management/products/strategies.rst:23 -msgid "Reordering rules can be created and managed in the replenishment report or from the product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:26 -msgid "Make to Order" +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/management/products/strategies.rst:28 -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*." +msgid "Reordering rules can be created and managed in the replenishment report, or from the product form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:31 -msgid "Unlike products replenished using reordering rules, Odoo automatically links the sales order to the purchase order (PO) or manufacturing order (MO) generated by the MTO route. Another difference between reordering rules and MTO is with MTO, Odoo generates a draft :abbr:`PO (Purchase Order)` or :abbr:`MO (Manufacturing Order)` immediately after the sales order is confirmed. With reordering rules, Odoo generates a draft :abbr:`PO (Purchase Order)` or :abbr:`MO (Manufacturing Order)` when the product's forecasted stock falls below the set minimum quantity. In addition, Odoo will automatically add quantities to the :abbr:`PO (Purchase Order)`/:abbr:`MO (Manufacturing Order)` as the forecast changes, as long as the :abbr:`PO (Purchase Order)`/:abbr:`MO (Manufacturing Order)` is not confirmed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:41 -msgid "The MTO route is the best replenishment strategy for products that are customized and should be used for this purpose only." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:50 -msgid "To access the replenishment report, go to :menuselection:`Inventory --> Operations --> Replenishment`. By default, the replenishment report shows every product that needs to be manually reordered. If there is no specific rule for a product, Odoo assumes that the :guilabel:`Minimum Quantity` and :guilabel:`Maximum Quantity` stock are both `0.00`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:-1 -msgid "The replenishment report shows products that need to be reordered manually." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:60 -msgid "For products that don't have a set reordering rule, Odoo calculates the forecast as sales orders, deliveries, and receipts are confirmed. For products that have a set reordering rule, Odoo calculates the forecast normally, but also takes into account the purchase/manufacturing lead time and security lead time." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:65 -msgid "Before creating a new reordering rule, make sure the product has a vendor or a bill of materials configured on the product form. Also, make sure the :guilabel:`Product Type` is set to `Storable Product` on the product form. By definition, a consumable product does not have its inventory levels tracked, so Odoo can not account for a consumable product in the stock valuation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:70 -msgid "To create a new reordering rule from the replenishment report, go to :menuselection:`Inventory --> Operations --> Replenishment`, click :guilabel:`Create`, and set the :guilabel:`Product`. If desired, set a :guilabel:`Min Quantity` and a :guilabel:`Max Quantity`. Finally, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:75 -msgid "To create a new reordering rule from the product form, go to :menuselection:`Inventory --> Products --> Products`, select a product to open its product form, click the :guilabel:`Reordering Rules` smart button, and click :guilabel:`Create`. Then, fill out the fields and save the new reordering rule." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:80 -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, changing the value, and clicking :guilabel:`Save`. To replenish a product manually, click :guilabel:`Order Once`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:85 -msgid "To automate replenishment, click :guilabel:`Automate Orders`. When this button is clicked, Odoo will automatically generate a draft :abbr:`PO (Purchase Order)`/:abbr:`MO (Manufacturing Order)` every time the forecasted stock level falls below the set :guilabel:`Min Quantity` of the reordering rule." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:91 -msgid "A reordering rule can be temporarily deactivated for a given period by using the :guilabel:`Snooze` button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:-1 -msgid "Snooze feature to temporarily deactivate reordering rules." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:98 -msgid "A :abbr:`PO (Purchase Order)` or :abbr:`MO (Manufacturing Order)` created by a manual replenishment will have `Replenishment Report` as the source document. A :abbr:`PO (Purchase Order)` or :abbr:`MO (Manufacturing Order)` created by an automated reordering rule will have the sales order(s) reference number(s) that triggered the rule as the source document." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:-1 -msgid "Look at the source panel showing where RFQ/MFG orders originated from." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:108 msgid "Make to order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:110 -msgid "Since the Make to Order (MTO) route is only recommended for customized products, the route is hidden by default." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:33 +msgid "*Make to order (MTO)* is a procurement route that creates a draft purchase order (or manufacturing order) each time a sales order is confirmed, **regardless of the current stock level**." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:113 -msgid "To activate the Make to Order (MTO) route in Odoo:" +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:36 +msgid "Unlike products replenished using reordering rules, Odoo automatically links the sales order to the |PO| or |MO| generated by the |MTO| route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:115 -msgid "Go to :menuselection:`Inventory --> Configuration --> Settings --> Warehouse`." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:39 +msgid "Another difference between reordering rules and |MTO| is, with |MTO|, Odoo generates a draft |PO| or |MO| immediately after the |SO| is confirmed. With reordering rules, Odoo generates a draft |PO| or |MO| when the product's forecasted stock falls below the set minimum quantity." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:116 -msgid "Activate :guilabel:`Multi-Step Routes` setting and click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:43 +msgid "In addition, Odoo automatically adds quantities to the |PO| or |MO| as the forecast changes, so long as the |PO| or |MO| is not confirmed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:117 -msgid "Go to :menuselection:`Inventory --> Configuration --> Routes`." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:46 +msgid "The |MTO| route is the best replenishment strategy for products that are customized, and/or for products that have no stock kept on-hand." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:118 -msgid "Click on :menuselection:`Filters --> Archived` to show archived routes." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:56 +msgid "To access the replenishment report, go to :menuselection:`Inventory app --> Operations --> Replenishment.`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:119 -msgid "Select the checkbox next to :guilabel:`Replenish on Order (MTO)`, and click on :menuselection:`Action --> Unarchive`." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:59 +msgid "By default, the replenishment report dashboard shows every product that needs to be manually reordered. If there is no specific rule for a product, Odoo assumes the :guilabel:`Min Quantity` and :guilabel:`Max Quantity` stock are both `0.00`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:123 -msgid "Activating the :guilabel:`Multi-Step Routes` setting also activates :guilabel:`Storage Locations` setting. If these features aren't applicable to the warehouse, disable these settings after unarchiving the MTO route." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:64 +msgid "For products that don't have a set reordering rule, Odoo calculates the forecast based on confirmed sales orders, deliveries, and receipts. For products that have a set reordering rule, Odoo calculates the forecast normally, but also takes into account the purchase/manufacturing lead time and security lead time." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:127 -msgid "To set a product's procurement route to MTO, go to :menuselection:`Inventory --> Products --> Products`, click on a product to open the product form, and click :guilabel:`Edit`. Then, click on the :guilabel:`Inventory` tab and in the :guilabel:`Routes` options, select :guilabel:`Replenish on Order (MTO)`. For products purchased directly from a vendor, make sure the :guilabel:`Buy` route is selected in addition to the MTO route and a vendor is configured in the :guilabel:`Purchase` tab. For products manufactured in-house, make sure the :guilabel:`Manufacture` route is selected in addition to the MTO route and a bill of materials is configured for the product. Finally, click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:70 +msgid "Before creating a new reordering rule, make sure the product has a *vendor* or a *bill of materials* configured on the product form. To check this, go to :menuselection:`Inventory app --> Products --> Products`, and select the product to open its product form. The vendor, if configured, is listed in the :guilabel:`Purchase` tab, and the bill on materials, if configured, is found in the :guilabel:`Bill of Materials` smart button at the top of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:76 +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/management/products/strategies.rst:-1 -msgid "Enable the Replenish on Order (MTO) route on the product settings." +msgid "Replenishment report listing all items needing to be purchased to meet current needs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:85 +msgid "To create a new reordering rule from the replenishment report, go to :menuselection:`Inventory app --> Operations --> Replenishment`, click :guilabel:`Create`, and select the desired product from the drop-down menu in the :guilabel:`Product` column. If necessary, a :guilabel:`Min Quantity` and a :guilabel:`Max Quantity` can be configured in the corresponding columns on the :guilabel:`Replenishment` report page, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:91 +msgid "To create a new reordering rule from the product form, go to :menuselection:`Inventory app --> Products --> Products`, and select a product to open its product form. Click the :guilabel:`Reordering Rules` smart button, click :guilabel:`Create`, and fill out the fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:96 +msgid "Replenishment report fields" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:98 +msgid "The following fields are on the :guilabel:`Replenishment` report. If any of these fields are not visible, click the :guilabel:`⋮ (additional options)` icon on the far right side of the report, then click the checkbox next to a field to make it visible." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:102 +msgid ":guilabel:`Product`: the product that requires a replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:103 +msgid ":guilabel:`Location`: the specific location where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:104 +msgid ":guilabel:`Warehouse`: the warehouse where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:105 +msgid ":guilabel:`On Hand`: the amount of product currently available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:106 +msgid ":guilabel:`Forecast`: the amount of product available after all current orders (sales, manufacturing, purchase, etc.) are taken into account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:108 +msgid ":guilabel:`Preferred Route`: how the product is procured, either :guilabel:`Buy`, :guilabel:`Manufactured`, :guilabel:`Dropship`, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:110 +msgid ":guilabel:`Vendor`: the company from which the product is acquired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:111 +msgid ":guilabel:`Bill of Materials`: the bill of materials for the product (if one is configured)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:112 +msgid ":guilabel:`Trigger`: how the replenishment is created, either :guilabel:`Auto` (automatically, once the :guilabel:`On Hand` quantity goes below the :guilabel:`Min Quantity`) or :guilabel:`Manual` (only when the replenishment is requested)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:115 +msgid ":guilabel:`Procurement Group`: the reference number for how the product is being acquired, such as a sales order, purchase order, or manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:117 +msgid ":guilabel:`Min Quantity`: the minimum amount of product that should be available. When inventory levels goes below this number, the replenishment is triggered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:119 +msgid ":guilabel:`Max Quantity`: the amount of product that should be available after replenishing the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:121 +msgid ":guilabel:`Multiple Quantity`: if the product should be ordered in specific quantities, enter the number that should be ordered. For example, if the :guilabel:`Multiple Quantity` is set to `5`, and only 3 are needed, 5 products are replenished." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:124 +msgid ":guilabel:`To Order`: the amount of product that is currently needed, and will be ordered, if the :guilabel:`Order Once` or :guilabel:`Automate Orders` button is clicked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:126 +msgid ":guilabel:`UoM`: the unit of measure used to acquire the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:127 +msgid ":guilabel:`Company`: the company for which the product is acquired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:129 +msgid "By default, the quantity in the :guilabel:`To Order` field is the quantity required to reach the set :guilabel:`Max Quantity`. However, the :guilabel:`To Order` quantity can be adjusted by clicking on the field and, changing the value, and clicking :guilabel:`Save`. To replenish a product manually, click :guilabel:`Order Once`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:134 +msgid "To automate a replenishment from the :guilabel:`Replenishment` page, click :guilabel:`Automate Orders` on the right-side of the line, represented by a :guilabel:`🔄 (circular arrow)` icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:137 +msgid "When this button is clicked, Odoo will automatically generate a draft |PO|/|MO| every time the forecasted stock level falls below the set :guilabel:`Min Quantity` of the reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:140 +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/management/products/strategies.rst:-1 +msgid "Snooze options to turn off notifications for reordering for a period of time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:148 +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/management/products/strategies.rst:-1 +msgid "Quote request list shows which quotes are directly from the replenishment report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:157 +msgid "Make to order (MTO) route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:159 +msgid "Since the |MTO| route is recommended for customized products, the route is hidden by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:168 +msgid "To activate the |MTO| route in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:162 +msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:163 +msgid "Activate the :guilabel:`Multi-Step Routes` setting, located under the :guilabel:`Warehouse` section, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:165 +msgid "Then, go to :menuselection:`Inventory app --> Configuration --> Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:166 +msgid "Click on :menuselection:`Filters --> Archived` to show archived routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:167 +msgid "Select the checkbox next to :guilabel:`Replenish on Order (MTO)`, and click on :menuselection:`Action --> Unarchive`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:171 +msgid "Activating the :guilabel:`Multi-Step Routes` setting also activates :guilabel:`Storage Locations`. If these features aren't applicable to the warehouse, disable these settings after unarchiving the |MTO| route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:175 +msgid "To set a product's procurement route to |MTO|, go to :menuselection:`Inventory app --> Products --> Products`, click on the desired product to open its product form, and click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:178 +msgid "Then, click the :guilabel:`Inventory` tab, and in the :guilabel:`Routes` section of options, select :guilabel:`Replenish on Order (MTO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:181 +msgid "For products purchased directly from a vendor, make sure the :guilabel:`Buy` route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` route. Also, make sure a vendor is configured in the :guilabel:`Purchase` tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:185 +msgid "For products manufactured in-house, make sure the :guilabel:`Manufacture` route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` route. Also, make sure a bill of materials is configured for the product, which is accessible via the :guilabel:`Bill of Materials` smart button on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:190 +msgid "Finally, when all configurations are complete, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:193 +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/management/products/strategies.rst:-1 +msgid "Replenish on Order selected on the product form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/products/uom.rst:3 @@ -2482,129 +2822,161 @@ msgid "In Odoo, this process can be conducted manually— by warehouse employees msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:13 -msgid ":ref:`Inventory valuation configuration `" +msgid "Automatic inventory valuation" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:16 -msgid "Understand the basics of inventory valuation" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:18 -msgid "In order to understand how moving products in and out of stock affects the company's overall value, consider the following product and stock moves scenario below." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:15 +msgid "To use Odoo to automatically generate a trail of inventory valuation entries, first navigate to the :menuselection:`Product Categories` list by going to :menuselection:`Inventory app --> Configuration --> Product Categories` and select the desired product category. On the form, set the :guilabel:`Inventory Valuation` as :guilabel:`Automated` and the :guilabel:`Costing Method` to any of the three options." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:22 -msgid "Receive a product" +msgid ":ref:`Set up inventory valuation `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:24 -msgid "For example, consider an physical product, a simple *table*, which is categorized as `Office Furniture` in the product form's :guilabel:`Product Category` field." +msgid "In order to understand how moving products in and out of stock affects the company's overall value, consider the following product and stock moves scenario below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:27 -msgid "Navigate to the the product category itself by going to :menuselection:`Inventory app --> Configuration --> Product Categories`, and on the form, set the :guilabel:`Costing Method` as `First In First Out (FIFO)` and the :guilabel:`Inventory Valuation` field as `Automated`." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:28 +msgid "Receive a product" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:32 -msgid "Alternatively access the :guilabel:`Product Categories` dashboard by clicking on the :guilabel:`internal link` arrow on the individual product's form, by hovering over the :guilabel:`Product Category` field." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:30 +msgid "To track the value of incoming products, such as a simple *table*, configure the product category on the the product itself. To get there, navigate to :menuselection:`Inventory app --> Products --> Products` and click the desired product. On the product form, click the :guilabel:`➡️ (right arrow)` icon beside the :guilabel:`Product Category` field, which opens an internal link to edit the product category. Next, set the :guilabel:`Costing Method` as :guilabel:`First In First Out (FIFO)` and :guilabel:`Inventory Valuation` as :guilabel:`Automated`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:38 +msgid "Alternatively access the :guilabel:`Product Categories` dashboard by navigating to :menuselection:`Inventory app --> Configuration --> Product Categories` and select the desired product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:42 msgid "Next, assume 10 tables are purchased at a price of $10.00, each. The :abbr:`PO (Purchase Order)` for those tables will show the subtotal of the purchase as $100, plus any additional costs or taxes." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 -msgid "Purchase order with 10 tables products valued at $10 each." +msgid "Purchase order with 10 tables products valued at $10.00 each." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:43 -msgid "After selecting :guilabel:`Validate` on the :abbr:`PO (Purchase Order)`, use the :guilabel:`Valuation` smart button to view how the value of inventory was impacted." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 -msgid "Valuation smart button on a receipt." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:51 -msgid ":ref:`Developer mode ` must be turned on to see the *Valuation* smart button." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:49 +msgid "After selecting :guilabel:`Validate` on the :abbr:`PO (Purchase Order)`, the :guilabel:`Valuation` smart button is enabled. Clicking on this button displays a report showing how the inventory valuation for the table was affected by this purchase." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:54 -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 ":ref:`Developer mode ` **must** be turned on to see the :guilabel:`Valuation` smart button." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:58 -msgid "The :guilabel:`Stock Valuation` dashboard then displays valuation of all products in the shipment, along with their quantities and valuation. In the example of 10 tables being purchased, the :guilabel:`Total Value` column of the dashboard would display a calculated valuation of $100." +msgid "The :doc:`consignment ` feature allows ownership to items in stock. Thus, products owned by other companies are not accounted for in the host company's inventory valuation." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 -msgid "Stock valuation page depicting the products within a shipment." +msgid "See Valuation smart button on a receipt, with Developer mode enabled." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:66 -msgid "In Odoo, automatic inventory valuation records are also recorded in the *Accounting* app. To access these accounting entries, navigate to :menuselection:`Accounting --> Journal Entries`, and look for inventory valuation entries with the `STJ` prefix in the :guilabel:`Journal` and :guilabel:`Number` columns, respectively." +msgid "For a comprehensive dashboard that includes the inventory valuation of all product shipments, inventory adjustments, and warehouse operations, refer to the :ref:`stock valuation report `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 -msgid "Accounting entry for the inventory valuation of 10 tables." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:71 msgid "Deliver a product" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:78 -msgid "In the same logic, when a table is shipped to a customer and leaves the warehouse, the stock valuation decreases. The :guilabel:`Valuation` smart button on the :abbr:`DO (Delivery Order)`, likewise, displays the stock valuation record as it does on a :abbr:`PO (Purchase Order)`" +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:73 +msgid "In the same logic, when a table is shipped to a customer and leaves the warehouse, the stock valuation decreases. The :guilabel:`Valuation` smart button on the :abbr:`DO (Delivery Order)`, likewise, displays the stock valuation record as it does on a :abbr:`PO (Purchase Order)`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 msgid "Decreased stock valuation after a product is shipped." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:87 -msgid "The inventory valuation report" +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:84 +msgid "Inventory valuation report" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:89 -msgid "To view the current value of all products in the warehouse, go to :menuselection:`Inventory app --> Reporting --> Inventory Valuation`. The records in the table are organized by product, and selecting a product's drop-down menu displays detailed records with the :guilabel:`Date`, :guilabel:`Quantity`, and :guilabel:`Total Value` of the inventory." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:86 +msgid "To view the current value of all products in the warehouse, first turn on :ref:`Developer mode ` and navigate to :menuselection:`Inventory app --> Reporting --> Valuation`. The :guilabel:`Stock Valuation` dashboard displays detailed records of products with the :guilabel:`Date`, :guilabel:`Quantity`, :guilabel:`Unit Value`, and :guilabel:`Total Value` of the inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:93 +msgid ":ref:`Developer mode ` **must** be enabled to see the :guilabel:`Valuation` option under :guilabel:`Reporting`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 msgid "Inventory valuation report showing multiple products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:99 -msgid "The :guilabel:`Inventory At Date` button, located in the top-left corner of the :guilabel:`Stock Valuation` dashboard, shows the inventory valuation of products available during a prior specified date." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:100 +msgid "The :guilabel:`Valuation At Date` button, located in the top-left corner of the :guilabel:`Stock Valuation` page, reveals a pop-up window. In this pop-up, the inventory valuation of products available during a prior specified date can be seen and selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:104 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:105 +msgid "View a detailed record of a product's inventory value, stock move, and on-hand stock by selecting the teal :guilabel:`➡️ (right arrow)` button to the right of the :guilabel:`Reference` column value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:110 msgid "Update product unit price" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:112 msgid "For any company: lead times, supply chain failures, and other risk factors can contribute to invisible costs. Although Odoo attempts to accurately represent the stock value, *manual valuation* serves as an additional tool to update the unit price of products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:111 -msgid "Manual valuation is intended for products that can be purchased and received for a cost greater than 0, or have product categories set with :guilabel:`Costing Method` set as either `Average Cost (AVCO)` or `First In First Out (FIFO)`." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:117 +msgid "Manual valuation is intended for products that can be purchased and received for a cost greater than 0, or have product categories set with :guilabel:`Costing Method` set as either :guilabel:`Average Cost (AVCO)` or :guilabel:`First In First Out (FIFO)`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 msgid "Add manual valuation of stock value to a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:119 -msgid "Create manual valuation entries on the :guilabel:`Stock Valuation` dashboard by first navigating to :menuselection:`Inventory app --> Reporting --> Inventory Valuation`, and then click the little gray drop-down icon to the left of a product's name, to then reveal stock valuation line items below as well as a teal :guilabel:`+ (plus)` button on the right." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:125 +msgid "Create manual valuation entries on the :guilabel:`Stock Valuation` dashboard by first navigating to :menuselection:`Inventory app --> Reporting --> Valuation`. Next, to enable the *product revaluation* feature, select :menuselection:`Group by --> Product` to organize all the records by product. Click on the gray :guilabel:`▶️ (drop-down triangle)` icon to reveal stock valuation line items below, as well as a teal :guilabel:`➕ (plus)` button on the right." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:124 -msgid "Click the teal :guilabel:`+ (plus)` button to open up the :guilabel:`Product Revaluation` form, where updates to the calculation of inventory valuation can be made, by increasing or decreasing the unit price of each product." +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:131 +msgid "Click the teal :guilabel:`+ (plus)` button to open up the :guilabel:`Product Revaluation` form. Here, the inventory valuation for a product can be recalculated, by increasing or decreasing the unit price of each product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:136 +msgid "The :guilabel:`▶️ (drop-down triangle)` and :guilabel:`➕ (plus)` buttons are only visible after grouping entries by product." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:-1 msgid "Product revaluation form adding a value of $1.00 with the reason being inflation." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:144 +msgid "Inventory valuation journal entries" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:146 +msgid "In Odoo, automatic inventory valuation records are also recorded in the :menuselection:`Accounting app --> Accounting --> Journal Entries` dashboard. On this comprehensive list of accounting entries, inventory valuation records are identified by checking values in the :guilabel:`Journal` column, or looking for the :guilabel:`Reference` column value which matches the warehouse operation reference (e.g. `WH/IN/00014` for receipts)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:152 +msgid "Clicking on an inventory valuation journal entry opens a *double-entry accounting* record. These records are generated by Odoo to track the change of value in inventory valuation as products are moved in and out of the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:157 +msgid "To view the inventory valuation of 10 *tables*, costing $10.00 each, upon reception from the vendor, go to the :menuselection:`Journal Entries` page found in :menuselection:`Accounting app --> Accounting --> Journal Entries`. Here, click the journal line where the :guilabel:`Reference` column value matches the reference on the receipt, `WH/IN/00014`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:0 +msgid "Stock valuation page depicting the products within a shipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:166 +msgid "`Stock interim` is a holding account for money intended to pay vendors for the product. The `stock valuation` account stores the value of all on-hand stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:0 +msgid "Accounting entry for the inventory valuation of 10 tables." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation.rst:174 +msgid "`Odoo Tutorial: Inventory Valuation `_" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/management/shipments_deliveries.rst:6 msgid "Incoming shipments and delivery orders" msgstr "" @@ -5132,7 +5504,7 @@ msgid "In Odoo, there are a variety of different types of shipping labels that c msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:15 -msgid "In the :menuselection:`Inventory` module, go to :menuselection:`Configuration --> Delivery --> Shipping Methods.` Choose a delivery method and click :guilabel:`Edit`. For the following example, *FedEx International* will be used." +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/operation/label_type.rst:-1 @@ -5140,7 +5512,7 @@ msgid "Different shipping methods." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:23 -msgid "In the :guilabel:`Configuration` tab, under :guilabel:`Label Type`, choose one of the label types available. The availability will vary depending on the carrier. :guilabel:`Save` the changes." +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/operation/label_type.rst:-1 @@ -5271,6 +5643,11 @@ msgstr "" msgid "To check your information, go to the **Settings** application and click on **General Settings**. Click on the first link **Configure your company data**." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:90 +msgid "Product configuration" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:70 #: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:92 msgid "The shipper companies need the weight of your product, otherwise the price computation cannot be done." @@ -6440,26 +6817,6 @@ msgstr "" msgid "Applying components to multiple variants." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/quality_control.rst:3 -msgid "Quality Control" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/quality_control.rst:5 -msgid "Whether you want to control the quality of your production, or the production of your subcontractor, before registering the products into your stock, you can rely on Odoo's Quality module." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/quality_control.rst:10 -msgid "To control the quality of your production, you need to set a *Quality Control Point* on the Manufacturing Operation Type, as shown below. To create it, Go to :menuselection:`Quality --> Quality Control --> Control Points`, and click **Create**. If the check only applies to specific products, or product categories, you can specify these during the setup as well." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/quality_control.rst:19 -msgid "Regarding the reception of subcontracted products, instead of the Manufacturing Operation Type, you need to select the 'Receipts' Operation type. For the rest, the same principles apply." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/quality_control.rst:25 -msgid "By doing so, a quality check is automatically created each time a finished product is made and/or received. Note that several Quality Check *Types* can be chosen from the dropdown. Note also that several Quality Check Points can be set up for the same Operation Type." -msgstr "" - #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:3 msgid "Manage semi-finished products" msgstr "" @@ -6952,23 +7309,23 @@ msgstr "" msgid ":guilabel:`MTBF`, :guilabel:`MTTR`, and :guilabel:`Est. Next Failure` are all calculated automatically based on past failure data, if any exists." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:79 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:81 msgid "Integrate IoT devices" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:81 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:83 msgid "The :guilabel:`IoT Triggers` tab enables the integration of :abbr:`IoT (Internet of Things)` devices with a work center:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:84 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:86 msgid ":guilabel:`Device`: specifies the IoT device to be triggered" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:85 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:87 msgid ":guilabel:`Key`: the security key for the device" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:86 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:88 msgid ":guilabel:`Action`: the IoT device action triggered" msgstr "" @@ -6976,19 +7333,19 @@ msgstr "" msgid "The IoT Triggers tab of the work center form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:93 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:95 msgid "Use case: configure an alternative work center" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:95 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:97 msgid "When a work center is at capacity, it cannot accept any new work orders. Instead of waiting for the work center to become available, it is possible to specify an alternative work center where surplus work orders should be carried out." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:99 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:101 msgid "Begin by creating a new work center. Configure the :guilabel:`Equipment` tab so that it has all of the same equipment as the main work center. This will ensure that the same tasks can be carried out at both work centers. Navigate to the main work center and include the new work center in the :guilabel:`Alternative Workcenters` selection field." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:104 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:106 msgid "Now, create a new manufacturing order that uses the main work center for one of its operations. The main work center will automatically be selected for the operation in the :guilabel:`Work Orders` tab. After confirming the manufacturing order, click the :guilabel:`Plan` button that appears at the top left of the form." msgstr "" @@ -6996,7 +7353,7 @@ msgstr "" msgid "Click the plan button to automatically select an available work center." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:113 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:115 msgid "If the main work center is at capacity, the work center selected for the operation will be automatically changed to the alternative work center." msgstr "" @@ -7004,27 +7361,27 @@ msgstr "" msgid "The alternative work center is automatically selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:121 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:123 msgid "Monitor work center performance" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:123 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:125 msgid "Performance for an individual work center can be viewed by selecting :menuselection:`Configuration --> Work Centers`, and clicking on a work center. A variety of metrics showing work center performance can be viewed at the top right of the form:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:127 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:129 msgid ":guilabel:`OEE`: overall effective efficiency, the percentage of time that the work center has been fully productive" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:129 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:131 msgid ":guilabel:`Lost`: the amount of time lost due to work stoppages" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:130 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:132 msgid ":guilabel:`Load`: the amount of time it will take to complete the current workload" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:131 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:133 msgid ":guilabel:`Performance`: the real duration of work time, shown as a percentage of the expected duration" msgstr "" diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index 58af999b6..8e7e0547b 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: 2023-05-02 14:02+0000\n" +"POT-Creation-Date: 2023-07-03 09:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -779,124 +779,131 @@ msgid "Target an audience" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:5 -msgid "Delivering marketing campaigns to the *right* audience is paramount when trying to grow a business. The :guilabel:`Odoo Marketing Automation` application helps marketers to do just that by providing filtering tools, that can be as simple or as complex as necessary, to reach the right customers at the right time." +msgid "Delivering marketing campaigns to the right audience is paramount when trying to grow a business. The Odoo *Marketing Automation* application helps marketers to do just that by providing detailed filtering tools, which can be as simple (or as complex) as necessary, to reach the right customers at the right time." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:11 -msgid "Work with target filters" +msgid "Configure target filters" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:13 -msgid "When configuring the filters on a marketing campaign, there are some options that have an arrow icon beside them. The arrow signifies that the filter has more refined parameters within it." +msgid "When configuring the target filters on a marketing campaign, there are some options that have an :guilabel:`> (arrow)` icon beside them. The :guilabel:`> (arrow)` icon signifies that the particular filter has more refined parameters within it that can be customized." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:-1 msgid "The drop-down filter menu in the Marketing Automation application." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:20 -msgid "Filters can be extended by adding *branches* and *nodes*. A *node* adds another filtering parameter to a group of targeting conditions (e.g. a new line), and a *branch* creates a narrowly refined cluster of parameters, allowing filters to be grouped with *Any* or *All* statements." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:24 -msgid "Every time a new branch is created, there are two options:" +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:21 +msgid "Filters can be extended by adding *branches* and *nodes*. A *node* adds another filtering parameter to a group of targeting conditions (e.g. a new line), and a *branch* creates a narrowly refined cluster of parameters, allowing filters to be grouped with :guilabel:`ANY` or :guilabel:`ALL` statements." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:26 -msgid "Either the records can match :guilabel:`ALL` criteria for the upcoming rules (an AND statement where all criteria must match)." +msgid "Every time a new branch is created, there are two options:" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:29 -msgid "Or, the records can match :guilabel:`ANY` criteria for the upcoming rules (an OR statement where only one of the criteria must match)." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:28 +msgid "Either the records can match :guilabel:`ALL` criteria for the upcoming rules (creating an AND statement where *all* criteria must match)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:32 -msgid "To change between these two options, simply click the drop-down arrow icon in the green box and select :guilabel:`Any` or :guilabel:`All`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:30 +msgid "Or, the records can match :guilabel:`ANY` criteria for the upcoming rules (creating an OR statement where *only one* of the criteria must match)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:35 -msgid "To add a node, click on the :guilabel:`+ (plus sign icon)` and to add another branch click on the :guilabel:`... (ellipses icon)`. To exclude a :guilabel:`node` (or a :guilabel:`branch`), click on :guilabel:`x (delete)`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:33 +msgid "To change between these two options, simply click the drop-down arrow icon in the green box and select :guilabel:`ANY` or :guilabel:`ALL`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:44 +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:36 +msgid "To add a node, click on the :guilabel:`➕ (plus sign)` icon, and to add another branch click on the :guilabel:`⋯ (ellipses)` icon. To exclude a node or a branch, click on :guilabel:`✖ (delete)` icon to delete it." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:45 msgid "Use cases" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:46 -msgid "The following scenarios below outline different combinations of filters a marketing campaign might commonly use." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:47 +msgid "The following scenarios outline different combinations of filters a marketing campaign might commonly use." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:50 -msgid "Scenario #1: Narrow the target down to new opportunities in the pipeline" +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:51 +msgid "Scenario #1: Narrow target down to new opportunities in the pipeline" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:52 -msgid "While in Edit mode on a campaign template form, select the :guilabel:`Target` field, and click :guilabel:`Search More` from the drop-down menu. Then, search for :guilabel:`Lead/Opportunity` and select it." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:53 +msgid "While in *Edit mode* on a campaign template form (by clicking the :guilabel:`Edit` button), select the :guilabel:`Target` field, and click :guilabel:`Search More` from the drop-down menu. Then, search for :guilabel:`Lead/Opportunity`, and select it." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:56 -msgid "Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on the default :guilabel:`ID` filter option in the first portion of the filter equation. Doing so reveals a drop-down menu full of filter options. From this drop-down, scroll down (or search for) :guilabel:`Type`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:57 +msgid "Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Then, click on the default :guilabel:`ID` filter option in the first portion of the filter equation. Doing so reveals a drop-down menu full of filter options. From this drop-down, scroll down (or search for) :guilabel:`Type`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:61 -msgid "Keep the second portion of the filter equation on the default :guilabel:`= (equal sign)`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:62 +msgid "Keep the second portion of the filter equation on the default :guilabel:`🟰 (equal sign)` icon." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:63 -msgid "Then, change the third (and final) portion of the filter equation from :guilabel:`Lead` to :guilabel:`Opportunity`. The number of :guilabel:`Records` that fit this specific filter equation will change as the equation is customized." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:64 +msgid "Next, change the third (and final) portion of the filter equation from :guilabel:`Lead` to :guilabel:`Opportunity`. The number of :guilabel:`Records` that fit this specific filter equation changes as the equation is customized." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:67 -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:103 -msgid "Add another node to this filter by clicking the :guilabel:`+ (plus sign)` to the right of the equation." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:68 +msgid "Add another node to this filter by clicking the :guilabel:`➕ (plus sign)` icon to the right of the equation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:70 -msgid "With \"new\" opportunities being the target of this filter, the second node will focus on only locating opportunities that are in the :guilabel:`New` stage of the pipeline. To do that, select the default :guilabel:`ID` from the first portion of the second filter equation, and scroll down (or search for) :guilabel:`Stage` from the field drop-down menu." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:71 +msgid "With \"new\" opportunities being the target of this filter, the second node will focus on *only* locating opportunities that are in the :guilabel:`New` stage of the pipeline. To do that, select the default :guilabel:`ID` from the first portion of the second filter equation, and scroll down (or search for) :guilabel:`Stage` from the field drop-down menu." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:75 -msgid "Once again, leave the second portion of the filter equation on :guilabel:`= (equal sign)`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:76 +msgid "Once again, leave the second portion of the filter equation on :guilabel:`🟰 (equal sign)` icon." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:77 -msgid "Lastly, highlight the default value in the third (and final) portion of the second filter equation and type in :guilabel:`New`. With that completed, Odoo will only target opportunities that are in the \"New\" stage of the pipeline." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:78 +msgid "Lastly, highlight the default value in the third (and final) portion of the second filter equation, and type in `New`. With that in place, Odoo only targets opportunities that are in the \"New\" stage of the pipeline." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:-1 msgid "A standard scenario using filters in the Odoo Marketing Automation app." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:86 -msgid "Scenario #2: Narrow the target down to the event attendees that purchased a specific ticket" +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:87 +msgid "Scenario #2: Narrow down target to event attendees who purchased a specific ticket" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:88 -msgid "While in Edit mode on a campaign template form, select the :guilabel:`Target` field, and click :guilabel:`Search More` from the drop-down menu. Then, scroll down (or search for) :guilabel:`Event` and select it." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:89 +msgid "While in *Edit mode* on a campaign template form (by clicking the :guilabel:`Edit` button), select the :guilabel:`Target` field, and click :guilabel:`Search More` from the drop-down menu. Then, scroll down (or search for) :guilabel:`Event`, and select it." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:92 +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:93 msgid "Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on the default :guilabel:`ID` filter option in the first portion of the filter equation. Doing so reveals a drop-down menu full of filter options. From this drop-down, scroll down (or search for) :guilabel:`Event`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:97 -msgid "Click the the default :guilabel:`= (equal sign)` in the second portion of the filter equation. This reveals a drop-down menu. On this menu, select :guilabel:`contains`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:98 +msgid "Click the default :guilabel:`🟰 (equal sign)` icon in the second portion of the filter equation. This reveals a drop-down menu. From this drop-down menu, select :guilabel:`contains`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:100 -msgid "In the third (and final) empty portion of the filter equation, type in the name of the event(s) that you would like Odoo to consider for this campaign filter." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:101 +msgid "In the third (and final) empty portion of the filter equation, type in the name of the event(s) that Odoo should consider for this campaign filter." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:106 -msgid "The second node will focus on targeting this campaign to attendees who purchase a specific type of ticket to the aforementioned event(s) in the first filter equation. To do that, select the default :guilabel:`ID` from the first portion of the second filter equation, and scroll down (or search for) :guilabel:`Event Ticket` from the field drop-down menu. Then, in that same drop-down menu, select :guilabel:`Name`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:104 +msgid "Then, add another node to this filter by clicking the :guilabel:`➕ (plus sign)` icon to the right of the equation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:112 -msgid "Once again, click the the default :guilabel:`= (equal sign)` in the second portion of the filter equation, and select :guilabel:`contains`." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:107 +msgid "The second node will focus on targeting this campaign to attendees who purchase a specific type of ticket to the aforementioned event(s) mentioned in the first filter equation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:115 -msgid "Lastly, in the third (and final) portion of the second filter equation, which will be blank, type in the name of the ticket type that should be used for the filter. In this case, :guilabel:`Standard` is the name of the event ticket type for this sample filter." +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:110 +msgid "To do that, select the default :guilabel:`ID` from the first portion of the second filter equation, and scroll down (or search for) :guilabel:`Event Ticket` from the field drop-down menu. Then, in that same drop-down menu, select :guilabel:`Name`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:114 +msgid "Once again, click the default :guilabel:`🟰 (equal sign)` icon in the second portion of the filter equation, and select :guilabel:`contains`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:117 +msgid "Lastly, in the third (and final) portion of the second filter equation, which is blank, type in the name of the ticket type that should be used for the filter. In this case, :guilabel:`Standard` is the name of the event ticket type for this sample filter." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:-1 @@ -904,7 +911,7 @@ msgid "An event ticket filter in the Odoo Marketing Automation application." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:3 -msgid "Testing and running a campaign" +msgid "Testing/running campaigns" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:5 @@ -912,39 +919,51 @@ msgid "Odoo gives users the ability to test marketing campaigns (and mailings) b msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:8 -msgid "First, open the :guilabel:`Marketing Automation` application and click on a campaign. Make sure the campaign already has activities configured on it (or build a campaign by following the directions here on :doc:`this documentation `). To start a test, click the :guilabel:`Launch a Test` button at the top of the template form." +msgid "First, open the :menuselection:`Marketing Automation` application, and select the desired campaign, which reveals that campaign's detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:11 +msgid "On the campaign detail form, make sure the campaign already has activities configured (or build a campaign by following the directions here on :doc:`this documentation `)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:15 +msgid "To start a test, click the :guilabel:`Launch a Test` button at the top of the campaign form." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 msgid "Launch a test button in Odoo Marketing Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:17 -msgid "When clicked, a pop-up window appears. In the dropdown field choose a specific record to run the test on, or create a brand new record by clicking the :guilabel:`Search More...` link at the bottom of the dropdown menu, and then click the :guilabel:`Create` button." +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:21 +msgid "When clicked, a :guilabel:`Launch a test` pop-up window appears. In the drop-down field, choose an existing record (or create a new one) to run the test on. To create a brand new record, click the :guilabel:`Search More...` link at the bottom of the drop-down menu, and then click the :guilabel:`Create` button." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:21 -msgid "Once the record is selected, click :guilabel:`Continue`, and Odoo will redirect to the campaign test page." +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:26 +msgid "Doing so reveals a blank contact form, in which the :guilabel:`Name` and :guilabel:`Email` **must** be entered. When all the necessary information has been entered, click :guilabel:`Save`, and Odoo returns to the :guilabel:`Launch a test` pop-up, with that new record in the :guilabel:`Choose an existing record or create a new one to test` field." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:31 +msgid "Once a record is selected, click :guilabel:`Continue`, and Odoo reveals the campaign test page." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 msgid "Test screen in Odoo Marketing Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:28 -msgid "Here, the name of the :guilabel:`Record` being tested is visible, along with the precise time this test workflow was started. Beneath that is the first activity (or activities) in the workflow." +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:37 +msgid "On the campaign test page, the name of the :guilabel:`Record` being tested is visible, along with the precise time this test workflow was started in the :guilabel:`Workflow Started On` field. Beneath that, in the :guilabel:`Workflow` section is the first activity (or activities) in the workflow that's being tested." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:31 -msgid "To start a test, click the :guilabel:`Run` icon beside the first activity in the workflow. When clicked, the page will reload, and Odoo will show the various results (and analytics) connected to that specific activity." +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:42 +msgid "To start a test, click the :guilabel:`Run` button, represented by a :guilabel:`▶️ (play button)` icon beside the first activity in the workflow. When clicked, the page reloads, and Odoo shows the various results (and analytics) connected to that specific activity as they occur, in real-time." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 msgid "Workflow test progress in Odoo Marketing Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:39 -msgid "Once all the workflow activities are completed, the test will end and be moved to the :guilabel:`Completed` stage. To stop a test before all the workflow activities are completed, click the :guilabel:`Stop` button." +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:50 +msgid "Once all the workflow activities are completed, the test will end, and move to the :guilabel:`Completed` stage. To stop a test before all the workflow activities are completed, click the :guilabel:`Stop` button in the upper-left corner of the campaign test page." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:3 @@ -952,115 +971,127 @@ msgid "Marketing activities" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:5 -msgid "When creating a campaign in the :guilabel:`Marketing Automation` app, users can plan marketing activities such as email or SMS campaigns. To get started, navigate to the :guilabel:`Workflow` area, and click :guilabel:`Add New Activity`. A blank activity template will appear where parameters can be set for that specific activity." +msgid "When creating a campaign in the *Marketing Automation* app, users can plan marketing activities, such as email or SMS campaigns." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:10 -msgid "When :guilabel:`Add New Activity` is selected, a blank activity template will appear with the following customizable fields:" +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:8 +msgid "To get started, navigate to the bottom of a marketing automation campaign detail form, and click :guilabel:`Add New Activity`. Doing so reveals a :guilabel:`Create Activities` pop-up window. This pop-up window is a blank activity template, where specific parameters can be set for that particular activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:13 +msgid "The following fields are available in the :guilabel:`Create Activities` pop-up window (when :guilabel:`Add New Activity` is clicked):" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:-1 msgid "An activity template in Odoo Marketing Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:17 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:20 msgid ":guilabel:`Activity Name`: the title of the activity." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:18 -msgid ":guilabel:`Activity Type`: choose between Email, Server Action (internal Odoo operation), or SMS." +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:21 +msgid ":guilabel:`Activity Type`: choose between `Email`, `Server Action` (internal Odoo operation), or `SMS`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:19 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:23 msgid ":guilabel:`Mail Template`: choose from pre-configured templates (or create a new one on-the-fly)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:20 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:24 msgid ":guilabel:`Trigger`: choose when this activity should be triggered." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:21 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:25 msgid ":guilabel:`Expiry Duration`: configure to stop the actions after a specific amount of time (after the scheduled date). When selected, a :guilabel:`Cancel after` field appears, in which the user can choose how many :guilabel:`Hours, Days, Weeks, or Months` they want the actions to cease after the initial date." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:25 -msgid ":guilabel:`Activity Filter`: domain related to this activity (and all subsequent Child Activities)." +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:29 +msgid ":guilabel:`Activity Filter`: domain related to this activity (and all subsequent child activities)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:27 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:31 msgid ":guilabel:`Applied Filter`: activity will *only* be performed if it satisfies the specified domain (filter)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:30 -msgid "After the activity's settings are fully configured, click :guilabel:`Save & Close` to finish creating the activity." -msgstr "" - #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:34 -msgid "Workflow activity" -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:36 -msgid "Once saved, the :guilabel:`Workflow Activity` will appear in Odoo, where each activity will be shown as a graph by default. The configured trigger time for that activity can be found to the left of the :guilabel:`Workflow Activity` card." +msgid "After the activity's settings are fully configured, click :guilabel:`Save & Close` to save the activity and return to the marketing automation campaign form, :guilabel:`Save & New` to save the activity and immediately create another one in a fresh :guilabel:`Create Activities` pop-up window, or :guilabel:`Discard` to delete the activity and return to the marketing automation campaign form." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:40 -msgid "In the :guilabel:`Workflow Activity` section, there is also the number of activities that are successful or rejected. The :guilabel:`Success` and :guilabel:`Rejected` numbers are color-coded in the graph for easy reference (in green and red, respectively)." +msgid "Workflow activity" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:42 +msgid "Once an activity is saved, the :guilabel:`Workflow Activity` section appears at the bottom of the marketing automation campaign form. Each activity is displayed as a line graph." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:45 +msgid "The configured :guilabel:`Trigger` time for that activity can be found to the left of the :guilabel:`Workflow Activity` card in the :guilabel:`Workflow` section." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:48 +msgid "Once the activity has been triggered, a figure representing the number of :guilabel:`Success` or :guilabel:`Rejected` activities will be displayed to the right of the graph." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:-1 msgid "Typical workflow activity in Odoo Marketing Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:49 -msgid "If the :guilabel:`Activity Type` of the activity is set to :guilabel:`Email`, there are more in-depth analytics beneath the :guilabel:`Workflow Activity` data detailing how many emails have been :guilabel:`Sent`, and what percentage of those have been :guilabel:`Clicked`, :guilabel:`Replied` to, or :guilabel:`Bounced`." +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:56 +msgid "If the :guilabel:`Activity Type` of the activity is set to :guilabel:`Email`, there are more in-depth analytics beneath the activity graph data, detailing how many emails have been :guilabel:`Sent`, and what percentage of those have been :guilabel:`Clicked`, :guilabel:`Replied` to, or :guilabel:`Bounced`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:55 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:62 msgid "Child activities" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:57 -msgid "Odoo also has the option to :guilabel:`Add Child Activity`. *Child Activities* are sub-activities that are connected to (and triggered by) the activity above it, which is also known as its *Parent Activity*." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:61 -msgid "Odoo provides a number of triggering options to launch a :guilabel:`Child Activity` - all of which depend on the trigger configurations related to the parent activity. Under the desired parent activity, hover over :guilabel:`Add child activity`, and select the trigger:" -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:65 -msgid ":guilabel:`Add Another Activity`: instantly add another activity." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:66 -msgid ":guilabel:`Opened`: the next activity will be triggered if the (email) recipient opens the mailing." +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:64 +msgid "There is also the option to add a *child activity* by clicking :guilabel:`Add child activity`, located at the bottom of each activity block in the :guilabel:`Workflow` section of a marketing automation form." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:68 -msgid ":guilabel:`Not Opened`: the next activity will be triggered if the recipient does not open the mailing." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:70 -msgid ":guilabel:`Replied`: the next activity will be triggered if the recipient replies to the mailing." +msgid "Child activities are sub-activities that are connected to (and triggered by) the activity above it, which is also known as its *parent activity*." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:71 -msgid ":guilabel:`Not Replied`: the next activity will be triggered if the recipient does not reply to the mailing." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:73 -msgid ":guilabel:`Clicked`: the next activity will be triggered if the recipient clicks on a link included in the mailing." +msgid "Odoo provides a number of triggering options to launch a child activity - all of which depend on the trigger configurations related to the parent activity. Under the desired parent activity, hover over :guilabel:`Add child activity`, and select any of the following triggers:" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:75 +msgid ":guilabel:`Add Another Activity`: instantly add another activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:76 +msgid ":guilabel:`Opened`: the next activity will be triggered if the (email) recipient opens the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:78 +msgid ":guilabel:`Not Opened`: the next activity will be triggered if the recipient does not open the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:80 +msgid ":guilabel:`Replied`: the next activity will be triggered if the recipient replies to the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:81 +msgid ":guilabel:`Not Replied`: the next activity will be triggered if the recipient does not reply to the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:83 +msgid ":guilabel:`Clicked`: the next activity will be triggered if the recipient clicks on a link included in the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:85 msgid ":guilabel:`Not Clicked`: the next activity will be triggered if the recipient does not click on a link included in the mailing." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:77 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:87 msgid ":guilabel:`Bounced`: the next activity will be triggered if the mailing is bounced (not sent)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:79 -msgid "Once a trigger is selected, the user can configure the child activity (it has the same configuration options as a regular activity) and click :guilabel:`Save & Close`` to finish creating the child activity." +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:89 +msgid "Once a trigger is selected, the user can configure the child activity (it has the same configuration options as a regular activity), and click :guilabel:`Save & Close` to finish creating the child activity, which will then be displayed in the :guilabel:`Workflow` section, in a slightly indented position beneath its parent activity." msgstr "" #: ../../content/applications/marketing/sms_marketing.rst:8 diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index 0328c3733..80e27a70a 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: 2023-06-02 08:43+0000\n" +"POT-Creation-Date: 2023-07-03 09:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -414,7 +414,7 @@ msgid "Create a Twilio account" msgstr "" #: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:13 -msgid "First, go to `Twilio `_ and click :guilabel:`Sign up` to create a new Twilio account. Next, enter your name and email address, create a password, and accept Twilio's terms of service. Then, click :guilabel:`Start your free trial`. Verify your email address with Twilio, as per their instructions." +msgid "First, go to `Twilio `_ and click :guilabel:`Sign up` to create a new Twilio account. Next, enter your name and email address, create a password, and accept Twilio's terms of service. Then, click :guilabel:`Start your free trial`. Verify your email address with Twilio, as per their instructions." msgstr "" #: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:18 @@ -848,111 +848,251 @@ msgid "Configuration" msgstr "" #: ../../content/applications/productivity/iot/config/connect.rst:3 -msgid "Connect an IoT Box to your database" +msgid "Connect an IoT box to Odoo" msgstr "" #: ../../content/applications/productivity/iot/config/connect.rst:5 -msgid "Install the Internet of Things (IoT) App on your Odoo Database." +msgid "An Internet of Things (IoT) box is a micro-computer device that allows for the connection of input and output devices to an Odoo database. An :abbr:`IoT (Internet of Things)` box subscription is required in order to use the :abbr:`IoT (Internet of Things)` box with a secured connection. A computer is also required to set up the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:10 -msgid "Go in the IoT App and click on Connect on the IoT Boxes page." +#: ../../content/applications/productivity/iot/config/connect.rst:11 +msgid "`IoT Box FAQ `_" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:15 -msgid "Follow the steps to connect your IoT Box." +#: ../../content/applications/productivity/iot/config/connect.rst:13 +msgid "Begin the :abbr:`IoT (Internet of Things)` configuration process by :ref:`installing the IoT app ` on the Odoo database through the :menuselection:`Apps` application." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:21 -msgid "Ethernet Connection" +#: ../../content/applications/productivity/iot/config/connect.rst:-1 +msgid "The Internet of Things (IoT) app on the Odoo database." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:23 -msgid "Connect to the IoT Box all the devices that have to be connected with cables (ethernet, usb devices, etc.)." +#: ../../content/applications/productivity/iot/config/connect.rst:20 +msgid "Next, after the *IoT app* is installed, navigate to :menuselection:`IoT app --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in the upper-left corner of the :menuselection:`IoT Boxes` dashboard." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:26 -msgid "Power on the IoT Box." +#: ../../content/applications/productivity/iot/config/connect.rst:-1 +msgid "Connecting an IoT box to the Odoo database." msgstr "" #: ../../content/applications/productivity/iot/config/connect.rst:28 -msgid "Read the Pairing Code from a screen or a receipt printer connected to the IoT Box." +msgid "There are two recommended ways to connect the :abbr:`IoT (Internet of Things)` box to the database once the *IoT app* is installed. Follow the steps in either of the next two sections to connect the :abbr:`IoT (Internet of Things)` box via :ref:`wired ethernet connection ` or via :ref:`WiFi `." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:32 -msgid "Input the Pairing Code and click on the Pair button." +#: ../../content/applications/productivity/iot/config/connect.rst:-1 +msgid "Connection steps for a wired connection or WiFi connection." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:35 -msgid "Recent changes in modern web browsers forced us to modify the connection wizard. If your screen is different from the screenshots, make sure that the ``iot_pairing`` module is installed." +#: ../../content/applications/productivity/iot/config/connect.rst:38 +msgid "The disk image that the :abbr:`IoT (Internet of Things)` box SD card is formatted with is unique to the version of the Odoo database that the :abbr:`IoT (Internet of Things)` box is running on. Ensure that the :abbr:`IoT (Internet of Things)` box is :doc:`flashed ` with the most up-to-date disk image." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:40 -msgid "WiFi Connection" -msgstr "" - -#: ../../content/applications/productivity/iot/config/connect.rst:42 -msgid "Power on the IoT Box" -msgstr "" - -#: ../../content/applications/productivity/iot/config/connect.rst:44 -msgid "Copy the token" +#: ../../content/applications/productivity/iot/config/connect.rst:46 +msgid "Ethernet connection" msgstr "" #: ../../content/applications/productivity/iot/config/connect.rst:48 -msgid "Connect to the IoT Box WiFi Network (make sure there is no ethernet cable plugged in your computer)." +msgid "The following is the process to connect the :abbr:`IoT (Internet of Things)` box via an ethernet cable to the Odoo database (by way of the ethernet port; RJ-45)." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:53 -msgid "You will be redirected to the IoT Box Homepage (if it doesn't work, connect to the IP address of the box). Give a name to your IoT Box (not required) and paste the token, then click on next." +#: ../../content/applications/productivity/iot/config/connect.rst:51 +msgid "First, connect all wired devices to the :abbr:`IoT (Internet of Things)` box (ethernet, :abbr:`USB (Universal Serial Bus)` devices, etc.). At minimum, an HDMI screen should be connected. Then, plug the :abbr:`IoT (Internet of Things)` box into a power source." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:60 -msgid "If you are on Runbot, do not forget to add the -all or -base in the token (e.g. this token **http://375228-saas-11-5-iot-f3f920.runbot16.odoo.com\\|4957098401** should become **http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)." +#: ../../content/applications/productivity/iot/config/connect.rst:55 +msgid "Immediately after the unit powers on and boots up, read the *pairing code* from the screen or from the printout of a receipt printer connected to the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:66 -msgid "Choose the WiFi network you want to connect with (enter the password if there is one) and click on Submit. Wait a few seconds before being redirected to your database." +#: ../../content/applications/productivity/iot/config/connect.rst:59 +msgid "By default, the :abbr:`IoT (Internet of Things)` box will display the *pairing code* for a maximum of 5 minutes after the unit boots up. After 5 minutes, the *pairing code* will disappear for security purposes and the :abbr:`IoT (Internet of Things)` box will need to be rebooted manually by unplugging the unit from the power source for ten seconds and re-plugging it back in." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:72 -msgid "You should now see the IoT Box." +#: ../../content/applications/productivity/iot/config/connect.rst:65 +msgid "If no screen is attached to the :abbr:`IoT (Internet of Things)` box, then the *pairing code* can be accessed from the :abbr:`IoT (Internet of Things)` box homepage by clicking on the :guilabel:`POS Display` button. For instructions on how to access the :abbr:`IoT (Internet of Things)` box homepage visit :ref:`iot_connect/token`." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:78 -msgid "IoT Box Schema" +#: ../../content/applications/productivity/iot/config/connect.rst:70 +msgid "On the computer, navigate to :menuselection:`IoT app --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in the upper-left corner of the the :menuselection:`IoT Boxes` dashboard. Input the *pairing code* in the :guilabel:`Pairing Code` field and click on the :guilabel:`Pair` button. The database will now link to the :abbr:`IoT (Internet of Things)` box and it will appear on the :menuselection:`IoT Boxes` page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:79 +msgid "WiFi connection" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:81 +msgid "The following is the process to connect the :abbr:`IoT (Internet of Things)` box via a WiFi connection to the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:84 +msgid "First, ensure there is no ethernet cable plugged into the :abbr:`IoT (Internet of Things)` box. Then, connect all wired devices to the :abbr:`IoT (Internet of Things)` box (:abbr:`USB (Universal Serial Bus)` devices, etc.)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:88 +msgid "After connecting the devices, plug the :abbr:`IoT (Internet of Things)` box into to a power source. On the computer, navigate to :menuselection:`IoT app --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in the upper-left corner of the the :menuselection:`IoT Boxes` dashboard. Then copy the :guilabel:`Token` from the :guilabel:`WiFi connection` section as this will later be used to link the Odoo database to the :abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:94 +msgid "Back on the computer, navigate to the available WiFi networks and connect to the :abbr:`IoT (Internet of Things)` box WiFi network. The WiFi network dispersed by the :abbr:`IoT (Internet of Things)` box will start with `IoTBox-xxxxxxxxxx`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:-1 +msgid "WiFi networks available on the computer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:102 +msgid "Upon connecting to the :abbr:`IoT (Internet of Things)` box WiFi, a browser will automatically redirect to the :menuselection:`Configure Iot Box` wizard. Name the :abbr:`IoT (Internet of Things)` box, then paste the previously copied *token* into the :guilabel:`Server Token` field, and then click on :guilabel:`Next`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:-1 +msgid "Enter the server token into the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:112 +msgid "If the :abbr:`IoT (Internet of Things)` box WiFi connection wizard doesn't start, then see the documentation on :ref:`connecting with a token `." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:115 +msgid "Now, choose the WiFi network that the :abbr:`IoT (Internet of Things)` box will connect with (enter the password if there is one) and click on :guilabel:`Connect`. Wait a few seconds and the browser will redirect to the :abbr:`IoT (Internet of Things)` box homepage. The computer may need to be manually re-connected back to the original WiFi connection, if this does not happen automatically." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:-1 +msgid "Configuring the WiFi for the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:124 +msgid "After completing each step, the :abbr:`IoT (Internet of Things)` box should appear when navigating to :menuselection:`IoT app --> IoT Boxes` on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:-1 +msgid "The IoT box has been successfully configured on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:132 +msgid "The :abbr:`IoT (Internet of Things)` box may need to be manually rebooted upon successfully connecting via WiFi for the box to appear in the *IoT app* on the Odoo database. To do so, simply unplug the device and plug it back into the power source after ten seconds." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:139 +msgid "Manually connecting the IoT box using the token" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:141 +msgid "A manual connection of the :abbr:`IoT (Internet of Things)` box to the :abbr:`IoT (Internet of Things)` app can be made using the *token*, from a computer. The *token* can be found by navigating to :menuselection:`IoT app --> IoT Boxes` and clicking on :guilabel:`Connect`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:145 +msgid "Under the :guilabel:`WiFi Connection` section of the :guilabel:`Connect an IoT Box` page that appears, click :guilabel:`Copy` to the right of the :guilabel:`Token`. This token will be entered into the :abbr:`IoT (Internet of Things)` box homepage." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:149 +msgid "Access the :abbr:`IoT (Internet of Things)` box homepage by entering the :abbr:`IP (Internet Protocol)` address of the :abbr:`IoT (Internet of Things)` box into a browser window from a computer on the same network as the :abbr:`IoT (Internet of Things)` box (preferably by ethernet connection)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:154 +msgid "The :abbr:`IP (Internet Protocol)` address can be accessed by the router admin console that the :abbr:`IoT (Internet of Things)` box is connected to, or by connecting a receipt printer to the :abbr:`IoT (Internet of Things)` box. A receipt will print out with the :abbr:`IoT (Internet of Things)` box's :abbr:`IP (Internet Protocol)` address on it." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:159 +msgid "On the :abbr:`IoT (Internet of Things)` box homepage, enter the *token* under the :guilabel:`Server` section by clicking on :guilabel:`Configure`. Then, paste the *token* into the :guilabel:`Server Token` field and click :guilabel:`Connect`. The :abbr:`IoT (Internet of Things)` box will then link to the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:167 +msgid "IoT box schema" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:170 +msgid "Raspberry Pi 4" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:174 +msgid "The Odoo IoT box (Raspberry Pi 4) schema with labels." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:177 +msgid "Raspberry Pi 3" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:181 +msgid "The Odoo IoT box (Raspberry Pi 3) schema with labels." msgstr "" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:3 -msgid "Flashing your SD Card" +msgid "Flashing the SD card" msgstr "" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:5 -msgid "In some case, you may need to reflash your IoT Box’s SD Card to benefit from our latest updates." +msgid "In some circumstances, the :abbr:`IoT (Internet of Things)` box's micro SD Card may need to be re-flashed to benefit from Odoo's latest :abbr:`IoT (Internet of Things)` image update. This means that the Odoo :abbr:`IoT (Internet of Things)` box software may need to be updated." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:9 -msgid "Upgrade from the IoT Box homepage" +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:10 +msgid "Upgrade from the IoT box home page" msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:11 -msgid "Go to the IoT Box homepage, click on *Update*, next to the version number. If a new version of the IoT Box image is available, you will see a *Upgrade to ___* button a the bottom of the page, the IoT Box will then flash itself to the new version of the IoT Box. All of your configurations will be saved." +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:12 +msgid "Go to the :abbr:`IoT (Internet of Things)` box homepage by navigating to :menuselection:`IoT app --> IoT Boxes` and clicking on the :guilabel:`IP address` of the :abbr:`IoT (Internet of Things)` box. Then click on :guilabel:`Update` (next to the version number)." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:18 -msgid "This process can take more than 30 minutes. Do not turn off or unplug the IoT Box as it would leave it in an inconsistent state." +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:16 +msgid "If a new version of the :abbr:`IoT (Internet of Things)` Box image is available, an :guilabel:`Upgrade to _xx.xx_` button will appear at the bottom of the page. Click this button to upgrade the unit and the :abbr:`IoT (Internet of Things)` box will then flash itself to the new version. All of the previous configurations will be saved." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:25 -msgid "Upgrade with Etcher" +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:22 +msgid "This process can take more than 30 minutes. Do not turn off or unplug the :abbr:`IoT (Internet of Things)` box as it would leave it in an inconsistent state. This means that the :abbr:`IoT (Internet of Things)` box will need to be re-flashed with a new image. See :ref:`flash_sdcard/etcher`." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:27 -msgid "Go to Balena’s website and download `Etcher `__. It’s a free and open-source utility used for burning image files. Install and launch it. Download the latest image from `nightly `__." +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:-1 +msgid "IoT box software upgrade in the IoT Box Home Page." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:32 -msgid "Then, open *Etcher* and select *Flash from file*, find the image you just downloaded. Insert the IoT Box SD card into your computer and select it. Click on *Flash* and wait for the process to finish." +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:34 +msgid "Upgrade with Etcher Software" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:37 +msgid "A computer with a micro SD card reader/adapter is required in order to re-flash the micro SD card." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:40 +msgid "Navigate to Balena's website and download `Etcher `_. It's a free and open-source utility used for burning image files onto drives. Click to `download `_. Install and launch the program on the computer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:44 +msgid "Then download the version-specific :abbr:`IoT (Internet of Things)` image from `nightly `_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:47 +msgid "The following are image versions on the `nightly `_ website with their corresponding Odoo database version:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:50 +msgid "Odoo V16 --> iotbox-latest.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:51 +msgid "Odoo V15 --> iotboxv21_10.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:52 +msgid "Odoo V14 --> iotboxv21_04.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:53 +msgid "Odoo V13 --> iotboxv20_10.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:55 +msgid "The images should be downloaded and extracted to a convenient file location." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:57 +msgid "After this step is complete, insert the :abbr:`IoT (Internet of Things)` box's micro SD card into the computer or reader. Open *Etcher* and select :guilabel:`Flash from file`, then find and select the image just downloaded and extracted. Next, select the drive the image should be burned to. Lastly, click on :guilabel:`Flash` and wait for the process to finish." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:-1 +msgid "Balena's Etcher software dashboard." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:67 +msgid "An alternative software for flashing the micro SD card is *Raspberry Pi Imager*. Download the *Raspberry Pi* software `here `_." msgstr "" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:5 @@ -1258,83 +1398,126 @@ msgid "Consult with your system or network administrator should this issue arise msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:3 -msgid "Use the IoT Box for the PoS" +msgid "Use an IoT box with a PoS" msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:9 +#: ../../content/applications/productivity/iot/config/pos.rst:6 msgid "Prerequisites" msgstr "" +#: ../../content/applications/productivity/iot/config/pos.rst:8 +msgid "Before starting, make sure the following equipment is available:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:10 +msgid "An :abbr:`IoT (Internet of Things)` box, with its power adapter." +msgstr "" + #: ../../content/applications/productivity/iot/config/pos.rst:11 -msgid "Before starting, make sure you have the following:" +msgid "A computer or tablet with an up-to-date web browser." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:12 +msgid "Odoo Online or an Odoo instance with the *Point of Sale* and *IoT* applications installed." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:13 -msgid "An IoT Box, with its power adapter." +msgid "A local network set up with :abbr:`DHCP (Dynamic Host Configuration Protocol)` (this is the default setting)." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:15 -msgid "A computer or tablet with an up-to-date web browser" +msgid "An RJ45 Ethernet Cable (optional, but preferred over WiFi, which is already built in)." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:17 -msgid "A running Odoo Online or Odoo instance with the Point of Sale and IoT apps installed" +#: ../../content/applications/productivity/iot/config/pos.rst:16 +msgid "Any of the supported hardware (receipt printer, barcode scanner, cash drawer, payment terminal, scale, customer display, etc.). The list of supported hardware can be found on the `POS Hardware page `_." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:20 -msgid "A local network setup with DHCP (this is the default setting)" +#: ../../content/applications/productivity/iot/config/pos.rst:21 +msgid "Setup" msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:22 -msgid "An RJ45 Ethernet Cable (optional, WiFi is built in)" +#: ../../content/applications/productivity/iot/config/pos.rst:25 +msgid "A suggested configuration for a point of sale system." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:24 -msgid "Any of the supported hardware (receipt printer, barcode scanner, cash drawer, payment terminal, scale, customer display, etc.). The list of supported hardware can be found on the `POS Hardware page `__" +#: ../../content/applications/productivity/iot/config/pos.rst:27 +msgid "To connect hardware to the :abbr:`PoS (Point of Sale)`, the first step is to connect an :abbr:`IoT (Internet of Things)` box to the database. To do this, follow these instructions: :doc:`Connect an Internet of Things (IoT) box to the Odoo database `." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:30 -msgid "Set Up" +#: ../../content/applications/productivity/iot/config/pos.rst:31 +msgid "Then, connect the peripheral devices to the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:32 -msgid "To connect hardware to the PoS, the first step is to connect an IoT Box to your database. For this, follow this :doc:`documentation `." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:36 -msgid "Then, you have to connect the peripheral devices to your IoT Box." +#: ../../content/applications/productivity/iot/config/pos.rst:37 +msgid "Device Name" msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:38 -msgid "**Printer**: Connect a supported receipt printer to a USB port or to the network and power it on." +msgid "Instructions" msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:41 -msgid "**Cash drawer**: The cash drawer should be connected to the printer with an RJ25 cable." +#: ../../content/applications/productivity/iot/config/pos.rst:39 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:66 +msgid "Printer" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:40 +msgid "Connect a supported receipt printer to a :abbr:`USB (Universal Serial Bus)` port or to the network, and power it on. Refer to :doc:`/applications/sales/point_of_sale/restaurant/kitchen_printing`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:43 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:149 +msgid "Cash drawer" msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:44 -msgid "**Barcode scanner**: Connect your barcode scanner. In order for your barcode scanner to be compatible it must end barcodes with an Enter character (keycode 28). This is most likely the default configuration of your barcode scanner." +msgid "The cash drawer should be connected to the printer with an RJ25 cable." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:45 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:117 +msgid "Barcode scanner" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:46 +msgid "In order for the barcode scanner to be compatible it must end barcodes with an `ENTER` character (keycode 28). This is most likely the default configuration of the barcode scanner." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:48 +msgid "Scale" msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:49 -msgid "**Scale**: Connect your scale and power it on." +msgid "Connect the scale and power it on. Refer to :doc:`/applications/productivity/iot/devices/scale`." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:51 -msgid "**Customer Display**: Connect a screen to the IoT Box to display the PoS order. Please refer to :doc:`/applications/productivity/iot/devices/screen`." +msgid "Customer display" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:52 +msgid "Connect a screen to the :abbr:`IoT (Internet of Things)` box to display the :abbr:`PoS (Point of Sale)` order. Refer to :doc:`/applications/productivity/iot/devices/screen`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:54 +msgid "Payment terminal" msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:55 -msgid "**Payment terminal**: The connection process depends on the terminal, please refer to the :doc:`payment terminals documentation `." +msgid "The connection process depends on the terminal. Refer to the :doc:`payment terminals documentation `." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:59 -msgid "Once it's done, you can connect the IoT Box to your PoS. For this, go in :menuselection:`Point of Sale --> Configuration --> PoS`, tick *IoT Box* and select the devices you want to use in this Point of Sale. Save the changes." +#: ../../content/applications/productivity/iot/config/pos.rst:58 +msgid "Once this is completed, connect the :abbr:`IoT (Internet of Things)` box to the :menuselection:`PoS` application. To do this, go to :menuselection:`Point of Sale --> Configuration --> PoS`, tick the :guilabel:`IoT Box` option, and select the devices to be used in this :abbr:`PoS (Point of Sale)`. :guilabel:`Save` the the changes." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:-1 +msgid "Configuring the connected devices in the POS application." msgstr "" #: ../../content/applications/productivity/iot/config/pos.rst:67 -msgid "Set up is done, you can launch a new PoS Session." +msgid "Once set up is done, a new :abbr:`PoS (Point of Sale)` session can be launched." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:3 @@ -1343,15 +1526,15 @@ msgid "Troubleshooting" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:6 -msgid "IoT Box Connection" +msgid "IoT box connection" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:9 -msgid "I can't find the pairing code to connect my IoT Box" +msgid "Unable to locate the pairing code to connect the IoT box" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:11 -msgid "The pairing code should be printed on receipt printers connected to the IoT Box and should also be displayed on connected monitors." +msgid "The pairing code should be printed on receipt printers connected to the :abbr:`IoT (Internet of Things)` box and should also be displayed on connected monitors." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:14 @@ -1359,123 +1542,147 @@ msgid "The pairing code doesn't show under the following circumstances:" msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:16 -msgid "The IoT Box is already connected to an Odoo database;" +msgid "The :abbr:`IoT (Internet of Things)` box is already connected to an Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:17 +msgid "The :abbr:`IoT (Internet of Things)` box is not connected to the Internet." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:18 -msgid "The IoT Box is not connected to the Internet;" +msgid "The code is only valid for 5 minutes after the :abbr:`IoT (Internet of Things)` box has started. It's automatically removed from connected displays when this time has expired." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:20 -msgid "The code is only valid for 5 minutes after the IoT Box has started. It's automatically removed from connected displays when this delay has expired;" +msgid "The version of the :abbr:`IoT (Internet of Things)` box image is too old. If the :abbr:`IoT (Internet of Things)` box image is from an earlier version, then the SD card of the :abbr:`IoT (Internet of Things)` box will need to be re-flashed to update the image (see :doc:`Flashing the SD Card `)." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:23 -msgid "The version of the IoT Box image is too old. It should use version 20.06 or more recent. If your IoT Box image is from an earlier version, then you will have to reflash the SD card of your IoT Box to update the image (see :doc:`Flashing your SD Card `)" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:25 +msgid "If none of the cases listed above correct the issue, then make sure that the :abbr:`IoT (Internet of Things)` box has correctly started, by checking that a fixed green LED is showing next to the power port." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:28 -msgid "If you are not in any of the cases listed above, make sure that the IoT Box has correctly started, by checking that a fixed green LED is showing next to the micro-USB port." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:30 +msgid "IoT box is connected but it's not showing in the database" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:33 -msgid "I've connected my IoT Box but it's not showing in my database" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:32 +msgid "When an :abbr:`IoT (Internet of Things)` box connects to a database, it may restart. If so, it can take up to five minutes before appearing in the database. If the :abbr:`IoT (Internet of Things)` box is still not showing after five minutes, make sure that the :abbr:`IoT (Internet of Things)` box can reach the database and that the server doesn't use a multi-database environment." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:35 -msgid "When you connect an IoT Box to a database, the IoT Box might restart, if that is the case, it might take up to one minute before appearing in your database. If after some time the IoT is still not showing, make sure that your database can be reached from the IoT Box and that your server doesn't use a multi-database environment." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:37 +msgid "To access the database from the :abbr:`IoT (Internet of Things)` box, open a browser and type in the database address." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:42 -msgid "My IoT Box is connected to my database, but cannot be reached" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:41 +msgid "The IoT box is connected to the Odoo database, but cannot be reached" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:44 -msgid "Make sure that the IoT Box and the device running the browser are located on the same network as the IoT Box cannot be reached from outside the local network." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:43 +msgid "Make sure that the :abbr:`IoT (Internet of Things)` box and the computer running the browser are located on the same network, as the :abbr:`IoT (Internet of Things)` box cannot be reached from outside the local network." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:49 -msgid "Printer" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:48 +msgid "The HTTPS certificate doesn't generate" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:52 -msgid "My printer is not detected" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:50 +msgid "In order to generate a :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate, an IoT box subscription is required for the :abbr:`IoT (Internet of Things)` box. Connecting the :abbr:`IoT (Internet of Things)` box prior to configuring an :abbr:`IoT (Internet of Things)` subscription for the database and :abbr:`IoT (Internet of Things)` box with the Account Manager will result in an unsecured connection." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:54 -msgid "If one of your printers doesn't show up in your devices list, go to the IoT Box homepage and make sure that it is listed under *Printers*." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:56 +msgid "In addition, a firewall can also prevent the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate from generating correctly. In this case, deactivate the firewall until the certificate is successfully generated. It should also be noted that certain devices, such as a router that has a built-in firewall, can prevent the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate from generating." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:60 -msgid "If your printer is not present on the IoT Box homepage, hit *Printers Server*, go to the *Administration* tab and click on *Add Printer*. If you can't find your printer in the list, it's probably not connected properly." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:63 +msgid ":doc:`HTTPS certificate (IoT) `" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:66 -msgid "My printer outputs random text" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:69 +msgid "The printer is not detected" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:68 -msgid "For most printers, the correct driver should be automatically detected and selected. However, in some cases, the automatic detection mechanism might not be enough, and if no driver is found the printer might print random characters." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:71 +msgid "If a printer doesn't show up in the devices list, go to the :abbr:`IoT (Internet of Things)` box homepage and make sure that it is listed under :guilabel:`Printers`." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:73 -msgid "The solution is to manually select the corresponding driver. On the IoT Box homepage, click on *Printers Server*, go to the *Printers* tab and select the printer in the list. In the Administration dropdown, click on *Modify Printer*. Follow the steps and select the Make and Model corresponding to your printer." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:-1 +msgid "The IoT box Home Page landing page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:78 +msgid "If the printer is not present on the :abbr:`IoT (Internet of Things)` box homepage, click :guilabel:`Printers Server`, go to the :guilabel:`Administration` tab and click on :guilabel:`Add Printer`. If the printer is not present in the list, it's likely not connected properly." msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:83 +msgid "The printer outputs random text" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:85 +msgid "For most printers, the correct driver should be automatically detected and selected. However, in some cases, the automatic detection mechanism might not be enough, and if no driver is found, the printer might print random characters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:89 +msgid "The solution is to manually select the corresponding driver. On the :abbr:`IoT (Internet of Things)` box homepage, click on :guilabel:`Printers Server`, go to the :guilabel:`Printers` tab and select the printer in the list. In the :guilabel:`Administration` dropdown, click on :guilabel:`Modify Printer`. Follow the steps and select the *make* and *model* corresponding to the printer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:-1 +msgid "Edit the printer connected to the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:99 msgid "Epson and Star receipt printers and Zebra label printers do not need a driver to work. Make sure that no driver is selected for those printers." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:88 -msgid "My Zebra Printer doesn't print anything" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:103 +msgid "The Zebra printer doesn't print anything" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:90 -msgid "Zebra printers are quite sensitive to the format of the ZPL code that is printed. If nothing comes out of the printer or blank labels are printed, try changing the format of the report that is sent to the printer by accessing :menuselection:`Settings ~~> Technical ~~> Views` in developer mode and look for the corresponding template." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:105 +msgid "Zebra printers are quite sensitive to the format of the Zebra Programming Language (ZPL) code that is printed. If nothing comes out of the printer or blank labels are printed, try changing the format of the report that is sent to the printer by accessing :menuselection:`Settings --> Technical --> User Interface --> Views` in :ref:`developer mode ` and look for the corresponding template." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:97 -msgid "Barcode Scanner" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:112 +msgid "Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming Language)` files `here `_." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:100 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:120 msgid "The characters read by the barcode scanner don't match the barcode" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:102 -msgid "By default, we assume that your barcode scanner is configured in US QWERTY. This is the default configuration of most barcode readers. If your barcode scanner uses a different layout, please go to the form view of your device and select the correct one." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:122 +msgid "By default, most barcode scanners are configured in the US QWERTY format. If the barcode scanner uses a different layout, go to the form view of the device (:menuselection:`IoT App --> Devices --> Barcode Device`) and select the correct format." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:108 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:127 msgid "Nothing happens when a barcode is scanned" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:110 -msgid "Make sure that the correct device is selected in your Point of Sale configuration and that your barcode is configured to send an ENTER character (keycode 28) at the end of every barcode." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:129 +msgid "Make sure that the correct device is selected in the :menuselection:`Point of Sale` configuration and that the barcode is configured to send an `ENTER` character (keycode 28) at the end of every barcode. To do so, navigate to :menuselection:`PoS app --> 3-Dot Menu on the PoS --> IoT Box section --> Edit`." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:115 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:135 msgid "The barcode scanner is detected as a keyboard" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:117 -msgid "Some poorly built barcode scanners do not advertise themselves as barcode scanners but as a USB keyboard instead, and will not be recognized by the IoT Box." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:138 +msgid "Some barcode scanners do not advertise themselves as barcode scanners but as a USB keyboard instead, and will not be recognized by the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:121 -msgid "You can manually change the device type by going to its form view and activating the *Is scanner* option." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:141 +msgid "The device type can be manually changed by going to its form view (:menuselection:`IoT App --> Devices --> Barcode Device`) and activating the :guilabel:`Is scanner` option." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:128 -msgid "Cashdrawer" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:-1 +msgid "Modifying the form view of the barcode scanner." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:131 -msgid "The cashdrawer does not open" +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:152 +msgid "The cash drawer does not open" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:133 -msgid "The cashdrawer should be connected to the printer and the *Cashdrawer* checkbox should be ticked in the POS configuration." +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:154 +msgid "The cash drawer should be connected to the printer and the :guilabel:`Cash drawer` checkbox should be ticked in the :abbr:`PoS (Point of Sale)` configuration. To do so, navigate to :menuselection:`POS app --> 3-Dot Menu on the POS --> IoT Box section --> Edit --> Receipt Printer --> Cashdrawer checkbox`." msgstr "" #: ../../content/applications/productivity/iot/config/windows_iot.rst:3 @@ -1703,288 +1910,395 @@ msgid "Devices" msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:3 -msgid "Connect a Camera" +msgid "Connect a camera" msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:5 -msgid "When using your *IoT Box* in Odoo, you could need to use a camera. As it can be done in a few steps, this device is really easy to configure. Then, you can use it in your manufacturing process and link it to a control point. Doing so will allow you to take pictures when you reach the chosen quality control point." +msgid "A camera can be connected to an :abbr:`IoT (Internet of Things)` box with an Odoo database in just a few steps. Once a camera is connected to an :abbr:`IoT (Internet of Things)` box, it can be used in a manufacturing process, or it can be linked to a quality control point/quality check. Doing so allows for the taking of pictures when a chosen quality control point/check has been reached, or when a specific key is pressed during manufacturing." msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:12 -#: ../../content/applications/productivity/iot/devices/footswitch.rst:13 +#: ../../content/applications/productivity/iot/devices/footswitch.rst:14 #: ../../content/applications/productivity/iot/devices/printer.rst:11 #: ../../content/applications/productivity/iot/devices/scale.rst:10 -#: ../../content/applications/productivity/iot/devices/screen.rst:17 +#: ../../content/applications/productivity/iot/devices/screen.rst:18 msgid "Connection" msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:14 -msgid "To connect the camera to the *IoT Box*, simply connect the two by cable." +msgid "To connect a camera to an :abbr:`IoT (Internet of Things)` box, simply connect the two via cable. This is usually done with a :abbr:`USB (Universal Serial Bus)` cable of some sort." msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:17 -msgid "If your camera is a `*supported one* `__, there is no need to set up anything as it will be detected as soon as it is connected." +msgid "If the camera is `supported `_, there is no need to set up anything, as it'll be detected as soon as it's connected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:-1 +msgid "Camera recognized on the IoT box." msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:25 -msgid "Link a Camera to a Quality Control Point" +msgid "Link camera to quality control point in manufacturing process" msgstr "" -#: ../../content/applications/productivity/iot/devices/camera.rst:28 -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:34 -msgid "With the Manufacturing app" +#: ../../content/applications/productivity/iot/devices/camera.rst:27 +msgid "In the :menuselection:`Quality app`, a device can be set up on a :guilabel:`Quality Control Point`. To do that, navigate to the :menuselection:`Quality app --> Quality Control --> Control Points` and open the desired :guilabel:`Control Point` that'll be linked to the camera." msgstr "" -#: ../../content/applications/productivity/iot/devices/camera.rst:30 -msgid "In your *Quality app*, you can setup the device on a *Quality Control Point*. Go to the *Control Points* menu, under *Quality Control* and open the control point you want to link with the camera." +#: ../../content/applications/productivity/iot/devices/camera.rst:31 +msgid "On the control point form, edit the control point by selecting the :guilabel:`Type` field, and clicking on :guilabel:`Take a Picture` from the drop-down menu. Doing so reveals a field called :guilabel:`Device`, wherein the attached *device* can be selected. :guilabel:`Save` the changes, if required." msgstr "" -#: ../../content/applications/productivity/iot/devices/camera.rst:34 -msgid "Now, you can edit the control point and select the device from the dropdown list. Now, hit save." +#: ../../content/applications/productivity/iot/devices/camera.rst:-1 +msgid "Setting up the device on the quality control point." msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst:40 -msgid "Then, your camera can be used with the picked *Control Point*. During the manufacturing process, reaching the *Quality Control Point* you chose before will allow you to take a picture." +msgid "The camera is now useable with the selected quality control point. When the quality control point is reached during the manufacturing process, the database prompts the operator to take a picture." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:-1 +msgid "Graphic user interface of the device on the quality control point." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:48 +msgid "Quality control points can also be accessed by navigating to :menuselection:`IoT App --> Devices`. From here, select the device. There is a :guilabel:`Quality Control Points` tab, where they can be added with the device." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:53 +msgid "On a quality check form, the :guilabel:`Type` of check can also be specified to :guilabel:`Take a Picture`. Navigate to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New` to create a new quality check from the :guilabel:`Quality Checks` page." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:58 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:66 +#: ../../content/applications/productivity/iot/devices/printer.rst:70 +msgid ":doc:`../../../inventory_and_mrp/manufacturing/quality_control/quality_control_points`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:59 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:67 +#: ../../content/applications/productivity/iot/devices/printer.rst:71 +msgid ":doc:`../../../inventory_and_mrp/manufacturing/quality_control/quality_alerts`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:62 +msgid "Link camera to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:64 +msgid "To link a camera to an action, it first needs to be configured on a work center. Navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. Next, go to the desired :guilabel:`Work Center` in which a camera will be used to reveal that specific work center's detail form. From here, add the device in the :guilabel:`IoT Triggers` tab, in the :guilabel:`Device` column, by clicking :guilabel:`Add a Line`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:70 +msgid "Now, the camera device can be linked to the :guilabel:`Action` column drop-down option labeled :guilabel:`Take a Picture`. A key can also be added to trigger the action." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:74 +msgid "The first trigger listed is chosen first. The order of triggers matters, and they can be dragged into any desired order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:78 +msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the camera." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:82 +#: ../../content/applications/productivity/iot/devices/footswitch.rst:52 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:90 +#: ../../content/applications/productivity/iot/devices/printer.rst:95 +msgid ":ref:`workcenter_iot`" msgstr "" #: ../../content/applications/productivity/iot/devices/footswitch.rst:3 -msgid "Connect a Footswitch" +msgid "Connect a footswitch" msgstr "" #: ../../content/applications/productivity/iot/devices/footswitch.rst:5 -msgid "When working, it is always better to have your two hands available. Using Odoo’s *IoT Box* and a footswitch will allow it." +msgid "When working in a manufacturing environment, it's always better for an operator to have both hands available at all times. Odoo's :abbr:`IoT (Internet of Things)` box makes this possible when using a footswitch." msgstr "" -#: ../../content/applications/productivity/iot/devices/footswitch.rst:8 -msgid "In fact, you will be able to go from one screen to another and perform actions by using your foot and the footswitch. Really convenient, it can be configured in a few steps." +#: ../../content/applications/productivity/iot/devices/footswitch.rst:9 +msgid "In fact, with a footswitch, the operator is able to go from one screen to another, and perform actions using their foot. This can be configured in just a few steps on the work center in the *Manufacturing* app." msgstr "" -#: ../../content/applications/productivity/iot/devices/footswitch.rst:15 -msgid "Connecting the footswitch to the *IoT Box* is easy, you just have to connect the two by cable." +#: ../../content/applications/productivity/iot/devices/footswitch.rst:16 +msgid "To connect a footswitch to the :abbr:`IoT (Internet of Things)` box, connect the two devices via cable. More often than not, this is done with a :abbr:`USB (Universal Serial Bus)` cable." msgstr "" -#: ../../content/applications/productivity/iot/devices/footswitch.rst:18 -msgid "If your footswitch is a `supported one `__, there is no need to set up anything since it will be automatically detected when connected." +#: ../../content/applications/productivity/iot/devices/footswitch.rst:19 +msgid "If the footswitch is a `supported device `_, there is no need to take further action, since it'll be automatically detected when connected." msgstr "" -#: ../../content/applications/productivity/iot/devices/footswitch.rst:26 -msgid "Link a Footswitch to a Workcenter" +#: ../../content/applications/productivity/iot/devices/footswitch.rst:-1 +msgid "Footswitch recognized on the IoT box." msgstr "" -#: ../../content/applications/productivity/iot/devices/footswitch.rst:28 -msgid "To link the footswitch to an action, it needs to be configured on a workcenter. Go to the workcenter you want to use the footswitch in and add the device in the *IoT Triggers* tab. Then, you can link it to an action and also add a key to trigger it." +#: ../../content/applications/productivity/iot/devices/footswitch.rst:27 +msgid "Link a footswitch to a work center in the Odoo Manufacturing app" msgstr "" -#: ../../content/applications/productivity/iot/devices/footswitch.rst:36 -msgid "Note that the one that is first in the list will be chosen. So, the order matters! In the picture above, using the footswitch will, for example, automatically skip the current part of the process you work on." +#: ../../content/applications/productivity/iot/devices/footswitch.rst:29 +msgid "To link a footswitch to an action, it first needs to be configured on a work center. Navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. From here, go to the desired :guilabel:`Work Center` in which the footswitch will be used, and add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. Doing so means the footswitch can be linked to an option in the :guilabel:`Action` column drop-down, and optionally, a key can be added to trigger it. An example of an :guilabel:`Action` in the *Manufacturing app* could be the :guilabel:`Validate` or :guilabel:`Mark as Done` buttons on a manufacturing work order." msgstr "" -#: ../../content/applications/productivity/iot/devices/footswitch.rst:41 -msgid "When you are on the work order screen, a status button indicates if you are correctly connected to the footswitch." +#: ../../content/applications/productivity/iot/devices/footswitch.rst:-1 +msgid "Footswitch trigger setup on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:43 +msgid "It should be noted that the first listed trigger is chosen first. So, the order matters, and these triggers can be dragged into any order. In the picture above, using the footswitch automatically skips the part of the process that's currently being worked on." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:48 +msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the footswitch." msgstr "" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:3 -msgid "Connect a Measurement Tool" +msgid "Connect a measurement tool" msgstr "" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:5 -msgid "With Odoo’s *IoT Box*, it is possible to connect measurement tools to your database. Find the list of supported devices here: `Supported devices `__,." +msgid "With Odoo's :abbr:`IoT (Internet of Things)` box, it is possible to connect measurement tools to the Odoo database for use in the *Quality app* on a quality control point/quality check, or for use in a work center during the manufacturing process." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:10 -msgid "Connect in USB" +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:9 +msgid "Find the list of supported devices here: `Supported devices `_." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:12 -msgid "To add a device connected by USB, just plug the USB cable in the *IoT Box*, and the device should appear in your Odoo database." +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:13 +msgid "Connect with universal serial bus (USB)" msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:19 -msgid "Connect in Bluetooth" +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:15 +msgid "To add a device connected by :abbr:`USB (Universal Serial Bus)`, plug the :abbr:`USB (Universal Serial Bus)` cable into the :abbr:`IoT (Internet of Things)` box, and the device appears in the Odoo database." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:21 -msgid "Activate the Bluetooth on your device (see your device manual for further explanation) and the IoT Box will automatically try to connect to the device." +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:-1 +msgid "Measurement tool recognized on the IoT box." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:25 -msgid "Here is an example of what it should look like:" +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:24 +msgid "Connect with bluetooth" msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:31 -msgid "Link a measurement tool to a quality control point" +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:26 +msgid "Activate the Bluetooth functionality on the device (see the device manual for further explanation), and the :abbr:`IoT (Internet of Things)` box automatically connects to the device." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:36 -msgid "In your *Quality app*, you can setup a device on your *Quality Control Points*. To do so, go to the *Control Points* menu, under *Quality Control* and open the control point to which you want to assign a measurement tool." +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:-1 +msgid "Bluetooth indicator on measurement tool." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:35 +msgid "Link a measurement tool to a quality control point in the manufacturing process" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:37 +msgid "In the *Quality app*, a device can be set up on a quality control point. To do that, navigate to :menuselection:`Quality app --> Quality Control --> Control Points`, and open the desired control point to which the measurement tool should be linked." msgstr "" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:41 -msgid "Now, you can edit the control point and choose the device from the dropdown list. Then, hit save." +msgid "From here, edit the control point, by selecting the :guilabel:`Type` field, and clicking :guilabel:`Measure` from the drop-down menu. Doing so reveals a field called :guilabel:`Device`, where the attached device can be selected." msgstr "" -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:47 -msgid "Now, your measurement tool is linked to the chosen *Control Point*. The value, which needs to be changed manually, will be automatically updated while the tool is being used." +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:45 +msgid "Additionally, :guilabel:`Norm` and :guilabel:`Tolerance` can be configured. :guilabel:`Save` the changes, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:48 +msgid "At this point, the measurement tool is linked to the chosen quality control point. The value, which usually needs to be changed manually, is automatically updated while the tool is being used." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:-1 +msgid "Measurement tool input in the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:56 +#: ../../content/applications/productivity/iot/devices/printer.rst:60 +msgid "Quality control points can also be accessed by navigating to :menuselection:`IoT App --> Devices`, then select the device. There is a :guilabel:`Quality Control Points` tab, where they can be added with the device." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:61 +msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Measure`. Access a new quality check detail page, by navigating to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:70 +msgid "Link a measurement tool to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:72 +msgid "To link a measurement tool to an action, it first needs to be configured on a work center. To do that, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. Then, select the desired work center in which the measurement tool will be used." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:76 +msgid "On the work center page, add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. Then, the measurement tool can be linked to the :guilabel:`Action` drop-down menu option labeled :guilabel:`Take Measure`. A key can be added to trigger the action." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:82 +msgid "It should be noted that the first listed trigger is chosen first. The order matters, and these triggers can be dragged into any order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:86 +msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the measurement tool." msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:3 -msgid "Connect a Printer" +msgid "Connect a printer" msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:5 -msgid "When using your *IoT Box* in Odoo, you could need to use a printer. Doing so is easy and convenient as it can be done in a few steps. Then, you can use it to print receipts, orders or even reports in different Odoo apps." +msgid "Printer installation can be done in a few easy steps. The printer can be used to print receipts, labels, orders, or even reports from the different Odoo apps. In addition, printer actions can be assigned as an *action on a trigger* during the manufacturing process, or added onto a quality control point or a quality check." msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:13 -msgid "The IoT Box supports printers connected through USB, network or Bluetooth. `Supported printers `__ will be detected automatically and will appear in the *Devices* list of your IoT app." +msgid "The :abbr:`IoT (Internet of Things)` box supports printers connected through :abbr:`USB (Universal Serial Bus)`, network connection, or Bluetooth. `Supported printers `__ are detected automatically, and appear in the :guilabel:`Devices` list of the *IoT app*." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:18 -msgid "The printer can take up to two minutes to appear in your devices list." +#: ../../content/applications/productivity/iot/devices/printer.rst:-1 +msgid "The printer as it would appear in the IoT app devices list." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:24 -msgid "Link the Printer" +#: ../../content/applications/productivity/iot/devices/printer.rst:23 +msgid "The printer can take up to two minutes to appear in the *IoT app* devices list." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:27 -msgid "To Work Orders" +#: ../../content/applications/productivity/iot/devices/printer.rst:26 +msgid "Link printer" msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:29 -msgid "You can link *Work Orders* to printers via a *Quality Control Point* to print labels for manufactured products." +msgid "Link printer to work orders" msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:32 -msgid "To do so, you need to create a *Quality Control Point* from the *Quality* app. Then, you can select the correct manufacturing operation and the work order operation. In type, choose *Print Label* and hit save." +#: ../../content/applications/productivity/iot/devices/printer.rst:31 +msgid "*Work Orders* can be linked to printers, via a quality control point, to print labels for manufactured products." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:40 -msgid "Now, each time you reach the quality control point for the chosen product, a *Print Label* button will appear." +#: ../../content/applications/productivity/iot/devices/printer.rst:34 +msgid "In the *Quality app*, a device can be set up on a quality control point. To do that, go to the :menuselection:`Quality app --> Quality Control --> Control Points`, and open the desired control point to which the printer will be linked." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:47 -msgid "To Reports" +#: ../../content/applications/productivity/iot/devices/printer.rst:39 +msgid "A *Manufacturing Operation* and *Work Order Operation* need to be attached to a quality control point before the :guilabel:`Type` field allows for the :guilabel:`Print Label` option to be selected." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:49 -msgid "You can also link a type of report to a certain printer. In the *IoT* app, go to the *Devices* menu and select the printer you want to set up." +#: ../../content/applications/productivity/iot/devices/printer.rst:43 +msgid "From here, edit the control point, by selecting the :guilabel:`Type` field, and selecting :guilabel:`Print Label` from the drop-down menu of options. Doing so reveals a field called :guilabel:`Device`, where the attached *device* can be selected. :guilabel:`Save` the changes, if required." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:56 -msgid "Now, go to the *Printer Reports* tab." +#: ../../content/applications/productivity/iot/devices/printer.rst:-1 +msgid "This is the quality control point setup." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:61 -msgid "Hit edit and then, click on *Add a line*. In the window that shows up, check all the types of reports that should be linked to this printer. Click on select and save." +#: ../../content/applications/productivity/iot/devices/printer.rst:52 +msgid "The printer can now be used with the selected quality control point. When the quality control point is reached during the manufacturing process, the database presents the option to print labels for a specific product." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:68 -msgid "Now, each time you click on *Print* in the control panel, instead of downloading a PDF, it will send it to the selected printer and automatically print it." +#: ../../content/applications/productivity/iot/devices/printer.rst:65 +msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Print Label`. To create new quality checks, navigate to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:73 -msgid "Print Receipts from the PoS" +#: ../../content/applications/productivity/iot/devices/printer.rst:74 +msgid "Link a printer to a work center in the Manufacturing app" msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:75 -msgid "You can link a printer to your *Point of Sale* app so you can print receipts directly from your *PoS*." +#: ../../content/applications/productivity/iot/devices/printer.rst:76 +msgid "To link a printer to an action, it first needs to be configured on a work center. To do that, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. From here, select the desired work center in which the printer will be used. Next, add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:78 -msgid "Doing so is really easy. Go to your *Point of Sale* app and open your *Point of Sale* settings, under *Configuration*. There, click on *Edit* and check the *IoT Box* feature. Then, choose your *Receipt Printer* from the dropdown." +#: ../../content/applications/productivity/iot/devices/printer.rst:82 +msgid "Then, the printer can be linked to either of the following options in the :guilabel:`Actions` drop-down menu: :guilabel:`Print Labels`, :guilabel:`Print Operation`, or :guilabel:`Print Delivery Slip`. A key can also be added to trigger the action." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:86 -msgid "Now, you will be able to print different kinds of tickets from your *POS*: **receipts**, **sale details** and **bills**." +#: ../../content/applications/productivity/iot/devices/printer.rst:87 +msgid "The first listed trigger on the form will be chosen first. So, the order matters, and these triggers can be dragged into any order." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:89 -msgid "Receipts are printed once the order is validated. The process is automated when you enable the feature in your *PoS* configuration." +#: ../../content/applications/productivity/iot/devices/printer.rst:91 +msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the printer." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:92 -msgid "Sales details can be printed by clicking on the printer icon on the navbar at the top of the *PoS*. It will print the details of the sales of the current day." +#: ../../content/applications/productivity/iot/devices/printer.rst:98 +msgid "Link printer to reports" msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:99 -msgid "As for the bill, it is only available in restaurant mode. In your restaurant settings, activate *Print Bills* and a *Bill* button will appear in the left panel of the *PoS*." +#: ../../content/applications/productivity/iot/devices/printer.rst:100 +msgid "It's also possible to link a type of report to a certain printer. In the *IoT app*, go to the :guilabel:`Devices` menu, and select the desired printer that needs to be configured." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:107 -msgid "Print Orders in the kitchen" +#: ../../content/applications/productivity/iot/devices/printer.rst:103 +msgid "From here, click :guilabel:`Edit`, go to the :guilabel:`Printer Reports` tab, and select :guilabel:`Add a line`. In the window that appears, check all the types of :guilabel:`Reports` that should be linked to this printer." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:109 -msgid "In restaurant mode, you can send order tickets to the kitchen." +#: ../../content/applications/productivity/iot/devices/printer.rst:-1 +msgid "The printer devices listed in the IoT Devices menu." msgstr "" #: ../../content/applications/productivity/iot/devices/printer.rst:111 -msgid "To do so, go to the *PoS* app and open your *PoS* settings. Then, tick *Order Printer*." +msgid "Now, each time :guilabel:`Print` is selected in the control panel, instead of downloading a PDF, Odoo sends the report to the selected printer, and automatically prints it." msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:117 -msgid "Now, go to the *Printers* menu. Hit create, select the printer from the dropdown and, in the *Printer Product Categories* field, choose all the categories of products that should be printed on this printer." +#: ../../content/applications/productivity/iot/devices/printer.rst:115 +msgid ":doc:`POS Order Printing <../../../sales/point_of_sale/restaurant/kitchen_printing>`" msgstr "" -#: ../../content/applications/productivity/iot/devices/printer.rst:124 -msgid "In the *PoS*, when you add or remove a product from one of the selected categories, the button *Order* will be green. If you click on it, the IoT Box will print a receipt on the corresponding printer." +#: ../../content/applications/productivity/iot/devices/printer.rst:118 +msgid "Reports can also be configured in the :guilabel:`Technical Menu` while in :ref:`debug mode `. To do that, navigate to :menuselection:`Settings App --> Technical Menu --> Actions --> Reports`. From here, the individual report can be found in this list, where the :guilabel:`IoT Device` can be set on the report." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:3 -msgid "Connect a Scale" +msgid "Connect a scale" msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:5 -msgid "When using your **IoT Box** in Odoo, you could need to use a scale. Doing so is easy and convenient as it can be done in a few steps. Then, you can use it in your **Point of Sale app** to weigh your products, which is helpful if their price are based on it." +msgid "A scale can be connected to the :abbr:`IoT (Internet of Things)` box on an Odoo database in a few easy steps. After setup, the *Point of Sale* app can be used to weigh products, which is helpful if their prices are calculated based on weight." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:12 -msgid "To link the scale to the **IoT Box**, connect them with a cable." +msgid "To link the scale to the :abbr:`IoT (Internet of Things)` box, connect it with a :abbr:`USB (Universal Serial Bus)` cable." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:15 -msgid "In some cases, a serial to USB adapter may be needed." +#: ../../content/applications/productivity/iot/devices/scale.rst:16 +msgid "In some cases, a serial port to :abbr:`USB (Universal Serial Bus)` adapter may be needed." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:17 -msgid "If your scale is `compatible with Odoo IoT Box `_, there is no need to set up anything because it will be automatically detected as soon as it is connected." +#: ../../content/applications/productivity/iot/devices/scale.rst:18 +msgid "If the scale is `compatible with Odoo IoT Box `_, there is no need to set up anything because it will be automatically detected as soon as it is connected." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:-1 msgid "IOT box auto detection." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:24 -msgid "You may need to restart the box and download your scales’ drivers from the box in some cases. To do so, go to the *IoT Box Home Page* and click on *drivers list*. Then, click on load drivers." +#: ../../content/applications/productivity/iot/devices/scale.rst:25 +msgid "The :abbr:`IoT (Internet of Things)` box may need to be restarted and the scale's drivers may need to be downloaded to the box in some cases. To update the drivers, go to the :abbr:`IoT (Internet of Things)` box homepage and click on :guilabel:`Drivers List`. Then, click on :guilabel:`Load Drivers`." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:-1 msgid "View of the IoT box settings and driver list." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:32 -msgid "Use a Scale in Point of Sale" -msgstr "" - #: ../../content/applications/productivity/iot/devices/scale.rst:34 -msgid "To use the scale in your *Point of Sale* app, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, open the one you want to configure, then click on *Edit* and enable the *IoT Box* feature." +msgid "If loading the drivers still doesn't allow for the scale to function, it may be that the scale is not compatible with the Odoo :abbr:`IoT (Internet of Things)` box. In this case, a different scale will need to be used." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:-1 -msgid "View of the IoT box feature inside of the PoS settings." +#: ../../content/applications/productivity/iot/devices/scale.rst:39 +msgid "Use a scale in a point of sale (POS) system" msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:42 -msgid "Now, choose the *IoT Box* in the dropdown menu and check the *Electronic Scale* option. Then, you hit save." +#: ../../content/applications/productivity/iot/devices/scale.rst:41 +msgid "To use the scale in the *Point of Sale app*, go to :menuselection:`PoS app --> 3-Dot Menu on the PoS --> Settings`, then enable the :abbr:`IoT (Internet of Things)` box feature. After this is complete, the scale device can be set." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:45 +msgid "Select the scale from the :guilabel:`Electronic Scale` drop-down menu. Then click :guilabel:`Save` to save the changes, if required." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:-1 msgid "List of the external tools that can be used with PoS and the IoT box." msgstr "" -#: ../../content/applications/productivity/iot/devices/scale.rst:49 -msgid "The scale is now available in all your *PoS* sessions. Then, if a product has a price per weight set, clicking on it on the *PoS* screen opens the scale screen, where the cashier can weigh the product and add the correct price to the cart." +#: ../../content/applications/productivity/iot/devices/scale.rst:52 +msgid "The scale is now available in all the :abbr:`PoS (Point of Sale)` sessions. Now, if a product has a price per weight set, clicking on it on the :guilabel:`PoS` screen opens the scale screen, where the cashier can weigh the product and add the correct price to the cart." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:-1 @@ -1996,113 +2310,117 @@ msgid "Connect a screen" msgstr "" #: ../../content/applications/productivity/iot/devices/screen.rst:5 -msgid "In Odoo, an :abbr:`IoT (Internet of Things)` Box can be connected to a screen display. After being connected, the screen can be used to display a :abbr:`PoS (Point of Sale)` order to a client." +msgid "In Odoo, an :abbr:`IoT (Internet of Things)` box can be connected to a screen display. After being configured, the screen can be used to display a Point of Sale (PoS) order to a client." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:-1 +#: ../../content/applications/productivity/iot/devices/screen.rst:10 msgid "An example of a PoS (point of sale) order on a screen display." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:13 -msgid "Access the customer display from any other computer by going to the :abbr:`IoT (Internet of Things)` Box homepage and clicking on the :guilabel:`POS Display` button." +#: ../../content/applications/productivity/iot/devices/screen.rst:12 +msgid "Access the customer display by going to the :abbr:`IoT (Internet of Things)` box homepage and clicking on the :guilabel:`PoS Display` button. To get to the :abbr:`IoT (Internet of Things)` box homepage, navigate to :menuselection:`IoT app --> IoT Boxes` and click on the :abbr:`IoT (Internet of Things)` box homepage link." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:19 -msgid "The way to connect the screen display to the :abbr:`IoT (Internet of Things)` Box differs depending on the model." +#: ../../content/applications/productivity/iot/devices/screen.rst:20 +msgid "The way to connect the screen display to the :abbr:`IoT (Internet of Things)` box differs depending on the model." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:24 +#: ../../content/applications/productivity/iot/devices/screen.rst:25 msgid "IoT Box model 4" msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:26 -msgid "Connect up to two screens with Micro-HDMI cables on the side of the :abbr:`IoT (Internet of Things)` Box. If two screens are connected, they can display distinct content (see usage below)." +#: ../../content/applications/productivity/iot/devices/screen.rst:27 +msgid "Connect up to two screens with micro-HDMI cables on the side of the :abbr:`IoT (Internet of Things)` box. If two screens are connected, they can display distinct content (see :ref:`Screen Usage `)." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:30 +#: ../../content/applications/productivity/iot/devices/screen.rst:31 msgid "IoT Box model 3" msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:32 -msgid "Connect the screen with an HDMI cable on the side of the :abbr:`IoT (Internet of Things)` Box." +#: ../../content/applications/productivity/iot/devices/screen.rst:33 +msgid "Connect the screen with an HDMI cable on the side of the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:35 -msgid "Screen(s) should be connected before the :abbr:`IoT (Internet of Things)` Box is switched on. If it is already on, connect the screen(s), and then restart the :abbr:`IoT (Internet of Things)` Box by unplugging it and plugging it back into its power source." +#: ../../content/applications/productivity/iot/devices/screen.rst:36 +msgid ":ref:`See the Raspberry Pi Schema `." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:40 -msgid "The usage of HDMI/Micro-HDMI adapters may cause issues which will result in a blank, black screen on the screen display. Cable usage is recommended." +#: ../../content/applications/productivity/iot/devices/screen.rst:39 +msgid "Screen(s) should be connected before the :abbr:`IoT (Internet of Things)` box is switched on. If it is already on, connect the screen(s), and then restart the :abbr:`IoT (Internet of Things)` box by unplugging it for ten seconds and plugging it back into its power source." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:43 +#: ../../content/applications/productivity/iot/devices/screen.rst:44 +msgid "The usage of HDMI/micro-HDMI adapters may cause issues which will result in a blank, black screen on the screen display. Using the specific cable for the display connection is recommended." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:47 msgid "If the connection was successful, the screen should display the :guilabel:`POS Client display` screen." msgstr "" #: ../../content/applications/productivity/iot/devices/screen.rst:-1 msgid "The default \"POS Client Display\" screen that appears when a screen display is successfully\n" -"connected to an IoT Box." +"connected to an IoT box." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:51 -msgid "The screen should also appear in the list of :guilabel:`Displays` on the :abbr:`IoT (Internet of Things)` Box homepage." +#: ../../content/applications/productivity/iot/devices/screen.rst:55 +msgid "The screen should also appear in the list of :guilabel:`Displays` on the :abbr:`IoT (Internet of Things)` box homepage. Alternatively, the display can be seen by accessing :menuselection:`IoT app --> Devices`." msgstr "" #: ../../content/applications/productivity/iot/devices/screen.rst:-1 -msgid "An example of a screen display name shown on the IoT Box homepage." +msgid "An example of a screen display name shown on the IoT Box Home Page." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:59 -msgid "If no screen is detected, a default display named :guilabel:`Distant Display` will be used instead." +#: ../../content/applications/productivity/iot/devices/screen.rst:64 +msgid "If no screen is detected, a default display named :guilabel:`Distant Display` will be displayed instead. This indicates that there is no hardware screen connected." msgstr "" #: ../../content/applications/productivity/iot/devices/screen.rst:0 msgid "The \"Distant Display\" screen name will be used if no screen is detected." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:67 +#: ../../content/applications/productivity/iot/devices/screen.rst:74 msgid "Usage" msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:70 -msgid "Show Point of Sales orders to customers" +#: ../../content/applications/productivity/iot/devices/screen.rst:77 +msgid "Show Point of Sale orders to customers" msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:72 -msgid "To use the screen in the :guilabel:`Point of Sale` app, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, open the desired screen, click on :guilabel:`Edit`, and enable the :guilabel:`IoT Box Devices` feature." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:76 -msgid "Now, select :guilabel:`IoT Box` in the drop-down menu and choose the screen in the :guilabel:`Customer Display` option. Then, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:0 -msgid "Connect the screen display to the Point of Sale app." +#: ../../content/applications/productivity/iot/devices/screen.rst:79 +msgid "To use the screen in the *Point of Sale app*, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, select a :abbr:`PoS (Point of Sale)`, click :guilabel:`Edit` if necessary, and enable the :guilabel:`IoT Box` feature." msgstr "" #: ../../content/applications/productivity/iot/devices/screen.rst:83 -msgid "The screen is now available for :abbr:`PoS (Point of Sale)` sessions. A \"screen\" icon will appear in the top bar to inform the connection status with the screen." +msgid "Next, select the screen from the :guilabel:`Customer Display` drop-down menu. Then click :guilabel:`Save`, if required." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:0 +#: ../../content/applications/productivity/iot/devices/screen.rst:-1 +msgid "Connect the screen display to the Point of Sale app." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:90 +msgid "The screen is now available for :abbr:`PoS (Point of Sale)` sessions. A screen icon will appear in the menu at the top of the screen to indicate the screen's connection status." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:-1 msgid "The \"screen\" icon on the Point of Sale display shows the connection status with the\n" "screen." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:91 -msgid "The screen will automatically show the :abbr:`PoS (Point of Sale)` orders and update when changes are performed on the order." +#: ../../content/applications/productivity/iot/devices/screen.rst:98 +msgid "The screen will automatically show the :abbr:`PoS (Point of Sale)` orders and update when changes are made to the order." msgstr "" #: ../../content/applications/productivity/iot/devices/screen.rst:-1 msgid "An example of a PoS order on a screen display." msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:99 -msgid "Display a website" +#: ../../content/applications/productivity/iot/devices/screen.rst:106 +msgid "Display a website on the screen" msgstr "" -#: ../../content/applications/productivity/iot/devices/screen.rst:101 -msgid "Opening the screen form view at :menuselection:`IoT --> Devices --> (screen device)` allows the user to choose a particular website URL to display on the screen with the :guilabel:`Screen URL` field." +#: ../../content/applications/productivity/iot/devices/screen.rst:108 +msgid "Open the screen form view by accessing :menuselection:`IoT app --> Devices --> Customer Display`. This allows the user to choose a particular website URL to display on the screen using the :guilabel:`Display URL` field." msgstr "" #: ../../content/applications/productivity/knowledge.rst:7 diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index dcec508c8..a1a652e2b 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: 2023-06-15 11:45+0000\n" +"POT-Creation-Date: 2023-07-03 09:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -58,6 +58,7 @@ msgstr "" #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:12 #: ../../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:11 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:13 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:12 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:16 @@ -77,7 +78,6 @@ msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:23 #: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:9 #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:9 -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:16 #: ../../content/applications/sales/subscriptions/closing.rst:31 #: ../../content/applications/sales/subscriptions/upselling.rst:25 msgid "Configuration" @@ -1836,46 +1836,66 @@ msgstr "" msgid "Creating a new payment method for a POS." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods.rst:21 -msgid "Selecting a :guilabel:`bank` journal automatically adds the :guilabel:`Use a Payment Terminal` field in which you can add your terminal's information." +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:18 +msgid "Selecting a :guilabel:`bank` journal automatically adds the :guilabel:`Use a Payment Terminal` field in which you can add your :doc:`payment terminal's information `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods.rst:23 -msgid "Credentials are mandatory to use a payment terminal. To learn how to configure the different terminals, check out the following documentation pages:" +msgid ":doc:`payment_methods/terminals`." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods.rst:26 -msgid ":doc:`Adyen configuration `" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/payment_methods.rst:27 -msgid ":doc:`Ingenico configuration `" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/payment_methods.rst:28 -msgid ":doc:`Six configuration `" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/payment_methods.rst:29 -msgid ":doc:`Stripe configuration `" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/payment_methods.rst:30 -msgid ":doc:`Vantiv configuration `" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/payment_methods.rst:31 -msgid ":doc:`Worldline configuration `" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/payment_methods.rst:33 -msgid "Once the payment method is created, you can select it to be used in your POS. To do so, go to the :ref:`POS settings `, select the POS for which you wish to make the payment method available in the :guilabel:`Point of Sale` field, and add the payment method(s) under the :guilabel:`Payment` section." +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:25 +msgid "Once the payment method is created, you can select it in your POS settings. To do so, go to the :ref:`POS' settings `, click :guilabel:`Edit`, and add the payment method under the :guilabel:`Payments` section." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:5 msgid "Payment terminals" msgstr "" +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:7 +msgid "Connecting and integrating a payment terminal with your POS system allows you to accept multiple payment options, including credit and debit cards, making the payment process more efficient." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:13 +msgid "Go to the :doc:`application settings <../configuration>`, scroll down to the :guilabel:`Payment Terminals` section, and tick your terminal's checkbox." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:-1 +msgid "checkbox in the settings to enable a payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:19 +msgid "Then, follow the corresponding documentation to configure your device:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:21 +msgid ":doc:`Adyen configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:22 +msgid ":doc:`Ingenico configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:23 +msgid ":doc:`SIX configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:24 +msgid ":doc:`Stripe configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:25 +msgid ":doc:`Vantiv configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:26 +msgid ":doc:`Worldline configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:28 +msgid "Once the terminal is configured, you can :doc:`create the corresponding payment method and add it to the POS <../payment_methods>`." +msgstr "" + #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:3 msgid "Adyen" msgstr "" @@ -4156,107 +4176,204 @@ msgid "Invoicing Method" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:3 -msgid "Request a down payment" +msgid "Down payments" msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:5 -msgid "A down payment is a partial payment made by the buyer when a sales contract is concluded. This implies both parties' full commitment (seller and buyer) to honor the contract. With a down payment, the buyers show their will to acquire the product and agree to pay the rest later, while the sellers are obliged to provide the goods by accepting it." +msgid "A down payment is a partial payment made by the buyer when a sales contract is concluded. This implies both parties' (seller and buyer) full commitment to honor the contract." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:10 -msgid "Sometimes a down payment is required for expensive orders or projects. That way, you can protect yourself and make sure that your customer is reliable." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:8 +msgid "With a down payment, the buyer pays a portion of the total amount owed while agreeing to pay the remaining amount at a later date. In turn, the seller provides goods or services to the buyer after accepting the down payment, trusting that the remaining amount will be paid later on." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:14 -msgid "First time you request a down payment" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:13 +msgid "Initial down payment request" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:16 -msgid "When a sales order is confirmed, you then have the possibility to create an invoice. Invoices are automatically created in drafts so that you can review them before validation. To create an invoice, Odoo Sales offers you 3 options:" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:15 +msgid "When a sales order is confirmed, the option to create an invoice becomes available, via the :guilabel:`Create Invoice` button, located in the upper-left corner of the sales order form. When clicked, a :guilabel:`Create invoices` pop-up appears." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:20 -msgid "Regular invoice" -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:21 -msgid "Down payment (percentage)" +msgid "Invoices are automatically created in drafts, so they can be reviewed before validation." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:22 -msgid "Down payment (fixed amount)" +msgid "On the :guilabel:`Create invoices` pop-up, there are 3 options to choose from in the :guilabel:`Create Invoice` field:" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:24 -msgid "In terms of down payment, it can either be a fixed amount or a percentage of the total amount. The first time you request a down payment, you can set a percentage or a fixed amount of your choice, and select the right income account and taxes. These settings will be reused for future down payments." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:27 +msgid ":guilabel:`Regular invoice`" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 -msgid "How can you do a down payment on Odoo Sales?" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:27 +msgid "If :guilabel:`Regular Invoice` is selected the other fields disappear, as they only pertain to down payment configurations." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:29 +msgid ":guilabel:`Down payment (percentage)`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:30 +msgid ":guilabel:`Down payment (fixed amount)`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:32 +msgid "In terms of a down payment, it can either be a fixed amount or a percentage of the total amount." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:34 -msgid "When you request your first down payment, a new product called **Down payment** will be created. This product will be registered as a **service** product with an invoicing policy of **ordered quantities**. As a reminder, you can edit this product and modify it at any time. Please note that if you choose **delivered quantities** as invoicing policy, **you will not be able to create an invoice**." +msgid "Once the desired down payment option is selected in the :guilabel:`Create Invoice` field, designate the desired amount (either as a percentage or fixed amount) in the :guilabel:`Down Payment Amount` field." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:41 -msgid "Basic sales flow using down payments" -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:43 -msgid "For this first example, we will use a 50% amount down payment with a product using **ordered quantities** as invoicing policy. Make sure to check out our documentation about invoicing policies here: :doc:`invoicing_policy` , before requesting your first down payment. When it comes to create and view the invoice, you will only have access to a draft invoice mentioning the down payment (as you can see below)." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:38 +msgid "Then, select the appropriate income account for the invoice in the :guilabel:`Income Account` field, and add a tax amount, if necessary, in the :guilabel:`Customer Taxes` field. These settings will be reused for future down payments." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 -msgid "What is a basic sales flow using down payments on Odoo Sales (1)?" +msgid "How to configure a down payment on Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:53 -msgid "There, you can post the invoice and register the payment of your customer. But, we all know that in real life this flow does not happen immediately. So, for now, you can return to the sales order. There, you will have the possibility to see the order as a customer with the **Customer preview** button or to reach easily the previous draft invoice with the **Invoice** button. In any case, the down payment will be mentioned on both (sales order and draft invoice)." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:47 +msgid "When a down payment is first requested, a new product called :guilabel:`Down payment` is created. This product is registered as a :guilabel:`Service` product, with an invoicing policy of :guilabel:`Ordered quantities`. This product can be edited and modified at any time." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:52 +msgid "If :guilabel:`Delivered quantities` is chosen as the invoicing policy, an invoice will **not** be able to be created." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:56 +msgid "Request a 50% down payment" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:58 +msgid "For the following example, the flow involves a 50% amount down payment on a product with :guilabel:`Ordered quantities` as the invoicing policy." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:62 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:184 +msgid ":doc:`/applications/sales/sales/invoicing/invoicing_policy`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:64 +msgid "When the order is confirmed (via the :guilabel:`Confirm` button), it's time to create/view the invoice, by clicking :guilabel:`Create Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:67 +msgid "Then, on the :guilabel:`Create invoices` pop-up window that appears, select :guilabel:`Down payment (percentage)`, and type `50` in the :guilabel:`Down Payment Amount` field. Lastly, click :guilabel:`Create and View Invoice` to create and view the invoice." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 -msgid "What is a basic sales flow using down payments on Odoo Sales (2)?" +msgid "Create invoices pop up window in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:63 -msgid "To complete the flow, when the customer wants to pay the rest of his sales order, you must create another invoice. Once again, you will have the choice to make another down payment or to deduct all the down payments and so, paying the rest of the invoice as a regular invoice." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:75 +msgid "Doing so reveals the draft invoice, which mentions the down payment." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 -msgid "What is a basic sales flow using down payments on Odoo Sales (3)?" +msgid "A sample draft invoice with down payment mentioned in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:71 -msgid "This flow is also possible with a down payment taking into account a fixed amount." -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:74 -msgid "Be careful that if you do a down payment with a product using **delivered quantities** as invoicing policy, you won’t be able to deduct all the down payments when it comes to invoicing your customer. Indeed, you have to deliver a product before creating the final invoice. If nothing has been delivered, you create a **credit note** that cancels the draft invoice created after the down payment. To do so, you have to install the **Inventory App** to confirm the delivery. Otherwise, you can enter the delivered quantity manually on the sales order." -msgstr "" - -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:82 -msgid "Modify the income account and customer taxes" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:81 +msgid "From there, the invoice can be confirmed/posted, and the payment can be registered. Return to the sales order, via the breadcrumbs." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:84 -msgid "From the products list, search for the **Down Payment** product." +msgid "On the sales order, the option to view what the customer will see is available, via the :guilabel:`Customer Preview` smart button, and the :guilabel:`Invoice` button reveals the drafted invoice. In either case, the down payment is mentioned on both the sales order and draft invoice." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 -msgid "Creation of a down payment product on Odoo Sales" +msgid "How the down payment is mentioned on the sales order in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:90 -msgid "You can edit it and under the **General Information Tab** you will be able to change the customer taxes. Now, to change the income account, you will need to install the **Accounting App** to have the possibility to see the **Accounting Tab** on the product form." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:92 +msgid "To confirm and register the first payment of the down payment, click the :guilabel:`Invoices` smart button to return to the invoice. On the :guilabel:`Customer Invoice` page, click :guilabel:`Confirm`, then :guilabel:`Register Payment` to open a :guilabel:`Register Payment` pop-up form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "How the register payment pop up looks in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:101 +msgid "On this form, select the appropriate :guilabel:`Journal` and confirm that the down payment amount is correct in the :guilabel:`Amount` field. Then, make any other modifications to the other fields, if necessary, before clicking :guilabel:`Create Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:105 +msgid "Odoo returns to the invoice, which now has a green :guilabel:`In Payment` banner visible in the upper-right corner." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "How the initial down payment invoice has a green paid banner in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:112 +msgid "Now, when the customer wants to pay the remaining amount of the order, another invoice must be created. To do that, return to the sales order, and click :guilabel:`Create Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:115 +msgid "On the :guilabel:`Create invoices` pop-up window, there is now an option to :guilabel:`Deduct down payments`, which is selected by default." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "The deduct down payment option on the create invoices pop up in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:122 +msgid "If the remaining amount is ready to be paid, the :guilabel:`Regular Invoice` option should be selected, and the :guilabel:`Deduct down payments` option should *stay* selected. Then, click :guilabel:`Create and View Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:126 +msgid "Doing so reveals a separate :guilabel:`Invoices` page, listing all the invoices for that specific sales order. Each invoice line item displays all the necessary information related to each invoice, along with the current :guilabel:`Payment Status`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "The down payment invoices page in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:134 +msgid "To complete the flow, select the invoice with the :guilabel:`Not Paid` status, which opens that invoice. On the invoice page, click :guilabel:`Confirm`, then :guilabel:`Register Payment`, and confirm that the remaining :guilabel:`Amount` is correct. Then, click :guilabel:`Create Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:138 +msgid "That pop-up window disappears, and a green :guilabel:`In Payment` banner is now present on the invoice. The line items on the invoice show that the total amount has been paid, including mentions of the down payment, and the flow is complete." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:142 +msgid "This flow is also possible with the :guilabel:`Fixed amount` down payment option." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:145 +msgid "If a down payment is used with a product that has a :guilabel:`Delivered quantities` invoicing policy, the down payments will **not** be able to be deducted when it comes time to invoice the customer. This is because, due to the invoicing policy, the product(s) would have to be delivered *before* creating the final invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:150 +msgid "If nothing has been delivered, a :guilabel:`Credit Note` is created, which cancels the draft invoice that was created after the down payment. To utilize the :guilabel:`Credit Note` option, the *Inventory* application must be installed, in order to confirm the delivery. Otherwise, the delivered quantity can be entered manually directly on the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:156 +msgid "Income account and customer taxes modifications" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:158 +msgid "To adjust the income account and customer taxes attached to a down payment, navigate to the :guilabel:`Products` page (:menuselection:`Sales app --> Products --> Products`), search for the `Down Payment` product in the search bar, and select it to reveal the product detail page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:162 +msgid "On the :guilabel:`Down Payment` product page, click :guilabel:`Edit`, then scroll down to the :guilabel:`General Information` tab. In this tab, the customer taxes can be modified in the :guilabel:`Customer Taxes` field." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 msgid "How to modify the income account link to down payments" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:99 -msgid ":doc:`invoicing_policy`" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:170 +msgid "To change or adjust the income account attached to the :guilabel:`Down Payment` product page, the *Accounting* app **must** be installed. With the *Accounting* app installed, the :guilabel:`Accounting` tab becomes available on the product page. That tab will **not** be accessible without the *Accounting* app installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:175 +msgid "In the :guilabel:`Accounting` tab, the income account can be changed in the :guilabel:`Income Account` field, in the :guilabel:`Receivables` section. Once all desired changes are complete, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/invoicing/expense.rst:3 @@ -4446,28 +4563,59 @@ msgid "You can then invoice that first milestone." msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:3 -#: ../../content/applications/sales/sales/invoicing/proforma.rst:22 -msgid "Send a pro-forma invoice" +msgid "Pro-forma invoices" msgstr "" #: ../../content/applications/sales/sales/invoicing/proforma.rst:5 -msgid "A pro-forma invoice is an abridged or estimated invoice in advance of a delivery of goods. It notes the kind and quantity of goods, their value, and other important information such as weight and transportation charges. Pro-forma invoices are commonly used as preliminary invoices with a quotation, or for customs purposes in importation. They differ from a normal invoice in not being a demand or request for payment." +msgid "A *pro-forma invoice* is an abridged or estimated invoice sent in advance of a delivery of goods. It notes the kind and quantity of goods, their value, and other important information, such as weight and transportation charges." msgstr "" -#: ../../content/applications/sales/sales/invoicing/proforma.rst:13 +#: ../../content/applications/sales/sales/invoicing/proforma.rst:9 +msgid "Pro-forma invoices are commonly used as preliminary invoices with a quotation. They are also used for customs purposes during importation. They differ from a normal invoice in that they are not a demand (or request) for payment." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:14 msgid "Activate the feature" msgstr "" -#: ../../content/applications/sales/sales/invoicing/proforma.rst:15 -msgid "Go to :menuselection:`SALES --> Configuration --> Settings` and activate the *Pro-Forma Invoice* feature." +#: ../../content/applications/sales/sales/invoicing/proforma.rst:16 +msgid "In order to utilize pro-forma invoices, the *Pro-Forma Invoice* feature **must** be activated. To do that, navigate to :menuselection:`Sales app --> Configuration --> Settings`, and in the :guilabel:`Quotations & Orders` section, click the checkbox next to :guilabel:`Pro-Forma Invoice`. Then, click :guilabel:`Save` to save all changes." msgstr "" -#: ../../content/applications/sales/sales/invoicing/proforma.rst:24 -msgid "From any quotation or sales order, you know have an option to send a pro-forma invoice." +#: ../../content/applications/sales/sales/invoicing/proforma.rst:-1 +msgid "The Pro-Forma Invoice feature setting in the Odoo Sales application." msgstr "" -#: ../../content/applications/sales/sales/invoicing/proforma.rst:30 -msgid "When you click on send, Odoo will send an email with the pro-forma invoice in attachment." +#: ../../content/applications/sales/sales/invoicing/proforma.rst:26 +msgid "Send a pro-forma invoice" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:28 +msgid "With the :guilabel:`Pro-Forma Invoice` feature activated, the option to send a pro-forma invoice is now available on any quotation or sales order, via the :guilabel:`Send Pro-Forma Invoice` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:-1 +msgid "The Send Pro-Forma Invoice button on a typical sales order in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:35 +msgid "When the :guilabel:`Send Pro-Forma Invoice` button is clicked, an email pop-up appears. The :guilabel:`Recipients` field is auto-populated with the customer from the sales order or quotation. Then, if needed, modify the :guilabel:`Subject` field and the body of the email. The pro-forma invoice is automatically added as an attachment to the email." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:40 +msgid "When ready, click :guilabel:`Send`, and Odoo instantly sends the email, with the attached pro-forma invoice, to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:-1 +msgid "The email pop-up window that appears with pro-forma invoice attached in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:48 +msgid "To preview what the pro-forma invoice looks like, click on the PDF at the bottom of the email pop-up window *before* clicking :guilabel:`Send`. When clicked, the pro-forma invoice is downloaded instantly. Open that PDF to view (and review) the pro-forma invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:0 +msgid "Sample pro-forma invoice PDF from Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/invoicing/time_materials.rst:3 @@ -4767,7 +4915,6 @@ msgid "The Odoo *Sales*, *eCommerce*, and *Point of Sale* applications allow use msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:11 -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:10 msgid "Configure the settings" msgstr "" @@ -5802,78 +5949,9 @@ msgstr "" #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:50 #: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:51 #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:65 -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:115 msgid ":doc:`quote_template`" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:3 -msgid "Deliver and invoice to different addresses" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:5 -msgid "People and businesses often use separate addresses for billing (invoicing) and shipping (delivery) purposes. With the Odoo *Sales* app, contacts can have different specified addresses for delivery and invoicing." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:12 -msgid "Go to :menuselection:`Invoicing --> Configuration --> Settings` and scroll down to the :guilabel:`Customer Invoices` section. Then, check the box next to :guilabel:`Customer Addresses`, and click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:17 -msgid "Navigating through the *Invoicing* app will not be possible if the *Accounting* app has been installed. Instead, go through :menuselection:`Accounting --> Configuration --> Settings` to enable the :guilabel:`Customer Addresses` feature." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:-1 -msgid "Activate the Customer Addresses setting." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:26 -msgid "Configure the contact form" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:28 -msgid "Navigate to the :menuselection:`Contacts` app (or to :menuselection:`Sales --> Orders --> Customers`), and click on a customer to open their contact form." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:31 -msgid "Under the :guilabel:`Contacts & Addresses` tab, click :guilabel:`Add`." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:-1 -msgid "Add a contact/address to the contact form" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:37 -msgid "Then, select which type of address to add to the contact form (i.e. :guilabel:`Invoice Address` or :guilabel:`Delivery Address`)." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:-1 -msgid "Create a new contact/address on a contact form." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:44 -msgid "Enter the address information. Then click :guilabel:`Save & Close` to save the address and close the :guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save this address and immediately input another one." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:49 -msgid "Add addresses to the quotation" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:51 -msgid "When a customer is added to a quotation, the :guilabel:`Invoice Address` and :guilabel:`Delivery Address` fields will autopopulate according to the addresses specified on the customer's contact form." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:-1 -msgid "Invoice and Delivery Addresses autopopulate on a quotation." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:59 -msgid "The :guilabel:`Invoice Address` and :guilabel:`Delivery Address` can also be edited directly from the quotation by clicking on the :guilabel:`Internal link` buttons next to each address line." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:62 -msgid "These addresses can be updated at any time to ensure accurate invoicing and delivery." -msgstr "" - #: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:3 msgid "Get paid to confirm an order" msgstr "" @@ -6112,217 +6190,99 @@ msgid "Line items for grid variants." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:3 -msgid "Use quotation templates" +msgid "Quotation templates" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:5 -msgid "By creating custom quotation templates, you will save a lot of time. Indeed, with the use of templates, you will be able to send complete quotations at a fast pace." +msgid "Using quotation templates speeds up the creation of sales orders by filling in most quotation fields automatically." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:11 -msgid "To enable this feature, go to :menuselection:`Sales --> Configuration --> Settings` and activate **Quotation Templates**." +msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and enable :guilabel:`Quotation Templates`." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "How to enable quotation templates on Odoo Sales?" +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:15 +msgid "Create a template" msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:19 -msgid "For even more convenience, it is also recommended to add the **Quotation Builder** feature which will help you design your quotation templates very easily. This option will automatically install the Odoo Website App." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:17 +msgid "Go to :menuselection:`Sales --> Configuration --> Quotations Templates` and click :guilabel:`New`." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "How to enable quotation builder on Odoo Sales?" +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:20 +msgid "Apart from the name, all template fields are optional." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:22 +msgid "After having named the template, choose default values for the following fields:" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:24 +msgid ":guilabel:`Quotation expires after`: choose the number of days for which the quotation is valid." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:25 +msgid ":guilabel:`Online confirmation`: after sending the quotation by email, it is possible to ask the customer to confirm it online on their customer portal:" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:28 +msgid "by providing a :guilabel:`Signature`," msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:29 -msgid "Create your first template" +msgid "by making a :guilabel:`Payment`," msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:31 -msgid "Quotation templates are under :menuselection:`Sales --> Configuration`." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:30 +msgid "or both." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:33 -msgid "You can create a new template or edit an existing one. Once named, you will be able to select products and quantities as well as the expiration time of the quotation." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:32 +msgid ":guilabel:`Confirmation Mail`: select an email template to automatically send an email to the customer upon confirming the quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:35 +msgid "On the :guilabel:`Lines` tab, add the default products and their quantity. Add :doc:`optional products ` in the :guilabel:`Optional Products` tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:38 +msgid "Finally, add any specific sales terms and conditions on the :guilabel:`Terms & Conditions` tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:41 +msgid "If the terms and conditions are standard across all quotations, :doc:`set them globally in the Accounting/Invoicing settings ` instead." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:46 +msgid "Design a template" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:48 +msgid "Customize the appearance of quotations on the customer portal by going to :menuselection:`Sales --> Configuration --> Settings` and enabling the :guilabel:`Quotation Builder` feature." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:52 +msgid "If necessary, Odoo automatically activates the :doc:`Website ` app when enabling this feature." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:55 +msgid "Select a template by going to :menuselection:`Sales --> Configuration --> Quotations Templates` and clicking on a template. Then click the :guilabel:`Design Template` button. On the website builder, click :guilabel:`Edit`. Drag and drop the building blocks, edit the content, and :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Create a new quotation template on Odoo Sales" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:42 -msgid "Design your template" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:44 -msgid "You will have the possibility to design your template and edit the customer interface in order to manage what clients will see before accepting and paying the quotation. For example, you will be able to describe your company, your services and your products. To do so, you can click on **Edit** and you will be brought to the quotation builder." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Design your quotation template on Odoo Sales" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:54 -msgid "You can easily edit the content of your template by dragging & dropping different building blocks to organize your quotation. For example, you can add a content block to describe your products." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Drag & drop building blocks to create your quotation template on Odoo Sales" +msgid "Using the quotation builder" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:63 -msgid "Use a quotation template" +msgid "Use a template" msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:65 -msgid "When creating a quotation, you can choose a specific template." +msgid "When creating a quotation, choose a template under the :guilabel:`Quotation Template` field. All the fields are then filled accordingly. Manually edit any pre-filled field if needed." msgstr "" -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Select a specific template on Odoo Sales" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:73 -msgid "You can select any template of your choice and suggest it as the default template in the **Sales** settings." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:77 -msgid "Confirm the quotation" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:79 -msgid "Templates facilitate the confirmation process by allowing customers to sign electronically or to pay online. You can activate these two options directly in the quotation template itself." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:-1 -msgid "Allow your customers to sign electronically or to pay online on Odoo Sales" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:88 -msgid "Every quotation will now have this setting. Of course you can always change it and make it specific for each quotation." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:92 -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:116 -msgid ":doc:`get_signature_to_validate`" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:93 -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:117 -msgid ":doc:`get_paid_to_validate`" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:3 -msgid "Add terms & conditions" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:5 -msgid "Specifying terms and conditions is essential to set out important contractual points such as payment terms, limitation of liability and delivery terms between customers and sellers. Every seller must declare all formal information concerning products and company policy. On the other hand, each customer must take note of all these conditions before committing to anything. With Odoo Sales, it is very easy to include your default terms and conditions on every quotation, sales order, and invoice that you manage." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:13 -msgid "Default Terms & Conditions" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:18 -msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` and activate *Default Terms & Conditions*." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1 -msgid "How to enable Default Terms & Conditions on Odoo Sales?" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:27 -msgid "Please note that this feature is activated via the settings of the **Invoicing App** and **not** via the settings of the **Sales App**. Moreover, you don't need to install the invoicing application since it is done automatically with the installation of the sales application." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:32 -msgid "DT&C on your quotations, sales orders, and invoices" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:34 -msgid "In the settings of the **Invoicing App**, you have the possibility to insert your default terms and conditions." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1 -msgid "Default Terms & Conditions on quotation on Odoo Sales" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:42 -msgid "They appear subsequently on every quotation, sales order, and invoice." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:45 -msgid "DT&C on your quotation templates" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:47 -msgid "According to your business needs, you can specify your terms and conditions on your quotation templates. This is interesting if you have different terms and conditions within your company." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1 -msgid "Add Default Terms & Conditions to your quotation templates on Odoo Sales" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:56 -msgid "Be sure to check out our documentation about quotation templates: :doc:`quote_template`, to master each step of this amazing feature." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:60 -msgid "General Terms & Conditions" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:63 -msgid "GT&C on your website" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:65 -msgid "Use the **Website App** and create your own general terms and conditions page. For example, here is the Odoo terms and conditions page:" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1 -msgid "General Terms & Conditions on your website" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:73 -msgid "You can refer to this page in the footer of all your documents. The layout is available in the **General Settings** under the **Business Documents** category. For example, this footer appears in every document from Odoo." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1 -msgid "General Terms & Conditions in your business documents" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:83 -msgid "GT&C as attachment in your emails" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:85 -msgid "Attach an external document with your general terms and conditions when you are about to send your quotation by email to your customers." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1 -msgid "General Terms & conditions as attachment in your email" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:94 -msgid "GT&C as attachment in your quotation templates" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:96 -msgid "Create and edit email templates to set a default attachment for all quotation emails that you will send in the future. To do so, you have to go to :menuselection:`Sales --> Configuration --> Quotation templates` and create a new quotation template or modify an existing one. Under the confirmation tab, you are now able to activate online signatures, online payments and to set a confirmation mail in which you have the possibility to configure the default attachment. There, you can put your general terms & conditions." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:-1 -msgid "General Terms & conditions as attachment in your quotation templates" -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:109 -msgid "To customize your email templates, activate the **developer mode** and go to :menuselection:`Settings --> Technical --> Email --> Templates`." -msgstr "" - -#: ../../content/applications/sales/sales/send_quotations/terms_and_conditions.rst:112 -msgid "With Odoo Sales it is now very simple to deal with terms & conditions." +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:69 +msgid "Go to :menuselection:`Sales --> Configuration --> Settings` to select a :guilabel:`Default Template`." msgstr "" #: ../../content/applications/sales/subscriptions.rst:5 @@ -6390,7 +6350,7 @@ msgid "Fill out the quotation normally, making sure to select a recurrence and a msgstr "" #: ../../content/applications/sales/subscriptions.rst:42 -msgid "You can define different invoice and delivery addresses by enabling the :doc:`Customer Addresses ` feature." +msgid "You can define different invoice and delivery addresses by enabling the :doc:`Customer Addresses ` feature." msgstr "" #: ../../content/applications/sales/subscriptions.rst:48 @@ -6763,7 +6723,7 @@ msgid "In the :guilabel:`Optional Products` tab, enter any optional products tha msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:77 -msgid "If the subscription plan has unique :doc:`terms and conditions `, add them in the :guilabel:`Terms & Conditions` tab. If terms conditions are specified on a plan, these will be used instead of the default terms and conditions set up in the *Sales* app settings." +msgid "If the subscription plan has unique :doc:`terms and conditions `, add them in the :guilabel:`Terms & Conditions` tab. If terms conditions are specified on a plan, these will be used instead of the default terms and conditions set up in the *Sales* app settings." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:-1 diff --git a/locale/sources/services.pot b/locale/sources/services.pot index a97ddcee8..5965978cf 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: 2023-06-02 08:43+0000\n" +"POT-Creation-Date: 2023-07-03 09:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -882,93 +882,6 @@ msgstr "" msgid "Overview" msgstr "" -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:3 -msgid "Forum and eLearning" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:6 -msgid "Forum" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:8 -msgid "To go above and beyond email, live chat, web forms, and phone lines, offer your customers a support forum. This way, customers might become more attached to your company as they would be investing time to get into details of your business. You also encourage the exchange of experiences and knowledge, supporting the feeling of belonging to a community (your community!)." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:14 -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:52 -msgid "Set up" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:16 -msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Team` and enable *Help Center*." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1 -msgid "Overview of the settings page of a helpdesk team emphasizing the help center feature in\n" -"Odoo Helpdesk" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:23 -msgid "Create, or edit a forum by clicking on the external link. Among the editing options, choose if you would like the *Forum Mode* to be *Questions*: only one answer is allowed per question or *Discussions*: multiple answers are allowed per question." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1 -msgid "Overview of a forum’s settings page in Odoo Helpdesk" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:31 -msgid "From now on, logged in users can start their discussions. To keep track of posts, go to :menuselection:`Website --> Forum --> Posts`." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1 -msgid "Overview of the Forums page of a website to show the available ones in Odoo Helpdesk" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:38 -msgid "Turn tickets into forum posts by simply clicking on *Share on the Forum* on the ticket's page." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:45 -msgid "eLearning" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:47 -msgid "In addition to a forum, offer online courses. When doing so, you link your customers and users’ needs and questions to useful content, helping to boost efficiency as they can also find their answers there." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:54 -msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *eLearning*." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1 -msgid "Overview of the settings page of a customer care team emphasizing the feature elearning in\n" -"Odoo Helpdesk" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:61 -msgid "Once the structure and content of your course are ready, *Publish* it by clicking on *Unpublished*." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1 -msgid "View of a course being published for Odoo Helpdesk" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:67 -msgid "To keep track of your course statistics, go to *eLearning* and *View Course*." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1 -msgid "View of the elearning applications dashboard for Odoo Helpdesk" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:73 -msgid "Todo" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:73 -msgid "DETAILS/INFO SHOULD COME FROM ELEARNING DOCS. THEREFORE, LINK DOCS ONCE AVAILABLE!" -msgstr "" - #: ../../content/applications/services/helpdesk/overview/getting_started.rst:3 msgid "Getting started with Helpdesk" msgstr "" @@ -1171,6 +1084,562 @@ msgstr "" msgid "Manually folding a stage from the kanban view will not close the tickets in the stage." msgstr "" +#: ../../content/applications/services/helpdesk/overview/help_center.rst:3 +msgid "Help center" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:5 +msgid "Odoo *Helpdesk* integrates with the *Forums*, *eLearning*, and *Knowledge* apps to create the *help center*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1 +msgid "Overview of the settings page of a team emphasizing the help center features." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:12 +msgid "The *help center* is a centralized location where teams and customers can search for and share detailed information about products and services." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:16 +msgid "In order to activate any of these features on a *Helpdesk* team, (*Forums*, *eLearning*, or *Knowledge*), the :guilabel:`Visibility` of the team has to be set to :guilabel:`Invited portal users and all internal users`. See :doc:`Getting Started ` for more information on *Helpdesk* team settings and configuration." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:23 +msgid "Since all of the *help center* features require integration with other applications, enabling any of them may result in the installation of additional modules or applications." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:26 +msgid "Installing a new application on a *One-App-Free* database will trigger a 15-day trial. At the end of the trial, if a paid subscription has not been added to the database, it will no longer be active or accessible." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:31 +msgid "Knowledge" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:33 +msgid "Odoo's *Knowledge* application is a collaborative library where users can store, edit, and share information. The *Knowledge* app is represented throughout the database by a *book* icon." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1 +msgid "View of a message in Helpdesk focusing on the Knowledge book icon." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:41 +msgid "Enable Knowledge on a Helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:43 +msgid "To enable the *Knowledge* feature on a *Helpdesk* team, go to :menuselection:`Helpdesk --> Configuration --> Teams` and select a team, or create a :doc:`new one `." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:47 +msgid "When a team has been selected or created, Odoo displays that team's detail form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:49 +msgid "On the team's detail form, scroll down to the :guilabel:`Self-Service` section. Click the box next to :guilabel:`Knowledge` to activate the *Knowledge* feature. When clicked, a new field labeled :guilabel:`Article` appears." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:53 +msgid "Clicking the :guilabel:`Article` field reveals a drop-down menu. At first, there is only one option in the drop-down menu titled :guilabel:`Help`, which Odoo provides by default. Select :guilabel:`Help` from the drop-down menu to choose this article." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:58 +msgid "To create a new article, go to the :menuselection:`Knowledge app`, then hover the cursor next to the :guilabel:`Workspace` section heading, located in the left sidebar. Moving the cursor there reveals a hidden :guilabel:`➕ (plus sign)` icon." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:62 +msgid "Click the :guilabel:`➕ (plus sign)` to create a new article in the :guilabel:`Workspace`. In the upper right corner of the page, click the :guilabel:`Share` button, and slide the :guilabel:`Share to Web` toggle switch until it reads :guilabel:`Article Published`. It can then be added to a *Helpdesk* team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:67 +msgid "Once an article has been created and assigned to a *Helpdesk* team, content can be added and organized through the *Knowledge* app." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:71 +msgid ":doc:`Editing Knowledge articles `" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:74 +msgid "Search articles from a Helpdesk ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:76 +msgid "When members of a *Helpdesk* team are trying to solve a ticket, they can search through the content in the *Knowledge* app for more information on the issue." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:79 +msgid "To search *Knowledge* articles, open a ticket — either from the *Helpdesk* app dashboard, or by going to :menuselection:`Helpdesk app --> Tickets --> All Tickets`, and selecting a :guilabel:`Ticket` from the list." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:83 +msgid "When a :guilabel:`Ticket` is selected, Odoo reveals that ticket's detail form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:85 +msgid "Click the :guilabel:`Knowledge (book)` icon, located above the chatter to open a search window." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1 +msgid "View of knowledge search window from a helpdesk ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:92 +msgid "*Knowledge* articles can also be searched by pressing :command:`Ctrl + K` to open the command palette, then typing :command:`?`, followed by the name of the desired article." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:95 +msgid "When Odoo reveals the desired article, click it, or highlight the :guilabel:`Article` title, and press :command:`Enter`. This will open the article in the :guilabel:`Knowledge` application." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:98 +msgid "To open the article in a new tab, press :command:`Ctrl + Enter`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:101 +msgid "If a more in-depth search is required, press :command:`Alt + B`. That will reveal a separate page, in which a more detailed search can occur." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:105 +msgid "Share articles to the help center" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:107 +msgid "In order for a *Knowledge* article to be available to customers and website visitors, it has to be published." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:111 +msgid "Even though the *Help* article has been enabled on a team, Odoo will not share all the nested articles to the web. Individual articles intended for customers **must** be published for them to be viewable on the website." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:115 +msgid "To publish an article, navigate to the desired article, by following the above steps, and click the :guilabel:`Share` icon in the upper-right corner. This will reveal a menu. Slide the toggle button labeled :guilabel:`Share to Web` to read :guilabel:`Article Published`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1 +msgid "View of a knowledge article focused on sharing and publishing options." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:124 +msgid "Solve tickets with templates" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:126 +msgid "*Template* boxes can be added to *Knowledge* articles to allow content to be reused, copied, sent as messages, or added to the description on a ticket. This allows teams to maintain consistency when answering customer tickets, and minimize the amount of time spent on responding to repeat questions." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:131 +msgid "Add templates to articles" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:133 +msgid "To create a template, go to :menuselection:`Knowledge --> Help`. Click on an existing nested article or create a new one by clicking the :guilabel:`➕ (plus sign)` icon next to *Help*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:136 +msgid "Type `/` to open the :guilabel:`Powerbox` and view a list of :doc:`commands `. Select or type `template`. A gray template block will be added to the page. Add any necessary content to this block." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1 +msgid "View of a template in knowledge with focus on send and copy options." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:145 +msgid "Templates will only display the :guilabel:`Use as description` or :guilabel:`Send as Message` options if they are accessed directly from *Helpdesk*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:149 +msgid "Use templates in tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:151 +msgid "Templates can be used to respond directly to a *Helpdesk* ticket as a message, or to add information to the ticket's description." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:154 +msgid "To use templates in a *Helpdesk* ticket, first, open a ticket, either from the :guilabel:`Helpdesk` dashboard or by going to :menuselection:`Helpdesk --> Tickets --> All Tickets` and selecting a :guilabel:`Ticket` from the list." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:158 +msgid "Click on the :guilabel:`Knowledge (book)` icon above the chatter for the ticket. This opens a search window. In this search window, select, or search for the desired article. Doing so reveals that article page in the Odoo *Knowledge* application." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:162 +msgid "To use a template to respond to a ticket, click :guilabel:`Send as message` in the upper right corner of the template box, located in the body of the article." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:165 +msgid "Doing so opens a :guilabel:`Compose email` pop-up window. In this window, select the recipients, make any necessary additions or edits to the template, then click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:169 +msgid "To use a template to add information to a ticket's description, click :guilabel:`Use as description` in the upper right corner of the template box, located in the body of the article. Doing so will not replace the existing text in a ticket's description. The template will be added as additional text." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:175 +msgid "Community Forum" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:177 +msgid "A *Community Forum* provides a space for customers to answer each other's questions and share information. By integrating a forum with a *Helpdesk* team, tickets submitted by customers can be converted to posts and shared." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:182 +msgid "Enable forums on a Helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:184 +msgid "To enable :guilabel:`Community Forums` on a *Helpdesk* team, start by navigating to :menuselection:`Helpdesk app --> Configuration --> Teams` and select a team, or create a :doc:`new one `." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:188 +msgid "Selecting or creating a team reveals that team's detail form. Scroll down to the :guilabel:`Self-Service` section of features, and enable :guilabel:`Community Forum`, by checking the box beside it." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:192 +msgid "When activated, a new field labeled :guilabel:`Forums` appears beneath." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:194 +msgid "Click the empty :guilabel:`Forums` field to reveal a drop-down menu. By default, there is only one option to begin with, labeled :guilabel:`Help`. That is the option Odoo automatically created when the :guilabel:`Community Forums` feature was enabled. Select :guilabel:`Help` from the drop-down menu to enable that forum." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:199 +msgid "To create a new forum, type a name into the blank :guilabel:`Forums` field, then click the :guilabel:`Create and Edit` option. Multiple forums can be selected in this field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:203 +msgid "Set up a forum" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:205 +msgid "The settings on a forum are managed through either the *Website* or *eLearning* applications. From the Odoo Dashboard, navigate to :menuselection:`Website --> Configuration --> Forums` or :menuselection:`eLearning --> Forum --> Forums`. In either case, select a forum to edit from the list." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:210 +msgid "On the forum detail form, select a mode." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:212 +msgid "The :guilabel:`Questions` mode allows for one answer/response for each post, while :guilabel:`Discussion` mode allows for multiple responses. To limit the forum to a single website, select it from the :guilabel:`Website` field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:216 +msgid "Under the :guilabel:`Order and Visibility` section, in the :guilabel:`Options` tab, choose how the posts should be sorted, by modifying the :guilabel:`Default Sort` field. Change the :guilabel:`Privacy` setting to change which users will have access to the forum." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:220 +msgid "Below these settings, there is space to add a description for the forum. This description will be visible on the website where the forum is published." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1 +msgid "Overview of a forum's settings page in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:228 +msgid "Karma gains and karma related rights" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:230 +msgid "When users interact on forums - either through posting questions, submitting answers, or upvoting responses - they earn points, called *karma*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:233 +msgid "Karma points are used to build the credibility of a user within the community. The more positive interactions a user has on the forum, the more karma points they gain. Certain activities, such as posting without validation, or editing posts, require users to have earned a specific level of karma points to prove their legitimacy and trustworthiness." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:238 +msgid "These figures can be adjusted on the :guilabel:`Karma gains` and :guilabel:`Karma related rights` tabs, located on the forums detail form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:243 +msgid "Karma gains" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:245 +msgid "In the :guilabel:`Karma gains` tab, there are listed actions that will cause users to gain (or lose) karma points. Those actions are:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:248 +msgid "Asking a question" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:249 +msgid "Question upvoted" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:250 +msgid "Question downvoted" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:251 +msgid "Answer upvoted" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:252 +msgid "Answer downvoted" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:253 +msgid "Accepting an answer" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:254 +msgid "Answer accepted" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:255 +msgid "Answer flagged" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:257 +msgid "Karma related rights" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:259 +msgid "In the :guilabel:`Karma related rights` tab, there are listed activities that users cannot complete, without having a specific level of karma points. Those activities are:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:262 +msgid "Ask questions" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:263 +msgid "Answer questions" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:264 +msgid "Upvote" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:265 +msgid "Downvote" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:266 +msgid "Edit own posts" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:267 +msgid "Edit all posts" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:268 +msgid "Close own posts" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:269 +msgid "Close all posts" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:270 +msgid "Delete own posts" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:271 +msgid "Delete all posts" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:272 +msgid "Nofollow links" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:273 +msgid "Accept an answer on own question" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:274 +msgid "Accept an answer to all questions" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:275 +msgid "Editor features: image and links" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:276 +msgid "Comment on own posts" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:277 +msgid "Comment on all posts" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:278 +msgid "Convert own answers to comments (and vice versa)" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:279 +msgid "Convert all answers to comments (and vice versa)" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:280 +msgid "Unlink own comments" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:281 +msgid "Unlink all comments" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:282 +msgid "Ask questions without validation" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:283 +msgid "Flag a post as offensive" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:284 +msgid "Moderate posts" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:285 +msgid "Change question tags" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:286 +msgid "Create new tags" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:289 +msgid "Create a forum post from a Helpdesk ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:291 +msgid "When a *Helpdesk* team has a *Forum* enabled, tickets submitted to that team can be converted to forum posts." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:294 +msgid "To do that, select a ticket, either from a team's pipeline or from :menuselection:`Tickets --> All Tickets` in the :guilabel:`Helpdesk` application." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:297 +msgid "At the top of the ticket detail form, click the :guilabel:`Share on Forum` button." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1 +msgid "Overview of the Forums page of a website to show the available ones in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:303 +msgid "When clicked, a pop-up appears. Here, the post and title can be edited to correct any typos, or modified to remove any proprietary or client information. :guilabel:`Tags` can also be added to help organize the post in the forum, making it easier for users to locate during a search. When all adjustments have been made, click :guilabel:`Create and View Post`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:309 +msgid "eLearning" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:311 +msgid "Odoo *eLearning* courses offer customers additional training and content in the form of videos, presentations, and certifications/quizzes. Providing additional training enables customers to work through issues and find solutions on their own. They can also develop a deeper understanding of the services and products they are using." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:317 +msgid "Enable eLearning courses on a Helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:319 +msgid "To enable *eLearning* courses on a *Helpdesk* team, go to :menuselection:`Helpdesk --> Configuration --> Teams` and select a team, or create a :doc:`new one `." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:323 +msgid "On the team's settings page, scroll to the :guilabel:`Self-Service` section, and check the box next to :guilabel:`eLearning`. A new field will appear below, labeled :guilabel:`Courses`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:326 +msgid "Click the empty field next to :guilabel:`Courses` beneath the :guilabel:`eLearning` feature to reveal a drop-down menu. Select an available course from the drop-down menu, or type a title into the field, and click :guilabel:`Create and edit` to create a new course from this page. Multiple courses can be assigned to a single team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:332 +msgid "Create an eLearning course" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:334 +msgid "A new *eLearning* course can be created from the :guilabel:`Helpdesk` team's settings page, as in the step above, or from the *eLearning* app." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:337 +msgid "To create a course directly through the *eLearning* application, navigate to :menuselection:`eLearning --> New`. This reveals a blank course template that can be customized and modified as needed." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:341 +msgid "On the course template page, add a :guilabel:`Course Title`, and below that, :guilabel:`Tags`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:343 +msgid "Click on the :guilabel:`Options` tab. Under :guilabel:`Access Rights`, choose the :guilabel:`Enroll Policy`. This determines which users will be allowed to take the course. Under :guilabel:`Display`, choose the course :guilabel:`Type` and :guilabel:`Visibility`. The :guilabel:`Visibility` setting determines whether the course will be available to public site visitors or members." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:349 +msgid "Add content to an eLearning course" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:351 +msgid "To add content to a course, click the :guilabel:`Content` tab and select :guilabel:`Add Content`. Choose the :guilabel:`Content Type` from the drop-down menu and upload the file, or paste the link, where instructed. Click :guilabel:`Save` when finished. Click :guilabel:`Add Section` to organize the course in sections." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1 +msgid "View of a course being published for Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:361 +msgid "In order to add a certification to a course, go to :menuselection:`eLearning --> Configuration --> Settings`, check the box labeled :guilabel:`Certifications`, and :guilabel:`Save` to activate the setting." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:366 +msgid "`Odoo Tutorials: eLearning `_" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:369 +msgid "Publish an eLearning course" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:371 +msgid "To allow customers to enroll in a course, both the course and the contents need to be published." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:373 +msgid "If the course is published, but the contents of the course are not published, customers can enroll in the course on the website, but they won't be able to view any of the course content. Knowing this, it may be beneficial to publish the course first if the course contents are intended to be released over time, such as classes with a weekly schedule." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:378 +msgid "To make the entire course available at once, each piece of course content must be published first, then the course can be published." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:381 +msgid "To publish a course, choose a course from the *eLearning* dashboard. On the course template page, click the :guilabel:`Go to Website` smart button." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:384 +msgid "This will reveal the front end of the course's web page. At the top of the course web page, move the :guilabel:`Unpublished` toggle switch to :guilabel:`Published`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:388 +msgid "Publish eLearning course contents from the back-end" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:390 +msgid "To publish *eLearning* course content from the back-end, choose a course from the *eLearning* dashboard. On the course template page, click the :guilabel:`Published Contents` smart button." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:393 +msgid "Doing so reveals a separate page displaying all the published content related to that course. Remove the default :guilabel:`Published` filter from the search bar in the upper-right corner, to reveal all the content related to the course - even the non-published content." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:397 +msgid "Click the :guilabel:`≣ (List View)` icon in the upper-right corner, directly beneath the search bar to switch to list view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:400 +msgid "While in :guilabel:`List View`, there is a checkbox on the far left of the screen, above the listed courses, to the left of the :guilabel:`Title` column. When that checkbox is clicked, all the course contents are selected at once." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:404 +msgid "With all the course content selected, double click any of the boxes in the :guilabel:`Is Published` column. This reveals a pop-up window, asking for confirmation that all selected records are intended to be published. Click :guilabel:`OK` to automatically publish all course content." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:-1 +msgid "View of a course contents being published in Odoo Helpdesk back-end." +msgstr "" + #: ../../content/applications/services/helpdesk/overview/ratings.rst:3 msgid "Customer ratings" msgstr "" diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index e46db8930..5793bbb88 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: 2023-06-15 11:45+0000\n" +"POT-Creation-Date: 2023-07-03 09:37+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -349,6 +349,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:95 #: ../../content/applications/websites/website/configuration.rst:5 #: ../../content/applications/websites/website/configuration/cookies_bar.rst:24 +#: ../../content/applications/websites/website/configuration/recaptcha.rst:16 #: ../../content/applications/websites/website/reporting/link_tracker.rst:10 msgid "Configuration" msgstr "" @@ -1772,107 +1773,335 @@ msgid "Live Chat" msgstr "" #: ../../content/applications/websites/livechat.rst:8 -msgid "Live Chat has the highest satisfaction rating of any communication tool. It allows fast responses and it is accessible and convenient, as your customers can keep doing what they are doing while interacting with you. Remember: your customers want to talk to you, so let's make it easy." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:13 -msgid "`Live Chat: product page `_" +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 -msgid ":doc:`livechat/ratings`" +msgid "Enable Live Chat" msgstr "" -#: ../../content/applications/websites/livechat.rst:15 -msgid ":doc:`livechat/responses`" +#: ../../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." msgstr "" -#: ../../content/applications/websites/livechat.rst:18 -msgid "Set up" +#: ../../content/applications/websites/livechat.rst:19 +msgid "Go to :menuselection:`Apps --> Live Chat` and click :guilabel:`Install`." msgstr "" #: ../../content/applications/websites/livechat.rst:20 -msgid "Once *Live Chat* is installed on your database, if your website was created with Odoo, the application is automatically added to it. All that is left to do is to go to :menuselection:`Website --> Configuration --> Settings --> Live Chat`." +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`." msgstr "" #: ../../content/applications/websites/livechat.rst:-1 -msgid "View of the settings page and the live chat feature for Odoo Live Chat" +msgid "View of the settings page and the live chat feature for Odoo Live Chat." msgstr "" #: ../../content/applications/websites/livechat.rst:28 -msgid "Select the channel to be linked to your website or create one on the fly." +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" +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." 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:33 -msgid "For both scenarios, under:" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:36 -msgid "- **Operators**: add agents to respond to the chat requests. Add as many as you like, and keep in mind that operators that do not show any activity in Odoo for more than 30min are considered disconnected." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:39 -msgid "- **Options**: set the default text to be shown on the live chat button; an automated welcome message to be seen by visitors when a conversation is initiated, and the text that prompts the user to initiate a chat." +msgid "View of a live chat channel form for Odoo Live Chat." msgstr "" #: ../../content/applications/websites/livechat.rst:42 -msgid "- **Channel Rules**: choose an action for a given URL, and/or per country. In the example below, the chat window automatically pops-up 3 seconds after users (from any country) land on the contact us page." +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:-1 -msgid "View of a channel’s rules form for Odoo Live Chat" +#: ../../content/applications/websites/livechat.rst:46 +msgid "Operators" msgstr "" #: ../../content/applications/websites/livechat.rst:48 -msgid "GeoIP, which refers to the process of finding a computer terminal’s geographical location by its IP address, must be installed on your server. Otherwise, under *Channel Rules*, countries are not taken into account." +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." msgstr "" -#: ../../content/applications/websites/livechat.rst:53 -msgid "External options" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:56 -msgid "If your website was not created with Odoo, you can find the code to be added to your own, under the *Widget* tab." +#: ../../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 "Odoo also offers an URL you can send to users so they can have access to a single live chat page." +msgid "The user who originally created the live chat channel will be added as an operator by default." msgstr "" -#: ../../content/applications/websites/livechat.rst:-1 -msgid "View of the widget tab for Odoo Live Chat" +#: ../../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." msgstr "" -#: ../../content/applications/websites/livechat.rst:63 -msgid "Managing chat requests" +#: ../../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`." msgstr "" -#: ../../content/applications/websites/livechat.rst:65 -msgid "Conversations initiated by visitors pop up as a direct message, and are shown in *Discuss*. Therefore, inquiries can be answered wherever you are in Odoo." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:-1 -msgid "View of the discuss application with a message sent through live chat in Odoo" +#: ../../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)." msgstr "" #: ../../content/applications/websites/livechat.rst:72 -msgid "Conversations are dispatched based on the current workload of the online operators." +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:75 -msgid "Leave or join a channel" +#: ../../content/applications/websites/livechat.rst:78 +msgid "Options" msgstr "" -#: ../../content/applications/websites/livechat.rst:77 -msgid "Go to :menuselection:`Website --> Configuration --> Settings`, access your channel under *Live Chat*, and *Join Channel* or *Leave Channel*." +#: ../../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." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:84 +msgid "Livechat button" +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 a channel form and the option to join a channel for Odoo Live Chat" +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." +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." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:106 +msgid "Livechat window" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:108 +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." +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." +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." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:124 +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" +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)." +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." +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 +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`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:148 +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" +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." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:178 +msgid "Country" +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." +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 `." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:191 +msgid "Widget" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:193 +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." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:197 +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." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:201 +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:204 +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." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:-1 +msgid "View of the widget tab for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:213 +msgid "Participate in a conversation" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:215 +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:220 +msgid "Set an online chat name" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:222 +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:225 +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 "" + +#: ../../content/applications/websites/livechat.rst:-1 +msgid "View of the My Profile option in Odoo." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:234 +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:238 +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 "" + +#: ../../content/applications/websites/livechat.rst:0 +msgid "View of user profile in Odoo, emphasizing the Online Chat name field." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:247 +msgid "Join or leave a channel" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:249 +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:252 +msgid "Any channel where the user is currently active will show 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:260 +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:264 +msgid "Manage live chat requests" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:266 +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:271 +msgid "Conversations can also be accessed by clicking the :guilabel:`Conversations` 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:278 +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 "" + +#: ../../content/applications/websites/livechat.rst:-1 +msgid "View of the discuss application with a message sent through live chat in Odoo." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:285 +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:289 +msgid ":doc:`Get Started with Discuss `" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:290 +msgid ":doc:`/applications/websites/livechat/responses`" msgstr "" #: ../../content/applications/websites/livechat/ratings.rst:3 @@ -1936,83 +2165,239 @@ msgid ":doc:`responses`" msgstr "" #: ../../content/applications/websites/livechat/responses.rst:3 -msgid "Commands and Canned Responses" +msgid "Commands and canned responses" msgstr "" #: ../../content/applications/websites/livechat/responses.rst:5 -msgid "Using canned responses can help you save time and have a previous, well-thought response, to some of your most common questions and comments." -msgstr "" - -#: ../../content/applications/websites/livechat/responses.rst:9 -msgid "Use commands" +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." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:11 -msgid "Commands are shortcuts that do specific actions within the chat window:" -msgstr "" - -#: ../../content/applications/websites/livechat/responses.rst:13 -msgid "**/help**: shows a help message." -msgstr "" - -#: ../../content/applications/websites/livechat/responses.rst:14 -msgid "**/helpdesk**: creates a helpdesk ticket." +msgid "Both commands and canned responses save time, and allow users to maintain a level of consistency throughout their conversations." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:15 -msgid "**/helpdesk_search**: searches for a helpdesk ticket." -msgstr "" - -#: ../../content/applications/websites/livechat/responses.rst:16 -msgid "**/history**: shows the last 15 visited pages." +msgid "Execute a command" msgstr "" #: ../../content/applications/websites/livechat/responses.rst:17 -msgid "**/lead**: creates a new lead." +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." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:18 -msgid "**/leave**: leaves the channel." -msgstr "" - -#: ../../content/applications/websites/livechat/responses.rst:0 -msgid "- For *helpdesk tickets*: make sure the application is installed on your database and the option *Live Chat* under :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` is enabled." -msgstr "" - -#: ../../content/applications/websites/livechat/responses.rst:0 -msgid "- For *leads*: the *CRM* application must be installed on your database." -msgstr "" - -#: ../../content/applications/websites/livechat/responses.rst:26 -msgid "To access the ticket or lead created from the chat, click on the shortcut link." +#: ../../content/applications/websites/livechat/responses.rst:21 +msgid "Commands, and the resulting actions, are only visible in the conversation window for the live chat operator. A customer will not see any commands that an operator uses in a conversation from their view of the chat." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:-1 -msgid "View of the chat window with a helpdesk ticket created in Odoo Live Chat" +msgid "View of the chat window with a helpdesk ticket created in Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:33 -msgid "Helpdesk tickets created from the chat automatically add the conversation as a description of the ticket. The same goes for the creation of a lead." +#: ../../content/applications/websites/livechat/responses.rst:29 +msgid "More information about each available command can be found below." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:32 +msgid "Help" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:34 +msgid "If an operator types `/help` in the chat window, an informative message that includes the potential entry types an operator can make is displayed." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:37 -msgid "Send canned responses" +msgid "Type `@username` to mention a user in the conversation. A notification will be sent to that user's inbox or email, depending on their notification settings." +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 "Canned responses allow you to have a full piece of text being placed when you type a shortcut word. To create them, go to :menuselection:`Live Chat --> Configuration --> Canned Responses`." +msgid "Type `/command` to execute a command." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:41 -msgid "To use them during a conversation, simply type **:** followed by the shortcut word you created." +msgid "Type `:shortcut` to insert a :ref:`canned response `." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:-1 -msgid "View of a chat window and the use of a canned response in Odoo Live Chat" +msgid "View of the message generated from using the /help command in Odoo Live Chat." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:48 -msgid ":doc:`ratings`" +msgid ":doc:`/applications/productivity/discuss/overview/get_started`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:49 +msgid ":doc:`/applications/productivity/discuss/overview/team_communication`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:52 +msgid "Helpdesk & Helpdesk search" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:54 +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`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:64 +msgid "Create a ticket from a live chat" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:66 +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:69 +msgid "After entering the `/helpdesk` command, type a title for the ticket into the chat window, then press `Enter`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:-1 +msgid "View of the results from a helpdesk search in a Live Chat conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:76 +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:80 +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:83 +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:88 +msgid "Search for a ticket from a live chat" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:90 +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:93 +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:102 +msgid "Results from the search command will only be seen by the operator, not the customer." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:105 +msgid "History" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:107 +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)." +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:115 +msgid "Lead" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:117 +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:124 +msgid "The `/lead` command can only be used if the *CRM* app has been installed." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:126 +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:131 +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:133 +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:136 +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:140 +msgid "Leave" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:142 +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:147 +msgid ":doc:`/applications/sales/crm/acquire_leads`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:148 +msgid ":doc:`/applications/services/helpdesk/overview/getting_started`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:153 +msgid "Canned responses" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:155 +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." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:160 +msgid "Create canned responses" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:162 +msgid "To create a new canned response, go to :menuselection:`Live Chat app --> Configuration --> Canned Responses --> New`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:165 +msgid "From here, type the shortcut command into the :guilabel:`Shortcut` field." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:167 +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:171 +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." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:175 +msgid "Use canned responses in a live chat conversation" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:177 +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:181 +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 "" + +#: ../../content/applications/websites/livechat/responses.rst:-1 +msgid "View of a chat window and the use of a canned response in Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:190 +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 "" + +#: ../../content/applications/websites/livechat/responses.rst:0 +msgid "View of a chat window and the list of available canned responses." msgstr "" #: ../../content/applications/websites/website.rst:8 @@ -2401,6 +2786,123 @@ msgstr "" msgid "The GeoIP database was unable to resolve the given IP address" msgstr "" +#: ../../content/applications/websites/website/configuration/recaptcha.rst:3 +msgid "reCAPTCHA v3 on forms" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:5 +msgid "Google's reCAPTCHA protects website forms against spam and abuse. It attempts to distinguish between human and bot submissions." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:9 +msgid "reCAPTCHA v3 works in the background and does not interrupt visitors. However, if the check fails, visitors cannot submit the form." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:13 +msgid "`Google's reCAPTCHA v3 guide `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:19 +msgid "On Google" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:21 +msgid "Open `the reCAPTCHA website registration page `_. Log in or create a Google account if necessary." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:24 +msgid "On the website registration page:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:26 +msgid "Give the website a :guilabel:`Label`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:27 +msgid "Leave the :guilabel:`reCAPTCHA type` on :guilabel:`Score based (v3)`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:28 +msgid "Enter one or more :guilabel:`Domains` (e.g., *example.com* or *subdomain.example.com*)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:29 +msgid "Under :guilabel:`Google Cloud Platform`, a project is automatically selected if one was already created with the logged-in Google account. If not, one is automatically created. Click :guilabel:`Google Cloud Platform` to select a project yourself or rename the automatically created project." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:33 +msgid "Agree to the terms of service." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:34 +msgid "Click :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:-1 +msgid "reCAPTCHA website registration example" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:39 +msgid "A new page with the generated keys is then displayed. Leave it open for convenience, as copying the keys to Odoo is required next." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:43 +msgid "On Odoo" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:45 +msgid "From the database dashboard, click :guilabel:`Settings`. Under :guilabel:`Integrations`, enable :guilabel:`reCAPTCHA` if needed." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:49 +msgid "Do not disable the :guilabel:`reCAPTCHA` feature or uninstall the :guilabel:`Google reCAPTCHA integration` module, as many other modules would also be removed." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:52 +msgid "Open the Google reCAPTCHA page, copy the :guilabel:`Site key`, and paste it into the :guilabel:`Site Key` field in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:54 +msgid "Open the Google reCAPTCHA page, copy the :guilabel:`Secret key`, and paste it into the :guilabel:`Secret Key` field in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:56 +msgid "Change the default :guilabel:`Minimum score` (`0.5`) if necessary, using a value between `1.0` and `0.0`. The higher the threshold is, the more difficult it is to pass the reCAPTCHA, and vice versa." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:59 +#: ../../content/applications/websites/website/configuration/translate.rst:95 +msgid "Click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:61 +msgid "All pages using the :guilabel:`Form`, :guilabel:`Newsletter Block`, :guilabel:`Newsletter Popup` snippets, and the eCommerce :guilabel:`Extra Step During Checkout` form are now protected by reCAPTCHA." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:66 +msgid "If the reCAPTCHA check fails, the following error message is displayed:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:0 +msgid "Google reCAPTCHA verification error message" +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:71 +msgid "reCAPTCHA v3 is free for up to `1 million assessments per month `_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:74 +msgid "Analytics and additional settings are available on `Google's reCAPTCHA administration page `_. For example, you can receive email alerts if Google detects suspicious traffic on your website or view the percentage of suspicious requests, which could help you determine the right minimum score." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:79 +msgid "You can notify visitors that reCAPTCHA protects a form. To do so, open the website editor and navigate to the form. Then, click somewhere on the form, and on the right sidebar's :guilabel:`Customize` tab, toggle :guilabel:`Show reCAPTCHA Policy` found under the :guilabel:`Form` section." +msgstr "" + +#: ../../content/applications/websites/website/configuration/recaptcha.rst:0 +msgid "reCAPTCHA policy message displayed on a form" +msgstr "" + #: ../../content/applications/websites/website/configuration/translate.rst:3 msgid "Translations" msgstr "" @@ -2537,10 +3039,6 @@ msgstr "" msgid "Add a language selector menu." msgstr "" -#: ../../content/applications/websites/website/configuration/translate.rst:95 -msgid "Click :guilabel:`Save`." -msgstr "" - #: ../../content/applications/websites/website/configuration/unsplash.rst:3 msgid "Unsplash (free images)" msgstr ""