[IMP] mexico: broken url

Removing a dead URL taskid-3636231
[I18N] *: export latest terms
2024-07-25 10:15:11 +02:00 · 2024-07-23 11:47:22 +00:00 · 2024-07-20 03:01:47 +00:00 · 2024-07-20 02:37:23 +00:00 · 2024-07-16 15:57:11 +00:00 · 2024-07-16 09:22:39 +00:00
235 changed files with 66130 additions and 20335 deletions
@@ -21,7 +21,7 @@ turned into a testing environment.
 Deactivated features
 ====================

-Here is a non-exhaustive list of the deactivated parameters:
+Here is a non-exhaustive list of the deactivated features:

 - all planned actions (e.g., automatic invoicing of subscriptions, mass mailing, etc.)
 - outgoing emails
@@ -29,6 +29,7 @@ Here is a non-exhaustive list of the deactivated parameters:
 - payment providers
 - delivery methods
 - :abbr:`IAP (In-App Purchase)` tokens
+- website visibility (prevent search engines from indexing your site)

 .. note::
   **A red banner at the top of the screen is displayed on the neutralized database so that it can
@@ -50,7 +50,7 @@ This matrix shows the support status of every version.
     - November 2023
     - October 2026 (planned)
   * - Odoo saas~16.4
-     - |green|
+     - |red|
     - N/A
     - N/A
     - August 2023
@@ -272,9 +272,6 @@ Upgrading the production database

 Once the :ref:`tests <upgrade/test_your_db>` are completed and you are confident that the upgraded
 database can be used as your main database without any issues, it is time to plan the go-live day.
-It can be planned in coordination with Odoo's upgrade support analysts by `submitting a ticket for
-an issue related to my future upgrade (I am testing an upgrade)
-<https://odoo.com/help?stage=migration>`_.

 Your production database will be unavailable during its upgrade. Therefore, we recommend planning
 the upgrade at a time when the use of the database is minimal.
@@ -2,6 +2,11 @@
 France
 ======

+.. important::
+   You must :doc:`install <../../general/apps_modules>` the **France - Adding Mandatory Invoice
+   Mentions (Decree no. 2022-1299)** (`l10n_fr_invoice_addr`) module to comply with the `local
+   legislation <https://www.legifrance.gouv.fr/jorf/id/JORFTEXT000046383394>`_.
+
 .. _france/fec:

 FEC - Fichier des Écritures Comptables
@@ -172,7 +172,7 @@ German Tax Accounting Standards: Odoo's guide to GoBD Compliance

 **GoBD** stands for `Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern,
 Aufzeichnungen und Unterlagen in elektronischer Form sowie zum Datenzugriff
-<https://www.bundesfinanzministerium.de/Content/DE/Downloads/BMF_Schreiben/Weitere_Steuerthemen/Abgabenordnung/2019-11-28-GoBD.pdf>`_.
+<https://ao.bundesfinanzministerium.de/ao/2021/Anhaenge/BMF-Schreiben-und-gleichlautende-Laendererlasse/Anhang-64/anhang-64.html>`_.
 In short, it is a **guideline for the proper management and storage of books, records, and documents
 in electronic form, as well as for data access**, that is relevant for the German tax authority, tax
 declaration, and balance sheet.
@@ -370,9 +370,8 @@ Payment complements
 Payment policy
 **************

-One  addition of the Mexican localization is the :guilabel:`Payment Policy` field . `According to
-the SAT documentation <https://www.sat.gob.mx/consultas/92764/comprobante-de-recepcion-de-pagos>`_,
-there may be 2 types of payments:
+One  addition of the Mexican localization is the :guilabel:`Payment Policy` field. According to
+the SAT documentation, there are two types of payments:

 - `PUE` (Pago en una Sola Exhibición/Payment in a Single Exhibition)
 - `PPD` (Pago en Parcialidades o Diferido/Payment in Installements or Deferred)
@@ -1,61 +1,49 @@
-===============
-Change language
-===============
+================
+Change languages
+================

-Odoo provides you with the option to manage Odoo in different languages,
-and each user can use Odoo in his own language .
+You select the language of your database upon its creation. However, you can
+:ref:`add <language/add>` and :ref:`install <language/install>` additional languages to allow users
+to manage the database in another language or to
+:doc:`translate <../../websites/website/configuration/translate>` your website.

-Load your desired language
-==========================
+.. _language/add:

-The first thing to do is to load your desired language on your Odoo
-instance.
+Add languages
+=============

-From the general dashboard click on the **Settings** app; on the top
-left of the page select :menuselection:`Translations --> Load a Translation`,
-select a language to install and click on **LOAD.**
+To download additional languages:

-.. image:: language/choose_language01.png
-    :align: center
+- either click the profile icon in the upper-right corner, select :menuselection:`My profile`, and
+  click the :icon:`fa-globe` (:guilabel:`globe`) icon next to the :guilabel:`Language` field;
+- or go to the **Settings** app, and click :guilabel:`Add Languages` in the :guilabel:`Languages`
+  section.

-.. note::
-
-    If you check the "Websites to translate" checkbox you will have the option
-    to change the navigation language on your website.
-
-Change your language
-====================
-
-You can change the language to the installed language by going to the
-drop-down menu at the top right side of the screen, choose
-**Preferences**.
-
-.. image:: language/choose_language02.png
-    :align: center
-
-Then change the Language setting to your installed language and click
-**SAVE.**
-
-.. image:: language/choose_language03.png
-    :align: center
-
-Open a new menu to view the changes.
-
-Change another user's language
-==============================
-
-Odoo also gives you the possibility for each user to choose his
-preferred language.
-
-To change the language for a different user, choose :menuselection:`Users --> Users`
-from the Settings app. Here you have a list of all users and you can
-choose the user who you'd like to change the language for. Select the
-user and click on **Edit** in the top left corner. Under Preferences you
-can change the Language to any previously installed language and click
-**SAVE.**
-
-.. image:: language/choose_language04.png
-    :align: center
+You can then select the languages you want from the dropdown menu and click :guilabel:`Add`.

 .. seealso::
-    * :doc:`../../websites/website/configuration/translate`
+   :doc:`Translations <../../websites/website/configuration/translate>`
+
+.. _language/install:
+
+Change languages
+================
+
+To select their preferred language, users can click the profile icon in the upper-right corner, go
+to :menuselection:`My profile`, and select a :guilabel:`Language` in the dropdown list.
+
+Change another user's language
+------------------------------
+
+To change the database language for a user:
+
+#. Go to the :guilabel:`Settings` app and click :guilabel:`Manage Users` in the :guilabel:`Users`
+   section.
+
+#. Click on the user whose language you want to change.
+
+#. Go to the :guilabel:`Preferences` tab and select a previously
+   :ref:`installed language <language/add>` from the :guilabel:`Language` dropdown menu.
+
+.. note::
+   Emails and documents will be sent to the user in the selected language.
@@ -3,11 +3,16 @@ Packaging
 =========

 In Odoo *Inventory*, *packaging* refers to disposable containers holding multiple units of a
-specific product. Each specific packaging **must** be defined on the individual product form.
+specific product.

-For example, different packages for cans of soda, such as a 6-pack, a 12-pack, or a case of 36, need
-to be configured on the individual product form. This is because packagings are product specific —
-**not** generic.
+For example, different packages for cans of soda, such as a 6-pack, a 12-pack, or a case of 36,
+**must** be configured on the individual product form. This is because packagings are product
+specific, not generic.
+
+.. tip::
+   Packaging can be used in conjunction with Odoo :ref:`Barcode <inventory/barcode/software>`. When
+   receiving products from suppliers, scanning the packaging barcode automatically adds the number
+   of units in the packaging to the internal count of the product.

 Configuration
 =============
@@ -20,6 +25,8 @@ under the :guilabel:`Products` heading, enable the :guilabel:`Product Packagings
   :align: center
   :alt: Enable packagings by selecting "Product Packagings".

+.. _inventory/product_management/packaging-setup:
+
 Create packaging
 ================

@@ -82,6 +89,43 @@ list of all packagings that have been created for all products. Create new packa
      :align: center
      :alt: List of different packagings for products.

+Partial reservation
+-------------------
+
+After :ref:`completing the packaging setup <inventory/product_management/packaging-setup>`,
+packagings can be reserved in full or partial quantities for outgoing shipments. Partial packaging
+flexibility expedites order fulfillment by allowing the immediate shipment of available items, while
+awaiting the rest.
+
+To configure packaging reservation methods, go to :menuselection:`Inventory app --> Configuration
+--> Product Categories`. Then, click :guilabel:`New`, or select the desired product category.
+
+On the product category's form, in the :guilabel:`Logistics` section, :guilabel:`Reserve Packagings`
+can be set to :guilabel:`Reserve Only Full Packagings` or :guilabel:`Reserve Partial Packagings`.
+
+.. important::
+   To see the :guilabel:`Reserve Packaging` field, the :guilabel:`Product Packaging` feature
+   **must** be enabled. To enable this feature, go to :menuselection:`Inventory app -->
+   Configuration --> Settings`, scroll to the :guilabel:`Products` section, tick the
+   :guilabel:`Product Packagings` checkbox, and click :guilabel:`Save`.
+
+.. image:: packaging/reserve-packaging.png
+   :align: center
+   :alt: Show Reserve Packagings field on the product categories page.
+
+.. example::
+   To better evaluate the options based on business needs, consider the following example:
+
+   - a product is sold in twelve units per packaging.
+   - an order demands two packagings.
+   - there are only twenty-two units in stock.
+
+   When :guilabel:`Reserve Only Full Packagings` is selected, only twelve units are reserved for the
+   order.
+
+   Conversely, when :guilabel:`Reserve Partial Packagings` is selected, twenty-two units are
+   reserved for the order.
+
 Apply packagings
 ================

@@ -96,8 +140,4 @@ used for the product. The chosen packaging is displayed on the :abbr:`SO (Sales
      :align: center
      :alt: Assign packagings on the Sales Order Line.

-.. tip::
-   Packaging can be used in conjunction with Odoo :ref:`Barcode <inventory/barcode/software>`. When
-   receiving products from suppliers, scanning the packaging barcode automatically adds the number
-   of units in the packaging to the internal count of the product.

@@ -10,6 +10,8 @@ Setup and configuration
   setup_configuration/delivery_method
   setup_configuration/third_party_shipper
   setup_configuration/labels
+   setup_configuration/bpost
+   setup_configuration/dhl_credentials
   setup_configuration/sendcloud_shipping
   setup_configuration/ups_credentials
-   setup_configuration/dhl_credentials
+
@@ -0,0 +1,110 @@
+=================
+Bpost integration
+=================
+
+Set up the *Bpost* shipping connector in Odoo to manage Bpost shipments to clients directly within
+Odoo. To configure it, complete these steps:
+
+#. Create a Bpost account.
+#. Get the :ref:`Account ID and passphrase <inventory/shipping/Bpost-account>`.
+#. Set up the shipping method in Odoo.
+
+Upon completion, it is possible to calculate the cost of shipping, based on package size and weight,
+have the charges applied directly to a Bpost business account, and automatically print Bpost
+tracking labels through Odoo.
+
+.. seealso::
+   - :doc:`third_party_shipper`
+   - :doc:`delivery_method`
+   - :doc:`dhl_credentials`
+   - :doc:`ups_credentials`
+
+Bpost account setup
+===================
+
+To begin, go to the `Bpost website <https://parcel.bpost.be/en/home/business>`_ to create, or log
+into, the company's Bpost business account. When creating the Bpost account, have the company's VAT
+number and mobile phone number ready.
+
+Follow the website's steps to complete registration, and sign up for shipping services. Doing so
+submits a request to enter a contractual business relationship between the company and Bpost.
+
+.. important::
+   Odoo **cannot** be integrated with `non-business Bpost
+   <https://bpost.freshdesk.com/support/solutions/articles/174847-account-id-and-passphrase>`_
+   accounts.
+
+After completing the setup, get the Bpost account ID and passphrase, by navigating to the
+:guilabel:`Shipping Manager` menu item.
+
+.. _inventory/shipping/bpost-account:
+
+On the :guilabel:`Shipping Manager` page, go to the :guilabel:`Admin` tab, then the
+:guilabel:`General Settings` tab, to find the :guilabel:`Account ID` and :guilabel:`Passphrase`
+needed to configure Odoo's shipping method.
+
+.. image:: bpost/credentials.png
+   :align: center
+   :alt: In the *Admin* tab, show the Account ID and Passphrase.
+
+Configure Bpost shipping method
+===============================
+
+With those necessary credentials, configure the Bpost shipping method in Odoo by going to
+:menuselection:`Inventory app --> Configuration --> Shipping Methods`.
+
+On the :guilabel:`Shipping Methods` page, click :guilabel:`Create`.
+
+In the :guilabel:`Provider` field, select :guilabel:`Bpost` from the drop-down menu. Doing so
+reveals the :guilabel:`Bpost Configuration` tab at the bottom of the form, where the Bpost
+credentials can be entered.
+
+For details on configuring the other fields on the shipping method, such as :guilabel:`Delivery
+Product`, refer to the :doc:`Configure third-party carrier <third_party_shipper>` documentation.
+
+.. note::
+   To generate Bpost :doc:`shipping labels <labels>` through Odoo, ensure the :guilabel:`Integration
+   Level` option is set to :guilabel:`Get Rate and Create Shipment`.
+
+In the :guilabel:`Bpost Configuration` tab, complete the following fields:
+
+- :guilabel:`Bpost Account Number` (required field): enter the company's unique :ref:`account ID
+  <inventory/shipping/bpost-account>` from the Bpost website.
+- :guilabel:`Passphrase` (required field): enter the :ref:`passphrase
+  <inventory/shipping/bpost-account>` from the Bpost website.
+- :guilabel:`Bpost Delivery Nature`: select either :guilabel:`Domestic` or :guilabel:`International`
+  shipping services. Choosing :guilabel:`Domestic` shows the :guilabel:`Options` section, while
+  :guilabel:`International` enables the :guilabel:`Bpost Shipment Type` and :guilabel:`Bpost Parcel
+  Return Instructions` fields.
+- :guilabel:`Bpost Package Type`: select the type of shipping service from the drop-down menu.
+
+  For `domestic delivery
+  <https://help.shipmondo.com/en/articles/6092265-bpost-belgium-parcel-types-and-requirements>`_,
+  the options are: :guilabel:`bpack 24h Pro`, :guilabel:`bpack 24h business`, or :guilabel:`bpack
+  Bus`.
+
+  For `international delivery <https://www.bpost.be/en/business-parcels-send/international>`_, the
+  options are: :guilabel:`bpack World Express Pro`, :guilabel:`bpack World Business`, or
+  :guilabel:`bpack Europe Business`.
+- :guilabel:`Bpost Shipment Type` (required field): for international deliveries, declare the type
+  of goods in the package as :guilabel:`SAMPLE`, :guilabel:`GIFT`, :guilabel:`GOODS`,
+  :guilabel:`DOCUMENTS`, or :guilabel:`OTHER`.
+- :guilabel:`Bpost Parcel Return Address`: return address when an international shipment fails to
+  deliver. Select from the drop-down menu: :guilabel:`Destroy`, :guilabel:`Return to sender by air`,
+  or :guilabel:`Return to sender by road`.
+- :guilabel:`Label Type`: choose :guilabel:`A6` or :guilabel:`A4` label sizes from the drop-down
+  menu.
+- :guilabel:`Label Format`: choose :guilabel:`PDF` or :guilabel:`PNG` from the drop-down menu.
+
+For domestic deliveries, these features are available in the :guilabel:`Options` section:
+
+- Enable the :guilabel:`Delivery on Saturday` feature to include Saturdays as possible delivery
+  dates. Depending on the :guilabel:`Bpost Package Type` selected, this option might incur
+  additional costs to the company.
+- Enable the :guilabel:`Generate Return Label` feature to automatically print a return label upon
+  validating the delivery order.
+
+.. image:: bpost/bpost.png
+   :align: center
+   :alt: Show Bpost shipping method.
+
@@ -97,8 +97,8 @@ Install Sendcloud shipping module
 ---------------------------------

 After the Sendcloud account is set up and configured, it's time to configure the Odoo database. To
-get started, go to Odoo's :guilabel:`Apps` module, search for the `Sendcloud Shipping`
-integration, and install it.
+get started, go to Odoo's :guilabel:`Apps` module, search for the `Sendcloud Shipping` integration,
+and install it.

 .. image:: sendcloud_shipping/sendcloud-mod.png
   :align: center
@@ -214,9 +214,40 @@ chatter, which include the following:
 Additionally, the tracking number is now available.

 .. important::
-   When return labels are created, Sendcloud will automatically charge the configured Sendcloud
+   When return labels are created, Sendcloud automatically charges the configured Sendcloud
   account.

+Shipping rules
+--------------
+
+Optionally, create shipping rules to automatically generate shipping labels tailored to different
+product needs. For example, a shipping rule can be created for customers shipping expensive jewelry
+items to purchase insurance.
+
+To use shipping rules, navigate to :menuselection:`Inventory app --> Configuration --> Delivery:
+Shipping Methods`, and select the intended `Sendcloud` shipping method.
+
+Under the :guilabel:`Sendcloud Configuration` tab, in the :guilabel:`OPTIONS` section, choose the
+kind of shipments the shipping rules apply to, via the :guilabel:`Use Sendcloud shipping rules`
+field.
+
+From here, choose either: :guilabel:`Shipping` to customers, :guilabel:`Returns` from customers, or
+:guilabel:`Both`.
+
+.. image:: sendcloud_shipping/enable-shipping-rules.png
+   :align: center
+   :alt: Use Shipping Rules field.
+
+Then, in the Sendcloud website, navigate to :menuselection:`Settings --> Shipping rules`. Create a
+new shipping rule by clicking :guilabel:`Create New`.
+
+In the :guilabel:`Actions` section, set a :guilabel:`Condition` to determine when the rule applies.
+Then, configure what to do when packages meet the condition.
+
+.. seealso::
+   `Create shipping rules on Sendcloud
+   <https://support.sendcloud.com/hc/en-us/articles/10274470454292-How-to-create-shipping-rules#examples-smart-shipping-rules>`_
+
 FAQ
 ===

@@ -93,6 +93,8 @@ match is found:
     :align: center
     :alt: Some examples of putaway rules.

+.. _inventory/warehouses_storage/storage-category:
+
 Storage categories
 ==================

@@ -2,8 +2,6 @@
 Removal strategies (FIFO, LIFO, FEFO)
 =====================================

-.. _inventory/routes/strategies/removal:
-
 For companies with warehouses, **removal strategies** determine which products are taken from the
 warehouse, and when. Removal strategies are typically defined for specific picking operations. This
 helps companies to select the best products, optimize the distance workers need to travel when
@@ -73,7 +73,7 @@ steps below to finish configuring the virtual parent warehouse.
   :alt: New warehouse form.

 .. seealso::
-   - :doc:`Warehouse configurations <../inventory_management/warehouses_locations>`
+   - :doc:`Warehouse configurations <../inventory_management/warehouses>`
   - :ref:`Incoming and outgoing shipments <inventory/receipts_delivery_one_step/wh>`
   - :doc:`Resupply from another warehouse <../inventory_management/resupply_warehouses>`

@@ -1,18 +1,144 @@
-:nosearch:
+:show-content:
+:hide-page-toc:

 ====================
 Inventory management
 ====================

+In the Odoo *Inventory* app, :doc:`warehouses <inventory_management/warehouses>` handle the broader
+organization and distribution of stock across different physical sites, while :doc:`locations
+<inventory_management/use_locations>` provide a more detailed breakdown within each warehouse for
+efficient item management.
+
+This document serves as an introduction to the terminology and concepts necessary to master
+*Inventory*. For specific instructions and examples of how things work, refer to individual
+documentation pages.
+
+.. seealso::
+   `Odoo Tutorials: Warehouses & Locations <https://www.youtube.com/watch?v=zMvudZVLuUo>`_
+
+Warehouses
+==========
+
+:doc:`Warehouses <inventory_management/warehouses>` represent a physical place, with a physical
+address, where a company's items are stored.
+
+Configure :doc:`routes <inventory_management/use_routes>` in a warehouse to control how products
+move to customers, from vendors, within the warehouse, or :doc:`between warehouses
+<inventory_management/resupply_warehouses>`.
+
+Locations
+=========
+
+:doc:`Locations <inventory_management/use_locations>` refer to specific areas within a warehouse,
+such as shelves, floors, or aisles. These are sub-divisions within a warehouse, and are unique to
+that warehouse. Users can create and manage numerous locations within a single warehouse to organize
+inventory more precisely.
+
+.. seealso::
+   - :doc:`inventory_management/use_locations`
+   - :doc:`inventory_management/count_products`
+   - :doc:`inventory_management/cycle_counts`
+   - :doc:`inventory_management/scrap_inventory`
+
+.. _inventory/warehouses_storage/location-type:
+
+Location types
+--------------
+
+*Location types* in Odoo help categorize and manage where products are, and what actions need to be
+taken with them. By default, on the :menuselection:`Inventory app --> Configuration --> Locations`
+page, only internal locations are displayed.
+
+To view the seven location types in Odoo, select any location, and in the :guilabel:`Location Type`
+field, there are:
+
+- :guilabel:`Vendor Location`: defines an area where products purchased from vendors originate.
+  Items here are **not** in stock.
+
+- :guilabel:`View`: used to organize and structure the warehouse hierarchy. For example, the view
+  location `WH` (short for warehouse) groups all internal locations, such as `Stock`, receiving
+  docks, quality checkpoints, and packing areas to show they all belong to the same warehouse.
+
+  .. important::
+     View locations should **not** contain products, but it is possible to move them there.
+
+- :guilabel:`Internal Location`: storage locations within the warehouse. Items stored in these
+  locations are accounted for in :doc:`inventory valuation
+  <inventory_valuation/using_inventory_valuation>`.
+
+- :guilabel:`Customer Location`: where sold products are tracked; items here are no longer in stock.
+
+- :guilabel:`Inventory Loss`: counterpart location to consume missing items or create stock,
+  accounting for discrepancies.
+
+  In Odoo, examples of inventory loss locations are *Inventory Adjustment*, used to account for
+  discrepancies during an inventory count, and *Scrap*, which is where damaged goods are sent to
+  account for inventory losses.
+
+   .. example::
+      `Virtual Locations/Inventory Adjustment` is a location with the :guilabel:`Inventory Loss`
+      type. The database shows `65` units in `WH/Stock`, but an inventory check reveals `60`. To
+      correct the quantity, five units are moved from `WH/Stock` to `Virtual Locations/Inventory
+      Adjustment`.
+
+      .. image:: inventory_management/inventory_management/inventory-loss.png
+         :align: center
+         :alt: Product ends up in Virtual Locations/Inventory Adjustment.
+
+- :guilabel:`Production`: where raw materials are consumed, and :doc:`manufactured products
+  <../../manufacturing>` are created.
+
+- :guilabel:`Transit Location`: used for inter-company or inter-warehouse operations to track
+  products shipped between different addresses, such as :ref:`Physical Locations/Inter-warehouse
+  transit <inventory/warehouses_storage/interwarehouse-transit>`.
+
+.. image:: inventory_management/inventory_management/locations.png
+   :align: center
+   :alt: List of locations in Odoo.
+
+.. note::
+   In Odoo, location types are color-coded:
+     - **Red**: internal locations
+     - **Blue**: view locations
+     - **Black**: external locations (including inventory loss, vendor, and customer locations).
+
+View locations in Odoo
+----------------------
+
+Odoo databases include pre-configured view locations to organize the hierarchy of locations. These
+provide helpful context, and distinguish between internal and external locations.
+
+- *Physical locations* serve as an umbrella for external locations, without changing a product's
+  inventory value. (Inventory valuation changes occur when products move from internal to external
+  locations).
+
+.. _inventory/warehouses_storage/interwarehouse-transit:
+
+  .. example::
+     When moving products in warehouses `WH` and `WH2`, the items are not in either warehouse, but
+     still belong to the company. While in transit, they are placed in the `Inter-warehouse transit`
+     location, a :guilabel:`Transit Location` type.
+
+     This location is under the view location, `Physical Locations`, indicating that
+     `Inter-warehouse transit` is outside of a warehouse, but still part of the company. Doing so
+     does not affect the inventory valuation of the products.
+
+- *Partner locations* group customer and vendor locations (external locations) together. Transfers
+  to these locations affect inventory valuation.
+- *Virtual locations* are locations that do **not** exist physically, but it is where items that are
+  not in inventory can be placed. These can be items that are no longer in inventory due to loss, or
+  other factors.
+
 .. toctree::
   :titlesonly:

-   inventory_management/resupply_warehouses
-   inventory_management/warehouse_replenishment_transfer
-   inventory_management/warehouses_locations
-   inventory_management/create_a_second_warehouse
-   inventory_management/use_routes
+   inventory_management/warehouses
   inventory_management/use_locations
   inventory_management/count_products
   inventory_management/cycle_counts
   inventory_management/scrap_inventory
+   inventory_management/resupply_warehouses
+   inventory_management/warehouse_replenishment_transfer
+   inventory_management/use_routes
+
@@ -1,100 +0,0 @@
-=========================
-Create a second warehouse
-=========================
-
-A *warehouse* is a physical building or space where items are stored. In Odoo, it is possible to set
-up multiple warehouses and transfer stored items between them.
-
-By default, the Odoo platform has one warehouse that is already configured, with the address set as
-the company's address. To create a second warehouse, select :menuselection:`Configuration -->
-Warehouses`, then click :guilabel:`Create` and configure the form as follows:
-
- :guilabel:`Warehouse`: the full name of the warehouse
- :guilabel:`Short Name`: the abbreviated code by which the warehouse is referred to; the short name
-  for the default warehouse in Odoo is **WH**
- :guilabel:`Company`: the company that owns the warehouse; this can be set as the company that owns
-  the Odoo database or the company of a customer or vendor
- :guilabel:`Address`: the address where the warehouse is located
-
-.. important::
-   The options below will only appear if the :guilabel:`Multi-Step Routes` checkbox is enabled in
-   :menuselection:`Configuration --> Settings` under the :guilabel:`Warehouse` heading. For more
-   information about routes and how they work in Odoo, see :ref:`Using Routes and Pull/Push Rules
-   <use-routes>`.
-
- :guilabel:`Incoming/Outgoing Shipments`: select the routes that incoming and outgoing shipments
-  should follow
- :guilabel:`Resupply Subcontractors`: allow subcontractors to be resupplied from this warehouse
- :guilabel:`Manufacture to Resupply`: allow for items to be manufactured in this warehouse
- :guilabel:`Manufacture`: select the route that should be followed when manufacturing goods inside
-  the warehouse
- :guilabel:`Buy to Resupply`: check the box to allow for purchased products to be delivered to the
-  warehouse
- :guilabel:`Resupply From`: select warehouses that can be used to resupply the warehouse being
-  created
-
-.. image:: create_a_second_warehouse/new-warehouse-configuration.png
-   :align: center
-   :alt: A filled out form for creating a new warehouse.
-
-.. important::
-   Creating a second warehouse will automatically enable the *Storage Locations* setting, which
-   allows location tracking of products within a warehouse. To toggle this setting, navigate to
-   :menuselection:`Configuration --> Settings` and click the checkbox under the
-   :guilabel:`Warehouse` heading.
-
-After filling out the form, click :guilabel:`Save` and the new warehouse will be created.
-
-Add inventory to a new warehouse
-================================
-
-If a new warehouse is created that has existing inventory in it, the inventory counts should be
-added to Odoo so that the stock listed in the Odoo database reflects what is in the physical
-warehouse. To add inventory to a new warehouse, navigate to :menuselection:`Inventory -->
-Operations --> Inventory Adjustments`, and then click :guilabel:`Create`. The inventory adjustment
-form can then be filled out as follows:
-
- :guilabel:`Inventory Reference`: the name or code that the inventory adjustment can be referred to
-  by
- :guilabel:`Locations`: the location(s) where the inventory is stored; include the new warehouse
-  and any locations within it that inventory will be added to
- :guilabel:`Products`: include all products that will be added to inventory or leave blank to
-  select any product during the next step
- :guilabel:`Include Exhausted Products`: include products with a quantity of zero; does not affect
-  inventory adjustments for new warehouses since they have no existing inventory
- :guilabel:`Accounting Date`: the date used by accounting teams for bookkeeping related to the
-  inventory
- :guilabel:`Company`: the company that owns the inventory; can be set as the user's company or as a
-  customer or vendor
- :guilabel:`Counted Quantities`: choose whether the counted quantities for products being added
-  should default to stock on hand or zero; does not affect inventory adjustments for new warehouses
-  since they have no existing inventory
-
-.. image:: create_a_second_warehouse/inventory-adjustment-configuration.png
-   :align: center
-   :alt: A filled out form for an inventory adjustment.
-
-Once the form is properly configured, click on :guilabel:`Start Inventory` to be taken to the next
-page where products can be added to the inventory adjustment. Add a new product by clicking on
-:guilabel:`Create` and then fill out the product line as follows:
-
- :guilabel:`Product`: the product being added to inventory
- :guilabel:`Location`: the location where the product is currently stored in the new warehouse;
-  this can be set as the overall warehouse or a location within the warehouse
- :guilabel:`Lot/Serial Number`: the lot that the product belongs to or the serial number used to
-  identify it
- :guilabel:`On Hand`: the total quantity of the product stored in the location for which inventory
-  is being adjusted; this should be zero for a new location or warehouse
- :guilabel:`Counted`: the amount of the product that is being added to inventory
- :guilabel:`Difference`: the difference between the *On Hand* and *Counted* values; this will
-  automatically update to reflect the value entered in the :guilabel:`Counted` column
- :guilabel:`UoM`: the unit of measure used for counting the product
-
-.. image:: create_a_second_warehouse/product-line-configuration.png
-   :align: center
-   :alt: Include a line for each product being added to inventory.
-
-After adding all the products already stored in the new warehouse, click :guilabel:`Validate
-Inventory` to complete the inventory adjustment. The values in the :guilabel:`On Hand` column will
-update to reflect those in the :guilabel:`Counted` column and the products added will appear in the
-inventory of the new warehouse.
@@ -23,7 +23,7 @@ rather a designation in Odoo that is used to track items that are no longer in p
 .. admonition:: Learn more

   For more information about virtual locations, see the documentation about the different types of
-   :ref:`locations <inventory/management/difference-warehouse-location>`.
+   :ref:`location types <inventory/warehouses_storage/location-type>`.

 Scrap from stock
 ================
@@ -2,58 +2,118 @@
 Locations
 =========

-A *location* is a specific space within a warehouse. This can be a shelf, room, aisle, etc. There
-are three types of locations in Odoo:
+A *location* is a specific space within a warehouse. This can be a shelf, room, aisle, etc.

- *Physical locations* are spaces within a warehouse owned by the user's company. These can be a an
-  area where items are stored like an aisle or shelf, or an area where operations take place, like
-  loading and unloading bays.
- *Partner locations* are the same as physical locations except that they exist within the warehouse
-  of a customer or vendor.
- *Virtual locations* are locations that do not exist physically, but where items that are not in
-  inventory can be placed. These can be items that have not yet entered inventory, like products
-  that are on the way to a warehouse, or items that are no longer in inventory due to loss or other
-  factors.
+Configuration
+=============

-.. important::
-   In order to use locations, the :guilabel:`Storage Locations` setting must be enabled. To do so,
-   navigate to :menuselection:`Inventory --> Configuration --> Settings`, scroll down to the
-   :guilabel:`Warehouse` heading, and enable the :guilabel:`Storage Locations` checkbox.
+To create specific storage locations, enable the *Storage Locations* feature by going to
+:menuselection:`Inventory app --> Configuration --> Settings`. In the :guilabel:`Warehouses`
+section, tick the :guilabel:`Storage Locations` checkbox. Then, click :guilabel:`Save`.

-Create a new location inside a warehouse
-========================================
+.. note::
+   Typically, the :guilabel:`Storage Locations` feature is used with :doc:`Multi-Step Routes
+   <use_routes>`, which controls how products move between locations.

-Starting from the :menuselection:`Inventory` app, select :menuselection:`Configuration --> Locations
--> Create`. The new location form can then be configured as follows:
+.. image:: use_locations/enable-location.png
+   :align: center
+   :alt: Show Storage Locations feature.

- :guilabel:`Location Name`: the name that will be used to reference the location
- :guilabel:`Parent Location`: the location or warehouse that the new location exists within
- :guilabel:`Location Type`: choose the category that the location belongs to
- :guilabel:`Company`: the company that owns the warehouse that the location is inside of
- :guilabel:`Is a Scrap Location?`: check this box to allow for scrapped/damaged goods to be stored
-  in this location
- :guilabel:`Is a Return Location?`: check this box to allow products to be returned to this
-  location
- :guilabel:`Barcode`: the barcode number assigned to the location
- :guilabel:`Removal Strategy`: the :ref:`strategy <inventory/routes/strategies/removal>` for how
-  items should be taken from inventory
+Create new location
+===================

-.. image:: use_locations/new-location-form.png
+After enabling *Storage Locations*, go to :menuselection:`Inventory app --> Configuration -->
+Locations`.
+
+.. image:: use_locations/locations.png
+   :align: center
+   :alt: List of internal locations.
+
+On this page, click :guilabel:`New`. The new location form can then be configured as follows:
+
+- :guilabel:`Location Name`: recognizable name of the location.
+- :guilabel:`Parent Location`: the location within which the new location exists. After the location
+  is created, it is listed on the :guilabel:`Locations` page using a *location hierarchy*, to
+  describe how a specific location fits within larger areas of the warehouse.
+
+  .. example::
+    In `WH/Stock/Zone A/Refrigerator 1`, "Refrigerator 1" is the location name, "Zone A" is the
+    parent location, and everything before it is the path showing where this spot is within the
+    warehouse.
+
+Additional Information section
+------------------------------
+
+In addition to the required fields above, configure the following location fields to ensure the
+location serves its intended purpose in the database:
+
+- :guilabel:`Location Type`: from the drop-down menu, choose :guilabel:`Vendor Location`,
+  :guilabel:`View`, :guilabel:`Internal Location`, :guilabel:`Customer Location`,
+  :guilabel:`Inventory Loss`, :guilabel:`Production`, or :guilabel:`Transit Location` to categorize
+  the location. For details on each location type, refer to the :ref:`Location Types section
+  <inventory/warehouses_storage/location-type>`.
+- :guilabel:`Storage Category`: only available with the :ref:`Storage Categories
+  <inventory/warehouses_storage/storage-category>` feature enabled in :menuselection:`Inventory app
+  --> Configuration --> Settings`.
+- :guilabel:`Company`: the company the location belongs to.
+- :guilabel:`Is a Scrap Location?`: tick this checkbox to allow for scrapped/damaged goods to be
+  stored in this location.
+- :guilabel:`Is a Return Location?`: tick this checkbox to allow products to be returned to this
+  location.
+- :guilabel:`Barcode`: used with the *Barcode* app, enter the barcode to :ref:`identify actions
+  <barcode/setup/location>` at this location when scanned.
+- :guilabel:`Replenish Location`: used for :doc:`configuring routes <use_routes>`, tick this
+  checkbox to set the location as a destination for receiving products from *Buy*, *Manufacture*, or
+  other procurement routes, ensuring products are correctly supplied to the warehouse.
+
+.. image:: use_locations/new-location.png
   :align: center
   :alt: The form for creating a new location.

-Create location hierarchies
-===========================
+Cyclic Counting section
+-----------------------

-The *Parent Location* setting on the new location form allows for a location to exist within a
-warehouse or another location. Every location can serve as a parent location, and every parent
-location can have multiple locations within it, allowing for the creation of a virtually infinite
-hierarchical structure.
+To schedule regular inventory counts at this location, set the :guilabel:`Inventory Frequency
+(Days)` field to the desired interval. By default, it is set to `0` (no scheduled counts).
+
+For example, setting this field to `30`, schedules a count every thirty days. For more specifics on
+setting up and using this feature, refer to the :doc:`Cycle Counts documentation <cycle_counts>`.
+
+The :guilabel:`Last Effective Inventory` field displays the date the last inventory count at this
+location occurred. When scheduled inventory counts are enabled, the :guilabel:`Next Expected
+Inventory` field displays the date of the next inventory count.

 .. example::
-   Location hierarchy could be organized so that a shelf is located within an aisle, which is
-   located within a room, which is located within the overall warehouse.
+   With inventory counts scheduled to occur every `30` days, and the :guilabel:`Last Effective
+   Inventory` count occurring on July 16, the :guilabel:`Next Expected Inventory` is August 15.

-To create the location hierarchy in the example above, set the warehouse as the parent of the room,
-the room as the parent of the aisle, and the aisle as the parent of the shelf. This can be adapted
-to a hierarchy of any magnitude.
+   .. image:: use_locations/scheduled-count.png
+      :align: center
+      :alt: Show Cyclic Count section of the locations form.
+
+Logistics section
+-----------------
+
+In the :guilabel:`Logistics` section of the locations form, optionally select a :guilabel:`Removal
+Strategy` to determine the order and priority of how products are picked from inventory. The options
+are: :guilabel:`First In First Out (FIFO)`, :guilabel:`Last In First Out (LIFO)`, :guilabel:`Closest
+Location`, and :guilabel:`First Expiry First Out (FEFO)`.
+
+.. seealso::
+   :doc:`../advanced_operations_warehouse/removal`
+
+Current stock at location
+=========================
+
+To view the current stock at a single location, go to :menuselection:`Inventory app -->
+Configuration --> Locations`, and select the desired location.
+
+Next, click the :guilabel:`Current Stock` smart button to get a list of all products at the
+location.
+
+.. example::
+   A list of current stock at `Shelf 1` consists of `266` cabinets and `39` desks.
+
+   .. image:: use_locations/current-stock.png
+      :align: center
+      :alt: Show stock at Shelf 1.
@@ -0,0 +1,73 @@
+==========
+Warehouses
+==========
+
+In the Odoo *Inventory* app, a *warehouse* is a physical space with an address for storing items,
+such as a storage facility, distribution center, or physical store.
+
+Each database has a pre-configured warehouse with the company's address. Users can set up multiple
+warehouses, and :doc:`create stock moves <use_routes>` between them.
+
+Configuration
+=============
+
+To create or manage warehouses, go to :menuselection:`Inventory app --> Configuration -->
+Warehouses`.
+
+Then, select an existing warehouse, or create a new one by clicking :guilabel:`New`. Doing so opens
+the warehouse form, which contains the following fields:
+
+- :guilabel:`Warehouse` (*required field*): the full name of the warehouse.
+- :guilabel:`Short Name` (*required field*): the abbreviated code for the warehouse (maximum five
+  characters). The short name for the default warehouse in Odoo is `WH`.
+
+  .. important::
+     The :guilabel:`Short Name` appears on warehouse documents, so it is recommended to use an
+     memorable one, like "WH[first letters of location]" (e.g. `WHA`, `WHB`, etc.).
+
+- :guilabel:`Address` (*required field*): the address of the warehouse. To change the warehouse
+  address when creating two or more warehouses, hover over the field, and click the
+  :icon:`fa-arrow-right` :guilabel:`(right arrow)`.
+- :guilabel:`Company` (*required field*): the company that owns the warehouse; this can be set as
+  the company that owns the Odoo database, or the company of a customer or vendor.
+- :guilabel:`Intrastat region`: :doc:`region name
+  <../../../../finance/accounting/reporting/intrastat>` required for companies in the European
+  Union.
+
+.. important::
+   The options below are available **only** when the *Multi-Step Routes* feature is enabled in
+   :menuselection:`Inventory app --> Configuration --> Settings`.
+
+- :guilabel:`Incoming Shipments`: select the option to receive products from the warehouse in
+  :doc:`one <../../shipping_receiving/daily_operations/receipts_delivery_one_step>`, :doc:`two
+  <../../shipping_receiving/daily_operations/receipts_delivery_two_steps>`, or :doc:`three
+  <../../shipping_receiving/daily_operations/receipts_three_steps>` steps.
+
+- :guilabel:`Outgoing Shipments`: select the option to deliver products from the warehouse in
+  :doc:`one <../../shipping_receiving/daily_operations/receipts_delivery_one_step>`, :doc:`two
+  <../../shipping_receiving/daily_operations/receipts_delivery_two_steps>`, or :doc:`three
+  <../../shipping_receiving/daily_operations/delivery_three_steps>` steps.
+
+- :guilabel:`Dropship Subcontractors`: available with the *Subcontracting* feature enabled in
+  :menuselection:`Manufacturing app --> Configuration --> Settings`. Tick this checkbox to purchase
+  components from vendors, and dropship them to subcontractors.
+- :guilabel:`Resupply Subcontractors`: available with the *Subcontracting* feature, tick this
+  checkbox to supply subcontractors with raw materials stored in *this* specific warehouse.
+- :guilabel:`Manufacture to Resupply`: tick this checkbox to allow for items to be manufactured in
+  this warehouse.
+- :guilabel:`Manufacture`: choose whether to manufacture products in :doc:`one
+  <../../../manufacturing/management/one_step_manufacturing>`, :doc:`two
+  <../../../manufacturing/management/two_step_manufacturing>`, or :doc:`three steps
+  <../../../manufacturing/management/three_step_manufacturing>`.
+- :guilabel:`Buy to Resupply`: tick this checkbox to allow for purchased products to be delivered to
+  the warehouse.
+- :guilabel:`Resupply From`: available with multiple warehouses in the database, select warehouses
+  to pull stock *from* to fulfill orders.
+
+.. seealso::
+   :doc:`Use inventory adjustments to add stock to new warehouses <count_products>`
+
+.. image:: warehouses/warehouse-form.png
+   :align: center
+   :alt: Example warehouse form.
+
@@ -1,95 +0,0 @@
-===============================
-Manage Warehouses and Locations
-===============================
-
-Terminology
-===========
-
-Warehouse
---------
-
-In Odoo, a **Warehouse** is the actual building/place in which a company's items are stocked.
-Multiple warehouses can be set up in Odoo and the user can create moves between warehouses.
-
-.. _inventory/management/difference-warehouse-location:
-
-Location
--------
-
-A **Location** is a specific space within the warehouse. It can be a sublocation of the warehouse
-(a shelf, a floor, an aisle, and so on). Therefore, a location is part of one warehouse only and it
-is not possible to link one location to multiple warehouses. In Odoo, as many locations can be
-configured as needed under one warehouse.
-
-There are three types of locations:
-
- The **Physical Locations** are internal locations that are part of the warehouses that the
-  company owns. They can be the loading and unloading areas of the warehouse, a shelf, a department,
-  etc.
-
- The **Partner Locations** are spaces within a customer and/or vendor's warehouse. They work the
-  same way as physical locations, with the only difference being that they are not owned by the
-  user's company.
-
- The **Virtual Locations** are places that do not exist, but in which products can be placed when
-  they are not physically in an inventory yet (or anymore). They come in handy when recording lost
-  products (**Inventory Loss**), or accounting for products that are on their way to the warehouse
-  (**Procurements**).
-
-In Odoo, locations are structured hierarchically. Locations can be structured as a tree, dependent
-on a parent-child relationship. This gives more detailed levels of analysis of the stock operations
-and the organization of the warehouses.
-
-Configuration
-=============
-
-To activate locations, go to :menuselection:`Configuration --> Settings` and enable
-:guilabel:`Storage Locations`. Then, click :guilabel:`Save`.
-
-.. image:: warehouses_locations/storage-location-warehouse-setting.png
-   :align: center
-   :alt: Enable the storage location feature in Odoo Inventory settings.
-
-.. important::
-   To manage several routes within the warehouses, also enable :guilabel:`Multi-Step Routes` and
-   check :doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes`.
-
-Create a new warehouse
-======================
-
-To create a warehouse, go to :menuselection:`Configuration --> Warehouse Management --> Warehouses`
-and click on :guilabel:`Create`.
-
-Then, fill out a :guilabel:`Warehouse Name` and a :guilabel:`Short Name`. The short name is five
-characters maximum.
-
-.. image:: warehouses_locations/create-new-warehouse.png
-   :align: center
-   :alt: Short name field of a warehouse on Odoo Inventory.
-
-.. important::
-   The :guilabel:`Short Name` appears on transfer orders and other warehouse documents. Odoo
-   recommends using an understandable one like "WH/[first letters of location]".
-
-Now, go back to the :guilabel:`Inventory` dashboard. There, new operations related to the newly
-created warehouse have been automatically generated.
-
-.. image:: warehouses_locations/new-transfer-types.png
-   :align: center
-   :alt: Inventory app dashboard displaying new transfer types for the recently created warehouse.
-
-.. note::
-   Adding a second warehouse will automatically activate the :guilabel:`Locations` setting.
-
-Create a new location
-=====================
-
-To create a location, go to :menuselection:`Configuration --> Warehouse Management --> Locations`
-and click on :guilabel:`Create`.
-
-Then, fill out a :guilabel:`Location Name` and a :guilabel:`Parent Location` and click
-:guilabel:`Save`.
-
-.. image:: warehouses_locations/create-new-location.png
-   :align: center
-   :alt: Create a new warehouse location in Odoo Inventory.
@@ -9,9 +9,9 @@ workspaces.

 .. seealso::
   - `Odoo Documents: product page <https://www.odoo.com/app/documents>`_
-   - `Odoo Tutorials: Documents basics <https://www.odoo.com/slides/slide/documents-basics-674>`_
+   - `Odoo Tutorials: Documents basics <https://www.odoo.com/slides/slide/documents-basics-6841?fullscreen=1>`_
   - `Odoo Tutorials: Using Documents with your Accounting App
-     <https://www.odoo.com/slides/slide/using-documents-with-your-accounting-app-675?fullscreen=1#>`_
+     <https://www.odoo.com/slides/slide/accounting-integration-and-workflow-actions-6853?fullscreen=1>`_

 Configuration
 =============
@@ -24,6 +24,12 @@ countries. The legal validity of electronic signatures generated by Odoo depends
 legislation. Companies doing business abroad should also consider other countries' electronic
 signature laws.

+.. important::
+   The below information has no legal value; it is only provided for general informational purposes.
+   As laws governing electronic signatures rapidly evolve, we cannot guarantee that all information
+   is up-to-date. We advise contacting a local attorney for legal advice regarding electronic
+   signature compliance and validity.
+
 European Union
 --------------

@@ -76,11 +82,19 @@ Overall, to be recognized as valid, electronic signatures have to meet five crit
   example, by providing the signer either a fully-executed copy or the possibility to download a
   copy.

-.. important::
-   The above information has no legal value; it is only provided for general informational purposes.
-   As laws governing electronic signatures rapidly evolve, we cannot guarantee that all information
-   is up-to-date. We advise contacting a local attorney for legal advice regarding electronic
-   signature compliance and validity.
+Other countries
+---------------
+
+- :doc:`Australia <sign/australia>`
+- :doc:`Brazil <sign/brazil>`
+- :doc:`Canada <sign/canada>`
+- :doc:`China <sign/china>`
+- :doc:`India <sign/india>`
+- :doc:`Japan <sign/japan>`
+- :doc:`Mexico <sign/mexico>`
+- :doc:`Russia <sign/russia>`
+- :doc:`South Korea <sign/south_korea>`
+- :doc:`United Kingdom <sign/united_kingdom>`

 Send a document to sign
 =======================
@@ -0,0 +1,72 @@
+:orphan:
+
+===============================
+Odoo Sign legality in Australia
+===============================
+
+:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
+electronic signatures in Australia.
+
+Legal framework for electronic signatures in Australia
+======================================================
+
+In Australia, electronic signatures are regulated under the `Electronic Transactions Act (ETA)
+<https://www.legislation.gov.au/C2004A00553/latest/text>`_, the `Electronic Transactions Regulations
+(ETR) <https://www.legislation.wa.gov.au/legislation/prod/filestore.nsf/FileURL/mrdoc_23907.pdf/$FILE/Electronic%20Transactions%20Regulations%202012%20-%20%5B00-a0-04%5D.pdf?OpenElement>`_
+and local regulations in each state. The law governs transactions performed through electronic means
+and the use of electronic signatures. The key points of the law include:
+
+- **Legal recognition**: electronic signatures are legally equivalent to handwritten signatures if
+  they meet certain criteria.
+- **Reliability and security**: electronic signatures must be created with a secure method that can
+  reliably identify the signatory and ensure the integrity of the signed document.
+
+How Odoo Sign complies with Australian regulations
+==================================================
+
+Odoo Sign ensures full compliance with the Electronic Signature Law of Australia by incorporating
+the following features:
+
+- **Secure signature creation**: Odoo Sign utilizes advanced cryptographic techniques to ensure the
+  authenticity and integrity of electronic signatures.
+- **Third-party signature authenticator**: Odoo Online serves as an independent validation mechanism
+  that adds an extra layer of security to the procurement process.
+- **Audit trails**: detailed audit logs are maintained to provide evidence of the signing process,
+  including timestamps, IP addresses, and identity verification.
+- **Cryptographic traceability and immutability**: Odoo Sign ensures that any operation is logged
+  securely. An audit log provides full transparency to all parties while preserving private data.
+- **Multiple authentication means**: authentication by SMS, email, geoIP or handwritten electronic
+  signature.
+
+Types of documents you can sign with Odoo Sign
+==============================================
+
+Odoo Sign is versatile and can be used for a wide range of documents, including but not limited to:
+
+- **Contracts and agreements**: business contracts, employment agreements, and service contracts.
+- **Financial documents**: loan agreements, investment documents, and financial reports.
+- **HR documents**: employee onboarding forms, non-disclosure agreements (NDAs), and performance
+  reviews.
+- **Commercial transactions**: purchase orders, sales agreements, and supplier contracts.
+
+Potential exceptions
+====================
+
+While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may
+not be suitable or legally recognized in Australia:
+
+- **Wills and trusts**: documents related to inheritance, wills, and trusts often require
+  handwritten signatures.
+- **Real estate transactions**: some property transactions may still require notarized handwritten
+  signatures.
+- **Government forms**: specific government forms and applications may mandate physical signatures.
+
+.. admonition:: Disclaimer
+
+   The information provided on this page is for general informational purposes only and does not
+   constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Australia,
+   users should consult with legal professionals to ensure specific document types and use cases
+   meet all legal requirements. Compliance with additional industry-specific regulations may also be
+   necessary.
+
+*Last updated: June 19, 2024*
@@ -0,0 +1,77 @@
+:orphan:
+
+============================
+Odoo Sign legality in Brazil
+============================
+
+:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
+electronic signatures in Brazil.
+
+Legal framework for electronic signatures in Brazil
+===================================================
+
+In Brazil, electronic signatures are regulated under the `Brazilian Civil Code <https://webfiles-sc1.blackbaud.com/files/support/helpfiles/npoconnect-qa/content/resources/attachments/brazil-law-civil-code-13.777-2018.pdf>`_
+and the Provisional Executive Act 2.200-2 (EA 2200) regulations. The law governs transactions
+performed through electronic means and the use of electronic signatures. The key points of the law
+include:
+
+- **Legal recognition**: electronic signatures are legally equivalent to handwritten signatures if
+  they meet certain criteria.
+- **Reliability and security**: electronic signatures must be created with a secure method that can
+  reliably identify the signatory and ensure the integrity of the signed document.
+- **Infraestrutura de Chaves Públicas Brasileira (ICP-Brazil)**: Brazil maintains its own public key
+  infrastructure (PKI) for digital certificates called “Infraestrutura de Chaves Públicas
+  Brasileira”. These are  digital signature certificates or “seals” that serve as proof of identity
+  of an individual for a certain purpose that can be used in special cases to provide additional
+  security. These certificates are issued by Certification Authorities and are required by law for
+  the signature of specific acts.
+
+How Odoo Sign complies with Brazilian regulations
+=================================================
+
+Odoo Sign ensures full compliance with the Electronic Signature Law of Brazil by incorporating the
+following features:
+
+- **Secure signature creation**: Odoo Sign utilizes advanced cryptographic techniques to ensure the
+  authenticity and integrity of electronic signatures.
+- **Third-party signature authenticator**: Odoo Online serves as an independent validation mechanism
+  that adds an extra layer of security to the procurement process.
+- **Audit trails**: detailed audit logs are maintained to provide evidence of the signing process,
+  including timestamps, IP addresses, and identity verification.
+- **Cryptographic traceability and immutability**: Odoo Sign ensures that any operation is logged
+  securely. An audit log provides full transparency to all parties while preserving private data.
+- **Multiple authentication means**: authentication by SMS, email, geoIP or handwritten electronic
+  signature.
+
+Types of documents you can sign with Odoo Sign
+==============================================
+
+Odoo Sign is versatile and can be used for a wide range of documents, including but not limited to:
+
+- **Contracts and agreements**: business contracts, employment agreements, and service contracts.
+- **Financial documents**: loan agreements, investment documents, and financial reports.
+- **HR documents**: employee onboarding forms, non-disclosure agreements (NDAs), and performance
+  reviews.
+- **Commercial transactions**: purchase orders, sales agreements, and supplier contracts.
+
+Potential exceptions
+====================
+
+While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may
+not be suitable or legally recognized in Brazil:
+
+- **Wills and trusts**: documents related to inheritance, wills, and trusts often require
+  handwritten signatures.
+- **Real estate transactions**: some property transactions may still require notarized handwritten
+  signatures.
+- **Government forms**: specific government forms and applications may mandate physical signatures.
+
+.. admonition:: Disclaimer
+
+   The information provided on this page is for general informational purposes only and does not
+   constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Brazil,
+   users should consult with legal professionals to ensure specific document types and use cases
+   meet all legal requirements. Compliance with additional industry-specific regulations may also be
+   necessary.
+
+*Last updated: June 19, 2024*
@@ -0,0 +1,75 @@
+:orphan:
+
+============================
+Odoo Sign legality in Canada
+============================
+
+:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
+electronic signatures in Canada.
+
+Legal framework for electronic signatures in Canada
+===================================================
+
+In Canada, electronic signatures are regulated under the `Personal Information Protection and
+Electronic Documents Act (PIPEDA) <https://laws-lois.justice.gc.ca/pdf/p-8.6.pdf>`_ and local
+regulations. The law establishes electronic equivalents to paper-based documents and signatures at
+the federal level. The key points of the law include:
+
+- **Legal recognition**: electronic signatures are legally equivalent to handwritten signatures if
+  they meet certain criteria.
+- **Reliability and security**: electronic signatures must be created with a secure method that can
+  reliably identify the signatory and ensure the integrity of the signed document.
+- **Secure electronic signature**: the law recognizes digital signature certificates or “seals” that
+  serve as proof of identity of an individual for a certain purpose that can be used in special
+  cases to provide additional security. These certificates are issued by Certification Authorities
+  and are required by law for the signature of specific acts.
+
+How Odoo Sign complies with Canadian regulations
+================================================
+
+Odoo Sign ensures full compliance with the Electronic Signature Law of Canada by incorporating the
+following features:
+
+- **Secure signature creation**: Odoo Sign utilizes advanced cryptographic techniques to ensure the
+  authenticity and integrity of electronic signatures.
+- **Third-party signature authenticator**: Odoo Online serves as an independent validation mechanism
+  that adds an extra layer of security to the procurement process.
+- **Audit trails**: detailed audit logs are maintained to provide evidence of the signing process,
+  including timestamps, IP addresses, and identity verification.
+- **Cryptographic traceability and immutability**: Odoo Sign ensures that any operation is logged
+  securely. An audit log provides full transparency to all parties while preserving private data.
+- **Multiple authentication means**: authentication by SMS, email, geoIP or handwritten electronic
+  signature.
+
+Types of documents you can sign with Odoo Sign
+==============================================
+
+Odoo Sign is versatile and can be used for a wide range of documents, including but not limited to:
+
+- **Contracts and agreements**: business contracts, employment agreements, and service contracts.
+- **Financial documents**: loan agreements, investment documents, and financial reports.
+- **HR documents**: employee onboarding forms, non-disclosure agreements (NDAs), and performance
+  reviews.
+- **Commercial transactions**: purchase orders, sales agreements, and supplier contracts.
+
+Potential exceptions
+====================
+
+While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may
+not be suitable or legally recognized in Canada:
+
+- **Wills and trusts**: documents related to inheritance, wills, and trusts often require
+  handwritten signatures.
+- **Real estate transactions**: some property transactions may still require notarized handwritten
+  signatures.
+- **Government forms**: specific government forms and applications may mandate physical signatures.
+
+.. admonition:: Disclaimer
+
+   The information provided on this page is for general informational purposes only and does not
+   constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Canada,
+   users should consult with legal professionals to ensure specific document types and use cases
+   meet all legal requirements. Compliance with additional industry-specific regulations may also be
+   necessary.
+
+*Last updated: June 19, 2024*
@@ -0,0 +1,66 @@
+:orphan:
+
+===========================
+Odoo Sign legality in China
+===========================
+
+:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in
+China.
+
+Legal framework for electronic signatures in China
+==================================================
+
+In China, electronic signatures are regulated under the Electronic Signature Law (ESL) of the People's Republic of
+China, enacted in 2005 and amended in 2015. The law provides the foundation for the use and legal recognition of
+electronic signatures. The key points of the ESL include:
+
+- **Legal recognition**: electronic signatures are legally equivalent to handwritten signatures if they meet certain
+  criteria.
+- **Reliability and security**: electronic signatures must be created with a secure method that can reliably identify
+  the signatory and ensure the integrity of the signed document.
+- **Certification Authorities (CAs)**: the law recognizes electronic signatures supported by digital certificates issued
+  by accredited Certification Authorities (CAs).
+
+How Odoo Sign complies with Chinese regulations
+===============================================
+
+Odoo Sign ensures full compliance with the Electronic Signature Law of China by incorporating the following features:
+
+- **Secure signature creation**: Odoo Sign utilizes advanced cryptographic techniques to ensure the authenticity and
+  integrity of electronic signatures.
+- **Third-party signature authenticator**: Odoo Online serves as an independent validation mechanism that adds an extra
+  layer of security to the procurement process.
+- **Audit trails**: detailed audit logs are maintained to provide evidence of the signing process, including timestamps,
+  IP addresses, and identity verification.
+- **Cryptographic traceability and immutability**: Odoo Sign ensures that any operation is logged securely. An audit log
+  provides full transparency to all parties while preserving private data.
+- **Multiple authentication means**: authentication by SMS, email, geoIP or handwritten electronic signature.
+
+Types of documents you can sign with Odoo Sign
+==============================================
+
+Odoo Sign is versatile and can be used for a wide range of documents, including but not limited to:
+
+- **Contracts and agreements**: business contracts, employment agreements, and service contracts.
+- **Financial documents**: loan agreements, investment documents, and financial reports.
+- **HR documents**: employee onboarding forms, non-disclosure agreements (NDAs), and performance reviews.
+- **Commercial transactions**: purchase orders, sales agreements, and supplier contracts.
+
+Potential exceptions
+====================
+
+While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or
+legally recognized in China:
+
+- **Wills and trusts**: documents related to inheritance, wills, and trusts often require handwritten signatures.
+- **Real estate transactions**: some property transactions may still require notarized handwritten signatures.
+- **Government forms**: specific government forms and applications may mandate physical signatures.
+
+.. admonition:: Disclaimer
+
+   The information provided on this page is for general informational purposes only and does not constitute legal
+   advice. While Odoo Sign complies with the Electronic Signature Law of China, users should consult with legal
+   professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional
+   industry-specific regulations may also be necessary.
+
+*Last updated: June 19, 2024*
@@ -0,0 +1,76 @@
+:orphan:
+
+===========================
+Odoo Sign legality in India
+===========================
+
+:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
+electronic signatures in India.
+
+Legal framework for electronic signatures in India
+==================================================
+
+In India, electronic signatures are regulated under the `Information Technology Act (ITA) <https://eprocure.gov.in/cppp/rulesandprocs/kbadqkdlcswfjdelrquehwuxcfmijmuixngudufgbuubgubfugbububjxcgfvsbdihbgfGhdfgFHytyhRtMjk4NzY=>`_,
+the `Indian Contract Act (ICA)
+<https://www.indiacode.nic.in/bitstream/123456789/2187/2/A187209.pdf>`_ and the Electronic Signature
+or Electronic Authentication Technique and Procedure Rules (ESEATPR). The law provides the
+foundation for the use and legal recognition of electronic signatures. The key points of the law
+include:
+
+- **Legal recognition**: electronic signatures are legally equivalent to handwritten signatures if
+  they meet certain criteria.
+- **Reliability and security**: electronic signatures must be created with a secure method that can
+  reliably identify the signatory and ensure the integrity of the signed document.
+- **Digital signature certificates**: the law recognizes digital signature certificates that serve
+  as proof of identity of an individual for a certain purpose that can be used in special cases to
+  provide additional security.
+
+How Odoo Sign complies with Indian regulations
+==============================================
+
+Odoo Sign ensures full compliance with the Electronic Signature Law of India by incorporating the
+following features:
+
+- **Secure signature creation**: Odoo Sign utilizes advanced cryptographic techniques to ensure the
+  authenticity and integrity of electronic signatures.
+- **Third-party signature authenticator**: Odoo Online serves as an independent validation mechanism
+  that adds an extra layer of security to the procurement process.
+- **Audit trails**: detailed audit logs are maintained to provide evidence of the signing process,
+  including timestamps, IP addresses, and identity verification.
+- **Cryptographic traceability and immutability**: Odoo Sign ensures that any operation is logged
+  securely. An audit log provides full transparency to all parties while preserving private data.
+- **Multiple authentication means**: authentication by SMS, email, geoIP or handwritten electronic
+  signature.
+
+Types of documents you can sign with Odoo Sign
+==============================================
+
+Odoo Sign is versatile and can be used for a wide range of documents, including but not limited to:
+
+- **Contracts and agreements**: business contracts, employment agreements, and service contracts.
+- **Financial documents**: loan agreements, investment documents, and financial reports.
+- **HR documents**: employee onboarding forms, non-disclosure agreements (NDAs), and performance
+  reviews.
+- **Commercial transactions**: purchase orders, sales agreements, and supplier contracts.
+
+Potential exceptions
+====================
+
+While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may
+not be suitable or legally recognized in India:
+
+- **Wills and trusts**: documents related to inheritance, wills, and trusts often require
+  handwritten signatures.
+- **Real estate transactions**: some property transactions may still require notarized handwritten
+  signatures.
+- **Government forms**: specific government forms and applications may mandate physical signatures.
+
+.. admonition:: Disclaimer
+
+   The information provided on this page is for general informational purposes only and does not
+   constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of India,
+   users should consult with legal professionals to ensure specific document types and use cases
+   meet all legal requirements. Compliance with additional industry-specific regulations may also be
+   necessary.
+
+*Last updated: June 19, 2024*
@@ -0,0 +1,73 @@
+:orphan:
+
+===========================
+Odoo Sign legality in Japan
+===========================
+
+:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
+electronic signatures in Japan.
+
+Legal framework for electronic signatures in Japan
+==================================================
+
+In Japan, electronic signatures are regulated under the `Act on Electronic Signatures and
+Certification Business (E-signature Act) <https://www.cas.go.jp/jp/seisaku/hourei/data/aescb.pdf>`_
+published in the official gazette on May 31, 2000. The law provides the foundation for the use and
+legal recognition of electronic signatures. The key points of the E-signature Act include:
+
+- **Legal recognition**: electronic signatures are legally equivalent to handwritten signatures if
+  they meet certain criteria.
+- **Reliability and security**: electronic signatures must be created with a secure method that can
+  reliably identify the signatory and ensure the integrity of the signed document.
+- **Certification Businesses (CBs)**: the law recognizes electronic signatures supported by digital
+  certificates issued by accredited CBs.
+
+How Odoo Sign complies with Japanese regulations
+================================================
+
+Odoo Sign ensures full compliance with the Electronic Signature Law of Japan by incorporating the
+following features:
+
+- **Secure signature creation**: Odoo Sign utilizes advanced cryptographic techniques to ensure the
+  authenticity and integrity of electronic signatures.
+- **Third-party signature authenticator**: Odoo Online serves as an independent validation mechanism
+  that adds an extra layer of security to the procurement process.
+- **Audit trails**: detailed audit logs are maintained to provide evidence of the signing process,
+  including timestamps, IP addresses, and identity verification.
+- **Cryptographic traceability and immutability**: Odoo Sign ensures that any operation is logged
+  securely. An audit log provides full transparency to all parties while preserving private data.
+- **Multiple authentication means**: authentication by SMS, email, geoIP or handwritten electronic
+  signature.
+
+Types of documents you can sign with Odoo Sign
+==============================================
+
+Odoo Sign is versatile and can be used for a wide range of documents, including but not limited to:
+
+- **Contracts and agreements**: business contracts, employment agreements, and service contracts.
+- **Financial documents**: loan agreements, investment documents, and financial reports.
+- **HR documents**: employee onboarding forms, non-disclosure agreements (NDAs), and performance
+  reviews.
+- **Commercial transactions**: purchase orders, sales agreements, and supplier contracts.
+
+Potential exceptions
+====================
+
+While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may
+not be suitable or legally recognized in Japan:
+
+- **Wills and trusts**: documents related to inheritance, wills, and trusts often require
+  handwritten signatures.
+- **Real estate transactions**: some property transactions may still require notarized handwritten
+  signatures.
+- **Government forms**: specific government forms and applications may mandate physical signatures.
+
+.. admonition:: Disclaimer
+
+   The information provided on this page is for general informational purposes only and does not
+   constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Japan,
+   users should consult with legal professionals to ensure specific document types and use cases
+   meet all legal requirements. Compliance with additional industry-specific regulations may also be
+   necessary.
+
+*Last updated: June 19, 2024*
@@ -0,0 +1,75 @@
+:orphan:
+
+============================
+Odoo Sign legality in Mexico
+============================
+
+:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
+electronic signatures in Mexico.
+
+Legal framework for electronic signatures in Mexico
+===================================================
+
+In Mexico, electronic signatures are regulated under the `Mexican Civil Code
+<https://www.diputados.gob.mx/LeyesBiblio/pdf/CCF.pdf>`_ and the `Commercial Code
+<http://www.ordenjuridico.gob.mx/Publicaciones/pdf/L222.pdf>`_, as well as the civil codes of each
+state. The law governs transactions performed through electronic means and the use of electronic
+signatures. The key points of the law include:
+
+- **Legal recognition**: electronic signatures are legally equivalent to handwritten signatures if
+  they meet certain criteria.
+- **Reliability and security**: electronic signatures must be created with a secure method that can
+  reliably identify the signatory and ensure the integrity of the signed document.
+- **NORMA Oficial Mexicana NOM-151-SCFI-2016 (NOM 151)**: establishes the requirements for the
+  conservation of data messages and digitization of documents with full guarantees of integrity. It
+  also establishes the certification and time stamping requirements for certain documents.
+
+How Odoo Sign complies with Mexican regulations
+===============================================
+
+Odoo Sign ensures full compliance with the Electronic Signature Law of Mexico by incorporating the
+following features:
+
+- **Secure signature creation**: Odoo Sign utilizes advanced cryptographic techniques to ensure the
+  authenticity and integrity of electronic signatures.
+- **Third-party signature authenticator**: Odoo Online serves as an independent validation mechanism
+  that adds an extra layer of security to the procurement process.
+- **Audit trails**: detailed audit logs are maintained to provide evidence of the signing process,
+  including timestamps, IP addresses, and identity verification.
+- **Cryptographic traceability and immutability**: Odoo Sign ensures that any operation is logged
+  securely. An audit log provides full transparency to all parties while preserving private data.
+- **Multiple authentication means**: authentication by SMS, email, geoIP or handwritten electronic
+  signature.
+
+Types of documents you can sign with Odoo Sign
+==============================================
+
+Odoo Sign is versatile and can be used for a wide range of documents, including but not limited to:
+
+- **Contracts and agreements**: business contracts, employment agreements, and service contracts.
+- **Financial documents**: loan agreements, investment documents, and financial reports.
+- **HR documents**: employee onboarding forms, non-disclosure agreements (NDAs), and performance
+  reviews.
+- **Commercial transactions**: purchase orders, sales agreements, and supplier contracts.
+
+Potential exceptions
+====================
+
+While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may
+not be suitable or legally recognized in Mexico:
+
+- **Wills and trusts**: documents related to inheritance, wills, and trusts often require
+  handwritten signatures.
+- **Real estate transactions**: some property transactions may still require notarized handwritten
+  signatures.
+- **Government forms**: specific government forms and applications may mandate physical signatures.
+
+.. admonition:: Disclaimer
+
+   The information provided on this page is for general informational purposes only and does not
+   constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Mexico,
+   users should consult with legal professionals to ensure specific document types and use cases
+   meet all legal requirements. Compliance with additional industry-specific regulations may also be
+   necessary.
+
+*Last updated: June 19, 2024*
@@ -0,0 +1,77 @@
+:orphan:
+
+============================
+Odoo Sign legality in Russia
+============================
+
+:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
+electronic signatures in Russia.
+
+Legal framework for electronic signatures in Russia
+===================================================
+
+In Russia, electronic signatures are regulated under the `Federal Law No. 63-FZ as of 6 April 2011
+"On electronic signature" <https://afyonluoglu.org/PublicWebFiles/e-imza/int-legislation/Russia-Federal%20Law%20on%20e-Signatures.pdf>`_
+and the `Civil Code of the Russian Federation
+<https://www.wto.org/english/thewto_e/acc_e/rus_e/wtaccrus58_leg_360.pdf>`_. The law provides the
+foundation for the use and legal recognition of electronic signatures. The key points of the law
+include:
+
+- **Legal recognition**: electronic signatures are legally equivalent to handwritten signatures if
+  they meet certain criteria.
+- **Reliability and security**: electronic signatures must be created with a secure method that can
+  reliably identify the signatory and ensure the integrity of the signed document.
+- **Qualified electronic signatures**: the law recognizes digital signature certificates that serve
+  as proof of identity of an individual for a certain purpose that can be used in special cases to
+  provide additional security. These certificates are issued by Certification Authorities and are
+  required by law for the signature of specific acts.
+
+How Odoo Sign complies with Russian regulations
+===============================================
+
+Odoo Sign ensures full compliance with the Electronic Signature Law of Russia by incorporating the
+following features:
+
+- **Secure signature creation**: Odoo Sign utilizes advanced cryptographic techniques to ensure the
+  authenticity and integrity of electronic signatures.
+- **Third-party signature authenticator**: Odoo Online serves as an independent validation mechanism
+  that adds an extra layer of security to the procurement process.
+- **Audit trails**: detailed audit logs are maintained to provide evidence of the signing process,
+  including timestamps, IP addresses, and identity verification.
+- **Cryptographic traceability and immutability**: Odoo Sign ensures that any operation is logged
+  securely. An audit log provides full transparency to all parties while preserving private data.
+- **Multiple authentication means**: authentication by SMS, email, geoIP or handwritten electronic
+  signature.
+
+Types of documents you can sign with Odoo Sign
+==============================================
+
+Odoo Sign is versatile and can be used for a wide range of documents, including but not limited to:
+
+- **Contracts and agreements**: business contracts, employment agreements, and service contracts.
+- **Financial documents**: loan agreements, investment documents, and financial reports.
+- **HR documents**: employee onboarding forms, non-disclosure agreements (NDAs), and performance
+  reviews.
+- **Commercial transactions**: purchase orders, sales agreements, and supplier contracts.
+
+Potential exceptions
+====================
+
+While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may
+not be suitable or legally recognized in Russia:
+
+- **Wills and trusts**: documents related to inheritance, wills, and trusts often require
+  handwritten signatures.
+- **Real estate transactions**: some property transactions may still require notarized handwritten
+  signatures.
+- **Government forms**: specific government forms and applications may mandate physical signatures.
+
+.. admonition:: Disclaimer
+
+   The information provided on this page is for general informational purposes only and does not
+   constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Russia,
+   users should consult with legal professionals to ensure specific document types and use cases
+   meet all legal requirements. Compliance with additional industry-specific regulations may also be
+   necessary.
+
+*Last updated: June 19, 2024*
@@ -0,0 +1,75 @@
+:orphan:
+
+=================================
+Odoo Sign legality in South Korea
+=================================
+
+:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
+electronic signatures in South Korea.
+
+Legal framework for electronic signatures in South Korea
+========================================================
+
+In South Korea, electronic signatures are regulated under the `Digital Signature Act <https://elaw.klri.re.kr/eng_mobile/viewer.do?hseq=61440&type=part&key=28#:~:text=The%20purpose%20of%20this%20Act,infrastructure%20for%20facilitating%20the%20use>`_
+and the `Framework Act on Electronic Documents and Transactions of Korea <https://elaw.klri.re.kr/eng_mobile/viewer.do?hseq=61440&type=part&key=28#:~:text=The%20purpose%20of%20this%20Act,infrastructure%20for%20facilitating%20the%20use>`_.
+The law governs transactions performed through electronic means and the use of electronic
+signatures. The key points of the law include:
+
+- **Legal recognition**: electronic signatures are legally equivalent to handwritten signatures if
+  they meet certain criteria.
+- **Reliability and security**: electronic signatures must be created with a secure method that can
+  reliably identify the signatory and ensure the integrity of the signed document.
+- **Electronic signature certification services**: the law recognizes digital signature certificates
+  or “seals” that serve as proof of identity of an individual for a certain purpose that can be used
+  in special cases to provide additional security. These certificates are issued by Certification
+  Authorities and are required by law for the signature of specific acts.
+
+How Odoo Sign complies with South Korean regulations
+====================================================
+
+Odoo Sign ensures full compliance with the Electronic Signature Law of South Korea by incorporating
+the following features:
+
+- **Secure signature creation**: Odoo Sign utilizes advanced cryptographic techniques to ensure the
+  authenticity and integrity of electronic signatures.
+- **Third-party signature authenticator**: Odoo Online serves as an independent validation mechanism
+  that adds an extra layer of security to the procurement process.
+- **Audit trails**: detailed audit logs are maintained to provide evidence of the signing process,
+  including timestamps, IP addresses, and identity verification.
+- **Cryptographic traceability and immutability**: Odoo Sign ensures that any operation is logged
+  securely. An audit log provides full transparency to all parties while preserving private data.
+- **Multiple authentication means**: authentication by SMS, email, geoIP or handwritten electronic
+  signature.
+
+Types of documents you can sign with Odoo Sign
+==============================================
+
+Odoo Sign is versatile and can be used for a wide range of documents, including but not limited to:
+
+- **Contracts and agreements**: business contracts, employment agreements, and service contracts.
+- **Financial documents**: loan agreements, investment documents, and financial reports.
+- **HR documents**: employee onboarding forms, non-disclosure agreements (NDAs), and performance
+  reviews.
+- **Commercial transactions**: purchase orders, sales agreements, and supplier contracts.
+
+Potential exceptions
+====================
+
+While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may
+not be suitable or legally recognized in South Korea:
+
+- **Wills and trusts**: documents related to inheritance, wills, and trusts often require
+  handwritten signatures.
+- **Real estate transactions**: some property transactions may still require notarized handwritten
+  signatures.
+- **Government forms**: specific government forms and applications may mandate physical signatures.
+
+.. admonition:: Disclaimer
+
+   The information provided on this page is for general informational purposes only and does not
+   constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of South
+   Korea, users should consult with legal professionals to ensure specific document types and use
+   cases meet all legal requirements. Compliance with additional industry-specific regulations may
+   also be necessary.
+
+*Last updated: June 19, 2024*
@@ -0,0 +1,79 @@
+:orphan:
+
+========================================
+Odoo Sign legality in the United Kingdom
+========================================
+
+:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
+electronic signatures in the United Kingdom.
+
+Legal framework for electronic signatures in the United Kingdom
+===============================================================
+
+In the United Kingdom, electronic signatures are regulated under Electronic Communications Act
+(ECA), and the `UK version <https://ico.org.uk/for-organisations/guide-to-eidas/>`_ of Regulation
+(EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic
+identification and trust services for electronic transactions in the internal market (eIDAS) as
+amended by the `Electronic Identification and Trust Services for Electronic Transactions
+<https://www.legislation.gov.uk/uksi/2019/89/made>`_ (Amendment) (EU Exit) Regulations 2019 (SI
+2019/89) (the “UK eIDAS Regulation”). The law provides the foundation for the use and legal
+recognition of electronic signatures. The key points of the law include:
+
+- **Legal recognition**: electronic signatures are legally equivalent to handwritten signatures if
+  they meet certain criteria.
+- **Reliability and security**: electronic signatures must be created with a secure method that can
+  reliably identify the signatory and ensure the integrity of the signed document.
+- **Digital signature certificates**: the law recognizes digital signature certificates that serve
+  as proof of identity of an individual for a certain purpose that can be used in special cases to
+  provide additional security. These certificates are issued by Certification Authorities and are
+  required by law for the signature of specific acts.
+
+How Odoo Sign complies with the United Kingdom regulations
+==========================================================
+
+Odoo Sign ensures full compliance with the Electronic Signature Law of the United Kingdom by
+incorporating the following features:
+
+- **Secure signature creation**: Odoo Sign utilizes advanced cryptographic techniques to ensure the
+  authenticity and integrity of electronic signatures.
+- **Third-party signature authenticator**: Odoo Online serves as an independent validation mechanism
+  that adds an extra layer of security to the procurement process.
+- **Audit trails**: detailed audit logs are maintained to provide evidence of the signing process,
+  including timestamps, IP addresses, and identity verification.
+- **Cryptographic traceability and immutability**: Odoo Sign ensures that any operation is logged
+  securely. An audit log provides full transparency to all parties while preserving private data.
+- **Multiple authentication means**: authentication by SMS, email, geoIP or handwritten electronic
+  signature.
+
+Types of documents you can sign with Odoo Sign
+==============================================
+
+Odoo Sign is versatile and can be used for a wide range of documents, including but not limited to:
+
+- **Contracts and agreements**: business contracts, employment agreements, and service contracts.
+- **Financial documents**: loan agreements, investment documents, and financial reports.
+- **HR documents**: employee onboarding forms, non-disclosure agreements (NDAs), and performance
+  reviews.
+- **Commercial transactions**: purchase orders, sales agreements, and supplier contracts.
+
+Potential exceptions
+====================
+
+While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may
+not be suitable or legally recognized in the United Kingdom:
+
+- **Wills and trusts**: documents related to inheritance, wills, and trusts often require
+  handwritten signatures.
+- **Real estate transactions**: some property transactions may still require notarized handwritten
+  signatures.
+- **Government forms**: specific government forms and applications may mandate physical signatures.
+
+.. admonition:: Disclaimer
+
+   The information provided on this page is for general informational purposes only and does not
+   constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of the United
+   Kingdom, users should consult with legal professionals to ensure specific document types and use
+   cases meet all legal requirements. Compliance with additional industry-specific regulations may
+   also be necessary.
+
+*Last updated: June 19, 2024*
@@ -9,9 +9,9 @@ Odoo VoIP (Voice over Internet Protocol) can be set up to work together with `Ax
 <https://www.axivox.com/>`_. In that case, an Asterisk server is **not** necessary, as the
 infrastructure is hosted and managed by Axivox.

-To use this service, `contact Axivox <https://www.axivox.com/contact/>`_ to open an account. Before
-doing so, verify that Axivox covers the company's area, along with the areas the company's users
-wish to call.
+To use this service, `contact Axivox <https://www.axivox.com/en/contact/>`_ to open an account.
+Before doing so, verify that Axivox covers the company's area, along with the areas the company's
+users wish to call.

 Configuration
 =============
@@ -32,7 +32,6 @@ The following ePOS printers are directly compatible with Odoo without needing an
 - Epson TM-T70II-DT
 - Epson TM-T88V-DT
 - Epson TM-L90-i
- Epson TM-T20II-i
 - Epson TM-T70-i
 - Epson TM-T82II-i
 - Epson TM-T83II-i
@@ -6,8 +6,8 @@ Connecting a Vantiv payment terminal allows you to offer a fluid payment flow to
 ease the work of your cashiers.

 .. note::
-   Please note MercuryPay only operates with US and Canadian banks, making
-   this procedure only suitable for North American businesses.
+   Please note MercuryPay only operates with US and Canadian banks, making this procedure only
+   suitable for North American businesses.

 .. warning::
   Vantiv card readers should be purchased exclusively from Vantiv, as certain Vantiv terminals
@@ -16,35 +16,30 @@ ease the work of your cashiers.
 Configuration
 =============

-Configure the Payment Method
+Configure the payment method
 ----------------------------

-First, go in the general settings of the POS app, and activate the
-Vantiv setting.
+Enable the payment terminal in the :guilabel:`Payment Terminals` section :ref:`of the application
+settings <configuration/settings>`.

-.. image:: vantiv/vantiv_01.png
-    :align: center
+Then, go to :menuselection:`Point of Sale --> Configuration --> Payment Methods`, and :doc:`create
+the related payment method <../../payment_methods>`. Set the journal type as :guilabel:`Bank` and
+select :guilabel:`Vantiv` in the :guilabel:`Use a Payment Terminal` field.

-Back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, go in the
-payments section and access your payment methods. Create a new payment
-method for Vantiv, select the payment terminal option Vantiv, and create
-new Vantiv credentials.
+Type the name you want to give to your :guilabel:`Vantiv Credentials` and click :guilabel:`Create
+and edit`. Enter your :guilabel:`Merchant ID` and :guilabel:`Merchant Password`, then click
+:guilabel:`Save & Close`.

-.. image:: vantiv/vantiv_02.png
-    :align: center
+.. image:: vantiv/vantiv-method.png
+   :alt: Vantiv payment method

-To create new Vantiv credentials, fill in your merchant ID and password,
-then save. Make sure the credentials you just created are selected, then
-save the payment method.
+Once the payment method is created, you can select it in your POS settings. To do so, go to the
+:ref:`POS' settings <configuration/settings>` and add the payment method under the
+:guilabel:`Payment` section.

-.. image:: vantiv/vantiv_03.png
-    :align: center
-
-Pay with a Payment Terminal
+Pay with a payment terminal
 ===========================

-In your PoS interface, at the moment of the payment, select your Vantiv
-payment method and… that’s all.
-
-.. image:: vantiv/vantiv_04.png
-    :align: center
+When processing a payment, select the related payment method. Check the amount and click on
+:guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment
+Successful`.
@@ -26,7 +26,7 @@ Once activated, you can:

 .. seealso::
   - :doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method`
-   - :doc:`../../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations`
+   - :doc:`../../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses`

 Practical application
 =====================
@@ -60,6 +60,18 @@ The following table lists capabilities provided by Odoo when using the Amazon Co
 |                           |                            | status synchronized from Odoo.      |
 +---------------------------+----------------------------+-------------------------------------+

+.. important::
+   The stock synchronization does **not** currently support selling the same product as :abbr:`FBM
+   (Fulfilled By Merchant)` *and* :abbr:`FBA (Fulfilled By Amazon)`.
+
+   At times, when stock is sent for all products, it triggers a stock problem with Amazon, where
+   Amazon incorrectly thinks the :abbr:`FBM (Fulfilled By Merchant)` product has some quantity in
+   :abbr:`FBM (Fulfilled By Merchant)`.
+
+   As a result, Amazon then sells it as :abbr:`FBM (Fulfilled By Merchant)`, instead of taking from
+   their own warehouse. Odoo developers are currently working on resolving this issue to avoid
+   future discrepancies.
+
 .. note::
   The Amazon Connector is designed to synchronize the data of sales orders. Other actions, such as
   downloading monthly fees reports, handling disputes, or issuing refunds, **must** be managed from
@@ -16,6 +16,18 @@ For *FBM* (Fulfilled by Merchant), the same is done for *Unshipped* and *Cancele
 synchronized order, a sales order and customer are created in Odoo (if the customer is not already
 registered in the database).

+.. important::
+   The stock synchronization does **not** currently support selling the same product as :abbr:`FBM
+   (Fulfilled By Merchant)` *and* :abbr:`FBA (Fulfilled By Amazon)`.
+
+   At times, when stock is sent for all products, it triggers a stock problem with Amazon, where
+   Amazon incorrectly thinks the :abbr:`FBM (Fulfilled By Merchant)` product has some quantity in
+   :abbr:`FBM (Fulfilled By Merchant)`.
+
+   As a result, Amazon then sells it as :abbr:`FBM (Fulfilled By Merchant)`, instead of taking from
+   their own warehouse. Odoo developers are currently working on resolving this issue to avoid
+   future discrepancies.
+
 .. note::
   When an order is canceled in Amazon, and was already synchronized in Odoo, the corresponding
   sales order is automatically canceled in Odoo.
@@ -16,7 +16,7 @@ Configuration
 =============

 To set up a user default warehouse, the :doc:`storage locations
-</applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations>`
+<../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations>`
 feature needs to be activated in the **Inventory** app. It is also necessary to have more than one
 warehouse in your database.

@@ -24,7 +24,7 @@ You can either set it up :ref:`for your profile <default-warehouse/my-profile>`,
 users <default-warehouse/all-users>`.

 .. seealso::
-   :doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations`
+   :doc:`../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations`

 .. _default-warehouse/my-profile:

@@ -13,19 +13,27 @@ Studio
   studio/models_modules_apps
   studio/automated_actions
   studio/pdf_reports
+   studio/approval_rules

 Studio is a toolbox that allows you to customize Odoo without coding knowledge. For example, you
-can, on any app, add or modify:
+can, in any app, add or modify:

 - :doc:`Fields <studio/fields>`
 - :doc:`Views <studio/views>`
 - :doc:`Models <studio/models_modules_apps>`
 - :doc:`Automated actions <studio/automated_actions>`
 - :doc:`PDF reports <studio/pdf_reports>`
- Approval rules
+- :doc:`Approval rules <studio/approval_rules>`
 - Security rules

-Or you can :doc:`build an app from scratch <studio/models_modules_apps>`.
+You can also :doc:`build an app from scratch <studio/models_modules_apps>`.
+
+.. _studio/access:
+
+To access Studio, navigate to the app and model you want to modify, then click the **Toggle Studio**
+button, or vice versa.
+
+To close Studio, click :guilabel:`Close` in the upper right corner.

 .. seealso::
-   - `Odoo Tutorials: Studio <https://www.odoo.com/slides/studio-31>`_
+   `Odoo Tutorials: Studio <https://www.odoo.com/slides/studio-31>`_
@@ -0,0 +1,73 @@
+==============
+Approval rules
+==============
+
+Studio approval rules are used to automate approval processes for actions. They allow you to define
+the criteria for when an approval is required before an action can be performed using a button.
+
+Configuration
+=============
+
+To add approval rules, proceed as follows:
+
+#. :ref:`Open Studio <studio/access>` and switch to the required :doc:`view <views>`.
+#. Select the button for which you want to add approval rules.
+#. In the :guilabel:`Properties` tab on the left, enable the :guilabel:`Set approval rules`
+   feature.
+#. Specify the :guilabel:`Approval Group` to limit the approval permission to a specific user
+   group.
+#. Define the :guilabel:`Responsible` user to create an activity for a specific user when an
+   approval is requested from them.
+#. Add a :guilabel:`Description` to be displayed in the :ref:`Approval dialog <approval-rules/use>`.
+#. Enable :guilabel:`Limit approver to this rule` to require approvers to be different users (when
+   there are multiple approval rules).
+
+Optionally, you can also add conditions for the approval rule to be applied by clicking the
+:icon:`fa-filter` (:guilabel:`filter`) icon next to the :guilabel:`Approval Group` field.
+
+Click :guilabel:`Add an approval rule` to add another rule.
+
+Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the :guilabel:`Approval group` field to
+delete the approval rule.
+
+.. tip::
+   You can create :ref:`user groups <access-rights/groups>` specifically for approvals.
+
+.. _approval-rules/use:
+
+Use
+===
+
+Once approval rules have been defined for a button:
+
+- A **user avatar** icon is displayed next to the button's label for each approval rule that has
+  been defined.
+
+   .. image:: approval_rules/approvals-button.png
+      :alt: Confirm button with approval for purchase orders
+
+- When an unauthorized user clicks the button, an error message is displayed in the top-right corner
+  and an activity is created for the user specified in the :guilabel:`Responsible` field.
+- Only users from the group defined in the :guilabel:`Approval Group` field are allowed to approve
+  or reject the action.
+
+Authorized users can:
+
+- approve and perform the action by clicking the button;
+- approve the action and allow another user to perform it by clicking the **user avatar** icon next
+  to the button's label, then clicking the :icon:`fa-check` (:guilabel:`Approve`) button in the
+  dialog that opens.
+- reject the action by clicking the **user avatar** icon next to the button's label, then clicking
+  the :icon:`fa-times` (:guilabel:`Reject`) button in the dialog that opens.
+
+.. image:: approval_rules/approvals-awaiting.png
+   :alt: Approval dialog
+
+.. tip::
+   - The user who approved/rejected the action can revoke their decision by clicking the **user
+     avatar** icon next to the button's label, then clicking the :icon:`fa-undo`
+     (:guilabel:`Revoke`) button.
+   - Approvals are tracked in the record's chatter. An approval entry is also created every time
+     a Studio approval-related action is performed. To access the approval entries, :doc:`activate
+     the developer mode </applications/general/developer_mode>` and go to :menuselection:`Settings
+     --> Technical --> Studio Approval Entries`.
@@ -2,75 +2,56 @@
 Cookies bar
 ===========

-Cookies are small text files sent to your device when you visit a website. They are processed and
-stored by your browser and contain information about your visit, such as login data, location,
-language, etc. There are two main types of cookies:
+**Cookies** are small text files sent to your device when you visit a website. They are processed
+and stored by your browser and track user information like login details, preferences, and browsing
+history. **Essential cookies** are necessary for the website to function, while **optional cookies**
+are used to analyze behavior or display ads.

- Essential cookies, which are necessary for the website to function properly;
- Non-essential or optional cookies, which are used to analyze your behavior or display
-  advertisements.
-
-.. image:: cookies_bar/popup.png
-   :width: 500
-   :alt: Example of a cookies bar with the popup layout.
-
-Notifying users about data collection, as well as its methods and purposes, is required by data
-protection laws such as `GDPR <https://gdpr.eu>`_. Cookies bars are commonly used to fulfill this
-obligation in a user-friendly and transparent manner. They are displayed immediately upon a user's
-first visit to inform them that the website uses cookies and let them decide whether they want to
-store non-essential cookies on their device.
+Data protection laws require notifying users about data collection methods and purposes.
+**Cookies bar** fulfill this obligation by informing users on their first visit and allowing them to
+decide whether to store all or only essential cookies on their device.

 Configuration
 =============

-To enable the cookies bar on your Odoo website, go to :menuselection:`Website --> Configuration` and
-enable :guilabel:`Cookies Bar` in the :guilabel:`Privacy` section.
+To enable the cookies bar on your website, go to :menuselection:`Website --> Configuration -->
+Settings` and enable :guilabel:`Cookies Bar` in the :guilabel:`Privacy` section.

-You can :ref:`customize the appearance of your cookies bar <cookies-bar/customization>` and :ref:`edit the content of
-the related Cookie Policy page <cookies-bar/policy>`.
+.. note::
+   The :ref:`Cookies Policy <cookies-bar/policy>` page (/cookie-policy`) is automatically created
+   when you enable the cookies bar.

 .. _cookies-bar/customization:

 Customization
 =============

-To adapt the display of the cookies bar, click :guilabel:`Edit` and select the :guilabel:`Cookies
-Bar` building block in the :guilabel:`Invisible Elements` at the bottom of the panel. Customize it
-using the options in the :guilabel:`Customize` tab in the edit panel. Three :guilabel:`Layouts` are
-available:
+To adapt the display of the cookies bar, click :guilabel:`Edit`, go to the
+:guilabel:`Invisible Elements` section at the bottom of the panel, and click
+:guilabel:`Cookies Bar`. You can modify the :guilabel:`Layout` and :guilabel:`Size` of the
+cookies bar, and enable :guilabel:`Backdrop` to gray out the page in the background when the cookies
+bar is displayed on the screen.

- :guilabel:`Discrete`: thin bar
- :guilabel:`Classic`: banner
- :guilabel:`Popup`: you can change the popup's :guilabel:`Position` to the :guilabel:`Top`,
-  :guilabel:`Middle`, or :guilabel:`Bottom` of the screen.
-
-You can also:
-
- modify the :guilabel:`Size` of the cookies bar;
- enable :guilabel:`Backdrop` to gray out the page in the background when the cookies bar is
-  displayed on the screen;
- further customize the appearance of the cookies bar using :guilabel:`Block` and/or
-  :guilabel:`Column` customization options, which are available after clicking anywhere in the
-  building block.
+Click anywhere in the building block to further customize the appearance of the cookies bar using
+:guilabel:`Block`, :guilabel:`Column` and/or :guilabel:`Inline Text` customization options.

 To edit the contents of the cookies bar (i.e., the consent message), click directly in the building
 block.

-.. image:: cookies_bar/customization.png
-   :alt: Odoo Website's edit panel to customize the cookies bar.
-
 .. _cookies-bar/policy:

-Cookie policy
-=============
+Cookies policy
+==============

 When you enable the cookies bar for your website, Odoo creates the **Cookie Policy** page
-(`/cookie-policy`) with the list of essential and optional cookies. To access it, click the
-:guilabel:`Cookie Policy` hyperlink in the cookies bar or open the page from :menuselection:`Website
--> Site --> Pages`.
+(`/cookie-policy`) containing a non-exhaustive list of cookies, with their purpose and examples. To
+access it, click the :guilabel:`Cookie Policy` hyperlink in the cookies bar or open the page from
+:menuselection:`Website --> Site --> Pages`.

-The contents of the page can be adapted based on your website's features and characteristics if
-needed.
+To adapt the content of the page according to your needs, click the :guilabel:`Edit` button.

 .. tip::
-   You could add a link providing access to this page, in your website's footer, for example.
+   You could add a link to this page in your website's footer, for example.
+
+.. seealso::
+   :doc:`Pages <../pages>`
@@ -2,94 +2,109 @@
 Translations
 ============

-The contents of your website pages (i.e., text strings) can be translated into different languages
-directly on your website.
+Your website is displayed in the language that matches your visitor’s browser. If the browser’s
+language has not been installed and added to your website, the content is shown in the
+:ref:`default language <translate/default-language>`. When additional languages are installed, users
+can choose their preferred language using the :ref:`language selector <translate/language-selector>`.

-Your website is displayed in the language that matches the visitor's browser's language, unless that
-particular language has not been installed. In this case, the website is displayed in the
-:ref:`default language <translate/default-language>`. The visitor can still select another language
-in the language menu.
+The :ref:`Translate <translate/translate>` feature on your website allows automatic translation of
+standard terms and provides a tool for manual content translation.

-Installing languages
-====================
+Install languages
+=================

-To translate your website, you first have to add the required languages:
+To allow translation of your website, you must first :doc:`install <../../../general/users/language>`
+the required languages and add them to your website. To do so, go to :menuselection:`Website -->
+Configuration --> Settings` and click :guilabel:`Install languages` in the :guilabel:`Website info`
+section. In the dialog box that opens, select the :guilabel:`Languages` you want from the dropdown
+menu, tick the required :guilabel:`Websites to translate`, and click :guilabel:`Add`.

-#. Go to your website.
-#. Scroll to the bottom of the page to the **language menu**.
-#. Click the language and select :guilabel:`Add a language`.
-
-   .. image:: translate/website-add-language.png
-      :alt: Add a language to your website.
-
-#. Click the :guilabel:`Languages` field and select the required language from the drop-down list.
-   Repeat this step for each additional language.
-#. Click the :guilabel:`Add` button.
+To edit your website's languages, go to :menuselection:`Website –> Configuration –> Settings` and
+add/remove the required languages in/from the :guilabel:`Languages` field in the
+:guilabel:`Website info` section.

 .. tip::
-   You can also edit your website's languages from the backend, in the :guilabel:`Settings`. Go to
-   :menuselection:`Website –> Configuration –> Settings` and add/remove the required languages in
-   the :guilabel:`Languages` field, in the :guilabel:`Website info` section.
+   Alternatively, once the languages have been installed, you can add them from the :ref:`language
+   selector <translate/language-selector>`. You might then need to refresh your page to see the new
+   language.

 .. _translate/default-language:

 Default language
 ----------------

-If the language of the visitor's browser is not installed on your website, the content is displayed
-in the default language.
-
-To define a default language, go to :menuselection:`Website –> Configuration –> Settings`, and
-select a language in the :guilabel:`Default` field.
+When multiple languages are available on your website, you can set a default language to be used if
+the visitor’s browser language is not available. To do so, go to :menuselection:`Website –->
+Configuration -–> Settings`, and select a language in the :guilabel:`Default` field.

 .. note::
-   This field is visible only if multiple languages are already configured for your website.
+   This field is only visible if multiple languages have been installed and added to your website.

-Translating the contents
-========================
+.. _translate/language-selector:

-Once the languages have been added, you can translate the contents of your website. To do so, go to
-your website, select the language from the language menu and click the :guilabel:`Translate` button
-on the right part of the task bar to activate the **translation mode**.
+Language selector
+=================

-.. image:: translate/translate-button.png
-   :alt: Translate button
+Your website’s visitors can switch languages using the language selector, available by default in
+the :guilabel:`Copyright` section at the bottom of the page. To edit the language selector menu:

-As a result:
+#. Go to your website and click :guilabel:`Edit`;
+#. Click the language selector available in the :guilabel:`Copyright` block and go to the
+   :guilabel:`Copyright` section of the website builder;
+#. Set the :guilabel:`Language selector` field to either :guilabel:`Dropdown` or :guilabel:`Inline`.
+   Click :guilabel:`None` if you do not want to display the  :guilabel:`Language selector`;

- Text strings that have already been translated are highlighted in green;
- Text strings that need to be translated are highlighted in yellow.
-
-.. image:: translate/website-translation-yellow.png
-   :alt: Text to be translated highlighted in yellow
-
-You can then replace the original text with the translation by clicking the block, editing its
-contents and saving.
-
-.. tip::
-   - Once the languages have been installed, you can also translate some items (e.g.,
-     the product's name and description) from the backend (e.g., in the product template). To do so,
-     click the language code (e.g., :guilabel:`EN`) next to the text you want to translate (e.g.,
-     the product name) and add the translation.
-
-     .. image:: translate/product-translation.png
-        :alt: Translate product-related items.
-
-   - You can also :doc:`export/import translations <../../../../developer/howtos/translations>`
-     to translate multiple items (e.g., product names and descriptions) in one go.
-
-Language selector menu
-======================
-
-To add a language selector menu:
-
-#. Go to your website and click :guilabel:`Edit`.
-#. Select the block where you want to add the language selector menu (e.g., the header).
-#. Select the :guilabel:`Customize` tab.
-#. In the :guilabel:`Navbar` section, set the :guilabel:`Language selector` field to either
-   :guilabel:`Dropdown` or :guilabel:`Inline`.
-
-   .. image:: translate/language-selector.png
-      :alt: Add a language selector menu.
+     .. image:: translate/language-selector.png
+        :alt: Add a language selector menu.

 #. Click :guilabel:`Save`.
+
+.. tip::
+  You can also add the :guilabel:`Language Selector` to the :guilabel:`Header` of your page. To do
+  so, click the :guilabel:`Header` block and go to the :guilabel:`Navbar` section to edit the
+  :guilabel:`Language Selector`.
+
+.. _translate/translate:
+
+Translate your website
+======================
+
+Select your desired language from the language selector to see your content in another language.
+Then, click the :guilabel:`Translate` button in the top-right corner to manually activate the
+translation mode so that you can translate what has not been translated automatically by Odoo.
+
+Translated text strings are highlighted in green; text strings that were not translated
+automatically are highlighted in yellow.
+
+.. image:: translate/translated-text.png
+  :alt: Entering the translation mode
+
+In this mode, you can only translate text. To change the page's structure, you must edit the master
+page, i.e., the page in the original language of the database. Any changes made to the master page
+are automatically applied to all translated versions.
+
+To replace the original text with the translation, click the block, edit its contents, and save.
+
+.. note::
+  When a website supports multiple languages, the content is accessible through different URLs,
+  depending on the language selected. For example,
+  `https://www.mywebsite.com/shop/product/my-product-1` is the URL to the master page, in English,
+  while `https://www.mywebsite.com/fr_FR/shop/product/mon-produit-1` is the URL to the French
+  version of the same page.
+
+.. tip::
+  Once the desired language is installed, you can translate some items from the backend (e.g., the
+  product's name in the product form). To do so, click the language code (e.g., :guilabel:`EN`) next
+  to the text you want to translate and add the translation.
+
+Content visibility by language
+------------------------------
+
+You can hide content (such as images or videos, for example) depending on the language. To do so:
+
+#. Click :guilabel:`Edit` and select an element of your website;
+#. Go to the :guilabel:`Text - Image` section and :guilabel:`Visibility`;
+#. Click :guilabel:`No condition` and select :guilabel:`Conditionally` instead;
+#. Go to :guilabel:`Languages` to configure the condition(s) to apply by selecting
+   :guilabel:`Visible for` or :guilabel:`Hidden for`, and click :guilabel:`Choose a record` to
+   decide which languages are impacted.
@@ -16,7 +16,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2024-05-30 07:20+0000\n"
+"POT-Creation-Date: 2024-06-21 15:46+0000\n"
 "PO-Revision-Date: 2023-01-13 14:30+0000\n"
 "Last-Translator: Wil Odoo, 2024\n"
 "Language-Team: Arabic (https://app.transifex.com/odoo/teams/41243/ar/)\n"
@@ -575,8 +575,8 @@ msgid "Deactivated features"
 msgstr "الخصائص المعطلة "

 #: ../../content/administration/neutralized_database.rst:24
-msgid "Here is a non-exhaustive list of the deactivated parameters:"
-msgstr "فيما يلي قائمة غير شاملة بالمعايير المعطلة: "
+msgid "Here is a non-exhaustive list of the deactivated features:"
+msgstr ""

 #: ../../content/administration/neutralized_database.rst:26
 msgid ""
@@ -606,7 +606,11 @@ msgstr "طرق التوصيل "
 msgid ":abbr:`IAP (In-App Purchase)` tokens"
 msgstr "رموز :abbr:`IAP (عمليات الشراء داخل التطبيق)` "

-#: ../../content/administration/neutralized_database.rst:34
+#: ../../content/administration/neutralized_database.rst:32
+msgid "website visibility (prevent search engines from indexing your site)"
+msgstr ""
+
+#: ../../content/administration/neutralized_database.rst:35
 msgid ""
 "**A red banner at the top of the screen is displayed on the neutralized "
 "database so that it can be seen immediately.**"
@@ -6760,9 +6764,9 @@ msgstr ""
 #: ../../content/administration/on_premise/source.rst:176
 #: ../../content/administration/on_premise/source.rst:204
 #: ../../content/administration/on_premise/source.rst:235
-#: ../../content/administration/on_premise/source.rst:320
-#: ../../content/administration/on_premise/source.rst:389
-#: ../../content/administration/on_premise/source.rst:452
+#: ../../content/administration/on_premise/source.rst:325
+#: ../../content/administration/on_premise/source.rst:394
+#: ../../content/administration/on_premise/source.rst:457
 msgid "Windows"
 msgstr "Windows"

@@ -6781,8 +6785,8 @@ msgstr ""
 #: ../../content/administration/on_premise/source.rst:195
 #: ../../content/administration/on_premise/source.rst:224
 #: ../../content/administration/on_premise/source.rst:267
-#: ../../content/administration/on_premise/source.rst:380
-#: ../../content/administration/on_premise/source.rst:442
+#: ../../content/administration/on_premise/source.rst:385
+#: ../../content/administration/on_premise/source.rst:447
 msgid "Linux"
 msgstr "Linux"

@@ -7324,7 +7328,7 @@ msgstr ""
 "الأمر التالي لتثبيت خادم PostgreSQL: "

 #: ../../content/administration/on_premise/packages.rst:57
-#: ../../content/administration/on_premise/source.rst:412
+#: ../../content/administration/on_premise/source.rst:417
 msgid ""
 "`wkhtmltopdf` is not installed through **pip** and must be installed "
 "manually in `version 0.12.6 "
@@ -7596,9 +7600,9 @@ msgstr "الاستنساخ باستخدام SSH "
 #: ../../content/administration/on_premise/source.rst:182
 #: ../../content/administration/on_premise/source.rst:209
 #: ../../content/administration/on_premise/source.rst:249
-#: ../../content/administration/on_premise/source.rst:343
-#: ../../content/administration/on_premise/source.rst:401
-#: ../../content/administration/on_premise/source.rst:463
+#: ../../content/administration/on_premise/source.rst:348
+#: ../../content/administration/on_premise/source.rst:406
+#: ../../content/administration/on_premise/source.rst:468
 msgid "Mac OS"
 msgstr "Mac OS"

@@ -7782,26 +7786,29 @@ msgstr ""

 #: ../../content/administration/on_premise/source.rst:276
 msgid ""
-"For Debian-based systems, the packages are listed in the `debian/control "
-"<https://github.com/odoo/odoo/blob/16.0/debian/control>`_ file of the Odoo "
-"sources."
-msgstr ""
-"بالنسبة للأنظمة المستندة إلى Debian، يتم إدراج الحزم في ملف `debian/control "
-"<https://github.com/odoo/odoo/blob/16.0/debian/control>`_ الخاص بمصادر أودو."
-" "
-
-#: ../../content/administration/on_premise/source.rst:279
-msgid ""
 "On Debian/Ubuntu, the following commands should install the required "
 "packages:"
 msgstr ""
 "في نظام Debian/Ubuntu، يجب أن تقوم الأوامر التالية بتثبيت الحزم المطلوبة: "

+#: ../../content/administration/on_premise/source.rst:283
+msgid ""
+"The `setup/debinstall.sh` script will parse the `debian/control "
+"<https://github.com/odoo/odoo/blob/16.0/debian/control>`_ file and install "
+"the found packages."
+msgstr ""
+
 #: ../../content/administration/on_premise/source.rst:286
 msgid "Install with pip"
 msgstr "التثبيت باستخدام pip "

-#: ../../content/administration/on_premise/source.rst:288
+#: ../../content/administration/on_premise/source.rst:290
+msgid ""
+"Using pip may lead to security issues and broken dependencies; only do this "
+"if you know what you are doing."
+msgstr ""
+
+#: ../../content/administration/on_premise/source.rst:293
 msgid ""
 "As some of the Python packages need a compilation step, they require system "
 "libraries to be installed."
@@ -7809,7 +7816,7 @@ msgstr ""
 "نظراً لأن بعض حزم Python تحتاج إلى خطوة تجميع، فإنها تتطلب تثبيت مكتبات "
 "النظام. "

-#: ../../content/administration/on_premise/source.rst:291
+#: ../../content/administration/on_premise/source.rst:296
 msgid ""
 "On Debian/Ubuntu, the following command should install these required "
 "libraries:"
@@ -7817,7 +7824,7 @@ msgstr ""
 "في نظام Debian/Ubuntu، يجب أن يقوم الأمر التالي بتثبيت هذه المكتبات "
 "المطلوبة: "

-#: ../../content/administration/on_premise/source.rst:297
+#: ../../content/administration/on_premise/source.rst:302
 msgid ""
 "Odoo dependencies are listed in the :file:`requirements.txt` file located at"
 " the root of the Odoo Community directory."
@@ -7825,7 +7832,7 @@ msgstr ""
 "تم إدراج تبعيات أودو في ملف :file:`requirements.txt` الموجود في جذر دليل "
 "مجتمع أودو. "

-#: ../../content/administration/on_premise/source.rst:301
+#: ../../content/administration/on_premise/source.rst:306
 msgid ""
 "The Python packages in :file:`requirements.txt` are based on their "
 "stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo "
@@ -7839,9 +7846,9 @@ msgstr ""
 "و2.6.0 في Ubuntu Focal. يتم بعد ذلك اختيار الإصدار الأدنى في "
 ":file:`requirements.txt`. "

-#: ../../content/administration/on_premise/source.rst:308
-#: ../../content/administration/on_premise/source.rst:330
-#: ../../content/administration/on_premise/source.rst:349
+#: ../../content/administration/on_premise/source.rst:313
+#: ../../content/administration/on_premise/source.rst:335
+#: ../../content/administration/on_premise/source.rst:354
 msgid ""
 "It can be preferable not to mix Python module packages between different "
 "instances of Odoo or with the system. However, it is possible to use "
@@ -7852,7 +7859,7 @@ msgstr ""
 "النظام. ومع ذلك، من الممكن استخدام `virtualenv "
 "<https://pypi.org/project/virtualenv/>`_ لإنشاء بيئات Python معزولة. "

-#: ../../content/administration/on_premise/source.rst:312
+#: ../../content/administration/on_premise/source.rst:317
 msgid ""
 "Navigate to the path of the Odoo Community installation "
 "(:file:`CommunityPath`) and run **pip** on the requirements file to install "
@@ -7861,7 +7868,7 @@ msgstr ""
 "انتقل إلى مسار تثبيت مجتمع أودو (:file:`CommunityPath`) وقم بتشغيل **pip** "
 "في ملف المتطلبات لتثبيت المتطلبات للمستخدم الحالي. "

-#: ../../content/administration/on_premise/source.rst:322
+#: ../../content/administration/on_premise/source.rst:327
 msgid ""
 "Before installing the dependencies, download and install the `Build Tools "
 "for Visual Studio <https://visualstudio.microsoft.com/downloads/>`_. Select "
@@ -7871,8 +7878,8 @@ msgstr ""
 "<https://visualstudio.microsoft.com/downloads/>`_. قم بتحديد **أدوات بناء "
 "C++** في علامة تبويب **ضغط العمل** وقم بتثبيتها عند المطالبة بذلك. "

-#: ../../content/administration/on_premise/source.rst:326
-#: ../../content/administration/on_premise/source.rst:345
+#: ../../content/administration/on_premise/source.rst:331
+#: ../../content/administration/on_premise/source.rst:350
 msgid ""
 "Odoo dependencies are listed in the `requirements.txt` file located at the "
 "root of the Odoo Community directory."
@@ -7880,7 +7887,7 @@ msgstr ""
 "يتم إدراج تبعيات أودو في ملف \"requirements.txt\" الموجود في جذر دليل مجتمع "
 "أودو. "

-#: ../../content/administration/on_premise/source.rst:334
+#: ../../content/administration/on_premise/source.rst:339
 msgid ""
 "Navigate to the path of the Odoo Community installation (`CommunityPath`) "
 "and run **pip** on the requirements file in a terminal **with Administrator "
@@ -7889,7 +7896,7 @@ msgstr ""
 "انتقل إلى مسار تثبيت مجتمع أودو (`CommunityPath`) وقم بتشغيل **pip** على ملف"
 " المتطلبات في الوحدة الطرفية **مع امتيازات المسؤول**: "

-#: ../../content/administration/on_premise/source.rst:353
+#: ../../content/administration/on_premise/source.rst:358
 msgid ""
 "Navigate to the path of the Odoo Community installation (`CommunityPath`) "
 "and run **pip** on the requirements file:"
@@ -7897,7 +7904,7 @@ msgstr ""
 "انتقل إلى مسار تثبيت مجتمع أودو (`CommunityPath`) وقم بتشغيل **pip** في ملف "
 "المتطلبات: "

-#: ../../content/administration/on_premise/source.rst:363
+#: ../../content/administration/on_premise/source.rst:368
 msgid ""
 "Non-Python dependencies must be installed with a package manager (`Homebrew "
 "<https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_)."
@@ -7905,15 +7912,15 @@ msgstr ""
 "يجب تثبيت التبعيات لغير Python باستخدام مدير الحزم (`Homebrew "
 "<https://brew.sh/>`_، `MacPorts <https://www.macports.org>`_). "

-#: ../../content/administration/on_premise/source.rst:366
+#: ../../content/administration/on_premise/source.rst:371
 msgid "Download and install the **Command Line Tools**:"
 msgstr "قم بتنزيل وتثبيت **أدوات بند الأمر**: "

-#: ../../content/administration/on_premise/source.rst:372
+#: ../../content/administration/on_premise/source.rst:377
 msgid "Use the package manager to install non-Python dependencies."
 msgstr "استخدم مدير الحزم لتثبيت التبعيات لغير Python. "

-#: ../../content/administration/on_premise/source.rst:375
+#: ../../content/administration/on_premise/source.rst:380
 msgid ""
 "For languages using a **right-to-left interface** (such as Arabic or "
 "Hebrew), the `rtlcss` package is required."
@@ -7921,21 +7928,21 @@ msgstr ""
 "بالنسبة للغات التي تستخدم **واجهة من اليمين إلى اليسار** (مثل العربية أو "
 "العبرية)، تكون الحزمة `rtlcss` مطلوبة. "

-#: ../../content/administration/on_premise/source.rst:382
+#: ../../content/administration/on_premise/source.rst:387
 msgid "Download and install **nodejs** and **npm** with a package manager."
 msgstr "قم بتنزيل وتثبيت **nodejs** و**npm** باستخدام مدير الحزم. "

-#: ../../content/administration/on_premise/source.rst:383
-#: ../../content/administration/on_premise/source.rst:392
-#: ../../content/administration/on_premise/source.rst:405
+#: ../../content/administration/on_premise/source.rst:388
+#: ../../content/administration/on_premise/source.rst:397
+#: ../../content/administration/on_premise/source.rst:410
 msgid "Install `rtlcss`:"
 msgstr "قم بتثبيت `rtlcss`: "

-#: ../../content/administration/on_premise/source.rst:391
+#: ../../content/administration/on_premise/source.rst:396
 msgid "Download and install `nodejs <https://nodejs.org/en/download>`_."
 msgstr "قم بتنزيل وتثبيت `nodejs <https://nodejs.org/en/download>`_. "

-#: ../../content/administration/on_premise/source.rst:398
+#: ../../content/administration/on_premise/source.rst:403
 msgid ""
 "Edit the system environment's variable `PATH` to add the folder where "
 "`rtlcss.cmd` is located (typically: "
@@ -7945,7 +7952,7 @@ msgstr ""
 " (يكون عادةً: "
 ":file:`C:\\\\Users\\\\<user>\\\\AppData\\\\Roaming\\\\npm\\\\`). "

-#: ../../content/administration/on_premise/source.rst:403
+#: ../../content/administration/on_premise/source.rst:408
 msgid ""
 "Download and install **nodejs** with a package manager (`Homebrew "
 "<https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_)."
@@ -7953,11 +7960,11 @@ msgstr ""
 "قم بتنزيل **nodejs** وتثبيته باستخدام مدير الحزم (`Homebrew "
 "<https://brew.sh/>`_، `MacPorts <https://www.macports.org>`_). "

-#: ../../content/administration/on_premise/source.rst:420
+#: ../../content/administration/on_premise/source.rst:425
 msgid "Running Odoo"
 msgstr "تشغيل أودو "

-#: ../../content/administration/on_premise/source.rst:422
+#: ../../content/administration/on_premise/source.rst:427
 msgid ""
 "Once all dependencies are set up, Odoo can be launched by running `odoo-"
 "bin`, the command-line interface of the server. It is located at the root of"
@@ -7966,7 +7973,7 @@ msgstr ""
 "بمجرد أن قد تم إعداد كافة التبعيات، يمكن تشغيل أودو عن طريق تشغيل \"odoo-"
 "bin\"، وهي واجهة بند الأوامر للخادم. وهو موجود في جذر دليل مجتمع أودو. "

-#: ../../content/administration/on_premise/source.rst:425
+#: ../../content/administration/on_premise/source.rst:430
 msgid ""
 "To configure the server, either specify :ref:`command-line arguments "
 "<reference/cmdline/server>` or a :ref:`configuration file "
@@ -7975,7 +7982,7 @@ msgstr ""
 "لتهيئة الخادم، حدد إما :ref:`وسائط بند الأوامر <reference/cmdline/server>` "
 "أو :ref:`ملف التهيئة <reference/cmdline/config>`. "

-#: ../../content/administration/on_premise/source.rst:429
+#: ../../content/administration/on_premise/source.rst:434
 msgid ""
 "For the Enterprise edition, add the path to the `enterprise` add-ons to the "
 "`addons-path` argument. Note that it must come before the other paths in "
@@ -7985,25 +7992,25 @@ msgstr ""
 "للمؤسسات` إلى الوسيطة `addons-path`. لاحظ أنه يجب أن يأتي قبل المسارات "
 "الأخرى في \"addons-path\" حتى يتم تحميل الوظائف الإضافية بشكل صحيح. "

-#: ../../content/administration/on_premise/source.rst:433
+#: ../../content/administration/on_premise/source.rst:438
 msgid "Common necessary configurations are:"
 msgstr "من التهيئات الضرورية الشائعة: "

-#: ../../content/administration/on_premise/source.rst:435
+#: ../../content/administration/on_premise/source.rst:440
 msgid "PostgreSQL user and password."
 msgstr "اسم المستخدم وكلمة المرور لـ PostgreSQL "

-#: ../../content/administration/on_premise/source.rst:436
+#: ../../content/administration/on_premise/source.rst:441
 msgid "Custom addon paths beyond the defaults to load custom modules."
 msgstr ""
 "مسارات إضافية مخصصة تتجاوز الإعدادات الافتراضية لتحميل الوحدات المخصصة. "

-#: ../../content/administration/on_premise/source.rst:438
+#: ../../content/administration/on_premise/source.rst:443
 msgid "A typical way to run the server would be:"
 msgstr "الطريقة النموذجية لتشغيل الخادم هي: "

-#: ../../content/administration/on_premise/source.rst:449
-#: ../../content/administration/on_premise/source.rst:470
+#: ../../content/administration/on_premise/source.rst:454
+#: ../../content/administration/on_premise/source.rst:475
 msgid ""
 "Where `CommunityPath` is the path of the Odoo Community installation, and "
 "`mydb` is the name of the PostgreSQL database."
@@ -8011,7 +8018,7 @@ msgstr ""
 "حيث `CommunityPath` هو مسار تثبيت مجتمع أودو، و`mydb` هو اسم قاعدة بيانات "
 "PostgreSQL. "

-#: ../../content/administration/on_premise/source.rst:459
+#: ../../content/administration/on_premise/source.rst:464
 msgid ""
 "Where `CommunityPath` is the path of the Odoo Community installation, "
 "`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, "
@@ -8021,7 +8028,7 @@ msgstr ""
 "PostgreSQL، و`dbpassword` هو كلمة مرور PostgreSQL، و`mydb` هو اسم قاعدة "
 "بيانات PostgreSQL. "

-#: ../../content/administration/on_premise/source.rst:473
+#: ../../content/administration/on_premise/source.rst:478
 msgid ""
 "After the server has started (the INFO log `odoo.modules.loading: Modules "
 "loaded.` is printed), open http://localhost:8069 in a web browser and log "
@@ -8033,7 +8040,7 @@ msgstr ""
 "الدخول إلى قاعدة بيانات أودو باستخدام حساب المدير الأساسي: استخدم كلمة "
 "`admin` كالبريد الإلكتروني، ونفس كلمة `admin` ككلمة المرور. "

-#: ../../content/administration/on_premise/source.rst:478
+#: ../../content/administration/on_premise/source.rst:483
 msgid ""
 "From there, create and manage new :doc:`users "
 "<../../applications/general/users>`."
@@ -8041,7 +8048,7 @@ msgstr ""
 "من هناك، قم بإنشاء وإدارة :doc:`المستخدمين الجدد "
 "<../../applications/general/users>`. "

-#: ../../content/administration/on_premise/source.rst:479
+#: ../../content/administration/on_premise/source.rst:484
 msgid ""
 "The user account used to log into Odoo's web interface differs from the "
 ":option:`--db_user <odoo-bin -r>` CLI argument."
@@ -8049,7 +8056,7 @@ msgstr ""
 "يختلف حساب المستخدِم المستخدَم لتسجيل الدخول إلى واجهة الويب الخاصة بأودو عن"
 " وسيطة CLI :option:`--db_user <odoo-bin -r>`. "

-#: ../../content/administration/on_premise/source.rst:483
+#: ../../content/administration/on_premise/source.rst:488
 msgid ""
 ":doc:`The list of CLI arguments for odoo-bin </developer/reference/cli>`"
 msgstr ":doc:`قائمة وسيطات CLI لـ odoo-bin </developer/reference/cli>` "
@@ -4,17 +4,17 @@
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 # 
 # Translators:
-# Malaz Abuidris <msea@odoo.com>, 2024
 # Wil Odoo, 2024
+# Malaz Abuidris <msea@odoo.com>, 2024
 # 
 #, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2024-04-29 10:38+0000\n"
+"POT-Creation-Date: 2024-06-21 15:46+0000\n"
 "PO-Revision-Date: 2024-04-04 12:31+0000\n"
-"Last-Translator: Wil Odoo, 2024\n"
+"Last-Translator: Malaz Abuidris <msea@odoo.com>, 2024\n"
 "Language-Team: Arabic (https://app.transifex.com/odoo/teams/41243/ar/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -577,6 +577,542 @@ msgstr ":doc:`/applications/productivity/discuss`"
 msgid ":doc:`/applications/productivity/discuss/team_communication`"
 msgstr ":doc:`/applications/productivity/discuss/team_communication`"

+#: ../../content/applications/essentials/contacts.rst:3
+msgid "Contacts"
+msgstr "جهات الاتصال"
+
+#: ../../content/applications/essentials/contacts.rst:5
+msgid ""
+"The *Contacts* application comes installed on all Odoo databases. Contacts "
+"are created for customers the company does business with through Odoo. A "
+"contact is a repository of vital business information, facilitating "
+"communication and business transactions."
+msgstr ""
+"يتم تثبيت تطبيق *جهات الاتصال* على جميع قواعد بيانات Odoo. يتم إنشاء جهات "
+"الاتصال للعملاء الذين تتعامل معهم الشركة من خلال Odoo. جهة الاتصال هي مستودع"
+" للمعلومات التجارية الحيوية، مما يسهل الاتصالات والمعاملات التجارية. "
+
+#: ../../content/applications/essentials/contacts.rst:10
+msgid "Contact form"
+msgstr "استمارة التواصل "
+
+#: ../../content/applications/essentials/contacts.rst:12
+msgid ""
+"To create a new contact, navigate to the :menuselection:`Contacts app`, and "
+"click :guilabel:`Create`. A new form appears where various contact "
+"information can be added."
+msgstr ""
+"لإنشاء جهة اتصال جديدة، انتقل إلى :menuselection:`تطبيق جهات الاتصال`، وانقر"
+" على :guilabel:`إنشاء`. يظهر نموذج جديد حيث يمكن إضافة معلومات اتصال مختلفة."
+
+#: ../../content/applications/essentials/contacts.rst:16
+msgid "Contact type"
+msgstr "نوع جهة الاتصال  "
+
+#: ../../content/applications/essentials/contacts.rst:18
+msgid ""
+"Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` "
+"contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, "
+"depending on the type of contact that is being added."
+msgstr ""
+"يسمح Odoo بكل من جهات الاتصال :guilabel:`Individual` و :guilabel:`Company`. "
+"حدد إما :guilabel:`فرد` أو :guilabel:`شركة`، حسب نوع جهة الاتصال التي تتم "
+"إضافتها. "
+
+#: ../../content/applications/essentials/contacts.rst:22
+msgid "Name"
+msgstr "الاسم "
+
+#: ../../content/applications/essentials/contacts.rst:24
+msgid ""
+"First, fill in the name of the :guilabel:`Individual` or "
+":guilabel:`Company`. This is how the name appears throughout the database. "
+"This field is **mandatory**."
+msgstr ""
+"أولاً، قم بملء اسم :guilabel:`فرد` أو :guilabel:`شركة`. هذه هي الطريقة التي "
+"يظهر بها الاسم في جميع أنحاء قاعدة البيانات. هذا الحقل **إلزامي**. "
+
+#: ../../content/applications/essentials/contacts.rst:28
+msgid ""
+":guilabel:`Individual` contacts can have a :guilabel:`Company` contact "
+"linked to it. After selecting :guilabel:`Individual`, a new "
+":guilabel:`Company Name...` field appears below the first name field."
+msgstr ""
+":guilabel:يمكن أن تحتوي جهات الاتصال `الفردية' على جهة اتصال "
+":guilabel:`شركة` مرتبطة بها. بعد تحديد :guilabel:`فرد`، يظهر حقل جديد "
+":guilabel:`اسم الشركة...` أسفل حقل الاسم الأول. "
+
+#: ../../content/applications/essentials/contacts.rst:33
+msgid "Address"
+msgstr "العنوان "
+
+#: ../../content/applications/essentials/contacts.rst:35
+msgid ""
+"Next, enter the :guilabel:`Address` of the :guilabel:`Company` or "
+":guilabel:`Individual`."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:38
+msgid ""
+"If the :guilabel:`Individual` option is chosen, then the *type of address* "
+"can be chosen from a drop-down menu. Options for this drop-down menu "
+"include: :guilabel:`Contact`, :guilabel:`Invoice Address`, "
+":guilabel:`Delivery Address`, :guilabel:`Other Address`, and "
+":guilabel:`Private Address`."
+msgstr ""
+"إذا تم تحديد الخيار :guilabel:`Individual`، فيمكن اختيار *نوع العنوان* من "
+"القائمة المنسدلة. تتضمن خيارات هذه القائمة المنسدلة ما يلي: :guilabel:`جهة "
+"الاتصال`، :guilabel:`عنوان الفاتورة`، :guilabel:`عنوان التسليم`، "
+":guilabel:`عنوان آخر`، و :guilabel:`عنوان خاص`. "
+
+#: ../../content/applications/essentials/contacts.rst:44
+msgid "Additional fields"
+msgstr "الحقول الإضافية "
+
+#: ../../content/applications/essentials/contacts.rst:46
+msgid ""
+"Additional details are included on the initial form. The following fields "
+"are available:"
+msgstr "يتم تضمين تفاصيل إضافية في النموذج الأولي. الحقول التالية متاحة: "
+
+#: ../../content/applications/essentials/contacts.rst:48
+msgid ":guilabel:`VAT`: Value Added Tax number."
+msgstr ":guilabel:`VAT`: رقم ضريبة القيمة المضافة. "
+
+#: ../../content/applications/essentials/contacts.rst:49
+msgid ""
+":guilabel:`Citizen Identification`: citizen or government identification "
+"number (only available on :guilabel:`Individual`)."
+msgstr ""
+":guilabel:`تعريف المواطن`: رقم هوية المواطن أو الحكومة (متاح فقط على "
+":guilabel:`فردي`). "
+
+#: ../../content/applications/essentials/contacts.rst:51
+msgid ""
+":guilabel:`Job Position`: list the job position of the "
+":guilabel:`Individual` (only available on :guilabel:`Individual`)."
+msgstr ""
+":guilabel:`Job Position`: قم بإدراج المنصب الوظيفي لـ :guilabel:`فرد` (متاح "
+"فقط على :guilabel:`فرد`). "
+
+#: ../../content/applications/essentials/contacts.rst:53
+msgid ""
+":guilabel:`Phone`: list phone number (with country code). Make a call, send "
+"an SMS, or WhatsApp message by hovering over the field on the saved form, "
+"and clicking the desired option."
+msgstr ""
+":guilabel:`Phone`: قائمة رقم الهاتف (مع رمز البلد). قم بإجراء مكالمة أو "
+"إرسال رسالة نصية قصيرة أو رسالة عبر تطبيق WhatsApp من خلال تمرير الماوس فوق "
+"الحقل الموجود في النموذج المحفوظ، والنقر فوق الخيار المطلوب. "
+
+#: ../../content/applications/essentials/contacts.rst:55
+msgid ""
+":guilabel:`Mobile`: list mobile phone number (with country code). Make a "
+"call, send an SMS, or WhatsApp message by hovering over the field on the "
+"saved form, and clicking on the desired option."
+msgstr ""
+":guilabel:`Mobile`: قائمة رقم الهاتف المحمول (مع رمز البلد). قم بإجراء "
+"مكالمة أو إرسال رسالة نصية قصيرة أو رسالة عبر تطبيق WhatsApp من خلال تمرير "
+"الماوس فوق الحقل الموجود في النموذج المحفوظ، والنقر فوق الخيار المطلوب. "
+
+#: ../../content/applications/essentials/contacts.rst:57
+msgid ":guilabel:`Email`: enter the email address with the domain."
+msgstr ":guilabel:`Email`: أدخل عنوان البريد الإلكتروني مع المجال. "
+
+#: ../../content/applications/essentials/contacts.rst:58
+msgid ""
+":guilabel:`Website`: enter the full website address, starting with `http` or"
+" `https`."
+msgstr ""
+":guilabel:`موقع الويب`: أدخل عنوان موقع الويب بالكامل، بدءًا من `http` أو "
+"`https`. "
+
+#: ../../content/applications/essentials/contacts.rst:59
+msgid ""
+":guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, "
+":guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new"
+" one directly from this field."
+msgstr ""
+":guilabel:`Title`: حدد :guilabel:`Doctor`، :guilabel:`Madam`، "
+":guilabel:`Miss`، :guilabel:`Mister`، :guilabel:`Professor`، أو قم بإنشاء "
+"واحدة جديدة مباشرة من هذا الحقل. "
+
+#: ../../content/applications/essentials/contacts.rst:61
+msgid ""
+":guilabel:`Tags`: enter preconfigured tags by typing them in the field, or "
+"clicking the drop-down menu, and selecting one. To create a new one, type "
+"the new tag in the field, and click :guilabel:`Create` from the resulting "
+"drop-down menu."
+msgstr ""
+":guilabel:`العلامات`: أدخل العلامات التي تم تكوينها مسبقًا عن طريق كتابتها "
+"في الحقل، أو النقر فوق القائمة المنسدلة، واختيار واحدة. لإنشاء علامة جديدة، "
+"اكتب العلامة الجديدة في الحقل، ثم انقر فوق :guilabel:`Create` من القائمة "
+"المنسدلة الناتجة. "
+
+#: ../../content/applications/essentials/contacts.rst:66
+msgid "Contacts & Addresses tab"
+msgstr "علامة تبويب جهات الاتصال والعناوين  "
+
+#: ../../content/applications/essentials/contacts.rst:68
+msgid ""
+"At the bottom of the contact form are several tabs. On the "
+":guilabel:`Contacts & Addresses` tab, contacts can be added that are "
+"associated with a :guilabel:`Company` and related addresses. For example, a "
+"specific contact person for the company can be listed here."
+msgstr ""
+"يوجد في الجزء السفلي من نموذج الاتصال عدة علامات تبويب. في علامة التبويب "
+":guilabel:`جهات الاتصال والعناوين`، يمكن إضافة جهات الاتصال المرتبطة بـ "
+":guilabel:`الشركة` والعناوين ذات الصلة. على سبيل المثال، يمكن إدراج جهة "
+"اتصال محددة للشركة هنا. "
+
+#: ../../content/applications/essentials/contacts.rst:72
+msgid ""
+"Multiple addresses can be added on both :guilabel:`Individual` and "
+":guilabel:`Company` contacts. To do so, click :guilabel:`Add` in the "
+":guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create "
+"Contact` pop-up form, in which additional addresses can be configured."
+msgstr ""
+"يمكن إضافة عناوين متعددة على كل من جهات الاتصال :guilabel:`Individual` و "
+":guilabel:`Company`. للقيام بذلك، انقر فوق :guilabel:`إضافة` في علامة "
+"التبويب :guilabel:`جهات الاتصال والعناوين`. يؤدي القيام بذلك إلى ظهور نموذج "
+"منبثق :guilabel:`Create Contact`، حيث يمكن تكوين عناوين إضافية. "
+
+#: ../../content/applications/essentials/contacts.rst-1
+msgid "Add a contact/address to the contact form."
+msgstr "أضف جهة اتصال/عنوانًا إلى نموذج الاتصال. "
+
+#: ../../content/applications/essentials/contacts.rst:80
+msgid ""
+"On the :guilabel:`Create Contact` pop-up form, start by clicking the default"
+" :guilabel:`Other Address` field at the top to reveal a drop-down menu of "
+"address-related options."
+msgstr ""
+"في النموذج المنبثق :guilabel:`Create Contact`، ابدأ بالنقر فوق الحقل "
+"الافتراضي :guilabel:`عنوان آخر` في الجزء العلوي للكشف عن قائمة منسدلة "
+"بالخيارات المتعلقة بالعنوان. "
+
+#: ../../content/applications/essentials/contacts.rst:83
+msgid "Select any of the following options:"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:85
+msgid ""
+":guilabel:`Contact`: adds another contact to the existing contact form."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:86
+msgid ""
+":guilabel:`Invoice Address`: adds a specific invoice address to the existing"
+" contact form."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:87
+msgid ""
+":guilabel:`Delivery Address`: adds a specific delivery address to the "
+"existing contact form."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:88
+msgid ""
+":guilabel:`Other Address`: adds an alternate address to the existing contact"
+" form."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:89
+msgid ""
+":guilabel:`Private Address`: adds a private address to the existing contact "
+"form."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst-1
+msgid "Create a new contact/address on a contact form."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:95
+msgid ""
+"Once an option is selected, enter the corresponding contact information that"
+" should be used for the specified address type."
+msgstr ""
+"بمجرد تحديد أحد الخيارات، أدخل معلومات الاتصال المقابلة التي يجب استخدامها "
+"لنوع العنوان المحدد. "
+
+#: ../../content/applications/essentials/contacts.rst:98
+msgid ""
+"Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, "
+"along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below."
+msgstr ""
+"أضف :guilabel:`اسم جهة الاتصال`، :guilabel:`العنوان`، :guilabel:`البريد "
+"الإلكتروني`، بالإضافة إلى أرقام :guilabel:`الهاتف` و/أو :guilabel:`الجوال` "
+"أدناه. "
+
+#: ../../content/applications/essentials/contacts.rst:101
+msgid ""
+"Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` "
+"address type has been selected. This is similar to the "
+":guilabel:`Individual` contact."
+msgstr ""
+"قم بتعيين :guilabel:`Job Position`، الذي يظهر إذا تم تحديد نوع عنوان "
+":guilabel:`Contact`. وهذا مشابه لجهة الاتصال :guilabel:`الفردية`. "
+
+#: ../../content/applications/essentials/contacts.rst:104
+msgid ""
+"To add a note, click on the text field next to :guilabel:`Notes`, and write "
+"anything that is applicable to the customer or contact."
+msgstr ""
+"لإضافة ملاحظة، انقر فوق حقل النص بجوار :guilabel:`Notes`، واكتب أي شيء ينطبق"
+" على العميل أو جهة الاتصال. "
+
+#: ../../content/applications/essentials/contacts.rst:107
+msgid ""
+"Then, click :guilabel:`Save & Close` to save the address, and close the "
+":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save "
+"the address, and immediately input another one."
+msgstr ""
+"ثم انقر فوق :guilabel:`حفظ وإغلاق` لحفظ العنوان، وأغلق نافذة "
+":guilabel:`إنشاء جهة اتصال`. أو انقر فوق :guilabel:`Save & New` لحفظ "
+"العنوان، وإدخال عنوان آخر على الفور. "
+
+#: ../../content/applications/essentials/contacts.rst:111
+msgid "Sales & Purchase tab"
+msgstr "علامة تبويب المبيعات والمشتريات "
+
+#: ../../content/applications/essentials/contacts.rst:113
+msgid ""
+"Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the "
+"*Sales*, *Purchase*, **or** *Point of Sale* applications are installed."
+msgstr ""
+"بعد ذلك، هي علامة التبويب :guilabel: `المبيعات والمشتريات`، والتي تظهر فقط "
+"عند تثبيت تطبيقات *Sales* أو *Purchase* أو **أو** *Point of Sale*. "
+
+#: ../../content/applications/essentials/contacts.rst:116
+msgid ""
+"The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & "
+"Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down "
+"menu."
+msgstr ""
+"يمكن تعيين :guilabel:`المركز المالي` في علامة التبويب :guilabel:`المبيعات "
+"والمشتريات`. حدد :guilabel:`الوضع المالي` من القائمة المنسدلة. "
+
+#: ../../content/applications/essentials/contacts.rst:120
+msgid "Sales section"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:122
+msgid ""
+"Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can "
+"be assigned to a contact. To do that, click the :guilabel:`Salesperson` "
+"drop-down field, and select one. Create a new :guilabel:`Salesperson` by "
+"typing the user's name, and making the appropriate selection."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:126
+msgid ""
+"Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can "
+"also be set, if needed. Click the drop-down menu next to :guilabel:`Payment "
+"Terms`, and change it to one of the preselected :guilabel:`Payment Terms`, "
+"or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down "
+"menu to choose the appropriate :guilabel:`Pricelist`."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:131
+msgid ""
+"Click into the :guilabel:`Delivery Method` field to select an option from "
+"the drop-down menu."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:134
+msgid "Point Of Sale section"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:136
+msgid ""
+"Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` "
+"that can be used to identify the contact. Use the :guilabel:`Loyalty Points`"
+" field to track points the user won as part of a *Loyalty Program*."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:141
+msgid "Purchase section"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:143
+msgid ""
+"Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a "
+"preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` "
+"can be set here, as well."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:147
+msgid "Misc section"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:149
+msgid ""
+"Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add "
+"any additional information for this contact. If this contact should only be "
+"accessible for one company in a multi-company database, select it from the "
+":guilabel:`Company` field drop-down list. Use the :guilabel:`Website` drop-"
+"down menu to restrict the publishing of this contact to one website (if "
+"working on a database with multiple websites). Select one or more "
+":guilabel:`Website Tags` to assist in filtering published customers on the "
+"`/customers` website page. Select an :guilabel:`Industry` for this contact "
+"from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a "
+"*Helpdesk* SLA policy to this contact."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:159
+msgid "Accounting tab"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:161
+msgid ""
+"The :guilabel:`Accounting` tab appears when the *Accounting* application is "
+"installed. Here, a user can add any related :guilabel:`Bank Accounts`, or "
+"set default :guilabel:`Accounting entries`."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:164
+msgid ""
+"Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field "
+"to enter a Legal Entity Identifier, if necessary."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:168
+msgid "Internal Notes tab"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:170
+msgid ""
+"Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` "
+"tab, where notes can be left on this contact form, just like on the contact "
+"form noted above."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:174
+msgid "Partner Assignment tab"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:176
+msgid ""
+"Next is the :guilabel:`Partner Assignment` tab, which by default, includes a"
+" :guilabel:`Geolocation` section, and other partner options, including "
+":guilabel:`Partner Activation` and :guilabel:`Partner Review` "
+"configurations. These are **only** present when the *Enterprise Resellers* "
+"module is installed."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:182
+msgid "Membership tab"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:184
+msgid ""
+"Finally, there is the :guilabel:`Membership` tab, which can help users "
+"manage any memberships that are being offered to this specific contact. It "
+"should be noted that this tab only appears when the *Members* applications "
+"is installed."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:189
+msgid "Smart buttons"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:191
+msgid ""
+"At the top of the contact form, there are some additional options available,"
+" known as *smart buttons*."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:194
+msgid ""
+"Here, Odoo displays a variety of records, related to this contact, that were"
+" created on other apps. Odoo integrates information from every single app, "
+"so there are many smart buttons."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:198
+msgid ""
+"For example, there is an :guilabel:`Opportunities` smart button, where all "
+"the opportunities related to this customer from the *CRM* app are "
+"accessible."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:202
+msgid ""
+"If the corresponding applications are installed, their related smart buttons"
+" appear automatically on a contact form."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:205
+msgid ""
+"A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS "
+"Orders`, :guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the "
+":guilabel:`More` smart button reveals additional options, via a drop-down "
+"menu. A user can even quickly access :guilabel:`Purchases`, "
+":guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, "
+":guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the "
+":guilabel:`Partner Ledger` connected to this contact."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:211
+msgid ""
+"Deliveries, documents, loyalty cards, and direct debits are *also* linked to"
+" smart buttons, like this, should there be any outstanding/on-file for this "
+"contact."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:214
+msgid ""
+"If the contact is a partner, the user can visit their partner page on the "
+"Odoo-built website by clicking the :guilabel:`Go to Website` smart button."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:218
+msgid "Archive contacts"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:220
+msgid ""
+"If a user decides they no longer want to have this contact active, the "
+"record can be archived. To do that, go to the :icon:`fa-cog` "
+":guilabel:`Action` menu at the top of the contact form, and click "
+":guilabel:`Archive`."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:224
+msgid ""
+"Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-"
+"up window."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:226
+msgid ""
+"With this contact successfully archived, as indicated by a banner at the "
+"top, they do not show up in the main contacts page, but they can still be "
+"searched for with the :guilabel:`Archived` filter."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:230
+msgid ""
+"A contact can be *unarchived*, if the user decides to work with them again. "
+"To do that, just click the :icon:`fa-cog` :guilabel:`Action` menu again at "
+"the top of the archived contact form, and click :guilabel:`Unarchive`. Upon "
+"doing so, the :guilabel:`Archived` banner is removed, and the contact is "
+"restored."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:236
+msgid ""
+":doc:`Add different addresses in CRM "
+"<../sales/sales/send_quotations/different_addresses>`"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:237
+msgid ""
+"`Odoo's eLearning Contacts tutorial "
+"<https://www.odoo.com/slides/slide/contacts-2527?fullscreen=1>`_"
+msgstr ""
+
 #: ../../content/applications/essentials/export_import_data.rst:3
 msgid "Export and import data"
 msgstr "استيراد وتصدير البيانات "
@@ -2362,6 +2362,12 @@ msgid ""
 "<reconciliation/manual-operations>`, and :ref:`reconciliation model buttons "
 "<reconciliation/button>`."
 msgstr ""
+"يمكن أن تتم مطابقة المعاملات تلقائياً باستخدام :doc:`نماذج "
+"التسوية<reconciliation_models>`، أو يمكن مطابقتها مع :ref:`القيود الموجودة "
+"<reconciliation/existing-entries>`, :ref:`المدفوعات المجمعة "
+"<reconciliation/batch-payments >`, :ref:`العمليات اليدوية "
+"<reconciliation/manual-operations>`، و :ref:`أزرار نموذج "
+"التسوية<reconciliation/button>`. "

 #: ../../content/applications/finance/accounting/bank/reconciliation.rst:67
 msgid "Select a transaction among unmatched bank transactions."
@@ -2376,6 +2382,11 @@ msgid ""
 "<reconciliation/batch-payments>`, and :ref:`reconciliation model buttons "
 "<reconciliation/button>`."
 msgstr ""
+"قم بتحديد النظير. هناك عدة خيارات لتحديد النظير، بما في ذلك :ref:`مطابقة "
+"القيود الموجودة <reconciliation/existing-entries>`, :ref:`العمليات اليدوية "
+"<reconciliation/manual-operations>`, :ref:`المدفوعات المجمعة "
+"<reconciliation/batch-payments>`، و:ref:`أزرار نموذج التسوية "
+"<reconciliation/button>`. "

 #: ../../content/applications/finance/accounting/bank/reconciliation.rst:72
 msgid ""
@@ -2428,6 +2439,9 @@ msgid ""
 ":doc:`reconciliation models <reconciliation_models>`, with suggested entries"
 " appearing first."
 msgstr ""
+"تحتوي علامة التبويب هذه على قيود مطابقة يقوم أودو بتحديدها تلقائياً بشكل "
+"مسبق وفقاً لنماذج التسوية. يعتمد ترتيب القيد على :doc:`نماذج "
+"التسوية<reconciliation_models>`، وتظهر القيود المقترحة أولاً. "

 #: ../../content/applications/finance/accounting/bank/reconciliation.rst:97
 msgid ""
@@ -2500,10 +2514,13 @@ msgid ""
 "quickly reconcile bank transactions manually and can also be used in "
 "combination with existing entries."
 msgstr ""
+"استخدم زر :doc:`نموذج التسوية` <reconciliation_models>للعمليات اليدوية التي "
+"يتم استخدامها بشكل متكرر. تسمح لك هذه الأزرار المخصصة بتسوية المعاملات "
+"البنكية يدوياً بسرعة ويمكن استخدامها أيضاً مع القيود الموجودة. "

 #: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:3
 msgid "Reconciliation models"
-msgstr ""
+msgstr "نماذج التسوية "

 #: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:5
 msgid ""
@@ -2528,7 +2545,7 @@ msgstr ""

 #: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:19
 msgid "Reconciliation model types"
-msgstr ""
+msgstr "أنواع نموذج التسوية "

 #: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:21
 msgid ""
@@ -2794,7 +2811,7 @@ msgstr ""

 #: ../../content/applications/finance/accounting/bank/transactions.rst:42
 msgid ":doc:`/applications/essentials/export_import_data`"
-msgstr ""
+msgstr ":doc:`/applications/essentials/export_import_data`"

 #: ../../content/applications/finance/accounting/bank/transactions.rst:47
 msgid "Register bank transactions manually"
@@ -15093,6 +15110,9 @@ msgid ""
 "<https://community.avalara.com/support/s/document-"
 "item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Tell_us_where_you_collect_and_pay_tax.html&_LANG=enus>`_."
 msgstr ""
+"`Tell us where the company collects and pays tax "
+"<https://community.avalara.com/support/s/document-"
+"item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Tell_us_where_you_collect_and_pay_tax.html&_LANG=enus>`_."

 #: ../../content/applications/finance/accounting/taxes/avatax.rst:63
 msgid ""
@@ -15100,6 +15120,9 @@ msgid ""
 "<https://community.avalara.com/support/s/document-"
 "item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Verify_your_jurisdictions_and_activate_your_company.html&_LANG=enus>`_."
 msgstr ""
+"`Verify jurisdictions and activate the company "
+"<https://community.avalara.com/support/s/document-"
+"item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Verify_your_jurisdictions_and_activate_your_company.html&_LANG=enus>`_."

 #: ../../content/applications/finance/accounting/taxes/avatax.rst:65
 msgid ""
@@ -15108,6 +15131,10 @@ msgid ""
 "item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Add_other_company_locations_for_location-"
 "based_filing.html&_LANG=enus>`_."
 msgstr ""
+"`Add other company locations for location-based filing "
+"<https://community.avalara.com/support/s/document-"
+"item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Add_other_company_locations_for_location-"
+"based_filing.html&_LANG=enus>`_."

 #: ../../content/applications/finance/accounting/taxes/avatax.rst:67
 msgid ""
@@ -15115,16 +15142,21 @@ msgid ""
 "<https://community.avalara.com/support/s/document-"
 "item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Add_marketplace_transactions_to_your_company_profile.html&_LANG=enus>`_."
 msgstr ""
+"`Add a marketplace to the company profile "
+"<https://community.avalara.com/support/s/document-"
+"item?bundleId=dqa1657870670369_dqa1657870670369&topicId=Add_marketplace_transactions_to_your_company_profile.html&_LANG=enus>`_."

 #: ../../content/applications/finance/accounting/taxes/avatax.rst:73
 msgid "Connect to AvaTax"
-msgstr ""
+msgstr "Connect to AvaTax"

 #: ../../content/applications/finance/accounting/taxes/avatax.rst:75
 msgid ""
 "After creating the basic company profile in Avalara, connect to *AvaTax*. "
 "This step links Odoo and *AvaTax* bidirectionally."
 msgstr ""
+"After creating the basic company profile in Avalara, connect to *AvaTax*. "
+"This step links Odoo and *AvaTax* bidirectionally."

 #: ../../content/applications/finance/accounting/taxes/avatax.rst:78
 msgid ""
@@ -15132,6 +15164,9 @@ msgid ""
 " or `production <https://admin.avalara.com/>`_ environment. This will depend"
 " on which type of Avalara account the company would like to integrate."
 msgstr ""
+"Navigate to either Avalara's `sandbox <https://sandbox.admin.avalara.com/>`_"
+" or `production <https://admin.avalara.com/>`_ environment. This will depend"
+" on which type of Avalara account the company would like to integrate."

 #: ../../content/applications/finance/accounting/taxes/avatax.rst:83
 msgid ""
@@ -15139,12 +15174,17 @@ msgid ""
 "<https://knowledge.avalara.com/bundle/fzc1692293626742/page/sandbox-vs-"
 "production.html>`_."
 msgstr ""
+"`Sandbox vs production environments in Avalara "
+"<https://knowledge.avalara.com/bundle/fzc1692293626742/page/sandbox-vs-"
+"production.html>`_."

 #: ../../content/applications/finance/accounting/taxes/avatax.rst:86
 msgid ""
 "Log in to create the :guilabel:`License Key`. Go to :menuselection:`Settings"
 " --> License and API Keys`. Click :guilabel:`Generate License Key`."
 msgstr ""
+"Log in to create the :guilabel:`License Key`. Go to :menuselection:`Settings"
+" --> License and API Keys`. Click :guilabel:`Generate License Key`."

 #: ../../content/applications/finance/accounting/taxes/avatax.rst:90
 msgid ""
@@ -15152,6 +15192,9 @@ msgid ""
 "solutions, the connection will be broken until you update the app with the "
 "new license key. This action cannot be undone.`"
 msgstr ""
+"A warning appears stating: `If your business app is connected to Avalara "
+"solutions, the connection will be broken until you update the app with the "
+"new license key. This action cannot be undone.`"

 #: ../../content/applications/finance/accounting/taxes/avatax.rst:94
 msgid ""
@@ -16493,6 +16536,11 @@ msgid ""
 "<https://admin.avalara.com/>`_ environment. This will depend on which type "
 "of account was set in the :doc:`integration <../avatax>`."
 msgstr ""
+"Additional jurisdictions (tax locations) can be added in the Avalara "
+"management console. Navigate to either Avalara's `sandbox "
+"<https://sandbox.admin.avalara.com/>`_ or `production "
+"<https://admin.avalara.com/>`_ environment. This will depend on which type "
+"of account was set in the :doc:`integration <../avatax>`."

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:198
 msgid ""
@@ -16503,6 +16551,12 @@ msgid ""
 "collect sales and use tax` to add another location where the company "
 "collects sales and use tax."
 msgstr ""
+"Next, navigate to :menuselection:`Settings --> Where you collect tax`. "
+"Choose between the three different tabs, depending on the business need. The"
+" first tab is :guilabel:`Sales and use tax`, where tax can be collected for "
+"the United States. Click the :icon:`fa-plus` :guilabel:`Add to where you "
+"collect sales and use tax` to add another location where the company "
+"collects sales and use tax."

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:203
 msgid ""
@@ -16511,6 +16565,10 @@ msgid ""
 "selected to add another country or territory where the company collects "
 "VAT/GST."
 msgstr ""
+"The second option, is the :guilabel:`VAT/GST` tab where the :icon:`fa-plus` "
+":guilabel:`Add a country or territory where you collect VAT/GST` can be "
+"selected to add another country or territory where the company collects "
+"VAT/GST."

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:207
 msgid ""
@@ -16519,12 +16577,18 @@ msgid ""
 "on the :icon:`fa-plus` :guilabel:`Add a country where you calculate customs "
 "duty` icon below the tab."
 msgstr ""
+"Finally, on the far-right, is the :guilabel:`Customs duty` tab, where a "
+"country can be added where the company collects customs duty. Simply click "
+"on the :icon:`fa-plus` :guilabel:`Add a country where you calculate customs "
+"duty` icon below the tab."

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst-1
 msgid ""
 "AvaTax management console, on the Where you collect tax page, with the add button and\n"
 "sales and use tax tab highlighted."
 msgstr ""
+"AvaTax management console, on the Where you collect tax page, with the add button and\n"
+"sales and use tax tab highlighted."

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:217
 msgid ""
@@ -16532,10 +16596,13 @@ msgid ""
 "<https://community.avalara.com/support/s/document-"
 "item?language=en_US&bundleId=bla1700809896571_bla1700809896571&topicId=nbw1698727575499.html&_LANG=enus>`_."
 msgstr ""
+"`See Avalara's documentation: Add local jurisdiction taxes "
+"<https://community.avalara.com/support/s/document-"
+"item?language=en_US&bundleId=bla1700809896571_bla1700809896571&topicId=nbw1698727575499.html&_LANG=enus>`_."

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:221
 msgid "Tax exemption certificate"
-msgstr ""
+msgstr "Tax exemption certificate"

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:223
 msgid ""
@@ -16546,6 +16613,12 @@ msgid ""
 " on the :icon:`fa-plus` :guilabel:`Add a certificate` to configure an "
 "exemption."
 msgstr ""
+"Tax exemption certificates for customers can be added into the Avalara "
+"management console, so that *AvaTax* is aware of which customers may be "
+"exempt from paying certain taxes. To add an *exception certificate* navigate"
+" to :menuselection:`Exemptions --> Customer certificates`. From there, click"
+" on the :icon:`fa-plus` :guilabel:`Add a certificate` to configure an "
+"exemption."

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:229
 msgid ""
@@ -16555,10 +16628,15 @@ msgid ""
 "<https://community.avalara.com/support/s/document-"
 "item?language=en_US&bundleId=hff1682048150115_hff1682048150115&topicId=fol1682356576230.html&_LANG=enus>`_."
 msgstr ""
+"An Avalara subscription to Exemption Certificate Management (ECM) is "
+"required in order to attach certificate images, and to be ready for an "
+"audit. For more on subscribing to this add-on, visit `Avalara "
+"<https://community.avalara.com/support/s/document-"
+"item?language=en_US&bundleId=hff1682048150115_hff1682048150115&topicId=fol1682356576230.html&_LANG=enus>`_."

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:235
 msgid "End-of-year operations"
-msgstr ""
+msgstr "End-of-year operations"

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:237
 msgid ""
@@ -16569,10 +16647,16 @@ msgid ""
 "to log in for security purposes, and redirect the user to the *Returns* "
 "portal."
 msgstr ""
+"Avalara's services include tax return services, for when it is time to file "
+"taxes at the end of the year. To access Avalara's tax services log, into the"
+" `management portal <https://admin.avalara.com/>`_. Then, from the main "
+"dashboard, click :guilabel:`Returns`. Avalara will prompt the Avalara user "
+"to log in for security purposes, and redirect the user to the *Returns* "
+"portal."

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst-1
 msgid "Avalara portal with the returns shortcut highlighted."
-msgstr ""
+msgstr "Avalara portal with the returns shortcut highlighted."

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:247
 msgid ""
@@ -16581,25 +16665,31 @@ msgid ""
 "<https://community.avalara.com/support/s/document-"
 "item?language=en_US&bundleId=hps1656397152776_hps1656397152776&topicId=Learn_about_Managed_Returns.html&_LANG=enus>`_."
 msgstr ""
+"Click :guilabel:`Get started` to begin the tax return process. For more "
+"information, refer to this Avalara documentation: `About Managed Returns "
+"<https://community.avalara.com/support/s/document-"
+"item?language=en_US&bundleId=hps1656397152776_hps1656397152776&topicId=Learn_about_Managed_Returns.html&_LANG=enus>`_."

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:252
 msgid ""
 "Alternatively, click on the :menuselection:`Returns` button in the top menu "
 "of the Avalara management console."
 msgstr ""
+"Alternatively, click on the :menuselection:`Returns` button in the top menu "
+"of the Avalara management console."

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:256
 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:159
 msgid ":doc:`../avatax`"
-msgstr ""
+msgstr ":doc:`../avatax`"

 #: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:257
 msgid ":doc:`avatax_use`"
-msgstr ""
+msgstr ":doc:`avatax_use`"

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:3
 msgid "AvaTax use"
-msgstr ""
+msgstr "AvaTax use"

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:5
 msgid ""
@@ -16607,6 +16697,9 @@ msgid ""
 " United States and Canada. Once the :doc:`integration setup <../avatax>` is "
 "complete, the calculated tax is simple and automatic."
 msgstr ""
+"AvaTax is a tax calculation software that can be integrated with Odoo in the"
+" United States and Canada. Once the :doc:`integration setup <../avatax>` is "
+"complete, the calculated tax is simple and automatic."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:10
 msgid "Tax calculation"
@@ -16619,18 +16712,26 @@ msgid ""
 "the taxes manually by clicking the :guilabel:`Compute taxes using Avatax` "
 "button while these documents are in draft mode."
 msgstr ""
+"Automatically calculate taxes on Odoo quotations and invoices with AvaTax by"
+" confirming the documents during the sales flow. Alternatively, calculate "
+"the taxes manually by clicking the :guilabel:`Compute taxes using Avatax` "
+"button while these documents are in draft mode."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:17
 msgid ""
 "Clicking the :guilabel:`Compute taxes using Avatax` button recalculates "
 "taxes if any product lines are edited on the invoice."
 msgstr ""
+"Clicking the :guilabel:`Compute taxes using Avatax` button recalculates "
+"taxes if any product lines are edited on the invoice."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst-1
 msgid ""
 "Sales quotation with the confirm and compute taxes using AvaTax buttons "
 "highlighted."
 msgstr ""
+"Sales quotation with the confirm and compute taxes using AvaTax buttons "
+"highlighted."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:24
 msgid ""
@@ -16638,58 +16739,65 @@ msgid ""
 "trigger <avatax/automatic-triggers>` and :ref:`manual trigger "
 "<avatax/manual-triggers>` circumstances."
 msgstr ""
+"The tax calculation is triggered during the following :ref:`automatic "
+"trigger <avatax/automatic-triggers>` and :ref:`manual trigger "
+"<avatax/manual-triggers>` circumstances."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:30
 msgid "Automatic triggers"
-msgstr ""
+msgstr "Automatic triggers"

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:32
 msgid ""
 "When the sales rep sends the quote by email with :guilabel:`Send by email` "
 "button (pop-up)."
 msgstr ""
+"When the sales rep sends the quote by email with :guilabel:`Send by email` "
+"button (pop-up)."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:33
 msgid "When the customer views the online quote on the portal."
-msgstr ""
+msgstr "When the customer views the online quote on the portal."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:34
 msgid "When a quote is confirmed and becomes a sales order."
-msgstr ""
+msgstr "When a quote is confirmed and becomes a sales order."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:35
 msgid "When the customer views the invoice on the portal."
-msgstr ""
+msgstr "When the customer views the invoice on the portal."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:36
 msgid "When a draft invoice is validated."
-msgstr ""
+msgstr "When a draft invoice is validated."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:37
 msgid "When the customer views the subscription in the portal."
-msgstr ""
+msgstr "When the customer views the subscription in the portal."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:38
 msgid "When a subscription generates an invoice."
-msgstr ""
+msgstr "When a subscription generates an invoice."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:39
 msgid "When the customer gets to the last screen of the eCommerce checkout."
-msgstr ""
+msgstr "When the customer gets to the last screen of the eCommerce checkout."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:44
 msgid "Manual triggers"
-msgstr ""
+msgstr "Manual triggers"

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:46
 msgid ""
 ":guilabel:`Compute taxes using Avatax` button at the bottom of the quote."
 msgstr ""
+":guilabel:`Compute taxes using Avatax` button at the bottom of the quote."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:47
 msgid ""
 ":guilabel:`Compute taxes using Avatax` button at the top of the invoice."
 msgstr ""
+":guilabel:`Compute taxes using Avatax` button at the top of the invoice."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:50
 msgid ""
@@ -16698,6 +16806,10 @@ msgid ""
 "AvaTax. This field is located under the :menuselection:`Other info` tab of "
 "the sales order or quotation in the :guilabel:`Sales` section."
 msgstr ""
+"Use the :guilabel:`Avalara Partner Code` field that is available on customer"
+" records, quotations, and invoices to cross-reference data in Odoo and "
+"AvaTax. This field is located under the :menuselection:`Other info` tab of "
+"the sales order or quotation in the :guilabel:`Sales` section."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:54
 msgid ""
@@ -16705,21 +16817,26 @@ msgid ""
 "Then open the :guilabel:`Sales & Purchase` tab and the :guilabel:`Avalara "
 "Partner Code` under the :guilabel:`Sales` section."
 msgstr ""
+"On the customer record, navigate to *Contacts app* and select a contact. "
+"Then open the :guilabel:`Sales & Purchase` tab and the :guilabel:`Avalara "
+"Partner Code` under the :guilabel:`Sales` section."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:59
 msgid ""
 "The :guilabel:`Automatic Tax Mapping (AvaTax)` fiscal position is also "
 "applied on those Odoo documents, like subscriptions."
 msgstr ""
+"The :guilabel:`Automatic Tax Mapping (AvaTax)` fiscal position is also "
+"applied on those Odoo documents, like subscriptions."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:63
 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:163
 msgid ":doc:`../fiscal_positions`"
-msgstr ""
+msgstr ":doc:`../fiscal_positions`"

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:66
 msgid "AvaTax synchronization"
-msgstr ""
+msgstr "AvaTax synchronization"

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:68
 msgid ""
@@ -16727,12 +16844,17 @@ msgid ""
 "This means the sales tax is recorded with Avalara (AvaTax software "
 "developer)."
 msgstr ""
+"Synchronization occurs with AvaTax, when the *invoice* is created in Odoo. "
+"This means the sales tax is recorded with Avalara (AvaTax software "
+"developer)."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:71
 msgid ""
 "To do so, navigate to :menuselection:`Sales app --> Orders --> Quotations`. "
 "Select a quotation from the list."
 msgstr ""
+"To do so, navigate to :menuselection:`Sales app --> Orders --> Quotations`. "
+"Select a quotation from the list."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:74
 msgid ""
@@ -16741,6 +16863,10 @@ msgid ""
 "invoice`, :guilabel:`Down payment (percentage)`, or :guilabel:`Down payment "
 "(fixed amount)`."
 msgstr ""
+"After confirming a quotation and validating the delivery, click "
+":guilabel:`Create Invoice`. Indicate whether it is a :guilabel:`Regular "
+"invoice`, :guilabel:`Down payment (percentage)`, or :guilabel:`Down payment "
+"(fixed amount)`."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:78
 msgid ""
@@ -16749,16 +16875,22 @@ msgid ""
 "different taxes depending on the location of the :guilabel:`Delivery "
 "Address`."
 msgstr ""
+"Then click :guilabel:`Create and view invoice`. The recorded taxes can be "
+"seen in the :guilabel:`Journal Items` tab of the invoice. There will be "
+"different taxes depending on the location of the :guilabel:`Delivery "
+"Address`."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst-1
 msgid "Journal items highlighted on a invoice in Odoo."
-msgstr ""
+msgstr "Journal items highlighted on a invoice in Odoo."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:86
 msgid ""
 "Finally, press the :guilabel:`Confirm` button to complete the invoice and "
 "synchronize with the AvaTax portal."
 msgstr ""
+"Finally, press the :guilabel:`Confirm` button to complete the invoice and "
+"synchronize with the AvaTax portal."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:90
 msgid ""
@@ -16767,10 +16899,14 @@ msgid ""
 " note` and state: `Sync with AvaTax Portal`. See this documentation: "
 ":doc:`../../../accounting/customer_invoices/credit_notes`."
 msgstr ""
+"An invoice cannot be :guilabel:`Reset to draft` because this causes de-"
+"synchronization with the AvaTax Portal. Instead, click :guilabel:`Add credit"
+" note` and state: `Sync with AvaTax Portal`. See this documentation: "
+":doc:`../../../accounting/customer_invoices/credit_notes`."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:95
 msgid "Fixed price discounts"
-msgstr ""
+msgstr "Fixed price discounts"

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:97
 msgid ""
@@ -16779,11 +16915,16 @@ msgid ""
 ":guilabel:`Price` to either a positive or negative value. To recalculate the"
 " taxes, click :guilabel:`Compute taxes using Avatax`."
 msgstr ""
+"Add a fixed price discount to a valuable customer by click :guilabel:`Add a "
+"line` on the customer's invoice. Add the product discount and set the "
+":guilabel:`Price` to either a positive or negative value. To recalculate the"
+" taxes, click :guilabel:`Compute taxes using Avatax`."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:102
 msgid ""
 "Tax calculation can even be done on negative subtotals and credit notes."
 msgstr ""
+"Tax calculation can even be done on negative subtotals and credit notes."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:105
 msgid "Logging"
@@ -16795,24 +16936,33 @@ msgid ""
 " or verification of functionality. Logging is accessible through the "
 "*AvaTax* settings."
 msgstr ""
+"It is possible to log Avalara/*AvaTax* actions in Odoo for further analysis,"
+" or verification of functionality. Logging is accessible through the "
+"*AvaTax* settings."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:110
 msgid ""
 "To start logging *AvaTax* actions, first, navigate to the "
 ":menuselection:`Accounting app --> Configuration --> Settings`."
 msgstr ""
+"To start logging *AvaTax* actions, first, navigate to the "
+":menuselection:`Accounting app --> Configuration --> Settings`."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:113
 msgid ""
 "Then, in the :guilabel:`Taxes` section, under the :guilabel:`AvaTax` "
 "settings, click :guilabel:`Start logging for 30 minutes`."
 msgstr ""
+"Then, in the :guilabel:`Taxes` section, under the :guilabel:`AvaTax` "
+"settings, click :guilabel:`Start logging for 30 minutes`."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:116
 msgid ""
 "Upon starting the log process, Odoo will log all Avalara/*AvaTax* actions "
 "performed in the database."
 msgstr ""
+"Upon starting the log process, Odoo will log all Avalara/*AvaTax* actions "
+"performed in the database."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:118
 msgid ""
@@ -16820,54 +16970,61 @@ msgid ""
 ":guilabel:`Start logging for 30 minutes`. This reveals a detailed list of "
 "Avalara/*AvaTax* actions. This list is sortable by the following columns:"
 msgstr ""
+"To view the logs, click on :guilabel:`Show logs` to the right of the "
+":guilabel:`Start logging for 30 minutes`. This reveals a detailed list of "
+"Avalara/*AvaTax* actions. This list is sortable by the following columns:"

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:122
 msgid ":guilabel:`Created on`: timestamp of the *AvaTax* calculation."
-msgstr ""
+msgstr ":guilabel:`Created on`: timestamp of the *AvaTax* calculation."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:123
 msgid ":guilabel:`Created by`: numeric value of the user in the database."
-msgstr ""
+msgstr ":guilabel:`Created by`: numeric value of the user in the database."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:124
 msgid ":guilabel:`Database name`: name of the database."
-msgstr ""
+msgstr ":guilabel:`Database name`: name of the database."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:125
 msgid ""
 ":guilabel:`Type`: two values can be chosen for this field, "
 ":guilabel:`Server` or :guilabel:`Client`."
 msgstr ""
+":guilabel:`Type`: two values can be chosen for this field, "
+":guilabel:`Server` or :guilabel:`Client`."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:127
 msgid ""
 ":guilabel:`Name`: Avalara service name. In this case, it will be *AvaTax*."
 msgstr ""
+":guilabel:`Name`: Avalara service name. In this case, it will be *AvaTax*."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:128
 msgid ":guilabel:`Level`: by default, this will be `INFO`."
-msgstr ""
+msgstr ":guilabel:`Level`: by default, this will be `INFO`."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:129
 msgid ":guilabel:`Path`: indicates the path taken to make the calculation."
-msgstr ""
+msgstr ":guilabel:`Path`: indicates the path taken to make the calculation."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:130
 msgid ":guilabel:`Line`: indicates the line the calculation is made on."
-msgstr ""
+msgstr ":guilabel:`Line`: indicates the line the calculation is made on."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:131
 msgid ":guilabel:`Function`: indicates the calculation taken on the line."
-msgstr ""
+msgstr ":guilabel:`Function`: indicates the calculation taken on the line."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst-1
 msgid "Avalara logging page with top row of list highlighted."
-msgstr ""
+msgstr "Avalara logging page with top row of list highlighted."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:137
 msgid ""
 "Click into the log line to reveal another field, called :guilabel:`Message`."
 msgstr ""
+"Click into the log line to reveal another field, called :guilabel:`Message`."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:139
 msgid ""
@@ -16875,6 +17032,9 @@ msgid ""
 "the creation (or adjustment) of a sales invoice using the Avalara *AvaTax* "
 "API."
 msgstr ""
+"This field populates a raw transcription of the transaction, which involves "
+"the creation (or adjustment) of a sales invoice using the Avalara *AvaTax* "
+"API."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:142
 msgid ""
@@ -16882,12 +17042,17 @@ msgid ""
 "to, line items describing the products or services, tax codes, tax amounts, "
 "and other relevant information."
 msgstr ""
+"The transaction includes details, such as addresses for shipping from and "
+"to, line items describing the products or services, tax codes, tax amounts, "
+"and other relevant information."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:145
 msgid ""
 "The :guilabel:`Message` contains the calculated taxes for different "
 "jurisdictions and confirms the creation (or adjustment) of the transaction."
 msgstr ""
+"The :guilabel:`Message` contains the calculated taxes for different "
+"jurisdictions and confirms the creation (or adjustment) of the transaction."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:149
 msgid ""
@@ -16896,6 +17061,10 @@ msgid ""
 "Then click :icon:`fa-plus` :guilabel:`Add custom field`. This action opens "
 "Odoo *Studio*."
 msgstr ""
+"Custom fields can be made using Odoo *Studio*. Click the :icon:`fa-"
+"ellipsis-v` :guilabel:`(ellipsis)` menu to the far-right of the header row. "
+"Then click :icon:`fa-plus` :guilabel:`Add custom field`. This action opens "
+"Odoo *Studio*."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:154
 msgid ""
@@ -16904,10 +17073,14 @@ msgid ""
 "if Odoo *Studio* is included in the database's current pricing plan. See "
 "this documentation: :doc:`../../../../studio`."
 msgstr ""
+"Odoo *Studio* requires a *custom* pricing plan. Consult the database's "
+"customer success manager for more information on switching plans. Or to see "
+"if Odoo *Studio* is included in the database's current pricing plan. See "
+"this documentation: :doc:`../../../../studio`."

 #: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:160
 msgid ":doc:`avalara_portal`"
-msgstr ""
+msgstr ":doc:`avalara_portal`"

 #: ../../content/applications/finance/accounting/taxes/cash_basis.rst:3
 msgid "Cash basis taxes"
@@ -3163,7 +3163,7 @@ msgstr ""

 #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:31
 msgid "Activity types"
-msgstr ""
+msgstr "أنواع الأنشطة "

 #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:33
 msgid ""
@@ -15,7 +15,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2024-04-29 10:38+0000\n"
+"POT-Creation-Date: 2024-06-21 15:46+0000\n"
 "PO-Revision-Date: 2022-10-04 12:54+0000\n"
 "Last-Translator: Malaz Abuidris <msea@odoo.com>, 2024\n"
 "Language-Team: Arabic (https://app.transifex.com/odoo/teams/41243/ar/)\n"
@@ -1457,14 +1457,14 @@ msgstr ""
 #: ../../content/applications/productivity/documents.rst:12
 msgid ""
 "`Odoo Tutorials: Documents basics "
-"<https://www.odoo.com/slides/slide/documents-basics-674>`_"
+"<https://www.odoo.com/slides/slide/documents-basics-6841?fullscreen=1>`_"
 msgstr ""

 #: ../../content/applications/productivity/documents.rst:13
 msgid ""
 "`Odoo Tutorials: Using Documents with your Accounting App "
-"<https://www.odoo.com/slides/slide/using-documents-with-your-accounting-"
-"app-675?fullscreen=1#>`_"
+"<https://www.odoo.com/slides/slide/accounting-integration-and-workflow-"
+"actions-6853?fullscreen=1>`_"
 msgstr ""

 #: ../../content/applications/productivity/documents.rst:17
@@ -6559,10 +6559,13 @@ msgstr ""

 #: ../../content/applications/productivity/voip/axivox/axivox_config.rst:12
 msgid ""
-"To use this service, `contact Axivox <https://www.axivox.com/contact/>`_ to "
-"open an account. Before doing so, verify that Axivox covers the company's "
-"area, along with the areas the company's users wish to call."
+"To use this service, `contact Axivox <https://www.axivox.com/en/contact/>`_ "
+"to open an account. Before doing so, verify that Axivox covers the company's"
+" area, along with the areas the company's users wish to call."
 msgstr ""
+"To use this service, `contact Axivox <https://www.axivox.com/en/contact/>`_ "
+"to open an account. Before doing so, verify that Axivox covers the company's"
+" area, along with the areas the company's users wish to call."

 #: ../../content/applications/productivity/voip/axivox/axivox_config.rst:19
 msgid ""
@@ -4,7 +4,7 @@
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 # 
 # Translators:
-# Martin Trigaux, 2023
+# Malaz Abuidris <msea@odoo.com>, 2024
 # 
 #, fuzzy
 msgid ""
@@ -13,7 +13,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2021-05-18 07:12+0200\n"
 "PO-Revision-Date: 2022-10-04 12:54+0000\n"
-"Last-Translator: Martin Trigaux, 2023\n"
+"Last-Translator: Malaz Abuidris <msea@odoo.com>, 2024\n"
 "Language-Team: Arabic (https://app.transifex.com/odoo/teams/41243/ar/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -23,11 +23,11 @@ msgstr ""

 #: ../../content/applications/settings.rst:3
 msgid "Settings"
-msgstr "الإعدادات"
+msgstr "الإعدادات "

 #: ../../content/applications/settings/users_and_features.rst:6
 msgid "Users and Features"
-msgstr ""
+msgstr "المستخدمين والخصائص "

 #: ../../content/applications/settings/users_and_features.rst:8
 msgid ""
@@ -35,6 +35,8 @@ msgid ""
 "This includes the Apps you install as well as the number of users currently "
 "in use."
 msgstr ""
+"بصفتك مدير قاعدة البيانات، أنت مسؤول عن استخدامها. يشمل ذلك التطبيقات التي "
+"تقوم بثبيتها بالإضافة إلى عدد المستخدمين النشطين في الوقت الحالي. "

 #: ../../content/applications/settings/users_and_features.rst:12
 msgid ""
@@ -44,6 +46,12 @@ msgid ""
 "subscription amount significantly (or switch you from a free account to a "
 "paying one on our online platform)."
 msgstr ""
+"أودو هو العديد من الأشياء (برنامج لتخطيط موارد المؤسسات، نظام إدارة محتوى، "
+"تطبيق لإدارة علاقات العملاء، واجهة خلفية للتجارة الإلكترونية، إلخ..)، ولكنه "
+"*ليس* هاتفاً ذكياً. عليك توخي الحذر عند إضافة/إزالة الخصائص (خصوصاً "
+"التطبيقات) في قاعدة بياناتك، حيث قد يؤثر ذلك على تكلفة اشتراكك بشكل كبير (أو"
+" قد يؤدي إلى انتقالك من الحساب المجاني إلى الحساب المدفوع على منصتنا عبر "
+"الإنترنت). "

 #: ../../content/applications/settings/users_and_features.rst:18
 msgid ""
@@ -52,6 +60,9 @@ msgid ""
 "to test them on a duplicate of your database first. That way, if something "
 "goes wrong, your day-to-day business is not impacted."
 msgstr ""
+"تحتوي هذه الصفحة على معلومات حول كيفية إدارة مثيلات أودو الخاصة بك. قبل "
+"القيام بتلك العمليات، نوصي **بشدة** اختبارها أولاً على نسخة من قاعدة "
+"البيانات. بهذه الطريقة، إذا حدث خطأ ما، لن يتأثر عملك الجاري بذلك الخطأ. "

 #: ../../content/applications/settings/users_and_features.rst:23
 msgid ""
@@ -59,6 +70,9 @@ msgid ""
 " <duplicate_online>` and :ref:`on premise <duplicate_premise>` "
 "installations."
 msgstr ""
+"ستجد الدلائل التي توضح كيفية إنشاء نسخة مطابقة لقاعدة البيانات لكل من إصداري"
+" أودو :ref:`أونلاين <duplicate_online>` و :ref:`الاستضافة الذاتية "
+"<duplicate_premise>`. "

 #: ../../content/applications/settings/users_and_features.rst:27
 msgid ""
@@ -66,35 +80,42 @@ msgid ""
 "issue while carrying out these procedures, please contact us through our "
 "`support form <https://www.odoo.com/help>`__."
 msgstr ""
+"إذا كانت لديك أسئلة حول محتوى هذه الصفحة أو إذا واجهتك مشكلة أثناء تنفيذ هذه"
+" الإجراءات، فلا تتردد في التواصل معنا عن طريق `استمارة الدعم "
+"<https://www.odoo.com/help>`__. "

 #: ../../content/applications/settings/users_and_features.rst:33
 msgid "Deactivating Users"
-msgstr ""
+msgstr "تعطيل المستخدمين "

 #: ../../content/applications/settings/users_and_features.rst:35
 msgid ""
 "Make sure you have sufficient **administrative rights** if you want to "
 "change the status of any of your users."
 msgstr ""
+"تأكد من أنك تملك **صلاحيات الوصول الإدارية** الكافية إذا كنت ترغب في تغيير "
+"حالة أي من المستخدمين لديك. "

 #: ../../content/applications/settings/users_and_features.rst:38
 msgid ""
 "In your Odoo instance, click on **Settings**. You will have a section "
 "showing you the active users on your database. Click on **Manage Users.**"
 msgstr ""
+"في مثيل أودو الخاص بك،قم بالضغط على **الإعدادات**. سيكون لديك قسم يُظهِر "
+"المستخدمين النشطين في قاعدة بياناتك. اضغط على **إدارة المستخدمين.** "

 #: ../../content/applications/settings/users_and_features.rst:42
 #: ../../content/applications/settings/users_and_features.rst:79
 msgid "|settings|"
-msgstr ""
+msgstr "|settings|"

 #: ../../content/applications/settings/users_and_features.rst:42
 msgid "|browse_users|"
-msgstr ""
+msgstr "|browse_users|"

 #: ../../content/applications/settings/users_and_features.rst:45
 msgid "You'll then see the list of your users."
-msgstr ""
+msgstr "سترى عندها قائمة بمستخدميك. "

 #: ../../content/applications/settings/users_and_features.rst:50
 msgid ""
@@ -102,6 +123,9 @@ msgid ""
 "from the *Portal Users* which are free). If you remove this filter, you'll "
 "get all your users (the ones you pay for and the portal ones)"
 msgstr ""
+"يُظهر فلتر *المستخدمين الداخليين* المحدد مسبقًا المستخدمين المدفوعين "
+"(يختلفون عن *مستخدمي البوابة* المجانيين). إذا قمت بإزالة هذا الفلتر، فستحصل "
+"على كافة المستخدمين (المستخدمين المدفوعين ومستخدمي البوابة) "

 #: ../../content/applications/settings/users_and_features.rst:55
 msgid ""
@@ -109,18 +133,21 @@ msgid ""
 "you are on the userform, click on the Action drop down menu, and then click "
 "on Archive."
 msgstr ""
+"في قائمة المستخدمين الخاصة بك،قم بالضغط على المستخدم الذي ترغب في تعطيله. "
+"بمجرد دخولك إلى استمارة المستخدم، قم بالضغط على  القائمة المنسدلة \"إجراء\"،"
+" ثم اضغط على \"أرشفة\". "

 #: ../../content/applications/settings/users_and_features.rst:63
 msgid "The user is now deactivated."
-msgstr ""
+msgstr "تم تعطيل المستخدم. "

 #: ../../content/applications/settings/users_and_features.rst:65
 msgid "**Never** deactivate the main user (*admin*)"
-msgstr ""
+msgstr "لا تقم **مطلقًا** بتعطيل المستخدم الرئيسي (*admin*) "

 #: ../../content/applications/settings/users_and_features.rst:68
 msgid "Uninstalling Apps"
-msgstr ""
+msgstr "إلغاء تثبيت التطبيقات "

 #: ../../content/applications/settings/users_and_features.rst:70
 msgid ""
@@ -128,6 +155,9 @@ msgid ""
 "<duplicate_online>` of your database before making any changes (*especially*"
 " installing/uninstalling apps)."
 msgstr ""
+"تأكد أولاً من اختبار ما أنت على وشك القيام به على :ref:`نسخة مطابقة لقاعدة "
+"البيانات <duplicate_online>` قبل إجراء أي تغييرات (*خاصة* تثبيت/إلغاء تثبيت "
+"التطبيقات). "

 #: ../../content/applications/settings/users_and_features.rst:74
 msgid ""
@@ -135,10 +165,13 @@ msgid ""
 "to see how many applications you have installed. Click on **Browse Apps** to"
 " access the list of your installed applications."
 msgstr ""
+"في مثيل أودو الخاص بك، قم بالضغط على **الإعدادات**؛ ستتمكن في هذا التطبيق من"
+" معرفة عدد التطبيقات التي قمت بتثبيتها. اضغط على **تصفح التطبيقات** للوصول "
+"إلى قائمة التطبيقات المثبتة لديك. "

 #: ../../content/applications/settings/users_and_features.rst:79
 msgid "|browse_apps|"
-msgstr ""
+msgstr "|browse_apps|"

 #: ../../content/applications/settings/users_and_features.rst:82
 msgid ""
@@ -146,6 +179,9 @@ msgid ""
 "applications. Click on the application you want to uninstall. Then, on the "
 "form of the application, click on **Uninstall**."
 msgstr ""
+"في لوحة بيانات تطبيقاتك، سترى كافة أيقونات تطبيقاتك. قم بالضغط على التطبيق "
+"الذي ترغب في إلغاء تثبيته، ثم اضفط على **إلغاء التثبيت** في استمارة التطبيق."
+" "

 #: ../../content/applications/settings/users_and_features.rst:89
 msgid ""
@@ -156,19 +192,25 @@ msgid ""
 "permanently disappear). If you are sure you still want to uninstall it, then"
 " click **Confirm**."
 msgstr ""
+"تحتوي بعض التطبيقات على تطبيقات معتمدة عليها، مثل الفوترة والمتجر الإلكتروني"
+" وما إلى ذلك. لذلك، سيعرض النظام رسالة تحذيرية لإعلامك بما هو على وشك أن تتم"
+" إزالته. إذا قمت بإلغاء تثبيت تطبيقك، فسيتم إلغاء تثبيت كافة التطبيقات "
+"المعتمدة عليه أيضاً (وستختفي البيانات الموجودة فيه نهائياً). إذا كنت متأكداً"
+" من أنك لا تزال ترغب في إلغاء تثبيته، فانقر فوق **تأكيد**. "

 #: ../../content/applications/settings/users_and_features.rst:96
 msgid ""
 "Last, after having checked the warning message (if any), click **Confirm**."
 msgstr ""
+"أخيراً، بعد التحقق من رسالة التحذير (إن وجدت)، اضغط على زر **تأكيد**. "

 #: ../../content/applications/settings/users_and_features.rst:101
 msgid "You have finished uninstalling your application."
-msgstr ""
+msgstr "لقد انتهيت من إلغاء تثبيت التطبيق الخاص بك."

 #: ../../content/applications/settings/users_and_features.rst:104
 msgid "Good to know"
-msgstr ""
+msgstr "من الجيد معرفته "

 #: ../../content/applications/settings/users_and_features.rst:106
 msgid ""
@@ -179,6 +221,11 @@ msgid ""
 "*do not know how you work* and therefore cannot validate these kinds of "
 "operations."
 msgstr ""
+"**إلغاء تثبيت التطبيقات وإدارة المستخدمين وما إلى ذلك أمر متروك لك**: لا "
+"يمكن لأي شخص آخر معرفة ما إذا كان سير أعمالك معطلاً أفضل منك. إذا أردنا "
+"إلغاء تثبيت التطبيقات لك، فلن نتمكن أبدًا من معرفة ما إذا كانت البيانات ذات "
+"الصلة قد تمت إزالتها أو ما إذا كان أحد تدفقات أعمالك معطلاً لأننا *لا نعرف "
+"كيف تعمل* وبالتالي لا يمكننا التحقق من صحة هذه الأنواع من العمليات. "

 #: ../../content/applications/settings/users_and_features.rst:112
 msgid ""
@@ -189,6 +236,11 @@ msgid ""
 "need or use the Website itself, it is needed for the Online Quotes feature "
 "to work properly."
 msgstr ""
+"**تحتوي تطبيقات Odoo على تبعيات**: هذا يعني أنك قد تحتاج إلى تثبيت وحدات لا "
+"تستخدمها بشكل نشط للوصول إلى بعض ميزات Odoo التي قد تحتاجها. على سبيل "
+"المثال، يلزم وجود تطبيق Website Builder لتتمكن من عرض أسعاره لعميلك في صفحة "
+"ويب. على الرغم من أنك قد لا تحتاج إلى موقع الويب نفسه أو تستخدمه، إلا أنه "
+"ضروري لكي تعمل ميزة عروض الأسعار عبر الإنترنت بشكل صحيح. "

 #: ../../content/applications/settings/users_and_features.rst:119
 msgid ""
@@ -196,3 +248,7 @@ msgid ""
 "database): that way you can know what other apps may be required, etc. This "
 "will avoid surprises when uninstalling or when receiving your invoices."
 msgstr ""
+"**اختبر دائمًا تثبيت/إزالة التطبيق على نسخة مكررة** (أو على قاعدة بيانات "
+"تجريبية مجانية): وبهذه الطريقة يمكنك معرفة التطبيقات الأخرى التي قد تكون "
+"مطلوبة، وما إلى ذلك. سيؤدي هذا إلى تجنب المفاجآت عند إلغاء التثبيت أو عند "
+"استلام فواتيرك. "
@@ -16,7 +16,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2024-05-30 07:20+0000\n"
+"POT-Creation-Date: 2024-06-21 15:46+0000\n"
 "PO-Revision-Date: 2022-10-04 12:54+0000\n"
 "Last-Translator: Malaz Abuidris <msea@odoo.com>, 2024\n"
 "Language-Team: Arabic (https://app.transifex.com/odoo/teams/41243/ar/)\n"
@@ -761,7 +761,7 @@ msgstr ":doc:`../checkout_payment_shipping/checkout`"
 #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:14
 #: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:95
 #: ../../content/applications/websites/website/configuration.rst:5
-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:24
+#: ../../content/applications/websites/website/configuration/cookies_bar.rst:15
 #: ../../content/applications/websites/website/configuration/recaptcha.rst:19
 #: ../../content/applications/websites/website/reporting/link_tracker.rst:10
 msgid "Configuration"
@@ -877,14 +877,12 @@ msgstr ""
 ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method`"

 #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:35
-#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:83
 msgid ""
 ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing`"
 msgstr ""
 ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing`"

 #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:36
-#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:85
 msgid ""
 ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack`"
 msgstr ""
@@ -908,37 +906,37 @@ msgid ""
 "labels."
 msgstr ""

-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:49
-msgid ""
-":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`"
-msgstr ""
-":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`"
-
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:50
-msgid ""
-":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials`"
-msgstr ""
-":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials`"
-
 #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:51
 msgid ""
-":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials`"
+":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`"
 msgstr ""
-":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials`"
+":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`"

 #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:52
+msgid ""
+":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials`"
+msgstr ""
+":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials`"
+
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:53
+msgid ""
+":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials`"
+msgstr ""
+":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials`"
+
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:54
 #: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:84
 msgid ""
-":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels`"
+":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels`"
 msgstr ""
-":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels`"
+":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels`"

-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:55
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:57
 #: ../../content/applications/websites/ecommerce/managing_products/products.rst:203
 msgid "Website availability"
 msgstr ""

-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:57
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:59
 msgid ""
 "Shipping methods can be made available on **specific** websites *only*, if "
 "desired. To do so, go to :menuselection:`Website --> Configuration --> "
@@ -948,11 +946,11 @@ msgid ""
 "available on *all* websites."
 msgstr ""

-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:63
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:65
 msgid "Delivery method at checkout"
 msgstr ""

-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:65
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:67
 msgid ""
 "Customers can choose the shipping method at the end of the checkout process,"
 " at the :guilabel:`Confirm Order` step."
@@ -1353,6 +1351,18 @@ msgid ""
 "in stock."
 msgstr ""

+#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:83
+msgid ""
+":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing`"
+msgstr ""
+":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing`"
+
+#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:85
+msgid ""
+":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack`"
+msgstr ""
+":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack`"
+
 #: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:88
 msgid "Returns and refunds"
 msgstr ""
@@ -6019,140 +6029,89 @@ msgstr ""

 #: ../../content/applications/websites/website/configuration/cookies_bar.rst:5
 msgid ""
-"Cookies are small text files sent to your device when you visit a website. "
-"They are processed and stored by your browser and contain information about "
-"your visit, such as login data, location, language, etc. There are two main "
-"types of cookies:"
-msgstr ""
-
-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:9
-msgid ""
-"Essential cookies, which are necessary for the website to function properly;"
+"**Cookies** are small text files sent to your device when you visit a "
+"website. They are processed and stored by your browser and track user "
+"information like login details, preferences, and browsing history. "
+"**Essential cookies** are necessary for the website to function, while "
+"**optional cookies** are used to analyze behavior or display ads."
 msgstr ""

 #: ../../content/applications/websites/website/configuration/cookies_bar.rst:10
 msgid ""
-"Non-essential or optional cookies, which are used to analyze your behavior "
-"or display advertisements."
-msgstr ""
-
-#: ../../content/applications/websites/website/configuration/cookies_bar.rst-1
-msgid "Example of a cookies bar with the popup layout."
+"Data protection laws require notifying users about data collection methods "
+"and purposes. **Cookies bar** fulfill this obligation by informing users on "
+"their first visit and allowing them to decide whether to store all or only "
+"essential cookies on their device."
 msgstr ""

 #: ../../content/applications/websites/website/configuration/cookies_bar.rst:17
 msgid ""
-"Notifying users about data collection, as well as its methods and purposes, "
-"is required by data protection laws such as `GDPR <https://gdpr.eu>`_. "
-"Cookies bars are commonly used to fulfill this obligation in a user-friendly"
-" and transparent manner. They are displayed immediately upon a user's first "
-"visit to inform them that the website uses cookies and let them decide "
-"whether they want to store non-essential cookies on their device."
+"To enable the cookies bar on your website, go to :menuselection:`Website -->"
+" Configuration --> Settings` and enable :guilabel:`Cookies Bar` in the "
+":guilabel:`Privacy` section."
 msgstr ""
-"Notifying users about data collection, as well as its methods and purposes, "
-"is required by data protection laws such as `GDPR <https://gdpr.eu>`_. "
-"Cookies bars are commonly used to fulfill this obligation in a user-friendly"
-" and transparent manner. They are displayed immediately upon a user's first "
-"visit to inform them that the website uses cookies and let them decide "
-"whether they want to store non-essential cookies on their device."

-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:26
+#: ../../content/applications/websites/website/configuration/cookies_bar.rst:21
 msgid ""
-"To enable the cookies bar on your Odoo website, go to "
-":menuselection:`Website --> Configuration` and enable :guilabel:`Cookies "
-"Bar` in the :guilabel:`Privacy` section."
+"The :ref:`Cookies Policy <cookies-bar/policy>` page (/cookie-policy`) is "
+"automatically created when you enable the cookies bar."
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/cookies_bar.rst:27
+msgid "Customization"
 msgstr ""

 #: ../../content/applications/websites/website/configuration/cookies_bar.rst:29
 msgid ""
-"You can :ref:`customize the appearance of your cookies bar <cookies-"
-"bar/customization>` and :ref:`edit the content of the related Cookie Policy "
-"page <cookies-bar/policy>`."
+"To adapt the display of the cookies bar, click :guilabel:`Edit`, go to the "
+":guilabel:`Invisible Elements` section at the bottom of the panel, and click"
+" :guilabel:`Cookies Bar`. You can modify the :guilabel:`Layout` and "
+":guilabel:`Size` of the cookies bar, and enable :guilabel:`Backdrop` to gray"
+" out the page in the background when the cookies bar is displayed on the "
+"screen."
 msgstr ""

 #: ../../content/applications/websites/website/configuration/cookies_bar.rst:35
-msgid "Customization"
-msgstr ""
-
-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:37
 msgid ""
-"To adapt the display of the cookies bar, click :guilabel:`Edit` and select "
-"the :guilabel:`Cookies Bar` building block in the :guilabel:`Invisible "
-"Elements` at the bottom of the panel. Customize it using the options in the "
-":guilabel:`Customize` tab in the edit panel. Three :guilabel:`Layouts` are "
-"available:"
+"Click anywhere in the building block to further customize the appearance of "
+"the cookies bar using :guilabel:`Block`, :guilabel:`Column` and/or "
+":guilabel:`Inline Text` customization options."
 msgstr ""

-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:42
-msgid ":guilabel:`Discrete`: thin bar"
-msgstr ""
-
-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:43
-msgid ":guilabel:`Classic`: banner"
-msgstr ""
-
-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:44
-msgid ""
-":guilabel:`Popup`: you can change the popup's :guilabel:`Position` to the "
-":guilabel:`Top`, :guilabel:`Middle`, or :guilabel:`Bottom` of the screen."
-msgstr ""
-
-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:47
-msgid "You can also:"
-msgstr ""
-
-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:49
-msgid "modify the :guilabel:`Size` of the cookies bar;"
-msgstr ""
-
-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:50
-msgid ""
-"enable :guilabel:`Backdrop` to gray out the page in the background when the "
-"cookies bar is displayed on the screen;"
-msgstr ""
-
-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:52
-msgid ""
-"further customize the appearance of the cookies bar using :guilabel:`Block` "
-"and/or :guilabel:`Column` customization options, which are available after "
-"clicking anywhere in the building block."
-msgstr ""
-
-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:56
+#: ../../content/applications/websites/website/configuration/cookies_bar.rst:38
 msgid ""
 "To edit the contents of the cookies bar (i.e., the consent message), click "
 "directly in the building block."
 msgstr ""

-#: ../../content/applications/websites/website/configuration/cookies_bar.rst-1
-msgid "Odoo Website's edit panel to customize the cookies bar."
+#: ../../content/applications/websites/website/configuration/cookies_bar.rst:44
+msgid "Cookies policy"
 msgstr ""

-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:65
-msgid "Cookie policy"
-msgstr ""
-
-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:67
+#: ../../content/applications/websites/website/configuration/cookies_bar.rst:46
 msgid ""
 "When you enable the cookies bar for your website, Odoo creates the **Cookie "
-"Policy** page (`/cookie-policy`) with the list of essential and optional "
-"cookies. To access it, click the :guilabel:`Cookie Policy` hyperlink in the "
-"cookies bar or open the page from :menuselection:`Website --> Site --> "
-"Pages`."
+"Policy** page (`/cookie-policy`) containing a non-exhaustive list of "
+"cookies, with their purpose and examples. To access it, click the "
+":guilabel:`Cookie Policy` hyperlink in the cookies bar or open the page from"
+" :menuselection:`Website --> Site --> Pages`."
 msgstr ""

-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:72
+#: ../../content/applications/websites/website/configuration/cookies_bar.rst:51
 msgid ""
-"The contents of the page can be adapted based on your website's features and"
-" characteristics if needed."
+"To adapt the content of the page according to your needs, click the "
+":guilabel:`Edit` button."
 msgstr ""

-#: ../../content/applications/websites/website/configuration/cookies_bar.rst:76
+#: ../../content/applications/websites/website/configuration/cookies_bar.rst:54
 msgid ""
-"You could add a link providing access to this page, in your website's "
-"footer, for example."
+"You could add a link to this page in your website's footer, for example."
 msgstr ""

+#: ../../content/applications/websites/website/configuration/cookies_bar.rst:57
+msgid ":doc:`Pages <../pages>`"
+msgstr ":doc:`Pages <../pages>`"
+
 #: ../../content/applications/websites/website/configuration/domain_names.rst:3
 msgid "Domain names"
 msgstr "أسماء النطاقات "
@@ -12,7 +12,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2024-04-29 10:38+0000\n"
+"POT-Creation-Date: 2024-06-21 15:46+0000\n"
 "PO-Revision-Date: 2024-04-04 12:31+0000\n"
 "Last-Translator: Larissa Manderfeld, 2024\n"
 "Language-Team: German (https://app.transifex.com/odoo/teams/41243/de/)\n"
@@ -618,6 +618,490 @@ msgstr ":doc:`/applications/productivity/discuss`"
 msgid ":doc:`/applications/productivity/discuss/team_communication`"
 msgstr ":doc:`/applications/productivity/discuss/team_communication`"

+#: ../../content/applications/essentials/contacts.rst:3
+msgid "Contacts"
+msgstr "Kontakte"
+
+#: ../../content/applications/essentials/contacts.rst:5
+msgid ""
+"The *Contacts* application comes installed on all Odoo databases. Contacts "
+"are created for customers the company does business with through Odoo. A "
+"contact is a repository of vital business information, facilitating "
+"communication and business transactions."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:10
+msgid "Contact form"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:12
+msgid ""
+"To create a new contact, navigate to the :menuselection:`Contacts app`, and "
+"click :guilabel:`Create`. A new form appears where various contact "
+"information can be added."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:16
+msgid "Contact type"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:18
+msgid ""
+"Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` "
+"contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, "
+"depending on the type of contact that is being added."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:22
+msgid "Name"
+msgstr "Name"
+
+#: ../../content/applications/essentials/contacts.rst:24
+msgid ""
+"First, fill in the name of the :guilabel:`Individual` or "
+":guilabel:`Company`. This is how the name appears throughout the database. "
+"This field is **mandatory**."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:28
+msgid ""
+":guilabel:`Individual` contacts can have a :guilabel:`Company` contact "
+"linked to it. After selecting :guilabel:`Individual`, a new "
+":guilabel:`Company Name...` field appears below the first name field."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:33
+msgid "Address"
+msgstr "Adresse"
+
+#: ../../content/applications/essentials/contacts.rst:35
+msgid ""
+"Next, enter the :guilabel:`Address` of the :guilabel:`Company` or "
+":guilabel:`Individual`."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:38
+msgid ""
+"If the :guilabel:`Individual` option is chosen, then the *type of address* "
+"can be chosen from a drop-down menu. Options for this drop-down menu "
+"include: :guilabel:`Contact`, :guilabel:`Invoice Address`, "
+":guilabel:`Delivery Address`, :guilabel:`Other Address`, and "
+":guilabel:`Private Address`."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:44
+msgid "Additional fields"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:46
+msgid ""
+"Additional details are included on the initial form. The following fields "
+"are available:"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:48
+msgid ":guilabel:`VAT`: Value Added Tax number."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:49
+msgid ""
+":guilabel:`Citizen Identification`: citizen or government identification "
+"number (only available on :guilabel:`Individual`)."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:51
+msgid ""
+":guilabel:`Job Position`: list the job position of the "
+":guilabel:`Individual` (only available on :guilabel:`Individual`)."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:53
+msgid ""
+":guilabel:`Phone`: list phone number (with country code). Make a call, send "
+"an SMS, or WhatsApp message by hovering over the field on the saved form, "
+"and clicking the desired option."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:55
+msgid ""
+":guilabel:`Mobile`: list mobile phone number (with country code). Make a "
+"call, send an SMS, or WhatsApp message by hovering over the field on the "
+"saved form, and clicking on the desired option."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:57
+msgid ":guilabel:`Email`: enter the email address with the domain."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:58
+msgid ""
+":guilabel:`Website`: enter the full website address, starting with `http` or"
+" `https`."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:59
+msgid ""
+":guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, "
+":guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new"
+" one directly from this field."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:61
+msgid ""
+":guilabel:`Tags`: enter preconfigured tags by typing them in the field, or "
+"clicking the drop-down menu, and selecting one. To create a new one, type "
+"the new tag in the field, and click :guilabel:`Create` from the resulting "
+"drop-down menu."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:66
+msgid "Contacts & Addresses tab"
+msgstr "Reiter „Kontakte & Adressen“"
+
+#: ../../content/applications/essentials/contacts.rst:68
+msgid ""
+"At the bottom of the contact form are several tabs. On the "
+":guilabel:`Contacts & Addresses` tab, contacts can be added that are "
+"associated with a :guilabel:`Company` and related addresses. For example, a "
+"specific contact person for the company can be listed here."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:72
+msgid ""
+"Multiple addresses can be added on both :guilabel:`Individual` and "
+":guilabel:`Company` contacts. To do so, click :guilabel:`Add` in the "
+":guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create "
+"Contact` pop-up form, in which additional addresses can be configured."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst-1
+msgid "Add a contact/address to the contact form."
+msgstr "Dem Kontaktformular einen Kontakt/Adresse hinzufügen."
+
+#: ../../content/applications/essentials/contacts.rst:80
+msgid ""
+"On the :guilabel:`Create Contact` pop-up form, start by clicking the default"
+" :guilabel:`Other Address` field at the top to reveal a drop-down menu of "
+"address-related options."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:83
+msgid "Select any of the following options:"
+msgstr "Wählen Sie eine der folgenden Optionen aus:"
+
+#: ../../content/applications/essentials/contacts.rst:85
+msgid ""
+":guilabel:`Contact`: adds another contact to the existing contact form."
+msgstr ""
+":guilabel:`Kontakt`: fügt dem bestehenden Kontaktformular einen weiteren "
+"Kontakt hinzu."
+
+#: ../../content/applications/essentials/contacts.rst:86
+msgid ""
+":guilabel:`Invoice Address`: adds a specific invoice address to the existing"
+" contact form."
+msgstr ""
+":guilabel:`Rechnungsadresse`: fügt dem bestehenden Kontaktformular eine "
+"bestimmte Rechnungsadresse hinzu."
+
+#: ../../content/applications/essentials/contacts.rst:87
+msgid ""
+":guilabel:`Delivery Address`: adds a specific delivery address to the "
+"existing contact form."
+msgstr ""
+":guilabel:`Lieferadresse`: fügt dem bestehenden Kontaktformular eine "
+"bestimmte Lieferadresse hinzu."
+
+#: ../../content/applications/essentials/contacts.rst:88
+msgid ""
+":guilabel:`Other Address`: adds an alternate address to the existing contact"
+" form."
+msgstr ""
+":guilabel:`Andere Adresse`: fügt dem bestehenden Kontaktformular eine "
+"alternative Adresse hinzu."
+
+#: ../../content/applications/essentials/contacts.rst:89
+msgid ""
+":guilabel:`Private Address`: adds a private address to the existing contact "
+"form."
+msgstr ""
+":guilabel:`Privatadresse`: fügt dem bestehenden Kontaktformular eine "
+"Privatadresse hinzu."
+
+#: ../../content/applications/essentials/contacts.rst-1
+msgid "Create a new contact/address on a contact form."
+msgstr ""
+"Einen neuen Kontakt/eine neue Adresse auf dem Kontaktformular hinzufügen."
+
+#: ../../content/applications/essentials/contacts.rst:95
+msgid ""
+"Once an option is selected, enter the corresponding contact information that"
+" should be used for the specified address type."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:98
+msgid ""
+"Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, "
+"along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:101
+msgid ""
+"Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` "
+"address type has been selected. This is similar to the "
+":guilabel:`Individual` contact."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:104
+msgid ""
+"To add a note, click on the text field next to :guilabel:`Notes`, and write "
+"anything that is applicable to the customer or contact."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:107
+msgid ""
+"Then, click :guilabel:`Save & Close` to save the address, and close the "
+":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save "
+"the address, and immediately input another one."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:111
+msgid "Sales & Purchase tab"
+msgstr "Reiter „Verkauf & Einkauf“"
+
+#: ../../content/applications/essentials/contacts.rst:113
+msgid ""
+"Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the "
+"*Sales*, *Purchase*, **or** *Point of Sale* applications are installed."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:116
+msgid ""
+"The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & "
+"Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down "
+"menu."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:120
+msgid "Sales section"
+msgstr "Bereich „Verkauf“"
+
+#: ../../content/applications/essentials/contacts.rst:122
+msgid ""
+"Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can "
+"be assigned to a contact. To do that, click the :guilabel:`Salesperson` "
+"drop-down field, and select one. Create a new :guilabel:`Salesperson` by "
+"typing the user's name, and making the appropriate selection."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:126
+msgid ""
+"Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can "
+"also be set, if needed. Click the drop-down menu next to :guilabel:`Payment "
+"Terms`, and change it to one of the preselected :guilabel:`Payment Terms`, "
+"or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down "
+"menu to choose the appropriate :guilabel:`Pricelist`."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:131
+msgid ""
+"Click into the :guilabel:`Delivery Method` field to select an option from "
+"the drop-down menu."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:134
+msgid "Point Of Sale section"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:136
+msgid ""
+"Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` "
+"that can be used to identify the contact. Use the :guilabel:`Loyalty Points`"
+" field to track points the user won as part of a *Loyalty Program*."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:141
+msgid "Purchase section"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:143
+msgid ""
+"Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a "
+"preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` "
+"can be set here, as well."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:147
+msgid "Misc section"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:149
+msgid ""
+"Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add "
+"any additional information for this contact. If this contact should only be "
+"accessible for one company in a multi-company database, select it from the "
+":guilabel:`Company` field drop-down list. Use the :guilabel:`Website` drop-"
+"down menu to restrict the publishing of this contact to one website (if "
+"working on a database with multiple websites). Select one or more "
+":guilabel:`Website Tags` to assist in filtering published customers on the "
+"`/customers` website page. Select an :guilabel:`Industry` for this contact "
+"from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a "
+"*Helpdesk* SLA policy to this contact."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:159
+msgid "Accounting tab"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:161
+msgid ""
+"The :guilabel:`Accounting` tab appears when the *Accounting* application is "
+"installed. Here, a user can add any related :guilabel:`Bank Accounts`, or "
+"set default :guilabel:`Accounting entries`."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:164
+msgid ""
+"Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field "
+"to enter a Legal Entity Identifier, if necessary."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:168
+msgid "Internal Notes tab"
+msgstr "Reiter „Interne Notizen“"
+
+#: ../../content/applications/essentials/contacts.rst:170
+msgid ""
+"Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` "
+"tab, where notes can be left on this contact form, just like on the contact "
+"form noted above."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:174
+msgid "Partner Assignment tab"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:176
+msgid ""
+"Next is the :guilabel:`Partner Assignment` tab, which by default, includes a"
+" :guilabel:`Geolocation` section, and other partner options, including "
+":guilabel:`Partner Activation` and :guilabel:`Partner Review` "
+"configurations. These are **only** present when the *Enterprise Resellers* "
+"module is installed."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:182
+msgid "Membership tab"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:184
+msgid ""
+"Finally, there is the :guilabel:`Membership` tab, which can help users "
+"manage any memberships that are being offered to this specific contact. It "
+"should be noted that this tab only appears when the *Members* applications "
+"is installed."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:189
+msgid "Smart buttons"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:191
+msgid ""
+"At the top of the contact form, there are some additional options available,"
+" known as *smart buttons*."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:194
+msgid ""
+"Here, Odoo displays a variety of records, related to this contact, that were"
+" created on other apps. Odoo integrates information from every single app, "
+"so there are many smart buttons."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:198
+msgid ""
+"For example, there is an :guilabel:`Opportunities` smart button, where all "
+"the opportunities related to this customer from the *CRM* app are "
+"accessible."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:202
+msgid ""
+"If the corresponding applications are installed, their related smart buttons"
+" appear automatically on a contact form."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:205
+msgid ""
+"A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS "
+"Orders`, :guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the "
+":guilabel:`More` smart button reveals additional options, via a drop-down "
+"menu. A user can even quickly access :guilabel:`Purchases`, "
+":guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, "
+":guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the "
+":guilabel:`Partner Ledger` connected to this contact."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:211
+msgid ""
+"Deliveries, documents, loyalty cards, and direct debits are *also* linked to"
+" smart buttons, like this, should there be any outstanding/on-file for this "
+"contact."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:214
+msgid ""
+"If the contact is a partner, the user can visit their partner page on the "
+"Odoo-built website by clicking the :guilabel:`Go to Website` smart button."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:218
+msgid "Archive contacts"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:220
+msgid ""
+"If a user decides they no longer want to have this contact active, the "
+"record can be archived. To do that, go to the :icon:`fa-cog` "
+":guilabel:`Action` menu at the top of the contact form, and click "
+":guilabel:`Archive`."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:224
+msgid ""
+"Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-"
+"up window."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:226
+msgid ""
+"With this contact successfully archived, as indicated by a banner at the "
+"top, they do not show up in the main contacts page, but they can still be "
+"searched for with the :guilabel:`Archived` filter."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:230
+msgid ""
+"A contact can be *unarchived*, if the user decides to work with them again. "
+"To do that, just click the :icon:`fa-cog` :guilabel:`Action` menu again at "
+"the top of the archived contact form, and click :guilabel:`Unarchive`. Upon "
+"doing so, the :guilabel:`Archived` banner is removed, and the contact is "
+"restored."
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:236
+msgid ""
+":doc:`Add different addresses in CRM "
+"<../sales/sales/send_quotations/different_addresses>`"
+msgstr ""
+
+#: ../../content/applications/essentials/contacts.rst:237
+msgid ""
+"`Odoo's eLearning Contacts tutorial "
+"<https://www.odoo.com/slides/slide/contacts-2527?fullscreen=1>`_"
+msgstr ""
+
 #: ../../content/applications/essentials/export_import_data.rst:3
 msgid "Export and import data"
 msgstr "Daten exportieren und importieren"
@@ -2200,6 +2684,11 @@ msgid ""
 ":guilabel:`Contacts` section. Under the :guilabel:`Contacts` section, where "
 "it says :guilabel:`Odoo IAP`, click :guilabel:`View My Services`."
 msgstr ""
+"Gehen Sie zunächst zur :menuselection:`Einstellungen-App` und geben Sie "
+"`IAP` in die Leiste :guilabel:`Suchen ...` ein. Alternativ können Sie auch "
+"zum Abschnitt :guilabel:`Kontakte` scrollen. Unter dem Abschnitt "
+":guilabel:`Kontakte`, unter :guilabel:`Odoo IAP`, klicken Sie auf "
+":guilabel:`Meine Services ansehen`."

 #: ../../content/applications/essentials/in_app_purchase.rst-1
 msgid ""
@@ -2259,6 +2748,10 @@ msgid ""
 ":guilabel:`Search...` bar. Under the :guilabel:`Contacts` section, where it "
 "says :guilabel:`Odoo IAP`, click :guilabel:`View My Services`."
 msgstr ""
+"Gehen Sie zur :menuselection:`Einstellungen-App` und geben Sie `IAP` in die "
+"Leiste :guilabel:`Suchen ...` ein. Unter dem Abschnitt :guilabel:`Kontakte`,"
+" unter :guilabel:`Odoo IAP`, klicken Sie auf :guilabel:`Meine Services "
+"ansehen`."

 #: ../../content/applications/essentials/in_app_purchase.rst:180
 msgid ""
@@ -9,8 +9,8 @@
 # Martin Trigaux, 2024
 # Johannes Croe <jcr@odoo.com>, 2024
 # Chris Egal <sodaswed@web.de>, 2024
-# Larissa Manderfeld, 2024
 # Wil Odoo, 2024
+# Larissa Manderfeld, 2024
 # 
 #, fuzzy
 msgid ""
@@ -19,7 +19,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2024-05-30 07:20+0000\n"
 "PO-Revision-Date: 2022-10-04 12:53+0000\n"
-"Last-Translator: Wil Odoo, 2024\n"
+"Last-Translator: Larissa Manderfeld, 2024\n"
 "Language-Team: German (https://app.transifex.com/odoo/teams/41243/de/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -528,7 +528,7 @@ msgstr ":doc:`../finance/accounting/get_started/multi_currency`"

 #: ../../content/applications/general/companies/digest_emails.rst:3
 msgid "Digest emails"
-msgstr ""
+msgstr "Übersichts-E-Mails"

 #: ../../content/applications/general/companies/digest_emails.rst:5
 msgid ""
@@ -536,6 +536,9 @@ msgid ""
 "organization that include high-level information about how the business is "
 "performing."
 msgstr ""
+"*Übersichts-E-Mails* sind regelmäßige Speicherauszüge, die per E-Mail an "
+"Benutzer in der Organisation gesendet werden und detaillierte Informationen "
+"darüber enthalten, wie Ihr Betrieb läuft."

 #: ../../content/applications/general/companies/digest_emails.rst:8
 msgid ""
@@ -543,6 +546,10 @@ msgid ""
 ":menuselection:`Settings app --> Statistics section`, activate the "
 ":guilabel:`Digest Emails` feature, and click :guilabel:`Save`."
 msgstr ""
+"Um mit dem Versand von Übersichts-E-Mails zu beginnen, navigieren Sie "
+"zunächst zu :menuselection:`Einstellungen --> Bereich Statistik`, aktivieren"
+" die Funktion :guilabel:`Übersichts-E-Mails` und klicken auf "
+":guilabel:`Speichern`."

 #: ../../content/applications/general/companies/digest_emails.rst-1
 msgid "Digest Emails section inside General Settings."
@@ -551,30 +558,36 @@ msgstr "Abschnitt für Übersichts-E-Mails in den Allgemeinen Einstellungen."
 #: ../../content/applications/general/companies/digest_emails.rst:15
 msgid "A variety of settings can be configured for digest emails, such as:"
 msgstr ""
+"Für Übersichts-E-Mails kann eine Vielzahl von Einstellungen konfiguriert "
+"werden, wie z. B:"

 #: ../../content/applications/general/companies/digest_emails.rst:17
 msgid ""
 "Deciding which :abbr:`KPIs (key performance indicators)` are shared in the "
 "digest emails"
 msgstr ""
+"Entscheidung darüber, welche :abbr:`KPIs (Key Performance Indicators)` in "
+"den Übersichts-E-Mails mitgeteilt werden"

 #: ../../content/applications/general/companies/digest_emails.rst:18
 msgid "Determining how often digest emails are sent"
-msgstr ""
+msgstr "Festlegung, wie oft Übersichts-E-Mails gesendet werden"

 #: ../../content/applications/general/companies/digest_emails.rst:19
 msgid "Choosing who in the organization receives digest emails"
-msgstr ""
+msgstr "Auswahl, wer in der Organisation Übersichts-E-Mails erhält"

 #: ../../content/applications/general/companies/digest_emails.rst:20
 msgid "Creating custom digest email templates"
-msgstr ""
+msgstr "Erstellung benutzerdefinierter Übersichts-E-Mail-Vorlagen"

 #: ../../content/applications/general/companies/digest_emails.rst:21
 msgid ""
 "Adding additional :abbr:`KPIs (key performance indicators)` (*Studio* app "
 "required)"
 msgstr ""
+"Hinzufügung zusätzlicher :abbr:`KPIs (Key Performance Indicators)` "
+"(*Studio*-APp erforderlich)"

 #: ../../content/applications/general/companies/digest_emails.rst:24
 msgid ""
@@ -583,6 +596,10 @@ msgid ""
 ":abbr:`KPI (key performance indicator)` measurements across the Odoo "
 "database, and is sent daily to administrators."
 msgstr ""
+"Standardmäßig ist die :guilabel:`Übersichts-E-Mail` aktiviert, und "
+":guilabel:`Ihre periodische Übersicht von Odoo` dient als primäre Vorlage, "
+"die alle :guilabel:`KPI (key performance indicator)`-Messungen in der Odoo-"
+"Datenbank enthält und täglich an Administratoren gesendet wird."

 #: ../../content/applications/general/companies/digest_emails.rst:29
 msgid ""
@@ -590,6 +607,9 @@ msgid ""
 "testing-mode), the digest emails continue to send from the duplicate "
 "database, unless deactivated."
 msgstr ""
+"Wenn Sie Duplikate von Datenbanken erstellen, die über Sendefunktionen "
+"verfügen (nicht im Testmodus), werden die Übersichts-E-Mails weiterhin von "
+"der duplizierten Datenbank versendet, es sei denn, Sie deaktivieren sie."

 #: ../../content/applications/general/companies/digest_emails.rst:32
 msgid ""
@@ -598,10 +618,15 @@ msgid ""
 " by un-ticking the checkbox, and clicking :guilabel:`Save`. See the section "
 "on :ref:`digest-emails/deactivate`."
 msgstr ""
+"Um die Übersichts-E-Mails zu deaktivieren, gehen Sie zu "
+":menuselection:`Einstellungen --> Bereich Statistik`. Deaktivieren Sie dann "
+"die Funktion :guilabel:`Übersichts-E-mails`, indem Sie das Kontrollkästchen "
+"deaktivieren und auf :guilabel:`Speichern` klicken. Siehe den Abschnitt "
+":ref:`digest-emails/deactivate`."

 #: ../../content/applications/general/companies/digest_emails.rst:39
 msgid "Customize default digest email"
-msgstr ""
+msgstr "Standard-Übersichts-E-Mails anpassen"

 #: ../../content/applications/general/companies/digest_emails.rst:41
 msgid ""
@@ -610,17 +635,24 @@ msgid ""
 " Then, select :guilabel:`Your Odoo Periodic Digest`, and click on the "
 ":guilabel:`↗️ (External link)` icon, next to the drop-down menu selection."
 msgstr ""
+"Um die Standard-Übersichts-E-Mail (*Ihre periodische Übersicht von Odoo*) "
+"anzupassen, gehen Sie zu :menuselection:`Einstellungen --> Statistik --> "
+"Übersichts-E-Mail`, wählen Sie :guilabel:`Ihre periodische Übersicht von "
+"Odoo` und klicken Sie auf :guilabel:`↗️ (Externer Link)` neben der Dropdown-"
+"Auswahl."

 #: ../../content/applications/general/companies/digest_emails.rst:45
 msgid ""
 "A pop-up window appears, and presents a variety of editable settings, which "
 "include:"
 msgstr ""
+"Ein Pop-up-Fenster erscheint und zeigt eine Reihe bearbeitbarer "
+"Einstellungen an, wie zum Beispiel:"

 #: ../../content/applications/general/companies/digest_emails.rst:47
 #: ../../content/applications/general/companies/digest_emails.rst:179
 msgid ":guilabel:`Digest Name`: the name of the digest email."
-msgstr ""
+msgstr ":guilabel:`Übersichtstitel`: der Name der Übersichts-E-Mail."

 #: ../../content/applications/general/companies/digest_emails.rst:48
 #: ../../content/applications/general/companies/digest_emails.rst:180
@@ -629,6 +661,9 @@ msgid ""
 "(:guilabel:`Daily`, :guilabel:`Weekly`, :guilabel:`Monthly`, or "
 ":guilabel:`Quarterly`)."
 msgstr ""
+":guilabel:`Periodizität`: legen Sie fest, wie oft Übersichts-E-Mails "
+"gesendet werden (:guilabel:`Täglich`, :guilabel:`Wöchentlich`, "
+":guilabel:`Monatlich` oder :guilabel:`Vierteljährlich`)."

 #: ../../content/applications/general/companies/digest_emails.rst:50
 #: ../../content/applications/general/companies/digest_emails.rst:182
@@ -636,6 +671,8 @@ msgid ""
 ":guilabel:`Next Send Date`: the date on which the digest email will be sent "
 "again."
 msgstr ""
+":guilabel:`Nächstes Mailingdatum`: das Datum, an dem die Übersichts-E-Mail "
+"erneut gesendet wird."

 #: ../../content/applications/general/companies/digest_emails.rst:51
 #: ../../content/applications/general/companies/digest_emails.rst:183
@@ -645,6 +682,11 @@ msgid ""
 "indicates an active :abbr:`KPI (key performance indicator)` in the digest "
 "email. See the section on :ref:`digest-emails/kpis`."
 msgstr ""
+"Reiter :guilabel:`KPIs`: Aktivieren/deaktivieren Sie jeden berechneten "
+":abbr:`KPI (Key Performance Indicator)`, der in Übersichts-E-Mails "
+"erscheint. Ein angekreuztes Kästchen bedeutet, dass ein :abbr:`KPI (Key "
+"Performance Indicator)` in der Übersichts-E-Mail aktiv ist. Siehe den "
+"Abschnitt über :ref:`digest-emails/kpis`."

 #: ../../content/applications/general/companies/digest_emails.rst:54
 #: ../../content/applications/general/companies/digest_emails.rst:186
@@ -652,6 +694,9 @@ msgid ""
 ":guilabel:`Recipients` tab: add/remove users who receive the digest emails. "
 "See the section on :ref:`digest-emails/recipients`."
 msgstr ""
+"Reiter :guilabel:`Empfänger`: Fügen Sie Benutzer, die Übersichts-E-Mails "
+"erhalten sollten, hinzu oder entfernen Sie sie. Siehe den Abschnitt "
+":ref:`digest-emails/recipients`."

 #: ../../content/applications/general/companies/digest_emails.rst:58
 msgid ""
@@ -660,6 +705,10 @@ msgid ""
 "*Studio* need to be installed. See this section on :ref:`digest-"
 "emails/custom-kpi`."
 msgstr ""
+"Die :abbr:`KPIs (Key Performance Indicators)` können mit Odoo *Studio* "
+"angepasst werden. Wenn *Studio* installiert werden muss, fallen zusätzliche "
+"Kosten für das Datenbankabonnement an. Siehe diesen Abschnitt über "
+":ref:`digest-emails/custom-kpi`."

 #: ../../content/applications/general/companies/digest_emails.rst-1
 msgid "Customize default Digest Email settings and custom KPIs."
@@ -669,7 +718,7 @@ msgstr ""

 #: ../../content/applications/general/companies/digest_emails.rst:69
 msgid "Deactivate digest email"
-msgstr ""
+msgstr "Übersichts-E-Mail deaktivieren"

 #: ../../content/applications/general/companies/digest_emails.rst:71
 msgid ""
@@ -678,6 +727,11 @@ msgid ""
 ":guilabel:`Configure Digest Emails`. Then, select the desired digest email "
 "from the list that should be deactivated."
 msgstr ""
+"Um eine einzelne Übersichts-E-Mail manuell zu deaktivieren, navigieren Sie "
+"zunächst zu :menuselection:`Einstellungen --> Bereich Statistik`, und "
+"klicken Sie auf :guilabel:`Übersichts-E-Mails konfigurieren`. Wählen Sie "
+"dann die gewünschte Übersichts-E-Mail aus der Liste aus, die deaktiviert "
+"werden soll."

 #: ../../content/applications/general/companies/digest_emails.rst:75
 msgid ""
@@ -686,10 +740,14 @@ msgid ""
 "user from the mailing list. These buttons are located in the top menu, just "
 "above the :guilabel:`Digest Name`."
 msgstr ""
+"Klicken Sie dann auf :guilabel:`DEAKTIVIEREN FÜR ALLE`, um die Übersichts-E-"
+"Mail für alle zu deaktivieren, oder auf :guilabel:`MICH ABMELDEN`, um den "
+"angemeldeten Benutzer aus der Mailingliste zu entfernen. Diese Schaltflächen"
+" befinden sich im oberen Menü, direkt über dem :guilabel:`Übersichtstitel`."

 #: ../../content/applications/general/companies/digest_emails.rst:80
 msgid "Manually send digest email"
-msgstr ""
+msgstr "Übersichts-E-Mail manuell senden"

 #: ../../content/applications/general/companies/digest_emails.rst:82
 msgid ""
@@ -698,6 +756,12 @@ msgid ""
 "Then, select the desired digest email, and click :guilabel:`SEND NOW`. This "
 "button is located in the top menu, just above the :guilabel:`Digest Name`."
 msgstr ""
+"Um eine Übersichts-E-Mail manuell zu senden, navigieren Sie zunächst zu "
+":menuselection:`Einstellungen --> Bereich Statistik`, und klicken Sie auf "
+":guilabel:`Übersichts-E-Mails konfigurieren`. Wählen Sie dann die gewünschte"
+" Übersichts-E-Mail aus der Liste aus und klicken Sie auf :guilabel:`JETZT "
+"SENDEN`. Diese Schaltfläche befindet sich im oberen Menü, direkt über dem "
+":guilabel:`Übersichtstitel`."

 #: ../../content/applications/general/companies/digest_emails.rst:90
 msgid "KPIs"
@@ -709,17 +773,25 @@ msgid ""
 " digest email from the :guilabel:`KPIs` tab of the digest email template "
 "form."
 msgstr ""
+"Vorkonfigurierte :abbr:`KPIs (Key Performance Indicators)` können der "
+"Übersichts-E-Mail über den Reiter :guilabel:`KPIs` des Formulars für die "
+"Übersichts-E-Mail-Vorlage hinzugefügt werden."

 #: ../../content/applications/general/companies/digest_emails.rst:95
 msgid ""
 "First, navigate to :menuselection:`Settings app --> Statistics section`, and"
 " click :guilabel:`Configure Digest Emails`."
 msgstr ""
+"Navigieren Sie zunächst zu :menuselection:`Einstellungen --> Bereich "
+"Statistik`, und klicken Sie auf :guilabel:`Übersichts-E-Mails "
+"konfigurieren`."

 #: ../../content/applications/general/companies/digest_emails.rst:98
 msgid ""
 "Then, select the desired digest email, and open the :guilabel:`KPIs` tab."
 msgstr ""
+"Wählen Sie dann die gewünschte Übersichts-E-Mail und öffnen Sie den Reiter "
+":guilabel:`KPIs`."

 #: ../../content/applications/general/companies/digest_emails.rst:100
 msgid ""
@@ -728,76 +800,83 @@ msgid ""
 "After all :abbr:`KPIs (key performance indicators)` are added (or "
 "deselected), click :guilabel:`Save`."
 msgstr ""
+"Um einen :abbr:`KPI (Leistungskennzahlen)` zur Übersichts-E-Mail "
+"hinzuzufügen, markieren Sie das Kästchen neben der gewünschten :abbr:`KPI "
+"(Key Performance Indicator)`. Nachdem alle :abbr:`KPIs "
+"(Leistungskennzahlen)` hinzugefügt (oder abgewählt) wurden, klicken Sie auf "
+":guilabel:`Speichern`."

 #: ../../content/applications/general/companies/digest_emails.rst:104
 msgid ""
 "The following :abbr:`KPIs (key performance indicators)` are available in the"
 " :guilabel:`KPIs` tab on a digest email template form out-of-box in Odoo:"
 msgstr ""
+"Die folgenden :abbr:`KPIs (Leistungskennzahlen)` sind in Odoo im Reiter "
+":guilabel:`KPIs` im Formular einer Übersichts-E-Mail-Vorlage verfügbar:"

 #: ../../content/applications/general/companies/digest_emails.rst-1
 msgid "KPIs listed in the out-of-box digest email."
-msgstr ""
+msgstr "KPIs, die in der einsatzbereiten Übersichts-E-Mail aufgeführt sind."

 #: ../../content/applications/general/companies/digest_emails.rst:113
 msgid ":guilabel:`General`"
-msgstr ""
+msgstr ":guilabel:`Allgemein`"

 #: ../../content/applications/general/companies/digest_emails.rst:112
 msgid ":guilabel:`Connected Users`"
-msgstr ""
+msgstr ":guilabel:`Verbundene Benutzer`"

 #: ../../content/applications/general/companies/digest_emails.rst:113
 msgid ":guilabel:`Messages`"
-msgstr ""
+msgstr ":guilabel:`Nachrichten`"

 #: ../../content/applications/general/companies/digest_emails.rst:116
 msgid ":guilabel:`Project`"
-msgstr ""
+msgstr ":guilabel:`Projekt`"

 #: ../../content/applications/general/companies/digest_emails.rst:116
 msgid ":guilabel:`Open Tasks`"
-msgstr ""
+msgstr ":guilabel:`Offene Aufgaben`"

 #: ../../content/applications/general/companies/digest_emails.rst:119
 msgid ":guilabel:`Recruitment`"
-msgstr ""
+msgstr ":guilabel:`Personalbeschaffung`"

 #: ../../content/applications/general/companies/digest_emails.rst:119
 msgid ":guilabel:`Employees`"
-msgstr ""
+msgstr ":guilabel:`Mitarbeiter`"

 #: ../../content/applications/general/companies/digest_emails.rst:123
 msgid ":guilabel:`CRM`"
-msgstr ""
+msgstr ":guilabel:`CRM`"

 #: ../../content/applications/general/companies/digest_emails.rst:122
 msgid ":guilabel:`New Leads/Opportunities`"
-msgstr ""
+msgstr ":guilabel:`Neue Leads/Verkaufschancen`"

 #: ../../content/applications/general/companies/digest_emails.rst:123
 msgid ":guilabel:`Opportunities Won`"
-msgstr ""
+msgstr ":guilabel:`Gewonnene Verkaufschancen`"

 #: ../../content/applications/general/companies/digest_emails.rst:127
 msgid ":guilabel:`Sales`"
-msgstr ""
+msgstr ":guilabel:`Verkäufe`"

 #: ../../content/applications/general/companies/digest_emails.rst:126
 msgid ":guilabel:`All Sales`"
-msgstr ""
+msgstr ":guilabel:`Alle Verkäufe`"

 #: ../../content/applications/general/companies/digest_emails.rst:127
 msgid ":guilabel:`eCommerce Sales`"
-msgstr ""
+msgstr ":guilabel:`E-Commerce-Verkäufe`"

 #: ../../content/applications/general/companies/digest_emails.rst:130
 msgid ":guilabel:`Point of Sale`"
-msgstr ""
+msgstr ":guilabel:`Kassensystem`"

 #: ../../content/applications/general/companies/digest_emails.rst:130
 msgid ":guilabel:`POS Sales`"
-msgstr ""
+msgstr ":guilabel:`Kassenverkäufe`"

 #: ../../content/applications/general/companies/digest_emails.rst:135
 msgid ":guilabel:`Live Chat`"
@@ -805,35 +884,35 @@ msgstr ":guilabel:`Livechat`"

 #: ../../content/applications/general/companies/digest_emails.rst:133
 msgid ":guilabel:`% of Happiness`"
-msgstr ""
+msgstr ":guilabel:`% Zufriedenheit`"

 #: ../../content/applications/general/companies/digest_emails.rst:134
 msgid ":guilabel:`Conversations handled`"
-msgstr ""
+msgstr ":guilabel:`Verwaltete Unterhaltungen`"

 #: ../../content/applications/general/companies/digest_emails.rst:135
 msgid ":guilabel:`Time to answer (sec)`"
-msgstr ""
+msgstr ":guilabel:`Zeit zum Antworten (Sek.)`"

 #: ../../content/applications/general/companies/digest_emails.rst:138
 msgid ":guilabel:`Helpdesk`"
-msgstr ""
+msgstr ":guilabel:`Kundendienst`"

 #: ../../content/applications/general/companies/digest_emails.rst:138
 msgid ":guilabel:`Tickets Closed`"
-msgstr ""
+msgstr ":guilabel:`Geschlossene Tickets`"

 #: ../../content/applications/general/companies/digest_emails.rst:142
 msgid ":guilabel:`Invoicing`"
-msgstr ""
+msgstr ":guilabel:`Rechnungsstellung`"

 #: ../../content/applications/general/companies/digest_emails.rst:141
 msgid ":guilabel:`Revenue`"
-msgstr ""
+msgstr ":guilabel:`Umsatz`"

 #: ../../content/applications/general/companies/digest_emails.rst:142
 msgid ":guilabel:`Banks and Cash Moves`"
-msgstr ""
+msgstr ":guilabel:`Bank- und Bargeldtransaktionen`"

 #: ../../content/applications/general/companies/digest_emails.rst:147
 msgid "Recipients"
@@ -844,6 +923,8 @@ msgid ""
 "Digest email recipients are added from the :guilabel:`Recipients` tab of the"
 " digest email template form."
 msgstr ""
+"Die Empfänger von Übersichts-E-Mails werden im Reiter :guilabel:`Empfänger` "
+"des Formulars für die Übersichts-E-Mail-Vorlage hinzugefügt."

 #: ../../content/applications/general/companies/digest_emails.rst:152
 msgid ""
@@ -851,6 +932,10 @@ msgid ""
 "section`, and click :guilabel:`Configure Digest Emails`. Then, select the "
 "desired digest email, and open the :guilabel:`Recipients` tab."
 msgstr ""
+"Um einen Empfänger hinzuzufügen, navigieren Sie zunächst zu "
+":menuselection:`Einstellungen --> Bereich Statistik`, und klicken Sie auf "
+":guilabel:`Übersichts-E-Mails konfigurieren`. Wählen Sie dann die gewünschte"
+" Übersichts-E-Mail aus und öffnen Sie den Reiter :guilabel:`Empfänger`."

 #: ../../content/applications/general/companies/digest_emails.rst:156
 msgid ""
@@ -858,26 +943,37 @@ msgid ""
 "Recipients` pop-up window appears, with all available users to add as "
 "recipients."
 msgstr ""
+"Um einen Empfänger hinzuzufügen, klicken Sie auf :guilabel:`Zeile "
+"hinzufügen`. Daraufhin erscheint ein Pop-up-Fenster :guilabel:`Empfänger "
+"hinzufügen` mit allen verfügbaren Benutzern, die Sie als Empfänger "
+"hinzufügen können."

 #: ../../content/applications/general/companies/digest_emails.rst:159
 msgid ""
 "From the pop-up window, tick the checkbox next to the :guilabel:`Name` of "
 "the user(s), and click the :guilabel:`Select` button."
 msgstr ""
+"Aktivieren Sie im Pop-up-Fenster das Kontrollkästchen neben dem "
+":guilabel:`Name` des/der Benutzer(s) und klicken Sie auf die Schaltfläche "
+":guilabel:`Auswählen`."

 #: ../../content/applications/general/companies/digest_emails.rst:162
 msgid ""
 "To remove a user as a recipient, click the :guilabel:`❌ (remove)` icon to "
 "the far-right of the user listed in the :guilabel:`Recipients` tab."
 msgstr ""
+"Um einen Benutzer als Empfänger zu entfernen, klicken Sie auf das Symbol "
+":guilabel:`❌ (entfernen)` ganz rechts neben dem Benutzer im Reiter "
+":guilabel:`Empfänger`."

 #: ../../content/applications/general/companies/digest_emails.rst:165
 msgid "Click :guilabel:`Save` to implement the changes."
 msgstr ""
+"Klicken Sie auf :guilabel:`Speichern`, um die Änderungen zu übernehmen."

 #: ../../content/applications/general/companies/digest_emails.rst:170
 msgid "Create digest emails"
-msgstr ""
+msgstr "Übersichts-E-Mails erstellen"

 #: ../../content/applications/general/companies/digest_emails.rst:172
 msgid ""
@@ -885,12 +981,19 @@ msgid ""
 "Statistics section`, and click :guilabel:`Configure Digest Emails`. Then, "
 "click :guilabel:`Create` to create a new digest email."
 msgstr ""
+"Um eine neue Übersichts-E-Mail zu erstellen, navigieren Sie zu "
+":menuselection:`Einstellungen --> Abschnitt Statistik` und klicken Sie auf "
+":guilabel:`Übersichts-E-Mails konfigurieren`. Klicken Sie dann auf "
+":guilabel:`Neu`, um eine neue Übersichts-E-Mail zu erstellen."

 #: ../../content/applications/general/companies/digest_emails.rst:176
 msgid ""
 "A separate page, with a blank digest email template appears, and presents a "
 "variety of editable settings, including:"
 msgstr ""
+"Es wird eine separate Seite mit einer leeren Übersichts-E-Mail-Vorlage "
+"angezeigt, auf der Sie eine Reihe von Einstellungen vornehmen können, "
+"darunter auch die folgenden:"

 #: ../../content/applications/general/companies/digest_emails.rst:189
 msgid ""
@@ -898,6 +1001,9 @@ msgid ""
 ":guilabel:`Periodicity`, choose the desired :abbr:`KPIs (key performance "
 "indicators)`, and add :guilabel:`Recipients`, as needed."
 msgstr ""
+"Geben Sie der Übersichts-E-Mail einen :guilabel:`Übersichtstitel`, legen Sie"
+" :guilabel:`Periodizität` fest, wählen Sie die gewünschten :abbr:`KPIs "
+"(Leistungskennzahlen)` und fügen Sie bei Bedarf :guilabel:`Empfänger` hinzu."

 #: ../../content/applications/general/companies/digest_emails.rst:193
 msgid ""
@@ -905,52 +1011,71 @@ msgid ""
 " a selection in the :guilabel:`Digest Email` field, located in the "
 ":menuselection:`Settings app --> Statistics section`."
 msgstr ""
+"Nachdem Sie auf :guilabel:`Speichern` geklickt haben, steht Ihnen die neue "
+"benutzerdefinierte Übersichts-E-Mail als Auswahl im Feld "
+":guilabel:`Übersichts-E-Mail` zur Verfügung, das sich in der "
+":menuselection:`Einstellungen --> Bereich Statistik` befindet."

 #: ../../content/applications/general/companies/digest_emails.rst:199
 msgid "Custom KPIs with Odoo Studio"
-msgstr ""
+msgstr "Benutzerdefinierte KPIs mit Osoo Studio"

 #: ../../content/applications/general/companies/digest_emails.rst:201
 msgid ""
 "The :abbr:`KPIs (key performance indicators)` on a digest email template "
 "form, in the :guilabel:`KPIs` tab, can be customized using Odoo *Studio*."
 msgstr ""
+"Die :abbr:`KPIs (Leistungskennzahlen)` auf einem Formular für eine "
+"Übersichts-E-Mail-Vorlage, im Reiter :guilabel:`KPIs`, können mit Odoo "
+"*Studio* angepasst werden."

 #: ../../content/applications/general/companies/digest_emails.rst:205
 msgid ""
 "Additional costs to the database subscription are incurred, should Odoo "
 "*Studio* need to be installed."
 msgstr ""
+"Es fallen zusätzliche Kosten für das Datenbankabonnement an, wenn Odoo "
+"*Studio* installiert werden muss."

 #: ../../content/applications/general/companies/digest_emails.rst:208
 msgid ""
 "To begin, click the :guilabel:`🛠️ (tools)` icon in the top-right of the "
 "screen. This is the link to the Odoo *Studio* application."
 msgstr ""
+"Um zu beginnen, klicken Sie auf das Symbol :guilabel:`🛠️ (Tools)` oben "
+"rechts auf dem Bildschirm. Dies ist der Link zu Odoo *Studio*."

 #: ../../content/applications/general/companies/digest_emails.rst:211
 msgid ""
 "In order to create additional fields, create two fields on the digest "
 "object:"
 msgstr ""
+"Um zusätzliche Felder zu erstellen, müssen Sie zwei Felder für das "
+"Übersichtsobjekt anlegen:"

 #: ../../content/applications/general/companies/digest_emails.rst:213
 msgid ""
 "Create a boolean field called `kpi_myfield`, and display it in the "
 ":guilabel:`KPIs` tab."
 msgstr ""
+"Erstellen Sie ein boolesches Feld mit dem Namen `kpi_myfield` und zeigen Sie"
+" es im Reiter :guilabel:`KPIs` an"

 #: ../../content/applications/general/companies/digest_emails.rst:214
 msgid ""
 "Create a computed field called `kpi_myfield_value` that computes the "
 "customized :abbr:`KPI (key performance indicator)`."
 msgstr ""
+"Erstellen Sie ein berechnetes Feld mit dem Namen `kpi_myfield_value`, das "
+"die benutzerdefinierte :abbr:`KPI (Leistungskennzahl)` berechnet"

 #: ../../content/applications/general/companies/digest_emails.rst:216
 msgid ""
 "Select the :abbr:`KPIs (key performance indicators)` in the :guilabel:`KPIs`"
 " tab."
 msgstr ""
+"Wählen Sie im Reiter :guilabel:`KPIs (Leistungskennzahlen)` die "
+":abbr:`KPIs`."

 #: ../../content/applications/general/companies/digest_emails.rst:219
 msgid ""
@@ -959,6 +1084,10 @@ msgid ""
 "for the `digest.py` file, which guides the programmer in the coding of the "
 "computed field."
 msgstr ""
+"Hier ist der `Quellcode "
+"<https://github.com/odoo/odoo/blob/15.0/addons/digest/models/digest.py>`_ "
+"für die Datei `digest.py`, die den Programmierer zur Codierung des "
+"berechneten Felds führt."

 #: ../../content/applications/general/companies/digest_emails.rst:224
 msgid ""
@@ -966,6 +1095,10 @@ msgid ""
 "three-dot :guilabel:`(kebab)` menu to edit this view. Either click "
 ":guilabel:`EDIT LIST VIEW` or :guilabel:`EDIT FORM VIEW` to modify this tab."
 msgstr ""
+"Sie können auch im Reiter :guilabel:`Empfänger` und dann auf das vertikale "
+"Drei-Punkte-Menü :guilabel:`(Kebab)` klicken, um diese Ansicht zu "
+"bearbeiten. Klicken Sie entweder auf :guilabel:`LISTENANSICHT BEARBEITEN` "
+"oder auf :guilabel:`FORMULARANSICHT BEARBEITEN`, um diesen Reiter zu ändern."

 #: ../../content/applications/general/companies/digest_emails.rst:229
 msgid "Computed values reference table"
@@ -1806,13 +1939,16 @@ msgstr ""

 #: ../../content/applications/general/developer_mode.rst:5
 msgid "Developer mode (debug mode)"
-msgstr ""
+msgstr "Entwicklermodus (Fehlerbeseitigungsmodus)"

 #: ../../content/applications/general/developer_mode.rst:7
 msgid ""
 "The developer mode, also known as debug mode, unlocks access to advanced "
 ":ref:`tools and settings <developer-mode/tools>` in Odoo."
 msgstr ""
+"Der Entwicklermodus, auch bekannt als Fehlerbeseitungsmodus, schaltet den "
+"Zugriff auf die erweiterten :ref:`Tools und Einstellungen <developer-"
+"mode/tools>` in Odoo frei."

 #: ../../content/applications/general/developer_mode.rst:11
 msgid ""
@@ -1820,6 +1956,10 @@ msgid ""
 "considered advanced and may have associated risks. Only use them if you "
 "understand the implications and are confident in your actions."
 msgstr ""
+"Seien Sie vorsichtig, denn einige Entwickler-Tools und technische "
+"Einstellungen gelten als fortgeschritten und können mit Risiken verbunden "
+"sein. Verwenden Sie sie nur, wenn Sie die Auswirkungen verstehen und sicher "
+"sind, dass Sie richtig handeln."

 #: ../../content/applications/general/developer_mode.rst:16
 msgid ""
@@ -1828,6 +1968,11 @@ msgid ""
 "code, and with :ref:`tests assets <frontend/framework/tests_debug_mode>`, "
 "which are used to run test tours."
 msgstr ""
+"Der Entwicklermodus ist auch mit :ref:`Assets "
+"<frontend/framework/assets_debug_mode>` verfügbar, die zur Fehlerbeseitung "
+"von JavaScript-Code verwendet werden, und mit :ref:`Test-Assets "
+"<frontend/framework/tests_debug_mode>`, die zum Ausführen von Testführungen "
+"verwendet werden."

 #: ../../content/applications/general/developer_mode.rst:23
 msgid "Activation"
@@ -1839,6 +1984,9 @@ msgid ""
 ":guilabel:`Developer Tools` section, and click :guilabel:`Activate the "
 "developer mode`."
 msgstr ""
+"Um ihn zu aktivieren, öffnen Sie die :guilabel:`Einstellungen`, scrollen Sie"
+" nach unten zum Abschnitt :guilabel:`Entwicklertools` und klicken Sie auf "
+":guilabel:`Entwicklermodus aktivieren`."

 #: ../../content/applications/general/developer_mode.rst:28
 msgid ""
@@ -1850,7 +1998,7 @@ msgstr ""

 #: ../../content/applications/general/developer_mode.rst-1
 msgid "Activating the developer mode in the Settings app"
-msgstr ""
+msgstr "Aktivierung des Entwicklermodus in den Einstellungen"

 #: ../../content/applications/general/developer_mode.rst:33
 msgid ""
@@ -1859,22 +2007,31 @@ msgid ""
 "`https://example.odoo.com/web?debug=1#action=menu&cids=1`). To deactivate "
 "it, use `?debug=0` instead."
 msgstr ""
+"Um den Entwicklermodus **von einer beliebigen Stelle in der Datenbank** aus "
+"zu aktivieren, fügen Sie `?debug=1` an die URL nach `/web` an (z. B. "
+"`https://example.odoo.com/web?debug=1#action=menu&cids=1`). Um ihn zu "
+"deaktivieren, verwenden Sie stattdessen `?debug=0`."

 #: ../../content/applications/general/developer_mode.rst:37
 msgid ""
 "Use `?debug=assets` to activate the developer mode with assets and "
 "`?debug=tests` to activate it with tests assets."
 msgstr ""
+"Verwenden Sie `?debug=assets`, um den Entwicklermodus mit Assets zu "
+"aktivieren und `?debug=tests`, um ihn mit Test-Assets zu aktivieren."

 #: ../../content/applications/general/developer_mode.rst:41
 msgid ""
 "Open the **command palette** by pressing `Ctrl + K` or `Cmd ⌘ + K`, then "
 "type `debug` to activate the developer mode with assets or deactivate it."
 msgstr ""
+"Öffnen Sie die **Befehlspalette**, indem Sie `Strg + K` oder `Cmd ⌘ + K` "
+"drücken. Geben Sie dann `debug` ein, um den Entwicklermodus mit Assets zu "
+"aktivieren oder zu deaktivieren."

 #: ../../content/applications/general/developer_mode.rst:44
 msgid "Browser extension"
-msgstr ""
+msgstr "Browser-Erweiterung"

 #: ../../content/applications/general/developer_mode.rst:46
 msgid ""
@@ -1885,10 +2042,17 @@ msgid ""
 "debug/hmdmhilocobgohohpdpolmibjklfgkbi>`_ and `Firefox Add-ons "
 "<https://addons.mozilla.org/firefox/addon/odoo-debug/>`_."
 msgstr ""
+"Die Browser-Erweiterung `Odoo Fehlerbeseitung "
+"<https://github.com/Droggol/OdooDebug>`_ fügt ein Symbol hinzu, mit dem Sie "
+"den Entwicklermodus in der Symbolleiste des Browsers ein- oder ausschalten "
+"können. Sie ist im `Chrome Web Store "
+"<https://chromewebstore.google.com/detail/odoo-"
+"debug/hmdmhilocobgohohpdpolmibjklfgkbi>`_ und `Firefox Add-ons "
+"<https://addons.mozilla.org/firefox/addon/odoo-debug/>`_ erhältlich."

 #: ../../content/applications/general/developer_mode.rst:54
 msgid "Developer tools and technical menu"
-msgstr ""
+msgstr "Entwicklertools und technisches Menü"

 #: ../../content/applications/general/developer_mode.rst:56
 msgid ""
@@ -1898,10 +2062,16 @@ msgid ""
 " filters, or actions. The options available depend on where the menu is "
 "accessed from."
 msgstr ""
+"Sobald der Entwicklermodus aktiviert ist, können Sie auf die Entwicklertools"
+" zugreifen, indem Sie auf das Symbol :icon:`fa-bug` :guilabel:`(bug)` "
+"klicken. Das Menü enthält Tools, die für das Verständnis oder die "
+"Bearbeitung technischer Daten nützlich sind, wie z. B. das Feld einer "
+"Ansicht, Filter oder Aktionen. Die verfügbaren Optionen hängen davon ab, von"
+" wo aus das Menü aufgerufen wird."

 #: ../../content/applications/general/developer_mode.rst-1
 msgid "Accessing the developer tools"
-msgstr ""
+msgstr "Zugriff auf die Entwicklertools"

 #: ../../content/applications/general/developer_mode.rst:64
 msgid ""
@@ -1909,10 +2079,14 @@ msgid ""
 ":guilabel:`Settings` app. It contains advanced database settings, such as "
 "ones related to the database structure, security, actions, etc."
 msgstr ""
+"Datenbankadministratoren können das technische Menü über die "
+":guilabel:`Einstellungen` aufrufen. Es enthält erweiterte "
+"Datenbankeinstellungen, z. B. für die Datenbankstruktur, Sicherheit, "
+"Aktionen usw."

 #: ../../content/applications/general/developer_mode.rst-1
 msgid "Accessing the technical menu"
-msgstr ""
+msgstr "Zugriff auf das technische Menü"

 #: ../../content/applications/general/email_communication.rst:5
 msgid "Email communication"
@@ -5755,6 +5929,8 @@ msgid ""
 "The :guilabel:`System Parameters` can be accessed by activating the "
 ":ref:`developer mode <developer-mode>`."
 msgstr ""
+"Auf die :guilabel:`Systemparameter` können Sie zugreifen, indem Sie den "
+":ref:`Entwicklermodus <developer-mode>` aktivieren."

 #: ../../content/applications/general/email_communication/mailjet_api.rst:216
 msgid ""
@@ -5776,10 +5952,12 @@ msgstr "Geolokalisierung"
 msgid ""
 "You can locate contacts or places and generate routes on a map in Odoo."
 msgstr ""
+"Sie können in Odoo Kontakte oder Orte lokalisieren und Routen auf einer "
+"Karte erstellen."

 #: ../../content/applications/general/integrations/geolocation.rst-1
 msgid "Map displaying a contact's location."
-msgstr ""
+msgstr "Karte mit dem Standort eines Kontakts."

 #: ../../content/applications/general/integrations/geolocation.rst:10
 msgid ""
@@ -5787,6 +5965,10 @@ msgid ""
 ":guilabel:`Integrations`, section, activate :guilabel:`Geo Localization`. "
 "Then, choose between using the OpenStreetMap or Google Places API."
 msgstr ""
+"Um die Funktion zu nutzen, öffnen Sie die :guilabel:`Einstellungen` und "
+"aktivieren Sie unter dem Abschnitt :guilabel:`Integrationen` die Option "
+":guilabel:`Geolokalisierung`. Wählen Sie dann zwischen der Verwendung der "
+"API von OpenStreetMap oder Google Places."

 #: ../../content/applications/general/integrations/geolocation.rst:14
 msgid "**OpenStreetMap**"
@@ -5797,6 +5979,9 @@ msgid ""
 "OpenStreetMap is a free, open geographic database updated and maintained by "
 "volunteers. To use it, select :guilabel:`Open Street Map`."
 msgstr ""
+"OpenStreetMap ist eine kostenlose, offene geografische Datenbank, die von "
+"Freiwilligen aktualisiert und gepflegt wird. Um sie zu nutzen, wählen Sie "
+":guilabel:`Open Street Map`."

 #: ../../content/applications/general/integrations/geolocation.rst:20
 msgid ""
@@ -5804,10 +5989,13 @@ msgid ""
 "community <https://www.openstreetmap.org/fixthemap>`_ to fix any issues "
 "encountered."
 msgstr ""
+"OpenStreetMap ist möglicherweise nicht immer genau. Sie können der "
+"`OpenStreetMap-Community <https://www.openstreetmap.org/fixthemap>`_ "
+"beitreten, um aufgetretene Probleme zu beheben."

 #: ../../content/applications/general/integrations/geolocation.rst:23
 msgid "**Google Places API map**"
-msgstr ""
+msgstr "**Karte der Google Places API**"

 #: ../../content/applications/general/integrations/geolocation.rst:25
 msgid ""
@@ -5815,27 +6003,35 @@ msgid ""
 "points of interest. It supports location-based features like search, "
 "navigation, and recommendations."
 msgstr ""
+"Die Google-Places-API-Karte bietet detaillierte Informationen zu Orten, "
+"Unternehmen und Interessen. Sie unterstützt ortsbezogene Funktionen wie "
+"Suche, Navigation und Empfehlungen."

 #: ../../content/applications/general/integrations/geolocation.rst:29
 msgid ""
 "Using the Google Places API could require `payment to Google "
 "<https://mapsplatform.google.com/pricing/>`_."
 msgstr ""
+"Die Verwendung der Google Places API könnte eine `Zahlung an Google "
+"<https://mapsplatform.google.com/pricing/>`_ erfordern."

 #: ../../content/applications/general/integrations/geolocation.rst:32
 msgid ""
 "To use it, select :guilabel:`Google Place Map` and enter your :ref:`API Key "
 "<address_autocomplete/generate_api_key>`."
 msgstr ""
+"Um es zu verwenden, wählen Sie :guilabel:`Google Place Map` und geben Sie "
+"Ihren :ref:`API-Schlüssel <address_autocomplete/generate_api_key>` ein."

 #: ../../content/applications/general/integrations/geolocation.rst-1
 msgid "Google Places API key"
-msgstr ""
+msgstr "API-Schlüssel von Google Places"

 #: ../../content/applications/general/integrations/geolocation.rst:39
 msgid ""
 ":doc:`/applications/websites/website/configuration/address_autocomplete`"
 msgstr ""
+":doc:`/applications/websites/website/configuration/address_autocomplete`"

 #: ../../content/applications/general/integrations/mail_plugins.rst:5
 msgid "Mail Plugins"
@@ -11483,7 +11679,7 @@ msgstr ""

 #: ../../content/applications/general/users.rst:109
 msgid "To resolve the issue, either:"
-msgstr ""
+msgstr "Zur Lösung des Problems:"

 #: ../../content/applications/general/users.rst:111
 msgid ""
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Tom Aarab (toaa)	1ab9261c32	[IMP] mexico: broken url Removing a dead URL taskid-3636231	2024-07-25 10:15:11 +02:00
Tiffany Chang (tic)	b37934a7d9	[I18N] *: export latest terms As per usual, leave off developer.pot and contributing.pot since we don't translate them (not useful, can't really contribute to/dev in Odoo without knowing English) closes odoo/documentation#10304 Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>	2024-07-23 11:47:22 +00:00
Felicious	1c927fa911	[IMP] inventory: refactor WH and locations closes odoo/documentation#10238 Signed-off-by: Felicia Kuan (feku) <feku@odoo.com> Co-authored-by: Jess Rogers <104637850+jero-odoo@users.noreply.github.com> Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>	2024-07-20 03:01:47 +00:00
Odoo Translation Bot	e0ab879c54	[I18N] *: export 16.0 source terms	2024-07-20 02:37:23 +00:00
sovi-odoo	c84d525452	[IMP] accounting/l10n: tell users to install l10n_fr_invoice_addr In Odoo 15.0, an extra module is necessary to conform to the french legislation. This will tell users to install it. This is a forward port of odoo/documentation#9820 task-3856826 closes odoo/documentation#10025 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> Co-authored-by: toaa-odoo <toaa@odoo.com>	2024-07-16 15:57:11 +00:00
Donatienne (dopi)	fda2534a74	[IMP] website: translations taskid-3617120 closes odoo/documentation#9945 Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>	2024-07-16 09:22:39 +00:00
Felicious	21779a5eb6	[IMP] inventory: sendcloud shipping rules closes odoo/documentation#10112 Signed-off-by: Samuel Lieber (sali) <sali@odoo.com> Co-authored-by: larm-odoo <121518652+larm-odoo@users.noreply.github.com> Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>	2024-07-15 19:14:14 +00:00
Odoo Translation Bot	28634eca60	[I18N] *: export 15.0 source terms	2024-07-13 02:41:59 +00:00
“Audrey	13ddb59da9	[ADD] Studio: approval rules task-3553095 closes odoo/documentation#10029 Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>	2024-07-09 10:34:00 +00:00
Felicious	7566002f49	[IMP] inventory: bpost customer accounts closes odoo/documentation#10100 X-original-commit: `4a527db915` Signed-off-by: Samuel Lieber (sali) <sali@odoo.com> Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>	2024-07-09 00:08:38 +00:00
Odoo Translation Bot	10c7321ca4	[I18N] *: export 15.0 source terms	2024-07-08 20:11:52 +00:00
KC (ksc)	03f5c0660e	[IMP] sales: added important admonition to amazon docs closes odoo/documentation#9780 Signed-off-by: Kevin Scannell (ksc) <ksc@odoo.com>	2024-07-05 20:51:57 +00:00
Felicious	58990cb4c6	[FIX] inventory: UoM redirect rules closes odoo/documentation#10054 Signed-off-by: Felicia Kuan (feku) <feku@odoo.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>	2024-07-04 20:20:55 +00:00
“Dallas”	8ebc2d20b1	[FIX] german localization: Fixed broken GoBD link If merged, this commit will replace the broken GoBD link with the correct link. task ID: 4034487 closes odoo/documentation#10076 X-original-commit: `0e783b0dfa` Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com> Signed-off-by: Dallas Dean (dade) <dade@odoo.com>	2024-07-04 13:52:40 +00:00
xpl-odoo	50b8a2100d	[FIX] sign: line break after 100 characters closes odoo/documentation#10068 Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>	2024-07-03 21:43:44 +00:00
xpl-odoo	fa64368f21	[ADD] sign: legality task-4008122 closes odoo/documentation#10027 Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>	2024-07-02 15:17:46 +00:00
Odoo Translation Bot	363483c4aa	[I18N] Update translation terms from Transifex	2024-06-30 01:40:52 +02:00
Donatienne (dopi)	afe32dfbeb	[IMP] General: Change language taskid-3964562 closes odoo/documentation#9670 Signed-off-by: Donatienne Pirlot (dopi) <dopi@odoo.com>	2024-06-24 09:03:44 +00:00
Odoo Translation Bot	31485036f3	[I18N] Update translation terms from Transifex	2024-06-23 01:40:56 +02:00
Adrien Widart (awt)	95e348eb51	[IMP] supported_versions: end of saas-16.4 closes odoo/documentation#9890 X-original-commit: `37ca3f1917` Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> Signed-off-by: Adrien Widart (awt) <awt@odoo.com>	2024-06-22 08:37:23 +00:00
Tiffany Chang (tic)	a727f25be8	[I18N] *: export latest terms As per usual, leave off developer.pot and contributing.pot since we don't translate them (not useful, can't really contribute to/dev in Odoo without knowing English) closes odoo/documentation#9882 X-original-commit: `89c308c` Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>	2024-06-21 17:13:48 +00:00
XPL	8e143196f1	[IMP] upgrade: remove ticket go-live mention The phrase is confusing and leads customers to contact support to carry out the upgrade for them. closes odoo/documentation#9883 X-original-commit: `51323fba44` Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>	2024-06-21 15:59:49 +00:00
guillaume gallant (guga)	0e6358b6cb	[IMP] point_of_sale: improve text and replace pictures for Vantiv task-3005157 closes odoo/documentation#9858 X-original-commit: `3d5ff64bab` Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com> Signed-off-by: Guillaume Gallant (guga) <guga@odoo.com>	2024-06-21 06:47:42 +00:00
Donatienne (dopi)	eb1eb38cce	[IMP] website: cookies bar taskid-3961318 closes odoo/documentation#9571 Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>	2024-06-18 16:06:44 +00:00
Odoo Translation Bot	df99292384	[I18N] Update translation terms from Transifex	2024-06-16 01:40:50 +02:00
Audrey (auva)	95dd9329de	[FIX] voip: broken contact link Changed https://www.axivox.com/contact into https://www.axivox.com/en/contact as it didn't exist (anymore). closes odoo/documentation#9759 X-original-commit: `f9ab7b716b` Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>	2024-06-11 15:44:26 +00:00
Loredana Perazzo	1394d4813a	[IMP] pos: remove Epson TM-20 from list of compatible task-3925551 closes odoo/documentation#9652 X-original-commit: `2e47b6a600` Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>	2024-06-11 08:57:07 +00:00
Odoo Translation Bot	6f48100e70	[I18N] Update translation terms from Transifex	2024-06-09 01:40:57 +02:00
Felicious	f39139aea9	[ADD] inventory: bpost closes odoo/documentation#9720 X-original-commit: `91a2973306` Signed-off-by: Felicia Kuan (feku) <feku@odoo.com> Co-authored-by: hojo-odoo <123424465+hojo-odoo@users.noreply.github.com> Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>	2024-06-08 01:32:44 +00:00
Felicious	dc0dec9d65	[IMP] inventory: reserve full vs partial packaging closes odoo/documentation#9646 X-original-commit: `2cebcb0cda` Signed-off-by: Felicia Kuan (feku) <feku@odoo.com> Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>	2024-06-07 21:29:42 +00:00
Serge Bayet (seba)	c770eb5618	[ADD] administration: neutralized databases doc This commit updates the documentation for neutralized databases to include information about how search engine indexing is prevented for these databases. task-3895772 closes odoo/documentation#9653 Signed-off-by: Serge Bayet (seba) <seba@odoo.com>	2024-06-07 14:01:19 +00:00
Donatienne (dopi)	6078b9107c	[IMP] documents: links to tutorials to be updated taskid-3960925 closes odoo/documentation#9671 Signed-off-by: Donatienne Pirlot (dopi) <dopi@odoo.com>	2024-06-07 10:40:23 +00:00