[I18N] *: export translations

closes odoo/documentation#5046

X-original-commit: 640b9f46e8
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>

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-07-03 09:37+0000\n"
+"POT-Creation-Date: 2023-07-07 11:55+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -1709,6 +1709,7 @@ msgid ":doc:`../../applications/general/email_communication/email_servers`"
 msgstr ""
 
 #: ../../content/administration/maintain/domain_names.rst:3
+#: ../../content/administration/maintain/odoo_online.rst:70
 msgid "Domain names"
 msgstr ""
 
@@ -2893,66 +2894,54 @@ msgid "Odoo Online database management"
 msgstr ""
 
 #: ../../content/administration/maintain/odoo_online.rst:5
-msgid "To manage a database, sign in to https://www.odoo.com and access the `database management page <https://www.odoo.com/my/databases>`_ by clicking on the user icon, then on :guilabel:`My Databases`."
+msgid "To manage a database, go to the `database manager <https://www.odoo.com/my/databases>`_ and sign in as the database administrator."
+msgstr ""
+
+#: ../../content/administration/maintain/odoo_online.rst:8
+msgid "All the main database management options are available by clicking the database name, except the upgrade option, which can be accessed by clicking the **arrow in a circle** icon next to the database name. It is only displayed if an upgrade is available."
 msgstr ""
 
 #: ../../content/administration/maintain/odoo_online.rst:-1
-msgid "Clicking on the user icon opens a drop-down menu. \"My databases\" button is highlighted."
+msgid "Accessing the database management options"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:14
-msgid "Make sure to connect as the administrator of the database that changes will be made on."
-msgstr ""
-
-#: ../../content/administration/maintain/odoo_online.rst:-1
-msgid "Clicking on the gear icon opens the drop-down menu."
-msgstr ""
-
-#: ../../content/administration/maintain/odoo_online.rst:20
-msgid "Open the drop-down menu next to the database that changes will be made on by clicking on the gear icon."
-msgstr ""
-
-#: ../../content/administration/maintain/odoo_online.rst:23
-msgid "Several actions are available:"
-msgstr ""
-
-#: ../../content/administration/maintain/odoo_online.rst:25
+#: ../../content/administration/maintain/odoo_online.rst:15
 msgid ":ref:`odoo_online/upgrade`"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:26
+#: ../../content/administration/maintain/odoo_online.rst:16
 msgid ":ref:`odoo_online/duplicate`"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:27
+#: ../../content/administration/maintain/odoo_online.rst:17
 msgid ":ref:`odoo_online/rename`"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:28
+#: ../../content/administration/maintain/odoo_online.rst:18
 msgid ":ref:`odoo_online/download`"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:29
+#: ../../content/administration/maintain/odoo_online.rst:19
 msgid ":ref:`odoo_online/domains`"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:30
+#: ../../content/administration/maintain/odoo_online.rst:20
 msgid ":ref:`odoo_online/tags`"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:31
+#: ../../content/administration/maintain/odoo_online.rst:21
 msgid ":ref:`odoo_online/delete`"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:32
+#: ../../content/administration/maintain/odoo_online.rst:22
 msgid ":ref:`odoo_online/contact-support`"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:33
+#: ../../content/administration/maintain/odoo_online.rst:23
 msgid ":ref:`odoo_online/users`"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:38
+#: ../../content/administration/maintain/odoo_online.rst:28
 #: ../../content/administration/odoo_sh/getting_started/branches.rst:293
 #: ../../content/administration/odoo_sh/getting_started/settings.rst:77
 #: ../../content/administration/odoo_sh/getting_started/settings.rst:113
@@ -2960,157 +2949,133 @@ msgstr ""
 msgid "Upgrade"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:40
-msgid "If the database is *not* on the latest **Online version**, the administrator should receive an invitation to :doc:`upgrade <../upgrade>` the database. A :guilabel:`Rolling Release`` button on the database's main screen proposes an upgrade to the latest version (e.g., 14.0 to 16.1)."
+#: ../../content/administration/maintain/odoo_online.rst:30
+msgid "Trigger a database upgrade."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:0
-msgid "**If the Odoo database's version is lower than the latest major release:**"
+#: ../../content/administration/maintain/odoo_online.rst:33
+msgid "For more information about the upgrade process, check out the :doc:`Odoo Online upgrade documentation <../upgrade/odoo_online>`."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:0
-msgid "The database must be upgraded within two months. After these two months, an automatic upgrade is initiated."
-msgstr ""
-
-#: ../../content/administration/maintain/odoo_online.rst:0
-msgid "**If the Odoo database's version is equal to or higher than the latest major release:**"
-msgstr ""
-
-#: ../../content/administration/maintain/odoo_online.rst:0
-msgid "Disregard the invitation to upgrade as the database probably wouldn't benefit from new features every two months."
-msgstr ""
-
-#: ../../content/administration/maintain/odoo_online.rst:53
-msgid "Versions that are not supported anymore become deprecated and need to be updated to avoid security issues. Odoo recommends that the company initiate the upgrade, as this method allows for the company to request a test upgrade of the database to check for any discrepancies."
-msgstr ""
-
-#: ../../content/administration/maintain/odoo_online.rst:58
-msgid ":doc:`../upgrade`"
-msgstr ""
-
-#: ../../content/administration/maintain/odoo_online.rst:59
-msgid ":doc:`supported_versions`"
-msgstr ""
-
-#: ../../content/administration/maintain/odoo_online.rst:64
+#: ../../content/administration/maintain/odoo_online.rst:39
 msgid "Duplicate"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:66
-msgid "This allows to make an exact copy of the database to be able to perform testing without compromising the daily operations."
+#: ../../content/administration/maintain/odoo_online.rst:41
+msgid "Create an exact copy of the database, which can be used to perform testing without compromising daily operations."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:70
-msgid "By checking :guilabel:`For testing purposes`, all external communication (emails, payments, delivery orders, etc.) are disabled by default on the duplicated database."
+#: ../../content/administration/maintain/odoo_online.rst:45
+msgid "By checking :guilabel:`For testing purposes`, all external actions (emails, payments, delivery orders, etc.) are disabled by default on the duplicated database."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:72
-msgid "Duplicate databases expire automatically after 15 days."
+#: ../../content/administration/maintain/odoo_online.rst:47
+msgid "Duplicated databases expire automatically after 15 days."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:77
+#: ../../content/administration/maintain/odoo_online.rst:52
 msgid "Rename"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:79
+#: ../../content/administration/maintain/odoo_online.rst:54
 msgid "Rename the database and its URL."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:84
+#: ../../content/administration/maintain/odoo_online.rst:59
 msgid "Download"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:86
-msgid "Instantly download a ZIP file with a backup of the database."
+#: ../../content/administration/maintain/odoo_online.rst:61
+msgid "Download a ZIP file containing a backup of the database."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:89
-msgid "Databases are backed up daily according to the `Odoo Cloud SLA <https://www.odoo.com/cloud-sla>`_."
+#: ../../content/administration/maintain/odoo_online.rst:64
+msgid "Databases are backed up daily as per the `Odoo Cloud Hosting SLA <https://www.odoo.com/cloud-sla>`_."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:95
-msgid "Domains"
+#: ../../content/administration/maintain/odoo_online.rst:72
+msgid "Use a custom :doc:`domain name <domain_names>` to access the database via another URL."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:97
-msgid "Configure custom domains to access the database via another URL."
+#: ../../content/administration/maintain/odoo_online.rst:75
+msgid "You can :ref:`register a domain name for free <domain-name/odoo-register>`."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:100
-msgid ":doc:`domain_names`"
-msgstr ""
-
-#: ../../content/administration/maintain/odoo_online.rst:105
+#: ../../content/administration/maintain/odoo_online.rst:80
 msgid "Tags"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:107
-msgid "Add tags to sort your databases out. You can search the tags in the search bar."
+#: ../../content/administration/maintain/odoo_online.rst:82
+msgid "Add tags to easily identify and sort your databases."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:112
+#: ../../content/administration/maintain/odoo_online.rst:85
+msgid "You can search for tags in the search bar."
+msgstr ""
+
+#: ../../content/administration/maintain/odoo_online.rst:90
 #: ../../content/administration/odoo_sh/getting_started/branches.rst:550
 msgid "Delete"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:114
+#: ../../content/administration/maintain/odoo_online.rst:92
 msgid "Delete a database instantly."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:117
-msgid "Deleting a database means that all data is permanently lost. The deletion is instant and for all users. It is recommended to create a backup of the database before deleting it."
+#: ../../content/administration/maintain/odoo_online.rst:95
+msgid "Deleting a database means that all data is permanently lost. The deletion is instant and applies to all users. It is recommended to create a backup of the database before deleting it."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:120
-msgid "Carefully read the warning message that pops up and proceed only if the implications of deleting a database are fully understood:"
+#: ../../content/administration/maintain/odoo_online.rst:98
+msgid "Carefully read the warning message and only proceed if the implications of deleting a database are fully understood."
 msgstr ""
 
 #: ../../content/administration/maintain/odoo_online.rst:-1
-msgid "A warning message is prompted before deleting a database."
+msgid "The warning message displayed before deleting a database"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:128
+#: ../../content/administration/maintain/odoo_online.rst:105
 msgid "Only an administrator can delete a database."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:129
-msgid "The database name is immediately available for a new database."
+#: ../../content/administration/maintain/odoo_online.rst:106
+msgid "The database name is immediately made available to anyone."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:130
-msgid "It is not possible to delete a database if it is expired or linked to a subscription. If needed, please get in touch with `Odoo Support <https://www.odoo.com/help>`_."
+#: ../../content/administration/maintain/odoo_online.rst:107
+msgid "Deleting a database if it has expired or is linked to a subscription is impossible. In that case, contact `Odoo Support <https://www.odoo.com/help>`_."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:136
-msgid "Contact Support"
+#: ../../content/administration/maintain/odoo_online.rst:113
+msgid "Contact us"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:138
-msgid "Access the Odoo `support page <https://www.odoo.com/help>`_ with your database's details already pre-filled."
+#: ../../content/administration/maintain/odoo_online.rst:115
+msgid "Access the `Odoo.com support page <https://www.odoo.com/help>`_ with the database's details already pre-filled."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:144
-msgid "Invite / Remove Users"
+#: ../../content/administration/maintain/odoo_online.rst:121
+msgid "Invite / remove users"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:146
-msgid "To invite users, fill out the email address of the new user and click on :guilabel:`Invite`. To add multiple users, click on :guilabel:`Add more users`."
+#: ../../content/administration/maintain/odoo_online.rst:123
+msgid "To invite users, fill out the new user's email address and click :guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`."
 msgstr ""
 
 #: ../../content/administration/maintain/odoo_online.rst:-1
-msgid "Clicking on \"Add more users\" adds additional email fields."
+msgid "Inviting a user on a database"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:153
-msgid "To remove users, select the users to remove and click on :guilabel:`Remove`."
+#: ../../content/administration/maintain/odoo_online.rst:129
+msgid "To remove users, select them and click :guilabel:`Remove`."
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:156
-msgid ":doc:`/applications/general/users/manage_users`"
+#: ../../content/administration/maintain/odoo_online.rst:132
+msgid ":doc:`../../applications/general/users/manage_users`"
 msgstr ""
 
-#: ../../content/administration/maintain/odoo_online.rst:157
-msgid ":doc:`/applications/general/users/delete_account`"
+#: ../../content/administration/maintain/odoo_online.rst:133
+msgid ":doc:`../../applications/general/users/delete_account`"
 msgstr ""
 
 #: ../../content/administration/maintain/on_premise.rst:3
@@ -6683,14 +6648,34 @@ msgid "The database manager page with an upgrade button next to the name of a da
 msgstr ""
 
 #: ../../content/administration/upgrade/odoo_online.rst:17
-msgid "Test database"
+msgid "If the database's version is **lower** than the latest major release: the database must be upgraded within two months. After these two months, an automatic upgrade is initiated."
 msgstr ""
 
 #: ../../content/administration/upgrade/odoo_online.rst:19
+msgid "If the database's version is **equal** to or **higher** than the latest major release: you can disregard the invitation to upgrade, as the database probably would not benefit from new features every two months."
+msgstr ""
+
+#: ../../content/administration/upgrade/odoo_online.rst:23
+msgid "If a database is *not* on the latest online version, its administrator should receive an invitation to upgrade on the database's dashboard, displayed as an **arrow in a circle**."
+msgstr ""
+
+#: ../../content/administration/upgrade/odoo_online.rst:-1
+msgid "Invitation to upgrade on the database dashboard."
+msgstr ""
+
+#: ../../content/administration/upgrade/odoo_online.rst:30
+msgid "Versions that are not supported anymore become deprecated and must be updated to avoid security issues. It is recommended to initiate the upgrade yourself and not wait for the automatic upgrade, as the former method allows you to request a test upgrade of the database to check for any discrepancies."
+msgstr ""
+
+#: ../../content/administration/upgrade/odoo_online.rst:36
+msgid "Test database"
+msgstr ""
+
+#: ../../content/administration/upgrade/odoo_online.rst:38
 msgid "Click on the **arrow in a circle** icon to start the upgrade process. On the :guilabel:`Upgrade your database` pop-up, select the version of Odoo that the platform will be upgraded to. In the :guilabel:`Email to notify` field, enter an email address that will receive email notifications about the database upgrade."
 msgstr ""
 
-#: ../../content/administration/upgrade/odoo_online.rst:24
+#: ../../content/administration/upgrade/odoo_online.rst:43
 msgid "There is also a :guilabel:`Purpose` section on the pop-up that is used to specify the reason for the upgrade. However, at this stage of the process, the only selectable option is :guilabel:`Test`, as Odoo requires users to create a test copy of the upgraded database before converting the actual database."
 msgstr ""
 
@@ -6698,7 +6683,7 @@ msgstr ""
 msgid "The \"Upgrade your database\" pop-up."
 msgstr ""
 
-#: ../../content/administration/upgrade/odoo_online.rst:33
+#: ../../content/administration/upgrade/odoo_online.rst:52
 msgid "After filling out the form, click the :guilabel:`Upgrade` button. The pop-up disappears and the database being upgraded shows a red :guilabel:`Upgrade in progress` tag next to its name. An email confirming that the upgrade is in progress is also sent to the email address specified on the pop-up."
 msgstr ""
 
@@ -6706,7 +6691,7 @@ msgstr ""
 msgid "The \"Upgrade in progress\" tag next to the database name."
 msgstr ""
 
-#: ../../content/administration/upgrade/odoo_online.rst:42
+#: ../../content/administration/upgrade/odoo_online.rst:61
 msgid "Once the upgrade is complete, a new test database appears on the `database manager <https://www.odoo.com/my/databases>`_ 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 ""
 
@@ -6714,23 +6699,27 @@ msgstr ""
 msgid "A test database on the database manager page."
 msgstr ""
 
-#: ../../content/administration/upgrade/odoo_online.rst:52
+#: ../../content/administration/upgrade/odoo_online.rst:71
 msgid "Except for being on the newer version of Odoo, the test database is an exact copy of the one being upgraded. It is important to do extensive testing in this database to ensure that the upgrade has not altered or corrupted any data, and that all workflows still proceed as expected."
 msgstr ""
 
-#: ../../content/administration/upgrade/odoo_online.rst:57
+#: ../../content/administration/upgrade/odoo_online.rst:76
 msgid "Production database"
 msgstr ""
 
-#: ../../content/administration/upgrade/odoo_online.rst:59
+#: ../../content/administration/upgrade/odoo_online.rst:78
 msgid "After confirming the integrity of the new version, return to the `database manager <https://www.odoo.com/my/databases>`_ 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
+#: ../../content/administration/upgrade/odoo_online.rst:83
 msgid "Select the :guilabel:`Production` option and then click :guilabel:`Upgrade` to begin the upgrade process. As before, a notification email is sent to the email address provided and a red :guilabel:`Upgrade in progress` tag appears next to the name of the database."
 msgstr ""
 
-#: ../../content/administration/upgrade/odoo_online.rst:68
+#: ../../content/administration/upgrade/odoo_online.rst:87
+msgid "The production database is then taken offline and will be upgraded automatically. The time it takes to upgrade the production database should be similar to the time that was necessary to upgrade the test database. Make sure to inform database users of the scheduled downtime."
+msgstr ""
+
+#: ../../content/administration/upgrade/odoo_online.rst:91
 msgid "After the upgrade is finished, the :guilabel:`Upgrade in progress` tag disappears and the database is upgraded to the version specified."
 msgstr ""
 

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-07-03 09:37+0000\n"
+"POT-Creation-Date: 2023-07-07 11:55+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"

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-07-03 09:37+0000\n"
+"POT-Creation-Date: 2023-07-07 11:55+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"

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-07-03 09:37+0000\n"
+"POT-Creation-Date: 2023-07-07 11:55+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -361,8 +361,8 @@ msgstr ""
 #: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:14
 #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:23
 #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:9
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:15
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:10
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:31
 msgid "Configuration"
 msgstr ""
 
@@ -2163,6 +2163,270 @@ msgstr ""
 msgid "Products"
 msgstr ""
 
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:3
+msgid "Replenish on order (MTO)"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:9
+msgid "*Replenish on order*, also known as *MTO* (make to order), is a replenishment strategy that creates a draft order for a product every time a sales order is created for it. For products that are purchased from a vendor, a request for quotation (RFQ) is created, while a sales order for a product manufactured in-house triggers the creation of a manufacturing order. The creation of a |RFQ| or manufacturing order occurs every time a sales order is created, regardless of the current stock level of the product being ordered."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:17
+msgid "Unarchive the Replenish on Order (MTO) route"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:19
+msgid "By default, Odoo sets the |MTO| route as *archived*. This is because |MTO| is a somewhat niche workflow that is only used by certain companies. However, it is easy to unarchive the route in just a few simple steps."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:23
+msgid "To do so, begin by navigating to :menuselection:`Inventory --> Configuration --> Routes`. On the :guilabel:`Routes` page, click the :guilabel:`Filters` button and select the :guilabel:`Archived` option. This shows all routes that are currently archived."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1
+msgid "The archived filter on the Routes page."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:31
+msgid "Enable the checkbox next to :guilabel:`Replenish on Order (MTO)`, then click the :guilabel:`Action` button to reveal a drop-down menu. From the drop-down menu, select :guilabel:`Unarchive`."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1
+msgid "The unarchive action on the Routes page."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:38
+msgid "Finally, remove the :guilabel:`Archived` filter from the :guilabel:`Search...` bar. The :guilabel:`Routes` page will now show all available routes, including :guilabel:`Replenish on Order (MTO)`, which is now selectable on the inventory tab of each product page."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1
+msgid "The MTO route appears on the Routes page after unarchiving it."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:47
+msgid "Configure a product to use the MTO route"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:49
+msgid "With the |MTO| route unarchived, products can now be properly configured to use replenish on order. To do so, begin by going to :menuselection:`Inventory --> Products --> Products`, then select an existing product, or click :guilabel:`Create` to configure a new one."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:53
+msgid "On the product page, select the :guilabel:`Inventory` tab and enable the :guilabel:`Replenish on Order (MTO)` route in the :guilabel:`Routes` section, along with one other route."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:57
+msgid "The :guilabel:`Replenish on Order (MTO)` route **does not** work unless another route is selected as well. This is because Odoo needs to know how to replenish the product when an order is placed for it (buy it, manufacture it, etc.)."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1
+msgid "Select the MTO route and a second route on the Inventory tab."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:65
+msgid "If the product is purchased from a vendor to fulfill sales orders, enable the :guilabel:`Can be Purchased` checkbox under the product name. Doing so makes the :guilabel:`Purchase` tab appear alongside the other settings tabs below."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:69
+msgid "Select the :guilabel:`Purchase` tab and specify a :guilabel:`Vendor` and the :guilabel:`Price` they sell the product for."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:-1
+msgid "Enable \"Can be Purchased\" and specify a vendor."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:76
+msgid "If the product is manufactured, make sure that it has a bill of materials (BOM) configured for it. To do so, click the :guilabel:`Bill of Materials` smart button at the top of the screen, then click :guilabel:`Create` on the :guilabel:`Bill of Materials` page to configure a new |BOM| for the product."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:81
+msgid "On the blank |BOM| form, add the components used to manufacture the product on the :guilabel:`Components` tab, along with the operations required for the manufacturing workflow on the :guilabel:`Operations` tab."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:85
+msgid "Finally, click :guilabel:`Save` to save the |BOM|."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:88
+msgid "Fulfill a sales order using the MTO route"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:90
+msgid "After configuring a product to use the |MTO| route, a replenishment order is created for it every time a sales order including the product is confirmed. The type of order created depends on the second route selected in addition to |MTO|."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:94
+msgid "For example, if *Buy* was the second route selected, then a purchase order is created upon confirmation of a sales order."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:98
+msgid "When the |MTO| route is enabled for a product, a replenishment order is always created upon confirmation of a sales order. This is the case even if there is enough stock of the product on-hand to fulfill the sales order, without buying or manufacturing additional units of it."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:102
+msgid "While the |MTO| route can be used in unison with a variety of other routes, the *Buy* route is used as the example for this workflow. Begin by navigating to the :menuselection:`Sales` app, then click :guilabel:`Create`, which opens a blank quotation form."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:106
+msgid "On the blank quotation form, add a :guilabel:`Customer`, then click :guilabel:`Add a product` under the :guilabel:`Order Lines` tab, and enter a product that has been configured to use the *MTO* and *Buy* routes. Click :guilabel:`Confirm` and the quotation is turned into a sales order."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:110
+msgid "A :guilabel:`Purchase` smart button now appears in the top-right corner of the sales order. Clicking it opens the |RFQ| associated with the sales order."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:113
+msgid "Click :guilabel:`Confirm Order` to confirm the |RFQ|, and turn it into a purchase order. A green :guilabel:`Receive Products` button now appears at the top of the purchase order. Once the products are received, click :guilabel:`Receive Products` to register them into inventory."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:117
+msgid "Return to the sales order by clicking the :guilabel:`SO` breadcrumb, or by navigating to :menuselection:`Sales --> Orders --> Orders`, and selecting the sales order."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/mto.rst:120
+msgid "Finally, click the :guilabel:`Delivery` smart button in the top-right of the order to be taken to the delivery order. Once the products have been shipped to the customer, click :guilabel:`Validate` to confirm the delivery."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:3
+msgid "Reordering rules"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:5
+msgid "Reordering rules are used to keep forecasted stock levels above a certain threshold without exceeding a specified upper limit. This is accomplished by specifying a minimum quantity that stock should not fall below and a maximum quantity that stock should not exceed."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:9
+msgid "Reordering rules can be configured for each product based on the route used to replenish it. If a product uses the *Buy* route, then a Request for Quotation (RFQ) is created when the reordering rule is triggered. If a product uses the *Manufacture* route, then a Manufacturing Order (MO) is created instead. This is the case regardless of the selected replenishment route."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:15
+msgid "Configure products for reordering rules"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:17
+msgid "In order to use reordering rules for a product, it must first be correctly configured. Begin by navigating to :guilabel:`Inventory --> Products --> Products`, then select an existing product, or create a new one by clicking :guilabel:`Create`."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:21
+msgid "First, on the :guilabel:`General Information` tab, make sure that the :guilabel:`Product Type` is set to :guilabel:`Storable Product`. This is necessary because Odoo only tracks stock quantities for storable products, and this number is used to trigger reordering rules."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1
+msgid "Set the Product Type as Storable."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:29
+msgid "Next, click on the :guilabel:`Inventory` tab and select one or more routes from the :guilabel:`Routes` section. Doing so tells Odoo which route to use to replenish the product."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1
+msgid "Select one or more routes on the Inventory tab."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:36
+msgid "If the product is reordered using the :guilabel:`Buy` route, confirm that the :guilabel:`Can be Purchased` checkbox is enabled under the product name. This makes the :guilabel:`Purchase` tab appear. Click on the :guilabel:`Purchase` tab, and specify at least one vendor, and the price that they sell the product for, so that Odoo knows which company the product should be purchased from."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1
+msgid "Specify a vendor and price on the Purchase tab."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:45
+msgid "If the product is replenished using the :guilabel:`Manufacture` route, it needs to have at least one Bill of Materials (BoM) associated with it. This is necessary because Odoo only creates manufacturing orders for products with a :abbr:`BoM (Bill of Materials)`."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:49
+msgid "If a :abbr:`BoM (Bill of Materials)` does not already exist for the product, select the :guilabel:`Bill of Materials` smart button at the top of the product form, then click :guilabel:`Create` to configure a new :abbr:`BoM (Bill of Materials)`."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1
+msgid "The Bill of Materials smart button on a product form."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:58
+msgid "Create new reordering rules"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:60
+msgid "To create a new reordering rule, navigate to :menuselection:`Inventory --> Configuration --> Reordering Rules`, then click :guilabel:`Create`, and fill out the new line as follows:"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:63
+msgid ":guilabel:`Product`: The product that is replenished by the rule."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:64
+msgid ":guilabel:`Location`: The location where the product is stored."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:65
+msgid ":guilabel:`Min Quantity`: The minimum quantity that can be forecasted without the rule being triggered. When forecasted stock falls below this number, a replenishment order for the product is created."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:68
+msgid ":guilabel:`Max Quantity`: The maximum quantity that stock is replenished up to."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:69
+msgid ":guilabel:`Multiple Quantity`: Specify if the product should be replenished in batches of a certain quantity (e.g., a product could be replenished in batches of 20)."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:71
+msgid ":guilabel:`UoM`: The unit of measure used for reordering the product. This value can simply be `Units` or a specific unit of measurement for weight, length, etc."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1
+msgid "The form for creating a new reordering rule."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:79
+msgid "Reordering rules can also be created from each product form. To do so, navigate to :menuselection:`Inventory --> Products --> Products`, then select a product. Click on :menuselection:`Reordering Rules --> Create`, then fill out the new line as detailed above."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:83
+msgid "Once a reordering rule has been created for a product, if its forecasted quantity is below the rule's minimum quantity when the scheduler runs, a replenishment order for the product is automatically generated. By default, the scheduler runs once each day."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:88
+msgid "To manually trigger a reordering rule before the scheduler runs, select :menuselection:`Inventory --> Operations --> Run Scheduler`. Then, select the green :guilabel:`Run Scheduler` button on the pop-up that appears. Be aware that this also triggers any other scheduled actions."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:92
+msgid "If the :guilabel:`Buy` route is selected, then an :abbr:`RFQ (Request for Quotation)` is generated. To view and manage :abbr:`RFQs (Requests for Quotation)`, navigate to :menuselection:`Purchase --> Orders --> Requests for Quotation`."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:96
+msgid "If the :guilabel:`Manufacture` route is selected, then an :abbr:`MO (Manufacturing Order)` is generated. To view and manage :abbr:`MOs (Manufacturing Orders)`, navigate to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:101
+msgid "Set a preferred route for reordering"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:103
+msgid "Odoo allows for multiple routes to be selected under the :guilabel:`Inventory` tab on each product form. For instance, it is possible to select both :guilabel:`Buy` and :guilabel:`Manufacture`, thus enabling the functionality of both routes."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:107
+msgid "Odoo also enables users to set a preferred route for a product's reordering rule. This is the route that the rule defaults to if multiple are selected. To select a preferred route, begin by navigating to :menuselection:`Inventory --> Configuration --> Reordering Rules`."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:111
+msgid "By default, the :guilabel:`Preferred Route` column is hidden on the :guilabel:`Reordering Rules` page. Enable it by selecting the :guilabel:`⋮ (three-dot)` option button on the right side of the page and checking the :guilabel:`Preferred Route` checkbox. Doing so reveals the :guilabel:`Preferred Route` column."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:116
+msgid "Click inside of the column on the row of a reordering rule and a drop-down menu shows all available routes for that rule. Select one to set it as the preferred route."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:-1
+msgid "Select a preferred route from the drop-down."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst:124
+msgid "If multiple routes are enabled for a product but no preferred route is set for its reordering rule, the product is reordered using the selected route that is listed first on the :guilabel:`Inventory` tab of the product form."
+msgstr ""
+
 #: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:3
 msgid "Selecting a replenishment strategy"
 msgstr ""
@@ -2322,18 +2586,18 @@ 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`."
+msgid "By default, the quantity in the :guilabel:`To Order` field is the quantity required to reach the set :guilabel:`Max Quantity`. However, the :guilabel:`To Order` quantity can be adjusted by clicking on the field and changing the value. To replenish a product manually, click :guilabel:`Order Once`."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:134
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:133
 msgid "To automate a replenishment from the :guilabel:`Replenishment` page, click :guilabel:`Automate Orders` on the right-side of the line, represented by a :guilabel:`🔄 (circular arrow)` icon."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:137
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:136
 msgid "When this button is clicked, Odoo will automatically generate a draft |PO|/|MO| every time the forecasted stock level falls below the set :guilabel:`Min Quantity` of the reordering rule."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:140
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:139
 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 ""
 
@@ -2341,7 +2605,7 @@ msgstr ""
 msgid "Snooze options to turn off notifications for reordering for a period of time."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:148
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:147
 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 ""
 
@@ -2349,63 +2613,59 @@ msgstr ""
 msgid "Quote request list shows which quotes are directly from the replenishment report."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:157
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:156
 msgid "Make to order (MTO) route"
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:159
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:158
 msgid "Since the |MTO| route is recommended for customized products, the route is hidden by default."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:168
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:167
 msgid "To activate the |MTO| route in Odoo:"
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:162
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:161
 msgid "Go to :menuselection:`Inventory app --> Configuration  --> Settings`."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:163
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:162
 msgid "Activate the :guilabel:`Multi-Step Routes` setting, located under the :guilabel:`Warehouse` section, and click :guilabel:`Save`."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:165
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:164
 msgid "Then, go to :menuselection:`Inventory app --> Configuration  --> Routes`."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:166
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:165
 msgid "Click on :menuselection:`Filters --> Archived` to show archived routes."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:167
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:166
 msgid "Select the checkbox next to :guilabel:`Replenish on Order (MTO)`, and click on :menuselection:`Action --> Unarchive`."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:171
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:170
 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`."
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:174
+msgid "To set a product's procurement route to |MTO|, go to :menuselection:`Inventory app --> Products --> Products`, and click on the desired product to open its product form."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:178
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:177
 msgid "Then, click the :guilabel:`Inventory` tab, and in the :guilabel:`Routes` section of options, select :guilabel:`Replenish on Order (MTO)`."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:181
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:180
 msgid "For products purchased directly from a vendor, make sure the :guilabel:`Buy` route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` route. Also, make sure a vendor is configured in the :guilabel:`Purchase` tab of the product form."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:185
+#: ../../content/applications/inventory_and_mrp/inventory/management/products/strategies.rst:184
 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 ""
 
@@ -7385,6 +7645,122 @@ msgstr ""
 msgid ":guilabel:`Performance`: the real duration of work time, shown as a percentage of the expected duration"
 msgstr ""
 
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:3
+msgid "Make work centers unavailable using Time Off"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:5
+msgid "In Odoo, *work centers* are used to carry out manufacturing operations at specific locations. However, if a work center cannot be used for some reason, work orders begin to pile up at the work center until it is operational again."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:9
+msgid "As a result, it is necessary to make the work center unavailable in Odoo so that the platform routes new work orders to alternative work centers that are operational. Using Odoo *Time Off*, it is possible to designate a work center as being unavailable for a set period of time. Doing so ensures that manufacturing operations can continue until the impacted work center is available again."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:17
+msgid "Before a work center can be designated as unavailable, the Odoo platform must be properly configured. First, it is necessary to enable :ref:`developer mode <developer-mode>`. This allows the :guilabel:`Time Off` smart button to appear on each work center's :guilabel:`Working Hours` pop-up window."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:22
+msgid "Enable developer mode by going to :menuselection:`Settings`, scrolling to the bottom of the page, and clicking :guilabel:`Activate the developer mode` under the :guilabel:`Developer Tools` heading."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1
+msgid "The \"Activate the developer mode\" button."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:29
+msgid "Next, install the *Time Off* app. This is the app used for assigning time off to all resources within Odoo, including employees and work centers. Navigate to :menuselection:`Apps`, then type `Time Off` in the :guilabel:`Search...` bar. The card for the :guilabel:`Time Off` module should be the only one that appears on the page. Click the green :guilabel:`Install` button on the card to install the app."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1
+msgid "The Time Off module installation card."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:39
+msgid "The last step is to properly configure work centers. For this workflow, it is necessary to have at least two work centers: one that is made unavailable and a second that receives the work orders that the other cannot accept. If no second work center is configured, Odoo cannot route work orders away from the unavailable work center and they will pile up in its queue."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:44
+msgid "To create a work center, navigate to :menuselection:`Manufacturing --> Configuration --> Work Centers --> Create`."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:47
+msgid "Make sure that both work centers have the same equipment listed under the :guilabel:`Equipment` tab. This ensures that operations carried out at one work center can also be performed at the other."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1
+msgid "The equipment tab on a work center form."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:54
+msgid "For the work center that will be made unavailable, select the second work center on the :guilabel:`Alternative Workcenters` drop-down menu. Now, Odoo knows to send work orders to the second work center when the first is unavailable for any reason."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1
+msgid "A work center form configured with an alternative work center."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:63
+msgid "Add time off for a work center"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:65
+msgid "With configuration completed, time off can now be assigned to the work center that will be made unavailable. Begin by navigating to :menuselection:`Manufacturing --> Configuration --> Work Centers` and selecting the affected work center. Click :guilabel:`Edit`, and then the :guilabel:`↗ (external link)` button next to the :guilabel:`Working Hours` drop-down menu."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1
+msgid "The Working Hours \"External link\" button on the work center form."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:74
+msgid "A pop-up appears, titled :guilabel:`Open: Working Hours`. The standard working hours for the work center are listed here, along with various other details about it. Since developer mode was enabled, there is a :guilabel:`Time Off` button in the top right of the pop-up. Click it to be taken to the :guilabel:`Resource Time Off` page."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1
+msgid "The Time Off button on the Working Hours pop-up."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:83
+msgid "On this page, click :guilabel:`Create` to configure a new time-off entry. On the time-off form, note the :guilabel:`Reason` for the work center closure (broken, maintenance, etc.), select the affected work center as the :guilabel:`Resource`, and choose a :guilabel:`Start Date` and :guilabel:`End Date` to specify the period during which the work center will be unavailable. Click :guilabel:`Save` and the time off for the work center is logged in Odoo."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1
+msgid "The \"Resource Time Off\" form."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:94
+msgid "Route orders to an alternative work center"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:96
+msgid "Once a work center is within its specified time-off period, work orders sent to it can be automatically routed to an alternative work center using the :guilabel:`Plan` button."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:99
+msgid "Begin by creating a new manufacturing order by selecting :menuselection:`Operations --> Manufacturing Orders --> Create`. On the manufacturing order form, specify a :guilabel:`Product` that uses the unavailable work center for one of its operations. Click :guilabel:`Confirm` to confirm the work order."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:104
+msgid "On the confirmed work order, select the :guilabel:`Work Orders` tab. By default, the unavailable work center is specified in the :guilabel:`Work Center` column. There is also a green :guilabel:`Plan` button on the top left of the page."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1
+msgid "The Plan button on a manufacturing order."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:112
+msgid "Click :guilabel:`Plan` and the work center listed under the :guilabel:`Work Orders` tab is automatically changed to the alternative work center."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1
+msgid "The selected work center updates automatically after clicking the Plan button."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:119
+msgid "Once the time-off period for the unavailable work center ends, Odoo recognizes that the work center is available again. At this point, clicking the :guilabel:`Plan` button does not route work orders to an alternative work center unless the first one is at capacity."
+msgstr ""
+
 #: ../../content/applications/inventory_and_mrp/manufacturing/quality_control.rst:5
 msgid "Quality control"
 msgstr ""
@@ -8206,6 +8582,7 @@ msgid "Now that all product quantities have been ordered, the purchase process c
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:3
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:15
 msgid "Bill control policies"
 msgstr ""
 
@@ -8218,10 +8595,12 @@ msgid "To view the default bill control policy and make changes, go to :menusele
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:17
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:28
 msgid "The policy selected will be the default for any new product created. The definition of each policy is as follows:"
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:20
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:31
 msgid ":guilabel:`Ordered quantities`: creates a vendor bill as soon as a purchase order is confirmed. The products and quantities in the purchase order are used to generate a draft bill."
 msgstr ""
 
@@ -8262,6 +8641,7 @@ msgid "In the :guilabel:`Purchase` app, create a new :abbr:`RFQ (Request for Quo
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:63
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:46
 msgid "3-way matching"
 msgstr ""
 
@@ -8373,212 +8753,239 @@ msgstr ""
 msgid "Manage vendor bills"
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:5
-msgid "The **Purchase** application allows you to manage your purchase orders, incoming products, and vendor bills all seamlessly in one place."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:7
+msgid "A *vendor bill* is an invoice received for products and/or services that a company purchases from a vendor. Vendor bills record payables as they arrive from vendors, and can include amounts owed for the goods and/or services purchased, sales taxes, freight and delivery charges, and more."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:8
-msgid "If you want to set up a vendor bill control process, the first thing you need to do is to have purchase data in Odoo. Knowing what has been purchased and received is the first step towards understanding your purchase management processes."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:11
+msgid "In Odoo, a vendor bill can be created at different points in the purchasing process, depending on the *bill control* policy chosen in the *Purchase* app settings."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:13
-msgid "Here is the standard work flow in Odoo:"
-msgstr ""
-
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:15
-msgid "You begin with a **Request for Quotation (RFQ)** to send out to your vendor(s)."
-msgstr ""
-
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:18
-msgid "Once the vendor has accepted the RFQ, confirm the RFQ into a **Purchase Order (PO)**."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:17
+msgid "To view and edit the default bill control policy and make changes to it, go to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section."
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:21
-msgid "Confirming the PO generates an **Incoming Shipment** if you purchased any stockable products."
+msgid "Here, there are two :guilabel:`Bill Control` policy options: :guilabel:`Ordered quantities` and :guilabel:`Received quantities`. After a policy is selected, click :guilabel:`Save` to save changes."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:24
-msgid "Upon receiving a **Vendor Bill** from your Vendor, validate the bill with products received in the previous step to ensure accuracy."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1
+msgid "Bill control policies in purchase app settings."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:27
-msgid "This process may be done by three different people within the company, or only one."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:33
+msgid ":guilabel:`Received quantities`: a bill is only created **after** part of the total order has been received. The products and quantities **received** are used to generate a draft bill."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:34
-msgid "Installing the Purchase and Inventory applications"
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:37
+msgid "If a product needs a different control policy, the default bill control policy can be overridden by going to the :guilabel:`Purchase` tab in a product's template, and modifying its :guilabel:`Control Policy` field."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:36
-msgid "From the **Apps** application, search for the **Purchase** module and install it. Due to certain dependencies, installing Purchase will automatically install the **Inventory** and **Accounting** applications."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1
+msgid "Control policy field on product form."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:41
-msgid "Creating products"
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:48
+msgid "*3-way matching* ensures vendor bills are only paid once some (or all) of the products included in the purchase order have actually been received."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:43
-msgid "Creating products in Odoo is essential for quick and efficient purchasing within Odoo. Simply navigate to the Products submenu under Purchase and click create."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:51
+msgid "To activate it, go to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section. Then, check the box next to :guilabel:`3-way matching: purchases, receptions, and bills`, and click :guilabel:`Save` to save changes."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:50
-msgid "When creating the product, pay attention to the **Product Type** field, since it is important:"
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:56
+msgid ":guilabel:`3-way matching` is **only** intended to work with the :guilabel:`Bill Control` policy set to :guilabel:`Received quantities`."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:53
-msgid "Products that are set as **Stockable or Consumable** will allow you to keep track of their inventory levels. These options imply stock management and will allow for receiving these kinds of products."
-msgstr ""
-
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:58
-msgid "Conversely, products that are set as a **Service or Digital Product** will not imply stock management, simply due to the fact that there is no inventory to manage. You will not be able to receive products under either of these designations."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0
+msgid "Activated three-way matching feature in purchase settings."
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:64
-msgid "It is recommended that you create a **Miscellaneous** product for all purchases that occur infrequently and do not require inventory valuation or management. If you create such a product, it is recommended to set the product type to **Service**."
+msgid "Create and manage vendor bills on receipts"
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:69
-msgid "Managing your Vendor Bills"
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:66
+msgid "When products are received into a company's warehouse, receipts are created. Once the company processes the received quantities, they can choose to create a vendor bill directly from the warehouse receipt form. Depending on the bill control policy chosen in the settings, vendor bill creation is completed at different steps of the procurement process."
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:72
-msgid "Purchasing products or services"
+msgid "With the bill control policy set to ordered quantities"
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:74
-msgid "From the purchase application, you can create a purchase order with as many products as you need. If the vendor sends you a confirmation or quotation for an order, you may record the order reference number in the **Vendor Reference** field. This will enable you to easily match the PO with the the vendor bill later (as the vendor bill will probably include the Vendor Reference)"
+msgid "To create and manage vendor bills on receipts using the *ordered quantities* bill control policy, first go to :menuselection:`Purchase app --> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` section, and select :guilabel:`Ordered quantities` under :guilabel:`Bill Control`. Then, click :guilabel:`Save` to save changes."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:84
-msgid "Validate the purchase order and receive the products from the Inventory application."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:79
+msgid "Next, go to the :menuselection:`Purchase` app, and click :guilabel:`Create` to create a new request for quotation (RFQ). Doing so reveals a blank :abbr:`RFQ (request for quotation)` detail form."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:88
-msgid "Receiving Products"
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:82
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:144
+msgid "On the blank detail form, add a vendor to the :abbr:`RFQ (request for quotation)` in the :guilabel:`Vendor` field, and add products to the :guilabel:`Product` lines by clicking :guilabel:`Add a line`."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:86
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:148
+msgid "Then, confirm the :abbr:`RFQ (request for quotation)` by clicking the :guilabel:`Confirm Order` button above the detail form. Doing so turns the :abbr:`RFQ (request for quotation)` into a purchase order."
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:90
-msgid "If you purchased any stockable products that you manage the inventory of, you will need to receive the products from the Inventory application after you confirm a purchase order. From the **Inventory dashboard**, you should see a button linking you directly to the transfer of products. This button is outlined in red below:"
+msgid "Then, click the :guilabel:`Create Bill` button to create a vendor bill for the purchase order."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:92
+msgid "Clicking the :guilabel:`Create Bill` button reveals the :guilabel:`Draft Bill` page for the purchase order."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:95
+msgid "On the :guilabel:`Draft Bill`, click the :guilabel:`Edit` button to modify the bill, and add a bill date in the :guilabel:`Bill Date` field. If needed, add additional products to the :guilabel:`Product` lines by clicking :guilabel:`Add a line` in the :guilabel:`Invoice Lines` tab."
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:99
-msgid "Navigating this route will take you to a list of all orders waiting to be received."
+msgid "Next, confirm the bill by clicking the :guilabel:`Confirm` button on the :guilabel:`Draft Bill` page."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:105
-msgid "If you have a lot of awaiting orders, apply a filter using the search bar in the upper right. With this search bar, you may filter based on the vendor (partner), the product, or the source document (also known as the reference of your purchase order). You can also group the orders by different criteria under **Group By**. Selecting an item from this list will open the following screen where you then will receive the products."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:103
+msgid "Since the bill control policy is set to *ordered quantities*, the draft bill can be confirmed as soon as it is created, before any products have been received."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:116
-msgid "Purchasing service products does not trigger a delivery order."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:106
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:179
+msgid "On the new :guilabel:`Vendor Bill`, add a :guilabel:`Bill Reference` number, which can be used to match the bill with additional documents (such as the :abbr:`PO (purchase order)`). Then, click :menuselection:`Confirm --> Register Payment`. Doing so causes a pop-up to appear, wherein a payment :guilabel:`Journal` can be chosen; a :guilabel:`Payment Method` selected; and a :guilabel:`Recipient Bank Account` can be selected from a drop-down menu."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:119
-msgid "Managing Vendor Bills"
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:112
+msgid "Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and :guilabel:`Memo` (:dfn:`Reference Number`) can be changed from this pop-up. Once ready, click :guilabel:`Create Payment` to finish creating the :guilabel:`Vendor Bill`. Doing so causes a green :guilabel:`In Payment` banner to display on the :abbr:`RFQ (request for quotation)` form."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:121
-msgid "When you receive a vendor bill for a previous purchase, be sure to record it in the Purchases application under the **Control Menu**. You need to create a new vendor bill even if you already registered a purchase order."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1
+msgid "Vendor bill form for ordered quantities control policy."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:129
-msgid "The first thing you will need to do upon creating a vendor bill is to select the appropriate vendor, since doing so will also pull up any associated accounting or pricelist information. From there, you can choose to specify one or multiple Purchase Orders to populate the Vendor Bill with. When you select a Purchase Order from the list, Odoo will pull any uninvoiced products associated to that Purchase Order and automatically populate that information below. If you are having a hard time finding the appropriate vendor bill, you may search through the list by inputting the vendor reference number or your internal purchase order number."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:122
+msgid "Each vendor bill provides the option to either :guilabel:`Add Credit Note` or :guilabel:`Add Debit Note`. A *credit note* is typically issued when a vendor or supplier of goods get some quantity of products back from the customer to whom they were sold, while *debit notes* are reserved for goods returned from the customer/buyer to the vendor or supplier."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:143
-msgid "While the invoice is in a draft state, you can make any modifications you need (i.e. remove or add product lines, modify quantities, and change prices)."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:128
+msgid "With the bill control policy set to received quantities"
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:148
-msgid "Your vendor may send you several bills for the same Purchase Order if:"
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:131
+msgid "If the creation of a vendor bill is attempted without receiving any quantities of a product (while using the *received quantities* bill control policy), an error message appears, and settings must be changed before proceeding."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:150
-msgid "Your vendor is in back-order and is sending you invoices as they ship the products."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:135
+msgid "To create and manage vendor bills on receipts using the *received quantities* bill control policy, first go to :menuselection:`Purchase app --> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` section, and select :guilabel:`Received quantities` under :guilabel:`Bill Control`. Then, click :guilabel:`Save` to save changes."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:151
-msgid "Your vendor is sending you a partial bill or asking for a deposit."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:140
+msgid "Next, go to the :menuselection:`Purchase` app, and click :guilabel:`Create` to create a new :abbr:`RFQ (request for quotation)`. Doing so reveals a blank :abbr:`RFQ (request for quotation)` detail form."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:153
-msgid "Every time you record a new vendor bill, Odoo will automatically populate the product quantities based on what has been received from the vendor. If this value is showing a zero, this means that you have not yet received this product and simply serves as a reminder that the product is not in hand and you may need to inquire further into this. At any point in time, before you validate the Vendor Bill, you may override this zero quantity."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:152
+msgid "Finally, click the :guilabel:`Create Bill` button to create a bill for the purchase order."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:162
-msgid "Vendor Bill Matching"
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:155
+msgid "Clicking :guilabel:`Create Bill` before any products have been received will cause a :guilabel:`User Error` pop-up to appear. The :guilabel:`Purchase Order` requires the receipt of at least partial quantity of the items included on the order to create a vendor bill."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1
+msgid "User error pop-up for received quantities control policy."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:163
+msgid "Next, click the :guilabel:`Receipt` smart button to view the warehouse receipt form."
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:165
-msgid "What to do if your vendor bill does not match what you received"
+msgid "On the warehouse receipt form, click :menuselection:`Validate --> Apply` to mark the :guilabel:`Done` quantities. Then, navigate back to the :menuselection:`Purchase Order` (via the breadcrumbs), and click the :guilabel:`Create Bill` button on the purchase order form."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:167
-msgid "If the bill you receive from the vendor has quantities that do not match the quantities automatically populated by Odoo, this could be due to several reasons:"
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:169
+msgid "Doing so reveals the :guilabel:`Draft Bill` for the purchase order. On the :guilabel:`Draft Bill`, click the :guilabel:`Edit` button, and add a :guilabel:`Bill Date`. If needed, add additional products to the :guilabel:`Product` lines by clicking :guilabel:`Add a line`."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:171
-msgid "The vendor is incorrectly charging you for products and/or services that you have not ordered."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:173
+msgid "Next, click the :guilabel:`Confirm` button to confirm the :guilabel:`Draft Bill`."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:174
-msgid "The vendor is billing you for products that you might not have received yet, as the invoicing control may be based on ordered or received quantities."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:176
+msgid "Since the bill control policy is set to *received quantities*, the draft bill can **only** be confirmed when at least some of the quantities are received."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:178
-msgid "The vendor did not bill you for previously purchased products."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:185
+msgid "Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and :guilabel:`Memo` (:dfn:`Reference Number`) can be changed from this pop-up. Once ready, click :guilabel:`Create Payment` to finish creating the vendor bill. Doing so causes a green **In Payment** banner to display on the :abbr:`RFQ (request for quotation)` form."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:180
-msgid "In these instances it is recommended that you verify that the bill, and any associated purchase order to the vendor, are accurate and that you understand what you have ordered and what you have already received."
-msgstr ""
-
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:184
-msgid "If you are unable to find a purchase order related to a vendor bill, this could be due to one of a few reasons:"
-msgstr ""
-
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:187
-msgid "The vendor has already invoiced you for this purchase order; therefore it is not going to appear anywhere in the selection."
-msgstr ""
-
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:190
-msgid "Someone in the company forgot to record a purchase order for this vendor."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:191
+msgid "Create and manage vendor bills in Accounting"
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:193
-msgid "The vendor is charging you for something you did not order."
+msgid "Vendor bills can also be created directly from the *Accounting* app, **without** having to create a purchase order first. To do this, go to :menuselection:`Accounting app --> Vendors --> Bills`, and click :guilabel:`Create`. Doing so reveals a blank vendor bill detail form."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:198
-msgid "How product quantities are managed"
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:197
+msgid "On this blank vendor bill detail form, add a vendor in the :guilabel:`Vendor` field, and add products to the :guilabel:`Product` lines (under the :guilabel:`Invoice Lines` tab), by clicking :guilabel:`Add a line`. Then, add a bill date in the :guilabel:`Bill Date` field, and any other necessary information. Finally, click :guilabel:`Confirm` to confirm the bill."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:200
-msgid "By default, services are managed based on ordered quantities, while stockables and consumables are managed based on received quantities."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:202
+msgid "From here, click the :guilabel:`Journal Items` tab to view (or change) the :guilabel:`Account` journals that were populated based on the configuration on the corresponding :guilabel:`Vendor` and :guilabel:`Product` forms."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:203
-msgid "If you need to manage products based on ordered quantities over received quantities, you will need to belong to the group **Purchase Manager**. Ask your system administrator to enable these access on :menuselection:`Settings --> Users --> Users --> Access Rights`. Once you belong to the correct group, select the product(s) you wish to modify, and you should see a new field appear, labeled **Control Purchase Bills**."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:206
+msgid "Then, click :guilabel:`Add Credit Note` or :guilabel:`Add Debit Note` to add credit or debit notes to the bill. Or, add a :guilabel:`Bill Reference` number (while in :guilabel:`Edit` mode)."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:209
+msgid "Then, when ready, click :menuselection:`Register Payment --> Create Payment` to complete the :guilabel:`Vendor Bill`."
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:213
-msgid "You can then change the default management method for the selected product to be based on either:"
+msgid "To tie the draft bill to an existing purchase order, click the drop-down menu next to :guilabel:`Auto-Complete`, and select a :abbr:`PO (purchase order)` from the menu. The bill will auto-populate with the information from the :abbr:`PO (purchase order)`."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:216
-msgid "Ordered quantities"
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0
+msgid "Auto-complete drop-down list on draft vendor bill."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:218
-msgid "or Received quantities"
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:222
+msgid "Batch billing"
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:221
-msgid "Batch Billing"
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:224
+msgid "Vendor bills can be processed and managed in batches in the *Accounting* app."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:223
-msgid "When creating a vendor bill and selecting the appropriate purchase order, you may continue to select additional purchase orders. Odoo will add the additional line items from the purchase orders you select. If you have not deleted the previous line items from the first purchase order, the bill will be linked to all the appropriate purchase orders."
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:226
+msgid "To do this, go to :menuselection:`Accounting app --> Vendors --> Bills`. Then, click the :guilabel:`checkbox` at the top left of the page, beside the :guilabel:`Number` column, under the :guilabel:`Create` button. This selects all existing vendor bills with a :guilabel:`Posted` or :guilabel:`Draft` :guilabel:`Status`."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:231
+msgid "From here, click the :guilabel:`Action` gear icon to export, delete, or send & print the bills; click the :guilabel:`Print` icon to print the invoices or bills; or click :guilabel:`Register Payment` to create and process payments for multiple vendor bills at once."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:235
+msgid "When :guilabel:`Register Payment` is selected, a pop-up appears. In this pop-up window, select the appropriate journal in the :guilabel:`Journal` field, choose a payment date in the :guilabel:`Payment Date` field, and choose a :guilabel:`Payment Method`. There is also the option to :guilabel:`Group Payments` on this pop-up, as well."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:240
+msgid "When ready, click the :guilabel:`Create Payment` button, which creates a list of journal entries on a separate page. This list of journal entries are all tied to their appropriate vendor bills."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1
+msgid "Batch billing register payment pop-up."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:248
+msgid "The :guilabel:`Register Payment` option for vendor bills in batches will only work for journal entries whose :guilabel:`Status` is set to :guilabel:`Posted`."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:252
+msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/control_bills`"
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:3

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-07-03 09:37+0000\n"
+"POT-Creation-Date: 2023-07-07 11:55+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"

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-07-03 09:37+0000\n"
+"POT-Creation-Date: 2023-07-07 11:55+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"

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-07-03 09:37+0000\n"
+"POT-Creation-Date: 2023-07-07 11:55+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"

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-07-03 09:37+0000\n"
+"POT-Creation-Date: 2023-07-07 11:55+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -46,6 +46,7 @@ msgstr ""
 
 #: ../../content/applications/services/field_service/default_warehouse.rst:16
 #: ../../content/applications/services/project/project_management.rst:17
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:13
 msgid "Configuration"
 msgstr ""
 
@@ -2795,6 +2796,74 @@ msgstr ""
 msgid "View of the email alias chosen on the dashboard view in Odoo Project"
 msgstr ""
 
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:3
+msgid "Recurring tasks"
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:5
+msgid "When handling a project, the same task often needs to be performed several times: for example, weekly meetings or status reports. The **recurring tasks** feature allows you to automate the creation of those tasks."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:10
+msgid "`Odoo Tutorials: Recurring tasks <https://www.odoo.com/slides/slide/recurring-tasks-1946>`_"
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:15
+msgid "To enable recurring tasks, go to :menuselection:`Project --> Configuration --> Settings`, then activate :guilabel:`Recurring Tasks`, and :guilabel:`Save`."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:18
+msgid "Recurring tasks are now activated on all existing projects. The feature can be deactivated on an individual project by clicking the drop-down menu button :guilabel:`⋮` next to the project name, then going to :menuselection:`Settings --> Settings --> Task Management` and disabling :guilabel:`Recurring Tasks`."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:24
+msgid "Set up task recurrence"
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:26
+msgid "In an existing task, go to the :guilabel:`Recurrent` tab, then check the :guilabel:`Recurrent` box. A set of options allows you to configure the frequency: :guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, :guilabel:`Years`, and the number of repetitions."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:30
+msgid "On the scheduled recurrency date, a new task is created on your project dashboard with the following configuration:"
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:33
+msgid ":guilabel:`Stage`: first stage of the project dashboard (:guilabel:`New` or equivalent);"
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:34
+msgid ":guilabel:`Name`, :guilabel:`Description`, :guilabel:`Project`, :guilabel:`Assignees`, :guilabel:`Customer`, :guilabel:`Tags`: copied from the original task;"
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:36
+msgid ":guilabel:`Milestones`, :guilabel:`Deadline`, :guilabel:`Timesheets`, :guilabel:`Chatter`, :guilabel:`Activities`: those fields are not copied;"
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:38
+msgid ":guilabel:`Subtasks`: copied from the original task, which becomes a parent of all the tasks in recurrence;"
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:40
+msgid "A **smart button** on the task displays the total number of existing recurrences."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:43
+msgid "To see the task in your project dashboard before the scheduled date, consider setting up the recurrence date to a day earlier."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:47
+msgid "Edit or stop task recurrence"
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:49
+msgid "**To edit** the recurrence, open the task: a blue banner invites you to choose whether you wish to apply your changes to this task only or to a sequence of tasks."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:52
+msgid "**To stop** the recurrence, open the task, then go to the :guilabel:`Recurrency` tab and uncheck :guilabel:`Recurrent`."
+msgstr ""
+
 #: ../../content/applications/services/timesheets.rst:8
 msgid "Timesheets"
 msgstr ""

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-07-03 09:37+0000\n"
+"POT-Creation-Date: 2023-07-07 11:55+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -2104,6 +2104,283 @@ msgstr ""
 msgid ":doc:`/applications/websites/livechat/responses`"
 msgstr ""
 
+#: ../../content/applications/websites/livechat/chatbots.rst:3
+msgid "Chatbots"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:5
+msgid "A *Chatbot* is a program designed to mimic a conversation with a live human. Chatbots are assigned a script of pre-written steps to follow. The scripts are designed to anticipate a visitor's potential response, and lead them through a series of questions and answers the same way a live team member would."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:10
+msgid "Chatbots can be customized to fill various roles, from customer support, to creating leads, to collecting contact information. The goal of the chatbot depends on the page of the website they are assigned, and the messages included in the script, among other criteria."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:-1
+#: ../../content/applications/websites/livechat/responses.rst:-1
+msgid "View of the chat window with a helpdesk ticket created in Odoo Live Chat."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:19
+msgid "Build a chatbot"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:21
+msgid "Before creating a new chatbot, the *Live Chat* application must first be installed on the database. This can be done directly from the :menuselection:`Apps` menu by searching for `Live Chat` in the :guilabel:`search bar` and clicking :guilabel:`Install`."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:25
+msgid "Alternatively, *Live Chat* can be installed and enabled by navigating to the :menuselection:`Website application --> Configuration --> Settings`, and checking the box labeled :guilabel:`Livechat`. Once enabled, the database will refresh, and the *Live Chat* application is accessible."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:29
+msgid "Once the *Live Chat* application has been installed on the database, open it, and go to :menuselection:`Configuration --> Chatbots`."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:33
+msgid "When the *Live Chat* app is installed, a sample chatbot is created, named *Welcome Bot*. This chatbot has a pre-configured script that walks through a few basic steps, including asking for a visitor's email address, and forwarding the conversation to an operator."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:37
+msgid "*Welcome Bot* can be used as a starting point. The existing steps can be edited or removed, and new steps can be added to customize the script, as needed."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:40
+msgid "*Welcome Bot* can be deleted (or archived)."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:0
+msgid "View of the Welcome Bot script in Odoo Live Chat."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:46
+msgid "To create a new chatbot, navigate to the :guilabel:`Chatbot` page (:menuselection:`Live Chat app --> Configuration --> Chatbots`) and click :guilabel:`New`. This opens a blank chatbot details page."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:49
+msgid "On the blank chatbot details page, enter a name in the :guilabel:`Chatbot Name` field and click on the :guilabel:`Edit Image` icon in the upper right corner of the form to add a photo."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:53
+msgid "Chatbot scripts"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:55
+msgid "Once the new chatbot has been created and named, the next step is to create a script. Chatbot conversations follow an accompanying script. These scripts are comprised of lines of dialogue, each designed to either deliver or capture information."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:59
+msgid "To create a chatbot script, navigate to the :guilabel:`Script` tab of the chatbot details page, and click :guilabel:`Add a Line` to open the :guilabel:`Create Script Steps` pop-up form."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:62
+msgid "This form must be filled out for each line of text (dialogue) that the chatbot could potentially deliver during the conversation."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:65
+msgid "First, enter the content of the message in the :guilabel:`Message` field. Then, select an option from the :guilabel:`Step Types` drop-down menu."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:69
+msgid "Step types"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:71
+msgid "The :guilabel:`Step Type` selected depends on the intended purpose of the message. The available options in the :guilabel:`Step Type` drop-down are listed below, as well as their use, and any additional information:"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:76
+msgid "Text"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:78
+msgid "This step is used for messages where no answer is expected (or necessary). Text steps can be used for greetings and/or to deliver information."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:82
+msgid "Text step types are only intended to deliver information, and do not allow for any visitor input. As such, they need to be followed by additional steps to continue the conversation."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:86
+msgid "Question"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:88
+msgid "This step asks a question and provides a set of answers. The visitor clicks on one answer, which either leads to a new step in the conversation, or can lead to an optional link to a new webpage."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:92
+msgid "It is helpful to add a catchall answer to question steps (ex: \"Something else\"). This helps visitors continue the conversation, even if their needs don't exactly fit with any of the other answers."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:97
+msgid "Email"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:99
+msgid "This step prompts visitors to provide their email address, which is stored and can be used by team members later to follow up with additional information."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:102
+msgid "The only accepted inputs for this step type are email addresses that are in a valid format. If a visitor attempts to enter anything other than a valid email address, the chatbot responds with a message stating it does not recognize the information submitted."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:-1
+msgid "View of a chatbot responding to an invalid email."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:111
+msgid "Phone"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:113
+msgid "Similar to email, this step type prompts the visitor to enter their phone number, which can be used at a later time to follow up with additional information, or to schedule demos, and more."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:117
+msgid "Due to the vast number of formats used for phone numbers worldwide, responses to this step type are **not** validated for formatting."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:121
+msgid "Forward to Operator"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:123
+msgid "This step forwards the conversation to an active live chat operator, so that they can continue assisting the visitor. As the conversation transcript is passed on to the operator they are able to pick up where the chatbot left off. This not only saves time for all parties involved, it can also help qualify conversations before they reach live human operators."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:129
+msgid "If no active operator is available on the channel, the chatbot continues the conversation with the visitor. Therefore, additional steps should be added after this one to ensure that there is no abrupt end to the conversation."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:0
+msgid "View of a chatbot follow up messages when no live chat operator is available."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:138
+msgid "Free Input/Multi-Line"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:140
+msgid "The free input step allows visitors to respond to questions without providing pre-written responses. Information provided in these responses is stored in the chat transcripts."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:143
+msgid "Choose between :guilabel:`Free Input` and :guilabel:`Free Input (Multi-Line)` depending on the type and amount of information being requested from the visitor."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:147
+msgid "Create Lead"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:149
+msgid "This step creates a lead in the *CRM* application. Select an option from the :guilabel:`Sales Team` drop-down to assign the created lead to a specific team."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:153
+msgid "Create Ticket"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:155
+msgid "This step creates a :doc:`ticket </applications/services/helpdesk/overview/receiving_tickets>` in the *Helpdesk* application. Select an option from the :guilabel:`Helpdesk Team` drop-down to assign the created ticket to a specific team."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:160
+msgid "Only if"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:162
+msgid "Chatbot scripts operate on an if/then basis, which means the next question presented to the visitor is determined by the answer they provide to the previous question."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:165
+msgid "To continue the progression of the conversation, the form for a new step contains a field labeled :guilabel:`Only If`. This field is where the progression of questions is defined."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:168
+msgid "If a step is intended to follow all of the previous messages, this field can be left empty. However, if a message should **only** be sent conditionally, based on a previous response (or several previous responses), those responses need to be added to this field."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:173
+msgid "If there are any selections made in the :guilabel:`Only If` field, the step will **not** be shown in a conversation unless **all** of the answers have been selected. Only include selections in this field if they are necessary for this step to be displayed."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:178
+msgid "In the *Welcome Bot* script, a visitor can ask about pricing information. If the visitor selects this response, a step is included to forward the conversation to an operator. The chatbot first sends a message informing the visitor that it is checking to see if an operator is available to chat."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:183
+msgid "However, this message should **only** be delivered if the visitor requests pricing information. In that situation, the conversation would proceed as below:"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:186
+msgid "Welcome Bot: \"*What are you looking for?*\""
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:187
+msgid "Visitor: \"**I have a pricing question.**\""
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:188
+msgid "Welcome Bot: \"*Hmmm, let me check if I can find someone that could help you with that...*\""
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:190
+msgid "In the details form for the :guilabel:`Text` step, the *I have a pricing question* response has been selected in the :guilabel:`Only If` field. As such, this step is **only** shown in conversations where that response has been selected."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:0
+msgid "View of the new message form emphasizing the Only If field."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:199
+msgid "Script testing"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:201
+msgid "In order to ensure all visitors have a satisfactory experience with the chatbot, each message needs to lead to a natural conclusion. Chatbot scripts should be tested to confirm there are no dead-ends, and to get an understanding of what the visitor sees when they interact with the chatbot."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:206
+msgid "If there is an answer or input provided by the visitor that is **not** assigned a corresponding follow-up response, the conversation stops (*dead-end*). Since the visitor cannot re-engage the chatbot, they will have to re-start the conversation, by refreshing the chat window, or their browser."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:211
+msgid "To test the performance of a chatbot, first click on the :guilabel:`Test` button at the top-left of the chatbot script page. Then, upon being redirected to the testing screen, answer the chatbot prompts the same way a potential site visitor would."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:215
+msgid "When the script has reached an end-point, the message *Conversation ended...Restart* appears at the bottom of the chat window. To begin the conversation at the beginning of the script, click on :guilabel:`Restart`. To return to the script page, click :guilabel:`Back to edit mode` at the top of the page."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:221
+msgid "Add chatbot to a channel"
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:223
+msgid "After a chatbot has been created and tested, it needs to be added to a live chat channel."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:225
+msgid "First, open the :menuselection:`Live Chat` application, and select the kanban card for a :guilabel:`Channel`, or create a :doc:`new one </applications/websites/livechat>`. Click on the :guilabel:`Channel Rules` tab. Then, open an existing rule, or create a new one by clicking :guilabel:`Add a line`."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:230
+msgid "On the :guilabel:`Create Rules` pop-up detail form, choose the appropriate chatbot in the :guilabel:`Chatbot` field."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:233
+msgid "If the chatbot should **only** be active if there are no available live chat operators, check the box labeled :guilabel:`Enabled only if no operator`."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:-1
+msgid "View of the channel rules emphasizing the chatbot field."
+msgstr ""
+
+#: ../../content/applications/websites/livechat/chatbots.rst:241
+msgid ":doc:`Live chat channel rules </applications/websites/livechat>`"
+msgstr ""
+
 #: ../../content/applications/websites/livechat/ratings.rst:3
 msgid "Ratings"
 msgstr ""
@@ -2188,10 +2465,6 @@ msgstr ""
 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."
-msgstr ""
-
 #: ../../content/applications/websites/livechat/responses.rst:29
 msgid "More information about each available command can be found below."
 msgstr ""