[FIX] accounting: mark salt edge bank sync provider available worldwide

task-3329454

conf.py

@@ -291,16 +291,13 @@ latex_documents = [
      'Odoo Enterprise Subscription Agreement (ES)', '', 'howto'),
     ('legal/terms/i18n/partnership_tex_es',
      'odoo_partnership_agreement_es.tex', 'Odoo Partnership Agreement (ES)', '', 'howto'),
-
-    ('legal/terms/i18n/enterprise_tex_pt_BR', 'odoo_enterprise_agreement_pt_BR.tex',
-     'Odoo Enterprise Subscription Agreement (PT)', '', 'howto'),
 ]
 
 # List of languages that have legal translations (excluding EN). The keys must be in
 # `languages_names`. These translations will have a link to their versions of the legal
 # contracts, instead of the default EN one. The main legal documents are not part of the
 # translations since they have legal meaning.
-legal_translations = ['de', 'es', 'fr', 'nl', 'pt_BR']
+legal_translations = ['de', 'es', 'fr', 'nl']
 
 # The name of an image file (relative to this directory) to place at the top of the title page.
 latex_logo = 'static/img/odoo_logo.png'

content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst

@@ -1,61 +1,69 @@
-============
-EPC QR codes
-============
+============================
+Add EPC QR Codes to invoices
+============================
 
-European Payments Council quick response codes, or **EPC QR codes**, are two-dimensional barcodes
-that customers can scan with their **mobile banking applications** to initiate a **SEPA credit
-transfer (SCT)** and pay their invoices instantly.
+European Payments Council Quick Response Code,
+or **EPC QR Code**, are two-dimensional barcodes
+that customers can scan with their **mobile banking
+applications** to initiate a **SEPA Credit Transfer
+(SCT)**, and pay their invoices instantly.
 
-In addition to bringing ease of use and speed, it greatly reduces typing errors that would
-potentially make for payment issues.
+In addition to bringing ease of use and speed,
+it greatly reduces typing errors that would potentially
+make for payment issues.
 
 .. note::
-   This feature is only available for companies in several European countries such as Austria,
-   Belgium, Finland, Germany, and the Netherlands.
-
-.. seealso::
-   - :doc:`../../bank/setup/bank_accounts`
-   - `Odoo Academy: QR Code on Invoices for European Customers <https://www.odoo.com/r/VuU>`_
+   This feature is only available in several European
+   countries such as Austria, Belgium, Finland, Germany,
+   and The Netherlands.
 
 Configuration
 =============
 
-Go to :menuselection:`Accounting --> Configuration --> Settings` and activate the :guilabel:`QR
-Codes` feature in the :guilabel:`Customer Payments` section.
+Go to :menuselection:`Accounting --> Configuration --> Settings`
+and activate the **SEPA QR Code** feature.
 
-Configure your bank account's journal
+.. image:: epc_qr_code/epc_qr_code01.png
+   :align: center
+
+Configure your Bank Account’s journal
 -------------------------------------
 
-Make sure that your :guilabel:`Bank Account` is correctly configured in Odoo with your IBAN and BIC.
+Make sure that your *Bank Account* is correctly configured
+on Odoo with your IBAN and BIC.
 
-To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open your bank journal,
-then fill out the :guilabel:`Account Number` and :guilabel:`Bank` under the :guilabel:`Bank Account
-Number` column.
+To do so, go to :menuselection:`Accounting --> Configuration
+--> Journals`, open your *bank journal*, then fill out the
+*Bank Account* and *Bank* under the *Bank Account* tab.
 
-.. image:: epc_qr_code/bank-journal.png
-   :alt: Bank account number column in the bank journal
+.. image:: epc_qr_code/epc_qr_code02.png
+   :align: center
 
-Issue invoices with EPC QR codes
+Issue Invoices with EPC QR Codes
 ================================
 
-EPC QR codes are added automatically to your invoices. Customers whose bank supports making payments
-via EPC QR codes will be able to scan the code and pay the invoice.
+EPC QR Codes are added automatically to your invoices, as
+long as you issue them to customers that are located in a
+country where this feature is available.
 
-Go to :menuselection:`Accounting --> Customers --> Invoices`, and create a new invoice.
+Go to :menuselection:`Accounting --> Customers --> Invoices`,
+and create a new invoice.
 
-Before posting it, open the :guilabel:`Other Info` tab. Odoo automatically fills out the
-:guilabel:`Recipient Bank` field with your IBAN.
+Before posting it, open the *Other Info* tab. Odoo automatically
+fills out the *Bank Account* field with your IBAN.
 
-.. note::
-   In the :guilabel:`Other Info` tab, the account indicated in the :guilabel:`Recipient Bank` field
-   is used to receive your customer's payment. Odoo automatically populates this field with your
-   IBAN by default and uses it to generate the EPC QR code.
+Make sure that the account indicated is the one you want to use to
+receive your customer’s payment as Odoo uses this field to generate
+the EPC QR Code.
 
-When the invoice is printed or previewed, the QR code is included at the bottom.
-
-.. image:: epc_qr_code/invoice-qr-code.png
-   :alt: QR code on a customer invoice
+.. image:: epc_qr_code/epc_qr_code03.png
+   :align: center
 
 .. tip::
-   If you want to issue an invoice without an EPC QR code, remove the IBAN indicated in the
-   :guilabel:`Recipient Bank` field, under the :guilabel:`Other Info` tab of the invoice.
+   If you want to issue an invoice without an EPC QR Code,
+   remove the IBAN indicated in the *Bank Account* field,
+   under the *Other Info* tab of the invoice.
+
+.. seealso::
+   * :doc:`../../bank/setup/bank_accounts`
+   * `Odoo Academy: QR Code on Invoices for European Customers <https://www.odoo.com/r/VuU>`_

content/applications/finance/fiscal_localizations/colombia_ES.rst

@@ -16,7 +16,6 @@ requiere los siguientes Módulos:
    - Impuestos
    - Retenciones
    - Tipos de Documentos de Identificación
-   - test and
 
 #. **l10n_co_edi**: Este módulo incluye todos los campos adicionales que son
    requeridos para la Integración entre Carvajal y la generación de la

content/applications/finance/payment_acquirers.rst

@@ -50,9 +50,10 @@ Bank Payments
 - | :doc:`Wire Transfer <payment_acquirers/wire_transfer>`
   | When selected, Odoo displays your payment information with a payment reference. You have to
     approve the payment manually once you have received it on your bank account.
-- | :doc:`SEPA Direct Debit <../finance/accounting/receivables/customer_payments/batch_sdd>`
+- | SEPA Direct Debit
   | Your customers can sign a SEPA Direct Debit mandate online and get their bank account charged
-    directly.
+    directly. :doc:`Click here <../finance/accounting/receivables/customer_payments/batch_sdd>` for more
+    information about this payment method.
 
 .. _payment_acquirers/online_providers:
 
@@ -106,7 +107,7 @@ Add a new Payment Acquirer
 --------------------------
 
 To add a new Payment acquirer and make it available to your customers, go to
-:menuselection:`Accounting / Website --> Configuration --> Payment Acquirers`, look for
+:menuselection:`Accounting / Website --> Configuration --> eCommerce: Payment Acquirers`, look for
 your payment acquirer, install the related module, and activate it. To do so, open the payment
 acquirer and change its state from *Disabled* to *Enabled*.
 
@@ -211,7 +212,7 @@ Multi-company environment
 
 If you have multiple companies on your database and wish to use the same payment acquirer for
 several or all of them, switch to the company on which the payment acquirer is configured, then go
-to :menuselection:`Accounting / Website --> Configuration --> Payment Acquirers` and
+to :menuselection:`Accounting / Website --> Configuration --> Payments: Payment Acquirers` and
 select the payment acquirer to use. Then, click :menuselection:`Action --> Duplicate`, and in the
 :guilabel:`Company` field, set the company for which you want to have that payment acquirer
 available. Configure the rest of the fields according to your needs, and :guilabel:`Save`.

content/applications/finance/payment_acquirers/wire_transfer.rst

@@ -1,47 +1,40 @@
-==============
-Wire transfers
-==============
+===================================
+How to get paid with wire transfers
+===================================
 
-The **Wire transfer** payment method allows you to provide payment instructions to your customers,
-such as the bank details and communication. They are displayed:
+**Wire Transfer** is the default payment method available.
+The aim is providing your customers with your bank details
+so they can pay on their own.
+This is very easy to start with but slow and inefficient process-wise.
+Opt for payment acquirers as soon as you can!
 
-- at the end of the checkout process, once the customer has selected :guilabel:`Wire transfer` as a
-  payment method and clicked the :guilabel:`Pay now` button:
+How to provide customers with payment instructions
+==================================================
 
-  .. image:: wire_transfer/payment_instructions_checkout.png
-     :alt: Payment instructions at checkout
-
-- on the customer portal:
-
-  .. image:: wire_transfer/payment_instructions_portal.png
-     :alt: Payment instructions on the customer portal
-
-.. note::
-   - While this method is very accessible and requires minimal setup, it is very inefficient
-     process-wise. We recommend setting up a :doc:`payment acquirer <../payment_acquirers>` instead.
-   - Online orders remain in the :guilabel:`Quotation sent` (i.e., unpaid order) stage until you
-     receive the payment and :guilabel:`Confirm` the order.
-
-.. tip::
-   **Wire transfer** can be used as a template for other payment methods that are processed
-   manually, such as checks, by renaming or duplicating it.
-
-Configuration
-=============
-
-**Wire Transfer** is installed and enabled by default.
-
-To configure it, go to :menuselection:`Accounting / Website --> Configuration -->
-Payment Acquirers`, and open the :guilabel:`Wire Transfer` card. Then, select the
-:guilabel:`Communication` to be used in the :guilabel:`Configuration` tab:
-
-  - :guilabel:`Based on Document Reference`: sales order or invoice number
-  - :guilabel:`Based on Customer ID`: customer identifier
-
-Define the payment instructions in the :guilabel:`Messages` tab:
+Put your payment instructions in the **Thanks Message** of your payment method.
 
 .. image:: wire_transfer/payment_instructions.png
-   :alt: Define payment instructions
+   :align: center
 
-.. seealso::
-   :doc:`../accounting/getting_started/cheat_sheet`
+They will appear to the customers when they place an order.
+
+.. image:: wire_transfer/payment_customer_instructions.png
+   :align: center
+
+How to manage an order once you get paid
+========================================
+
+Whenever a customer pays by wire transfer, the order stays in an
+intermediary stage **Quotation Sent** (i.e. unpaid order).
+When you get paid,
+you confirm the order manually to launch the delivery.
+
+How to create other manual payment methods
+==========================================
+
+If you manage a B2B business, you can create other manually-processed
+payment methods like paying by check.
+To do so, just rename *Wire Transfer* or duplicate it.
+
+.. image:: wire_transfer/payment_check.png
+   :align: center

content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences.rst

@@ -2,8 +2,6 @@
 What's the difference between lots and serial numbers?
 ======================================================
 
-.. _inventory/management/lots-serial-numbers:
-
 Introduction
 ============
 

content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst

@@ -1,282 +1,137 @@
-=====================================
-Use lots to manage groups of products
-=====================================
+=================================
+Manage lots of identical products
+=================================
 
-*Lots* are one of the two ways to identify and track products in Odoo. A lot usually indicates a
-specific batch of an item that was received, is currently stored, or was shipped from a warehouse,
-but can also pertain to a batch of products manufactured in-house, as well.
+Lots are useful for products you receive in great quantity and for which
+a lot number can help in reporting, quality controls, or any other info.
+Lots will help identify a number of pieces having, for instance, a
+production fault. It can be useful for a batch production of clothes or
+food.
 
-Manufacturers assign lot numbers to groups of products that have common properties; this can lead to
-multiple goods sharing the same lot number. This helps to identify a number of products in a single
-group, and allows for end-to-end traceability of these products through each step in their
-lifecycles.
+Odoo has the capacity to manage lots, ensuring compliance with the
+traceability requirements imposed by the majority of industries.
 
-Lots are useful for products that are manufactured or received in large quantities (such as clothes
-or food), and can be used to trace a product back to a group. This is especially useful when
-managing product recalls or expiration dates.
+The double-entry management in Odoo enables you to run very advanced
+traceability.
 
-.. seealso::
-   :doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers`
+Setting Up
+==========
 
-Enable lots & serial numbers
-============================
+Application Configuration
+-------------------------
 
-To track products using lots, the *Lots & Serial Numbers* feature must be enabled. Go to
-the :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the
-:guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Then,
-click the :guilabel:`Save` button to save changes.
+First, you need to activate the tracking of lot numbers. To do so, go to
+:menuselection:`Inventory --> Configuration --> Settings` and tick *Lots & Serial
+Numbers*. Then, click on save.
 
-.. image:: lots/lots-enabled-lots-setting.png
-   :align: center
-   :alt: Enabled lots and serial numbers feature in inventory settings.
+.. image:: lots/lots_01.png
+    :align: center
 
-Track products by lots
-======================
+Product Configuration
+---------------------
 
-Once the :guilabel:`Lots & Serial Numbers` setting has been activated, individual products can now
-be configured to be tracked using lots. To do this, go to the :menuselection:`Inventory app -->
-Products --> Products`, and choose a product.
+Now, you have to configure which products you want to track by serial
+numbers.
 
-Once on the product form, click :guilabel:`Edit` to make changes to the form. Then, click the
-:guilabel:`Inventory` tab. In the :guilabel:`Traceability` section, click :guilabel:`By Lots`. Then,
-click :guilabel:`Save` to save changes. Existing or new lot numbers can now be assigned to
-newly-received or manufactured batches of this product.
+Go to :menuselection:`Master Data --> Products` and open the product of your choice.
+There, click on *Edit* and select *Tracking by Lots* in the
+inventory tab.
 
-.. important::
-   If a product has stock on-hand prior to activating tracking by lots or serial numbers, an
-   inventory adjustment might need to be performed to assign lot numbers to the existing stock.
+.. image:: lots/lots_02.png
+    :align: center
 
-.. image:: lots/lots-tracking-product-form.png
-   :align: center
-   :alt: Enabled tracking by lots feature on product form.
+.. image:: lots/lots_03.png
+    :align: center
 
-Create new lots for products already in stock
----------------------------------------------
+Manage Lots
+===========
 
-New lots can be created for products already in stock with no assigned lot number. To do this, go to
-the :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`, and click
-:guilabel:`Create`. Doing so reveals a separate page where a new :guilabel:`Lot/Serial Number` is
-generated automatically.
+Receipts
+--------
 
-.. tip::
-   While Odoo automatically generates a new :guilabel:`Lot/Serial Number` to follow the most recent
-   number, it can be edited and changed to any desired number, by clicking the line under the
-   :guilabel:`Lot/Serial Number` field, and changing the generated number.
+In order to receive a product tracked by lots, you have to specify its
+lot numbers. You have several ways of doing so:
 
-Once the new :guilabel:`Lot/Serial Number` is generated, click the blank field next to
-:guilabel:`Product` to reveal a drop-down menu. From this menu, select the product to which this new
-number will be assigned.
+1. Manually assign the different lot numbers
 
-This form also provides the option to adjust the :guilabel:`Quantity`, assign a unique
-:guilabel:`Internal Reference` number (for traceability purposes), and assign this specific lot or
-serial number configuration to a specific website in the :guilabel:`Website` field (if working in a
-multi-website environment).
+2. Copy/paste lot numbers from an Excel file
 
-A detailed description of this specific lot or serial number can also be added in the
-:guilabel:`Description` tab below.
+First, you need to open the detailed operations of your picking.
 
-When all desired configurations are complete, click the :guilabel:`Save` button to save all changes.
+.. image:: lots/lots_04.png
+    :align: center
 
-.. image:: lots/lots-new-lot-number.png
-   :align: center
-   :alt: New lot number creation form with assigned product.
+Manually assign the different lot numbers
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-After a new lot number has been created, saved, and assigned to the desired product, navigate back
-to the product form in the :menuselection:`Inventory` app, by going to :menuselection:`Products -->
-Products`, and selecting the product to which this newly-created lot number was just assigned.
+When opening the detailed operations, you can click on *Add a line*.
+Then, you will be able to fill the lot number in. Once done, you can
+click on *Add a line* again to register a new lot number.
 
-On that product's detail form, click the :guilabel:`Lot/Serial Numbers` smart button to view the new
-lot number. When additional quantity of this product is received or manufactured, this new lot
-number can be selected and assigned to it.
+.. image:: lots/lots_05.png
+    :align: center
 
-Manage lots for shipping and receiving
-======================================
+Copy/paste lot number from an Excel file
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Lot numbers can be assigned for both **incoming** and **outgoing** goods. For incoming goods, lot
-numbers are assigned directly on the purchase order form. For outgoing goods, lot numbers are
-assigned directly on the sales order form.
+Once the spreadsheet containing the lot numbers you received from your
+supplier and copy the list. Then, you can paste them in the *Lot/Serial
+Number Name* column for Odoo to automatically create the necessary
+lines. After that, you will have to manually enter the number of
+products that are contained in each one of the lots.
 
-Manage lots on receipts
------------------------
+.. image:: lots/lots_06.png
+    :align: center
 
-Assigning lot numbers to **incoming** goods can be done directly from the purchase order (PO).
+.. image:: lots/lots_05.png
+    :align: center
 
-To create a :abbr:`PO (purchase order)`, go to :menuselection:`Purchase app --> Create`. Doing so
-reveals a new, blank request for quotation (RFQ) form.
+.. image:: lots/lots_07.png
+    :align: center
 
-On this :abbr:`RFQ (request for quotation)`, fill out the necessary information by adding a
-:guilabel:`Vendor`, and adding the desired products to the :guilabel:`Product` lines, by clicking
-:guilabel:`Add a product` (under the :guilabel:`Products` tab).
+Operation Types
+---------------
 
-Choose the desired quantity of the product to order by changing the number in the
-:guilabel:`Quantity` column.
+Of course, you also have the possibility to define how you will manage
+lots for each operation type. To do so, open the *Inventory* app and
+go to :menuselection:`Configuration --> Operation Types`.
 
-Once the :abbr:`RFQ (request for quotation)` has been filled out, click :guilabel:`Confirm Order`.
-When the :abbr:`RFQ (request for quotation)` is confirmed, it becomes a :guilabel:`Purchase Order`,
-and a :guilabel:`Receipt` smart button appears. Click the :guilabel:`Receipt` smart button to be
-taken to the warehouse receipt form.
+For each type (receipts, internal transfers, deliveries, …), you can
+decide if you allow to create new lot numbers or only use existing ones.
+By default, the creation of new lots is only allowed at product
+reception, and using existing lot numbers isn’t allowed in this
+operation. If you have inter-warehouse transfers and track products by
+lots, it can be useful to allow using existing lot numbers in receipts
+too.
 
-.. note::
-   Clicking :guilabel:`Validate` before assigning a lot number to the ordered product quantities
-   will result in a :guilabel:`User Error` pop-up. The pop-up requires entry of a lot or serial
-   number for the ordered products. The :abbr:`RFQ (request for quotation)` **cannot** be validated
-   without a lot number being assigned.
-
-.. image:: lots/lots-user-error-popup.png
-   :align: center
-   :alt: Add lot/serial number user error popup.
-
-From here, click the :guilabel:`Additional Options` menu, represented by a :guilabel:`hamburger
-(four horizontal lines)` icon, located to the right of the :guilabel:`Unit of Measure` column in the
-:guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up.
-
-In this pop-up, configure a number of different fields, including the assignation of a lot number,
-under the :guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-up.
-
-There are two ways to assign lot numbers: **manually** and **copy/paste**.
-
-- **Manually assign lot numbers**: Click :guilabel:`Add a line` and choose the location the products
-  will be stored in under the :guilabel:`To` column. Then, type a new :guilabel:`Lot Number Name`
-  and set the :guilabel:`Done` quantity.
-
-   .. image:: lots/lots-assign-lot-number-popup.png
-      :align: center
-      :alt: Assign lot number detailed operations popup.
-
-   .. note::
-      If quantities should be processed in multiple locations and lots, click :guilabel:`Add a line`
-      and type a new :guilabel:`Lot Number Name` for additional quantities. Repeat until the
-      :guilabel:`Quantity Done` matches the :guilabel:`Demand`.
-
-- **Copy/paste lot numbers from a spreadsheet**: Populate a spreadsheet with all of the lot numbers
-  received from the supplier (or manually chosen to assign upon receipt). Then, copy and paste them
-  in the :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create the necessary
-  number of lines based on the amount of numbers pasted in the column. From here, the :guilabel:`To`
-  locations and :guilabel:`Done` quantities can be manually entered in each of the lot number lines.
-
-   .. image:: lots/lots-excel-spreadsheet.png
-      :align: center
-      :alt: List of lot numbers copied on excel spreadsheet.
-
-Once all product quantities have been assigned a lot number, click :guilabel:`Confirm` to close the
-pop-up. Then, click :guilabel:`Validate`.
-
-A :guilabel:`Traceability` smart button appears upon validating the receipt. Click the
-:guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which
-includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the
-:guilabel:`Lot/Serial #` assigned, and more.
-
-Manage lots on delivery orders
-------------------------------
-
-Assigning lot numbers to **outgoing** goods can be done directly from the sales order (SO).
-
-To create an :abbr:`SO (sales order)`, go to the :menuselection:`Sales app --> Create`. Doing so
-reveals a new, blank quotation form.
-
-On this blank quotation form, fill out the necessary information by adding a :guilabel:`Customer`,
-and adding products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` tab) by
-clicking :guilabel:`Add a product`.
-
-Then, choose the desired quantity to sell by changing the number in the :guilabel:`Quantity` column.
-
-Once the quotation has been filled out, click the :guilabel:`Confirm` button to confirm the
-quotation. When the quotation is confirmed, it becomes an :abbr:`SO (sales order)`, and a
-:guilabel:`Delivery` smart button appears.
-
-Click the :guilabel:`Delivery` smart button to view the warehouse receipt form for that specific
-:abbr:`SO (sales order)`.
-
-From here, click the :guilabel:`Additional Options` menu, represented by a `hamburger` icon (four
-horizontal lines, located to the right of the :guilabel:`Unit of Measure` column in the
-:guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up.
-
-In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, with the full
-:guilabel:`Reserved` quantity taken from that specific lot (if there is enough stock in that
-particular lot).
-
-If there is insufficient stock in that lot, or if partial quantities of the :guilabel:`Demand`
-should be taken from multiple lots, change the quantity in the :guilabel:`Done` column to only
-include that specific part of the total quantity.
-
-.. note::
-   The lot automatically chosen for delivery orders varies, depending on the selected removal
-   strategy (:abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO
-   (First Expiry, First Out)`). It will also depend on the quantity ordered, and if there is enough
-   quantity in one lot to fulfill the order.
-
-.. seealso::
-   :doc:`/applications/inventory_and_mrp/inventory/routes/strategies/removal`
-
-Then, click :guilabel:`Add a line`, select an additional (different) :guilabel:`Lot/Serial Number`,
-apply the rest of the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the
-pop-up. Lastly, click the :guilabel:`Validate` button to deliver the products.
-
-.. image:: lots/lots-detailed-operations-popup.png
-   :align: center
-   :alt: Detailed operations popup for source lot number on sales order.
-
-Upon validating the delivery order, a :guilabel:`Traceability` smart button appears. Click the
-:guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which
-includes a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the
-:guilabel:`Date`, and the :guilabel:`Lot/Serial #` assigned.
-
-The :guilabel:`Traceability Report` can also include a :guilabel:`Reference` receipt from the
-previous purchase order, if the product quantities shared the same lot number.
-
-Manage lots for different operations types
-==========================================
-
-In Odoo, the creation of new lots is only allowed upon **receiving** products from a purchase order,
-by default. **Existing** lot numbers cannot be used.
-
-For sales orders, the opposite is true: new lot numbers cannot be created on the delivery order,
-only existing lot numbers can be used.
-
-To change the ability to use new (or existing) lot numbers on any operation type, go to the
-:menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired
-:guilabel:`Operation Type`.
-
-For :guilabel:`Receipts`, found on the :menuselection:`Operations Types` page, the :guilabel:`Use
-Existing Lots/Serial Numbers` option can be enabled, by clicking :guilabel:`Edit`, and then clicking
-the checkbox beside the :guilabel:`Use Existing Lots/Serial Numbers` option (in the
-:guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button to save the changes.
-
-For :guilabel:`Delivery Orders`, the :guilabel:`Create New Lots/Serial Numbers` option can be
-enabled, by clicking :guilabel:`Edit`, and clicking the checkbox beside the :guilabel:`Create New
-Lots/Serial Numbers` option. Be sure to click the :guilabel:`Save` button to save all changes.
-
-.. image:: lots/lots-operations-type-form.png
-   :align: center
-   :alt: Enabled traceability setting on operations type form.
-
-.. tip::
-   For inter-warehouse transfers involving products tracked by lots, it can be useful to enable the
-   :guilabel:`Use Existing Lots/Serial Numbers` option for warehouse receipts.
+.. image:: lots/lots_08.png
+    :align: center
 
 Lots traceability
 =================
 
-Manufacturers and companies can refer to traceability reports to see the entire lifecycle of a
-product: where (and when) it came from, where it was stored, and who (and when) it went to.
+The lot number given to the products allows you to keep track of where
+they were received, put in stock, to whom they were sold and where they
+were shipped to.
 
-To see the full traceability of a product, or group by lots, go to the :menuselection:`Inventory app
---> Products --> Lots/Serial Numbers`. Doing so reveals the :menuselection:`Lots/Serial Numbers`
-dashboard.
+To track an item, open the *Inventory* module and, in :menuselection:`Master Data -->
+Lots/Serial Numbers`, click on the lot number corresponding to your
+search.
 
-From here, products with lot numbers assigned to them will be listed by default, and can be expanded
-to show the lot numbers those products have assigned to them.
+.. image:: lots/lots_09.png
+    :align: center
 
-To group by lots (or serial numbers), begin by removing any filters in the search bar. Then, click
-the :guilabel:`Group By` drop-down, select :guilabel:`Add Custom Group`, and select
-:guilabel:`Lot/Serial Number` from the drop-down menu. Then, click :guilabel:`Apply`.
+When you open the *Traceability* information, you see in which
+documents the lot number has been used.
 
-Doing so displays all existing lots and serial numbers, and can be expanded to show all quantities
-of products with that assigned number.
+.. image:: lots/lots_10.png
+    :align: center
 
-.. image:: lots/lots-traceability-report.png
-   :align: center
-   :alt: Lots and serial numbers traceability report.
+Now, if you want to locate the lot number, you can do so by clicking on
+the *Location* stat button.
 
-.. seealso::
-   :doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences`
+.. image:: lots/lots_11.png
+    :align: center
+
+.. image:: lots/lots_12.png
+    :align: center

content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/serial_numbers.rst

@@ -1,317 +1,147 @@
-====================================
-Use serial numbers to track products
-====================================
+========================
+Work with serial numbers
+========================
 
-*Serial numbers* are one of the two ways to identify and track products in Odoo. A serial number is
-a unique identifier assigned incrementally (or sequentially) to an item or product, used to
-distinguish it from other items and products.
+To track products with serial numbers, you can use the serial number
+tracking. With them, you can track the current location of the product
+and, when the products are moved from one location to another, the
+system will automatically identify the current location of the product,
+based on its last movement.
 
-Serial numbers can consist of many different types of characters: they can be strictly numerical,
-they can contain letters and other typographical symbols, or they can be a mix of all of the above.
+If you want to do it or run very advanced traceability, the Odoo
+double-entry management is the feature you need.
 
-The goal of assigning serial numbers to individual products is to make sure that every item's
-history is identifiable when it travels through the supply chain. This can be especially useful for
-manufacturers that provide after-sales services to products that they sell and deliver.
+Configurations
+==============
 
-.. seealso::
-   :doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots`
+Application configuration
+-------------------------
 
-Enable lots & serial numbers
-============================
+First, you need to activate the serial numbers tracking. To do so, go to
+:menuselection:`Configuration --> Settings` in the *Inventory* application. Then,
+enable the feature and hit save.
 
-To track products using serial numbers, the :guilabel:`Lots & Serial Numbers` feature must be
-enabled. To enable this, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll
-down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial
-Numbers`. Remember to click the :guilabel:`Save` button to save changes.
+.. image:: serial_numbers/serial_numbers_01.png
+    :align: center
 
-.. image:: serial_numbers/serial-numbers-enabled-setting.png
-   :align: center
-   :alt: Enabled lots and serial numbers setting.
+Product configuration
+---------------------
 
-Configure serial number tracking on products
-============================================
+Now, you have to configure the products you want to track by serial
+numbers. To do so, go to :menuselection:`Master Data --> Products` and open the product
+of your choice. Edit it and select *Tracking By Unique Serial Number*
+in the *Inventory tab*. Then, click on save.
 
-Once the :guilabel:`Lots & Serial Numbers` setting has been activated, individual products can now
-be tracked using serial numbers. To configure this, go to :menuselection:`Inventory app --> Products
---> Products`, and choose a desired product to track.
+.. image:: serial_numbers/serial_numbers_02.png
+    :align: center
 
-Once on the product form, click :guilabel:`Edit`, and click the :guilabel:`Inventory` tab.
+.. image:: serial_numbers/serial_numbers_03.png
+    :align: center
 
-Once on the product form, click :guilabel:`Edit`, navigate to the :guilabel:`Inventory` tab, and
-scroll to the :guilabel:`Traceability` section. Then, select the :guilabel:`By Unique Serial Number`
-option, and click :guilabel:`Save` to save the changes. Existing or new serial numbers can now be
-selected and assigned to newly-received or manufactured batches of this product.
+Manage Serial Numbers
+=====================
 
-.. image:: serial_numbers/serial-numbers-product-tracking.png
-   :align: center
-   :alt: Enabled serial number tracking on product form.
+Receipts
+--------
 
-.. warning::
-   If a product doesn't have a serial number assigned to it, a user error pop-up window will appear.
-   The error message states that the product(s) in stock have no lot/serial number. However, a
-   lot/serial number can be assigned to the product by making an inventory adjustment.
+To receive a product that is tracked by serial number, you have to
+specify its serial number. Of course, you have several ways of doing so:
 
-Create new serial numbers for products already in stock
--------------------------------------------------------
+-  Manual assignation
 
-New serial numbers can be created for products already in stock with no assigned serial number. To
-do this, go to :menuselection:`Inventory --> Products --> Lots/Serial Numbers`, and click
-:guilabel:`Create`. Doing so reveals a blank lots/serial numbers form. On this form, a new
-:guilabel:`Lot/Serial Number` is generated automatically.
+-  Multi-assignation
+
+-  Copy/pasting from an Excel file
+
+Whatever could be your favorite way to assign serial numbers, you
+firstly need to open the detailed operations of your picking.
+
+.. image:: serial_numbers/serial_numbers_04.png
+    :align: center
+
+Manual assignation of the different serial numbers
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When opening the detailed operations, you can click on *Add a line*.
+Then, you will be able to fill in the serial number field. Once done,
+you can click again on *Add a line* to register a new serial number.
+
+.. image:: serial_numbers/serial_numbers_05.png
+    :align: center
+
+Multi-assignation
+~~~~~~~~~~~~~~~~~
+
+By using the multi-assignation of serial numbers, Odoo will
+automatically create the necessary lines. To do so, you have to enter
+the first serial number of your set and the number of products you have
+to assign a serial number to.
+
+Once done, click on *Assign Serial Numbers* and Odoo will do the rest.
+
+.. image:: serial_numbers/serial_numbers_06.png
+    :align: center
+
+.. image:: serial_numbers/serial_numbers_07.png
+    :align: center
+
+Copy/pasting from an Excel file
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To use copy/pasting, open the spreadsheet containing the serial numbers
+you received and copy the list. Then, past them in the *Lot/Serial
+Number Name* column of the wizard. Doing so, Odoo will automatically
+create the lines you need.
+
+.. image:: serial_numbers/serial_numbers_08.png
+    :align: center
+
+.. image:: serial_numbers/serial_numbers_09.png
+    :align: center
+
+.. image:: serial_numbers/serial_numbers_10.png
+    :align: center
+
+Operation types
+===============
+
+You also have the possibility to define how you will manage lots for
+each operation type. To define it, go to :menuselection:`Configuration --> Operation Types` in the
+*Inventory* app.
+
+For each type, you can decide if you allow the creation of new lot
+numbers or want to use existing ones. By default, the creation of new
+lots is only allowed at product reception.
+
+.. image:: serial_numbers/serial_numbers_11.png
+    :align: center
 
 .. tip::
-   While Odoo automatically generates a new lot/serial number to follow the most recent number, it
-   can be edited and changed to any desired number, by clicking the line under the
-   :guilabel:`Lot/Serial Number` field, and changing the generated number.
+      If you have inter-warehouse transfers and track products by lots, it can
+      be useful to allow using existing lot numbers in receipts too.
 
-Once the :guilabel:`Lot/Serial Number` is generated, click the blank field next to
-:guilabel:`Product` to reveal a drop-down menu. From this menu, select the product to which this new
-number will be assigned.
-
-This form also provides the option to adjust the :guilabel:`Quantity`, to assign a unique
-:guilabel:`Internal Reference` number (for traceability purposes), and to assign this specific
-lot/serial number configuration to a specific website in the :guilabel:`Website` field (if working
-in a multi-website environment).
-
-A detailed description of this specific lot/serial number can also be added in the
-:guilabel:`Description` tab below.
-
-When all desired configurations are complete, click the :guilabel:`Save` button to save all changes.
-
-.. image:: serial_numbers/serial-numbers-new-serial-number.png
-   :align: center
-   :alt: New serial number created for existing product stock.
-
-After a new serial number has been created, assigned to the desired product, and saved, navigate
-back to the product form, by going to :menuselection:`Products --> Products`, and selecting the
-product that this newly-created serial number was just assigned to.
-
-On that product's detail form, click the :guilabel:`Lot/Serial Numbers` smart button to view the new
-serial number.
-
-Manage serial numbers for shipping and receiving
-================================================
-
-Serial numbers can be assigned for both **incoming** and **outgoing** goods. For incoming goods,
-serial numbers are assigned directly on the purchase order form. For outgoing goods, serial numbers
-are assigned directly on the sales order form.
-
-Manage serial numbers on receipts
----------------------------------
-
-Assigning serial numbers to **incoming** goods can be done directly from the purchase order (PO).
-
-To create a :abbr:`PO (purchase order)`, go to the :menuselection:`Purchase app --> Create`. Doing
-so reveals a new, blank request for quotation (RFQ) form.
-
-On this :abbr:`RFQ (request for quotation)` form, fill out the necessary information, by adding a
-:guilabel:`Vendor`, and by adding the desired products to the :guilabel:`Product` lines, by clicking
-:guilabel:`Add a product`, under the :guilabel:`Products` tab.
-
-Choose the desired quantity of the product to order, by changing the number in the
-:guilabel:`Quantity` column.
-
-When the necessary configurations are complete, click :guilabel:`Confirm Order`. This will convert
-the :abbr:`RFQ (request for quotation)` to a purchase order.
-
-Then, click the :guilabel:`Receipt` smart button to be taken to the warehouse receipt form page for
-that specific :abbr:`PO (purchase order)`.
-
-.. warning::
-   Clicking :guilabel:`Validate` before assigning a serial number to the ordered product quantities
-   will cause a :guilabel:`User Error` pop-up to appear. The pop-up requires entry of a lot or
-   serial number for the ordered products. The :abbr:`RFQ (request for quotation)` **cannot** be
-   validated without a serial number being assigned.
-
-.. image:: serial_numbers/serial-numbers-user-error-popup.png
-   :align: center
-   :alt: User error popup prompting serial number entry.
-
-From here, click the :guilabel:`Additional Options` menu, represented by a `hamburger` icon (four
-horizontal lines, located to the right of the :guilabel:`Unit of Measure` column in the
-:guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up.
-
-In this pop-up, configure a number of different fields, including the assignation of a serial number
-(or serial numbers) under the :guilabel:`Lot/Serial Number Name` column, located at the bottom of
-the pop-up.
-
-There are three ways to do this: manually assigning serial numbers, automatically assigning serial
-numbers, and copy/pasting serial numbers from a spreadsheet.
-
-Assign serial numbers manually
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To assign serial numbers manually, click :guilabel:`Add a line` from the :guilabel:`Detailed
-Operations` pop-up, and first choose the location where the product will be stored under the
-:guilabel:`To` column.
-
-Then, type a new :guilabel:`Serial Number Name`, and set the :guilabel:`Done` quantity in the
-appropriate columns.
-
-Repeat this process for the quantity of products shown in the :guilabel:`Demand` field, and until
-the :guilabel:`Quantity Done` field displays the correct (matching) number of products processed.
-
-Assign serial numbers automatically
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-If a large quantity of products need individual serial numbers assigned to them, Odoo can
-automatically generate and assign serial numbers to each of the individual products.
-
-To accomplish this, start with the :guilabel:`First SN` field in the :guilabel:`Detailed Operations`
-pop-up window, and type the first serial number in the desired order to be assigned.
-
-Then, in the :guilabel:`Number of SN` field, type the total number of items that need
-newly-generated unique serial numbers assigned to them.
-
-Finally, click :guilabel:`Assign Serial Numbers`, and a list will populate with new serial numbers
-matching the ordered quantity of products.
-
-.. image:: serial_numbers/serial-numbers-auto-assign-sn.png
-   :align: center
-   :alt: Automatic serial number assignment in detailed operations popup.
-
-Copy/paste serial numbers from a spreadsheet
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To copy and paste serial numbers from an existing spreadsheet, first populate a spreadsheet with all
-of the serial numbers received from the supplier (or manually chosen upon receipt). Then, copy and
-paste them in the :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create the
-necessary number of lines based on the amount of numbers pasted in the column.
-
-From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can be manually entered in
-each of the serial number lines.
-
-.. image:: serial_numbers/serial-numbers-excel-spreadsheet.png
-   :align: center
-   :alt: List of serial numbers copied in Excel spreadsheet.
-
-.. tip::
-   For purchase orders that include large quantities of products to receive, the best method of
-   serial number assignment is to automatically assign serial numbers using the :guilabel:`Assign
-   Serial Numbers` button located on the :abbr:`PO (purchase order)`. This prevents any serial
-   numbers from being reused or duplicated, and improves traceability reporting.
-
-Once all product quantities have been assigned a serial number, click the :guilabel:`Confirm` button
-to close the pop-up. Then, click :guilabel:`Validate`.
-
-A :guilabel:`Traceability` smart button appears upon validating the receipt. Click the
-:guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which
-includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the
-:guilabel:`Lot/Serial #`, and more.
-
-Once all product quantities have been assigned a serial number, click :guilabel:`Confirm` to close
-the popup, and click :guilabel:`Validate`. A :guilabel:`Traceability` smart button will appear upon
-validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated
-:guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the
-:guilabel:`Product` being traced, the :guilabel:`Lot/Serial #`, and more.
-
-Manage serial numbers on delivery orders
-----------------------------------------
-
-Assigning serial numbers to **outgoing** goods can be done directly from the sales order (SO).
-
-To create an :abbr:`SO (sales order)`, navigate to the :menuselection:`Sales` app, and click the
-:guilabel:`Create` button. Doing so reveals a new, blank quotation form. On this blank quotation
-form, fill out the necessary information, by adding a :guilabel:`Customer`, and adding products to
-the :guilabel:`Product` lines (in the :guilabel:`Order Lines` tab), by clicking :guilabel:`Add a
-product`.
-
-Then, choose the desired quantity to sell by changing the number in the :guilabel:`Quantity` column.
-
-Once the quotation has been filled out, click the :guilabel:`Confirm` button to confirm the
-quotation. When the quotation is confirmed, the quotation becomes an :abbr:`SO (sales order)`, and a
-:guilabel:`Delivery` smart button appears.
-
-Click the :guilabel:`Delivery` smart button to view the warehouse receipt form for that specific
-:abbr:`SO (sales order)`.
-
-From here, click the :guilabel:`Additional Options` menu, represented by a `hamburger` icon (four
-horizontal lines, located to the right of the :guilabel:`Unit of Measure` column in the
-:guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up.
-
-In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, with each product of the
-total :guilabel:`Reserved` quantity listed with their unique serial numbers (most likely listed in
-sequential order).
-
-To manually change a product's serial number, click the drop-down menu under :guilabel:`Lot/Serial
-Number`, and choose (or type) the desired serial number. Then, mark the :guilabel:`Done` quantities,
-and click :guilabel:`Confirm` to close the pop-up.
-
-Finally, click the :guilabel:`Validate` button to deliver the products.
-
-.. image:: serial_numbers/serial-numbers-detailed-operations-popup.png
-   :align: center
-   :alt: Serial numbers listed in detailed operations popup.
-
-Upon validating the delivery order, a :guilabel:`Traceability` smart button appears. Click the
-:guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which
-includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the
-:guilabel:`Date`, and the :guilabel:`Lot/Serial #` assigned.
-
-The :guilabel:`Traceability Report` can also include a :guilabel:`Reference` receipt from the
-previous purchase order (PO), if any of the product quantities shared a serial number assigned
-during receipt of that specific :abbr:`PO (purchase order)`.
-
-Manage serial numbers for different operations types
-====================================================
-
-By default in Odoo, the creation of new serial numbers is only allowed upon **receiving** products
-from a purchase order. **Existing** serial numbers cannot be used. For sales orders, the opposite is
-true: new serial numbers cannot be created on the delivery order, only existing serial numbers can
-be used.
-
-To change the ability to use new (or existing) serial numbers on any operation type, go to
-:menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired
-:guilabel:`Operation Type`.
-
-For the :guilabel:`Receipts` operation type, found on the :guilabel:`Operations Types` page, the
-:guilabel:`Use Existing Lots/Serial Numbers` option can be enabled, by selecting
-:guilabel:`Receipts` from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and then
-clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial Numbers` option (in the
-:guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button to save the changes.
-
-For the :guilabel:`Delivery Orders` operation type, located on the :guilabel:`Operations Types`
-page, the :guilabel:`Create New Lots/Serial Numbers` option can be enabled, by selecting
-:guilabel:`Delivery Orders` from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`,
-and clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option (in the
-:guilabel:`Traceability` section). Be sure to click :guilabel:`Save` to save changes.
-
-.. image:: serial_numbers/serial-numbers-operations-types.png
-   :align: center
-   :alt: Enabled traceability setting in operations type form.
-
-Serial number traceability
+Serial Number traceability
 ==========================
 
-Manufacturers and companies can refer to the traceability reports to see the entire lifecycle of a
-product: where it came from (and when), where it was stored, and who it went to.
+Using serial numbers allows you to keep track of where the products were
+received, put in stock, to whom they were sold, and where they were
+shipped to.
 
-To see the full traceability of a product, or group by serial numbers, go to
-:menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the
-:guilabel:`Lots/Serial Numbers` dashboard.
+Tracking an item is easy: open the *Inventory* app, and go to :menuselection:`Master Data -->
+Lots/Serial Numbers` and click on the serial number corresponding to your search. Then, open the
+*Traceability* information. There, you will see in which documents the serial number has been used.
 
-From here, products with serial numbers assigned to them will be listed by default, and can be
-expanded to show what serial numbers have been specifically assigned to them.
+.. image:: serial_numbers/serial_numbers_12.png
+    :align: center
 
-To group by serial numbers (or lots), first remove any default filters from the search bar in the
-upper-right corner. Then, click :guilabel:`Group By`, and select :guilabel:`Add Custom Group`, which
-reveals a mini drop-down menu. From this mini drop-down menu, select :guilabel:`Lot/Serial Number`,
-and click :guilabel:`Apply`.
+.. image:: serial_numbers/serial_numbers_13.png
+    :align: center
 
-Doing so reveals all existing serial numbers and lots, and can be expanded to show all quantities of
-products with that assigned number. For unique serial numbers that are not reused, there should be
-just one product per serial number.
+And, if you want to locate a serial number, you can do so by clicking on
+the *Location* button available on the serial number form.
 
-.. image:: serial_numbers/serial-numbers-reporting-page.png
-   :align: center
-   :alt: Serial numbers reporting page with drop-down lists.
+.. image:: serial_numbers/serial_numbers_14.png
+    :align: center
 
-.. tip::
-   For additional information regarding an individual serial number (or lot number), click the line
-   item for the serial number to reveal that specific serial number's :guilabel:`Serial Number`
-   form. From this form, click the :guilabel:`Location` and :guilabel:`Traceability` smart buttons
-   to see all stock on-hand using that serial number, and any operations made using that serial
-   number.
-
-.. seealso::
-   :doc:`/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/differences`
+.. image:: serial_numbers/serial_numbers_15.png
+    :align: center

content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst

@@ -90,17 +90,11 @@ menu (e.g. :guilabel:`Standard`, :guilabel:`Average Cost (AVCO)`, or :guilabel:`
    </applications/inventory_and_mrp/inventory/management/reporting/using_inventory_valuation>`
 
 .. note::
-   When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, changing the
-   numerical value in the :guilabel:`Cost` field for products in the respective product category
-   creates a new record in the *Inventory Valuation* report to adjust the value of the product. The
-   :guilabel:`Cost` amount will then automatically update based on the average purchase price both
-   of inventory on hand and the costs accumulated from validated purchase orders.
-
-When the :guilabel:`Costing Method` is changed, products already in stock that were using the
-:guilabel:`Standard` costing method **do not** change value; rather, the existing units keep their
-value, and any product moves from then on affect the average cost, and the cost of the product will
-change. If the value in the :guilabel:`Cost` field on a product form is changed manually, Odoo will
-generate a corresponding record in the *Inventory Valuation* report.
+   When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, the numerical
+   value in the :guilabel:`Cost` field for products in the respective product category will no
+   longer be editable, and will appear grayed out. The :guilabel:`Cost` amount will instead
+   automatically update based on the average purchase price both of inventory on hand and the costs
+   accumulated from validated purchase orders.
 
 On the same screen, the :guilabel:`Account Stock Properties` fields will appear, as they are now
 required fields given the change to automated inventory valuation. These accounts are defined as

content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst

@@ -6,8 +6,6 @@ In Odoo, a **Warehouse** is the actual building/place in which your items
 are stocked. You can setup multiple warehouses and create moves between
 warehouses.
 
-.. _inventory/warehouses/location-definition:
-
 A **Location**, is a specific space within your warehouse. It can be
 considered as a sublocation of your warehouse, as a shelf, a floor, an
 aisle, etc. Therefore, a location is part of one warehouse only and it

content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst

@@ -75,8 +75,6 @@ Area* is created.
    While working, the operator process these transfers in the opposite order: first the picking,
    then the packing, then the delivery order.
 
-.. _inventory/routes/concepts/use-routes/push:
-
 Push Rules
 ----------
 

content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst

@@ -1,248 +1,54 @@
-=============
-Putaway rules
+=======================
+What is a Putaway Rule?
+=======================
+
+A good warehouse implementation takes care that products automatically move to their appropriate
+destination location. To make that process easier, Odoo uses *Putaway rules*. But what is a putaway
+rule? Putaway is the process of taking products off the receiving shipments and directly putting
+them into the most appropriate location.
+
+If, for example, a warehouse contains volatile substances, it is important to make sure that certain
+products are not stored close to each other because of a potential chemical reaction. That’s where
+putaway rules intervene, to avoid storing products wrongly.
+
+Configuration
 =============
 
-Putaway is the process of routing products to appropriate storage locations upon shipment arrival.
-Odoo can accomplish this seamlessly using *putaway rules*, which dictate how products move through
-specified warehouse locations.
+In the *Inventory* app, go to :menuselection:`Configuration --> Settings` and activate the
+*Multi-Step Routes*. By doing so, the *Storage Locations* will be automatically activated.
 
-Upon shipment arrival, operations are generated based on putaway rules to efficiently move products
-to specified locations and ensure easy retrieval. Putaway rules can also prevent volatile substances
-from being stored in close proximity by directing them to different locations determined by the
-warehouse manager.
-
-.. seealso::
-   - :ref:`How push rules work <inventory/routes/concepts/use-routes/push>`
-   - :ref:`Warehouse locations <inventory/warehouses/location-definition>`
-
-Enable putaway rules
-====================
-
-Begin by navigating to :menuselection:`Inventory app --> Configuration --> Settings`, then activate
-the :guilabel:`Multi-Step Routes` checkbox under the :guilabel:`Warehouse` heading. By doing so, the
-:guilabel:`Storage Locations` setting is automatically enabled as well. Finally, click
-:guilabel:`Save`.
-
-.. image:: putaway/multi-step-routes.png
+.. image:: putaway/putaw1.png
    :align: center
-   :alt: In configs, for the Inventory app, check multi-step routes box to enable Putaway rules.
 
-Put away products
-=================
+Setting up a Putaway Rule
+=========================
 
-Putaway rules are commonly used to move products to specific locations for easy retrieval. Thus,
-products are grouped in the same *product category* when a single putaway rule captures the group's
-storage needs.
+In some cases, like for a retail shop storing vegetables and fruits, we have to store products in
+different locations to maintain product quality.
 
-To manage where specific products are routed for storage, navigate to :menuselection:`Inventory app
---> Configuration --> Putaway Rules`. Use the :guilabel:`Create` button to configure a new putaway
-rule on a :guilabel:`Product` or :guilabel:`Product Category` that the rule affects.
+Let’s suppose there are one warehouse location *WH/Stock* and two sub-locations
+*WH/Stock/Vegetables* and *WH/Stock/Fruits*.
 
-In the same line, the :guilabel:`When product arrives in` location is where the putaway rule is
-triggered to create an operation to move the product to the :guilabel:`Store to` location. The
-:guilabel:`Store to` location must be a sublocation of the first (e.g. `WH/Stock/Fruits` is a
-specific, named location inside `WH/Stock` to make the products stored here easier to find).
-
-.. example::
-   Ensure all apples are stored in the fruits section by filling the field :guilabel:`Store to` with
-   the location `WH/Stock/Fruits` when the :guilabel:`Product`, `Apple` arrives in `WH/Stock`.
-   Repeat this for all products and hit :guilabel:`Save`.
-
-   .. image:: putaway/create-putaway-rules.png
-      :align: center
-      :alt: Create putaway rules for apples and carrots.
+To manage those locations, we will create putaway rules. To do so, open the *Inventory* app and go
+to :menuselection:`Configuration --> Putaway Rules`. Then, click on create and configure your first
+rule indicating the main location the product will enter before being redirected to the right
+location.
 
 .. note::
-   It is also possible to create and manage putaway rules for a single product by going to the
-   product page and clicking the :guilabel:`Putaway Rules` smart button at the top of the page. If
-   the button is not visible at first glance, select the :guilabel:`More` button at the top right to
-   view additional smart buttons.
+   The putaway rules can be defined either per product or per product category.
 
-.. _inventory/routes/strategies/putaway/internal-stock-moves:
-
-.. tip::
-   Check whether putaway rules work as intended using the summary of internal product movements. In
-   the :menuselection:`Inventory` app, select :menuselection:`Reporting --> Product Moves` and
-   enable the :guilabel:`Internal` search filter on the :guilabel:`Filters` drop-down menu under the
-   search bar at the top of the page. In this view, confirm that products are moved to the
-   :guilabel:`Store to` location detailed in the putaway rule. More details in :ref:`this section
-   <inventory/routes/strategies/putaway/wrong-location>`.
-
-Use putaway rules
------------------
-
-Once a putaway rule is configured, the product it specifies is automatically routed to the
-:guilabel:`Store to` location upon arriving in the :guilabel:`When product arrives in` location.
-
-For example, on a putaway rule with the :guilabel:`When product arrives in` location set to
-`WH/Stock`, internal stock moves are automatically created when products first enter the warehouse.
-To trigger this putaway rule, begin by creating a :ref:`purchase order
-<inventory/purchase/manage_deals/manage>` (PO) to bring products into the warehouse.
-
-To create a :guilabel:`Request for Quotation` (RFQ), go to the :menuselection:`Purchase` app, and
-click :guilabel:`Create`. Then, add products to the :abbr:`RFQ (Request for Quotation)` by clicking
-:guilabel:`Add a line`, and selecting the desired product(s) from the drop-down menu in the
-:guilabel:`Product` column.
-
-Once ready, click :guilabel:`Confirm`. Doing so turns the :abbr:`RFQ (Request for Quotation)` into a
-:abbr:`PO (Purchase Order)`. Next, click :guilabel:`Send by Email` to send the :abbr:`PO (Purchase
-Order)` to the vendor, if needed.
-
-.. image:: putaway/purchase-apples-and-carrots.png
+.. image:: putaway/putaw2.png
    :align: center
-   :alt: View purchase order for apples and carrots.
 
-Begin receiving the incoming shipment by selecting the :guilabel:`Receipt` smart button on the
-:abbr:`PO (Purchase Order)`. Click :guilabel:`Receive products` and then :guilabel:`Validate` to
-move products into the warehouse. Since the putaway rule is set to trigger when products arrive in
-stock, internal transfers are automatically created when products arrive in the
-:guilabel:`Destination Location`, `WH/Stock`. This ensures products entering the warehouse are
-stored in specific locations suitable for their storage needs.
+Now, if I purchase apples and carrots to my supplier, they will be grouped in the same receipt but
+redirected to the right location automatically, thanks to putaway rules. This information is
+available from *Inventory Report*, under the reporting menu.
 
-.. image:: putaway/receive-incoming-stock.png
+.. image:: putaway/putaw3.png
    :align: center
-   :alt: In the WH reception operation, receive package of apples and carrots.
 
-Verify stock moves
-==================
-
-Confirm whether the putaway rule worked as intended and that the products have been moved to the
-correct location using the :guilabel:`Stock On Hand` dashboard. View all products in stock in
-:menuselection:`Inventory app --> Reporting --> Inventory Report`. By default, the products are
-grouped by location.
-
-Select a product's collapsable drop-down menu, which displays the current location(s) of the
-product. Then, select a :guilabel:`Location` drop-down menu to view a list of all stock movements in
-and out of each location. Each of these lines are records of a stock move, called a *stock move
-line*.
-
-.. image:: putaway/destination-locations.png
+.. image:: putaway/putaw4.png
    :align: center
-   :alt: Verify stock moves triggered by putaway rule in the Inventory Report.
 
-.. _inventory/routes/strategies/putaway/wrong-location:
-
-Trace products in wrong locations
----------------------------------
-
-To trace products and associated documents for warehouse operations, use the :guilabel:`Product
-Moves` report in :menuselection:`Inventory app --> Reporting --> Product Moves`. View a product's
-warehouse operation history by selecting a product's drop-down menu. Each stock move line contains
-details about any movement of stock, such as manufacturing orders, inventory adjustments, or
-internal transfers. Click on a stock move line to view all the information in a comprehensive
-report.
-
-The stock move line is useful because the :guilabel:`Reference` displays the warehouse operation
-associated to the :guilabel:`Product`. Use the :guilabel:`From` and :guilabel:`To` location and
-associated :guilabel:`Source` documents to trace the product path and identify the type of
-operation.
-
-.. tip::
-   It is also possible to view the stock moves of a product directly from the product page. Open the
-   desired product page by navigating to :menuselection:`Inventory --> Products --> Products` and
-   select the product. From there, click on the :guilabel:`Product Moves` smart button, then click
-   the product's collapsable drop-down menu from the list. This displays the stock moves history of
-   the product.
-
-.. _inventory/strategies/putaway/stock-moves:
-
-.. example::
-   A putaway rule was purposely set up incorrectly on `Apple`, so the product was moved from
-   `WH/Stock` to `WH/Stock/Shelf 1` instead of the expected location, `WH/Stock/Fruits`. To trace
-   the path the apple moved and identify the cause of the wrong stock move, open the
-   :guilabel:`Product Moves` report in :menuselection:`Inventory app --> Reporting --> Product
-   Moves`. The apple's drop-down menu, when opened, displays a list of stock moves of the apple.
-   line to open a report that is useful to trace the path the product moved and identify the cause
-   of the wrong stock move.
-
-   The :guilabel:`To` field displays where the product currently is, `WH/Stock/Shelf 1`, which is
-   the wrong location. The :guilabel:`From` location is the vendor's location, which is expected
-   since the :guilabel:`Source` of the stock move is a :abbr:`PO (Purchase Order)`.
-
-   The :guilabel:`Reference` operation, `WH/IN/00015`, which is a warehouse reception of products
-   from the vendor, would further explain why the apples were moved to the wrong location.
-
-   .. image:: putaway/stock-move-report.png
-      :align: center
-      :alt: Open stock move report
-
-To follow an operation identified from the :guilabel:`Product Moves` report, navigate to
-:menuselection:`Inventory --> Operations --> Transfers`. This is the page that displays all
-warehouse transfers— internal or external. Search for and click on the corresponding
-:guilabel:`Reference` operation to view the document explaining why the product was moved to the
-wrong location.
-
-.. tip::
-   When there are too many records, use either the :guilabel:`Filters` or :guilabel:`Group by`
-   features to sort and :ref:`find desired records
-   <inventory/routes/strategies/putaway/use-advanced-filters>`. It is useful to search exclusively
-   for the receipt operation type because putaway rules store products *into* a specific stock
-   location.
-
-.. example::
-   Continuing to diagnose why the product, `Apple`, was placed in `WH/Stock/Shelf 1`, navigate to
-   the list of all transfers in :menuselection:`Inventory --> Operations --> Transfers`. Click on
-   the list item where the :guilabel:`Reference` field matches the `WH/IN/00015` operation
-   identified in the :ref:`previous example <inventory/strategies/putaway/stock-moves>` to open the
-   receipt.
-
-   .. image:: putaway/transfers.png
-      :align: center
-      :alt: In the Transfers page in the Inventory app, select the desired transfer to view the
-            record.
-
-   This receipt describes which products were received from the supplier, with the affiliated
-   :abbr:`PO (Purchase Order)` linked in the :guilabel:`Source Document` field. On the warehouse
-   reception document, the field :guilabel:`Destination Location` shows where the product is
-   received upon entering the warehouse.
-
-   Clicking on the :guilabel:`≣ (Detailed Operations)` icon to the right of the product line opens a
-   window that shows the product was moved to the wrong location. Based on this information it can
-   be gathered that the putaway rule was triggered but the location was set incorrectly. Rectify
-   this in :menuselection:`Inventory --> Configuration --> Putaway Rules`.
-
-   .. image:: putaway/detailed-operations.png
-      :align: center
-      :alt: Click Detailed Operations button on the right of warehouse transfers page to the right
-            of the WH reception document.
-
-   .. image:: putaway/automated.png
-      :align: center
-      :alt: Show putaway rule in detailed operations popup.
-
-.. _inventory/routes/strategies/putaway/use-advanced-filters:
-
-Advanced filter search
-----------------------
-
-Keep track of and trace products on the :guilabel:`Product Moves` report by navigating to
-:menuselection:`Inventory app --> Reporting --> Product Moves` and use the :guilabel:`Filters` and
-:guilabel:`Group by` features to stay updated on warehouse operations.
-
-Transfers based on putaway rules can be found by toggling on the :guilabel:`Internal` filter as
-mentioned in this :ref:`tip <inventory/routes/strategies/putaway/internal-stock-moves>` previously.
-Other useful filters and groupbys intended for reporting on the company's internal operations
-include:
-
-#. Filter by :guilabel:`Incoming` and :guilabel:`To Do` to display shipments from vendors yet to be
-   processed.
-
-   .. image:: putaway/product-moves-to-do.png
-      :align: center
-      :alt: Filter warehouse transfer records by Incoming shipments and processes ToDo.
-
-#. Use custom filters to search for a specific product by its name, :ref:`lot/serial number
-   <inventory/management/lots-serial-numbers>` or barcode. Create a custom filter by clicking on
-   :guilabel:`Filters`. Click :guilabel:`Add Custom Filter`, fill in the identifying information,
-   and click :guilabel:`Apply`. Now that the custom filter is active, click on the
-   :guilabel:`Filters` button again to create any additional filters.
-#. Group by :guilabel:`Date`: View all product moves on a specific date.
-#. Group by :guilabel:`From`: Create a custom filter that displays all locations that currently
-   store at least 1 product. This is useful to view all the locations and sublocations to optimize
-   storage space.
-#. :guilabel:`Favorite` the current search with filters applied. This feature is useful to apply the
-   filters promptly, especially if this search is often used.
-
-   .. image:: putaway/save-favorites.png
-      :align: center
-      :alt: Use the star button under the search bar to save current search as a favorite view.
+.. image:: putaway/putaw5.png
+   :align: center

content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst

@@ -1,134 +1,94 @@
-================================
-Create a bill of materials (BoM)
-================================
+=========================
+Create Bills of Materials
+=========================
 
-A *bill of materials* (or *BoM*) is a document that defines the quantity of each component required
-to manufacture (or deliver) a finished product. It can also include various operations types, steps,
-and instructions for the individual guidelines needed to complete a production process.
+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.
 
-In Odoo *Manufacturing*, multiple :abbr:`BoMs (Bills of Materials)` can be linked to a product, so
-even product variants can have their own specific :abbr:`BoMs (Bills of Materials)`.
+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.
 
-Correctly setting up a :abbr:`BoM (Bill of Materials)` helps optimize the manufacturing process, and
-saves time.
+This feature will help optimize your manufacturing process while saving
+you time.
 
-Set up a BoM
-============
+Setting up a BoM
+================
 
-:abbr:`BoMs (Bills of Materials)` can be set up with or without operations steps or instructions,
-and can include as many or as few components as needed. The simplest setup is one without operations
-or instructions. In that case, the production is solely managed with *manufacturing orders* (MOs).
+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.
 
-To create a :abbr:`BoM (Bill of Materials)`, navigate to :menuselection:`Manufacturing app -->
-Products --> Bills of Materials`, and click :guilabel:`Create`. Then, in the :guilabel:`Product`
-field, choose the product that will be associated with the :abbr:`BoM (Bill of Materials)`.
+Before creating your *BoM*, you have to create the product using the
+*BoM* and, at least, one of the components. Go to the :menuselection:`Master Data menu --> Products`
+and create both the finished product and the component.
 
-.. image:: bill_configuration/bill-configuration-bom-creation.png
-   :align: center
-   :alt: Bill of materials creation screen.
+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*.
 
-There are three :guilabel:`BoM Types` that can be chosen for any bill of materials:
+.. image:: bill_configuration/bills_of_materials_01.png
+    :align: center
 
-#. :guilabel:`Manufacture this product` indicates that this product is manufactured in-house, from
-   start to finish using the components listed on the :abbr:`BoM (Bill of Materials)`.
-#. :guilabel:`Kits` are sets of unassembled components that may be sold as products, and are useful
-   for managing more complex :abbr:`BoMs (Bills of Materials)`.
-#. :guilabel:`Subcontracting` outsources the production of some (or all) components or products to
-   outside manufacturers. This feature needs to be enabled in :menuselection:`Manufacturing app -->
-   Configuration --> Settings`, under the :guilabel:`Operations` section.
+.. warning::
+   The destination location should **not** be a scrap location. A scrap location is where you put
+   products that you don't need.
+
+Using the same BoM to describe Variants
+---------------------------------------
+
+As said above, you can use *BoM* for *Product Variants*. It is
+basically the same as for the standard product.
+
+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.
+
+.. image:: bill_configuration/bills_of_materials_02.png
+    :align: center
+
+Adding a routing
+================
+
+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.
+
+.. image:: bill_configuration/bills_of_materials_03.png
+    :align: center
 
 .. note::
-   A :abbr:`BoM (Bill of Materials)` can also be created directly from the :abbr:`BoM (Bill of
-   Materials)` smart button on the product template, in which case the :guilabel:`Product` field is
-   pre-filled.
+         Each *BoM* can have only one routing while each routing can be used
+         multiple times.
 
-The most common :guilabel:`BoM Type` is :guilabel:`Manufacture this product`. Once the
-:guilabel:`BoM Type` is chosen, click :guilabel:`Add a Line` to add all the :guilabel:`Components`
-that go into the production of the final product, as well as the :guilabel:`Quantity` of each
-component. Finally, click :guilabel:`Save` to finish creating the :abbr:`BoM (Bill of Materials)`.
+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.
 
-.. tip::
-   New components can be added, even during production, directly from the :abbr:`BoM (Bill of
-   Materials)`. After selecting :guilabel:`Add a line`, create the new component and select
-   :guilabel:`Create` or :guilabel:`Create and Edit`. Components can also be created by going to
-   :menuselection:`Manufacturing app --> Products --> Products`, and clicking :guilabel:`Create`.
+.. image:: bill_configuration/bills_of_materials_04.png
+    :align: center
 
-Specify a BoM for a product variant
------------------------------------
+Adding By-Products
+==================
 
-.. important::
-   To assign *product variants* to :abbr:`BoMs (Bills of Materials)`, the feature must be enabled in
-   :menuselection:`Inventory --> Configuration --> Settings`, under the :guilabel:`Products` section
-   by selecting :guilabel:`Variants` and clicking :guilabel:`Save`.
+In Odoo, a *by-product* is any product produced by a *BoM* in
+addition to the primary product.
 
-:abbr:`BoMs (Bills of Materials)` can also be assigned to specific *product variants*, with two
-setup options available to choose from.
+To add *by-products* to a *BoM*, you will first need to enable them
+from the *Manufacturing* app settings.
 
-.. image:: bill_configuration/bill-configuration-product-variants.png
-   :align: center
-   :alt: Bill of materials product variants and apply on variants options.
+.. image:: bill_configuration/bills_of_materials_05.png
+    :align: center
 
-The first method is to create one :abbr:`BoM (Bill of Materials)` per product variant, by specifying
-the :guilabel:`Product Variant` every time a new :abbr:`BoM (Bill of Materials)` is created.
+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.
 
-The second method is to create **one** master :abbr:`BoM (Bill of Materials)` that contains all
-components, and specify which variant each component applies to in the :guilabel:`Apply on Variants`
-column.
-
-.. seealso::
-   `Managing with Product Variants
-   <https://www.odoo.com/slides/slide/manufacturing-with-product-variants-2805>`_
-
-.. note::
-   The :guilabel:`Apply on Variants` column is hidden by default and can be accessed by clicking on
-   the :guilabel:`Additional Options` menu icon at the right of the :guilabel:`Components` tab.
-
-Set up operations steps
-=======================
-
-Some :abbr:`BoMs (Bills of Materials)` require multiple operations and steps during the
-manufacturing process. To create :guilabel:`Operations` on a :abbr:`BoM (Bill of Materials)`, first
-enable the :guilabel:`Work Orders` feature in :menuselection:`Manufacturing app --> Configuration
---> Settings --> Operations`.
-
-.. image:: bill_configuration/bill-configuration-create-operation.png
-   :align: center
-   :alt: An example of a Bill of Materials operation and the steps creation tab.
-
-When creating a new :abbr:`BoM (Bill of Materials)`, click the :guilabel:`Operations` tab and click
-:guilabel:`Add a line` to add a new operation.
-
-In the :guilabel:`Create Operations` box, give the operation a name, and specify the :guilabel:`Work
-Center` and the :guilabel:`Default Duration` settings. Under the :guilabel:`Work Sheet` tab, the
-type of :guilabel:`Work Sheet` can also be chosen, if assembly instructions need to be attached.
-
-The :guilabel:`Work Sheet` types that can be added are: :guilabel:`Text` (with a
-:guilabel:`Description`); :guilabel:`PDF` files; and :guilabel:`Google Slide` presentations. When
-all the information has been filled out, select :guilabel:`Save & Close`.
-
-.. image:: bill_configuration/bill-configuration-operations-popup.png
-   :align: center
-   :alt: Bill of materials create operations popup on operations tab.
-
-Add by-products to a BoM
-========================
-
-A *by-product* is a residual product that is created during production of a :abbr:`BoM (bill of
-materials)`. Unlike the finished product, there can be more than one by-product on a :abbr:`BoM
-(Bill of Materials)`.
-
-To add by-products to a :abbr:`BoM (Bill of Materials)`, first enable the :guilabel:`By-Products`
-feature in :menuselection:`Manufacturing app --> Configuration --> Settings --> Operations`.
-
-Once the feature is enabled, by-products can be added to a :abbr:`BoM (Bill of Materials)` from the
-:guilabel:`By-products` tab by clicking :guilabel:`Add a line`. The by-product can be named, its
-:guilabel:`Quantity` specified, and a :guilabel:`Unit of Measure` chosen.
-
-If the :abbr:`BoM (Bill of Materials)` has :guilabel:`Operations` steps, specify exactly which
-operation the by-product is produced from in the :guilabel:`Produced in Operation` field. Finally,
-click :guilabel:`Save` to save changes.
-
-.. seealso::
-   - :doc:`/applications/inventory_and_mrp/manufacturing/management/kit_shipping`
-   - :doc:`/applications/inventory_and_mrp/manufacturing/management/product_variants`
-   - :doc:`/applications/inventory_and_mrp/manufacturing/management/routing_kit_bom`
+.. image:: bill_configuration/bills_of_materials_06.png
+    :align: center

content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst

@@ -2,8 +2,6 @@
 Manage vendor bills
 ===================
 
-.. _inventory/purchase/manage_deals/manage:
-
 The **Purchase** application allows you to manage your purchase orders,
 incoming products, and vendor bills all seamlessly in one place.
 

content/contributing/documentation/rst_cheat_sheet.rst

@@ -145,7 +145,7 @@ Use the `abbr` markup to write a self-defining abbreviation that is displayed as
 
 .. _contributing/markups/guilabel:
 
-:abbr:`GUI (graphical user interface)` element
+:abbr:`GUI (Graphical User Interface)` element
 ----------------------------------------------
 
 Use the `guilabel` markup to identify any text of the interactive user interface (e.g., button

content/legal/terms/i18n/enterprise_pt_BR.rst

@@ -1,664 +0,0 @@
-.. _enterprise_agreement_pt:
-
-===========================================
-Odoo Enterprise Subscription Agreement (PT)
-===========================================
-
-.. only:: html
-
-    `Download PDF <https://www.odoo.com/documentation/{CURRENT_BRANCH}/odoo_enterprise_agreement_pt_BR.pdf>`_
-.. warning::
-    Esta é uma tradução em português do Contrato “Odoo Enterprise Subscription Agreement”.
-    A tradução é fornecida com o intuito de facilitar a sua compreensão, mas não tem
-    valor legal. A única referência oficial aos termos do Contrato “Odoo Enterprise Subscription Agreement”
-    é a :ref:`versão original em inglês <enterprise_agreement>`.
-
-.. note:: Versão 10a - 2022-10-27
-
-.. v6: add "App" definition + update pricing per-App
-.. v7: remove possibility of price change at renewal after prior notice
-.. 7.1: specify that 7% renewal increase applies to all charges, not just per-User.
-.. v8.0: adapt for "Self-Hosting" + "Data Protection" for GDPR
-.. v8a: minor wording changes, tuned User definition, + copyright guarantee
-.. v9.0: add "Working with an Odoo Partner" + Maintenance of [Covered] Extra Modules + simplifications
-.. v9a: clarification wrt second-level assistance for standard features
-.. v9b: clarification that maintenance is opt-out + name of `cloc` command (+ paragraph 5.1 was partially outdated in FR)
-.. v9c: minor wording changes, tuned User definition, + copyright guarantee (re-application of v8a changes
-        on all branches)
-.. v9c2: minor simplification in FR wording
-.. v10: fall 2022 pricing change - removal of "per app" notions
-.. v10.001FR: typo: removed 1 leftover 16€/10LoC price
-.. v10a: clarified wording for Section 5.1 "(at that time)"
-
-Ao assinar os serviços do Odoo Enterprise (os "Serviços") fornecidos pela Odoo SA e suas
-afiliadas (coletivamente, "Odoo SA") em relação ao Odoo Enterprise Edition ou Odoo
-Community Edition (o "Logiciel"), hospedado nas plataformas de nuvem da Odoo SA ("Cloud
-Platform") ou no local ("Hospedagem Própria"), você (o "Cliente") concorda em estar
-vinculado aos seguintes termos e condições (o "Contrato").
-
-.. _term_pt:
-
-1 Vigência do Contrato
-======================
-
-A duração deste Contrato (a "Vigência") será especificada por escrito no ato da celebração
-deste Contrato, começando a partir da data de assinatura. O Contrato é automaticamente
-renovado por uma Vigência igual, a menos que qualquer uma das partes forneça um aviso por
-escrito de rescisão para a outra parte, no mínimo 30 dias antes do final da Vigência.
-
-.. _definitions_pt:
-
-2 Definições
-============
-
-Usuário
-    Qualquer conta de usuário indicada como ativa no Software, com acesso ao modo de criação e/ou edição.
-    Contas de usuário desativadas e contas usadas por pessoas externas (ou sistemas)
-    que têm apenas acesso limitado ao Software por meio das instalações do portal (conhecidas como
-    "Usuários do Portal") não são consideradas como Usuários.
-
-App
-    Um "Aplicativo" (App) é um grupo especializado de recursos disponíveis para instalação no Software.
-
-Parceiro Odoo
-    Um Parceiro Odoo é uma empresa ou indivíduo terceirizado, escolhido pelo Cliente e que
-    trabalha com o Cliente para seus serviços relacionados ao Odoo. O Cliente pode decidir a
-    qualquer momento trabalhar com um Parceiro Odoo diferente ou trabalhar diretamente com a
-    Odoo SA (sujeito a aviso prévio).
-
-Módulo Extra
-    Um Módulo Extra é um diretório de arquivos de código-fonte ou um conjunto de
-    customizações baseadas em Python, criadas em uma base de dados (por exemplo, com o Odoo
-    Studio), que adiciona recursos ou altera o comportamento padrão do Software. Pode ter sido
-    desenvolvido pelo Cliente, pela Odoo SA, por um Parceiro Odoo em nome do Cliente ou por
-    terceiros.
-
-Módulo Extra Coberto
-    Um Módulo Extra Coberto é um Módulo Extra pelo qual o Cliente escolhe pagar uma taxa de
-    manutenção para obter serviços de suporte, atualização e correção de bugs.
-
-Bug
-    É considerado Bug qualquer falha do Software ou de um Módulo Extra Coberto que resulte em
-    uma parada completa, rastreamento de erro ou violação de segurança e não seja causada
-    diretamente por uma instalação ou configuração defeituosa. A não conformidade com
-    especificações ou requisitos será considerada como Bug, a critério da Odoo SA (normalmente,
-    quando o Software não produz os resultados ou desempenho para o qual foi projetado ou
-    quando um recurso específico do país não atende mais aos requisitos legais de contabilidade).
-
-Versões Cobertas
-    A menos que seja especificado, os Serviços fornecidos sob este Contrato são aplicáveis apenas
-    às Versões Cobertas do Software, que incluem as 3 versões principais lançadas mais
-    recentemente.
-
-Plano de Assinatura
-    Um Plano de Assinatura define um conjunto de Aplicativos, recursos e soluções de
-    hospedagem cobertos por este Contrato e é definido por escrito na celebração deste Contrato.
-
-.. _enterprise_access_pt:
-
-3 Acesso ao Software
-====================
-
-O Cliente pode utilizar o Software hospedado na Cloud Platform, ou escolher a opção de
-Hospedagem Própria. A Cloud Platform é hospedada e totalmente gerenciada pela Odoo SA e
-acessada remotamente pelo Cliente. Com a opção de Hospedagem Própria, o Cliente hospeda
-o Software em sistemas de computador de sua escolha, que não estão sob o controle da Odoo SA.
-
-Durante a vigência deste Contrato, a Odoo SA concede ao Cliente uma licença não exclusiva e
-intransferível para usar (executar, modificar, executar após modificação) o software Odoo
-Enterprise Edition, nos termos estabelecidos em :ref:`appendix_a_pt`.
-
-O Cliente concorda em tomar todas as medidas necessárias para garantir a execução inalterada
-da parte do Software que verifica a validade de uso do Odoo Enterprise Edition e coleta
-estatísticas para esse fim, incluindo, entre outros, a execução de uma instância, o número de
-Usuários, os Aplicativos instalados e o número de linhas de código dos Módulos Extras Cobertos.
-
-A Odoo SA compromete-se a não divulgar figuras individuais ou nomeadas a terceiros sem o
-consentimento do Cliente, e a tratar todos os dados recolhidos em conformidade com a sua
-Política de Privacidade oficial, publicada em https://www.odoo.com/privacy.
-
-Após a expiração ou rescisão deste Contrato, esta licença é revogada imediatamente e o Cliente
-concorda em parar de usar o software Odoo Enterprise Edition e a Cloud Platform.
-
-Se o Cliente violar os termos desta seção, o Cliente concorda em pagar à Odoo SA uma taxa
-extra igual a 300% do preço de tabela aplicável ao número real de Usuários.
-
-.. _services_pt:
-
-4 Serviços
-==========
-
-.. _bugfix_pt:
-
-4.1 Serviço de Correção de Bugs
--------------------------------
-
-Durante a vigência deste Contrato, a Odoo SA se compromete a realizar todos os esforços
-razoáveis para corrigir qualquer Bug do Software e Módulos Extras Cobertos relatados pelo
-Cliente por meio de um canal apropriado (normalmente, o formulário da Web ou os números
-de telefone listados em http://www.odoo.com.help, ou, ao trabalhar com um parceiro Odoo, o canal
-fornecido pelo parceiro) e começar a lidar com essas solicitações do Cliente em 2 dias úteis.
-
-Assim que o Bug for corrigido, uma solução apropriada será comunicada ao Cliente. Se o
-Cliente estiver usando uma Versão Coberta, ele não será solicitado a atualizar para uma Versão
-Coberta mais recente do Software como solução para um Bug.
-
-Quando um Bug é corrigido em qualquer Versão Coberta, a Odoo SA se compromete a corrigir
-o Bug em todas as Versões Cobertas mais recentes do Software.
-
-Ambas as partes reconhecem que, conforme especificado na licença do Software e na seção
-:ref:`liability_pt` deste Contrato, a Odoo SA não pode ser responsabilizada por Bugs
-no Software ou nos Módulos Extras Cobertos.
-
-4.2 Serviço de Atualizações de Segurança
-----------------------------------------
-
-.. _secu_self_hosting_pt:
-
-Hospedagem Própria
-~~~~~~~~~~~~~~~~~~
-
-Durante a vigência deste Contrato, a Odoo SA se compromete a enviar um “Aviso de
-Segurança” ao Cliente para qualquer Bug de segurança descoberto nas Versões Cobertas do
-Software (isso exclui Módulos Extras), pelo menos 2 semanas antes de publicar o Comunicado
-de Segurança, a menos que o Bug já tenha sido divulgado publicamente por terceiros. Os
-Comunicados de Segurança incluem uma descrição completa do Bug, sua causa, seus possíveis
-impactos nos sistemas do Cliente e a solução correspondente para cada Versão Coberta.
-
-O Cliente entende que o Bug e as informações do Comunicado de Segurança devem ser
-tratados como Informações Confidenciais conforme descrito em
-:ref:`confidentiality_pt` durante o período de embargo que precede a divulgação pública.
-
-.. _secu_cloud_platform_pt:
-
-Cloud Platform
-~~~~~~~~~~~~~~
-
-A Odoo SA se compromete a aplicar os reparos de segurança para qualquer Bug de segurança
-descoberto em uma versão do Software hospedada na Cloud Platform, em todos os sistemas
-sob seu controle, assim que o reparo estiver disponível, sem exigir nenhuma ação manual do Cliente.
-
-
-.. _upgrade_pt:
-
-4.3 Serviços de Atualização
----------------------------
-
-.. _upgrade_odoo_pt:
-
-Serviço de Atualização para o Software
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Durante a vigência deste Contrato, o Cliente pode enviar solicitações de atualização por meio
-do canal apropriado (geralmente, o site do serviço de atualização da Odoo SA), a fim de
-converter uma base de dados do Software de qualquer versão do Software para uma Versão
-Coberta mais recente (a "Versão de Destino").
-
-Para a Cloud Platform, as solicitações de atualização são enviadas diretamente do painel de
-controle da Cloud Platform e não requerem nenhum upload de dados. Para Hospedagem
-Própria, as solicitações de atualização devem incluir uma cópia da base de dados do Cliente e
-os dados associados (normalmente obtidos no menu Backup do Software).
-
-Este serviço é fornecido por meio de uma plataforma automatizada para permitir que o Cliente
-execute atualizações autônomas, uma vez que uma versão anterior da base de dados do
-Cliente tenha sido atualizada com sucesso para uma Versão Coberta.
-
-O Serviço de Atualização é limitado à conversão técnica e adaptação da base de dados do
-Cliente para torná-lo compatível com a Versão de Destino, a correção de qualquer Bug causado
-diretamente pela operação de atualização e que não ocorre normalmente na Versão de
-Destino, e a conversão do código-fonte e dados dos Módulos Extras Cobertos para a Versão de
-Destino.
-
-É responsabilidade do Cliente verificar e validar a base de dados atualizada para detectar Bugs,
-analisar o impacto de alterações e novos recursos implementados na Versão de Destino e
-converter e adaptar para a Versão de Destino quaisquer extensões de terceiros do Software
-que tenham sido instaladas na base de dados antes da atualização (por exemplo, Módulos
-Extras não cobertos). O Cliente pode fazer várias solicitações de atualização para uma base de
-dados, até que um resultado aceitável seja alcançado.
-
-
-.. _cloud_hosting_pt:
-
-4.4 Serviços de Hospedagem na Nuvem
------------------------------------
-
-Durante a vigência deste Contrato, quando o Cliente optar por usar a Cloud Platform,
-a Odoo SA se compromete a fornecer pelo menos os seguintes serviços:
-
-- Opções de várias regiões de hospedagem (mínimo 3: Europa, América, Ásia/Pacífico)
-- Hospedagem em data centers Tier III ou equivalente, com 99,9% de tempo de atividade da rede
-- Criptografia SSL (HTTPS) de comunicação classe A
-- Backups totalmente automatizados e verificados, replicados em várias regiões
-- Plano de recuperação de desastres, testado regularmente
-
-Os detalhes dos Serviços de Hospedagem na Nuvem são descritos na página do Acordo de Nível
-de Serviço (SLA) em https://www.odoo.com/cloud-sla.
-
-
-.. _support_service_pt:
-
-4.5 Serviços de Suporte
------------------------
-
-Escopo
-~~~~~~
-
-Durante a vigência deste Contrato, o Cliente pode abrir um número ilimitado de chamados
-de suporte gratuitamente, exclusivamente para questões relacionadas a Bugs (consulte :ref:`bugfix_pt`)
-ou orientação com relação ao uso dos recursos padrão do Software e Módulos Extras Cobertos.
-
-Outras solicitações de assistência, como questões relacionadas a desenvolvimento ou
-customizações, podem ser cobertas por meio da compra de um contrato de serviço separado.
-Caso não esteja claro se uma solicitação é coberta por este Contrato, a decisão fica a critério da
-Odoo SA.
-
-Disponibilidade
-~~~~~~~~~~~~~~~
-
-Os chamados podem ser feitos por meio do formulário da web ou dos números de
-telefone listados em https://www.odoo.com/help, ou, ao trabalhar com um
-Parceiro Odoo, o canal fornecido pelo parceiro, sujeito ao horário de
-funcionamento local.
-
-
-
-.. _maintenance_partner_pt:
-
-4.6 Trabalhando com um Parceiro Odoo
-------------------------------------
-
-Para correções de bugs, suporte e serviços de atualização, o cliente pode trabalhar com um
-parceiro Odoo como principal ponto de contato ou trabalhar diretamente com a Odoo SA.
-
-Se o Cliente decidir trabalhar com um Parceiro Odoo, a Odoo SA subcontratará os serviços
-relacionados com os Módulos Extras Cobertos ao Parceiro Odoo, que se torna o principal ponto
-de contacto do Cliente. O Parceiro Odoo pode entrar em contato com a Odoo SA em nome do
-Cliente para obter assistência de segundo nível com relação aos recursos padrão do Software.
-
-Se o Cliente decidir trabalhar diretamente com a Odoo SA, os serviços relacionados aos
-Módulos Extras Cobertos serão fornecidos somente se o Cliente estiver hospedado na Odoo
-Cloud Platform.
-
-
-.. _charges_pt:
-
-5 Preços e Taxas
-================
-
-.. _charges_standard_pt:
-
-5.1 Preços Padrões
-------------------
-
-Os preços padrões para a assinatura do Odoo Enterprise e os Serviços são baseados no número
-de Usuários e no Plano de Assinatura usado pelo Cliente e especificados por escrito na
-celebração do Contrato.
-
-Se durante a Vigência, o Cliente tiver mais Usuários ou usar recursos que exijam outro Plano de
-Assinatura do que o especificado no momento da celebração deste Contrato, o Cliente
-concorda em pagar uma taxa extra equivalente ao preço de tabela aplicável (no momento do
-desvio do número especificado de Usuários ou Plano de Assinatura) para os Usuários adicionais
-ou o Plano de Assinatura necessário, pelo restante da Vigência.
-
-Além disso, os serviços dos Módulos Extras Cobertos são cobrados com base no número de
-linhas de código nesses módulos. Quando o Cliente optar pela manutenção dos Módulos Extras
-Cobertos, a cobrança será mensal por 100 linhas de código (arredondadas para a próxima
-centena), conforme especificado por escrito na celebração do Contrato. As linhas de código
-serão contabilizadas com o comando ``cloc`` do Software, e incluirão todas as linhas de texto no
-código fonte desses módulos, independente da linguagem de programação (Python, Javascript,
-XML etc.), excluindo linhas em branco, linhas de comentário e arquivos que não são carregados
-durante a instalação ou execução do Software.
-
-Quando o Cliente solicitar uma atualização, para cada Módulo Extra Coberto que não tenha
-sido coberto por uma taxa de manutenção nos últimos 12 meses, a Odoo SA poderá cobrar
-uma taxa extra única para cada mês de cobertura faltante.
-
-.. _charges_renewal_pt:
-
-5.2 Custos de Renovação
------------------------
-
-Após a renovação, conforme previsto na seção :ref:`term_pt`, se os preços aplicados
-durante a Vigência anterior forem inferiores ao preço de tabela aplicável mais atual, tais preços
-aumentarão em até 7%.
-
-.. _taxes_pt:
-
-5.3 Impostos
-------------
-
-Todas as taxas e preços não incluem quaisquer impostos, taxas ou encargos federais,
-provinciais, estaduais, locais ou outros aplicáveis (coletivamente, “Impostos”). O Cliente é
-responsável pelo pagamento de todos os Impostos associados às compras feitas pelo Cliente
-nos termos deste Contrato, exceto quando a Odoo SA for legalmente obrigada a pagar ou
-cobrar impostos pelos quais o Cliente é responsável.
-
-.. _conditions_pt:
-
-6 Condições dos Serviços
-========================
-
-6.1 Obrigações do Cliente
--------------------------
-
-O Cliente concorda em:
-
-- pagar à Odoo SA quaisquer valores aplicáveis pelos Serviços do presente Contrato, de acordo
-  com as condições de pagamento especificadas na assinatura deste contrato;
-- notificar imediatamente a Odoo SA quando seu número real de Usuários exceder o número
-  especificado no ato da celebração do Contrato e, nesse caso, pagar a taxa adicional aplicável,
-  conforme descrito na seção :ref:`charges_standard_pt`;
-- tomar todas as medidas necessárias para garantir a execução inalterada da parte do Software
-  que verifica a validade do uso do Odoo Enterprise Edition, conforme descrito
-  em :ref:`enterprise_access_pt`;
-- nomear 1 pessoa de contato dedicada ao Cliente durante toda a vigência do Contrato;
-- fornecer notificação por escrito à Odoo SA 30 dias antes de mudar seu ponto de contato principal
-  para trabalhar com outro Parceiro Odoo ou para trabalhar diretamente com a Odoo SA.
-
-Quando o Cliente opta por usar a Cloud Platform, o Cliente concorda ainda em:
-
-- tomar todas as medidas razoáveis para manter suas contas de usuário seguras,
-  inclusive escolhendo uma senha forte e não compartilhando com ninguém;
-- fazer uso razoável dos Serviços de Hospedagem, renunciando quaisquer atividades ilegais ou
-  abusivas, e observar estritamente as regras descritas na Política de Uso Aceitável
-  publicada em https://www.odoo.com/acceptable-use.
-
-Quando o cliente escolhe a opção de Hospedagem Própria, o cliente concorda ainda em:
-
-- tomar todas as medidas razoáveis para proteger os arquivos e bases de dados do Cliente e
-  garantir que os dados do Cliente estejam seguros e protegidos, reconhecendo que a Odoo SA
-  não pode ser responsabilizada por qualquer perda de dados;
-- conceder à Odoo SA o acesso necessário para verificar a validade do uso do Odoo Enterprise
-  Edition mediante solicitação (por exemplo, se a validação automática for considerada
-  inoperante para o Cliente).
-
-6.2 Sem Aliciamento ou Contratações
------------------------------------
-
-Exceto quando a outra parte der seu consentimento por escrito, cada parte, suas afiliadas e
-representantes concordam em não solicitar ou oferecer emprego a qualquer funcionário da
-outra parte que esteja envolvido na execução ou uso dos Serviços sob este Contrato, durante a
-vigência do Contrato e por um período de 12 meses a partir da data de rescisão ou vencimento
-deste Contrato. Em caso de descumprimento das condições desta seção que leve à demissão
-do referido funcionário para o efeito, a parte infratora obriga-se a pagar à outra parte um
-montante de 30 000,00 euros (€) (trinta mil euros).
-
-
-.. _publicity_pt:
-
-6.3 Publicidade
----------------
-
-Exceto quando vetado através de notificação por escrito, cada parte concede à outra uma
-licença mundial intransferível, não exclusiva e isenta de royalties para reproduzir e exibir o
-nome, logotipos e marcas registradas da outra parte, exclusivamente para fins de referência à
-outra parte como um cliente ou fornecedor, em sites, press releases e outros materiais de
-marketing.
-
-.. _confidentiality_pt:
-
-6.4 Confidencialidade
----------------------
-
-Definição de “Informações Confidenciais”:
-    Todas as informações divulgadas por uma parte (a “Parte Divulgadora”) à outra parte (a “Parte
-    Receptora”), oralmente ou por escrito, que seja designada como confidencial ou que
-    razoavelmente deva ser entendida como confidencial, dada a natureza do informações e as
-    circunstâncias da divulgação. Em particular, qualquer informação relacionada a negócios,
-    assuntos, produtos, desenvolvimentos, segredos comerciais, know-how, pessoal, clientes e
-    fornecedores de qualquer uma das partes deve ser considerada confidencial.
-
-Para todas as Informações Confidenciais recebidas durante a Vigência deste Contrato, a Parte
-Receptora usará o mesmo grau de cuidado que usa para proteger a confidencialidade de suas
-próprias Informações Confidenciais semelhantes, mas não menos do que o cuidado razoável.
-
-A Parte Receptora pode divulgar Informações Confidenciais da Parte Divulgadora na medida em
-que for obrigada por lei a fazê-lo, desde que a Parte Receptora notifique a Parte Divulgadora
-com antecedência sobre a divulgação obrigatória, na medida permitida por lei.
-
-.. _data_protection_pt:
-
-6.5 Proteção de Dados
----------------------
-
-Definições
-    "Dados Pessoais", "Controlador", "Processamento" têm os mesmos significados que no
-    Regulamento (UE) 2016/679 e na Diretiva 2002/58/EC, e qualquer regulamento ou legislação
-    que os altere ou substitua (doravante referido como "Legislação de Proteção de Dados")
-
-Processamento de Dados Pessoais
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-As partes reconhecem que a base de dados do Cliente pode conter Dados Pessoais, dos quais o
-Cliente é o Controlador. Estes dados serão processados pela Odoo SA quando o Cliente assim o
-instruir, mediante a utilização de algum dos Serviços que necessitem de uma base de dados
-(e.g. os Serviços de Hospedagem na Nuvem ou o Serviço de Atualização da Base de Dados), ou
-se o Cliente transferir a sua base de dados ou parte da sua base de dados à Odoo SA por
-qualquer motivo relacionado a este Contrato.
-
-Este processamento será realizado em conformidade com a Legislação de Proteção de Dados.
-Em particular, a Odoo SA compromete-se a:
-
-- (a) apenas processar os Dados Pessoais quando e conforme instruído pelo Cliente, e com a
-  finalidade de executar um dos Serviços sob este Contrato, a menos que haja exigência por lei,
-  caso em que a Odoo SA notificará o Cliente com antecedência, a não ser que a lei a proíba;
-- (b) garantir que todas as pessoas dentro da Odoo SA autorizadas a processar os Dados Pessoais
-  se comprometam com a confidencialidade;
-- (c) implementar e manter medidas técnicas e organizacionais apropriadas para proteger os
-  Dados Pessoais contra processamento não autorizado ou ilegal e contra perda, destruição,
-  dano, roubo, alteração ou divulgação acidental;
-- (d) encaminhar prontamente ao Cliente qualquer solicitação de Proteção de Dados que tenha
-  sido enviada à Odoo SA em relação à base de dados do Cliente;
-- (e) notificar o Cliente imediatamente ao tomar conhecimento e confirmar qualquer processamento
-  acidental, não autorizado ou ilegal, divulgação ou acesso aos Dados Pessoais;
-- (f) notificar o Cliente se as instruções de processamento infringirem a Legislação de
-  Proteção de Dados aplicável, na opinião da Odoo SA;
-- (g) disponibilizar ao Cliente todas as informações necessárias para demonstrar conformidade
-  com a Legislação de Proteção de Dados, permitir e contribuir razoavelmente para auditorias,
-  incluindo inspeções, conduzidas ou ordenadas pelo Cliente;
-- (h) excluir permanentemente todas as cópias da base de dados do Cliente em posse da Odoo
-  SA, ou devolver tais dados, à escolha do Cliente, após a rescisão deste Contrato, sujeito
-  aos atrasos especificados na `Política de Privacidade <https://www.odoo.com/privacy>`_
-  da Odoo SA;
-
-No que diz respeito às alíneas (d) a (f), o Cliente concorda em fornecer à Odoo SA informações
-de contato precisas em todos os momentos, conforme necessário para notificar o responsável pela
-Proteção de Dados do Cliente.
-
-Subprocessadores
-~~~~~~~~~~~~~~~~
-
-O Cliente reconhece e concorda que, para fornecer os Serviços, a Odoo SA pode usar
-provedores de serviços terceirizados (Subprocessadores) para tratar Dados Pessoais. A Odoo SA
-compromete-se a usar apenas Subprocessadores em conformidade com a Legislação de
-Proteção de Dados. Esta utilização estará abrangida por um contrato entre a Odoo SA e o
-Subprocessador que dá garantias nesse sentido. A Política de Privacidade da Odoo SA,
-publicada em https://www.odoo.com/privacy, fornece informações atualizadas sobre os
-nomes e propósitos dos Subprocessadores atualmente em uso pela Odoo SA para a execução
-dos Serviços.
-
-.. _termination_pt:
-
-6.6 Cessão
-----------
-
-Caso qualquer uma das partes não cumpra qualquer uma de suas obrigações decorrentes deste
-Contrato, e se tal violação não for sanada dentro de 30 dias corridos a partir da notificação por
-escrito de tal violação, este Contrato poderá ser rescindido imediatamente pela parte não
-infratora.
-
-Além disso, a Odoo SA pode rescindir o Contrato imediatamente caso o Cliente não pague as
-taxas aplicáveis pelos Serviços dentro de 21 dias após a data de vencimento especificada na
-fatura correspondente e após no mínimo 3 lembretes.
-
-Cláusulas Subsistentes:
-  As seções ":ref:`confidentiality_pt`", “:ref:`disclaimers_pt`",   “:ref:`liability_pt`",
-  e “:ref:`general_provisions_pt`" subsistirão a qualquer rescisão ou expiração deste Contrato.
-
-
-.. _warranties_disclaimers_pt:
-
-7 Garantias, Isenções de Responsabilidade, Limitação de Responsabilidade
-========================================================================
-
-.. _warranties_pt:
-
-7.1 Garantias
--------------
-
-A Odoo SA detém os direitos autorais ou equivalente [#cla_pt1]_ de 100% do código do Software e
-confirma que todas as bibliotecas de software necessárias para usar o Software estão disponíveis
-sob uma licença compatível com a licença do Software.
-
-Durante a vigência deste Contrato, a Odoo SA se compromete a realizar esforços
-comercialmente razoáveis para executar os Serviços de acordo com os padrões de indústria
-geralmente aceitos, desde que:
-
-- os sistemas computacionais do Cliente estejam em bom estado de funcionamento e, para o
-  caso de Hospedagem Própria, o Software esteja instalado num ambiente operacional adequado;
-- o Cliente forneça informações adequadas de solução de problemas e, para o caso de
-  Hospedagem Própria, qualquer acesso que a Odoo SA possa precisar para identificar,
-  reproduzir e resolver problemas;
-- todos os valores devidos à Odoo SA sejam pagos.
-
-O único e exclusivo recurso do Cliente e a única obrigação da Odoo SA por qualquer violação
-desta garantia é que a Odoo SA retome a execução dos Serviços sem custo adicional.
-
-.. [#cla_pt1] As contribuições externas são cobertas por um `Contrato de Licença de Direitos
-              Autorais <https://www.odoo.com/cla>`_
-              fornece uma licença permanente, gratuita e irrevogável de direitos autorais e patente para a Odoo SA.
-
-
-.. _disclaimers_pt:
-
-7.2 Isenções de Responsabilidade
---------------------------------
-
-Exceto conforme expressamente disposto neste documento, nenhuma das partes oferece
-qualquer garantia de qualquer tipo, seja expressa, implícita, estatutária ou de outra maneira, e
-cada parte se isenta especificamente de todas as garantias implícitas, incluindo qualquer
-garantia implícita de comercialização, adequação a uma finalidade específica ou não violação,
-na extensão máxima permitida pela lei aplicável.
-
-A Odoo SA não garante que o Software esteja em conformidade com qualquer lei ou
-regulamentação local ou internacional.
-
-.. _liability_pt:
-
-7.3 Limitação de Responsabilidade
----------------------------------
-
-Na extensão máxima permitida por lei, a responsabilidade agregada de cada parte juntamente
-com suas afiliadas, decorrente ou relacionada a este Contrato, não excederá 50% do valor total
-pago pelo Cliente sob este Contrato durante os 12 meses imediatamente anteriores à data do
-evento que deu origem a tal ação judicial. Reivindicações múltiplas não devem ampliar esta
-limitação.
-
-Em nenhum caso, qualquer uma das partes ou suas afiliadas serão responsáveis por quaisquer
-danos indiretos, especiais, exemplares, incidentais ou consequentes de qualquer tipo,
-incluindo, mas não limitado a, perda de receita, lucros, economias, perda de negócios ou
-outras perdas financeiras, custos de paralisação ou atraso, dados perdidos ou corrompidos,
-decorrentes ou relacionados a este Contrato, independentemente da forma de ação, seja por
-contrato, ato ilícito ou não, mesmo que uma parte ou suas afiliadas tenham sido avisadas da
-possibilidade de tais danos, ou se o reparo de uma parte ou de suas afiliadas falhar em seu
-propósito essencial.
-
-.. _force_majeure_pt:
-
-7.4 Força Maior
----------------
-
-Nenhuma das partes será responsável perante a outra parte pelo atraso em qualquer
-cumprimento ou falha em cumprir qualquer ação sob este Contrato quando tal falha ou atraso
-encontrar sua causa em um caso de *força maior*, como regulamentações governamentais,
-incêndio, greve, guerra, inundação, acidente, epidemia, embargo, apropriação total ou parcial
-de fábrica ou produto por qualquer governo ou autoridade pública, ou qualquer outra causa ou
-causas, de natureza semelhante ou diferente, fora do controle razoável de tal parte, desde que
-tal causa ou causas existam.
-
-.. _general_provisions_pt:
-
-8 Disposições Gerais
-====================
-
-.. _governing_law_pt:
-
-8.1 Jurisdição
---------------
-
-Este Contrato e todas as ordens do Cliente estarão sujeitos à lei belga. Qualquer disputa
-decorrente ou relacionada a este Contrato ou a qualquer ordem do Cliente estará sujeita à
-jurisdição exclusiva do Tribunal Comercial de Nivelles.
-
-.. _severability_pt:
-
-8.2 Independência das Disposições Contratuais
----------------------------------------------
-
-No caso de qualquer uma ou mais das disposições deste Contrato ou qualquer aplicação do
-mesmo ser inválida, ilegal ou inexequível em qualquer aspecto, a validade, legalidade e
-aplicabilidade das demais disposições deste Contrato e qualquer aplicação do mesmo não
-serão de forma alguma afetadas ou prejudicadas. Ambas as partes se comprometem a
-substituir qualquer disposição inválida, ilegal ou inexequível deste Contrato por uma disposição
-válida com os mesmos efeitos e objetivos.
-
-.. _appendix_a_pt:
-
-9 Anexo A: Licença do Odoo Enterprise Edition
-=============================================
-
-A versão Enterprise do Odoo tem a licença Odoo Enterprise Edition v1.0, que é
-definida da seguinte forma:
-
-.. warning::
-    Esta é uma tradução em português da "Licença Odoo Enterprise Edition v1.0".
-    A tradução é fornecida com o intuito de facilitar a sua compreensão, mas não tem valor legal.
-    A única referência oficial aos termos da "Licença Odoo Enterprise Edition"
-    é a :ref:`versão original em inglês <odoo_enterprise_license>`
-
-.. raw:: html
-
-    <tt>
-
-.. raw:: latex
-
-    {\tt
-
-
-Licença Odoo Enterprise Edition v1.0
-
-Este software e arquivos associados (o "Software") só podem ser usados (executados, modificados,
-executados após modificações) com uma Assinatura do Odoo Enterprise válida para o número correto
-de usuários.
-
-Com um Acordo de Parceria válido com a Odoo S.A., as permissões acima também são concedidas,
-desde que o uso seja limitado a um ambiente de testes ou desenvolvimento.
-
-Você pode desenvolver módulos Odoo com base no Software e distribuí-los sob a licença de sua
-escolha, desde que seja compatível com os termos da Licença Odoo Enterprise Edition (por exemplo:
-LGPL, MIT ou licenças proprietárias similares a esta).
-
-Você pode usar módulos Odoo publicados sob qualquer licença junto com o Software, desde que a
-licença deles seja compatível com os termos da Licença Odoo Enterprise (incluindo, mas não se
-limitando a, qualquer módulo publicado na Odoo Apps Store em odoo.com/apps).
-
-É proibido publicar, distribuir, sublicenciar ou vender cópias do Software ou cópias modificadas
-do Software.
-
-O aviso de direitos autorais acima e este aviso de permissão devem ser incluídos em todas
-as cópias ou partes substanciais do Software.
-
-O SOFTWARE É FORNECIDO "COMO ESTÁ", SEM GARANTIA DE QUALQUER TIPO, EXPRESSA OU IMPLÍCITA,
-INCLUINDO, MAS NÃO SE LIMITANDO A, GARANTIAS DE COMERCIALIZAÇÃO, ADEQUAÇÃO A UM PROPÓSITO
-ESPECÍFICO E NÃO VIOLAÇÃO. EM NENHUMA CIRCUNSTÂNCIA, OS AUTORES OU TITULARES DE DIREITOS
-AUTORAIS SERÃO RESPONSÁVEIS POR QUALQUER REIVINDICAÇÃO, DANOS OU OUTRA RESPONSABILIDADE,
-SEJA EM AÇÃO DE CONTRATO, DELITO OU DE OUTRA FORMA, DECORRENTE DE, OU EM CONEXÃO COM
-O SOFTWARE OU O USO OU OUTRAS TRANSAÇÕES NO SOFTWARE.
-
-.. raw:: latex
-
-    }
-
-.. raw:: html
-
-    </tt>

content/legal/terms/i18n/enterprise_tex_pt_BR.rst

@@ -1,8 +0,0 @@
-:nosearch:
-:orphan:
-
-.. toctree::
-   :maxdepth: 4
-   :hidden:
-
-   enterprise_pt_BR

content/legal/terms/i18n/partnership_es.rst

@@ -24,9 +24,8 @@ Odoo Partnership Agreement (ES)
 .. v8a: minor clarifications and simplifications
 .. v... !missing updates!
 .. v10: 2023-01-09 - change Odoo SH commission rate to 50%
-.. v11: 2023-05-19 - updated partnership requirements, some clarifications
 
-.. note:: Versión 11 - 2023-05-19
+.. note:: Versión 8a - 2019-08-09
 
 | ENTRE:
 |  Odoo S.A., una empresa que tiene su sede social en Chaussée de Namur, 40, 1367 Grand-Rosière,
@@ -40,7 +39,7 @@ ODOO y EL COLABORADOR se denominan individualmente “Parte” y conjuntamente
 
 1 Objeto
 ========
-El presente Contrato tiene por objeto regular las condiciones bajo las cuales ODOO presta servicios
+El presente contrato tiene por objeto regular las condiciones bajo las cuales ODOO presta servicios
 a EL COLABORADOR, acceso al software Odoo Enterprise Edition, y bajo las cuales EL COLABORADOR
 cumple con las obligaciones establecidas a continuación.
 
@@ -72,9 +71,6 @@ Contrato.
 Además, ODOO otorga a EL COLABORADOR acceso gratuito a la plataforma ODOO.SH con fines de prueba
 y desarrollo.
 
-EL COLABORADOR no tiene permitido bloquear, restringir o limitar de ninguna manera el acceso y uso
-de la Licencia Odoo Enterprise Edition por parte del cliente, sin consulta previa y autorización
-por escrito de ODOO.
 
 .. _restrictions_es:
 
@@ -105,33 +101,29 @@ sin visibilidad como socio oficial hasta que obtengan la experiencia requerida;
 "Official Partners" es para empresas que desean la visibilidad como Ready, Silver y Gold,
 según su experiencia con Odoo.
 
-El nivel de colaboración otorgado a EL COLABORADOR depende de los *nuevos usuarios netos de
-Odoo Enterprise vendidos* en los últimos 12 meses, el número de recursos certificados y la Tasa
-de Retención de clientes. Los *nuevos usuarios netos de Odoo Enterprise vendidos* incluyen nuevos
-clientes, ventas adicionales a clientes existentes, reducciones en ventas a clientes existentes y
-la pérdida de clientes.
-Las renovaciones de contratos existentes no se cuentan como parte del número de usuarios vendidos,
-pero EL COLABORADOR aún recibe una comisión por estos contratos según se establece en la sección
-:ref:`benefits_es`.
+El nivel de colaboración otorgado a EL COLABORADOR depende de los ingresos anuales de
+Odoo Enterprise generados para ODOO (en términos de Usuarios de Odoo Enterprise vendidos).
+Las renovaciones de los contratos existentes no cuentan para el número de Usuarios vendidos,
+pero EL COLABORADOR sigue recibiendo una comisión por estos
+contratos, tal como se indica en la sección :ref:`benefits_es`..
 
 La tabla siguiente resume los requisitos para cada nivel de colaboración.
 
-La *Tasa de Retención* de clientes se calcula dividiendo el número total de clientes de Odoo Enterprise
-adquiridos por EL COLABORADOR en los últimos 3 años que están actualmente activos, entre el
-número total de clientes de Odoo Enterprise adquiridos por EL COLABORADOR en los últimos 3 años.
-
 +--------------------------------------------------+------------------+--------------------+--------------------+--------------------+
 |                                                  | Learning Partner | Official: Ready    | Official: Silver   | Official: Gold     |
 +==================================================+==================+====================+====================+====================+
-| Nuevos Usuarios netos de Odoo Enterprise         |   0              |  10                | 50                 | 300                |
-| vendidos anualmente                              |                  |                    |                    |                    |
+| Usuarios de Odoo Enterprise anuales vendidos     |   0              |  10                | 50                 | 150                |
 +--------------------------------------------------+------------------+--------------------+--------------------+--------------------+
-| Número de empleados certificados en al menos uno |   0              |  1                 |  3                 |  6                 |
+| Número de empleados certificados en al menos uno |   0              |  1                 |  2                 |  3                 |
 | de las 3 últimas versiones de Odoo               |                  |                    |                    |                    |
 +--------------------------------------------------+------------------+--------------------+--------------------+--------------------+
-| Tasa de Retención mínima                         |   n/a            |  n/a               | 70%                |  80%               |
+| Tasa de retención mínima                         |   n/a            |  n/a               | 70%                |  80%               |
 +--------------------------------------------------+------------------+--------------------+--------------------+--------------------+
 
+La Tasa de Retención se define como la relación entre el número de contratos de Odoo Enterprise que
+están actualmente activos y la cantidad de contratos de Odoo Enterprise que han estado activos en
+algún momento en los últimos 12 meses.
+
 Las certificaciones son personales, por lo que cuando un miembro certificado del personal deja
 la empresa, EL COLABORADOR debe notificarlo a ODOO para que actualice la cantidad de recursos
 certificados activos para el contrato de colaboración.
@@ -198,8 +190,7 @@ En la tabla siguiente se describen los detalles de las ventajas para cada nivel
 | y promoción de ODOO                   |                  |                    |                    |                    |
 +---------------------------------------+------------------+--------------------+--------------------+--------------------+
 
-.. [#s1] hasta un máximo de 150€ (o $180) de comisión mensual por suscripción, o 1440€
-   (o $1728) de comisión anual por suscripción.
+.. [#s1] hasta un máximo de 150€ (o 180 $) de comisión mensual por suscripción
 
 4.3 Reconocimiento de socios
 ----------------------------
@@ -243,12 +234,6 @@ enviada por ODOO. La tarifa se especificará por escrito al momento de la firma
 
 EL COLABORADOR reconoce que la tarifa de colaboración mencionadas anteriormente no son reembolsables.
 
-Todos los honorarios y cargos son exclusivos de todos los impuestos, tarifas o cargos gubernamentales,
-federales, provinciales, estatales, locales u otros aplicables (en conjunto, "Impuestos").
-EL COLABORADOR es responsable de pagar todos los Impuestos asociados a las compras realizadas por
-EL COLABORADOR bajo este Contrato, excepto cuando ODOO esté legalmente obligado a pagar o recaudar
-Impuestos de los cuales EL COLABORADOR es responsable.
-
 6 Resolución
 ============
 En el caso de que cualquiera de las Partes no cumpla con cualquiera de sus obligaciones que se
@@ -274,18 +259,17 @@ En el momento de la resolución de este contrato, EL COLABORADOR:
 ===================================
 Ambas Partes están vinculadas por una obligación de medios aquí descrita.
 
-En la medida máxima permitida por la ley, la responsabilidad de cada Parte por cualquier reclamo,
+En la medida máxima permitida por la ley, la responsabilidad de ODOO por cualquier reclamo,
 pérdida, daño o gasto derivado de cualquier manera o bajo cualquier circunstancia del presente
 contrato se limitará a los daños directos demostrados, pero en ningún caso excederá por todos los
 eventos o series de eventos relacionados que ocasionen daños la cantidad total de las tarifas
 pagadas por EL COLABORADOR en el transcurso de los seis (6) meses inmediatamente anteriores a la
 fecha del evento que dio lugar a dicha reclamación.
 
-En ningún caso cada Parte será responsable de ningún daño indirecto o consecuente, incluyendo,
-entre otros, pero no limitándose a, reclamaciones de clientes o terceros, pérdidas de ingresos,
-ganancias, ahorros, pérdidas de negocios y otras pérdidas financieras, costos de paralización y
-retraso, datos perdidos o dañados derivados o relacionados con el cumplimiento de sus obligaciones
-en virtud de este Contrato.
+En ningún caso ODOO será responsable de ningún daño indirecto o consecuente, incluyendo,
+entre otros, reclamaciones de clientes o terceros, pérdidas de ingresos, ganancias, ahorros,
+pérdidas de negocios y otras pérdidas financieras, costos de paralización y retraso, datos perdidos
+o dañados derivados o relacionados con el cumplimiento de sus obligaciones en virtud de este contrato.
 
 EL COLABORADOR reconoce que no tiene ninguna expectativa y que no ha recibido garantías de recuperar
 ninguna inversión realizada en la ejecución de este contrato y el programa de socios de Odoo o de

content/legal/terms/i18n/partnership_fr.rst

@@ -20,9 +20,8 @@ Odoo Partnership Agreement (FR)
 .. v9a: minor clarification to allow OE commission even without maintenance
 .. v9b: 2021-01-12 - update requirements for Partnership levels
 .. v10: 2023-01-09 - change Odoo SH commission rate to 50%
-.. v11: 2023-05-19 - updated partnership requirements, some clarifications
 
-.. note:: Version 11 - 2023-05-19
+.. note:: Version 10 - 2023-01-09
 
 | ENTRE:
 |  Odoo S.A., une entreprise dont le siège social se situe Chaussée de Namur, 40,
@@ -85,10 +84,6 @@ Nonobstant ce qui précède, le PARTENAIRE s’engage à préserver totalement l
 d’Odoo Enterprise Edition requis pour vérifier la validité de l’utilisation d’Odoo Enterprise Edition
 et recueillir les données statistiques nécessaires à cette fin.
 
-Le PARTENAIRE n'est pas autorisé à bloquer, restreindre ou limiter d'aucune manière l'accès et
-l'usage de la licence Odoo Enterprise Edition pour les clients, sauf en cas de consultation préalable
-et accord écrit d'ODOO.
-
 4 Services du partenariat
 =========================
 
@@ -100,34 +95,30 @@ mise en oeuvre d'Odoo, mais sans la visibilité d'un partenaire officiel, en att
 l'expérience requise; tandis qu' "Official Partners" est prévu pour les sociétés qui veulent la visibilité
 en tant que partenaire Ready, Silver ou Gold, suivant leur niveau d'expérience.
 
-Le niveau de partenariat accordé au PARTENAIRE dépend du *nombre net de nouveaux utilisateurs Odoo Enterprise
-vendus* au cours des 12 derniers mois, du nombre de ressources internes certifiées, et du Taux de Rétention
-de clients. Le *nombre net de nouveaux utilisateurs Odoo Enterprise vendus* comprend les nouveaux clients,
-les ventes supplémentaires aux clients existants, les ventes réduites aux clients existants ainsi que
-la perte de clients.
-
-Les renouvellements des contrats existants ne sont pas pris en compte dans le nombre d'utilisateurs
-vendus, mais le PARTENAIRE reçoit toujours une commission sur ces contrats, comme indiqué à la section
-:ref:`benefits_fr`.
+Le niveau de partenariat accordé au PARTENAIRE dépend des nouvelles recettes annuelles Odoo Enterprise
+générées par le PARTENAIRE pour ODOO (en terme du nombre de nouveaux utilisateur Odoo Enterprise vendus),
+du nombre de ressources internes certifiées, et du taux de rétention de clients.
+Les renouvellements de contrats existants
+n’entrent pas en ligne de compte pour le nombre de nouveaux utilisateurs vendus, mais le PARTENAIRE
+reçoit tout de même une commission sur ces contrats, comme indiqué dans la section :ref:`benefits_fr`.
 
 Le tableau ci-dessous résume les exigences pour chaque niveau de partenariat.
 
-Le *Taux de Rétention* de clients est calculé en divisant le nombre total de clients Odoo Enterprise
-acquis par le PARTENAIRE au cours des 3 dernières années et actuellement actifs par le nombre total
-de clients Odoo Enterprise acquis par le PARTENAIRE au cours des 3 dernières années.
-
 +----------------------------------------------+------------------+--------------------+--------------------+--------------------+
 |                                              | Learning Partner | Official: Ready    | Official: Silver   | Official: Gold     |
 +==============================================+==================+====================+====================+====================+
-| Nouveaux utilisateurs net Odoo Enterprise    |   0              |  10                | 75                 | 300                |
-| vendus annuellement                          |                  |                    |                    |                    |
+| Nouveaux utilisateurs Odoo Enterprise vendus |   0              |  10                | 75                 | 200                |
 +----------------------------------------------+------------------+--------------------+--------------------+--------------------+
-| Nombre d'employés certifiés sur au moins une |   0              |  1                 |  3                 |  6                 |
+| Nombre d'employés certifiés sur au moins une |   0              |  1                 |  2                 |  3                 |
 | des 3 dernières version d'Odoo               |                  |                    |                    |                    |
 +----------------------------------------------+------------------+--------------------+--------------------+--------------------+
 | Taux de Rétention minimum                    |   n/a            |  n/a               | 70%                |  80%               |
 +----------------------------------------------+------------------+--------------------+--------------------+--------------------+
 
+Le Taux de Rétention est défini comme le rapport entre le nombre de contrats Odoo Enterprise qui sont
+toujours en cours, et le nombre de contrats Odoo Enterprise qui ont été actifs à un moment au cours
+des 12 derniers mois.
+
 Les certifications sont personnelles, donc lorsqu’un membre du personnel quitte ou rejoint l’entreprise,
 le PARTENAIRE doit en informer ODOO.
 
@@ -195,8 +186,8 @@ Les avantages de chaque niveau de partenariat sont détaillés dans le tableau c
 | promotion                             |                  |                    |                    |                    |
 +---------------------------------------+------------------+--------------------+--------------------+--------------------+
 
-.. [#s1f] jusqu'à un maximum de 150€ (ou $180) de commission mensuelle par contrat Odoo.SH, ou 1440€
-   (ou $1728) de commission annuelle par contrat Odoo.SH.
+.. [#s1f] jusqu'à un maximum de 150€ (ou 180$) de commission mensuelle par contrat Odoo.SH.
+
 
 4.3 Reconnaissance du partenaire
 --------------------------------
@@ -259,11 +250,6 @@ Contrat.
 
 Le PARTENAIRE accepte que les frais de partenariat susmentionnés ne soient pas remboursables.
 
-Tous les frais et tarifs sont indiqués hors taxes, frais et charges fédérales, provinciales, locales
-ou autres taxes gouvernementales applicables (collectivement, les "Taxes"). Le PARTENAIRE est
-responsable du paiement de toutes les Taxes liées aux achats effectués par le PARTENAIRE en vertu
-de ce Contrat, sauf lorsque ODOO est légalement tenu de payer ou de percevoir les Taxes dont
-le PARTENAIRE est responsable.
 
 6 Résiliation
 =============
@@ -290,14 +276,14 @@ Maintien des dispositions:
 ==============================
 Les deux Parties sont liées par l’obligation de moyens ci-après.
 
-Dans les limites autorisées par la loi, la responsabilité de chaque Partie pour quelque réclamation, perte,
+Dans les limites autorisées par la loi, la responsabilité d’ODOO pour quelque réclamation, perte,
 dommage ou dépense que ce soit découlant de n’importe quelle cause et survenant de quelque manière
 que ce soit dans le cadre de ce Contrat sera limitée aux dommages directs prouvés, mais ne dépassera
 en aucun cas, pour tous les événements ou séries d’événements connexes entraînant des dommages,
 le montant total des frais payés par le PARTENAIRE au cours de six (6) mois précédant immédiatement
 la date de l’événement donnant naissance à une telle plainte.
 
-En aucun cas chaque Partie ne sera responsable pour tout dommage indirect ou consécutif, y compris, mais
+En aucun cas, ODOO ne sera responsable pour tout dommage indirect ou consécutif, y compris, mais
 sans s’y restreindre, aux plaintes, pertes de revenu, de recettes, d’économies, d’entreprise ou
 autre perte financière, coûts d’arrêt ou de retard, pertes de données ou données corrompues
 de tiers ou de clients résultant de ou en lien avec l’exécution de ses obligations dans le cadre

content/legal/terms/partnership.rst

@@ -16,9 +16,8 @@ Odoo Partnership Agreement
 .. v9a: minor clarification to allow OE commission even without maintenance
 .. v9b: 2021-01-12 - update requirements for Partnership levels
 .. v10: 2023-01-09 - change Odoo SH commission rate to 50%
-.. v11: 2023-05-19 - updated partnership requirements, some clarifications
 
-.. note:: Version 11 - 2023-05-19
+.. note:: Version 10 - 2023-01-09
 
 | BETWEEN:
 |  Odoo S.A., having its registered office at Chaussée de Namur, 40, 1367 Grand-Rosière,
@@ -80,9 +79,6 @@ Notwithstanding the above, PARTNER commits to wholly preserve the integrity of t
 Odoo Enterprise Edition code that is required to verify the validity of usage of Odoo Enterprise
 Edition and to collect statistics that are needed for that purpose.
 
-PARTNER is not allowed to block, restrict or limit in any way the customer's access and use of
-the Odoo Enterprise Edition License, without prior consultation and written authorisation from ODOO.
-
 
 4 Partnership Services
 ======================
@@ -95,30 +91,29 @@ without visibility as an official partner until they get the required experience
 “Official Partners” is for companies who want the visibility as Ready, Silver, and Gold,
 according to their experience with Odoo.
 
-Partnership level granted to PARTNER depends on the *net new Odoo Enterprise users sold* in
-the last 12 months, the number of certified resources and the customer
-Retention Rate. The *net new Odoo Enterprise users sold* includes new customers, upsells on existing
-customer, downsells on existing customers, and customer churn.
+Partnership level granted to PARTNER depends on the annual new Odoo Enterprise revenue generated
+for ODOO (in terms of Odoo Enterprise Users sold), the number of certified resources and the customer
+Retention Rate.
 Renewals of existing contracts do not count towards the number of Users Sold, but PARTNER
 still gets a commission on these contracts as stated in section :ref:`benefits`.
 
 The table below summarizes the requirements that have to be met for each partnership level.
 
-The customer *Retention Rate* is calculated by dividing the total number of Odoo Enterprise customers
-acquired by PARTNER in the last 3 years that are currently active by the total number of Odoo Enterprise
-customers acquired by PARTNER in the last 3 years.
-
 +--------------------------------------------+------------------+--------------------+--------------------+--------------------+
 |                                            | Learning Partner | Official: Ready    | Official: Silver   | Official: Gold     |
 +============================================+==================+====================+====================+====================+
-| Annual Net New Odoo Enterprise Users Sold  |   0              |  10                | 75                 | 300                |
+| Annual New Odoo Enterprise Users Sold      |   0              |  10                | 75                 | 200                |
 +--------------------------------------------+------------------+--------------------+--------------------+--------------------+
-| Number of Certified Employees on at least  |   0              |  1                 | 3                  | 6                  |
+| Number of Certified Employees on at least  |   0              |  1                 |  2                 |  3                 |
 | one of the 3 last Odoo versions            |                  |                    |                    |                    |
 +--------------------------------------------+------------------+--------------------+--------------------+--------------------+
 | Minimum Retention Rate                     |   n/a            |  n/a               | 70%                |  80%               |
 +--------------------------------------------+------------------+--------------------+--------------------+--------------------+
 
+The Retention Rate is defined as the ratio between the number of Odoo Enterprise contracts that
+are currently active, and the number of Odoo Enterprise contracts that have been active at some point
+in the last 12 months
+
 Certifications are personal, so when a certified staff member leaves or joins the company,
 PARTNER must notify ODOO.
 
@@ -186,8 +181,7 @@ The details of the benefits for each level of the partnership are described in t
 | Promotion                             |                  |                    |                    |                    |
 +---------------------------------------+------------------+--------------------+--------------------+--------------------+
 
-.. [#s1] up to a maximum of 150€ (or $180) of monthly commission per subscription, or 1440€
-   (or $1728) of yearly commission per subscription
+.. [#s1] up to a maximum of 150€ (or 180$) of monthly commission per subscription
 
 
 4.3 Partner Recognition
@@ -246,11 +240,6 @@ agreement.
 
 PARTNER acknowledges that the above-mentioned Partnership fee is not refundable.
 
-All fees and charges are exclusive of all applicable federal, provincial, state, local or other
-governmental taxes, fees or charges (collectively, “Taxes”). PARTNER is responsible for paying
-all Taxes associated with purchases made by PARTNER under this Agreement, except when ODOO is
-legally obliged to pay or collect Taxes for which PARTNER is responsible.
-
 
 6 Termination
 =============
@@ -276,13 +265,13 @@ On expiry or termination of this Agreement, PARTNER:
 ===========================
 Both Parties are bound by a best endeavours obligation hereunder.
 
-To the maximum extent permitted by law, the liability of each Party for any and all claims, losses, damages or
+To the maximum extent permitted by law, ODOO’s liability for any and all claims, losses, damages or
 expenses from any cause whatsoever and howsoever arising under this Agreement will be limited to
 the direct damages proved, but will in no event exceed for all damage-causing event or series of
 connected events causing damages the total amount for the fees paid by PARTNER in the course of the
 six (6) months immediately preceding the date of the event giving rise to such claim.
 
-In no event will each Party be liable for any indirect or consequential damages, including but not limited
+In no event will ODOO be liable for any indirect or consequential damages, including but not limited
 third parties or customer claims, loss of revenue, profits, savings, loss of business or other
 financial loss, costs of standstill or delay, lost or corrupted data arising out of or in connection
 with the performance of its obligations under this Agreement.
@@ -313,7 +302,7 @@ Non-compliance with the provisions of this section shall be a cause for terminat
 
 8.1 Publicity
 -------------
-PARTNER grants ODOO the non-exclusive right to use PARTNER's name or trademarks in press releases,
+PARTNER grants ODOO the nonexclusive right to use PARTNER's name or trademarks in press releases,
 advertisements or other public announcements.
 
 In particular, PARTNER accepts to be mentioned in the official list of Odoo Partners on odoo.com,