[I18N] export 13.0 source terms

2019-10-03 11:45:10 +02:00 · 2019-10-03 11:45:10 +02:00 · 9560e6060f
commit 9560e6060f
parent efcb1a48fd
21 changed files with 4185 additions and 2061 deletions
--- a/.tx/config
+++ b/.tx/config
@ -2,122 +2,122 @@
 host = https://www.transifex.com
 type = PO

-[odoo-12-doc.accounting]
+[odoo-13-doc.accounting]
 file_filter = locale/<lang>/LC_MESSAGES/accounting.po
 source_file = locale/sources/accounting.pot
 source_lang = en

-[odoo-12-doc.applications]
+[odoo-13-doc.applications]
 file_filter = locale/<lang>/LC_MESSAGES/applications.po
 source_file = locale/sources/applications.pot
 source_lang = en

-[odoo-12-doc.crm]
+[odoo-13-doc.crm]
 file_filter = locale/<lang>/LC_MESSAGES/crm.po
 source_file = locale/sources/crm.pot
 source_lang = en

-[odoo-12-doc.db_management]
+[odoo-13-doc.db_management]
 file_filter = locale/<lang>/LC_MESSAGES/db_management.po
 source_file = locale/sources/db_management.pot
 source_lang = en

-[odoo-12-doc.discuss]
+[odoo-13-doc.discuss]
 file_filter = locale/<lang>/LC_MESSAGES/discuss.po
 source_file = locale/sources/discuss.pot
 source_lang = en

-[odoo-12-doc.ecommerce]
+[odoo-13-doc.ecommerce]
 file_filter = locale/<lang>/LC_MESSAGES/ecommerce.po
 source_file = locale/sources/ecommerce.pot
 source_lang = en

-[odoo-12-doc.expenses]
+[odoo-13-doc.expenses]
 file_filter = locale/<lang>/LC_MESSAGES/expenses.po
 source_file = locale/sources/expenses.pot
 source_lang = en

-[odoo-12-doc.general]
+[odoo-13-doc.general]
 file_filter = locale/<lang>/LC_MESSAGES/general.po
 source_file = locale/sources/general.pot
 source_lang = en

-[odoo-12-doc.getting_started]
+[odoo-13-doc.getting_started]
 file_filter = locale/<lang>/LC_MESSAGES/getting_started.po
 source_file = locale/sources/getting_started.pot
 source_lang = en

-[odoo-12-doc.helpdesk]
+[odoo-13-doc.helpdesk]
 file_filter = locale/<lang>/LC_MESSAGES/helpdesk.po
 source_file = locale/sources/helpdesk.pot
 source_lang = en

-[odoo-12-doc.index]
+[odoo-13-doc.index]
 file_filter = locale/<lang>/LC_MESSAGES/index.po
 source_file = locale/sources/index.pot
 source_lang = en

-[odoo-12-doc.inventory]
+[odoo-13-doc.inventory]
 file_filter = locale/<lang>/LC_MESSAGES/inventory.po
 source_file = locale/sources/inventory.pot
 source_lang = en

-[odoo-12-doc.iot]
+[odoo-13-doc.iot]
 file_filter = locale/<lang>/LC_MESSAGES/iot.po
 source_file = locale/sources/iot.pot
 source_lang = en

-[odoo-12-doc.livechat]
+[odoo-13-doc.livechat]
 file_filter = locale/<lang>/LC_MESSAGES/livechat.po
 source_file = locale/sources/livechat.pot
 source_lang = en

-[odoo-12-doc.mobile]
+[odoo-13-doc.mobile]
 file_filter = locale/<lang>/LC_MESSAGES/mobile.po
 source_file = locale/sources/mobile.pot
 source_lang = en

-[odoo-12-doc.manufacturing]
+[odoo-13-doc.manufacturing]
 file_filter = locale/<lang>/LC_MESSAGES/manufacturing.po
 source_file = locale/sources/manufacturing.pot
 source_lang = en

-[odoo-12-doc.point_of_sale]
+[odoo-13-doc.point_of_sale]
 file_filter = locale/<lang>/LC_MESSAGES/point_of_sale.po
 source_file = locale/sources/point_of_sale.pot
 source_lang = en

-[odoo-12-doc.portal]
+[odoo-13-doc.portal]
 file_filter = locale/<lang>/LC_MESSAGES/portal.po
 source_file = locale/sources/portal.pot
 source_lang = en

-[odoo-12-doc.practical]
+[odoo-13-doc.practical]
 file_filter = locale/<lang>/LC_MESSAGES/practical.po
 source_file = locale/sources/practical.pot
 source_lang = en

-[odoo-12-doc.project]
+[odoo-13-doc.project]
 file_filter = locale/<lang>/LC_MESSAGES/project.po
 source_file = locale/sources/project.pot
 source_lang = en

-[odoo-12-doc.purchase]
+[odoo-13-doc.purchase]
 file_filter = locale/<lang>/LC_MESSAGES/purchase.po
 source_file = locale/sources/purchase.pot
 source_lang = en

-[odoo-12-doc.recruitment]
+[odoo-13-doc.recruitment]
 file_filter = locale/<lang>/LC_MESSAGES/recruitment.po
 source_file = locale/sources/recruitment.pot
 source_lang = en

-[odoo-12-doc.sales]
+[odoo-13-doc.sales]
 file_filter = locale/<lang>/LC_MESSAGES/sales.po
 source_file = locale/sources/sales.pot
 source_lang = en

-[odoo-12-doc.website]
+[odoo-13-doc.website]
 file_filter = locale/<lang>/LC_MESSAGES/website.po
 source_file = locale/sources/website.pot
 source_lang = en
--- a/locale/sources/accounting.pot
+++ b/locale/sources/accounting.pot
--- a/locale/sources/crm.pot
+++ b/locale/sources/crm.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 12.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-07-03 08:44+0200\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -97,7 +97,7 @@ msgid "|image0|\\ |image1|"
 msgstr ""

 #: ../../crm/acquire_leads/generate_from_website.rst:16
-msgid "With the CRM app installed, you benefit from ready-to-use contact form on your Odoo website that will generate leads/opportunities automatically."
+msgid "With the CRM app installed, you benefit from a ready-to-use contact form on your Odoo website that will generate leads/opportunities automatically."
 msgstr ""

 #: ../../crm/acquire_leads/generate_from_website.rst:23
@ -110,23 +110,23 @@ msgid "Create a custom contact form"
 msgstr ""

 #: ../../crm/acquire_leads/generate_from_website.rst:34
-msgid "You may want to know more from your visitor when they use the contact form to contact you. You will then need to build a custom contact form on your website. Those contact forms can generate multiple types of records in the system (emails, leads/opportunities, project tasks, helpdesk tickets, etc...)"
+msgid "You may want to know more from your visitor when they use the contact form to you will need to build a custom contact form on your website. These contact forms can generate multiple types of records in the system (emails, leads/opportunities, project tasks, helpdesk tickets, etc.)"
 msgstr ""

 #: ../../crm/acquire_leads/generate_from_website.rst:43
-msgid "You will need to install the free *Form Builder* module. Only available in Odoo Enterprise."
+msgid "You will need to install the free *Form Builder* module, only available in Odoo Enterprise."
 msgstr ""

 #: ../../crm/acquire_leads/generate_from_website.rst:52
-msgid "From any page you want your contact form to be in, in edit mode, drag the form builder in the page and you will be able to add all the fields you wish."
+msgid "First, go to the page where you want to put your contact form. In edit mode, drag the form builder onto the page, and you will be able to add all the fields you wish."
 msgstr ""

 #: ../../crm/acquire_leads/generate_from_website.rst:59
-msgid "By default any new contact form will send an email, you can switch to lead/opportunity generation in *Change Form Parameters*."
+msgid "By default, any new contact form will send an email. You can switch to lead/opportunity generation in *Change Form Parameters*."
 msgstr ""

 #: ../../crm/acquire_leads/generate_from_website.rst:63
-msgid "If the same visitor uses the contact form twice, the second information will be added to the first lead/opportunity in the chatter."
+msgid "If the same visitor uses the contact form twice, the second entry will be added to the first lead/opportunity in the chatter."
 msgstr ""

 #: ../../crm/acquire_leads/generate_from_website.rst:67
@ -134,7 +134,7 @@ msgid "Generate leads instead of opportunities"
 msgstr ""

 #: ../../crm/acquire_leads/generate_from_website.rst:69
-msgid "When using a contact form, it is advised to use a qualification step before assigning to the right sales people. To do so, activate *Leads* in CRM settings and refer to :doc:`convert`."
+msgid "When using a contact form, you should use a qualification step before assigning the form to the right sales people. To do so, activate *Leads* in CRM settings and refer to :doc:`convert`."
 msgstr ""

 #: ../../crm/acquire_leads/send_quotes.rst:3
--- a/locale/sources/db_management.pot
+++ b/locale/sources/db_management.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 11.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-07-27 11:08+0200\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -93,123 +93,167 @@ msgid "Upgrade"
 msgstr ""

 #: ../../db_management/db_online.rst:53
-msgid "Make sure to be connected to the database you want to upgrade and access the database management page. On the line of the database you want to upgrade, click on the \"Upgrade\" button."
+msgid "Upgrading your database to a newer version of Odoo is a complex operation that require time and caution. It is extremely important that you fully test the process before upgrading your production database."
+msgstr ""
+
+#: ../../db_management/db_online.rst:57
+msgid "Odoo releases new versions regularly (at least once a year), and upgrading your database to enjoy new Odoo features is part of the Odoo Online experience."
 msgstr ""

 #: ../../db_management/db_online.rst:60
-msgid "You have the possibility to choose the target version of the upgrade. By default, we select the highest available version available for your database; if you were already in the process of testing a migration, we will automatically select the version you were already testing (even if we released a more recent version during your tests)."
+msgid "The upgrade process can take some time, especially if you use multiple apps or apps that manage sensitive data (e.g. Accounting, Inventory, etc.). In general, the 'smaller' the database, the quickest the upgrade. A single-user database that uses only CRM will be processed faster than a multi-company, multi-user database that uses Accounting, Sales, Purchase and Manufacturing."
 msgstr ""

 #: ../../db_management/db_online.rst:66
-msgid "By clicking on the \"Test upgrade\" button an upgrade request will be generated. If our automated system does not encounter any problem, you will receive a \"Test\" version of your upgraded database."
+msgid "Unfortunately, it is impossible to give time estimates for every upgrade request, since Odoo.com will test manually every database upgrade at least once and will need to correct/adapt changes made to the standard Odoo Apps (e.g. through Studio or through a Success Pack) on a case-by-case basis. This can make the process slower, since requests are treated in the order they arrive. This is especially true in the months following the release of a new major version, which can lengthen the upgrade delay significantly."
 msgstr ""

-#: ../../db_management/db_online.rst:73
-msgid "If our automatic system detect an issue during the creation of your test database, our dedicated team will have to work on it. You will be notified by email and the process will take up to 4 weeks."
+#: ../../db_management/db_online.rst:74
+msgid "The upgrade process is quite simple from your point of view:"
+msgstr ""
+
+#: ../../db_management/db_online.rst:76
+msgid "You request a test upgrade"
 msgstr ""

 #: ../../db_management/db_online.rst:77
-msgid "You will have the possibility to test it for 1 month. Inspect your data (e.g. accounting reports, stock valuation, etc.), check that all your usual flows work correctly (CRM flow, Sales flow, etc.)."
+msgid "Once all tests have been validated **by you**, you upgrade your actual database"
+msgstr ""
+
+#: ../../db_management/db_online.rst:79
+msgid "The process to request a test or a production (*actual*) upgrade is the same."
 msgstr ""

 #: ../../db_management/db_online.rst:81
-msgid "Once you are ready and that everything is correct in your test migration, you can click again on the Upgrade button, and confirm by clicking on Upgrade (the button with the little rocket!) to switch your production database to the new version."
+msgid "First, make sure to be connected to the database you want to upgrade and access the `database management page <https://www.odoo.com/my/databases>`__."
 msgstr ""

-#: ../../db_management/db_online.rst:89
-msgid "Your database will be taken offline during the upgrade (usually between 30min up to several hours for big databases), so make sure to plan your migration during non-business hours."
+#: ../../db_management/db_online.rst:84
+msgid "You have to have an active session with access to the Settings app in the database you want to upgrade for the button to be visible."
 msgstr ""

-#: ../../db_management/db_online.rst:96
-msgid "Duplicating a database"
+#: ../../db_management/db_online.rst:87
+msgid "On the line of the database you want to upgrade, click on the \"Cog\" menu. If an newer version of Odoo is available, you will see an 'Upgrade' button."
 msgstr ""

-#: ../../db_management/db_online.rst:98
-msgid "Database duplication, renaming, custom DNS, etc. is not available for trial databases on our Online platform. Paid Databases and \"One App Free\" database can duplicate without problem."
+#: ../../db_management/db_online.rst:94
+msgid "You have the possibility to choose the target version of the upgrade. By default, we select the highest available version available for your database; if you were already in the process of testing an upgrade, we will automatically select the version you were already testing (even if we released a more recent version during your tests)."
 msgstr ""

 #: ../../db_management/db_online.rst:103
-msgid "In the line of the database you want to duplicate, you will have a few buttons. To duplicate your database, just click **Duplicate**. You will have to give a name to your duplicate, then click **Duplicate Database**."
+msgid "By clicking on the \"Test upgrade\" button, an upgrade request will be generated. Only one request can be made at time for each database; if a request has already been made, you will see an 'Upgrade Queued' note instead and asking another request will not be possible."
 msgstr ""

-#: ../../db_management/db_online.rst:110
-msgid "If you do not check the \"For testing purposes\" checkbox when duplicating a database, all external communication will remain active:"
+#: ../../db_management/db_online.rst:108
+msgid "A test upgrade will create a copy of your database, upgrade it and make it available to you automatically once successful. If this is the first test you request for this particular database, a manual testing phase will be done by Odoo.com - this could take time (up to several weeks). Subsequent requests will not go through that manual testing step and will usually be made available in a few hours. Once the test database is available, you should receive an e-mail with the URL of the test database."
 msgstr ""

-#: ../../db_management/db_online.rst:113
-msgid "Emails are sent"
+#: ../../db_management/db_online.rst:116
+msgid "**Testing your database is the most important step of the upgrade process!** Even though we test all upgrades manually, we do not know your work processes. A change in standard worfklows of Odoo in new versions might require you to change internal processes, or some of the customizations you made through Odoo Studio might now work properly. *It is up to you to make sure that everything works as it should!* You can report issues with your test database through our `Support page <https://www.odoo.com/help>`__."
 msgstr ""

-#: ../../db_management/db_online.rst:115
-msgid "Payments are processed (in the e-commerce or Subscriptions apps, for example)"
-msgstr ""
-
-#: ../../db_management/db_online.rst:118
-msgid "Delivery orders (shipping providers) are sent"
-msgstr ""
-
-#: ../../db_management/db_online.rst:120
-msgid "Etc."
-msgstr ""
-
-#: ../../db_management/db_online.rst:122
-msgid "Make sure to check the checkbox \"For testing purposes\" if you want these behaviours to be disabled."
-msgstr ""
-
-#: ../../db_management/db_online.rst:125
-msgid "After a few seconds, you will be logged in your duplicated database. Notice that the url uses the name you chose for your duplicated database."
+#: ../../db_management/db_online.rst:124
+msgid "Make sure to do one last test of your upgrade right before the final upgrade (e.g. the day before) to ensure everything will run smoothly. Downgrading is not possible and post-poning an upgrade is always easier than being prevented to work by an upgrade issue after the fact!"
 msgstr ""

 #: ../../db_management/db_online.rst:129
-msgid "Duplicate databases expire automatically after 15 days."
-msgstr ""
-
-#: ../../db_management/db_online.rst:137
-msgid "Rename a Database"
+msgid "Once you are ready and you have validated all your tests, you can click again on the Upgrade button and confirm by clicking on Upgrade (the button with the little rocket!) to switch your production database to the new version. Your database will then be taken offline within the next 10 minutes and will be upgraded automatically; you receive a confirmation e-mail once the process is completed."
 msgstr ""

 #: ../../db_management/db_online.rst:139
-msgid "To rename your database, make sure you are connected to the database you want to rename, access the `database management page <https://www.odoo.com/my/databases>`__ and click **Rename**. You will have to give a new name to your database, then click **Rename Database**."
+msgid "Your database will be taken offline during the upgrade (usually between 30min up to several hours for big databases), so make sure to plan your migration during non-business hours."
 msgstr ""

-#: ../../db_management/db_online.rst:150
-msgid "Deleting a Database"
+#: ../../db_management/db_online.rst:146
+msgid "Duplicating a database"
 msgstr ""

-#: ../../db_management/db_online.rst:152
-msgid "You can only delete databases of which you are the administrator."
+#: ../../db_management/db_online.rst:148
+msgid "Database duplication, renaming, custom DNS, etc. is not available for trial databases on our Online platform. Paid Databases and \"One App Free\" database can duplicate without problem."
 msgstr ""

-#: ../../db_management/db_online.rst:154
-msgid "When you delete your database all the data will be permanently lost. The deletion is instant and for all the Users. We advise you to do an instant backup of your database before deleting it, since the last automated daily backup may be several hours old at that point."
+#: ../../db_management/db_online.rst:153
+msgid "In the line of the database you want to duplicate, you will have a few buttons. To duplicate your database, just click **Duplicate**. You will have to give a name to your duplicate, then click **Duplicate Database**."
 msgstr ""

 #: ../../db_management/db_online.rst:160
-msgid "From the `database management page <https://www.odoo.com/my/databases>`__, on the line of the database you want to delete, click on the \"Delete\" button."
+msgid "If you do not check the \"For testing purposes\" checkbox when duplicating a database, all external communication will remain active:"
 msgstr ""

-#: ../../db_management/db_online.rst:167
-msgid "Read carefully the warning message that will appear and proceed only if you fully understand the implications of deleting a database:"
+#: ../../db_management/db_online.rst:163
+msgid "Emails are sent"
 msgstr ""

-#: ../../db_management/db_online.rst:173
-msgid "After a few seconds, the database will be deleted and the page will reload automatically."
+#: ../../db_management/db_online.rst:165
+msgid "Payments are processed (in the e-commerce or Subscriptions apps, for example)"
 msgstr ""

-#: ../../db_management/db_online.rst:177
-msgid "If you need to re-use this database name, it will be immediately available."
+#: ../../db_management/db_online.rst:168
+msgid "Delivery orders (shipping providers) are sent"
+msgstr ""
+
+#: ../../db_management/db_online.rst:170
+msgid "Etc."
+msgstr ""
+
+#: ../../db_management/db_online.rst:172
+msgid "Make sure to check the checkbox \"For testing purposes\" if you want these behaviours to be disabled."
+msgstr ""
+
+#: ../../db_management/db_online.rst:175
+msgid "After a few seconds, you will be logged in your duplicated database. Notice that the url uses the name you chose for your duplicated database."
 msgstr ""

 #: ../../db_management/db_online.rst:179
+msgid "Duplicate databases expire automatically after 15 days."
+msgstr ""
+
+#: ../../db_management/db_online.rst:187
+msgid "Rename a Database"
+msgstr ""
+
+#: ../../db_management/db_online.rst:189
+msgid "To rename your database, make sure you are connected to the database you want to rename, access the `database management page <https://www.odoo.com/my/databases>`__ and click **Rename**. You will have to give a new name to your database, then click **Rename Database**."
+msgstr ""
+
+#: ../../db_management/db_online.rst:200
+msgid "Deleting a Database"
+msgstr ""
+
+#: ../../db_management/db_online.rst:202
+msgid "You can only delete databases of which you are the administrator."
+msgstr ""
+
+#: ../../db_management/db_online.rst:204
+msgid "When you delete your database all the data will be permanently lost. The deletion is instant and for all the Users. We advise you to do an instant backup of your database before deleting it, since the last automated daily backup may be several hours old at that point."
+msgstr ""
+
+#: ../../db_management/db_online.rst:210
+msgid "From the `database management page <https://www.odoo.com/my/databases>`__, on the line of the database you want to delete, click on the \"Delete\" button."
+msgstr ""
+
+#: ../../db_management/db_online.rst:217
+msgid "Read carefully the warning message that will appear and proceed only if you fully understand the implications of deleting a database:"
+msgstr ""
+
+#: ../../db_management/db_online.rst:223
+msgid "After a few seconds, the database will be deleted and the page will reload automatically."
+msgstr ""
+
+#: ../../db_management/db_online.rst:227
+msgid "If you need to re-use this database name, it will be immediately available."
+msgstr ""
+
+#: ../../db_management/db_online.rst:229
 msgid "It is not possible to delete a database if it is expired or linked to a Subscription. In these cases contact `Odoo Support <https://www.odoo.com/help>`__"
 msgstr ""

-#: ../../db_management/db_online.rst:183
+#: ../../db_management/db_online.rst:233
 msgid "If you want to delete your Account, please contact `Odoo Support <https://www.odoo.com/help>`__"
 msgstr ""

 #: ../../db_management/db_premise.rst:7
-msgid "On-premise Database management"
+msgid "On-premises Database management"
 msgstr ""

 #: ../../db_management/db_premise.rst:10
@ -229,8 +273,8 @@ msgid "If you are unable to register your database, you will likely encounter th
 msgstr ""

 #: ../../db_management/db_premise.rst:31
-#: ../../db_management/db_premise.rst:97
-#: ../../db_management/db_premise.rst:130
+#: ../../db_management/db_premise.rst:110
+#: ../../db_management/db_premise.rst:143
 msgid "Solutions"
 msgstr ""

@ -263,7 +307,7 @@ msgid "Do you have the updated version of Odoo 9?"
 msgstr ""

 #: ../../db_management/db_premise.rst:61
-#: ../../db_management/db_premise.rst:190
+#: ../../db_management/db_premise.rst:176
 msgid "From July 2016 onward, Odoo 9 now automatically change the uuid of a duplicated database; a manual operation is no longer required."
 msgstr ""

@ -279,107 +323,95 @@ msgstr ""
 msgid "For your information, we identify database with UUID. Therefore, each database should have a distinct UUID to ensure that registration and invoicing proceed effortlessly for your and for us."
 msgstr ""

+#: ../../db_management/db_premise.rst:80
+msgid "Check your network and firewall settings"
+msgstr ""
+
 #: ../../db_management/db_premise.rst:82
+msgid "The Update notification must be able to reach Odoo's subscription validation servers. In other words, make sure that the Odoo server is able to open outgoing connections towards:"
+msgstr ""
+
+#: ../../db_management/db_premise.rst:86
+msgid "services.odoo.com on port 443 (or 80)"
+msgstr ""
+
+#: ../../db_management/db_premise.rst:87
+msgid "services.openerp.com on port 443 (or 80) for older deployments"
+msgstr ""
+
+#: ../../db_management/db_premise.rst:89
+msgid "Once you activated your database, you must keep these ports open, as the Update notification runs once a week."
+msgstr ""
+
+#: ../../db_management/db_premise.rst:95
 msgid "Error message due to too many users"
 msgstr ""

-#: ../../db_management/db_premise.rst:84
+#: ../../db_management/db_premise.rst:97
 msgid "If you have more users in your local database than provisionned in your Odoo Enterprise subscription, you may encounter this message:"
 msgstr ""

-#: ../../db_management/db_premise.rst:93
+#: ../../db_management/db_premise.rst:106
 msgid "When the message appears you have 30 days before the expiration. The countdown is updated everyday."
 msgstr ""

-#: ../../db_management/db_premise.rst:99
+#: ../../db_management/db_premise.rst:112
 msgid "**Add more users** on your subscription: follow the link and Validate the upsell quotation and pay for the extra users."
 msgstr ""

-#: ../../db_management/db_premise.rst:102
+#: ../../db_management/db_premise.rst:115
 msgid "or"
 msgstr ""

-#: ../../db_management/db_premise.rst:104
-msgid "**Deactivate users** as explained in this `Documentation <https://www.odoo.com /documentation/user/11.0/db_management/documentation.html#deactivating-users>`__ and **Reject** the upsell quotation."
+#: ../../db_management/db_premise.rst:117
+msgid "**Deactivate users** as explained in this `Documentation <https://www.odoo.com /documentation/user/13.0/db_management/documentation.html#deactivating-users>`__ and **Reject** the upsell quotation."
 msgstr ""

-#: ../../db_management/db_premise.rst:109
+#: ../../db_management/db_premise.rst:122
 msgid "Once your database has the correct number of users, the expiration message will disappear automatically after a few days, when the next verification occurs. We understand that it can be a bit frightening to see the countdown, so you can :ref:`force an Update Notification <force_ping>`  to make the message disappear right away."
 msgstr ""

-#: ../../db_management/db_premise.rst:116
+#: ../../db_management/db_premise.rst:129
 msgid "Database expired error message"
 msgstr ""

-#: ../../db_management/db_premise.rst:118
+#: ../../db_management/db_premise.rst:131
 msgid "If your database reaches its expiration date before your renew your subscription, you will encounter this message:"
 msgstr ""

-#: ../../db_management/db_premise.rst:126
+#: ../../db_management/db_premise.rst:139
 msgid "This **blocking** message appears after a non-blocking message that lasts 30 days. If you fail to take action before the end of the countdown, the database is expired."
 msgstr ""

-#: ../../db_management/db_premise.rst:134
+#: ../../db_management/db_premise.rst:147
 msgid "Renew your subscription: follow the link and renew your subscription - note that"
 msgstr ""

-#: ../../db_management/db_premise.rst:133
+#: ../../db_management/db_premise.rst:146
 msgid "if you wish to pay by Wire Transfer, your subscription will effectively be renewed only when the payment arrives, which can take a few days. Credit card payments are processed immediately."
 msgstr ""

-#: ../../db_management/db_premise.rst:136
+#: ../../db_management/db_premise.rst:149
 msgid "Contact our `Support <https://www.odoo.com/help>`__"
 msgstr ""

-#: ../../db_management/db_premise.rst:138
+#: ../../db_management/db_premise.rst:151
 msgid "None of those solutions worked for you? Please contact our `Support <https://www.odoo.com/help>`__"
 msgstr ""

-#: ../../db_management/db_premise.rst:145
-msgid "Force an Update Notification"
-msgstr ""
-
-#: ../../db_management/db_premise.rst:147
-msgid "Update Notifications happen once every 7 days and keep your database up-to-date with your Odoo Enterprise subscription. If you modify your subscription (i.e. add more users, renew it for a year, etc.), your local database will only be made aware of the change once every 7 days - this can cause discrepancies between the state of your subscription and some notifications in your App Switcher. When doing such an operation on your subscription, you can force an Update using the following procedure:"
-msgstr ""
-
-#: ../../db_management/db_premise.rst:154
-msgid "Connect to the database with the **Administrator** account"
-msgstr ""
-
-#: ../../db_management/db_premise.rst:155
-msgid "Switch to the Developer mode by using the **About** option in the top-right menu (in V9) /  in **Settings**  (in V10): click on **Activate the developer mode**"
-msgstr ""
-
-#: ../../db_management/db_premise.rst:158
-msgid "Navigate to the \"Settings\" menu, then \"Technical\" > \"Automation\" > \"Scheduled Actions\""
-msgstr ""
-
 #: ../../db_management/db_premise.rst:160
-msgid "Find \"Update Notification\" in the list, click on it, and finally click on the button \"**RUN MANUALLY**\""
-msgstr ""
-
-#: ../../db_management/db_premise.rst:162
-msgid "Refresh the page, the \"Expiration\" notification should be gone"
-msgstr ""
-
-#: ../../db_management/db_premise.rst:165
-msgid "You may have kept the same UUID on different databases and we receive information from those databases too. So please read :ref:`this documentation <duplicate_premise>` to know how to change the UUID. After the change you can force a ping to speed up the verification, your production database will then be correctly identified."
-msgstr ""
-
-#: ../../db_management/db_premise.rst:174
 msgid "Duplicate a database"
 msgstr ""

-#: ../../db_management/db_premise.rst:176
+#: ../../db_management/db_premise.rst:162
 msgid "You can duplicate your database by accessing the database manager on your server (<odoo-server>/web/database/manager). In this page, you can easily duplicate your database (among other things)."
 msgstr ""

-#: ../../db_management/db_premise.rst:184
+#: ../../db_management/db_premise.rst:170
 msgid "When you duplicate a local database, it is **strongly** advised to change the duplicated database's uuid (Unniversally Unique Identifier), since this uuid is how your database identifies itself with our servers. Having two databases with the same uuid could result in invoicing problems or registration problems down the line."
 msgstr ""

-#: ../../db_management/db_premise.rst:193
+#: ../../db_management/db_premise.rst:179
 msgid "The database uuid is currently accessible from the menu **Settings > Technical > System Parameters**, we advise you to use a `uuid generator <https://www.uuidgenerator.net>`__ or to use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any other record by clicking on it and using the edit button."
 msgstr ""

--- a/locale/sources/discuss.pot
+++ b/locale/sources/discuss.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 11.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-10-19 10:03+0200\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -73,114 +73,114 @@ msgid "How to use a G Suite server"
 msgstr ""

 #: ../../discuss/email_servers.rst:48
-msgid "You can use an G Suite server for any Odoo hosting type. To do so you need to enable a SMTP relay and to allow *Any addresses* in the *Allowed senders* section. The configuration steps are explained in `Google documentation <https://support.google.com/a/answer/2956491?hl=en>`__."
+msgid "You can use an G Suite server for any Odoo hosting type. To do so you need to setup the SMTP relay service. The configuration steps are explained in `Google documentation <https://support.google.com/a/answer/2956491?hl=en>`__."
 msgstr ""

-#: ../../discuss/email_servers.rst:56
+#: ../../discuss/email_servers.rst:55
 msgid "Be SPF-compliant"
 msgstr ""

-#: ../../discuss/email_servers.rst:57
+#: ../../discuss/email_servers.rst:56
 msgid "In case you use SPF (Sender Policy Framework) to increase the deliverability of your outgoing emails, don't forget to authorize Odoo as a sending host in your domain name settings. Here is the configuration for Odoo Online:"
 msgstr ""

-#: ../../discuss/email_servers.rst:61
+#: ../../discuss/email_servers.rst:60
 msgid "If no TXT record is set for SPF, create one with following definition: v=spf1 include:_spf.odoo.com ~all"
 msgstr ""

-#: ../../discuss/email_servers.rst:63
+#: ../../discuss/email_servers.rst:62
 msgid "In case a SPF TXT record is already set, add \"include:_spf.odoo.com\". e.g. for a domain name that sends emails via Odoo Online and via G Suite it could be: v=spf1 include:_spf.odoo.com include:_spf.google.com ~all"
 msgstr ""

-#: ../../discuss/email_servers.rst:67
+#: ../../discuss/email_servers.rst:66
 msgid "Find `here <https://www.mail-tester.com/spf/>`__ the exact procedure to create or modify TXT records in your own domain registrar."
 msgstr ""

-#: ../../discuss/email_servers.rst:70
+#: ../../discuss/email_servers.rst:69
 msgid "Your new SPF record can take up to 48 hours to go into effect, but this usually happens more quickly."
 msgstr ""

-#: ../../discuss/email_servers.rst:73
+#: ../../discuss/email_servers.rst:72
 msgid "Adding more than one SPF record for a domain can cause problems with mail delivery and spam classification. Instead, we recommend using only one SPF record by modifying it to authorize Odoo."
 msgstr ""

-#: ../../discuss/email_servers.rst:78
+#: ../../discuss/email_servers.rst:77
 msgid "Allow DKIM"
 msgstr ""

-#: ../../discuss/email_servers.rst:79
+#: ../../discuss/email_servers.rst:78
 msgid "You should do the same thing if DKIM (Domain Keys Identified Mail) is enabled on your email server. In the case of Odoo Online & Odoo.sh, you should add a DNS \"odoo._domainkey\" CNAME record to \"odoo._domainkey.odoo.com\". For example, for \"foo.com\" they should have a record \"odoo._domainkey.foo.com\" that is a CNAME with the value \"odoo._domainkey.odoo.com\"."
 msgstr ""

-#: ../../discuss/email_servers.rst:87
+#: ../../discuss/email_servers.rst:86
 msgid "How to manage inbound messages"
 msgstr ""

-#: ../../discuss/email_servers.rst:89
+#: ../../discuss/email_servers.rst:88
 msgid "Odoo relies on generic email aliases to fetch incoming messages."
 msgstr ""

-#: ../../discuss/email_servers.rst:91
+#: ../../discuss/email_servers.rst:90
 msgid "**Reply messages** of messages sent from Odoo are routed to their original discussion thread (and to the inbox of all its followers) by the catchall alias (**catchall@**)."
 msgstr ""

-#: ../../discuss/email_servers.rst:95
+#: ../../discuss/email_servers.rst:94
 msgid "**Bounced messages** are routed to **bounce@** in order to track them in Odoo. This is especially used in `Odoo Email Marketing <https://www.odoo.com/page/email-marketing>`__ to opt-out invalid recipients."
 msgstr ""

-#: ../../discuss/email_servers.rst:99
+#: ../../discuss/email_servers.rst:98
 msgid "**Original messages**: Several business objects have their own alias to create new records in Odoo from incoming emails:"
 msgstr ""

-#: ../../discuss/email_servers.rst:102
+#: ../../discuss/email_servers.rst:101
 msgid "Sales Channel (to create Leads or Opportunities in `Odoo CRM <https://www.odoo.com/page/crm>`__),"
 msgstr ""

-#: ../../discuss/email_servers.rst:104
+#: ../../discuss/email_servers.rst:103
 msgid "Support Channel (to create Tickets in `Odoo Helpdesk <https://www.odoo.com/page/helpdesk>`__),"
 msgstr ""

-#: ../../discuss/email_servers.rst:106
+#: ../../discuss/email_servers.rst:105
 msgid "Projects (to create new Tasks in `Odoo Project <https://www.odoo.com/page/project-management>`__),"
 msgstr ""

-#: ../../discuss/email_servers.rst:108
+#: ../../discuss/email_servers.rst:107
 msgid "Job Positions (to create Applicants in `Odoo Recruitment <https://www.odoo.com/page/recruitment>`__),"
 msgstr ""

-#: ../../discuss/email_servers.rst:110
+#: ../../discuss/email_servers.rst:109
 msgid "etc."
 msgstr ""

-#: ../../discuss/email_servers.rst:112
+#: ../../discuss/email_servers.rst:111
 msgid "Depending on your mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Odoo alias in your mail server."
 msgstr ""

-#: ../../discuss/email_servers.rst:116
+#: ../../discuss/email_servers.rst:115
 msgid "Create the corresponding email addresses in your mail server (catchall@, bounce@, sales@, etc.)."
 msgstr ""

-#: ../../discuss/email_servers.rst:118
+#: ../../discuss/email_servers.rst:117
 msgid "Set your domain name in the General Settings."
 msgstr ""

-#: ../../discuss/email_servers.rst:123
+#: ../../discuss/email_servers.rst:122
 msgid "If you use Odoo on-premise, create an *Incoming Mail Server* in Odoo for each alias. You can do it from the General Settings as well. Fill out the form according to your email provider’s settings. Leave the *Actions to Perform on Incoming Mails* blank. Once all the information has been filled out, click on *TEST & CONFIRM*."
 msgstr ""

-#: ../../discuss/email_servers.rst:132
+#: ../../discuss/email_servers.rst:131
 msgid "If you use Odoo Online or Odoo.sh, We do recommend to redirect incoming messages to Odoo's domain name rather than exclusively use your own email server. That way you will receive incoming messages without delay. Indeed, Odoo Online is fetching incoming messages of external servers once per hour only. You should set redirections for all the email addresses to Odoo's domain name in your email server (e.g. *catchall@mydomain.ext* to *catchall@mycompany.odoo.com*)."
 msgstr ""

-#: ../../discuss/email_servers.rst:139
+#: ../../discuss/email_servers.rst:138
 msgid "All the aliases are customizable in Odoo. Object aliases can be edited from their  respective configuration view. To edit catchall and bounce aliases, you first need to activate the developer mode from the Settings Dashboard."
 msgstr ""

-#: ../../discuss/email_servers.rst:147
+#: ../../discuss/email_servers.rst:146
 msgid "Then refresh your screen and go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (*mail.catchall.alias* & * mail.bounce.alias*)."
 msgstr ""

-#: ../../discuss/email_servers.rst:154
+#: ../../discuss/email_servers.rst:153
 msgid "By default inbound messages are fetched every 5 minutes in Odoo on-premise. You can change this value in developer mode. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*."
 msgstr ""

--- a/locale/sources/ecommerce.pot
+++ b/locale/sources/ecommerce.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 11.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-10-19 10:03+0200\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -462,7 +462,7 @@ msgid "You can access the web page from the detail form by clicking the *Publish
 msgstr ""

 #: ../../ecommerce/maximizing_revenue/upselling.rst:3
-msgid "How to sell pricier product alternatives (upselling)"
+msgid "How to sell pricier alternative products (upselling)"
 msgstr ""

 #: ../../ecommerce/maximizing_revenue/upselling.rst:5
@ -570,7 +570,6 @@ msgid "Once ready, switch to **Production** mode."
 msgstr ""

 #: ../../ecommerce/shopper_experience/authorize.rst:30
-#: ../../ecommerce/shopper_experience/paypal.rst:74
 msgid "Set up Odoo"
 msgstr ""

@ -587,7 +586,6 @@ msgid "To get those credentials in Authorize.Net, you can rely on *API Login ID
 msgstr ""

 #: ../../ecommerce/shopper_experience/authorize.rst:47
-#: ../../ecommerce/shopper_experience/paypal.rst:102
 msgid "Go live"
 msgstr ""

@ -620,13 +618,11 @@ msgid "To perform ficticious transactions you can use fake card numbers provided
 msgstr ""

 #: ../../ecommerce/shopper_experience/authorize.rst:76
-#: ../../ecommerce/shopper_experience/paypal.rst:154
 msgid ":doc:`payment`"
 msgstr ""

 #: ../../ecommerce/shopper_experience/authorize.rst:77
 #: ../../ecommerce/shopper_experience/payment.rst:111
-#: ../../ecommerce/shopper_experience/paypal.rst:155
 msgid ":doc:`payment_acquirer`"
 msgstr ""

@ -844,137 +840,205 @@ msgid "With other payment acquirers, you can manage the capture in their own int
 msgstr ""

 #: ../../ecommerce/shopper_experience/paypal.rst:3
-msgid "How to get paid with Paypal"
+msgid "Configure your Paypal account"
 msgstr ""

 #: ../../ecommerce/shopper_experience/paypal.rst:5
-msgid "Paypal is the easiest online payment acquirer to configure. It is also the only one without any subscription fee. We definitely advise it to any starter."
+msgid "Paypal is available and popular worldwide. It doesn’t charge any subscription fee and creating an account is very easy. That’s why we definitely recommend it for starters in Odoo. It works as a seamless flow where the customer is routed to Paypal website to register the payment."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:11
-msgid "Set up your Paypal account"
+#: ../../ecommerce/shopper_experience/paypal.rst:12
+msgid "Paypal account"
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:13
-msgid "Create a `Paypal Business Account <https://www.paypal.com>`__ or upgrade your account to *Business account* if you have a basic account."
+#: ../../ecommerce/shopper_experience/paypal.rst:14
+msgid "A business account is needed to get paid with Paypal. Create a  `Paypayl Business Account <https://www.paypal.com/us/merchantsignup/applicationChecklist?signupType=CREATE_NEW_ACCOUNT&productIntentId=wp_standard>`__ or upgrade your Personal account to a Business account. Go to the Paypal settings and click on *Upgrade to a Business account*. Then follow the few configuration steps."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:16
-msgid "Log in to `Paypal <https://www.paypal.com>`__ and open the settings of your **Profile**."
+#: ../../ecommerce/shopper_experience/paypal.rst:18
+msgid "Settings in Paypal"
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:22
-msgid "Now enter the menu **My selling tools**."
+#: ../../ecommerce/shopper_experience/paypal.rst:21
+msgid "First, let’s see how to set up your Paypal account in order to build a seamless customer experience with Odoo."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:27
-msgid "Let's start with the **Website Preferences**."
+#: ../../ecommerce/shopper_experience/paypal.rst:23
+msgid "Log in and open the settings. Go to *Products & Services > Website payments* and click *Update* on *Website preferences*."
 msgstr ""

 #: ../../ecommerce/shopper_experience/paypal.rst:29
-msgid "Turn on **Auto Return** and enter the **Return URL**: <odoo_instance_url>/shop/confirmation. Verify that this address uses the correct protocol (HTTP/HTTPS)."
+msgid "Auto Return"
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:31
+msgid "*Auto Return* automatically redirects your customers to Odoo once the payment is processed. Check *Auto Return* and enter your domain name \"/shop/confirmation\" as *Return URL* (e.g. https://yourcompany.odoo.com/shop/confirmation)."
 msgstr ""

 #: ../../ecommerce/shopper_experience/paypal.rst:36
-msgid "Turn on **Payment Data Transfer**. When saving, an **Identity Token** is generated. You will be later requested to enter it in Odoo."
+msgid "This URL is requested in Paypal but not used in practice as Odoo transmits it at each transaction. Don’t worry if you manage several sales channels or Odoo databases."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:43
-msgid "Then, get back to your profile to activate the **Instant Payment Notification (IPN)** in *My selling tools*."
+#: ../../ecommerce/shopper_experience/paypal.rst:44
+msgid "Payment Data Transfer (PDT)"
 msgstr ""

 #: ../../ecommerce/shopper_experience/paypal.rst:46
-msgid "Enter the **Notification URL**: <odoo_instance_url>/payment/paypal/ipn"
+msgid "*Payment Data Transfer* delivers the payment confirmation to Odoo as soon as it is processed. Without it, Odoo cannot end the sales flow. This setting must be activated as well. When saving, an *Identity Token* is generated. You will be later requested to enter it in Odoo."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:51
-msgid "Now you must change the encoding format of the payment request sent by Odoo to Paypal. To do so, get back to *My selling tools* and click **PayPal button language encoding** in *More Selling Tools* section."
+#: ../../ecommerce/shopper_experience/paypal.rst:54
+msgid "Paypal Account Optional"
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:58
-msgid "Then, click *More Options* and set the two default encoding formats as **UTF-8**."
+#: ../../ecommerce/shopper_experience/paypal.rst:56
+msgid "We advise you to not prompt customers to log in with a Paypal account when they get to pay. Let them pay with debit/credit cards as well, or you might lose some deals. Make sure this setting is turned on."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:66
-msgid "If you want your customers to pay without creating a Paypal account, **Paypal Account Optional** needs to be turned on."
+#: ../../ecommerce/shopper_experience/paypal.rst:63
+msgid "Instant Payment Notification (IPN)"
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:65
+msgid "PDT sends order confirmations once and only once. As a result, your site must be running when it happens; otherwise, it will never receive the message. That’s why we advise to activate the *Instant Payment Notification* (IPN) on top. With IPN, delivery of order confirmations is virtually guaranteed since IPN resends a confirmation until your site acknowledges receipt."
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:72
+msgid "To activate IPN, get back to *Website payments* menu and click *Update* in *Instant Payment Notification*."
 msgstr ""

 #: ../../ecommerce/shopper_experience/paypal.rst:75
-msgid "Open Paypal setup form in :menuselection:`Website or Sales or Accounting --> Settings --> Payment Acquirers+`. Enter both your **Email ID** and your **Merchant ID** and check **Use IPN**."
+msgid "The *Notification URL* to set is your domain name + “payment/paypal/ipn” (e.g. https://yourcompany.odoo.com/payment/paypal/ipn)."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:82
-msgid "They are both provided in your Paypal profile, under :menuselection:`My business info`."
+#: ../../ecommerce/shopper_experience/paypal.rst:81
+msgid "Payment Messages Format"
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:85
-msgid "Enter your **Identity Token** in Odoo (from *Auto Return* option). To do so, open the *Settings* and activate the **Developer Mode**."
+#: ../../ecommerce/shopper_experience/paypal.rst:83
+msgid "Finally make sure the encoding format of payment messages is correctly set. Go to *PayPal button language encoding*."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:91
-msgid "Then, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` and create a parameter with following values:"
+#: ../../ecommerce/shopper_experience/paypal.rst:89
+msgid "Click *More Options* and set the two default encoding formats as *UTF-8*."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:94
-msgid "Key: payment_paypal.pdt_token"
+#: ../../ecommerce/shopper_experience/paypal.rst:98
+msgid "Your Paypal account is ready!"
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:95
-msgid "Value: your Paypal *Identity Token*"
+#: ../../ecommerce/shopper_experience/paypal.rst:100
+msgid "For Encrypted Website Payments & EWP_SETTINGS error, please check the `paypal documentation. <https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/encryptedwebpayments/#encrypted-website-payments-ewp>`__"
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:103
-msgid "Your configuration is now ready! You can make Paypal visible on your merchant interface and activate the **Production mode**."
+#: ../../ecommerce/shopper_experience/paypal.rst:104
+msgid "Settings in Odoo"
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:112
-msgid "Transaction fees"
+#: ../../ecommerce/shopper_experience/paypal.rst:107
+msgid "Activation"
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:114
-msgid "You can charge an extra to the customer to cover the transaction fees Paypal charges you. Once redirected to Paypal, your customer sees an extra applied to the order amount."
+#: ../../ecommerce/shopper_experience/paypal.rst:109
+msgid "Activate *Paypal* from the config bar of Sales, Invoicing and eCommerce apps, or from the configuration menu of *Payment Acquirers*."
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:113
+msgid "Credentials"
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:115
+msgid "Odoo requires three Paypal credentials:"
 msgstr ""

 #: ../../ecommerce/shopper_experience/paypal.rst:117
-msgid "To activate this, go to the *Configuration* tab of Paypal config form in Odoo and check *Add Extra Fees*. Default fees for US can be seen here below."
+msgid "*Email ID* is your login email address in Paypal."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:123
-msgid "To apply the right fees for your country, please refer to `Paypal Fees <https://www.paypal.com/webapps/mpp/paypal-fees>`__."
+#: ../../ecommerce/shopper_experience/paypal.rst:119
+msgid "*Merchant ID* can be found in the settings of your Paypal account, in *Profile > About the business*."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:128
-msgid "Test the payment flow"
+#: ../../ecommerce/shopper_experience/paypal.rst:121
+msgid "*Paypal PDT Token* is given in *Website payments* configuration as explained here above."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:130
-msgid "You can test the entire payment flow thanks to Paypal Sandbox accounts."
+#: ../../ecommerce/shopper_experience/paypal.rst:127
+msgid "Transaction fees"
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:129
+msgid "You can charge extra fees to your customers for paying with Paypal; This to cover the transaction fees Paypal charges you. Once redirected to Paypal, your customer sees an extra applied to the order amount."
 msgstr ""

 #: ../../ecommerce/shopper_experience/paypal.rst:132
-msgid "Log in to `Paypal Developer Site <https://developer.paypal.com>`__ with your Paypal credentials. This will create two sandbox accounts:"
+msgid "To activate this, go to the Configuration tab of Paypal configuration in Odoo and check *Add Extra Fees*."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:136
-msgid "A business account (to use as merchant, e.g. pp.merch01-facilitator@example.com)."
+#: ../../ecommerce/shopper_experience/paypal.rst:138
+msgid "You can refer to `Paypal Fees <https://www.paypal.com/webapps/mpp/paypal-fees>`__ to set up fees."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:137
-msgid "A default personal account (to use as shopper, e.g. pp.merch01-buyer@example.com)."
+#: ../../ecommerce/shopper_experience/paypal.rst:141
+msgid "..note:: `Traders in the EU <https://europa.eu/youreurope/citizens/consumers/shopping/pricing-payments/index_en.htm>`__ are not allowed to charge extra fees for paying with credit cards."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:139
-msgid "Log in to `Paypal Sandbox <https://www.sandbox.paypal.com>`__ with the merchant account and follow the same configuration instructions."
+#: ../../ecommerce/shopper_experience/paypal.rst:145
+msgid "Go live!"
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:142
-msgid "Enter your sandbox credentials in Odoo and make sure Paypal is still set on *Test* mode. Also, make sure the confirmation mode of Paypal is not *Authorize & capture the amount, confirm the SO and auto-validate the invoice on acquirer confirmation*. Otherwise a confirmed invoice will be automatically generated when the transaction is completed."
+#: ../../ecommerce/shopper_experience/paypal.rst:147
+msgid "Your configuration is ready to roll. Make sure *Production* mode is on. Then publish the payment method by clicking the *Published* button right next to it."
 msgstr ""

-#: ../../ecommerce/shopper_experience/paypal.rst:150
+#: ../../ecommerce/shopper_experience/paypal.rst:156
+msgid "Paypal is now available in your payment form available in eCommerce, Sales and Invoicing apps. Customers are redirected to Paypal website when hitting *Pay Now*. They get back to a confirmation page in Odoo once the payment is processed."
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:165
+msgid "Test environment"
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:167
+msgid "You can test the entire payment flow in Odoo thanks to Paypal Sandbox accounts."
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:169
+msgid "Log in to `Paypal Developer Site <https://developer.paypal.com/>`__ with your Paypal credentials."
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:171
+msgid "This will create two sandbox accounts:"
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:173
+msgid "A business account (to use as merchant, e.g. `pp.merch01-facilitator@example.com <mailto:pp.merch01-facilitator@example.com>`__)."
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:175
+msgid "A default personal account (to use as shopper, e.g. `pp.merch01-buyer@example.com <mailto:pp.merch01-buyer@example.com>`__)."
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:177
+msgid "Log in to Paypal Sandbox with the merchant account and follow the same configuration instructions. Enter your sandbox credentials in Odoo and make sure Paypal is still set on *Test Environment*. Also, make sure the automatic invoicing is not activated in your eCommerce settings, to not generate invoices when a fictitious transaction is completed."
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:183
 msgid "Run a test transaction from Odoo using the sandbox personal account."
 msgstr ""

+#: ../../ecommerce/shopper_experience/paypal.rst:185
+msgid "See also"
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:187
+msgid "`How to manage orders paid with payment acquirers <https://www.odoo.com/documentation/user/13.0/ecommerce/shopper_experience/payment.html>`__"
+msgstr ""
+
+#: ../../ecommerce/shopper_experience/paypal.rst:189
+msgid "`How to manage orders paid with payment acquirers <https://www.odoo.com/documentation/user/13.0/ecommerce/shopper_experience/payment_acquirer.html>`__"
+msgstr ""
+
 #: ../../ecommerce/shopper_experience/portal.rst:3
 msgid "How customers can access their customer account"
 msgstr ""
--- a/locale/sources/general.pot
+++ b/locale/sources/general.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 12.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-11-07 15:38+0100\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -24,6 +24,14 @@ msgstr ""
 msgid "Authentication"
 msgstr ""

+#: ../../general/auth/azure.rst:3
+msgid "OAuth"
+msgstr ""
+
+#: ../../general/auth/azure.rst:5
+msgid "Due to specific requirements in Azure's OAuth implementation, Microsoft Azure OAuth identification is NOT compatible with Odoo at the moment."
+msgstr ""
+
 #: ../../general/auth/google.rst:3
 msgid "How to allow users to sign in with their Google account"
 msgstr ""
@ -64,6 +72,50 @@ msgstr ""
 msgid "Once done, you receive two information (your Client ID and Client Secret). You have to insert your Client ID in the **General Settings**."
 msgstr ""

+#: ../../general/auth/ldap.rst:3
+msgid "How to allow users to sign in with LDAP"
+msgstr ""
+
+#: ../../general/auth/ldap.rst:5
+msgid "Install the LDAP module in General Settings."
+msgstr ""
+
+#: ../../general/auth/ldap.rst:7
+msgid "Click on **Create** in Setup your LDAP Server."
+msgstr ""
+
+#: ../../general/auth/ldap.rst:15
+msgid "Choose the company about to use the LDAP."
+msgstr ""
+
+#: ../../general/auth/ldap.rst:20
+msgid "In **Server Information**, enter the IP address of your server and the port it listens to."
+msgstr ""
+
+#: ../../general/auth/ldap.rst:22
+msgid "Tick **User TLS** if your server is compatible."
+msgstr ""
+
+#: ../../general/auth/ldap.rst:27
+msgid "In **Login Information**, enter ID and password of the account used to query the server. If left empty, the server will be queried anonymously."
+msgstr ""
+
+#: ../../general/auth/ldap.rst:32
+msgid "In **Process Parameter**, enter the domain name of your LDAP server in LDAP nomenclature (e.g. ``dc=example,dc=com``)."
+msgstr ""
+
+#: ../../general/auth/ldap.rst:34
+msgid "In **LDAP filter**, enter ``uid=%s``"
+msgstr ""
+
+#: ../../general/auth/ldap.rst:39
+msgid "In **User Information**, tick *Create User* if you want Odoo to create a User profile the first time someone log in with LDAP."
+msgstr ""
+
+#: ../../general/auth/ldap.rst:41
+msgid "In **Template User**, indicate a template for the new profiles created. If left blanked, the admin profile will be used as template."
+msgstr ""
+
 #: ../../general/base_import.rst:3
 msgid "Data Import"
 msgstr ""
@ -198,7 +250,7 @@ msgid "Where can I change the date import format?"
 msgstr ""

 #: ../../general/base_import/import_faq.rst:81
-msgid "Odoo can automatically detect if a column is a date and it will try to guess the date format from a set of most used date format. While this process can work for a lot of simple date format, some exotic date format will not be recognize and it is also possible to have some confusion (day and month inverted as example) as it is difficult to guess correctly which part is the day and which one is the month in a date like '01-03-2016'."
+msgid "Odoo can automatically detect if a column is a date, and it will try to guess the date format from a set of most commonly used date formats. While this process can work for many date formats, some date formats will not be recognized. This can cause confusion due to day-month inversions; it is difficult to guess which part of a date format is the day and which part is the month in a date such as '01-03-2016'."
 msgstr ""

 #: ../../general/base_import/import_faq.rst:83
@ -505,6 +557,14 @@ msgstr ""
 msgid "`Deactivating Users <../../db_management/documentation.html#deactivating-users>`_"
 msgstr ""

+#: ../../general/odoo_basics/add_user.rst:47
+msgid "Todo"
+msgstr ""
+
+#: ../../general/odoo_basics/add_user.rst:47
+msgid "Add link to How to add companies"
+msgstr ""
+
 #: ../../general/odoo_basics/choose_language.rst:3
 msgid "Manage Odoo in your own language"
 msgstr ""
@ -569,43 +629,59 @@ msgstr ""
 msgid "How to generate an Unsplash access key"
 msgstr ""

-#: ../../general/unsplash/unsplash_access_key.rst:5
+#: ../../general/unsplash/unsplash_access_key.rst:6
+msgid "**As an SaaS user**, you are ready to use Unsplash. You won't need to follow this guide to set up Unsplash informations, since you will use our own Odoo Unsplash key in a transparent way."
+msgstr ""
+
+#: ../../general/unsplash/unsplash_access_key.rst:9
+msgid "Generate an Unsplash access key for **non-Saas** users"
+msgstr ""
+
+#: ../../general/unsplash/unsplash_access_key.rst:11
 msgid "Create an account on `Unsplash.com <https://unsplash.com/join>`_."
 msgstr ""

-#: ../../general/unsplash/unsplash_access_key.rst:7
+#: ../../general/unsplash/unsplash_access_key.rst:13
 msgid "Go to your `applications dashboard <https://unsplash.com/oauth/applications>`_ and click on **New Application**."
 msgstr ""

-#: ../../general/unsplash/unsplash_access_key.rst:12
+#: ../../general/unsplash/unsplash_access_key.rst:18
 msgid "Accept the conditions and click on **Accept terms**."
 msgstr ""

-#: ../../general/unsplash/unsplash_access_key.rst:17
-msgid "You will be prompted to insert an **Application name** and a **Description**. Once done, click on **Create application**."
+#: ../../general/unsplash/unsplash_access_key.rst:23
+msgid "You will be prompted to insert an **Application name** and a **Description**. Please prefix your application name by \"**Odoo:** \" so that Unsplash can recognize it as an Odoo instance. Once done, click on **Create application**."
 msgstr ""

-#: ../../general/unsplash/unsplash_access_key.rst:22
+#: ../../general/unsplash/unsplash_access_key.rst:28
 msgid "You should be redirected to your application details page. Scroll down a bit to find your **access key**."
 msgstr ""

+#: ../../general/unsplash/unsplash_access_key.rst:34
+msgid "**As a non-SaaS user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a restriction of 50 Unsplash requests per hour."
+msgstr ""
+
+#: ../../general/unsplash/unsplash_access_key.rst:37
+msgid ":doc:`unsplash_application_id`"
+msgstr ""
+
 #: ../../general/unsplash/unsplash_application_id.rst:3
 msgid "How to generate an Unsplash application ID"
 msgstr ""

-#: ../../general/unsplash/unsplash_application_id.rst:5
-msgid "You should first create and set up your Unsplash application with this tutorial: `How to generate an Unsplash access key <https://www.odoo.com/documentation/user/unsplash_access_key.html>`_."
+#: ../../general/unsplash/unsplash_application_id.rst:6
+msgid "You should first create and set up your Unsplash application with this tutorial: :doc:`unsplash_access_key`."
 msgstr ""

-#: ../../general/unsplash/unsplash_application_id.rst:7
+#: ../../general/unsplash/unsplash_application_id.rst:8
 msgid "Go to your `applications dashboard <https://unsplash.com/oauth/applications>`_ and click on your newly created Unsplash application under **Your applications**."
 msgstr ""

-#: ../../general/unsplash/unsplash_application_id.rst:12
-msgid "You will be redirected to your application details page. The **application ID** will be visible in your browser's URL. The URL should be something like ``https://unsplash.com/oauth/applications/application_id``"
+#: ../../general/unsplash/unsplash_application_id.rst:13
+msgid "You will be redirected to your application details page. The **application ID** will be visible in your browser's URL. The URL should be something like ``https://unsplash.com/oauth/applications/<application_id>``"
 msgstr ""

-#: ../../general/unsplash/unsplash_application_id.rst:17
-msgid "Note that if you `apply for a production account <https://unsplash.com/documentation#registering-your-application>`_ and it got approved, your will also find your application ID in the UI. It will be listed next to your **Access Key** on your application details page."
+#: ../../general/unsplash/unsplash_application_id.rst:19
+msgid "**As a non-SaaS user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a 50 Unsplash requests per hour restriction."
 msgstr ""

--- a/locale/sources/getting_started.pot
+++ b/locale/sources/getting_started.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 12.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-11-07 15:38+0100\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -93,7 +93,7 @@ msgid "**The GAP Analysis**: The comparison of the request with the standard fea
 msgstr ""

 #: ../../getting_started/documentation.rst:118
-msgid "`The User Story <https://help.rallydev.com/writing-great-user-story>`__: This technique clearly separates the responsibilities between the SPoC, responsible for explaining the WHAT, the WHY and the WHO, and the Consultant who will provide a response to the HOW."
+msgid "**The User Story**: This technique clearly separates the responsibilities between the SPoC, responsible for explaining the WHAT, the WHY and the WHO, and the Consultant who will provide a response to the HOW."
 msgstr ""

 #: ../../getting_started/documentation.rst:126
@ -213,70 +213,10 @@ msgid "8. Support"
 msgstr ""

 #: ../../getting_started/documentation.rst:255
-msgid "Your Odoo Online subscription includes **unlimited 24hr support at no extra cost, Monday to Friday**. Our teams are located around the world to ensure you have support, no matter your location. Your support representative could be communicating to you from San Francisco, Belgium, or India!"
+msgid "When your project is put in production, our support teams take care of your questions or technical issues."
 msgstr ""

-#: ../../getting_started/documentation.rst:260
-msgid "What kind of support is included?"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:262
-msgid "Providing you with relevant material (guidelines, product documentation, etc...)"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:264
-msgid "Answers to issues that you may encounter in your standard Odoo database (eg. “I cannot close my Point of Sale” or “I cannot find my sales KPIs?”)"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:266
-msgid "Questions related to your account, subscription, or billing"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:267
-msgid "Bug resolution (blocking issues or unexpected behaviour not due to misconfiguration or customization)"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:269
-msgid "Issues that might occur in a test database after upgrading to a newer version"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:271
-msgid "*Odoo Support does not make changes to your production database, but gives you the material and knowledge to do it yourself!*"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:274
-msgid "What kind of support is not included?"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:276
-msgid "Questions that require us to understand your business processes in order to help you implement your database"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:278
-msgid "Training on how to use our software (we will direct you to our many resources)"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:279
-msgid "Importation of documents into your database"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:280
-msgid "Guidance on which configurations to apply inside of an application or the database"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:281
-msgid "How to set up configuration models (Examples include: Inventory Routes, Payment Terms, Warehouses, etc)"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:283
-msgid "Questions or issues related to specific developments or customizations done either by Odoo or a third party (this is specific only to your database or involving code)"
-msgstr ""
-
-#: ../../getting_started/documentation.rst:287
-msgid "You can get this type of support with a `Success Pack <https://www.odoo.com/pricing-packs>`__. With a pack, one of our consultants will analyze the way your business runs and tell you how you can get the most out of your Odoo Database. We will handle all configurations and coach you on how to use Odoo."
-msgstr ""
-
-#: ../../getting_started/documentation.rst:292
-msgid "Our support team can be contacted through our `online support form <https://www.odoo.com/help>`__."
+#: ../../getting_started/documentation.rst:258
+msgid "See :ref:`support-expectations`."
 msgstr ""

--- a/locale/sources/helpdesk.pot
+++ b/locale/sources/helpdesk.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 11.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-10-19 10:03+0200\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -93,7 +93,7 @@ msgid "Live Chat allows your customers to submit a ticket via Live Chat on your
 msgstr ""

 #: ../../helpdesk/getting_started.rst:86
-msgid "The final option to submit tickets is thru an API connection. View the documentation `*here* <https://www.odoo.com/documentation/11.0/webservices/odoo.html>`__."
+msgid "The final option to submit tickets is thru an API connection. View the documentation `*here* <https://www.odoo.com/documentation/13.0/webservices/odoo.html>`__."
 msgstr ""

 #: ../../helpdesk/getting_started.rst:91
--- a/locale/sources/inventory.pot
+++ b/locale/sources/inventory.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 12.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-11-07 15:38+0100\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -269,11 +269,11 @@ msgid "If you scan products at a computer location, the **USB scanner** is the w
 msgstr ""

 #: ../../inventory/barcode/setup/hardware.rst:25
-msgid "The **bluetooth scanner** can be paired with a smartphone or a tablet and is a good choice if you want to be mobile but don't need a big investment. An approach is to log in Odoo on you smartphone, pair the bluetooth scanner with the smartphone and work in the warehouse with always the possibility to check your smartphone from time to time and use the software 'manually'."
+msgid "The **bluetooth scanner** can be paired with a smartphone or a tablet and is a good choice if you want to be mobile but don't need a big investment. An approach is to log in Odoo on you smartphone, pair the bluetooth scanner with the smartphone and work in the warehouse with the possibility to check your smartphone from time to time and use the software 'manually'."
 msgstr ""

 #: ../../inventory/barcode/setup/hardware.rst:32
-msgid "For heavy use, the **mobile computer scanner** is the handiest solution. It consists in a small computer with a built-in barcode scanner. This one can turn out to be a very productive solution, however you need to make sure that is is capable of running Odoo smoothy. The most recent models using Android + Google Chrome or Windows + Internet Explorer Mobile should do the job. However, due to the variety of models and configurations on the market, it is essential to test it first."
+msgid "For heavy use, the **mobile computer scanner** is the handiest solution. It consists of a small computer with a built-in barcode scanner. This one can turn out to be a very productive solution, however you need to make sure that is is capable of running Odoo smoothly. The most recent models using Android + Google Chrome or Windows + Internet Explorer Mobile should do the job. However, due to the variety of models and configurations on the market, it is essential to test it first."
 msgstr ""

 #: ../../inventory/barcode/setup/hardware.rst:42
@ -304,47 +304,39 @@ msgstr ""
 msgid "The barcode scanning features can save you a lot of the time usually lost switching between the keyboard, the mouse and the scanner. Properly attributing barcodes to products, pickings locations, etc. allows you to work more efficiently by controlling the software almost exclusively with the barcode scanner."
 msgstr ""

-#: ../../inventory/barcode/setup/software.rst:17
-msgid "Print this document to be able to use your barcode scanner to perform more actions."
-msgstr ""
-
-#: ../../inventory/barcode/setup/software.rst:19
-msgid "Document: |download_barcode|"
-msgstr ""
-
-#: ../../inventory/barcode/setup/software.rst:23
+#: ../../inventory/barcode/setup/software.rst:12
 msgid "Set products barcodes"
 msgstr ""

-#: ../../inventory/barcode/setup/software.rst:28
+#: ../../inventory/barcode/setup/software.rst:17
 msgid "In order to fill a picking or to perform an inventory, you need to make sure that your products are encoded in Odoo along with their barcodes. If this is not already done, you can fill in the products barcodes through a handy interface. Go to :menuselection:`Inventory --> Configuration --> Settings` and click :menuselection:`Operations --> Barcode Scanner`. Click Save, and go back into the previous screen to click Configure Product Barcodes.  This interface can also be accessed via the planner."
 msgstr ""

-#: ../../inventory/barcode/setup/software.rst:39
+#: ../../inventory/barcode/setup/software.rst:28
 msgid "Product variants: be careful to add barcodes directly on the variant, and not the template product (otherwise you won't be able to differentiate them)."
 msgstr ""

-#: ../../inventory/barcode/setup/software.rst:44
+#: ../../inventory/barcode/setup/software.rst:33
 msgid "Set locations barcodes"
 msgstr ""

-#: ../../inventory/barcode/setup/software.rst:49
+#: ../../inventory/barcode/setup/software.rst:38
 msgid "If you manage multiple locations, you will find useful to attribute a barcode to each location and stick it on the location. You can configure the locations barcodes in :menuselection:`Inventory --> Configuration --> Warehouse Management --> Locations`. There is button in the **Print** menu that you can use to print the locations names and barcodes. There are 4 barcodes per page, arranged in a way that is convenient to print on sticker paper."
 msgstr ""

-#: ../../inventory/barcode/setup/software.rst:58
+#: ../../inventory/barcode/setup/software.rst:47
 msgid "Example of location naming: **warehouse short name** - **location short name** - (**Corridor X** - **Shelf Y** - **Height Z**) Example: A032-025-133"
 msgstr ""

-#: ../../inventory/barcode/setup/software.rst:65
+#: ../../inventory/barcode/setup/software.rst:54
 msgid "Barcode formats"
 msgstr ""

-#: ../../inventory/barcode/setup/software.rst:67
+#: ../../inventory/barcode/setup/software.rst:56
 msgid "Most retail products use EAN-13 barcodes. They cannot be made up without proper authorization: you must pay the International Article Numbering Association a fee in exchange for an EAN code sequence (that's why no two products in a store will ever have the same EAN code)."
 msgstr ""

-#: ../../inventory/barcode/setup/software.rst:72
+#: ../../inventory/barcode/setup/software.rst:61
 msgid "Still, as Odoo supports any string as a barcode, so you can always define your own barcode format for internal use."
 msgstr ""

@ -503,7 +495,7 @@ msgstr ""
 #: ../../inventory/routes/concepts/procurement_rule.rst:25
 #: ../../inventory/routes/concepts/push_rule.rst:29
 #: ../../inventory/routes/concepts/use_routes.rst:22
-#: ../../inventory/routes/costing/landed_costs.rst:18
+#: ../../inventory/routes/costing/landed_costs.rst:17
 #: ../../inventory/routes/strategies/putaway.rst:23
 #: ../../inventory/routes/strategies/removal.rst:18
 #: ../../inventory/settings/products/strategies.rst:30
@ -610,6 +602,42 @@ msgstr ""
 msgid "The choice between the two options is thus dependent of your inventory strategy. If you prefer to have a buffer and always have at least a minimum amount, the minimum stock rule should be used. If you want to reorder your stocks only if your sale is confirmed it is better to use the Make to Order."
 msgstr ""

+#: ../../inventory/management/adjustment/virtual_warehouses.rst:3
+msgid "TaKing stock from different warehouses"
+msgstr ""
+
+#: ../../inventory/management/adjustment/virtual_warehouses.rst:5
+msgid "When you plan to deliver a customer, you don’t know in advance if the products will come from Warehouse A or Warehouse B. You may, in some cases, need to take stock from different warehouses. With *Odoo*, you can configure this by using the concept of virtual warehouses. Let us show you how to set those virtual warehouses."
+msgstr ""
+
+#: ../../inventory/management/adjustment/virtual_warehouses.rst:12
+msgid "Set up virtual warehouses"
+msgstr ""
+
+#: ../../inventory/management/adjustment/virtual_warehouses.rst:14
+msgid "Let’s say you have two warehouses: Warehouse A and Warehouse B. Create a new warehouse, that will be a virtual one. It will allow you to take the stock from A or B. To do so, go to your inventory app settings and enable the multi-warehouses feature. Then, go to the warehouses menu and click on create."
+msgstr ""
+
+#: ../../inventory/management/adjustment/virtual_warehouses.rst:24
+msgid "The *Storage Location* feature will be automatically enabled. Good news, because you will need it later in the process."
+msgstr ""
+
+#: ../../inventory/management/adjustment/virtual_warehouses.rst:27
+msgid "Now, you have to make sure that the main stock locations of warehouse A and warehouse B are children locations of the main stock location of warehouse A + B. Go to the locations menu, and edit the main location of your two warehouses. Then, change their parent location to main location of warehouse A+B."
+msgstr ""
+
+#: ../../inventory/management/adjustment/virtual_warehouses.rst:37
+msgid "Sell a product from the virtual warehouse"
+msgstr ""
+
+#: ../../inventory/management/adjustment/virtual_warehouses.rst:39
+msgid "Let’s say you have two products, one stored in warehouse A and one stored in warehouse B. Now, you can create a new quotation for one of each product. Go to other information and choose Warehouse A+B in the shipping information."
+msgstr ""
+
+#: ../../inventory/management/adjustment/virtual_warehouses.rst:47
+msgid "Once you have done it, you can convert it to a sales order. Then, a delivery order will be automatically generated, with a product reserved in warehouse A and one in warehouse B."
+msgstr ""
+
 #: ../../inventory/management/delivery.rst:3
 msgid "Delivery Orders"
 msgstr ""
@ -767,7 +795,7 @@ msgid "Now, open the menu :menuselection:`Sales --> Sales --> Products`. Add a s
 msgstr ""

 #: ../../inventory/management/delivery/dropshipping.rst:74
-msgid "How to send products from the customers directly to the suppliers"
+msgid "How to send products from the suppliers directly to the customers"
 msgstr ""

 #: ../../inventory/management/delivery/dropshipping.rst:76
@ -790,6 +818,21 @@ msgstr ""
 msgid ":doc:`inventory_flow`"
 msgstr ""

+#: ../../inventory/management/delivery/dropshipping.rst:105
+#: ../../inventory/management/delivery/one_step.rst:63
+#: ../../inventory/management/delivery/three_steps.rst:159
+#: ../../inventory/management/delivery/two_steps.rst:129
+#: ../../inventory/management/incoming/handle_receipts.rst:70
+#: ../../inventory/overview/concepts/double-entry.rst:179
+#: ../../inventory/settings/products/uom.rst:124
+#: ../../inventory/settings/products/variants.rst:222
+msgid "Todo"
+msgstr ""
+
+#: ../../inventory/management/delivery/dropshipping.rst:106
+msgid "Add link to this section when available * How to analyse the performance of my vendors?"
+msgstr ""
+
 #: ../../inventory/management/delivery/inventory_flow.rst:3
 msgid "How to choose the right inventory flow to handle delivery orders?"
 msgstr ""
@ -954,6 +997,16 @@ msgstr ""
 msgid "This has completed the **Shipping Step** and the WH/OUT should now show **Done** in the status column at the top of the page, which means the product has been shipped to the customer."
 msgstr ""

+#: ../../inventory/management/delivery/one_step.rst:64
+msgid "Ajouter un lien vers ces pages quand elles existeront -  Process Overview: From sales orders to delivery orders"
+msgstr ""
+
+#: ../../inventory/management/delivery/one_step.rst:67
+#: ../../inventory/management/delivery/three_steps.rst:163
+#: ../../inventory/management/delivery/two_steps.rst:133
+msgid "Process Overview: From purchase orders to receptions"
+msgstr ""
+
 #: ../../inventory/management/delivery/packaging_type.rst:3
 msgid "How can you change the packaging type for your sale order?"
 msgstr ""
@ -1083,7 +1136,7 @@ msgid "Sales safety days are **back-up** days to ensure you will be able to deli
 msgstr ""

 #: ../../inventory/management/delivery/scheduled_dates.rst:84
-msgid "To set ut your security dates, go to :menuselection:`Settings --> General settings` and click on **Configure your company data**."
+msgid "To set up your security dates, go to :menuselection:`Settings --> General settings` and click on **Configure your company data**."
 msgstr ""

 #: ../../inventory/management/delivery/scheduled_dates.rst:90
@ -1298,6 +1351,10 @@ msgstr ""
 msgid "This has completed the shipping step and the **WH/OUT** should now show **Done** in the status column at the top of the page. The product has been shipped to the customer."
 msgstr ""

+#: ../../inventory/management/delivery/three_steps.rst:160
+msgid "Link to these sections when available -  Process Overview: From sales orders to delivery orders"
+msgstr ""
+
 #: ../../inventory/management/delivery/two_steps.rst:3
 msgid "How to process delivery orders in two steps (pick + ship)?"
 msgstr ""
@ -1378,6 +1435,10 @@ msgstr ""
 msgid "This has completed the shipping step and the **WH/OUT** move should now show **Done** in the status column at the top of the page. The product has been shipped to the customer."
 msgstr ""

+#: ../../inventory/management/delivery/two_steps.rst:130
+msgid "link to these sections when they will be available -  Process Overview: From sales orders to delivery orders"
+msgstr ""
+
 #: ../../inventory/management/incoming.rst:3
 msgid "Incoming Shipments"
 msgstr ""
@ -1440,6 +1501,10 @@ msgstr ""
 msgid ":doc:`../delivery/inventory_flow`"
 msgstr ""

+#: ../../inventory/management/incoming/handle_receipts.rst:71
+msgid "Add section when available -  How to analyse the performance of my vendors?"
+msgstr ""
+
 #: ../../inventory/management/incoming/three_steps.rst:3
 msgid "How to add a quality control step in goods receipt? (3 steps)"
 msgstr ""
@ -1867,7 +1932,7 @@ msgid "A window will pop-up. Click on **Add an item** and fill in the serial num
 msgstr ""

 #: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:68
-msgid "If you move products that already have serial numbers assigned, those will appear in the list. Just click on the **+** icon to to confirm that you are moving those serial numbers."
+msgid "If you move products that already have serial numbers assigned, those will appear in the list. Just click on the **+** icon to confirm that you are moving those serial numbers."
 msgstr ""

 #: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:76
@ -3245,6 +3310,10 @@ msgstr ""
 msgid "whether the procurement is :abbr:`MTO (Made To Order)` or :abbr:`MTS (Made To Stock)`"
 msgstr ""

+#: ../../inventory/overview/concepts/double-entry.rst:179
+msgid "needs schema thing from FP"
+msgstr ""
+
 #: ../../inventory/overview/concepts/double-entry.rst:182
 msgid "Routes"
 msgstr ""
@ -4002,7 +4071,7 @@ msgid "In the Procurement rules section, click on Add an item."
 msgstr ""

 #: ../../inventory/routes/concepts/procurement_rule.rst:45
-msgid "Here you can set the conditions of your rule. There are 3 types of action possibles :"
+msgid "Here you can set the conditions of your rule. There are 3 types of action possible :"
 msgstr ""

 #: ../../inventory/routes/concepts/procurement_rule.rst:48
@ -4010,11 +4079,11 @@ msgid "Move from another location rules"
 msgstr ""

 #: ../../inventory/routes/concepts/procurement_rule.rst:50
-msgid "Manufacturing rules that will trigger the creation of manufacturing orders."
+msgid "Manufacturing rules that will trigger the creation of manufacturing orders"
 msgstr ""

 #: ../../inventory/routes/concepts/procurement_rule.rst:53
-msgid "Buy rules that will trigger the creation of purchase orders."
+msgid "Buy rules that will trigger the creation of purchase orders"
 msgstr ""

 #: ../../inventory/routes/concepts/procurement_rule.rst:56
@ -4056,7 +4125,7 @@ msgid "What is a push rule?"
 msgstr ""

 #: ../../inventory/routes/concepts/push_rule.rst:8
-msgid "The push system of inventory control involves forecasting inventory needs to meet customer demand. Companies must predict which products customers will purchase along with determining what quantity of goods will be purchased. The company will in turn produce enough product to meet the forecast demand and sell, or push, the goods to the consumer. Disadvantages of the push inventory control system are that forecasts are often inaccurate as sales can be unpredictable and vary from one year to the next. Another problem with push inventory control systems is that if too much product is left in inventory. This increases the company's costs for storing these goods. An advantage to the push system is that the company is fairly assured it will have enough product on hand to complete customer orders, preventing the inability to meet customer demand for the product."
+msgid "The push system of inventory control involves forecasting inventory needs to meet customer demand. Companies must predict which products customers will purchase along with determining what quantity of goods will be purchased. The company will in turn produce enough product to meet the forecast demand and sell, or push, the goods to the consumer. Disadvantages of the push inventory control system are that forecasts are often inaccurate as sales can be unpredictable and vary from one year to the next. Another problem with push inventory control systems is that if too much product is left in inventory, this increases the company's costs for storing these goods. An advantage to the push system is that the company is fairly assured it will have enough product on hand to complete customer orders, preventing the inability to meet customer demand for the product."
 msgstr ""

 #: ../../inventory/routes/concepts/push_rule.rst:22
@ -4249,67 +4318,31 @@ msgid "Product Costing"
 msgstr ""

 #: ../../inventory/routes/costing/landed_costs.rst:3
-msgid "How to integrate landed costs in the cost of the product?"
+msgid "How to integrate additional costs in the cost of the product? (landed costs)"
 msgstr ""

 #: ../../inventory/routes/costing/landed_costs.rst:8
-msgid "Landed costs include all charges associated to a good transfer."
-msgstr ""
-
-#: ../../inventory/routes/costing/landed_costs.rst:10
-msgid "Landed cost includes = Cost of product + Shipping + Customs + Risk"
+msgid "The landed cost feature in Odoo allows to include additional costs (shipment, insurance, customs duties, etc.) into the cost of the product."
 msgstr ""

 #: ../../inventory/routes/costing/landed_costs.rst:12
-msgid "All of these components might not be applicable in every shipment, but relevant components must be considered as a part of the landed cost. We have to identify landed cost to decide sale price of product because it will impact on company profits."
+msgid "Landed costs can only be applied to products with a FIFO costing method and an automated inventory valuation (which requires the accounting application to be installed)."
 msgstr ""

-#: ../../inventory/routes/costing/landed_costs.rst:21
-msgid "Applications configuration"
+#: ../../inventory/routes/costing/landed_costs.rst:20
+msgid "First, you need to activate the landed costs feature in :menuselection:`Inventory --> Configuration --> Settings`."
 msgstr ""

-#: ../../inventory/routes/costing/landed_costs.rst:23
-msgid "First, you need to activate the use of the landed costs. Go to :menuselection:`Inventory application --> Configuration --> Setting`. Check accounting option **Include landed costs in product costing computation** & **Perpetual inventory valuation**, then click on **Apply** to save changes."
+#: ../../inventory/routes/costing/landed_costs.rst:27
+msgid "Add costs to products"
 msgstr ""

-#: ../../inventory/routes/costing/landed_costs.rst:32
-msgid "Then go to the :menuselection:`Purchase application --> Configuration --> Setting`. Choose costing method **Use a 'Fixed', 'Real' or 'Average' price costing method**, then click on **Apply** to save changes."
+#: ../../inventory/routes/costing/landed_costs.rst:29
+msgid "Go in :menuselection:`Inventory --> Operations --> Landed Costs` and click on the **Create** button. You then have to select the transfers on which you want to attribute additional costs and the costs lines you want to add up. Once it's done, click on the **Compute** button to see how the costs lines will be split accross your transfers lines."
 msgstr ""

-#: ../../inventory/routes/costing/landed_costs.rst:40
-msgid "Landed Cost Types"
-msgstr ""
-
-#: ../../inventory/routes/costing/landed_costs.rst:42
-msgid "Start by creating specific products to indicate your various **Landed Costs**, such as freight, insurance or custom duties. Go to :menuselection:`Inventory --> Configuration --> Landed Cost types`."
-msgstr ""
-
-#: ../../inventory/routes/costing/landed_costs.rst:50
-msgid "Landed costs are only possible for products configured in real time valuation with real price costing method. The costing method is configured on the product category."
-msgstr ""
-
-#: ../../inventory/routes/costing/landed_costs.rst:55
-msgid "Link landed costs to a transfer"
-msgstr ""
-
-#: ../../inventory/routes/costing/landed_costs.rst:57
-msgid "To calculate landed costs, go to :menuselection:`Inventory --> Inventory Control --> Landed Costs`."
-msgstr ""
-
-#: ../../inventory/routes/costing/landed_costs.rst:60
-msgid "Click on the **Create** button and select the picking(s) you want to attribute landed costs."
-msgstr ""
-
-#: ../../inventory/routes/costing/landed_costs.rst:66
-msgid "Select the account journal in which to post the landed costs. We recommend you to create a specific journal for landed costs. Therefore it will be easier to keep track of your postings."
-msgstr ""
-
-#: ../../inventory/routes/costing/landed_costs.rst:73
-msgid "Click the **Compute** button to see how the landed costs will be split across the picking lines."
-msgstr ""
-
-#: ../../inventory/routes/costing/landed_costs.rst:79
-msgid "To confirm the landed costs attribution, click on the **Validate** button."
+#: ../../inventory/routes/costing/landed_costs.rst:38
+msgid "To confirm, click on the **Validate** button."
 msgstr ""

 #: ../../inventory/routes/strategies.rst:3
@ -4485,7 +4518,7 @@ msgid "**End of Life Date:** This is the date on which the goods with this seria
 msgstr ""

 #: ../../inventory/routes/strategies/removal.rst:125
-msgid "**Removal Date:** This is the date on which the goods with this serial/lot number should be removed from the stock. Using the FEFO removal strategym goods are picked for delivery orders using this date."
+msgid "**Removal Date:** This is the date on which the goods with this serial/lot number should be removed from the stock. Using the FEFO removal strategy goods are picked for delivery orders using this date."
 msgstr ""

 #: ../../inventory/routes/strategies/removal.rst:129
@ -4647,7 +4680,7 @@ msgid "How to use different units of measure?"
 msgstr ""

 #: ../../inventory/settings/products/uom.rst:8
-msgid "In some cases, handling products in different unit of measures is necessary. For example, if you buy products in a country where the metric system is of application and sell the in a country where the imperial system is used, you will need to convert the units."
+msgid "In some cases, handling products in different unit of measures is necessary. For example, if you buy products in a country where the metric system is of application and sell them in a country where the imperial system is used, you will need to convert the units."
 msgstr ""

 #: ../../inventory/settings/products/uom.rst:13
@ -4663,7 +4696,7 @@ msgid "Setting up units on your products"
 msgstr ""

 #: ../../inventory/settings/products/uom.rst:29
-msgid "In :menuselection:`Inventory Control --> Products`, open the product which you would like to change the purchase/sale unit of measure, and click on **Edit**."
+msgid "In :menuselection:`Master Data --> Products`, open the product which you would like to change the purchase/sale unit of measure, and click on **Edit**."
 msgstr ""

 #: ../../inventory/settings/products/uom.rst:32
@ -4755,6 +4788,10 @@ msgstr ""
 msgid "But the transfer is done in the product unit of measure. Everything is converted automatically :"
 msgstr ""

+#: ../../inventory/settings/products/uom.rst:125
+msgid "Create a link when the document is available -  When should you use packages, units of measure or kits?"
+msgstr ""
+
 #: ../../inventory/settings/products/usage.rst:3
 msgid "When should you use packages, units of measure or kits?"
 msgstr ""
@ -5063,6 +5100,14 @@ msgstr ""
 msgid "When you have entered all the extra values, click on **Save**."
 msgstr ""

+#: ../../inventory/settings/products/variants.rst:226
+msgid "Accounting Memento: Details of Journal Entries"
+msgstr ""
+
+#: ../../inventory/settings/products/variants.rst:227
+msgid "Process Overview: From Billing to Payment Orders"
+msgstr ""
+
 #: ../../inventory/settings/warehouses/difference_warehouse_location.rst:3
 msgid "What is the difference between warehouses and locations?"
 msgstr ""
@ -5300,7 +5345,7 @@ msgid "The price is computed when you **save** the sale order. Confirm the sale
 msgstr ""

 #: ../../inventory/shipping/operation/invoicing.rst:64
-msgid "The real shipping cost are computed when the delivery order is validated."
+msgid "The real shipping cost is computed when the delivery order is validated, you can see the real cost in the chatter of the delivery order."
 msgstr ""

 #: ../../inventory/shipping/operation/invoicing.rst:70
--- a/locale/sources/iot.pot
+++ b/locale/sources/iot.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 11.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-10-19 10:03+0200\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -88,6 +88,58 @@ msgstr ""
 msgid "IoT Box Schema"
 msgstr ""

+#: ../../iot/flash_sdcard.rst:3
+msgid "Flashing your SD Card"
+msgstr ""
+
+#: ../../iot/flash_sdcard.rst:5
+msgid "In some case, you may need to reflash your IoT Box’s SD Card to benefit from our latest updates."
+msgstr ""
+
+#: ../../iot/flash_sdcard.rst:9
+msgid "Updating your SD Card with Etcher"
+msgstr ""
+
+#: ../../iot/flash_sdcard.rst:11
+msgid "Go to Balena’s website and download `Etcher <http://wwww.balena.org>`__, It’s a free and open-source utility used for burning image files. Install and launch it."
+msgstr ""
+
+#: ../../iot/flash_sdcard.rst:15
+msgid "Now, download the latest image `here <http://nightly.odoo.com/master/posbox/iotbox/>`__, and extract it from the zip file. Then, open *Etcher* and select the image. Select the drive to flash (where your SD Card is) and click on *Flash*!."
+msgstr ""
+
+#: ../../iot/flash_sdcard.rst:19
+msgid "Now, your image will be automatically updated. You just have to wait 5 minutes for it to finish."
+msgstr ""
+
+#: ../../iot/iot_notfound.rst:3
+msgid "IoT Box not found"
+msgstr ""
+
+#: ../../iot/iot_notfound.rst:5
+msgid "When using your IoT Box, a common issue you might encounter is that your box is not found on your database. Fortunately, there are a few easy steps you can follow to find your IoT box."
+msgstr ""
+
+#: ../../iot/iot_notfound.rst:10
+msgid "HTTPS Issues"
+msgstr ""
+
+#: ../../iot/iot_notfound.rst:12
+msgid "Your IoT Box is not found? You probably have https issues!"
+msgstr ""
+
+#: ../../iot/iot_notfound.rst:14
+msgid "To check it, go to your database and verify if your database address starts with an https (like https://www.odoo.com). If this is the case, then you may have problems with your IoT Box image. It should be version 18.12 or later."
+msgstr ""
+
+#: ../../iot/iot_notfound.rst:19
+msgid "If your IoT Box image is from an earlier version, then you will have to reflash the SD card of your IoT Box to update the image (the latest image can be found `here <http://nightly/odoo.com>`__)."
+msgstr ""
+
+#: ../../iot/iot_notfound.rst:23
+msgid "You can find the documentation about SD card flashing here (`here <https://docs.google.com/document/d/1bqKsZhWqMqI4mhv4ltF61M_QPiBCHygYjjvkhsCTdaY/edit>`__)."
+msgstr ""
+
 #: ../../iot/pos.rst:3
 msgid "Use the IoT Box for the PoS"
 msgstr ""
--- a/locale/sources/livechat.pot
+++ b/locale/sources/livechat.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 11.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-07-23 12:10+0200\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -21,7 +21,7 @@ msgid "Live Chat"
 msgstr ""

 #: ../../livechat/livechat.rst:8
-msgid "Chat in live with website visitors"
+msgid "Chat in real time with website visitors"
 msgstr ""

 #: ../../livechat/livechat.rst:10
@ -85,11 +85,11 @@ msgid "If no operator is available and/or if the channel is unpublished on the w
 msgstr ""

 #: ../../livechat/livechat.rst:92
-msgid "In practice, the conversations initiated by the visitors will appear in the Discuss module and will also pop up as a direct message. Therefore, inquiries can be answered wherever you are in Odoo."
+msgid "Conversations initiated by visitors also appear in the Discuss module in addition to popping up as a direct message. Therefore, inquiries can be answered wherever you are in Odoo."
 msgstr ""

 #: ../../livechat/livechat.rst:96
-msgid "If there several operators in charge of a channel, the system will dispatch sessions randomly between them."
+msgid "If there are several operators who have all joined a channel, the system will dispatch visitor sessions randomly between them."
 msgstr ""

 #: ../../livechat/livechat.rst:100
--- a/locale/sources/manufacturing.pot
+++ b/locale/sources/manufacturing.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 11.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-10-19 10:03+0200\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -24,129 +24,184 @@ msgstr ""
 msgid "Manufacturing Management"
 msgstr ""

+#: ../../manufacturing/management/alternative_wc.rst:3
+msgid "Using an alternative Work Center"
+msgstr ""
+
+#: ../../manufacturing/management/alternative_wc.rst:5
+msgid "For many manufacturing companies, a common issue is to have to manufacture, at the same time, several products usually produced at the same work center. If in practice, employees can manufacture the goods at another work center, it is not that simple."
+msgstr ""
+
+#: ../../manufacturing/management/alternative_wc.rst:10
+msgid "You need to keep track of the job: which work center has been used and when, so you can schedule maintenance efficiently. With Odoo, you can configure it so you can keep tracking manufacturing orders and your employees have an alternative work center to use."
+msgstr ""
+
+#: ../../manufacturing/management/alternative_wc.rst:15
+msgid "This way, your process becomes more efficient, and less non-productive time will be noticed."
+msgstr ""
+
+#: ../../manufacturing/management/alternative_wc.rst:20
+msgid "Configure your Work Centers"
+msgstr ""
+
+#: ../../manufacturing/management/alternative_wc.rst:22
+msgid "The first thing to do is to go to the *Manufacturing* app settings. Then, enable the *Work Orders* feature and hit save."
+msgstr ""
+
+#: ../../manufacturing/management/alternative_wc.rst:30
+msgid "Now, go to the *Work Centers* menu under *Master Data* and create two new work centers. Add the second work centers as an alternative to the first and vice versa."
+msgstr ""
+
+#: ../../manufacturing/management/alternative_wc.rst:39
+msgid "The next step is to create your *routing*. Add your work center and an operation to it before saving."
+msgstr ""
+
+#: ../../manufacturing/management/alternative_wc.rst:47
+msgid "Then, you can create your *Bill of Materials* and add components and routing to it."
+msgstr ""
+
+#: ../../manufacturing/management/alternative_wc.rst:56
+msgid "Create your Work Orders"
+msgstr ""
+
+#: ../../manufacturing/management/alternative_wc.rst:58
+msgid "Now that everything is configured, you can create your *Work Orders*. Go to the *Manufacturing Orders* menu and hit *Create*. There, add your product and plan it. In the *Work Orders* list, you can find it ready to be assembled."
+msgstr ""
+
+#: ../../manufacturing/management/alternative_wc.rst:68
+msgid "Each new *Work Order*, which will be created before the end of the first one, will be scheduled at the alternative work center you configured."
+msgstr ""
+
+#: ../../manufacturing/management/alternative_wc.rst:78
+msgid "Keep in mind that, if you add time after production to your work center, you may have work orders scheduled for your alternative work center even if the usual one is free."
+msgstr ""
+
 #: ../../manufacturing/management/bill_configuration.rst:3
-msgid "How to create a Bill of Materials"
+msgid "Create Bills of Materials"
 msgstr ""

 #: ../../manufacturing/management/bill_configuration.rst:5
-msgid "A bill of materials (BoM) is a document that describes the component products, the quantity of each component, and the process required to manufacture a product, including a routing and individual steps."
+msgid "A *Bill of Materials* is a document defining the quantity of each component required to manufacture a finished product. It also includes the routing and individual steps of the manufacturing process."
 msgstr ""

 #: ../../manufacturing/management/bill_configuration.rst:9
-msgid "In Odoo, each product may have multiple BoMs associated with it, but a BoM can only be associated with a single product. A single BoM can, however, describe multiple variants of the same product."
+msgid "With Odoo, you can link multiple BoMs to each product and use it to describe multiple variants of them. Each BoM will, yet, be associated with one product only."
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:14
-msgid "Setting up a Basic BoM"
+#: ../../manufacturing/management/bill_configuration.rst:13
+msgid "This feature will help optimize your manufacturing process while saving you time."
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:16
-msgid "If you choose to manage your manufacturing operations using manufacturing orders only, you will define basic bills of materials without routings."
+#: ../../manufacturing/management/bill_configuration.rst:17
+msgid "Setting up a BoM"
 msgstr ""

 #: ../../manufacturing/management/bill_configuration.rst:19
-msgid "Before creating your first bill of materials, you will need to create a product and at least one component (components are considered products in Odoo). You can do so from :menuselection:`Master Data --> Products`, or on the fly from the relevant fields on the BoM form. Review the Inventory chapter for more information about configuring products. Once you have created a product and at least one component, select them from the relevant dropdown menus to add them to your bill of materials. A new bill of materials can be created from :menuselection:`Master Data --> Bills of Materials`, or using the button on the top of the product form."
+msgid "You can use BoMs without routings. You will use this if you choose to manage your manufacturing operations using manufacturing orders only. In other words, you choose to realize your manufacturing process in one step and do not track the steps the product goes through."
+msgstr ""
+
+#: ../../manufacturing/management/bill_configuration.rst:24
+msgid "Before creating your *BoM*, you have to create the product using the *BoM* and, at least, one of the components. Go to the *Master Data* menu > *Products* and create both the finished product and the component."
 msgstr ""

 #: ../../manufacturing/management/bill_configuration.rst:29
-msgid "Under the **Miscellaneous** tab, you can fill additional fields. **Sequence** defines the order in which your BoMs will be selected for production orders, with lower numbers having higher priority. **Version** allows you to track changes to your BoM over time."
+msgid "Once done, go to the *Bills of Materials* menu under *Master Data*. Now, create it. Choose the product from the dropdown menu and add your components and the quantity. In this case, keep the default *BoM* type, which is *Manufacture this Product*."
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:35
-msgid "Adding a Routing to a BoM"
+#: ../../manufacturing/management/bill_configuration.rst:38
+msgid "Using the same BoM to describe Variants"
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:37
-msgid "A routing defines a series of operations required to manufacture a product and the work center at which each operation is performed. A routing may be added to multiple BoMs, though a BoM may only have one routing. For more information about configuring routings, review the chapter on routings."
+#: ../../manufacturing/management/bill_configuration.rst:40
+msgid "As said above, you can use *BoM* for *Product Variants*. It is basically the same as for the standard product."
 msgstr ""

 #: ../../manufacturing/management/bill_configuration.rst:43
-msgid "After enabling routings from :menuselection:`Configuration --> Settings`, you will be able to add a routing to a bill of materials by selecting a routing from the dropdown list or creating one on the fly."
+msgid "If your *BoM* is for one variant only, then specify which one in the *Product Variant* field. If not, specify the variant it is consumed for on each component line. You can add several variants for each component."
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:47
-msgid "You may define the work operation or step in which each component is consumed using the field, **Consumed in Operation** under the **Components** tab. Similarly, you can define the operation at which the product will be produced under the **Miscellaneous** tab using the field **Produced at Operation**. If this field is left blank, the products will be consumed/produced at the final operation in the routing."
+#: ../../manufacturing/management/bill_configuration.rst:52
+msgid "Adding a routing"
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:58
-msgid "Adding Byproducts to a BoM"
-msgstr ""
-
-#: ../../manufacturing/management/bill_configuration.rst:60
-msgid "In Odoo, a byproduct is any product produced by a BoM in addition to the primary product."
+#: ../../manufacturing/management/bill_configuration.rst:54
+msgid "You can add routing to your *BoM*. You will do this if you need to define a series of operations required by your manufacturing process. To use it, enable the *Work Orders* feature in the *Manufacturing* app settings."
 msgstr ""

 #: ../../manufacturing/management/bill_configuration.rst:63
-msgid "To add byproducts to a BoM, you will first need to enable them from :menuselection:`Configuration --> Settings`."
+msgid "Each *BoM* can have only one routing while each routing can be used multiple times."
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:69
-msgid "Once byproducts are enabled, you can add them to your bills of materials under the **Byproducts** tab of the bill of materials. You can add any product or products as byproducts. Byproducts are produced in the same step of the routing as the primary product of the BoM."
+#: ../../manufacturing/management/bill_configuration.rst:66
+msgid "Now that you have created your routing, add it to your *BoM*. You can select when, in the work operations, your components are consumed with the dropdown menu."
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:78
-msgid "Setting up a BoM for a Product With Sub-Assemblies"
+#: ../../manufacturing/management/bill_configuration.rst:74
+msgid "Adding By-Products"
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:80
-#: ../../manufacturing/management/sub_assemblies.rst:5
-msgid "A subassembly is a manufactured product which is intended to be used as a component of another manufactured product. You may wish to employ sub-assemblies to simplify a complex BoM, to more accurately represent your manufacturing flow, or to use the same subassembly in multiple BoMs. A BoM that employs subassemblies is often referred to as a multi-level BoM."
+#: ../../manufacturing/management/bill_configuration.rst:76
+msgid "In Odoo, a *by-product* is any product produced by a *BoM* in addition to the primary product."
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:87
-#: ../../manufacturing/management/sub_assemblies.rst:12
-msgid "Multi-level bills of materials in Odoo are accomplished by creating a top-level BoM and subassembly BoMs. Next, the procurement route of the subassembly product is defined. This ensures that every time a manufacturing order for the top-level product is created, a manufacturing order for each subassembly is created as well."
+#: ../../manufacturing/management/bill_configuration.rst:79
+msgid "To add *by-products* to a *BoM*, you will first need to enable them from the *Manufacturing* app settings."
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:94
-msgid "Configure the Top-Level Product BoM"
+#: ../../manufacturing/management/bill_configuration.rst:85
+msgid "Once the feature is enabled, you can add your *By-Products* to your *BoMs*. You can add as many *By-Products* as you want. Just keep in mind that you need to register during which operation your by-product is produced."
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:96
-#: ../../manufacturing/management/sub_assemblies.rst:21
-msgid "To configure a multi-level BoM, create the top-level product and its BoM. Include any subassemblies in the list of components. Create a BoM for each subassembly as you would for any product."
+#: ../../manufacturing/management/flexible_components_consumption.rst:3
+msgid "Use flexible components consumption"
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:104
-#: ../../manufacturing/management/sub_assemblies.rst:29
-msgid "Configure the Subassembly Product Data"
+#: ../../manufacturing/management/flexible_components_consumption.rst:5
+msgid "Sometimes, you might need more components than usual to manufacture a product. Let’s say that you produce a desk combination of 4 desks and two chairs but your customer asks you one more desk. Alright, you can do that. But you will need to register it!"
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:106
-#: ../../manufacturing/management/sub_assemblies.rst:31
-msgid "On the product form of the subassembly, you must select the routes **Manufacture** and **Make To Order**. The **Manufacture** route takes precedence over the **Buy** route, so selecting the latter will have no effect."
+#: ../../manufacturing/management/flexible_components_consumption.rst:10
+msgid "In case this happens, Odoo has the *flexible components consumption* feature available. If you enable it, you will be able to consume as many components as needed and it will make you save time in the registration of your items consumption."
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:114
-#: ../../manufacturing/management/sub_assemblies.rst:39
-msgid "If you would like to be able to purchase the subassembly in addition to manufacturing it, select **Can be Purchased**. All other fields on the subassembly product form may be configured according to your preference."
+#: ../../manufacturing/management/flexible_components_consumption.rst:16
+#: ../../manufacturing/management/kit_shipping.rst:31
+#: ../../manufacturing/management/kit_shipping.rst:66
+#: ../../manufacturing/management/subcontracting.rst:9
+#: ../../manufacturing/management/use_mps.rst:9
+msgid "Configuration"
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:120
-msgid "Using a Single BoM to Describe Several Variants of a Single Product"
+#: ../../manufacturing/management/flexible_components_consumption.rst:18
+msgid "Using flexible component consumption is easy and can be done in a few steps. All you need is a *BoM* and a *Quality Control Point*. Therefore, you will need to activate the feature *Quality* in the *MRP* app settings."
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:122
-#: ../../manufacturing/management/product_variants.rst:5
-msgid "Odoo allows you to use one bill of materials for multiple variants of the same product. Simply enable variants from :menuselection:`Configuration --> Settings`."
+#: ../../manufacturing/management/flexible_components_consumption.rst:23
+msgid "First, open the *BoM* you want to use for flexible component consumption and edit it. In the *Miscellaneous* tab, choose *Flexible* as the consumption type. Then, save."
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:129
-#: ../../manufacturing/management/product_variants.rst:12
-msgid "You will then be able to specify which component lines are to be used in the manufacture of each product variant. You may specify multiple variants for each line. If no variant is specified, the line will be used for all variants."
+#: ../../manufacturing/management/flexible_components_consumption.rst:30
+msgid "Now, in the *Quality* app, open the *Control Point* menu, under *Quality Control* and create a new *Quality Control Point*. Choose your product, your operation and work order operation. Then, choose *Register Consumed Materials* as type."
 msgstr ""

-#: ../../manufacturing/management/bill_configuration.rst:134
-#: ../../manufacturing/management/product_variants.rst:17
-msgid "When defining variant BoMs on a line-item-basis, the **Product Variant** field in the main section of the BoM should be left blank. This field is used when creating a BoM for one variant of a product only."
+#: ../../manufacturing/management/flexible_components_consumption.rst:38
+msgid "Next, go back to your *Manufacturing* app and create a *Manufacturing order*. Choose the product for which you have created the flexible *BoM*."
+msgstr ""
+
+#: ../../manufacturing/management/flexible_components_consumption.rst:42
+msgid "Then, confirm it and launch the process step. While processing, you will have the possibility to consume more components than expected in the *BoM*. To do so, click on *Continue Consumption*."
+msgstr ""
+
+#: ../../manufacturing/management/flexible_components_consumption.rst:49
+msgid "When the job is over, you will find a summary of your component consumption in the *Finished Steps* tab of your work order."
 msgstr ""

 #: ../../manufacturing/management/kit_shipping.rst:3
-msgid "How to Sell a Set of Products as a Kit"
+msgid "Sell sets of products as kits"
 msgstr ""

 #: ../../manufacturing/management/kit_shipping.rst:5
-msgid "A *kit* is a set of components that are delivered without first being assembled or mixed. Kits are described in Odoo using *bills of materials*. There are two basic ways to configure kits, depending on how stock of the kit product is to be managed. In either case, both the Inventory and Manufacturing apps must be installed."
+msgid "A *kit* is a set of components that are delivered without first being assembled or mixed. *Kits* are described in Odoo using *Bills of Materials*. There are two basic ways to configure *kits*, depending on how the stock of the kit product is to be managed. In either case, both the *Inventory* and *Manufacturing* apps must be installed."
 msgstr ""

 #: ../../manufacturing/management/kit_shipping.rst:12
@ -154,121 +209,419 @@ msgid "Manage Stock of Component Products"
 msgstr ""

 #: ../../manufacturing/management/kit_shipping.rst:14
-msgid "If you would like to assemble kits as they are ordered, managing stock of the kit *components* only, you will use a Kit BoM without a manufacturing step."
+msgid "If you want to assemble kits as they are ordered, managing stock of the kit components only, you will use a *Kit BoM* without a manufacturing step."
 msgstr ""

 #: ../../manufacturing/management/kit_shipping.rst:18
-msgid "A product using a Kit BoM will appear as a single line item on a quotation and sales order, but will generate a delivery order with one line item for each of the components of the kit. In the examples below, the image at left shows a sales order for the kit \"Custom Computer Kit\", while the image at right shows the corresponding delivery order."
+msgid "A product using a *Kit BoM* will appear as a single line item on a quotation and sales order, but will generate a delivery order with one line item for each of the components of the kit. In the examples below, the first image shows a sales order for the kit *Custom Computer Kit*, while the second image shows the corresponding delivery order."
 msgstr ""

-#: ../../manufacturing/management/kit_shipping.rst:24
-msgid "|image0|\\ |image1|"
+#: ../../manufacturing/management/kit_shipping.rst:33
+msgid "From the *Products menu* in either the *Inventory* or *Manufacturing* app, create each component product as you would with any other product, then create the top-level, or kit product. The kit product should have only the *route Manufacture* set, in the *Inventory tab*. Because you cannot track the stock of kit products, the *Product Type* should be set to Consumable. Because a kit product cannot be purchased, then, *Can be Purchased* should be unchecked."
 msgstr ""

-#: ../../manufacturing/management/kit_shipping.rst:27
-#: ../../manufacturing/management/kit_shipping.rst:62
-msgid "Configuration"
+#: ../../manufacturing/management/kit_shipping.rst:41
+msgid "All other parameters on the kit product may be modified according to your preference. The component products require no particular configuration."
 msgstr ""

-#: ../../manufacturing/management/kit_shipping.rst:29
-msgid "From the **Products** menu in either the Inventory or Manufacturing app, create each component product as you would any other product, then create the top-level, or kit product. The kit product should have only the route **Manufacture** set. Because you cannot track the stock of kit products, the Product Type should be set to **Consumable**. Because a kit product cannot be purchased, **Can be Purchased** should be unchecked."
+#: ../../manufacturing/management/kit_shipping.rst:48
+msgid "Once the products are configured, create a *bill of materials* for the kit product. Add each component and its quantity. Select the *BoM Type Ship this product as a set of components*. All other options may be left with their default values."
 msgstr ""

-#: ../../manufacturing/management/kit_shipping.rst:37
-msgid "All other parameters on the kit product may be modified according to your preference. The component products require no special configuration."
-msgstr ""
-
-#: ../../manufacturing/management/kit_shipping.rst:44
-msgid "Once the products are configured, create a bill of materials for the kit product. Add each component and its quantity. Select the BoM Type **Ship this product as a set of components**. All other options may be left with their default values."
-msgstr ""
-
-#: ../../manufacturing/management/kit_shipping.rst:53
+#: ../../manufacturing/management/kit_shipping.rst:57
 msgid "Manage Stock of Kit Product and Component Products"
 msgstr ""

-#: ../../manufacturing/management/kit_shipping.rst:55
-msgid "If you would like to manage stock of the top-level kit product, you will use a standard BoM with a manufacturing step instead of a Kit BoM. When using a standard BoM to assemble kits, a manufacturing order will be created. The manufacturing order must be registered as completed before the kit product will appear in your stock."
+#: ../../manufacturing/management/kit_shipping.rst:59
+msgid "If you want to manage stock of the *top-level kit product*, you will use a standard *BoM* with a manufacturing step instead of a *Kit BoM*. When using a standard BoM to assemble kits, a *manufacturing order* will be created. The *manufacturing order* must be registered as completed before the kit product will appear in your stock."
 msgstr ""

-#: ../../manufacturing/management/kit_shipping.rst:64
-msgid "On the kit product, select the route **Manufacture**. You may also select **Make to Order**, which will create a manufacturing order whenever a sales order is confirmed. Select the product type **Stockable Product** to enable stock management."
+#: ../../manufacturing/management/kit_shipping.rst:68
+msgid "On the kit product, select the *route Manufacture*. You may also select *Make to Order*, which will create a *manufacturing order* whenever a sales order is confirmed. Select the product type *Storable Product* to enable stock management."
 msgstr ""

-#: ../../manufacturing/management/kit_shipping.rst:72
-msgid "When you create the bill of materials, select the BoM Type **Manufacture this product**. The assembly of the kit will be described by a manufacturing order rather than a packing operation."
+#: ../../manufacturing/management/kit_shipping.rst:76
+msgid "When you create the *bill of materials*, select the BoM Type *Manufacture this product*. The assembly of the kit will be described by a *manufacturing order* rather than a packing operation."
 msgstr ""

 #: ../../manufacturing/management/manufacturing_order.rst:3
-msgid "How to process a manufacturing order"
+msgid "Process Manufacturing Orders"
 msgstr ""

-#: ../../manufacturing/management/manufacturing_order.rst:6
-msgid "Introduction"
+#: ../../manufacturing/management/manufacturing_order.rst:5
+msgid "In Odoo, you can manage your manufacturing process in two different ways. You can work with one document, or decide to have more information and control over it."
 msgstr ""

-#: ../../manufacturing/management/manufacturing_order.rst:8
-msgid "There are two basic ways to manage manufacturing in Odoo. The first way manages work with one document only. This document is the **manufacturing order**. The second way uses additional documents to give you more precise control over the manufacturing process. In this way, **Manufacturing orders** are divided into one or more steps defined by **work orders**, performed in an order defined by **routings**."
+#: ../../manufacturing/management/manufacturing_order.rst:9
+msgid "In the first case, Odoo makes things easier and helps you manage work with one document only: the manufacturing order. No complex steps during the process, you just have to schedule the job and record the production."
 msgstr ""

-#: ../../manufacturing/management/manufacturing_order.rst:17
-msgid "How to manage manufacturing without routings"
+#: ../../manufacturing/management/manufacturing_order.rst:14
+msgid "But, if you need more control, you can use additional documents (steps) to your manufacturing process. This way, *Manufacturing Orders* are divided into one or more steps defined by *Work Orders* and performed in a sequence defined by *routings*."
 msgstr ""

 #: ../../manufacturing/management/manufacturing_order.rst:19
-msgid "You will most likely use manufacturing orders without routings if all the work to produce your product is performed in one place, by one person, in one step, and/or you do not need the level of granular control afforded by work orders and routings."
+msgid "Using Odoo will allow you to precisely schedule the job, analyze your efficiency but also have ease when realizing each step of your manufacturing process."
 msgstr ""

 #: ../../manufacturing/management/manufacturing_order.rst:24
-msgid "Managing your operations in this way is the default behavior in Odoo. There are two basic phases from planning to production:"
+msgid "Manage Manufacturing Without Routings"
 msgstr ""

-#: ../../manufacturing/management/manufacturing_order.rst:27
-#: ../../manufacturing/management/manufacturing_order.rst:52
-msgid "Create manufacturing orders"
+#: ../../manufacturing/management/manufacturing_order.rst:26
+msgid "If your manufacturing process is limited to one place, one person and one step, you will probably use manufacturing orders without routings."
 msgstr ""

 #: ../../manufacturing/management/manufacturing_order.rst:29
-msgid "Record Production"
+msgid "In Odoo, it is the default behavior. If work this way, there are two basic phases from planning to production:"
 msgstr ""

 #: ../../manufacturing/management/manufacturing_order.rst:32
-msgid "How to manage manufacturing with routings and work orders"
+msgid "Create a manufacturing order"
 msgstr ""

 #: ../../manufacturing/management/manufacturing_order.rst:34
-msgid "To use work orders and routings, you will need to enable the option **Manage production by work orders** From :menuselection:`Configuration --> Settings`. You will then be able to add routings to bills of materials, and configure some additional related fields. You will also be able to create **work centers**, the locations at which work orders are performed."
+msgid "Record the production"
 msgstr ""

-#: ../../manufacturing/management/manufacturing_order.rst:41
-msgid "When manufacturing with routings and work orders, each work order is scheduled individually. You will also have access to time and capacity planning, and reports on costing and efficiency on a work center level."
+#: ../../manufacturing/management/manufacturing_order.rst:37
+msgid "Manage Manufacturing with Routings and Work Centers"
 msgstr ""

-#: ../../manufacturing/management/manufacturing_order.rst:45
-msgid "Manufacturing using routings can be broken down into several steps. When configuring your BoM, you will need to add a routing defining the component work orders. After planning the manufacturing order, you will have the added step of scheduling work orders."
+#: ../../manufacturing/management/manufacturing_order.rst:39
+msgid "To use *Work Centers* and *Routings*, you will need to enable the *Work Orders* feature. To do so, go to the *Manufacturing* app settings."
 msgstr ""

-#: ../../manufacturing/management/manufacturing_order.rst:50
-msgid "The workflow is thus divided into three basic phases, as follows:"
+#: ../../manufacturing/management/manufacturing_order.rst:46
+msgid "Now, you can add routings to *BoMs* and configure your operations taking place at different *work centers*. The *Work Centers* are the locations at which work orders are performed."
 msgstr ""

-#: ../../manufacturing/management/manufacturing_order.rst:54
-msgid "Schedule the associated work orders."
+#: ../../manufacturing/management/manufacturing_order.rst:53
+msgid "When manufacturing this way, each *Work Order* is scheduled individually. You will also have access to time and capacity planning, as well as reports on costing and efficiency for each *Work Center*."
 msgstr ""

-#: ../../manufacturing/management/manufacturing_order.rst:56
-msgid "Perform the scheduled work and record production."
+#: ../../manufacturing/management/manufacturing_order.rst:60
+msgid "Thus, the workflow is divided into three basic phases:"
+msgstr ""
+
+#: ../../manufacturing/management/manufacturing_order.rst:62
+msgid "Create the manufacturing order"
+msgstr ""
+
+#: ../../manufacturing/management/manufacturing_order.rst:67
+msgid "Schedule the associated work orders"
+msgstr ""
+
+#: ../../manufacturing/management/manufacturing_order.rst:72
+msgid "Perform the scheduled work and record production"
+msgstr ""
+
+#: ../../manufacturing/management/plan_work_orders.rst:3
+msgid "Plan Work Orders"
+msgstr ""
+
+#: ../../manufacturing/management/plan_work_orders.rst:5
+msgid "In some cases, companies need to schedule their work orders. Doing so, they can organize the work for the whole day and be sure everything goes well. It helps to avoid scheduling multiple work orders at the same time when you don’t have the capacity to do so."
+msgstr ""
+
+#: ../../manufacturing/management/plan_work_orders.rst:10
+msgid "With Odoo, companies can schedule the planned start date for their manufacturing orders. No possible duplication, no potential issues with the planning. And, if you plan two work orders at the same work center, at the same hour, the second one will be scheduled right after the first one, avoiding work superposition."
+msgstr ""
+
+#: ../../manufacturing/management/plan_work_orders.rst:17
+msgid "Create the Work Orders"
+msgstr ""
+
+#: ../../manufacturing/management/plan_work_orders.rst:19
+msgid "The first thing you need to do is to open the *Manufacturing* app. Then, Go to the settings and enable the *Work Orders* feature."
+msgstr ""
+
+#: ../../manufacturing/management/plan_work_orders.rst:25
+msgid "Now, go to the *Manufacturing Orders* menu and hit *Create*. Choose your product and add a *Planned Start Date*."
+msgstr ""
+
+#: ../../manufacturing/management/plan_work_orders.rst:32
+msgid "The “Deadline Start” field is informative. It shows you until when you can launch the manufacturing order to fulfill the initial demand."
+msgstr ""
+
+#: ../../manufacturing/management/plan_work_orders.rst:35
+msgid "Mark your *Manufacturing Order* as todo and plan it. By going to the *Planning* menu, you can access to the scheduled orders. Here is the one we just created:"
+msgstr ""
+
+#: ../../manufacturing/management/plan_work_orders.rst:43
+msgid "If you plan two work orders at the same hour, the second one will be scheduled after the first one if the jobs need to be done at the same work center. The start date will, then, be automatically updated considering the first free slot on the work center."
+msgstr ""
+
+#: ../../manufacturing/management/plan_work_orders.rst:48
+msgid "If you overrun the planned date and begin the job later, you will have a track of it in the *Time Tracking* tab of your work order."
 msgstr ""

 #: ../../manufacturing/management/product_variants.rst:3
 msgid "How to manage BoMs for product variants"
 msgstr ""

+#: ../../manufacturing/management/product_variants.rst:5
+msgid "Odoo allows you to use one bill of materials for multiple variants of the same product. Simply enable variants from :menuselection:`Configuration --> Settings`."
+msgstr ""
+
+#: ../../manufacturing/management/product_variants.rst:12
+msgid "You will then be able to specify which component lines are to be used in the manufacture of each product variant. You may specify multiple variants for each line. If no variant is specified, the line will be used for all variants."
+msgstr ""
+
+#: ../../manufacturing/management/product_variants.rst:17
+msgid "When defining variant BoMs on a line-item-basis, the **Product Variant** field in the main section of the BoM should be left blank. This field is used when creating a BoM for one variant of a product only."
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:3
+msgid "Set routings on kit Bills of materials"
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:5
+msgid "It often happens that you want to use kit BoM’s within manufactured product BoM’s in order to lighten the list of components for this manufactured product. When doing so, you would like to have the possibility to specify, for each kit component, in which operation they are consumed."
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:11
+msgid "We will see the three use cases that you can face in these kinds of configurations."
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:15
+msgid "Finished Product & Kit Component have the same Routing"
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:18
+#: ../../manufacturing/management/routing_kit_bom.rst:63
+#: ../../manufacturing/management/routing_kit_bom.rst:107
+msgid "Create BoM for the Finished Product"
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:20
+#: ../../manufacturing/management/routing_kit_bom.rst:65
+msgid "Create a manufactured BoM for the finished product which includes a kit component. Set a routing on your BoM, for example, *Assemble Furniture*."
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:28
+#: ../../manufacturing/management/routing_kit_bom.rst:73
+#: ../../manufacturing/management/routing_kit_bom.rst:117
+msgid "Create a Kit BoM for the Kit Component"
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:30
+msgid "Update the kit component to define its BoM. Make sure that the routing which is set on this BoM is the same one than on the Finished Product."
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:36
+msgid "You can define the operations in which the kit components are used directly in the BoM of the kit."
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:40
+#: ../../manufacturing/management/routing_kit_bom.rst:84
+#: ../../manufacturing/management/routing_kit_bom.rst:127
+msgid "Manufacturing Order"
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:42
+msgid "In the list of components, the kit is split. Two work orders are created as we have two operations defined in the *Assemble Furniture* routing. The components of the kits are well consumed in the operations defined in the kit BoM."
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:57
+msgid "Finished Product & Kit Component haven’t the same Routing"
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:60
+msgid "Kit Consumption set on Finished Product BoM"
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:75
+msgid "Update the kit component to define its BoM. In this use case, the routing which is set on this Kit BoM is different than the one of the Finished Product. Specify the operations at which the kit components are consumed in this BoM."
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:86
+#: ../../manufacturing/management/routing_kit_bom.rst:129
+msgid "When the manufacturing order is created for the Manufactured product, the kit is split among its components. When the manufacturing order is planned, three work orders are created in our case, one coming from the routing of the manufactured products, the two other ones coming from the routing of the kit BoM."
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:95
+msgid "The components are all consumed during their respective operations."
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:104
+msgid "Kit Consumption set on Kit BoM"
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:109
+msgid "Create a manufactured BoM for the finished product which includes a kit component. Set a routing on your BoM, for example, *Assemble Furniture*. Precise the consumption of the components on this BoM."
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:119
+msgid "Update the kit component to define its BoM. In this use case, the routing which is set on this Kit BoM is different than the one of the Finished Product."
+msgstr ""
+
+#: ../../manufacturing/management/routing_kit_bom.rst:138
+msgid "All the components of the kits are consumed during the first operation. The last component is consumed during the second operation."
+msgstr ""
+
 #: ../../manufacturing/management/sub_assemblies.rst:3
-msgid "How to manage semi-finished products"
+msgid "Manage semi-finished products"
+msgstr ""
+
+#: ../../manufacturing/management/sub_assemblies.rst:5
+msgid "In Odoo, you can use subassembly products to simplify a complex *Bill of Materials* or to represent your manufacturing flow more accurately. A *subassembly product* is a manufactured product that is used as a component to make another one."
+msgstr ""
+
+#: ../../manufacturing/management/sub_assemblies.rst:10
+msgid "A *BoM* that employs *subassemblies* is referred to as a multi-level BoM. Those are accomplished by creating a *top-level BoM* and *subassembly ones*. This process requires a route that will ensure that every time a manufacturing order for the top-level product is created, another one will be for subassemblies."
+msgstr ""
+
+#: ../../manufacturing/management/sub_assemblies.rst:17
+msgid "Configure the Subassembly Product"
 msgstr ""

 #: ../../manufacturing/management/sub_assemblies.rst:19
-msgid "Configure the Top -Level Product BoM"
+msgid "To configure a *multi-level BoM*, you will need a top-level product but also its subassemblies. The first step is to create a product form for each of the subassemblies. Select the routes *Manufacture* and *Replenish on Order*. Now, hit save."
+msgstr ""
+
+#: ../../manufacturing/management/sub_assemblies.rst:27
+msgid "In the *Bill of Materials* menu, under *Master Data*, create a new *Bill of Materials*. Choose the product you just created and add its components."
+msgstr ""
+
+#: ../../manufacturing/management/sub_assemblies.rst:35
+msgid "Configure the Main BoM"
+msgstr ""
+
+#: ../../manufacturing/management/sub_assemblies.rst:37
+msgid "Now, you can configure the top-level product and its *BoM*. Include any subassemblies in the list of components."
+msgstr ""
+
+#: ../../manufacturing/management/sub_assemblies.rst:43
+msgid "Now, each time you will plan a manufacturing order for the top-level product, a manufacturing order will be created for the subassembly one. Then, you will have to manufacture the subassembly in order to make it available before manufacturing the finished product."
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:3
+msgid "Subcontract the manufacturing"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:5
+msgid "Some businesses subcontract the production of some finished products through subcontractors. This can be easily managed through Odoo."
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:11
+msgid "Go to the *Manufacturing app > Configuration > Settings* and tick the box *Subcontracting*."
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:17
+msgid "You can now define subcontractors contacts. When you purchase or receive products from a contact of type subcontractor, the correct stock moves are created to represent the subcontracting of the production."
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:25
+msgid "You can set the subcontractor as a vendor in case you plan to buy him the subcontracted products via purchase orders."
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:28
+msgid "The next step is to create a *Bill of Material* of type *subcontracted*. In this *BoM*, list the components you need to supply to the subcontractor."
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:35
+msgid "You can also define subcontractors on the BoM."
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:37
+msgid "If no subcontractor is set, the BoM can be used by any subcontractor"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:39
+msgid "If some are set, the BoM can only be used for those subcontractors"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:45
+msgid "Receive or buy a subcontracted product"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:47
+msgid "You have two options to trigger the subcontracting of a product:"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:50
+msgid "**Option A**: You can buy the subcontracted product from your"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:50
+msgid "subcontractor"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:52
+msgid "**Option B**: You can directly receive the subcontracted product"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:54
+msgid "Let’s start with option A (option B is just a simpler version of it)."
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:56
+msgid "Create a new purchase order. The vendor must be a subcontractor. The unit price should be the cost you are paying to the subcontractor for the subcontracting (thus, it’s not necessarily the total cost of the subcontracted product)."
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:64
+msgid "The validation of the purchase order automatically creates the receipt. Whenever you receive the product, you can validate the receipt. The following stock moves are created:"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:68
+msgid "For the components"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:70
+msgid "From Subcontracting To Production"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:72
+msgid "For the subcontracted product"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:74
+msgid "From Production to Subcontracting"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:76
+msgid "From Subcontracting to Stock"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:78
+msgid "The *Subcontracting Location* represents the place where the products are at your subcontractor’s warehouse. It is configured as an internal location, the components that are sent to the subcontractor are still valued in your stock."
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:83
+msgid "For option B, you can simply create the receipt manually with a partner of type subcontractor defined on it."
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:87
+msgid "Resupply the subcontractor with the components"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:89
+msgid "There are 3 ways to manage the resupply of your subcontractor with the components:"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:94
+msgid "**Manually**: You create a delivery order in which you set the"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:93
+msgid "subcontractor as a partner and you choose the components to deliver."
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:103
+msgid "**With reordering rules**: You can define a *reordering rule*"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:100
+msgid "on the *Subcontracting location* to ensure that they are always enough components sent to your subcontractors. When the reordering rule is triggered, a delivery order is created for the product is automatically created."
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:111
+msgid "**On order**: You can also deliver the components to your"
+msgstr ""
+
+#: ../../manufacturing/management/subcontracting.rst:109
+msgid "subcontractors each time you order a subcontracted product. For this, you need to tick the route *Resupply Subcontractor on Order* on the wanted components."
 msgstr ""

 #: ../../manufacturing/management/unbuild.rst:3
@ -311,6 +664,122 @@ msgstr ""
 msgid "If you unbuild a product you bought, you will get the components from the BoM back in stock."
 msgstr ""

+#: ../../manufacturing/management/use_mps.rst:3
+msgid "Use the Master Production Schedule"
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:5
+msgid "The Master Production Schedule (MPS) is a valuable tool to plan your production based on your demand forecast."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:11
+msgid "Go to the *Manufacturing app > Configuration > Settings* and activate the Master Production Schedule feature before hitting save."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:18
+msgid "In the manufacturing settings, you can define the time range of your MPS (month/week/day) and the number of periods you want to display."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:20
+msgid "Now, go in *Planning > Master Production Schedule* and click on add a product. You can now define your safety stock target (= the stock you want to have on hand at the end of the period) and the minimum and maximum quantities to replenish."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:29
+msgid "The products are ordered in the MPS based on their sequence. You can rearrange that sequence by going on the list of your products and reorganize them with drag and drop."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:36
+msgid "In the MPS view, you can decide which information you would like to show by clicking on *rows*. Some fields can be added to the view, such as *Actual demand*, which will show which quantity of products has already been ordered for the period, or *Available to Promise*, which allows you to know what can still be sold during the period (what you plan to replenish - what is already sold during the period). You can also decide to hide some information if it isn’t necessary."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:48
+msgid "Estimate your demand and launch replenishment"
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:50
+msgid "The next step is to estimate the demand for the period. This estimation should be entered in the row *Demand Forecast*. You can easily, at any time, compare the demand forecast with the actual demand (= confirmed sales). The demand forecast for a finished product will impact the indirect demand for its components."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:59
+msgid "Then, the quantity to replenish for the different periods will be automatically computed. The replenishments you are supposed to launch based on your lead times (vendor lead time or manufacturing lead time) are displayed in green. You can now launch the replenishment by clicking on the replenish button."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:65
+msgid "Depending on the configuration of the product (buy vs. manufacture), requests for quotations or manufacturing orders will be created. You can easily access those by clicking on the *Actual Replenishment* cell."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:75
+msgid "In case you manually edit the *To replenish* quantity, a small cross will appear on the left. In case you want to go back to the automatically computed value given by Odoo, you can click the cross."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:83
+msgid "Cells color signification"
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:85
+msgid "The cells, which are part of the *To replenish* line, can take different colors depending on the situation:"
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:90
+msgid "**Green**: quantity of products which should be replenished to"
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:89
+msgid "reach the expected safety stock considering the demand forecast and the indirect demand forecast."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:93
+msgid "**Grey**: replenishment order has already been generated, and its"
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:93
+msgid "quantity still matches current data."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:96
+msgid "**Red**: replenishment order has already been generated, and its"
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:96
+msgid "quantity was too high considering current data."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:99
+msgid "**Orange**: replenishment order has already been generated, and"
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:99
+msgid "its quantity was too low considering current data."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:101
+msgid "The *Forecasted stock* line can also contain red cells, which means the stock will be negative during the period in question."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:105
+msgid "What if I have underestimated the demand?"
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:107
+msgid "You can still increase the demand forecast. It will impact the quantity to replenish. The cell will become orange, and you’ll be able to launch a new replenishment."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:112
+msgid "What if I have overestimated the demand?"
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:114
+msgid "You can decrease the demand forecast. The cell will become red to inform you that you’ve ordered more than planned. If you’re still able to do it, you can cancel some RFQ or MO manually."
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:119
+msgid "What if I wrongly added a product to the MPS?"
+msgstr ""
+
+#: ../../manufacturing/management/use_mps.rst:121
+msgid "You can easily remove a product from the MPS by clicking the small bin on the right of its name."
+msgstr ""
+
 #: ../../manufacturing/overview.rst:5
 msgid "Overview"
 msgstr ""
--- a/locale/sources/mobile.pot
+++ b/locale/sources/mobile.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 11.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-10-19 10:03+0200\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -21,78 +21,14 @@ msgid "Mobile"
 msgstr ""

 #: ../../mobile/firebase.rst:8
-msgid "Setup your Firebase Cloud Messaging"
+msgid "Push Notifications"
 msgstr ""

 #: ../../mobile/firebase.rst:10
-msgid "In order to have mobile notifications in our Android app, you need an API key."
+msgid "As of Odoo 12.0, 13.0 or above, there is no more complex configuration to enable push notifications in the mobile app."
 msgstr ""

 #: ../../mobile/firebase.rst:13
-msgid "If it is not automatically configured (for instance for On-premise or Odoo.sh) please follow these steps below to get an API key for the android app."
-msgstr ""
-
-#: ../../mobile/firebase.rst:18
-msgid "The iOS app doesn't support mobile notifications for Odoo versions < 12."
-msgstr ""
-
-#: ../../mobile/firebase.rst:22
-msgid "Firebase Settings"
-msgstr ""
-
-#: ../../mobile/firebase.rst:25
-msgid "Create a new project"
-msgstr ""
-
-#: ../../mobile/firebase.rst:27
-msgid "First, make sure you to sign in to your Google Account. Then, go to `https://console.firebase.google.com <https://console.firebase.google.com/>`__ and create a new project."
-msgstr ""
-
-#: ../../mobile/firebase.rst:34
-msgid "Choose a project name, click on **Continue**, then click on **Create project**."
-msgstr ""
-
-#: ../../mobile/firebase.rst:37
-msgid "When you project is ready, click on **Continue**."
-msgstr ""
-
-#: ../../mobile/firebase.rst:39
-msgid "You will be redirected to the overview project page (see next screenshot)."
-msgstr ""
-
-#: ../../mobile/firebase.rst:43
-msgid "Add an app"
-msgstr ""
-
-#: ../../mobile/firebase.rst:45
-msgid "In the overview page, click on the Android icon."
-msgstr ""
-
-#: ../../mobile/firebase.rst:50
-msgid "You must use \"com.odoo.com\" as Android package name. Otherwise, it will not work."
-msgstr ""
-
-#: ../../mobile/firebase.rst:56
-msgid "No need to download the config file, you can click on **Next** twice and skip the fourth step."
-msgstr ""
-
-#: ../../mobile/firebase.rst:60
-msgid "Get generated API key"
-msgstr ""
-
-#: ../../mobile/firebase.rst:62
-msgid "On the overview page, go to Project settings:"
-msgstr ""
-
-#: ../../mobile/firebase.rst:67
-msgid "In **Cloud Messaging**, you will see the **API key** and the **Sender ID** that you need to set in Odoo General Settings."
-msgstr ""
-
-#: ../../mobile/firebase.rst:74
-msgid "Settings in Odoo"
-msgstr ""
-
-#: ../../mobile/firebase.rst:76
-msgid "Simply paste the API key and the Sender ID from Cloud Messaging."
+msgid "Simply go to *Settings* > *General Settings* > *Odoo Cloud Notification (OCN)* and make sure that **Push Notifications** is checked."
 msgstr ""

--- a/locale/sources/point_of_sale.pot
+++ b/locale/sources/point_of_sale.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 11.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-10-19 10:03+0200\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -33,13 +33,13 @@ msgid "Using a barcode scanner to process point of sale orders improves your eff
 msgstr ""

 #: ../../point_of_sale/advanced/barcode.rst:9
-#: ../../point_of_sale/advanced/loyalty.rst:9
 #: ../../point_of_sale/advanced/mercury.rst:25
 #: ../../point_of_sale/advanced/reprint.rst:8
+#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:9
+#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:10
 #: ../../point_of_sale/overview/start.rst:22
 #: ../../point_of_sale/restaurant/setup.rst:9
 #: ../../point_of_sale/restaurant/split.rst:10
-#: ../../point_of_sale/shop/seasonal_discount.rst:10
 msgid "Configuration"
 msgstr ""

@ -52,159 +52,25 @@ msgid "Under the IoT Box / Hardware category, you will find *Barcode Scanner* se
 msgstr ""

 #: ../../point_of_sale/advanced/barcode.rst:21
-msgid "You can find more about Barcode Nomenclature here (ADD HYPERLINK)"
-msgstr ""
-
-#: ../../point_of_sale/advanced/barcode.rst:25
 msgid "Add barcodes to product"
 msgstr ""

-#: ../../point_of_sale/advanced/barcode.rst:27
+#: ../../point_of_sale/advanced/barcode.rst:23
 msgid "Go to :menuselection:`Point of Sale --> Catalog --> Products` and select a product."
 msgstr ""

-#: ../../point_of_sale/advanced/barcode.rst:30
+#: ../../point_of_sale/advanced/barcode.rst:26
 msgid "Under the general information tab, you can find a barcode field where you can input any barcode."
 msgstr ""

-#: ../../point_of_sale/advanced/barcode.rst:37
+#: ../../point_of_sale/advanced/barcode.rst:33
 msgid "Scanning products"
 msgstr ""

-#: ../../point_of_sale/advanced/barcode.rst:39
+#: ../../point_of_sale/advanced/barcode.rst:35
 msgid "From your PoS interface, scan any barcode with your barcode scanner. The product will be added, you can scan the same product to add it multiple times or change the quantity manually on the screen."
 msgstr ""

-#: ../../point_of_sale/advanced/discount_tags.rst:3
-msgid "Using discount tags with a barcode scanner"
-msgstr ""
-
-#: ../../point_of_sale/advanced/discount_tags.rst:5
-msgid "If you want to sell your products with a discount, for a product getting close to its expiration date for example, you can use discount tags. They allow you to scan discount barcodes."
-msgstr ""
-
-#: ../../point_of_sale/advanced/discount_tags.rst:10
-msgid "To use discount tags you will need to use a barcode scanner, you can see the documentation about it `here <https://docs.google.com/document/d/1tg7yarr2hPKTddZ4iGbp9IJO-cp7u15eHNVnFoL40Q8/edit>`__"
-msgstr ""
-
-#: ../../point_of_sale/advanced/discount_tags.rst:15
-msgid "Barcode Nomenclature"
-msgstr ""
-
-#: ../../point_of_sale/advanced/discount_tags.rst:17
-msgid "To use discounts tags, we need to learn about barcode nomenclature."
-msgstr ""
-
-#: ../../point_of_sale/advanced/discount_tags.rst:19
-msgid "Let's say you want to have a discount for the product with the following barcode:"
-msgstr ""
-
-#: ../../point_of_sale/advanced/discount_tags.rst:25
-msgid "You can find the *Default Nomenclature* under the settings of your PoS interface."
-msgstr ""
-
-#: ../../point_of_sale/advanced/discount_tags.rst:34
-msgid "Let's say you want 50% discount on a product you have to start your barcode with 22 (for the discount barcode nomenclature) and then 50 (for the %) before adding the product barcode. In our example, the barcode would be:"
-msgstr ""
-
-#: ../../point_of_sale/advanced/discount_tags.rst:43
-msgid "Scan the products & tags"
-msgstr ""
-
-#: ../../point_of_sale/advanced/discount_tags.rst:45
-msgid "You first have to scan the desired product (in our case, a lemon)."
-msgstr ""
-
-#: ../../point_of_sale/advanced/discount_tags.rst:50
-msgid "And then scan the discount tag. The discount will be applied and you can finish the transaction."
-msgstr ""
-
-#: ../../point_of_sale/advanced/loyalty.rst:3
-msgid "Manage a loyalty program"
-msgstr ""
-
-#: ../../point_of_sale/advanced/loyalty.rst:5
-msgid "Encourage your customers to continue to shop at your point of sale with a *Loyalty Program*."
-msgstr ""
-
-#: ../../point_of_sale/advanced/loyalty.rst:11
-msgid "To activate the *Loyalty Program* feature, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS interface. Under the Pricing features, select *Loyalty Program*"
-msgstr ""
-
-#: ../../point_of_sale/advanced/loyalty.rst:19
-msgid "From there you can create and edit your loyalty programs."
-msgstr ""
-
-#: ../../point_of_sale/advanced/loyalty.rst:24
-msgid "You can decide what type of program you wish to use, if the reward is a discount or a gift, make it specific to some products or cover your whole range. Apply rules so that it is only valid in specific situation and everything in between."
-msgstr ""
-
-#: ../../point_of_sale/advanced/loyalty.rst:30
-msgid "Use the loyalty program in your PoS interface"
-msgstr ""
-
-#: ../../point_of_sale/advanced/loyalty.rst:32
-msgid "When a customer is set, you will now see the points they will get for the transaction and they will accumulate until they are spent. They are spent using the button *Rewards* when they have enough points according to the rules defined in the loyalty program."
-msgstr ""
-
-#: ../../point_of_sale/advanced/loyalty.rst:40
-#: ../../point_of_sale/shop/seasonal_discount.rst:45
-msgid "You can see the price is instantly updated to reflect the pricelist. You can finalize the order in your usual way."
-msgstr ""
-
-#: ../../point_of_sale/advanced/loyalty.rst:44
-#: ../../point_of_sale/shop/seasonal_discount.rst:49
-msgid "If you select a customer with a default pricelist, it will be applied. You can of course change it."
-msgstr ""
-
-#: ../../point_of_sale/advanced/manual_discount.rst:3
-msgid "Apply manual discounts"
-msgstr ""
-
-#: ../../point_of_sale/advanced/manual_discount.rst:5
-msgid "If you seldom use discounts, applying manual discounts might be the easiest solution for your Point of Sale."
-msgstr ""
-
-#: ../../point_of_sale/advanced/manual_discount.rst:8
-msgid "You can either apply a discount on the whole order or on specific products."
-msgstr ""
-
-#: ../../point_of_sale/advanced/manual_discount.rst:12
-msgid "Apply a discount on a product"
-msgstr ""
-
-#: ../../point_of_sale/advanced/manual_discount.rst:14
-msgid "From your session interface, use *Disc* button."
-msgstr ""
-
-#: ../../point_of_sale/advanced/manual_discount.rst:19
-msgid "You can then input a discount (in percentage) over the product that is currently selected and the discount will be applied."
-msgstr ""
-
-#: ../../point_of_sale/advanced/manual_discount.rst:23
-msgid "Apply a global discount"
-msgstr ""
-
-#: ../../point_of_sale/advanced/manual_discount.rst:25
-msgid "To apply a discount on the whole order, go to :menuselection:`Point of Sales --> Configuration --> Point of sale` and select your PoS interface."
-msgstr ""
-
-#: ../../point_of_sale/advanced/manual_discount.rst:28
-msgid "Under the *Pricing* category, you will find *Global Discounts* select it."
-msgstr ""
-
-#: ../../point_of_sale/advanced/manual_discount.rst:34
-msgid "You now have a new *Discount* button in your PoS interface."
-msgstr ""
-
-#: ../../point_of_sale/advanced/manual_discount.rst:39
-msgid "Once clicked you can then enter your desired discount (in percentages)."
-msgstr ""
-
-#: ../../point_of_sale/advanced/manual_discount.rst:44
-msgid "On this example, you can see a global discount of 50% as well as a specific product discount also at 50%."
-msgstr ""
-
 #: ../../point_of_sale/advanced/mercury.rst:3
 msgid "Accept credit card payment using Mercury"
 msgstr ""
@ -249,72 +115,76 @@ msgstr ""
 msgid "You now have a new option to pay by credit card when validating a payment."
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:3
-msgid "Manage multiple cashiers"
+#: ../../point_of_sale/advanced/multicashiers.rst:3
+msgid "Log in with employee"
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:5
-msgid "With Odoo Point of Sale, you can easily manage multiple cashiers. This allows you to keep track on who is working in the Point of Sale and when."
+#: ../../point_of_sale/advanced/multicashiers.rst:5
+msgid "With Odoo *Point of Sale*, you can manage multiple cashiers. This feature allows you to keep track of who is working, when and how much each cashier made for that session."
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:9
-msgid "There are three different ways of switching between cashiers in Odoo. They are all explained below."
+#: ../../point_of_sale/advanced/multicashiers.rst:9
+msgid "There are three ways to switch cashiers in Odoo: by *selecting the cashier*, by *entering a PIN code* or by *scanning a barcode*."
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:13
-msgid "To manage multiple cashiers, you need to have several users (at least two)."
+#: ../../point_of_sale/advanced/multicashiers.rst:13
+msgid "To manage multiple cashiers, you need several employees (at least two)."
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:17
+#: ../../point_of_sale/advanced/multicashiers.rst:16
+msgid "Set up log in with employees"
+msgstr ""
+
+#: ../../point_of_sale/advanced/multicashiers.rst:18
+msgid "To enable the feature, go to your *PoS settings* and check log in with employees on your *PoS form*. Then, add the employees that have access to the cash register."
+msgstr ""
+
+#: ../../point_of_sale/advanced/multicashiers.rst:25
+msgid "Now, you can switch cashier easily."
+msgstr ""
+
+#: ../../point_of_sale/advanced/multicashiers.rst:28
 msgid "Switch without pin codes"
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:19
-msgid "The easiest way to switch cashiers is without a code. Simply press on the name of the current cashier in your PoS interface."
+#: ../../point_of_sale/advanced/multicashiers.rst:30
+msgid "The easiest way to switch cashiers is without a code. To do so, click on the cashier name in your PoS interface."
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:25
-msgid "You will then be able to change between different users."
+#: ../../point_of_sale/advanced/multicashiers.rst:36
+msgid "Now, you just have to click on your name."
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:30
-msgid "And the cashier will be changed."
+#: ../../point_of_sale/advanced/multicashiers.rst:42
+msgid "Switch cashier with pin codes"
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:33
-msgid "Switch cashiers with pin codes"
+#: ../../point_of_sale/advanced/multicashiers.rst:44
+msgid "You can set a pin code on each cashier. To set up a pin code, go to the employee form and add a security PIN, in the *HR settings tab*."
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:35
-msgid "You can also set a pin code on each user. To do so, go to :menuselection:`Settings --> Manage Access rights` and select the user."
+#: ../../point_of_sale/advanced/multicashiers.rst:50
+msgid "Now, when switching cashier, a PIN password will be asked."
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:41
-msgid "On the user page, under the *Point of Sale* tab you can add a Security PIN."
+#: ../../point_of_sale/advanced/multicashiers.rst:56
+msgid "Switch cashier with barcodes"
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:47
-msgid "Now when you switch users you will be asked to input a PIN password."
+#: ../../point_of_sale/advanced/multicashiers.rst:58
+msgid "You can ask your employees to log themselves with their badges. To do so, set up a barcode at the same place you add the PIN code. Print the badge and when they will scan it, the cashier will be switched to that employee."
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:53
-msgid "Switch cashiers with barcodes"
+#: ../../point_of_sale/advanced/multicashiers.rst:67
+msgid "Find who was the cashier"
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:55
-msgid "You can also ask your cashiers to log themselves in with their badges."
+#: ../../point_of_sale/advanced/multicashiers.rst:69
+msgid "Once you have closed your *PoS session*, you can have an overview of the amount each cashier sold for. To do so, go to the orders menu."
 msgstr ""

-#: ../../point_of_sale/advanced/multi_cashiers.rst:57
-msgid "Back where you put a security PIN code, you could also put a barcode."
-msgstr ""
-
-#: ../../point_of_sale/advanced/multi_cashiers.rst:62
-msgid "When they scan their barcode, the cashier will be switched to that user."
-msgstr ""
-
-#: ../../point_of_sale/advanced/multi_cashiers.rst:64
-msgid "Barcode nomenclature link later on"
+#: ../../point_of_sale/advanced/multicashiers.rst:75
+msgid "Now, you can open the order and have a summary of the sold products."
 msgstr ""

 #: ../../point_of_sale/advanced/reprint.rst:3
@ -326,25 +196,199 @@ msgid "Use the *Reprint receipt* feature if you have the need to reprint a ticke
 msgstr ""

 #: ../../point_of_sale/advanced/reprint.rst:10
-msgid "To activate *Reprint Receipt*, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS interface."
+msgid "To activate *Reprint Receipt*, go to :menuselection:`Point of Sale --> Configuration --> Point of sale`. and select your PoS interface."
 msgstr ""

 #: ../../point_of_sale/advanced/reprint.rst:13
 msgid "Under the Bills & Receipts category, you will find *Reprint Receipt* option."
 msgstr ""

-#: ../../point_of_sale/advanced/reprint.rst:20
+#: ../../point_of_sale/advanced/reprint.rst:17
+msgid "In order to allow the option reprint receipt, you need to activate the receipt printer."
+msgstr ""
+
+#: ../../point_of_sale/advanced/reprint.rst:23
 msgid "Reprint a receipt"
 msgstr ""

-#: ../../point_of_sale/advanced/reprint.rst:22
+#: ../../point_of_sale/advanced/reprint.rst:25
 msgid "On your PoS interface, you now have a *Reprint receipt* button."
 msgstr ""

-#: ../../point_of_sale/advanced/reprint.rst:27
+#: ../../point_of_sale/advanced/reprint.rst:30
 msgid "When you use it, you can then reprint your last receipt."
 msgstr ""

+#: ../../point_of_sale/advanced_pricing_features.rst:3
+msgid "Advanced Pricing Features"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:3
+msgid "Using discount tags with a barcode scanner"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:5
+msgid "If you want to sell your products with a discount, for a product getting close to its expiration date for example, you can use discount tags. They allow you to scan discount barcodes."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:10
+msgid "To use discount tags you will need to use a barcode scanner."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:13
+msgid "Barcode Nomenclature"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:15
+msgid "To use discounts tags, we need to learn about barcode nomenclature."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:17
+msgid "Let's say you want to have a discount for the product with the following barcode:"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:23
+msgid "You can find the *Default Nomenclature* under the settings of your PoS interface."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:32
+msgid "Let's say you want 50% discount on a product you have to start your barcode with 22 (for the discount barcode nomenclature) and then 50 (for the %) before adding the product barcode. In our example, the barcode would be:"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:41
+msgid "Scan the products & tags"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:43
+msgid "You first have to scan the desired product (in our case, a lemon)."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:48
+msgid "And then scan the discount tag. The discount will be applied and you can finish the transaction."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:3
+msgid "Manage a loyalty program"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:5
+msgid "Encourage your customers to continue to shop at your point of sale with a *Loyalty Program*."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:11
+msgid "To activate the *Loyalty Program* feature, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS interface. Under the Pricing features, select *Loyalty Program*"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:19
+msgid "From there you can create and edit your loyalty programs."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:24
+msgid "You can decide what type of program you wish to use, if the reward is a discount or a gift, make it specific to some products or cover your whole range. Apply rules so that it is only valid in specific situation and everything in between."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:30
+msgid "Use the loyalty program in your PoS interface"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:32
+msgid "When a customer is set, you will now see the points they will get for the transaction and they will accumulate until they are spent. They are spent using the button *Rewards* when they have enough points according to the rules defined in the loyalty program."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:40
+#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:45
+msgid "You can see the price is instantly updated to reflect the pricelist. You can finalize the order in your usual way."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:44
+#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:49
+msgid "If you select a customer with a default pricelist, it will be applied. You can of course change it."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:3
+msgid "Apply manual discounts"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:5
+msgid "If you seldom use discounts, applying manual discounts might be the easiest solution for your Point of Sale."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:8
+msgid "You can either apply a discount on the whole order or on specific products."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:12
+msgid "Apply a discount on a product"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:14
+msgid "From your session interface, use *Disc* button."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:19
+msgid "You can then input a discount (in percentage) over the product that is currently selected and the discount will be applied."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:23
+msgid "Apply a global discount"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:25
+msgid "To apply a discount on the whole order, go to :menuselection:`Point of Sales --> Configuration --> Point of sale` and select your PoS interface."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:28
+msgid "Under the *Pricing* category, you will find *Global Discounts* select it."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:34
+msgid "You now have a new *Discount* button in your PoS interface."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:39
+msgid "Once clicked you can then enter your desired discount (in percentages)."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:44
+msgid "On this example, you can see a global discount of 50% as well as a specific product discount also at 50%."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:3
+msgid "Apply time-limited discounts"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:5
+msgid "Entice your customers and increase your revenue by offering time-limited or seasonal discounts. Odoo has a powerful pricelist feature to support a pricing strategy tailored to your business."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:12
+msgid "To activate the *Pricelists* feature, go to :menuselection:`Point of Sales --> Configuration --> Point of sale` and select your PoS interface."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:18
+msgid "Choose the pricelists you want to make available in this Point of Sale and define the default pricelist. You can access all your pricelists by clicking on *Pricelists*."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:23
+msgid "Create a pricelist"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:25
+msgid "By default, you have a *Public Pricelist* to create more, go to :menuselection:`Point of Sale --> Catalog --> Pricelists`"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:31
+msgid "You can set several criterias to use a specific price: periods, min. quantity (meet a minimum ordered quantity and get a price break), etc. You can also chose to only apply that pricelist on specific products or on the whole range."
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:37
+msgid "Using a pricelist in the PoS interface"
+msgstr ""
+
+#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:39
+msgid "You now have a new button above the *Customer* one, use it to instantly select the right pricelist."
+msgstr ""
+
 #: ../../point_of_sale/analyze.rst:3
 msgid "Analyze sales"
 msgstr ""
@ -679,34 +723,34 @@ msgid "To activate the *Order printing* feature, go to :menuselection:`Point of
 msgstr ""

 #: ../../point_of_sale/restaurant/kitchen_printing.rst:16
-msgid "Under the IoT Box / Hardware Proxy category, you will find *Order Printers*."
+msgid "Under the IoT Box / Hardware Proxy category, you will find *Order Printers*. Note that you need an IoT Box to connect your Printer to the PoS."
 msgstr ""

-#: ../../point_of_sale/restaurant/kitchen_printing.rst:19
+#: ../../point_of_sale/restaurant/kitchen_printing.rst:20
 msgid "Add a printer"
 msgstr ""

-#: ../../point_of_sale/restaurant/kitchen_printing.rst:21
+#: ../../point_of_sale/restaurant/kitchen_printing.rst:22
 msgid "In your configuration menu you will now have a *Order Printers* option where you can add the printer."
 msgstr ""

-#: ../../point_of_sale/restaurant/kitchen_printing.rst:28
+#: ../../point_of_sale/restaurant/kitchen_printing.rst:29
 msgid "Print a kitchen/bar order"
 msgstr ""

-#: ../../point_of_sale/restaurant/kitchen_printing.rst:33
+#: ../../point_of_sale/restaurant/kitchen_printing.rst:34
 msgid "Select or create a printer."
 msgstr ""

-#: ../../point_of_sale/restaurant/kitchen_printing.rst:36
+#: ../../point_of_sale/restaurant/kitchen_printing.rst:37
 msgid "Print the order in the kitchen/bar"
 msgstr ""

-#: ../../point_of_sale/restaurant/kitchen_printing.rst:38
+#: ../../point_of_sale/restaurant/kitchen_printing.rst:39
 msgid "On your PoS interface, you now have a *Order* button."
 msgstr ""

-#: ../../point_of_sale/restaurant/kitchen_printing.rst:43
+#: ../../point_of_sale/restaurant/kitchen_printing.rst:44
 msgid "When you press it, it will print the order on your kitchen/bar printer."
 msgstr ""

@ -858,7 +902,7 @@ msgstr ""
 msgid "Once on the payment interface, you now have a new *Tip* button"
 msgstr ""

-#: ../../point_of_sale/restaurant/tips.rst:31
+#: ../../point_of_sale/restaurant/tips.rst:28
 msgid "Add the tip your customer wants to leave and process to the payment."
 msgstr ""

@ -1014,39 +1058,3 @@ msgstr ""
 msgid "As you can see, the total is in negative, to end the refund you simply have to process the payment."
 msgstr ""

-#: ../../point_of_sale/shop/seasonal_discount.rst:3
-msgid "Apply time-limited discounts"
-msgstr ""
-
-#: ../../point_of_sale/shop/seasonal_discount.rst:5
-msgid "Entice your customers and increase your revenue by offering time-limited or seasonal discounts. Odoo has a powerful pricelist feature to support a pricing strategy tailored to your business."
-msgstr ""
-
-#: ../../point_of_sale/shop/seasonal_discount.rst:12
-msgid "To activate the *Pricelists* feature, go to :menuselection:`Point of Sales --> Configuration --> Point of sale` and select your PoS interface."
-msgstr ""
-
-#: ../../point_of_sale/shop/seasonal_discount.rst:18
-msgid "Choose the pricelists you want to make available in this Point of Sale and define the default pricelist. You can access all your pricelists by clicking on *Pricelists*."
-msgstr ""
-
-#: ../../point_of_sale/shop/seasonal_discount.rst:23
-msgid "Create a pricelist"
-msgstr ""
-
-#: ../../point_of_sale/shop/seasonal_discount.rst:25
-msgid "By default, you have a *Public Pricelist* to create more, go to :menuselection:`Point of Sale --> Catalog --> Pricelists`"
-msgstr ""
-
-#: ../../point_of_sale/shop/seasonal_discount.rst:31
-msgid "You can set several criterias to use a specific price: periods, min. quantity (meet a minimum ordered quantity and get a price break), etc. You can also chose to only apply that pricelist on specific products or on the whole range."
-msgstr ""
-
-#: ../../point_of_sale/shop/seasonal_discount.rst:37
-msgid "Using a pricelist in the PoS interface"
-msgstr ""
-
-#: ../../point_of_sale/shop/seasonal_discount.rst:39
-msgid "You now have a new button above the *Customer* one, use it to instantly select the right pricelist."
-msgstr ""
-
--- a/locale/sources/portal.pot
+++ b/locale/sources/portal.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 11.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-07-23 12:10+0200\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -21,11 +21,11 @@ msgid "My Odoo Portal"
 msgstr ""

 #: ../../portal/my_odoo_portal.rst:8
-msgid "In this section of the portal you will find all the communications between you and Odoo, documents such Quotations, Sales Orders, Invoices and your Subscriptions."
+msgid "In this section of the portal, you will find all the communications between you and Odoo: documents such as quotations, sales orders, invoices and subscriptions."
 msgstr ""

 #: ../../portal/my_odoo_portal.rst:11
-msgid "To access this section you have to log with your username and password to `Odoo <https://www.odoo.com/my/home>`__ . If you are already logged-in just click on your name on the top-right corner and select \"My Account\"."
+msgid "To access this section, you have to log with your username and password to `Odoo <https://www.odoo.com/my/home>`__ . If you are already logged in, just click on your name on the top-right corner and select \"My Account\"."
 msgstr ""

 #: ../../portal/my_odoo_portal.rst:20
@ -33,15 +33,15 @@ msgid "Quotations"
 msgstr ""

 #: ../../portal/my_odoo_portal.rst:22
-msgid "Here you will find all the quotations sent to you by Odoo. For example, a quotation can be generated for you after adding an Application or a User to your database or if your contract has to be renewed."
+msgid "Here you will find all the quotations sent to you by Odoo. For example, a quotation can be generated for you after adding an application or a user to your database or if your contract has to be renewed."
 msgstr ""

 #: ../../portal/my_odoo_portal.rst:29
-msgid "The *Valid Until* column shows until when the quotation is valid; after that date the quotation will be \"Expired\". By clicking on the quotation you will see all the details of the offer, the pricing and other useful information."
+msgid "The *Valid Until* column shows the date through which the quotation is valid; after that date, the quotation will be \"Expired\". By clicking on the quotation, you will see all the details of the offer, such as the pricing and other useful information."
 msgstr ""

 #: ../../portal/my_odoo_portal.rst:36
-msgid "If you want to accept the quotation just click \"Accept & Pay\" and the quote will get confirmed. If you don't want to accept it, or you need to ask for some modifications, click on \"Ask Changes Reject\"."
+msgid "If you want to accept the quotation, just click \"Accept & Pay,\" and the quote will get confirmed. If you don't want to accept it, or you need to ask for some modifications, click on \"Ask Changes Reject.\""
 msgstr ""

 #: ../../portal/my_odoo_portal.rst:41
@ -49,11 +49,11 @@ msgid "Sales Orders"
 msgstr ""

 #: ../../portal/my_odoo_portal.rst:43
-msgid "All your purchases within Odoo such as Upsells, Themes, Applications, etc. will be registered under this section."
+msgid "All your purchases within Odoo (Upsells, Themes, Applications, etc.) will be registered under this section."
 msgstr ""

 #: ../../portal/my_odoo_portal.rst:49
-msgid "By clicking on the sale order you can review the details of the products purchased and process the payment."
+msgid "By clicking on the sale order, you can review the details of the products purchased and process the payment."
 msgstr ""

 #: ../../portal/my_odoo_portal.rst:53
@ -61,11 +61,11 @@ msgid "Invoices"
 msgstr ""

 #: ../../portal/my_odoo_portal.rst:55
-msgid "All the invoices of your subscription(s), or generated by a sales order, will be shown in this section. The tag before the Amount Due will indicate you if the invoice has been paid."
+msgid "All the invoices of your subscriptions and/or sales orders will be shown in this section. The tag before the Amount Due will indicate if the invoice has been paid."
 msgstr ""

 #: ../../portal/my_odoo_portal.rst:62
-msgid "Just click on the Invoice if you wish to see more information, pay the invoice or download a PDF version of the document."
+msgid "Just click on the invoice if you wish to see more information, pay the invoice, or download a PDF version of the document."
 msgstr ""

 #: ../../portal/my_odoo_portal.rst:66
@ -73,42 +73,42 @@ msgid "Tickets"
 msgstr ""

 #: ../../portal/my_odoo_portal.rst:68
-msgid "When you submit a ticket through `Odoo Support <https://www.odoo.com/help>`__ a ticket will be created. Here you can find all the tickets that you have opened, the conversation between you and our Agents, the Status of the ticket and the ID (# Ref)."
+msgid "When you submit a ticket through `Odoo Support <https://www.odoo.com/help>`, a ticket will be created. Here you can find all the tickets that you have opened, the conversations between you and our Agents, and the statuses and IDs (# Ref) of the tickets."
 msgstr ""

-#: ../../portal/my_odoo_portal.rst:77
+#: ../../portal/my_odoo_portal.rst:76
 msgid "Subscriptions"
 msgstr ""

-#: ../../portal/my_odoo_portal.rst:79
-msgid "You can access to your Subscription with Odoo from this section. The first page shows you the subscriptions that you have and their status."
+#: ../../portal/my_odoo_portal.rst:78
+msgid "You can access your subscriptions with Odoo from this section. The first page shows you the subscriptions that you have and their status."
 msgstr ""

-#: ../../portal/my_odoo_portal.rst:85
-msgid "By clicking on the Subscription you will access to all the details regarding your plan: this includes the number of applications purchased, the billing information and the payment method."
+#: ../../portal/my_odoo_portal.rst:84
+msgid "By clicking on the subscription you will access all the details regarding your plan: the number of applications purchased, the billing information, and the payment method."
 msgstr ""

-#: ../../portal/my_odoo_portal.rst:89
-msgid "To change the payment method click on \"Change Payment Method\" and enter the new credit card details."
+#: ../../portal/my_odoo_portal.rst:88
+msgid "To change the payment method, click on \"Change Payment Method\" and enter the new credit card details."
 msgstr ""

-#: ../../portal/my_odoo_portal.rst:95
-msgid "If you want to remove the credit cards saved, you can do it by clicking on \"Manage you payment methods\" at the bottom of the page. Click then on \"Delete\" to delete the payment method."
+#: ../../portal/my_odoo_portal.rst:94
+msgid "If you want to remove the credit cards that are saved, you can do so by clicking on \"Manage your payment methods\" at the bottom of the page. Click \"Delete\" to delete the payment method."
 msgstr ""

-#: ../../portal/my_odoo_portal.rst:102
-msgid "At the date of the next invoice, if there is no payment information provided or if your credit card has expired, the status of your subscription will change to \"To Renew\".  You will then have 7 days to provide a valid method of payment. After this delay, the subscription will be closed and you will no longer be able to access the database."
+#: ../../portal/my_odoo_portal.rst:101
+msgid "At the date of the next invoice, if there is no payment information provided or if your credit card has expired, the status of your subscription will change to \"To Renew\".  You will then have 7 days to provide a valid method of payment. After this delay, the subscription will be closed, and you will no longer be able to access the database."
 msgstr ""

-#: ../../portal/my_odoo_portal.rst:109
+#: ../../portal/my_odoo_portal.rst:108
 msgid "Success Packs"
 msgstr ""

-#: ../../portal/my_odoo_portal.rst:110
-msgid "With a Success Pack/Partner Success Pack, you are assigned an expert to provide unique personalized assistance to help you customize your solution and optimize your workflows as part of your initial implementation. These hours never expire allowing you to utilize them whenever you need support."
+#: ../../portal/my_odoo_portal.rst:109
+msgid "With a Success Pack/Partner Success Pack, you are assigned an expert to provide unique personalized assistance to help you customize your solution and optimize your workflows as part of your initial implementation. These hours never expire, allowing you to utilize them whenever you need support."
 msgstr ""

-#: ../../portal/my_odoo_portal.rst:116
+#: ../../portal/my_odoo_portal.rst:115
 msgid "If you need information about how to manage your database see :ref:`db_online`"
 msgstr ""

--- a/locale/sources/project.pot
+++ b/locale/sources/project.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 12.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-11-07 15:38+0100\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -151,7 +151,11 @@ msgid "In order to be able to generate a task from a sale order you will need to
 msgstr ""

 #: ../../project/advanced/so_to_task.rst:39
-msgid "Moreover if you wish to be able to invoice your customers based on time spent on the task, it is also necessary to install the **Timesheet** module. Simply go into the application module and install the following:"
+msgid "And finally, the **Timesheet** app, Timesheet will not only let you create a task from a Sales order, but also invoice your customer based on the time spent on that task."
+msgstr ""
+
+#: ../../project/advanced/so_to_task.rst:41
+msgid "Simply go into the application module and install the following:"
 msgstr ""

 #: ../../project/advanced/so_to_task.rst:47
--- a/locale/sources/purchase.pot
+++ b/locale/sources/purchase.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 12.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-11-07 15:38+0100\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -41,7 +41,7 @@ msgstr ""
 #: ../../purchase/purchases/rfq/3_way_matching.rst:18
 #: ../../purchase/purchases/rfq/analyze.rst:24
 #: ../../purchase/purchases/rfq/approvals.rst:9
-#: ../../purchase/purchases/rfq/bills.rst:31
+#: ../../purchase/purchases/rfq/bills.rst:10
 #: ../../purchase/purchases/rfq/create.rst:13
 #: ../../purchase/purchases/rfq/lock_orders.rst:9
 #: ../../purchase/purchases/rfq/reception.rst:14
@ -385,215 +385,39 @@ msgid "Once approved, the purchase order follows the normal process."
 msgstr ""

 #: ../../purchase/purchases/rfq/bills.rst:3
-msgid "Control supplier bills"
+msgid "Bill Control"
 msgstr ""

 #: ../../purchase/purchases/rfq/bills.rst:5
-msgid "The **Purchase** application allows you to manage your purchase orders, incoming products, and vendor bills all seamlessly in one place."
+msgid "With Odoo, you can define a setting to help the control of your bills. *Bill Control* lets you choose if the supplier sends you the bill before or after you receive the goods."
 msgstr ""

-#: ../../purchase/purchases/rfq/bills.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."
+#: ../../purchase/purchases/rfq/bills.rst:12
+msgid "For this feature to work, go to :menuselection:`Purchases --> Configuration --> Settings` and select which way you want to control your bills."
 msgstr ""

-#: ../../purchase/purchases/rfq/bills.rst:13
-msgid "Here is the standard work flow in Odoo:"
+#: ../../purchase/purchases/rfq/bills.rst:20
+msgid "Change the control policy"
 msgstr ""

-#: ../../purchase/purchases/rfq/bills.rst:15
-msgid "You begin with a **Request for Quotation (RFQ)** to send out to your vendor(s)."
+#: ../../purchase/purchases/rfq/bills.rst:22
+msgid "While the setting above will be your default method of bill control, you can always select which way you want to invoice your product on each product page under the *Purchase* tab."
 msgstr ""

-#: ../../purchase/purchases/rfq/bills.rst:18
-msgid "Once the vendor has accepted the RFQ, confirm the RFQ into a **Purchase Order (PO)**."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:21
-msgid "Confirming the PO generates an **Incoming Shipment** if you purchased any stockable products."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:24
-msgid "Upon receiving a **Vendor Bill** from your Vendor, validate the bill with products received in the previous step to ensure accuracy."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:27
-msgid "This process may be done by three different people within the company, or only one."
+#: ../../purchase/purchases/rfq/bills.rst:26
+msgid "You might want to use different settings for different types of products."
 msgstr ""

 #: ../../purchase/purchases/rfq/bills.rst:34
-msgid "Installing the Purchase and Inventory applications"
+msgid "Verify your Vendor Bill"
 msgstr ""

 #: ../../purchase/purchases/rfq/bills.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."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:41
-msgid "Creating products"
+msgid "If you didn’t receive any of your product yet on *Purchase Order* under the *Shipment* tab,"
 msgstr ""

 #: ../../purchase/purchases/rfq/bills.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**."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:50
-msgid "When creating the product, Pay attention to the **Product Type** field, as it is important:"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.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 ""
-
-#: ../../purchase/purchases/rfq/bills.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."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.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 recommend to set the product type to **Service**."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:70
-msgid "Managing your Vendor Bills"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:73
-msgid "Purchasing products or services"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:75
-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)"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:85
-msgid "Validate the purchase order and receive the products from the **Inventory** application."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:89
-msgid "Receiving Products"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:91
-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:"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:100
-msgid "Navigating this route will take you to a list of all orders awaiting to be received."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:106
-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** (or **Partner**), the product, or the source document, also known as the reference of your purchase order. You also have the capability to 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."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:117
-msgid "Purchasing **Service** products does not trigger a delivery order."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:120
-msgid "Managing Vendor Bills"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:122
-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."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:130
-msgid "The first thing you will need to do upon creating a **Vendor Bill** is to select the appropriate **Vendor** as this will also pull up any associated accounting or pricelist information. From there, you can choose to specify any 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."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:144
-msgid "While the invoice is in draft state, you can make any modifications you need (i.e. remove or add product lines, modify quantities, and change prices)."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:149
-msgid "Your vendor may send you several bills for the same purchase order if:"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:151
-msgid "Your vendor is in back-order and is sending you invoices as they ship the products."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:154
-msgid "Your vendor is sending you a partial bill or asking for a deposit."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:156
-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."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:165
-msgid "Vendor Bill Matching"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:168
-msgid "What to do if your vendor bill does not match what you received"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:170
-msgid "If the bill you receive from the vendor has different quantities than what Odoo automatically populates as quantities, this could be due to several reasons:"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:174
-msgid "The vendor is incorrectly charging you for products and/or services that you have not ordered."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:177
-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."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:181
-msgid "Or the vendor did not bill you for previously purchased products."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:183
-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 ""
-
-#: ../../purchase/purchases/rfq/bills.rst:187
-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 ""
-
-#: ../../purchase/purchases/rfq/bills.rst:190
-msgid "The vendor has already invoiced you for this purchase order, therefore it is not going to appear anywhere in the selection."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:193
-msgid "Someone in the company forgot to record a purchase order for this vendor."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:196
-msgid "Or the vendor is charging you for something you did not order."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:199
-msgid "How product quantities are managed"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:201
-msgid "By default, services are managed based on ordered quantities, while stockables and consumables are managed based on received quantities."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:204
-msgid "If you need to manage products based on ordered quantities over received quantities, you will need to enable **Debug Mode** from the **About Odoo** information. Once debug mode is activated, select the product(s) you wish to modify, and you should see a new field appear, labeled **Control Purchase Bills**."
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:213
-msgid "You can then change the default management method for the selected product to be based on either:"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:216
-msgid "Ordered quantities"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:218
-msgid "Received quantities"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:221
-msgid "Batch Billing"
-msgstr ""
-
-#: ../../purchase/purchases/rfq/bills.rst:223
-msgid "When creating a vendor bill and selecting the appropriate purchase order, you may continue to select additional purchase orders and Odoo will add the additional line items from that purchase order. 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."
+msgid "Depending on the billing policy defined above. If you're supposed to be billed based on ordered quantity, Odoo will suggest a bill for the number of units ordered. If you're supposed to be billed based on the received quantities, Odoo will suggest a bill for 0 as shown above."
 msgstr ""

 #: ../../purchase/purchases/rfq/cancel.rst:3
--- a/locale/sources/sales.pot
+++ b/locale/sources/sales.pot
@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo 11.0\n"
+"Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2018-10-19 10:03+0200\n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
@ -538,134 +538,150 @@ msgid "How to adapt your prices to your customers and apply discounts"
 msgstr ""

 #: ../../sales/products_prices/prices/pricing.rst:5
-msgid "Odoo has a powerful pricelist feature to support a pricing strategy tailored to your business. A pricelist is a list of prices or price rules that Odoo searches to determine the suggested price. You can set several critarias to use a specific price: periods, min. sold quantity (meet a minimum order quantity and get a price break), etc. As pricelists only suggest prices, they can be overridden by users completing sales orders. Choose your pricing strategy from :menuselection:`Sales --> Settings`."
+msgid "Odoo has a powerful pricelist feature to support a pricing strategy tailored to your business. A pricelist is a list of prices or price rules that Odoo searches to determine the suggested price. You can set several critarias to use a specific price: periods, min. sold quantity (meet a minimum order quantity and get a price break), etc."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:16
-msgid "Several prices per product"
+#: ../../sales/products_prices/prices/pricing.rst:9
+msgid "As pricelists only suggest prices, they can be overridden by vendors completing sales orders. Choose your pricing strategy from :menuselection:`Sales --> Settings`."
 msgstr ""

 #: ../../sales/products_prices/prices/pricing.rst:18
-msgid "To apply several prices per product, select *Different prices per customer segment* in :menuselection:`Sales --> Settings`. Then open the *Sales* tab in the product detail form. You can settle following strategies."
+msgid "*A single sale price per product :* doesn't let you adapt prices, it use default product price ;"
+msgstr ""
+
+#: ../../sales/products_prices/prices/pricing.rst:19
+msgid "*Different prices per customer segment :* you will set several prices per products ;"
+msgstr ""
+
+#: ../../sales/products_prices/prices/pricing.rst:20
+msgid "*Advanced pricing based on formula :* will let you apply discounts, margins and roundings."
 msgstr ""

 #: ../../sales/products_prices/prices/pricing.rst:23
-msgid "Prices per customer segment"
+msgid "Several prices per product"
 msgstr ""

 #: ../../sales/products_prices/prices/pricing.rst:25
-msgid "Create pricelists for your customer segments: e.g. registered, premium, etc."
+msgid "To apply several prices per product, select *Different prices per customer segment* in :menuselection:`Sales --> Settings`. Then open the *Sales* tab in the product detail form. You can settle following strategies."
 msgstr ""

 #: ../../sales/products_prices/prices/pricing.rst:30
+msgid "Prices per customer segment"
+msgstr ""
+
+#: ../../sales/products_prices/prices/pricing.rst:32
+msgid "Create pricelists for your customer segments: e.g. registered, premium, etc."
+msgstr ""
+
+#: ../../sales/products_prices/prices/pricing.rst:37
 msgid "The default pricelist applied to any new customer is *Public Pricelist*. To segment your customers, open the customer detail form and change the *Sale Pricelist* in the *Sales & Purchases* tab."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:38
+#: ../../sales/products_prices/prices/pricing.rst:45
 msgid "Temporary prices"
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:40
+#: ../../sales/products_prices/prices/pricing.rst:47
 msgid "Apply deals for bank holidays, etc. Enter start and end dates dates."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:46
+#: ../../sales/products_prices/prices/pricing.rst:53
 msgid "Make sure you have default prices set in the pricelist outside of the deals period. Otherwise you might have issues once the period over."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:50
+#: ../../sales/products_prices/prices/pricing.rst:57
 msgid "Prices per minimum quantity"
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:56
+#: ../../sales/products_prices/prices/pricing.rst:63
 msgid "The prices order does not matter. The system is smart and applies first prices that match the order date and/or the minimal quantities."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:60
+#: ../../sales/products_prices/prices/pricing.rst:67
 msgid "Discounts, margins, roundings"
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:62
-msgid "The third option allows to set price change rules. Changes can be relative to the product list/catalog price, the product cost price, or to another pricelist. Changes are calculated via discounts or surcharges and can be forced to fit within floor (minumum margin) and ceilings (maximum margins). Prices can be rounded to the nearest cent/dollar or multiple of either (nearest 5 cents, nearest 10 dollars)."
+#: ../../sales/products_prices/prices/pricing.rst:69
+msgid "*Advanced pricing based on formula* allows to set price change rules. Changes can be relative to the product list/catalog price, the product cost price, or to another pricelist. Changes are calculated via discounts or surcharges and can be forced to fit within floor (minumum margin) and ceilings (maximum margins). Prices can be rounded to the nearest cent/dollar or multiple of either (nearest 5 cents, nearest 10 dollars)."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:69
+#: ../../sales/products_prices/prices/pricing.rst:76
 msgid "Once installed go to :menuselection:`Sales --> Configuration --> Pricelists` (or :menuselection:`Website Admin --> Catalog --> Pricelists` if you use e-Commerce)."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:77
+#: ../../sales/products_prices/prices/pricing.rst:84
 msgid "Each pricelist item can be associated to either all products, to a product internal category (set of products) or to a specific product. Like in second option, you can set dates and minimum quantities."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:84
+#: ../../sales/products_prices/prices/pricing.rst:91
 msgid "Once again the system is smart. If a rule is set for a particular item and another one for its category, Odoo will take the rule of the item."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:86
+#: ../../sales/products_prices/prices/pricing.rst:93
 msgid "Make sure at least one pricelist item covers all your products."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:88
+#: ../../sales/products_prices/prices/pricing.rst:95
 msgid "There are 3 modes of computation: fix price, discount & formula."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:93
+#: ../../sales/products_prices/prices/pricing.rst:100
 msgid "Here are different price settings made possible thanks to formulas."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:96
+#: ../../sales/products_prices/prices/pricing.rst:103
 msgid "Discounts with roundings"
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:98
+#: ../../sales/products_prices/prices/pricing.rst:105
 msgid "e.g. 20% discounts with prices rounded up to 9.99."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:104
+#: ../../sales/products_prices/prices/pricing.rst:111
 msgid "Costs with markups (retail)"
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:106
+#: ../../sales/products_prices/prices/pricing.rst:113
 msgid "e.g. sale price = 2*cost (100% markup) with $5 of minimal margin."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:112
+#: ../../sales/products_prices/prices/pricing.rst:119
 msgid "Prices per country"
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:113
+#: ../../sales/products_prices/prices/pricing.rst:120
 msgid "Pricelists can be set by countries group. Any new customer recorded in Odoo gets a default pricelist, i.e. the first one in the list matching the country. In case no country is set for the customer, Odoo takes the first pricelist without any country group."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:116
+#: ../../sales/products_prices/prices/pricing.rst:123
 msgid "The default pricelist can be replaced when creating a sales order."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:118
+#: ../../sales/products_prices/prices/pricing.rst:125
 msgid "You can change the pricelists sequence by drag & drop in list view."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:121
+#: ../../sales/products_prices/prices/pricing.rst:128
 msgid "Compute and show discount % to customers"
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:123
+#: ../../sales/products_prices/prices/pricing.rst:130
 msgid "In case of discount, you can show the public price and the computed discount % on printed sales orders and in your eCommerce catalog. To do so:"
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:125
+#: ../../sales/products_prices/prices/pricing.rst:132
 msgid "Check *Allow discounts on sales order lines* in :menuselection:`Sales --> Configuration --> Settings --> Quotations & Sales --> Discounts`."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:126
+#: ../../sales/products_prices/prices/pricing.rst:133
 msgid "Apply the option in the pricelist setup form."
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:133
+#: ../../sales/products_prices/prices/pricing.rst:140
 msgid ":doc:`currencies`"
 msgstr ""

-#: ../../sales/products_prices/prices/pricing.rst:134
+#: ../../sales/products_prices/prices/pricing.rst:141
 msgid ":doc:`../../../ecommerce/maximizing_revenue/pricing`"
 msgstr ""

@ -737,6 +753,178 @@ msgstr ""
 msgid "Set taxes"
 msgstr ""

+#: ../../sales/sale_amazon.rst:3
+msgid "Amazon MWS Connector"
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:3
+msgid "Manage Amazon orders in Odoo"
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:6
+msgid "Synchronization of orders"
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:8
+msgid "Orders are automatically fetched from Amazon and synchronized in Odoo at regular intervals. The synchronization is based on the Amazon status: only orders whose status has changed since the last synchronization are fetched from Amazon. For **FBA** (Fulfilled by Amazon), only **Shipped** and **Canceled** orders are fetched. For **FBM** (Fulfilled by Merchant), the same is done for **Unshipped** and **Canceled** orders. For each synchronized order, a sales order and a customer are created in Odoo if they are not yet registered."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:15
+msgid "If you did not request access to Personally Identifiable Information of your customers in the `Developer Registration and Assessment form <setup.html#developer-form>`_, the customers are created anonymously (the name, postal address and phone number are omitted) and named **Amazon Customer**."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:20
+msgid "When an order is canceled in Amazon and was already synchronized in Odoo, the corresponding sales order is canceled in Odoo. When an order is canceled in Odoo, a notification is sent to Amazon who will mark it as such in Seller Central and notify the customer."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:25
+msgid "To force the synchronization of an order whose status has not changed since the last synchronization, activate the **Developer mode**, navigate to your Amazon account and modify the date under :menuselection:`Orders Follow-up --> Last Order Sync`. Pick a date anterior to the last status change of the order that you wish to synchronize and save."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:30
+msgid "To synchronize immediately the orders of your Amazon account, open that later's form in **Developer mode** and click the button **SYNC ORDERS**. The same can be done with order cancellations and pickings by clicking the buttons **SYNC CANCELLATIONS** and **SYNC PICKINGS**."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:36
+msgid "Manage deliveries in FBM"
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:38
+msgid "When a **FBM** (Fulfilled by Merchant) order is synchronized in Odoo, a picking is created along with the sales order and the customer. You can either ship all the ordered products to your customer at once or ship products partially by using backorders."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:42
+msgid "When a picking related to the order is confirmed, a notification is sent to Amazon who will, in turn, notify the customer that the order (or a part of it) is on its way."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:46
+msgid "Follow deliveries in FBA"
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:48
+msgid "When a **FBA** (Fulfilled by Amazon) order is synchronized in Odoo, a stock move is recorded for each sales order item so that it is saved in your system. Inventory managers can find such moves in :menuselection:`Inventory --> Reporting --> Product Moves`. They pick up products in a specific inventory location called **Amazon**. This location represents your stock in Amazon's warehouses and allows you to manage the stock of your products under the FBA program."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:54
+msgid "To follow your Amazon (FBA) stock in Odoo, you can make an inventory adjustment after replenishing it. You can also trigger an automated replenishment from reordering rules on the Amazon location."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:58
+msgid "The Amazon location is configurable by Amazon account managed in Odoo. All accounts of the same company use the same location by default. It is however possible to follow the stock by marketplace. First, remove the marketplace for which you want to follow the stock separately from the list of synchronized marketplaces. Then, create another registration for this account and remove all marketplaces, except the one to isolate from the others. Finally, assign another stock location to the second registration of your account."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:67
+msgid "Issue invoices and register payments"
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:69
+msgid "You can issue invoices for Amazon orders in Odoo. Click **Create Invoice** in the sales order to do so. You can also do it in batch from the list view of orders. Then, confirm and send the invoices to your customers."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:73
+msgid "To display only Amazon-related orders on the list view, you can filter orders based on the sales team."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:76
+msgid "As the customer has paid Amazon as an intermediary, you should register invoice payments in a payment journal dedicated to Amazon (e.g. Amazon Payments, with a dedicated intermediary account). You can do the same with the vendor bill received from Amazon and dedicated to commissions. When you receive the balance on your bank account at the end of the month and record your bank statements in Odoo, you simply credit the Amazon intermediary account by the amount received."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:83
+msgid "Follow your Amazon sales in sales reporting"
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:85
+msgid "As a sales team is set on your account under the tab **Order Follow-up**, this helps you give quick glances at the figures in just a few clicks in Sales reporting. By default, your account's sales team is shared between all of your company's accounts."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:89
+msgid "If you wish, you can change the sales team on your account for another to perform a separate reporting for the sales of this account."
+msgstr ""
+
+#: ../../sales/sale_amazon/manage.rst:92
+msgid "It is also possible to perform reporting on a per-marketplace basis in a similar fashion. First, remove the marketplace you wish to track separately from the list of synchronized marketplaces. Then, create another registration for this account and remove all marketplaces, except the one to isolate from the others. Finally, assign another sales team to one of the two registrations of your account."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:3
+msgid "Configure Amazon MWS Connector in Odoo"
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:6
+msgid "Get your Amazon MWS Credentials"
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:8
+msgid "In order to integrate Amazon with Odoo, a seller account on professional selling plan is required."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:13
+msgid "Visit the `Amazon Marketplace Web Service documentation <http://docs.developer.amazonservices.com/en_US/dev_guide/DG_Registering.html>`_ and follow the instructions to register as a developer."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:17
+msgid "Fill the Developer Registration and Assessment form as suggested below and provide your own contact information in the **Developer contact information** section. For the other sections, take care to adapt your responses accordingly to your business case. In particular, select the correct region of your seller account and uncheck the **Merchant Fulfilled Shipping** function if you plan to sell exclusively with the Fulfillment by Amazon service."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:23
+msgid "If you select the **Merchant Fulfilled Shipping** function (i.e. you request access to Personally Identifiable Information (PII) of your customers), Amazon may request you to fill out a second form, depending on the data protection policy in the region of your seller account (e.g. GDPR in Europe)."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:32
+msgid "Register your Amazon account in Odoo"
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:34
+msgid "To register your seller account in Odoo, navigate to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts` and click on **CREATE**."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:37
+msgid "The **Seller ID** can be found in Seller Central under the link **Your Merchant Token** on the **Seller Account Information** page. The **Access Key** and the **Secret Key** can be found in Developer Central (where the Developer Registration and Assessment form was located)."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:41
+msgid "Once the account is registered, the marketplaces available to this account are synchronized and listed under the **Marketplaces** tab. If you wish, you can remove some from the list of synchronized marketplaces to disable their synchronization."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:46
+msgid "Match database products in Amazon orders"
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:51
+msgid "When an Amazon order is synchronized, up to three sales order items are created in Odoo for each product sold on Amazon: one for the marketplace product, one for the shipping charges (if any) and one for the gift wrapping charges (if any)."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:55
+msgid "The selection of a database product for a sales order item is done by matching its **internal reference** with the **SKU** for marketplace items, the **shipping code** for delivery charges, and the **gift wrapping** code for gift wrapping charges."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:59
+msgid "For marketplace products, matchings are saved as **Amazon Offers** which are listed under the **Offers** stat button on the account form. Offers are automatically created when the matching is established and are used for subsequent orders to lookup SKUs. If no offer with a matching SKU is found, :ref:`the internal reference is used instead <matching>`."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:64
+msgid "It is possible to force the matching of a marketplace item with a specific product by changing either the product or the SKU of an offer. The offer can be manually created if it was not automatically done yet. This is useful if you do not use the internal reference as the SKU or if you sell the product under different conditions."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:69
+msgid "If no database product with a matching internal reference is found for a given SKU or gift wrapping code, a default database product **Amazon Sale** is used. The same is done with the default product **Amazon Shipping** and the shipping code."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:73
+msgid "To modify the default products, activate the **Developer mode** and navigate to :menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync --> Default Products`."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:78
+msgid "Configure taxes of products"
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:80
+msgid "To allow for tax reporting of Amazon sales with Odoo, the taxes applied to the sales order items are those set on the product or determined by the fiscal position. Make sure to have set the correct taxes on your products in Odoo or to have it done by a fiscal position, to avoid discrepancies in the subtotals between Seller Central and Odoo."
+msgstr ""
+
+#: ../../sales/sale_amazon/setup.rst:85
+msgid "As Amazon does not necessarily apply the same taxes as those configured in Odoo, it may happen that order totals differ by a few cents from that on Seller Central. Those differences can be resolved with a write-off when reconciling the payments in Odoo."
+msgstr ""
+
 #: ../../sales/sale_ebay.rst:3
 msgid "eBay"
 msgstr ""
@ -750,7 +938,7 @@ msgid "Stimulate customers with quotations deadline"
 msgstr ""

 #: ../../sales/send_quotations/deadline.rst:5
-msgid "As you send quotations, it is important to set a quotation deadline; Both to entice your customer into action with the fear of missing out on an offer and to protect yourself. You don't want to have to fulfill an order at a price that is no longer cost effective for you."
+msgid "As you send quotations, it is important to set a quotation deadline, both to entice your customer into action with the fear of missing out on an offer and to protect yourself. You don't want to have to fulfill an order at a price that is no longer cost effective for you."
 msgstr ""

 #: ../../sales/send_quotations/deadline.rst:11
@ -770,7 +958,7 @@ msgid "You can also set a default deadline in a *Quotation Template*. Each time
 msgstr ""

 #: ../../sales/send_quotations/deadline.rst:29
-msgid "On your customer side, they will see this."
+msgid "On your customer side, they will see this:"
 msgstr ""

 #: ../../sales/send_quotations/different_addresses.rst:3
--- a/locale/sources/support.pot
+++ b/locale/sources/support.pot
@ -0,0 +1,571 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2015-TODAY, Odoo S.A.
+# This file is distributed under the same license as the Odoo package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Odoo 13.0\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2019-10-03 11:39+0200\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"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../support.rst:5
+msgid "Support"
+msgstr ""
+
+#: ../../support/supported_versions.rst:6
+msgid "Supported versions"
+msgstr ""
+
+#: ../../support/supported_versions.rst:9
+msgid "Odoo provides support and bug fixing **for the 3 last major versions** of Odoo."
+msgstr ""
+
+#: ../../support/supported_versions.rst:11
+msgid "Users hosted on **Odoo Online** may use intermediary versions (sometimes called *SaaS versions*) that are supported as well. These versions are not published for Odoo.sh or On-Premise installations."
+msgstr ""
+
+#: ../../support/supported_versions.rst:17
+msgid "What's the support status of my Odoo?"
+msgstr ""
+
+#: ../../support/supported_versions.rst:19
+msgid "This matrix shows the support status of every version."
+msgstr ""
+
+#: ../../support/supported_versions.rst:21
+msgid "**Major releases are in bold type.**"
+msgstr ""
+
+#: ../../support/supported_versions.rst:24
+msgid "Odoo Online"
+msgstr ""
+
+#: ../../support/supported_versions.rst:24
+msgid "Odoo.sh"
+msgstr ""
+
+#: ../../support/supported_versions.rst:24
+msgid "On-Premise"
+msgstr ""
+
+#: ../../support/supported_versions.rst:24
+msgid "Release date"
+msgstr ""
+
+#: ../../support/supported_versions.rst:26
+msgid "**Odoo 13.0**"
+msgstr ""
+
+#: ../../support/supported_versions.rst:26
+#: ../../support/supported_versions.rst:26
+#: ../../support/supported_versions.rst:26
+#: ../../support/supported_versions.rst:28
+#: ../../support/supported_versions.rst:30
+#: ../../support/supported_versions.rst:30
+#: ../../support/supported_versions.rst:30
+#: ../../support/supported_versions.rst:32
+#: ../../support/supported_versions.rst:34
+#: ../../support/supported_versions.rst:34
+#: ../../support/supported_versions.rst:34
+msgid "🟢"
+msgstr ""
+
+#: ../../support/supported_versions.rst:26
+msgid "October 2019"
+msgstr ""
+
+#: ../../support/supported_versions.rst:28
+msgid "Odoo 12.saas~3"
+msgstr ""
+
+#: ../../support/supported_versions.rst:28
+#: ../../support/supported_versions.rst:28
+#: ../../support/supported_versions.rst:32
+#: ../../support/supported_versions.rst:32
+#: ../../support/supported_versions.rst:36
+#: ../../support/supported_versions.rst:36
+#: ../../support/supported_versions.rst:38
+#: ../../support/supported_versions.rst:38
+#: ../../support/supported_versions.rst:42
+#: ../../support/supported_versions.rst:42
+#: ../../support/supported_versions.rst:44
+#: ../../support/supported_versions.rst:46
+#: ../../support/supported_versions.rst:46
+#: ../../support/supported_versions.rst:48
+msgid "N/A"
+msgstr ""
+
+#: ../../support/supported_versions.rst:28
+msgid "August 2019"
+msgstr ""
+
+#: ../../support/supported_versions.rst:30
+msgid "**Odoo 12.0**"
+msgstr ""
+
+#: ../../support/supported_versions.rst:30
+msgid "October 2018"
+msgstr ""
+
+#: ../../support/supported_versions.rst:32
+msgid "Odoo 11.saas~3"
+msgstr ""
+
+#: ../../support/supported_versions.rst:32
+msgid "April 2018"
+msgstr ""
+
+#: ../../support/supported_versions.rst:34
+msgid "**Odoo 11.0**"
+msgstr ""
+
+#: ../../support/supported_versions.rst:34
+msgid "October 2017"
+msgstr ""
+
+#: ../../support/supported_versions.rst:34
+msgid "*End-of-support is planned for October 2020*"
+msgstr ""
+
+#: ../../support/supported_versions.rst:36
+msgid "Odoo 10.saas~15"
+msgstr ""
+
+#: ../../support/supported_versions.rst:36
+#: ../../support/supported_versions.rst:38
+#: ../../support/supported_versions.rst:40
+#: ../../support/supported_versions.rst:40
+#: ../../support/supported_versions.rst:42
+#: ../../support/supported_versions.rst:44
+#: ../../support/supported_versions.rst:46
+#: ../../support/supported_versions.rst:48
+msgid "🟠"
+msgstr ""
+
+#: ../../support/supported_versions.rst:36
+msgid "March 2017"
+msgstr ""
+
+#: ../../support/supported_versions.rst:38
+msgid "Odoo 10.saas~14"
+msgstr ""
+
+#: ../../support/supported_versions.rst:38
+msgid "January 2017"
+msgstr ""
+
+#: ../../support/supported_versions.rst:40
+msgid "**Odoo 10.0**"
+msgstr ""
+
+#: ../../support/supported_versions.rst:40
+#: ../../support/supported_versions.rst:44
+#: ../../support/supported_versions.rst:48
+msgid "🔴"
+msgstr ""
+
+#: ../../support/supported_versions.rst:40
+msgid "October 2016"
+msgstr ""
+
+#: ../../support/supported_versions.rst:42
+msgid "Odoo 9.saas~11"
+msgstr ""
+
+#: ../../support/supported_versions.rst:42
+msgid "May 2016"
+msgstr ""
+
+#: ../../support/supported_versions.rst:44
+msgid "**Odoo 9.0**"
+msgstr ""
+
+#: ../../support/supported_versions.rst:44
+msgid "October 2015"
+msgstr ""
+
+#: ../../support/supported_versions.rst:46
+msgid "Odoo 8.saas~6"
+msgstr ""
+
+#: ../../support/supported_versions.rst:46
+msgid "February 2015"
+msgstr ""
+
+#: ../../support/supported_versions.rst:48
+msgid "**Odoo 8.0**"
+msgstr ""
+
+#: ../../support/supported_versions.rst:48
+msgid "September 2014"
+msgstr ""
+
+#: ../../support/supported_versions.rst:54
+msgid "🟢 Supported version"
+msgstr ""
+
+#: ../../support/supported_versions.rst:56
+msgid "🔴 End-of-support"
+msgstr ""
+
+#: ../../support/supported_versions.rst:58
+msgid "N/A Never released for this platform"
+msgstr ""
+
+#: ../../support/supported_versions.rst:60
+msgid "🟠 Some of our older customers may still run this version on our Odoo Online servers, we provide help only on blocking issues and advise you to upgrade."
+msgstr ""
+
+#: ../../support/supported_versions.rst:62
+msgid "🏁 Future version, not released yet"
+msgstr ""
+
+#: ../../support/supported_versions.rst:66
+msgid "I run an older version of Odoo/OpenERP/TinyERP"
+msgstr ""
+
+#: ../../support/supported_versions.rst:68
+msgid "OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform."
+msgstr ""
+
+#: ../../support/supported_versions.rst:70
+msgid "TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform."
+msgstr ""
+
+#: ../../support/supported_versions.rst:72
+msgid "You should consider `upgrading <https://upgrade.odoo.com/>`_ your database."
+msgstr ""
+
+#: ../../support/user_doc.rst:6
+msgid "Contribute to the documentation"
+msgstr ""
+
+#: ../../support/user_doc.rst:9
+msgid "First of all..."
+msgstr ""
+
+#: ../../support/user_doc.rst:11
+msgid "**... Thank you for landing here and helping us to improve the user documentation of Odoo.**"
+msgstr ""
+
+#: ../../support/user_doc.rst:15
+msgid "Edit an existing page"
+msgstr ""
+
+#: ../../support/user_doc.rst:17
+msgid "As our documentation is maintained on GitHub, you'll need a free `GitHub account <https://help.github.com/en/articles/signing-up-for-a-new-github-account>`_."
+msgstr ""
+
+#: ../../support/user_doc.rst:18
+msgid "Pick a page in our `user documentation <https://www.odoo.com/documentation/user>`_. **Please take care of choosing the right version of Odoo.**"
+msgstr ""
+
+#: ../../support/user_doc.rst:19
+msgid "Click on **Edit on Github** in the left menu."
+msgstr ""
+
+#: ../../support/user_doc.rst:25
+msgid "If this is the first time you edit our documentation, click on **Fork repository**, else you won't see this step."
+msgstr ""
+
+#: ../../support/user_doc.rst:26
+msgid "Use Github's editor to add your text. Text is tagged with a simple syntax called `RST <http://docutils.sourceforge.net/rst.html>`_. Don't worry, it's not so hard to learn 🤓... See the following section of this document for a quick overview of RST commands."
+msgstr ""
+
+#: ../../support/user_doc.rst:32
+msgid "Click on **Preview changes** to review your contribution in a human-readable format."
+msgstr ""
+
+#: ../../support/user_doc.rst:38
+msgid "In the **Propose file change** section, add a short title to your contribution. The title should summarize your changes. You may use the second box to add an extended description if your contribution requires a longer explanation."
+msgstr ""
+
+#: ../../support/user_doc.rst:44
+msgid "Submit your contribution by clicking on **Propose file change**."
+msgstr ""
+
+#: ../../support/user_doc.rst:45
+msgid "Click on **Create pull request**."
+msgstr ""
+
+#: ../../support/user_doc.rst:46
+msgid "Wait for an Odoo maintainer to add your contribution. Thank you for your help!"
+msgstr ""
+
+#: ../../support/user_doc.rst:49
+msgid "There is no automatic port of your edit to another version of the documentation."
+msgstr ""
+
+#: ../../support/user_doc.rst:51
+msgid "If your change should apply to multiple versions of Odoo, please warn us in your contribution message."
+msgstr ""
+
+#: ../../support/user_doc.rst:55
+msgid "RST Cheat Sheet"
+msgstr ""
+
+#: ../../support/user_doc.rst:57
+msgid "Here is a summary of the markup elements you may use while editing our documentation."
+msgstr ""
+
+#: ../../support/user_doc.rst:60
+msgid "Code"
+msgstr ""
+
+#: ../../support/user_doc.rst:60
+msgid "Display"
+msgstr ""
+
+#: ../../support/user_doc.rst:60
+msgid "Comments"
+msgstr ""
+
+#: ../../support/user_doc.rst:62
+msgid "Text in *italics*"
+msgstr ""
+
+#: ../../support/user_doc.rst:66
+msgid "Text in **bold** letters"
+msgstr ""
+
+#: ../../support/user_doc.rst:70
+#: ../../support/user_doc.rst:76
+msgid "Numbered"
+msgstr ""
+
+#: ../../support/user_doc.rst:71
+#: ../../support/user_doc.rst:77
+msgid "Bullet"
+msgstr ""
+
+#: ../../support/user_doc.rst:72
+#: ../../support/user_doc.rst:78
+msgid "List"
+msgstr ""
+
+#: ../../support/user_doc.rst:70
+#: ../../support/user_doc.rst:76
+msgid "Must be surrounded by white lines."
+msgstr ""
+
+#: ../../support/user_doc.rst:82
+msgid "This is `a  hyper link <https://www.odoo.com>`_."
+msgstr ""
+
+#: ../../support/user_doc.rst:82
+msgid "Here is `how to enter backticks on your keyboard <https://superuser.com/a/254077>`_."
+msgstr ""
+
+#: ../../support/user_doc.rst:85
+msgid "Don't forget terminal *underscore*."
+msgstr ""
+
+#: ../../support/user_doc.rst:90
+msgid "There are many more commands available, see `comprehensive documentation <http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html>`_ of RST."
+msgstr ""
+
+#: ../../support/user_doc.rst:94
+msgid "Add images to your documents"
+msgstr ""
+
+#: ../../support/user_doc.rst:98
+msgid "This procedure is possible only for users who have **push** access on the documentation repository (eg: mainly, Odoo maintainers). We are working on improving this."
+msgstr ""
+
+#: ../../support/user_doc.rst:101
+msgid "First of all, prepare your screenshots."
+msgstr ""
+
+#: ../../support/user_doc.rst:103
+msgid "They must be good-quality PNG images."
+msgstr ""
+
+#: ../../support/user_doc.rst:104
+msgid "Crop your screenshots to display only the relevant part of the screen. Large screenshots are hard to read and don't display well in a documentation."
+msgstr ""
+
+#: ../../support/user_doc.rst:106
+msgid "Always take your screenshots on a demo instance of Odoo; **never** include any personal data."
+msgstr ""
+
+#: ../../support/user_doc.rst:108
+msgid "Upload them to the ``media/`` directory which is located next to the page you are editing. If the directory does not exist, create it."
+msgstr ""
+
+#: ../../support/user_doc.rst:109
+msgid "When editing your page, use this code piece in order to load your image:"
+msgstr ""
+
+#: ../../support/user_doc.rst:117
+msgid "Submit your changes"
+msgstr ""
+
+#: ../../support/user_doc.rst:128
+msgid "Technical Details for Nerds"
+msgstr ""
+
+#: ../../support/user_doc.rst:130
+msgid "Advanced users may, of course, fork and clone `the GitHub repository <https://github.com/odoo/documentation-user>`_. Then submit a pull request with the canonical Git/GitHub workflow."
+msgstr ""
+
+#: ../../support/user_doc.rst:133
+msgid "See our `README <https://github.com/odoo/documentation-user/blob/13.0/README.rst>`_ file about building the documentation."
+msgstr ""
+
+#: ../../support/user_doc.rst:138
+msgid "Developer documentation"
+msgstr ""
+
+#: ../../support/user_doc.rst:140
+msgid "Documentation that targets developers of Odoo apps is maintained alongside `the source code of Odoo <https://github.com/odoo/odoo/tree/13.0/doc>`_."
+msgstr ""
+
+#: ../../support/user_doc.rst:143
+msgid "User documentation might contain technicalities yet, when they are related to configuration and everyday use of Odoo."
+msgstr ""
+
+#: ../../support/user_doc.rst:149
+#: ../../support/where_can_i_get_support.rst:36
+msgid "*Last revision of this page:* |date|"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:8
+msgid "What can I expect from the support service?"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:12
+msgid "5 days a week"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:14
+msgid "Your Odoo Online subscription includes **unlimited 24hr support at no extra cost, Monday to Friday**. Our teams are located around the world to ensure you have support, no matter your location. Your support representative could be communicating to you from San Francisco, Belgium, or India!"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:19
+msgid "Our support team can be contacted through our `online support form <https://www.odoo.com/help>`__."
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:23
+msgid "What kind of support is included?"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:25
+msgid "Providing you with relevant material (guidelines, product documentation, etc...)"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:27
+msgid "Answers to issues that you may encounter in your standard Odoo database (eg. “I cannot close my Point of Sale” or “I cannot find my sales KPIs?”)"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:29
+msgid "Questions related to your account, subscription, or billing"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:30
+msgid "Bug resolution (blocking issues or unexpected behaviour not due to misconfiguration or customization)"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:32
+msgid "Issues that might occur in a test database after upgrading to a newer version"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:34
+msgid "*Odoo Support does not make changes to your production database, but gives you the material and knowledge to do it yourself!*"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:39
+msgid "What kind of support is not included?"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:41
+msgid "Questions that require us to understand your business processes in order to help you implement your database"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:43
+msgid "Training on how to use our software (we will direct you to our many resources)"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:44
+msgid "Import of documents into your database"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:45
+msgid "Guidance on which configurations to apply inside of an application or the database"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:46
+msgid "How to set up configuration models (Examples include: Inventory Routes, Payment Terms, Warehouses, etc)"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:48
+msgid "Any intervention on your own servers/deployments of Odoo"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:49
+msgid "Questions or issues related to specific developments or customizations done either by Odoo or a third party (this is specific only to your database or involving code)"
+msgstr ""
+
+#: ../../support/what_can_i_expect.rst:53
+msgid "You can get this type of support with a `Success Pack <https://www.odoo.com/pricing-packs>`__. With a pack, one of our consultants will analyze the way your business runs and tell you how you can get the most out of your Odoo Database. We will handle all configurations and coach you on how to use Odoo."
+msgstr ""
+
+#: ../../support/where_can_i_get_support.rst:6
+msgid "Where to find help?"
+msgstr ""
+
+#: ../../support/where_can_i_get_support.rst:10
+msgid "Odoo Enterprise"
+msgstr ""
+
+#: ../../support/where_can_i_get_support.rst:12
+msgid "Users who have a valid Odoo Enterprise subscription may always contact our support teams through our `support form <https://www.odoo.com/help>`_, no matter the hosting type you chose (Odoo Online, Odoo.sh or on your own server)."
+msgstr ""
+
+#: ../../support/where_can_i_get_support.rst:14
+msgid "Please include in your request:"
+msgstr ""
+
+#: ../../support/where_can_i_get_support.rst:16
+msgid "your subscription number,"
+msgstr ""
+
+#: ../../support/where_can_i_get_support.rst:17
+msgid "if your database is hosted by Odoo (Odoo Online or Odoo.sh), please also send the URL of your database."
+msgstr ""
+
+#: ../../support/where_can_i_get_support.rst:19
+msgid "Our agents will get back to you as soon as possible."
+msgstr ""
+
+#: ../../support/where_can_i_get_support.rst:23
+msgid "Odoo Community"
+msgstr ""
+
+#: ../../support/where_can_i_get_support.rst:25
+msgid "*Odoo Community users don't get access to the support service.*"
+msgstr ""
+
+#: ../../support/where_can_i_get_support.rst:27
+msgid "Here are some resources that might help you:"
+msgstr ""
+
+#: ../../support/where_can_i_get_support.rst:29
+msgid "Our `documentation pages <https://www.odoo.com/page/docs>`_."
+msgstr ""
+
+#: ../../support/where_can_i_get_support.rst:30
+msgid "Ask your question on the `community forum <https://www.odoo.com/forum/help-1>`_."
+msgstr ""
+
+#: ../../support/where_can_i_get_support.rst:31
+msgid "`Buy Odoo Enterprise <https://www.odoo.com/help>`_ to get the support and bugfix services."
+msgstr ""
+
--- a/locale/sources/website.pot
+++ b/locale/sources/website.pot